This JSON schema is used for meta databases which works as an extension to conventional databases.
Works for .ldf
and .dbc
. The meta database is used by the RemotiveBroker to describe functions not available in conventional databases. Such as, E2E and Covesa VCC naming.
The RemotiveBroker will read a meta database IF the meta database has the same file name as the conventional AND the suffix .meta.json
. For example the DBC database ./my_db.dbc
and the meta database ./my_db.meta.json
will work together.
This document is written for format version 0.1.0
File format version. Verifies that the RemotiveBroker can read the file.
Dictionary with frame names as keys and meta database information as value.
All properties whose name matches the following regular expression must respect the following conditions
Property name regular expression:.+
Frames must be named with a corresponding frame in the parent signal database.
E2E information, different profiles need different fields. Se profile field for more information
Name of signal containing the E2E counter.
Name of signal containing the E2E checksum.
Data ID to be used in CRC calculation.
Profile to use. Supported profiles and required fields:
* PROFILE_AR_01A
, requires counter
, crc
and dataId
.
Signal groups, these are byte spanning ranges inside of a frame.
No Additional ItemsSignal group properties. Each groups is limitid to a range of bytes.
E2E information, different profiles need different fields. Se profile field for more information
Same definition as e2eByte offset insife of the frame signifying the start of this group
Size of the group in bytes