What CAN IDs are occupied?
siliXcon device occupies CAN ID space for communication. The following tables show the CAN IDs used.
tip
- The protocol is not limited to the CAN bus. Other communication interfaces, such as USART, USB or Bluetooth may be used to access the device as well.
- In case of a conflict, you can turn off (or relocate) the parts of siliXcon protocol on the CAN bus (or any other interface), using the
protoconfcommand. - The number of address bits n can be changed with the
msgconfcommand (CANcfg2parameter). - The SID offset can be configured via
protoconfSID remapping.
Use the controls below to recalculate the CAN IDs for a different addressing configuration. When the resulting CAN ID exceeds the standard 11-bit range (0x7FF), extended 29-bit CAN IDs are used (marked with EXT).
Find SID Offset From a CAN ID
If you know a CAN ID and want to derive the SID offset for SID 0, enter the CAN ID and the number of address bits below.
SID Offset From CAN ID
Suggested SID offset for SID 0: 0
0x0Address bits in the entered CAN ID: 0 of 7
SID offset = 0x000 >> 3uint32_t bytes, little-endian:
0, 0, 0, 0Group size: 8 (max 8 devices on bus) ·
CAN_ID = (SID << 3) + address · Standard CAN ID max: 0x7FFService protocol
The service protocol is used by all siliXcon devices to communicate with the SWTools.
| Service name | SID | Start ID (addr 0) | End ID (addr 7) |
|---|---|---|---|
| Reset | 0 | 0x000 | 0x007 |
| reserved | 1 | 0x008 | 0x00F |
| Forward | 2 | 0x010 | 0x017 |
| ID | 3 | 0x018 | 0x01F |
| Bootloader | 4 | 0x020 | 0x027 |
| Bootloader | 5 | 0x028 | 0x02F |
| File system | 6 | 0x030 | 0x037 |
| File system | 7 | 0x038 | 0x03F |
| RPC | 8 | 0x040 | 0x047 |
| RPC | 9 | 0x048 | 0x04F |
| Terminal | 10 | 0x050 | 0x057 |
| Terminal | 11 | 0x058 | 0x05F |
| Scope | 12 | 0x060 | 0x067 |
| Scope | 13 | 0x068 | 0x06F |
| Scope | 14 | 0x070 | 0x077 |
| Scope | 20 | 0x0A0 | 0x0A7 |
| Scope | 21 | 0x0A8 | 0x0AF |
| Scope | 22 | 0x0B0 | 0x0B7 |
siliXcon controllers
Driver protocol
The driver protocol is used only by siliXcon controllers.
| Service name | SID | Start ID (addr 0) | End ID (addr 7) |
|---|---|---|---|
| Sampling setup Driver execute command | 24 | 0x0C0 | 0x0C7 |
| CMD | 25 | 0x0C8 | 0x0CF |
| State 1 | 26 | 0x0D0 | 0x0D7 |
| Range | 27 | 0x0D8 | 0x0DF |
| Supply 1 | 28 | 0x0E0 | 0x0E7 |
| Supply 2 | 29 | 0x0E8 | 0x0EF |
| Motor 1 | 30 | 0x0F0 | 0x0F7 |
| Motor 2 | 31 | 0x0F8 | 0x0FF |
| Motor 3 | 32 | 0x100 | 0x107 |
| Motor 4 | 33 | 0x108 | 0x10F |
| Supply 3 | 34 | 0x110 | 0x117 |
| Supply 4 | 35 | 0x118 | 0x11F |
| State 2 | 36 | 0x120 | 0x127 |
Common block protocol
| Service name | SID | Start ID (addr 0) | End ID (addr 7) |
|---|---|---|---|
| CMIO periodic sampling | 40 | 0x140 | 0x147 |
| Bank 0 | 41 | 0x148 | 0x14F |
| Bank 1 | 42 | 0x150 | 0x157 |
| Bank 2 | 43 | 0x158 | 0x15F |
| Bank 3 | 44 | 0x160 | 0x167 |