Open EasternPA opened 2 years ago
As a follow-up, it seems stratux is only processing FIS-B data services and TIS-B traffic on UAT. No direct 978 traffic (bad weather, no surprise there) but no 1090 traffic either -- that's a surprise. The green light on the pingEFB device only blinks about 4 or 5 times at first power-up, but only the red light blinks after that. It has been a few years since I last used this, so I don't recall which color is linked to which band. I've toggled the 978 and 1090 hardware switches on (even though I don't have an SDR) and as expected that did not fix the problem. I'm only seeing FIS-B and TIS-B data coming through.
Here's the log snippet showing no ES traffic. Only UAT targets:
2021/05/07 18:01:31 stats [started: 49 minutes ago]
2021/05/07 18:01:31 - Disk bytes used = 565 kB (0.2 %), Disk bytes free = 262 MB (99.8 %)
2021/05/07 18:01:31 - CPUTemp=55.31 [52.62 - 60.15] deg C, MemStats.Alloc=1.8 MB, MemStats.Sys=74 MB, totalNetworkMessagesSent=33,016
2021/05/07 18:01:31 - UAT/min 0/14 [maxSS=0.00%], ES/min 0/0, Total traffic targets tracked=4
2021/05/07 18:01:31 - Network data messages sent: 31832 total, 31816 nonqueueable. Network data bytes sent: 666876 total, 656310 nonqueueable.
2021/05/07 18:01:31 - Mode-S Distance factors (<5000, <10000, >10000): 2500.000000, 2800.000000, 3000.000000
Update: I received direct 978 traffic today as well as a screenful of TIS-B traffic and METARS. Still no 1090 traffic.
Update: I updated to eu027. PingEFB worked out of the box, but did not survive a reboot. I still need to edit the symlink after every boot in order to get the pingEFB to show connected in the web UI. I also have 0 packets on the 1090 side and no 1090 traffic.
Stratux version:
1.6r1-eu0261.6r1-eu027Stratux config:
SDR
GPS
AHRS
power source: Pi power 4ft
usb cable: 6 inch USB A to micro USB for pingEFB
EFB app and version: (e.g., WingX Pro7 8.6.2) Avare 10.0.8
EFB platform: (e.g., iOS 9.2) Android 12
EFB hardware: (e.g., iPad Mini 2) OnePlus 3T
Description of your issue:
If possible, enable "Replay Logs", reproduce the problem, and provide a copy of the logs in http://192.168.10.1/logs/stratux/ and http://192.168.10.1/logs/stratux.log.
I updated for the first time in over 2 years and can't get pingEFB support to work. The first boot linked
/dev/ping
to/dev/bus/usb/001/004
which matches the FTDI device onlsusb
. However, the web interface showsDisconnected
for the ping device. Here is the failure in the log.dmesg
showed the device was assigned/dev/ttyUSB0
. I deleted the symlink for/dev/ping
and replaced it withsudo ln -s /dev/ttyUSB0 /dev/ping
The UI shows
connected
in green, but no ADS-B traffic seems to flow.Upon reboot, when I reenable ping support, the UI shows disconnected. The symlink for/dev/ping
is now linked to/dev/gpiochip3
. This is the failure that shows up in the log with that symlink.So manually symlinking
/dev/ttyUSB0
to/dev/ping
is the only way I can get the pingEFB device to showconnected
in the web UI, but no traffic is flowing to the web UI or the Avare EFB. I have confirmed that my pingEFB device does not need to have the firmware update by uAvionix applied.Update: I moved my pingEFB away from a large monitor and data started flowing. The issue of the symlink for
/dev/ping
still remains. The web UI showsconnected
when I symlink/dev/ttyUSB0
to/dev/ping
, but does not survive a reboot or manually disconnecting and reconnecting the pingEFB USB cable at any time.