An industrial wireless sensor loses data intermittently when the radio path or the data path degrades faster than the system’s margin can absorb: moving or new metal equipment blocking the path, multipath cancellation, a gateway placed inside a metal cabinet or at the edge of coverage, interference from other radio equipment, weakening batteries or unstable power, or congestion and timeouts in the network between gateway and platform. The first safe check is pattern analysis — timestamps of the missing data against site events (shift patterns, vehicle movements, machine startups). Radio work at height or near energized equipment belongs to qualified personnel.
Key Takeaways
- Intermittent loss means marginal margin, not hard failure. The link works most of the time and collapses under specific conditions — the goal is to name the condition.
- Timestamps are evidence. When data gaps correlate with forklift routes, shift changes, door positions or machine states, the cause is physical obstruction or interference, not the sensor.
- Gateway placement decides most of the coverage. A gateway in a metal enclosure, behind equipment, or equidistant-from-everything-but-close-to-nothing cannot be fixed at the sensor end.
- Power problems masquerade as radio problems. A battery whose voltage sags in cold weather or under transmission load resets or skips reports — check power trends before repositioning antennas.
- Collect before changing. Link-quality readings, RSSI where the system reports it, packet-loss statistics and gateway logs turn guesswork into a diagnosis.
Symptom Definition
This article covers intermittent gaps in the data stream of wireless sensor nodes:
- Periodic gaps — regular missing reports from one node;
- Correlated gaps — losses at specific times or site events (vehicle movement, machine startups, shift patterns);
- Multi-node gaps — several nodes lose data together;
- Recovery-after-reboot gaps — loss ends when gateway or node restarts.
Permanent loss from a single node (never reporting since installation) is a commissioning/coverage topic — covered in the wireless planning guide (wireless sensors and gateways planning guide) — not an intermittent-fault diagnosis.
Cause Table
| Cause category | Why it creates the symptom | Safe check | Corrective direction | Technician required? |
|---|---|---|---|---|
| Metal obstruction (moving) | Forklifts, cranes, trolleys and moving machinery block the path during movement; the link drops while the obstruction passes | Correlate loss timestamps with vehicle/equipment movement logs | Reroute the path (relocate node/gateway); add a repeater per system design; raise antenna height | Yes for work at height |
| Metal obstruction (new/static) | Installed equipment, racking or stock piles changed since the radio survey | Walk the path with the site layout; compare against the commissioning layout | Relocate antenna/gateway; re-run the coverage assessment | Yes |
| Multipath cancellation | Reflections combine out of phase at specific positions — small position changes cause big link changes | Note whether moving the node or gateway slightly (test position) changes link quality dramatically | Reposition for a primary-path-dominant geometry; antenna placement per system documentation | Yes |
| Gateway placement | Gateway inside a metal cabinet, low behind equipment, or beyond the coverage edge for far nodes | Compare gateway position against the coverage plan; check per-node link indicators in the system | Relocate the gateway centrally and elevated; the planning guide (https://www.kjt-sensors.com/show-27177.html) covers placement principles | Yes |
| RF interference | Other radio systems (WiFi crowding, other industrial links) or inverter noise raise the noise floor | Check whether losses correlate with specific equipment or network activity times; review the RF environment per site practice | Channel/frequency planning per system documentation; physical separation of antennas | Yes |
| Node battery / power | Cold weather, aging or high transmission rates sag the supply below the radio’s operating point — skipped reports or resets | Review battery voltage trend against loss times and temperature; check reporting interval vs. battery design life | Replace batteries; lengthen reporting interval within monitoring needs; review power budget | No for battery swap in accessible, de-energized locations |
| Reporting interval / congestion | Interval too aggressive for the radio environment, or many nodes contending — retries collide and reports time out | Compare configured reporting intervals and node count against the system’s documented capacity | Stagger reporting intervals; reduce rate; add gateways per capacity guidance | Yes for configuration |
| Gateway power / network path | Gateway resets, Ethernet/cellular drops, or platform timeouts interrupt all nodes behind that path | Check whether multi-node gaps share one gateway and one timestamp cluster | Stabilize gateway power; verify network path (cabling, router, cellular coverage); add buffering if the system supports it | Yes — network work |
Diagnostic Sequence (Least Invasive First)
- Build the loss timeline. Export the data-gap timestamps for affected nodes over at least a week. Patterns (clock-time clusters, event correlation, single vs. multi-node) direct everything after.
- Classify the pattern. Single node → node-side (power, local obstruction). Multiple nodes on one gateway → gateway power/network or coverage. All nodes at once → gateway or platform path.
- Correlate with site events. Overlay the timeline with shift patterns, vehicle/equipment activity, door positions, temperature records.
- Review power trends. Battery voltage or supply trends against the loss times — power sag is invisible from the radio side.
- Check link indicators in the system. RSSI/link-quality readings, retry counts and packet statistics where the platform reports them; compare far nodes against near nodes.
- Walk the path. Compare the current site layout (new equipment, racking, stock) against the commissioning layout; physically inspect antenna and gateway positions from safe locations.
- Review configuration. Reporting intervals, node count per gateway, channel plan — against the system’s documented capacity and planning guidance (wireless sensors and gateways planning guide).
- Escalate with the evidence pack. Timeline, correlation, link statistics and layout changes — the information below — for a structured RF/site review before relocating hardware.
Conditional Corrective Actions
- If losses correlate with vehicle or machine movement → the path crosses a moving obstruction: relocate the node or gateway for a clear primary path, or add a repeater per system design.
- If one node repeats while neighbors are stable → suspect that node’s battery and local environment first; repositioning the gateway for one marginal node is the last step.
- If all nodes behind one gateway drop together → gateway power, mounting position or its backhaul network (Ethernet/cellular) — not the sensors.
- If losses grow in cold months → battery capacity at low temperature; review power budget and reporting interval.
- If the system reports heavy retries at one timeslot → reporting-interval congestion: stagger intervals per the system’s guidance.
Replacement and Reselection Criteria
Re-plan rather than repeatedly repair when:
- the site has physically changed such that no placement achieves stable coverage — re-run the planning survey per the wireless planning guide (wireless sensors and gateways planning guide);
- node density exceeds the documented gateway capacity — add gateways, not antennas;
- battery life at the required reporting rate cannot meet maintenance cycles — review the wired-vs-wireless trade-off in the retrofit guide (wired-vs-wireless retrofit comparison);
- monitoring needs (latency, reliability class) have grown beyond the installed system’s design.
Information to Send KJT Sensors Support
- System description: node types, count, gateway count and positions, topology;
- The loss timeline (per-node gap timestamps, at least one week) and its correlation with site events;
- Link-quality/RSSI/packet statistics from the platform, if available;
- Site layout sketch: node and gateway positions, metal structures, new equipment since commissioning;
- Battery/power trends for affected nodes; reporting intervals configured;
- Gateway power and backhaul description (Ethernet/cellular).
Frequently Asked Questions
Can moving metal equipment block the signal?
Yes — this is the signature intermittent cause in plants. A forklift, crane, transfer car or even moving stock can fully obscure a radio path for the seconds it takes to pass; if the node’s report lands in that window, it is lost or delayed. The evidence is timestamp correlation: gaps that line up with vehicle and equipment movement logs. The fixes are geometric — reroute the primary path, elevate antennas, or add a repeater per the system design — not configuration.
How does gateway placement affect reliability?
Decisively. The gateway is one position serving many paths: inside a metal cabinet it is effectively shielded; low behind equipment it collects obstructions; at the extreme edge of the network its far nodes operate with no margin. Central, elevated placement with clear primary paths to the node population is the planning rule — the wireless planning guide (wireless sensors and gateways planning guide) covers placement, capacity and survey practice for a full design.
What logs or timestamps should be collected?
Four sets: (1) per-node data-gap timestamps over at least a week; (2) site event logs for the same period — vehicle/equipment activity, shift patterns, temperature; (3) link-quality indicators the platform provides — RSSI, retry counts, packet statistics; (4) configuration records — reporting intervals, channel plan, node-to-gateway assignment. Together these convert “it loses data sometimes” into a diagnosis most of the time.
Is it the battery or the radio?
Check the power trend before touching antennas. A battery that sags under transmission load or in cold weather causes skipped reports and resets that look exactly like radio loss. If battery voltage dips align with the data gaps, the fix is power (replacement, interval lengthening, power-budget review); if voltage is flat through the gaps, continue with the radio-path investigation.
Conclusion
Intermittent wireless data loss is a margin problem with a nameable trigger. Build the timeline, classify single-node vs. gateway-wide, correlate with site events, verify power trends, then walk the radio paths against the current layout. Gateway placement and moving-metal obstruction dominate the cause list; batteries masquerade as radios. Collect the four log sets before relocating anything — and re-plan formally when the site has outgrown the original coverage design.
Sources
- KJT Sensors, Wireless Sensors category (wireless sensors, gateways, measurement and control software; star/chain network topologies; manufacturer-stated) — https://www.kjt-sensors.com/list-wxcgq.html (verified 2026-10-10)
- KJT Sensors, Service & Support — https://www.kjt-sensors.com/list-services.html (verified 2026-10-10)
- KJT Sensors internal category knowledge base: wireless sensors — version current at drafting
- General industrial radio practice (path loss, multipath, interference, network capacity; no third-party claims)
Contact Technical Support
Send your site layout, point count and loss pattern via the KJT Sensors service page — include the gap timeline and any link-quality statistics, and a wireless application engineer will help separate coverage, interference and power causes and propose the re-placement or re-plan.
https://www.kjt-sensors.com/
KJT Sensors