FAQ: General (Snape 1.0)

Q111What is the warranty period for Ackcio products?

• Hardware warranty: 1 year (limited)
• Software support: Up to 5 years from date of purchase

Q112What tools should be prepared before an onboarding session?

• Android device with the latest Ackcio Nimbus app (Google Play Store)
• Windows or Mac OS laptop with Wi-Fi capability, for Gateway configuration
• Separate device for the video call session
• Phillips screwdriver and test pen
• Fresh 3.6 V ER34615 D-Cell batteries: Tadiran or EVE, manufactured within 3 months

Q113Where can Nimbus 2.0 commissioning videos be found?

All node and Gateway commissioning videos are available at:

Nimbus 2.0 Commissioning Videos: Google Drive

Q114What case studies are available?

• Success stories: Please visit the Ackcio official website

Q115What is the battery connector part number for out-of-warranty node self-repair?

Clients may procure the following part at their own risk:

• Keystone Electronics Battery Connector: Digi-Key part no. 2175

Reference: Keystone 2175 battery connector on Digi-Key ↗

Q116How does battery consumption compare between nodes on separate Gateways?

Direct comparisons are inherently difficult. Key influencing factors include:

• Environmental conditions: temperature and humidity affect self-discharge rates
• PCBA component tolerances: minor manufacturing variations in passive components
• RF network load: nodes with more child nodes or weaker links consume more power

Q117How do I interpret spikes on some TM nodes and zero readings on others?

Spikes: Typically caused by brief external disturbances. The system emits an error code: not a zero, when a conversion failure occurs. These are stored in the error folder.

Zero readings: Inspect sensor wiring and connectivity. If persistent, contact Ackcio support at [email protected].

Q118What should be considered when scaling up an Ackcio deployment to 100+ sensors?

Key considerations for large-scale deployments:

• Plan multiple Gateways: each handles up to 50 nodes. Design node clusters to minimise cross-cluster RF interference.
• Stagger sampling rates: avoid all nodes triggering simultaneously to prevent mesh congestion.
• Plan repeater placement: for sites with obstacles or long distances, pre-survey repeater mounting points.
• Centralize data collection: use a common FTP/API endpoint to aggregate data from all Gateways.
• Standardise naming conventions: use consistent sensor codes and node names from the outset for clean data exports.

Q119How should the Ackcio system be integrated with a third-party monitoring platform?

Integration is supported via the following methods:

• API (HTTP/HTTPS POST): Real-time JSON push to any cloud endpoint or custom application
• FTP/FTPS: Periodic CSV file delivery to an FTP server
• Modbus TCP: Available upon request for SCADA/PLC systems

Q120How to prolong the lifespan of nodes and the Gateway?

• Install nodes inside IP66-rated polycarbonate enclosures: expose only the antenna
• For coastal sites: clean salt deposits from enclosures and hardware regularly
• Mount in elevated, sheltered positions: minimise direct rain and wind exposure
• Ensure continuous, stable Gateway power: prevent flash memory corruption

Q121Can I connect 8 sensors to an ANS4 node?

• Yes, but only if total power usage is within the limit. ANS4 supports up to 8 analogue channels = 8 sensors max
• All ports share one power supply (not per port)
• Power limit based on excitation voltage:
• 5V = Max Total Current 100mA
• 12V = Max Total Current 90mA
• 24V = Max Total Current 40 mA
• Example: 8 sensors x 10mA = 80 mA OK (5V) while 8 sensors x 20mA = 160mA Not OK (5V)

Q122Why does the Gateway (GW) only support 2.4 GHz WiFi and not 5 GHz?

The Gateway is equipped with a single external antenna (short black cylindrical antenna) that integrates two communication functions within one hardware unit:

• Cellular connectivity (via SIM card) for data transmission
• WiFi connectivity for:
• Accessing the Gateway hotspot (e.g. Access SNAPE for configuration)
• Connecting the Gateway to a local WiFi network for internet access

The WiFi module is designed to operate on 2.4 GHz only and does not support 5 GHz networks.

This is an intentional design choice to prioritise connection stability and reliability in real-world deployment environments:

• Improved signal range and penetration 2.4 GHz provides better coverage and performs more reliably through obstacles such as concrete, soil, and structural elements commonly found on site.
• Higher connection stability While 5 GHz offers higher data speeds, it is more susceptible to signal attenuation and dropouts. The Gateway transmits relatively small data packets, where stability is far more critical than bandwidth.
• Broader compatibility 2.4 GHz networks are more universally available across industrial and site environments, ensuring easier integration with existing infrastructure.
• Optimised antenna performance The combined cellular and WiFi functionality within a single compact antenna is optimised for consistent performance at 2.4 GHz, ensuring reliable operation across both communication modes.

The Gateway is purpose-built for robust and dependable connectivity, rather than high-speed data transfer. Supporting 2.4 GHz WiFi ensures stable communication, which is essential for continuous and reliable data delivery in field conditions.

Q123How often should I back up my Gateway's project configuration or Gateway Logs, and why is it important?

We recommend downloading and saving your Gateway's project configuration file at least once every 3 to 6 months, or immediately after any significant changes to your project setup (e.g., adding/removing Nodes, updating sensor configurations).

The project configuration file is stored on your Gateway's Snape server and contains the settings of all commissioned Ackcio Nodes and sensors. In the event of a Gateway hardware failure, loss, or theft, where Snape becomes completely inaccessible, this backup file allows you to restore your entire project onto a replacement Gateway within seconds, without the need to recommission every Node on site.

To export your project configuration:

1. Connect to your Gateway's Wi-Fi network or remote.it link.
2. Click Export Project Configuration under the “Projects” tile.
3. A .zip file containing your project configuration will be saved to your device.

To restore on a new Gateway:

1. Connect to the new Gateway's Wi-Fi network or remote.it link.
2. Click Import Project Configuration under the “Projects” tile and select the previously saved .zip file.
3. The project will be restored and your Nodes will automatically reconnect and resume sending data to the new Gateway.

Q125Can I use Gray/Fibreglass antenna on the latest GW 3.6 and onwards?

No. GW 3.6 and onwards can only run on short black antennas. Using the older Gray/Fibreglass antenna which is meant for GW 3.5 and older versions would introduce radio disruptions and cause data loss on the latest GW 3.6 and onwards.

Q126What does the EXT/BAT switch on the BEAM-DG node do?

The EXT/BAT switch controls which power source is used to power the connected sensor:

• BAT selected: the sensor is powered by the internal D-Cell battery.
• EXT selected: the sensor is powered directly by the external power supply.

There is no automatic fallback between the two. If the selected power source is absent or interrupted, the sensor will not power up, even if the other source is available.

Q127Can the external supply voltage on a BEAM-DG be monitored via Snape?

Not directly. The external power supply passes through an internal converter that steps it down to match the battery voltage range. The value shown on the Snape dashboard reflects this converted voltage, not the raw external supply input. To verify the external supply voltage, measure it directly at the input terminal using a multimeter.

Q129How long can the HPC sustain a node which is turned ON if there is no D-Cell battery fitted?

The HPC can sustain the node for approximately one week without a D-Cell battery installed. After this point, the HPC will begin to deep discharge.

Q130How long can a node (turned ON) last if it has a D-Cell fitted but no Gateway to connect to?

A node can last approximately 1 to 2 months when powered on with a D-Cell fitted but without a Gateway configured. During this time, the node continuously attempts to find and connect to a Gateway, which drains the D-Cell faster than normal operation. Once the D-Cell depletes, the HPC will begin to discharge, if left long enough, this risks deep discharge below 2.5V.

Q131How long can a Gateway run on its D-Cell battery alone, and what happens during this time? (Applies to GW 3.5 and below, and GW 3.7 onwards, does not apply to GW 3.6)

When the Gateway loses its main power supply but has a D-Cell battery fitted, the D-Cell powers the Gateway’s radio module to maintain communication with nodes. This is referred to as low power mode.

While in low power mode:

• ✅ Sensor data continues to flow in from nodes as normal.
• ❌ Node metrics and network metrics will NOT be transmitted.
• ❌ Snape access via Gateway hotspot or remote access is unavailable.
• ❌ FTP/API uploads will not occur.

All of the above resume automatically once main power supply is restored.

A Gateway can sustain low power mode on its D-Cell for up to approximately 3 months.

Q132Why is Sweep Mode selection important when commissioning a VW sensor (VWS1/VWS8), and how should I choose it?

Sweep Mode selection is mandatory and must be based on the sensor’s datasheet, never left on a default or guessed value.

• Check the sensor datasheet for its rated operating frequency (Hz) range.
• Select the narrowest Sweep Mode that fully covers that range, do not default to a wide/universal sweep unless the range is unknown.
• Example: A strain gauge with an operating range of 700 to 900 Hz should use Sweep H (400 to 1200 Hz), not Sweep E (400 to 5000 Hz).

Q133When should I set the Wheatstone Bridge adaptor switch to HIGH or LOW?

The setting depends on your sensor’s output, shown on the sensor datasheet as mV/V (listed as “sensitivity” or “rated output”).

• LOW: Sensors up to 5 mV/V. Most load cells fall here (1 to 3 mV/V).
• HIGH: Sensors from 5 to 50 mV/V, such as some pressure transducers.
• Above 50 mV/V: Not supported. Please contact Ackcio.

Why it matters:
The sensor’s signal is very small, so the adaptor boosts it before the node reads it.

• LOW: Strong boost, for sensors with a small signal.
• HIGH: Lighter boost, for sensors with a bigger signal.

If set incorrectly:

• Small-signal sensor on HIGH: Still works, but readings are less precise.
• Big-signal sensor on LOW: The signal is boosted too much and the reading gets stuck at its maximum.