Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 4 added, 0 removed)
  • 1657520100595-569.png
  • image-20220908154949-1.png
  • image-20220908163102-2.png
  • image-20221009001045-1.png

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Xiaoling
	1	+XWiki.Edwin

Content

...	...	@@ -9,6 +9,7 @@
9	9
10	10	**Table of Contents:**
11	11
	12	+{{toc/}}
12	12
13	13
14	14
...	...	@@ -16,21 +16,35 @@
16	16
17	17	= 1.  Introduction =
18	18
	20	+
19	19	== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
20	20
21	21	(((
22	22
23	23
	26	+(((
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*.
	28	+)))
25	25
	30	+(((
26	26	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	+)))
27	27
	34	+(((
28	28	N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
	36	+)))
29	29
	38	+(((
30	30	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	+)))
31	31
	42	+(((
	43	+
	44	+)))
32	32
	46	+(((
33	33	~* make sure you have NB-IoT coverage locally.
	48	+)))
34	34
35	35
36	36	)))
...	...	@@ -41,6 +41,7 @@
41	41
42	42	== 1.2 ​ Features ==
43	43
	59	+
44	44	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
45	45	* Monitor Temperature & Humidity via SHT31
46	46	* AT Commands to change parameters
...	...	@@ -52,9 +52,6 @@
52	52	* Micro SIM card slot for NB-IoT SIM
53	53	* 8500mAh Battery for long term use
54	54
55		-
56		-
57		-
58	58	== 1.3  Specification ==
59	59
60	60
...	...	@@ -74,7 +74,6 @@
74	74
75	75	(% style="color:#037691" %)**Battery:**
76	76
77		-
78	78	* Li/SOCI2 un-chargeable battery
79	79	* Capacity: 8500mAh
80	80	* Self Discharge: <1% / Year @ 25°C
...	...	@@ -81,11 +81,9 @@
81	81	* Max continuously current: 130mA
82	82	* Max boost current: 2A, 1 second
83	83
84		-
85		-
86		-
87	87	== ​1.4  Applications ==
88	88
	98	+
89	89	* Smart Buildings & Home Automation
90	90	* Logistics and Supply Chain Management
91	91	* Smart Metering
...	...	@@ -97,15 +97,21 @@
97	97	​
98	98
99	99
100		-== 1.5  Pin Definitions ==
101	101
	111	+
	112	+== 1.5  Pin Definitions & Switch ==
	113	+
	114	+
102	102	N95S31B use the mother board from NBSN95 which as below.
103	103
	117	+
104	104	[[image:image-20220709144723-1.png]]
105	105
106	106
	121	+
107	107	=== 1.5.1 Jumper JP2 ===
108	108
	124	+
109	109	Power on Device when put this jumper.
110	110
111	111
...	...	@@ -112,14 +112,20 @@
112	112
113	113	=== 1.5.2 BOOT MODE / SW1 ===
114	114
	131	+
	132	+(((
115	115	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.
	134	+)))
116	116
	136	+(((
117	117	2) Flash: work mode, device starts to work and send out console output for further debug
	138	+)))
118	118
119	119
120	120
121	121	=== 1.5.3 Reset Button ===
122	122
	144	+
123	123	Press to reboot the device.
124	124
125	125
...	...	@@ -126,14 +126,15 @@
126	126
127	127	=== 1.5.4 LED ===
128	128
	151	+
129	129	It will flash:
130	130
131	131	1. When boot the device in flash mode
132	132	1. Send an uplink packet
133	133
134		-
135	135	= 2.  Use N95S31B to communicate with IoT Server =
136	136
	159	+
137	137	== 2.1  How it works ==
138	138
139	139
...	...	@@ -150,7 +150,7 @@
150	150
151	151	)))
152	152
153		-[[image:1657350248151-650.png]]
	176	+[[image:1657520100595-569.png]]
154	154
155	155	(((
156	156
...	...	@@ -166,26 +166,49 @@
166	166	[[image:image-20220709150546-2.png]]
167	167
168	168
	192	+
169	169	=== 2.2.1 Test Requirement ===
170	170
171	171
	196	+(((
172	172	To use N95S31B in your city, make sure meet below requirements:
	198	+)))
173	173
174		-* Your local operator has already distributed a NB-IoT Network there.
175		-* The local NB-IoT network used the band that N95S31B supports.
176		-* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	200	+* (((
	201	+Your local operator has already distributed a NB-IoT Network there.
	202	+)))
	203	+* (((
	204	+The local NB-IoT network used the band that N95S31B supports.
	205	+)))
	206	+* (((
	207	+Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	208	+)))
177	177
	210	+(((
178	178	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
	212	+)))
179	179
	214	+(((
180	180	N95S31B supports different communication protocol such as :
	216	+)))
181	181
182	182	(((
183		-* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
184		-* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
185		-* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
186		-* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	219	+* (((
	220	+CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
	221	+)))
	222	+* (((
	223	+raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
	224	+)))
	225	+* (((
	226	+MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
	227	+)))
	228	+* (((
	229	+TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	230	+)))
187	187
	232	+(((
188	188	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.
	234	+)))
189	189
190	190
191	191	)))
...	...	@@ -196,6 +196,7 @@
196	196
197	197	=== 2.2.3  Insert SIM card ===
198	198
	245	+
199	199	(((
200	200	Insert the NB-IoT Card get from your provider.
201	201	)))
...	...	@@ -211,14 +211,18 @@
211	211
212	212	=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
213	213
	261	+
214	214	(((
215	215	(((
216	216	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.
	265	+
	266	+
217	217	)))
218	218	)))
219	219
220	220	[[image:1657351312545-300.png]]
221	221
	272	+
222	222	**Connection:**
223	223
224	224	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
...	...	@@ -242,8 +242,9 @@
242	242
243	243	[[image:1657329814315-101.png]]
244	244
	296	+
245	245	(((
246		-(% 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/]]
	298	+(% 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]]**
247	247	)))
248	248
249	249
...	...	@@ -250,9 +250,10 @@
250	250
251	251	=== 2.2.5  Use CoAP protocol to uplink data ===
252	252
253		-(% 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/]]
254	254
	306	+(% 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/]]**
255	255
	308	+
256	256	(((
257	257	**Use below commands:**
258	258	)))
...	...	@@ -300,6 +300,7 @@
300	300
301	301	=== 2.2.7  Use MQTT protocol to uplink data ===
302	302
	356	+
303	303	N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
304	304
305	305	* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
...	...	@@ -315,6 +315,7 @@
315	315
316	316	[[image:1657352645687-385.png]]
317	317
	372	+
318	318	(((
319	319	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.
320	320	)))
...	...	@@ -328,6 +328,7 @@
328	328
329	329	=== 2.2.8  Use TCP protocol to uplink data ===
330	330
	386	+
331	331	This feature is supported since firmware version v110
332	332
333	333	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
...	...	@@ -342,6 +342,7 @@
342	342
343	343	=== 2.2.9  Change Update Interval ===
344	344
	401	+
345	345	User can use below command to change the (% style="color:green" %)**uplink interval**.
346	346
347	347	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
...	...	@@ -350,58 +350,104 @@
350	350
351	351	)))
352	352
	410	+(((
	411	+(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
	412	+)))
353	353
	414	+(((
	415	+(% 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).**
	416	+)))
354	354
	418	+
	419	+
355	355	== 2.3  Uplink Payload ==
356	356
357	357
358		-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.
	423	+(((
	424	+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.
	425	+)))
359	359
360	360
	428	+(((
361	361	For example:
	430	+)))
362	362
363		- (% 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.
	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	+)))
364	364
365	365
	437	+(((
366	366	The uplink payloads are composed in  ASCII String. For example:
	439	+)))
367	367
	441	+(((
368	368	0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
	443	+)))
369	369
	445	+(((
370	370	0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
	447	+)))
371	371
372	372
	450	+(((
373	373	(% style="color:red" %)**NOTE:**
	452	+)))
374	374
375	375	(% style="color:red" %)
376		-1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
377		-1. By default, the device will send an uplink message every 1 hour.
	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.**
378	378
379	379
380	380
	463	+
	464	+)))
	465	+
381	381	=== 2.3.1  Payload Analyze ===
382	382
	468	+
	469	+==== 2.3.1.1  Before Firmware v1.2 ====
	470	+
	471	+
383	383	N95S31B uplink payload includes in total 21 bytes
384	384
385	385
386		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
	475	+(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %)
387	387	|=(% style="width: 60px;" %)(((
388	388	**Size(bytes)**
389		-)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1**
390		-|(% 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:123px" %)MOD 0X01|(% style="width:99px" %)(((
	478	+)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 174px;" %)5|=(% style="width: 106px;" %)**2**|=(% style="width: 85px;" %)**2**
	479	+|(% 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:174px" %)(((
	480	+(((
391	391	Reserve/ Same as NBSN95 CFGMOD=1
	482	+)))
392	392
	484	+(((
393	393	No function here.
394		-)))|(% style="width:77px" %)(((
395		-[[Temperature >>||anchor="H2.4.5A0Distance"]]
	486	+)))
	487	+)))|(% style="width:106px" %)(((
	488	+(((
	489	+[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
	490	+)))
396	396
	492	+(((
397	397	By SHT31
398		-)))|(% style="width:80px" %)(((
399		-[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
	494	+)))
	495	+)))|(% style="width:85px" %)(((
	496	+(((
	497	+[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
	498	+)))
400	400
	500	+(((
401	401	By SHT31
402	402	)))
	503	+)))
403	403
404	404	(((
	506	+
	507	+
405	405	(((
406	406	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
407	407	)))
...	...	@@ -413,27 +413,80 @@
413	413
414	414	The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
415	415
416		-* Device ID: 0x724031607457 = 724031607457
417		-* Version: 0x006e=110=1.1.0
	519	+* Device ID:  0x724031607457 = 724031607457
418	418
419		-* BAT: 0x0ccd = 3277 mV = 3.277V
420		-* Signal: 0x1b = 27
421		-* Model: 0x01 = 1
	521	+* Version:  0x006e=110=1.1.0
	522	+
	523	+* BAT:  0x0ccd = 3277 mV = 3.277V
	524	+
	525	+* Signal:  0x1b = 27
	526	+
	527	+* Model:  0x01 = 1
	528	+
422	422	* 0x00dc000ccc= reserve, ignore in N95S31B
423		-* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
424		-* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
425	425
	531	+* Temperature by SHT31:  0x00e1 = 225 = 22.5 °C
	532	+
	533	+* Humidity by SHT31:  0x0186 = 390 = 39.0 %rh
	534	+
426	426	(((
427	427
428		-)))
429	429
430		-(((
	538	+
431	431
432	432	)))
433	433
	542	+==== 2.3.1.2 Since Firmware v1.2 ====
434	434
	544	+
	545	+In this mode, uplink payload includes 91 bytes in total by default.
	546	+
	547	+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.
	548	+
	549	+
	550	+(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %)
	551	+|(% style="width:95px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:43px" %)**2**|(% style="width:47px" %)**2**|(% style="width:124px" %)**1**|(% style="width:56px" %)**1**|(% style="width:109px" %)**2**|(% style="width:80px" %)**1**|(% style="width:51px" %)**2**|(% style="width:79px" %)**2**|(% style="width:84px" %)**2**|(% style="width:100px" %)**4**|(% style="width:76px" %)**2**|(% style="width:81px" %)**2**|(% style="width:121px" %)**4**
	552	+|(% 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 .....
	553	+
	554	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
	555	+
	556	+
	557	+[[image:image-20220908154949-1.png]]
	558	+
	559	+
	560	+The payload is ASCII string, representative same HEX:
	561	+
	562	+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:
	563	+
	564	+* (% style="color:red" %)Device ID: f868411056758782 = f868411056758782
	565	+
	566	+* (% style="color:blue" %)Version: 0x000c=120=1.2
	567	+
	568	+* (% style="color:green" %)BAT: 0x0d0f = 3343 mV = 3.343V
	569	+
	570	+* (% style="color:red" %)Singal: 0x0c = 12
	571	+
	572	+* (% style="color:blue" %)Mod: 0x01 = 1
	573	+
	574	+* TemDS18B20: 0x0000= 0 = 0
	575	+
	576	+* (% style="color:green" %)Interrupt: 0x00= 0
	577	+
	578	+* (% style="color:green" %)adc: 0x0030= 48
	579	+
	580	+* SHTTEM: 0x0114= 276 = 27.6
	581	+
	582	+* SHTHUM:0x0231 =561=56.1%
	583	+
	584	+* (% style="color:red" %)Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	585	+
	586	+* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
	587	+
	588	+* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,.......
	589	+
435	435	=== 2.3.2  Device ID ===
436	436
	592	+
437	437	(((
438	438	By default, the Device ID equal to the last 6 bytes of IMEI.
439	439	)))
...	...	@@ -440,10 +440,12 @@
440	440
441	441	(((
442	442	User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	599	+
	600	+
443	443	)))
444	444
445	445	(((
446		-**Example:**
	604	+(% style="color:blue" %)**Example:**
447	447	)))
448	448
449	449	(((
...	...	@@ -451,22 +451,47 @@
451	451	)))
452	452
453	453	(((
454		-The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	612	+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.
	613	+
	614	+
455	455	)))
456	456
	617	+(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
457	457
458	458
	620	+By default, the Device ID equal to the last 15 bits of IMEI.
	621	+
	622	+User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
	623	+
	624	+
	625	+**​​​​​​​​​​​​​​(% style="color:blue" %)Example:(%%)**
	626	+
	627	+AT+DEUI=868411056754138
	628	+
	629	+
	630	+
459	459	=== 2.3.3  Version Info ===
460	460
461	461
	634	+(((
462	462	These bytes include the hardware and software version.
	636	+)))
463	463
	638	+(((
464	464	Higher byte: Specify hardware version: always 0x00 for N95S31B
	640	+)))
465	465
	642	+(((
466	466	Lower byte: Specify the software version: 0x6E=110, means firmware version 110
	644	+)))
467	467
	646	+(((
	647	+
	648	+)))
468	468
	650	+(((
469	469	For example: 0x00 6E: this device is N95S31B with firmware version 110.
	652	+)))
470	470
471	471	(((
472	472
...	...	@@ -475,6 +475,7 @@
475	475
476	476	=== 2.3.4  Battery Info ===
477	477
	661	+
478	478	(((
479	479	Ex1: 0x0B45 = 2885mV
480	480	)))
...	...	@@ -487,6 +487,7 @@
487	487
488	488	=== 2.3.5  Signal Strength ===
489	489
	674	+
490	490	(((
491	491	NB-IoT Network signal Strength.
492	492	)))
...	...	@@ -519,6 +519,7 @@
519	519
520	520	=== 2.3.6  Temperature & Humidity ===
521	521
	707	+
522	522	The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
523	523
524	524	[[image:image-20220709161741-3.png]]
...	...	@@ -535,10 +535,11 @@
535	535
536	536
537	537
538		-== 2.5  Downlink Payload ==
	724	+== 2.4  Downlink Payload ==
539	539
540		-By default, NDDS75 prints the downlink payload to console port.
541	541
	727	+By default, N95S31B prints the downlink payload to console port.
	728	+
542	542	[[image:image-20220709100028-1.png]]
543	543
544	544
...	...	@@ -575,7 +575,7 @@
575	575	)))
576	576
577	577	(((
578		-If payload = 0x04FF, it will reset the NDDS75
	765	+If payload = 0x04FF, it will reset the N95S31B
579	579	)))
580	580
581	581
...	...	@@ -587,13 +587,76 @@
587	587
588	588
589	589
590		-== 2.5  ​Battery Analysis ==
	777	+== 2.5  Humidity and Temperature alarm function ==
591	591
592		-=== 2.5.1  ​Battery Type ===
593	593
	780	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
594	594
	782	+
	783	+(% style="color:#037691" %)**AT+ SHHUM=min,max**
	784	+
	785	+
	786	+² When min=0, and max≠0, Alarm higher than max
	787	+
	788	+² When min≠0, and max=0, Alarm lower than min
	789	+
	790	+² When min≠0 and max≠0, Alarm higher than max or lower than min
	791	+
	792	+
	793	+ (% style="color:blue" %)**Example:**
	794	+
	795	+AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
	796	+
	797	+
	798	+(% style="color:#037691" %)**AT+ SHTEMP=min,max**
	799	+
	800	+² When min=0, and max≠0, Alarm higher than max
	801	+
	802	+² When min≠0, and max=0, Alarm lower than min
	803	+
	804	+² When min≠0 and max≠0, Alarm higher than max or lower than min
	805	+
	806	+
	807	+**~ (% style="color:blue" %)Example:(%%)**
	808	+
	809	+AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
	810	+
	811	+
	812	+
	813	+== 2.6 Set the number of data to be uploaded and the recording time ==
	814	+
	815	+
	816	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
	817	+
	818	+* (% 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)
	819	+* (% 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.
	820	+
	821	+ The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
	822	+
	823	+[[image:image-20221009001045-1.png||height="726" width="1009"]]
	824	+
	825	+
	826	+
	827	+== 2.7 Read or Clear cached data ==
	828	+
	829	+
	830	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
	831	+
	832	+* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
	833	+* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
	834	+
	835	+[[image:image-20220908163102-2.png]]
	836	+
	837	+
	838	+
	839	+== 2.8  ​Battery Analysis ==
	840	+
	841	+
	842	+=== 2.8.1  ​Battery Type ===
	843	+
	844	+
595	595	(((
596		-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.
	846	+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.
597	597	)))
598	598
599	599	(((
...	...	@@ -614,56 +614,37 @@
614	614
615	615
616	616
617		-=== 2.5.2  Power consumption Analyze ===
	867	+=== 2.8.2  Power consumption Analyze ===
618	618
619		-(((
620		-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.
621		-)))
622	622
623		-
624	624	(((
625		-Instruction to use as below:
	871	+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.
626	626	)))
627	627
628	628	(((
629		-(% 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/]]
	875	+
630	630	)))
631	631
632	632
633		-(((
634		-(% style="color:blue" %)**Step 2: **(%%) Open it and choose
635		-)))
	879	+=== 2.8.3  ​Battery Note ===
636	636
637		-* (((
638		-Product Model
639		-)))
640		-* (((
641		-Uplink Interval
642		-)))
643		-* (((
644		-Working Mode
645		-)))
646	646
647	647	(((
648		-And the Life expectation in difference case will be shown on the right.
	883	+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.
649	649	)))
650	650
651		-[[image:image-20220709110451-3.png]]
652	652
653	653
	888	+=== 2.8.4  Replace the battery ===
654	654
655		-=== 2.5.3  ​Battery Note ===
656	656
657	657	(((
658		-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.
	892	+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.
659	659	)))
660	660
661	661
662		-
663		-=== 2.5.4  Replace the battery ===
664		-
665	665	(((
666		-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).
	897	+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).
667	667	)))
668	668
669	669
...	...	@@ -670,6 +670,7 @@
670	670
671	671	= 3. ​ Access NB-IoT Module =
672	672
	904	+
673	673	(((
674	674	Users can directly access the AT command set of the NB-IoT module.
675	675	)))
...	...	@@ -676,6 +676,8 @@
676	676
677	677	(((
678	678	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/]]
	911	+
	912	+
679	679	)))
680	680
681	681	[[image:1657333200519-600.png]]
...	...	@@ -684,11 +684,13 @@
684	684
685	685	= 4.  Using the AT Commands =
686	686
	921	+
687	687	== 4.1  Access AT Commands ==
688	688
689		-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/]]
690	690
	925	+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]]
691	691
	927	+
692	692	AT+<CMD>?  : Help on <CMD>
693	693
694	694	AT+<CMD>         : Run <CMD>
...	...	@@ -728,7 +728,24 @@
728	728
729	729	AT+SERVADDR  : Server Address
730	730
	967	+AT+TR      : Get or Set record time
731	731
	969	+AT+APN     : Get or set the APN
	970	+
	971	+AT+FBAND   : Get or Set whether to automatically modify the frequency band
	972	+
	973	+AT+DNSCFG  : Get or Set DNS Server
	974	+
	975	+AT+GETSENSORVALUE   : Returns the current sensor measurement
	976	+
	977	+AT+NOUD      : Get or Set the number of data to be uploaded
	978	+
	979	+AT+CDP     : Read or Clear cached data
	980	+
	981	+AT+SHTEMP: Get or Set alarm of temp
	982	+
	983	+AT+SHHUM: Get or Set alarm of moisture
	984	+
732	732	(% style="color:#037691" %)**COAP Management**
733	733
734	734	AT+URI            : Resource parameters
...	...	@@ -762,6 +762,7 @@
762	762
763	763	= ​5.  FAQ =
764	764
	1018	+
765	765	== 5.1 ​ How to Upgrade Firmware ==
766	766
767	767
...	...	@@ -774,13 +774,18 @@
774	774	)))
775	775
776	776	(((
777		-(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
	1031	+
	1032	+
	1033	+(((
	1034	+(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
778	778	)))
	1036	+)))
779	779
780	780
781	781
782	782	= 6.  Trouble Shooting =
783	783
	1042	+
784	784	== 6.1  ​Connection problem when uploading firmware ==
785	785
786	786
...	...	@@ -796,6 +796,7 @@
796	796
797	797	== 6.2  AT Command input doesn't work ==
798	798
	1058	+
799	799	(((
800	800	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.
801	801
...	...	@@ -806,7 +806,7 @@
806	806	= 7. ​ Order Info =
807	807
808	808
809		-Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
	1069	+Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
810	810
811	811
812	812	(% class="wikigeneratedid" %)
...	...	@@ -821,7 +821,7 @@
821	821
822	822	(% style="color:#037691" %)**Package Includes**:
823	823
824		-* NSE01 NB-IoT Distance Detect Sensor Node x 1
	1084	+* N95S31B NB-IoT Temperature and Humidity Sensor
825	825	* External antenna x 1
826	826	)))
827	827
...	...	@@ -830,11 +830,10 @@
830	830
831	831	(% style="color:#037691" %)**Dimension and weight**:
832	832
833		-
834	834	* Device Size: 13.0 x 5 x 4.5 cm
835	835	* Device Weight: 150g
836		-* Package Size / pcs : 15 x 12x 5.5 cm
837		-* Weight / pcs : 220g
	1095	+* Package Size / pcs : 14.0 x 8x 5 cm
	1096	+* Weight / pcs : 180g
838	838	)))
839	839
840	840	(((
...	...	@@ -846,5 +846,7 @@
846	846
847	847	= 9.  Support =
848	848
	1108	+
849	849	* 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.
850	850	* 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]]
	1111	+

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

image-20221009001045-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Edwin

Size

...	...	@@ -1,0 +1,1 @@
	1	+282.9 KB

Content