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
  • 1. Assess the battery
  • 2. Check the activation procedure
  • 3. Verify the LoRa keys
  • 4. Corroborate LoRa coverage
  1. How-to
  2. General

How to troubleshoot a NEON device not connecting to the network

PreviousGeneralNextHow to fix a bad connection

Last updated 10 months ago

Like any wireless device, NEON devices using LoRa can experience connectivity issues that may disrupt their operation. Such issues can arise from various factors, including interference, lack of coverage, or configuration errors. If the activation procedure fails repeatedly, it is essential to troubleshoot systematically. Follow these steps to identify and resolve the problem:

1. Assess the battery

Ensure that the device has a functioning battery. If the device's LED doesn't turn on upon activation attempt, an empty battery can be the cause of the issue. Follow the steps outlined on .

2. Check the activation procedure

Check that you are following the correct steps of the activation procedure. This varies for every product, refer to the product manual of your device to verify the activation steps.

3. Verify the LoRa keys

Errors while introducing the LoRa keys in the LoRa Network Server (LNS) are common. Ensure that the keys being used match the ones provided by TWTG. For more information refer to the article on .

4. Corroborate LoRa coverage

Lack of sufficient LoRa coverage can cause the device to limit or even stop operation. First, try to get the device closer to the gateway or with a direct line of sight. Second, review the data frames passing through the gateway for the messages being sent upon activation (further details available in the communication protocol specific to the device being used). Third, check the gateway latency. If the gateway's latency is too high the device won't be able to receive the confirmed message to proceed with the activation sequence (applicable to the devices that require such confirmation as defined in the communication protocol).

The communication protocol for every device and how to identify it is available in the section

how to replace a battery
how to identify the keys
Communication Protocol