Current plan
M-01 running
- Energy over 30 min
- 31.1 kWh
- Peak power
- 64.7 kW
Hardware / Outdoor LoRaWAN Gateway
Outdoor LoRaWAN Gateway
Aggregate LoRaWAN sensor data across outdoor sites. A pole-mounted enclosure for agriculture, buildings and utilities.
Outdoor LoRaWAN Gateway
Details and scope
Details are based on supplier reference images. Confirm the model, specifications, included accessories and AIoT TH Cloud integration before quotation.
- Chipset
- Semtech SX1302
- Channels
- 8-channel LoRaWAN
- Enclosure
- IP67 · Outdoor
- Development
- Node-RED · Python
- Data path
- LoRaWAN sensor → Gateway → Network Server → Application
- Before ordering
- Confirm variant, firmware, accessories and destination integration
- Reference receive sensitivity
- Up to −141 dBm, as stated in the supplier image
Interface and feature references
More images and details
Suitable device connections
For distributed sensors and sites where cabling is difficult.
- LoRaWAN sensors using the gateway’s frequency variant
- Temperature, humidity or environmental measurements supported by each sensor
- A network server and matching sensor payload decoder are required
Installation preparation
Have the site owner confirm power, installation position and networking before selecting accessories.
- Survey pole placement, maintenance access and the environment
- Confirm power, uplink and included mounting accessories
- Test packet reception and decoded values from actual sensors
Software and delivery scope
Confirm the selected frequency variant, network server and platform integration for each project.
- Exact variant, firmware and preinstalled software
- Antennas, cables, power supply and mounting parts specified in the quotation
- Agreed cloud setup, testing and handover documentation
FACTORY APPLICATIONS
From a site problem to a practical system
Illustrative system designs with equipment, data, responsible teams and project conditions. These are not customer case studies.
DIGITAL TWIN · SIMULATED
Simulated digital twin: site, equipment and events in one view
This simulated digital twin is a model running in your browser. It does not mirror a PLC or customer site and does not control equipment.
Loading 3D map…
Live (simulated) · 08:00:00
Illustrative 3D layout, not surveyed coordinates. Scene labels show values from the simulated twin. Select equipment on the scene or in the twin tree.
Total power62.0 kW
M-02 temperature46.0 °C
M-02 vibration2.10 mm/s
WHAT-IF · SIMULATED
Current plan vs alternative · next 30 simulated minutes
Alternative
M-01 stopped
- Energy over 30 min
- 17.4 kWh
- Peak power
- 36.2 kW
Computed from the browser simulation to compare choices; not a prediction for a real site.
Inspection and command history
Select a scene device, then inspect or control it
Data path
PLC / Meter → Modbus TCP / RS485 → Gateway → MQTT TLS :8883 → Monitor
CCTV uses IP over PoE / NVR independently of LoRaWAN. This scene is illustrative and has no live video.
Operator view
Connect power readings and machine states to site locations for maintenance inspection.
ILLUSTRATIVE SYSTEMMonitor pumps, tanks and distributed measurement points
Example system: factory water tanks and pump stations
Give teams the latest readings, update times and connectivity context before deciding which location needs an on-site check.
This illustrative site has a tank and pump stations in separate locations. Wired devices may use an industrial gateway. LoRaWAN sensors need a compatible gateway, network server and payload decoder before data reaches the agreed application.
Problems and practical approaches
Staff travel to each point to check level or pressure
Routine visits take time and may miss events between inspections
Approach · Select suitable sensors and connectivity, group readings by station and retain appropriate physical inspection routines
A value remains visible after the device disconnects
Users may mistake an old reading for the current condition
Approach · Display timestamps and connectivity, distinguishing threshold events from missing data
No one is clearly responsible after an alert
Data exists without an investigation and coordination process
Approach · Assign station owners, recipients and checking procedures, then test them with the actual team
Equipment and components
- Level, pressure or flow sensors selected for the task
- A wired gateway or LoRaWAN system suited to the sensor network
- Site-appropriate power, mounting and uplink equipment
- Cloud station views with scoped history and notifications
Data to monitor
- Level, pressure, flow or other values exposed by the equipment
- The last update time for each point
- Gateway connectivity and data completeness
Data journey
- Sensors / meters
- Wired or LoRaWAN + network server
- Available site uplink
- Cloud stations
- Operator review
Workflow and responsibilities
Survey installation points
Utilities and IT
Identify stations, power, access, antenna positions and connectivity constraints
Connect sensor readings
Installer
Verify interfaces or frequency plans and decode values into correct units
Test continuity
Site team
Check actual readings, disconnection and recovery under an approved site test plan
Review values and time
Station operator
Read values together with update times; do not treat stale values as current evidence
Notify and inspect
Incident owner
Identify the event and coordinate an on-site check; use approved procedures for pump control
Review site maintenance
Utilities manager
Use history to support inspection planning and record network or equipment issues
How each factory team benefits
Utilities
Prioritize checks using missing-data and measurement context by station
Maintenance
Prepare site visits with relevant readings and timestamps
IT and networking
Separate sensor acquisition issues from uplink or access problems
Multi-site operators
Coordinate using consistent station names and ownership rather than verbal descriptions alone
Who this is suitable for
- Factories with distributed tanks, pumps or utility systems
- Sites where suitable power and a data uplink can be provided
- Teams with assigned recipients and inspection capacity, without replacing safety controls with cloud monitoring
Acceptance checks
- Readings and units match the actual measurement point
- Operators can distinguish stale values during disconnection
- Alert recipients can identify the station and follow the agreed check procedure
DETAILS & PLANNING
Check the path from sensors to the application
The gateway is one part of a LoRaWAN network
A deployment also needs sensors using the matching frequency plan, a network server and a decoder that translates payloads into useful units. Images showing many nodes do not guarantee capacity in every environment. Assess reporting intervals and site radio conditions.
- Confirm gateway and sensor frequency variants
- Prepare the required device-provisioning information
- Test payload decoding against actual measurements
Outdoor installation depends on the complete assembly
The reference image describes an IP67 enclosure. The installation must also account for cable glands, mounting, power and site protection requirements. Survey gateway and antenna placement in the actual area rather than assuming coverage from marketing material.
- Check pole mounting and maintenance access
- Confirm included power and uplink accessories
- Test reception at distant and obstructed locations
Systems related to this page
Review each system’s scope before opening it or using the example to plan your project.
Live public observations · Read-only
Flood Monitoring
View rain, water-level and road-water observations on a station map with timestamps and source attribution.
Demonstration with simulated data
Demo Center
Explore energy, machine monitoring and OEE examples with a 3D factory to understand data and workflows before planning a project.
Questions about this topic
Does it work with every LoRa sensor?
Do not assume LoRa and LoRaWAN devices are interchangeable. Confirm protocol, frequency plan, provisioning and payload format for each sensor model.
Are Node-RED and a network server included and configured?
Confirm the firmware and supplier bundle. The images describe reference capabilities; network-server setup and cloud integration must be specified for the project.
Choose hardware and software that work together
Start with your equipment and data points, then define the right site scope.