IN’O sensor

 

Declaration of conformity


Download the declaration of conformity

Presentation


The IN’O sensor is LoRaWAN class A sensor, it manages two different power supplies, one is external and may range from 9V to 24V, the other one is internal on the battery.

The IN’O sensor integrates 10 digital inputs, and 4 optocoupled outputs. It  also includes an external antenna.

It is possible to report the level or a counter on the different inputs. It is also possible to get the voltage of the power supply, and to switch ON, OFF or toggle the outputs.

 

ino1

Family code

The family code of IN’O sensors is:

50-70-016-xxx Class A

50-70-087-xxx Class C

 

Electronic input/output

The schematic of the different inputs and outputs of the IN’O sensor is illustrated below:

Electrical schematic example for inputs

 

1

 

→ Due to limitation software, the maximum frequency is 100 Hz on each input

Electrical schematic example for outputs

2

Installation and use


Installation

The housing is intended to be installed inside or outside a building but to the shelter of a vertical splash water and direct sunlight.

The product is delivered disassembled. This enables the connection to the screw terminals.

Before connecting your cable strands to the product’s screw terminals, you must insert the cable gland’s nut and the seal.

 

cable-gland2

Then connect wires on Inputs and Outputs that will be used:

ino_carte

For connectors, it is preferable to use several single wires with a gauge of 20-26 AWG. As the connectors pluck the wires plugged inside at about 4mm of the wire-end , strip the wires on about 5 to 6 mm of their extremity before plugging them into the connectors.

Once the assembly is done, the casing can be closed.

The housing is compatible with the following DIN rail adapter:

din

For more information about the casing, visit: www.spelsberg.com

Propagation radio

In order for the sensor to function correctly, it is better to limit the number of obstacles in order to avoid excessive attenuation of the radio wave, it is also important to put the sensor as high as possible. Also, the antenna needs to be directed upwards.

ino_propagation

Autonomy


The information in the table below represents how long the battery can last. It is  based on the default configuration at ambient temperature (+25°C) within the optimal use of the sensor throught LoRaWAN network (one uplink frame), and when  the spreading factor used is SF12.

The capacity of the disposable battery is 3.6Ah, 85% of it is used.

Transmission periodicityBattery lifeBattery life (Input closed contact)
1 frames/2 hours14 years12 years
1 frames/24 hours+15 years+15 years

A value of 3µA of consumption is added per connected input which contact is closed.

When one of the outputs is on ON state, a consumption of 160µA is added.

Human Machine Interface


After installing the device, switch ON the power.

There are three leds on the IN’O devices:

ASS:      blinking until the association to a network is done.

association

FNC:     blinking each minute while an input is activated.

CNF:     blinking in the configuration mode.

  • A user button is available to enter in configuration mode, « void » frames are then sent every minute for 10 minutes.

Standard reports are not functioning during this mode.

Configuration mode
Way to trigger itOne press on the USER button or specific ZCL command
Way to stop it Another press on the USER button or specific ZCL command
Effects on the sensorThe CONF led (red) blinks (3 sec. OFF, 3 sec. ON) and the sensor sends an uplink frame every minute. The blinking is illustrated below this table.
Time durationThe configuration mode lasts 10 minutes when it is triggered by pressing the USER button

4

  • It is possible to ask a ReAssociation procedure if no down frame is received by the sensor during a given periodicity (4 days by default) or if a given number (100 by default) or failure (no acquittement is received) are reached by sending an applicative frame to the sensor or by the IHM of the sensor.

The sensor keeps the AppEUi and DevAddr configured, Confirmed/Unconfirmed  configuration and all applicative configurations. On the other hand, LoRaWAN configuration (channel, datarate …) are lost.

ReAssociation Mode
Way to trigger itThree short press on the USER button or ZCL command from LoRaWAN cluster.
Effects on the sensorThe ASSO led (green) blinks as the “no commissioned sensor” led lightning.
  • A factory reset is available on nke Watteco’s sensors. It deletes all the applicative settings saved in the flash memory (i.e.: the configured batches and reports will be deleted).

The sensor keeps the AppEUi and DevAddr configured. On the other hand, LoRaWAN configurations (channel, datarate …) and applicative configurations are lost.

Factory reset
Way to trigger ittwo short presses and one long press for approximately 7 seconds on the USER button.
Effects on the sensorThe CONF led (red) and ASSO led (green) blink at the same time briefly. All the applicative settings (about batches and reports) are deleted. The blinking is illustrated below this table.

5

Applicative layer


The IN’O device implements “ON/OFF” and “Binary Input” clusters, associated to their Outputs and Inputs. The corresponding between the connectors and the EndPoint is done below:

ConnectorEnd PointCluster Fctrl
Input 1+/1-0Binary Input0x11
Input 2+/2-1Binary Input0x31
Input 3+/3-2Binary Input0x51
Input 4+/4-3Binary Input0x71
Input 5+/5-4Binary Input0x91
Input 6+/6-5Binary Input0xB1
Input 7+/7-6Binary Input0xD1
Input 8+/8-7Binary Input0xF1
Input 9+/9-8Binary Input0x13
Input 10+/10-9Binary Input0x33
Output 1+/1-0ON/OFF0x11
Output 2+/2-1ON/OFF0x31
Output 3+/3-2ON/OFF0x51
Output 4+/4-3ON/OFF0x71

IN’O integrate clusters:

clustercluster namemanaged attributes
0x0000BasicAll
0x0050ConfigurationAll
0x0006ON/OFFAll
0x000FBinary InputAll
0x8004LoRaWANAll
0x8005Multi Binary Inputs All

Default configuration

A default configuration is set:

  • The device reports each day the counter associated to the input 1+/1- (EndPoint 0 / Cluster Binary Input /Attribut Count).
  • The device reports the state of input 2+/2- at each variation with a hysteresis of 2 hours (Endpoint 1 / Cluster Binary Input / Attribut Present Value).

Every change on the default configuration must respect the legal duty cycle. (For example the most restrictive in EU is 0.1%, so in SF12 it is around 1 frame each hour)

Frame examples


Standard report

Report

 

Report of the present value of the connector input 1+/1-

→ Applicative payload is: 11 0a 00 0f 00 55 10 01

 11: Fctrl (Endpoint=0)

 01: current binary value

Report of the current value of the counter of the connector input 2+/2-

→Applicative payload is: 31 0a 00 0f 04 02 23 00 00 00 01

 31: Fctrl (Endpoint=1)

 00 00 00 01: current value of the counter 

 

Configuration

 

Toggle the output 2+/2-

→The output 2+/2- is the End Point 1; Cluster “ON/OFF” is 0x0006. It is necessary to use a specific command 0x50 with payload 0x02 for the toggle.

Applicative payload is: 31 50 00 06 02

31: Fctrl (Endpoint=1)

02: invert the relay state of the sensor 

 

Configure a standard report on the connector input 6+/6-

Report the value of the connector Input 6+/6- every 1 pulse. The value has to be reported at less each 10 minutes, and a minimal timing of 10 seconds between 2 reports has to be settled to optimize the consumption:

→The value on Input 6+/6- is the End Point 5, Cluster “Binary Input” is 0x000F, and Attribute “present value” is 0x0055. The maximum field has to be 0x800A to have a report all 10 minutes and the minimum  field has to be 0x000A to have a minimal timing between two reports. The delta has to be configured to 0x01 for a report every 1 pulse.

 Applicative payload is: b1 06 00 0f 00 00 55 10 00 0a 80 0a 01

b1: Fctrl (Endpoint=5)

00 0a: minimum reporting interval (10 seconds)

80 0a: maximum reporting interval (10 minutes)

01: reportable change (1 pulse)

→Response: b1 07 00 0f 00 00 00 55

To disable the previous configuration, change the value of the minimum and maximum sending interval and the delta to 0: b1 06 00 0f 00 00 55 10 00 00 00 00 00

 

Configure a standard report on the connector input 1+/1-

Report the counter all the 5 pulses on the connector Input 1+/1-. The counter has to be reported at least each hour:

→A counter on Input 1+/1 is the End Point 0, Cluster “Binary Input” is 0x000F, and Attribute “Count” is 0x0402. The maximum field has to be 0x0e10 to have a report all one hour and the minimum field has to be  0x0000 to have a report immediately after the right incrementation. The delta has to be configured to 0x05 for a report all the 5 pulses.

Applicative payload is: 11 06 00 0f 00 04 02 23 00 00 0e 10 00 00 00 05

11: Fctrl (Endpoint=0)

00 00: minimum reporting interval (0 seconds)

0e 10: maximum reporting interval (1 hour)

00 00 00 05: reportable change (5 pulses)

→Response:11 07 00 0f 00 00 04 02

To disable the previous configuration, change the value of the minimum and maximum sending interval and the delta to 0: 11 06 00 0f 00 04 02 23 00 00 00 00 00 00 00 00 

 

Configure the polarity on the connector Input 1+/1-

→Write attribute no response: 11 05 00 0f 00 54 10 nn

11: Fctrl (Endpoint=0)

nn: current polarity of the sensor (normal : 00, reversed: 01)

 

Configure the edge selection on the connector Input 1+/1-

→Write attribute no response: 11 05 00 0f 04 00 18 nn

11: Fctrl (Endpoint=0)

nn: the current edge selection ( 01: falling edge, 02: rising edge, 03: rising and falling edge, 04: polling) 

 

Configure the debounce period on the connector 3+/3-

→Write attribute no response: 51 05 00 0f 04 01 21 00 7D

51: Fctrl (Endpoint=2)

00 7D: debounce period (125 ms)

 

Batch report

Configuration

 

• Configure a batch report on the connector input 6+/6- and the connector input 5+/5-:

Timestamp and record the Input 6+/6- all the 100 pulses; and timestamp and record the level of the Input 5+/5-. A report has to be sent at least all 10 minutes:

→A counter on Input 6+/6- is the End Point 5, Cluster “Binary Input” is 0x000F, and Attribute “Count” is 0x0402.

A level on Input 5+/5- is End Point 4, Cluster “Binary Input” is 0x000F, and Attribute “Present Value” is 0x0055.

There are two different measures to record in the batch, so the tag size has to be 1. Label 0 can be used for counter and Label 1 for level.

For counter, the delta is 100 and resolution 1. For level, the delta is 1 and the resolution 1. The maximum has to be configured for all to 0x800a.

It is necessary to send two frames to configure this batch.

Number of labelTag labelTag size
1 or 20/11
3 or 400/01/11/102
5 or 6 or 7 or 8000/001/010/011/100/101/110/1113
.........

Applicative payload of the count on input 6+/6-

 b1 06 00 0f 1d 04 02 00 00 00 80 0a 00 00 00 64 00 00 00 01 01 

b1: Fctrl (Endpoint=5)

1d:  0b00011101 => 0001110: size of configuration string after attribute ID (14 bytes)

00 00: minimum recording interval (0 seconds)

80 0a: maximum recording interval (10 minutes)

00 00 00 64:  required delta value (size: 4 bytes for attribute Count => attribute type = 23, 100 pulses)

00 00 00 01: required resolution

01: tag value (ob00000001 => 00000: tag label, 001: tag size)

→Response: b1 07 00 0f 00 01 04 02

 

Applicative payload of the present value of input 5+/5-

 91 06 00 0f 11 00 55 00 00 00 80 0a  01  01 09 

91: Fctrl (Endpoint=4)

11: 0b00010001 => 0001000: size of configuration string after attribute ID (8 bytes)

00 00: minimum recording interval (0 seconds)

80 0a: maximum recording interval (10 minutes)

01: required delta value (size: 1 byte for attribute PresentValue => attribute type = 10, 1 pulse)

01: required resolution

09: tag value (ob00001001 => 00001: tag label, 001: tag size)

→Response: 91 07 00 0f 00 01 00 55

 

To decode the batch reception, use the br_uncompress. Type for binary input attribute counter is U32 (10), Type for binary input attribute PresentValue is Boolean (1), so it is necessary to use this command:

echo “ 26100040405e7692050000004006 ” | br_uncompress -a 1   0,1,10   1,1 ,1

Result

UNCOMPRESS SERIE

cnt: 7   #  Counter of the batch (from 0 to 7)

5778    # Timestamp in second of sending of the frame

#Format of data is: TimeStamp of Measure | Label | Value

5689 0 0     # TimeStamp: 5689 s                                Label 0                  Value: 0

5777 1 1     # TimeStamp: 5777 s                                Label 1                  Value: 1

 

 

Print Friendly