Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.24 >
edited by Xiaoling
on 2022/07/09 18:19
To version < 123.1 >
edited by David Huang
on 2022/09/08 16:37
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.David
Content
... ... @@ -17,21 +17,35 @@
17 17  
18 18  = 1.  Introduction =
19 19  
20 +
20 20  == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
21 21  
22 22  (((
23 23  
24 24  
26 +(((
25 25  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*.
28 +)))
26 26  
30 +(((
27 27  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.
32 +)))
28 28  
34 +(((
29 29  N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
36 +)))
30 30  
38 +(((
31 31  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).
40 +)))
32 32  
42 +(((
43 +
44 +)))
33 33  
46 +(((
34 34  ~* make sure you have NB-IoT coverage locally.
48 +)))
35 35  
36 36  
37 37  )))
... ... @@ -42,6 +42,7 @@
42 42  
43 43  == 1.2 ​ Features ==
44 44  
59 +
45 45  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
46 46  * Monitor Temperature & Humidity via SHT31
47 47  * AT Commands to change parameters
... ... @@ -72,7 +72,6 @@
72 72  
73 73  (% style="color:#037691" %)**Battery:**
74 74  
75 -
76 76  * Li/SOCI2 un-chargeable battery
77 77  * Capacity: 8500mAh
78 78  * Self Discharge: <1% / Year @ 25°C
... ... @@ -81,6 +81,7 @@
81 81  
82 82  == ​1.4  Applications ==
83 83  
98 +
84 84  * Smart Buildings & Home Automation
85 85  * Logistics and Supply Chain Management
86 86  * Smart Metering
... ... @@ -92,15 +92,20 @@
92 92  ​
93 93  
94 94  
95 -== 1.5  Pin Definitions ==
96 96  
111 +== 1.5  Pin Definitions & Switch ==
112 +
113 +
97 97  N95S31B use the mother board from NBSN95 which as below.
98 98  
116 +
99 99  [[image:image-20220709144723-1.png]]
100 100  
101 101  
120 +
102 102  === 1.5.1 Jumper JP2 ===
103 103  
123 +
104 104  Power on Device when put this jumper.
105 105  
106 106  
... ... @@ -107,14 +107,20 @@
107 107  
108 108  === 1.5.2 BOOT MODE / SW1 ===
109 109  
130 +
131 +(((
110 110  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.
133 +)))
111 111  
135 +(((
112 112  2) Flash: work mode, device starts to work and send out console output for further debug
137 +)))
113 113  
114 114  
115 115  
116 116  === 1.5.3 Reset Button ===
117 117  
143 +
118 118  Press to reboot the device.
119 119  
120 120  
... ... @@ -121,6 +121,7 @@
121 121  
122 122  === 1.5.4 LED ===
123 123  
150 +
124 124  It will flash:
125 125  
126 126  1. When boot the device in flash mode
... ... @@ -128,6 +128,7 @@
128 128  
129 129  = 2.  Use N95S31B to communicate with IoT Server =
130 130  
158 +
131 131  == 2.1  How it works ==
132 132  
133 133  
... ... @@ -144,7 +144,7 @@
144 144  
145 145  )))
146 146  
147 -[[image:1657350248151-650.png]]
175 +[[image:1657520100595-569.png]]
148 148  
149 149  (((
150 150  
... ... @@ -160,26 +160,49 @@
160 160  [[image:image-20220709150546-2.png]]
161 161  
162 162  
191 +
163 163  === 2.2.1 Test Requirement ===
164 164  
165 165  
195 +(((
166 166  To use N95S31B in your city, make sure meet below requirements:
197 +)))
167 167  
168 -* Your local operator has already distributed a NB-IoT Network there.
169 -* The local NB-IoT network used the band that N95S31B supports.
170 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
199 +* (((
200 +Your local operator has already distributed a NB-IoT Network there.
201 +)))
202 +* (((
203 +The local NB-IoT network used the band that N95S31B supports.
204 +)))
205 +* (((
206 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
207 +)))
171 171  
209 +(((
172 172  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
211 +)))
173 173  
213 +(((
174 174  N95S31B supports different communication protocol such as :
215 +)))
175 175  
176 176  (((
177 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
178 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
179 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
180 -* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
218 +* (((
219 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
220 +)))
221 +* (((
222 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
223 +)))
224 +* (((
225 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
226 +)))
227 +* (((
228 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
229 +)))
181 181  
231 +(((
182 182  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.
233 +)))
183 183  
184 184  
185 185  )))
... ... @@ -190,6 +190,7 @@
190 190  
191 191  === 2.2.3  Insert SIM card ===
192 192  
244 +
193 193  (((
194 194  Insert the NB-IoT Card get from your provider.
195 195  )))
... ... @@ -205,14 +205,18 @@
205 205  
206 206  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
207 207  
260 +
208 208  (((
209 209  (((
210 210  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.
264 +
265 +
211 211  )))
212 212  )))
213 213  
214 214  [[image:1657351312545-300.png]]
215 215  
271 +
216 216  **Connection:**
217 217  
218 218   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -236,8 +236,9 @@
236 236  
237 237  [[image:1657329814315-101.png]]
238 238  
295 +
239 239  (((
240 -(% 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/]]
297 +(% 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]]**
241 241  )))
242 242  
243 243  
... ... @@ -244,9 +244,10 @@
244 244  
245 245  === 2.2.5  Use CoAP protocol to uplink data ===
246 246  
247 -(% 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/]]
248 248  
305 +(% 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/]]**
249 249  
307 +
250 250  (((
251 251  **Use below commands:**
252 252  )))
... ... @@ -294,6 +294,7 @@
294 294  
295 295  === 2.2.7  Use MQTT protocol to uplink data ===
296 296  
355 +
297 297  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
298 298  
299 299  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
... ... @@ -309,6 +309,7 @@
309 309  
310 310  [[image:1657352645687-385.png]]
311 311  
371 +
312 312  (((
313 313  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.
314 314  )))
... ... @@ -322,6 +322,7 @@
322 322  
323 323  === 2.2.8  Use TCP protocol to uplink data ===
324 324  
385 +
325 325  This feature is supported since firmware version v110
326 326  
327 327  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -336,6 +336,7 @@
336 336  
337 337  === 2.2.9  Change Update Interval ===
338 338  
400 +
339 339  User can use below command to change the (% style="color:green" %)**uplink interval**.
340 340  
341 341  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -344,36 +344,60 @@
344 344  
345 345  )))
346 346  
409 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
347 347  
411 +**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).**
348 348  
413 +
349 349  == 2.3  Uplink Payload ==
350 350  
351 351  
352 -NBSN95 has different working mode for the connections of different type 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.
417 +(((
418 +N95S31B has different working mode for the connections of different type 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.
419 +)))
353 353  
354 354  
422 +(((
355 355  For example:
424 +)))
356 356  
357 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
426 +(((
427 + (% 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.
428 +)))
358 358  
359 359  
431 +(((
360 360  The uplink payloads are composed in  ASCII String. For example:
433 +)))
361 361  
435 +(((
362 362  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
437 +)))
363 363  
439 +(((
364 364  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
441 +)))
365 365  
366 366  
444 +(((
367 367  (% style="color:red" %)**NOTE:**
446 +)))
368 368  
369 369  (% style="color:red" %)
370 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
371 -1. By default, the device will send an uplink message every 1 hour.
449 +1. (((
450 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
451 +)))
452 +1. (((
453 +**By default, the device will send an uplink message every 1 hour.**
372 372  
373 373  
374 374  
457 +
458 +)))
459 +
375 375  === 2.3.1  Payload Analyze ===
376 376  
462 +
377 377  N95S31B uplink payload includes in total 21 bytes
378 378  
379 379  
... ... @@ -408,6 +408,8 @@
408 408  )))
409 409  
410 410  (((
497 +
498 +
411 411  (((
412 412  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
413 413  )))
... ... @@ -434,12 +434,41 @@
434 434  )))
435 435  
436 436  (((
437 -
525 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
438 438  )))
439 439  
528 +In this mode, uplink payload includes 91 bytes in total by default.
440 440  
530 +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.
531 +
532 +|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4
533 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp .....
534 +
535 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
536 +
537 +[[image:image-20220908154949-1.png]]
538 +
539 +The payload is ASCII string, representative same HEX:
540 +
541 +0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where:
542 +
543 +* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782
544 +* (% style="color:blue" %) Version: 0x000c=120=1.2
545 +* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V
546 +* (% style="color:red" %) Singal: 0x0c = 12
547 +* (% style="color:blue" %) Mod: 0x01 = 1
548 +* TemDS18B20: 0x0000= 0 = 0
549 +* (% style="color:green" %)Interrupt: 0x00= 0
550 +* (% style="color:green" %)adc: 0x0030= 48
551 +* SHTTEM: 0x0114= 276 = 27.6
552 +* SHTHUM:0x0231 =561=56.1%
553 +* (% style="color:red" %) Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
554 +* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
555 +* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,.......
556 +
441 441  === 2.3.2  Device ID ===
442 442  
559 +
443 443  (((
444 444  By default, the Device ID equal to the last 6 bytes of IMEI.
445 445  )))
... ... @@ -458,21 +458,44 @@
458 458  
459 459  (((
460 460  The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
578 +
579 +
461 461  )))
462 462  
582 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
463 463  
464 464  
585 +By default, the Device ID equal to the last 15 bits of IMEI.
586 +
587 +User can use **AT+DEUI** to set Device ID
588 +
589 +**Example:**
590 +
591 +AT+DEUI=868411056754138
592 +
593 +
465 465  === 2.3.3  Version Info ===
466 466  
467 467  
597 +(((
468 468  These bytes include the hardware and software version.
599 +)))
469 469  
601 +(((
470 470  Higher byte: Specify hardware version: always 0x00 for N95S31B
603 +)))
471 471  
605 +(((
472 472  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
607 +)))
473 473  
609 +(((
610 +
611 +)))
474 474  
613 +(((
475 475  For example: 0x00 6E: this device is N95S31B with firmware version 110.
615 +)))
476 476  
477 477  (((
478 478  
... ... @@ -481,6 +481,7 @@
481 481  
482 482  === 2.3.4  Battery Info ===
483 483  
624 +
484 484  (((
485 485  Ex1: 0x0B45 = 2885mV
486 486  )))
... ... @@ -493,6 +493,7 @@
493 493  
494 494  === 2.3.5  Signal Strength ===
495 495  
637 +
496 496  (((
497 497  NB-IoT Network signal Strength.
498 498  )))
... ... @@ -525,6 +525,7 @@
525 525  
526 526  === 2.3.6  Temperature & Humidity ===
527 527  
670 +
528 528  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
529 529  
530 530  [[image:image-20220709161741-3.png]]
... ... @@ -543,8 +543,9 @@
543 543  
544 544  == 2.4  Downlink Payload ==
545 545  
546 -By default, NDDS75 prints the downlink payload to console port.
547 547  
690 +By default, N95S31B prints the downlink payload to console port.
691 +
548 548  [[image:image-20220709100028-1.png]]
549 549  
550 550  
... ... @@ -581,7 +581,7 @@
581 581  )))
582 582  
583 583  (((
584 -If payload = 0x04FF, it will reset the NDDS75
728 +If payload = 0x04FF, it will reset the N95S31B
585 585  )))
586 586  
587 587  
... ... @@ -592,12 +592,59 @@
592 592  )))
593 593  
594 594  
739 +== 2.5 Humidity and Temperature alarm function ==
595 595  
596 -== 2.5  ​Battery Analysis ==
741 +➢ AT Command:
597 597  
598 -=== 2.5.1  ​Battery Type ===
743 +AT+ SHHUM=min,max
599 599  
745 +² When min=0, and max≠0, Alarm higher than max
600 600  
747 +² When min≠0, and max=0, Alarm lower than min
748 +
749 +² When min≠0 and max≠0, Alarm higher than max or lower than min
750 +
751 +Example:
752 +
753 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
754 +
755 +
756 +AT+ SHTEMP=min,max
757 +
758 +² When min=0, and max≠0, Alarm higher than max
759 +
760 +² When min≠0, and max=0, Alarm lower than min
761 +
762 +² When min≠0 and max≠0, Alarm higher than max or lower than min
763 +
764 +Example:
765 +
766 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
767 +
768 +== 2.6 Set the number of data to be uploaded and the recording time ==
769 +
770 +➢ AT Command:
771 +
772 +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)
773 +
774 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
775 +
776 +== 2.7 Read or Clear cached data ==
777 +
778 +➢ AT Command:
779 +
780 +AT+CDP ~/~/ Read cached data
781 +
782 +[[image:image-20220908163102-2.png]]
783 +
784 +AT+CDP=0 ~/~/ Clear cached data
785 +
786 +== 2.8  ​Battery Analysis ==
787 +
788 +
789 +=== 2.8.1  ​Battery Type ===
790 +
791 +
601 601  (((
602 602  The N95S31B 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.
603 603  )))
... ... @@ -620,10 +620,11 @@
620 620  
621 621  
622 622  
623 -=== 2.5.2  Power consumption Analyze ===
814 +=== 2.8.2  Power consumption Analyze ===
624 624  
816 +
625 625  (((
626 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
818 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
627 627  )))
628 628  
629 629  (((
... ... @@ -631,8 +631,9 @@
631 631  )))
632 632  
633 633  
634 -=== 2.5.3  ​Battery Note ===
826 +=== 2.8.3  ​Battery Note ===
635 635  
828 +
636 636  (((
637 637  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 uplink data, then the battery life may be decreased.
638 638  )))
... ... @@ -639,7 +639,7 @@
639 639  
640 640  
641 641  
642 -=== 2.5.4  Replace the battery ===
835 +=== 2.8.4  Replace the battery ===
643 643  
644 644  
645 645  (((
... ... @@ -655,6 +655,7 @@
655 655  
656 656  = 3. ​ Access NB-IoT Module =
657 657  
851 +
658 658  (((
659 659  Users can directly access the AT command set of the NB-IoT module.
660 660  )))
... ... @@ -661,6 +661,8 @@
661 661  
662 662  (((
663 663  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/]] 
858 +
859 +
664 664  )))
665 665  
666 666  [[image:1657333200519-600.png]]
... ... @@ -669,11 +669,13 @@
669 669  
670 670  = 4.  Using the AT Commands =
671 671  
868 +
672 672  == 4.1  Access AT Commands ==
673 673  
674 -See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]
675 675  
872 +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]]
676 676  
874 +
677 677  AT+<CMD>?  : Help on <CMD>
678 678  
679 679  AT+<CMD>         : Run <CMD>
... ... @@ -713,7 +713,24 @@
713 713  
714 714  AT+SERVADDR  : Server Address
715 715  
914 +AT+TR      : Get or Set record time
716 716  
916 +AT+APN     : Get or set the APN
917 +
918 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
919 +
920 +AT+DNSCFG  : Get or Set DNS Server
921 +
922 +AT+GETSENSORVALUE   : Returns the current sensor measurement
923 +
924 +AT+NOUD      : Get or Set the number of data to be uploaded
925 +
926 +AT+CDP     : Read or Clear cached data
927 +
928 +AT+SHTEMP: Get or Set alarm of temp
929 +
930 +AT+SHHUM: Get or Set alarm of moisture
931 +
717 717  (% style="color:#037691" %)**COAP Management**      
718 718  
719 719  AT+URI            : Resource parameters
... ... @@ -747,6 +747,7 @@
747 747  
748 748  = ​5.  FAQ =
749 749  
965 +
750 750  == 5.1 ​ How to Upgrade Firmware ==
751 751  
752 752  
... ... @@ -761,13 +761,16 @@
761 761  (((
762 762  
763 763  
764 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
980 +(((
981 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
765 765  )))
983 +)))
766 766  
767 767  
768 768  
769 769  = 6.  Trouble Shooting =
770 770  
989 +
771 771  == 6.1  ​Connection problem when uploading firmware ==
772 772  
773 773  
... ... @@ -783,6 +783,7 @@
783 783  
784 784  == 6.2  AT Command input doesn't work ==
785 785  
1005 +
786 786  (((
787 787  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.
788 788  
... ... @@ -832,5 +832,8 @@
832 832  
833 833  = 9.  Support =
834 834  
1055 +
835 835  * 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.
836 836  * 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]]
1058 +
1059 +
1657520100595-569.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
image-20220908154949-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +58.5 KB
Content
image-20220908163102-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +29.7 KB
Content

Applications

Navigation

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