KiloJuliett

Did you run your simulator? Any yellow messages in the EFB client status section? Sorry, that's to vague. Did you check Manual 5 Client - Chapter 12.2? If that doesn't help, please describe more precise.

Hi Frank This may help you. Verifiy that the actual files are really in the "AivlaSoft\Airac\Navigraph FMS Data" folder and not in further subfolders.

Perfect. Confirm, you allow the EFB server admin rights? Can you check the traffic monitor from the server and tell me, if there is some traffic in the list or if it is empty? What kind of AI traffic do you use (sim generated, 3rd party add-on, network traffic), and what sim do you have?

Hello Bob Please create a support file (see in your EFB program folder in the Windows start menu, or check Manual 3 Server - Chapter 2.4). The files generated will be on your Desktop. You may upload them here or send them to 'support@aivlasoft.com' if you prefer to not publish them here.

Hello Peter It is used here to abbreviate aircraft, although the official abbreviation ACFT might be less missleading. Those lines disappear when you are airborne?

Please ensure you have the latest versions downloaded: Client #71, Server #54.

Hi Leo I think there is no general fix. It all depends on your configuration. Whether you use the Windows firewall or another product, if the network you are connected is set as public or private (this is a classification you can choose). For example on my machine, I use the Kaspersky firewall and have my own WLAN categorized as private. I don't know if the Kaspersky firewall does also react differently to requests on port 13 if the network I use would be set as public. So you see, it really depends on your individual setting. And still, this is only to open the port 13 in general. If you later also experience the timeout issue with the time server, you might run again into problems. It's important to understand that there are two different issues, although they may affect each other (repeated connections on port 13 may lead certain firewalls to close or restrict the access again). So just make sure, you don't mix them.

Hi Rico If it already takes "some time" to start the app, it could be performance issue. Also the messages seem pointing to such a root cause. If your tablet is not able to respond quickly enough, there will never be a stable connection. Can you explain your current setup (machines you are running, how they are connected)? From the log I see two different clients trying to connect, and once one get accepted and then the other. But somehow, they both are disconnected again or at least try to re-connect. Also a weak WLAN connection could be a contributing factor.

Hello Victor Please follow the already existing thread on this topic where I also explain what files we need for troubeshooting. Although I fly online, I didn't see this issue yet. Otherwise, I would have investigated myself.

Glad you were able to resolve the issue. To my knowledge, it is a problem related to .NET framework on which EFB is built on.

Just to ensure: you are running EFB server with admin right? Does the error occur also when you start EFB server before any other application? (no sim, weather engine, ... running)

Nope. I meant that the ATC relevant information you need as a pilot is already presented in EFB. Integrating an ATC simulator is certainly not a topic for an EFB, like bobsk8 already explained. These are two separate types of addons, that certainly do interact with each other, but otherwise don't have much in common. You shouldn't expect a joint product of the kind you mentioned.

The time check is used to verify the validity of the trial licence. For this, you need a realiable/trustable server telling you the current time. This is to prevent abuse (use system time to keep a trial licence alive).

On the Desktop.

Thanks for the update! Does the issue return when you set those zoom key settings again?

How these values are calculated exactly will have to be answered by Urs. But, the underlying issue here is clearly that you missed a certain waypoint in your route. EFB has BOA as active waypoint, but you are between RUVIP and RONAB. So you obviously didn't pass by close enough to BOA. If you do a shortcut or pass a waypoint not sufficiently close, you have to tell EFB manually the next waypoint you are proceeding to. This is done with the "DIR TO" button in the RSB. Then, also the calculations should show reasonable numbers again.

EFB server running? With admin rights? EFB client showing any yellow messages in the status display of the sidebar?

@Roland Knöpfel can you provide the log files (Start > Aivlasoft > EFB2 Create support files) so I can have also a look in the priorities of your scenery entries? Especially, I would be interested if the warnings/errors generated are due to a conflict between other add-on scenery and FS Aerodata or between the default scenery and FS Aerodata.

No need to apologize. How about a simple text editor? So when you try to enter numbers from 1-3 in EFB and it doesn't work, quickly open a text editor and try to type numbers there. Does that work? I just want to be sure to exclude any strange input commands from the keyboard (either due to the keyboard hardware or the driver on your computer). If there is no such behaviour in other apps than EFB, I would suggest to re-install the EFB client (if you haven't tried that). Not really sure if that can help anything, but I'm running out of ideas slowly but surely.

Good hint Urs & Oski! Maybe even the root cause for these kind of problems could be rounding problems on the position of navaids. Looking at the screenshot of Roland, you can see that the latitude of RDS differs by a tenth of a minute (N36°20.4' vs. N36°20.5'). It's not the case for DAL. But as far as I know, the original position data is more accurate than the numbers presented by EFB. So the issue with a tool like FS Aerodata may simply derive from position data, that doesn't match with existing navaid position data. As the screenshots also shows only VORs activated, I think this is more likely than an unintended overlay of different navaids. @Roland Knöpfel maybe with this information, you can raise the issue with FS Aerodata? As EFB takes only what it gets from the sim database, it simply shows you the outcome of data manipulations by other apps. If you get any feedback, please post it here as well. Thanks.

The issue with traffic not showing on the map is already identified and in the queue for the next update. So, just be patient for a few days and you won't need to roll-back your entire setup.

See here Urs' recent answer on this topic. As you are using SimBrief anyway, I suggest to use the exporter from there offering all kinds of formats already. This way, you also keep the fligh planning tasks together and don't mix them too much with in-flight tools.

Good to hear everything works well now. Enjoy EFB v2!

Someone around using IVAO who can upload some screenshots of the servers traffic monitor when connected via IvAP to the network ("blue" traffic showing)? Would be best if different types of traffic is shown (on ground / airborne, GA / airliner, with FP / without FP). We need this information for some small improvements for the display of the traffic label. Thanks for your help in advance.

What I observed is that your folder posted in the screenshot was actually ..\AivlaSoft\EFB2\Server\AIRAC\Navigraph FMS Data\AIRAC\Navigraph FMS Data. So the AIRAC\Navigraph FMS Data was duplicated and the data put in a folder two layers too deep. This is most probably an issue of the path setting in the Navigraph client.