I dont think he made any changes to 1090RPi config, it should be still there. The only change in config he made was in 978RPi config by changing its feeder-id and that is all.
Most likely the reason of 1090RPi config not working is as in my post quoted below. I am still waiting for @wmccouch’s reply about fixed local ip of RPi.
Took a little while to think about everything, and appreciate your thoughts both @abcd567 and @obj. I think I have it figured out.
This must be what’s happening. My very first step in trying to get combined reporting was to run this script on the 1090:
Initially I was encouraged because my 1090 feeder site page added a line for the UAT position and aircraft counts right after I ran the script. But it reported nothing under the count, so I came back here and created the first post on this thread, to which @abcd567 replied with the suggestion of duplicating the 1090 feeder ID on my 978 RPi (see first reply to my original post). When I did the feeder ID duplication, my 978 numbers started populating on the 1090 stats page. So I thought everything was solved. In hindsight, @obj is right, that initial fetch script isn’t doing anything for me right now, the combined results are solely on account of the duplicate feeder ID.
Completely correct explanation. The 978 RP is on a fixed local IP; however, my 1090 RPi is connected via ethernet which runs to a Netgear unmanaged switch (all Cat-6 jacks in the house are connected to it). The 978 RPi is connected via WiFi to a router that itself is connected to the network switch. The router is issuing device addresses on a 192.168.x.x basis; however, devices connected directly to the network switch are addressed as 10.0.0.xx. It’s possible that the initial fetch script didn’t work because that 1090 RPi is working on a different subnet than the 978. While on the topic though, can you confirm that port 30978 is correct for the script?
Incidentally, the 1090 was on WiFi originally, but a while back I changed the network password. It was easier to just plug the RPi into a nearby Cat 6 jack than to pull the SD card and update the WiFi configuration in that text file in PiAware. I wasn’t aware of a way to update the wifi network settings remotely via putty.
Ultimately I’d prefer a single RPi running both dongles, so I’ll be following those instructions provided earlier. It’ll be further incentive to finish building a 15’ tall PVC antenna mast I designed for my roof to which I’ll be mounting both antennas. Got up on the roof last two weeks ago to scope it out and nearly had a Clark Griswold happen.
What script?
30978 is the raw data port that piaware needs to connect to, yes.
Look at the piaware logs if you have problems. They’ll tell you about any failure to connect.
These initial instructions from @abcd567:
Oh. That’s just config, not a script. You could equivalently just edit /boot/piaware-config.txt by hand.
On your 1090 RPi give this command, and wait for few minutes till some UAT traffic appears on your Skyaware978 map.
(Replace xxx.xxx.xx.xx by local IP of 978 RPi)
sudo nc xxx.xxx.xx.xx 30978
What do you see?
I’ll give this a try later this evening.
I’m still wondering if this would work if the 978 RPi is on a different subnet than the 1090.
Issue the following command on 1090RPi and from its output you will know
sudo nc xxx.xxx.xx.xx 30978
where xxx.xxx.xx.xx is IP of 978RPi
This is a “does my network work?” question. piaware et al don’t care what the IP address looks like, all they care about is if they can connect to it or not. The answer to that depends on whether you have your network correctly set up to support it.
FWIW, I recently setup UAT on my RPI4 ver A with the official Pi power supply. I did have power issues impacting the the Blue Pro Plust stick 1090 performance. It was simply solved by adding a spare powered USB hub I had in the cabinet and pluging in the 978 USB stick into the powered hub.
Appreciate that feedback, thanks!
Give this command on your 1090RPi
ping xxx.xxx.xx.xx -c 5
where xxx.xxx.xx.xx is Local IP of your 978 RPi.
.
Its output will show you if your 1090 RPi can access 978 RPI on your network.
Just to show you, I have given ping command to an non-existing address (192.168.0.25). Even if a computer existed at this address, but was unreachable, I will get the same output.
pi@piaware:~ $ ping 192.168.0.25 -c 5
PING 192.168.0.25 (192.168.0.25) 56(84) bytes of data.
From 192.168.0.21 icmp_seq=1 Destination Host Unreachable
From 192.168.0.21 icmp_seq=5 Destination Host Unreachable
--- 192.168.0.25 ping statistics ---
5 packets transmitted, 0 received, +2 errors, 100% packet loss, time 148ms
pipe 4
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.