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

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 15 added, 0 removed)
  • 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-20220709161741-3.png
  • image-20220908154949-1.png
  • image-20220908163102-2.png
  • image-20221009001045-1.png

Details

Page properties

Content

...	...	@@ -9,6 +9,7 @@
9	9
10	10	**Table of Contents:**
11	11
	12	+{{toc/}}
12	12
13	13
14	14
...	...	@@ -21,16 +21,29 @@
21	21	(((
22	22
23	23
	25	+(((
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*.
	27	+)))
25	25
	29	+(((
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.
	31	+)))
27	27
	33	+(((
28	28	N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
	35	+)))
29	29
	37	+(((
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).
	39	+)))
31	31
	41	+(((
	42	+
	43	+)))
32	32
	45	+(((
33	33	~* make sure you have NB-IoT coverage locally.
	47	+)))
34	34
35	35
36	36	)))
...	...	@@ -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
...	...	@@ -85,6 +85,7 @@
85	85
86	86	== ​1.4  Applications ==
87	87
	101	+
88	88	* Smart Buildings & Home Automation
89	89	* Logistics and Supply Chain Management
90	90	* Smart Metering
...	...	@@ -96,43 +96,49 @@
96	96	​
97	97
98	98
99		-== 1.5  Pin Definitions ==
	113	+== 1.5  Pin Definitions & Switch ==
100	100
	115	+
101	101	N95S31B use the mother board from NBSN95 which as below.
102	102
	118	+
103	103	[[image:image-20220709144723-1.png]]
104	104
105	105
106	106	=== 1.5.1 Jumper JP2 ===
107	107
	124	+
108	108	Power on Device when put this jumper.
109	109
110	110
111		-
112	112	=== 1.5.2 BOOT MODE / SW1 ===
113	113
114		-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.
115	115
116		-2) Flash: work mode, device starts to work and send out console output for further debug
	131	+(((
	132	+**1) ISP: ** upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
	133	+)))
117	117
	135	+(((
	136	+**2) Flash:**  work mode, device starts to work and send out console output for further debug
	137	+)))
118	118
119	119
120	120	=== 1.5.3 Reset Button ===
121	121
	142	+
122	122	Press to reboot the device.
123	123
124	124
125		-
126	126	=== 1.5.4 LED ===
127	127
	148	+
128	128	It will flash:
129	129
130		-1. When boot the device in flash mode
131		-1. Send an uplink packet
	151	+1.  When boot the device in flash mode
132	132
	153	+2.  Send an uplink packet
133	133
134	134
135		-
136	136	= 2.  Use N95S31B to communicate with IoT Server =
137	137
138	138	== 2.1  How it works ==
...	...	@@ -151,7 +151,7 @@
151	151
152	152	)))
153	153
154		-[[image:1657350248151-650.png]]
	174	+[[image:1657520100595-569.png]]
155	155
156	156	(((
157	157
...	...	@@ -160,7 +160,6 @@
160	160
161	161	== 2.2 ​ Configure the N95S31B ==
162	162
163		-
164	164	=== 2.2.1  Power On N95S31B ===
165	165
166	166
...	...	@@ -167,27 +167,48 @@
167	167	[[image:image-20220709150546-2.png]]
168	168
169	169
170		-=== 2.2.1 Test Requirement ===
	189	+=== 2.2.2 Test Requirement ===
171	171
172	172
	192	+(((
173	173	To use N95S31B in your city, make sure meet below requirements:
	194	+)))
174	174
175		-* Your local operator has already distributed a NB-IoT Network there.
176		-* The local NB-IoT network used the band that N95S31B supports.
177		-* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	196	+* (((
	197	+Your local operator has already distributed a NB-IoT Network there.
	198	+)))
	199	+* (((
	200	+The local NB-IoT network used the band that N95S31B supports.
	201	+)))
	202	+* (((
	203	+Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	204	+)))
178	178
179		-
	206	+(((
180	180	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
	208	+)))
181	181
	210	+(((
182	182	N95S31B supports different communication protocol such as :
	212	+)))
183	183
184	184	(((
185		-* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
186		-* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
187		-* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
188		-* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	215	+* (((
	216	+CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
	217	+)))
	218	+* (((
	219	+raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
	220	+)))
	221	+* (((
	222	+MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
	223	+)))
	224	+* (((
	225	+TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	226	+)))
189	189
	228	+(((
190	190	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.
	230	+)))
191	191
192	192
193	193	)))
...	...	@@ -195,9 +195,9 @@
195	195	[[image:1657350625843-586.png]]
196	196
197	197
198		-
199	199	=== 2.2.3  Insert SIM card ===
200	200
	240	+
201	201	(((
202	202	Insert the NB-IoT Card get from your provider.
203	203	)))
...	...	@@ -210,26 +210,29 @@
210	210	[[image:1657351240556-536.png]]
211	211
212	212
	253	+=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
213	213
214		-=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
215	215
216	216	(((
217	217	(((
218		-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.
	258	+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.
	259	+
	260	+
219	219	)))
220	220	)))
221	221
222		-[[image:image-20220709092052-2.png]]
	264	+[[image:1657351312545-300.png]]
223	223
224		-**Connection:**
225	225
226		- (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
	267	+(% style="color:blue" %)**Connection:**
227	227
228		- (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
	269	+ (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
229	229
230		- (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
	271	+**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
231	231
	273	+**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
232	232
	275	+
233	233	In the PC, use below serial tool settings:
234	234
235	235	* Baud:  (% style="color:green" %)**9600**
...	...	@@ -239,20 +239,21 @@
239	239	* Flow Control: (% style="color:green" %)**None**
240	240
241	241	(((
242		-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.
	285	+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.
243	243	)))
244	244
245	245	[[image:1657329814315-101.png]]
246	246
	290	+
247	247	(((
248		-(% 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/]]
	292	+(% 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]]**
249	249	)))
250	250
251	251
	296	+=== 2.2.5  Use CoAP protocol to uplink data ===
252	252
253		-=== 2.2.4 Use CoAP protocol to uplink data ===
254	254
255		-(% 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/]]
	299	+(% 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/]]**
256	256
257	257
258	258	(((
...	...	@@ -263,17 +263,19 @@
263	263	(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
264	264	)))
265	265	* (((
266		-(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
	310	+(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
267	267	)))
268	268	* (((
269		-(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
	313	+(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
270	270	)))
271	271
272	272	(((
	317	+
	318	+
273	273	For parameter description, please refer to AT command set
274	274	)))
275	275
276		-[[image:1657330452568-615.png]]
	322	+[[image:1657352146020-183.png]]
277	277
278	278
279	279	(((
...	...	@@ -280,61 +280,67 @@
280	280	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.
281	281	)))
282	282
283		-[[image:1657330472797-498.png]]
	329	+[[image:1657352185396-303.png]]
284	284
285	285
	332	+=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
286	286
287		-=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
288	288
289		-
290	290	* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
291	291	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
292	292	* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
293	293
294		-[[image:1657330501006-241.png]]
	339	+[[image:1657352391268-297.png]]
295	295
296	296
297		-[[image:1657330533775-472.png]]
	342	+[[image:1657352403317-397.png]]
298	298
299	299
	345	+=== 2.2.7  Use MQTT protocol to uplink data ===
300	300
301		-=== 2.2.6 Use MQTT protocol to uplink data ===
302	302
	348	+N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
303	303
304		-* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
305		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
306		-* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
307		-* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
308		-* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
309		-* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
310		-* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
	350	+* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
	351	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
	352	+* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
	353	+* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
	354	+* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
	355	+* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
	356	+* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
311	311
312		-[[image:1657249978444-674.png]]
	358	+[[image:1657352634421-276.png]]
313	313
314	314
315		-[[image:1657330723006-866.png]]
	361	+[[image:1657352645687-385.png]]
316	316
317	317
318	318	(((
319		-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.
	365	+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	)))
321	321
322	322
	369	+(((
	370	+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.
	371	+)))
323	323
324		-=== 2.2.7 Use TCP protocol to uplink data ===
325	325
	374	+=== 2.2.8  Use TCP protocol to uplink data ===
326	326
	376	+
	377	+This feature is supported since firmware version v110
	378	+
327	327	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
328	328	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
329	329
330		-[[image:image-20220709093918-1.png]]
	382	+[[image:1657352898400-901.png]]
331	331
332	332
333		-[[image:image-20220709093918-2.png]]
	385	+[[image:1657352914475-252.png]]
334	334
335	335
	388	+=== 2.2.9  Change Update Interval ===
336	336
337		-=== 2.2.8 Change Update Interval ===
338	338
339	339	User can use below command to change the (% style="color:green" %)**uplink interval**.
340	340
...	...	@@ -341,164 +341,245 @@
341	341	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
342	342
343	343	(((
344		-(% style="color:red" %)**NOTE:**
	396	+
345	345	)))
346	346
347	347	(((
348		-(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
	400	+(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
349	349	)))
350	350
	403	+(((
	404	+(% 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).**
	405	+)))
351	351
352	352
353	353	== 2.3  Uplink Payload ==
354	354
355		-In this mode, uplink payload includes in total 14 bytes
356	356
	411	+(((
	412	+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.
	413	+)))
357	357
358		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
359		-|=(% style="width: 60px;" %)(((
360		-**Size(bytes)**
361		-)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
362		-|(% 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"]]
363	363
364	364	(((
365		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
	417	+For example:
366	366	)))
367	367
	420	+(((
	421	+ (% 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.
	422	+)))
368	368
369		-[[image:1657331036973-987.png]]
370	370
371	371	(((
372		-The payload is ASCII string, representative same HEX:
	426	+The uplink payloads are composed in  ASCII String. For example:
373	373	)))
374	374
375	375	(((
376		-0x72403155615900640c6c19029200 where:
	430	+0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
377	377	)))
378	378
379		-* (((
380		-Device ID: 0x724031556159 = 724031556159
	433	+(((
	434	+0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
381	381	)))
382		-* (((
383		-Version: 0x0064=100=1.0.0
	436	+
	437	+
	438	+(((
	439	+(% style="color:red" %)**NOTE:**
384	384	)))
385	385
386		-* (((
387		-BAT: 0x0c6c = 3180 mV = 3.180V
	442	+(% style="color:red" %)
	443	+1. (((
	444	+**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
388	388	)))
389		-* (((
390		-Signal: 0x19 = 25
391		-)))
392		-* (((
393		-Distance: 0x0292= 658 mm
394		-)))
395		-* (((
396		-Interrupt: 0x00 = 0
	446	+1. (((
	447	+**By default, the device will send an uplink message every 1 hour.**
397	397
398	398
399		-
400	400
401	401	)))
402	402
403		-== 2.4  Payload Explanation and Sensor Interface ==
	453	+=== 2.3.1  Payload Analyze ===
404	404
	455	+==== 2.3.1.1  Before Firmware v1.2 ====
405	405
406		-=== 2.4.1  Device ID ===
407	407
	458	+N95S31B uplink payload includes in total 21 bytes
	459	+
	460	+
	461	+(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
	462	+|=(% 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**
	463	+|(% 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" %)(((
408	408	(((
409		-By default, the Device ID equal to the last 6 bytes of IMEI.
	465	+Reserve/ Same as NBSN95 CFGMOD=1
410	410	)))
411	411
412	412	(((
413		-User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	469	+No function here.
414	414	)))
	471	+)))|(% style="width:102px" %)(((
	472	+(((
	473	+[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
	474	+)))
415	415
416	416	(((
417		-**Example:**
	477	+By SHT31
418	418	)))
	479	+)))|(% style="width:81px" %)(((
	480	+(((
	481	+[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
	482	+)))
419	419
420	420	(((
421		-AT+DEUI=A84041F15612
	485	+By SHT31
422	422	)))
	487	+)))
423	423
424	424	(((
425		-The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	490	+
	491	+
	492	+(((
	493	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
426	426	)))
	495	+)))
427	427
428	428
	498	+[[image:1657354294009-643.png]]
429	429
430		-=== 2.4.2  Version Info ===
431	431
432		-(((
433		-Specify the software version: 0x64=100, means firmware version 1.00.
434		-)))
	501	+The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
435	435
436		-(((
437		-For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
438		-)))
	503	+**where:**
439	439
	505	+* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
440	440
	507	+* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
441	441
442		-=== 2.4.3  Battery Info ===
	509	+* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
443	443
444		-(((
445		-Ex1: 0x0B45 = 2885mV
446		-)))
	511	+* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
447	447
448		-(((
449		-Ex2: 0x0B49 = 2889mV
450		-)))
	513	+* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
451	451
	515	+* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
452	452
	517	+* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
453	453
454		-=== 2.4.4  Signal Strength ===
	519	+* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
455	455
456	456	(((
457		-NB-IoT Network signal Strength.
458		-)))
	522	+
459	459
460		-(((
461		-**Ex1: 0x1d = 29**
	524	+
	525	+
462	462	)))
463	463
	528	+==== 2.3.1.2 Since Firmware v1.2 ====
	529	+
	530	+
	531	+In this mode, uplink payload includes 91 bytes in total by default.
	532	+
	533	+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.
	534	+
	535	+
	536	+(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
	537	+|=(% 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**
	538	+|=(% 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 .....
	539	+
	540	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
	541	+
	542	+
	543	+[[image:image-20220908154949-1.png]]
	544	+
	545	+
	546	+The payload is ASCII string, representative same HEX:
	547	+
	548	+**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__ **
	549	+
	550	+**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
	551	+
	552	+**where:**
	553	+
	554	+* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
	555	+
	556	+* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
	557	+
	558	+* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
	559	+
	560	+* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
	561	+
	562	+* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
	563	+
	564	+* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
	565	+
	566	+* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
	567	+
	568	+* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
	569	+
	570	+* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
	571	+
	572	+* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
	573	+
	574	+* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	575	+
	576	+* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
	577	+
	578	+* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
	579	+
	580	+
	581	+
	582	+=== 2.3.2  Device ID ===
	583	+
	584	+
464	464	(((
465		-(% style="color:blue" %)**0**(%%)  -113dBm or less
	586	+By default, the Device ID equal to the last 6 bytes of IMEI.
466	466	)))
467	467
468	468	(((
469		-(% style="color:blue" %)**1**(%%)  -111dBm
	590	+User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	591	+
	592	+
470	470	)))
471	471
472	472	(((
473		-(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
	596	+(% style="color:blue" %)**Example:**
474	474	)))
475	475
476	476	(((
477		-(% style="color:blue" %)**31**  (%%) -51dBm or greater
	600	+AT+DEUI=A84041F15612
478	478	)))
479	479
480	480	(((
481		-(% style="color:blue" %)**99**   (%%) Not known or not detectable
	604	+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.
	605	+
	606	+
482	482	)))
483	483
	609	+(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
484	484
485	485
486		-=== 2.4.5  Distance ===
	612	+By default, the Device ID equal to the last 15 bits of IMEI.
487	487
488		-Get the distance. Flat object range 280mm - 7500mm.
	614	+User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
489	489
	616	+
	617	+(% style="color:blue" %)**Example:**
	618	+
	619	+AT+DEUI=868411056754138
	620	+
	621	+
	622	+=== 2.3.3  Version Info ===
	623	+
	624	+
490	490	(((
491		-For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
	626	+These bytes include the hardware and software version.
492	492	)))
493	493
494	494	(((
495		-(((
496		-(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
	630	+Higher byte: Specify hardware version: always 0x00 for N95S31B
497	497	)))
498		-)))
499	499
500	500	(((
501		-
	634	+Lower byte: Specify the software version: 0x6E=110, means firmware version 110
502	502	)))
503	503
504	504	(((
...	...	@@ -505,65 +505,81 @@
505	505
506	506	)))
507	507
508		-=== 2.4.6  Digital Interrupt ===
509		-
510	510	(((
511		-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.
	642	+For example: 0x00 6E: this device is N95S31B with firmware version 110.
512	512	)))
513	513
514	514	(((
515		-The command is:
	646	+
516	516	)))
517	517
	649	+=== 2.3.4  Battery Info ===
	650	+
	651	+
518	518	(((
519		-(% 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]])**.**
	653	+Ex1: 0x0B45 = 2885mV
520	520	)))
521	521
522		-
523	523	(((
524		-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.
	657	+Ex2: 0x0B49 = 2889mV
525	525	)))
526	526
527	527
	661	+=== 2.3.5  Signal Strength ===
	662	+
	663	+
528	528	(((
529		-Example:
	665	+NB-IoT Network signal Strength.
530	530	)))
531	531
532	532	(((
533		-0x(00): Normal uplink packet.
	669	+**Ex1: 0x1d = 29**
534	534	)))
535	535
536	536	(((
537		-0x(01): Interrupt Uplink Packet.
	673	+(% style="color:blue" %)**0**(%%)  -113dBm or less
538	538	)))
539	539
540		-
541		-
542		-=== 2.4.7  ​+5V Output ===
543		-
544	544	(((
545		-NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
	677	+(% style="color:blue" %)**1**(%%)  -111dBm
546	546	)))
547	547
548		-
549	549	(((
550		-The 5V output time can be controlled by AT Command.
	681	+(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
551	551	)))
552	552
553	553	(((
554		-(% style="color:blue" %)**AT+5VT=1000**
	685	+(% style="color:blue" %)**31**  (%%) -51dBm or greater
555	555	)))
556	556
557	557	(((
558		-Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
	689	+(% style="color:blue" %)**99**   (%%) Not known or not detectable
559	559	)))
560	560
561	561
	693	+=== 2.3.6  Temperature & Humidity ===
562	562
563		-== 2.5  Downlink Payload ==
564	564
565		-By default, NDDS75 prints the downlink payload to console port.
	696	+The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
566	566
	698	+[[image:image-20220709161741-3.png]]
	699	+
	700	+
	701	+Convert the read byte to decimal and divide it by ten.
	702	+
	703	+
	704	+**Example:**
	705	+
	706	+Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
	707	+
	708	+Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
	709	+
	710	+
	711	+== 2.4  Downlink Payload ==
	712	+
	713	+
	714	+By default, N95S31B prints the downlink payload to console port.
	715	+
567	567	[[image:image-20220709100028-1.png]]
568	568
569	569
...	...	@@ -600,7 +600,7 @@
600	600	)))
601	601
602	602	(((
603		-If payload = 0x04FF, it will reset the NDDS75
	752	+If payload = 0x04FF, it will reset the N95S31B
604	604	)))
605	605
606	606
...	...	@@ -611,42 +611,65 @@
611	611	)))
612	612
613	613
	763	+== 2.5  Humidity and Temperature alarm function ==
614	614
615		-== 2.6  ​LED Indicator ==
616	616
	766	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
617	617
618		-The NDDS75 has an internal LED which is to show the status of different state.
619	619
	769	+(% style="color:#037691" %)**AT+ SHHUM=min,max**
620	620
621		-* 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)
622		-* Then the LED will be on for 1 second means device is boot normally.
623		-* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
624		-* For each uplink probe, LED will be on for 500ms.
625	625
626		-(((
627		-
628		-)))
	772	+² When min=0, and max≠0, Alarm higher than max
629	629
	774	+² When min≠0, and max=0, Alarm lower than min
630	630
	776	+² When min≠0 and max≠0, Alarm higher than max or lower than min
631	631
632		-== 2.7  ​Firmware Change Log ==
633	633
	779	+ (% style="color:blue" %)**Example:**
634	634
635		-(((
636		-Download URL & Firmware Change log
637		-)))
	781	+AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
638	638
639		-(((
640		-[[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/]]
641		-)))
642	642
	784	+(% style="color:#037691" %)**AT+ SHTEMP=min,max**
643	643
644		-(((
645		-Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
646		-)))
	786	+² When min=0, and max≠0, Alarm higher than max
647	647
	788	+² When min≠0, and max=0, Alarm lower than min
648	648
	790	+² When min≠0 and max≠0, Alarm higher than max or lower than min
649	649
	792	+
	793	+**~ (% style="color:blue" %)Example:(%%)**
	794	+
	795	+AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
	796	+
	797	+
	798	+== 2.6 Set the number of data to be uploaded and the recording time ==
	799	+
	800	+
	801	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
	802	+
	803	+* (% 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)
	804	+* (% 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.
	805	+
	806	+ The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
	807	+
	808	+[[image:image-20221009001045-1.png||height="726" width="1009"]]
	809	+
	810	+
	811	+== 2.7 Read or Clear cached data ==
	812	+
	813	+
	814	+**~ (% style="color:blue" %)➢ AT Command:(%%)**
	815	+
	816	+* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
	817	+* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
	818	+
	819	+[[image:image-20220908163102-2.png]]
	820	+
	821	+
650	650	== 2.8  ​Battery Analysis ==
651	651
652	652	=== 2.8.1  ​Battery Type ===
...	...	@@ -653,7 +653,7 @@
653	653
654	654
655	655	(((
656		-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.
	828	+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.
657	657	)))
658	658
659	659	(((
...	...	@@ -673,63 +673,41 @@
673	673	)))
674	674
675	675
676		-
677	677	=== 2.8.2  Power consumption Analyze ===
678	678
679		-(((
680		-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.
681		-)))
682	682
683		-
684	684	(((
685		-Instruction to use as below:
	852	+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.
686	686	)))
687	687
688	688	(((
689		-(% 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/]]
	856	+
690	690	)))
691	691
	859	+=== 2.8.3  ​Battery Note ===
692	692
693		-(((
694		-(% style="color:blue" %)**Step 2: **(%%) Open it and choose
695		-)))
696	696
697		-* (((
698		-Product Model
699		-)))
700		-* (((
701		-Uplink Interval
702		-)))
703		-* (((
704		-Working Mode
705		-)))
706		-
707	707	(((
708		-And the Life expectation in difference case will be shown on the right.
	863	+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.
709	709	)))
710	710
711		-[[image:image-20220709110451-3.png]]
712	712
	867	+=== 2.8.4  Replace the battery ===
713	713
714	714
715		-=== 2.8.3  ​Battery Note ===
716		-
717	717	(((
718		-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.
	871	+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.
719	719	)))
720	720
721	721
722		-
723		-=== 2.8.4  Replace the battery ===
724		-
725	725	(((
726		-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).
	876	+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).
727	727	)))
728	728
729	729
730		-
731	731	= 3. ​ Access NB-IoT Module =
732	732
	882	+
733	733	(((
734	734	Users can directly access the AT command set of the NB-IoT module.
735	735	)))
...	...	@@ -736,19 +736,21 @@
736	736
737	737	(((
738	738	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/]]
	889	+
	890	+
739	739	)))
740	740
741	741	[[image:1657333200519-600.png]]
742	742
743	743
744		-
745	745	= 4.  Using the AT Commands =
746	746
747	747	== 4.1  Access AT Commands ==
748	748
749		-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/]]
750	750
	901	+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]]
751	751
	903	+
752	752	AT+<CMD>?  : Help on <CMD>
753	753
754	754	AT+<CMD>         : Run <CMD>
...	...	@@ -788,7 +788,24 @@
788	788
789	789	AT+SERVADDR  : Server Address
790	790
	943	+AT+TR      : Get or Set record time
791	791
	945	+AT+APN     : Get or set the APN
	946	+
	947	+AT+FBAND   : Get or Set whether to automatically modify the frequency band
	948	+
	949	+AT+DNSCFG  : Get or Set DNS Server
	950	+
	951	+AT+GETSENSORVALUE   : Returns the current sensor measurement
	952	+
	953	+AT+NOUD      : Get or Set the number of data to be uploaded
	954	+
	955	+AT+CDP     : Read or Clear cached data
	956	+
	957	+AT+SHTEMP: Get or Set alarm of temp
	958	+
	959	+AT+SHHUM: Get or Set alarm of moisture
	960	+
792	792	(% style="color:#037691" %)**COAP Management**
793	793
794	794	AT+URI            : Resource parameters
...	...	@@ -819,7 +819,6 @@
819	819	AT+PWORD  : Serial Access Password
820	820
821	821
822		-
823	823	= ​5.  FAQ =
824	824
825	825	== 5.1 ​ How to Upgrade Firmware ==
...	...	@@ -834,11 +834,14 @@
834	834	)))
835	835
836	836	(((
837		-(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
	1005	+
	1006	+
	1007	+(((
	1008	+(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
838	838	)))
	1010	+)))
839	839
840	840
841		-
842	842	= 6.  Trouble Shooting =
843	843
844	844	== 6.1  ​Connection problem when uploading firmware ==
...	...	@@ -853,9 +853,9 @@
853	853
854	854	)))
855	855
856		-
857	857	== 6.2  AT Command input doesn't work ==
858	858
	1029	+
859	859	(((
860	860	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.
861	861
...	...	@@ -862,18 +862,12 @@
862	862
863	863	)))
864	864
865		-
866	866	= 7. ​ Order Info =
867	867
868	868
869		-Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
	1039	+Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
870	870
871	871
872		-(% class="wikigeneratedid" %)
873		-(((
874		-
875		-)))
876		-
877	877	= 8.  Packing Info =
878	878
879	879	(((
...	...	@@ -881,7 +881,7 @@
881	881
882	882	(% style="color:#037691" %)**Package Includes**:
883	883
884		-* NSE01 NB-IoT Distance Detect Sensor Node x 1
	1049	+* N95S31B NB-IoT Temperature and Humidity Sensor
885	885	* External antenna x 1
886	886	)))
887	887
...	...	@@ -890,21 +890,25 @@
890	890
891	891	(% style="color:#037691" %)**Dimension and weight**:
892	892
893		-
894	894	* Device Size: 13.0 x 5 x 4.5 cm
895	895	* Device Weight: 150g
896		-* Package Size / pcs : 15 x 12x 5.5 cm
897		-* Weight / pcs : 220g
	1060	+* Package Size / pcs : 14.0 x 8x 5 cm
	1061	+* Weight / pcs : 180g
898	898	)))
899	899
900	900	(((
901	901
902	902
903		-
904	904
905	905	)))
906	906
907	907	= 9.  Support =
908	908
	1072	+
909	909	* 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.
910	910	* 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]]
	1075	+
	1076	+
	1077	+
	1078	+
	1079	+

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-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