PilotAware
British Forum => General Discussion => Topic started by: jodel119 on November 07, 2015, 12:00:32 pm
-
Hi Lee,
I use EasyVFR for navigation, but I couldn't get Pilotaware to work with it, after much frustration I spoke to Dave, one of the guys at EV we went through a few things, to make sure I had done it correctly, all seemed to be OK, it was only when we checked marked ALL 4 "log interface messages " it started to show aircraft in EV, I closed down and restarted and all is working fine (the log check marks are not on), it seemed I needed it for just the first time.
Just thought it may help someone else.
Thanks for a great bit of kit.
Regards
Colin
-
Hi Colin
Glad to hear you got it working.
To be honest, I think turning on the debug was simply a coincedence, if there was an issue, it would have re-emerged after a reboot.
What is your GPS source ?
Are you using the GPS sharing from EasyVFR, CollisionAware or a GPS Dongle ?
Not having a GPS source would have yielded this behavior
Thx
Lee
-
Hi Lee,
Not sure why it needed this action, I'm using collision aware as the gps source. I thought it may help someone else, if there was a problem.
Regards
Colin
-
Like Colin, I've been waiting for the latest EV software release to be actually able to connect my iPad Mini2 Cellular tablet to my PAW, and hopefully see some ADSB traffic. Three problems seen that I'd like some help with please,
A) enabling FLARM, (with settings, 192.168.1.1 , port 2000, pin code 6001, TCP, 40000ft set), no traffic on display even though I can hear the CAT overhead. Tried two different DVB-T dongles/antennas. tried ticking the logging boxes in config screen as advised by Colin, still no good.
B) I can only see my plane symbol when using the iPad internal GPS source, even though have u-blox dongle on PAW,flashing away with a fix and trying collision aware both on and off. When FLARM is enabled, GPS source is lost (no plane symbol).
C) QNH is set to auto, in config screen, but resolutely shows 1013 and QFE =0, noticed this over past few weeks. GNSS gives a sensible height given my location. Using JC'S ARFShield with inbuilt baro.
All of the above conducted outside with clear view of sky.
I'm currently downloading latest PAW software, as I had 20151020 installed, (takes hours with my wifi), maybe this will help?
-
Hello Moffrestorer
I'm still getting a problem occasionally on start up, but I'm now trying to find where the issue is.
Colim
-
Hi Lee,
Downloaded 20151107 and tried to connect Easy VFR to PAW via my iPad (see above post). Still cannot see ADSB traffic ( though I can hear it and see it on FR24).
I'm thinking the main problem is that GPS only seems to work via IPad location services to give me the plane symbol on EV display. I have collision aware enabled. As soon as I enable FLARM on EV( with Use Flarm GPS=ON) I lose the plane symbol on map display, even though u-blox 7 GPS dongle has a fix. Again, tried checking the logging boxes on config on PAW config screen (Colin's post) - makes no difference!
I notice that config indicates "navigation =OFF". Could this me the problem? how do you get it to =ON?
Thx,
Chris
Would attach screen shot of PAW homepage but don't know how to get file size<200kbit
-
I notice that config indicates "navigation =OFF". Could this me the problem? how do you get it to =ON?
This isn't a switch, it's an indicator. It indicates if you have a valid piece of software such as Sky Demon or Easy VFR connected. It goes Enabled if you have.
How many satellites is it showing for the GPS fix and is it showing 2D or 3D fix?
If you have a UBlox GPS, shouldn't collision aware be switched off? It's one or the other.
-
Hi All
scsirob (forum member) sent me a screenshot of his settings, this is what he has setup, and EasyVFR is working for him
-
I just ran a quick test. I stuck my uBlock GPS receiver in an aluminium container so it lost fix. Not only the airplane indicator, but also all other traffic indication disappeared. So make sure you have GPS fix before expecting EasyVFR to show any ADS-B traffic.
-
Hi Lee,
The Flarm screen shot is exactly what I had selected. I can only think that the GPS and traffic data are not being communicated from the PAW to EV on the iPad. Shouldn't need collissionaware if using the Ublox dongle, but didn't get traffic even with this enabled and using internal iPad GPS.
GPS sentences(usb), msgs 10313(+72), Fix="GPS fix (SPS)", "Mode=3D", Satellites =9
-
You can trace the messages going to the nav tool, by ticking the 'nav' selection in the web config page.
Then go to the logging page to display the messages
-
Hi Lee,
Thinking about this problem, I realised my power pack is only rated at 1A output. So tried to see high level ADSB traffic using the car cigarette lighter and 2.4A USB adapter. Unfortunately still no joy.
Everything appears to be working, excepting the EasyVFR to PAW connection. PAW config home page doesn't show Navigation Enabled, no matter whether I try to connect using FLARM settings as posted by Rob, or using internal IPad Mini GPS (cellular model).
Reading Ian Fallon's excellent Software downloading and set up instructions (just posted) the only thing I have done differently is to reformat the micro USB card on the FULL (overwrite) setting, which I'm sure was documented in your early build documentation. As I've downloaded all of the updates, could this have led to a corruption?
I can try reformatting and downloading again if it's likely to help. Unfortunately I have very slow wifi and it takes about 2.5 hrs at its quickest. Is this par for the course?
-
Hi Chris,
I can try reformatting and downloading again if it's likely to help. Unfortunately I have very slow wifi and it takes about 2.5 hrs at its quickest. Is this par for the course?
I dont believe this is the issue.
A simple check you can perform, is to see what data PAW will stream to a connected NAV device, to do this open your web browser on the machine connected to the PilotAware Hotspot.
in the address bar type the following
192.168.1.1:2000
This should stream the messages to your browser, do you see anything ?
If so, this is what EasyVFR should be parsing.
Thx
Lee
-
Yep lots of $PFLAA, PFLAU, GPGgA, GPGSA, GPRMC msgs, repeating.
I'd send a screen shot but someone needs to give a tutorial on getting file size below 200kbit, cos forum doesn't allow me to post saying file too large.
Incidentally, this is with Ublox 7 and FLARM enabled.
Chris
-
Hi Chris.
So the point is, PAW is generating the data, the question is, why is easyVFR not connecting to read the data ?
It also looks like my EasyVFR license has expired to try myself.
Thx
Lee
-
I'm currently running EasyVFR 3.81.0 and PAW 20151107 and all appears to work just great:
(http://www.rtist.nl/images/PAW_EVFR.png)
-
Hi scsirob,
I'm trying to run this software combination on an iPad Mini (cellular model). As I recall from your posts you're running it on a panel mounted Windows mini PC using Ethernet connection?
As you may realise, EV doesn't seem to connect to PAW in my setup. When I select FLARM as per your screen shot, I lose the moving map aircraft symbol. Although PAW +Ublox 7 dongle is generating GPS data to pass to the tablet via the wi-fi hotspot, EV is not receiving or using it. Conversely, if I use the iPad internal GPS + Collisionaware, I retain the plane symbol but PAW doesn't seem to get the GPS data. In both cases PAW config. screen shows Navigation is not enabled.
EV has a "wi-if sharing" option in the autopilot (simulator?) settings screen. I've tried enabling this but still no luck in getting it all working. Can you think of any setting in EV that I'm overlooking?
I haven't checked out the EV forum for a day or two, maybe I'll raise the problem there, but hesitate because Easy ADSB doesn't seem to have been formally announced as yet.
Regards,
Chris
-
Chris, if you are using connect key 6000, can you try key 6001 ?
Thx
Lee
-
Thanks Lee, but I was using 6001!
-
Hi Lee,
Been on the EasyVFR forum and it seems that the FLARM settings page IS NOT used to connect EasyVFR to PAW. Will try out out the new instructions tomorrow and will report back how I get on.
Thanks,
Chris,
-
Hi Chris,
Please update us when you have more info, then I think we need to get some screenshots and add to the documentation
-
Hi Lee,
After starting this thread, I should come back and give you my thoughts. I've tried different ways to start up, just to see if that was the problem, what ever I do now I get aircraft on EasyVFR. Why I had a problem in the first place, I've no idea!!!!!!!
Running EV on Nexus 7.1
Start EasyVFR
Power PAW
Settings..connect to PAW
Start Pilotaware GPS app.
on EV FLAM settings
Address...192.168.1.1
Port.........2000
Pin Code...6001
Flarm GPS.OFF
Protocol....TCP
Proximit....35000 (I have had it at 3000ft, and picked up aircraft in the Oxford Circuit) I'm not far away.
So at the moment all seems to be OK, but I will keep trying to break it (ha.ha)
Regards
Colin
-
Lee,
I should have added that if I use EasyVFR GPSsharing with SGPGGA I do not get aircraft showing, but when I put Pilotaware GPS on again it works
Colin
-
Please update us when you have more info, then I think we need to get some screenshots and add to the documentation
Lee/Ian
I am happy to supply the screenshots for EasyVFR settings for installations with and without a GPS module on the PAW unit for both Android and iOS (might be a few days though).
Please note that EasyVFR is not currently displaying the Flight No./Hex Code of other traffic. This is being investigated.
Dave
-
Please note that EasyVFR is not currently displaying the Flight No./Hex Code of other traffic. This is being investigated.
Dave
Hi Dave,
Who is investigating ?
This is probably because we are using an extension to the FLARM Data format as defined by SkyDemon
I presume EasyVFR do not support this
Thx
Lee
-
Thanks - please post info re. documentation changes to me directly or via the Documentation thread. Best to email screenshots directly (email on that thread).
-
Something I have noticed on my Asus 173 is that if you run Sky Demon, it doesn't shut off properly when you exit the program. You have to press the bottom right button then swipe the program away to properly end it, otherwise it seems to block the ports and you then can't use them with other software, or even on Sky Demon itself. Having swiped it away, you can then use other software on the tablet.
-
I have the Asus Memopad 173X and have not seen this. Latest Skydemon. Android 4.2.2
-
Who is investigating ?
This is probably because we are using an extension to the FLARM Data format as defined by SkyDemon
I presume EasyVFR do not support this
Thx
Lee
Lee
I am a PocketFMS BetaCrew member but have not been spending too much time looking at PAW. I have had issues with connecting on my iPad but have put that down to facing East of an evening (not many Sats available) and hiding behind double glazing (K Glass) at the back of my house. Moving to the front which is West facing and different glass I now don't have any connectivity issues.
We are aware of the flight numbers not displaying in EasyVFR and on Monday I sent a PAW set of hardware (minus ARF module and minus GPS module) to Rob for him to fully investigate the technical interaction of PAW and EasyVFR in finer detail. It is hoped that he will have that in Lelystad by the end of the week so he can test and investigate.
PocketFMS have worked with FLARM for many years supporting interfaces with their products. However, we will test PAW very thoroughly and liaise with you with our findings.
In the meantime, I will liaise directly with Ian regarding the User Guide he is producing.
I have a Asus M173X and have never experienced any issues using EasyVFR on it, both with or without a PAW connected, or shutting the application down. If the CollisionAware for Android is going to remain, the ability to exit that App from within would be a useful addition as otherwise you have to navigate to Apps, scroll down and then forcibly stop it, which is a bit of a performance. Could it be this component that is affecting the SD users?
Dave
-
Easy VFR screenshots are now in the latest version of the guide which is now on the forum for download.
-
Hi Lee,
I recommend you check out the Easy ADSB thread in Easy VFR forum.
Kind regards for all your hard work,
Chris
-
Whoop,Whoop, I've got little green planes buzzing me on EVFR!
Roweda talked me through connecting PAW to EV by phone, on Thursday evening. Comparing logging messages with his unit, I appeared to have a software corruption on my PAW because the boot-up sequence was stopping prematurely.
Downloaded software once again and installed in PAW. Also took the precaution of using a higher current power bank to eliminate low voltage problems during initial boot-up.
In the meantime Dave had sent a PAW unit to Rob Weijers at the Pocket FMS Foundation for testing with iOS devices. Rob discovered a potential problem with PAW having no DNS address in the Pilotaware hotspot IP DHCP settings. Apparently Flarm does have DNS and the "FLARM" interface in EV requires this. It had been omitted by Lee in response to a request for cellular iPads to be able to retain cellular connectivity for downloading weather, notams etc while connected to EVFR and PAW.
I did an initial boot of my PAW earlier today and suffered the same lack of connectivity between my iPad and PAW that I was getting previously. I decided to try the work-around that Rob suggests in the PFMS forum EasyVFR thread, "Known issue with EasyVFR and Pilotaware on Apple devices without cellular datalink". Once I applied the work-around to the PAW hotspot settings in "iPad settings", all of the interface problems disappeared. This workaround should NOT have been necessary with a "working" cellular model, but I am on Pay as You Go, and don't have a current data allowance, so it seems I have to apply it also in these circumstances.
I'd like to thank both Dave and Rob for their first class support with this issue.
-
Whoop,Whoop, I've got little green planes buzzing me on EVFR!
Roweda talked me through connecting PAW to EV by phone, on Thursday evening. Comparing logging messages with his unit, I appeared to have a software corruption on my PAW because the boot-up sequence was stopping prematurely.
Downloaded software once again and installed in PAW. Also took the precaution of using a higher current power bank to eliminate low voltage problems during initial boot-up.
In the meantime Dave had sent a PAW unit to Rob Weijers at the Pocket FMS Foundation for testing with iOS devices. Rob discovered a potential problem with PAW having no DNS address in the Pilotaware hotspot IP DHCP settings. Apparently Flarm does have DNS and the "FLARM" interface in EV requires this. It had been omitted by Lee in response to a request for cellular iPads to be able to retain cellular connectivity for downloading weather, notams etc while connected to EVFR and PAW.
I did an initial boot of my PAW earlier today and suffered the same lack of connectivity between my iPad and PAW that I was getting previously. I decided to try the work-around that Rob suggests in the PFMS forum EasyVFR thread, "Known issue with EasyVFR and Pilotaware on Apple devices without cellular datalink". Once I applied the work-around to the PAW hotspot settings in "iPad settings", all of the interface problems disappeared. This workaround should NOT have been necessary with a "working" cellular model, but I am on Pay as You Go, and don't have a current data allowance, so it seems I have to apply it also in these circumstances.
I'd like to thank both Dave and Rob for their first class support with this issue.
Can you post a link here to the magic needed to get Wifi iPads to work ? Or post the info itself ? I have a friend with this problem.
-
Aha! Here:
http://www.pocketfms.com/phpBB3/viewtopic.php?f=44&t=9650&p=83065#p83065
-
This works for me both with and without PAW (Flarm) GPS.
(http://sn.www.idnet.com/pawevfr.jpg)
Pilotaware 21511107
EasyVFR v3.81 (32)
Nexus 7 (2013)
Android v6.0 Marshmallow (MRA58U)
-
On a Wifi only iPad ? I think you also need the DNS entry in the PAW Wifi settings for those.
-
On a Wifi only iPad ? I think you also need the DNS entry in the PAW Wifi settings for those.
Also on a cellular iPad if you don't have a Sim card installed. It appears that it doesn't have to be an operational SIM.
-
I need to add this to the next version of the software install / setup guide
-
EasyVFR connections are showing on the web browser Logging Page as connected to "RunwayHD".
Not sure what you are checking to check what the PAW is connected to? Possibly a common component?
-
Also on a cellular iPad if you don't have a Sim card installed. It appears that it doesn't have to be an operational SIM.
This is fixed in EasyVFR V3.82.0 which is already available via Google Play Store. Apple version will hopefully be later this week when approved by Apple.
-
Hi
Can anyone tell me if it is PAW or EVFR that determines the red coloured conflict aircraft on the screen.
I had the first airbourne test of my setup yesterday and was surprised to see so many red aircraft that were many miles away from me. They were, I assume, within 1000ft altitude of me (I find it difficult to read the on screen height and speed in cockpit situation) but more than 20 or 30 miles away. I had assumed that as well as the height difference parameter there would be a horizontal parameter too so that only aircraft in a fairly nearby proximity at similar height would be red. Although I suppose the fast jet jockey's wouldn't take long to close from 20/30 miles but I'm not sure if they're included in this set-up anyway are they? Do they transmit ADS-B?
I currently have the original ARF unit installed but nothing to test it against so waiting with bated breath for whats coming at the show. Only wish I could be there. however other than the issue above I was amazed at the coverage of ADS-B traffic from just the supplied dongle antenna which in effect has no ground plane as it is just velcroed onto the GRP pod of my flexwing behind the windscreen.
An amazing job by all concerned.
Alan
-
Alan
EasyVFR is determining whether the conflicting aircraft is Red or Green. At present, it is only determining the conflict by the vertical separation and not the horizontal, so if you are zoomed out and can see a wider area then you may see more Red aircraft.
There is no telling exactly who transmits ADS-B. I doubt that military jets do as nine times out of ten they don't want people to know where they are! I had heard that the likes of the BBMF and the Vulcan are fitted with FLARM units, presumably because of the low levels they fly at outside of controlled airspace and the difficulty of spotting gliders due to limited visibility.
-
The display is under the control of the Navigation device.
PAW simply passes all the data regarding traffic in the vicinity
Thx
Lee
-
Roweda & Lee
Thanks for the prompt response guys. That's what I suspected.
Alan