Skip to Content
Last modified by Mengting Qiu on 2025/07/21 10:33
Show last authors
1
2
3 [[image:image-20241126162133-3.png||data-xwiki-image-style-alignment="center"]]
4
5
6
7
8
9
10 **Table of Contents:**
11
12 {{toc/}}
13
14
15
16
17
18 = 1. Introduction =
19
20 == 1.1 Overview ==
21
22
23 (((
24 WQS-CB/CS is a Main Unit is advanced instruments designed for comprehensive (% style="color:blue" %)**water quality monitoring across various applications**(%%). They are ideal for (% style="color:blue" %)**monitoring tap water, industrial water, environmental water, and wastewater**(%%),etc,which ofer precise and reliable measurements to ensure water quality standards are met.
25
26 WQS-CB/CS is a (% style="color:blue" %)**Main Unit supports 1-3 probes**(%%). supports connecting 1 to 3 water quality probes, including EC, pH, DO, ORP, and TS probes.
27
28 The Dragino WQS-CB/CS is a (% style="color:blue" %)**NB-IoT/LTE-M Analog Sensor**(%%) for Internet of Things solution.
29
30 WQS-CB/CS will convert the Analog Value to NB-IoT wireless data and then upload to IoT server via NB-IoT or CAT-M1 network.
31
32 WQS-CB/CS supports different uplink methods including (% style="color:blue" %)**MQTT, MQTTs, UDP, TCP or CoAP**(%%) for different application requirement, and support uplinks to various IoT Servers.
33
34 WQS-CB/CS supports (% style="color:blue" %)**BLE con­figure and wireless OTA update**(%%) which makes user easy to use.
35
36 WQS-CB/CS is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery or solar powered+Li-ion battery**(%%) , it is designed for long-term use up to several years.
37 )))
38
39 (% style="color:red" %)**Note1: **(%%)The method of use is that the probe is in direct contact with the water quality. Before using the sensor probe, its protective cover and blue foam cushioning pad must be completely removed. These protective components are designed for transportation and storage, and can effectively resist factors such as physical collision that damage the probe.
40
41 (% style="color:red" %)**Note2: **(%%)Because the probe needs to adapt to the new water quality environment, the data collected at the beginning will be inaccurate. After standing in the new water quality for two hour, the data collected by the equipment will be more accurate.
42
43 == 1.2 Specifications ==
44
45
46 (% style="color:blue" %)**Common DC Characteristics:**
47
48 * Supply Voltage: 2.5v ~~ 3.6v
49 * Operating Temperature: -40 ~~ 85°C
50
51 (% style="color:blue" %)**I/O Interface:**
52
53 * Battery controllable output (2.6v ~~ 3.6v depends on battery)
54 * +5v controllable output
55 * 1 x RS485 Interface
56 * 1 x UART Interface , 3.3v or 5v
57 * 1 x Interrupt or Digital IN/OUT pins
58 * 1 x I2C Interface
59 * 1 x one wire interface
60
61 (% style="color:blue" %)**NB-IoT Spec:**
62
63 (% style="color:#4472c4" %)**NB-IoT Module: BG95-NGFF**
64
65 (% style="color:#4472c4" %)**Support Bands:**
66
67 * B1 @H-FDD: 2100MHz
68 * B2 @H-FDD: 1900MHz
69 * B3 @H-FDD: 1800MHz
70 * B4 @H-FDD: 2100MHz
71 * B5 @H-FDD: 860MHz
72 * B8 @H-FDD: 900MHz
73 * B12 @H-FDD: 720MHz
74 * B13 @H-FDD: 740MHz
75 * B17 @H-FDD: 730MHz
76 * B18 @H-FDD: 870MHz
77 * B19 @H-FDD: 870MHz
78 * B20 @H-FDD: 790MHz
79 * B25 @H-FDD: 1900MHz
80 * B28 @H-FDD: 750MHz
81 * B66 @H-FDD: 2000MHz
82 * B70 @H-FDD: 2000MHz
83 * B85 @H-FDD: 700MHz
84
85 (% style="color:blue" %)**Battery:**
86
87 * Li/SOCI2 un-chargeable battery
88 * Capacity: 8500mAh
89 * Self Discharge: <1% / Year @ 25°C
90 * Max continuously current: 130mA
91 * Max boost current: 2A, 1 second
92
93 (% style="color:blue" %)**Power Consumption:**
94
95 * STOP Mode: 10uA @ 3.3v
96 * Max transmit power: 350mA@3.3v
97
98 == 1.3 Features ==
99
100
101 * For -NB Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85
102 * For -CB Bands: B1/B2/B3/B4/B5/B8/B12/B13~/~/B18/B19/B20/B25/B28/B66/B71/B85
103 * CAT-M1 / LTE-M Bands: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85
104 * Ultra-low power consumption
105 * Measure water quality and provide information for water quality conditions
106 * Support EC / PH / DO / ORP/ TS Type Water Quality Probe
107 * Support 1 ~~ 3 probes
108 * Multiply Sampling and one uplink
109 * Uplink via MQTT, MQTTs, TCP, UDP or CoAP
110 * GNSS for Location Report
111 * Support Bluetooth v5.1 remote configure and update firmware
112 * Uplink on periodically
113 * Downlink to change configure
114 * Nano SIM card slot for NB-IoT SIM
115 * 8500mAh Li/SOCl2 Battery (WQS-CB)
116 * Solar panel + 3000mAh Li-ion battery (WQS-CS)
117
118 == 1.4 Applications ==
119
120
121 * Smart Buildings & Home Automation
122 * Logistics and Supply Chain Management
123 * Smart Metering
124 * Smart Agriculture
125 * Smart Cities
126 * Smart Factory
127
128 == 1.5 Sleep mode and working mode ==
129
130
131 (% style="color:blue" %)**Deep Sleep Mode: **(%%)Sensor doesn't have any NB-IoT/CAT-M1 activate. This mode is used for storage and shipping to save battery life.
132
133 (% style="color:blue" %)**Working Mode:** (%%)In this mode, Sensor will work as NB-IoT Sensor to Join NB-IoT network and send out sensor data to server. Between each sampling/tx/rx periodically, sensor will be in IDLE mode), in IDLE mode, sensor has the same power consumption as Deep Sleep mode.
134
135
136 == 1.6 Button & LEDs ==
137
138 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/RS485-LB_Waterproof_RS485UART_to_LoRaWAN_Converter/WebHome/image-20240103160425-4.png?rev=1.1||alt="image-20240103160425-4.png"]]
139
140 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
141 |=(% style="width: 167px;background-color:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width:226px;background-color:#4F81BD;color:white" %)**Action**
142 |[[image:1749539752756-534.png]] 1~~3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)(((
143 If sensor has already attached to NB-IoT/CAT-M1 network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once.
144 Meanwhile, BLE module will be active and user can connect via BLE to configure device.
145 )))
146 |[[image:1749539755488-143.png]] >3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)(((
147 (% style="color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:#037691" %)**OTA mode**(%%) for 3 seconds. And then start to attach NB-IoT/CAT-M1 network.
148 Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device attach NB-IoT/CAT-M1 network or not.
149 )))
150 |[[image:1749539766290-212.png]] x5|(% style="width:117px" %)Deactivate Device|(% style="width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means device is in Deep Sleep Mode.
151
152 (% style="color:red" %)**Note: When the device is executing a program, the buttons may become invalid. It is best to press the buttons after the device has completed the program execution.**
153
154
155 == 1.7 BLE connection ==
156
157
158 WQS-CB/CS support BLE remote configure and firmware update.
159
160
161 BLE can be used to configure the parameter of sensor or see the console output from sensor. BLE will be only activate on below case:
162
163 * Press button to send an uplink
164 * Press button to active device.
165 * Device Power on or reset.
166
167 If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode.
168
169
170 == 1.8 Pin Definitions , Switch & SIM Direction ==
171
172
173 [[image:image-20250424134010-1.jpeg||height="429" width="736"]]
174
175
176 === 1.8.1 Jumper JP2 ===
177
178
179 Power on Device when put this jumper.
180
181
182 === 1.8.2 BOOT MODE / SW1 ===
183
184
185 **1)** (% style="color:blue" %)**ISP:**(%%) upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
186
187 **2)** (% style="color:blue" %)**Flash: **(%%)work mode, device starts to work and send out console output for further debug
188
189
190 === 1.8.3 Reset Button ===
191
192
193 Press to reboot the device.
194
195
196 === 1.8.4 SIM Card Direction ===
197
198
199 See this link. [[How to insert SIM Card>>https://wiki.dragino.com/xwiki/bin/view/Main/General%20Manual%20for%20-CB%20%2C%20-CS%20models/#H2.1GeneralConfiguretoattachnetwork]].
200
201
202 === 1.8.5 SW2 Jumper (Define UART level to external Sensor) ===
203
204
205 SW2 defines the voltage level of BOARD_RX and BOARD_TX pins. It should match the external sensor voltage level
206
207
208 == 1.9 Wiring of DS18B20 temperature sensor ==
209
210
211 The WQS-CB/CS supports connection to the external temperature sensor DS18B20. The wiring method is as follows:
212
213 [[image:image-20250506152713-1.jpeg||height="657" width="816"]]
214
215
216 == 1.10 Mechanical ==
217
218 === 1.10.1 for CB version ===
219
220 [[image:image-20250401160104-1.jpeg]]
221
222
223 === 1.10.2 for CS version ===
224
225
226 [[image:image-20250401160124-2.jpeg]]
227
228
229 = 2. How to use =
230
231 == 2.1 Example to use for IoT network ==
232
233
234 The WQS-CB/CS is equipped with a NB-IoT module, the pre-loaded firmware in WQS-CB/CS will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by WQS-CB/CS.
235
236 Below shows the network structure:
237
238 [[image:image-20250110160340-1.png]]
239
240 There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1T**(%%) version of WQS-CB.
241
242
243 (% style="color:blue" %)**GE Version**(%%): This version doesn't include SIM card or point to any IoT server. User needs to use AT Commands to configure below two steps to set WQS-CB send data to IoT server.
244
245 * Install NB-IoT SIM card and configure APN. See instruction of [[Attach Network>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.AttachNetwork]].
246
247 * Set up sensor to point to IoT Server. See instruction of [[Configure to Connect Different Servers>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.Configuretoconnecttodifferentservers]]. 
248
249 Below shows result of different server as a glance.
250
251 (% border="1" cellspacing="3" style="width:515px" %)
252 |(% style="background-color:#4f81bd; color:white; width:100px" %)**Servers**|(% style="background-color:#4f81bd; color:white; width:300px" %)**Dash Board**|(% style="background-color:#4f81bd; color:white; width:115px" %)**Comments**
253 |(% style="width:127px" %)[[Node-Red>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.5A0Node-RedA028viaA0MQTT29]]|(% style="width:385px" %)(((
254 [[image:image-20250418154250-1.jpeg]]
255 )))|(% style="width:170px" %)
256 |(% style="width:127px" %)[[DataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.4Datacake]]|(% style="width:385px" %)(((
257 [[image:image-20250418154257-2.jpeg]]
258 )))|(% style="width:170px" %)
259 |(% style="width:127px" %)[[Tago.IO>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.7A0Tago.ioA028viaA0MQTT29]]|(% style="width:385px" %) |(% style="width:170px" %)
260 |(% style="width:127px" %)[[General UDP>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.1GeneralA0UDPA0Connection]]|(% style="width:385px" %)Raw Payload. Need Developer to design Dash Board|(% style="width:170px" %)
261 |(% style="width:127px" %)[[General MQTT>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.2GeneralA0MQTTA0Connection]]|(% style="width:385px" %)Raw Payload. Need Developer to design Dash Board|(% style="width:170px" %)
262 |(% style="width:127px" %)[[ThingSpeak>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.3A0ThingSpeakA028viaA0MQTT29]]|(% style="width:385px" %)(((
263 [[image:image-20250418154323-3.jpeg]]
264 )))|(% style="width:170px" %)
265 |(% style="width:127px" %)[[ThingsBoard>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.6A0ThingsBoard.CloudA028viaA0MQTT29]]|(% style="width:385px" %)(((
266 [[image:image-20250418154335-4.jpeg]]
267 )))|(% style="width:170px" %)
268
269 (% style="color:blue" %)**1T Version**(%%): This version has 1NCE SIM card pre-installed and configure to send value to ThingsEye. User Just need to select the sensor type in ThingsEyeand Activate WQS-CB/CS and user will be able to see data in ThingsEye. See here for [[ThingsEye Config Instruction>>url:https://wiki.thingseye.io/xwiki/bin/view/Main/]].
270
271
272 == 2.2 Uplink Payload ==
273
274
275 To meet different server requirement, WQS-CB supports different payload type.
276
277 **Includes:**
278
279 * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5)
280
281 * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0)
282
283 * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1)
284
285 * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3)
286
287 User can specify the payload type when choose the connection protocol. Example:
288
289 (% style="color:#037691" %)**AT+PRO=1,0**  (%%) ~/~/ Use COAP Connection & hex Payload
290
291 (% style="color:#037691" %)**AT+PRO=1,5**   (%%) ~/~/ Use COAP Connection & Json Payload
292
293 (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/ Use UDP Connection & hex Payload
294
295 (% style="color:#037691" %)**AT+PRO=2,5**   (%%) ~/~/ Use UDP Connection & Json Payload
296
297 (% style="color:#037691" %)**AT+PRO=3,0**  (%%) ~/~/ Use MQTT Connection & hex Payload
298
299 (% style="color:#037691" %)**AT+PRO=3,1           **(%%)~/~/ Use MQTT Connection & ThingSpeak
300
301 (% style="color:#037691" %)**AT+PRO=3,3           **(%%)~/~/ Use MQTT Connection & ThingsBoard
302
303 (% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload
304
305 (% style="color:#037691" %)**AT+PRO=4,0**  (%%) ~/~/ Use TCP Connection & hex Payload
306
307 (% style="color:#037691" %)**AT+PRO=4,5**   (%%) ~/~/ Use TCP Connection & Json Payload
308
309
310 === 2.2.1 General Json Format(Type~=5) ===
311
312
313 This is the General Json Format. As below:
314
315 (% style="color:#4472c4" %)**{"IMEI":"868508065601703","IMSI":"460240210507483","Model":"WQS-CB","Tur":23.90,"EC_K1":25,"PH":7.82,"interrupt":0,"interrupt_level":0,"battery":3.22,"signal":27,"time":"2025-01-10T09:11:18Z","latitude":0.000000,"longitude":0.000000,"gps_time":"1970-01-01T00:00:00Z","1":[24.10,25,0.00,"2025-01-10T09:03:16Z"],"2":[0.00,0,0.00,"2025-01-10T08:17:02Z"],"3":[0.00,0,0.00,"2025-01-10T08:02:02Z"],"4":[0.00,0,0.00,"2025-01-10T07:47:02Z"],"5":[0.00,0,0.00,"2025-01-10T07:32:02Z"],"6":[0.00,0,0.00,"2025-01-10T07:17:02Z"],"7":[0.00,0,0.00,"2025-01-10T07:02:02Z"],"8":[0.00,0,0.00,"2025-01-10T06:47:02Z"]}**
316
317 [[image:image-20250110172307-1.png]]
318
319 (% style="color:red" %)**Notice, from above payload:**
320
321 * Tur, EC_K1, PH, interrupt, interrupt_level, battery, signal, time, latitude, longitude, gps_time are the value at uplink time.
322
323 * Json entry 1 ~~ 8 are the last 1 ~~ 8 sampling data as specify by (% style="color:#037691" %)**AT+CLOCKLOG=1,65535,15,8 ** (%%)Command. Each entry includes (from left to right): Tur, EC_K1, PH & Sampling time.
324
325 * Since I tested with Turbidity Sensor (DR-TS1), EC K1 Sensor, and PH Sensor, the WQS-CB recognizes and sends readings for these sensors.
326
327 WQS-CB/CS supports six types of water quality sensors, the six sensor data sequence is: (% style="color:#037691" %)**TS1, DO1, ORP, ECK10, ECK1, PH01**
328
329 No matter which two or three sensors you're connected to, they're all in the same data order as above.
330
331
332 === 2.2.2 HEX format Payload(Type~=0) ===
333
334
335 This is the HEX Format. As below:
336
337 (% style="color:#4472c4" %)**f868508065601703f4602402105074836c6e0ccc1a0100002300f7001903056780ebac00000000000000000000000000f1001a030a6780e95c00ef0019030c6780e5d800f1001900006780e2540000000000006780d77e0000000000006780d3fa0000000000006780d0760000000000006780ccf20000000000006780c96e**
338
339 [[image:image-20250111094159-1.png]]
340
341
342 [[image:image-20250110174513-2.png]]z
343
344
345 (% style="color:blue" %)**Device ID(f+IMEI):**(%%)** **f868508065601703= 868508065601703
346
347
348 (% style="color:blue" %)**SIM Card ID(f+IMSI):**(%%)** **f460240210507483= 460240210507483
349
350
351 (% style="color:blue" %)**Version:**
352
353 These bytes include the hardware and software version.
354
355 (% style="color:#037691" %)**Higher byte: **(%%)Specify Sensor Model: 0x6C for WQS-CB/CS
356
357 (% style="color:#037691" %)**Lower byte: **(%%)Specify the software version: 0x6e=110, means firmware version 1.1.0
358
359
360 (% style="color:blue" %)**BAT (Battery Info):**
361
362 Ex1: 0x0ccc = 3276mV
363
364
365 (% style="color:blue" %)**Signal:**
366
367 NB-IoT Network signal Strength.
368
369 **Ex1: 0x1a = 26**
370
371 **0**  -113dBm or less
372
373 **1**  -111dBm
374
375 **2...30** -109dBm... -53dBm
376
377 **31**   -51dBm or greater
378
379 **99**    Not known or not detectable
380
381
382 (% style="color:blue" %)**Interrupt:**
383
384 This data field shows if this packet is generated by interrupt or not.
385
386 **Example:**
387
388 If byte[0]&0x01=0x00 : Normal uplink packet.
389
390 If byte[0]&0x01=0x01 : Interrupt Uplink Packet.
391
392
393 (% style="color:blue" %)**Interrupt_level:**
394
395 This byte shows whether the interrupt is triggered by a high or low level.
396
397 **Ex1:** 0x00  Interrupt triggered by falling edge (low level)
398
399 **Ex2: **0x01  Interrupt triggered by rising edge (high level)
400
401
402 (% style="color:blue" %)**Sensor flag:**
403
404 There are six types of water quality sensors, each of which is assigned a position in the memory.
405
406 One byte, using its binary Bit5~~bit0: 00(% style="color:#037691" %)**000000**
407
408 in order: (% style="color:#037691" %)**TS1, DO1, ORP, ECK10, ECK1, PH01**
409
410 **Example: **
411
412 **0x23(H)=00(% class="mark" %)100011(%%)(B)**
413
414 Then the sensors used and their data sequence are: TS1(Turbidity Sensor), ECK1(EC K1 Sensor), PH01(PH Sensor).
415
416
417 (% style="color:blue" %)**Sensor DATA:**
418
419 The sequence of sensor data is consistent with the sequence of sensors identified.
420
421 As mentioned above, the sensors I connected are TS1, ECK1 and PH01, the Sensor_flag is (% class="mark" %)**100011.**
422
423 (% style="color:red" %)**Note: The data for each sensor is 2 bytes.**
424
425 **Example:**
426
427 0x00f7 0019 0305
428
429 TS1: 0x00f7= 247/10 =24.70NTU
430
431 ECK1: 0x0019= 25us/cm
432
433 PH01: 0x0305= 773/100 =7.73PH
434
435
436 (% style="color:blue" %)**TimeStamp & GPS Timestamp**
437
438 Unit TimeStamp Example:  6780ebac(H) = 1736502188(D)
439
440 Put the decimal value into this link([[https:~~/~~/www.epochconverter.com/)>>url:https://www.epochconverter.com/)]] to get the time.
441
442
443 (% style="color:blue" %)**Latitude:**
444
445 EX1:** **0x00000000  ~/~/ Locating fails or is not enabled.
446
447 EX2: 0x015a77dc(H)=22706410(D): 22.706410
448
449
450 (% style="color:blue" %)**Longitutde:**
451
452 EX1:** **0x00000000  ~/~/ Locating fails or is not enabled.
453
454 EX2: 0x06cf3c7a(H)=114244730(D): 114.244730
455
456
457 (% style="color:blue" %)**GPS_Timestamp:**
458
459 EX1: 0x00000000  ~/~/ The value is "1970-01-01T00:00:00Z" in JSON format. The initial GPS time is not refreshed if GPS positioning is disabled or fails.
460
461 EX2: 0x6682595d =1719818589 = 2024-07-01 15:23:09
462
463
464 === 2.2.3 ThingsBoard Payload(Type~=3) ===
465
466
467 Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard.
468
469 (% style="color:#4472c4" %)**{
470 "topic": "WQS_CB",
471 "payload": {
472 "IMEI": "868508065601703",
473 "IMSI": "460240210507483",
474 "Model": "WQS-CB",
475 "Tur": 32.3,
476 "DO": 12.68,
477 "interrupt": 0,
478 "interrupt_level": 0,
479 "battery": 3.24,
480 "signal": 23,
481 "time": "2025-01-11T03:30:01Z",
482 "latitude": 0.0,
483 "longitude": 0.0,
484 "gps_time": "1970-01-01T00:00:00Z",
485 "1": [0.0, 0.0, "2025-01-11T03:13:34Z"],
486 "2": [0.0, 0.0, "2025-01-11T02:58:34Z"],
487 "3": [0.0, 0.0, "2025-01-11T02:43:34Z"],
488 "4": [0.0, 0.0, "2025-01-11T02:28:34Z"],
489 "5": [0.0, 0.0, "2025-01-11T02:13:34Z"],
490 "6": [0.0, 0.0, "2025-01-11T01:58:34Z"],
491 "7": [0.0, 0.0, "2025-01-11T01:43:34Z"],
492 "8": [0.0, 0.0, "2025-01-11T01:28:34Z"]
493 }
494 }**
495
496 [[image:image-20250111113220-1.png||height="556" width="1118"]]
497
498 [[image:image-20250111113312-2.png||height="406" width="739"]]
499
500
501 === 2.2.4 ThingSpeak Payload(Type~=1) ===
502
503
504 This payload meets ThingSpeak platform requirement. I used Turbidity sensor:DR-TS1 and Dissolved Oxygen Sensor:DR-D01, so the data is as follows:
505
506 (% style="color:#4472c4" %)** field1=Tur value&field2=DO value&field3=Interrupt&field4=Interrupt_level&field5=Latitude&field6=Longitude&field7=BatV&field8=Singal**
507
508 [[image:image-20250111115515-3.png||height="579" width="873"]]
509
510 [[image:image-20250111115531-4.png||height="581" width="874"]]
511
512
513 = 3. Configure WQS-CB =
514
515 == 3.1 Configure Methods ==
516
517
518 WQS-CB/CS supports below configure method:
519
520 * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]].
521
522 * AT Command via UART Connection : See [[UART Connection>>http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.4UARTConnectionforRS485-BLbasemotherboard]].
523
524 == 3.2  Serial Access Password ==
525
526
527 After the Bluetooth or UART connection is successful, use the Serial Access Password to enter the AT command window.
528
529 The label on the box of the node will print the initial password: AT+PIN=**xxxxxx**, and directly use the six-digit password to access the AT instruction window.
530
531 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/RS485-NB%2C-NS_RS485%2CUART_to_NB-IoT_Converter_User_Manual/WebHome/image-20250226165815-1.png?rev=1.1||alt="image-20250226165815-1.png"]]
532
533
534 If you need to change the password, use **AT+PWORD=**xxxxxx (6 characters), NB nodes only support lowercase letters.
535
536 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/RS485-NB%2C-NS_RS485%2CUART_to_NB-IoT_Converter_User_Manual/WebHome/image-20240826162734-1.png?rev=1.1||alt="image-20240826162734-1.png"]]
537
538
539 (% style="color:red" %)**Note: After entering the command, you need to add a line break, and you can also set automatic line breaks in the Bluetooth tool or UART connection tool.**
540
541 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_NB-IoT_Sensor_Node_User_Manual/WebHome/image-20240823174639-3.png?width=716&height=505&rev=1.1||alt="image-20240823174639-3.png"]]
542
543
544 == 3.3 AT Commands Set ==
545
546
547 AT+<CMD>? : Help on <CMD>
548
549 AT+<CMD> : Run <CMD>
550
551 AT+<CMD>=<value> : Set the value
552
553 AT+<CMD>=? : Get the value
554
555
556 (% style="color:blue" %)**General Commands**      
557
558 AT : Attention       
559
560 AT? : Short Help
561
562 AT+MODEL : Get module information
563
564 ATZ : Trig a reset of the MCU
565
566 AT+CFGMOD : Working mode selection
567
568 AT+DEUI : Get or set the Device ID
569
570 AT+CFG : Print all settings
571
572 AT+SERVADDR: Get or Set the Server address
573
574 AT+TDC : Get or set the application data transmission interval in s
575
576 AT+INTMOD : Get or Set the trigger interrupt mode (0:input,1:falling or rising,2:falling,3:rising)
577
578 AT+APN : Get or set the APN
579
580 AT+5VT : Get or Set extend the time of 5V power
581
582 AT+PRO : Get or Set usage agreement (1:COAP,2:UDP,3:MQTT,4:TCP)
583
584 AT+RXDL : Get or Set the receiving time
585
586 AT+CALPH : PH calibration Standard buffering (4:4.01,6:6.86,9:9.18)
587
588 AT+CALORP : ORP calibration Standard buffering(86:86mv,256:256mv)
589
590 AT+CALEC : EC calibration Standard buffering (1:1413HS/cm,10:12.88mS/cm)
591
592 AT+CALNTU : NTU calibration Standard buffering (0:0NTU,2:200NTU,4:400NTU,6:600NTU,8:800NTU,10:1000NTU)
593
594 AT+GETSENSORVALUE : Returns the current sensor measurement
595
596 AT+DNSCFG : Get or Set DNS Server
597
598 AT+CSQTIME : Get or Set the time to join the network
599
600 AT+GDNS : Get or Set the DNS
601
602 AT+TLSMOD : Get or Set the TLS mode
603
604 AT+SLEEP : Get or Set the sleep mode
605
606 AT+IPTYPE : Set the IPv4 or IPv6
607
608 AT+QSW : Power on and power off BG95 module
609
610 AT+CLOCKLOG: Get or set SHT record time
611
612 AT+QBAND: Get or set Frequency Band
613
614 AT+IOTMOD: Configure Network Category to be Searched for under LTE RAT
615
616 AT+DOWNTE: Get or set the conversion between the standard version and 1T version downlinks
617
618
619 (% style="color:blue" %)**MQTT Management**
620
621 AT+CLIENT : Get or Set the MQTT clientID
622
623 AT+UNAME : Get or Set the MQTT Username
624
625 AT+PWD : Get or Set the MQTT password
626
627 AT+PUBTOPIC: Get or set MQTT publishing topic
628
629 AT+SUBTOPIC: Get or set MQTT subscription topic
630
631 AT+MQOS : Set the QoS level of MQTT
632
633
634 (% style="color:blue" %)**COAP Management**
635
636 AT+URI1: Get or set CoAP option 1
637
638 AT+URI2: Get or set CoAP option 2
639
640 AT+URI3: Get or set CoAP option 3
641
642 AT+URI4: Get or set CoAP option 4
643
644 AT+URI5: Get or set CoAP option 5
645
646 AT+URI6: Get or set CoAP option 6
647
648 AT+URI7: Get or set CoAP option 7
649
650 AT+URI8: Get or set CoAP option 8
651
652
653 (% style="color:blue" %)**GPS**
654
655 AT+GNSST : Extend the time to turn on GNSS
656
657 AT+GPS : Turn off and on GPS
658
659 AT+GTDC : Get or set GPS positioning interval in units of h
660
661
662 (% style="color:blue" %)**Information**          
663
664 AT+FDR1 : Reset parameters to factory default values except for passwords
665
666 AT+FDR : Reset Parameters to Factory Default
667
668 AT+PWORD : Get or set the System password
669
670 AT+CDP : Read or Clear cached data
671
672 AT+LDATA : Get the last upload data
673
674 AT+GETLOG : Print serial port logs
675
676
677 == 3.4 Test Uplink and Change Update Interval ==
678
679
680 By default, Sensor will send uplinks **every 2 hours.**
681
682 User can use below commands to change the uplink interval.
683
684 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+TDC** (%%)
685
686 Example: AT+TDC=7200  ~/~/ Set Update Interval to 7200 seconds
687
688 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x01**
689
690 Format: Command Code (0x01) followed by 3 bytes.
691
692 Example:  12 hours= 43200 seconds  43200(D)=0xA8C0(H)
693
694 Downlink Payload: **01 00 A8 C0**  ~/~/ AT+TDC=43200, Set Update Interval to 12 hours.
695
696 (% style="color:red" %)**Note: User can also push the button for more than 1 second to activate an uplink.**
697
698
699 == 3.5 Set the receiving time ==
700
701
702 Feature: Extend the receiving time
703
704 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+RXDL**
705
706 Example: AT+RXDL=1000  ~/~/ Set the receiving time delay to 1000ms
707
708 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x03**
709
710 Format: Command Code (0x03) followed by 3 bytes.
711
712 Example:  Downlink Payload: **03 00 03 E8     **~/~/ AT+RXDL=1000
713
714
715 == 3.6 Reset ==
716
717
718 Feature: Trig a reset of the MCU.
719
720 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**ATZ**
721
722 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x04FF**
723
724
725 == 3.7 +5V ==
726
727
728 Feature: Set extend the time of 5V power.
729
730 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+5VT**
731
732 Example: AT+5VT=2000  ~/~/ Set extend the time of 5V power to 2000 ms
733
734 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x05**
735
736 Format: Command Code (0x05) followed by 3 bytes.
737
738 Example:  Downlink Payload: **05 00 07 D0    **~/~/ AT+5VT=2000
739
740
741 == 3.8 Trigger an uplink by external interrupt ==
742
743
744 WQS-CB/CS has an external trigger interrupt function. Users can use the GPIO_EXTI pin to trigger the upload of data packets.
745
746 (% style="color:blue" %)**AT command:**
747
748 * (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode
749
750 * (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Input, disable Interrupt
751
752 * (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge
753
754 * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge
755
756 * (% style="color:#037691" %)**AT+INTMOD=3  **(%%) ~/~/ Trigger by rising edge
757
758 (% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x06**
759
760 Format: Command Code (0x06) followed by 3 bytes.
761
762 Example1:  Downlink Payload: **06 00 00 01    **~/~/ AT+INTMOD=1
763
764 Example2:  Downlink Payload: **06 00 00 03    **~/~/ AT+INTMOD=3
765
766
767 == 3.9 Set the QoS level ==
768
769
770 This command is used to set the QoS level of **MQTT**.
771
772 (% style="color:blue" %)**AT command:**
773
774 * (% style="color:#037691" %)**AT+MQOS=xx**(%%)**   **~/~/ 0~~2
775
776 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x07(%%)**
777
778 Format: Command Code (0x07) followed by 1 byte.
779
780 **Ex1:** Downlink payload: **0x0700**  ~/~/ AT+MQOS=0
781
782 **Ex2:** Downlink payload: **0x0701**  ~/~/ AT+MQOS=1
783
784
785 == 3.10 Clock logging ==
786
787
788 Sometimes when we deploy lots of end nodes in field. We want all sensors sample data at the same time, and upload these data together for analyze. In such case, we can use clock loging feature.
789
790 We can use this command to set the start time of data recording and the time interval to meet the requirements of the specific collection time of data.
791
792 (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CLOCKLOG=a,b,c,d(%%)**
793
794 (% style="color:#037691" %)**a: **(%%)**0:** Disable Clock logging.  ** 1: **Enable Clock Logging
795
796 (% style="color:#037691" %)**b:**(%%)** **Specify First sampling start second: range **(0 ~~ 3599, 65535)   ** ~/~/  (% style="color:red" %)**Note: **(%%)If parameter b is set to 65535, the log period starts after the node accesses the network and sends packets.
797
798 (% style="color:#037691" %)**c: **(%%)Specify the sampling interval: range **(0 ~~ 255 minutes)**
799
800 (% style="color:#037691" %)**d:**(%%)** **How many entries should be uplink on every TDC **(max 32)**
801
802 (% style="color:red" %)**Note: To disable clock recording, set the following parameters: AT+CLOCKLOG=1,65535,0,0**
803
804 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SPH01-NB_NB-IoT_Soil_pH_Sensor_User_Manual/WebHome/image-20240315141254-1.png?rev=1.1||alt="image-20240315141254-1.png"]]
805
806 **Example:**
807
808 **AT+CLOCKLOG=1,65535,1,5**
809
810 After the node sends the first packet, data is recorded to the memory at intervals of 1 minute. For each TDC uplink, the uplink load will include: battery information + the last 5 memory records (payload + timestamp).
811
812 (% class="wikigeneratedid" %)
813 [[image:image-20250111134736-5.png||height="661" width="863"]]
814
815 (% class="wikigeneratedid" %)
816 (% style="color:red" %)**Note: Users need to synchronize the server time before configuring this command. If the server time is not synchronized before this command is configured, the command takes effect only after the node is reset.**
817
818 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x08(%%)**
819
820 Format: Command Code (0x08) followed by 5 bytes.
821
822 * **Example 1**: Downlink Payload:** 08 01 FFFF 0F 08**  ~/~/ Set SHT record time: AT+CLOCKLOG=1,65535,15,8
823 * **Example 2**: Downlink Payload:** 08 01 04B0 0F 08**  ~/~/ Set SHT record time: AT+CLOCKLOG=1,1200,15,8
824
825 (% style="color:red" %)**Note: When entering the downlink payload, there must be no Spaces between bytes.**
826
827
828 == 3.11 Set the TLS mode ==
829
830
831 Refer to this link ([[MQTT Connection to send data to Tago.io>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Manual%20for%20-CB%20%2C%20-CS%20models/#H3.7Tago.io28viaMQTT29]])to use the TLS mode.
832
833 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+TLSMOD**
834
835 **Example 1: ** AT+TLSMOD=0,0  ~/~/ Disable TLS Mode.
836
837 **Example 2:**  AT+TLSMOD=1,0  ~/~/ No authentication
838
839 AT+TLSMOD=1,1  ~/~/ Perform server authentication
840
841 AT+TLSMOD=1,2  ~/~/ Perform server and client authentication if requested by the remote server
842
843 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x09(%%)**
844
845 Format: Command Code (0x09) followed by 2 bytes.
846
847 Example1:  Downlink Payload: **09 00 00    **~/~/ AT+TLSMOD=0,0
848
849 Example2:  Downlink Payload: **09 01 02    **~/~/ AT+TLSMOD=1,2
850
851
852 == 3.12 Set GNSS open time ==
853
854
855 Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated.
856
857 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GNSST**
858
859 Example: AT+GNSST=30  ~/~/ Set the GPS positioning time to 30 seconds
860
861 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x10(%%)**
862
863 Format: Command Code (0x10) followed by 2 bytes.
864
865 Example:  Downlink Payload: **10 00 1E    **~/~/ AT+GNSST=30
866
867
868 == 3.13 Turn on/off GPS ==
869
870
871 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GPS **
872
873 **Ex1:  **AT+GPS=0  ~/~/ Turn off GPS
874
875 **Ex2:  **AT+GPS=1  ~/~/ Turn on GPS
876
877 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x11(%%)**
878
879 Format: Command Code (0x11) followed by 1 byte.
880
881 Example:  Downlink Payload: **11 01   **~/~/ AT+GPS=1
882
883
884 == 3.14 Set GPS positioning interval ==
885
886
887 Feature: Set GPS positioning interval (unit: hour).
888
889 When GPS is enabled, the node automatically locates and uplinks each time it passes **GTDC time** after activation.
890
891 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GTDC**
892
893 Example: AT+GTDC=24  ~/~/ Set the GPS positioning interval to 24h.
894
895 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x12(%%)**
896
897 Format: Command Code (0x12) followed by 3 bytes.
898
899 Example: 24 hours:  24(D)=0x18(H)
900
901 Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
902
903
904 == 3.15 Set the search network time ==
905
906
907 Feature: Get or Set the time to join the network(unit: minutes).
908
909 (% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+CSQTIME**
910
911 Example: AT+CSQTIME=10  ~/~/ Set the search time to 10 minutes.
912
913 (% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x13(%%)**
914
915 Format: Command Code (0x13) followed by 1 byte.
916
917 Example:  Downlink Payload: **13 0A   **~/~/ AT+CSQTIME=10
918
919
920 == 3.16 Set the IPv4 or IPv6 ==
921
922
923 This command is used to set IP version.
924
925 (% style="color:blue" %)**AT command:**
926
927 * (% style="color:#037691; font-weight:bold" %)**AT+IPTYPE**(% style="color:#037691" %)**=1**(%%)**      **~/~/ IPv4
928 * (% style="color:#037691; font-weight:bold" %)**AT+IPTYPE**(% style="color:#037691" %)**=2**(%%)**      **~/~/ IPv6
929
930 == 3.17 Configure Network Category to be Searched for under LTE RAT. ==
931
932
933 (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+IOTMOD=xx(%%)**
934
935 (% style="color:#037691" %)**xx:**(%%)  **0:** eMTC
936
937 **1:** NB-IoT
938
939 **2:** eMTC and NB-IoT
940
941
942 == 3.18 Factory data reset ==
943
944
945 Two different restore factory Settings configurations.
946
947 (% style="color:blue" %)**AT command:**
948
949 * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
950 * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values **except for passwords**.
951
952 == 3.19 Set CoAP option ==
953
954
955 Feature: Set CoAP option, follow this link to set up the CoaP protocol.
956
957 (% style="color:blue" %)**AT command: **(% style="color:#037691; font-weight:bold" %)**AT+URI1~~AT+URI8**
958
959 (% style="color:#037691; font-weight:bold" %)**AT+URI1=11,"i"         **(%%)~/~/ "i/" indicates that the endpoint supports observation mode. In -CB products, fixed  setting AT+URI1=11,"i"
960
961 (% style="color:#037691; font-weight:bold" %)**AT+URI2=11,"CoAP endpoint URl"   **(%%)~/~/ 11 is a fixed parameter.
962
963 **Example: ** i/13a35fbe-9515-6e55-36e8-081fb6aacf86
964
965 AT+URI1=11,"i"
966
967 AT+URI2=11,"13a35fbe-9515-6e55-36e8-081fb6aacf86"
968
969 ~-~-> If multiple groups of CoAP endpoint urls:
970
971 AT+URI3=11,"i"
972
973 AT+URI4=11,"CoAP endpoint URl"
974
975
976 == 3.20 Power on / power off BG95 module ==
977
978
979 This command is used to power on and power off BG95 module.
980
981 * (% style="color:blue" %)**AT command: **(% style="color:#037691" %)**AT+QSW**
982
983 The module is powered on after the command is sent for the first time, and powered off after the command is sent again.
984
985 [[image:image-20250111135034-6.png||height="600" width="834"]]
986
987
988 == 3.21 Example Query saved historical records ==
989
990
991 Read or Clear cached data.
992
993
994 * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CDP(%%)**
995
996 This command can be used to search the saved history, recording up to 32 groups of data, each group of historical data contains a maximum of 100 bytes.
997
998
999 [[image:image-20250111135152-7.png||height="607" width="848"]]
1000
1001 * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CDP=0(%%)**
1002
1003 Clear cached data.
1004
1005
1006 == 3.22 Uplink log query ==
1007
1008
1009 * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+GETLOG(%%)**
1010
1011 This command can be used to query upstream logs of data packets.
1012
1013 [[image:image-20250111135224-8.png||height="611" width="851"]]
1014
1015
1016 == 3.23 Set the downlink debugging mode ==
1017
1018
1019 Feature: Set the conversion between the standard version and 1T version downlinks.
1020
1021 (% style="color:blue" %)**AT command: AT+DOWNTE**
1022
1023 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1024 |=(% style="width: 134px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 143px; background-color: rgb(79, 129, 189); color: white;" %)**Function/Parameters**|=(% style="width: 233px; background-color: rgb(79, 129, 189); color: white;" %)**Response/Explanation**
1025 |(% style="width:134px" %)AT+DOWNTE=?|(% style="width:143px" %)Get current Settings|(% style="width:229px" %)(((
1026 0,0  (default)
1027 OK
1028 )))
1029 |(% colspan="1" rowspan="2" style="width:134px" %)(((
1030
1031
1032
1033
1034 AT+DOWNTE=a,b
1035 )))|(% style="width:143px" %)**a**: Set the conversion between the downlink of the standard version and 1T version|(% style="width:229px" %)(((
1036 **0**: Set the downlink of the standard version.
1037 **1**: Set the downlink of the 1T version(ThingsEye platform)
1038 )))
1039 |(% style="width:143px" %)**b**: Enable/Disable downlink debugging|(% style="width:229px" %)(((
1040 **0**: Disable downlink debugging mode.
1041 **1**: Enable downlink debugging mode, users can see the original downlink reception.
1042 )))
1043
1044 **Example:**
1045
1046 * AT+DOWNTE=0,1  ~/~/ Set to standard version downlink, and enable downlink debugging.
1047 * AT+DOWNTE=1,1  ~/~/ Set to 1T version downlink, and enable downlink debugging.
1048
1049 (% style="color:blue" %)**Downlink Command:  **
1050
1051 No downlink commands for feature
1052
1053
1054 == 3.24 PH calibration ==
1055
1056
1057 Specific operation steps(Applicable to all sensors)
1058 ~1. Put the sensor into the corresponding calibration liquid.
1059 2. Restart the device.
1060 3. Send calibration instructions.
1061 4. Receive the byte corresponding to return.
1062 5. Received OK is a successful calibration.
1063
1064 Feature: This command is used for three-point calibration of PH standard buffer solutions.
1065
1066 (% style="color:blue" %)**AT command: AT+CALPH**
1067
1068 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1069 |=(% style="width: 134px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 151px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 225px; background-color: rgb(79, 129, 189); color: white;" %)**Response**
1070 |(% style="width:134px" %)AT+CALPH=4|(% style="width:151px" %)Calibrate 4.00 standard buffer|(% style="width:223px" %)(((
1071 HEX:10 06 00 22 07 24 28 aa
1072 OK
1073 )))
1074 |(% colspan="1" style="width:134px" %)(((
1075 AT+CALPH=6
1076 )))|(% style="width:151px" %)Calibrate 6.86
1077 standard buffer|(% style="width:223px" %)(((
1078 HEX:10 06 00 21 07 4e 58 85
1079 OK
1080 )))
1081 |(% colspan="1" style="width:134px" %)AT+CALPH=9|(% style="width:151px" %)Calibrate 9.18 standard buffer|(% style="width:223px" %)(((
1082 HEX:10 06 00 20 08 bc 8d 30
1083 OK
1084 )))
1085
1086 (% style="color:blue" %)**Downlink Command:  **
1087
1088 No downlink commands for feature
1089
1090
1091 == 3.25 ORP calibration ==
1092
1093
1094 Feature: This command is used for two-point calibration of ORP standard buffer solutions.
1095
1096 (% style="color:blue" %)**AT command: AT+CALORP**
1097
1098 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1099 |=(% style="width: 134px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 151px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 225px; background-color: rgb(79, 129, 189); color: white;" %)**Response**
1100 |(% style="width:134px" %)(((
1101 AT+CALORP=86
1102 )))|(% style="width:151px" %)Calibrate 86mV standard buffer|(% style="width:223px" %)(((
1103 HEX:13 06 00 24 07 dc c9 1a
1104 OK
1105 )))
1106 |(% colspan="1" style="width:134px" %)AT+CALORP=256|(% style="width:151px" %)Calibrate 256mV
1107 standard buffer|(% style="width:223px" %)(((
1108 HEX:13 06 00 25 07 37 d8 95
1109 OK
1110 )))
1111
1112 (% style="color:blue" %)**Downlink Command:  **
1113
1114 No downlink commands for feature
1115
1116
1117 == 3.26 EC calibration ==
1118
1119
1120 Feature: This command is used for two-point calibration of EC standard buffer solutions.
1121
1122 (% style="color:blue" %)**AT command: AT+CALEC**
1123
1124 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1125 |=(% style="width: 134px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 161px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 215px; background-color: rgb(79, 129, 189); color: white;" %)**Response**
1126 |(% style="width:134px" %)(((
1127 AT+CALEC=1
1128 )))|(% style="width:161px" %)Calibrate 1413HS/cm
1129 standard buffer|(% style="width:215px" %)(((
1130 HEX:12 01 00 26 00 02 A2 A0
1131 OK
1132 )))
1133 |(% colspan="1" style="width:134px" %)AT+CALEC=10|(% style="width:161px" %)Calibrate 12.88mS/cm
1134 standard buffer|(% style="width:215px" %)(((
1135 HEX:11 06 00 26 00 02 EB 50
1136 OK
1137 )))
1138
1139 (% style="color:blue" %)**Downlink Command:  **
1140
1141 No downlink commands for feature
1142
1143
1144 == 3.27 NTU calibration ==
1145
1146
1147 Feature: This command is used for turbidity calibration.
1148
1149 (% style="color:blue" %)**AT command: AT+CALNTU**
1150
1151 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1152 |=(% style="width: 134px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 172px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 204px; background-color: rgb(79, 129, 189); color: white;" %)**Response**
1153 |(% style="width:134px" %)AT+CALNTU=0|(% style="width:172px" %)Calibrate(((
1154 0NTU turbidity solution
1155 )))|(% style="width:233px" %)(((
1156 HEX:15 06 00 5E 00 01 2A CC
1157 OK
1158 )))
1159 |(% colspan="1" style="width:134px" %)AT+CALNTU=2|(% style="width:172px" %)Calibrate(((
1160 200NTU turbidity solution
1161 )))|(% style="width:233px" %)(((
1162 HEX:15 06 00 5E 00 02 6A CD
1163 OK
1164 )))
1165 |(% colspan="1" style="width:134px" %)AT+CALNTU=4|(% style="width:172px" %)Calibrate(((
1166 400NTU turbidity solution
1167 )))|(% style="width:233px" %)(((
1168 HEX:15 06 00 5E 00 03 AB 0D
1169 OK
1170 )))
1171 |(% colspan="1" style="width:134px" %)AT+CALNTU=6|(% style="width:172px" %)Calibrate(((
1172 600NTU turbidity solution
1173 )))|(% style="width:233px" %)(((
1174 HEX:15 06 00 5E 00 04 EA CF
1175 OK
1176 )))
1177 |(% colspan="1" style="width:134px" %)AT+CALNTU=8|(% style="width:172px" %)Calibrate(((
1178 800NTU turbidity solution
1179 )))|(% style="width:233px" %)(((
1180 HEX:15 06 00 5E 00 05 2B 0F
1181 OK
1182 )))
1183 |(% colspan="1" style="width:134px" %)AT+CALNTU=10|(% style="width:172px" %)Calibrate(((
1184 1000NTU turbidity solution
1185 )))|(% style="width:233px" %)(((
1186 HEX:15 06 00 5E 00 06 6B 0E
1187 OK
1188 )))
1189
1190 (% style="color:blue" %)**Downlink Command:  **
1191
1192 No downlink commands for feature
1193
1194
1195 == 3.28 Set the downlink debugging mode(Since firmware v1.1.0) ==
1196
1197
1198 Feature: Set the conversion between the standard version and 1T version downlinks.
1199
1200 (% style="color:blue" %)**AT command: AT+DOWNTE**
1201
1202 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1203 |=(% style="width: 134px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 143px; background-color: rgb(79, 129, 189); color: white;" %)**Function/Parameters**|=(% style="width: 233px; background-color: rgb(79, 129, 189); color: white;" %)**Response/Explanation**
1204 |(% style="width:134px" %)AT+DOWNTE=?|(% style="width:143px" %)Get current Settings|(% style="width:229px" %)(((
1205 0,0  (default)
1206
1207 OK
1208 )))
1209 |(% colspan="1" rowspan="2" style="width:134px" %)(((
1210
1211
1212
1213
1214 AT+DOWNTE=a,b
1215 )))|(% style="width:143px" %)**a**: Set the conversion between the downlink of the standard version and 1T version|(% style="width:229px" %)(((
1216 **0**: Set the downlink of the standard version.
1217 **1**: Set the downlink of the 1T version(ThingsEye platform)
1218 )))
1219 |(% style="width:143px" %)**b**: Enable/Disable downlink debugging|(% style="width:229px" %)(((
1220 **0**: Disable downlink debugging mode.
1221 **1**: Enable downlink debugging mode, users can see the original downlink reception.
1222 )))
1223
1224 **Example:**
1225
1226 * AT+DOWNTE=0,1  ~/~/ Set to standard version downlink, and enable downlink debugging.
1227 * AT+DOWNTE=1,1  ~/~/ Set to 1T version downlink, and enable downlink debugging.
1228
1229 (% style="color:blue" %)**Downlink Command:  **
1230
1231 No downlink commands for feature
1232
1233
1234 == 3.29 Domain name resolution settings(Since firmware v1.1.1) ==
1235
1236
1237 Feature: Set static DNS resolution IP address.
1238
1239 (% style="color:blue" %)**AT command: AT+BKDNS**
1240
1241 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1242 |=(% style="width: 138px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 143px; background-color: rgb(79, 129, 189); color: white;" %)**Function/Parameters**|=(% style="width: 229px; background-color: rgb(79, 129, 189); color: white;" %)**Response/Explanation**
1243 |(% style="width:134px" %)(((
1244 AT+BKDNS=?
1245 )))|(% style="width:143px" %)Get current Settings|(% style="width:606px" %)(((
1246 1,0,NULL  (default)
1247 OK
1248 )))
1249 |(% colspan="1" rowspan="3" style="width:134px" %)(((
1250
1251
1252
1253
1254
1255
1256 AT+BKDNS=a,b,c
1257 )))|(% style="width:143px" %)(((
1258 **a**: Enable/Disable static DNS resolution.
1259 )))|(% style="width:606px" %)(((
1260 **0:** Disable static DNS resolution
1261
1262 **1**: Enable static DNS resolution. The ip address will be saved after the domain name is resolved, if the next domain name resolution fails, the last saved ip address will be used.
1263 )))
1264 |(% style="width:143px" %)**b**: Meaningless.|(% style="width:606px" %)(((
1265 Set to **0**.
1266 )))
1267 |(% style="width:143px" %)(((
1268 **c**: Set the IP address manually.
1269 )))|(% style="width:606px" %)(((
1270 The format is the same as AT+SERVADDR.
1271 If domain name resolution fails, this ip address will be used directly, if domain name resolution succeeds, parameter c will be updated to the successfully resolved IP address.
1272 )))
1273
1274 **Example:**
1275
1276 * AT+BKDNS=0,0,NULL  ~/~/Disable static DNS resolution.
1277 * AT+BKDNS=1,0,NULL  ~/~/ Enable static DNS resolution.
1278 * AT+BKDNS=1,0,3.69.98.183,1883  ~/~/Enable static DNS resolution, if domain name resolution succeeds, the node uses the ip address successfully resolved and saves it to parameter c. If the domain name resolution fails, use the manually set ip address: 3.69.98.183 for communication.
1279
1280 (% style="color:blue" %)**Downlink Command:  **
1281
1282 No downlink commands for feature.
1283
1284
1285 = 4. Water Qualit Sensors =
1286
1287 == 4.1  PH Sensor ==
1288
1289
1290 (((
1291 PH01 is a device for measuring the pH value (hydrogen ion concentration index, acidity and alkalinity) of a solution.
1292
1293 It adopts an integrated design, is lighter and simpler in structure, and is more convenient to use. The waterproof grade is IP68.
1294
1295 The reference electrode adopts a double salt bridge design, which has stronger anti-pollution ability.
1296
1297 This product is suitable for industrial sewage, domestic sewage, agriculture, aquaculture and other scenes in non-corrosive weak acid and weak alkali environments.
1298 )))
1299
1300
1301 === 4.1.1 Feature ===
1302
1303
1304 * pH measurement range 0~~14pH, resolution 0.01pH.
1305 * One-piece design, light and simple structure, easy to use.
1306 * The reference adopts a double salt bridge design, which has stronger anti-pollution ability and waterproof grade IP68.
1307 * The equipment adopts a wide voltage power supply DC 7~~30V.
1308
1309 === 4.1.2 Specification ===
1310
1311
1312 * **Power supply**: DC7~~30V
1313 * **Power consumption**: ≤0.5W
1314 * **Communication interface**: RS485; standard MODBUS-RTU protocol; communication baud rate: default 9600
1315 * **pH measurement range**: 0~~14.00pH; resolution: 0.01pH
1316 * **pH measurement error**: ±0.15pH
1317 * **Repeatability error**: ±0.02pH
1318 * **Working environment:**
1319 ** Ambient Temperature: 0–60°C
1320 ** Relative Humidity: <85% RH(Specifically refers to the cable male and female)
1321 * **Waterproof grade**: IP68
1322 * **Pressure resistance**: 0.6MPa
1323
1324 === 4.1.3 Dimension ===
1325
1326
1327 [[image:image-20240715181651-3.png||height="223" width="562"]]
1328
1329
1330 === 4.1.4 Installation Notice ===
1331
1332
1333 (((
1334 Do not power on while connect the cables. Double check the wiring before power on.
1335 )))
1336
1337 (((
1338 Installation Photo as reference:
1339 )))
1340
1341
1342 (((
1343 (% style="color:#4472c4" %)** Submerged installation:**
1344 )))
1345
1346 (((
1347 The lead wire of the equipment passes through the waterproof pipe, and the 3/4 thread on the top of the equipment is connected to the 3/4 thread of the waterproof pipe with raw tape. Ensure that the top of the equipment and the equipment wire are not flooded.
1348
1349
1350 [[image:image-20240715181933-4.png||height="281" width="258"]]
1351 )))
1352
1353
1354 (((
1355 (% style="color:#4472c4" %)** Pipeline installation:**
1356 )))
1357
1358 (((
1359 Connect the equipment to the pipeline through the 3/4 thread.
1360 )))
1361
1362 [[image:image-20240715182122-6.png||height="291" width="408"]]
1363
1364
1365 (% style="color:#4472c4" %)**Sampling:**
1366
1367 Take representative water samples according to sampling requirements. If it is inconvenient to take samples, you can also put the electrode into the solution to be tested and read the output data. After a period of time, take out the electrode and clean it.
1368
1369
1370 (% style="color:#4472c4" %)**Measure the pH of the water sample:**
1371
1372 First rinse the electrode with distilled water, then rinse it with the water sample, then immerse the electrode in the sample, carefully shake the test cup or stir it to accelerate the electrode balance, let it stand, and record the pH value when the reading is stable.
1373
1374
1375 === 4.1.5 Maintenance ===
1376
1377
1378 * The equipment itself generally does not require daily maintenance. When an obvious fault occurs, please do not open it and repair it yourself. Contact us as soon as possible!
1379 * There is an appropriate amount of soaking solution in the protective bottle at the front end of the electrode. The electrode head is soaked in it to keep the glass bulb and the liquid junction activated. When measuring, loosen the bottle cap, pull out the electrode, and rinse it with pure water before use.
1380 * Preparation of electrode soaking solution: Take a packet of PH4.00 buffer, dissolve it in 250 ml of pure water, and soak it in 3M potassium chloride solution. The preparation is as follows: Take 25 grams of analytical pure potassium chloride and dissolve it in 100 ml of pure water.
1381 * The glass bulb at the front end of the electrode cannot come into contact with hard objects. Any damage and scratches will make the electrode ineffective.
1382 * Before measurement, the bubbles in the electrode glass bulb should be shaken off, otherwise it will affect the measurement. When measuring, the electrode should be stirred in the measured solution and then placed still to accelerate the response.
1383 * The electrode should be cleaned with deionized water before and after measurement to ensure accuracy.
1384 * After long-term use, the pH electrode will become passivated, which is characterized by a decrease in sensitivity gradient, slow response, and inaccurate readings. At this time, the bulb at the bottom of the electrode can be soaked in 0.1M dilute hydrochloric acid for 24 hours (0.1M dilute hydrochloric acid preparation: 9 ml of hydrochloric acid is diluted to 1000 ml with distilled water), and then soaked in 3.3M potassium chloride solution for 24 hours. If the pH electrode is seriously passivated and soaking in 0.1M hydrochloric acid has no effect, the pH electrode bulb can be soaked in 4% HF (hydrofluoric acid) for 3-5 seconds, washed with pure water, and then soaked in 3.3M potassium chloride solution for 24 hours to restore its performance.
1385 * Glass bulb contamination or liquid junction blockage can also cause electrode passivation. At this time, it should be cleaned with an appropriate solution according to the nature of the contaminant.
1386 * (((
1387 The equipment should be calibrated before each use. For long-term use, it is recommended to calibrate once every 3 months. The calibration frequency should be adjusted appropriately according to different application conditions (degree of dirt in the application, deposition of chemical substances, etc.). After aging, the electrodes should be replaced in time.
1388 )))
1389
1390 === 4.1.6 Calibration ===
1391
1392
1393 This device uses three-point calibration, and three known PH standard solutions need to be prepared.
1394
1395 (% style="color:#4472c4" %)**The steps are as follows:**
1396
1397 (1) Wash the electrode in distilled water, and put it in 9.18 standard buffer solution. After the data stabilizes, enter the following calibration command, that is, 9.18 calibration is completed. (% style="color:#4472c4" %)**"AT+CALPH=9" **(%%)
1398
1399
1400 (2) Wash the electrode in distilled water, and put it in 6.86 standard buffer solution. After the data stabilizes, enter the following calibration command, that is, 6.86 calibration is completed; (% style="color:#4472c4" %)**"AT+CALPH=6" **(%%)
1401
1402
1403 (3) Wash the electrode in distilled water, and put it in 4.01 standard buffer solution. After the data stabilizes, enter the following calibration command, that is, 4.00 calibration is completed. (% style="color:#4472c4" %)**"AT+CALPH=4" **(%%)
1404
1405
1406 == 4.2 EC Sensor ==
1407
1408
1409 EC K1/K10 is a device for measuring the conductivity of solutions. EC K1/K10 adopts an integrated design, which is lighter and simpler in structure and more convenient to use.
1410
1411 The waterproof grade is IP68. It can be widely used in continuous monitoring of the conductivity of aqueous solutions such as cross-section water quality, aquaculture, sewage treatment, environmental protection, pharmaceuticals, food and tap water.
1412
1413 (((
1414
1415 )))
1416
1417 === 4.2.1 Feature ===
1418
1419
1420 * Conductivity measurement range is 0-2000us/cm; 10~~20000us/cm.
1421 * Integrated design, light and simple structure, easy to use.
1422 * Waterproof grade IP68.
1423 * With salinity and TDS conversion function.
1424 * RS485 communication interface: MDDBUS RTU communication protocol can be easily connected to the computer for monitoring and communication.
1425 * ModBus communication address can be set and baud rate can be modified.
1426 * The device adopts wide voltage power supply, DC 7~~30V is available.
1427
1428 === 4.2.2 Specification ===
1429
1430
1431 * **Power supply**: DC7~~30V
1432 * **Power consumption**: ≤0.5W
1433 * **Communication interface**: RS485; standard MODBUS-RTU protocol; communication baud rate: default 9600
1434 * **Conductivity measurement range**: K=1: 0~~2000μs/cm; resolution: 1μs/cm K=10: 10~~20000μs/cm; resolution: 10μs/cm 200:0-200000 μS/cm; resolution: 1 μS/cm
1435 * **Conductivity measurement error**: ±1%FS
1436 * **Working environment:**
1437 ** Ambient Temperature: 0–60°C
1438 ** Relative Humidity: <85% RH(Specifically refers to the cable male and female)
1439 * **Waterproof grade**: IP68
1440 * **Pressure resistance**: 0.6MPa
1441
1442 === 4.2.3 Dimension ===
1443
1444
1445 [[image:image-20240715181651-3.png||height="223" width="562"]]
1446
1447
1448 === 4.2.4 Installation Notice ===
1449
1450
1451 Selection of matching electrode constant
1452
1453 [[image:image-20240716104100-1.png||height="349" width="641"]]
1454
1455
1456 (% style="color:#4472c4" %)**Electrode installation form**
1457
1458 A:Side wall installation
1459
1460 B:Top flange installation
1461
1462 C:Pipeline bend installation
1463
1464 D:Pipeline bend installation
1465
1466 E:Flow-through installation
1467
1468 F:Submerged installation
1469
1470 [[image:image-20240716104537-2.png||height="475" width="706"]]
1471
1472 (% style="color:#4472c4" %)**Several common installation methods of electrodes**
1473
1474 When installing the sensor on site, you should strictly follow the correct installation method shown in the following picture. Incorrect installation method will cause data deviation.
1475
1476 A. Several common incorrect installation methods
1477
1478 [[image:image-20240717103452-1.png||height="320" width="610"]]
1479
1480 Error cause: The electrode joint is too long, the extension part is too short, the sensor is easy to form a dead cavity, resulting in measurement error.
1481
1482
1483 [[image:image-20240716105124-4.png||height="326" width="569"]]
1484
1485 Error cause: Measurement error or instability may occur due to water flow not being able to fill the pipe or air accumulation at high altitudes.
1486
1487 B. Correct installation method
1488
1489 [[image:image-20240716105318-5.png||height="330" width="594"]]
1490
1491
1492 === 4.2.5 Maintenance ===
1493
1494
1495 * The equipment itself generally does not require daily maintenance. When an obvious fault occurs, please do not open it and repair it yourself, and contact us as soon as possible.
1496 * If the electrode is not used for a long time, it can generally be stored in a dry place, but it must be placed (stored) in distilled water for several hours before use to activate the electrode. Electrodes that are frequently used can be placed (stored) in distilled water.
1497 * Cleaning of conductivity electrodes: Organic stains on the electrode can be cleaned with warm water containing detergent, or with alcohol. Calcium and magnesium precipitates are best cleaned with 10% citric acid. The electrode plate or pole can only be cleaned by chemical methods or by shaking in water. Wiping the electrode plate will damage the coating (platinum black) on the electrode surface.
1498 * The equipment should be calibrated before each use. It is recommended to calibrate it every 3 months for long-term use. The calibration frequency should be adjusted appropriately according to different application conditions (degree of dirt in the application, deposition of chemical substances, etc.).
1499
1500 === 4.2.6 Calibration ===
1501
1502
1503 This device uses one-point calibration, and you need to prepare a known E standard solution. When the mileage K=1, 1~~2000 uses 1413uS/cm standard solution, and when the mileage K=10, 10~~20000 uses 12.88mS/cm standard solution.
1504
1505 (% style="color:#4472c4" %)**The steps are as follows:**
1506
1507 (1) Put the electrode in distilled water to clean it. When the mileage is 1~~2000, use 1413HS/cm standard solution.After the data is stable, enter the following calibration command
1508
1509 (% style="color:#4472c4" %)**"AT+CALEC=1" **
1510
1511 (2) Put the electrode in distilled water to clean it. When the range is 10~~20000, use 12.88mS/cm standard solution.After the data is stable, enter the following calibration command
1512
1513 (% style="color:#4472c4" %)**"AT+CALEC=10" **
1514
1515
1516 == 4.3 ORP Sensor ==
1517
1518
1519 (((
1520 ORP01 is a device for measuring the redox potential of a solution. It uses high-purity platinum to make an ORP composite electrode, which has strong acid and alkali resistance and antioxidant capacity, and has high measurement accuracy, fast response, and good stability.
1521
1522 The electrode can automatically compensate according to temperature. It is suitable for online monitoring of the redox potential of cyanide-containing and chromium-containing wastewater.
1523 )))
1524
1525
1526 === 4.3.1 Feature ===
1527
1528
1529 * ORP measurement range -1999~~1999mV, resolution 1mV.
1530 * Applicable electrode temperature 0~~80℃.
1531 * The electrode is made of high-purity platinum, which has strong acid and alkali resistance and antioxidant capacity, high measurement accuracy, fast response and good stability.
1532 * RS485 communication interface: ModBus-RTU communication protocol can be easily connected to the computer for monitoring and communication.
1533 * ModBus communication address can be set and baud rate can be modified.
1534 * The equipment adopts wide voltage power supply, DC 7~~30V
1535
1536 === 4.3.2 Specification ===
1537
1538
1539 * **Measuring range**: -1999~~1999mV
1540 * **Resolution**: 1mV
1541 * **Output signal**: RS485
1542 * **Measurement error**: ±3mV
1543 * **Stability**: ≤2mv/24 hours
1544 * **Working environment:**
1545 ** Ambient Temperature: 0–60°C
1546 ** Relative Humidity: <85% RH(Specifically refers to the cable male and female)
1547 * **Waterproof grade**: IP68
1548 * **Pressure resistance**: 0.6MP
1549
1550 === 4.3.3 Dimension ===
1551
1552
1553 [[image:image-20240715181651-3.png||height="223" width="562"]]
1554
1555 === 4.3.4 Installation Notice ===
1556
1557
1558 (((
1559 (% id="cke_bm_321773S" style="display:none" %) (%%)Do not power on while connect the cables. Double check the wiring before power on.
1560 )))
1561
1562 (((
1563 Installation Photo as reference:
1564 )))
1565
1566
1567 (((
1568 (% style="color:#4472c4" %)** Submerged installation:**
1569 )))
1570
1571 (((
1572 The lead wire of the equipment passes through the waterproof pipe, and the 3/4 thread on the top of the equipment is connected to the 3/4 thread of the waterproof pipe with raw tape. Ensure that the top of the equipment and the equipment wire are not flooded.
1573
1574
1575 [[image:image-20240715181933-4.png||height="281" width="258"]]
1576 )))
1577
1578
1579 (((
1580 (% style="color:#4472c4" %)** Pipeline installation:**
1581 )))
1582
1583 (((
1584 Connect the equipment to the pipeline through the 3/4 thread.
1585 )))
1586
1587 [[image:image-20240715182122-6.png||height="291" width="408"]]
1588
1589 === 4.3.5 Maintenance ===
1590
1591
1592 (1) The equipment itself generally does not require daily maintenance. When an obvious fault occurs, please do not open it and repair it yourself, and contact us as soon as possible.
1593 (2) In general, ORP electrodes do not need to be calibrated and can be used directly. When there is doubt about the quality and test results of the ORP electrode, the electrode potential can be checked with an ORP standard solution to determine whether the ORP electrode meets the measurement requirements, and the electrode can be recalibrated or replaced with a new ORP electrode. The frequency of calibration or inspection of the measuring electrode depends on different application conditions (the degree of dirt in the application, the deposition of chemical substances, etc.).
1594 (3) There is an appropriate soaking solution in the protective bottle at the front end of the electrode, and the electrode head is soaked in it to ensure the activation of the platinum sheet and the liquid junction. When measuring, loosen the bottle cap, pull out the electrode, and rinse it with pure water before use.
1595 (4) Preparation of electrode soaking solution: Take 25 grams of analytical pure potassium chloride and dissolve it in 100 ml of pure water to prepare a 3.3M potassium chloride solution.
1596 (5) Before measuring, the bubbles in the electrode glass bulb should be shaken off, otherwise it will affect the measurement. When measuring, the electrode should be stirred in the measured solution and then placed still to accelerate the response.
1597 (6) The electrode should be cleaned with deionized water before and after the measurement to ensure the measurement accuracy.
1598 (7) After long-term use, the ORP electrode will be passivated, which is manifested as a decrease in sensitivity gradient, slow response, and inaccurate readings. At this time, the platinum sheet at the bottom of the electrode can be soaked in 0.1M dilute hydrochloric acid for 24 hours (0.1M dilute hydrochloric acid preparation: 9 ml of hydrochloric acid is diluted to 1000 ml with distilled water), and then soaked in 3.3M potassium chloride solution for 24 hours to restore its performance.
1599 (8) Electrode contamination or liquid junction blockage can also cause electrode passivation. At this time, it should be cleaned with an appropriate solution according to the nature of the contaminant. If the platinum of the electrode is severely contaminated and an oxide film is formed, toothpaste can be applied to the platinum surface and then gently scrubbed to restore the platinum's luster.
1600 (9) The equipment should be calibrated before each use. It is recommended to calibrate once every 3 months for long-term use. The calibration frequency should be adjusted appropriately according to different application conditions (degree of dirt in the application, deposition of chemical substances, etc.). After aging, the electrodes should be replaced in time.
1601
1602
1603 === 4.3.6 Calibration ===
1604
1605
1606 OPR01 uses two-point calibration. You need to prepare two known ORP standard solutions.
1607
1608 (% style="color:#4472c4" %)**The steps are as follows:**(%%)
1609 (1) Put the electrode in distilled water to clean it, put it in 86mV standard buffer, wait for the data to stabilize, enter the following calibration command, and the 86mV point calibration is completed.
1610
1611 (% style="color:#4472c4" %)**"AT+CALORP=86" **(%%)
1612 (2) Put the electrode in distilled water to clean it, put it in 256mV standard buffer, wait for the data to stabilize, enter the following calibration command, and the 256mV point calibration is completed.
1613
1614 (% style="color:#4472c4" %)**"AT+CALORP=256" **
1615
1616
1617 == 4.4  Dissolved Oxygen Sensor ==
1618
1619
1620 (((
1621 The fluorescence dissolved oxygen sensor is a newly developed online digital sensor, using imported components and advanced production technology and surface mounting technology.
1622
1623 It has an IP68 waterproof rating, and the cable is seawater-proof. It can be directly put into the water without a protective tube, ensuring the long-term stability, reliability and accuracy of the sensor.
1624
1625 The fluorescence dissolved oxygen sensor is based on the principle of quenching active fluorescence by specific substances in physics.
1626
1627 The blue light from a light-emitting diode (LED) shines on the fluorescent material on the inner surface of the fluorescent cap.
1628
1629 The fluorescent material on the inner surface is excited and emits red light.
1630
1631 By detecting the phase difference between the red light and the blue light and comparing it with the internal calibration value, the concentration of oxygen molecules is calculated, and the final value is automatically compensated for temperature and air pressure.
1632 )))
1633
1634
1635 === 4.4.1 Feature ===
1636
1637
1638 * Small size, low power consumption, easy to carry.
1639 * Truly achieve low cost, low price, high performance.
1640 * High integration, long life, high reliability.
1641 * Up to four isolations, can resist complex interference conditions on site, waterproof level IP68.
1642 * The electrode uses high-quality low-noise cable, which can make the signal output length reach more than 20 meters.
1643
1644 === 4.4.2 Specification ===
1645
1646
1647 * **Measuring range**: 0-20mg/L, 0-50℃
1648 * **Accuracy**: 3%, ±0.5℃
1649 * **Resolution**: 0.01 mg/L, 0.01℃
1650 * **Maximum operating pressure**: 6 bar
1651 * **Output signal**: A: 4-20mA (current loop)
1652 * B: RS485 (standard Modbus-RTU protocol, device default address: 01)
1653 * **Power supply voltage**: 5-24V DC
1654 * **Working environment:**
1655 ** Ambient Temperature: 0–60°C
1656 ** Relative Humidity: <85% RH(Specifically refers to the cable male and female)
1657 * **Power consumption**: ≤0.5W
1658
1659 === 4.4.3 Dimension ===
1660
1661
1662 [[image:image-20240717105043-2.png||height="232" width="515"]]
1663
1664 === 4.4.4 Instructions for use and maintenance ===
1665
1666
1667 * Sampling: Take representative water samples according to the sampling requirements.
1668 * Determine dissolved oxygen in water samples: First rinse the electrode three times with distilled water, then rinse it three times with the water sample, then immerse the electrode in the sample, carefully shake the test cup or stir it to accelerate the electrode balance, let it stand, and record the dissolved oxygen when the reading is stable.
1669 * If it is inconvenient to take samples, you can also put the electrode in the measured solution, wait for the measured data to stabilize, read the output data, and take out the electrode after a period of time. Clean it.
1670 * After the sample measurement is completed, rinse the electrode three times with distilled water and put the electrode back in the protective solution upright.
1671
1672 Note: When measuring multiple samples, the electrode should be cleaned before measuring the next sample to avoid affecting the experimental data.
1673
1674 If the water conditions are complex and you want accurate data, you need to wipe the sensor probe frequently.
1675
1676
1677 === 4.4.5 Precautions ===
1678
1679
1680 * To ensure that the electrode measures correctly on the pipeline, avoid bubbles between the measuring cells that may cause data inaccuracy.
1681 * Please check whether the packaging is intact and whether the product model is consistent with the selected model.
1682 * Do not connect the wires with power on. After the wiring is completed and checked, power can be turned on.
1683 * Do not arbitrarily change the components or wires that have been welded at the factory when using the product.
1684 * The sensor is a precision device. When using it, please do not disassemble it by yourself or contact the sensor surface with sharp objects or corrosive liquids to avoid damaging the product.
1685
1686 == 4.5  Turbidity Sensor ==
1687
1688
1689 (((
1690 The turbidity sensor is a newly developed online digital turbidity sensor, using imported components and advanced production technology and surface mounting technology.
1691
1692 It has an IP68 waterproof rating, and the cable is seawater-proof.It can be directly put into the water without a protective tube, ensuring the long-term stability, reliability and accuracy of the sensor. This sensor probe uses a scattered light turbidity measurement method.
1693
1694 Since the turbidity in the water sample causes light to scatter, the intensity of the scattered light in the direction perpendicular to the incident light is measured and compared with the internal calibration value to calculate the turbidity in the water sample.
1695
1696 The ambient light interference is eliminated by infrared light and filters. After linearization processing, the output signal is stable and accurate.
1697 )))
1698
1699
1700 === 4.5.1 Feature ===
1701
1702
1703 * RS485 Temperature, Humidity, Illuminance, Pressure sensor
1704 * Axial capacitor filtering is used internally, and 100MΩ resistor increases impedance and enhances stability.
1705 * Small size, low power consumption, and easy to carry.
1706 * Truly achieve low cost, low price, and high performance.
1707 * High integration, long life, and high reliability.
1708 * Up to four isolations can resist complex interference conditions on site, and the waterproof level is IP68.
1709 * The electrode uses high-quality low-noise cable, which can make the signal output length reach more than 20 meters
1710
1711 === 4.5.2 Specification ===
1712
1713
1714 * **Measuring range**: 0.1～1000.0NTU
1715 * **Accuracy**: ±5%
1716 * **Resolution**: 0.1NTU
1717 * **Stability**: ≤3mV/24 hours
1718 * **Output signal**: A: 4～20 mA (current loop)B: RS485 (standard Modbus-RTU protocol, device default address: 15)
1719 * **Power supply voltage**: 5～24V DC (when the output signal is RS485)
1720 * 12～24V DC (when the output signal is 4～20mA)
1721 * **Working environment:**
1722 ** Ambient Temperature: 0–60°C
1723 ** Relative Humidity: <85% RH(Specifically refers to the cable male and female)
1724 * **Power consumption**: ≤0.5W
1725
1726 === 4.5.3 Dimension ===
1727
1728
1729 [[image:image-20240717112849-3.png||height="285" width="582"]]
1730
1731
1732 === 4.5.4 Instructions for use and maintenance ===
1733
1734
1735 * It can be directly put into water without adding a protective tube, ensuring the long-term stability, reliability and accuracy of the sensor.
1736 * If the water conditions are complex and you want accurate data, you need to wipe the sensor probe frequently.
1737
1738 === 4.5.5 Calibration ===
1739
1740
1741 For turbidity calibration, you only need to prepare a solution. You can choose 0NTU, 200NTU, 400NTU, 600NTU, 800NTU, 1000NTU, and then enter the corresponding calibration command.
1742
1743 (% style="color:#4472c4" %)**"AT+CALNTU=0"         **(%%)0NTU turbidity solution
1744
1745 (% style="color:#4472c4" %)**"AT+CALNTU=2"         **(%%)200NTU turbidity solution
1746
1747 (% style="color:#4472c4" %)**"AT+CALNTU=4"         **(%%)400NTU turbidity solution
1748
1749 (% style="color:#4472c4" %)**"AT+CALNTU=6"         **(%%)600NTU turbidity solution
1750
1751 (% style="color:#4472c4" %)**"AT+CALNTU=8"         **(%%)800NTU turbidity solution
1752
1753 (% style="color:#4472c4" %)**"AT+CALNTU=10"      **(%%)1000NTU turbidity solution
1754
1755
1756 === 4.5.6 Precautions ===
1757
1758
1759 * To ensure that the electrode measures correctly on the pipeline, avoid bubbles between the measuring cells that may cause data inaccuracy.
1760 * Please check whether the packaging is intact and whether the product model is consistent with the selected model.
1761 * Do not connect the wires with power on. After the wiring is completed and checked, power can be turned on.
1762 * Do not arbitrarily change the components or wires that have been welded at the factory when using the product.
1763 * The sensor is a precision device. When using it, please do not disassemble it by yourself or contact the sensor surface with sharp objects or corrosive liquids to avoid damaging the product.
1764 * Do not power on while connect the cables. Double check the wiring before power on.
1765
1766 = 4.6 Residual Chlorine Sensor =
1767
1768 == 4.6.1 Specification: ==
1769
1770 * **Power Input**: DC7~~30
1771
1772 * **Power Consumption** : 0.19W
1773
1774 * **Interface**: RS485. 9600 Baud Rate
1775
1776 * **CL Range & Resolution:**
1777 ** **CL2ML:**0-2mg/L
1778 ** **CL10ML:**0-10mg/L
1779 ** **Resolution:**0.01mg/L
1780
1781 * **CL Accuracy**: ±5% FS
1782 * **Temperature Accuracy: **±0.5 °C
1783 * **Working environment:**
1784 ** Ambient Temperature: 0–50°C
1785 ** pH:4-9
1786 ** Flow rate: 30L/h~~60L/h (flow tank installation)
1787 * **IP Rated**: IP68
1788
1789 * **Max Pressure**: 0.6MPa
1790
1791 == 4.6.2 Mechinical Drawing ==
1792
1793 [[image:1752573238705-910.png||height="467" width="187"]]
1794
1795 == 4.6.3 Maintenance ==
1796
1797 * The device itself generally does not require daily maintenance. When an obvious fault occurs, please do not open it and repair it yourself, and contact us as soon as possible!
1798 * After using the electrode, please clean the electrode head with clean water and cover it with a protective cover.
1799 * When measuring the device, the measured liquid should flow and the flow rate should be uniform, and there should be no bubbles attached to the measuring end of the device.
1800 * If the electrode diaphragm is attached with dirt and mineral components, the sensitivity will be reduced, and it may not be possible to perform sufficient measurement. Please ensure that the platinum ring is clean.
1801 * The platinum induction ring of a good residual chlorine electrode should always be kept clean and bright. If the platinum ring of the electrode becomes rough or covered with pollutants after measurement, please clean it according to the following method: (For reference) Inorganic pollution: immerse the electrode in 0.1mol/L dilute hydrochloric acid for 15 minutes, gently wipe the platinum ring of the residual chlorine electrode with a cotton swab, and then wash it with tap water.
1802 * Organic or oil pollution: immerse the electrode in tap water with a small amount of detergent, such as dishwashing liquid, and thoroughly clean the sensing surface of the electrode sensor. Gently wipe the platinum ring of the electrode with a cotton swab, then rinse with tap water, and the cleaning is complete. If the platinum ring of the electrode has formed an oxide film, please use toothpaste or 1000-grit fine sandpaper to properly polish the sensing surface, and then clean it with tap water. The platinum ring is connected to the glass, so please handle it carefully when polishing.
1803 The electrode has a service life of about one year, and a new electrode should be replaced in time after aging.
1804 * Before the cable plug and the device plug are locked, do not put the plug part into water.
1805
1806 = 5. Battery & Power Consumption =
1807
1808
1809 WQS-CB use ER26500 + SPC1520 battery pack and WQS-CS use 3000mAh Recharable Battery with Solar Panel. See below link for detail information about the battery info and how to replace.
1810
1811 [[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
1812
1813
1814 = 6. FAQ =
1815
1816 == 6.1  External Power Supply Connection (For Battery Depletion/Multi-Sensor Use) ==
1817
1818 The WQS-CB system includes a 1-to-3 splitter cable for connecting multiple water quality sensors simultaneously. Please be aware that power consumption increases with each additional sensor connected. External power is strongly recommended when:
1819
1820 * The battery is depleted
1821 * Operating 2-3 sensors simultaneously
1822 * For extended monitoring periods
1823
1824 (% style="color:blue" %)**Connection Method:**
1825
1826 * Disconnect the battery wires
1827 * Use a power supply with 3.3V voltage and 2A current rating, connecting it to the battery terminals
1828
1829 (% style="color:blue" %)**Recommended Power Specifications: **(%%)3.3V/2A external supply
1830
1831 (% style="color:blue" %)**Compatible Power Adapter:**
1832
1833 [[image:1750239222397-509.png||height="350" width="231"]]
1834
1835 (% style="color:blue" %)**Connector Type:**
1836
1837 [[image:image-20230131145708-3.png]]
1838
1839 = 7. Firmware update =
1840
1841
1842 User can change device firmware to:
1843
1844 * Update with new features.
1845
1846 * Fix bugs.
1847
1848 Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/scl/fo/j8rg5kottlo2bc3ij3v5i/AMO7NBJfZ-kmRXKHpgqAGbw?rlkey=4nckz7xodql0yiaxkkan0wur9&st=fi4m70at&dl=0]]**
1849
1850 Methods to Update Firmware:
1851
1852 * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]].
1853
1854 * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
1855
1856 = 8. ​Packing Info =
1857
1858
1859 (% style="color:#037691" %)**Package Includes**:
1860
1861 * WQS-CB/CS Water Quality Sensor Transmitter Node x 1
1862
1863 * External antenna x 1
1864
1865 (% style="color:#037691" %)**Dimension and weight**:
1866
1867 * Device Size: 13.0 x 5 x 4.5 cm
1868
1869 * Device Weight: 150g
1870
1871 * Package Size / pcs : 14.0 x 8x 5 cm
1872
1873 * Weight / pcs : 180g
1874
1875 = 9. Sensors =
1876
1877
1878 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %)
1879 |=(% style="width: 300px;background-color:#4F81BD;color:white" %)**Sensor Model**|=(% style="width: 200px;background-color:#4F81BD;color:white" %)**Part Number**
1880 |(% style="width:462px" %)PH Sensor|(% style="width:120px" %)DR-PH01
1881 |(% style="width:462px" %)EC K1 Sensor|(% style="width:120px" %)DR-ECK1.0
1882 |(% style="width:462px" %)EC K10 Sensor|(% style="width:120px" %)DR-ECK10.0
1883 |(% style="width:462px" %)ORP Sensor|(% style="width:120px" %)DR-ORP1
1884 |(% style="width:462px" %)Dissolved Oxygen Sensor|(% style="width:120px" %)DR-DO1
1885 |(% style="width:462px" %)Turbidity Sensor|(% style="width:120px" %)DR-TS1
1886
1887 = 10. Support =
1888
1889
1890 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1891
1892 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].