Introduction
The AIO has an onboard Eeprom connected via I2C to the DSPIC33E (The Master). This document describes the Eeprom memory locations used.
General Configuration Bytes (Page 0)
- Page 0 -> Controller specific data
- When this value = 255, Automatic detection (detected via the Front Panel Hardware) will be done if this module is a Core or a Core+ module. When this value = 0 the system is forced to act as a Core, when this value = 1 the system is forced to act as a Core+ without any hardware detection.
- Number of output modules: This byte specifies the number of output (output, dim control, shutter/curtain ...) modules known by the Master controller on the RS485 bus. Maximum 80.
- Number of input modules: This byte specifies the number of input (input, can control ...) modules known by the Master controller on the RS485 bus. Maximum 80.
- Number of sensor modules: This byte specifies the number of sensor modules known by the Master controller on the RS485 bus. Maximum 16.
- Scan time RS485 sensor modules: This value (between 1 and 254) will indicate the scan time (in 100ms) between each of the sensor module values of the individual modules. If the value =255 or =0, the standard value (50) will be taken (=value scan every 5 seconds). The more sensor modules, the lower this value can be set.
- Nr of CAN Inputs: This value indicate the number of CAN inputs found on the CAN bus. When this value is 0 or 255 then no inputs have been found yet.
- Nr of CAN sensors: This value indicate the number of CAN sensors found on the CAN bus. When this value is 0 or 255 then no sensors have been found yet.
- Nr of CAN modules: This value indicate the number of CAN modules found on the CAN bus. When this value is 0 or 255 then no CAN modules have been found yet.
- Scan time RS485 Bus: This value (between 1 and 254) will indicate the scan time (in ms) between each individual module. If the value =255 or =0, the standard value (8) will be taken (=scan time 8ms between 2 communication sessions). Higher value will slow down the bus, too low values can increase the error rate on the Bus.
- Nr of CAN Control modules: This value (max 16) indicates the number of CAN Control modules found on the RS485 Bus. When this value is 0 or 255 then no CAN Control modules have been found yet.
- Scan time RS485 Can Control modules: This value (between 1 and 254) will indicate the scan time (in 100ms) between each of the Can Control modules. If the value =255 or =0, the standard value (50) will be taken (=value scan every 5 seconds).
- Byte 50: This is the group nr (MSB) of the follow group action that will be executed when output all off is triggered
- Byte 51: This is the group nr (LSB) of the follow group action that will be executed when output all off is triggered
- Byte 52: This is the group nr (MSB) of the startup group action that will be executed at startup or reset of the processor
- Byte 53: This is the group nr (LSB) of the startup group action that will be executed at startup or reset of the processor
- Byte 54: This is the group nr (MSB) that will be executed when the time (minutes) is changed.
- Byte 55: This is the group nr (LSB) that will be executed when the time (minutes) is changed.
- Byte 56: This is the group nr (MSB) that will be executed when the time (hours) is changed.
- Byte 57: This is the group nr (LSB) that will be executed when the time (hours) is changed.
- Byte 58: This is the group nr (MSB) that will be executed when the date (days) is changed.
- Byte 59: This is the group nr (LSB) that will be executed when the date (days) is changed.
Data output modules (Page 1-80)
- Page 1 – 80 -> Contains data of the output modules (80 modules maximum, 640 outputs -> 0-639)
The output data can be found back from page 1 till page 80. These Pages that contains active data depending on Page0/Byte1.
Every output Module (that can be configured in normal or Roller/Shutter mode) has its own output page which contains the normal output data and the Roller/Shutter data:
- This page is entirely used for output module 0.
- This page is entirely used for output module 1.
- This page is entirely used for output module 2.
...
- This page is entirely used for output module 79.
- Every output page has following structure
Output data
- Byte 0: Type device (more information see document “Technical device information”)
- Byte 1: ID1 (ID1, 2, 3 gives the unique ID of the device)
- Byte 2: ID2
- Byte 3: ID3
- Byte 4: Firmware Version F1 (Major)
- Byte 5: Firmware Version F2 (Minor)
- Byte 6: Firmware Version F3 (Built)
- Standard Timer values for an output to be used. Each timer value has a word format and is programmed in 2 bytes (first byte LSB). The function of this word is decibed in the Timer Type Byte..
- Byte 7 (LSB) and 8 (MSB) will specify the timer value for output 0
- Byte 9 (LSB) and 10 (MSB) will specify the timer value for output 1
- ...
- Byte 21 (LSB) and 22 (MSB) will specify the timer value for output 7
- Standard Timer types for an output to be used. Each output has a timer type
- Byte 23 Timer type for output 0
- Byte 24 Timer type for output 1
- ...
- Byte 30 Timer type for output 7
- When Timer Type=0 or 255 -> Timer not active or not configured
- When Timer Type=1 -> Timer value contains 100ms value in other words, if for example the Timer value (word) = 6004, the timer is set to 600.4 seconds
- When Timer Type=2 -> Timer value contains second value in other words, if for example the Timer value (word) = 6004, the timer is set to 6004 seconds
- When Timer Type=3 -> Time value contains switch off time (MSB=Hour, LSB=minute)
- Byte 31: Output type byte output0 (=0: standard output, >0: Light output)
- Byte 32: Output Type byte output1 (=0: standard output, >0: Light output)
- …
- Byte 38: Output Type byte output7 (=0: standard output, >0: Light output)
- Output Type byte will indicate if the indicated output is a light or not. When specific instruction (by using action type 163 for example) to switch off a light will be used, only lights (and not outputs) will be switched off.
- Byte 39: Minimum output level when dimming for Output 0.
- Byte 40: Minimum output level when dimming for Output 0.
- …
- Byte 46: Minimum output level when dimming for Output 7.
- Note: When the standard value (255) of eeprom is used, the minimum value is set on 8. The programmed value should be between 0 and 62.
- Byte 47: Maximum output level when dimming for Output 0.
- Byte 48: Maximum output level when dimming for Output 0.
- …
- Byte 54: Maximum output level when dimming for Output 7.
Output Group Follow
- Output Group follow: Page 1-80, byte 55-70
- Byte 55: Group nr (MSB) to execute when Output 0 of this module is changing
- Byte 56: Group nr (LSB) to execute when Output 0 of this module is changing
- Byte 57: Group nr (MSB) to execute when Output 1 of this module is changing
- Byte 58: Group nr (LSB) to execute when Output 1 of this module is changing
- …
- Byte 69: Group nr (MSB) to execute when Output 7 of this module is changing
- Byte 70: Group nr (LSB) to execute when Output 7 of this module is changing
DALI: Link Output Nr with Dali Nr
Every output can be linked to a Dali output with address (0-63) or linked to a Dali group (0-15). When the output is switched ON, OFF or dimmed, the Dali output will follow. Typically, a virtual output module is created and the those virtual outputs are linked to Dali outputs. In the below page, the Dali Output can be programmed for a system output.
- Byte 71: Output 0 of this module is linked with Dali Output x (when x<64) or with Dali Group x-64 (when x>63 and x<80)
- Byte 72: Output 1 of this module is linked with Dali Output x (when x<64) or with Dali Group x-64 (when x>63 and x<80)
- …
- Byte 78: Output 7 of this module is linked with Dali Output x (when x<64) or with Dali Group x-64 (when x>63 and x<80)
ascii Names outputs
- Byte 128 – 143: ascii name of the first output of this module (16 characters)
- Byte 144 – 159: ascii name of the second output of this module (16 characters)
- …
- Byte 240 – 255: ascii name of the last output (16 characters)
Data input modules (Page 81 - 238)
- Page 81 – 238 -> Contains data of the input modules (79 modules maximum, 632 inputs -> 0-631)
The input data can be found back from page 81 till page 238, each input module has 2 pages. These Pages contain active data depending on Page0/Byte2.
Every input Module has 2 input pages which contains all the input and configuration data:
- These pages are entirely used for input module 0. Page 81 is the first page, 82 the second.
- These pages are entirely used for input module 1. Page 83 is the first page, 84 the second.
- These pages are entirely used for input module 2. Page 85 is the first page, 86 the second.
...
- These pages are entirely used for input module 78. Page 237 is the first page, 238 the second.
- Every input page has following structure
Input data
- Byte 0: Type device (more information see document “Technical device information”)
- Byte 1: ID1 (ID1, 2, 3 gives the unique ID of the device)
- Byte 2: ID2
- Byte 3: ID3
- Byte 4: Firmware Version F1 (Major)
- Byte 5: Firmware Version F2 (Minor)
- Byte 6: Firmware Version F3 (Built)
Input configuration
| Page
|
Byte
|
| First page |
7-14
|
Each input has 1 configuration byte, 8 configuration bytes per module. Each BIT of the configuration byte represents an input configuration. BIT0 is the least significant BIT of the configuration BYTE, BIT7 is the most significant BIT.
- Configuration Byte of first input (0) of this module:
- BIT0: On the different inputs of the OpenMotics system, both NC (normally close, BIT0=0) and NO (normally open, BIT0=1) switches can be connected. In this byte, in BIT0, you can program for each input if the input is NO or NC. Standard, all inputs are programmed as NO (BIT0=1).
- Configuration Byte of second input (1) of this module:
- BIT0: On the different inputs of the OpenMotics system, both NC (normally close, BIT0=0) and NO (normally open, BIT0=1) switches can be connected. In this byte, in BIT0, you can program for each input if the input is NO or NC. Standard, all inputs are programmed as NO (BIT0=1).
…
- Configuration Byte of last input (7) of this module:
- BIT0: On the different inputs of the OpenMotics system, both NC (normally close, BIT0=0) and NO (normally open, BIT0=1) switches can be connected. In this byte, in BIT0, you can program for each input if the input is NO or NC. Standard, all inputs are programmed as NO (BIT0=1).
DALI: Link Input Nr with Dali Nr
Every input can be linked to a Dali input (like motion sensor) with address (0-63). When the Dali Motion sensor detects motion, the linked input will be triggered. Typically, a virtual input module is created and the those virtual inputs are linked to Dali inputs. Lunatone and Helvar inputs are supported. In the below page, the Dali inputs can be programmed to be linked to a system input.
| Page
|
Byte
|
| First page |
15-22
|
- Byte 15: Input 0 of this module is linked with Dali Lunatone input x (when x<64) or with Dali Helvar input x-64 (when x>63 and x<128)
- Byte 16: Input 1 of this module is linked with Dali Lunatone input x (when x<64) or with Dali Helvar input x-64 (when x>63 and x<128)
- …
- Byte 22: Input 7 of this module is linked with Dali Lunatone input x (when x<64) or with Dali Helvar input x-64 (when x>63 and x<128)
ascii Names inputs
| Page
|
Byte
|
| First page |
128-255
|
- Byte 128 – 143: ascii name of the first input of this module (16 characters)
- Byte 144 – 159: ascii name of the second input of this module (16 characters)
- …
- Byte 240 – 255: ascii name of the last input (16 characters)
Toggle input link
| Page
|
Byte
|
| Second page |
0-15
|
For each input, an output or a special function (basic actions) can be linked. This is configured in the following bytes:
- Byte 0: MSB of the input link word of input 0 of this input module
- Byte 1: LSB of the input link word of input 0 of this input module
- Byte 2: MSB of the input link word of input 1 of this input module
- Byte 3: LSB of the input link word of input 1 of this input module
- Byte 4: MSB of the input link word of input 2 of this input module
- Byte 5: LSB of the input link word of input 2 of this input module
- …
The input link word has following configuration:
- BIT 0-9: These bits contains the output number of the output to be toggled by input x (only works when BIT10,12,13,14,15=0)
- BIT10: 0->Toggle output in BIT0-9 is used, 1->"input action press" basic actions, "input action release" basic actions etc are being used
- BIT11: 1-> Dimming up when the BIT10=0 and BIT0-9 contains a dimmer output, 0->Dimming down when the BIT10=0 and BIT0-9 contains a dimmer output (this bit can be ignored when programming the input link word)
- BIT12: 1-> 1 second press & hold function is programmed, 0-> 1 second press & hold function is not programmed
- BIT13: 1-> 2 second press & hold function is programmed, 0-> 2 second press & hold function is not programmed
- BIT14: Not used
- BIT15: 1-> Double press is programmed, 0-> Double press is not programmed
Notes:
- When Input link BIT10=1, the PRESS and RELEASE basic action will work.
- For the 1SEC, 2SEC or DOUBLE PRESS actions to work BIT10=0 and BIT(12 and/or 13 and/or 15)=1
- When 1SEC or 2SEC or DOUBLE PRESS actions is activated, the RELEASE action will work but not the PRESS action
Input action "Press"
| Page
|
Byte
|
| Second page |
16-63
|
Each input can be linked to a basic action (6 bytes) when the input is pressed. See Action Types AIO for more details about the possible basic actions that can be used.
| Page
|
Byte
|
| Second page |
16-21
|
These 6 bytes represents the basic action bytes for input 0 of this module:
- Byte 16: Type
- Byte 17: Action
- Byte 18: Device Nr (MSB)
- Byte 19: Device Nr (LSB)
- Byte 20: Extra Parameter (MSB)
- Byte 21: Extra Parameter (LSB)
| Page
|
Byte
|
| Second page |
22-27
|
These 6 bytes represents the basic action bytes for input 1 of this module:
- Byte 22: Type
- Byte 23: Action
- Byte 24: Device Nr (MSB)
- Byte 25: Device Nr (LSB)
- Byte 26: Extra Parameter (MSB)
- Byte 27: Extra Parameter (LSB)
...
Input action "Release"
| Page
|
Byte
|
| Second page |
64-111
|
Each input can be linked to a basic action (6 bytes) when the input is released. See Action Types AIO for more details about the possible basic actions that can be used.
| Page
|
Byte
|
| Second page |
64-69
|
These 6 bytes represents the basic action bytes for input 0 of this module:
- Byte 64: Type
- Byte 65: Action
- Byte 66: Device Nr (MSB)
- Byte 67: Device Nr (LSB)
- Byte 68: Extra Parameter (MSB)
- Byte 69: Extra Parameter (LSB)
| Page
|
Byte
|
| Second page |
70-75
|
These 6 bytes represents the basic action bytes for input 1 of this module:
- Byte 70: Type
- Byte 71: Action
- Byte 72: Device Nr (MSB)
- Byte 73: Device Nr (LSB)
- Byte 74: Extra Parameter (MSB)
- Byte 75: Extra Parameter (LSB)
...
Input action "1 second press"
| Page
|
Byte
|
| Second page |
112-159
|
Each input can be linked to a basic action (6 bytes) when the input is pressed for 1 second. See Action Types AIO for more details about the possible basic actions that can be used.
| Page
|
Byte
|
| Second page |
112-117
|
These 6 bytes represents the basic action bytes for input 0 of this module:
- Byte 112: Type
- Byte 113: Action
- Byte 114: Device Nr (MSB)
- Byte 115: Device Nr (LSB)
- Byte 116: Extra Parameter (MSB)
- Byte 117: Extra Parameter (LSB)
| Page
|
Byte
|
| Second page |
118-123
|
These 6 bytes represents the basic action bytes for input 1 of this module:
- Byte 118: Type
- Byte 119: Action
- Byte 120: Device Nr (MSB)
- Byte 121: Device Nr (LSB)
- Byte 122: Extra Parameter (MSB)
- Byte 123: Extra Parameter (LSB)
...
Input action "2 second press"
| Page
|
Byte
|
| Second page |
160-207
|
Each input can be linked to a basic action (6 bytes) when the input is pressed for 2 seconds. See Action Types AIO for more details about the possible basic actions that can be used.
| Page
|
Byte
|
| Second page |
160-165
|
These 6 bytes represents the basic action bytes for input 0 of this module:
- Byte 160: Type
- Byte 161: Action
- Byte 162: Device Nr (MSB)
- Byte 163: Device Nr (LSB)
- Byte 164: Extra Parameter (MSB)
- Byte 165: Extra Parameter (LSB)
| Page
|
Byte
|
| Second page |
166-171
|
These 6 bytes represents the basic action bytes for input 1 of this module:
- Byte 166: Type
- Byte 167: Action
- Byte 168: Device Nr (MSB)
- Byte 169: Device Nr (LSB)
- Byte 170: Extra Parameter (MSB)
- Byte 171: Extra Parameter (LSB)
...
Input action "double press"
| Page
|
Byte
|
| Second page |
208-255
|
Each input can be linked to a basic action (6 bytes) when the input is double pressed. if an input is single pressed, the action "Release" will be executed. See Action Types AIO for more details about the possible basic actions that can be used.
| Page
|
Byte
|
| Second page |
208-213
|
These 6 bytes represents the basic action bytes for input 0 of this module:
- Byte 208: Type
- Byte 209: Action
- Byte 210: Device Nr (MSB)
- Byte 211: Device Nr (LSB)
- Byte 212: Extra Parameter (MSB)
- Byte 213: Extra Parameter (LSB)
| Page
|
Byte
|
| Second page |
214-219
|
These 6 bytes represents the basic action bytes for input 1 of this module:
- Byte 214: Type
- Byte 215: Action
- Byte 216: Device Nr (MSB)
- Byte 217: Device Nr (LSB)
- Byte 218: Extra Parameter (MSB)
- Byte 219: Extra Parameter (LSB)
...
Data Sensor modules (Page 239 - 254)
- Page 239 – 254 -> Contains data of the Sensor modules (16 modules maximum, 128 Sensors -> 0-127)
The sensor data can be found back from page 229 till page 254. These Pages that contain active data depending on Page0/Byte3.
- This page is entirely used for sensor module 0.
- This page is entirely used for sensor module 1.
- This page is entirely used for sensor module 2.
...
- This page is entirely used for sensor module 15.
- Every sensor page has following structure
Sensor data
- Byte 0: Type device (more information see document “Technical device information”)
- Byte 1: ID1 (ID1, 2, 3 gives the unique ID of the device)
- Byte 2: ID2
- Byte 3: ID3
- Byte 4: Firmware Version F1 (Major)
- Byte 5: Firmware Version F2 (Minor)
- Byte 6: Firmware Version F3 (Built)
Temperature Group Follow
- Byte 8: Group nr (MSB) to execute when temperature 0 of this module is changing
- Byte 9: Group nr (LSB) to execute when temperature 0 of this module is changing
- Byte 10: Group nr (MSB) to execute when temperature 1 of this module is changing
- Byte 11: Group nr (LSB) to execute when temperature 1 of this module is changing
- …
- Byte 22: Group nr (MSB) to execute when temperature 7 of this module is changing
- Byte 23: Group nr (LSB) to execute when temperature 7 of this module is changing
Humidity Group Follow
- Byte 24: Group nr (MSB) to execute when humidity 0 of this module is changing
- Byte 25: Group nr (LSB) to execute when humidity 0 of this module is changing
- Byte 26: Group nr (MSB) to execute when humidity 1 of this module is changing
- Byte 27: Group nr (LSB) to execute when humidity 1 of this module is changing
- …
- Byte 38: Group nr (MSB) to execute when humidity 7 of this module is changing
- Byte 39: Group nr (LSB) to execute when humidity 7 of this module is changing
Brightness Group Follow
- Byte 40: Group nr (MSB) to execute when brightness 0 of this module is changing
- Byte 41: Group nr (LSB) to execute when brightness 0 of this module is changing
- Byte 42: Group nr (MSB) to execute when brightness 1 of this module is changing
- Byte 43: Group nr (LSB) to execute when brightness 1 of this module is changing
- …
- Byte 54: Group nr (MSB) to execute when brightness 7 of this module is changing
- Byte 55: Group nr (LSB) to execute when brightness 7 of this module is changing
Air Quality Group Follow
- Byte 56: Group nr (MSB) to execute when brightness 0 of this module is changing
- Byte 57: Group nr (LSB) to execute when brightness 0 of this module is changing
- Byte 58: Group nr (MSB) to execute when brightness 1 of this module is changing
- Byte 59: Group nr (LSB) to execute when brightness 1 of this module is changing
- …
- Byte 70: Group nr (MSB) to execute when brightness 7 of this module is changing
- Byte 71: Group nr (LSB) to execute when brightness 7 of this module is changing
DALI: Link sensor Nr with Dali Nr
Every sensor can be linked to a Dali input (with sensor capabilities) with address (0-63). Some Dali motion sensors also have built-in temperature sensors and by some models also a built-in Lux meter. These values can be used to take smart actions. Typically, a virtual sensor module is created and the those virtual sensors are linked to the available Dali sensors. Lunatone is supported. In the below page, the Dali sensors can be programmed to be linked to a virtual system sensor.
- Byte 72: Sensor 0 of this module is linked with Dali Sensor x (when x<64).
- Byte 73: Sensor 1 of this module is linked with Dali Sensor x (when x<64).
- …
- Byte 79: Sensor 7 of this module is linked with Dali Sensor x (when x<64).
ascii Names Sensors
| Page
|
Byte
|
| 239-254 |
128-255
|
- Byte 128 – 143: ascii name of the first sensor of this module (16 characters)
- Byte 144 – 159: ascii name of the second sensor of this module (16 characters)
- …
- Byte 240 – 255: ascii name of the last sensor (16 characters)
Can Control modules (Page 255)
- Page 255 -> Contains data of maximum 16 Can Control modules
In this page, every Can Control has 16 bytes to keep the most important configuration data.
- Byte 0: Type device (more information see document “Technical device information”) of the first Can Control module
- Byte 1: ID1 (ID1, 2, 3 gives the unique ID of the device)
- Byte 2: ID2
- Byte 3: ID3
- Byte 4:
- Byte 5:
- Byte 6:
- Byte 7:
- Byte 8:
- Byte 9:
- Byte 10:
- Byte 11:
- Byte 12:
- Byte 13:
- Byte 14:
- Byte 15:
- Byte 16: Type device (more information see document “Technical device information”) of the second Can Control module
- Byte 17: ID1 (ID1, 2, 3 gives the unique ID of the device)
- Byte 18: ID2
- Byte 19: ID3
- Byte 20:
- Byte 21:
- Byte 22:
- Byte 23:
- Byte 24:
- Byte 25:
- Byte 26:
- Byte 27:
- Byte 28:
- Byte 29:
- Byte 30:
- Byte 31:
- ...
Group Actions Pages (Page 256 - 382)
A Group Action is a list of Basic Actions (BA's) to be executed together.
Group actions are implemented in a flexible way in other words, a group action can contain a flexible number of BA's. As an example, you can configure Group Action 0 to be able to contain 7 BA's, Group Action 1 for 33 BA's.
Group Actions are configured in Eeprom and consist of 3 eeprom sections:
- Page 256-259: GAT (Group Allocation table): This table indicates the start and end address of the BA's of each group action
- Page 261-276: Contains the Group names of each Group Action
- Page 281-380: Contains all the BA's of each Group
Group Action GAT Pages
The Group Allocation Table (GAT) will define the start and end address of each Group Action. These 4 pages defines the start and end addresses of 256 (0-255) group actions.
- Page 256 – 259 -> Contains the Start Address and end addresses of 256 Group Actions
- These 2 bytes contains the start address of Group Action 0 (0->LSB, 1->MSB)
- These 2 bytes contains the end address of Group Action 0 (2->LSB, 3->MSB)
- These 2 bytes contains the start address of Group Action 1 (4->LSB, 5->MSB)
- These 2 bytes contains the end address of Group Action 1 (6->LSB, 7->MSB)
- ...
Group Action Name Page
- Page 261 – 276 -> Contains the Group Actions name.
- Page 261 Byte 0 – 15: ascii name of Group Action 0 (16 characters)
- Page 261 Byte 16 – 31: ascii name of Group Action 1 (16 characters)
- Page 261 Byte 32 – 47: aascii name of Group Action 2 (16 characters)
- ...
- Page 261 Byte 240 – 255: ascii name of Group Action 15 (16 characters)
- Page 261 Byte 0 – 15: ascii name of Group Action 16 (16 characters)
- ...
- Page 277 – 280 -> Reserved for extension Group Action Names.
Group Action BA Pages
Each Page contains 42 BA's. Each BA is made of 6 bytes. The first BA of each page is written in Byte 0-5, the second BA is written in Byte 6-11 etc
- Page 281 – 380 -> Contains data of 4200 BA's.
- This page is entirely used for BA 0 - 41.
- This page is entirely used for BA 42 - 83.
- This page is entirely used for BA 84 - 125.
...
CAN slave modules (Page 383 - 390)
CAN slave configuration
- Page 383-390 -> Contains the configuration data of the CAN slave modules (128 modules maximum)
- This page is entirely used for the configuration data of the CAN slave modules 0-15.
- This page is entirely used for the configuration data of the CAN slave modules 16-31.
- This page is entirely used for the configuration data of the CAN slave modules 32-47.
- This page is entirely used for the configuration data of the CAN slave modules 48-63.
- This page is entirely used for the configuration data of the CAN slave modules 64-79.
- This page is entirely used for the configuration data of the CAN slave modules 80-95.
- This page is entirely used for the configuration data of the CAN slave modules 96-111.
- This page is entirely used for the configuration data of the CAN slave modules 112-127.
- Byte 0: ID_2 of the first CAN module of this page
- Byte 1: ID_1 of the first CAN module of this page
- Byte 2: ID_0 of the first CAN module of this page
- Byte 3: Sensor Link 0 of the first CAN module of this page
- Byte 4: Sensor Link 1 of the first CAN module of this page
- Byte 5: Module link Type:
- Module link type:
- Type = 0: This CAN slave is linked to the internal CAN bus of the Core/Core+
- Type = 1: This CAN slave is linked to the first CAN Control
- Type = 2: This CAN slave is linked to the second CAN Control
- ...
- Byte 6: Input Link 0 of the first CAN module of this page
- Byte 7: Input Link 1 of the first CAN module of this page
- Byte 8: Input Link 2 of the first CAN module of this page
- Byte 9: Input Link 3 of the first CAN module of this page
- Byte 10: Input Link 4 of the first CAN module of this page
- Byte 11: Input Link 5 of the first CAN module of this page
- Byte 12: Modbus Address of the Modbus device connected to the uCAN - See Modbus Parameters
- Byte 13: Modbus Type - See Modbus Parameters
- Byte 14: Modbus Model - See Modbus Parameters
- Byte 15: Modbus Speed - See Modbus Parameters
- Byte 16: ID_2 of the second CAN module of this page
- Byte 17: ID_1 of the second CAN module of this page
- Byte 18: ID_0 of the second CAN module of this page
- Byte 19: Sensor Link 0 of the second CAN module of this page
- Byte 20: Sensor Link 1 of the second CAN module of this page
- Byte 21: Module link Type:
- Module link type:
- Type = 0: This CAN slave is linked to the internal CAN bus of the Core/Core+
- Type = 1: This CAN slave is linked to the first CAN Control
- Type = 2: This CAN slave is linked to the second CAN Control
- ...
- Byte 22: Input Link 0 of the second CAN module of this page
- Byte 23: Input Link 1 of the second CAN module of this page
- Byte 24: Input Link 2 of the second CAN module of this page
- Byte 25: Input Link 3 of the second CAN module of this page
- Byte 26: Input Link 4 of the second CAN module of this page
- Byte 27: Input Link 5 of the second CAN module of this page
- Byte 28: Modbus Address of the Modbus device connected to the uCAN - See Modbus Parameters
- Byte 29: Modbus Type - See Modbus Parameters
- Byte 30: Modbus Model - See Modbus Parameters
- Byte 31: Modbus Speed - See Modbus Parameters
- ...
Roller/Shutter (Page 391 - 414)
Link Shutter Nr with Output Nr
Every set of (2 consecutive) outputs can be configured as output or as Roller/Shutter. When configured as Roller/Shutter, those outputs can never be ON at the same time and a time and a delay will be applied between one output going OFF and the other going ON. Every Roller/Shutter has a number that is linked to a set of outputs. The below page will set this link.
- Byte 0: Shutter 0 is linked with Output x*2 and (x*2)+1 (x is the value stored in this byte)
- Byte 1: Shutter 1 is linked with Output x*2 and (x*2)+1 (x is the value stored in this byte)
- Byte 2: Shutter 2 is linked with Output x*2 and (x*2)+1 (x is the value stored in this byte)
- Byte 3: Shutter 3 is linked with Output x*2 and (x*2)+1 (x is the value stored in this byte)
- …
- Byte 254: Shutter 254 is linked with Output x*2 and (x*2)+1 (x is the value stored in this byte)
- Byte 255: Shutter 255 is linked with Output x*2 and (x*2)+1 (x is the value stored in this byte)
Example: When in this Page, 7 is stored in byte 10, Output 14 and 15 are linked to Roller/Shutter nr 10.
Note: The outputs that can be used range from 0 to 511.
Configure Roller/Shutter Outputs
- Byte 0: Roller/Shutter setting for Output Module 0 (and the 8 outputs representing this module)
- Byte 1: Roller/Shutter setting for Output Module 1
- Byte 2: Roller/Shutter setting for Output Module 2
- ...
- Byte 79: Roller/Shutter setting for Output Module 79
Every Roller/shutter setting has following bit representation:
- BIT7: =1-> Output 7 and 6 of this module configured as Output, =0-> Output 7 and 6 configured as Roller/Shutter.
- BIT6: =1-> Output 5 and 4 of this module configured as Output, =0-> Output 5 and 4 configured as Roller/Shutter.
- BIT5: =1-> Output 3 and 2 of this module configured as Output, =0-> Output 3 and 2 configured as Roller/Shutter.
- BIT4: =1-> Output 1 and 0 of this module configured as Output, =0-> Output 1 and 0 configured as Roller/Shutter.
- BIT3: =1-> Output 7 configured as UP, Output 6 configured as DOWN, =0-> Output 6 configured as UP, Output 7 configured as DOWN.
- BIT2: =1-> Output 5 configured as UP, Output 4 configured as DOWN, =0-> Output 4 configured as UP, Output 5 configured as DOWN.
- BIT1: =1-> Output 3 configured as UP, Output 2 configured as DOWN, =0-> Output 2 configured as UP, Output 3 configured as DOWN.
- BIT0: =1-> Output 1 configured as UP, Output 0 configured as DOWN, =0-> Output 0 configured as UP, Output 1 configured as DOWN.
Up Timer settings of an individual Roller/Shutter
- Page 393 Byte 0: Up Timer for Roller/Shutter 0 (LSB)
- Page 393 Byte 1: Up Timer for Roller/Shutter 0 (MSB)
- Page 393 Byte 2: Up Timer for Roller/Shutter 1 (LSB)
- Page 393 Byte 3: Up Timer for Roller/Shutter 1 (MSB)
- …
- Page 394 Byte 254: Up Timer for Roller/Shutter 255 (LSB)
- Page 394 Byte 255: Up Timer for Roller/Shutter 255 (MSB)
Note: This timer setting is in seconds, when 0 the timer is not in use.
Down Timer settings of an individual Roller/Shutter
- Page 395 Byte 0: Down Timer for Roller/Shutter 0 (LSB)
- Page 395 Byte 1: Down Timer for Roller/Shutter 0 (MSB)
- Page 395 Byte 2: Down Timer for Roller/Shutter 1 (LSB)
- Page 395 Byte 3: Down Timer for Roller/Shutter 1 (MSB)
- …
- Page 396 Byte 254: Down Timer for Roller/Shutter 255 (LSB)
- Page 396 Byte 255: Down Timer for Roller/Shutter 255 (MSB)
Note: This timer setting is in seconds, when 0 the timer is not in use.
Name of a Roller/Shutter
Every Roller/Shutter can have a name of max 16 characters.
- Page 395 Byte 0-15: Name of Roller/Shutter 0
- Page 395 Byte 16-31: Name of Roller/Shutter 1
- Page 395 Byte 32-47: Name of Roller/Shutter 2
- …
- Page 410 Byte 240-255: Name of Roller/Shutter 255
Note: This timer setting is in seconds, when 0 the timer is not in use.
Shutter Nr linked to shutter group
Every Shutter can be linked to 16 (0-15) Shutter groups. Every Shutter has an associated shutter group value (word->16 bits). This shutter group value contains 16 bits which represents the 16 existing shutter groups:
- If BIT0=1 -> the shutter is not part of Group 0
- If BIT0=0 -> the shutter is part of Group 0
- If BIT1=1 -> the shutter is not part of Group 1
- If BIT1=0 -> the shutter is part of Group 1
...
- If BIT15=1 -> the shutter is not part of Group 15
- If BIT15=0 -> the shutter is part of Group 15
- Page 413 Byte 0: Shutter Group Value for Roller/Shutter 0 (LSB)
- Page 413 Byte 1: Shutter Group Value for Roller/Shutter 0 (MSB)
- Page 413 Byte 2: Shutter Group Value for Roller/Shutter 1 (LSB)
- Page 413 Byte 3: Shutter Group Value for Roller/Shutter 1 (MSB)
- …
- Page 414 Byte 254: Shutter Group Value for Roller/Shutter 255 (LSB)
- Page 414 Byte 255: Shutter Group Value for Roller/Shutter 255 (MSB)
- Byte 0: Group nr (MSB) to execute when Sensor Extra 0 is changing
- Byte 1: Group nr (LSB) to execute when Sensor Extra 0 is changing
- Byte 2: Group nr (MSB) to execute when Sensor Extra 1 is changing
- Byte 3: Group nr (LSB) to execute when Sensor Extra 1 is changing
- …
- Byte 254: Group nr (MSB) to execute when Sensor Extra 127 is changing
- Byte 255: Group nr (LSB) to execute when Sensor Extra 127 is changing
- Page 472 – 479 -> Contains the Name (16 characters Max) of each extra sensor used. The system can contain maximum 64 sensors that can be freely used. 4 pages are reserved for future use
- Page 476 Byte 0 – 15: ascii name of Validation Bit 0 (16 characters)
- Page 476 Byte 16 – 31: ascii name of Validation Bit 1 (16 characters)
- Page 476 Byte 32 – 47: ascii name of Validation Bit 2 (16 characters)
- ...
- Page 476 Byte 240 – 255: ascii name of Validation Bit 15 (16 characters)
- Page 477 Byte 0 – 15: ascii name of Validation Bit 16 (16 characters)
- ...
Validation Bit (Page 480 - 497)
Validation Bit Group Follow
- Page 480 – 481 -> Contains the Group Nr's (0-254) that needs to be executed when the validation bits (0-255) are changing.
- Page 480 Byte 0: Group nr (MSB) to execute when Validation Bit 0 is changing
- Page 480 Byte 1: Group nr (LSB) to execute when Validation Bit 0 is changing
- Page 480 Byte 2: Group nr (MSB) to execute when Validation Bit 1 is changing
- Page 480 Byte 3: Group nr (LSB) to execute when Validation Bit 1 is changing
- …
- Page 480 Byte 254: Group nr (MSB) to execute when Validation Bit 127 is changing
- Page 480 Byte 255: Group nr (LSB) to execute when Validation Bit 127 is changing
- Page 481 Byte 0: Group nr (MSB) to execute when Validation Bit 128 is changing
- Page 481 Byte 1: Group nr (LSB) to execute when Validation Bit 128 is changing
- ...
Validation Bit Name Page
- Page 482 – 497 -> Contains the Name (16 characters Max) of each Validation Bit (0-255).
- Page 482 Byte 0 – 15: ascii name of Validation Bit 0 (16 characters)
- Page 482 Byte 16 – 31: ascii name of Validation Bit 1 (16 characters)
- Page 482 Byte 32 – 47: ascii name of Validation Bit 2 (16 characters)
- ...
- Page 482 Byte 240 – 255: ascii name of Validation Bit 15 (16 characters)
- Page 483 Byte 0 – 15: ascii name of Validation Bit 16 (16 characters)
- ...
