Hi again John,
I'm confused
Your first post in this thread was on June 29th, effectively stating that... 'having installed the latest software I now cannot connect my PilotAware to SkyDemon on my iPad'. Your screenshots - posted in response to requests for further information - however, clearly show the date on the Home Screen as 'Wed May 23' and indicate that the update to 20180520 had already taken place by that date and that following the update, your licence was correctly installed and valid until the 17th May 2019 (PilotAware Version (20180520) License Expires (20190517)). This means that your previous license would have expired on 17th May 2018 - at least 3 days before the update was released. You would therefore have
had to renew the license and insert the New License Key either before or at the time of installing the update for it to take effect.
This morning, however, you said that...
I did look at my 192.168.1.1 and noticed that it said Licence expired.
When was this? For the reasons I have given above, I'm guessing just
before (or during) the download and application of the update.
The screenshots show that you are running a Pi2 based unit - presumably a Classic - but as others have indicated, they show no GPS device attached to the unit at the time the screenshots were taken -
viz. 'GPS Unavailable' on the Home Screen and no reference to
any GPS Device in the 'USB Devices List' at the bottom of that Home Screen. (The 3 devices listed are the Raspberry Pi Linux USB Controller, PilotAware SDR Dongle and WiFi Dongle). The absence of a GPS device would automatically stop the PilotAware Transmitting and would also mean that position data could not possibly be sent to your Nav Device, - hence the earlier queries as to whether you have (had) a GPS connected correctly.
If the GPS Device
was there at the time the screengrabs were taken, we need to find out why it wasn't (isn't) being recognised / reported.
The most likely reasons for this are either that the GPS device (or Raspberry Pi) has developed a fault, or that there is a software conflict stopping the device being recognised.
Your screenshot indicates that your PilotAware is running a fairly old Raspberry Pi 'Kernel' (Model B Pi 2, Kernel=3.18.7-v7+). IMO it would be worth updating this by carrying out a Full Manual Software Update as described in the Full PilotAware Operating Manual here...
http://www.pilotaware.com/180520-Operating-Instructions.pdf This should eliminate the possibility of a software conflict, though it WILL require reformatting the microSD card before downloading a copy of the Full Installation Image from
https://pilotaware.lode.co.uk/ and copying the content of the folder onto the re-formatted card as per the instructions. If you are unsure or feel you are unable to carry this out, we could probably arrange to help with this.
You will also need to re-configure your setup, including reinserting the License Key (which Keith has quoted above) and also insert the correct ICAO Hex ID and Flight ID (Reg ID) for your aircraft and we may need to review your other configuration settings as well as those on your Nav System.
Let us know how you get on.
Best regards
Peter
