Air nav pro flarm not connecting

[Exraf]

I am unable to get flarm to work on my iPad after connecting ?

[Admin]

Hi Exraf

I think we need a bit more information to help you out.

Can you explain exactly what you have done, which version of PilotAware etc.
Which Nav software are you using, how is it setup.

Anything else you can tell us, will help to resolve the problem

Thx
Lee

[Smaragd]

Same subject, different submitter: re the Software Installation Guide and Air Nav Pro, it says select Configuration>Sensors>Flarm. On Air Nav Pro on my Nexus, Configuration just gives me the options of Map Store and Settings. Is FLARM capability not included in the Android version, perhaps?

[Paul_Sengupta]

There are a lot of things missing from the Android version. Development for the Android version seems to be glacial.

[Exraf]

Hi Lee
Air nav pro and collision aware  on a iPad mini retina, PAW release 20151107 loaded onto the pi
Flarms set as per instructions
Pin: 6001
IP address:192.168.1.1
Port:2000
The sensor button turns orange briefly then turns back to red.
Air nav pro firmware: 5.8.2
Is this ok ?

[Admin]

All sounds correct to me.

I found an unusual bug in airnavpro, i have to delete and re enter the settings each time I startup airnavpro, I am sure I reported this, but dont believe it has been fixed.

Can you try this ?

Collision aware must be running before starting airnavpro
Thx
Lee

[Exraf]

That did it it just tracked traffic out of Eastmidland!

Thanks lee

Neil

[ianfallon]

Hi - if you have a reliable set of steps for setup on Air Nav Pro I'd be interested to add them to the Software Guide, inc step by step screenshots.

[tfede]

Hi,

got this turnaround from Lee: it seems there's a bug in ANP, try the following procedure, with mine works every time (boring but working).

Goto configuration, sensors, FLARM.

Tick off the sensor (form green to White)

goto pin code, delete the value and reenter 6001
goto IP Address, delete the value and reenter 192.168.1.1
goto Port number, delete the value and reenter 2000

Tick on the sensor, it will connect immediately.

Unfortunatelly you have to do this every time you start ANP.

Please write something to Xample FB page about this, the more they receive bug notes the better they will improve it in next release.

Federico

[Admin]

I have had a reply from Alexis at Xample (Air Nav Pro)
They will see if they can get this fix into the December release.
so fingers crossed

Thx
Lee

[Paul_Sengupta]

If you're talking to him, ask him if there's any plan to introduce this into the Android version.

Or even airspace updates for that matter!

[Steve6443]

Better yet, just dump ANP and move to another Moving Map software. I turned my back on that program after they continuously kept introducing the same bug on repeated updates (the system would delete the links to all installed maps - they were physically there, but the software didn't know and the only way to have the maps reappear was to download them again. Three times they released an update to fix the bug and 3 times they released a new version which reintroduced this bug - worse, due to iTunes security, if an update was available, you HAD to install it or the software wouldn't start.

The final time this happened I was in Hungary and had to pay a fortune to download the maps via Data Roaming and all Xample said was "not our problem" even though they knew the flaw was of their own making. I don't trust their programming capabilities and continuously having to enter those details on each start is something I would not accept, especially as there are other options out there......

[Exraf]

It finds heavys at 33,000 ft at 400 knots, but can't locate a c150 in circuit! Not seeing transponders!
What should I do next?

Thanks for your time Lee

Neil.

[Ian Melville]

Unless the C150 has a PAW unit or Mode S with ADSB OUT, then you won't see it.

Are you sure you understand what PilotWare is capable of?