Hi Team,
Came across something new today. Its the first flight I have done today after the new SkyDemon and PAW updates. I set S/D to PAW connection. (original connection type, FLARM) Sadly I could not get it to connect to S/D (No GPS) so reverted back to FLARM connection within S/D settings, 6000 Key, and all worked again as it should. I tried it few times, same result.
Just do be clear on my setup. I'm using FLARM RedBox also for my GPS source. OK Looking at my setup, I am using FLARM so It should be FLARM selected in S/D. but PAW is the WiFi connection to the Ipad so should it be PAW in the S/D settings?
This may be a Bug? Its not a problem for me but I just thought I would make Lee and the team aware of it. Sorry if you already know about it.
Hi Richard
Could you please post a copy of your home page from PilotAware?
Shouldn't be related to the redbox, but a possibility
Thx
Lee
Hi Lee
All working now but I have not had chance to test fly dew to Aircraft Annual today. I applied the latest update you have release this week Fitst then connnected succesfully to SD using PAW option. I'm not sure what the problem was.
Hi Richard,
Glad to hear you have now got it working after installing the latest update.
I was busy typing out the following post to you, when I saw you had posted the above.
I obviously know from previous posts that you are running Flarm RedBox and you say you are using your RedBox to provide both Traffic and GPS signals to PilotAware, so you presumably have the relevant PilotAware port configured to 'Flarm-IN' and also have your RedBox configured to provide 'Navigation
and FLARM' Data - so
NO PilotAware GPS device connected (this would automatically take priority).
For the connection to SD, you can use
either Flarm
or PilotAware. The settings in 'SkyDemon/Settings/Connectivity Options' relate to the
connection protocol,
NOT the device supplying the data. IMO the 'No GPS' message you got more likely indicates a breakdown in the PAW / SD connectivity, rather than a lack of GPS signal itself, and may have been due to the WiFi setting on your iPad being set to a Static IP address, which will NOT WORK on the UDP protocol used for the 'PilotAware' setting as Max has since found. If so, changing the PilotAware WiFi setting on your iPad from Static to to DHCP would have cured the problem.
Anyway, glad you've got it working.
Regards
Peter