Jump to content

IVAO ATC stations in the Netherlands issue


Recommended Posts

When I use EFB when flying online, it won't show the online ATC positions in the Netherlands correctly. It does show the online ATC positions in the countries surrounding the Netherlands, but in the Netherlands it only shows the Rotterdam Airport positions (EHRD_xxx), but not the Schiphol Airport (EHAM_x_xxx) and Amsterdam Radar positions (EHAA_x_CTR).

Below are screenshots of IVAO's 'The Eye' and Aivlasoft EFB, taken at the same time:

IvAe%20online%20ATC.png

 

EFB%20online%20ATC.png

You can clearly see there's a lot of ATC online in the country, but EFB only displays the EHRD positions.

 

I hope you can solve this issue, because 99% of my flights start or end at Schiphol Airport. ;)

Link to comment
Share on other sites

Since I'm at another computer now, I don't have other screenshots available. However, I did notice two green circles around Schiphol Airport on the departure chart. Also visible on that chart were the online ATC services in Germany, but the online radar controller in the Netherlands was invisible.

I filed a route from Schiphol to Venice in the EFB.

Link to comment
Share on other sites

Kevin,

 

a closer look into the file "firs.dat" shows that e.g. no positions like "_E_" or "_W_" are defined for EHAA:

EHAA::NL:Amsterdam:Radar:52.8:4.6

 

Whereas other FIRs/ARTCCs like EDGG (Langen Radar) have explicitly defined their sub-positions like "_W_" or "_N_" etc:

EDGG:N:DE:Langen:Radar:51.30:7.4:EDGG NORTH

EDGG:W:DE:Langen:Radar:49.8:7.28:EDGG WEST

EDGG:S:DE:Langen:Radar:49:8.91:EDGG SOUTH

EDGG:E:DE:Langen:Radar:50.35:9.44:EDGG EAST

EDGG:NW:DE:Langen:Radar:50.7:6.76:EDGG NORTH-WEST

EDGG:SE:DE:Langen:Radar:49.6:8.9:EDGG SOUTH-EAST

EDGG::DE:Langen:Radar

 

Therefore EFB cannot recognize the active services from a sector if the controllers are logged in with an ID that is not known due to the definitions in the file "firs.dat".

 

For the airports it seems to be a bug that they are not show correctly. Should be fixed with 1.3.1.

Link to comment
Share on other sites

×
×
  • Create New...