Raspberry 3 Pi and FlightAware Pro Plus

[goingaround]

I used to operate the Kinetics SBS 1er but due to my situation I had to let my SBS 1er go. However I am trying to get back in to the hobby and I have purchased  a  Raspberry Pi 3 B + and a FlightAware Pro stick pro. I followed the instruction and think I have set things up ok. I can go to FlightAware site and see what I have tracked and as I have entered my geographical position I am able to participate with MLAT. 
I can see the aircraft I have actually tracked on the Flightaware website on a separate pc, but for what ever reason I thought I may have seen them on the Raspberry.  With regards to the Raspberry, if I try to use "alt f2" screen I am asked for a Raspberry Pi login. I don't believe I have set up a Raspberry login only the Flightaware and if I try to use this I am told it is erroneous.
Any comments or info appreciated as I am not sure where to go from here. I do believe that I can probably output my data to Planeplotter.

[IanH]

Just leave the Pi to do its thing with Piaware.

If you are running PlanePlotter on a PC, go and download modesmixer2 - check out this post: https://radarspotting.com/forum/index.php/topic,2978.0.html to find modesdeco2_windows_20180429.zip

You will use modesmixer2 to merge the raw ADSB data from the Pi with the MLAT data from Piaware and then plot the combined data in PlanePlotter. The basic command line looks like this

Code Select Expand

<pathto>\modesmixer2.exe --inConnect <IP address of Pi>:30105 --inConnect <IP address of Pi>:30005 --outServer beast:30009


So perhaps something like : C:\radar\modesmixer2.exe --inConnect 192.168.0.18:30105 --inConnect 192.168.0.18:30005 --outServer beast:30009

Put that command line in a batch file to make it easy to start each time.

Once that is working, in PlanePlotter change the Options/Mode-S receiver/Beast receiver/Setup TCP/IP client to <IP of PC>:30009 Probably 127.0.0.1:30009 will work.

[goingaround]

Ian, Thanks for your reply, I will work on it tomorrow and report back. Rich

[abcd567]

You can watch the planes on a map and table in a browser of your Desktop/Laptop/Tablet (on same LAN as Pi3) on following address:

IP-OF-PI/dump1090-fa/

My Rpi's Local IP is 192.168.0.22, and I see the map in the browser of my Windows Desktop (on same LAN/Router as RPi) at:
192.168.0.22/dump1090-fa/

NOTE:
(1) If you have written your microSD card with Piaware image or Raspbian LITE image, then both do not have a GUI.

(2) To login to Piaware SD Card image (through SSH), login as user pi, password flightaware

(3) To login to Raspbian image (through SSH), login as user pi, password raspberry

[attachment deleted reduce file load]

[Anmer]

(1) If you have written your microSD card with Piaware image or Raspbian LITE image, then both do not have a GUI.

If you're running the PiAware "build" image (total install, OS and PiAware) you should be able to view your local traffic on a map.

Type the locally assigned IP address of the RPi running PiAware into a local browser to access the PiAware Status page from where there's a link to "Go to Map".



[attachment deleted reduce file load]

[abcd567]

You can watch the planes on a map and table in a browser of your Desktop/Laptop/Tablet (on same LAN as Pi3) on following address:

IP-OF-PI/dump1090-fa/

Type the locally assigned IP address of the RPi running PiAware into a local browser to access the PiAware Status page from where there's a link to "Go to Map".

(1) Clicking "Go to Map" link in Piaware Status page takes to "IP-OF-PI/dump1090-fa/"

(2) If Raspbian image is used (with Piaware + dump1090-fa package install), then Piaware Status page is not available. In this case only way to go to Map is "IP-OF-PI/dump1090-fa/"

.

[Anmer]

(1) Clicking "Go to Map" link in Piaware Status page takes to "IP-OF-PI/dump1090-fa/"

I'm not disputing that.  It was your previous statement that a PiAware image doesn't have a GUI.

And offering a "usability" route to it.  Both are valid.

[abcd567]

I'm not disputing that.  It was your previous statement that a PiAware image doesn't have a GUI.

I think you misunderstood what I meant by GUI.
By GUI, I meant the display on a Monitor when Pi is connected to it using HDMI cable, like the one shown below.

This GUI is missing from "Raspbian Stretch Lite" and "Piaware image". 

It is available in "Raspbian Stretch with desktop" and has its own browser, and map can be seen on it at "localhost/dump1090-fa" or "127.0.0.1/dump1090-fa"



[attachment deleted reduce file load]

[Anmer]

I think you misunderstood what I meant by GUI.
By GUI, I meant the display on a Monitor when Pi is connected to it using HDMI cable, like the one shown below.

Thanks, now I understand.

[goingaround]

I appreciate all the replies and will digest them later, thanks all.
I am very pleased so far with what I can see via Flightaware, more than I did previously
even with a masthead preamp.

[goingaround]

I have re registered my PP as requested, and I am receiving shared data. I believe my share code has been modified too. I have created a batch file and actually run it but are unable to see my data in PP.
I have not used this type of information before and feel somewhat lost.

So my batch file goes like this

C:\TOOLS\MM\modemixer2.exe --inConnectt 192.168.0.18:30105 inConnect 192.168.0.18:30005 --outServer beast:30009

I have copied the example  given by Ian but not sure if this is an example to follow with my own info or use exactly as stated. My RPI address 192.168.1.141:  should I use this instead of the example?
2.The outserver refers to beast  again do I use this or select RTL in the Options/SMode/Receiver ?

I have tried various combinations and have got into a bit of a muddle. Any assistance really appreciated.

[IanH]

Use this:

C:\TOOLS\MM\modemixer2.exe --inConnect 192.168.1.141:30105 --inConnect 192.168.1.141:30005 --outServer beast:30009

That is Pi address. just 1 "t" in first inConnect and two "-" in front of second inConnect.

Use Beast as Mode_S receiver (since that is what is being generated by modesmixer2) and set the TCP/IP client as 127.0.0.1:30009

[goingaround]

Use this:

C:\TOOLS\MM\modemixer2.exe --inConnect 192.168.1.141:30105 --inConnect 192.168.1.141:30005 --outServer beast:30009

That is Pi address. just 1 "t" in first inConnect and two "-" in front of second inConnect.

Use Beast as Mode_S receiver (since that is what is being generated by modesmixer2) and set the TCP/IP client as 127.0.0.1:30009

Ian
Many thanks again for your reply. When I get back home I will correct my bat file as shown.

[goingaround]

I have rebooted the PC and then ran the batch file, and have PP showing shared data received, but still unable to see my own.
I actually cut and paste the bat file data to make sure I had it right.
In options Input/output I have tried selecting Beast but that crashes the system.

[Anmer]

In PP what do you have set for:

Options-> I/O Settings-> Mode-S/ADS-B->

Options-> Mode-S Receiver->