[canbus]
This section is only required if you are using any of the canbus features in the system, such as canbus rebroadcast, or are using a second instance of SDC as a control screen to drive your cluster over canbus.
| Setting | Type | Explanation |
|---|---|---|
| controllerid | Integer | Default value 2001. This specifies the canbus ID of the “controller” for instances where you want to control one instance of SDC with another over the canbus. Both instances should be configured with the same controller id. |
| ecuid | Integer | Default 2000. This specifies the canbus ID that messages containing ECU data will be broadcast on. If the node you are configuring is set up for Canbus Rebroadcast, then this is the canbus ID it will send all data with. If the node you are configuring is intended to receive canbus data, then this is the canbus ID it should expect data to be received on |
| accessoryid | Integer | Default 1998. The canbus ID of accessory status messages. SDC expects to receive these over canbus but never broadcasts them. By default this id is lower than the ECU data so that things like indicator messages are as timely as possible. See the help on accessory bits in the Attribute Names help |
| speed | Integer | Default value 1000. Defines the speed in kbps (kilobits per second) that the bus should be initialised for. Possible values are 100, 125, 200, 250, 500, 1000. So 1000kbps = 1mbit, which is the fastest possible speed. |
| rebroadcastmicroseconddelay | Integer | Default 0 (no delay). Defines a period in microseconds that the rebroadcast process should wait for between sending canbus messages. This setting is not normally required. |
| loggingratehz | Integer | Default value 25. Defines the number of times per second the canbus implementation should dump a datalog row. Specifying zero or removing the line from the ini file will use the default value of 25. To disable data logging altogether, use the setting in the [datalog] section. |
Although ECU data is by default sent on canbus ID 2000, a small number of parameters will be sent on canbus Id 1999 (i.e. ecuid - 1). This is because canbus networks use the canbus ID as a priority field and 1999 has a higher priority than 2000. So sending some data with an ID of 1999 prevents them from being overwritten by other less important data. The attributes that are sent as a higher priority are:
- RPM
- MAP
- VE
- O2