Mode-S Beast:DIP Switches
The 10 DIP switches on the component side of the PCB. Remove the brown protection with a sharp knife.
There are 10 DIP switches plus 6 solder jumpers used for configuring various optional functions of the Mode-S Beast. Currently not all of them are used and so foreseen to further extensions.
On HW V1.0 (sold around May 2011), at minimum one solder jumper is always needed at the TX-Data multiplexer:
In most cases it is the solder jumper named USB, which connects the serial output of the FPGA to the USB interface. The other possible selections are Xport (Xp) and BlueTooth (BT). Multiple connections are possible for TX-Data. The default configuration for USB is normally done before shipping.
The fallback position of the DIP switches is all off, means towards the LED: 3MBit/sec over USB, no special function activated. In case of problems with the Mode-S Beast, I always suggest falling back to this setting.
DIP Switches in the Short
| DIP | Function (if set to ON) | Recommened Setting |
| 1,2 | Baudrate between FPGA and USB interface | both OPEN |
| 3 | FW <=V1.21: AVR Format for transmission over Ethernet FW >= V1.30: Binary Format |
FW <=V1.21: OPEN FW >=V1.30: ON |
| 4 | DF11/17 filter: The Mode-S Beast only decodes DF-17 and DF-11 frames | OPEN |
| 5 | MLAT timestamp enable | ON |
| 6 | CRC check disable (for DF-11 and DF-17) | OPEN (*1) |
| 7 | DF-0/4/5 filter: The Mode-S Beast does not decode those types (mostly used when having performance problems) |
OPEN |
| 8 | RTS handshake enable | ON (see note below) |
| 9 | 1 bit forward error correction disable | OPEN (*2) |
| 10 | Mode-A/C decoding enable | ON |
(*1) Only then use DIP#6 ON position if you really know what it does.
(*2) 1 bit FEC may cause some spurious decodes of non existing aircraft because the safety of the CRC is decreased with it. If you are feeding databases, sharing networks or similar, and if this is a matter for you, disable FEC (DIP#9=ON). Otherwise, if you are just watching the air traffic, keep this switch in OPEN position in order to have as many frames as possible. Those just watching would never recognize but enjoy a bigger number of frames beeing received and enjoy some smoother traces.
Technical note: The Mode-S documents speak about even up to 5 bits beeing correctible, but when I once tried a 3 bit error correction, there were so many spuriouses that even just watching was not a pleasure. I have no idea how a true good/bad decision on these frames can be made successfully in order to make use of them.
DIP Switches in Detail
| Baudrate | SW1 | SW2 | Usage |
| 3 MBit/sec (*3) | open | open | USB serial interface (with USB over FT232R only) |
| 921600 Bit/sec (*4) | closed | open | Bluetooth interface, Lantronix Xport (Xport needs to be set to high performance mode) |
| 230400 Bit/sec | open | closed | |
| 115200 Bit/sec | closed | closed |
(*3) Until FW version V1.15 this baudrate was 1MBit/sec. It became changed to 3MBit/sec with FW Version V1.21 and later
(*4) This setting can be used when operating USB and Ethernet in parallel
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. See also my comment here.
The Mode-S frames capability of the different baudrates is about:
| Baudrate | Estimated number of Mode-S frames per second maximum in UDP format |
Estimated number of Mode-S frames per second maximum in binary format |
| 3 MBit | more than 2000 | more than 4000 |
| 921600 Bit/sec | 1100 | 2200 |
| 230400 Bit/sec | 550 | 1100 |
| 115200 Bit/sec | 300 | 150 |
These are very rougth estimations!!!
Mode-AC frames are output with lower priority, so if your interface is already conguested with Mode-S frames, you will see less or no Mode-AC frames.
| Planeplotter UDP Input Format FW V1.21 and earlier (mostly obsolete) |
SW3 | Usage (see also output formats page) |
| disabled | open | Standard output: 56 Bit Mode-S frames: *02E99619FACDAE; 112 Bit Mode-S frames: *8D3C5EE69901BD9540078D37335F; Mode-A/C frames: *7700; (Mode-A/C frame values are octal) With MLAT information: 56 Bit Mode-S frames: @016CE3671C745DFFE7AB7BFCAB; 112 Bit Mode-S frames: @016CE3671AA88D00199A8BB80030A8000628F400; Mode-A/C frames: @016CE3671C747700; (Mode-A/C frame values are octal) The distinction between Mode-S and Mode-A/C is done using the length of the frame. |
| enabled | closed | Only necessary/used if 1) Lantronix Xport is used for network data transfer AND 2) UDP data transfer towards Planeplotter is used (there is also a COM port emulation for the Lantronix Xport, using TCP/IP between the Xport and the computer, which does not need the 'AV' prefix) Planeplotter then needs a prefix 'AV' in order to distinguish the data from other network data. Standard output: AV*02E99619FACDAE; AV*8D3C5EE69901BD9540078D37335F; AV*7700; With MLAT information: AV@016CE3671C7423FFE7AB7BFCAB; AV@016CE3671AA8A800199A8BB80030A8000628F400; AV@016CE3671C747700; |
| Output Binary format FW V1.30 and later |
SW3 | Usage (see also output formats page) |
| open | ||
| closed |
| DF-11/DF-17 only | SW4 | Usage |
| open | ||
| closed |
| MLAT enable | SW5 | Usage |
| open | ||
| closed |
| ' | ' | Usage |
| open | ||
| closed |
| CRC disable | SW6 | Usage |
| open | ||
| closed |
| DF-0/DF-4/DF-5 filter | SW7 | Usage |
| open | ||
| closed |
| RTS Handshake enable | SW8 | Usage |
| open | ||
| closed |
The reason why this DIP is in OPEN in delivery state is that the Beast always should output data, disregarding any handshake setting. I am simply afraid of too many users that come back with the note "The Beast does not output data...." just because of this small DIP. After having seen that the Beast works, please enable RTS handshake and see that it still works.
| 1 Bit FEC disable |
SW9 | Usage |
| open | ||
| closed | ||
| Mode-A/C frame decoding | SW10 | Usage |
| open | ||
| closed |