Lluis del Cerro 810821 Posted September 26, 2014 at 05:09 PM Posted September 26, 2014 at 05:09 PM Hi, I am now training a controller in LEPA. We are managing two different approach sectors. He has set the ATIS for LEPA and as arriving traffic to LEIB crosses our airspace, I have tried to set the ATIS for LEIB. I did all things to connect LEIB_ATIS and apparenly it is connected and listened by me, but it is not listed in the ATC facilities. If I do it using the Euroscope ATIS it is listed. Is it possible to set an ATIS for a different airport to that being managed and if so, what should I do to make it work? Thanks in advance. Regards, Lluís Lluís del Cerro Senior Instructor http://www.catalonian-airlines.cat Link to comment Share on other sites More sharing options...
Bradley Grafelman Posted September 26, 2014 at 05:12 PM Posted September 26, 2014 at 05:12 PM As long as you have an active controller connection, you should be able to connect vATIS using any airport identifier - it has no limitations on what airports are allowed based on what your controller callsign is at the moment. Are you sure you changed the callsign to "LEIB_ATIS" when connect vATIS to VATSIM? EDIT: I checked the lat/lon coordinates in vATIS' navdata against your sector file, and it looked fine (almost perfectly centered at the midpoint of runway 6/24. Link to comment Share on other sites More sharing options...
Ross Carlson Posted September 26, 2014 at 05:24 PM Posted September 26, 2014 at 05:24 PM It may be the LEIB is too far from LEPA for it to show up in your controller list. I definitely see LEIB_ATIS online in VATSpy. Edit: I see they are only about 75 miles apart ... so that shouldn't be it. Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Bradley Grafelman Posted September 26, 2014 at 05:26 PM Posted September 26, 2014 at 05:26 PM (edited) Actually, I take that back... even though the coordinates appear fine in the .xml file, vATIS is definitely not centering its vispoint where it should be... EDIT: @Justin - either Lluis' airports.xml file is corrupted, or vATIS is doing something weird with truncation. From the datafeed: LEIB_ATIS:810821:Lluis del Cerro:ATC:119.800:38.00000:1.00000 from my airports.xml: Ibiza Airport 38.8728981018 1.37311995029 EDIT2: Testing vATIS version 1.0.7168.40764 on Sweatbox shows that it placed LEIB_ATIS at the correct location. Edited September 26, 2014 at 05:39 PM by Guest Link to comment Share on other sites More sharing options...
Lluis del Cerro 810821 Posted September 26, 2014 at 05:29 PM Author Posted September 26, 2014 at 05:29 PM Hi, As long as you have an active controller connection, you should be able to connect vATIS using any airport identifier - it has no limitations on what airports are allowed based on what your controller callsign is at the moment. Are you sure you changed the callsign to "LEIB_ATIS" when connect vATIS to VATSIM? I am now logged in as LEPA_E_APP. LEPA_W_APP has set ATIS for LEPA using ES. I have set in vATIS the airport for LEIB and loaded LEIB_W profile file (west configuration). I have connected vATIS to VATSIM, set the ATIS letter, connected vATIS and clicked on "auto update". The frequency set for LEIB_ATIS is the correct as indicated in the ES *.ESE file. However, LEIB_ATIS is not listed in the ATC list when using vATIS although it is and works correctly when using the voice ATIS from ES. Thaks for your help, Lluís Lluís del Cerro Senior Instructor http://www.catalonian-airlines.cat Link to comment Share on other sites More sharing options...
Bradley Grafelman Posted September 26, 2014 at 05:50 PM Posted September 26, 2014 at 05:50 PM I tested LEIB_ATIS on Sweatbox using the same version Lluis is using (latest stable, 1.0.7166.38666) and it again worked correctly. Lluis, it is possible that something is wrong with the location of the LEIB airport in the file that vATIS uses to store airport information (it doesn't use the ESE/SCT files). Try doing the following: Close vATIS if it is running. Open the following folder (use the "Run" or "Start Menu" in Windows to copy/paste this path): %appdata%\vATIS\NavData\ Rename airports.xml to airports_old.xml Download this version of airports.xml and save it to the same folder as above. This will not affect any of your saved profiles. Once you do the above, try re-opening vATIS and connecting the ATIS again. Link to comment Share on other sites More sharing options...
Lluis del Cerro 810821 Posted September 26, 2014 at 06:06 PM Author Posted September 26, 2014 at 06:06 PM Hi, vATIS says I am not connected to VATSIM although I am. Likely is the airport.xml file. I have copied and pasted it to a file and likely it has not the correct structure. Can you send it to me as a file insted of a list? Thanks, Lluís Lluís del Cerro Senior Instructor http://www.catalonian-airlines.cat Link to comment Share on other sites More sharing options...
Bradley Grafelman Posted September 26, 2014 at 06:17 PM Posted September 26, 2014 at 06:17 PM EDIT: The connection error is no longer an issue, but even with a known-good airports.xml file, the latitude/longitude coordinates were still being truncated to integers. The same happened for LEMH_ATIS as well. Even tried USA-E rather than EUROPE-W to no avail. I'm still out of ideas... and still must defer to Justin's expertise as to why the latitude/longitude values are being truncated. Link to comment Share on other sites More sharing options...
Justin Shannon Posted September 26, 2014 at 06:38 PM Posted September 26, 2014 at 06:38 PM This is odd. Were you having this issue yesterday? Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
Recommended Posts