Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 130.7 >
edited by Xiaoling
on 2023/04/28 13:59
To version < 114.1 >
edited by Xiaoling
on 2022/07/09 16:11
>
Change comment: Uploaded new attachment "1657354294009-643.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -9,7 +9,6 @@
9 9  
10 10  **Table of Contents:**
11 11  
12 -{{toc/}}
13 13  
14 14  
15 15  
... ... @@ -19,31 +19,27 @@
19 19  
20 20  == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
21 21  
22 -
23 23  (((
22 +
23 +
24 24  The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*.
25 -)))
26 26  
27 -(((
28 28  The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use.
29 -)))
30 30  
31 -(((
32 32  N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
33 -)))
34 34  
35 -(((
36 36  N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report).
37 -)))
38 38  
39 -(((
32 +
40 40  ~* make sure you have NB-IoT coverage locally.
34 +
35 +
41 41  )))
42 42  
43 -
44 44  [[image:1657348284168-431.png]]
45 45  
46 46  
41 +
47 47  == 1.2 ​ Features ==
48 48  
49 49  
... ... @@ -58,6 +58,8 @@
58 58  * Micro SIM card slot for NB-IoT SIM
59 59  * 8500mAh Battery for long term use
60 60  
56 +
57 +
61 61  == 1.3  Specification ==
62 62  
63 63  
... ... @@ -68,15 +68,16 @@
68 68  
69 69  (% style="color:#037691" %)**NB-IoT Spec:**
70 70  
71 -* B1 @H-FDD: 2100MHz
72 -* B3 @H-FDD: 1800MHz
73 -* B8 @H-FDD: 900MHz
74 -* B5 @H-FDD: 850MHz
75 -* B20 @H-FDD: 800MHz
76 -* B28 @H-FDD: 700MHz
68 +* - B1 @H-FDD: 2100MHz
69 +* - B3 @H-FDD: 1800MHz
70 +* - B8 @H-FDD: 900MHz
71 +* - B5 @H-FDD: 850MHz
72 +* - B20 @H-FDD: 800MHz
73 +* - B28 @H-FDD: 700MHz
77 77  
78 78  (% style="color:#037691" %)**Battery:**
79 79  
77 +
80 80  * Li/SOCI2 un-chargeable battery
81 81  * Capacity: 8500mAh
82 82  * Self Discharge: <1% / Year @ 25°C
... ... @@ -83,9 +83,10 @@
83 83  * Max continuously current: 130mA
84 84  * Max boost current: 2A, 1 second
85 85  
86 -== ​1.4  Applications ==
87 87  
88 88  
86 +== ​1.4  Applications ==
87 +
89 89  * Smart Buildings & Home Automation
90 90  * Logistics and Supply Chain Management
91 91  * Smart Metering
... ... @@ -97,49 +97,43 @@
97 97  ​
98 98  
99 99  
100 -== 1.5  Pin Definitions & Switch ==
99 +== 1.5  Pin Definitions ==
101 101  
102 -
103 103  N95S31B use the mother board from NBSN95 which as below.
104 104  
105 -
106 106  [[image:image-20220709144723-1.png]]
107 107  
108 108  
109 109  === 1.5.1 Jumper JP2 ===
110 110  
111 -
112 112  Power on Device when put this jumper.
113 113  
114 114  
111 +
115 115  === 1.5.2 BOOT MODE / SW1 ===
116 116  
114 +1) 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.
117 117  
118 -(((
119 -**1) 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.
120 -)))
116 +2) Flash: work mode, device starts to work and send out console output for further debug
121 121  
122 -(((
123 -**2) Flash:**  work mode, device starts to work and send out console output for further debug
124 -)))
125 125  
126 126  
127 127  === 1.5.3 Reset Button ===
128 128  
129 -
130 130  Press to reboot the device.
131 131  
132 132  
125 +
133 133  === 1.5.4 LED ===
134 134  
135 -
136 136  It will flash:
137 137  
138 -1.  When boot the device in flash mode
130 +1. When boot the device in flash mode
131 +1. Send an uplink packet
139 139  
140 -2.  Send an uplink packet
141 141  
142 142  
135 +
143 143  = 2.  Use N95S31B to communicate with IoT Server =
144 144  
145 145  == 2.1  How it works ==
... ... @@ -158,14 +158,16 @@
158 158  
159 159  )))
160 160  
161 -[[image:1657520100595-569.png]]
154 +[[image:1657350248151-650.png]]
162 162  
163 163  (((
164 164  
165 165  )))
166 166  
160 +
167 167  == 2.2 ​ Configure the N95S31B ==
168 168  
163 +
169 169  === 2.2.1  Power On N95S31B ===
170 170  
171 171  
... ... @@ -172,48 +172,27 @@
172 172  [[image:image-20220709150546-2.png]]
173 173  
174 174  
175 -=== 2.2.2 Test Requirement ===
170 +=== 2.2.1 Test Requirement ===
176 176  
177 177  
178 -(((
179 179  To use N95S31B in your city, make sure meet below requirements:
180 -)))
181 181  
182 -* (((
183 -Your local operator has already distributed a NB-IoT Network there.
184 -)))
185 -* (((
186 -The local NB-IoT network used the band that N95S31B supports.
187 -)))
188 -* (((
189 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
190 -)))
175 +* Your local operator has already distributed a NB-IoT Network there.
176 +* The local NB-IoT network used the band that N95S31B supports.
177 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
191 191  
192 -(((
179 +
193 193  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
194 -)))
195 195  
196 -(((
197 197  N95S31B supports different communication protocol such as :
198 -)))
199 199  
200 200  (((
201 -* (((
202 -CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
203 -)))
204 -* (((
205 -raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
206 -)))
207 -* (((
208 -MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
209 -)))
210 -* (((
211 -TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
212 -)))
185 +* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
186 +* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
187 +* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
188 +* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
213 213  
214 -(((
215 215  We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server.
216 -)))
217 217  
218 218  
219 219  )))
... ... @@ -221,9 +221,9 @@
221 221  [[image:1657350625843-586.png]]
222 222  
223 223  
198 +
224 224  === 2.2.3  Insert SIM card ===
225 225  
226 -
227 227  (((
228 228  Insert the NB-IoT Card get from your provider.
229 229  )))
... ... @@ -236,29 +236,26 @@
236 236  [[image:1657351240556-536.png]]
237 237  
238 238  
213 +
239 239  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
240 240  
241 -
242 242  (((
243 243  (((
244 244  User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below.
245 -
246 -
247 247  )))
248 248  )))
249 249  
250 250  [[image:1657351312545-300.png]]
251 251  
224 +**Connection:**
252 252  
253 -(% style="color:blue" %)**Connection:**
226 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
254 254  
255 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
228 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
256 256  
257 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
230 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
258 258  
259 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
260 260  
261 -
262 262  In the PC, use below serial tool settings:
263 263  
264 264  * Baud:  (% style="color:green" %)**9600**
... ... @@ -273,18 +273,17 @@
273 273  
274 274  [[image:1657329814315-101.png]]
275 275  
276 -
277 277  (((
278 -(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**
248 +(% style="color:red" %)Note: the valid AT Commands can be found at:  (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]
279 279  )))
280 280  
281 281  
252 +
282 282  === 2.2.5  Use CoAP protocol to uplink data ===
283 283  
255 +(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
284 284  
285 -(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**
286 286  
287 -
288 288  (((
289 289  **Use below commands:**
290 290  )))
... ... @@ -293,10 +293,10 @@
293 293  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
294 294  )))
295 295  * (((
296 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
266 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
297 297  )))
298 298  * (((
299 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
269 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
300 300  )))
301 301  
302 302  (((
... ... @@ -315,6 +315,7 @@
315 315  [[image:1657352185396-303.png]]
316 316  
317 317  
288 +
318 318  === 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
319 319  
320 320  
... ... @@ -328,18 +328,18 @@
328 328  [[image:1657352403317-397.png]]
329 329  
330 330  
302 +
331 331  === 2.2.7  Use MQTT protocol to uplink data ===
332 332  
333 -
334 334  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
335 335  
336 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
337 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
338 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
339 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
340 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
341 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
342 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
307 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
308 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
309 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
310 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
311 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
312 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527  **(%%)~/~/Set the sending topic of MQTT
313 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527  **(%%) ~/~/Set the subscription topic of MQTT
343 343  
344 344  [[image:1657352634421-276.png]]
345 345  
... ... @@ -346,19 +346,19 @@
346 346  
347 347  [[image:1657352645687-385.png]]
348 348  
349 -
350 350  (((
351 351  To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period.
352 352  )))
353 353  
324 +
354 354  (((
355 355  MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
356 356  )))
357 357  
358 358  
330 +
359 359  === 2.2.8  Use TCP protocol to uplink data ===
360 360  
361 -
362 362  This feature is supported since firmware version v110
363 363  
364 364  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -370,9 +370,9 @@
370 370  [[image:1657352914475-252.png]]
371 371  
372 372  
344 +
373 373  === 2.2.9  Change Update Interval ===
374 374  
375 -
376 376  User can use below command to change the (% style="color:green" %)**uplink interval**.
377 377  
378 378  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -381,239 +381,157 @@
381 381  
382 382  )))
383 383  
384 -(((
385 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
386 -)))
387 387  
388 -(((
389 -(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
390 -)))
391 391  
392 -
393 393  == 2.3  Uplink Payload ==
394 394  
359 +In this mode, uplink payload includes in total 14 bytes
395 395  
396 -(((
397 -N95S31B has different working modes for the connections of different types of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
398 -)))
399 399  
362 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
363 +|=(% style="width: 60px;" %)(((
364 +**Size(bytes)**
365 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
366 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
400 400  
401 401  (((
402 -For example:
369 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
403 403  )))
404 404  
405 -(((
406 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/  will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
407 -)))
408 408  
373 +[[image:1657331036973-987.png]]
409 409  
410 410  (((
411 -The uplink payloads are composed in  ASCII String. For example:
376 +The payload is ASCII string, representative same HEX:
412 412  )))
413 413  
414 414  (((
415 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
380 +0x72403155615900640c6c19029200 where:
416 416  )))
417 417  
418 -(((
419 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
383 +* (((
384 +Device ID: 0x724031556159 = 724031556159
420 420  )))
421 -
422 -
423 -(((
424 -(% style="color:red" %)**NOTE:**
386 +* (((
387 +Version: 0x0064=100=1.0.0
425 425  )))
426 426  
427 -(% style="color:red" %)
428 -1. (((
429 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
390 +* (((
391 +BAT: 0x0c6c = 3180 mV = 3.180V
430 430  )))
431 -1. (((
432 -**By default, the device will send an uplink message every 1 hour.**
393 +* (((
394 +Signal: 0x19 = 25
395 +)))
396 +* (((
397 +Distance: 0x0292= 658 mm
398 +)))
399 +* (((
400 +Interrupt: 0x00 = 0
433 433  
434 434  
403 +
435 435  
436 436  )))
437 437  
438 -=== 2.3.1  Payload Analyze ===
407 +== 2.4  Payload Explanation and Sensor Interface ==
439 439  
440 -==== 2.3.1.1  Before Firmware v1.2 ====
441 441  
410 +=== 2.4.1  Device ID ===
442 442  
443 -N95S31B uplink payload includes in total 21 bytes
444 -
445 -
446 -(% border="1" style="background-color:#f2f2f2; width:520px" %)
447 -|=(% style="width: 50px;background-color:#D9E2F3" %)**Size(bytes)**|=(% style="width: 45px;background-color:#D9E2F3" %)**6**|=(% style="width: 25px;background-color:#D9E2F3" %)2|=(% style="width: 25px;background-color:#D9E2F3" %)**2**|=(% style="width: 65px;background-color:#D9E2F3" %)**1**|=(% style="width: 50px;background-color:#D9E2F3" %)1|=(% style="width: 120px;background-color:#D9E2F3" %)5|=(% style="width: 70px;background-color:#D9E2F3" %)**2**|=(% style="width: 70px;background-color:#D9E2F3" %)**2**
448 -|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:162px" %)(((
449 449  (((
450 -Reserve/ Same as NBSN95 CFGMOD=1
413 +By default, the Device ID equal to the last 6 bytes of IMEI.
451 451  )))
452 452  
453 453  (((
454 -No function here.
417 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
455 455  )))
456 -)))|(% style="width:102px" %)(((
457 -(((
458 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
459 -)))
460 460  
461 461  (((
462 -By SHT31
421 +**Example:**
463 463  )))
464 -)))|(% style="width:81px" %)(((
465 -(((
466 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
467 -)))
468 468  
469 469  (((
470 -By SHT31
425 +AT+DEUI=A84041F15612
471 471  )))
472 -)))
473 473  
474 474  (((
475 -
476 -
477 -(((
478 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
429 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
479 479  )))
480 -)))
481 481  
482 482  
483 -[[image:1657354294009-643.png]]
484 484  
434 +=== 2.4.2  Version Info ===
485 485  
486 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
436 +(((
437 +Specify the software version: 0x64=100, means firmware version 1.00.
438 +)))
487 487  
488 -**where:**
440 +(((
441 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
442 +)))
489 489  
490 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
491 491  
492 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
493 493  
494 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
446 +=== 2.4.3  Battery Info ===
495 495  
496 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
497 -
498 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
499 -
500 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
501 -
502 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
503 -
504 -* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
505 -
506 506  (((
507 -
449 +Ex1: 0x0B45 = 2885mV
450 +)))
508 508  
509 -
452 +(((
453 +Ex2: 0x0B49 = 2889mV
510 510  )))
511 511  
512 -==== 2.3.1.2 Since Firmware v1.2 ====
513 513  
514 514  
515 -In this mode, uplink payload includes 91 bytes in total by default.
458 +=== 2.4.4  Signal Strength ===
516 516  
517 -Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
518 -
519 -
520 -(% border="1" style="background-color:#f2f2f2; width:520px" %)
521 -|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:30px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:55px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:35px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:30px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:35px" %)**4**
522 -|=(% style="width: 95px;" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp .....
523 -
524 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
525 -
526 -
527 -[[image:image-20220908154949-1.png]]
528 -
529 -
530 -The payload is ASCII string, representative same HEX:
531 -
532 -**0x (% style="color:red" %)__f868411056758782__ (% style="color:blue" %)__000c__ (% style="color:green" %)__0d0f__ (% style="color:#00b0f0" %)__0c__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__0000__ (% style="color:#a14d07" %)__00__ __0030__ (% style="color:#0020b0" %)__0114__ (% style="color:#420042" %)__0231__ (% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__// //__0112023763199baa__ __0112023263199af6__// //__0111023b631999a7__ **
533 -
534 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
535 -
536 -**where:**
537 -
538 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
539 -
540 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
541 -
542 -* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
543 -
544 -* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
545 -
546 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
547 -
548 -* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
549 -
550 -* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
551 -
552 -* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
553 -
554 -* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
555 -
556 -* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
557 -
558 -* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
559 -
560 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
561 -
562 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
563 -
564 -=== 2.3.2  Device ID ===
565 -
566 -
567 567  (((
568 -By default, the Device ID equal to the last 6 bytes of IMEI.
461 +NB-IoT Network signal Strength.
569 569  )))
570 570  
571 571  (((
572 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
465 +**Ex1: 0x1d = 29**
466 +)))
573 573  
574 -
468 +(((
469 +(% style="color:blue" %)**0**(%%)  -113dBm or less
575 575  )))
576 576  
577 577  (((
578 -(% style="color:blue" %)**Example:**
473 +(% style="color:blue" %)**1**(%%)  -111dBm
579 579  )))
580 580  
581 581  (((
582 -AT+DEUI=A84041F15612
477 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
583 583  )))
584 584  
585 585  (((
586 -The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
481 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
482 +)))
587 587  
588 -
484 +(((
485 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
589 589  )))
590 590  
591 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
592 592  
593 593  
594 -By default, the Device ID equal to the last 15 bits of IMEI.
490 +=== 2.4.5  Distance ===
595 595  
596 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
492 +Get the distance. Flat object range 280mm - 7500mm.
597 597  
598 -
599 -(% style="color:blue" %)**Example:**
600 -
601 -AT+DEUI=868411056754138
602 -
603 -
604 -=== 2.3.3  Version Info ===
605 -
606 -
607 607  (((
608 -These bytes include the hardware and software version.
495 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
609 609  )))
610 610  
611 611  (((
612 -**Higher byte:** Specify hardware version: always 0x00 for N95S31B
499 +(((
500 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
613 613  )))
502 +)))
614 614  
615 615  (((
616 -**Lower byte:** Specify the software version: 0x6E=110, means firmware version 110
505 +
617 617  )))
618 618  
619 619  (((
... ... @@ -620,87 +620,65 @@
620 620  
621 621  )))
622 622  
512 +=== 2.4.6  Digital Interrupt ===
513 +
623 623  (((
624 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
515 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
625 625  )))
626 626  
627 627  (((
628 -
519 +The command is:
629 629  )))
630 630  
631 -=== 2.3.4  Battery Info ===
632 -
633 -
634 634  (((
635 -Ex1: 0x0B45 = 2885mV
523 +(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
636 636  )))
637 637  
526 +
638 638  (((
639 -Ex2: 0x0B49 = 2889mV
528 +The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
640 640  )))
641 641  
642 642  
643 -=== 2.3.5  Signal Strength ===
644 -
645 -
646 646  (((
647 -NB-IoT Network signal Strength.
533 +Example:
648 648  )))
649 649  
650 650  (((
651 -**Ex1: 0x1d = 29**
537 +0x(00): Normal uplink packet.
652 652  )))
653 653  
654 654  (((
655 -(% style="color:blue" %)**0**(%%)  -113dBm or less
541 +0x(01): Interrupt Uplink Packet.
656 656  )))
657 657  
544 +
545 +
546 +=== 2.4.7  ​+5V Output ===
547 +
658 658  (((
659 -(% style="color:blue" %)**1**(%%)  -111dBm
549 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
660 660  )))
661 661  
552 +
662 662  (((
663 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
554 +The 5V output time can be controlled by AT Command.
664 664  )))
665 665  
666 666  (((
667 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
558 +(% style="color:blue" %)**AT+5VT=1000**
668 668  )))
669 669  
670 670  (((
671 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
562 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
672 672  )))
673 673  
674 674  
675 -=== 2.3.6  Temperature & Humidity ===
676 676  
567 +== 2.5  Downlink Payload ==
677 677  
678 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
569 +By default, NDDS75 prints the downlink payload to console port.
679 679  
680 -[[image:image-20220709161741-3.png]]
681 -
682 -
683 -Convert the read byte to decimal and divide it by ten.
684 -
685 -
686 -**Example:**
687 -
688 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
689 -
690 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
691 -
692 -
693 -== 2.4  Downlink Payload ==
694 -
695 -
696 -By default, N95S31B prints the downlink payload to console port.
697 -
698 -(% border="1" style="background-color:#f2f2f2; width:520px" %)
699 -|(% style="background-color:#d9e2f3; color:#0070c0; width:210px" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:210px" %)**Downlink payload size(bytes)**
700 -|(% style="width:82px" %)TDC(Transmit Time Interval)|(% style="width:43px" %)Any|(% style="width:47px" %)01|(% style="width:124px" %)4
701 -|(% style="width:82px" %)RESET|(% style="width:43px" %)Any|(% style="width:47px" %)04|(% style="width:124px" %)2
702 -|(% style="width:82px" %)INTMOD|(% style="width:43px" %)Any|(% style="width:47px" %)06|(% style="width:124px" %)4
703 -
704 704  [[image:image-20220709100028-1.png]]
705 705  
706 706  
... ... @@ -737,7 +737,7 @@
737 737  )))
738 738  
739 739  (((
740 -If payload = 0x04FF, it will reset the N95S31B
607 +If payload = 0x04FF, it will reset the NDDS75
741 741  )))
742 742  
743 743  
... ... @@ -748,97 +748,144 @@
748 748  )))
749 749  
750 750  
751 -== 2.5  Humidity and Temperature alarm function ==
752 752  
619 +== 2.6  ​LED Indicator ==
753 753  
754 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
755 755  
622 +The NDDS75 has an internal LED which is to show the status of different state.
756 756  
757 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
758 758  
625 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
626 +* Then the LED will be on for 1 second means device is boot normally.
627 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
628 +* For each uplink probe, LED will be on for 500ms.
759 759  
760 -² When min=0, and max≠0, Alarm higher than max
630 +(((
631 +
632 +)))
761 761  
762 -² When min≠0, and max=0, Alarm lower than min
763 763  
764 -² When min≠0 and max≠0, Alarm higher than max or lower than min
765 765  
636 +== 2.7  ​Firmware Change Log ==
766 766  
767 - (% style="color:blue" %)**Example:**
768 768  
769 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
639 +(((
640 +Download URL & Firmware Change log
641 +)))
770 770  
643 +(((
644 +[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
645 +)))
771 771  
772 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
773 773  
774 -² When min=0, and max≠0, Alarm higher than max
648 +(((
649 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
650 +)))
775 775  
776 -² When min≠0, and max=0, Alarm lower than min
777 777  
778 -² When min≠0 and max≠0, Alarm higher than max or lower than min
779 779  
654 +== 2.8  ​Battery Analysis ==
780 780  
781 -**~ (% style="color:blue" %)Example:(%%)**
656 +=== 2.8.1  ​Battery Type ===
782 782  
783 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
784 784  
659 +(((
660 +The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
661 +)))
785 785  
786 -== 2.6 Set the number of data to be uploaded and the recording time ==
663 +(((
664 +The battery is designed to last for several years depends on the actually use environment and update interval. 
665 +)))
787 787  
667 +(((
668 +The battery related documents as below:
669 +)))
788 788  
789 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
671 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
672 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
673 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
790 790  
791 -* (% style="color:#037691" %)**AT+TR=900**     (%%)~/~/  The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
792 -* (% 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.
675 +(((
676 +[[image:image-20220709101450-2.png]]
677 +)))
793 793  
794 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
795 795  
796 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
797 797  
681 +=== 2.8.2  Power consumption Analyze ===
798 798  
799 -== 2.7 Read or Clear cached data ==
683 +(((
684 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
685 +)))
800 800  
801 801  
802 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
688 +(((
689 +Instruction to use as below:
690 +)))
803 803  
804 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
805 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
692 +(((
693 +(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
694 +)))
806 806  
807 -[[image:image-20220908163102-2.png]]
808 808  
697 +(((
698 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
699 +)))
809 809  
810 -== 2.8 Battery & Power Consumption ==
701 +* (((
702 +Product Model
703 +)))
704 +* (((
705 +Uplink Interval
706 +)))
707 +* (((
708 +Working Mode
709 +)))
811 811  
711 +(((
712 +And the Life expectation in difference case will be shown on the right.
713 +)))
812 812  
813 -N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
715 +[[image:image-20220709110451-3.png]]
814 814  
815 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
816 816  
817 817  
818 -= 3. ​ Access NB-IoT Module =
719 +=== 2.8.3  ​Battery Note ===
819 819  
721 +(((
722 +The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
723 +)))
820 820  
725 +
726 +
727 +=== 2.8.4  Replace the battery ===
728 +
821 821  (((
730 +The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
731 +)))
732 +
733 +
734 +
735 += 3. ​ Access NB-IoT Module =
736 +
737 +(((
822 822  Users can directly access the AT command set of the NB-IoT module.
823 823  )))
824 824  
825 825  (((
826 826  The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
827 -
828 -
829 829  )))
830 830  
831 831  [[image:1657333200519-600.png]]
832 832  
833 833  
748 +
834 834  = 4.  Using the AT Commands =
835 835  
836 836  == 4.1  Access AT Commands ==
837 837  
753 +See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
838 838  
839 -See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]]
840 840  
841 -
842 842  AT+<CMD>?  : Help on <CMD>
843 843  
844 844  AT+<CMD>         : Run <CMD>
... ... @@ -878,24 +878,7 @@
878 878  
879 879  AT+SERVADDR  : Server Address
880 880  
881 -AT+TR      : Get or Set record time
882 882  
883 -AT+APN     : Get or set the APN
884 -
885 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
886 -
887 -AT+DNSCFG  : Get or Set DNS Server
888 -
889 -AT+GETSENSORVALUE   : Returns the current sensor measurement
890 -
891 -AT+NOUD      : Get or Set the number of data to be uploaded
892 -
893 -AT+CDP     : Read or Clear cached data
894 -
895 -AT+SHTEMP: Get or Set alarm of temp
896 -
897 -AT+SHHUM: Get or Set alarm of moisture
898 -
899 899  (% style="color:#037691" %)**COAP Management**      
900 900  
901 901  AT+URI            : Resource parameters
... ... @@ -926,6 +926,7 @@
926 926  AT+PWORD  : Serial Access Password
927 927  
928 928  
826 +
929 929  = ​5.  FAQ =
930 930  
931 931  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -940,12 +940,11 @@
940 940  )))
941 941  
942 942  (((
943 -Firmware Download：[[https:~~/~~/www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0>>https://www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0]]
944 -
945 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
841 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
946 946  )))
947 947  
948 948  
845 +
949 949  = 6.  Trouble Shooting =
950 950  
951 951  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -955,10 +955,14 @@
955 955  **Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
956 956  )))
957 957  
855 +(% class="wikigeneratedid" %)
856 +(((
857 +
858 +)))
958 958  
860 +
959 959  == 6.2  AT Command input doesn't work ==
960 960  
961 -
962 962  (((
963 963  In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
964 964  
... ... @@ -965,18 +965,18 @@
965 965  
966 966  )))
967 967  
968 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
969 969  
970 -
971 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
972 -
973 -
974 974  = 7. ​ Order Info =
975 975  
976 976  
977 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
873 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
978 978  
979 979  
876 +(% class="wikigeneratedid" %)
877 +(((
878 +
879 +)))
880 +
980 980  = 8.  Packing Info =
981 981  
982 982  (((
... ... @@ -984,7 +984,7 @@
984 984  
985 985  (% style="color:#037691" %)**Package Includes**:
986 986  
987 -* N95S31B NB-IoT Temperature and Humidity Sensor
888 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
988 988  * External antenna x 1
989 989  )))
990 990  
... ... @@ -993,19 +993,21 @@
993 993  
994 994  (% style="color:#037691" %)**Dimension and weight**:
995 995  
897 +
996 996  * Device Size: 13.0 x 5 x 4.5 cm
997 997  * Device Weight: 150g
998 -* Package Size / pcs : 14.0 x 8x 5 cm
999 -* Weight / pcs : 180g
900 +* Package Size / pcs : 15 x 12x 5.5 cm
901 +* Weight / pcs : 220g
1000 1000  )))
1001 1001  
904 +(((
905 +
1002 1002  
1003 1003  
908 +
909 +)))
910 +
1004 1004  = 9.  Support =
1005 1005  
1006 -
1007 1007  * 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.
1008 -
1009 1009  * 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:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
1010 -
1011 -
1657520100595-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -111.2 KB
Content
image-20220908154949-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -58.5 KB
Content
image-20220908163102-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -29.7 KB
Content
image-20221009001045-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0