FAQ: Sensor errors and diagnostics
Snape 1.0 and Snape 2.0Version 1.1 · 6 November 2026KC-03-010
This guide is for Snape 2.0. Other versions: Standalone.
Q90What are Error Codes, and when are they generated?
Any sensor output value exceeding 60,000 is classified as an Error Code, indicating a valid reading could not be obtained. Error values are automatically routed to a dedicated error folder, keeping valid data clean.
Q91What should be done when values above 60,000 appear?
- No sensor connected → Verify sensor is physically attached to the affected port.
- Loose/incorrect wiring → Inspect and secure all cable connections.
- Faulty sensor → Move sensor to a known-working channel, trigger a live reading via Nimbus, and validate with the manufacturer's diagnostic tool.
Q92What causes intermittent error codes (not continuous)?
- Sensor not rigidly mounted: vibration induces harmonics and occasional spurious readings.
- Brief external electrical disturbance: causes a one-off spike; the system emits an error code rather than a zero value.
Q93What should be done if error codes have persisted continuously over multiple days?
- Check sensor mounting: confirm it is rigidly and correctly installed.
- Validate the sensor with the manufacturer's diagnostic tool.
- Inspect all cable connections for damage or incorrect pin assignments.
- If unresolved, contact Ackcio support at support@ackcio.com with a summary of the above findings.
Q94What are the specific error code ranges and meanings?
- 64,000 to 65,000: Node-level errors (e.g., 64413 = VW Sweep Band error)
All error values are stored separately in the error folder and never mixed with valid sensor data.
Q95What is the VW Sweep Band Error (Code 64413), and how is it resolved?
Caused by commissioning a new node to a Gateway running outdated Mesh firmware or Snape.
- Update the Gateway to the latest Mesh firmware and Snape software.
- Use the latest version of the Nimbus app.
- Optionally update node firmware.
- Recommission the VW node with the correct sweep range from the sensor's datasheet.
Q96What causes spikes on DG nodes?
DG node spikes are associated with error codes in the 64,000 to 65,000 range. These are stored in the error folder and do not affect the valid data stream. Isolated spikes from brief disturbances are normal; persistent spikes warrant wiring and mounting investigation.
Q97What is the maximum resistance supported by the VW module in Ackcio VW nodes?
180 Ω maximum.
Q98How should I diagnose a node that shows readings fluctuating wildly in Snape?
Systematic diagnosis steps:
- Connect to the node via Nimbus app and trigger a live reading, confirm whether the fluctuation appears in real time.
- Inspect sensor wiring for loose connections, damaged insulation, or incorrect cable routing.
- Check for nearby EMI sources (motors, generators, RF transmitters) that may be interfering.
- Temporarily move the sensor to a known-working node port and compare readings.
- If the issue follows the sensor, it indicates a faulty sensor, validate with the manufacturer's tool.
- If the issue follows the node port, it indicates a faulty channel, contact Ackcio support at support@ackcio.com.