A few questions piaware related

If you are running a standard piaware image on your Pi you can see the detected output by putting

http://IP_of_your_Pi:30003/ in a browser.

I get output like this

MSG,6,1,1,7CF9C4,1,2018/12/16,04:03:32.552,2018/12/16,04:03:32.570,1416,0,0,0, MSG,3,1,1,7C6DB1,1,2018/12/16,04:03:32.556,2018/12/16,04:03:32.571,25400,-36.98352,145.79066,0 MSG,8,1,1,77058C,1,2018/12/16,04:03:32.588,2018/12/16,04:03:32.622,0 MSG,4,1,1,77058C,1,2018/12/16,04:03:32.607,2018/12/16,04:03:32.625,344,112,-1664,0 MSG,8,1,1,7C6D7E,1,2018/12/16,04:03:32.651,2018/12/16,04:03:32.678,0 MSG,7,1,1,7C6D22,1,2018/12/16,04:03:32.660,2018/12/16,04:03:32.679,20025, MSG,7,1,1,77058C,1,2018/12/16,04:03:32.676,2018/12/16,04:03:32.727,17975, MSG,4,1,1,7C6D81,1,2018/12/16,04:03:32.682,2018/12/16,04:03:32.728,466,165,832,0 MSG,3,1,1,7CF9C4,1,2018/12/16,04:03:32.687,2018/12/16,04:03:32.729,3850,-37.57892,144.82984,0 MSG,3,1,1,7C6D7E,1,2018/12/16,04:03:32.727,2018/12/16,04:03:32.781,5125,-37.75836,144.72939,0 MSG,1,1,1,7C39FC,1,2018/12/16,04:03:32.776,2018/12/16,04:03:32.790,QLK284D ,0 MSG,3,1,1,7C39FC,1,2018/12/16,04:03:32.796,2018/12/16,04:03:32.838,9425,-38.09677,145.02789,0 MSG,4,1,1,7C6B13,1,2018/12/16,04:03:32.812,2018/12/16,04:03:32.841,388,39,1728,0 MSG,7,1,1,7C6B13,1,2018/12/16,04:03:32.851,2018/12/16,04:03:32.893,16600, MSG,4,1,1,7C6B2B,1,2018/12/16,04:03:32.862,2018/12/16,04:03:32.895,170,10,-1024,0 MSG,3,1,1,7C7A3D,1,2018/12/16,04:03:32.866,2018/12/16,04:03:32.896,12575,-37.36153,144.78029,0 MSG,4,1,1,7C6D7E,1,2018/12/16,04:03:32.867,2018/12/16,04:03:32.896,270,182,-1152,0 MSG,8,1,1,7C4877,1,2018/12/16,04:03:32.870,2018/12/16,04:03:32.897,0 MSG,4,1,1,7C7A3D,1,2018/12/16,04:03:32.871,2018/12/16,04:03:32.897,304,172,-1472,0 MSG,8,1,1,7C6D7E,1,2018/12/16,04:03:32.877,2018/12/16,04:03:32.901,0 MSG,3,1,1,7C4028,1,2018/12/16,04:03:32.898,2018/12/16,04:03:32.946,14000,-38.20422,143.57851,0 MSG,4,1,1,7C4028,1,2018/12/16,04:03:32.899,2018/12/16,04:03:32.946,281,264,-256,0 MSG,3,1,1,7C6B2B,1,2018/12/16,04:03:32.902,2018/12/16,04:03:32.947,3175,-37.81906,144.86479,0 MSG,8,1,1,7C39FC,1,2018/12/16,04:03:32.936,2018/12/16,04:03:32.953,0 MSG,5,1,1,7CF9C4,1,2018/12/16,04:03:32.952,2018/12/16,04:03:33.001,3875,0,0, MSG,5,1,1,77058C,1,2018/12/16,04:03:32.961,2018/12/16,04:03:33.003,17975,0,0, MSG,3,1,1,77058C,1,2018/12/16,04:03:32.967,2018/12/16,04:03:33.005,17975,-36.86554,144.19223,0 MSG,4,1,1,7C39FC,1,2018/12/16,04:03:33.026,2018/12/16,04:03:33.059,246,308,-1152,0 MSG,3,1,1,780DFE,1,2018/12/16,04:03:33.034,2018/12/16,04:03:33.061,27875,-36.09860,144.09542

1 Like

That works for me with IE but not Chrome :roll_eyes:

I get to see all the output on the screen if I Telnet to that IP address on that port ie TELNET ip_of_Pi 30003

or

Use Putty selecting port 30005 and Telnet instead of the normal SSH.

S.

1 Like

If you are looking for close by aircraft you will want to reduce the gain on one of your receivers.

Because maybe the aircraft you see have a signal too strong to be received.

Also i get the impression you are not displaying the MLAT results in VRS.
Just create two data sources in your VRS:
pi:30005 and pi:30105

But for starters why don’t you use the local webview?
No need for VRS.

As for the gain stuff your best bet is checking the SkyView table:

Click on expand sidebar:
Screenshot%20from%202018-12-16%2010-44-54

Click the column head of RSSI twice so the numbers closer to zero are first:
Screenshot%20from%202018-12-16%2010-46-24

If you are interested in closeby aircraft procede as follows:
If there are entries larger than -3, for example -2 you reduce the gain.

This might reduce your range but will make sure you receive the close by aircraft.

1 Like

How to Telnet to RPi: Exploring Port 30003 and 30106

.

Telnet to RPi on Port 30003 (Format SBS, human readable)
CLICK ON IMAGE TO SEE LARGER SIZE

.
.

Telnet to RPi on Port 30005 (Format Beast, NOT human readable)
CLICK ON IMAGE TO SEE LARGER SIZE

.

.

EDIT :
Above diagram shows default arrangement of MLAT feedback from AdsbExchange.
In my case, I did NOT want to feed AdsbExchang MLAT to SkyView and feed it only to VRS, so for AdsbExchange, I have not followed above arrangement.

The default setting of AdsbExchange MLAT feedback in file adsbExchange-mlat_maint.sh are 127.0.0.1:30104

Since I did not want to feed AdsbExchange MLAT to SkyView, only to VRS, instead of 127.0.0.1:30104, I have used:

Pi-1:
192.168.0.10:30101

Pi-2:
192.168.0.10:30102

(The 192.168.0.10 is IP of my Windows Desktop running VRS)

In VRS, I have set two separate receivers
(1) “Pi-1 AdsbExchange MLAT”, and configured it as “Push Receiver” Port 30101
(2) “Pi-2 AdsbExchange MLAT”, and configured it as “Push Receiver” Port 30102

.

abcd567, that is a wonderful explanation, thank you as I was wanting to pass data to adsbexchange too.

2 years ago a storm took my mast down… I was so “down” that I didn’t want to build the entire system back on until a few days.
So now Im back online, feeding and tweaking…That means I has an idea… ehm why is everybody running away now? Anyway:
On right top we have the message rate and history. Maybe someone knows how to implement a positions/second box there and if not maybe some script that can output that value and in real time - if possible.

Have anyone managed to test the radarcape hdr?

Take care
Emil

Modifying dump1090-fa would be required, it currently doesn’t output the necessary data.

If you don’t need the exact number, you could count in javascript for how many aircraft the position changes when the new data comes in every second.
And just use this as a position rate
(it would more accurately be the number of aircraft you have received a position for in the last second, still a useful number)

Actually having not only a message but also position counter in the aircraft.json would be neat.
I might actually make a PR for dump1090-fa to add that functionality.
Unless you feel up to the task :wink:

Also a note: starting your own thread is the better alternative to posting under some random old thread.

Is actual my “old random” thread :wink:

1 Like

Not 100% sure but it seems that SBSplotter is showing the position rate as msg/sec.