Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual

Summary

• Page properties (3 modified, 0 added, 0 removed)
• Attachments (0 modified, 22 added, 0 removed)
  • 1657348034241-728.png
  • 1657348284168-431.png
  • 1657350248151-650.png
  • 1657350625843-586.png
  • 1657351240556-536.png
  • 1657351312545-300.png
  • 1657352146020-183.png
  • 1657352185396-303.png
  • 1657352391268-297.png
  • 1657352403317-397.png
  • 1657352634421-276.png
  • 1657352645687-385.png
  • 1657352898400-901.png
  • 1657352914475-252.png
  • 1657354294009-643.png
  • 1657520100595-569.png
  • image-20220709144723-1.png
  • image-20220709150546-2.png
  • image-20220709161741-3.png
  • image-20220908154949-1.png
  • image-20220908163102-2.png
  • image-20221009001045-1.png

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-NDDS75 NB-IoT Distance Detect Sensor User Manual
	1	+N95S31B NB-IoT Temperature & Humidity Sensor User Manual

Author

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

Content

...	...	@@ -1,10 +1,12 @@
1	1	(% style="text-align:center" %)
2		-[[image:image-20220709085040-1.png||height="542" width="524"]]
	2	+[[image:1657348034241-728.png||height="470" width="470"]]
3	3
4	4
5	5
6	6
7	7
	8	+
	9	+
8	8	**Table of Contents:**
9	9
10	10	{{toc/}}
...	...	@@ -13,49 +13,41 @@
13	13
14	14
15	15
16		-
17	17	= 1.  Introduction =
18	18
19		-== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
	20	+== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
20	20
21	21	(((
22	22
23	23
24	24	(((
25		-(((
26		-The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
	26	+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*.
27	27	)))
28	28
29	29	(((
30		-
31		-The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
	30	+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	32	)))
33	33
34	34	(((
35		-
36		-NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
	34	+N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
37	37	)))
38	38
39	39	(((
40		-
41		-NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
	38	+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).
42	42	)))
43	43
44	44	(((
45		-
46		-NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
	42	+
47	47	)))
48	48
49	49	(((
50		-
51		-To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
	46	+~* make sure you have NB-IoT coverage locally.
52	52	)))
53		-)))
54	54
55	55
56	56	)))
57	57
58		-[[image:1657327959271-447.png]]
	52	+[[image:1657348284168-431.png]]
59	59
60	60
61	61
...	...	@@ -63,15 +63,13 @@
63	63
64	64
65	65	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
66		-* Ultra low power consumption
67		-* Distance Detection by Ultrasonic technology
68		-* Flat object range 280mm - 7500mm
69		-* Accuracy: ±(1cm+S*0.3%) (S: Distance)
70		-* Cable Length: 25cm
	60	+* Monitor Temperature & Humidity via SHT31
71	71	* AT Commands to change parameters
72	72	* Uplink on periodically
73	73	* Downlink to change configure
74	74	* IP66 Waterproof Enclosure
	65	+* Ultra-Low Power consumption
	66	+* AT Commands to change parameters
75	75	* Micro SIM card slot for NB-IoT SIM
76	76	* 8500mAh Battery for long term use
77	77
...	...	@@ -86,12 +86,12 @@
86	86
87	87	(% style="color:#037691" %)**NB-IoT Spec:**
88	88
89		-* - B1 @H-FDD: 2100MHz
90		-* - B3 @H-FDD: 1800MHz
91		-* - B8 @H-FDD: 900MHz
92		-* - B5 @H-FDD: 850MHz
93		-* - B20 @H-FDD: 800MHz
94		-* - B28 @H-FDD: 700MHz
	81	+* B1 @H-FDD: 2100MHz
	82	+* B3 @H-FDD: 1800MHz
	83	+* B8 @H-FDD: 900MHz
	84	+* B5 @H-FDD: 850MHz
	85	+* B20 @H-FDD: 800MHz
	86	+* B28 @H-FDD: 700MHz
95	95
96	96	(% style="color:#037691" %)**Battery:**
97	97
...	...	@@ -101,14 +101,10 @@
101	101	* Max continuously current: 130mA
102	102	* Max boost current: 2A, 1 second
103	103
104		-(% style="color:#037691" %)**Power Consumption**
105	105
106		-* STOP Mode: 10uA @ 3.3v
107		-* Max transmit power: 350mA@3.3v
108		-
109		-
110	110	== ​1.4  Applications ==
111	111
	99	+
112	112	* Smart Buildings & Home Automation
113	113	* Logistics and Supply Chain Management
114	114	* Smart Metering
...	...	@@ -120,24 +120,61 @@
120	120	​
121	121
122	122
123		-== 1.5  Pin Definitions ==
	111	+== 1.5  Pin Definitions & Switch ==
124	124
125	125
126		-[[image:1657328609906-564.png]]
	114	+N95S31B use the mother board from NBSN95 which as below.
127	127
128	128
	117	+[[image:image-20220709144723-1.png]]
129	129
130		-= 2.  Use NDDS75 to communicate with IoT Server =
131	131
	120	+=== 1.5.1 Jumper JP2 ===
	121	+
	122	+
	123	+Power on Device when put this jumper.
	124	+
	125	+
	126	+=== 1.5.2 BOOT MODE / SW1 ===
	127	+
	128	+
	129	+(((
	130	+**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.
	131	+)))
	132	+
	133	+(((
	134	+**2) Flash:**  work mode, device starts to work and send out console output for further debug
	135	+)))
	136	+
	137	+
	138	+=== 1.5.3 Reset Button ===
	139	+
	140	+
	141	+Press to reboot the device.
	142	+
	143	+
	144	+=== 1.5.4 LED ===
	145	+
	146	+
	147	+It will flash:
	148	+
	149	+1.  When boot the device in flash mode
	150	+
	151	+2.  Send an uplink packet
	152	+
	153	+
	154	+= 2.  Use N95S31B to communicate with IoT Server =
	155	+
132	132	== 2.1  How it works ==
133	133
	158	+
134	134	(((
135		-The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 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 NDDS75.
	160	+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.
136	136	)))
137	137
138	138
139	139	(((
140		-The diagram below shows the working flow in default firmware of NDDS75:
	165	+The diagram below shows the working flow in default firmware of N95S31B:
141	141	)))
142	142
143	143	(((
...	...	@@ -144,7 +144,7 @@
144	144
145	145	)))
146	146
147		-[[image:1657328659945-416.png]]
	172	+[[image:1657520100595-569.png]]
148	148
149	149	(((
150	150
...	...	@@ -151,30 +151,66 @@
151	151	)))
152	152
153	153
154		-== 2.2 ​ Configure the NDDS75 ==
	179	+== 2.2 ​ Configure the N95S31B ==
155	155
	181	+=== 2.2.1  Power On N95S31B ===
156	156
157		-=== 2.2.1 Test Requirement ===
158	158
	184	+[[image:image-20220709150546-2.png]]
	185	+
	186	+
	187	+=== 2.2.2 Test Requirement ===
	188	+
	189	+
159	159	(((
160		-To use NDDS75 in your city, make sure meet below requirements:
	191	+To use N95S31B in your city, make sure meet below requirements:
161	161	)))
162	162
163		-* Your local operator has already distributed a NB-IoT Network there.
164		-* The local NB-IoT network used the band that NSE01 supports.
165		-* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	194	+* (((
	195	+Your local operator has already distributed a NB-IoT Network there.
	196	+)))
	197	+* (((
	198	+The local NB-IoT network used the band that N95S31B supports.
	199	+)))
	200	+* (((
	201	+Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	202	+)))
166	166
167	167	(((
168		-Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
	205	+Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
169	169	)))
170	170
	208	+(((
	209	+N95S31B supports different communication protocol such as :
	210	+)))
171	171
172		-[[image:1657328756309-230.png]]
	212	+(((
	213	+* (((
	214	+CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
	215	+)))
	216	+* (((
	217	+raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
	218	+)))
	219	+* (((
	220	+MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
	221	+)))
	222	+* (((
	223	+TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	224	+)))
173	173
	226	+(((
	227	+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.
	228	+)))
174	174
	230	+
	231	+)))
175	175
176		-=== 2.2.2 Insert SIM card ===
	233	+[[image:1657350625843-586.png]]
177	177
	235	+
	236	+=== 2.2.3  Insert SIM card ===
	237	+
	238	+
178	178	(((
179	179	Insert the NB-IoT Card get from your provider.
180	180	)))
...	...	@@ -184,29 +184,32 @@
184	184	)))
185	185
186	186
187		-[[image:1657328884227-504.png]]
	248	+[[image:1657351240556-536.png]]
188	188
189	189
	251	+=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
190	190
191		-=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
192	192
193	193	(((
194	194	(((
195		-User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
	256	+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.
	257	+
	258	+
196	196	)))
197	197	)))
198	198
199		-[[image:image-20220709092052-2.png]]
	262	+[[image:1657351312545-300.png]]
200	200
201		-**Connection:**
202	202
203		- (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
	265	+(% style="color:blue" %)**Connection:**
204	204
205		- (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
	267	+ (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
206	206
207		- (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
	269	+**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
208	208
	271	+**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
209	209
	273	+
210	210	In the PC, use below serial tool settings:
211	211
212	212	* Baud:  (% style="color:green" %)**9600**
...	...	@@ -216,20 +216,21 @@
216	216	* Flow Control: (% style="color:green" %)**None**
217	217
218	218	(((
219		-Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
	283	+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.
220	220	)))
221	221
222	222	[[image:1657329814315-101.png]]
223	223
	288	+
224	224	(((
225		-(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
	290	+(% 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]]**
226	226	)))
227	227
228	228
	294	+=== 2.2.5  Use CoAP protocol to uplink data ===
229	229
230		-=== 2.2.4 Use CoAP protocol to uplink data ===
231	231
232		-(% 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/]]
	297	+(% 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/]]**
233	233
234	234
235	235	(((
...	...	@@ -240,17 +240,19 @@
240	240	(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
241	241	)))
242	242	* (((
243		-(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
	308	+(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
244	244	)))
245	245	* (((
246		-(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
	311	+(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
247	247	)))
248	248
249	249	(((
	315	+
	316	+
250	250	For parameter description, please refer to AT command set
251	251	)))
252	252
253		-[[image:1657330452568-615.png]]
	320	+[[image:1657352146020-183.png]]
254	254
255	255
256	256	(((
...	...	@@ -257,61 +257,67 @@
257	257	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.
258	258	)))
259	259
260		-[[image:1657330472797-498.png]]
	327	+[[image:1657352185396-303.png]]
261	261
262	262
	330	+=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
263	263
264		-=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
265	265
266		-
267	267	* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
268	268	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
269	269	* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
270	270
271		-[[image:1657330501006-241.png]]
	337	+[[image:1657352391268-297.png]]
272	272
273	273
274		-[[image:1657330533775-472.png]]
	340	+[[image:1657352403317-397.png]]
275	275
276	276
	343	+=== 2.2.7  Use MQTT protocol to uplink data ===
277	277
278		-=== 2.2.6 Use MQTT protocol to uplink data ===
279	279
	346	+N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
280	280
281		-* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
282		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
283		-* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
284		-* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
285		-* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
286		-* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
287		-* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
	348	+* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
	349	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
	350	+* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
	351	+* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
	352	+* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
	353	+* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
	354	+* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
288	288
289		-[[image:1657249978444-674.png]]
	356	+[[image:1657352634421-276.png]]
290	290
291	291
292		-[[image:1657330723006-866.png]]
	359	+[[image:1657352645687-385.png]]
293	293
294	294
295	295	(((
296		-MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
	363	+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.
297	297	)))
298	298
299	299
	367	+(((
	368	+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.
	369	+)))
300	300
301		-=== 2.2.7 Use TCP protocol to uplink data ===
302	302
	372	+=== 2.2.8  Use TCP protocol to uplink data ===
303	303
	374	+
	375	+This feature is supported since firmware version v110
	376	+
304	304	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
305	305	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
306	306
307		-[[image:image-20220709093918-1.png]]
	380	+[[image:1657352898400-901.png]]
308	308
309	309
310		-[[image:image-20220709093918-2.png]]
	383	+[[image:1657352914475-252.png]]
311	311
312	312
	386	+=== 2.2.9  Change Update Interval ===
313	313
314		-=== 2.2.8 Change Update Interval ===
315	315
316	316	User can use below command to change the (% style="color:green" %)**uplink interval**.
317	317
...	...	@@ -318,162 +318,243 @@
318	318	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
319	319
320	320	(((
321		-(% style="color:red" %)**NOTE:**
	394	+
322	322	)))
323	323
324	324	(((
325		-(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
	398	+(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
326	326	)))
327	327
	401	+(((
	402	+(% 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).**
	403	+)))
328	328
329	329
330	330	== 2.3  Uplink Payload ==
331	331
332		-In this mode, uplink payload includes in total 14 bytes
333	333
	409	+(((
	410	+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.
	411	+)))
334	334
335		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
336		-|=(% style="width: 60px;" %)(((
337		-**Size(bytes)**
338		-)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
339		-|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
340	340
341	341	(((
342		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
	415	+For example:
343	343	)))
344	344
	418	+(((
	419	+ (% 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.
	420	+)))
345	345
346		-[[image:1657331036973-987.png]]
347	347
348	348	(((
349		-The payload is ASCII string, representative same HEX:
	424	+The uplink payloads are composed in  ASCII String. For example:
350	350	)))
351	351
352	352	(((
353		-0x72403155615900640c6c19029200 where:
	428	+0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
354	354	)))
355	355
356		-* (((
357		-Device ID: 0x724031556159 = 724031556159
	431	+(((
	432	+0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
358	358	)))
359		-* (((
360		-Version: 0x0064=100=1.0.0
	434	+
	435	+
	436	+(((
	437	+(% style="color:red" %)**NOTE:**
361	361	)))
362	362
363		-* (((
364		-BAT: 0x0c6c = 3180 mV = 3.180V
	440	+(% style="color:red" %)
	441	+1. (((
	442	+**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
365	365	)))
366		-* (((
367		-Signal: 0x19 = 25
368		-)))
369		-* (((
370		-Distance: 0x0292= 658 mm
371		-)))
372		-* (((
373		-Interrupt: 0x00 = 0
	444	+1. (((
	445	+**By default, the device will send an uplink message every 1 hour.**
374	374
375	375
376		-
377	377
378	378	)))
379	379
380		-== 2.4  Payload Explanation and Sensor Interface ==
	451	+=== 2.3.1  Payload Analyze ===
381	381
	453	+==== 2.3.1.1  Before Firmware v1.2 ====
382	382
383		-=== 2.4.1  Device ID ===
384	384
	456	+N95S31B uplink payload includes in total 21 bytes
	457	+
	458	+
	459	+(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
	460	+|=(% style="width: 50px;" %)**Size(bytes)**|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 65px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**2**
	461	+|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:162px" %)(((
385	385	(((
386		-By default, the Device ID equal to the last 6 bytes of IMEI.
	463	+Reserve/ Same as NBSN95 CFGMOD=1
387	387	)))
388	388
389	389	(((
390		-User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	467	+No function here.
391	391	)))
	469	+)))|(% style="width:102px" %)(((
	470	+(((
	471	+[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
	472	+)))
392	392
393	393	(((
394		-**Example:**
	475	+By SHT31
395	395	)))
	477	+)))|(% style="width:81px" %)(((
	478	+(((
	479	+[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
	480	+)))
396	396
397	397	(((
398		-AT+DEUI=A84041F15612
	483	+By SHT31
399	399	)))
	485	+)))
400	400
401	401	(((
402		-The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	488	+
	489	+
	490	+(((
	491	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
403	403	)))
	493	+)))
404	404
405	405
	496	+[[image:1657354294009-643.png]]
406	406
407		-=== 2.4.2  Version Info ===
408	408
409		-(((
410		-Specify the software version: 0x64=100, means firmware version 1.00.
411		-)))
	499	+The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
412	412
413		-(((
414		-For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
415		-)))
	501	+**where:**
416	416
	503	+* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
417	417
	505	+* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
418	418
419		-=== 2.4.3  Battery Info ===
	507	+* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
420	420
421		-(((
422		-Ex1: 0x0B45 = 2885mV
423		-)))
	509	+* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
424	424
425		-(((
426		-Ex2: 0x0B49 = 2889mV
427		-)))
	511	+* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
428	428
	513	+* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
429	429
	515	+* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
430	430
431		-=== 2.4.4  Signal Strength ===
	517	+* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
432	432
433	433	(((
434		-NB-IoT Network signal Strength.
435		-)))
	520	+
436	436
437		-(((
438		-**Ex1: 0x1d = 29**
	522	+
439	439	)))
440	440
	525	+==== 2.3.1.2 Since Firmware v1.2 ====
	526	+
	527	+
	528	+In this mode, uplink payload includes 91 bytes in total by default.
	529	+
	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	+
	533	+(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
	534	+|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:30px" %)**1**|(% style="width:20px" %)**1**|(% style="width:55px" %)**2**|(% style="width:35px" %)**1**|(% style="width:20px" %)**2**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:30px" %)**4**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:35px" %)**4**
	535	+|=(% 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 .....
	536	+
	537	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
	538	+
	539	+
	540	+[[image:image-20220908154949-1.png]]
	541	+
	542	+
	543	+The payload is ASCII string, representative same HEX:
	544	+
	545	+**0x (% style="color:red" %)__f868411056758782__ (% style="color:blue" %)__000c__ (% style="color:green" %)__0d0f__ (% style="color:#00b0f0" %)__0c__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__0000__ (% style="color:#a14d07" %)__00__ __0030__ (% style="color:#0020b0" %)__0114__ (% style="color:#420042" %)__0231__ (% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__// //__0112023763199baa__ __0112023263199af6__// //__0111023b631999a7__ **
	546	+
	547	+**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
	548	+
	549	+**where:**
	550	+
	551	+* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
	552	+
	553	+* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
	554	+
	555	+* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
	556	+
	557	+* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
	558	+
	559	+* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
	560	+
	561	+* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
	562	+
	563	+* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
	564	+
	565	+* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
	566	+
	567	+* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
	568	+
	569	+* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
	570	+
	571	+* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	572	+
	573	+* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
	574	+
	575	+* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
	576	+
	577	+
	578	+=== 2.3.2  Device ID ===
	579	+
	580	+
441	441	(((
442		-(% style="color:blue" %)**0**(%%)  -113dBm or less
	582	+By default, the Device ID equal to the last 6 bytes of IMEI.
443	443	)))
444	444
445	445	(((
446		-(% style="color:blue" %)**1**(%%)  -111dBm
	586	+User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	587	+
	588	+
447	447	)))
448	448
449	449	(((
450		-(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
	592	+(% style="color:blue" %)**Example:**
451	451	)))
452	452
453	453	(((
454		-(% style="color:blue" %)**31**  (%%) -51dBm or greater
	596	+AT+DEUI=A84041F15612
455	455	)))
456	456
457	457	(((
458		-(% style="color:blue" %)**99**   (%%) Not known or not detectable
	600	+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.
	601	+
	602	+
459	459	)))
460	460
	605	+(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
461	461
462	462
463		-=== 2.4.5  Distance ===
	608	+By default, the Device ID equal to the last 15 bits of IMEI.
464	464
465		-Get the distance. Flat object range 280mm - 7500mm.
	610	+User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
466	466
467		-For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
468	468
	613	+(% style="color:blue" %)**Example:**
	614	+
	615	+AT+DEUI=868411056754138
	616	+
	617	+
	618	+=== 2.3.3  Version Info ===
	619	+
	620	+
469	469	(((
	622	+These bytes include the hardware and software version.
	623	+)))
	624	+
470	470	(((
471		-(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
	626	+Higher byte: Specify hardware version: always 0x00 for N95S31B
472	472	)))
473		-)))
474	474
475	475	(((
476		-
	630	+Lower byte: Specify the software version: 0x6E=110, means firmware version 110
477	477	)))
478	478
479	479	(((
...	...	@@ -480,65 +480,81 @@
480	480
481	481	)))
482	482
483		-=== 2.4.6  Digital Interrupt ===
484		-
485	485	(((
486		-Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
	638	+For example: 0x00 6E: this device is N95S31B with firmware version 110.
487	487	)))
488	488
489	489	(((
490		-The command is:
	642	+
491	491	)))
492	492
	645	+=== 2.3.4  Battery Info ===
	646	+
	647	+
493	493	(((
494		-(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
	649	+Ex1: 0x0B45 = 2885mV
495	495	)))
496	496
497		-
498	498	(((
499		-The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
	653	+Ex2: 0x0B49 = 2889mV
500	500	)))
501	501
502	502
	657	+=== 2.3.5  Signal Strength ===
	658	+
	659	+
503	503	(((
504		-Example:
	661	+NB-IoT Network signal Strength.
505	505	)))
506	506
507	507	(((
508		-0x(00): Normal uplink packet.
	665	+**Ex1: 0x1d = 29**
509	509	)))
510	510
511	511	(((
512		-0x(01): Interrupt Uplink Packet.
	669	+(% style="color:blue" %)**0**(%%)  -113dBm or less
513	513	)))
514	514
515		-
516		-
517		-=== 2.4.7  ​+5V Output ===
518		-
519	519	(((
520		-NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
	673	+(% style="color:blue" %)**1**(%%)  -111dBm
521	521	)))
522	522
523		-
524	524	(((
525		-The 5V output time can be controlled by AT Command.
	677	+(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
526	526	)))
527	527
528	528	(((
529		-(% style="color:blue" %)**AT+5VT=1000**
	681	+(% style="color:blue" %)**31**  (%%) -51dBm or greater
530	530	)))
531	531
532	532	(((
533		-Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
	685	+(% style="color:blue" %)**99**   (%%) Not known or not detectable
534	534	)))
535	535
536	536
	689	+=== 2.3.6  Temperature & Humidity ===
537	537
538		-== 2.5  Downlink Payload ==
539	539
540		-By default, NDDS75 prints the downlink payload to console port.
	692	+The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
541	541
	694	+[[image:image-20220709161741-3.png]]
	695	+
	696	+
	697	+Convert the read byte to decimal and divide it by ten.
	698	+
	699	+
	700	+**Example:**
	701	+
	702	+Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
	703	+
	704	+Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
	705	+
	706	+
	707	+== 2.4  Downlink Payload ==
	708	+
	709	+
	710	+By default, N95S31B prints the downlink payload to console port.
	711	+
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
	748	+If payload = 0x04FF, it will reset the N95S31B
579	579	)))
580	580
581	581
...	...	@@ -586,140 +586,97 @@
586	586	)))
587	587
588	588
	759	+== 2.5  Humidity and Temperature alarm function ==
589	589
590		-== 2.6  ​LED Indicator ==
591	591
	762	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
592	592
593		-The NDDS75 has an internal LED which is to show the status of different state.
594	594
	765	+(% style="color:#037691" %)**AT+ SHHUM=min,max**
595	595
596		-* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
597		-* Then the LED will be on for 1 second means device is boot normally.
598		-* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
599		-* For each uplink probe, LED will be on for 500ms.
600	600
601		-(((
602		-
603		-)))
	768	+² When min=0, and max≠0, Alarm higher than max
604	604
	770	+² When min≠0, and max=0, Alarm lower than min
605	605
	772	+² When min≠0 and max≠0, Alarm higher than max or lower than min
606	606
607		-== 2.7  ​Firmware Change Log ==
608	608
	775	+ (% style="color:blue" %)**Example:**
609	609
610		-Download URL & Firmware Change log
	777	+AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
611	611
612		-(((
613		-[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
614		-)))
615	615
	780	+(% style="color:#037691" %)**AT+ SHTEMP=min,max**
616	616
617		-Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
	782	+² When min=0, and max≠0, Alarm higher than max
618	618
	784	+² When min≠0, and max=0, Alarm lower than min
619	619
	786	+² When min≠0 and max≠0, Alarm higher than max or lower than min
620	620
621		-== 2.8  ​Battery Analysis ==
622	622
623		-=== 2.8.1  ​Battery Type ===
	789	+**~ (% style="color:blue" %)Example:(%%)**
624	624
	791	+AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
625	625
626		-(((
627		-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.
628		-)))
629	629
630		-(((
631		-The battery is designed to last for several years depends on the actually use environment and update interval.
632		-)))
	794	+== 2.6 Set the number of data to be uploaded and the recording time ==
633	633
634		-(((
635		-The battery related documents as below:
636		-)))
637	637
638		-* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
639		-* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
640		-* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	797	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
641	641
642		-(((
643		-[[image:image-20220709101450-2.png]]
644		-)))
	799	+* (% 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)
	800	+* (% 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.
645	645
	802	+ The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
646	646
	804	+[[image:image-20221009001045-1.png||height="726" width="1009"]]
647	647
648		-=== 2.8.2  Power consumption Analyze ===
649	649
650		-(((
651		-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.
652		-)))
	807	+== 2.7 Read or Clear cached data ==
653	653
654	654
655		-(((
656		-Instruction to use as below:
657		-)))
	810	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
658	658
659		-(((
660		-(% 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/]]
661		-)))
	812	+* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
	813	+* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
662	662
	815	+[[image:image-20220908163102-2.png]]
663	663
664		-(((
665		-(% style="color:blue" %)**Step 2: **(%%) Open it and choose
666		-)))
667	667
668		-* (((
669		-Product Model
670		-)))
671		-* (((
672		-Uplink Interval
673		-)))
674		-* (((
675		-Working Mode
676		-)))
	818	+== 2.8 Battery & Power Consumption ==
677	677
678		-(((
679		-And the Life expectation in difference case will be shown on the right.
680		-)))
681	681
682		-[[image:image-20220709110451-3.png]]
	821	+N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
683	683
	823	+[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
684	684
685	685
686		-=== 2.8.3  ​Battery Note ===
	826	+= 3. ​ Access NB-IoT Module =
687	687
688		-(((
689		-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.
690		-)))
691	691
692		-
693		-
694		-=== 2.8.4  Replace the battery ===
695		-
696	696	(((
697		-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).
698		-)))
699		-
700		-
701		-
702		-= 3. ​ Access NB-IoT Module =
703		-
704		-(((
705	705	Users can directly access the AT command set of the NB-IoT module.
706	706	)))
707	707
708	708	(((
709	709	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/]]
	835	+
	836	+
710	710	)))
711	711
712	712	[[image:1657333200519-600.png]]
713	713
714	714
715		-
716	716	= 4.  Using the AT Commands =
717	717
718	718	== 4.1  Access AT Commands ==
719	719
720		-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/]]
721	721
	847	+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]]
722	722
	849	+
723	723	AT+<CMD>?  : Help on <CMD>
724	724
725	725	AT+<CMD>         : Run <CMD>
...	...	@@ -759,7 +759,24 @@
759	759
760	760	AT+SERVADDR  : Server Address
761	761
	889	+AT+TR      : Get or Set record time
762	762
	891	+AT+APN     : Get or set the APN
	892	+
	893	+AT+FBAND   : Get or Set whether to automatically modify the frequency band
	894	+
	895	+AT+DNSCFG  : Get or Set DNS Server
	896	+
	897	+AT+GETSENSORVALUE   : Returns the current sensor measurement
	898	+
	899	+AT+NOUD      : Get or Set the number of data to be uploaded
	900	+
	901	+AT+CDP     : Read or Clear cached data
	902	+
	903	+AT+SHTEMP: Get or Set alarm of temp
	904	+
	905	+AT+SHHUM: Get or Set alarm of moisture
	906	+
763	763	(% style="color:#037691" %)**COAP Management**
764	764
765	765	AT+URI            : Resource parameters
...	...	@@ -790,7 +790,6 @@
790	790	AT+PWORD  : Serial Access Password
791	791
792	792
793		-
794	794	= ​5.  FAQ =
795	795
796	796	== 5.1 ​ How to Upgrade Firmware ==
...	...	@@ -805,11 +805,14 @@
805	805	)))
806	806
807	807	(((
808		-(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
	951	+firmware：[[Dropbox - Firmware - 简化您的生活>>url:https://www.dropbox.com/sh/ap9k142hfnlh5w6/AACJeN_St0ryUl3AggrNB5x0a/N95S31B/Firmware?dl=0&subfolder_nav_tracking=1]]
	952	+
	953	+(((
	954	+(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
809	809	)))
	956	+)))
810	810
811	811
812		-
813	813	= 6.  Trouble Shooting =
814	814
815	815	== 6.1  ​Connection problem when uploading firmware ==
...	...	@@ -824,9 +824,9 @@
824	824
825	825	)))
826	826
827		-
828	828	== 6.2  AT Command input doesn't work ==
829	829
	975	+
830	830	(((
831	831	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.
832	832
...	...	@@ -833,18 +833,12 @@
833	833
834	834	)))
835	835
836		-
837	837	= 7. ​ Order Info =
838	838
839	839
840		-Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
	985	+Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
841	841
842	842
843		-(% class="wikigeneratedid" %)
844		-(((
845		-
846		-)))
847		-
848	848	= 8.  Packing Info =
849	849
850	850	(((
...	...	@@ -852,7 +852,7 @@
852	852
853	853	(% style="color:#037691" %)**Package Includes**:
854	854
855		-* NSE01 NB-IoT Distance Detect Sensor Node x 1
	995	+* N95S31B NB-IoT Temperature and Humidity Sensor
856	856	* External antenna x 1
857	857	)))
858	858
...	...	@@ -861,21 +861,22 @@
861	861
862	862	(% style="color:#037691" %)**Dimension and weight**:
863	863
864		-
865	865	* Device Size: 13.0 x 5 x 4.5 cm
866	866	* Device Weight: 150g
867		-* Package Size / pcs : 15 x 12x 5.5 cm
868		-* Weight / pcs : 220g
	1006	+* Package Size / pcs : 14.0 x 8x 5 cm
	1007	+* Weight / pcs : 180g
869	869	)))
870	870
871	871	(((
872	872
873	873
874		-
875	875
876	876	)))
877	877
878	878	= 9.  Support =
879	879
	1018	+
880	880	* 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.
881	881	* 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]]
	1021	+
	1022	+

1657348034241-728.png

Author

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

Size

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

Content

1657348284168-431.png

Author

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

Size

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

Content

1657350248151-650.png

Author

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

Size

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

Content

1657350625843-586.png

Author

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

Size

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

Content

1657351240556-536.png

Author

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

Size

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

Content

1657351312545-300.png

Author

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

Size

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

Content

1657352146020-183.png

Author

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

Size

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

Content

1657352185396-303.png

Author

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

Size

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

Content

1657352391268-297.png

Author

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

Size

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

Content

1657352403317-397.png

Author

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

Size

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

Content

1657352634421-276.png

Author

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

Size

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

Content

1657352645687-385.png

Author

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

Size

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

Content

1657352898400-901.png

Author

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

Size

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

Content

1657352914475-252.png

Author

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

Size

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

Content

1657354294009-643.png

Author

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

Size

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

Content

1657520100595-569.png

Author

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

Size

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

Content

image-20220709144723-1.png

Author

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

Size

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

Content

image-20220709150546-2.png

Author

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

Size

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

Content

image-20220709161741-3.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+111.2 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