"board": "Aesys(R) 1504B" the model/revision of the TC-430™ hardware PCB
"fw-version": "ID 0001, ver..." the version of the TC-430™ co-processor firmware
"os-version": "Linux tc430..." the build of the operating system being
run by TC-430™
"sw-version": "1.90.0", the version of TC-430™ application
}
11.7.2 Service data definition format
The following data fragment represents the JSON document returned when asking info about the service
data definition currently being used by TC-430™ (http://<tc-430-ipaddress>:<port>/system/data/status).
Every item of the JSON document is commented for documenting its meaning.
{
"format": "vdb", the format of the service data definition file being
used by the TC-430™ (it can be none, trx or
vdb)
"level": 90, the current service data definition; -1 if the level
is not available (e.g. for TRX files or no files)
"unit-profile": "0TC430" the code of the unit profile configured within
the current service data definition file, if any; an
empty string if not available (e.g. for TRX files or
no files)
}
11.7.3 Navigation data format (EXT-MIS format)
The following data fragment represents the JSON document returned when asking navigation data to the
TC-430™ using the HTTP interface returning them in EXT-MIS format (http://<tc-430-
ipaddress>:<port>/navigation-data/ext-mis).
Every item of the JSON document is commented for documenting its meaning.
{
"dt": "08/06/2017 15:33:04", date and time
"extra": { (reserved for future usage)
},
"id": 0, id that is incremented whenever
navigation data change
"position": {
"avis": -1, (reserved for future usage)
"dl": -1, current time profile of the bus, expressed in
seconds (delay if greather than zero, advances if
To Next Page
Loading...
Need help?
General