PilotAware
British Forum => Technical Support => Topic started by: Gary Nelson on August 25, 2020, 10:43:48 am
-
I and numerous others (going by the Facebook posts) are still plagued by the dreaded hanging message “Connecting to Device”. See attached image. I am using latest version iPad running Sky Demon and set to Pilotaware UDP. However, yesterday I could not run Sky Demon using PAW (so had to use the iPad internal Location Services to run Sky Demon) but frustratingly at same time I found my iPhone 11 connected and ran Pilot Aware to Sky Demon seamlessly.
It would be so good to resolve this issue for so many of us for what is otherwise such a great product!
-
Are you sure your Ipad was connectec to the Pilotaware WiFi?
-
Hi Gary,
If you see this issue again, can you check to see if you can see the web page
http://192.168.1.1
Also, if on iOS, can you add the PilotAware program from the iTunes store - this also checks connectivity
Thx
Lee
-
Gary,
I have had that a few times recently when trying to take screenshots during testing in bumpy conditions (SD on iPad Mini 5 using PilotAware UDP in both devices - both on latest Beta software). As you will know, to do this successfully, you need to press the power and home buttons at exactly the same time. On several occasions this has resulted in me shutting down the pad by mistake instead.
On restarting the Pad, it automatically reconnects to the PAW Wifi but SD ‘hangs’ on ‘Connecting to Device’. I have found that the quickest way to fix this is ‘Stop Navigating’ in SD then ‘Go Flying - Use PilotAware’. OK it means a break in the log, but this is easy to merge post flight.
The same thing can happen occasionally if you have PilotAware running and it drops out during engine start.
Regards
Peter
-
Lee - willdo to both suggestions - thanks.
Peter - every time this happens I always as a matter of course try “stop flying” then reconnecting but that generally doesn't stop the “Connecting to Device” hanging message.
Mariko - thanks for input but yes my iPad is connected to the PAW wifi.
-
Hi Lee
I attach screenshots of my iPhone and iPad from an earlier flight today - you can see the iPad is yet again showing the "Connecting to Device" hanging message while the iPhone is running PAW on SkyDemon just fine. I have the downloaded PAW track for that flight but it is 1.96Mb and this forum has a file size limit of 512KB. Should I send you this track somewhere? If so, I do hope it can give you a clue as to what is the issue!
-
Hi Gary,
There is definitely something strange going on here.
You said above that you are running the latest iPad mini (Mini 5/2019 - same as my newest one) and an iPhone 11, which I don’t have, but I regularly run two iPad Minis (2 / 3 / 5) in tandem without any connectivity issues other than as advised earlier. Both your devices are presumably running iOS 13 / iPadOS 13 (the same as my new iPad Mini - which as I say works fine). The only significant difference is that I am running the latest PilotAware and SkyDemon Betas on test (SD 3.14.3.256).
You say that you are running SkyDemon on PilotAware UDP - what setting do you have selected in PilotAware / Configure / Device Connect Setting ?
Also, am I correct in thinking that I see a FlarmMouse on the coaming? Is this connected into the PilotAware or running independently? Just wondering in case it could be significant.
You could put your track file in a Dropbox and PM Lee a link to the Dropbox, or alternatively Lee might PM you an e-mail address to send the file to.
Regards
Peter
-
Hi Peter
1. My 5th generation iPad runs 13.6.1. My iPhone runs 13.5.1 (but will update tonight)
2 I indeed have a Flarm mouse connected into the PAW
3. On the PAW/Configure/Device Connect Setting I have it set to PilotAware (UDP)
Gary
-
Thanks Gary,
So now we are at least on the same song sheet, though not necessarily yet on the same page and it doesn’t (unfortunately) immediately throw up any obvious explanation(s).
The obvious contender is some sort of WiFi connectivity problem - which is why mariko asked whether your iPad was definitely (still) connected to the PAW WiFi hotspot while it was displaying the ‘Connecting to Device’ message on SkyDemon and why Lee asked earlier whether you could connect to the PilotAware Home Screen on 192.168.1.1 via your browser during this period - which you haven’t yet confirmed. I realise that checking these two issues (especially during flight) is a significant ask, but it might be crucial to determining what is going on. We wouldn’t ask if it wasn’t important. The track log may of course also provide this information.
Regards
Peter
-
Hi Peter
1. I can confirm my iPad wifi source is indeed showing as Pilotaware when I get the “Connecting to Device” hanging message. It is always the first thing I check. Yesterday during the flight I then tried switching off the wifi and then back on. It quite happily reconnected Pilotaware as the wifi source but still got the “Connecting to Device” hanging message. I even switched the iPad entirely off and on in the hope that would make a difference. It did not, even though Pilotaware was once again the wifi source. On the flights I get the “Connecting to Device” message it is 50/50 whether at some point during that flight it starts working as then during the flight while on SD I keep flicking between the iPad internal “Use Location Services” which is 100% reliable and use “Pilotaware” until it works or I give up and continue the rest of the flight on “Use Location Services” and can’t see PAW traffic (which I still however hear via the PAW audio output plumbed into my transceiver).
2. I confirm I checked 192.168.1.1 and I can always always access the Pilotaware pages no problem. In fact last year I created a shortcut to my iPad home screen to this page so I can easily access PAW during a flight
3. I don’t see it can be the PAW wifi connection as yesterday it was simultaneously working on my iPhone while not working on the iPad - even though both devices had Pilotaware as the connected wifi source. Surely the conflict must be something else?
As I mentioned on my first post, there appear numerous others with this issue. I do hope the issue can be traced and hopefully sorted on what is otherwise for me such a fantastic product. I would be quite happy to purchase the upgrade from my Classic/ Standard PAW to Rosetta if that would evaporate the problem.
Gary
-
Morning Gary,
That helps narrow things down considerably!
First point - PAW is still running (confirmed by the audio alerts and the fact that your iPhone is still running SD).
Secondly - WiFi connection isn’t dropping out as both devices are still connected to PAW WiFi and you can still access the PAW screens via 192.168.1.1 on your iPad.
But the problem must still be due to some sort of connectivity issue between PAW and SkyDemon via iOS - but why only on the iPad? As stated above, mine - using the iPadOS 13.6.1 software is running fine apart from my finger-induced disconnects.
You have also indicated that you are running a PAW Classic, which does raise a couple of other possibilities, such as interference to the WiFi from a faulty SDR (or WiFi dongle) which could I suppose be causing a partial or intermittent block to the WiFi signal - but why would that only affect the iPad - unless there is some sort of proximity or blocking issue...
If you are flying again soon, it would be worth temporarily removing the 1090 SDR dongle for a short flight and see if that makes any difference to the connectivity - keep a good lookout though!
The other thing to try (after reinstating the SDR) would be using the Flarm TCP option on the iPad, with the iPhone remaining on PilotAware UDP. To do this you will need to set Connectivity Options to Auto in PAW to allow the iPhone to remain on UDP and the iPad to receive data via Flarm TCP. Select ‘FLARM with Air Connect’ in SD Setup Third-party Devices on the iPad (with Air Connect Key at the default 6000), then select ‘Go Flying - Use Flarm’ on the iPad (on phone continue to use ‘Use PilotAware’ as at present). Let us know what happens.
Finally, Lee has done a lot of work over the past year to improve connectivity for both Apple and Android devices and this will all be in the imminent new software release - currently in final Beta testing and now due for release within days. We could give you access to an advance copy to see if that resolves the issue, but please try the suggested tests on your existing setup first and let us know if either or both improve the situation - oh and let’s get your track file to Lee for analysis please.
Best Regards
Peter
p.s. I tried to find the Facebook posts you referred to in your OP but failed miserably. Can you point me to where they are please (for my own illumination).
-
Hi Peter
Re Facebook posts, if you go to the EV-97 Group and see the post started by Gordon Verity on 12th July 2020. There are now some 83 replies. His opening post was”.....Does anyone else have issues connecting Pilot aware to SkyDemon on a tablet from time to time? Seems to work perfectly for a couple of legs then get in the plane and it won’t connect. So have to go back to using the internal GPS in the tablet. All seems a bit flakey at times
-
.
-
Hi Peter
Re the last 3 paras of your post:
1. If i temporarily remove the 1090 SDR dongle for a short flight to see if that makes any difference to the connectivity, will that not disable the PAW as isn’t that the PAW wifi? So removing that will stop PAW transmitting to my iPad and iPhone, or am I getting confused?
2. Not sure what/where is the Air Connect Key at the “default 6000” but anyway I dont think Flarm will then show on my iPad as I have been told you need to pay an annual £30 to receive Flarm on SD if not piggy backing it via PAW
3. If days away then perhaps I should simply wait for the release to see if it cures this, especially as to physically access my Classic PAW I have to remove about 40 screws to take off a panel on my Eurostar.
3.1. What email shall i send the track file to Lee for analysis.
Thks
Gary
-
Morning Gary,
Re your recent posts above... Not being a member of the EV97 Forum, I was completely unaware you guys were having all these problems. I will investigate further. Thanks for bringing this to our attention.
Hi Peter
Re the last 3 paras of your post:
1. If i temporarily remove the 1090 SDR dongle for a short flight to see if that makes any difference to the connectivity, will that not disable the PAW as isn’t that the PAW wifi? So removing that will stop PAW transmitting to my iPad and iPhone, or am I getting confused?
The 1090 dongle is the one in the USB port with the cable to the small thin 1090 antenna. The WiFi on the Classic is the smaller black dongle with a red ring round it. (On Rosetta or an ‘upgraded’ Classic with a Pi3 Motherboard, the WiFi chip is on the Motherboard).
2. Not sure what/where is the Air Connect Key at the “default 6000” but anyway I dont think Flarm will then show on my iPad as I have been told you need to pay an annual £30 to receive Flarm on SD if not piggy backing it via PAW
Sorry for the confusion - this is nothing to do with ‘receiving’ Flarm. It is just using the Flarm ‘Protocol’ over a different transmission system (called TCP) to transfer data between PilotAware and your device instead of via PilotAware UDP. Set Device Connect Settings in PilotAware / Configure to ‘Auto’ then on your iPad only go to SkyDemon / Setup / Third Party Devices and select the ‘FLARM’ option. You should see the reference to ‘Air Connect Key’ just below this selection - it’s just an unlock code - as long as it says 6000 it will work. Then when you ‘Go Flying’ choose the ‘Use Flarm’ option on your iPad. On your phone just choose ‘Use PilotAware’ as normal. PilotAware is designed to allow multiple connections using different mixes of operating systems and protocols - I just want to confirm whether this helps with your connectivity issue,
3. If days away then perhaps I should simply wait for the release to see if it cures this, especially as to physically access my Classic PAW I have to remove about 40 screws to take off a panel on my Eurostar.
Ah! A VERY interesting comment - where exactly is your unit fitted? If it’s buried that far inside the metal bodywork, that could well explain the connectivity issues... The PAW WiFi may simply be getting blocked by the amount of metalwork between it and your iPad, while the phone may be in a slightly less obscured position. If this is the case, you can try tweaking the WiFi settings in the PAW ‘Network’ Screen, but take note of your initial settings (let me know what they are) and make any changes in small steps - IIRC PAW needs a reboot for each change to take effect. If this is the problem, you could move the WiFi dongle somewhere out in the clear on a USB extension cable.
Although the software update is now ‘imminent’, I can’t guarantee ‘a few days’ , and in the light of this new info, the problem might be to do with the position of your unit, not with the software, so let’s investigate further before you update your software.
3.1. What email shall i send the track file to Lee for analysis.
Thks
Gary
Send the track to support@pilotaware.com and mark the e-mail FAO Lee, he will be able to pick it up from there
Best Regards
Peter
Edit at 09:10: I have now read the full thread concerned on the EV97 Forum. If anything it increases my conviction that your problem is most likely due to a WiFi proximity/obscuration issue between your PAW (Classic) and your iPad. If so, you need to try adjusting the WiFi strength (up and down from the default) and/or relocate your WiFi dongle on a USB extender to outside the ‘metal box’.
-
Hi Peter
1. I have just now emailed Lee the Track and also 2 snapshots of (1) my iPhone and (2) my iPad, during this same flight showing iPhone running SD with PAW fine and at same time iPad showing "Connecting to Device"
2. I attach 3 photos showing the PAW installation with the 40 bolt panel removed and I have added some comments on this to help.
Rgds
Gary
-
Thanks Gary,
I have also e-mailed Ash and will copy that e-mail to Lee.
The photos reinforce my thoughts that we need to look at the WiFi setup/ position.
Edit: We have in the past had connectivity issues with some (Android) tablets where the problem was that the WiFi signal was too strong. Bearing in mind the proximity between your iPad and PAW that could be the issue here.
Regards
Peter
-
Hi Peter
I did wonder if it could be a proximity issue as it is literally on the rear of my console from where the iPad sits whereby my iphone (which is more solid in running SD/PAW) would be about 30cm away. See PAW page attached showing i have currently set on 50mv - is that what you mean?
-
Hi Gary,
Yes, that’s the one. Try increasing (or decreasing) in stages by say 10 at a time and check the effect after each change before going further. Remember, each time you ‘Apply’ the new setting, you need to wait for the unit to reboot.
Peter
-
Peter
Presumably as the iPad and PAW are on opposite sides of same part of my instrument console I should start with decreasing rather than increasing ?
Rgds
Gary
-
Hi Gary,
That sounds logical. Try a couple of steps and see how you get on. IIRC with the Android issue some users had the WiFi power down as low as 10mW, but you just need to experiment to see what happens with your specific circumstances.
Regards
Peter
-
Hi Gary
Can we confirm it is a connection issue first
1. Can you get a hotspot connection ?
2. Can you access the paw webpages?
Thx
Lee
-
Hi Lee
Yes is the answer to both questions. When I get the "Connecting to Device" hanging message I invariably check my Ipad settings to see if the iPad is still showing PAW as the wifi connection (it invariably is) and then use an iPad short cut link I created on my iPad to get onto the PAW webpage and I always can, no problems.
The above "proof of connection" is not a surprise to me in light of the fact my iPhone 11 is far less flakey at getting PAW to work with SD and although it may occasionally still get me the the "Connecting to Device" message, that is far less likely. See screen shots I previously posted (and emailed you when I sent the Track) of iPhone and iPad within a few seconds of each other showing only iPhone running SD/PAW and iPad showing "Connecting to Device"
rgds
Gary
-
Hi Gary
Thats good news, I am confident this issue is fixed in the next release
I will give you instructions within the week
Thx
Lee
-
:D that is good news - are you able to elaborate a little as to what was the issue?
-
May I add a few comments as I suffer the same issue. I fly a Robin DR400 using Sky Demon running on an iPad 4 using IOS 13.6.1 and Pilot Aware Rosetta running last year's (2019) software upgrade.
ALWAYS on the outbound leg of a trip the iPad connects seamlessly to Rosetta. ALWAYS on the return leg it refuses to connect and I am left with the hanging message as in this thread.
The only answer is to use Location Services and fly back without the benefit of Rosetta.
Interestingly on a recent trip away where the plane was parked for two consecutive nights away the same thing happened on our return, although it was the first flight of the day!! The only thing was we were away from base.....Explain that!!
On all legs the location of Rosetta and the iPad are identical and are in line of sight to each other about one metre apart. A stable power supply is feeding the Rosetta.
The only thing I haven't tried is to connect to Rosetta with Sky Demon on my iPhone 8. I will try this in the future.
I have tried most things suggested in this forum including firing up Rosetta first, waiting, then starting up Sky Demon. Nothing I have tried works.
I have just upgraded IOS to 13.7 on the iPad and downloaded the latest software from PAW. When the plane returns from Germany I will try with this new software and see what happens.
Any comments from Pilot Aware developers would be welcome. It is potentially a great bit of kit being spoiled, at present, by this problem.
-
To correct a minor error in my previous post. I use an iPad MINI 4. jrb
-
One possibility (perhaps, maybe) is that your Rosetta is picking up a Wifi signal from somewhere else when you visit and, therefore, your PAW is not actually connected to your iPad any more. On the way out, because there are no aberrant Wifi signals for it to connect to, it behaves itself but at the turnaround airfield etc it may connect to something else.
I only say this because the other day my iPad was locking onto a local Wifi and, therefore, my PAW wasn't connecting to my iPad and SkyDemon. I realised what was happening and just went into Settings and Wifi and 'clicked' on my PAW Wifi and all was well for ever after.
Of course, I may well be talking coomplete and utter bolleaux and it might be far more complex than that but it is a really easy thing to check. Just make sure your Wifi is connected to your PAW before telling SD to navigate.
-
Hi Jrb
Yes, exactly the issue a number of us have! Re PaulSS post just before, it is not that, as that is something I check every time the issue arises!
Ashley from PAW phoned me a few days ago about this issue. He mentioned the iPad OS has some differences to the iPhone OS and so could be a possibility why the iPhone gives a more consistent connection.
We agreed I would add a password to PAW as that may help iPad “see” PAW as a “Trusted Device” and therefore improve connectivity. I did two flights today with a PAW password (45 minute flight to Kent in morning and back in afternoon). Worked perfectly both ways. Fingers crossed but if it gets flakey again I will report here.
It would be interesting to know if others with the issue try a PAW password and what happened
-
Hi Gary,
Thanks for the feedback on the password test. Glad to hear that it appears to have helped.
Are you still running 13.6.1? I noticed a couple of days ago that my iPad Mini 5 is trying to update to iPadOS 13.7 but I have postponed the update until we are sure we have got to the bottom of your (and the others’ ) connectivity issues with 13.6.1.
I will continue to liaise with Ash and Lee, but please keep us posted on here if you experience any further issues either negative or positive.
Best Regards
Peter
-
Both my devices are on 13.6.1.
-
Thanks Gary,
I will obviously have to allow the update to 13.7 at some point, but suspect it doesn’t contain the ‘fix’ we need, so am holding off meantime.
p.s. for anyone else experiencing the same issue as Gary - please feel free to try adding a password to the PAW WiFi (in Network) and let us know if this helps in your case, but remember to use a password you won’t forget, as if you do you won’t be able to get back into your PAW. If this happens, the only way to ‘reset’ is by a full software reinstall on a new or freshly reformatted microSD card, so keep the password short, simple and memorable - on this occasion, security level is less important than memorability.
Regards
Peter
-
Hi Graham,
Most of my ‘gang’ up here have changed the default SSID to our aircraft Reg, which helps, but in my case, my pad has been connected to so many other PAWs while configuring/updating/checking other users units, that I always check for the right connection after startup.
The worry with using a password is as reported above. I know a few who will forget it with the resulting need to do a complete re-install before they can use their PAW again.
If ‘security’ is the problem with iPadOS 13.6.1 (or later), we probably need to look to a more technical solution.
Regards
Peter
-
Thanks to PaulSS and Gary for responding to my post. I do check the iPad is connected to PAW when I have the connection issue, so that is not the problem.
I am intrigued that a password may be the answer. Unfortunately, as I said, our plane is in Germany for a week or so at present so I am not able to check out that theory. When it returns I will upgrade the Rosetta software and install a password and see what happens............ I will report back.
-
Hi all, whenever I get this error - usually I have to go into ipad settings and turn off wifi- then turn on and that usually fixes it.
-
Hi David,
How often are you experiencing this issue? and also... Which version of PAW and which iPad model / iOS (iPadOS) software version are you running on your iPad?
We are now pretty sure this is iPad specific (at least as far as 'Apple' Devices are concerned) and need to improve our understanding of what exactly is causing the connection failures.
Regards
Peter
-
The saga continues but now iPhone!
My iPhone 11 just upgraded its operating system. Since this upgrade last week my iPhone refuses to connect PAW to SD and I just get the hanging message “Connecting to Device”. I then upgraded PAW a few days ago to the new upgrade but my iPhone still won’t connect - any thoughts!
PS my iPad is currently running PAW with SD perfectly!
Gary
iPad mini 5 IOS13.7
IPhone 11 IOS14.0
PAW classic Version 20200909
SD on iPad Version 3.14.2.254
SD on iPhone Version 3.14.3.258
-
Rule 1 of any technology: control the updates yourself, don’t let them happen automatically, particularly when it’s a completely new version!
-
The saga continues but now iPhone!
My iPhone 11 just upgraded its operating system. Since this upgrade last week my iPhone refuses to connect PAW to SD and I just get the hanging message “Connecting to Device”. I then upgraded PAW a few days ago to the new upgrade but my iPhone still won’t connect - any thoughts!
PS my iPad is currently running PAW with SD perfectly!
You can try forgetting the PAW WiFi network on the iPhone and then re-join it.
-
This has also been reported on the SkyDemon forum
Its an issue with SkyDemon/ios14
It also seems to be linked to UDP data - used by the settings Pilotaware and gdl90
If you tell SD to connect (To Pilotaware) using flarm (TCP) it connects
I think Tim is aware of this issue
Thx
Lee
-
This has also been reported on the SkyDemon forum
Its an issue with SkyDemon/ios14
It also seems to be linked to UDP data - used by the settings Pilotaware and gdl90
If you tell SD to connect (To Pilotaware) using flarm (TCP) it connects
I think Tim is aware of this issue
Thx
Lee
SkyDemon update has come out today, with a fix for some iOS 14 issues.
-
I’ve also been having these issue recently, I believe it’s an IOS issue. I have noticed within IOS 14 the WiFi settings have changed. There is an option to change your MAC address to each WiFi device you connect to, so you cannot be traced. I have turned this off on trusted WiFi points. I have attached some screenshots with the connection to my home WiFi. I’ll be flying later today and will be doing the same for my PilotAware, so I am hoping this will fix this problem, if not I’m sure there will be a fix soon. Still running last year version of the PilotAware OS (latest release) on a Rosetta.
Sorry unable to attach images, if you go to the settings on your iOS and click on WiFi, then click on the (i) next to your PilotAware connection and turn off Private Address, this might help with this connection issue. I have yet to try as only found this out myself on Saturday.
Happy flying all :) :)
-
SkyDemon update has come out today, with a fix for some iOS 14 issues.
Hi Jeremy,
I can’t see any new SD update - can you point me to where you found it please.
I am currently running SDBeta 3.14.3.258 which was released last Wednesday, but I still had difficulty connecting using UDP when I tried on Saturday evening.
Edit: Tim D has just posted on the SD Forum a few minutes ago that SD Version 3.14.3.258 was released yesterday. It probably doesn’t show as my pad is already running that version as a Beta - though worryingly, that was what I was running when I experienced the connectivity problem on Saturday evening!
Further testing since shows that (as Lee has reported) using the ‘Flarm’ TCP option certainly works, but mysteriously seems to have also restored my ability to reconnect using UDP and GDL90.
I have also just tried Alan’s ‘Switch Off Private Address’ option, which also seems to work, but I don’t know whether that is because I had already gone through the ‘Use Flarm’ loop first. I will await further feedback and developments.
Best Regards
Peter
-
I will check on my version of SD but I flew today, hadn’t changed any settings and everything worked as it usually does/did. My iPad Mini has the 14 update and my Pilot Aware is on the latest version but I didn’t need to change to the Flarm setting and yet it still worked normally.
Edited to add: My SD is version 3.14.3.258 but that update was performed after the flight. In other words, I had the previous SD version, the iPad Mini on 14 and the latest PAW and all was well.
-
Similar problems here.
iPad mini 4 running ios 13.7 and Sky Demon 3.14.3.258 connects to Pilot Aware no problem.
iPhone 8 running ios 14 and Sky Demon 3.14.3.258 will not connect to Pilot Aware. Just "hangs".
iPhone will connect to Pilot Aware (192.168.1.1) so appears to be a Sky Demon/ios 14 issue rather than iPhone issue. Sky Demon works fine on "location services".
Hope that makes sense!
-
ps I tried the "flarm" and "Private Address" suggestions to no effect. jrb
-
The promised feedback.
Rosetta updated to 20200906, "Device Connection Settings" set to "Pilot Aware UDP", password protection applied.
Flew yesterday and had absolutely no problems connecting to PAW either outbound or return legs.Not sure which change fixed it but seems sorted!
iPad mini 4 ios 13.7, running Sky Demon 3.14.3.258 & PAW 20200906
However as in previous post iPhone will not connect Sky Demon to PAW!
iPhone 8 ios 14, running Sky Demon 3.14.3.258 & PAW 20200906.
-
Hi Jrb
Have you logged this on the SkyDemon forum ?
http://forums.skydemon.aero/Topic32191.aspx#32201
Thx
Lee
-
Thanks Lee. Yes I've been following the Sky Demon forum you suggest. Didn't seem to fix it for me. I will get the Rosetta out of the plane and try again as it seems fixed for others.
-
Exactly like jrb reported above, my iPhone is still stubbornly refusing to run SD with PilotAware since my iPhone upgraded to IOS 14.0, even with the SD iPhone upgrade to 3.14.3.258.
My iPad (still on old IOS13.7) continues to work fine.
Gary
iPad mini 5 IOS13.7
iPhone 11 IOS14.0
PAW classic Version 20200909
SD on iPad Version 3.14.2.254
SD on iPhone Version 3.14.3.258
-
To update here
I have
iPhone SE upgraded to IOS 14.0,
SD iPhone upgrade to 3.14.3.258.
Connecting correctly
I suggest adding to the SkyDemon thread listed earlier
There is clearly still some issue here
-
Hi Gary / All,
As reported previously, I did have a connectivity problem with my iPad mini 5 on Saturday evening.
After updating my pad to iPadOS14, I tried it with my spare Rosetta - newly updated to PAW 20200906 - and with the latest SD Beta 3.14.3.258, which I had received from SkyDemon via Apple TestFlight last Wednesday.
The iPad connected to the PAW WiFi straight away and all the PAW Screens (including PAW Radar and METARs) were available via 192.168.1.1. I then checked the SD Third Part Device Settings - Set to PilotAware only. Clicked on ‘Go Flying - Use PilotAware’ and SD just hung on ‘Connecting to Device’.
After leaving it for quite a while, I ‘Stopped Navigation’ and went back to check my PAW ‘Device Connect’ setting - which was set to ‘All’.
Back to SD Third Party Devices again and added ‘FLARM with Air Connect’ (without removing the PilotAware option). This brought up the Air Connect Key ‘1234’, which traditionally always had to be ‘reset’ to ‘6000’ for PAW, but I decided to leave it at ‘1234’ to ‘see what happens’. I then selected ‘Go Flying - Use FLARM with Air Connect’ - SD immediately showed a new Banner (at least new to me) - ‘Authenticating’ then ‘Seeking GPS Satellites’ then went to its normal display screen with my Ownship, local Ground Station (now shown as a mast) and local ADSB Traffic displayed.
On Sunday morning, I decided to retry using the PAW setting only, which surprisingly now worked as normal. I then re-added the Third Party Device Options for ‘FLARM with Air Connect’, ‘uAvionix SkyEcho2’ (which I don’t have) and ‘GDL90 Compatible Device’ and found that all of these also connected to PilotAware and displayed traffic.
I have since had a direct e-mail exchange with Tim Dawson (under my ‘SD Testflight’ hat), which confirmed that SD Beta 3.14.3.258 - which I had been using up to Saturday Night, was subsequently released as the new 3.14.3 Public Release (with the same version number), though in light of my experience outlined above, I find it difficult to believe that nothing has changed between my receiving the Beta last Wednesday and the final Public Release over the weekend - especially as the ‘fix’ to deal with iOS 14’s new ‘local network permissions’ was reportedly incorporated in the previous SD Beta 3.14.3.257 issued on 8th September. If that was so, why did I still experience the connectivity issue on Saturday Evening running the final beta for the upcoming 3.14.3.258 Public Release?
For the avoidance of doubt, I have tried it again today, with only the PilotAware option set in SD Third Party Devices and SD connected straight away as intended.
There is, however, obviously still something weird going on, as most of you were previously reporting that SD 3.14.2 was connecting fine to iPhones on iOS 13.7 even when your iPads weren’t - and now, since the update to iOS 14 / iPadOS 14, the opposite seems to be the case!
Hopefully SD will get to the bottom of it soon, but I suggest keep reporting specific occurrences to them on the SD Forum. There is a specific ‘iOS 14’ thread in forums.skydemon.aero/Topic32191-2.aspx
Regards
Peter
-
Morning All,
Interestingly, SkyDemon has just issued a new Beta 3.14.4.259 for testing via the Apple Testflight Network.
What to test.
Some iOS 14 reliability improvements are being tested, particularly for the SkyEcho device.
I have just loaded it on this iPad Mini 5 with iPadOS 14 and running with a standard Rosetta loaded with PAW 20200906.
Pad connects to PAW, all screens including Radar and Metars working as expected. Device Connect Settings on Rosetta set to ‘All’.
SD Third Party set to PilotAware (Only). ‘Go Flying - Use PilotAware’ displayed ‘Connecting to Device’ banner for a brief fraction of a second then went straight to SD display, with Ownship, Ground Station and Traffic.
Can’t test it on an iPhone as I don’t have one, but hopefully one of the other Beta Testers will be able to do so shortly. If I see any reports I will report back here. Fingers firmly crossed.
Regards
Peter
-
3.14.4.260 has just been made available, seemingly to further help UDP connectivity issues.
-
Thanks Graham,
I received 3.14.4.260 (Beta) a couple of hours ago. I have downloaded and tested it on my iPad Mini 5 with iPadOS 14.0 and PAW 20200906. No connectivity (or other) issues noted using PAW UDP, Flarm or GDL90 settings, so looking hopeful. Can’t test on iPhone though as I don’t have one.
Test Result reported back to Tim D.
Best Regards
Peter
-
I just did the update via my iPad mini and guess what... SD hangs on Connecting to Device, just like all these long running reports in this thread. So now I have no working PAW, I wish I hadn’t done the update. Given the apparent extent of this problem, I hope somebody identifies the cause as a matter of urgency.
-
Try connecting via the Flarm protocol, and if that works, retry by connecting via PilotAware. Anecdotally, that makes it work for at least that session.
As noted above, Tim has issued a SkyDemon beta which appears to resolve the problem (or actually works around it until Apple fix iOS/iPadOS) which should go out on public release in a couple of days.
-
I don't have Flarm so cannot actually use that workaround but I am delighted to see you say that its an Apple matter that will be resolved in a couple of days. Thanks. The PAW software is SO astonishingly impressive that what I don't understand is why this problem, clearly affecting so many, exists at all since this is not a Beta update and as such, one imagines was vigorously tested and found to work.
-
I don't have Flarm so cannot actually use that workaround but I am delighted to see you say that its an Apple matter that will be resolved in a couple of days. Thanks. The PAW software is SO astonishingly impressive that what I don't understand is why this problem, clearly affecting so many, exists at all since this is not a Beta update and as such, one imagines was vigorously tested and found to work.
You don't need to have FLARM.
What is being suggested is that the FLARM protocol is used to send information from your PAW to the device running SD.
In order for this to work you would need to select this in both your PAW and Skydemon on the receiving device.
Please see destructions for both ends...
-
I don't have Flarm so cannot actually use that workaround but I am delighted to see you say that its an Apple matter that will be resolved in a couple of days. Thanks. The PAW software is SO astonishingly impressive that what I don't understand is why this problem, clearly affecting so many, exists at all since this is not a Beta update and as such, one imagines was vigorously tested and found to work.
It's nothing to do with SD code, but all to do with Apple changing things in iOS14 to 'improve security' and cocking it up.
-
I have a PilotAware Rosetta. It did have the 2019 software but I have successfully updated to the new September 2020 software version.
I use an iPad mini 4 with latest software (14.0). I can log onto the PAW via 192.168.1.1 and everything is working OK. Radar screen works and traffic is being detected.
HOWEVER I cannot connect to the PAW via SkyDemon. I just get the message "connecting to device" and nothing happens. Until a couple of weeks ago it worked perfectly. It would display "Connecting to device", then announce how many satellites it had found and off we went. I have checked the set-up in SkyDemon and everything is as it is meant to be.
The problem occurred first in the 2019 version of the PAW but is exactly the same in the new 2020 version.
I didn't touch or change anything before the problem appeared but there may have been SkyDemon updates or Apple OS updates in between it working and it not working, I'm just not sure on that point.
Advice would be welcome before I start pushing buttons at random!
Peter
-
http://forum.pilotaware.com/index.php/topic,1901.0.html (http://forum.pilotaware.com/index.php/topic,1901.0.html)
Page 3 onwards.
-
I have been having the same issue with SkyDemon in jabiru J430 (so no bits of metal to interfere with the signal). SkyDemon will still not connect even when a few centimetres from the Rosetta. But iPad will still connect direct to the PAW over 192.168.1.1
There are no other sources of interference as these tests have been outside the aircraft.
Switching off an on again has no effect on the problem.
Peter
-
Hi Peter K,
It’s nothing to do with the signal between PAW and the Pad. The signal is still there and you should still be able to connect to PAW via your browser on 192.168.1.1 and see all the screens. But Apple (and AFAIK Android) have made changes to their software - supposedly to improve security - which, at least in Apple’s case deliberately stops the App (in our case SkyDemon) connecting to an ‘unrecognised’ WiFi access point via ‘passive’ protocols such as UDP and GDL90. Tim & the SD Team have spent ages this week implementing a workaround to enable connection pending Apple (& Android) sorting out their own mess.
In the meantime we discovered that an active connection protocol like TCP (used by FLARM - and the original connectivity option used by PilotAware) causes iOS to grant the relevant access permission to the app, after which the permission is ‘remembered’ and the app can (usually) then also connect using the other protocols. As reported above, it’s nothing to do with interference or whether or not you can receive or transmit FLARM.
Hope this helps clarify the position. Can’t guarantee it will work with all devices though.
Regards
Peter R
-
Hi Peter,
I have just updated on this issue over in the other thread. Just back from flying using iPadOS 14.0 on my iPad Mini 5 with the latest SkyDemon 3.14.4.260 - all working reliably.
Just noticed that Apple have now released iPadOS 14.0.1, which will hopefully contain the ‘fix’ to sort the connectivity issue. I am in the process of updating my iPad, but address this problem, though from my understanding of the problem it really needs someone who hasn’t already tried the ‘FLARM Protocol’ work round to test and hopefully prove the efficacy of the ‘fix’ (assuming that is what the new version is intended to address (Apple aren’t good at telling users exactly what is going on).
Regards
Peter
-
Hi All,
Just noticed that Apple have released iPadOS 14.0.1, which will hopefully contain the ‘fix’ to sort the connectivity issue. I have just updated my iPad Mini 5, which allows SD to connect to Rosetta straight away using SD version 3.14.4.260, but from my understanding of the problem it really needs someone who hasn’t already tried the ‘FLARM Protocol work round’ to test and hopefully prove the efficacy of the ‘fix’ (assuming that is what the new version is intended to address - Apple aren’t good at telling users exactly what they are up to).
Looking forward to some positive feedback.
Regards
Peter R
-
Unfortunately the Apple update to 14.0.1 has no effect on the problem.
As others have found if you connect via Flarm Air connect the PAW will work and show location.
If you then switch back to PilotAware in third party devices the iPad will connect as usual when you select PilotAware from Go Flying. I did not have time to try to see if all the traffic options were function as usual but the radar screen was certainly OK.
So it looks like the origin of the problem is some connectivity glitch between SkyDemon and PAW, whether exacerbated by Mr Apple or not I cannot tell.
The only other idea I had was to reinstall SkyDemon but that is for later in the day.
Peter
-
My SD on iPhone 8 just updated to 3.14.4.260 and iOS to 14.0.1 and all connected with no problems. (With a few "conditions" which you have to accept on SD).
Not sure if it was the SD update or the iOS update which fixed it. Although previous post suggests it wasn't iOS 14.0.1
iPad mini 4 running iOS 13.7 and SD 3.14.3.258 still connects no problem.
Have I the nerve to update iPad to iOS 14 ???
-
Hi jrb,
Please do try the update on your iPad, and also update SD to 3.14.4.260, then try connecting using the PilotAware UDP option - (preferably with the FLARM option deselected in SD) and let us know what happens.
From conversations with Tim Dawson last week, what you have described with your iPhone is exactly what they expect to happen with the SD Mod contained in 3.14.4.260, but I can’t test it as I have already used the ‘FLARM prompt’ workaround on my iPad.
Regards
Peter
-
Hi Peter,
It might be a few days before I am at the airfield again. (Rosetta lives in the ‘plane as it is jointly owned). Nervous about updating iPad as it is my primary navigation aid (after chart and mk 1 eyeball of course). The success with iPhone gives me some confidence......
iPad still running SD 3.14.3.258. Can’t see a way of forcing it to update other than delete and reinstall App. Unless it needs iOS 14 to prompt an update?
Will feed back in a few days when I try it.
-
Just my two cents:
ipad mini 5 with iOS 14.0 and SD 3.14.3 connected to paw via udp pilotaware, however ground station and traffic was not visible.
Update to SD 3.14.4 solved the problem, even with iOS 14.0.
An update to 14.2 had no changes. So all working fine here and SD update did the trick for me.
I did not try Flarm, gdl or any other connection type.
Kind regards
Patrick
-
Hi jrb,
Update to iPadOS 14 may prompt the new SD update. If not, the latest version in the App Store is 3.14.4, so deleting and reinstalling certainly does go to SD 3.14.4.260 (or later).
Regards
Peter
-
PROBLEM SOLVED!!!
I am relieved and delighted to report that the fix just happened autonomously. All I did was go to the App Store on the iPad and I ran the SD Update (to 3.14.4.260) and it all just WORKED! No involving Flarm or other protocols or workarounds.
From that I imagine there's a good chance the problem lay in SD rather than PAW and so the brilliant marriage of the two services is restored. I am praying the fix does not revert and that all the rest of us on this Forum will enjoy the same successful outcome.
Many thanks to all those who contributed their experiences and suggestions
-
iPhone 8 running iOS 14.0.1 & Sky Demon 3.14.4.260
iPad mini 4 updated to iOS 14.0.1 & Sky Demon 3.14.4.260
Both connecting to Pilot Aware with no problems using UDP without previously connecting via Flarm TCP )
Thanks to all for suggestions and fixes. (Especially, I suspect, team at SD).
jrb
-
Hi jrb,
Thanks for having the courage to grasp the nettle and do the updates, and for updating us all on the result.
I’m glad to hear we have a working solution - and thanks to the SD Team for their prompt action.
Best Regards
Peter
-
Thanks SD. Both iPad and iPhone now running PAW through SD perfectly and no “Waiting for Device” messages any more. I am however keeping iPad on IOS13.7 and not upgrading just yet.
Gary
iPad mini 5 IOS13.7
iPhone 11 IOS14.0.1
PAW classic 20200909
SD - iPad 3.14.4.260
SD - iPhone 3.14.4.260
FLARM 7.01
-
Hi Gary,
Glad to hear things are working at last. Thanks for letting us all know.
It’s a real pain when the likes of Apple decide to ‘improve’ things without properly considering the effect their changes are likely to have on others. Not the first time either and I’m sure it won’t be the last.
Best Regards
Peter
-
I know I'm late to the parade (and only repeating what has been said before) but I've just been out to the hangar and had a 'play' with the latest iterations of everything I own to check they are all behaving themselves properly. I'm pleased to say they are.
I updated my iPad Mini 4 to 14.0.1
iPhone 8 is 14.0.1
SkyDemon is 3.14.4.260
PilotAware Firmware Updater (on iPhone and iPad Mini) is 1.7.5
My previous Pilot Aware version was a Beta of the latest so, to make sure all was oranges and oranges, I updated the PAW to 20200906 (using the Firmware Updater, which worked flawlessly and took but seconds to do ;D ).
Using the existing UDP connection setting in my PAW, i.e. WITHOUT selecting the SkyDemon connection (in third party equipment) to Flarm, I told SkyDemon to 'go flying'. It sent me a brief message along the lines of 'use third party equipment', to which I assented and the SkyDemon connected immediately. No hanging and deciding whatsoever. This happened when using both my iPad and iPhone, so I see no snags at all with using PAW 20200906, SkyDemon 3.14.4.260 and iPad/Phone 14.0.1. When trying again to connect I was not asked again for permission to use the third party device and SkyDemon just connected straight away to both devices.
Due to being lazy and not logging out of one of the i devices in order to log on another, I didn't try my old iPhone 5 on SkyDemon but it connected to PAW with no problems, so I don't think there will be any issues with that if I ever needed it.
Now to make some sloe gin as there's nothing of interest on my ATOM station :-\
Edited to add: PS: Gary, is your PAW version (20200909) a slip of the typing finger as I can only get 20200906?
-
Hi Paul,
Thanks for the confirmation. Your SD 3.14.4.260 setup has worked exactly as expected, with the ‘first time connection’ requiring ‘agreement to use 3rd party devices’ before iOS / iPadOS 14 will allow SD to connect to PilotAware. That should reassure others that may be holding back from updating.
Thanks Again
Best Regards
Peter
p.s. 20200906 is the latest Public Release of PilotAware
-
Hi Paul (and Peter) Yes typo on my part and I confirm my version PAW is 20200906 with a 6 (not 9) at end
iPad mini 5 IOS13.7
iPhone 11 IOS14.0.1
PAW classic 20200906
SD - iPad 3.14.4.260
SD - iPhone 3.14.4.260
FLARM 7.01
-
Thanks Gary,
Looks like it should now be OK to update your iPad to 14.0.1 as well.
Best Regards
Peter
-
Looks like there are more problems generally for iOS:
https://apple.slashdot.org/story/20/10/04/1730206/battery-drain-problems-after-iphone-upgrade-apple-suggests-complete-data-wipe (https://apple.slashdot.org/story/20/10/04/1730206/battery-drain-problems-after-iphone-upgrade-apple-suggests-complete-data-wipe)