Based on the discussion about CPDLC here: https://swift-project.slack.com/archives/C04J6J76N/p1547309311001200
- XPlane plugins use datarefs (XSB)
- We could also support them
- Not high prio
- but based on discussion some of them would be very easy to set on XSwiftBus side
we (i work for magknight) and Toliss/FF have got pretty good implementations of CPDLC for the 787/A350 working now using that interface
and where are the CPDLC data coming from? I fail to see how this is related to VATSIM as VATSIM does not support a CPDLC standard yet (edited)
In our case, we use contact-me messages for radio uplink, and have collected a substantial amount of euroscope alias messages, then match them
there is some _de facto_ standard used by agreement between controllers and pilots, this is the CPDLC we discussed supporting long time ago
swift supports 3+ different simulators, with more possible. So not just XP. We could provide the XSB datarefs on XP only. It would be nice to support XSB addons out of the box. But it's not a high priority at present. Beta is coming, and with it more open access to our source code; let's see if we get any more developers lending a hand.
it can also send structured text messages for quite a lot of stuff
Just for me to get it right, you are using normal FSD/VATSIM text messages for CPDLC? And by structured text messages you mean the format for those messages?
yes, we are
Can you upload those messages overview for me just to get an impression. Please use the + button "Code/Snippet"
Or upload as file
i'll assemble a list of them
most of what i've got in my local one is from the UK alias set
thanks, again for my understanding
- Do you also send CPDLC values or just display those messages in a CPDLC unit?
- Are there other use cases (besides CPDLC) you know usings those data refs?
there are seporate messages that are sent from the plane, but i don't have that list currently
i know it's used for selcal and some small things
mostly just adding features that XSB doesn't support by default
and are you sending CPDLC messages also or is it just displaying?
we are also sending them, but that code isn't very far along
it's used by some things for checking if you're connected to vatsim, such as aerobask's GA planes
and you "parse" all private ATC messages for the above patterns?
and if it matches you display them as CPDLC message, otherwise ignore
we parse every message that XSB recieves, which include ones on frequencies
the on-frequency ones we check against the callsign then the other stuff
Related internal discussion
@oktal what are the datarefs?
datarefs: that seems to be similar to the P3D/FSX offsets defined by SB4. writing and reading to a memory area.
To me it looks like it was reasonable effort to support setting these values. In the FSX driver I do that, but there it is actually only the XPDR mode. Of course I leave that up to RR/MS.
In P3D/FSX both vPilot and we swift support the SB offsets because those are the ones supported by the vendors
Yeah, read/write by XP plugin API: http://www.xsquawkbox.net/xpsdk/mediawiki/Category:XPLMDataAccess
For which in xswiftbus we have our C++ wrapper: https://dev.swift-project.org/source/pilotclient/browse/develop%252F0.8.8/src/xswiftbus/datarefs.h
Example using datarefs: https://dev.swift-project.org/source/pilotclient/browse/develop%252F0.8.8/src/xswiftbus/weather.h
What are the contact-me messages? I remember them as normal text messages starting with "contact me" or is this something different?
Being naive, it sounds like we would only need to set the dataref for text messages when they are sent via XSwiftBus (edited)
contact-me's are regular private messages from ATC user? so whatever format the ATC client developer chose (edited)