Justin Shannon Posted December 1, 2019 at 09:44 PM Posted December 1, 2019 at 09:44 PM Version 3.1.2.0 of vATIS is now available for download from the web site, or via the automatic update utility built into the ATIS client. The following items were added or fixed in this version: Add time parsing rule: ####Z (where # is a number between 0 and 9) is now synthesized as "# # # # zulu" Add support for facilities that use an IDS system Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
Justin Shannon Posted December 2, 2019 at 12:48 AM Author Posted December 2, 2019 at 12:48 AM For those that have installed the new update but are having issues connecting, please re-download the installer. http://vatis.clowd.io/installers/beta/vATIS-Setup-3.1.2.0.exe Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
John Wydrycs Posted December 2, 2019 at 11:52 PM Posted December 2, 2019 at 11:52 PM Getting a bot server failure currently....http://prntscr.com/q5at33 John Wydrycs NYARTCC Controller Link to comment Share on other sites More sharing options...
Matthew Simmons Posted December 3, 2019 at 02:14 AM Posted December 3, 2019 at 02:14 AM I am also having this issue.. Link to comment Share on other sites More sharing options...
Justin Shannon Posted December 3, 2019 at 02:21 AM Author Posted December 3, 2019 at 02:21 AM Please post this in the AFV forum... this error is originating from the AFV ATIS bot server. Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
Nick Warren Posted December 3, 2019 at 08:02 PM Posted December 3, 2019 at 08:02 PM Add support for facilities that use an IDS system Would love to see this more readily available to facilities alone Link to comment Share on other sites More sharing options...
Kyle Kaestner Posted January 5, 2020 at 08:25 PM Posted January 5, 2020 at 08:25 PM Can someone explain how the IDS endpoint URL works? I don't see anything in the docomeentation about it. Looking into integrating this with our IDS. Link to comment Share on other sites More sharing options...
Szymon Puzdrowski Posted January 12, 2020 at 05:11 PM Posted January 12, 2020 at 05:11 PM Can someone explain how the IDS endpoint URL works? I don't see anything in the docomeentation about it. Looking into integrating this with our IDS. Ditto. There's nothing in the docomeentation. Is there any information on this available? Link to comment Share on other sites More sharing options...
Justin Shannon Posted January 12, 2020 at 05:17 PM Author Posted January 12, 2020 at 05:17 PM (edited) If you have an endpoint URL configured in the facility settings, vATIS will make a POST request to the URL with the following JSON object structure: { "facility": "KMSP", "config_profile": "30-35 IMC", "atis_letter": "K", "airport_conditions": "SIMUL DEPENDENT, ILS RWY 30L APCH IN USE, ILS RWY 30R APCH IN USE, ILS *V RWY 35 APCH IN USE. DEPTG RWY 30L, RWY 30R. LAHSO IN EFCT, ACFT LDG RWY 30L EXPT TO HS TWY *A9 FOR CROSSING TFC, *8150 FT AVBL.", "notams": "SAY NO TO KILO", "time_stamp": "11/29/2019 8:32:25 PM", "vatis_version": "3.1.1.0" } It is up to you to configure your endpoint to accept and pass the data as you see fit. Edited April 16, 2020 at 12:52 AM by Justin Shannon Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
Recommended Posts