Wiki source code of DDS20-NB -- NB-IoT Ultrasonic Liquid Level Sensor User Manual
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | (% style="text-align:center" %) | ||
2 | [[image:image-20230911134259-1.png||height="570" width="570"]] | ||
3 | |||
4 | |||
5 | **Table of Contents:** | ||
6 | |||
7 | {{toc/}} | ||
8 | |||
9 | |||
10 | |||
11 | |||
12 | |||
13 | |||
14 | = 1. Introduction = | ||
15 | |||
16 | == 1.1 What is DDS20-NB NB-IoT Ultrasonic liquid level Sensor == | ||
17 | |||
18 | |||
19 | The Dragino DDS20-NB is a **NB-IoT Ultrasonic liquid level sensor** for Internet of Things solution. It uses **none-contact method **to measure the **height of liquid** in a container without opening the container, and send IoT platform via NB-IoT network. | ||
20 | |||
21 | The DDS20-NB sensor is installed directly below the container to detect the height of the liquid level. User doesn't need to open a hole on the container to be tested. The none-contact measurement makes the measurement safety, easier and possible for some strict situation. | ||
22 | |||
23 | DDS20-NB uses **ultrasonic sensing technology** for distance measurement. DDS20-NB is of high accuracy to measure various liquid such as: **toxic substances**, **strong acids**, **strong alkalis** and **various pure liquids** in high-temperature and high-pressure airtight containers. | ||
24 | |||
25 | PS-NB-NA supports different uplink methods including **MQTT, MQTTs, UDP & TCP** for different application requirement, and support uplinks to various IoT Servers. | ||
26 | |||
27 | PS-NB-NA **supports BLE configure **and** OTA update** which make user easy to use. | ||
28 | |||
29 | PS-NB-NA is powered by **8500mAh Li-SOCI2 battery**, it is designed for long-term use up to severa years. | ||
30 | |||
31 | PS-NB-NA has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration. | ||
32 | |||
33 | |||
34 | [[image:image-20230911140426-2.png||height="320" width="951"]] | ||
35 | |||
36 | |||
37 | == 1.2 Features == | ||
38 | |||
39 | |||
40 | * NB-IoT Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 @H-FDD | ||
41 | * Ultra-low power consumption | ||
42 | * Liquid Level Measurement by Ultrasonic technology | ||
43 | * Measure through container, No need to contact Liquid | ||
44 | * Valid level range 20mm - 2000mm | ||
45 | * Accuracy: ±(5mm+S*0.5%) (S: Measure Value) | ||
46 | * Multiply Sampling and one uplink | ||
47 | * Support Bluetooth v5.1 remote configure and update firmware | ||
48 | * Uplink on periodically | ||
49 | * Downlink to change configure | ||
50 | * IP66 Waterproof Enclosure | ||
51 | * 8500mAh Battery for long term use | ||
52 | * Nano SIM card slot for NB-IoT SIM | ||
53 | |||
54 | == 1.3 Specification == | ||
55 | |||
56 | |||
57 | (% style="color:blue" %)**Common DC Characteristics:** | ||
58 | |||
59 | * Supply Voltage: 2.5v ~~ 3.6v | ||
60 | * Operating Temperature: -40 ~~ 85°C | ||
61 | |||
62 | (% style="color:blue" %)**NB-IoT Spec:** | ||
63 | |||
64 | (% style="color:#037691" %)**NB-IoT Module: BC660K-GL** | ||
65 | |||
66 | (% style="color:#037691" %)**Support Bands:** | ||
67 | |||
68 | * B1 @H-FDD: 2100MHz | ||
69 | * B2 @H-FDD: 1900MHz | ||
70 | * B3 @H-FDD: 1800MHz | ||
71 | * B4 @H-FDD: 2100MHz | ||
72 | * B5 @H-FDD: 860MHz | ||
73 | * B8 @H-FDD: 900MHz | ||
74 | * B12 @H-FDD: 720MHz | ||
75 | * B13 @H-FDD: 740MHz | ||
76 | * B17 @H-FDD: 730MHz | ||
77 | * B18 @H-FDD: 870MHz | ||
78 | * B19 @H-FDD: 870MHz | ||
79 | * B20 @H-FDD: 790MHz | ||
80 | * B25 @H-FDD: 1900MHz | ||
81 | * B28 @H-FDD: 750MHz | ||
82 | * B66 @H-FDD: 2000MHz | ||
83 | * B70 @H-FDD: 2000MHz | ||
84 | * B85 @H-FDD: 700MHz | ||
85 | |||
86 | (% style="color:blue" %)**Battery:** | ||
87 | |||
88 | * Li/SOCI2 un-chargeable battery | ||
89 | * Capacity: 8500mAh | ||
90 | * Self Discharge: <1% / Year @ 25°C | ||
91 | * Max continuously current: 130mA | ||
92 | * Max boost current: 2A, 1 second | ||
93 | |||
94 | (% style="color:blue" %)**Power Consumption** | ||
95 | |||
96 | * STOP Mode: 10uA @ 3.3v | ||
97 | * Max transmit power: 350mA@3.3v | ||
98 | |||
99 | == 1.4 Applications == | ||
100 | |||
101 | |||
102 | * Smart Buildings & Home Automation | ||
103 | * Logistics and Supply Chain Management | ||
104 | * Smart Metering | ||
105 | * Smart Agriculture | ||
106 | * Smart Cities | ||
107 | * Smart Factory | ||
108 | |||
109 | == 1.5 Sleep mode and working mode == | ||
110 | |||
111 | |||
112 | (% style="color:blue" %)**Deep Sleep Mode: **(%%)Sensor doesn't have any LoRaWAN activate. This mode is used for storage and shipping to save battery life. | ||
113 | |||
114 | (% style="color:blue" %)**Working Mode:** (%%)In this mode, Sensor will work as LoRaWAN Sensor to Join LoRaWAN 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. | ||
115 | |||
116 | |||
117 | == 1.6 Button & LEDs == | ||
118 | |||
119 | |||
120 | [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]] | ||
121 | |||
122 | |||
123 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
124 | |=(% style="width: 167px;background-color:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width:225px;background-color:#4F81BD;color:white" %)**Action** | ||
125 | |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)((( | ||
126 | If sensor has already attached to NB-IoT network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once. | ||
127 | Meanwhile, BLE module will be active and user can connect via BLE to configure device. | ||
128 | ))) | ||
129 | |(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)((( | ||
130 | (% 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 network. | ||
131 | (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
132 | 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 network or not. | ||
133 | ))) | ||
134 | |(% style="width:167px" %)Fast press ACT 5 times.|(% 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. | ||
135 | |||
136 | == 1.7 BLE connection == | ||
137 | |||
138 | |||
139 | S31x-NB support BLE remote configure and firmware update. | ||
140 | |||
141 | |||
142 | 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: | ||
143 | |||
144 | * Press button to send an uplink | ||
145 | * Press button to active device. | ||
146 | * Device Power on or reset. | ||
147 | |||
148 | If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode. | ||
149 | |||
150 | |||
151 | == 1.8 Pin Definitions & Switch == | ||
152 | |||
153 | |||
154 | S31x-NB use the mother board from S31-NB which as below. | ||
155 | |||
156 | [[image:image-20230819104805-5.png]] | ||
157 | |||
158 | |||
159 | === 1.8.1 Jumper JP2 === | ||
160 | |||
161 | |||
162 | Power on Device when put this jumper. | ||
163 | |||
164 | |||
165 | === 1.8.2 BOOT MODE / SW1 === | ||
166 | |||
167 | |||
168 | **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. | ||
169 | |||
170 | **2)** (% style="color:blue" %)**Flash**(%%): work mode, device starts to work and send out console output for further debug | ||
171 | |||
172 | |||
173 | === 1.8.3 Reset Button === | ||
174 | |||
175 | |||
176 | Press to reboot the device. | ||
177 | |||
178 | |||
179 | == 1.9 Hardware Variant == | ||
180 | |||
181 | |||
182 | (% border="1" cellspacing="5" style="width:410px" %) | ||
183 | |=(% style="width: 102px;background-color:#4F81BD;color:white" %)Model|=(% style="width: 126px; background-color:#4F81BD;color:white" %)Photo|=(% style="width: 179px;background-color:#4F81BD;color:white" %)Probe Info | ||
184 | |(% style="width:102px" %)((( | ||
185 | S31-NB | ||
186 | )))|(% style="width:126px" %)((( | ||
187 | (% style="text-align:center" %) | ||
188 | [[image:image-20230819110632-6.png||height="130" width="104"]] | ||
189 | )))|(% style="width:179px" %)((( | ||
190 | 1 x SHT31 Probe | ||
191 | |||
192 | Cable Length : 3 meters | ||
193 | |||
194 | |||
195 | ))) | ||
196 | |(% style="width:102px" %)((( | ||
197 | S31B-NB | ||
198 | )))|(% style="width:126px" %)((( | ||
199 | (% style="text-align:center" %) | ||
200 | [[image:image-20230819110702-7.png||height="164" width="90"]] | ||
201 | )))|(% style="width:179px" %)((( | ||
202 | 1 x SHT31 Probe | ||
203 | |||
204 | Installed in device. | ||
205 | ))) | ||
206 | |||
207 | (% style="display:none" %) | ||
208 | |||
209 | |||
210 | |||
211 | = 2. Use S31-NB to communicate with IoT Server = | ||
212 | |||
213 | == 2.1 Send data to IoT server via NB-IoT network == | ||
214 | |||
215 | |||
216 | The S31-NB is equipped with a NB-IoT module, the pre-loaded firmware in S31-NB 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 S31-NB. | ||
217 | |||
218 | |||
219 | Below shows the network structure: | ||
220 | |||
221 | [[image:1692415924540-357.png]] | ||
222 | |||
223 | |||
224 | There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1D**(%%) version of S31-NB. | ||
225 | |||
226 | |||
227 | (% 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 S31-NB send data to IoT server. | ||
228 | |||
229 | * 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]]. | ||
230 | |||
231 | * 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]]. | ||
232 | |||
233 | Below shows result of different server as a glance. | ||
234 | |||
235 | (% border="1" cellspacing="4" style="width:515px" %) | ||
236 | |(% 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** | ||
237 | |(% 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" %)((( | ||
238 | (% style="text-align:center" %) | ||
239 | [[image:image-20230819113244-8.png||height="183" width="367"]] | ||
240 | )))|(% style="width:170px" %) | ||
241 | |(% 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" %)((( | ||
242 | (% style="text-align:center" %) | ||
243 | [[image:image-20230819113244-9.png||height="119" width="367"]] | ||
244 | )))|(% style="width:170px" %) | ||
245 | |(% 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" %) | ||
246 | |(% 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" %) | ||
247 | |(% 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" %) | ||
248 | |(% 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" %)((( | ||
249 | (% style="text-align:center" %) | ||
250 | [[image:image-20230819113244-10.png||height="104" width="367"]] | ||
251 | )))|(% style="width:170px" %) | ||
252 | |(% 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" %)((( | ||
253 | (% style="text-align:center" %) | ||
254 | [[image:image-20230819113244-11.png||height="141" width="367"]] | ||
255 | )))|(% style="width:170px" %) | ||
256 | |||
257 | (% style="color:blue" %)**1D Version**(%%): This version has 1NCE SIM card pre-installed and configure to send value to DataCake. User Just need to select the sensor type in DataCake and Activate S31-NB and user will be able to see data in DataCake. See here for [[DataCake Config Instruction>>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]]. | ||
258 | |||
259 | |||
260 | == 2.2 Payload Types == | ||
261 | |||
262 | |||
263 | To meet different server requirement, S31-NB supports different payload type. | ||
264 | |||
265 | **Includes:** | ||
266 | |||
267 | * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5) | ||
268 | |||
269 | * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0) | ||
270 | |||
271 | * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1) | ||
272 | |||
273 | * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3) | ||
274 | |||
275 | User can specify the payload type when choose the connection protocol. Example: | ||
276 | |||
277 | (% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Use UDP Connection & hex Payload | ||
278 | |||
279 | (% style="color:#037691" %)**AT+PRO=2,5** (%%) ~/~/ Use UDP Connection & Json Payload | ||
280 | |||
281 | (% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload | ||
282 | |||
283 | |||
284 | === 2.2.1 General Json Format(Type~=5) === | ||
285 | |||
286 | |||
287 | This is the General Json Format. As below: | ||
288 | |||
289 | (% style="color:#4472c4" %)**{"IMEI":866207053462762,"temperature":29.2,"humidity":54.2,"battery":3.27,"signal":24,"Model":S31x-NB, "1":{28.2,48.3,2023/08/10 08:00:37},"2":{28.1,49.1,2023/08/10 07:57:37},"3":{28.1,48.5,2023/08/10 07:54:37},"4":{28.2,48.6,2023/08/10 07:51:37},"5":{28.1,48.9,2023/08/10 07:48:37},"6":{28.2,48.8,2023/08/10 07:45:37},"7":{28.2,48.8,2023/08/10 07:42:37},"8":{28.0,48.8,2023/08/10 07:39:37}}** | ||
290 | |||
291 | |||
292 | (% style="color:red" %)**Notice, from above payload:** | ||
293 | |||
294 | * Temperature , Humidity , Battery & Signal are the value at uplink time. | ||
295 | |||
296 | * Json entry 1 ~~ 8 are the last 1 ~~ 8 sampling data as specify by (% style="color:#037691" %)**AT+NOUD=8 ** (%%)Command. Each entry includes (from left to right): Temperature, Humidity, Sampling time. | ||
297 | |||
298 | === 2.2.2 HEX format Payload(Type~=0) === | ||
299 | |||
300 | |||
301 | This is the HEX Format. As below: | ||
302 | |||
303 | (% style="color:#4472c4" %)**f86620705346276200640cba16010000000011011801e864d49c2d011a01e364d49925011901eb64d49871011901e564d497bd011a01e664d49709011901e964d49655011a01e864d495a1011a01e864d494ed011801e864d49439** | ||
304 | |||
305 | [[image:1692424009971-458.png]] | ||
306 | |||
307 | |||
308 | (% style="color:blue" %)**Version:** | ||
309 | |||
310 | These bytes include the hardware and software version. | ||
311 | |||
312 | (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x00 for S31B-NB & S31-NB | ||
313 | |||
314 | (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x64=100, means firmware version 100 | ||
315 | |||
316 | |||
317 | (% style="color:blue" %)**BAT (Battery Info):** | ||
318 | |||
319 | Ex1: 0x0CBA = 3258mV | ||
320 | |||
321 | |||
322 | (% style="color:blue" %)**Signal Strength:** | ||
323 | |||
324 | NB-IoT Network signal Strength. | ||
325 | |||
326 | **Ex1: 0x16 = 22** | ||
327 | |||
328 | **0** -113dBm or less | ||
329 | |||
330 | **1** -111dBm | ||
331 | |||
332 | **2...30** -109dBm... -53dBm | ||
333 | |||
334 | **31** -51dBm or greater | ||
335 | |||
336 | **99** Not known or not detectable | ||
337 | |||
338 | |||
339 | (% style="color:blue" %)**Temperature: ** | ||
340 | |||
341 | If payload is: 0105H: (0105 & 8000 == 0), temp = 0105H /10 = 26.1 degree | ||
342 | |||
343 | If payload is: FF3FH : (FF3F & 8000 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. | ||
344 | |||
345 | (FF3F & 8000: Judge whether the highest bit is 1, when the highest bit is 1, it is negative) | ||
346 | |||
347 | |||
348 | (% style="color:blue" %)**Humidity: ** | ||
349 | |||
350 | Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% | ||
351 | |||
352 | |||
353 | (% style="color:blue" %)**TimeStamp: ** | ||
354 | |||
355 | Unit TimeStamp Example: 64d49439(H) = 1691653177(D) | ||
356 | |||
357 | Put the decimal value into this link(https:~/~/www.epochconverter.com/) to get the time. | ||
358 | |||
359 | |||
360 | === 2.2.3 ThingsBoard Payload(Type~=3) === | ||
361 | |||
362 | |||
363 | Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard. | ||
364 | |||
365 | (% style="color:#4472c4" %)**{"IMEI":866207053462762,"temperature":29.2,"humidity":54.2,"battery":3.27,"signal":24}** | ||
366 | |||
367 | |||
368 | === 2.2.4 ThingSpeak Payload(Type~=1) === | ||
369 | |||
370 | |||
371 | This payload meets ThingSpeak platform requirement. It includes only four fields. Form 1~~4 are: | ||
372 | |||
373 | Temperature, Humidity, Battery & Signal. This payload type only valid for ThingsSpeak Platform | ||
374 | |||
375 | As below: | ||
376 | |||
377 | (% style="color:#4472c4" %)**field1=27.9&field2=49.9&field3=3.23&field4=28** | ||
378 | |||
379 | |||
380 | == 2.3 Test Uplink and Change Update Interval == | ||
381 | |||
382 | |||
383 | By default, Sensor will send uplinks (% style="color:blue" %)**every 2 hours**(%%) & AT+NOUD=8 | ||
384 | |||
385 | User can use below commands to change the (% style="color:blue" %)**uplink interval**. | ||
386 | |||
387 | (% style="color:#037691" %)**AT+TDC=600 ** (%%) ~/~/ Set Update Interval to 600s | ||
388 | |||
389 | User can also push the button for more than 1 seconds to activate an uplink. | ||
390 | |||
391 | |||
392 | == 2.4 Multi-Samplings and One uplink == | ||
393 | |||
394 | |||
395 | To save battery life, S31-NB will sample temperature & humidity data every 15 minutes and send one uplink every 2 hours. So each uplink it will include 8 stored data + 1 real-time data. They are defined by: | ||
396 | |||
397 | * (% style="color:#037691" %)**AT+TR=900** (%%) ~/~/ The unit is seconds, and the default is to record data once every 900 seconds (15 minutes, the minimum can be set to 180 seconds) | ||
398 | |||
399 | * (% style="color:#037691" %)**AT+NOUD=8** (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. | ||
400 | |||
401 | The diagram below explains the relationship between TR, NOUD, and TDC more clearly: | ||
402 | |||
403 | [[image:1692424376354-959.png]] | ||
404 | |||
405 | |||
406 | == 2.5 Humidity and Temperature alarm function == | ||
407 | |||
408 | |||
409 | On each sampling define by AT+TR ( default 900s or 15 minutes), when the value exceed the range, it will trigger an Alarm and immediately sends a uplink. | ||
410 | |||
411 | |||
412 | (% style="color:blue" %)**AT Commands:** | ||
413 | |||
414 | (% style="color:#037691" %)**AT+ SHHUM=min,max** | ||
415 | |||
416 | Example: AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50 or higher than 80. | ||
417 | |||
418 | |||
419 | (% style="color:#037691" %)**AT+ SHTEMP=min,max** | ||
420 | |||
421 | Example: AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20 or higher than 30 | ||
422 | |||
423 | |||
424 | (% style="color:red" %)**Notice:** | ||
425 | |||
426 | * To disable Alarm, user can set min and max to same value , such as (% style="color:#037691" %)**AT+SHTEMP=0,0.** | ||
427 | |||
428 | * If user only want to send only min or max, user can set the alarm to a value that device won’t reach. For example: (% style="color:#037691" %)**AT+SHTEMP=-80,0.** | ||
429 | |||
430 | == 2.6 Trggier an uplink by external interrupt == | ||
431 | |||
432 | |||
433 | S31-NB has an external trigger interrupt function. Users can use the PB15 pin to trigger the upload of data packets. | ||
434 | |||
435 | (% style="color:blue" %)**AT command:** | ||
436 | |||
437 | * (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode | ||
438 | |||
439 | * (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt | ||
440 | |||
441 | * (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge | ||
442 | |||
443 | * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge | ||
444 | |||
445 | * (% style="color:#037691" %)**AT+INTMOD=3 **(%%) ~/~/ Trigger by rising edge | ||
446 | |||
447 | = 3. Configure S31x-NB = | ||
448 | |||
449 | == 3.1 Configure Methods == | ||
450 | |||
451 | |||
452 | S31x-NB supports below configure method: | ||
453 | |||
454 | * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]. | ||
455 | |||
456 | * 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.3UARTConnectionforSN50v3basemotherboard]]. | ||
457 | |||
458 | == 3.2 AT Commands Set == | ||
459 | |||
460 | |||
461 | AT+<CMD>? : Help on <CMD> | ||
462 | |||
463 | AT+<CMD> : Run <CMD> | ||
464 | |||
465 | AT+<CMD>=<value> : Set the value | ||
466 | |||
467 | AT+<CMD>=? : Get the value | ||
468 | |||
469 | |||
470 | (% style="color:blue" %)**General Commands** | ||
471 | |||
472 | AT : Attention | ||
473 | |||
474 | AT? : Short Help | ||
475 | |||
476 | ATZ : MCU Reset | ||
477 | |||
478 | AT+TDC : Application Data Transmission Interval | ||
479 | |||
480 | AT+CFG : Print all configurations | ||
481 | |||
482 | AT+CFGMOD : Working mode selection | ||
483 | |||
484 | AT+DEUI : Get or set the Device ID | ||
485 | |||
486 | AT+INTMOD : Set the trigger interrupt mode | ||
487 | |||
488 | AT+5VT : Set extend the time of 5V power | ||
489 | |||
490 | AT+PRO : Choose agreement | ||
491 | |||
492 | AT+RXDL : Extend the sending and receiving time | ||
493 | |||
494 | AT+DNSCFG : Get or Set DNS Server | ||
495 | |||
496 | AT+GETSENSORVALUE : Returns the current sensor measurement | ||
497 | |||
498 | AT+NOUD : Get or Set the number of data to be uploaded | ||
499 | |||
500 | AT+CDP : Read or Clear cached data | ||
501 | |||
502 | AT+SHTEMP: Get or Set alarm of temp | ||
503 | |||
504 | AT+SHHUM: Get or Set alarm of moisture | ||
505 | |||
506 | AT+SERVADDR : Server Address | ||
507 | |||
508 | |||
509 | (% style="color:blue" %)**UDP Management** | ||
510 | |||
511 | AT+CFM : Upload confirmation mode (only valid for UDP) | ||
512 | |||
513 | |||
514 | (% style="color:blue" %)**MQTT Management** | ||
515 | |||
516 | AT+CLIENT : Get or Set MQTT client | ||
517 | |||
518 | AT+UNAME : Get or Set MQTT Username | ||
519 | |||
520 | AT+PWD : Get or Set MQTT password | ||
521 | |||
522 | AT+PUBTOPIC : Get or Set MQTT publish topic | ||
523 | |||
524 | AT+SUBTOPIC : Get or Set MQTT subscription topic | ||
525 | |||
526 | |||
527 | (% style="color:blue" %)**Information** | ||
528 | |||
529 | AT+FDR : Factory Data Reset | ||
530 | |||
531 | AT+PWORD : Serial Access Password | ||
532 | |||
533 | AT+LDATA : Get the last upload data | ||
534 | |||
535 | AT+CDP : Read or Clear cached data | ||
536 | |||
537 | |||
538 | = 4. Battery & Power Consumption = | ||
539 | |||
540 | |||
541 | S31x-NB use ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. | ||
542 | |||
543 | [[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . | ||
544 | |||
545 | |||
546 | = 5. Firmware update = | ||
547 | |||
548 | |||
549 | User can change device firmware to:: | ||
550 | |||
551 | * Update with new features. | ||
552 | |||
553 | * Fix bugs. | ||
554 | |||
555 | Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/sh/fhb3uyl4gt6clru/AAAiZVTFcxrfE1JOOyfcgO9ha?dl=0]]** | ||
556 | |||
557 | Methods to Update Firmware: | ||
558 | |||
559 | * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]]. | ||
560 | |||
561 | * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]**. | ||
562 | |||
563 | = 6. FAQ = | ||
564 | |||
565 | == 6.1 How can I access t BC660K-GL AT Commands? == | ||
566 | |||
567 | |||
568 | User can access to BC660K-GL directly and send AT Commands. | ||
569 | |||
570 | [[See BC660K-GL AT Command set>>url:https://www.dropbox.com/sh/5f6ssda5fum8rvs/AABT68l8ZzWOvZ5eg2qwOoFda?dl=0]] | ||
571 | |||
572 | |||
573 | = 7. Order Info = | ||
574 | |||
575 | |||
576 | Part Number: (% style="color:blue" %)**S31-NB-XX / S31B-NB-XX** | ||
577 | |||
578 | (% style="color:red" %)**XX**(%%): | ||
579 | |||
580 | * (% style="color:#037691" %)**GE**(%%): General version ( Exclude SIM card) | ||
581 | |||
582 | * (% style="color:#037691" %)**1D**(%%): with 1NCE* 10 years 500MB SIM card and Pre-configure to DataCake server | ||
583 | |||
584 | (% style="color:#037691" %)**1NCE SIM Card NB-IoT network coverage**(%%): Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands | ||
585 | |||
586 | |||
587 | = 8. Packing Info = | ||
588 | |||
589 | |||
590 | (% style="color:#037691" %)**Package Includes**: | ||
591 | |||
592 | * S31-NB or S31-NB NB-IoT Sensor Node x 1 | ||
593 | |||
594 | * External antenna x 1 | ||
595 | |||
596 | (% style="color:#037691" %)**Dimension and weight**: | ||
597 | |||
598 | * Device Size: 13.0 x 5 x 4.5 cm | ||
599 | |||
600 | * Device Weight: 150g | ||
601 | |||
602 | * Package Size / pcs : 14.0 x 8x 5 cm | ||
603 | |||
604 | * Weight / pcs : 180g | ||
605 | |||
606 | = 9. Support = | ||
607 | |||
608 | |||
609 | * 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. | ||
610 | |||
611 | * 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.cc>>mailto:Support@dragino.cc]]. | ||
612 | |||
613 | (% style="display:none" %) (%%) |