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