Skip to Content
Version 119.2 by Xiaoling on 2022/08/22 14:47
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 [[image:1657352391268-297.png]]
360
361
362 [[image:1657352403317-397.png]]
363
364
365
366 === 2.2.7  Use MQTT protocol to uplink data ===
367
368 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
369
370 * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
371 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
372 * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
373 * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
374 * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
375 * (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
376 * (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
377
378 [[image:1657352634421-276.png]]
379
380
381 [[image:1657352645687-385.png]]
382
383 (((
384 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.
385 )))
386
387
388 (((
389 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.
390 )))
391
392
393
394 === 2.2.8  Use TCP protocol to uplink data ===
395
396 This feature is supported since firmware version v110
397
398 * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
399 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
400
401 [[image:1657352898400-901.png]]
402
403
404 [[image:1657352914475-252.png]]
405
406
407
408 === 2.2.9  Change Update Interval ===
409
410 User can use below command to change the (% style="color:green" %)**uplink interval**.
411
412 * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
413
414 (((
415
416 )))
417
418
419
420 == 2.3  Uplink Payload ==
421
422
423 (((
424 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.
425 )))
426
427
428 (((
429 For example:
430 )))
431
432 (((
433 (% 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.
434 )))
435
436
437 (((
438 The uplink payloads are composed in  ASCII String. For example:
439 )))
440
441 (((
442 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
443 )))
444
445 (((
446 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
447 )))
448
449
450 (((
451 (% style="color:red" %)**NOTE:**
452 )))
453
454 (% style="color:red" %)
455 1. (((
456 All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
457 )))
458 1. (((
459 By default, the device will send an uplink message every 1 hour.
460
461
462
463
464 )))
465
466 === 2.3.1  Payload Analyze ===
467
468 N95S31B uplink payload includes in total 21 bytes
469
470
471 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
472 |=(% style="width: 60px;" %)(((
473 **Size(bytes)**
474 )))|=(% 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**
475 |(% 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" %)(((
476 (((
477 Reserve/ Same as NBSN95 CFGMOD=1
478 )))
479
480 (((
481 No function here.
482 )))
483 )))|(% style="width:77px" %)(((
484 (((
485 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
486 )))
487
488 (((
489 By SHT31
490 )))
491 )))|(% style="width:80px" %)(((
492 (((
493 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
494 )))
495
496 (((
497 By SHT31
498 )))
499 )))
500
501 (((
502 (((
503 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
504 )))
505 )))
506
507
508 [[image:1657354294009-643.png]]
509
510
511 The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
512
513 * Device ID: 0x724031607457 = 724031607457
514 * Version: 0x006e=110=1.1.0
515
516 * BAT: 0x0ccd = 3277 mV = 3.277V
517 * Signal: 0x1b = 27
518 * Model: 0x01 = 1
519 * 0x00dc000ccc= reserve, ignore in N95S31B
520 * Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
521 * Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
522
523 (((
524
525 )))
526
527 (((
528
529 )))
530
531
532 === 2.3.2  Device ID ===
533
534 (((
535 By default, the Device ID equal to the last 6 bytes of IMEI.
536 )))
537
538 (((
539 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
540 )))
541
542 (((
543 **Example:**
544 )))
545
546 (((
547 AT+DEUI=A84041F15612
548 )))
549
550 (((
551 The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
552 )))
553
554
555
556 === 2.3.3  Version Info ===
557
558 (((
559 These bytes include the hardware and software version.
560 )))
561
562 (((
563 Higher byte: Specify hardware version: always 0x00 for N95S31B
564 )))
565
566 (((
567 Lower byte: Specify the software version: 0x6E=110, means firmware version 110
568 )))
569
570 (((
571
572 )))
573
574 (((
575 For example: 0x00 6E: this device is N95S31B with firmware version 110.
576 )))
577
578 (((
579
580 )))
581
582
583 === 2.3.4  Battery Info ===
584
585 (((
586 Ex1: 0x0B45 = 2885mV
587 )))
588
589 (((
590 Ex2: 0x0B49 = 2889mV
591 )))
592
593
594
595 === 2.3.5  Signal Strength ===
596
597 (((
598 NB-IoT Network signal Strength.
599 )))
600
601 (((
602 **Ex1: 0x1d = 29**
603 )))
604
605 (((
606 (% style="color:blue" %)**0**(%%)  -113dBm or less
607 )))
608
609 (((
610 (% style="color:blue" %)**1**(%%)  -111dBm
611 )))
612
613 (((
614 (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
615 )))
616
617 (((
618 (% style="color:blue" %)**31**  (%%) -51dBm or greater
619 )))
620
621 (((
622 (% style="color:blue" %)**99**   (%%) Not known or not detectable
623 )))
624
625
626
627 === 2.3.6  Temperature & Humidity ===
628
629 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
630
631 [[image:image-20220709161741-3.png]]
632
633
634 Convert the read byte to decimal and divide it by ten.
635
636
637 **Example:**
638
639 Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
640
641 Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
642
643
644
645 == 2.4  Downlink Payload ==
646
647 By default, N95S31B prints the downlink payload to console port.
648
649 [[image:image-20220709100028-1.png]]
650
651
652 (((
653 (% style="color:blue" %)**Examples:**
654 )))
655
656 (((
657
658 )))
659
660 * (((
661 (% style="color:blue" %)**Set TDC**
662 )))
663
664 (((
665 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
666 )))
667
668 (((
669 Payload:    01 00 00 1E    TDC=30S
670 )))
671
672 (((
673 Payload:    01 00 00 3C    TDC=60S
674 )))
675
676 (((
677
678 )))
679
680 * (((
681 (% style="color:blue" %)**Reset**
682 )))
683
684 (((
685 If payload = 0x04FF, it will reset the N95S31B
686 )))
687
688
689 * (% style="color:blue" %)**INTMOD**
690
691 (((
692 Downlink Payload: 06000003, Set AT+INTMOD=3
693 )))
694
695
696
697 == 2.5  ​Battery Analysis ==
698
699 === 2.5.1  ​Battery Type ===
700
701
702 (((
703 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.
704 )))
705
706 (((
707 The battery is designed to last for several years depends on the actually use environment and update interval. 
708 )))
709
710 (((
711 The battery related documents as below:
712 )))
713
714 * [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
715 * [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
716 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
717
718 (((
719 [[image:image-20220709101450-2.png]]
720 )))
721
722
723
724 === 2.5.2  Power consumption Analyze ===
725
726 (((
727 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.
728 )))
729
730 (((
731
732 )))
733
734
735 === 2.5.3  ​Battery Note ===
736
737 (((
738 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.
739 )))
740
741
742
743 === 2.5.4  Replace the battery ===
744
745
746 (((
747 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.
748 )))
749
750
751 (((
752 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).
753 )))
754
755
756
757 = 3. ​ Access NB-IoT Module =
758
759 (((
760 Users can directly access the AT command set of the NB-IoT module.
761 )))
762
763 (((
764 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/]] 
765 )))
766
767 [[image:1657333200519-600.png]]
768
769
770
771 = 4.  Using the AT Commands =
772
773 == 4.1  Access AT Commands ==
774
775 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/]]
776
777
778 AT+<CMD>?  : Help on <CMD>
779
780 AT+<CMD>         : Run <CMD>
781
782 AT+<CMD>=<value> : Set the value
783
784 AT+<CMD>=?  : Get the value
785
786
787 (% style="color:#037691" %)**General Commands**(%%)      
788
789 AT  : Attention       
790
791 AT?  : Short Help     
792
793 ATZ  : MCU Reset    
794
795 AT+TDC  : Application Data Transmission Interval
796
797 AT+CFG  : Print all configurations
798
799 AT+CFGMOD           : Working mode selection
800
801 AT+INTMOD            : Set the trigger interrupt mode
802
803 AT+5VT  : Set extend the time of 5V power  
804
805 AT+PRO  : Choose agreement
806
807 AT+WEIGRE  : Get weight or set weight to 0
808
809 AT+WEIGAP  : Get or Set the GapValue of weight
810
811 AT+RXDL  : Extend the sending and receiving time
812
813 AT+CNTFAC  : Get or set counting parameters
814
815 AT+SERVADDR  : Server Address
816
817
818 (% style="color:#037691" %)**COAP Management**      
819
820 AT+URI            : Resource parameters
821
822
823 (% style="color:#037691" %)**UDP Management**
824
825 AT+CFM          : Upload confirmation mode (only valid for UDP)
826
827
828 (% style="color:#037691" %)**MQTT Management**
829
830 AT+CLIENT               : Get or Set MQTT client
831
832 AT+UNAME  : Get or Set MQTT Username
833
834 AT+PWD                  : Get or Set MQTT password
835
836 AT+PUBTOPIC  : Get or Set MQTT publish topic
837
838 AT+SUBTOPIC  : Get or Set MQTT subscription topic
839
840
841 (% style="color:#037691" %)**Information**          
842
843 AT+FDR  : Factory Data Reset
844
845 AT+PWORD  : Serial Access Password
846
847
848
849 = ​5.  FAQ =
850
851 == 5.1 ​ How to Upgrade Firmware ==
852
853
854 (((
855 User can upgrade the firmware for 1) bug fix, 2) new feature release.
856 )))
857
858 (((
859 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]]
860 )))
861
862 (((
863
864
865 (((
866 (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
867 )))
868 )))
869
870
871
872 = 6.  Trouble Shooting =
873
874 == 6.1  ​Connection problem when uploading firmware ==
875
876
877 (((
878 **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]]
879 )))
880
881 (% class="wikigeneratedid" %)
882 (((
883
884 )))
885
886
887 == 6.2  AT Command input doesn't work ==
888
889 (((
890 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.
891
892
893 )))
894
895
896 = 7. ​ Order Info =
897
898
899 Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
900
901
902 (% class="wikigeneratedid" %)
903 (((
904
905 )))
906
907 = 8.  Packing Info =
908
909 (((
910
911
912 (% style="color:#037691" %)**Package Includes**:
913
914 * N95S31B NB-IoT Temperature and Humidity Sensor
915 * External antenna x 1
916 )))
917
918 (((
919
920
921 (% style="color:#037691" %)**Dimension and weight**:
922
923 * Device Size: 13.0 x 5 x 4.5 cm
924 * Device Weight: 150g
925 * Package Size / pcs : 14.0 x 8x 5 cm
926 * Weight / pcs : 180g
927 )))
928
929 (((
930
931
932
933
934 )))
935
936 = 9.  Support =
937
938 * 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.
939 * 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]]