Could be because I installed both adsbx via script and tar1090 via script, not sure. What I am sure of is that opening http://192.168.1.4/tar1090/ opens tar1090 interface and it appears as I would expect. However, opening http://192.168.1.4/adsbx/ (which opens its own instance of 1090, I think) shows me having 56 aircraft in range, same as the other instance, yet they all show as Mode-S receptions and there are precisely zero aircraft in the display. The other instance shows like 6 or 7 received via Mode-S and the rest all as ADSB sourced and showing up just fine. What did I touch/look at wrong/breathe on? I tried uninstalling and reinstalling tar1090 and that went off without a hitch, but changed nothing(didn't expect it to, since it is the ADSBX instance that is going haywire. Also tried restarting browser and only opening http://192.168.1.4/adsbx/ and not both, thinking perhaps it doesn't like to share, but again, no change. I am hesitant to try the uninstall script I found because it references dump1090-fa and I don't want that uninstalled. Ideas?
If I am understanding this correctly, there is not much point in me using this feeder, given my wide range across the entire country, to feed ADSBExchange. If I have to rerun the script to put in a new lat long every day or so, that might get a bit tedious. I might tinker with automating the process a little, but, in the long term, I think it might be better for me to setup the one at my house and just feed adsbexchange from there, as it doesn't move. Thanks for putting up with my weird setup and the questions I inevitably have because of it. Followup: I did as suggested and it did indeed return to what I would call "normal" operation, so thanks once again, and especially for the explanation. If I am understanding further by inference, there is a maximum imposed radius from the lat/long entered during setup in order to feed and/or display. Accurate? And, I assume that changing the location in the web interface doesn't change the lat/long entered during setup, correct?
So you can automate if you wish. Just change lat / lon in /etc/defaulft/adsbexchange and restart adsbexchange-feed You can also start up adsbexchange-mlat if you're gonna sit still for a while. I didn't connect that you were moving around all the time. Display issue at /adsbx .... doesn't mean it's not sending data btw.
OK, so even if I am showing nothing in the display but still showing aircraft in range, albeit claiming they are all Mode-S, the feed is still sending what it is supposed to send? That's good to know. I'm still going to somehow parse one of gpsd's outputs and use that to modify /etc/defaulft/adsbexchange, say every time I stop for the day, and leave mlat turned off until I'm parked, then back off when I start moving again. That should sort things nicely. I hope.
Yeah that will certainly work Feel free to share the script, maybe i'll build on it and make it accessible to others who have asked for something like this.
Count me in on this fandango. I too want to drive to high points and see what I get. I'll share blame too!
After 10+ months, I still have not found time to dedicate to writing that script. I got close, but I never got around to educating myself on the use of "sed". I was going to use that to rewrite the config file, either at intervals or on demand. So, imagine my surprise when I had a distribution upgrade on my pi go wrong and I had to reinstall everything from scratch. Apparently wiedehopf found the time to do everything I was going to attempt and a whole lot more. My position(mobile) updates on page refresh, the web interface is configurable(custom range rings! woop-woop!) and I don't know what else; I'm still looking around at all the cool stuff like a little kid on Christmas morning. Merry Christmas and all that to all of us. That kind of work merits at least gratitude, so I am resurrecting this old-ish thread to say thanks to weidehopf. Perhaps I should learn sed(and regular expressions while I'm at it) anyway, but at least I don't have to wait on myself to get a great update to the tar1090 interface. Looking at the date, I almost wish I had had my problem sooner; I would have seen all the cool new stuff back in August(?). Thanks again.
Hi @wiedehopf With regards to the questions and your answers above, and the subsequent changes made to the feeder, can adsbexchange-mlat be left running all the time now, even if the receiver location changes, or will that cause problems? Guessing it won't hurt anything but I'd rather not be the culprit putting bad info into the database, just in case.
Aloha AI4FU, I've been asking the same questions for my mobile feeder over on Discord. AFIK, you still have to have the MLAT feed off while driving. The MLAT calculations can't keep up with GPS / location changes, and I'm assuming the backend code will bounce that data. That said, @wiedehopf posted a SED snippet, to modify both (i think) readsb with a "net-connect" command and an SED set that I have no idea how to add to my mobile feeder project, which is GPS / GPSd enabled. SEE: https://discord.com/channels/546776636352364576/568298837249359883/1058290599456940112 and https://discord.com/channels/546776636352364576/568298837249359883/1058295816206430288 You can also look for my posts over there for related issues. Since my mobile feeder is a Orange Pi 3 LTS. I have to make my own front end web page to work on a tiny 7" touch screen and can't use the ADSB-EX image. If you make any progress, LMK.
@Kuunanet Took too long getting back to you; I tried several times to go to those links, but all I got was a note at the bottom on a red banner saying messages failed to load. Could be I don't have auth for that channel. Either way, I'll leave MLAT turned off for now so I'm not making the server sort through bad data, because I know turning MLAT on and off will get lost in the shuffle. Might have a go at stopping/starting MLAT based off location change or speed over 5mph or something. I'll let you know if I make any progress. Thanks.
