Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 130.5 >
edited by Xiaoling
on 2023/04/28 13:51
To version < 108.1 >
edited by Xiaoling
on 2022/07/09 15:39
>
Change comment: Uploaded new attachment "1657352391268-297.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  
... ... @@ -59,6 +59,7 @@
59 59  * 8500mAh Battery for long term use
60 60  
61 61  
57 +
62 62  == 1.3  Specification ==
63 63  
64 64  
... ... @@ -69,15 +69,16 @@
69 69  
70 70  (% style="color:#037691" %)**NB-IoT Spec:**
71 71  
72 -* B1 @H-FDD: 2100MHz
73 -* B3 @H-FDD: 1800MHz
74 -* B8 @H-FDD: 900MHz
75 -* B5 @H-FDD: 850MHz
76 -* B20 @H-FDD: 800MHz
77 -* 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
78 78  
79 79  (% style="color:#037691" %)**Battery:**
80 80  
77 +
81 81  * Li/SOCI2 un-chargeable battery
82 82  * Capacity: 8500mAh
83 83  * Self Discharge: <1% / Year @ 25°C
... ... @@ -85,9 +85,9 @@
85 85  * Max boost current: 2A, 1 second
86 86  
87 87  
85 +
88 88  == ​1.4  Applications ==
89 89  
90 -
91 91  * Smart Buildings & Home Automation
92 92  * Logistics and Supply Chain Management
93 93  * Smart Metering
... ... @@ -99,49 +99,43 @@
99 99  ​
100 100  
101 101  
102 -== 1.5  Pin Definitions & Switch ==
99 +== 1.5  Pin Definitions ==
103 103  
104 -
105 105  N95S31B use the mother board from NBSN95 which as below.
106 106  
107 -
108 108  [[image:image-20220709144723-1.png]]
109 109  
110 110  
111 111  === 1.5.1 Jumper JP2 ===
112 112  
113 -
114 114  Power on Device when put this jumper.
115 115  
116 116  
111 +
117 117  === 1.5.2 BOOT MODE / SW1 ===
118 118  
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.
119 119  
120 -(((
121 -**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.
122 -)))
116 +2) Flash: work mode, device starts to work and send out console output for further debug
123 123  
124 -(((
125 -**2) Flash:**  work mode, device starts to work and send out console output for further debug
126 -)))
127 127  
128 128  
129 129  === 1.5.3 Reset Button ===
130 130  
131 -
132 132  Press to reboot the device.
133 133  
134 134  
125 +
135 135  === 1.5.4 LED ===
136 136  
137 -
138 138  It will flash:
139 139  
140 -1.  When boot the device in flash mode
130 +1. When boot the device in flash mode
131 +1. Send an uplink packet
141 141  
142 -2.  Send an uplink packet
143 143  
144 144  
135 +
145 145  = 2.  Use N95S31B to communicate with IoT Server =
146 146  
147 147  == 2.1  How it works ==
... ... @@ -160,14 +160,16 @@
160 160  
161 161  )))
162 162  
163 -[[image:1657520100595-569.png]]
154 +[[image:1657350248151-650.png]]
164 164  
165 165  (((
166 166  
167 167  )))
168 168  
160 +
169 169  == 2.2 ​ Configure the N95S31B ==
170 170  
163 +
171 171  === 2.2.1  Power On N95S31B ===
172 172  
173 173  
... ... @@ -174,48 +174,27 @@
174 174  [[image:image-20220709150546-2.png]]
175 175  
176 176  
177 -=== 2.2.2 Test Requirement ===
170 +=== 2.2.1 Test Requirement ===
178 178  
179 179  
180 -(((
181 181  To use N95S31B in your city, make sure meet below requirements:
182 -)))
183 183  
184 -* (((
185 -Your local operator has already distributed a NB-IoT Network there.
186 -)))
187 -* (((
188 -The local NB-IoT network used the band that N95S31B supports.
189 -)))
190 -* (((
191 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
192 -)))
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.
193 193  
194 -(((
179 +
195 195  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
196 -)))
197 197  
198 -(((
199 199  N95S31B supports different communication protocol such as :
200 -)))
201 201  
202 202  (((
203 -* (((
204 -CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
205 -)))
206 -* (((
207 -raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
208 -)))
209 -* (((
210 -MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
211 -)))
212 -* (((
213 -TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
214 -)))
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(%%))
215 215  
216 -(((
217 217  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.
218 -)))
219 219  
220 220  
221 221  )))
... ... @@ -223,9 +223,9 @@
223 223  [[image:1657350625843-586.png]]
224 224  
225 225  
198 +
226 226  === 2.2.3  Insert SIM card ===
227 227  
228 -
229 229  (((
230 230  Insert the NB-IoT Card get from your provider.
231 231  )))
... ... @@ -238,29 +238,26 @@
238 238  [[image:1657351240556-536.png]]
239 239  
240 240  
213 +
241 241  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
242 242  
243 -
244 244  (((
245 245  (((
246 246  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.
247 -
248 -
249 249  )))
250 250  )))
251 251  
252 252  [[image:1657351312545-300.png]]
253 253  
224 +**Connection:**
254 254  
255 -(% style="color:blue" %)**Connection:**
226 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
256 256  
257 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
228 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
258 258  
259 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
230 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
260 260  
261 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
262 262  
263 -
264 264  In the PC, use below serial tool settings:
265 265  
266 266  * Baud:  (% style="color:green" %)**9600**
... ... @@ -275,18 +275,17 @@
275 275  
276 276  [[image:1657329814315-101.png]]
277 277  
278 -
279 279  (((
280 -(% 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/]]
281 281  )))
282 282  
283 283  
252 +
284 284  === 2.2.5  Use CoAP protocol to uplink data ===
285 285  
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/]]
286 286  
287 -(% 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/]]**
288 288  
289 -
290 290  (((
291 291  **Use below commands:**
292 292  )))
... ... @@ -295,10 +295,10 @@
295 295  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
296 296  )))
297 297  * (((
298 -(% 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
299 299  )))
300 300  * (((
301 -(% 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
302 302  )))
303 303  
304 304  (((
... ... @@ -317,6 +317,7 @@
317 317  [[image:1657352185396-303.png]]
318 318  
319 319  
288 +
320 320  === 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
321 321  
322 322  
... ... @@ -324,56 +324,50 @@
324 324  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
325 325  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
326 326  
327 -[[image:1657352391268-297.png]]
296 +[[image:1657330501006-241.png]]
328 328  
329 329  
330 -[[image:1657352403317-397.png]]
299 +[[image:1657330533775-472.png]]
331 331  
332 332  
333 -=== 2.2.7  Use MQTT protocol to uplink data ===
334 334  
303 +=== 2.2.6 Use MQTT protocol to uplink data ===
335 335  
336 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
337 337  
338 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
339 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
340 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
341 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
342 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
343 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
344 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
306 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
307 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
308 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
309 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
310 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
311 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
312 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
345 345  
346 -[[image:1657352634421-276.png]]
314 +[[image:1657249978444-674.png]]
347 347  
348 348  
349 -[[image:1657352645687-385.png]]
317 +[[image:1657330723006-866.png]]
350 350  
351 351  
352 352  (((
353 -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.
321 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
354 354  )))
355 355  
356 -(((
357 -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.
358 -)))
359 359  
360 360  
361 -=== 2.2.8  Use TCP protocol to uplink data ===
326 +=== 2.2.7 Use TCP protocol to uplink data ===
362 362  
363 363  
364 -This feature is supported since firmware version v110
365 -
366 366  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
367 367  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
368 368  
369 -[[image:1657352898400-901.png]]
332 +[[image:image-20220709093918-1.png]]
370 370  
371 371  
372 -[[image:1657352914475-252.png]]
335 +[[image:image-20220709093918-2.png]]
373 373  
374 374  
375 -=== 2.2.9  Change Update Interval ===
376 376  
339 +=== 2.2.8 Change Update Interval ===
377 377  
378 378  User can use below command to change the (% style="color:green" %)**uplink interval**.
379 379  
... ... @@ -380,243 +380,164 @@
380 380  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
381 381  
382 382  (((
383 -
346 +(% style="color:red" %)**NOTE:**
384 384  )))
385 385  
386 386  (((
387 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
350 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
388 388  )))
389 389  
390 -(((
391 -(% 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).**
392 -)))
393 393  
394 394  
395 395  == 2.3  Uplink Payload ==
396 396  
357 +In this mode, uplink payload includes in total 14 bytes
397 397  
398 -(((
399 -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.
400 -)))
401 401  
360 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
361 +|=(% style="width: 60px;" %)(((
362 +**Size(bytes)**
363 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
364 +|(% 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"]]
402 402  
403 403  (((
404 -For example:
367 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
405 405  )))
406 406  
407 -(((
408 - (% 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.
409 -)))
410 410  
371 +[[image:1657331036973-987.png]]
411 411  
412 412  (((
413 -The uplink payloads are composed in  ASCII String. For example:
374 +The payload is ASCII string, representative same HEX:
414 414  )))
415 415  
416 416  (((
417 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
378 +0x72403155615900640c6c19029200 where:
418 418  )))
419 419  
420 -(((
421 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
381 +* (((
382 +Device ID: 0x724031556159 = 724031556159
422 422  )))
423 -
424 -
425 -(((
426 -(% style="color:red" %)**NOTE:**
384 +* (((
385 +Version: 0x0064=100=1.0.0
427 427  )))
428 428  
429 -(% style="color:red" %)
430 -1. (((
431 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
388 +* (((
389 +BAT: 0x0c6c = 3180 mV = 3.180V
432 432  )))
433 -1. (((
434 -**By default, the device will send an uplink message every 1 hour.**
391 +* (((
392 +Signal: 0x19 = 25
393 +)))
394 +* (((
395 +Distance: 0x0292= 658 mm
396 +)))
397 +* (((
398 +Interrupt: 0x00 = 0
435 435  
436 436  
401 +
437 437  
438 438  )))
439 439  
440 -=== 2.3.1  Payload Analyze ===
405 +== 2.4  Payload Explanation and Sensor Interface ==
441 441  
442 -==== 2.3.1.1  Before Firmware v1.2 ====
443 443  
408 +=== 2.4.1  Device ID ===
444 444  
445 -N95S31B uplink payload includes in total 21 bytes
446 -
447 -
448 -(% border="1" style="background-color:#f2f2f2; width:520px" %)
449 -|=(% 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**
450 -|(% 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" %)(((
451 451  (((
452 -Reserve/ Same as NBSN95 CFGMOD=1
411 +By default, the Device ID equal to the last 6 bytes of IMEI.
453 453  )))
454 454  
455 455  (((
456 -No function here.
415 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
457 457  )))
458 -)))|(% style="width:102px" %)(((
459 -(((
460 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
461 -)))
462 462  
463 463  (((
464 -By SHT31
419 +**Example:**
465 465  )))
466 -)))|(% style="width:81px" %)(((
467 -(((
468 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
469 -)))
470 470  
471 471  (((
472 -By SHT31
423 +AT+DEUI=A84041F15612
473 473  )))
474 -)))
475 475  
476 476  (((
477 -
478 -
479 -(((
480 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
427 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
481 481  )))
482 -)))
483 483  
484 484  
485 -[[image:1657354294009-643.png]]
486 486  
432 +=== 2.4.2  Version Info ===
487 487  
488 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
434 +(((
435 +Specify the software version: 0x64=100, means firmware version 1.00.
436 +)))
489 489  
490 -**where:**
438 +(((
439 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
440 +)))
491 491  
492 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
493 493  
494 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
495 495  
496 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
444 +=== 2.4.3  Battery Info ===
497 497  
498 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
499 -
500 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
501 -
502 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
503 -
504 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
505 -
506 -* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
507 -
508 508  (((
509 -
447 +Ex1: 0x0B45 = 2885mV
448 +)))
510 510  
511 -
450 +(((
451 +Ex2: 0x0B49 = 2889mV
512 512  )))
513 513  
514 -==== 2.3.1.2 Since Firmware v1.2 ====
515 515  
516 516  
517 -In this mode, uplink payload includes 91 bytes in total by default.
456 +=== 2.4.4  Signal Strength ===
518 518  
519 -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.
520 -
521 -
522 -(% border="1" style="background-color:#f2f2f2; width:520px" %)
523 -|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**8**|(% style="width:20px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:20px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:30px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:20px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:55px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:35px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:20px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:30px;background-color:#D9E2F3;color:#0070C0" %)**4**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:35px;background-color:#D9E2F3;color:#0070C0" %)**4**
524 -|=(% 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 .....
525 -
526 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
527 -
528 -
529 -[[image:image-20220908154949-1.png]]
530 -
531 -
532 -The payload is ASCII string, representative same HEX:
533 -
534 -**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__ **
535 -
536 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
537 -
538 -**where:**
539 -
540 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
541 -
542 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
543 -
544 -* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
545 -
546 -* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
547 -
548 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
549 -
550 -* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
551 -
552 -* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
553 -
554 -* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
555 -
556 -* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
557 -
558 -* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
559 -
560 -* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
561 -
562 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
563 -
564 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
565 -
566 -
567 -=== 2.3.2  Device ID ===
568 -
569 -
570 570  (((
571 -By default, the Device ID equal to the last 6 bytes of IMEI.
459 +NB-IoT Network signal Strength.
572 572  )))
573 573  
574 574  (((
575 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
463 +**Ex1: 0x1d = 29**
464 +)))
576 576  
577 -
466 +(((
467 +(% style="color:blue" %)**0**(%%)  -113dBm or less
578 578  )))
579 579  
580 580  (((
581 -(% style="color:blue" %)**Example:**
471 +(% style="color:blue" %)**1**(%%)  -111dBm
582 582  )))
583 583  
584 584  (((
585 -AT+DEUI=A84041F15612
475 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
586 586  )))
587 587  
588 588  (((
589 -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.
479 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
480 +)))
590 590  
591 -
482 +(((
483 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
592 592  )))
593 593  
594 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
595 595  
596 596  
597 -By default, the Device ID equal to the last 15 bits of IMEI.
488 +=== 2.4.5  Distance ===
598 598  
599 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
490 +Get the distance. Flat object range 280mm - 7500mm.
600 600  
601 -
602 -(% style="color:blue" %)**Example:**
603 -
604 -AT+DEUI=868411056754138
605 -
606 -
607 -=== 2.3.3  Version Info ===
608 -
609 -
610 610  (((
611 -These bytes include the hardware and software version.
493 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
612 612  )))
613 613  
614 614  (((
615 -**Higher byte:** Specify hardware version: always 0x00 for N95S31B
497 +(((
498 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
616 616  )))
500 +)))
617 617  
618 618  (((
619 -**Lower byte:** Specify the software version: 0x6E=110, means firmware version 110
503 +
620 620  )))
621 621  
622 622  (((
... ... @@ -623,81 +623,65 @@
623 623  
624 624  )))
625 625  
510 +=== 2.4.6  Digital Interrupt ===
511 +
626 626  (((
627 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
513 +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.
628 628  )))
629 629  
630 630  (((
631 -
517 +The command is:
632 632  )))
633 633  
634 -=== 2.3.4  Battery Info ===
635 -
636 -
637 637  (((
638 -Ex1: 0x0B45 = 2885mV
521 +(% 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]])**.**
639 639  )))
640 640  
524 +
641 641  (((
642 -Ex2: 0x0B49 = 2889mV
526 +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.
643 643  )))
644 644  
645 645  
646 -=== 2.3.5  Signal Strength ===
647 -
648 -
649 649  (((
650 -NB-IoT Network signal Strength.
531 +Example:
651 651  )))
652 652  
653 653  (((
654 -**Ex1: 0x1d = 29**
535 +0x(00): Normal uplink packet.
655 655  )))
656 656  
657 657  (((
658 -(% style="color:blue" %)**0**(%%)  -113dBm or less
539 +0x(01): Interrupt Uplink Packet.
659 659  )))
660 660  
542 +
543 +
544 +=== 2.4.7  ​+5V Output ===
545 +
661 661  (((
662 -(% style="color:blue" %)**1**(%%)  -111dBm
547 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
663 663  )))
664 664  
550 +
665 665  (((
666 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
552 +The 5V output time can be controlled by AT Command.
667 667  )))
668 668  
669 669  (((
670 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
556 +(% style="color:blue" %)**AT+5VT=1000**
671 671  )))
672 672  
673 673  (((
674 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
560 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
675 675  )))
676 676  
677 677  
678 -=== 2.3.6  Temperature & Humidity ===
679 679  
565 +== 2.5  Downlink Payload ==
680 680  
681 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
567 +By default, NDDS75 prints the downlink payload to console port.
682 682  
683 -[[image:image-20220709161741-3.png]]
684 -
685 -
686 -Convert the read byte to decimal and divide it by ten.
687 -
688 -
689 -**Example:**
690 -
691 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
692 -
693 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
694 -
695 -
696 -== 2.4  Downlink Payload ==
697 -
698 -
699 -By default, N95S31B prints the downlink payload to console port.
700 -
701 701  [[image:image-20220709100028-1.png]]
702 702  
703 703  
... ... @@ -734,7 +734,7 @@
734 734  )))
735 735  
736 736  (((
737 -If payload = 0x04FF, it will reset the N95S31B
605 +If payload = 0x04FF, it will reset the NDDS75
738 738  )))
739 739  
740 740  
... ... @@ -745,97 +745,144 @@
745 745  )))
746 746  
747 747  
748 -== 2.5  Humidity and Temperature alarm function ==
749 749  
617 +== 2.6  ​LED Indicator ==
750 750  
751 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
752 752  
620 +The NDDS75 has an internal LED which is to show the status of different state.
753 753  
754 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
755 755  
623 +* 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)
624 +* Then the LED will be on for 1 second means device is boot normally.
625 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
626 +* For each uplink probe, LED will be on for 500ms.
756 756  
757 -² When min=0, and max≠0, Alarm higher than max
628 +(((
629 +
630 +)))
758 758  
759 -² When min≠0, and max=0, Alarm lower than min
760 760  
761 -² When min≠0 and max≠0, Alarm higher than max or lower than min
762 762  
634 +== 2.7  ​Firmware Change Log ==
763 763  
764 - (% style="color:blue" %)**Example:**
765 765  
766 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
637 +(((
638 +Download URL & Firmware Change log
639 +)))
767 767  
641 +(((
642 +[[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/]]
643 +)))
768 768  
769 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
770 770  
771 -² When min=0, and max≠0, Alarm higher than max
646 +(((
647 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
648 +)))
772 772  
773 -² When min≠0, and max=0, Alarm lower than min
774 774  
775 -² When min≠0 and max≠0, Alarm higher than max or lower than min
776 776  
652 +== 2.8  ​Battery Analysis ==
777 777  
778 -**~ (% style="color:blue" %)Example:(%%)**
654 +=== 2.8.1  ​Battery Type ===
779 779  
780 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
781 781  
657 +(((
658 +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.
659 +)))
782 782  
783 -== 2.6 Set the number of data to be uploaded and the recording time ==
661 +(((
662 +The battery is designed to last for several years depends on the actually use environment and update interval. 
663 +)))
784 784  
665 +(((
666 +The battery related documents as below:
667 +)))
785 785  
786 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
669 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
670 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
671 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
787 787  
788 -* (% 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)
789 -* (% 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.
673 +(((
674 +[[image:image-20220709101450-2.png]]
675 +)))
790 790  
791 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
792 792  
793 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
794 794  
679 +=== 2.8.2  Power consumption Analyze ===
795 795  
796 -== 2.7 Read or Clear cached data ==
681 +(((
682 +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.
683 +)))
797 797  
798 798  
799 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
686 +(((
687 +Instruction to use as below:
688 +)))
800 800  
801 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
802 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
690 +(((
691 +(% 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/]]
692 +)))
803 803  
804 -[[image:image-20220908163102-2.png]]
805 805  
695 +(((
696 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
697 +)))
806 806  
807 -== 2.8 Battery & Power Consumption ==
699 +* (((
700 +Product Model
701 +)))
702 +* (((
703 +Uplink Interval
704 +)))
705 +* (((
706 +Working Mode
707 +)))
808 808  
709 +(((
710 +And the Life expectation in difference case will be shown on the right.
711 +)))
809 809  
810 -N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
713 +[[image:image-20220709110451-3.png]]
811 811  
812 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
813 813  
814 814  
815 -= 3. ​ Access NB-IoT Module =
717 +=== 2.8.3  ​Battery Note ===
816 816  
719 +(((
720 +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.
721 +)))
817 817  
723 +
724 +
725 +=== 2.8.4  Replace the battery ===
726 +
818 818  (((
728 +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).
729 +)))
730 +
731 +
732 +
733 += 3. ​ Access NB-IoT Module =
734 +
735 +(((
819 819  Users can directly access the AT command set of the NB-IoT module.
820 820  )))
821 821  
822 822  (((
823 823  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/]] 
824 -
825 -
826 826  )))
827 827  
828 828  [[image:1657333200519-600.png]]
829 829  
830 830  
746 +
831 831  = 4.  Using the AT Commands =
832 832  
833 833  == 4.1  Access AT Commands ==
834 834  
751 +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/]]
835 835  
836 -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]]
837 837  
838 -
839 839  AT+<CMD>?  : Help on <CMD>
840 840  
841 841  AT+<CMD>         : Run <CMD>
... ... @@ -875,24 +875,7 @@
875 875  
876 876  AT+SERVADDR  : Server Address
877 877  
878 -AT+TR      : Get or Set record time
879 879  
880 -AT+APN     : Get or set the APN
881 -
882 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
883 -
884 -AT+DNSCFG  : Get or Set DNS Server
885 -
886 -AT+GETSENSORVALUE   : Returns the current sensor measurement
887 -
888 -AT+NOUD      : Get or Set the number of data to be uploaded
889 -
890 -AT+CDP     : Read or Clear cached data
891 -
892 -AT+SHTEMP: Get or Set alarm of temp
893 -
894 -AT+SHHUM: Get or Set alarm of moisture
895 -
896 896  (% style="color:#037691" %)**COAP Management**      
897 897  
898 898  AT+URI            : Resource parameters
... ... @@ -923,6 +923,7 @@
923 923  AT+PWORD  : Serial Access Password
924 924  
925 925  
824 +
926 926  = ​5.  FAQ =
927 927  
928 928  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -937,12 +937,11 @@
937 937  )))
938 938  
939 939  (((
940 -Firmware Download：[[https:~~/~~/www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0>>https://www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0]]
941 -
942 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
839 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
943 943  )))
944 944  
945 945  
843 +
946 946  = 6.  Trouble Shooting =
947 947  
948 948  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -952,10 +952,14 @@
952 952  **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]]
953 953  )))
954 954  
853 +(% class="wikigeneratedid" %)
854 +(((
855 +
856 +)))
955 955  
858 +
956 956  == 6.2  AT Command input doesn't work ==
957 957  
958 -
959 959  (((
960 960  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.
961 961  
... ... @@ -962,18 +962,18 @@
962 962  
963 963  )))
964 964  
965 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
966 966  
967 -
968 -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]]//**.
969 -
970 -
971 971  = 7. ​ Order Info =
972 972  
973 973  
974 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
871 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
975 975  
976 976  
874 +(% class="wikigeneratedid" %)
875 +(((
876 +
877 +)))
878 +
977 977  = 8.  Packing Info =
978 978  
979 979  (((
... ... @@ -981,7 +981,7 @@
981 981  
982 982  (% style="color:#037691" %)**Package Includes**:
983 983  
984 -* N95S31B NB-IoT Temperature and Humidity Sensor
886 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
985 985  * External antenna x 1
986 986  )))
987 987  
... ... @@ -990,19 +990,21 @@
990 990  
991 991  (% style="color:#037691" %)**Dimension and weight**:
992 992  
895 +
993 993  * Device Size: 13.0 x 5 x 4.5 cm
994 994  * Device Weight: 150g
995 -* Package Size / pcs : 14.0 x 8x 5 cm
996 -* Weight / pcs : 180g
898 +* Package Size / pcs : 15 x 12x 5.5 cm
899 +* Weight / pcs : 220g
997 997  )))
998 998  
902 +(((
903 +
999 999  
1000 1000  
906 +
907 +)))
908 +
1001 1001  = 9.  Support =
1002 1002  
1003 -
1004 1004  * 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.
1005 -
1006 1006  * 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]]
1007 -
1008 -
1657352403317-397.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -547.7 KB
Content
1657352634421-276.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -163.6 KB
Content
1657352645687-385.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -214.7 KB
Content
1657352898400-901.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -144.8 KB
Content
1657352914475-252.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -157.0 KB
Content
1657354294009-643.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -214.7 KB
Content
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