Last I looked, the MLAT 30106 is not in a basestation format. It is comma separated and looks like basestation format, but there are a bunch more fields.
The binary format 30105 should show up as DF18 CF=2 or 5. VRS would have to decode that. I assume it can, but maybe not. Can you have more than one feed port?
Well, I started up VRS (haven’t used it in a long time).
Creating a receiver 2 with port 30105 showed it connected and receiving DF18 data.
Started up the web server. No MLAT. So I clicked on Menu and one of the options is receiver.
So I clicked on it and enabled receiver 2. Presto I had MLAT displaying.
Simple…
EDIT: created a “merged feed” and selected that in the Web display under the receiver option, and had MLAT and regular data.
THIS IS HOW I SETUP MY VRS IN BASESTATION FORMAT.
Please scroll down few post below to see how to setup in BEAST Format
SCREENSHOT 1 OF 4
https://c6.staticflickr.com/6/5778/30371042013_f69299960e_b.jpg
SCREENSHOT 2 OF 4 - ADSB RECEIVER (Basestation Format)
https://c2.staticflickr.com/6/5725/31177870625_99e2d3ce4a_o.png
SCREENSHOT 3 OF 4 - FA MLAT RECEIVER (Basestation Format)
https://c2.staticflickr.com/6/5733/30370811993_f140bbabf5_o.png
SCREENSHOT 4 OF 4 - MERGE FEED ADSB+MLAT (Basestation Format)
https://c2.staticflickr.com/6/5667/30810625430_230dc59700_o.png
.
Since VRS understands Beast Binary, you will probably get better data from that, then the Basestation “compatible” ports.
Let VRS decode the DF, and you don’t even need to run dump1090. Just saying…
As you can see from screenshots, I have configured all receivers and merged feeds twice, once for Basestation format and again for Beast format. I have tried both Basestation & Beast, and did not notice any difference. It is possible there is some difference, but I could not catch it.
In order to segregate the display of Flightaware MLAT feedback and Adsbexchange MLAT feedback, I configured the MLAT feedback of Adsbexchange to connect to VRS port 30102 on my Desktop, instead of connecting to dump1090 port30104. Now dump1090 map displays antenna adsb planes+ FA mlat planes. The Adsbexchane mlat planes are displayed only in VRS
This is how I did it:
In file adsbexchange-mlat_maint.sh, changed –results beast,connect,127.0.0.1:30104 to –results beast,connect,192.168.0.xx:30102 where 192.168.0.xx is local IP of my Desktop.
pi@piaware:~$ sudo nano adsb-receiver/build/adsbexchange/adsbexchange-mlat_maint.sh
#! /bin/sh
while true
do
sleep 30
/usr/bin/mlat-client --input-type dump1090 --input-connect 127.0.0.1:30005 --lat 43.5xxx --lon -79.6xxx --alt 150 --user 2-abcd567 --server feed.adsbexchange.com:31090 --no-udp --results beast,connect,192.168.0.xx:30102
done
Thanks for all your replies, it was in the end my own user error! I had set Dump1090 to output on 30106 so VRS was receiving clashing data. As soon as i removed the entry it was working fine.
Thanks
Kenny
Kenny have you (or has anyone else) noticed whether your stats from the VRS display are the same as through the dump1090 map?
When I run the two simultaneously, I show more results from dump1090 than I do with VRS. For example, right now at a glance I see that dump1090 is listing 212 aircraft, 163 with positions. VRS, meanwhile, shows 193 aircraft.
What accounts for that discrepancy? I’ve set VRS up in somewhat similar fashion to abcd567, in that I have an ADSB feed and an MLAT feed that I have merged. I thought that should cover all the data, and therefore equal the same number of viewable aircraft that is shown on dump1090’s map. Have I got something wrong somewhere?
I think VRS has a 600 second timeout for aircraft whereas it is 60 seconds for dump1090.
If 193 is the aircraft with positions then 193 seems about right.
HOW TO SETUP BEAST FORMAT FEED TO VRS
SCREENSHOT 1 OF 4
https://c2.staticflickr.com/6/5835/31199550285_f24595781b_o.png
SCREENSHOT 2 OF 4
https://c2.staticflickr.com/6/5757/31163697396_c3a841666d_o.png
SCREENSHOT 3 OF 4
https://c2.staticflickr.com/6/5526/31163702326_466facf210_o.png
SCREENSHOT 4 OF 4
https://c1.staticflickr.com/6/5692/30378985584_7aa46a2317_b.jpg
.
Thank you for your reply! The timeout could be a factor, I had not considered that. I did notice yesterday that dump1090 was displaying aircraft on the ground from what appeared to be a TIS-B broadcast, while VRS was not. This makes me wonder if VRS naturally filters more out than dump1090 does, and if I can offset that somehow.
Abcd567, I tried to mimic your setup but was unsuccessful with the MLAT server using Beast mode. It did work well when I set it as a “Basestation,” but not at all under Beast. Not sure what to make of that.
Check your settings:
For Basestation MLAT receiver:
Format = Basestation, Port = 30106
For Beast MLAT receiver:
Format = Beast or AVR, Port = 30105
.
Whats better beast or basestation?
I was under impression Flightaware pulled MLAT output for anything beyond the dump1090 output website.
What? No.
Beast.
VRS is better at decoding Mode-S, and has complete parameter adjustments. I’ve been running the linux version off and on.
VRS also has a better Basestation format, which you can create a merged server and feed others if you need that.
EDIT: I tried putting VRS on my RPi 2 and it sucked all the CPU, even in non-GUI mode. I think I have an old server I can use.
But with beast-splitter and a Beast receiver, you don’t need dump1090-fa at all.
You, sir, are a genius. I had those backwards! Thank you very much for your help!
It is up now in Beast mode, and I am noticing an immediate decrease in “bad messages” as flagged by VRS.
I have the 3.X update via console. I’ve tried using these port numbers and VRS will not connect o hem. But will connect to 30005
When I do a SSH command for piaware status it only lists 30005 for the active port. Am I missing something?
Give following command
*pi@piaware:~$ sudo piaware-config -show mlat-results-format *
This should be the response:
beast,connect,localhost:30104 beast,listen,30105 ext_basestation,listen,30106
If the response is not like line above, but like line below, it is the cause of problem you are facing.
beast,connect,localhost:30104
Why the configuration is incorrect?
This happens when following command was given sometime earlier:
pi@piaware:~$ sudo piaware-config mlat-results-format beast,connect,localhost:30104 beast,listen,30105 ext_basestation,listen,30106
The response below shows that the command was obeyed only partially.
mlat-results-format is unchanged
warning: cannot set option ‘beast,listen,30105’, it is not a known config option
After above command, following new line is added at the end of file /boot/piaware-config.txt
mlat-results-format beast,connect,localhost:30104 # updated by fa_piaware_config
How to remedy this situation?
#open file piaware-config.txt in text editor
pi@piaware:~$ sudo nano /boot/piaware-config.txt
#scroll down, and at the end you will see line
mlat-results-format beast,connect,localhost:30104 # updated by fa_piaware_config
#delete the above line (bring cursor on the line to be deleted, then press ctrl+k)
#Deleting this line will restore the default settings
#save file (ctrl+o) and close editor (ctrl+x)
#check the settings by giving this command
pi@piaware:~$ sudo piaware-config -show mlat-results-format
#the response of above command should now be like this (i.e. the default setting)
beast,connect,localhost:30104 beast,listen,30105 ext_basestation,listen,30106
Now REBOOT for correct configuration to take effect
Check your VRS.
Enjoy 
Or you can quote the arg to piaware-config:
$ piaware-config mlat-results-format "beast,connect,localhost:30104 beast,listen,30105 ext_basestation,listen,30106"
(as abcd says, this is only necessary if the config has been broken previously; the value show above is the default)