TWTG Documentation
Service Desk
Starting Guide
Starting Guide
  • Introduction
  • LoRa & LoRaWAN
    • LoRa
      • LoRa vs WirelessHART
      • LoRa vs BLE
    • LoRaWAN
      • Infrastructure
  • Installation & Provisioning
    • Box Content
    • Installation
      • Pressure Gauge (PG)
      • Pressure Sensor (PS)
      • Temperature Sensor (TS)
      • Temperature Transmitter (TT)
      • Vibration Sensor (VB)
      • Contact Sensor (VS-CS)
      • Valve Sensor - Multiturn (VS-MT)
      • Valve Sensor - Quarter Turn (VS-QT)
    • Provisioning
      • 📄Step 1: Product manual
      • 🔑Step 2: Identify the keys
      • 💻Step 3: Add the device to the LNS
      • ⚙️Step 4: Encoder & Decoder in the LNS
      • 🟩Step 5: Activating the device
  • Data & Communication
    • Communication Protocol
    • Measurements & Messages
    • Schedules
    • Data Visualization
  • Configuration
    • Online Configurator
    • Configure a Device
  • How-to
    • General
      • How to troubleshoot a NEON device not connecting to the network
      • How to fix a bad connection
      • How to replace a battery
    • Pressure Gauge (PG)
      • How to configure event triggers
    • Pressure Sensor (PS)
      • How to configure event triggers
    • Temperature Sensor (TS)
      • How to configure event triggers
      • How to change the configuration of the device from using FSB1 to FSB2 in US915
      • How to configure the frequency of measurements and messages
    • Temperature Transmitter (TT)
      • How to configure event triggers
      • How to use a temperature element different from type K
      • How to use a PT100/RTD
      • How to configure the frequency of measurements and messages
    • Vibration Sensor (VB)
      • Communication Protocol v2 & v3
        • How to obtain the FFT data
        • How to have an FFT for threshold values without periodic messages
        • How to configure event triggers
      • Communication Protocol v4
        • How to Get Started with the New Features of the NEON Vibration Sensor v4
      • How to configure the frequency of measurements and messages
      • How to replace the sensor or probe
      • How to debug a not connected sensor
      • How to debug a not paired sensor
      • How to enable Hanning Window
  • General Information
    • Available Regions
    • LoRaWAN Region
    • Hazardous Locations
    • Device Maintenance
    • Support & Troubleshooting
    • FAQs
Powered by GitBook
On this page
  • NEON TT Protocol v2
  • NEON TT Protocol v3
  • NEON TT Protocol v4
  1. How-to
  2. Temperature Transmitter (TT)

How to configure the frequency of measurements and messages

PreviousHow to use a PT100/RTDNextVibration Sensor (VB)

Last updated 8 months ago

One of the most common configurations a user would like to change is the frequency of the measurements taken by the sensor and the frequency of the messages the end user receives. To accomplish this, the user must generate a downlink (which can be done using the ) and send it to the device via their LoRa Network Server (LNS).

NEON TT Protocol v2

On the Application Configuration tab, the field Temperature Measurement Interval Seconds defines how often the sensor takes a measurement, and the field Periodic Event Message Interval establishes after how many measurements the transmitter sends data over LoRa.

Thus, the frequency of the messages is determined by Temperature Measurement Interval Seconds multiplied by Periodic Event Message Interval. For example, above the Temperature Measurement Interval Seconds is 900 seconds and the Periodic Event Message Interval is 16, which means that the frequency of the data messages will be 14400 seconds, equivalent to 4 hours.

NEON TT Protocol v3

On the Application Configuration tab, the field Temperature Measurement Interval Seconds defines how often the sensor takes a measurement, and the field Periodic Event Message Interval establishes after how many measurements the transmitter sends data over LoRa.

Thus, the frequency of the messages is determined by Temperature Measurement Interval Seconds multiplied by Periodic Event Message Interval. For example, above the Temperature Measurement Interval Seconds is 900 seconds and the Periodic Event Message Interval is 16, which means that the frequency of the data messages will be 14400 seconds, equivalent to 4 hours.

NEON TT Protocol v4

On the Sensortab, the field Measurement Interval Minutes defines how often the sensor takes a measurement, and the field Periodic Event Message Interval establishes after how many measurements the transmitter sends data over LoRa.

Thus, the frequency of the messages is determined by Measurement Interval Minutes multiplied by Periodic Event Message Interval. For example, above the Measurement Interval Minutes is 5 minutes and the Periodic Event Message Interval is 12, which means that the frequency of the data messages will be 60 minutes, equivalent to 1 hour.

On the Sensor tab, the user can also select the operating mode of the event messages. This can be:

  • extended: sends the maximum, minimum and average values of the measurements taken.

  • min_only: sends only the minimum value of the measurements taken.

  • max_only: sends only the maximum value among the recorded measurements.

  • avg_only: sends only the average of the measurements taken.

NEON configurator