Hi Frank,
It sounds like you are trying to manually configure the software. There is a much easier (and more efficient) method.
Download the latest software from...
https://pilotaware.lode.co.uk/downloads/OGN/PilotAware-OGN.latest.zip
You will currently get version 20200714 - please don’t use your pre-November 2019 version - it doesn’t contain the network or auto-update software.
Load this onto a fresh or fully reformatted card, install into your Pi, power up and leave it to unpack.
Log into the pi..
pi
12345678 (or later your own password if you’ve already set one)
Change directory (just type the bits in bold and hit [Enter])
cd rtlsdr-ogn
Then type...
./pilotaware-OGN.config.sh (in this step OGN is in caps)
This will automatically stop the rtlsdr-ogn service (which will be what is stopping your attempts) and lead you through the configuration process.
If you make a mistake, complete the sequence then power the Pi down, restart it, log back in (using your new password if you have already done that bit) change directory as above and re-run the config script.
Much easier than trying to stop/start the program and configure the files manually.
Best Regards
Peter
Hi Peter,
Thanks for your reply and info.
I'm just attempting to follow the setup information from here:
http://forum.pilotaware.com/index.php/topic,974.0.htmlwhich links to this document:
http://www.pilotaware.com/wp-content/uploads/2017/07/Building-an-OGN-PAW-Uplink.pdfI downloaded and unpacked the latest version as you suggested, but was still getting exactly the same error. HOWEVER I checked the directory contents and the penny dropped!! I typed ./PilotAware-OGN.config.sh and lo and behold it worked. It was the lack of capitals P and A in the right places that were causing the problem.
I note though the remote connection option using
http://ognpaw.local:4200/ still works on the latest version, none of the diagnostic ports:
http://ognpaw.local:8080http://ognpaw.local:8081http://ognpaw.local:8082listed in the above document seem to work now.
I've entered all the lat/long/height info etc, named the site and completed the setup but as yet can't see the station on the
https://ognrange.glidernet.org/ site. Whether it's because the Pi and aerials are inside at the moment I'm not sure, but I would have thought the station position would be sent to the server via the internet connection to update the location but I may be wrong - It's a learning thing!
I'm sure I'll have more questions as I progress, but it's a great project!
Thanks,
Frank.