The 7 LED's:

There is a heartbeatimplemented with the LEDs: All LEDs flash for a short moment about every 1 second if there is no antenna connected. This is to inform that the Beast is anyway active and working, waiting for a signal.
1 Channel Firmware 1.31

green

red

red

green

blue

yellow

green

DF-0, DF-4, DF-5

DF-11

DF-17,DF-18

DF-20,DF-21

Output overload

RS232 transfer

Power On

2 Channel Firmware 1.31

green

red

green

red

blue

yellow

green

DF-11
Channel 1

DF-17, DF-18
Channel 1

DF-11
Channel 2

DF-17, DF-18
Channel 2

Output overload

RS232 transfer

Power On

DF-xx Downlinkformats receiving.


Output overload: The Fifo-Buffer of the Beast overruns, the user reads data to slowly. To
solve this situation:
Always have DIP#8 in ON position in order to enable RTS handhake. If  you see the blue LED flashing for longer periods, there are several ways to solve this:
1. Disable Mode-A/C decoding if you are not interested in this data, e.g. for Beamfinder and Beamfinder plus -> set DIP#10 to OPEN
2. Mask all DF-0, DF-4, and DF-5 frames. These are reduandant to DF-20, DF-21 and DF-17. -> set DIP#7 to ON
3. If that still does not help, only decode DF-11 and DF-17 -> set DIP#4 to ON

The 10 Dip-Switches:

Baudrate

SW1

SW2

Usage

MBit/sec

open

open

USB serial interface  (with USB over FT232R only)

921600 Bit/sec

on

open

Lantronix Xport and FT232R USB

230400 Bit/sec

open

on

Lantronix Xport interface

115200 Bit/sec

on

on

Bluetooth

Note that depending on your local traffic rate the interface baudrate is the real bottleneck of your system! So if you see a significant miss here, first introduce the DF-0/4/5 filter with DIP #7, and if that does not help, switch on DF17/DF11 filter with DIP#4.

The Mode-S frames capability of the different baudrates is about

 


Baudrate

rough number of Mode-S Frames per Second max. in UDP Format

rough numberMode-S Frames per Second max. in Binary Format

3 MBit

>2000

>4000

921600 Bit/Sec

1100

2200

230400 Bit/Sec

550

1100

115200 Bit/Sec

300

600


Mode-AC frames
are transmitted with lower priority, so if your interface is already conguested with Mode-S frames, you will see less or no Mode-AC frames.

The Beast has 2 output-formats:

Output -Format

SW3

Usage

AVR Format

open

Output in AVR-Format (Formatdescription see Dip5)

Binär Format

on

Output in Binary-Format

The Binary-Format knows 3 different Formatlength every frame starts with  hex=1A.

Format Mode A/C

1

6 Byte MLAT-Time, 1 Byte Signalstrength, 2 Byte Mode A/C Squawk oder Altitude

Format Kurz-ADS-B

2

6 Byte MLAT-Time, 1 Byte Signalstrength, 7 Byte Mode S kurze Downlinkformate

Format Lang-ADS-B

3

6 Byte MLAT-Time, 1 Byte Signalstrength, 14 Byte Mode S lange Downlinkformate

Selected Binaryformat ignores MLAT-Timer (set with Dip5). If output in AVR-Format with MLAT-Time needed, then Dip3 open and Dip5 on.

only DF-17

SW4

Usage

Alle Standard DF's

open

The beast decodes all ADS-B Downlinkformat:
DF-0, DF-4, DF-5, DF-11, DF-16, DF-17, DF-18, DF20 und DF-21
Note: DF-0, DF-4 and DF-5 can extra be filtered off with Dip7  on

only DF-17

on

Only Downlinkformats: DF-11 und DF-17 are decoded.

 

MLAT -Format

SW5

Usage

MLAT off

open

No MLAT-output, data frames are initiated with '*' AVR-Format

MLAT on

on

Yes, MLAT-output with 12MHz as 6-Byte-clock every frame is initiated with '@'

 AVR Format if  Dip3 is open:

MLAT

SW5

Format

off

open

Standard output:
 

56 Bit Mode-S frames:

*02E99619FACDAE;

112 Bit Mode-S frames:

*8D3C5EE69901BD9540078D37335F;

Mode-A/C frames:

*7700; (Note: Mode-A/C Framesdaten are octal)

Example:
*02E99619FACDAE;
*8D3C5EE69901BD9540078D37335F;
*7700;

on

on

Format with MLAT timedate:

56 Bit Mode-S frames:

@016CE3671C745DFFE7AB7BFCAB;

112 Bit Mode-S frames:

@016CE3671AA88D00199A8BB80030A8000628F400;

Mode-A/C frames:

@016CE3671C747700;

Example:
@016CE3671C7423FFE7AB7BFCAB;
@016CE3671AA8A800199A8BB80030A8000628F400;
@016CE3671C747700;

 

CRC disable

SW6

Usage

CRC with DF-11 and DF-17

open

DF-17 frames are checked for a total match of the CRC
DF-11 frames are checked for all but the lower 6 bits, which are the Interrogator ID and not usable for check.

No CRC check

on

No CRC check is done for any frame. This can be used in conjunction with the CRC and  biterror correction PC software driver or Planeplotter's FEC correction in order to get a higher frame rate.

 

 

DF-0/DF-4/DF-5 Filter

SW7

Usage

No Filter

open

All DF-0/4/5 are decoded

AlleDF-0/4/5 Frames

on

All DF-0 und DF4 und DF5 are filtered off

 

RTS Handshake

SW8

Usage

No Handshake

open

As long as you do not experience any data loss, hardware handshake is not necessary to be enabled.

Handshake on

on

In case of a high frame rate and/or togehter with a slow PC, it might be useful to configure and enable RTS hardware handshake.
It should be mentioned already here that this handshake is acutally not done between Planeplotter and the FPGA, much better it is done exactly between the interface device and the FPGA.

 

 

1 Bit FEC disable

SW9

Usage

Forward error correction enable

open

The CRC checksum of Mode-S frames allows a correction of up to 5 bits. 1 Bit errors are those appearing most often and are corrected with this feature by the Beast.

disable

on

There is no bit error correction done in the Beast.

 

 

Mode-A/C decoding

SW10

Usage

disabled

open

No Mode-A/C frames are decoded by the Beast

enabled

on

.Mode-S beast also decodes Mode-A/C frames
Frame format see DIP#3