Hi, OK, Firstly imagine my 2nd pi as your laptop or desktop Richard, that's what I use my second pi for, the uploader is running headless in the loft and I can connect to it with any computer downstairs, I use the term 'downstairs' figuratively as we live in a bungalow and the antenna is not in the loft it's on the roof now. The 2nd pi is exactly the same as the uploader a Pi3 B+ (just a different ip address) and the uploader is still uploading in the loft, otherwise, I would have been offline all this while which I didn't want to happen and it puts no pressure on me to get this one sorted that I am setting up in my office. My plan was to get the pi in my office up and running and then just go to the loft and swop them out (I am a bit allergic to the fibre glass in the loft, I'm itching now just thinking about going up there, so, the less time I spend in there the better as far as I am concerned) and I will still have a Pi3 B+ in my office to monitor with. I do have another dongle in my office wiedehopf, it's a nooelec and I generally use it on my Dell laptop with a nooelec Ham it up and SDR but I must admit I didn't have it connected to the pi this time, (that has probably been my problem with the errors as you point out) which is remedied now so, I am going to still carry on the way I am doing it, it gives me a better understanding of how they work and slot in together, which I like. The first time I started with adsbx it was so easy and I do realise now that it was my error not to have a dongle fitted, I normally do. I did have another 3 more paragraphs explaining what I have and what they do but I've deleted them and just suffice to say once I have set my mind on what a computer is going to do, that's what it does and like I said Richard me using my pi for monitoring is no different than you using your laptop or desktop, except I may have it on all day, I have the time now I've retired. Every one in the NHS Richard has a job to do and that is getting rid of this virus, any small part played is appreciated, you are obviously a modest fella Richard so we'll say no more about it, I stand by what I said. Cheers for now, I'll let you know how I get on.
No need to reimage by the way .... the readsb installation is fine. tar1090 you should just re-run the install script with an SDR fitted. If you want to check what readsb is doing, check the log: sudo journalctl -e -u readsb Once you plug in the SDR, wait a minute and check the log, it should have started up.
Hi, I don't know what happened but I've already written this post and when I clicked post reply it told me I had to log in but I was so I logged in again and it kicked me out for a security breech, don't know where my post went. Basically it was a resounding success, installed everything in the order given in your instructions wiedehopf and tested it out at the end of each stage and all worked well. I did also try again and do the same to the one in the loft but it still wasn't having it, it loaded your page at /radar but still not /tar1090 for some reason. I'm going to install PF and FR24 in this one in my office and then swop it out with the one in the loft. I do like your map at /radar it looks to me like a users map, we can do a lot more within the settings etc. Thanks Wiedehopf and Richard for your patience and guidance, it's been very much appreciated. Best Regards.
Now that's something we can probably debug .... Please show the ouput for these commands: sudo journalctl --no-pager -u lighttpd | tail -n20 ls /etc/lighttpd/conf-enabled Still might be easier to swap them, but if the loft is hostile terrain, there are probably other ways to make it work.
Hi, It's ok wiedehopf I can't explain for the life of me how it happened but between my desk and swopping it out with the one in the loft it loads now three different ways. 1. /radar 2. /tar1090 3. when you click on the my ip and you get the smiley faces, then feeder map. In fact this one runs better than tar1090 it keeps the range rings and the other radar plots I have setup but it used to be the other way round. The range rings don't work at all in tar1090 but I am happy with the my ip route. Thanks
https://github.com/wiedehopf/adsb-scripts/wiki/Automatic-installation-for-readsb#configure-location you need to configure the location in readsb.
I've lost all my a/c, nothing is showing on tar1090, I've zoomed right out and no one else has got them. I've tried putting back to as was and went from port 30053 to 30005 and back again. Incidentally, tar1090 works fine on the pi but not when I go on it in Windows.
I am having problems with these posts today, already sent this one but I can't see it anywhere. I've lost all my aircraft, I've zoomed right out and can't see them anywhere else.
That tends to mean that you have browser options selected that hide the aircraft .... filters / layers You're not saying what you are switching the port for. So in the browser :30053 is the planefinder webinterface. :30005 is where you get the beast data (raw data) .... that should not be used in the browser. Is /radar still working?
Hi Colin At least you appear to have made some progress through out the day. Right, I see the point of the 2nd Pi, used like a low powered desktop. Good luck sorting out the last little tweaks. Next step is VRS on a Pi. I did have it running at one point on a Pi Zero. Was a tad slow. R
I'm switching the port because when I first started this program the port was set at 30053 and I had a post from you to alter it to 30005 so I was just trying it again to see if it would make a difference but alas no. Yeah, I realise that now as it opens a map with the heading planefinder. No I don't use 30005 in the browser. /radar opens ok and you can zoom in and out and move the map about it's not frozen or jerky but it does not show any a/c. I have done another readsb install that went ok. When I tried a tar1090 install I am getting a Fatal error can't find aircraft.json file.
I found out something else as well with the pi3B+ that is running in my office, that has ip address 192.168.1.180, somehow the pi in the loft which is 192.168.1.131 and the one I am working on through MobaXterm was picking up a signal from 180 and displaying it because I thought I got my a/c back but when I shut 180 down the a/c disappeared and I was back to nothing. I didn't know they could do that unless they were set to do it. As far as I know there is no setting reference to 180 in the programming that is on 131.
Good morning, I have been going through this and re-installing as I go along and when I try to install adsbexchange-stats I get the following message. < No data available on port 30005! --------------------- It looks like you are running FR24 or RB24 This means you will need to install a stand-alone decoder so data are available on port 30005! We recommend using this script to install and configure a stand-alone decoder: https://github.com/wiedehopf/adsb-scripts/wiki/readsb-script > Whenever I try to install the 'readsb-script' I get through all of the manual inputs but it also stops at the setting up stage and then also comes up with the above message. I am guessing from this message that maybe FR24 needs to be installed before ADSBx, it didn't matter when I first installed these as I had dump1090 in the computer, should I install dump1090? or uninstall ADSBx and FR24? and then re-install them FR24 first then ADSBx. I don't want to clutter up the sd card in the pi with unnecessary programs but it is a 32GB so it has plenty of room.
Here ya go. Jul 20 07:03:28 raspi2 systemd[1]: readsb.service: Service RestartSec=30s expired, scheduling restart Jul 20 07:03:28 raspi2 systemd[1]: readsb.service: Scheduled restart job, restart counter is at 1098. Jul 20 07:03:28 raspi2 systemd[1]: Stopped readsb ADS-B receiver. Jul 20 07:03:28 raspi2 systemd[1]: Started readsb ADS-B receiver. Jul 20 07:03:28 raspi2 readsb[10735]: readsb: Too many arguments Jul 20 07:03:28 raspi2 readsb[10735]: Try `readsb --help' or `readsb --usage' for more information. Jul 20 07:03:28 raspi2 readsb[10735]: Command line used: Jul 20 07:03:28 raspi2 readsb[10735]: /usr/bin/readsb --device 0 --device-type rtlsdr --gain -10 --pp Jul 20 07:03:28 raspi2 systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE Jul 20 07:03:28 raspi2 systemd[1]: readsb.service: Failed with result 'exit-code'. Jul 20 07:03:58 raspi2 systemd[1]: readsb.service: Service RestartSec=30s expired, scheduling restart Jul 20 07:03:58 raspi2 systemd[1]: readsb.service: Scheduled restart job, restart counter is at 1099. Jul 20 07:03:58 raspi2 systemd[1]: Stopped readsb ADS-B receiver. Jul 20 07:03:58 raspi2 systemd[1]: Started readsb ADS-B receiver. Jul 20 07:03:58 raspi2 readsb[10759]: readsb: Too many arguments Jul 20 07:03:58 raspi2 readsb[10759]: Try `readsb --help' or `readsb --usage' for more information. Jul 20 07:03:58 raspi2 readsb[10759]: Command line used: Jul 20 07:03:58 raspi2 readsb[10759]: /usr/bin/readsb --device 0 --device-type rtlsdr --gain -10 --pp Jul 20 07:03:58 raspi2 systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE Jul 20 07:03:58 raspi2 systemd[1]: readsb.service: Failed with result 'exit-code'. Jul 20 07:04:28 raspi2 systemd[1]: readsb.service: Service RestartSec=30s expired, scheduling restart Jul 20 07:04:28 raspi2 systemd[1]: readsb.service: Scheduled restart job, restart counter is at 1100. Jul 20 07:04:28 raspi2 systemd[1]: Stopped readsb ADS-B receiver. Jul 20 07:04:28 raspi2 systemd[1]: Started readsb ADS-B receiver. Jul 20 07:04:28 raspi2 readsb[10807]: readsb: Too many arguments Jul 20 07:04:28 raspi2 readsb[10807]: Try `readsb --help' or `readsb --usage' for more information. Jul 20 07:04:28 raspi2 readsb[10807]: Command line used: Jul 20 07:04:28 raspi2 readsb[10807]: /usr/bin/readsb --device 0 --device-type rtlsdr --gain -10 --pp Jul 20 07:04:28 raspi2 systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE Jul 20 07:04:28 raspi2 systemd[1]: readsb.service: Failed with result 'exit-code'. Jul 20 07:04:59 raspi2 systemd[1]: readsb.service: Service RestartSec=30s expired, scheduling restart Jul 20 07:04:59 raspi2 systemd[1]: readsb.service: Scheduled restart job, restart counter is at 1101. Jul 20 07:04:59 raspi2 systemd[1]: Stopped readsb ADS-B receiver. Jul 20 07:04:59 raspi2 systemd[1]: Started readsb ADS-B receiver. Jul 20 07:04:59 raspi2 readsb[10851]: readsb: Too many arguments Jul 20 07:04:59 raspi2 readsb[10851]: Try `readsb --help' or `readsb --usage' for more information. Jul 20 07:04:59 raspi2 readsb[10851]: Command line used: Jul 20 07:04:59 raspi2 readsb[10851]: /usr/bin/readsb --device 0 --device-type rtlsdr --gain -10 --pp Jul 20 07:04:59 raspi2 systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE Jul 20 07:04:59 raspi2 systemd[1]: readsb.service: Failed with result 'exit-code'.
sudo journalctl --no-pager -u readsb | tail -n15 It's not showing everything, i'll need the output for the above command.
Round two [email protected]:/etc/default $ sudo journalctl --no-pager -u readsb | tail -n15 Jul 20 11:10:30 raspi2 readsb[28412]: Try `readsb --help' or `readsb --usage' for more information. Jul 20 11:10:30 raspi2 readsb[28412]: Command line used: Jul 20 11:10:30 raspi2 readsb[28412]: /usr/bin/readsb --device 0 --device-type rtlsdr --gain -10 --ppm 0 --lat 52.416300 --lon 00.757230 --max-range 360 --net --net-heartbeat 60 --net-ro-size 1200 --net-ro-interval 0.1 --net-ri-port 0 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005 --json-location-accuracy 2 --write-json /run/readsb --quiet 192.168.1.131,30005,beast_in Jul 20 11:10:30 raspi2 systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE Jul 20 11:10:30 raspi2 systemd[1]: readsb.service: Failed with result 'exit-code'. Jul 20 11:11:01 raspi2 systemd[1]: readsb.service: Service RestartSec=30s expired, scheduling restart. Jul 20 11:11:01 raspi2 systemd[1]: readsb.service: Scheduled restart job, restart counter is at 1589. Jul 20 11:11:01 raspi2 systemd[1]: Stopped readsb ADS-B receiver. Jul 20 11:11:01 raspi2 systemd[1]: Started readsb ADS-B receiver. Jul 20 11:11:01 raspi2 readsb[28445]: readsb: Too many arguments Jul 20 11:11:01 raspi2 readsb[28445]: Try `readsb --help' or `readsb --usage' for more information. Jul 20 11:11:01 raspi2 readsb[28445]: Command line used: Jul 20 11:11:01 raspi2 readsb[28445]: /usr/bin/readsb --device 0 --device-type rtlsdr --gain -10 --ppm 0 --lat 52.416300 --lon 00.757230 --max-range 360 --net --net-heartbeat 60 --net-ro-size 1200 --net-ro-interval 0.1 --net-ri-port 0 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005 --json-location-accuracy 2 --write-json /run/readsb --quiet 192.168.1.131,30005,beast_in Jul 20 11:11:01 raspi2 systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE Jul 20 11:11:01 raspi2 systemd[1]: readsb.service: Failed with result 'exit-code'. [email protected]:/etc/default $
