Solid RED light issue | Official ADS-B Exchange Group | Page 1

swift jacinth Dec 2, 2024, 8:10 PM

#

Hello,
I recently noticed that my ADS-B receiver (the aluminum enclosed unit) has a solid red light indication. I checked the manual, but it doesn't explain what a solid red light means. I also checked the myip page, and everything appears to be working fine — all indicators are green, and ADSBx Anywhere is functioning correctly. The LED light indication setting is turned on.

I’ve already tried restarting the feeder and updating it via the webpage, but the red light persists. Can you please help me understand what might be causing this issue?

solar turtle Dec 2, 2024, 9:29 PM

#

the custom LED status should be blinking (the number of blinks means something). If it's solid red, it suggests the default Pi setup, where that just means that it has power. Under http://adsbexchange.local/config/ is "Use Custom LED Indications?" enabled?

swift jacinth Dec 2, 2024, 10:57 PM

#

@solar turtle Yes "Use Custom LED Indications" is turned on

round grove Dec 2, 2024, 11:13 PM

#

this has been an ongoing issue for a few months now iirc, I had a topic about this a while back one sec

#

@solar turtle https://discord.com/channels/1141047768266322061/1241757573204672543

#

and for clarification, has remained the same as then (ie no functionality of the custom led indications)

honest veldt Dec 3, 2024, 2:13 AM

#

Solid red means it is powered on and working properly, if red is blinking you have a problem.

#

This is a photo of the instruction sheet that comes with the feeder.

#

swift jacinth Dec 3, 2024, 10:54 AM

#

honest veldt Solid red means it is powered on and working properly, if red is blinking you h...

In this case it should be blinking green light proportional to the number of aircraft

solar turtle Dec 3, 2024, 10:54 AM

#

Under normal operation, red should be off, and green should be blinking (assuming you're able to receive any aircraft positions). I've reproduced the problem that @round grove reported after doing a apt-get dist-upgrade on the 8.0 image, which takes the Linux kernel from 5.15 to 6.1, and changes the way LEDs are addressed. There's a corresponding change here https://github.com/ADSBexchange/adsbx-webconfig/commit/0454a86efad46fe5fb3cbd4d3df13adbbee15293, but the 8.0 image doesn't use that git repo. It seems to work when I manually update to that on my test feeder, with:

curl -s https://raw.githubusercontent.com/adsbexchange/adsbx-webconfig/master/update-webconfig.sh | sudo bash
Not sure if this is officially supported, but I don't see any negative effects so-far

#

before you try that, confirm that you see: pi@adsbexchange:~ $ ls -l /sys/class/leds/ total 0 lrwxrwxrwx 1 root root 0 Dec 3 10:22 ACT -> ../../devices/platform/leds/leds/ACT lrwxrwxrwx 1 root root 0 Dec 3 10:22 default-on -> ../../devices/virtual/leds/default-on lrwxrwxrwx 1 root root 0 Dec 3 10:22 mmc0 -> ../../devices/virtual/leds/mmc0 lrwxrwxrwx 1 root root 0 Dec 3 10:22 mmc0:: -> ../../devices/platform/emmc2bus/fe340000.mmc/leds/mmc0:: lrwxrwxrwx 1 root root 0 Dec 3 10:22 PWR -> ../../devices/platform/leds/leds/PWR pi@adsbexchange:~ $

#

and not: root@adsbexchange:~# ls -l /sys/class/leds/ total 0 lrwxrwxrwx 1 root root 0 Apr 4 2022 default-on -> ../../devices/virtual/leds/default-on lrwxrwxrwx 1 root root 0 Apr 4 2022 led0 -> ../../devices/platform/leds/leds/led0 lrwxrwxrwx 1 root root 0 Apr 4 2022 led1 -> ../../devices/platform/leds/leds/led1 lrwxrwxrwx 1 root root 0 Apr 4 2022 mmc0 -> ../../devices/virtual/leds/mmc0 lrwxrwxrwx 1 root root 0 Apr 4 2022 mmc0:: -> ../../devices/platform/emmc2bus/fe340000.mmc/leds/mmc0:: root@adsbexchange:~#

#

the (better?) alternative would be to reimage with the 9.0 image

swift jacinth Dec 3, 2024, 12:09 PM

#

total 0
lrwxrwxrwx 1 root root 0 Dec  3 00:24 ACT -> ../../devices/platform/leds/leds/ACT
lrwxrwxrwx 1 root root 0 Dec  3 00:24 default-on -> ../../devices/virtual/leds/default-on
lrwxrwxrwx 1 root root 0 Dec  3 00:24 mmc0 -> ../../devices/virtual/leds/mmc0
lrwxrwxrwx 1 root root 0 Dec  3 00:24 mmc0:: -> ../../devices/platform/emmc2bus/fe340000.mmc/leds/mmc0::
lrwxrwxrwx 1 root root 0 Dec  3 00:24 PWR -> ../../devices/platform/leds/leds/PWR
pi@adsbexchange:~ $```

solar turtle Dec 3, 2024, 1:08 PM

#

yeah, so looks like you have the newer kernel too

honest veldt Dec 3, 2024, 5:45 PM

#

solar turtle Under normal operation, red should be off, and green should be blinking (assumin...

If this is true we need to change the documentation, Red and green are seperate LEDs so Red can be on while Green is blinking.

honest veldt Dec 3, 2024, 5:45 PM

#

swift jacinth In this case it should be blinking green light proportional to the number of air...

Correct, the Red LED should be on, and the Green LED should be blinking.

solar turtle Dec 3, 2024, 5:46 PM

#

It could be, but that's not what the code does ... it turns red off, then blinks the appropriate number of times for any fault detected

#

so when it's working normally, red is off, and green blinking with activity

#

the document doesn't disagree, AFAICT - it doesn't say that red should be on

honest veldt Dec 3, 2024, 5:48 PM

#

Hmm, your technically correct... I just read it as being on.

#

Next batch I'll clarify the wording.

solar turtle Dec 3, 2024, 5:49 PM

#

honest veldt Dec 3, 2024, 5:51 PM

#

No i don't disagree, I never paid attention to a working feeder, just the ones in testing.

solar turtle Dec 3, 2024, 5:54 PM

#

Yeah.... so the issue will come up if people manually update the OS on the 8.0 image ... it appears that the browser UI update only targets specific packages, not the entire OS

round grove Dec 4, 2024, 12:12 AM

#

nice, ty for the workaround, it's a nice to have for me with my pi on a side table and with me having previously bumped a shoddy usb extender (albeit my own fault for getting cheap ones) and having my 1090 stick disconnect from the pi just enough to not be visibly disconnected

#Solid RED light issue