Hello all, I’m playing around with another feeder. This one is a pi3 b+ with either a Nooelec stick or the flight radar stick. Running version 1.28. I have another feeder running the same setup and it receives more aircraft than when I load the 1.03 image. Not sure why. Tried different receiver sticks and different pis’ but not the same reception. I tried different gain settings too. Now that Ive set the second one up with the 1.28 I’m getting error messages stating it’s having problems fetching data from server. What did I miss.? My main feeder is running this same setup and works fine. Here’s the message. Problem fetching data from the server! AJAX call failed (parsererror: SyntaxError: JSON Parse error: Unexpected EOF). The displayed map data will be out of date. Thanks.
Old image has it at /dump1090 i think, is that what you're trying? Anyhow ..... why aren't you just using the new image? And "more aircraft" when i do X is .... most of the time just fluctuating traffic in the air.
I’ve been playing around with different hardware. Radar box stick, nooelec stick, pi zero w , pi 4+ and so on. I just noticed that the new 1.03 image doesn’t seem to hear as well as the 1.28. It doesn’t make sense to me but that’s what it appears. I can have them side by side and the 1.03 has fewer a/c shown than 1.28.
That's not an answer to my question. For side by side comparisons i'd expect the hardware differences to be the reason. readsb which is in use is tried and proven, really no use to compare it to the old dump1090-mutability. Also please only compare the "aircraft with position" count if you compare anything. Aircraft without position are often bogus decoding errors, those might be different in frequency for the two.
Thanks for that. When I get a chance I will reload 1.03. I wasn’t aware of the data difference between “aircraft with position” count errors. That might be what I’m seeing since it’s nearly double the a/c seen on 1.28 compared to 1.03.
Oh i think 1.28 was using --aggressive which is a bad idea and will produce bogus aircraft WITHOUT position. So that may be the reason. If you are curious about the command line used: pgrep -a dump1090
I just installed a new server on Linux Mint (Debian). Getting this error: "Problem fetching data from the server: 200: SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data" I may be using the wrong feeder ID. This is the link to my previous feeder https://globe.adsbexchange.com/?feed=UEI7AQdDKaSz Where can I find my current feeder ID - or will it be same as I'm using the same account data? Thanks!
Seems you don't have the stats package installed which is required for the feed map: https://github.com/adsbxchange/adsbexchange-stats I assumed it was installed and you just needed the link which is found on that page.
Hi! Few days ago i"ve checked my feeder and got this message: MLAT sync stats for feeder 'GynRO_LRCL_15be1c_1.28' (Region 5A) - ADSBExchange (Back to the region stats page) OOPS: Can't find myself (GynRO_LRCL_15be1c_1.28) in JSON table? Tried to restart, ethernet lights ok, removed/reinsert SD card, no change...
Check here to see which zone you are in: https://map.adsbexchange.com/mlat-map/ MLAT zones change from time to time.
Well i don't think your feed was ever on the map because --privacy is enabled. What is the output for these commands: sudo dmesg --ctime | grep voltage sudo vcgencmd get_throttled Probably either your SDR is going bad or your power supply. Another possibility might be water in the coax causing almost no aircraft being received. Sync requires ADS-B aircraft in common with other stations. Yeah it seems you're not receiving anything anymore ... Your image is a version i'm not very familiar with i think. Try this and get back to me with the output please it should show if the SDR is working at all: Code: sudo bash -c "$(wget -nv -O - https://raw.githubusercontent.com/wiedehopf/adsb-scripts/master/rtl_test.sh)" Or do you have other feed clients that work? Then you likely have them misconfigured and they are hogging the SDR.
Have a FR24 receiver near the ADSBx receiver, probably there was some interference between them. Now moved the FR receiver to another location, restarted the ADSBx , unplugged the power supply. It's working fine now, thanks 4 your support!
