Use device specific DBC files
You may have an Amazon/Google/Azure bucket/container that contains multiple device groups, each of which requires separate DBC files. Here you can use the below method[1]:
Download below
dbc-groups.jsonand update it with your device/DBC listsUpload the JSON file to your input bucket/container root
Ensure that your log files are stored in the CANedge folder structure
Verify that your automation now only applies the device specific DBC files
{
"common_dbc_files": ["can9-database-01.09.dbc"],
"dbc_groups": [
{
"devices": ["2A896980", "2F6913DB", "18D508A1"],
"dbc_files": ["can1-typeA.dbc", "can2-mydbc2.dbc"]
},
{
"devices": ["12345678"],
"dbc_files": ["can1-typeB.dbc", "can2-mydbc2.dbc"]
}
]
}
Each device uses the dbc_files of the first group that contains it, plus the optional common_dbc_files used by all your groups (e.g. the CAN9 GNSS/IMU DBC).Devices that are not in any group use all DBC files in the input bucket/container root.
From v4.5.0 you can also keep the DBC files in one folder of the input bucket/container, e.g. "dbc/can1-typeA.dbc". The file name still starts with the channel prefix (can1-, lin1- etc.), and file names must be unique per device.