A new version of the package node-red-contrib-vscp-tcp (1.2.2) was published at 2020-08-31T09:20:38.185Z
Fixes problem with transmit of events to VSCP host.
Category: VSCP
Categories
#VSCP turns 20
Today VSCP turns 20. Not a teenager anymore. So many hours. A game of fools. There will be no party. stop.
The initial release (1.0.0) of the VscpTcpClient library is now available. The VscpTcpClient library can be used to communicate with a VSCP remote host in an easy and intuitive way. The library supports all Arduino Ethernet Client compatible hardware (atmelavr,espressif8266,espressif32).
Repository is here: https://github.com/grodansparadis/arduino-vscptcpclient
Documentation is here: https://grodansparadis.github.io/arduino-vscptcpclient
In remote automation setups it can be very inconvenient to use a Raspberry Pi because of the need for a USB power supply. In a current setup of mine I have a bunch of CAN4VSCP boards and want to link them from a remote location to my central system. The Raspberry Pi Zero (W) is low cost, easy to work with and could serve as a good way to accomplish this.
In the official docs the recommendation for powering a Raspberry Pi Zero is 5V at 1.2 A power adapter. This is at first very disappointing for my project as a CAN4VSCP board only can deliver a maximum of one amp from +5V and the board itself takes about 100 mA of this.
But looking further reveals that the needed power is much less that the official requirements if just using WiFi and BT. 120mA is mentioned. Testing this I can verify this value but with some peaks up to 300 mA. Powering a Raspberry Pi Zero W from a CAN4VSCP board would therefore be possible.
I test this with a Vilnius A/D module that is feed with 24V from the CAN4VSCP bus and I experience no problems. The Vilnius A/D module have GND on pin 1 and +5V on pin 12 of the termination block and this can be a good place to get the power for the Raspberry Pi Zero. All 5V CAN4VSCP modules have +5V and GND somewhere on the termination block. Another possible location to get the power from is using the programming header, which also is available on all CAN4VSCP modules. This connector have +5V on pin 2 and GND on pin 3.
To reduce the power need I turn of HDMI on the board as discussed here and here. One can also turn of the LED’s to reduce power consumption even more. There is actually no need for this in my case.
To turnoff HDMI on startup add
@reboot /usr/bin/tvservice -o
to the root crontab job using
sudo crontab -e
This will turn of HDMI on startup. To put the same in /etc/rc.local is another option.
I will use a 3.3V TTL Frankfurt RS-232 module to connect to the CAN bus directly from the Raspberry Pi. Allowing a connection directly from the RX/TX GPIO pins. But more on this later in a separate howto.
I will try to use node-red together with the node-red-contrib-socketcan to connect this module with the main system. I can then choose to connect over MQTT or VSCP tcp/ip, websocket or whatever. It is mostly plug and play to set this up. I will do a separate howto about it to later. My concerns is that there may be a risk that this will be to slow for my needs and in that case I will do a separated link between socketcan and MQTT coded in C. But I will use node-red anyhow so it is still needed.
Installing node-red on a Raspberry Pi system (any Debian derived system) is very easy. Use the script at https://nodered.org/docs/getting-started/raspberrypi which looks like this
bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)and after that everything is installed issue
sudo systemctl enable nodered
and
suso systemctl start nodered
to install node-red as an auto staring service.
Thats it.
A new version of the package node-vscp (1.1.17) was published at 2020-06-10T12:23:44.225Z
In a previous howto (Getting started with node-red-contrib-vscp) we were looking at how to display temperature data from VSCP modules in node-red. In this howto we will look at the same hardware setup but concentrate on output from one module in the setup, the CAN4VSCP Beijing module.
Beijing is a general I/O module which in this setup is used to detect input from three PIR sensors and three magnetic door sensors. The inputs are currently used like this
| 0 | Magnetic door sensor office door. |
| 1 | Magnetic door sensor cellar door. |
| 2 | Magnetic door sensor main entrance door. |
| 3 | Unused. |
| 4 | PIR sensor cellar. |
| 5 | PIR sensor main entrance. |
| 6 | Unused. |
| 7 | PIR sensor inside of office door. |
The Beijing module will send a CLASS1.INFORMATION, Type=ON/OFF event when any of the sensors are activated. The data for the events are defined as follows
| Data byte | Description |
|---|---|
| 0 | index. Often used as an index for channels within a module. |
| 1 | Zone for which event applies to (0-255). 255 is all zones. |
| 2 | Sub-zone for which event applies to (0-255). 255 is all sub-zones. |
The index byte ( byte 0) will this contain the index for the PIR or switch as of above. Zone and subzone is used to indicate the sensors position and here I use bits 7,6,5 of the zone to indicate the floor (1 in this case) and the rest of the bits are set to the room number on that floor (2 in this case). Zone is therefore set to 0b00100010 = 0x22 = 34. Subzones are set to the same as the sensor index. Any schema of your own preference can be used for this. It is entirely up to the user.
The Beijing module is set to nickname id = 1. This is important as we need to filter on this nickname in case more PIR’s/switches are added in the future.
So as an example. If the main door is opened a CLASS1.INFORMATION, Type=ON (3) event will be sent and when it is closed again a CLASS1.INFORMATION, Type=OFF (4) event will be sent. The data will in both cases be
- Byte 0 = 2 for main entrance door.
- Byte 1 = 34, the set zone.
- Byte 2 = 2, subzone for main entrance door.
In our node-red flow we start as in the previous howto with a connection to pi11 the Raspberry Pi that is connected to the Beijing module.
This is a vscp-tcp-in node and it is configured like this
Nothing fancy or strange here.
Without filtering we will get all events on the bus. But we are only interested in the events coming from the Beijing module with nickname = 1. So in the filter above we have decided to set a filter that only let events through from that specific module. This filter is set to the GUID for the interface the Beijing module is located on with the LSB set to the nickname of the Beijing module. Here
FF:FF:FF:FF:FF:FF:FF:FD:C0:A8:01:2C:00:00:00:01
Filter setting is therefore
As a side note the vscpl1drv-can4vscp driver is used (CAN interface is the Frankfurt RS-232 module) and settings for it is
So now we will only get events from the Beijing module.
The next step is to create a flow for CLASS1.INFORMATION, Type=ON and CLASS1.INFORMATION, Type=OFF events like this
Both are VSCP filter nodes set up like this
and this
Just letting through the wanted events (it’s a filter – right).
We feed the output from each of these filters to a switch node
The filter nodes send the sensor index as msg.payload on there outputs. Both switch nodes is configured like this
We could have used a simple function node to handle this also of course. The main thing is that we now get a node-red message on the correct flow channel when a sensor is activated/deactivated. The content of the message is of no importance. We set this in the next step with a change node. We use the node-red-contrib-ui-state-trail to visualize the sensor states in the node-red UI.
Each of the change nodes just set the msg.payload to true or false to suite the UI node-red-contrib-ui-state-trail expected input. Like this (in the set to true case)
For the ui-state-trail nodes they are more or less configured the same, something like this
There are other possibilities here of course. But with settings like this the end result looks like this
You see current state of a sensor and get a 24 hour state trail. The front door is open here today as it is summer outside even here in the middle of Sweden.
There is one problem with this, and that is that we don’t have a state for a sensor before something actually happens at the sensor, that is if it detects movement or a door is opened/closed. This may be important or not for a specific setup.
Luckily the Beijing module also can be configured to send out i/o states with a preset interval. This ability solves this problem. The event used by Beijing for this is CLASS1.DATA Type=1 I/O which has it’s data content specified as
| 0 | Data coding. |
| 1-7 | Data with format defined by byte 0. |
For the Beijing module this is three bytes. The first byte, the VSCP data coding byte is set to zero. This says that the two bytes that follows is defined as bits and unit=0, sensorindex=0. The first of the two bytes holds output states and the second hold input states. This flow looks like this
First we filter out the CLASS1.DATA, Type=1 I/O events. Then we check which inputs are set and send true/false to the correct ui-state-trail node. The function node is simple and coded like this
// CLASS1.DATA, Type=1, I/O
// vscpData[0] - Datacoding
// vscpData[1] - Output states
// vscpData[2] - Input states
var msgarray = [
{ "payload": false },
{ "payload": false },
{ "payload": false },
{ "payload": false },
{ "payload": false },
{ "payload": false },
{ "payload": false },
{ "payload": false }
];
for ( i=0;i<8;i++) {
if ( msg.payload.vscpData[2] & (Math.pow(2,i)) ) {
msgarray[i].payload = true;
}
}
return msgarray;
The function node has eight outputs. Each is feed to the correct ui-state-trail node. Thats it.
With this in place we can now add alarms and control of automatic lights without much extra effort. You should also notice that even if we here use the CAN4VSCP module Beijing we could have used a mix of other techniques to receive the same result and functionality. If we at some point want to replace one of the PIR sensors with a Bluetooth or Zigbee solution we just need to code that sensor output as a VSCP event and everything will work as expected. The VSCP protocol is the abstraction that unite them all. Protocols and transfer techniques.
For reference is the node red flow and the Beijing module configuration listed below.
Have fun!
/Ake
Node-red flow for howto
[{"id":"82af1478.db09a8","type":"ui_statetrail","z":"d55b6e63.6443a8","group":"86ca358f.1ef4f8","order":6,"width":"12","height":"2","name":"Office door state","label":"Office door state","states":[{"state":true,"col":"#009933","t":"bool","label":"Open"},{"state":false,"col":"#999999","t":"bool","label":"Closed"}],"periodLimit":"24","periodLimitUnit":"3600","timeformat":"HH:mm","tickmarks":4,"persist":false,"legend":"3","combine":true,"blanklabel":"","x":1120,"y":860,"wires":[[]]},{"id":"433ab88d.14a528","type":"vscpfilter","z":"d55b6e63.6443a8","vscppriority":"","vscpclass":"20","vscptype":"3","vscpguid":"","name":"CLASS1.INFORMATION, ON","x":200,"y":1000,"wires":[["e7c014db.d982f8"]]},{"id":"dba27e7e.901248","type":"vscpfilter","z":"d55b6e63.6443a8","vscppriority":"","vscpclass":"20","vscptype":"4","vscpguid":"","name":"CLASS1.INFORMATION, OFF","x":210,"y":1100,"wires":[["62cdb0fe.3fad38"]]},{"id":"e7c014db.d982f8","type":"switch","z":"d55b6e63.6443a8","name":"","property":"payload.vscpData[0]","propertyType":"msg","rules":[{"t":"eq","v":"0","vt":"num"},{"t":"eq","v":"1","vt":"num"},{"t":"eq","v":"2","vt":"num"},{"t":"eq","v":"3","vt":"num"},{"t":"eq","v":"4","vt":"num"},{"t":"eq","v":"5","vt":"num"},{"t":"eq","v":"6","vt":"num"},{"t":"eq","v":"7","vt":"num"}],"checkall":"true","repair":false,"outputs":8,"x":430,"y":1000,"wires":[["6a7f782a.68e4f"],["8354a8b7.540938"],["59434168.7bf8f"],["8f7c7c69.bf4ee"],["1ba6d376.51f02d"],["3d18e2c3.e0faee"],["23a97f1c.51cf"],["32f01e41.9a4f92"]]},{"id":"6a7f782a.68e4f","type":"change","z":"d55b6e63.6443a8","name":"office=true","rules":[{"t":"set","p":"payload","pt":"msg","to":"true","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":670,"y":860,"wires":[["82af1478.db09a8"]]},{"id":"95de756f.fc4cf","type":"ui_statetrail","z":"d55b6e63.6443a8","group":"86ca358f.1ef4f8","order":6,"width":"12","height":"2","name":"Cellar Door State","label":"Cellar Door State","states":[{"state":true,"col":"#009933","t":"bool","label":"Open"},{"state":false,"col":"#999999","t":"bool","label":"Closed"}],"periodLimit":"24","periodLimitUnit":"3600","timeformat":"HH:mm","tickmarks":4,"persist":false,"legend":"3","combine":true,"blanklabel":"","x":1130,"y":900,"wires":[[]]},{"id":"8354a8b7.540938","type":"change","z":"d55b6e63.6443a8","name":"Cellar=true","rules":[{"t":"set","p":"payload","pt":"msg","to":"true","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":670,"y":900,"wires":[["95de756f.fc4cf"]]},{"id":"f7dc6e17.85bd28","type":"ui_statetrail","z":"d55b6e63.6443a8","group":"86ca358f.1ef4f8","order":6,"width":"12","height":"2","name":"Front door state","label":"Front Door state","states":[{"state":true,"col":"#009933","t":"bool","label":"Open"},{"state":false,"col":"#999999","t":"bool","label":"Closed"}],"periodLimit":"24","periodLimitUnit":"3600","timeformat":"HH:mm","tickmarks":4,"persist":false,"legend":"3","combine":true,"blanklabel":"","x":1120,"y":940,"wires":[[]]},{"id":"59434168.7bf8f","type":"change","z":"d55b6e63.6443a8","name":"front=true","rules":[{"t":"set","p":"payload","pt":"msg","to":"true","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":660,"y":940,"wires":[["f7dc6e17.85bd28"]]},{"id":"1dadefe2.73b87","type":"ui_statetrail","z":"d55b6e63.6443a8","d":true,"group":"86ca358f.1ef4f8","order":6,"width":"12","height":"2","name":"Unuse","label":"Unused","states":[{"state":true,"col":"#009933","t":"bool","label":""},{"state":false,"col":"#999999","t":"bool","label":""}],"periodLimit":"24","periodLimitUnit":"3600","timeformat":"HH:mm","tickmarks":4,"persist":false,"legend":"3","combine":false,"blanklabel":"","x":1090,"y":980,"wires":[[]]},{"id":"8f7c7c69.bf4ee","type":"change","z":"d55b6e63.6443a8","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"true","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":680,"y":980,"wires":[["1dadefe2.73b87"]]},{"id":"6162e7b8.cc655","type":"ui_statetrail","z":"d55b6e63.6443a8","group":"86ca358f.1ef4f8","order":6,"width":"12","height":"2","name":"PIR Cellar","label":"PIR Cellar","states":[{"state":true,"col":"#009933","t":"bool","label":"Detect"},{"state":false,"col":"#999999","t":"bool","label":"Rest"}],"periodLimit":"24","periodLimitUnit":"3600","timeformat":"HH:mm","tickmarks":4,"persist":false,"legend":"3","combine":true,"blanklabel":"","x":1110,"y":1020,"wires":[[]]},{"id":"1ba6d376.51f02d","type":"change","z":"d55b6e63.6443a8","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"true","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":680,"y":1020,"wires":[["6162e7b8.cc655"]]},{"id":"159222d2.262acd","type":"ui_statetrail","z":"d55b6e63.6443a8","group":"86ca358f.1ef4f8","order":6,"width":"12","height":"2","name":"PIR Main entrance","label":"PIR Main entrance","states":[{"state":true,"col":"#009933","t":"bool","label":"Detetc"},{"state":false,"col":"#999999","t":"bool","label":"Rest"}],"periodLimit":"24","periodLimitUnit":"3600","timeformat":"HH:mm","tickmarks":4,"persist":false,"legend":"3","combine":true,"blanklabel":"","x":1130,"y":1060,"wires":[[]]},{"id":"3d18e2c3.e0faee","type":"change","z":"d55b6e63.6443a8","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"true","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":680,"y":1060,"wires":[["159222d2.262acd"]]},{"id":"bfc9343a.c2fde8","type":"ui_statetrail","z":"d55b6e63.6443a8","d":true,"group":"86ca358f.1ef4f8","order":6,"width":"12","height":"2","name":"Unused","label":"Unused","states":[{"state":true,"col":"#009933","t":"bool","label":""},{"state":false,"col":"#999999","t":"bool","label":""}],"periodLimit":"24","periodLimitUnit":"3600","timeformat":"mm","tickmarks":4,"persist":false,"legend":"3","combine":true,"blanklabel":"","x":1100,"y":1100,"wires":[[]]},{"id":"23a97f1c.51cf","type":"change","z":"d55b6e63.6443a8","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"true","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":680,"y":1100,"wires":[["bfc9343a.c2fde8"]]},{"id":"f2f76475.1e32a","type":"ui_statetrail","z":"d55b6e63.6443a8","group":"86ca358f.1ef4f8","order":6,"width":"12","height":"2","name":"PIR Office Door","label":"PIR Office Door","states":[{"state":true,"col":"#fe0000","t":"bool","label":"Open"},{"state":false,"col":"#999999","t":"bool","label":"Closed"}],"periodLimit":"24","periodLimitUnit":"3600","timeformat":"HH:mm","tickmarks":4,"persist":false,"legend":"3","combine":true,"blanklabel":"","x":1120,"y":1140,"wires":[[]]},{"id":"32f01e41.9a4f92","type":"change","z":"d55b6e63.6443a8","name":"PIR Office = true","rules":[{"t":"set","p":"payload","pt":"msg","to":"true","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":690,"y":1140,"wires":[["f2f76475.1e32a"]]},{"id":"62cdb0fe.3fad38","type":"switch","z":"d55b6e63.6443a8","name":"","property":"payload.vscpData[0]","propertyType":"msg","rules":[{"t":"eq","v":"0","vt":"num"},{"t":"eq","v":"1","vt":"num"},{"t":"eq","v":"2","vt":"num"},{"t":"eq","v":"3","vt":"num"},{"t":"eq","v":"4","vt":"num"},{"t":"eq","v":"5","vt":"num"},{"t":"eq","v":"6","vt":"num"},{"t":"eq","v":"7","vt":"num"}],"checkall":"true","repair":false,"outputs":8,"x":430,"y":1360,"wires":[["c625622d.26fd08"],["e3c1ac7f.8d3a1"],["4648539f.147a04"],["a363d163.6b4ec8"],["8c44a2c4.ed5de8"],["99117390.c4adb8"],["ee2b8418.ba485"],["2a250160.c423b6"]]},{"id":"c625622d.26fd08","type":"change","z":"d55b6e63.6443a8","name":"office=false","rules":[{"t":"set","p":"payload","pt":"msg","to":"false","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":670,"y":1220,"wires":[["82af1478.db09a8"]]},{"id":"e3c1ac7f.8d3a1","type":"change","z":"d55b6e63.6443a8","name":"Cellar=false","rules":[{"t":"set","p":"payload","pt":"msg","to":"false","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":670,"y":1260,"wires":[["95de756f.fc4cf"]]},{"id":"4648539f.147a04","type":"change","z":"d55b6e63.6443a8","name":"front=false","rules":[{"t":"set","p":"payload","pt":"msg","to":"false","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":670,"y":1300,"wires":[["f7dc6e17.85bd28"]]},{"id":"a363d163.6b4ec8","type":"change","z":"d55b6e63.6443a8","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"false","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":680,"y":1340,"wires":[["1dadefe2.73b87"]]},{"id":"8c44a2c4.ed5de8","type":"change","z":"d55b6e63.6443a8","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"false","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":680,"y":1380,"wires":[["6162e7b8.cc655"]]},{"id":"99117390.c4adb8","type":"change","z":"d55b6e63.6443a8","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"false","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":680,"y":1420,"wires":[["159222d2.262acd"]]},{"id":"ee2b8418.ba485","type":"change","z":"d55b6e63.6443a8","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"false","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":680,"y":1460,"wires":[["bfc9343a.c2fde8"]]},{"id":"2a250160.c423b6","type":"change","z":"d55b6e63.6443a8","name":"PIR Office = false","rules":[{"t":"set","p":"payload","pt":"msg","to":"false","tot":"bool"}],"action":"","property":"","from":"","to":"","reg":false,"x":690,"y":1500,"wires":[["f2f76475.1e32a"]]},{"id":"8d3f89ae.3e49d8","type":"vscp-tcp-in","z":"d55b6e63.6443a8","name":"pi11","host":"e596ab59.2b98c8","username":"admin","password":"__PWRD__","filter":"3f11c8c2.e2dcd","keyctx":"pi11a","x":70,"y":860,"wires":[["433ab88d.14a528","dba27e7e.901248","14d7cd7f.7e456b"]]},{"id":"14d7cd7f.7e456b","type":"vscpfilter","z":"d55b6e63.6443a8","vscppriority":"","vscpclass":"15","vscptype":"1","vscpguid":"","name":"CLASS1.DATA, I/O","x":170,"y":1740,"wires":[["e712b13e.7d21a8"]]},{"id":"e712b13e.7d21a8","type":"function","z":"d55b6e63.6443a8","name":"Check input states","func":"\n// CLASS1.DATA, Type=1, I/O\n// vscpData[0] - Datacoding\n// vscpData[1] - Output states\n// vscpData[2] - Input states\n\nvar msgarray = [\n { \"payload\": false },\n { \"payload\": false },\n { \"payload\": false },\n { \"payload\": false },\n { \"payload\": false },\n { \"payload\": false },\n { \"payload\": false },\n { \"payload\": false }\n];\n\nfor ( i=0;i<8;i++) {\n if ( msg.payload.vscpData[2] & (Math.pow(2,i)) ) {\n msgarray[i].payload = true;\n }\n}\nreturn msgarray;","outputs":8,"noerr":0,"x":690,"y":1740,"wires":[["82af1478.db09a8"],["95de756f.fc4cf"],["f7dc6e17.85bd28"],["1dadefe2.73b87"],["6162e7b8.cc655"],["159222d2.262acd"],["bfc9343a.c2fde8"],["f2f76475.1e32a"]]},{"id":"86ca358f.1ef4f8","type":"ui_group","z":"","name":"States","tab":"7cdacae9.143d2c","order":3,"disp":true,"width":"12","collapse":false},{"id":"e596ab59.2b98c8","type":"vscp-tcp-config-host","z":"","name":"pi11","host":"192.168.1.44","port":"9598","timeout":"10000","interface":"","keepalive":"10000"},{"id":"3f11c8c2.e2dcd","type":"vscp-tcp-config-filter","z":"","name":"Only events from Beijing","filterPriority":"0","maskPriority":"0","filterClass":"0","maskClass":"0","filterType":"0","maskType":"0","filterGuid":"FF:FF:FF:FF:FF:FF:FF:FD:C0:A8:01:2C:11:22:00:01","maskGuid":"FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF"},{"id":"7cdacae9.143d2c","type":"ui_tab","z":"","name":"Home","icon":"dashboard","disabled":false,"hidden":false}]
Beijing module configuration
Can be loaded with VSCP works.
<?xml version = "1.0" encoding = "UTF-8" ?>
<registerset>
<register offset='0' page='0'>
<value>0x00</value>
<description>Zone
Zone this module belongs to</description>
</register>
<register offset='1' page='0'>
<value>0x00</value>
<description>Sub zone
Sub zone this module belongs to</description>
</register>
<register offset='2' page='0'>
<value>0x00</value>
<description>Sub zone I/O 0
Sub zone for I/O channel 0</description>
</register>
<register offset='3' page='0'>
<value>0x01</value>
<description>Sub zone I/O 1
Sub zone for I/O channel 1</description>
</register>
<register offset='4' page='0'>
<value>0x02</value>
<description>Sub zone I/O 2
Sub zone for I/O channel 2</description>
</register>
<register offset='5' page='0'>
<value>0x03</value>
<description>Sub zone I/O 3
Sub zone for I/O channel 3</description>
</register>
<register offset='6' page='0'>
<value>0x04</value>
<description>Sub zone I/O 4
Sub zone for I/O channel 4</description>
</register>
<register offset='7' page='0'>
<value>0x05</value>
<description>Sub zone I/O 5
Sub zone for I/O channel 5</description>
</register>
<register offset='8' page='0'>
<value>0x06</value>
<description>Sub zone I/O 6
Sub zone for I/O channel 6</description>
</register>
<register offset='9' page='0'>
<value>0x07</value>
<description>Sub zone I/O 7
Sub zone for I/O channel 7</description>
</register>
<register offset='10' page='0'>
<value>0x08</value>
<description>Sub zone I/O 8
Sub zone for I/O channel 8</description>
</register>
<register offset='11' page='0'>
<value>0x09</value>
<description>Sub zone I/O 9
Sub zone for I/O channel 9</description>
</register>
<register offset='12' page='0'>
<value>0x00</value>
<description>I/O direction MSB
Most significant part of I/O directions register. Set bit to zero for output and
one for input.
Bit 7 - Reserved.
Bit 6 - Reserved.
Bit 5 - Reserved.
Bit 4 - Reserved.
Bit 3 - Reserved.
Bit 2 - Reserved.
Bit 1 - Direction for I/O channel 9 - (RA0). 0=output. 1=input.
Bit 0 - Direction for I/O channel 8 - (RA1). 0=output. 1=input.
</description>
</register>
<register offset='13' page='0'>
<value>0x00</value>
<description>I/O direction LSB
Least significant part of I/O directions register.Set bit to zero for output and
one for input.
Bit 7 - Direction for I/O channel 7 - (RA2). 0=output. 1=input.
Bit 6 - Direction for I/O channel 6 - (RC7). 0=output. 1=input.
Bit 5 - Direction for I/O channel 5 - (RC6). 0=output. 1=input.
Bit 4 - Direction for I/O channel 4 - (RC5). 0=output. 1=input.
Bit 3 - Direction for I/O channel 3 - (RC4). 0=output. 1=input.
Bit 2 - Direction for I/O channel 2 - (RC3). 0=output. 1=input.
Bit 1 - Direction for I/O channel 1 - (RB1). 0=output. 1=input.
Bit 0 - Direction for I/O channel 0 - (RB0). 0=output. 1=input.
</description>
</register>
<register offset='14' page='0'>
<value>0x00</value>
<description>I/O channel 0 status register
Read or write the state of I/O channel 0 in this register.
0 - is returned for an inactive input or a low output. A written zero will set an
output channel low.
1 - is returned for an active input or a high output. A written one will set an
output channel high.
</description>
</register>
<register offset='15' page='0'>
<value>0x00</value>
<description>I/O channel 1 status register
Read or write the state of I/O channel 0 in this register.
0 - is returned for an inactive input or a low output. A written zero will set an
output channel low.
1 - is returned for an active input or a high output. A written one will set an
output channel high.
</description>
</register>
<register offset='16' page='0'>
<value>0x00</value>
<description>I/O channel 2 status register
Read or write the state of I/O channel 0 in this register.
0 - is returned for an inactive input or a low output. A written zero will set an
output channel low.
1 - is returned for an active input or a high output. A written one will set an
output channel high.
</description>
</register>
<register offset='17' page='0'>
<value>0x00</value>
<description>I/O channel 3 status register
Read or write the state of I/O channel 0 in this register.
0 - is returned for an inactive input or a low output. A written zero will set an
output channel low.
1 - is returned for an active input or a high output. A written one will set an
output channel high.
</description>
</register>
<register offset='18' page='0'>
<value>0x00</value>
<description>I/O channel 4 status register
Read or write the state of I/O channel 0 in this register.
0 - is returned for an inactive input or a low output. A written zero will set an
output channel low.
1 - is returned for an active input or a high output. A written one will set an
output channel high.
</description>
</register>
<register offset='19' page='0'>
<value>0x00</value>
<description>I/O channel 5 status register
Read or write the state of I/O channel 0 in this register.
0 - is returned for an inactive input or a low output. A written zero will set an
output channel low.
1 - is returned for an active input or a high output. A written one will set an
output channel high.
</description>
</register>
<register offset='20' page='0'>
<value>0x00</value>
<description>I/O channel 6 status register
Read or write the state of I/O channel 0 in this register.
0 - is returned for an inactive input or a low output. A written zero will set an
output channel low.
1 - is returned for an active input or a high output. A written one will set an
output channel high.
</description>
</register>
<register offset='21' page='0'>
<value>0x00</value>
<description>I/O channel 7 status register
Read or write the state of I/O channel 0 in this register.
0 - is returned for an inactive input or a low output. A written zero will set an
output channel low.
1 - is returned for an active input or a high output. A written one will set an
output channel high.
</description>
</register>
<register offset='22' page='0'>
<value>0x00</value>
<description>I/O channel 8 status register
Read or write the state of I/O channel 0 in this register.
0 - is returned for an inactive input or a low output. A written zero will set an
output channel low.
1 - is returned for an active input or a high output. A written one will set an
output channel high.
</description>
</register>
<register offset='23' page='0'>
<value>0x00</value>
<description>I/O channel 9 status register
Read or write the state of I/O channel 0 in this register.
0 - is returned for an inactive input or a low output. A written zero will set an
output channel low.
1 - is returned for an active input or a high output. A written one will set an
output channel high.
</description>
</register>
<register offset='24' page='0'>
<value>0x98</value>
<description>Output 0 control register
The output control bits enable/disable intelligent functionality for a channel set
as output.
Bit 0 - Enable pulse.
Bit 1 - If set: Alarm sent when protection timer triggers.
Bit 2 - Protection timer enable.
Bit 3 - Send On event when output goes to active state.
Bit 4 - Send Off event when output goes to inactive state.
Bit 5 - Reserved.
Bit 6 - Reserved.
Bit 7 - Enable output.
</description>
</register>
<register offset='25' page='0'>
<value>0x98</value>
<description>Output 1 control register
The output control bits enable/disable intelligent functionality for a channel set
as output.
Bit 0 - Enable pulse.
Bit 1 - If set: Alarm sent when protection timer triggers.
Bit 2 - Protection timer enable.
Bit 3 - Send On event when output goes to active state.
Bit 4 - Send Off event when output goes to inactive state.
Bit 5 - Reserved.
Bit 6 - Reserved.
Bit 7 - Enable output.
</description>
</register>
<register offset='26' page='0'>
<value>0x98</value>
<description>Output 2 control register
The output control bits enable/disable intelligent functionality for a channel set
as output.
Bit 0 - Enable pulse.
Bit 1 - If set: Alarm sent when protection timer triggers.
Bit 2 - Protection timer enable.
Bit 3 - Send On event when output goes to active state.
Bit 4 - Send Off event when output goes to inactive state.
Bit 5 - Reserved.
Bit 6 - Reserved.
Bit 7 - Enable output.
</description>
</register>
<register offset='27' page='0'>
<value>0x98</value>
<description>Output 3 control register
The output control bits enable/disable intelligent functionality for a channel set
as output.
Bit 0 - Enable pulse.
Bit 1 - If set: Alarm sent when protection timer triggers.
Bit 2 - Protection timer enable.
Bit 3 - Send On event when output goes to active state.
Bit 4 - Send Off event when output goes to inactive state.
Bit 5 - Reserved.
Bit 6 - Reserved.
Bit 7 - Enable output.
</description>
</register>
<register offset='28' page='0'>
<value>0x98</value>
<description>Output 4 control register
The output control bits enable/disable intelligent functionality for a channel set
as output.
Bit 0 - Enable pulse.
Bit 1 - If set: Alarm sent when protection timer triggers.
Bit 2 - Protection timer enable.
Bit 3 - Send On event when output goes to active state.
Bit 4 - Send Off event when output goes to inactive state.
Bit 5 - Reserved.
Bit 6 - Reserved.
Bit 7 - Enable output.
</description>
</register>
<register offset='29' page='0'>
<value>0x98</value>
<description>Output 5 control register
The output control bits enable/disable intelligent functionality for a channel set
as output.
Bit 0 - Enable pulse.
Bit 1 - If set: Alarm sent when protection timer triggers.
Bit 2 - Protection timer enable.
Bit 3 - Send On event when output goes to active state.
Bit 4 - Send Off event when output goes to inactive state.
Bit 5 - Reserved.
Bit 6 - Reserved.
Bit 7 - Enable output.
</description>
</register>
<register offset='30' page='0'>
<value>0x98</value>
<description>Output 6 control register
The output control bits enable/disable intelligent functionality for a channel set
as output.
Bit 0 - Enable pulse.
Bit 1 - If set: Alarm sent when protection timer triggers.
Bit 2 - Protection timer enable.
Bit 3 - Send On event when output goes to active state.
Bit 4 - Send Off event when output goes to inactive state.
Bit 5 - Reserved.
Bit 6 - Reserved.
Bit 7 - Enable output.
</description>
</register>
<register offset='31' page='0'>
<value>0x98</value>
<description>Output 7 control register
The output control bits enable/disable intelligent functionality for a channel set
as output.
Bit 0 - Enable pulse.
Bit 1 - If set: Alarm sent when protection timer triggers.
Bit 2 - Protection timer enable.
Bit 3 - Send On event when output goes to active state.
Bit 4 - Send Off event when output goes to inactive state.
Bit 5 - Reserved.
Bit 6 - Reserved.
Bit 7 - Enable output.
</description>
</register>
<register offset='32' page='0'>
<value>0x98</value>
<description>Output 8 control register
The output control bits enable/disable intelligent functionality for a channel set
as output.
Bit 0 - Enable pulse.
Bit 1 - If set: Alarm sent when protection timer triggers.
Bit 2 - Protection timer enable.
Bit 3 - Send On event when output goes to active state.
Bit 4 - Send Off event when output goes to inactive state.
Bit 5 - Reserved.
Bit 6 - Reserved.
Bit 7 - Enable output.
</description>
</register>
<register offset='33' page='0'>
<value>0x98</value>
<description>Output 9 control register
The output control bits enable/disable intelligent functionality for a channel set
as output.
Bit 0 - Enable pulse.
Bit 1 - If set: Alarm sent when protection timer triggers.
Bit 2 - Protection timer enable.
Bit 3 - Send On event when output goes to active state.
Bit 4 - Send Off event when output goes to inactive state.
Bit 5 - Reserved.
Bit 6 - Reserved.
Bit 7 - Enable output.
</description>
</register>
<register offset='34' page='0'>
<value>0x83</value>
<description>Input 0 control register
The input control bits enable/disable intelligent functionality for a channel set
as input.
Bit 0 - Send On/TurnOn event when input goes to active state.
Bit 1 - Send Off/TurnOff event when input goes to inactive state.
Bit 2 - 0 = Send On/off events. 1=Send turnon/turnoff events (if activated).
Different meaning in button input mode where 0 = TurnOn and 1 = TurnOff.
Bit 3 - Alarm event sent if input goes low.
Bit 4 - Alarm event sent if input goes high.
Bit 5 - Continuous alarm.
Bit 6 - Activate Button imput mode. Only TurnOff or TurnOn is sent when an input
goes low and button input mode is activated.
Bit 7 - Enable input.
</description>
</register>
<register offset='35' page='0'>
<value>0x83</value>
<description>Input 1 control register
The input control bits enable/disable intelligent functionality for a channel set
as input.
Bit 0 - Send On/TurnOn event when input goes to active state.
Bit 1 - Send Off/TurnOff event when input goes to inactive state.
Bit 2 - 0 = Send On/off events. 1=Send turnon/turnoff events (if activated).
Different meaning in button input mode where 0 = TurnOn and 1 = TurnOff.
Bit 3 - Alarm event sent if input goes low.
Bit 4 - Alarm event sent if input goes high.
Bit 5 - Continuous alarm.
Bit 6 - Activate Button imput mode. Only TurnOff or TurnOn is sent when an input
goes low and button input mode is activated.
Bit 7 - Enable input.
</description>
</register>
<register offset='36' page='0'>
<value>0x83</value>
<description>Input 2 control register
The input control bits enable/disable intelligent functionality for a channel set
as input.
Bit 0 - Send On/TurnOn event when input goes to active state.
Bit 1 - Send Off/TurnOff event when input goes to inactive state.
Bit 2 - 0 = Send On/off events. 1=Send turnon/turnoff events (if activated).
Different meaning in button input mode where 0 = TurnOn and 1 = TurnOff.
Bit 3 - Alarm event sent if input goes low.
Bit 4 - Alarm event sent if input goes high.
Bit 5 - Continuous alarm.
Bit 6 - Activate Button imput mode. Only TurnOff or TurnOn is sent when an input
goes low and button input mode is activated.
Bit 7 - Enable input.
</description>
</register>
<register offset='37' page='0'>
<value>0x83</value>
<description>Input 3 control register
The input control bits enable/disable intelligent functionality for a channel set
as input.
Bit 0 - Send On/TurnOn event when input goes to active state.
Bit 1 - Send Off/TurnOff event when input goes to inactive state.
Bit 2 - 0 = Send On/off events. 1=Send turnon/turnoff events (if activated).
Different meaning in button input mode where 0 = TurnOn and 1 = TurnOff.
Bit 3 - Alarm event sent if input goes low.
Bit 4 - Alarm event sent if input goes high.
Bit 5 - Continuous alarm.
Bit 6 - Activate Button imput mode. Only TurnOff or TurnOn is sent when an input
goes low and button input mode is activated.
Bit 7 - Enable input.
</description>
</register>
<register offset='38' page='0'>
<value>0x83</value>
<description>Input 4 control register
The input control bits enable/disable intelligent functionality for a channel set
as input.
Bit 0 - Send On/TurnOn event when input goes to active state.
Bit 1 - Send Off/TurnOff event when input goes to inactive state.
Bit 2 - 0 = Send On/off events. 1=Send turnon/turnoff events (if activated).
Different meaning in button input mode where 0 = TurnOn and 1 = TurnOff.
Bit 3 - Alarm event sent if input goes low.
Bit 4 - Alarm event sent if input goes high.
Bit 5 - Continuous alarm.
Bit 6 - Activate Button imput mode. Only TurnOff or TurnOn is sent when an input
goes low and button input mode is activated.
Bit 7 - Enable input.
</description>
</register>
<register offset='39' page='0'>
<value>0x83</value>
<description>Input 5 control register
The input control bits enable/disable intelligent functionality for a channel set
as input.
Bit 0 - Send On/TurnOn event when input goes to active state.
Bit 1 - Send Off/TurnOff event when input goes to inactive state.
Bit 2 - 0 = Send On/off events. 1=Send turnon/turnoff events (if activated).
Different meaning in button input mode where 0 = TurnOn and 1 = TurnOff.
Bit 3 - Alarm event sent if input goes low.
Bit 4 - Alarm event sent if input goes high.
Bit 5 - Continuous alarm.
Bit 6 - Activate Button imput mode. Only TurnOff or TurnOn is sent when an input
goes low and button input mode is activated.
Bit 7 - Enable input.
</description>
</register>
<register offset='40' page='0'>
<value>0x83</value>
<description>Input 6 control register
The input control bits enable/disable intelligent functionality for a channel set
as input.
Bit 0 - Send On/TurnOn event when input goes to active state.
Bit 1 - Send Off/TurnOff event when input goes to inactive state.
Bit 2 - 0 = Send On/off events. 1=Send turnon/turnoff events (if activated).
Different meaning in button input mode where 0 = TurnOn and 1 = TurnOff.
Bit 3 - Alarm event sent if input goes low.
Bit 4 - Alarm event sent if input goes high.
Bit 5 - Continuous alarm.
Bit 6 - Activate Button imput mode. Only TurnOff or TurnOn is sent when an input
goes low and button input mode is activated.
Bit 7 - Enable input.
</description>
</register>
<register offset='41' page='0'>
<value>0x83</value>
<description>Input 7 control register
The input control bits enable/disable intelligent functionality for a channel set
as input.
Bit 0 - Send On/TurnOn event when input goes to active state.
Bit 1 - Send Off/TurnOff event when input goes to inactive state.
Bit 2 - 0 = Send On/off events. 1=Send turnon/turnoff events (if activated).
Different meaning in button input mode where 0 = TurnOn and 1 = TurnOff.
Bit 3 - Alarm event sent if input goes low.
Bit 4 - Alarm event sent if input goes high.
Bit 5 - Continuous alarm.
Bit 6 - Activate Button imput mode. Only TurnOff or TurnOn is sent when an input
goes low and button input mode is activated.
Bit 7 - Enable input.
</description>
</register>
<register offset='42' page='0'>
<value>0x83</value>
<description>Input 8 control register
The input control bits enable/disable intelligent functionality for a channel set
as input.
Bit 0 - Send On/TurnOn event when input goes to active state.
Bit 1 - Send Off/TurnOff event when input goes to inactive state.
Bit 2 - 0 = Send On/off events. 1=Send turnon/turnoff events (if activated).
Different meaning in button input mode where 0 = TurnOn and 1 = TurnOff.
Bit 3 - Alarm event sent if input goes low.
Bit 4 - Alarm event sent if input goes high.
Bit 5 - Continuous alarm.
Bit 6 - Activate Button imput mode. Only TurnOff or TurnOn is sent when an input
goes low and button input mode is activated.
Bit 7 - Enable input.
</description>
</register>
<register offset='43' page='0'>
<value>0x83</value>
<description>Input 9 control register
The input control bits enable/disable intelligent functionality for a channel set
as input.
Bit 0 - Send On/TurnOn event when input goes to active state.
Bit 1 - Send Off/TurnOff event when input goes to inactive state.
Bit 2 - 0 = Send On/off events. 1=Send turnon/turnoff events (if activated).
Different meaning in button input mode where 0 = TurnOn and 1 = TurnOff.
Bit 3 - Alarm event sent if input goes low.
Bit 4 - Alarm event sent if input goes high.
Bit 5 - Continuous alarm.
Bit 6 - Activate Button imput mode. Only TurnOff or TurnOn is sent when an input
goes low and button input mode is activated.
Bit 7 - Enable input.
</description>
</register>
<register offset='44' page='0'>
<value>0x00</value>
<description>Module Control register
It is possible to control general module behaviour in this register.
Bit 0 - Turn of input event repeat.
Bit 1 - Reserved.
Bit 2 - Reserved.
Bit 3 - Reserved.
Bit 4 - Reserved.
Bit 5 - Reserved.
Bit 6 - Reserved.
Bit 7 - Enable weak pullups.
</description>
</register>
<register offset='45' page='0'>
<value>0x00</value>
<description>Input stream sample time
This is the time in seconds between input stream samples. Set to zero to disable.
CLASS1.DATA is sent with data coding=0(bits), unit=0, sensor=0 for the inputs/outputs
as set here. First byte is outputs, second byte is inputs. </description>
</register>
<register offset='46' page='0'>
<value>0x03</value>
<description>Debounce count
This is the number of counts a button input signal should be low to be regarded as
actice. Each count represents 10 ms. </description>
</register>
<register offset='47' page='0'>
<value>0x02</value>
<description>Short pulse duration
This is the duration for the short pulse action. Each count represents 10 ms. A
zero vaue gives a pulse that is the shortest possible. </description>
</register>
<register offset='0' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 0 MSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='1' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 0 LSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='2' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 1 MSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='3' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 1 LSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='4' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 2 MSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='5' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 2 LSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='6' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 3 MSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='7' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 3 LSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='8' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 4 MSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='9' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 4 LSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='10' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 5 MSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='11' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 5 LSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='12' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 6 MSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='13' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 6 LSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='14' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 7 MSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='15' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 7 LSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='16' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 8 MSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='17' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 8 LSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='18' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 9 MSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='19' page='1'>
<value>0x00</value>
<description>Output pulse time register for output 9 LSB
This is the pulse time for the each output expressed in seconds. This can be used
to make an output turn on and off with a certain preset interval. The min pulse time
is 1 second and the max time is 65535 seconds which is about 18 hours. Set to zero
(default) for no pulse time i.e. the output will be steady on/off.
To start a pulse sequence first write the pulse time to this register and then set
the corresponding bit in the output status register to start the output. The pulse
train is terminated by writing on or off (1 or 0) to the output status register.
</description>
</register>
<register offset='20' page='1'>
<value>0x00</value>
<description>Output protection time register for output 0 MSB
This is the output protection time. An output will be inactivated if not written
to before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='21' page='1'>
<value>0x00</value>
<description>Output protection time register for output 0 LSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='22' page='1'>
<value>0x00</value>
<description>Output protection time register for output 1 MSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='23' page='1'>
<value>0x00</value>
<description>Output protection time register for output 1 LSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='24' page='1'>
<value>0x00</value>
<description>Output protection time register for output 2 MSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='25' page='1'>
<value>0x00</value>
<description>Output protection time register for output 2 LSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='26' page='1'>
<value>0x00</value>
<description>Output protection time register for output 3 MSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='27' page='1'>
<value>0x00</value>
<description>Output protection time register for output 3 LSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='28' page='1'>
<value>0x00</value>
<description>Output protection time register for output 4 MSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='29' page='1'>
<value>0x00</value>
<description>Output protection time register for output 4 LSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='30' page='1'>
<value>0x00</value>
<description>Output protection time register for output 5 MSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='31' page='1'>
<value>0x00</value>
<description>Output protection time register for output 5 LSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='32' page='1'>
<value>0x00</value>
<description>Output protection time register for output 6 MSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='33' page='1'>
<value>0x00</value>
<description>Output protection time register for output 6 LSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='34' page='1'>
<value>0x00</value>
<description>Output protection time register for output 7 MSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='35' page='1'>
<value>0x00</value>
<description>Output protection time register for output 7 LSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='36' page='1'>
<value>0x00</value>
<description>Output protection time register for output 8 MSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='37' page='1'>
<value>0x00</value>
<description>Output protection time register for output 8 LSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='38' page='1'>
<value>0x00</value>
<description>Output protection time register for output 9 MSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='39' page='1'>
<value>0x00</value>
<description>Output protection time register for output 9 LSB
This is the output protection time. A output will be inactivated if not written to
before this time has elapsed.
Set to zero to disable (default). The max time is 65535 seconds which is about 18
hours.
The registers can be as an example be used as a security feature to ensure that
an output is deactivated after a preset time even if the controlling device failed
to deactivate the output. </description>
</register>
<register offset='0' page='2'>
<value>0x00</value>
<description>Decision matrix row 0: Oaddr
Originating address. Set to nickname for node that should trigger action. Oaddr is
the originating address. We are only interested in messages from the node given here.
0x00 is segment controller and 0xff is a node without a nickname. If bit 6 of flags
is set oaddr will not be checked and events from all nodes will be accepted. </description>
</register>
<register offset='1' page='2'>
<value>0x00</value>
<description>Decision matrix row 0: flags
Flags. Set selection behaviour.
The enable bit can be used to disable a decision matrix row while it is edited.
The zone and use sub zone bits can be activated to have a check on the zone/sub
zone information of an event. That is the zone/sub zone of the machine must match
the one of the event to trigger the DM row. </description>
</register>
<register offset='2' page='2'>
<value>0x00</value>
<description>Decision matrix row 0: Class mask (low eight bits)
The lowest eight bits of the class mask that defines the events that should trigger
the action of this decision matrix row.
Bit 8 of the class mask is stored in bit 1 of the flag byte. </description>
</register>
<register offset='3' page='2'>
<value>0x00</value>
<description>Decision matrix row 0: Class filter (low eight bits)
The lowest eight bits of the class filter that defines the events that should trigger
the action of thsi decision matrix row.
Bit 8 of the class filter is stored in bit 1 of the flag byte. </description>
</register>
<register offset='4' page='2'>
<value>0x00</value>
<description>Decision matrix row 0: Type mask
Type mask that defines the events that should trigger the action of this decision
matrix row.</description>
</register>
<register offset='5' page='2'>
<value>0x00</value>
<description>Decision matrix row 0: Type filter
Type filter that defines the events that should trigger the action of this decision
matrix row.</description>
</register>
<register offset='6' page='2'>
<value>0x00</value>
<description>Decision matrix row 0: Action
This is the action or operation that should be performed if the filtering is satisfied.
Only action code 0x00 is predefined and means No-Operation. All other codes are application
specific and typical application defined codes could do measurement, send predefined
event etc.</description>
</register>
<register offset='7' page='2'>
<value>0x00</value>
<description>Decision matrix row 0: Action parameter
A numeric action parameter can be set and its meaning is application specific.</description>
</register>
<register offset='8' page='2'>
<value>0x00</value>
<description>Decision matrix row 1: Oaddr
Originating address. Set to nickname for node that should trigger action. Oaddr is
the originating address. We are only interested in messages from the node given here.
0x00 is segment controller and 0xff is a node without a nickname. If bit 6 of flags
is set oaddr will not be checked and events from all nodes will be accepted. </description>
</register>
<register offset='9' page='2'>
<value>0x00</value>
<description>Decision matrix row 1: flags
Flags. Set selection behaviour.
The enable bit can be used to disable a decision matrix row while it is edited.
The zone and use sub zone bits can be activated to have a check on the zone/subzone
information of an event. That is the zone/sub zone of the machine must match the
one of the event to trigger the DM row. </description>
</register>
<register offset='10' page='2'>
<value>0x00</value>
<description>Decision matrix row 1: Class mask (low eight bits)
The lowest eight bits of the class mask that defines the events that should trigger
the action of this decision matrix row.
Bit 8 of the class mask is stored in bit 1 of the flag byte. </description>
</register>
<register offset='11' page='2'>
<value>0x00</value>
<description>Decision matrix row 1: Class filter (low eight bits)
The lowest eight bits of the class filter that defines the events that should trigger
the action of this decision matrix row.
Bit 8 of the class filter is stored in bit 1 of the flag byte. </description>
</register>
<register offset='12' page='2'>
<value>0x00</value>
<description>Decision matrix row 1: Type mask
Type mask that defines the events that should trigger the action of this decision
matrix row.</description>
</register>
<register offset='13' page='2'>
<value>0x00</value>
<description>Decision matrix row 1: Type filter
Type filter that defines the events that should trigger the action of this decision
matrix row.</description>
</register>
<register offset='14' page='2'>
<value>0x00</value>
<description>Decision matrix row 1: Action
This is the action or operation that should be performed if the filtering is satisfied.
Only action code 0x00 is predefined and means No-Operation. All other codes are application
specific and typical application defined codes could do measurement, send predefined
event etc.</description>
</register>
<register offset='15' page='2'>
<value>0x00</value>
<description>Decision matrix row 1: Action parameter
A numeric action parameter can be set and its meaning is application specific.</description>
</register>
<register offset='16' page='2'>
<value>0x00</value>
<description>Decision matrix row 2: Oaddr
Originating address. Set to nickname for node that should trigger action. Oaddr is
the originating address. We are only interested in messages from the node given here.
0x00 is segment controller and 0xff is a node without a nickname. If bit 6 of flags
is set oaddr will not be checked and events from all nodes will be accepted. </description>
</register>
<register offset='17' page='2'>
<value>0x00</value>
<description>Decision matrix row 2: flags
Flags. Set selection behaviour.
The enable bit can be used to disable a decision matrix row while it is edited.
The zone and use sub zone bits can be activated to have a check on the zone/sub
zone information of an event. That is the zone/sub zone of the machine must match
the one of the event to trigger the DM row. </description>
</register>
<register offset='18' page='2'>
<value>0x00</value>
<description>Decision matrix row 2: Class mask (low eight bits)
The lowest eight bits of the class mask that defines the events that should trigger
the action of this decision matrix row.
Bit 8 of the class mask is stored in bit 1 of the flag byte. </description>
</register>
<register offset='19' page='2'>
<value>0x00</value>
<description>Decision matrix row 2: Class filter (low eight bits)
The lowest eight bits of the class filter that defines the events that should trigger
the action of this decision matrix row.
Bit 8 of the class filter is stored in bit 1 of the flag byte. </description>
</register>
<register offset='20' page='2'>
<value>0x00</value>
<description>Decision matrix row 2: Type mask
Type mask that defines the events that should trigger the action of this decision
matrix row.</description>
</register>
<register offset='21' page='2'>
<value>0x00</value>
<description>Decision matrix row 2: Type filter
Type filter that defines the events that should trigger the action of this decision
matrix row.</description>
</register>
<register offset='22' page='2'>
<value>0x00</value>
<description>Decision matrix row 2: Action
This is the action or operation that should be performed if the filtering is satisfied.
Only action code 0x00 is predefined and means No-Operation. All other codes are application
specific and typical application defined codes could do measurement, send predefined
event etc.</description>
</register>
<register offset='23' page='2'>
<value>0x00</value>
<description>Decision matrix row 2: Action parameter
A numeric action parameter can be set and its meaning is application specific.</description>
</register>
<register offset='24' page='2'>
<value>0x00</value>
<description>Decision matrix row 3: Oaddr
Originating address. Set to nickname for node that should trigger action. Oaddr is
the originating address. We are only interested in messages from the node given here.
0x00 is segment controller and 0xff is a node without a nickname. If bit 6 of flags
is set oaddr will not be checked and events from all nodes will be accepted. </description>
</register>
<register offset='25' page='2'>
<value>0x00</value>
<description>Decision matrix row 3: flags
Flags. Set selection behaviour.
The enable bit can be used to disable a decision matrix row while it is edited.
The zone and use sub zone bits can be activated to have a check on the zone/sub
zone information of an event. That is the zone/sub zone of the machine must match
the one of the event to trigger the DM row. </description>
</register>
<register offset='26' page='2'>
<value>0x00</value>
<description>Decision matrix row 3: Class mask (low eight bits)
The lowest eight bits of the class mask that defines the events that should trigger
the action of this decision matrix row.
Bit 8 of the class mask is stored in bit 1 of the flag byte. </description>
</register>
<register offset='27' page='2'>
<value>0x00</value>
<description>Decision matrix row 3: Class filter (low eight bits)
The lowest eight bits of the class filter that defines the events that should trigger
the action of this decision matrix row.
Bit 8 of the class filter is stored in bit 1 of the flag byte. </description>
</register>
<register offset='28' page='2'>
<value>0x00</value>
<description>Decision matrix row 3: Type mask
Type mask that defines the events that should trigger the action of this decision
matrix row.</description>
</register>
<register offset='29' page='2'>
<value>0x00</value>
<description>Decision matrix row 3: Type filter
Type filter that defines the events that should trigger the action of this decision
matrix row.</description>
</register>
<register offset='30' page='2'>
<value>0x00</value>
<description>Decision matrix row 3: Action
This is the action or operation that should be performed if the filtering is satisfied.
Only action code 0x00 is predefined and means No-Operation. All other codes are application
specific and typical application defined codes could do measurement, send predefined
event etc.</description>
</register>
<register offset='31' page='2'>
<value>0x00</value>
<description>Decision matrix row 3: Action parameter
A numeric action parameter can be set and its meaning is application specific.</description>
</register>
<register offset='32' page='2'>
<value>0x00</value>
<description>Decision matrix row 4: Oaddr
Originating address. Set to nickname for node that should trigger action. Oaddr is
the originating address. We are only interested in messages from the node given here.
0x00 is segment controller and 0xff is a node without a nickname. If bit 6 of flags
is set oaddr will notbe checked and events from all nodes will be accepted. </description>
</register>
<register offset='33' page='2'>
<value>0x00</value>
<description>Decision matrix row 4: flags
Flags. Set selection behaviour.
The enable bit can be used to disable a decision matrix row while it is edited.
The zone and use sub zone bits can be activated to have a check on the zone/sub
zone information of an event. That is the zone/sub zone of the machine must match
the one of the event to trigger the DM row. </description>
</register>
<register offset='34' page='2'>
<value>0x00</value>
<description>Decision matrix row 4: Class mask (low eight bits)
The lowest eight bits of the class mask that defines the events that should trigger
the action of this decision matrix row.
Bit 8 of the class mask is stored in bit 1 of the flag byte. </description>
</register>
<register offset='35' page='2'>
<value>0x00</value>
<description>Decision matrix row 4: Class filter (low eight bits)
The lowest eight bits of the class filter that defines the events that should trigger
the action of this decision matrix row.
Bit 8 of the class filter is stored in bit 1 of the flag byte. </description>
</register>
<register offset='36' page='2'>
<value>0x00</value>
<description>Decision matrix row 4: Type mask
Type mask that defines the events that should trigger the action of this decision
matrix row.</description>
</register>
<register offset='37' page='2'>
<value>0x00</value>
<description>Decision matrix row 4: Type filter
Type filter that defines the events that should trigger the action of this decision
matrix row.</description>
</register>
<register offset='38' page='2'>
<value>0x00</value>
<description>Decision matrix row 4: Action
This is the action or operation that should be performed if the filtering is satisfied.
Only action code 0x00 is predefined and means No-Operation. All other codes are application
specific and typical application defined codes could do measurement, send predefined
event etc.</description>
</register>
<register offset='39' page='2'>
<value>0x00</value>
<description>Decision matrix row 4: Action parameter
A numeric action parameter can be set and its meaning is application specific.</description>
</register>
<register offset='40' page='2'>
<value>0x00</value>
<description>Decision matrix row 5: Oaddr
Originating address. Set to nickname for node that should trigger action. Oaddr
is the originating address. We are only interested in messages from the node given
here. 0x00 is segment controller and 0xff is a node without a nickname. If bit 6
of flags is set oaddr will not be checked and events from all nodes will be accepted.
</description>
</register>
<register offset='41' page='2'>
<value>0x00</value>
<description>Decision matrix row 5: flags
Flags. Set selection behaviour.
The enable bit can be used to disable a decision matrix row while it is edited.
The zone and use sub zone bits can be activated to have a check on the zone/sub
zone information of an event. That is the zone/sub zone of the machine must match
the one of the event to trigger the DM row. </description>
</register>
<register offset='42' page='2'>
<value>0x00</value>
<description>Decision matrix row 5: Class mask (low eight bits)
The lowest eight bits of the class mask that defines the events that should trigger
the action of this decision matrix row.
Bit 8 of the class mask is stored in bit 1 of the flag byte. </description>
</register>
<register offset='43' page='2'>
<value>0x00</value>
<description>Decision matrix row 5: Class filter (low eight bits)
The lowest eight bits of the class filter that defines the events that should trigger
the action of this decision matrix row.
Bit 8 of the class filter is stored in bit 1 of the flag byte. </description>
</register>
<register offset='44' page='2'>
<value>0x00</value>
<description>Decision matrix row 5: Type mask
Type mask that defines the events that should trigger the action of this decision
matrix row.</description>
</register>
<register offset='45' page='2'>
<value>0x00</value>
<description>Decision matrix row 5: Type filter
Type filter that defines the events that should trigger the action of this decision
matrix row.</description>
</register>
<register offset='46' page='2'>
<value>0x00</value>
<description>Decision matrix row 5: Action
This is the action or operation that should be performed if the filtering is satisfied.
Only action code 0x00 is predefined and means No-Operation. All other codes are application
specific and typical application defined codes could do measurement, send predefined
event etc.</description>
</register>
<register offset='47' page='2'>
<value>0x00</value>
<description>Decision matrix row 5: Action parameter
A numeric action parameter can be set and its meaning is application specific.</description>
</register>
<register offset='48' page='2'>
<value>0x00</value>
<description>Decision matrix row 6: Oaddr
Originating address. Set to nickname for node that should trigger action. Oaddr is
the originating address. We are only interested in messages from the node given here.
0x00 is segment controller and 0xff is a node without a nickname. If bit 6 of flags
is set oaddr will not be checked and events from all nodes will be accepted. </description>
</register>
<register offset='49' page='2'>
<value>0x00</value>
<description>Decision matrix row 6: flags
Flags. Set selection behaviour.
The enable bit can be used to disable a decision matrix row while it is edited.
The zone and use sub zone bits can be activated to have a check on the zone/sub
zone information of an event. That is the zone/subzone one of the machine must match
the one of the event to trigger the DM row. </description>
</register>
<register offset='50' page='2'>
<value>0x00</value>
<description>Decision matrix row 6: Class mask (low eight bits)
The lowest eight bits of the class mask that defines the events that should trigger
the action of this decision matrix row.
Bit 8 of the class mask is stored in bit 1 of the flag byte. </description>
</register>
<register offset='51' page='2'>
<value>0x00</value>
<description>Decision matrix row 6: Class filter (low eight bits)
The lowest eight bits of the class filter that defines the events that should trigger
the action of this decision matrix row.
Bit 8 of the class filter is stored in bit 1 of the flag byte. </description>
</register>
<register offset='52' page='2'>
<value>0x00</value>
<description>Decision matrix row 6: Type mask
Type mask that defines the events that should trigger the action of this decision
matrix row.</description>
</register>
<register offset='53' page='2'>
<value>0x00</value>
<description>Decision matrix row 6: Type filter
Type filter that defines the events that should trigger the action of this decision
matrix row.</description>
</register>
<register offset='54' page='2'>
<value>0x00</value>
<description>Decision matrix row 6: Action
This is the action or operation that should be performed if the filtering is satisfied.
Only action code 0x00 is predefined and means No-Operation. All other codes are application
specific and typical application defined codes could do measurement, send predefined
event etc.</description>
</register>
<register offset='55' page='2'>
<value>0x00</value>
<description>Decision matrix row 6: Action parameter
A numeric action parameter can be set and its meaning is application specific.</description>
</register>
<register offset='56' page='2'>
<value>0x00</value>
<description>Decision matrix row 7: Oaddr
Originating address. Set to nickname for node that should trigger action. Oaddr is
the originating address. We are only interested in messages from the node given here.
0x00 is segment controller and 0xff is a node without a nickname. If bit 6 of flags
is set oaddr will not be checked and events from all nodes will be accepted. </description>
</register>
<register offset='57' page='2'>
<value>0x00</value>
<description>Decision matrix row 7: flags
Flags. Set selection behaviour.
The enable bit can be used to disable a decision matrix row while it is edited.
The zone and use sub zone bits can be activated to have a check on the zone/sub
zone information of an event. That is the zone/subzone one of the machine must match
the one of the event to trigger the DM row. </description>
</register>
<register offset='58' page='2'>
<value>0x00</value>
<description>Decision matrix row 7: Class mask (low eight bits)
The lowest eight bits of the class mask that defines the events that should trigger
the action of this decision matrix row.
Bit 8 of the class mask is stored in bit 1 of the flag byte. </description>
</register>
<register offset='59' page='2'>
<value>0x00</value>
<description>Decision matrix row 7: Class filter (low eight bits)
The lowest eight bits of the class filter that defines the events that should trigger
the action of this decision matrix row.
Bit 8 of the class filter is stored in bit 1 of the flag byte. </description>
</register>
<register offset='60' page='2'>
<value>0x00</value>
<description>Decision matrix row 7: Type mask
Type mask that defines the events that should trigger the action of this decision
matrix row.</description>
</register>
<register offset='61' page='2'>
<value>0x00</value>
<description>Decision matrix row 7: Type filter
Type filter that defines the events that should trigger the action of this decision
matrix row.</description>
</register>
<register offset='62' page='2'>
<value>0x00</value>
<description>Decision matrix row 7: Action
This is the action or operation that should be performed if the filtering is satisfied.
Only action code 0x00 is predefined and means No-Operation. All other codes are application
specific and typical application defined codes could do measurement, send predefined
event etc.</description>
</register>
<register offset='63' page='2'>
<value>0x00</value>
<description>Decision matrix row 7: Action parameter
A numeric action parameter can be set and its meaning is application specific.</description>
</register>
<register offset='128' page='0'>
<value>0x00</value>
<description>Alarm Status Register</description>
</register>
<register offset='129' page='0'>
<value>0x01</value>
<description>VSCP Major version number</description>
</register>
<register offset='130' page='0'>
<value>0x06</value>
<description>VSCP Minor version number</description>
</register>
<register offset='131' page='0'>
<value>0x00</value>
<description>Node Control Flags
test</description>
</register>
<register offset='132' page='0'>
<value>0x00</value>
<description>User ID 0</description>
</register>
<register offset='133' page='0'>
<value>0x00</value>
<description>User ID 1</description>
</register>
<register offset='134' page='0'>
<value>0x00</value>
<description>User ID 2</description>
</register>
<register offset='135' page='0'>
<value>0xFF</value>
<description>User ID 3</description>
</register>
<register offset='136' page='0'>
<value>0xFF</value>
<description>User ID 4</description>
</register>
<register offset='137' page='0'>
<value>0x00</value>
<description>Manufacturer device id 0</description>
</register>
<register offset='138' page='0'>
<value>0x0F</value>
<description>Manufacturer device id 1</description>
</register>
<register offset='139' page='0'>
<value>0x0B</value>
<description>Manufacturer device id 2</description>
</register>
<register offset='140' page='0'>
<value>0x16</value>
<description>Manufacturer device id 3</description>
</register>
<register offset='141' page='0'>
<value>0x01</value>
<description>Manufacturer sub device id 0</description>
</register>
<register offset='142' page='0'>
<value>0x00</value>
<description>Manufacturer sub device id 1</description>
</register>
<register offset='143' page='0'>
<value>0x00</value>
<description>Manufacturer sub device id 2</description>
</register>
<register offset='144' page='0'>
<value>0x00</value>
<description>Manufacturer sub device id 3</description>
</register>
<register offset='145' page='0'>
<value>0x01</value>
<description>Nickname id</description>
</register>
<register offset='146' page='0'>
<value>0x00</value>
<description>Page select register MSB</description>
</register>
<register offset='147' page='0'>
<value>0x00</value>
<description>Page select register LSB</description>
</register>
<register offset='148' page='0'>
<value>0x01</value>
<description>Firmware major version number</description>
</register>
<register offset='149' page='0'>
<value>0x01</value>
<description>Firmware minor version number</description>
</register>
<register offset='150' page='0'>
<value>0x06</value>
<description>Firmware sub minor version number</description>
</register>
<register offset='151' page='0'>
<value>0x01</value>
<description>Boot loader algorithm</description>
</register>
<register offset='152' page='0'>
<value>0x08</value>
<description>Buffer Size</description>
</register>
<register offset='153' page='0'>
<value>0x03</value>
<description>Number of register pages used.</description>
</register>
<register offset='208' page='0'>
<value>0x01</value>
<description>GUID Byte 15, MSB
GUID=01:00:00:00:00:00:00:00:00:00:00:00:06:00:00:0F</description>
</register>
<register offset='209' page='0'>
<value>0x00</value>
<description>GUID Byte 14</description>
</register>
<register offset='210' page='0'>
<value>0x00</value>
<description>GUID Byte 13</description>
</register>
<register offset='211' page='0'>
<value>0x00</value>
<description>GUID Byte 12</description>
</register>
<register offset='212' page='0'>
<value>0x00</value>
<description>GUID Byte 11</description>
</register>
<register offset='213' page='0'>
<value>0x00</value>
<description>GUID Byte 10</description>
</register>
<register offset='214' page='0'>
<value>0x00</value>
<description>GUID Byte 9</description>
</register>
<register offset='215' page='0'>
<value>0x00</value>
<description>GUID Byte 8</description>
</register>
<register offset='216' page='0'>
<value>0x00</value>
<description>GUID Byte 7</description>
</register>
<register offset='217' page='0'>
<value>0x00</value>
<description>GUID Byte 6</description>
</register>
<register offset='218' page='0'>
<value>0x00</value>
<description>GUID Byte 5</description>
</register>
<register offset='219' page='0'>
<value>0x00</value>
<description>GUID Byte 4</description>
</register>
<register offset='220' page='0'>
<value>0x06</value>
<description>GUID Byte 3</description>
</register>
<register offset='221' page='0'>
<value>0x00</value>
<description>GUID Byte 2</description>
</register>
<register offset='222' page='0'>
<value>0x00</value>
<description>GUID Byte 1</description>
</register>
<register offset='223' page='0'>
<value>0x0F</value>
<description>GUID Byte 0, LSB</description>
</register>
<register offset='224' page='0'>
<value>0x77</value>
<description>Module Description File URL, MSB
http://www.eurosource.se/beijing_2.xml</description>
</register>
<register offset='225' page='0'>
<value>0x77</value>
<description>Module Description File URL</description>
</register>
<register offset='226' page='0'>
<value>0x77</value>
<description>Module Description File URL</description>
</register>
<register offset='227' page='0'>
<value>0x2E</value>
<description>Module Description File URL</description>
</register>
<register offset='228' page='0'>
<value>0x65</value>
<description>Module Description File URL</description>
</register>
<register offset='229' page='0'>
<value>0x75</value>
<description>Module Description File URL</description>
</register>
<register offset='230' page='0'>
<value>0x72</value>
<description>Module Description File URL</description>
</register>
<register offset='231' page='0'>
<value>0x6F</value>
<description>Module Description File URL</description>
</register>
<register offset='232' page='0'>
<value>0x73</value>
<description>Module Description File URL</description>
</register>
<register offset='233' page='0'>
<value>0x6F</value>
<description>Module Description File URL</description>
</register>
<register offset='234' page='0'>
<value>0x75</value>
<description>Module Description File URL</description>
</register>
<register offset='235' page='0'>
<value>0x72</value>
<description>Module Description File URL</description>
</register>
<register offset='236' page='0'>
<value>0x63</value>
<description>Module Description File URL</description>
</register>
<register offset='237' page='0'>
<value>0x65</value>
<description>Module Description File URL</description>
</register>
<register offset='238' page='0'>
<value>0x2E</value>
<description>Module Description File URL</description>
</register>
<register offset='239' page='0'>
<value>0x73</value>
<description>Module Description File URL</description>
</register>
<register offset='240' page='0'>
<value>0x65</value>
<description>Module Description File URL</description>
</register>
<register offset='241' page='0'>
<value>0x2F</value>
<description>Module Description File URL</description>
</register>
<register offset='242' page='0'>
<value>0x62</value>
<description>Module Description File URL</description>
</register>
<register offset='243' page='0'>
<value>0x65</value>
<description>Module Description File URL</description>
</register>
<register offset='244' page='0'>
<value>0x69</value>
<description>Module Description File URL</description>
</register>
<register offset='245' page='0'>
<value>0x6A</value>
<description>Module Description File URL</description>
</register>
<register offset='246' page='0'>
<value>0x69</value>
<description>Module Description File URL</description>
</register>
<register offset='247' page='0'>
<value>0x6E</value>
<description>Module Description File URL</description>
</register>
<register offset='248' page='0'>
<value>0x67</value>
<description>Module Description File URL</description>
</register>
<register offset='249' page='0'>
<value>0x5F</value>
<description>Module Description File URL</description>
</register>
<register offset='250' page='0'>
<value>0x32</value>
<description>Module Description File URL</description>
</register>
<register offset='251' page='0'>
<value>0x2E</value>
<description>Module Description File URL</description>
</register>
<register offset='252' page='0'>
<value>0x78</value>
<description>Module Description File URL</description>
</register>
<register offset='253' page='0'>
<value>0x6D</value>
<description>Module Description File URL</description>
</register>
<register offset='254' page='0'>
<value>0x6C</value>
<description>Module Description File URL</description>
</register>
<register offset='255' page='0'>
<value>0x00</value>
<description>Module Description File URL, LSB</description>
</register>
</registerset>
Info is here.
Categories
VSCP framework v1.1.0 released
Info is here.
VSCP + node-red