RemotiveBroker meta database json format schema

Type: object

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

Type: enum (of string)

File format version. Verifies that the RemotiveBroker can read the file.

Must be one of:

  • "0.1.0"

Type: object

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: .+
Type: object

Frames must be named with a corresponding frame in the parent signal database.

Type: object

E2E information, different profiles need different fields. Se profile field for more information

Type: string

Name of signal containing the E2E counter.

Type: string

Name of signal containing the E2E checksum.

Type: integer

Data ID to be used in CRC calculation.

Type: enum (of string)

Profile to use. Supported profiles and required fields:
* PROFILE_AR_01A, requires counter, crc and dataId.

Must be one of:

  • "PROFILE_AR_01A"

Type: array of object

Signal groups, these are byte spanning ranges inside of a frame.

No Additional Items

Each item of this array must be:

Type: object

Signal group properties. Each groups is limitid to a range of bytes.

Type: object

Type: object

E2E information, different profiles need different fields. Se profile field for more information

Same definition as e2e

Type: integer

Byte offset insife of the frame signifying the start of this group

Type: integer

Size of the group in bytes