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
  • Basic Overview
  • Key advantages of LoRa over WirelessHART
  • Use Case Example
  • Where to use WirelessHART
  1. LoRa & LoRaWAN
  2. LoRa

LoRa vs WirelessHART

PreviousLoRaNextLoRa vs BLE

Last updated 1 year ago

Basic Overview

WirelessHART is a protocol designed specifically for industrial automation, part of the HART (Highway Addressable Remote Transducer) family. It is known for its reliability and security in industrial environments and has a typical range for dense sites of 30 meters. On the other hand, LoRa is a wireless communication technology designed for long-range, low-power communication. It's known for its wide coverage area and low energy consumption with a typical range on dense sites between 1 and 1.5 kilometers.

Key advantages of LoRa over WirelessHART

  • Longer Range: LoRa offers significantly longer transmission ranges compared to WirelessHART. This makes LoRa more suitable for applications requiring wide-area coverage, such as large industrial complexes or remote monitoring.

  • Lower Power Consumption: LoRa is highly optimized for low power consumption, translating to longer battery life for sensors like the NEON Vibration Sensor. This is crucial for reducing maintenance and operational costs. In practice, the difference is about 2 to 3 times longer battery life for LoRa devices.

  • Scalability: LoRa networks can easily scale up to accommodate a large number of nodes, making it ideal for extensive sensor networks.

  • Cost-Effectiveness: LoRa devices and network infrastructure are generally more cost-effective than those for WirelessHART, making it a more economical choice for large-scale deployments. This is mainly due to the lower infrastructure cost and the far lower amount of needed gateways.

Use Case Example

If we take a known big refinery as an example at the moment of writing they operate 7500 LoRa devices with 3 gateways. If we use the formula from to estimate the number of gateways with a similar amount of WirelessHART sensors we would need more than 70 gateways just to support the capacity provided by 3 LoRa gateways.

Where to use WirelessHART

All control or safety-related use cases. WirelessHART is suitable for critical applications where real-time data transmission and high reliability are of utmost importance. Therefore, WirelessHART is recommended when the cost of downtime outweighs the cost of the monitoring.

Emerson Engineering Guide - IEC 62591 WirelessHART