2.12.6 sEEPromIDctrl eepID
The sEEPromIDctrl eepID variable contains the settings for the ID check. 18 IDs with up to 4 bytes together with a config variable and a global enable variable can be stored in this structure. See ID Check for a functional description, and ID Check for a hardware description.
|
Address |
Name |
Bit 7 |
Bit 6 |
Bit 5 |
Bit 4 |
Bit 3 |
Bit 2 |
Bit 1 |
Bit 0 |
|---|---|---|---|---|---|---|---|---|---|
|
0x0036 |
idEna | — | — | — |
ID[4:0] | ||||
|
0x0037 |
data[0][0] |
data0_byte0[7:0] | |||||||
|
0x0038 |
data[0][1] |
data0_byte1[7:0] | |||||||
|
0x0039 |
data[0][2] |
data0_byte2[7:0] | |||||||
|
0x003A |
data[0][3] |
data0_byte3[7:0] | |||||||
|
0x003B |
config[0] |
IDCE | — | — | — |
IDBO[1:0] |
IDL[1:0] | ||
|
... | ... | ... | |||||||
|
0x008C |
data[17][0] |
data17_byte0[7:0] | |||||||
|
0x008D |
data[17][1] |
data17_byte1[7:0] | |||||||
|
0x008E |
data[17][2] |
data17_byte2[7:0] | |||||||
|
0x008F |
data[17][3] |
data17_byte3[7:0] | |||||||
|
0x0090 |
config[17] |
IDCE | — | — | — |
IDBO[1:0] |
IDL[1:0] | ||
idEna
The idEna variable is used to activate the ID check and define the number of active IDs.
|
Address |
Name |
Bit 7 |
Bit 6 |
Bit 5 |
Bit 4 |
Bit 3 |
Bit 2 |
Bit 1 |
Bit 0 |
|---|---|---|---|---|---|---|---|---|---|
|
0x0036 |
idEna | — | — | — |
ID[4:0] | ||||
Bits 7..5: Reserved Bits
These bits are reserved for future use and must be set to ‘0’.
Bits 4..0: ID[4:0] – Number of Enabled IDs
|
ID[4] |
ID[3] |
ID[2] |
ID[1] |
ID[0] |
Description |
|---|---|---|---|---|---|
|
|
|
|
|
|
ID check function disabled |
|
|
|
|
|
|
ID check function enabled for ID 0 (all other IDs are disabled) |
|
|
|
|
|
|
ID check function enabled for ID 0 to 1 (all other IDs are disabled) |
|
|
|
|
|
|
ID check function enabled for ID 0 to 2 (all other IDs are disabled) |
|
... |
... |
... |
... |
... |
... |
|
|
|
|
|
|
ID check function enabled for ID 0 to 17 |
|
|
|
|
|
|
Not applicable |
|
... |
... |
... |
... |
... |
... |
|
|
|
|
|
|
Not applicable |
data
The data variables store the IDs themselves with a length of 1, 2, 3 or 4 bytes. The IDs are stored MSB-first, starting with the data[x][0] variable (x = 0..17). Each ID can have a unique length.
|
Name |
Bit 7 |
Bit 6 |
Bit 5 |
Bit 4 |
Bit 3 |
Bit 2 |
Bit 1 |
Bit 0 |
|---|---|---|---|---|---|---|---|---|
|
data[x][0] |
data0_byte0[7:0] | |||||||
|
data[x][1] |
data0_byte1[7:0] | |||||||
|
data[x][2] |
data0_byte2[7:0] | |||||||
|
data[x][3] |
data0_byte3[7:0] | |||||||
config
The config variable contains the configuration data of the corresponding ID.
|
Name |
Bit 7 |
Bit 6 |
Bit 5 |
Bit 4 |
Bit 3 |
Bit 2 |
Bit 1 |
Bit 0 |
|---|---|---|---|---|---|---|---|---|
|
config[x] |
IDCE | — | — | — |
IDBO[1:0] |
IDL[1:0] | ||
Bit 7: IDCE – ID Check Execute
This bit must be set to ‘1’. If set to ‘0’, the hardware
correlator omits the corresponding ID.
Bits 6..4: Reserved Bits
These bits are reserved for future use and must be set to ‘0’.
Bits 3..2: IDBO[1:0] – ID Byte Offset
|
IDBO[1] |
IDBO[0] |
Description |
|---|---|---|
|
|
|
ID check starts with 1st byte in telegram payload |
|
|
|
ID check starts with 2nd byte in telegram payload |
|
|
|
ID check starts with 3rd byte in telegram payload |
|
|
|
ID check starts with 4th byte in telegram payload |
Bits 1..0:IDL[1:0] – ID Length
|
IDL[1] |
IDL[0] |
Description |
|---|---|---|
|
|
|
ID length is 1 byte, data_byte0 is used only |
|
|
|
ID length is 2 bytes, data_byte0 and data_byte1 are used only |
|
|
|
ID length is 3 bytes, data_byte0 .. data_byte2 are used only |
|
|
|
ID length is 4 bytes, data_byte0 .. data_byte3 are used |
