Jump to content

aivlasoft

Administrators
 View Profile  See their activity

  • Posts

    5,914

  • Joined

  • Last visited

 Content Type 

Posts posted by aivlasoft

    Problems with install of distributed

    in EFB v1 (Read only, no longer supported)

    Posted

    Lothar,

     

    can you please try the following:

     

    - stop/exit the DataProvider

    - start the DisplayUnit on your second computer.

     

    Now the splash screen appears for some seconds and then it will disappear. After that, the yellow bar "Initializing EFB system" appears. After some further seconds it should change to "Connecting ..."

     

    - on the menu bar, press "System" > "Settings". The settings dialog opens.

     

    Now verify the following settings:

    - Is "Server Mode" set to "Remote"?

    - Is the "Server Name" exactly the same as the name of the DataProvider computers name?

    Problem connecting on a two-computer set-up. SOLVED!

    in EFB v1 (Read only, no longer supported)

    Posted

    Joel,

    and the DU computer's name is "5350" ... I've set that in DU's settings in the Server Name field.
    I assume that this is a typo? In the DisplayUnit's settings you must set the name of the DataProvider's computer, not the DU computer's name.

     

    although the version numbers are slightly different: DU: 1.3.1.13675, DP: 1.3.1.13677
    That's OK.

     

     

    If the DNS cannot resolve the DataProviders IP-address from the given name in the DU settings, we could try to add a fixed assignment in the file called "hosts". Do you know that file? You will find it as follows (on the DisplayUnit's computer): "C:\Windows\System32\drivers\etc\hosts". This file has no postfix like *.txt or *.exe or similar. It's just "hosts". If you are familiar with file editing you may add the following line at the end of the file:

     

    10.0.1.13  5350

    It is important to leave at least one whitespace between the IP-number and the computer name. After you have added this line, save the file and try to restart the DisplayUnit. Now if the DNS is looking for a computer named 5350 it will take the IP address 10.0.1.13 for a connection.

     

    Maybe this helps.

    Problem connecting on a two-computer set-up. SOLVED!

    in EFB v1 (Read only, no longer supported)

    Posted

    Joel,

     

    thanks for this detailed description. That helps really.

     

    As far as I can see it must be a problem with the DNS (Domain name service) which cannot properly resolve the computer name of your FSX computer. It returns 0.0.20.230 but it should return 10.0.1.13. Therefore the DisplayUnit cannot connect.

     

    Please check whether the name of the FSX computer is properly set in the DisplayUnit's settings. To find the FSX computer name please open: Control Panel\System and Security\System. There you can see the computer name.

     

    Are both computers in the same workgroup?

    Did you configure a homegroup?

    EFB not matching the real charts...

    in EFB v1 (Read only, no longer supported)

    Posted

    Hi,

    Is there anything I can do about this, apart from using the regular chart?
    No, there is currently no setting which can be changed.

     

    BUPUS is defined as D11 R180 RYG. These is not as helpful since this radial does not fit with any of the phases of the holding pattern.
    Not only that it doesn't fit the holding phases, it's also not a VOR but a DME. That's indeed not helpful since you won't get a radial from a DME :oops:. I will try to improve this in version 2.

     

    that the holding pattern in EFB was not in the same place as dictated by the description in the Navigraph chart
    If I compare a r/w chart against the EFB chart I can't see a "big" difference concerning the holding position. But it might be that I don't see what you mean :?

    [attachment=0]enry_ndb12.jpg[/attachment]

     

    please, according to the forum rules, sign your posts with your real first name. Thanks.

    Leipzig-Halle EDDP v. Aerosoft

    in EFB v1 (Read only, no longer supported)

    Posted

    Hi Lothar,

     

    just have a look into the file "Runways.txt" which can be found in the following directory: C:\Users\[username]\Documents\AivlaSoft\EFB\UserData. Most probably there are already some entries for EDDP. Try to remove them. For more information about the "Runways.txt" file, please read the operations manual, starting at section 2, page 3.

     

    Just download the latest Navigraph FMS data for AivlaSoft EFB to your FSX computer. Run the installer and - after a successful installation of the airac cycle - just restart the DataProvider.

     

    Merry Christmas to you too ;)

    Antarctica X errors with EFB Update.

    in EFB v1 (Read only, no longer supported)

    Posted

    Hi Todd,

     

    I think that I figured out the problem that the developers of Antarctica X must have been faced with:

     

    FSX needs a unique ICAO code for every airport, but ...

     

    1) Antarctica is "nobody's" land and therefore it has no official ICAO country code.

    2) Antarctica is only listed as a region using ICAO code "NZ".

    3) Many of the "airports" in Aerosoft's Antarctica X are not really airports but research stations and therefore you won't find it on any list of airports.

     

    Now the developers used the identifier "AQnn" for the "airports", where n stands for any number from 0 to 9.

     

    EFB didn't know "AQ" as a valid country code and therefore it raised an exception. After the exception has been raised, the process of creating the airport index must be corrupted.

     

    I changed the source code in EFB so that any airport with country code "AQ" is now mapped to "NZ" but the country is not New Zealand but Antarctica.

     

    A first build of the upcoming version 1.3.2 is currently under test by our beta-team.

     

    For further (interesting) reading:

    http://en.wikipedia.org/wiki/Internatio ... rport_code

    http://en.wikipedia.org/wiki/List_of_ai ... Antarctica

    http://en.wikipedia.org/wiki/List_of_re ... Antarctica

    Online flying

    in EFB v1 (Read only, no longer supported)

    Posted

    Richard,

     

    it seems to be the same problem than already answered in my posting above. Sometimes it might happen that controllers are using callsigns which do not correspond with the definitions in the "firs.dat" file. If so, then EFB cannot assign a certain frequency to a certain FIR/ARTCC area.

×
×
  • Create New...