Pilote wire LoRa remote

 

Declaration of conformity


Download the declaration of conformity

Presentation


The Pilote Wire LoRa Remote sensor is LoRaWAN class C sensor, it uses the main voltage as a power supply.

The Pilote Wire LoRa Remote sensor can be used in two different ways: it can either control a radiator, or it can be used in pair with a relay in order to control On/Off different devices.

pilot_wire

Family code

The family code of the Pilote Wire LoRa Remote sensors is: 50-70-027-xxx

Installation and use


Installation

 

CAUTION:

• The Pilot Wire LoRa remote is connected to the mains power source, harmful voltage will be present on all wires during operation.

• Connect or disconnect the device after MAKING SURE TO HAVE SWITCHED OFF MAINS POWER FROM ALL WIRES (disconnecting a single wire  e.g. from a manual switch is NOT sufficient).

The Pilot Wire LoRa remote is not waterproof. It has to be protected from the water splash and cannot be used in bathrooms.

During the installation, the ground wire (Green/Yellow) must not be connected to the Pilot Wire LoRa Remote. However, they have to be connected to the device that the sensor controls (a radiator for example).

Two fixing holes allow to attach the device to a wall. It is strongly advised to use an electric isolated screwdriver to fix the device.

Use only electric connection casing that are in compliance with electric applicable norms (NFC15-100).

The Pilot Wire LoRa remote has three wires, the brown wire has to be connected on the electrical phase, the blue one on the neutral, and the black one is the output of the pilot-wire order.

Installation for radiator control

 

radiator_control

 

The mains is used as a power supply and as a signal generator for the pilot wire output.
The Pilot Wire LoRa Remote is capable of generating 6 orders:

• Comfort (the radiator follow the thermostat order)

• Eco (the radiator maintains 3 or 4°C less than the thermostat order)

• Antifreeze (the radiator maintain a temperature in the room above 5°C)

• Stop (the radiator does not heat)

• -1°C (the radiator follows the thermostat order minus 1°C)

• -2°C (the radiator follows the thermostat order minus 2°C)

Installation for control of devices through a relay

 

The pilot wire LoRa remote cannot be directly used to work as a relay. But it can be used in pair with a relay.

The relay is connected following the schematic here below, in order to control On/Off different devices (hot water tank, lamp, street light, etc.).

 

relay_pilote_wire

 

The output signal will be used to control a relay that will be turned on if the command is the mains signal or off if there is no signal on the coil. The maximum current allowed will depend on the relay used. Moreover, a relay socket allows to put the relay inside an electrical panel.

The following relay and socket have been tested successfully with the Pilot wire LoRaWAN remote : relay and socket

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 strongly advised to not put the sensor right behind the radiator that it controls, a big metal piece can alterate the wireless signal quality.

Human Machine Interface


One led can be seen on the device. This led can have 3 different colors:

  • Green: blinking until the association to a network is done.

association

  • Red: blinking when AMR is activated.
  • Orange: blinking 3 times on a reset factory

An AMR (Magnetic Switch) is available in the Pilot Wire LoRa Remote. In order to activate it, a magnet has to be put really near the AMR Activation Zone.

pilot_wire_ihm

When the AMR is activated, the red led blink really fast. This behavior allows the user to easily know when the AMR is activated.

  • 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.

To ask the device to start a new association, pass the magnet 3 consecutive times near the AMR, the green led will start flashing again.

  • 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.

To reset the device, pass the magnet two quick passages and one long passage (more than 7 seconds) near the AMR, the orange led will blink 3 times. To complete the “Reset Factory”, the device needs to be rebooted.

Applicative layer


Codec are available to decode frame: Downloads

The Pilot Wire LoRa remote device implements “Multistate Output” cluster associated to the pilot wire output.

The Pilot Wire LoRa Remote integrates the following clusters:

ClusterCluster nameManaged attributes
0x0000BasicAll
0x0050ConfigurationAll
0x0013Multistate OutputAll

Frame examples


Standard report

Report

 

Report of the present value of multistate output

Applicative payload is: 11 0a 00 13 00 55 20 01

01: current present value (economy)

Configuration

 

Change of the state of the relay connected to the LoRa Remote

Applicative payload is: 11 05 00 13 00 55 20 01

01: relay state (ON)

Configure a standard report on the pilote wire output

Report the present value of the pilot wire output. The report has to be at less each 10 minutes, and a minimal timing of 10 seconds between 2 reports has to be setted.

→ As there is only one pilot wire output, the End Point is 0, cluster “Multistate Output” is 0x0013 and attribut “PresentValue” is 0x0055. The maximum field has to be 0x800A to have a report every 10 minutes and the minimum field has to be 0x000A to have a minimal timing of 10 seconds between two reports. The delta field has to be configured to 0x01 in order to trigger a report every time the pilot wire output change.

Applicative payload is: 11 06 00 13 00 00 55 20 00 0a 80 0a 01

00 0a: minimum reporting interval (10 seconds)

80 0a: maximum reporting interval (10 minutes)

01: reportable change

→Response: 11 07 00 13 00 00 00 55

To disable the previous configuration, change the value of the minimum and maximum sending interval and the delta to 0: 11 06 00 13 00 00 55 20 00 00 00 00 00

Batch report

Configuration

 

• Configure a batch report on the pilote wire output

Timestamp and record the pilot wire output each time it changes. A report has to be sent at least every 24 hours.

→ As there is only one pilot wire output, the End Point is 0, cluster “Multistate Output” is 0x0013 and attribut “PresentValue” is 0x0055.

The maximum field has to be 0x85A0 to have a report at least every 24 hours and the minimum field has to be 0x000A to have a minimal timing of 10 seconds between two reports.

There is just one value to record in the batch, the tag size can be 1 or 2 or 3. The tag size choosen here is 3. Label 0 will be used.

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

11 06 00 13 11 00 55 00 00 0a 85 a0 01 01 03

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

00 0a: minimum reporting interval (10 seconds)

85 a0: maximum reporting interval (24 hours)

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

01: required resolution

03: tag value (ob00000011 => 00000: tag label, 011: tag size)

→Response: 11 07 00 13 00 01 00 55

To decode the batch reception, use the br_uncompress. Type for Present Value is U8 (4) so it is necessary to use this command:

echo “ ….. ” | br_uncompress -a 3 0,1,4

Print Friendly