Link Search Menu Expand Document

Dragino - LTC2-LB

The LTC2-LB is a LoRaWAN Waterproof Outdoor Temperature Sensor with 2 external PT100 Probes.


Table of contents

  1. Specifications
  2. Documents/Links
  3. Ordering Info
  4. Button Actions, Modes and LED States
  5. Adding the Device to TTN
  6. Optional Settings
    1. Change sampling interval
      1. Examples
  7. Payload Decoder

Specifications

  • indoor/outdoor device
  • Attention, LTC2-LB doesn’t include temperature sensors, you need to purchase them separately
  • Price LTC2-LB ca. CHF 66.- (07.04.2025) without sensors
  • 2 External Temperature Sensors PT100 (support 3-wire), Cable Length 2m
    • DR-SI – Standard IP68
      • Price each ca. CHF 15.- (07.04.2025)
        • -60 … +200 [°C], Class A, IP68
    • DR-LT – Low Temperature
      • Price each ca. CHF 16.- (07.04.2025)
        • -196 … +150 [°C], Class A, IP68
    • DR-HT – High Temperature
      • Price each ca. CHF 66.- (07.04.2025)
        • -70 … +450 [°C], Class A, IP68
    • DR-FSA – Food Safety Type
      • Price each ca. CHF 66.- (07.04.2025)
        • -40 … +260 [°C], Class A, IP68
    • DR-FT – Flat Type - ideal to mount on pipes
      • Price each ca. CHF 15.- (07.04.2025)
        • -60 … +200 [°C], Class A, IP68
  • Power Supply: 1 built in 8500mAh Li-SOCI2 battery
    • Expected life time: depending on usage, 5 … 10 years
  • LoRaWAN version: 1.0.3
  • LoRaWAN device class: A
  • Protection: IP66
  • Operating Temperature: -40 … 85°C
  • Size: 145 × 102 × 51 mm
  • Weight: 271 g


Ordering Info


Button Actions, Modes and LED States

Device Overview

The LTC2-LB has two operating modes:

  • In Deep Sleep Mode, which is the default mode used for storage and shipping, the device does not perform any LoRaWAN activity to conserve battery life.
  • In Working Mode, the device joins a LoRaWAN network and sends sensor data to the server.
  • Between each sampling, transmission, and reception cycle, it enters STOP mode (also known as IDLE mode), which consumes the same low power as Deep Sleep Mode.

The ACT push button on the device is used to switch between the above mentioned modes.

ActionDescriptionLED Status
Press and hold 1–3sSends uplink if joined. BLE is active for configuration.Blue LED blinks once
Press and hold > 3sActivates device. Starts join procedure. BLE is active regardless of join result.Green LED blinks fast 5 times, then solid green for 5 seconds
Fast press 5 timesDeactivates device. Enters Deep Sleep Mode.Red LED solid on for 5 seconds

Adding the Device to TTN

  • The JoinEUI, App EUI and the DevEUI should be on a sticker on the cardboard box.
  • Before a device can communicate via “The Things Network” we have to add it to an application.
  1. Create a new application
  2. Under End devices in the application click (+) Register end device
  3. Under Input method select Enter end device specifics manually
  4. Under Frequency plan select Europe 863-870 Mhz (SF9 for RX2 - recommended)
  5. Under LoRaWAN version select 1.0.3
  6. Under JoinEUI enter the App EUI from the App and press Confirm
  7. Enter as well the DevEUI and the AppKey from the App
  8. Set an end-device name
  9. Press Register end device
  10. Add the payload formatter from below, either to the device itself or if all devices in the app are from the same type, to the application
  11. Switch on the device, see above table
  • After Configuration, the device restarts automatically and tries to join the network
  • Now the device should join the network and you can see the incoming telegrams in the Live data section

Optional Settings

Change sampling interval

To change the sampling interval, you have to send the device configuration telegrams (Downlink-Messages) The time interval in minutes at which the sensor queries the current values.

  1. In the TTN Console on the device view, select the device and change to the tab Messaging, select Downlink
  2. Change the FPort to 2
  3. Copy/paste the payload, e.g. 01000258 into the Payload field to set interval to 10 minutes
  4. Press Send
  5. In the Data tab you should now see the scheduled telegram. The device only receives downlink data after a transmission. Therefore start a transmission by pressing the button on the back of the sensor (push once short, green led will illuminate)

Examples

‘0100’ is an identifier, the rest represents the sampling interval in hex

  • 5 Minutes Interval: ‘0100012C’ (300s in hex are ‘012C’)
  • 10 Minutes Interval: ‘01000258’ (600s in hex are ‘0258’)
  • 15 Minutes Interval: ‘01000384’ (900s in hex are ‘0384’)
  • 60 Minutes Interval: ‘01000E10’ (3600s in hex are ‘0E10’)

Payload Decoder

function decodeUplink(input) {
  const port = input.fPort;
  const bytes = input.bytes;
  const data = {};

  function toTemperature(byteH, byteL) {
    const value = parseFloat(((byteH << 24 >> 16 | byteL) / 10).toFixed(1));
    return (value > 2000 || value < -2000) ? 0 : value;
  }

  if (port === 2) {
    data.battery_volt = (bytes[0] << 8 | bytes[1]) / 1000;
    data["temperature_degrC@channel1"] = toTemperature(bytes[3], bytes[4]);
    data["temperature_degrC@channel2"] = toTemperature(bytes[5], bytes[6]);
    return { data };
  }

  return {
    errors: ["Unsupported FPort"]
  };
}