An ECU entry identifies the electronic control unit behind a command address, such as the engine or transmission controller. Entries belong in the optional ecu array of a signalset.
Properties
The OBDb signals schema defines these properties:
| Property | Type | Required | Description |
|---|---|---|---|
hdr | string | Yes | Header the command is sent to, hex |
eax | string | No | Extended address the command is sent to, hex |
rax | string | No | Address the command is answered from, hex |
filter | object | No | |
type | string | Yes | Kinds of electronic control unit. Pelican maps each to a localized name, so add a value here only alongside its string there. |
Matching commands
An entry matches a command with the same hdr. If the entry sets eax or rax, those addresses must also match. If it sets filter, the car’s model year must match that filter.
When several entries match, the entry that sets the most of eax, rax, and filter wins.
Use filter.from and filter.to to set a model-year range, including both endpoints. Use filter.years to list individual model years.
Module types
The schema accepts these values for type:
| Value |
|---|
abs |
airbag |
allWheelDrive |
battery |
bodyControl |
charger |
cluster |
dcdcConverter |
door |
driverAssistance |
engine |
gateway |
hvac |
hybridControl |
infotainment |
keyless |
lighting |
motor |
parkingAssist |
seat |
steering |
suspension |
telematics |
tpms |
transmission |
vehicleControl |