Support CDM data to Nool VDGS system

[marud94]

Nool VDGS for MSFS are capable of showing CDM data (CTOT, TOBT and TSAT).

Any chance to Support pushing data there so pilots can see their times in sim?

https://vdgs.nool.ee/getting-started/datalink/

[paavoph]

FYI, specifications are now available from: https://fs.nool.ee/MSFS/VDGS/Specs/

The format is simple enough that a function similar to CDM::saveData() can create the airport data feed file.

[rpuig2001]

Hi all, I created the request, it would be enabled with the config parameter

vdgsFileType:

1. TXT File.
2. Json File.
3. Both

I created the following example: { "version":1, "flights":[ { "lat":41.2923, "lon":2.09795, "icao_type":"A320", "callsign":"CFG7521", "flight":"CFG7521", "tobt":"1910", "tsat":"1910", "runway":"24L", "sid":"MOPAS5Q" }, { "lat":41.2915, "lon":2.07371, "icao_type":"A320", "callsign":"BAW483B", "flight":"BAW483B", "tobt":"1913", "tsat":"1913", "runway":"24L", "sid":"MOPAS5Q" }, { "lat":41.296, "lon":2.08078, "icao_type":"B738", "callsign":"UAE902", "flight":"UAE902", "tobt":"1905", "tsat":"1910", "runway":"24L", "sid":"GRAUS6Q" }, { "lat":41.2895, "lon":2.08062, "icao_type":"A320", "callsign":"VLG07UD", "flight":"VLG07UD", "tobt":"1923", "tsat":"1923", "runway":"24L", "sid":"DALIN5Q" }, { "lat":41.2911, "lon":2.07241, "icao_type":"A320", "callsign":"BAW485", "flight":"BAW485", "tobt":"1925", "tsat":"1925", "runway":"24L", "sid":"NATPI3Q" }, { "lat":41.289, "lon":2.07675, "icao_type":"A339", "callsign":"CRL57WS", "flight":"CRL57WS", "tobt":"1940", "tsat":"1940", "runway":"24L", "sid":"DALIN5Q" }, { "lat":41.2912, "lon":2.07308, "icao_type":"A320", "callsign":"BAW481", "flight":"BAW481", "tobt":"1940", "tsat":"1940", "runway":"24L", "sid":"MOPAS5Q" }, { "lat":41.2918, "lon":2.07496, "icao_type":"A320", "callsign":"BAW49TA", "flight":"BAW49TA", "tobt":"1940", "tsat":"1942", "runway":"24L", "sid":"NATPI3Q" } ] }

Which other requirements are needed? Should it be sent to a configured ftp set by the CDM station or something has to be changed?

[paavoph]

Field flight should be set to IATA flight number if available (eg U22432 for an EasyJet flight with callsign EZY57UP), or left empty or entirely omitted if the flight number is not known. Field destination is missing from the JSON. If possible, ICAO code of the destination airport from the filed flight plan should be set there, because some docking devices show that on the screen. Everything else looks good. Thank you for implementing this.

As to uploading, I am not sure how vACCS have set things up, but uploading to the same destination where other text files go should be fine.

[rpuig2001]

Hi @paavoph,

Modifiactions done accordinlgy:

• Removed flight number (as we don't have it).
• Added destination.

Example: {"version":1,"flights":[{"lat":41.2914,"lon":2.07899,"icao_type":"A20N","callsign":"IBE2256","destination":"LEIB","tobt":"1210","tsat":"1210","runway":"24L","sid":"LARPA6Q"}]}

Roger.

[paavoph]

That looks perfect to me.