AIO API Event Codes

From OpenMotics
Jump to navigation Jump to search
Type Action DeviceNr.MSB DeviceNr.LSB Data0 Data1 Data2 Data3 Description
0
0
x.MSB
x.LSB
y
z
u.MSB
u.LSB
Output x off: This Event will be send when an output is switched off with dimmer value y, timer type z and timer value u. See Note 1.
0
1
x.MSB
x.LSB
y
z
u.MSB
u.LSB
Output x on: This Event will be send when an output is switched on with dimmer value y, timer type z and timer value u. See Note 1.
0
2
x.MSB
x.LSB
y
-
-
-
Output x lock/unlock status: This Event will be send when output x is locked/unlock. y=0->Unlock, y=1->Lock
1
0
x.MSB
x.LSB
0
0
0
0
Input x Released: This Event will be send when an input is released.
1
1
x.MSB
x.LSB
0
0
0
0
Input x Pressed: This Event will be send when an input is pressed.
1
2
x.MSB
x.LSB
y
-
-
-
Input x lock/unlock status: This Event will be send when Input x is locked/unlock. y=0->Unlock, y=1->Lock
2
0
0
x
0
y
0
0
Temperature sensor x changed: This Event will be send when Temperature sensor x has changed, new temperature will be found in y
2
1
0
x
0
y
0
0
Humidity sensor x changed: This Event will be send when Humidity sensor x has changed, new humidity will be found in y
2
2
0
x
y.MSB
y.LSB
0
0
Brightness sensor x changed: This Event will be send when Brightness sensor x has changed, new humidity will be found in y
20
0
0
x
Mode
Setpoint
0
0
Thermostat x has changed: The Thermostat setpoint/mode has been modified by the slave device (For example the Modbus thermostat connected to the Micro CAN has an updated value set by the user)
20
0
0
x
Mode
Setpoint
0
0
Thermostat x has changed: The Thermostat setpoint/mode has been modified by the slave device (For example the Modbus thermostat connected to the Micro CAN has an updated value set by the user)
21
0
0
ID2
ID1
ID0
Data0
Data1
uCAN with ID2.ID1.ID0 reports an event with content Data0 and Data1, see Note3.
22
0
BA DeviceNr.MSB
BA DeviceNr.LSB
BA Type
BA Action
BA Extra Parameter.MSB
BA Extra Parameter.LSB
When BB debug mode is ON (see Eeprom Memory model Page 0 Byte 13), this Event will be send to the BB for every BA that has been executed.
249
0
x.MSB
x.LSB
y.MSB
y.LSB
0
z
This event will be send when BA251 is triggered. x, y and z are the parameters received from BA251.
250
0
0
Button_nr
Status
0
0
0
Front Panel Button change: The Frontpanel of the Core has 3 buttons, the Core+ has 4 buttons. When a Button is pressed (short press, longer press), an event will be send. Button_nr: 0->Setup Button, 1->Action Button, 2->CAN Power Button, 3->Select Button. Status: 0->Button released, 1->Button pressed, 2->Button pressed for 5 seconds, 3->Button pressed longer then 8 seconds.
251
Chip_Nr
Led_Blinking_25.MSB
Led_Blinking_25.LSB
Led_Blinking_50.MSB
Led_Blinking_50.LSB
Led_Blinking_75.MSB
Led_Blinking_75.LSB
Front Panel Led state change: When a Led of the Front Panel changes state (from ON to OFF or the reverse), an event message will be send. 2 led driver chips (Chip_nr 0 and 1) are present on the Front panel. The 16 bit Led_blinking_25 will indicate for the 16 leds if the led is blinking at 25% (BIT=1) or not (BIT=0), Led_blinking_50 for 50% and Led_blinking_75 for 75% ON (and thus 25% of the time OFF). See Note 2
252
Chip_Nr
0
0
Led_status.MSB
Led_status.LSB
0
0
Front Panel Led state change: When a Led of the Front Panel changes state (from ON to OFF or the reverse), an event message will be send. 2 led driver chips (Chip_nr 0 and 1) are present on the Front panel. The 16 bit Led_status will indicate for 16 leds if the led is ON (BIT=1) or OFF (BIT=0). See Note 2.
253
0
0
Bus
Power_state
0
0
0
Power state change: When Bus=0 -> RS485 Bus, When Bus=1 -> CAN Bus, when Power_state=0 -> Bus OFF, when Power_state=1 -> Bus ON
254
0
0
0
0
0
0
0
Eeprom activate has just been fully performed and is finished.
254
1
0
0
Onboard_temp
0
0
0
Update of the Onboard Main PCB temperature. Temperature is represented as a signed integer.
254
2
0
0
type
cause
0
0
Reset Action:
  • type=0->Processor reset (or power startup) has just been performed
  • type=1->Health checker is requesting reset in 5 seconds (cause=1->CAN problem)
254
3
0
0
type
current health
previous health
0
This event indicates the health status:
  • Type=0->Change in status "Not all uCAN's are responding"
  • Type=1->Change in status "All uCAN's are not responding"
  • Type=2->Change status "All uCAN's OK"

Current&previous health:

  • BIT0=1: Not all uCAN's are responding
  • BIT1=1: All uCAN's are not responding
  • BIT2=1: All uCAN's OK

Notes:

  • Note 1: timer type specifies which kind of timer is active for a given output and his timer value.
    • timer type=0: No timer is active
    • timer type=1: 100ms timer
    • timer type=2: 1s timer
    • timer type=3: 1m timer
  • Note 2:

Front Panel Led Events

Core Core+ Description
Chip 1 / Led 10
Chip 0 / Led 1
EXP BUS (0)
Chip 1 / Led 8
Chip 0 / Led 3
LED ST GREEN (1)
Chip 1 / Led 9
Chip 0 / Led 2
LED ST RED (2)
Chip 1 / Led 3
Chip 0 / Led 12
LED CAN ST GREEN (3)
Chip 1 / Led 2
Chip 0 / Led 11
LED CAN ST RED (4)
Chip 1 / Led 4
Chip 0 / Led 10
LED CAN COM (5)
Chip 1 / Led 5
Chip 0 / Led 9
LED P1 (6)
Chip 1 / Led 14
Chip 0 / Led 8
LED LAN GREEN (7)
Chip 1 / Led 15
Chip 0 / Led 5
LED LAN RED (8)
Chip 1 / Led 12
Chip 0 / Led 6
LED CLOUD (9)
Chip 1 / Led 11
Chip 0 / Led 7
LED SETUP (10)
NA
Chip 1 / Led 6
LED RELAY 1-8 (11)
NA
Chip 0 / Led 15
LED RELAY 9-16 (12)
NA
Chip 1 / Led 7
LED DIG OUT 1-4 (13)
NA
Chip 0 / Led 13
LED DIG OUT 5-7 (14)
NA
Chip 0 / Led 13
LED DIG ANA 1-4 (15)
NA
Chip 0 / Led 0
LED INPUTS (16)
  1. define LED_RELAYS_1_8 11
  2. define LED_RELAYS_9_16 12
  3. define LED_OUTPUTS_DIG_1_4 13
  4. define LED_OUTPUTS_DIG_5_7 14
  5. define LED_OUTPUTS_ANA_1_4 15
  6. define LED_INPUTS 16