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
  • Step 1: Identify the Problem
  • Step 2: Check Sensor Placement
  • Step 3: Inspect the Gateway
  1. How-to
  2. General

How to fix a bad connection

LoRaWAN (Long Range Wide Area Network) sensors are commonly used in IoT applications for their ability to cover long distances while consuming minimal power. However, connectivity issues can sometimes arise. This guide provides practical steps to help you troubleshoot and fix a bad connection in LoRaWAN sensors.

Step 1: Identify the Problem

Start by understanding the specific issue you're facing. Common connectivity problems include:

  • Intermittent Connectivity: The sensor occasionally disconnects.

  • No Connectivity: The sensor fails to connect to the network.

  • Weak Signal Quality: The sensor has a poor signal, causing data loss or delays.

Step 2: Check Sensor Placement

  • Distance from Gateway: Ensure the sensor is within the optimal range of the gateway. While LoRaWAN sensors can cover long distances, obstacles such as buildings and terrain can affect connectivity.

  • RRSI and SNR: The average RSSI and average SNR, which are reported in the device status messages of the NEON sensors, can help identify a bad connection. The general threshold for RSSI is -120 dBm but a practical range where communication is generally possible is around -80 and -100 dBm. The SNR on the other hand, is recommended to be higher than -15 dB with a general threshold of -20 dB. The higher these values, the better for communication.

  • Obstructions and Interference: Physical barriers like walls, metal structures, and trees can interfere with the signal. Try relocating the sensor to an area with fewer obstructions and, if possible, line of sight with the gateway.

Step 3: Inspect the Gateway

  • Gateway Placement: Like sensors, gateways should be placed optimally with minimal obstructions.

  • Gateway Configuration: Ensure the gateway is configured correctly to communicate with your sensors. Verify network server settings and frequency plans.

  • Network Capacity: Ensure the gateway is not overloaded with too many devices, as each gateway has a limit to how many sensors it can handle simultaneously.

  • Transmission latency: verify the gateway latency, latencies higher than 1 second can impede the sensor from activating or sending confirmed messages.

  • Evaluate LoRaWAN coverage: consider that an additional gateway on-site can help improve the overall network quality.

PreviousHow to troubleshoot a NEON device not connecting to the networkNextHow to replace a battery

Last updated 10 months ago