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