FLARM data no longer displayed

VFRnav Support
1

Hello everyone, we have the following problem. We use VFRNav with Airconnect to integrate our FLARM data. Up until now it has worked perfectly and FLARM was displayed on the screen. The connection was also stable. Last week we carried out updates—map and system updates. Since then no FLARM data is displayed on the screen, i.e. the other aircraft are not shown. However, the connection is up and showing green. Does anyone know what’s going on?

2

Hello Jakomo,

there have been updates. Could you please clarify which version your report refers to.

The “Vernindung steht” …does that mean you see traffic data arriving under Settings? …just not on the MovingMap? …a Sceenshot is always helpful!

Pilot greetings,
Karsten

3

Hello,

Since the update it’s not working any more. I have version 4.17.5.

Screenshot 2025-10-18 at 18:52:44

By “connection” I mean that the connection from Airconnect to VFRNav is established, see image attached. However, the FLARM data is no longer displayed on the map, i.e. the other aircraft approaching me. Before the update these were displayed with altitude information etc. It can only be due to VFRNav since with other programmes the data are still displayed.

4

…and these values are correct as in the screenshot?

I don’t know the port number for the device. But the IP address already raises big questions! That’s definitely not an IP. Since you chose Network-TCP as the connection, that can’t be right. Can’t you use UDP instead of TCP?

…

5

Again: Yes, the values are correct. The whole thing worked like this until the update.

I have the IP address from the manufacturer. It worked like this !!!

6

Hello Jakomo,

please be patient until next week, then Hermann will be back from holiday. It could well be due to some internal system changes in VFRnav that were implemented with the last update.
IP: I do believe you that it worked that way. According to AirAvionics the IP 169.254.1.1 would be equivalent to 1.2.3.4. The internal data communication is apparently serial on the devices.
So please be a little more patient :slightly_smiling_face:… there’s no flying weather anyway at present :unamused_face:

Pilot greetings, Karsten

7

Hello,

Thanks to Hermann’s kind support, it worked with 1.2.3.4 :slight_smile: Everything is working fine. At the moment the weather isn’t suitable for flying either; Hermann has already got in touch to say he’ll be back next week.

Best wishes to everyone

9

Hello @Jakomo

Hello,

thank you very much for your patience.

Please install (if not already done automatically) Version 4.17.6 of VFRnav.

I know that testing isn’t exactly easy at this time of year or given the weather conditions. If no traffic is displayed with this version, it would be helpful if you could please carry out the following steps:

  1. Open Settings → External Data Source in VFRnav
  2. Open the menu at the top right
  3. Enable “Raw Data Logging”
  4. Wait about 2–3 minutes, then please disable this option again
  5. Open the menu at the top right again and select “Show Debug Files”
  6. A list will appear with an entry for the current date – please select “Share” there and send me the file by e-mail to mail@flugbetrieb.com

@KBfly

The 1.2.3.4 is indeed correct – this is an older AirConnect that uses this IP. Some NMEA data sets differ here from newer devices, which has caused this error after the last update.

Pilot’s regards
Hermann