Manual for WSNBM-AQUA | FW 1

• 1. Quick installation guide for WSNBM-AQUA
• 2. Maintenance for WSNBM-AQUA
• 3. Advanced guide for WSNBM-AQUA
• 4. Product Specifications for WSNBM-AQUA
• 5. Warranty for WSNBM-AQUA

1. Quick installation guide for WSNBM-AQUA

This manual is applied to the following products:

Item code	Hardware version	Firmware Version	Firmware released date	Change information
WSNBM-AQUA-1G10-IA WSNBM-AQUA-2G10-IA	1	1	10 June 2025	Initial firmware

1.1 Introduction

The WSNBM-AQUA is a cutting-edge NB-IoT and LTE Cat M1 data logger tailored for comprehensive water pipeline network monitoring. It includes pulse inputs, an RS485 Modbus RTU Master Node, and built-in pressure sensors. Designed for long-term performance, the device operates efficiently on one or two batteries, offering a lifespan of 5 to 10 years. With support for global frequency bands, it is an ideal solution for city water networks, industrial parks, smart utility systems, and various other applications.

1.1.1. The MQTT data logger system architecture

System components:

1. Aqua logger: publish the the data messages to the broker and subscribe request of configuration change messages from the application
2. MQTT broker: is the server that receives the data messages from the loggers then route them to the application. In addition, the broker also receives request of configuration change messages from the application and then route them to the logger
3. MQTT application: subscribe the data messages from loggers and publish request of configuration change messages to the logger

1.1.2. How to set up the MQTT system?

Please follow these steps:

• Configure on MQTT broker: the user, password, QoS, CA file, SSL
• Configure on the logger: MQTT configurations (host, port, user, password, CA file, SSL on/off, QoS, message retain), CAT M1/NB-IoT configurations (network category, frequency bands, RAT search sequence)
• Configure on the application: host, port, user, password, QoS, CA file
• Insert the CAT M1/NB-IoT SIM to the logger, then insert the batteries/power supply. The logger will publish the messages to the MQTT broker and then the broker will route the messages to the application

1.2 When does device publish the topic?

The device will publish the topic following cases to MQTT brokers:

Case 1: When device is power-up, the device will publish the first topic called START_UP. The payload will tell the user the full device configurations and device health statuses.

Case 2: In every interval time (pre-configured), for example, 24 hours, it will publish the topic called HEARTBEAT. The payload will tell the user the full device configurations and device health statuses.

Case 3: If users want to get the value of device configurations and device health immediately, user could force the device to publish the CONFIG-HEALTH-CHECK topic. The device could be forced by applying the magnet key in more than 5s.

Case 4: During the commissioning, testing, or calibration logger, the user can force the device to publish the topic to get the data immediately. This topic is called FORCE. The payload will provide data like raw measured value, scaled measured values, and device health. It can be forced by applying the magnet key on the reed switch in 1s;

Case 5: Then, in every interval time (pre-configured), for example, 10 minutes, it will publish the topic called CYCLE. The payload will tell the user the following data like measured values and device health. To change the cycle of data sending, you can change the value of the CYCLE_PERIOD parameter. 

Case 6 : If the application requests to change device configurations, the application will publish the CONFIG-REQUEST topic to the MQTT broker and the device subscribe the CONFIG-REQUEST topic. After that, the device will change the configuration as request in the CONFIG-REQUEST topic and publish CONFIG-RECEIPT topic.  The payload of CONFIG-RECEIPT topic contains the result of the configuration changes.

1.3 Default Configuration

Please refer to the END USER DEFAULT column in the memory map file at the section 1.9 Payload Document and Configuration Tables

1.4 Hardware overview

 

LED PRINCIPLE

	OFF	FLASHING
COM LED (Red)	Power-off OR sleep status	Operation status (measurement/data sending)
STT LED (Red)	Configuration port-off	Configuration port -on
ERR LED (Red)	Power Off or No Error	Hardware Error

1.5 Power supply

• Rechargeable battery:

• Use  2 x D-size battery 3.6V LiSOCl2 with 17Ah;

  Recommend to use SAFT LS33600 or equivalent from Tadiran.

Procedures to insert batteries

• Open the device upper housing by removing 4 screws

 

• Open the battery cover by removing a screw, then slide the cover upward slightly to move the cover out of the latch, then take out the cover

 

Note:

Hard slide the battery cover might result in broken the latch of the battery cover

 

• Unplug  power connector from the mainboard, and wait 5 minutes

   

  

• Insert batteries to the battery holder with right polarity

Note:

Wrong polarity might cause the device faulty

• Plug the power connector back
• Close the battery cover and device upper housing

1.6 What's in the Package?

1.7 Guide for Quick Test

Step 2: Configure on the logger the MQTT configurations (host, port, user, password, CA file, SSL on/off, QoS, message retain), CAT M1/NB-IoT configurations (network category, frequency bands, RAT search sequence) with offline tool and the template. 

Step 4: Connect RS485 Modbus RTU device to the logger

RS485 + wire (A label) of the cable to RS485 + of Slave device/meter

RS485 - wire(B label) of the cable to RS485 - of Slave device/meter

Plug M12 male connector of the cable to M12 female connector of the logger

Step 5: Connect pipes from the pressurized point on the pipeline to the pressure sensors on the logger

Step 6: Insert the batteries into the device. Please refer section 1.3 Battery for details

Step 7: After supplying the power, the device will publish topics to the MQTT broker. The application subscribes the topics and decode the payload to get measured values. Details of topic name and payload is at Section Section  Payload Document and Configuration Tables.

1.8 Installation and Wiring

1.8.1 Installation drawings

Dimension drawings for installation as below

1.8.2 Check list for installation

Please follow the checklist below for a successful installation:

​1. Have you studied the dimensions of the device as above drawings?
2. Have you tested and make sure the device have been connected successfully as Section "1.4 Guide for Quick Test" above?
3. Have the device been configured properly?
4. Have the device been calibrated or validated?
5. Then you can start to install the device at site. Please check the following Installation Notes for Sensor Part (if available) before installation.

1.8.3 Selection for installation location

• Make sure the site is good enough for CAT-M1/NB IoT signals.
• Choose a location far from light, heat, and vibration.
  
• DO NOT install the logger or its antenna inside a completed metallic box or housing because the cellular signal can not pass through the metallic wall. The housing is made from Non-metallic materials like plastic, glass, wood, leather, concrete, and cement…is acceptable.

1.8.4 Sample installation

 

 

 

 

 

 

 

 

 

 

1.9 Payload Document and Configuration Tables

Pease click below link for:

Click Payload document and configuration table to download Payload Document and Configuration Tables

1.10 How to connect device to MQTT Broker

Please find below the examples of adding Daviteq's MQTT device to the following MQTT broker:

• Mosquitto  MQTT broker

2. Maintenance for WSNBM-AQUA

2.1 Troubleshooting

• If the device cannot connect to the MQTT broker at the first time, it is the Communication Problem;
• If the device status like battery, RSSI level, data status or other communication is normal, but the measured values are not updated or wrong, it would be the problems of Sensor part;
• If the data coming to MQTT broker is not frequently as expected, the problem would be Communication.
  Please refer below the troubleshooting guide for Communication and Sensor Part.

2.1.1. Troubleshooting for Communication

 

2.1.2. Troubleshooting for Sensor Part (if available)

 

2.2 Maintenance

3. Advanced guide for WSNBM-AQUA

3.1 Principle of Operation

Daviteq WSNBM-AQUA comprises 04 parts linked internally:

• Pressure Sensor

• RS485 ModbusRTU Master

• Device controller

• CAT-M1/NB IoT modem

3.1.2. The parameters in published topic name

• SKU: Device SKU, read from DEVICE_SKU parameter in the device memory, max 20 characters, data type of string.
• DEVICE NAME: Device name, read from DEVICE_NAME parameter in device memory, max 20 characters, data type of string.
• DEVICE SN: Device serial number, read from DEVICE_SN parameter in device memory, 20 characters, data type of string.
• DEVICE ALIAS: Device alias, read from DEVICE_ALIAS parameter in device memory, max 20 characters, data type of string.
• TOPIC TYPE: Fixed type of the topic. One of below topic type:

-STARTUP
-HEARBEAT
-CONFIG-HEALTH-CHECK
-FORCE
-CYCLE
-CONFIG-RECEIPT
-CONFIG-REQUEST

3.1.3. Primary output values in the payload of published topics

3.1.4. Secondary output values in the payload of published topics

3.1.5. The parameters in subscribed topic name

• SKU: Device SKU, read from DEVICE_SKU parameter in the device memory, max 20 characters, data type of string.
• DEVICE NAME: Device name, read from DEVICE_NAME parameter in device memory, max 20 characters, data type of string.
• DEVICE SN: Device serial number, read from DEVICE_SN parameter in device memory, 20 characters, data type of string.
• DEVICE ALIAS: Device alias, read from DEVICE_ALIAS parameter in device memory, max 20 characters, data type of string.
• TOPIC TYPE: Fixed type of the topic. The topic type is CONFIG-REQUEST, a request to change the parameter.

3.1.6. Parameters in the payload of subscribed topic name

Subscibed Topic Type: Fixed type of the topic is CONFIG-REQUEST. This parameter is topicType in the published topic's payload.
Epoch Time: Topic's Epoch Time format, unit of millisecond. This parameter is epochTime in the published topic's payload.
Device Serial Number: Device serial number. This parameter is deviceSerialNumber in the published topic's payload.
Start Address: Start address of the changed configuration, in decimal. This parameter is startAddress in the published topic's payload.
Register Length: Register number of changed configuration, in decimal, max length = 400 hexadecimal value. This parameter is registerLength in the published topic's payload.
Requested Value: Requested value for the configuration change, in hexadecimal. This parameter is requestedValue in the published topic's payload.

3.1.7. Device operation flow chart

3.1.8. Device operation principle description

When a device subscribes to the CONFIG-REQUEST topic successfully, device implements the configuration change request and publishes CONFIG-RECEIPT topic to acknowledge the receipt of the CONFIG-REQUEST topic.

3.2 Configuration

3.2.1. How to configure the device?

Sensor configuration can be configured in 02 methods:

​Method 1: Online configuring via Subscribing CONFIG-REQUEST topic from MQTT Application.

Method 2: Offline configuring via Offline cable.

 

3.2.2 Which Parameters are configured?

Please check Part E. MEMORY MAP in Section 1.9 Payload Documents above.

3.2.3 Online configuring via subscribing CONFIG-REQUEST topic from MQTT Application.

Please refer Part C. SUBSCRIBE TOPIC in Section 1.9 Payload Documents above.

3.2.4 Offline configuring via Offline cable.

Please download the Configuration Template File of this sensor to be used in Step 4 below.

Click Download CSV file to download the Configuration Template File

Instructions for offline configuration of the Seismic sensors. Please follow the following steps.

Prepare equipment and tools

The following items must be prepared for configuration.

• A PC using the Windows OS (Windows 7 or above versions). The PC installed the COM port driver of the Modbus configuration cable (if needed). The driver is at link: Modbus Configuration Cable COM port driver for PC and the instruction to install the driver at link: How to install the driver.
• A Modbus configuration cable
• A M12-CAB-CONFIG cable 

Download and launch Modbus configuration software 

• Click the link below to download Modbus configuration software:

Click Modbus configuration software to download the software

After downloading the software, unzip the file named  Modbus Configuration.zip and then copy the extracted folder to the storage drive for long-term use. 

• Open the folder, double click on the file Modbus Configuration Tool Version.exe to launch the software and the software interface as below:

Note: The software only runs on Microsoft Windows OS (Windows 7 and above)

Connect the cable and configure the sensor

Step 1:

Connect the PC to the Battery Pack using the configuration cable and converter cable

- Use the configuration cable (Item code: TTL-LRW-USB-01).

- Connect the USB-A plug into the USB-A socket of the PC.

Step 2: 

On the configuration software, choose the relevant Port (the USB port which is the cable plugged in) and set the BaudRate: 115200, Parity: none

Step 3:

Click Connect button to connect the software to the sensor. After successful connection, the Connected status will show on the software.

Step 4:

Import the configuration template file of the sensor (as above link) to the software: click menu File/ Import New and then browse the relevant sensor template file (csv file) and click Open to import the template file.

Each sensor type has its own template file. Refer to the sensor's manual to download the correct file.

Step 5: Open the housing of the sensor and quickly plug the connector of the configuration cable into sensor's modbus configuration port. After that, turn on the switch 1. After the switch 1 is on, the software will read the parameter values automatically.

- Open the housing of the sensor.

- Plug the cable connector into sensor's Modbus configuration port.Note: this port is located at a different location, depends on the sensor type

- Turn on the switch 1

Step 6: Read the current value of the parameter with function 3

• At the relevant row of the parameter, check box 3 on column FC to read the value of the parameter. The read value is shown on VALUE ON MEMMAP column.

Step 7: Write the new setting to the parameter with function 16

• Double click on the column VALUE TO WRITE of the parameter and input the new setting of the parameter
• Uncheck the tick on the FC column of the parameter, click on the arrow, select 16 and then check on the FC column to write a new setting to the parameter. The WRITE_OK text will show on EXCEPTION column if the software successfully writes the setting.

• Repeat step 6 to read the setting of the parameter for checking.

For some critical parameters of the sensor, the password in "password for setting" must be written before writing the new settings to these parameters.

Only read/write registers are allowed to write.

Troubleshooting of offline configuration

No.	Phenomena	Reason	Solution
1	The status on the software always shows Disconnected although the configuration cable is connected to the PC	The selected COM port is incorrect	Select the correct COM port to which the configuration cable connects to PC
		The configuration cable is defective	Check the configuration cable
2	The software reads no value after importing the right template and connecting the right cable.	The cable is defective or lost connection	Check or replace the new configuration cable
		The USB port is defective	Check USB port
		There is no power supply to the sensor via configuration cable	Check the power line of the cable
		The sensor or sensor port is defective	Check the sensor and sensor port
3	No COM port appears in the Port list	No configuration cable is plugged into the PC	Plug the cable to the PC
		The cable driver is not installed on the PC	Install the driver for the PC
4	The parameter table on the software is empty	The template file has not been imported	Click menu File and sub-menu Import New to import the template file
5	The parameter table on the software does NOT match the memory map table of the sensor.	The wrong template file was imported.	Go to the correct manual page of the product and download the right template file, then import the template file into the software.

 

4. Product Specifications for WSNBM-AQUA

MEASUREMENT
Standard Inputs	02 x Pulses, 1 x RS485 Modbus RTU Master
Optional Input	1 or 2 Pressure Sensors
Digital Inputs	2-Digital channel inputs with dry-contact or voltage input (max 3.3VDC) DI Functions: Logic Detecting or Pulse Counting Logic Detecting: 2 channels, recommended minimum interval time between 02 statuses is 5 seconds. Pulse Counting: 2 channels, max frequency 100Hz, minimum Pulse width (low or high) is 200μS, counter is uint32 type.
RS485 Input port	1 x RS485 master port Protocol: Modbus RTU
Pressure Sensor	Advanced Piezo technology Measurement range: Select 0-10 barg, 0-16 barg, 0-20 barg Over pressure protection: 1.5 x span Accuracy & Stability: 0.25% or 0.5% of span, < 0.2% span/ year Wetted parts: 304SS/316SS Measuring Fluids: Any fluid which is workable with materials 304SS/316SS Working temperature: 20∼80℃ Compensation temperature: -10∼50℃ Process connection: Standard G 1/4 or Others (consult factory)
COMMUNICATION
Connectivity	LTE Cat NB1 for B1, B2, B3, B4, B5, B8, B9, B10, B12, B13, B17, B18, B19, B20, B25, B26, B27, B28, B66
LTE Cat M1	LTE HD-FDD B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66
LTE Cat NB1/NB2	LTE HD-FDD B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66
RF Power	Class 3, 23 dBm ±2.7 dB
Antenna	Internal Antenna 2.0 dbi
Battery	01 or 02 x D size 3.6VDC LiSOCl₂ Battery type, battery not included
Working temperature	-40∼85℃ (with SAFT LS33600 batteries)
Dimensions/ Netweight	H170 x W192 x D97, 190g
Housing	Anodized Aluminum + Engineering plastic, IP68.

5. Warranty for WSNBM-AQUA

5.1 Warranty

Below terms and conditions are applied for products manufactured and supplied by the Supplier.

5.1.1 Free Warranty Conditions

• The manufacturer undertakes to guarantee within 12 months from shipment date.
• Product failed due to defects in material or workmanship.
• Serial number, label, warranty stamp remains intact (not purged, detected, edited, scraped, tore, blurry, spotty, or pasted on top by certain items).
• During the warranty period, if any problem of damage occurs due to technical manufacturing, please notify our Support Center for free warranty consultancy. Unauthorized treatments and modifications are not allowed.
• Product failed due to the defects from the manufacturer, depending on the actual situation, Supplier will consider replacement or repairs.

Note: One way shipping cost to the Return center shall be paid by Customers.

5.1.2 Paid Warranty

• The warranty period has expired.
• The product is not manufactured by the Manufacturer.
• Product failed due to damage caused by disasters such as fire, flood, lightning or explosion, etc.
• Product damaged during shipment.
• Product damaged due to faulty installation, usage, or power supply.
• Product damage caused by the customer.
• Product rusted, stained by effects of the environment or due to vandalism, liquid (acids, chemicals, etc.)
• Product damage is caused by unauthorized treatments and modifications.

Note: Customers will be subjected to all repairing expenses and 2-way shipping costs. If arises disagreement with the company's determining faults, both parties will have a third party inspection appraise such damage and its decision be and is the final decision.