Version 119.3 by Xiaoling on 2022/08/22 15:05
Show last authors
1 (% style="text-align:center" %)
2 [[image:1657348034241-728.png||height="470" width="470"]]
3
4
5
6
7
8
9
10 **Table of Contents:**
11
12 {{toc/}}
13
14
15
16
17
18 = 1.  Introduction =
19
20
21 == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
22
23 (((
24
25
26 (((
27 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 )))
29
30 (((
31 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 )))
33
34 (((
35 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
36 )))
37
38 (((
39 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 )))
41
42 (((
43
44 )))
45
46 (((
47 ~* make sure you have NB-IoT coverage locally.
48 )))
49
50
51 )))
52
53 [[image:1657348284168-431.png]]
54
55
56
57 == 1.2 ​ Features ==
58
59
60 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
61 * Monitor Temperature & Humidity via SHT31
62 * AT Commands to change parameters
63 * Uplink on periodically
64 * Downlink to change configure
65 * IP66 Waterproof Enclosure
66 * Ultra-Low Power consumption
67 * AT Commands to change parameters
68 * Micro SIM card slot for NB-IoT SIM
69 * 8500mAh Battery for long term use
70
71
72
73
74 == 1.3  Specification ==
75
76
77 (% style="color:#037691" %)**Common DC Characteristics:**
78
79 * Supply Voltage: 2.1v ~~ 3.6v
80 * Operating Temperature: -40 ~~ 85°C
81
82
83
84 (% style="color:#037691" %)**NB-IoT Spec:**
85
86 * - B1 @H-FDD: 2100MHz
87 * - B3 @H-FDD: 1800MHz
88 * - B8 @H-FDD: 900MHz
89 * - B5 @H-FDD: 850MHz
90 * - B20 @H-FDD: 800MHz
91 * - B28 @H-FDD: 700MHz
92
93
94
95 (% style="color:#037691" %)**Battery:**
96
97 * Li/SOCI2 un-chargeable battery
98 * Capacity: 8500mAh
99 * Self Discharge: <1% / Year @ 25°C
100 * Max continuously current: 130mA
101 * Max boost current: 2A, 1 second
102
103
104
105
106 == ​1.4  Applications ==
107
108
109 * Smart Buildings & Home Automation
110 * Logistics and Supply Chain Management
111 * Smart Metering
112 * Smart Agriculture
113 * Smart Cities
114 * Smart Factory
115
116 (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
117 ​
118
119
120
121 == 1.5  Pin Definitions & Switch ==
122
123
124 N95S31B use the mother board from NBSN95 which as below.
125
126
127 [[image:image-20220709144723-1.png]]
128
129
130
131 === 1.5.1 Jumper JP2 ===
132
133
134 Power on Device when put this jumper.
135
136
137
138 === 1.5.2 BOOT MODE / SW1 ===
139
140
141 (((
142 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.
143 )))
144
145 (((
146 2) Flash: work mode, device starts to work and send out console output for further debug
147 )))
148
149
150
151 === 1.5.3 Reset Button ===
152
153
154 Press to reboot the device.
155
156
157
158 === 1.5.4 LED ===
159
160
161 It will flash:
162
163 1. When boot the device in flash mode
164 1. Send an uplink packet
165
166
167
168
169 = 2.  Use N95S31B to communicate with IoT Server =
170
171
172 == 2.1  How it works ==
173
174
175 (((
176 The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by N95S31B.
177 )))
178
179
180 (((
181 The diagram below shows the working flow in default firmware of N95S31B:
182 )))
183
184 (((
185
186 )))
187
188 [[image:1657520100595-569.png]]
189
190 (((
191
192 )))
193
194
195 == 2.2 ​ Configure the N95S31B ==
196
197
198 === 2.2.1  Power On N95S31B ===
199
200
201 [[image:image-20220709150546-2.png]]
202
203
204
205 === 2.2.1 Test Requirement ===
206
207
208 (((
209 To use N95S31B in your city, make sure meet below requirements:
210 )))
211
212 * (((
213 Your local operator has already distributed a NB-IoT Network there.
214 )))
215 * (((
216 The local NB-IoT network used the band that N95S31B supports.
217 )))
218 * (((
219 Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
220 )))
221
222 (((
223 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
224 )))
225
226 (((
227 N95S31B supports different communication protocol such as :
228 )))
229
230 (((
231 * (((
232 CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
233 )))
234 * (((
235 raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
236 )))
237 * (((
238 MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
239 )))
240 * (((
241 TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
242 )))
243
244 (((
245 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.
246 )))
247
248
249 )))
250
251 [[image:1657350625843-586.png]]
252
253
254
255 === 2.2.3  Insert SIM card ===
256
257
258 (((
259 Insert the NB-IoT Card get from your provider.
260 )))
261
262 (((
263 User need to take out the NB-IoT module and insert the SIM card like below:
264 )))
265
266
267 [[image:1657351240556-536.png]]
268
269
270
271 === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
272
273
274 (((
275 (((
276 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.
277
278
279 )))
280 )))
281
282 [[image:1657351312545-300.png]]
283
284
285 **Connection:**
286
287 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
288
289 (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
290
291 (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
292
293
294 In the PC, use below serial tool settings:
295
296 * Baud:  (% style="color:green" %)**9600**
297 * Data bits:** (% style="color:green" %)8(%%)**
298 * Stop bits: (% style="color:green" %)**1**
299 * Parity:  (% style="color:green" %)**None**
300 * Flow Control: (% style="color:green" %)**None**
301
302 (((
303 Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
304 )))
305
306 [[image:1657329814315-101.png]]
307
308
309 (((
310 (% 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]]**
311 )))
312
313
314
315 === 2.2.5  Use CoAP protocol to uplink data ===
316
317
318 (% 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/]]**
319
320
321 (((
322 **Use below commands:**
323 )))
324
325 * (((
326 (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
327 )))
328 * (((
329 (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
330 )))
331 * (((
332 (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
333 )))
334
335 (((
336
337
338 For parameter description, please refer to AT command set
339 )))
340
341 [[image:1657352146020-183.png]]
342
343
344 (((
345 After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
346 )))
347
348 [[image:1657352185396-303.png]]
349
350
351
352 === 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
353
354
355 * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
356 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
357 * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
358
359
360
361 [[image:1657352391268-297.png]]
362
363
364 [[image:1657352403317-397.png]]
365
366
367
368 === 2.2.7  Use MQTT protocol to uplink data ===
369
370
371 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
372
373 * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
374 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
375 * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
376 * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
377 * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
378 * (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
379 * (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
380
381
382
383 [[image:1657352634421-276.png]]
384
385
386 [[image:1657352645687-385.png]]
387
388
389 (((
390 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.
391 )))
392
393
394 (((
395 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.
396 )))
397
398
399
400 === 2.2.8  Use TCP protocol to uplink data ===
401
402
403 This feature is supported since firmware version v110
404
405 * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
406 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
407
408
409
410 [[image:1657352898400-901.png]]
411
412
413 [[image:1657352914475-252.png]]
414
415
416
417 === 2.2.9  Change Update Interval ===
418
419
420 User can use below command to change the (% style="color:green" %)**uplink interval**.
421
422 * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
423
424 (((
425
426 )))
427
428
429
430 == 2.3  Uplink Payload ==
431
432
433 (((
434 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.
435 )))
436
437
438 (((
439 For example:
440 )))
441
442 (((
443 (% 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.
444 )))
445
446
447 (((
448 The uplink payloads are composed in  ASCII String. For example:
449 )))
450
451 (((
452 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
453 )))
454
455 (((
456 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
457 )))
458
459
460 (((
461 (% style="color:red" %)**NOTE:**
462 )))
463
464 (% style="color:red" %)
465 1. (((
466 **All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
467 )))
468 1. (((
469 **By default, the device will send an uplink message every 1 hour.**
470
471
472
473
474 )))
475
476 === 2.3.1  Payload Analyze ===
477
478
479 N95S31B uplink payload includes in total 21 bytes
480
481
482 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
483 |=(% style="width: 60px;" %)(((
484 **Size(bytes)**
485 )))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**
486 |(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
487 (((
488 Reserve/ Same as NBSN95 CFGMOD=1
489 )))
490
491 (((
492 No function here.
493 )))
494 )))|(% style="width:77px" %)(((
495 (((
496 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
497 )))
498
499 (((
500 By SHT31
501 )))
502 )))|(% style="width:80px" %)(((
503 (((
504 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
505 )))
506
507 (((
508 By SHT31
509 )))
510 )))
511
512 (((
513
514
515 (((
516 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
517 )))
518 )))
519
520
521 [[image:1657354294009-643.png]]
522
523
524 The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
525
526 * Device ID: 0x724031607457 = 724031607457
527 * Version: 0x006e=110=1.1.0
528
529 * BAT: 0x0ccd = 3277 mV = 3.277V
530 * Signal: 0x1b = 27
531 * Model: 0x01 = 1
532 * 0x00dc000ccc= reserve, ignore in N95S31B
533 * Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
534 * Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
535
536 (((
537
538 )))
539
540 (((
541
542 )))
543
544
545 === 2.3.2  Device ID ===
546
547
548 (((
549 By default, the Device ID equal to the last 6 bytes of IMEI.
550 )))
551
552 (((
553 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
554 )))
555
556 (((
557 **Example:**
558 )))
559
560 (((
561 AT+DEUI=A84041F15612
562 )))
563
564 (((
565 The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
566 )))
567
568
569
570 === 2.3.3  Version Info ===
571
572
573 (((
574 These bytes include the hardware and software version.
575 )))
576
577 (((
578 Higher byte: Specify hardware version: always 0x00 for N95S31B
579 )))
580
581 (((
582 Lower byte: Specify the software version: 0x6E=110, means firmware version 110
583 )))
584
585 (((
586
587 )))
588
589 (((
590 For example: 0x00 6E: this device is N95S31B with firmware version 110.
591 )))
592
593 (((
594
595 )))
596
597
598 === 2.3.4  Battery Info ===
599
600
601 (((
602 Ex1: 0x0B45 = 2885mV
603 )))
604
605 (((
606 Ex2: 0x0B49 = 2889mV
607 )))
608
609
610
611 === 2.3.5  Signal Strength ===
612
613
614 (((
615 NB-IoT Network signal Strength.
616 )))
617
618 (((
619 **Ex1: 0x1d = 29**
620 )))
621
622 (((
623 (% style="color:blue" %)**0**(%%)  -113dBm or less
624 )))
625
626 (((
627 (% style="color:blue" %)**1**(%%)  -111dBm
628 )))
629
630 (((
631 (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
632 )))
633
634 (((
635 (% style="color:blue" %)**31**  (%%) -51dBm or greater
636 )))
637
638 (((
639 (% style="color:blue" %)**99**   (%%) Not known or not detectable
640 )))
641
642
643
644 === 2.3.6  Temperature & Humidity ===
645
646
647 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
648
649 [[image:image-20220709161741-3.png]]
650
651
652 Convert the read byte to decimal and divide it by ten.
653
654
655 **Example:**
656
657 Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
658
659 Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
660
661
662
663 == 2.4  Downlink Payload ==
664
665
666 By default, N95S31B prints the downlink payload to console port.
667
668 [[image:image-20220709100028-1.png]]
669
670
671 (((
672 (% style="color:blue" %)**Examples:**
673 )))
674
675 (((
676
677 )))
678
679 * (((
680 (% style="color:blue" %)**Set TDC**
681 )))
682
683 (((
684 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
685 )))
686
687 (((
688 Payload:    01 00 00 1E    TDC=30S
689 )))
690
691 (((
692 Payload:    01 00 00 3C    TDC=60S
693 )))
694
695 (((
696
697 )))
698
699 * (((
700 (% style="color:blue" %)**Reset**
701 )))
702
703 (((
704 If payload = 0x04FF, it will reset the N95S31B
705 )))
706
707
708 * (% style="color:blue" %)**INTMOD**
709
710 (((
711 Downlink Payload: 06000003, Set AT+INTMOD=3
712 )))
713
714
715
716 == 2.5  ​Battery Analysis ==
717
718
719 === 2.5.1  ​Battery Type ===
720
721
722 (((
723 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.
724 )))
725
726 (((
727 The battery is designed to last for several years depends on the actually use environment and update interval. 
728 )))
729
730 (((
731 The battery related documents as below:
732 )))
733
734 * [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
735 * [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
736 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
737
738 (((
739 [[image:image-20220709101450-2.png]]
740 )))
741
742
743
744 === 2.5.2  Power consumption Analyze ===
745
746
747 (((
748 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.
749 )))
750
751 (((
752
753 )))
754
755
756 === 2.5.3  ​Battery Note ===
757
758
759 (((
760 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.
761 )))
762
763
764
765 === 2.5.4  Replace the battery ===
766
767
768 (((
769 You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
770 )))
771
772
773 (((
774 The default battery pack of N95S31B 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).
775 )))
776
777
778
779 = 3. ​ Access NB-IoT Module =
780
781
782 (((
783 Users can directly access the AT command set of the NB-IoT module.
784 )))
785
786 (((
787 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/]] 
788
789
790 )))
791
792 [[image:1657333200519-600.png]]
793
794
795
796 = 4.  Using the AT Commands =
797
798
799 == 4.1  Access AT Commands ==
800
801
802 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]]
803
804
805 AT+<CMD>?  : Help on <CMD>
806
807 AT+<CMD>         : Run <CMD>
808
809 AT+<CMD>=<value> : Set the value
810
811 AT+<CMD>=?  : Get the value
812
813
814 (% style="color:#037691" %)**General Commands**(%%)      
815
816 AT  : Attention       
817
818 AT?  : Short Help     
819
820 ATZ  : MCU Reset    
821
822 AT+TDC  : Application Data Transmission Interval
823
824 AT+CFG  : Print all configurations
825
826 AT+CFGMOD           : Working mode selection
827
828 AT+INTMOD            : Set the trigger interrupt mode
829
830 AT+5VT  : Set extend the time of 5V power  
831
832 AT+PRO  : Choose agreement
833
834 AT+WEIGRE  : Get weight or set weight to 0
835
836 AT+WEIGAP  : Get or Set the GapValue of weight
837
838 AT+RXDL  : Extend the sending and receiving time
839
840 AT+CNTFAC  : Get or set counting parameters
841
842 AT+SERVADDR  : Server Address
843
844
845 (% style="color:#037691" %)**COAP Management**      
846
847 AT+URI            : Resource parameters
848
849
850 (% style="color:#037691" %)**UDP Management**
851
852 AT+CFM          : Upload confirmation mode (only valid for UDP)
853
854
855 (% style="color:#037691" %)**MQTT Management**
856
857 AT+CLIENT               : Get or Set MQTT client
858
859 AT+UNAME  : Get or Set MQTT Username
860
861 AT+PWD                  : Get or Set MQTT password
862
863 AT+PUBTOPIC  : Get or Set MQTT publish topic
864
865 AT+SUBTOPIC  : Get or Set MQTT subscription topic
866
867
868 (% style="color:#037691" %)**Information**          
869
870 AT+FDR  : Factory Data Reset
871
872 AT+PWORD  : Serial Access Password
873
874
875
876 = ​5.  FAQ =
877
878
879 == 5.1 ​ How to Upgrade Firmware ==
880
881
882 (((
883 User can upgrade the firmware for 1) bug fix, 2) new feature release.
884 )))
885
886 (((
887 Please see this link for how to upgrade:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
888 )))
889
890 (((
891
892
893 (((
894 (% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
895 )))
896 )))
897
898
899
900 = 6.  Trouble Shooting =
901
902
903 == 6.1  ​Connection problem when uploading firmware ==
904
905
906 (((
907 **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]]
908 )))
909
910 (% class="wikigeneratedid" %)
911 (((
912
913 )))
914
915
916 == 6.2  AT Command input doesn't work ==
917
918
919 (((
920 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.
921
922
923 )))
924
925
926 = 7. ​ Order Info =
927
928
929 Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
930
931
932 (% class="wikigeneratedid" %)
933 (((
934
935 )))
936
937 = 8.  Packing Info =
938
939 (((
940
941
942 (% style="color:#037691" %)**Package Includes**:
943
944 * N95S31B NB-IoT Temperature and Humidity Sensor
945 * External antenna x 1
946 )))
947
948 (((
949
950
951 (% style="color:#037691" %)**Dimension and weight**:
952
953 * Device Size: 13.0 x 5 x 4.5 cm
954 * Device Weight: 150g
955 * Package Size / pcs : 14.0 x 8x 5 cm
956 * Weight / pcs : 180g
957 )))
958
959 (((
960
961
962
963
964 )))
965
966 = 9.  Support =
967
968
969 * 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.
970 * 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]]
971
972
973

Applications

Navigation

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