PCR2 Configuration Payload V3

This document describes version 3 of the configuration payload introduced with Firmware V3.4.0

Older versions of this document can be found here

This payload is used to remotely read / write device configurations over LoRaWAN.

Configuration Payload Format

Byte Property Description Uplink Values Downlink Values
0 Vendor ID Always 0xbe for Parametric Devices be ignored (*)
1 DeviceFamily Always 0x01 for PCR2 Devices 01 ignored (*)
2 PayloadVersion Always 0x03 for V3 Payloads 03 ignored (*)
3 DeviceType 00: PCR2-IN
01: PCR2-OD
02: PCR2-R
03: PCR2-T
04: PCR2-XIO
00-04 ignored (*)
4:6 FirmwareVersion 0x030402 = V3.4.2 030400-0304ff ignored (*)
7 OperatingMode 00: Timespan
01: Not Zero
02: Trigger
03: CapacityAlert
00-03 00-03
8 PayloadType 00: ELSYS
01: Cayenne LPP
02: Extended
00-02 00-02
9 DeviceClass 00: Class A
02: Class C
00 or 02 00 or 02
10 UplinkType 00: Uncofirmed
01: Confirmed
00 or 01 00 or 01
11:12 UplinkInterval 1-1440 Minutes 0001-05a0 0001-05a0
13:14 LinkCheckInterval 1-1440 Minutes, 0 = No LinkChecks 0000-05a0 0000-05a0
15:16 CapacityLimit 0-65535 Objects 0000-ffff 0000-ffff
17:18 HoldoffTime 0-600s 0000-0258 0000-0258
19 RadarSensitivity 10-100% 0a-64 0a-64

(*) These fields values are ignored by the device when downlinking this payload

Payload Examples (Hexstring)

These examples show some example configuration payloads you might use as a starting point.

Default Settings

be 01 03 00 03 04 00 00 00 00 01 00 0a 05 a0 00 00 00 00 50

Radar Sensitivity reduced to 20%

be 01 03 00 03 04 00 00 00 00 01 00 0a 05 a0 00 00 00 00 14

Interval increased to 1 hour

be 01 03 00 03 04 00 00 00 00 01 00 3c 05 a0 00 00 00 00 50

Set CapacityLimit to 300 persons

be 01 03 00 03 04 00 00 00 00 01 00 0a 05 a0 01 2c 00 00 50

Unconfirmed Uplinks

be 01 03 00 03 04 00 00 00 00 00 00 0a 05 a0 00 00 00 00 50

Change Application Payload to Extended

be 01 03 00 03 04 00 00 02 00 01 00 0a 05 a0 00 00 00 00 50



Configuration Payload Ports

Uplink Port 190
Downlink Port 190



Best Practice

PCR2 devices accept downlink messages to Port 190 in the above format.

After sending the downlink to Port 190 it might take up to the Interval Time before PCR2 receives the data. (PCR2 are Class A devices)

As soon as the device received a proper Configuration Payload it parses the values and restarts with the new settings. Join procedure will start again and you should get the same Configuration Payload you sent before.

Note: Byte 0-6 are read only ROM values and cannot be changed

How to generate the Configuration Payload

You can use a config string sent by the device after joining the network and modify it manually. You could also use the PCR Setup tool to generate this string.

Keep track of your device settings

PCR2 devices are sending a uplink with this configuration string using Port 190. This is done at least once after devices joined the network.

Saving this information on your application server allows you to always know about your device settings.

Check Port and Payload Header in your decoder

Always check for port 190 prior to decoding a configuration payload. Additionally you could also check Bytes 0-2.


    // check for valid pcr2 config pl 
    if ( port == 190 && bytes[0] == 0xbe && bytes[1] == 0x01 && bytes[2] == 0x03 ) 
    {
        // decode it



    }


Find more example code in our public repository.