©

RFbeam Microwave GmbH | Schuppisstrasse 7 | CH-9016 St. Gallen | www.rfbeam.ch | K-MD2 Engineering Sample | data sheet

07/2018 – Revision A | Page 13/23

RADAR SYSTEM

For the processing of the digital signals, the radar

uses a Zynq XC7Z020 system on a chip (SoC). The

SoC is mounted on a TE720 adapter board from

Trenz electronic. It mainly consists out of a processing

system (PS) part, which contains two Cortex-A9 pro-

cessors, and the programmable logic (PL) part, which

contains the FPGA part. A Linux operating system is

running on the processing system.

Start-Up

The start-up script

/etc/init.d/rcS runs au-

tomatically when the radar is powered. This script

performs the following steps:

1. Mounts the file systems in

/etc/fstab

2. Look for

/mnt/rcS and refer to this script

if it is present

3. Start the Telnet daemon

4. Start the FTP daemon

5. Start the SSH daemon

6. Run the file

/mnt/init.sh if it is pre-

sent, otherwise

7. Run the file

/opt/init.sh

Users should put any additional start-up actions in the

file

/mnt/init.sh:

cp /opt/init.sh /mnt/init.sh

vi /mnt/init.sh

The default

/opt/init.sh script will display the

software version on the console and start the sensor

server running in the background.

Changing anything on the file system

can result in an irreparable state where

the radar has to be re-programmed by

RFbeam Microwave GmbH.

Network Interface

The radar uses a static IP address (default

192.168.16.2 / 255.255.255.0). The sensor server

listens for connections on the specified TCP port

(default 6172). The radar will continually send mes-

sages to any connected client and accept command

messages at any time. Command messages are

processed between frames.

The messages generated by the radar can exceed

the speed of the TCP/IP stack. When this hap-

pens the frame rate of the radar will drop so that all

messages are transmitted. This can be prevented

by limiting the type of messages transmitted using

the DSF0 command.

The IP address and netmask can be changed by

Telnet using the ifconfig command:

ifconfig eth0 192.168.1.5

netmask 255.255.255.0

Serial Interface

Specification

Value

Voltage

3.3V

Baudrate

115200

Data bits

8

Stop bits

1

Parity

No

Hardware flow control

No

Table 3: Serial interface specifications

The radar continually sends messages via the serial

interface and accepts command messages at any

time. Command messages are processed between

frames. Serial commands are processed after net-

work commands.

The messages generated by the radar can exceed the

speed of the serial interface. When this happens the

frame rate of the radar will drop so that all messages

are transmitted. This can be prevented by limiting the

maximum size of messages sent via the serial inter-

face with the

serial_max_length configuration

key. Messages exceeding this length will not be sent

via the serial interface, but they will still be sent via the

network interface.

Logging

The sensor server outputs messages to the console

and a log file (/opt/sensor_server.log). The level of the

messages can be different on the console and in the

log file. The levels are:

Level Description

0

No messages (silent operation)

1

Errors (These are usually fatal, and the software will exit)

2

Warnings (These are usually non-fatal, but are not expected)

3

Notes (These are expected and should only occur at start-up

or initialisation)

4

Trace (These messages provide additional information to the user)

5

Debug (These messages provide information

to development engineers)

Table 4: Level of log messages

The level specified includes all messages from lower

levels. The default level for the log file is Notes and

the default level for the console is Trace. Care should

be taken not to set the level for the log file too high in

case the file system runs out of space.