PCR2 Configuration Payload V2

This document describes version 2 of the PCR2 Configuration Payload

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

Configuration Payload Format

Byte Property escription Uplink Values Downlink Values
0 DeviceType 00: PCR2-IN
01: PCR2-OD
02: PCR2-R
03: PCR2-T
00-03 ignored (*)
1:3 FirmwareVersion 0x030200 = V3.2.0 030400-0304ff ignored (*)
4 OperatingMode 00: Timespan
01: Not Zero
02: Trigger
00-02 00-02
5 PayloadType 00: ELSYS
01: Cayenne LPP
00-01 00-01
6 UplinkType 00: Uncofirmed
01: Confirmed
00 or 01 00 or 01
7:8 UplinkInterval 1-1440 Minutes 0001-05a0 0001-05a0
9:10 LinkCheckInterval 1-1440 Minutes, 0 = No LinkChecks 0000-05a0 0000-05a0
11:12 HoldoffTime 0-600s 0000-0258 0000-0258
13 RadarSensitivity 10-100% 0a-64 0a-64

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

Configuration Payload Ports

Uplink Port 190
Downlink Port 190



Best Practice

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 (bytes.length == 14 && bytes[0] != 0xbe) {
    {
        // decode configuration payload v2



    }


Find more example code in our public repository.