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

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 24 added, 0 removed)
  • 1657332990863-496.png
  • 1657333200519-600.png
  • 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-20220709100028-1.png
  • image-20220709101450-2.png
  • image-20220709110451-3.png
  • image-20220709144723-1.png
  • image-20220709150546-2.png
  • image-20220709161741-3.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

Content

...	...	@@ -1,41 +1,56 @@
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		-**Table of Contents:**
9	9
10	10
	10	+**Table of Contents:**
11	11
	12	+{{toc/}}
12	12
13	13
14	14
15	15
	17	+
16	16	= 1.  Introduction =
17	17
18		-== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
19	19
	21	+== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
	22	+
20	20	(((
21	21
22	22
23	23	(((
24		-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.
25		-\\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.
26		-\\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.
27		-\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
28		-\\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)
29		-\\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.
	27	+The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*.
30	30	)))
31	31
	30	+(((
	31	+The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use.
	32	+)))
	33	+
	34	+(((
	35	+N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
	36	+)))
	37	+
	38	+(((
	39	+N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report).
	40	+)))
	41	+
	42	+(((
32	32
33	33	)))
34	34
35		-[[image:1654503236291-817.png]]
	46	+(((
	47	+~* make sure you have NB-IoT coverage locally.
	48	+)))
36	36
	50	+
	51	+)))
37	37
38		-[[image:1657327959271-447.png]]
	53	+[[image:1657348284168-431.png]]
39	39
40	40
41	41
...	...	@@ -43,18 +43,19 @@
43	43
44	44
45	45	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
46		-* Ultra low power consumption
47		-* Distance Detection by Ultrasonic technology
48		-* Flat object range 280mm - 7500mm
49		-* Accuracy: ±(1cm+S*0.3%) (S: Distance)
50		-* Cable Length: 25cm
	61	+* Monitor Temperature & Humidity via SHT31
51	51	* AT Commands to change parameters
52	52	* Uplink on periodically
53	53	* Downlink to change configure
54	54	* IP66 Waterproof Enclosure
	66	+* Ultra-Low Power consumption
	67	+* AT Commands to change parameters
55	55	* Micro SIM card slot for NB-IoT SIM
56	56	* 8500mAh Battery for long term use
57	57
	71	+
	72	+
	73	+
58	58	== 1.3  Specification ==
59	59
60	60
...	...	@@ -63,6 +63,8 @@
63	63	* Supply Voltage: 2.1v ~~ 3.6v
64	64	* Operating Temperature: -40 ~~ 85°C
65	65
	82	+
	83	+
66	66	(% style="color:#037691" %)**NB-IoT Spec:**
67	67
68	68	* - B1 @H-FDD: 2100MHz
...	...	@@ -72,6 +72,8 @@
72	72	* - B20 @H-FDD: 800MHz
73	73	* - B28 @H-FDD: 700MHz
74	74
	93	+
	94	+
75	75	(% style="color:#037691" %)**Battery:**
76	76
77	77	* Li/SOCI2 un-chargeable battery
...	...	@@ -80,14 +80,12 @@
80	80	* Max continuously current: 130mA
81	81	* Max boost current: 2A, 1 second
82	82
83		-(% style="color:#037691" %)**Power Consumption**
84	84
85		-* STOP Mode: 10uA @ 3.3v
86		-* Max transmit power: 350mA@3.3v
87	87
88	88
89	89	== ​1.4  Applications ==
90	90
	108	+
91	91	* Smart Buildings & Home Automation
92	92	* Logistics and Supply Chain Management
93	93	* Smart Metering
...	...	@@ -100,24 +100,67 @@
100	100
101	101
102	102
103		-== 1.5  Pin Definitions ==
	121	+== 1.5  Pin Definitions & Switch ==
104	104
105	105
106		-[[image:1657328609906-564.png]]
	124	+N95S31B use the mother board from NBSN95 which as below.
107	107
108	108
	127	+[[image:image-20220709144723-1.png]]
109	109
110		-= 2.  Use NDDS75 to communicate with IoT Server =
111	111
	130	+
	131	+=== 1.5.1 Jumper JP2 ===
	132	+
	133	+
	134	+Power on Device when put this jumper.
	135	+
	136	+
	137	+
	138	+=== 1.5.2 BOOT MODE / SW1 ===
	139	+
	140	+
	141	+(((
	142	+1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
	143	+)))
	144	+
	145	+(((
	146	+2) Flash: work mode, device starts to work and send out console output for further debug
	147	+)))
	148	+
	149	+
	150	+
	151	+=== 1.5.3 Reset Button ===
	152	+
	153	+
	154	+Press to reboot the device.
	155	+
	156	+
	157	+
	158	+=== 1.5.4 LED ===
	159	+
	160	+
	161	+It will flash:
	162	+
	163	+1. When boot the device in flash mode
	164	+1. Send an uplink packet
	165	+
	166	+
	167	+
	168	+
	169	+= 2.  Use N95S31B to communicate with IoT Server =
	170	+
	171	+
112	112	== 2.1  How it works ==
113	113
	174	+
114	114	(((
115		-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.
	176	+The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by N95S31B.
116	116	)))
117	117
118	118
119	119	(((
120		-The diagram below shows the working flow in default firmware of NDDS75:
	181	+The diagram below shows the working flow in default firmware of N95S31B:
121	121	)))
122	122
123	123	(((
...	...	@@ -124,7 +124,7 @@
124	124
125	125	)))
126	126
127		-[[image:1657328659945-416.png]]
	188	+[[image:1657520100595-569.png]]
128	128
129	129	(((
130	130
...	...	@@ -131,30 +131,69 @@
131	131	)))
132	132
133	133
134		-== 2.2 ​ Configure the NDDS75 ==
	195	+== 2.2 ​ Configure the N95S31B ==
135	135
136	136
	198	+=== 2.2.1  Power On N95S31B ===
	199	+
	200	+
	201	+[[image:image-20220709150546-2.png]]
	202	+
	203	+
	204	+
137	137	=== 2.2.1 Test Requirement ===
138	138
	207	+
139	139	(((
140		-To use NDDS75 in your city, make sure meet below requirements:
	209	+To use N95S31B in your city, make sure meet below requirements:
141	141	)))
142	142
143		-* Your local operator has already distributed a NB-IoT Network there.
144		-* The local NB-IoT network used the band that NSE01 supports.
145		-* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	212	+* (((
	213	+Your local operator has already distributed a NB-IoT Network there.
	214	+)))
	215	+* (((
	216	+The local NB-IoT network used the band that N95S31B supports.
	217	+)))
	218	+* (((
	219	+Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	220	+)))
146	146
147	147	(((
148		-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
	223	+Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
149	149	)))
150	150
	226	+(((
	227	+N95S31B supports different communication protocol such as :
	228	+)))
151	151
152		-[[image:1657328756309-230.png]]
	230	+(((
	231	+* (((
	232	+CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
	233	+)))
	234	+* (((
	235	+raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
	236	+)))
	237	+* (((
	238	+MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
	239	+)))
	240	+* (((
	241	+TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	242	+)))
153	153
	244	+(((
	245	+We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server.
	246	+)))
154	154
	248	+
	249	+)))
155	155
156		-=== 2.2.2 Insert SIM card ===
	251	+[[image:1657350625843-586.png]]
157	157
	253	+
	254	+
	255	+=== 2.2.3  Insert SIM card ===
	256	+
	257	+
158	158	(((
159	159	Insert the NB-IoT Card get from your provider.
160	160	)))
...	...	@@ -164,20 +164,24 @@
164	164	)))
165	165
166	166
167		-[[image:1657328884227-504.png]]
	267	+[[image:1657351240556-536.png]]
168	168
169	169
170	170
171		-=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
	271	+=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
172	172
	273	+
173	173	(((
174	174	(((
175		-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.
	276	+User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below.
	277	+
	278	+
176	176	)))
177	177	)))
178	178
179		-[[image:image-20220709092052-2.png]]
	282	+[[image:1657351312545-300.png]]
180	180
	284	+
181	181	**Connection:**
182	182
183	183	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
...	...	@@ -196,254 +196,287 @@
196	196	* Flow Control: (% style="color:green" %)**None**
197	197
198	198	(((
199		-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.
	303	+Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
200	200	)))
201	201
202	202	[[image:1657329814315-101.png]]
203	203
	308	+
204	204	(((
205		-(% 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/]]
	310	+(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**
206	206	)))
207	207
208	208
209	209
210		-=== 2.2.4 Use CoAP protocol to uplink data ===
	315	+=== 2.2.5  Use CoAP protocol to uplink data ===
211	211
212		-(% 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/]]
213	213
	318	+(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**
214	214
	320	+
	321	+(((
215	215	**Use below commands:**
	323	+)))
216	216
217		-* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
218		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
219		-* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
	325	+* (((
	326	+(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
	327	+)))
	328	+* (((
	329	+(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
	330	+)))
	331	+* (((
	332	+(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
	333	+)))
220	220
	335	+(((
	336	+
	337	+
221	221	For parameter description, please refer to AT command set
	339	+)))
222	222
223		-[[image:1657330452568-615.png]]
	341	+[[image:1657352146020-183.png]]
224	224
225	225
	344	+(((
226	226	After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
	346	+)))
227	227
228		-[[image:1657330472797-498.png]]
	348	+[[image:1657352185396-303.png]]
229	229
230	230
231	231
232		-=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
	352	+=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
233	233
234	234
235		-* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
	355	+* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
236	236	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
237		-* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
	357	+* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
238	238
239		-[[image:1657330501006-241.png]]
240	240
241	241
242		-[[image:1657330533775-472.png]]
	361	+[[image:1657352391268-297.png]]
243	243
244	244
	364	+[[image:1657352403317-397.png]]
245	245
246		-=== 2.2.6 Use MQTT protocol to uplink data ===
247	247
248	248
249		-* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
250		-* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
251		-* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
252		-* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
253		-* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
254		-* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
255		-* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
	368	+=== 2.2.7  Use MQTT protocol to uplink data ===
256	256
257		-[[image:1657249978444-674.png]]
258	258
	371	+N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
259	259
260		-[[image:1657330723006-866.png]]
	373	+* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
	374	+* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
	375	+* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
	376	+* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
	377	+* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
	378	+* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
	379	+* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
261	261
262	262
	382	+
	383	+[[image:1657352634421-276.png]]
	384	+
	385	+
	386	+[[image:1657352645687-385.png]]
	387	+
	388	+
263	263	(((
264		-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.
	390	+To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period.
265	265	)))
266	266
267	267
	394	+(((
	395	+MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
	396	+)))
268	268
269		-=== 2.2.7 Use TCP protocol to uplink data ===
270	270
271	271
	400	+=== 2.2.8  Use TCP protocol to uplink data ===
	401	+
	402	+
	403	+This feature is supported since firmware version v110
	404	+
272	272	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
273	273	* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
274	274
275		-[[image:image-20220709093918-1.png]]
276	276
277	277
278		-[[image:image-20220709093918-2.png]]
	410	+[[image:1657352898400-901.png]]
279	279
280	280
	413	+[[image:1657352914475-252.png]]
281	281
282		-=== 2.2.8 Change Update Interval ===
283	283
	416	+
	417	+=== 2.2.9  Change Update Interval ===
	418	+
	419	+
284	284	User can use below command to change the (% style="color:green" %)**uplink interval**.
285	285
286	286	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
287	287
288	288	(((
289		-(% style="color:red" %)**NOTE:**
	425	+
290	290	)))
291	291
292		-(((
293		-(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
294		-)))
295	295
296	296
297		-
298	298	== 2.3  Uplink Payload ==
299	299
300		-In this mode, uplink payload includes in total 14 bytes
301	301
	433	+(((
	434	+N95S31B has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
	435	+)))
302	302
303		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
304		-|=(% style="width: 60px;" %)(((
305		-**Size(bytes)**
306		-)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**1**
307		-|(% 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:108px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]
308	308
309	309	(((
310		-If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
	439	+For example:
311	311	)))
312	312
	442	+(((
	443	+ (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
	444	+)))
313	313
314		-[[image:1657331036973-987.png]]
315	315
316	316	(((
317		-The payload is ASCII string, representative same HEX:
	448	+The uplink payloads are composed in  ASCII String. For example:
318	318	)))
319	319
320	320	(((
321		-0x72403155615900640c6c19029200 where:
	452	+0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
322	322	)))
323	323
324		-* (((
325		-Device ID: 0x724031556159 = 724031556159
	455	+(((
	456	+0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
326	326	)))
327		-* (((
328		-Version: 0x0064=100=1.0.0
	458	+
	459	+
	460	+(((
	461	+(% style="color:red" %)**NOTE:**
329	329	)))
330	330
331		-* (((
332		-BAT: 0x0c6c = 3180 mV = 3.180V
	464	+(% style="color:red" %)
	465	+1. (((
	466	+**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
333	333	)))
334		-* (((
335		-Signal: 0x19 = 25
336		-)))
337		-* (((
338		-Distance: 0x0292= 658 mm
339		-)))
340		-* (((
341		-Interrupt: 0x00 = 0
342		-)))
	468	+1. (((
	469	+**By default, the device will send an uplink message every 1 hour.**
343	343
344	344
345	345
	473	+
	474	+)))
346	346
347		-== 2.4  Payload Explanation and Sensor Interface ==
	476	+=== 2.3.1  Payload Analyze ===
348	348
349	349
350		-=== 2.4.1  Device ID ===
	479	+N95S31B uplink payload includes in total 21 bytes
351	351
	481	+
	482	+(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
	483	+|=(% style="width: 60px;" %)(((
	484	+**Size(bytes)**
	485	+)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**
	486	+|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
352	352	(((
353		-By default, the Device ID equal to the last 6 bytes of IMEI.
	488	+Reserve/ Same as NBSN95 CFGMOD=1
354	354	)))
355	355
356	356	(((
357		-User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	492	+No function here.
358	358	)))
359		-
	494	+)))|(% style="width:77px" %)(((
360	360	(((
361		-**Example:**
	496	+[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
362	362	)))
363	363
364	364	(((
365		-AT+DEUI=A84041F15612
	500	+By SHT31
366	366	)))
367		-
	502	+)))|(% style="width:80px" %)(((
368	368	(((
369		-The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
	504	+[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
370	370	)))
371	371
372		-
373		-
374		-=== 2.4.2  Version Info ===
375		-
376	376	(((
377		-Specify the software version: 0x64=100, means firmware version 1.00.
	508	+By SHT31
378	378	)))
	510	+)))
379	379
380	380	(((
381		-For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
	513	+
	514	+
	515	+(((
	516	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
382	382	)))
	518	+)))
383	383
384	384
	521	+[[image:1657354294009-643.png]]
385	385
386		-=== 2.4.3  Battery Info ===
387	387
388		-(((
389		-Check the battery voltage for LSE01.
390		-)))
	524	+The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
391	391
	526	+* Device ID: 0x724031607457 = 724031607457
	527	+* Version: 0x006e=110=1.1.0
	528	+
	529	+* BAT: 0x0ccd = 3277 mV = 3.277V
	530	+* Signal: 0x1b = 27
	531	+* Model: 0x01 = 1
	532	+* 0x00dc000ccc= reserve, ignore in N95S31B
	533	+* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
	534	+* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
	535	+
392	392	(((
393		-Ex1: 0x0B45 = 2885mV
	537	+
394	394	)))
395	395
396	396	(((
397		-Ex2: 0x0B49 = 2889mV
	541	+
398	398	)))
399	399
400	400
	545	+=== 2.3.2  Device ID ===
401	401
402		-=== 2.4.4  Signal Strength ===
403	403
404	404	(((
405		-NB-IoT Network signal Strength.
	549	+By default, the Device ID equal to the last 6 bytes of IMEI.
406	406	)))
407	407
408	408	(((
409		-**Ex1: 0x1d = 29**
	553	+User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
410	410	)))
411	411
412	412	(((
413		-(% style="color:blue" %)**0**(%%)  -113dBm or less
	557	+**Example:**
414	414	)))
415	415
416	416	(((
417		-(% style="color:blue" %)**1**(%%)  -111dBm
	561	+AT+DEUI=A84041F15612
418	418	)))
419	419
420	420	(((
421		-(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
	565	+The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
422	422	)))
423	423
424		-(((
425		-(% style="color:blue" %)**31**  (%%) -51dBm or greater
426		-)))
427	427
428		-(((
429		-(% style="color:blue" %)**99**   (%%) Not known or not detectable
430		-)))
431	431
	570	+=== 2.3.3  Version Info ===
432	432
433	433
434		-=== 2.4.5  Soil Moisture ===
	573	+(((
	574	+These bytes include the hardware and software version.
	575	+)))
435	435
436	436	(((
437		-(((
438		-Get the moisture content of the soil. The value range of the register is 0-10000(Decimal), divide this value by 100 to get the percentage of moisture in the soil.
	578	+Higher byte: Specify hardware version: always 0x00 for N95S31B
439	439	)))
440		-)))
441	441
442	442	(((
443		-(((
444		-For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
	582	+Lower byte: Specify the software version: 0x6E=110, means firmware version 110
445	445	)))
446		-)))
447	447
448	448	(((
449	449
...	...	@@ -450,115 +450,87 @@
450	450	)))
451	451
452	452	(((
453		-(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
	590	+For example: 0x00 6E: this device is N95S31B with firmware version 110.
454	454	)))
455	455
	593	+(((
	594	+
	595	+)))
456	456
457	457
458		-=== 2.4.6  Soil Temperature ===
	598	+=== 2.3.4  Battery Info ===
459	459
460		-(((
461		-Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is __**0x09 0xEC**__, the temperature content in the soil is
462		-)))
463	463
464	464	(((
465		-**Example**:
	602	+Ex1: 0x0B45 = 2885mV
466	466	)))
467	467
468	468	(((
469		-If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
	606	+Ex2: 0x0B49 = 2889mV
470	470	)))
471	471
472		-(((
473		-If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
474		-)))
475	475
476	476
	611	+=== 2.3.5  Signal Strength ===
477	477
478		-=== 2.4.7  Soil Conductivity (EC) ===
479	479
480	480	(((
481		-Obtain (% style="color:#4f81bd" %)**__soluble salt concentration__**(%%) in soil or (% style="color:#4f81bd" %)**__soluble ion concentration in liquid fertilizer__**(%%) or (% style="color:#4f81bd" %)**__planting medium__**(%%). The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000).
	615	+NB-IoT Network signal Strength.
482	482	)))
483	483
484	484	(((
485		-For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
	619	+**Ex1: 0x1d = 29**
486	486	)))
487	487
488	488	(((
489		-Generally, the EC value of irrigation water is less than 800uS / cm.
	623	+(% style="color:blue" %)**0**(%%)  -113dBm or less
490	490	)))
491	491
492	492	(((
493		-
	627	+(% style="color:blue" %)**1**(%%)  -111dBm
494	494	)))
495	495
496	496	(((
497		-
	631	+(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
498	498	)))
499	499
500		-=== 2.4.8  Digital Interrupt ===
501		-
502	502	(((
503		-Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server.
	635	+(% style="color:blue" %)**31**  (%%) -51dBm or greater
504	504	)))
505	505
506	506	(((
507		-The command is:
	639	+(% style="color:blue" %)**99**   (%%) Not known or not detectable
508	508	)))
509	509
510		-(((
511		-(% 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]])**.**
512		-)))
513	513
514	514
515		-(((
516		-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.
517		-)))
	644	+=== 2.3.6  Temperature & Humidity ===
518	518
519	519
520		-(((
521		-Example:
522		-)))
	647	+The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
523	523
524		-(((
525		-0x(00): Normal uplink packet.
526		-)))
	649	+[[image:image-20220709161741-3.png]]
527	527
528		-(((
529		-0x(01): Interrupt Uplink Packet.
530		-)))
531	531
	652	+Convert the read byte to decimal and divide it by ten.
532	532
533	533
534		-=== 2.4.9  ​+5V Output ===
	655	+**Example:**
535	535
536		-(((
537		-NSE01 will enable +5V output before all sampling and disable the +5v after all sampling.
538		-)))
	657	+Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
539	539
	659	+Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
540	540
541		-(((
542		-The 5V output time can be controlled by AT Command.
543		-)))
544	544
545		-(((
546		-(% style="color:blue" %)**AT+5VT=1000**
547		-)))
548	548
549		-(((
550		-Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
551		-)))
	663	+== 2.4  Downlink Payload ==
552	552
553	553
	666	+By default, N95S31B prints the downlink payload to console port.
554	554
555		-== 2.5  Downlink Payload ==
	668	+[[image:image-20220709100028-1.png]]
556	556
557		-By default, NSE01 prints the downlink payload to console port.
558	558
559		-[[image:image-20220708133731-5.png]]
560		-
561		-
562	562	(((
563	563	(% style="color:blue" %)**Examples:**
564	564	)))
...	...	@@ -592,7 +592,7 @@
592	592	)))
593	593
594	594	(((
595		-If payload = 0x04FF, it will reset the NSE01
	704	+If payload = 0x04FF, it will reset the N95S31B
596	596	)))
597	597
598	598
...	...	@@ -604,78 +604,20 @@
604	604
605	605
606	606
607		-== 2.6  ​LED Indicator ==
	716	+== 2.5  ​Battery Analysis ==
608	608
609		-(((
610		-The NSE01 has an internal LED which is to show the status of different state.
611	611
	719	+=== 2.5.1  ​Battery Type ===
612	612
613		-* When power on, NSE01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
614		-* Then the LED will be on for 1 second means device is boot normally.
615		-* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
616		-* For each uplink probe, LED will be on for 500ms.
617		-)))
618	618
619		-
620		-
621		-
622		-== 2.7  Installation in Soil ==
623		-
624		-__**Measurement the soil surface**__
625		-
626	626	(((
627		-Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]]
	723	+The N95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
628	628	)))
629	629
630		-[[image:1657259653666-883.png]] ​
631		-
632		-
633	633	(((
634		-
635		-
636		-(((
637		-Dig a hole with diameter > 20CM.
638		-)))
639		-
640		-(((
641		-Horizontal insert the probe to the soil and fill the hole for long term measurement.
642		-)))
643		-)))
644		-
645		-[[image:1654506665940-119.png]]
646		-
647		-(((
648		-
649		-)))
650		-
651		-
652		-== 2.8  ​Firmware Change Log ==
653		-
654		-
655		-Download URL & Firmware Change log
656		-
657		-[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
658		-
659		-
660		-Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
661		-
662		-
663		-
664		-== 2.9  ​Battery Analysis ==
665		-
666		-=== 2.9.1  ​Battery Type ===
667		-
668		-
669		-(((
670		-The NSE01 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.
671		-)))
672		-
673		-
674		-(((
675	675	The battery is designed to last for several years depends on the actually use environment and update interval.
676	676	)))
677	677
678		-
679	679	(((
680	680	The battery related documents as below:
681	681	)))
...	...	@@ -685,61 +685,42 @@
685	685	* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
686	686
687	687	(((
688		-[[image:image-20220708140453-6.png]]
	739	+[[image:image-20220709101450-2.png]]
689	689	)))
690	690
691	691
692	692
693		-=== 2.9.2  Power consumption Analyze ===
	744	+=== 2.5.2  Power consumption Analyze ===
694	694
695		-(((
696		-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.
697		-)))
698	698
699		-
700	700	(((
701		-Instruction to use as below:
	748	+The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
702	702	)))
703	703
704	704	(((
705		-(% 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/]]
	752	+
706	706	)))
707	707
708	708
709		-(((
710		-(% style="color:blue" %)**Step 2: **(%%) Open it and choose
711		-)))
	756	+=== 2.5.3  ​Battery Note ===
712	712
713		-* (((
714		-Product Model
715		-)))
716		-* (((
717		-Uplink Interval
718		-)))
719		-* (((
720		-Working Mode
721		-)))
722	722
723	723	(((
724		-And the Life expectation in difference case will be shown on the right.
	760	+The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to uplink data, then the battery life may be decreased.
725	725	)))
726	726
727		-[[image:image-20220708141352-7.jpeg]]
728	728
729	729
	765	+=== 2.5.4  Replace the battery ===
730	730
731		-=== 2.9.3  ​Battery Note ===
732	732
733	733	(((
734		-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.
	769	+You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
735	735	)))
736	736
737	737
738		-
739		-=== 2.9.4  Replace the battery ===
740		-
741	741	(((
742		-The default battery pack of NSE01 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).
	774	+The default battery pack of N95S31B includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
743	743	)))
744	744
745	745
...	...	@@ -746,6 +746,7 @@
746	746
747	747	= 3. ​ Access NB-IoT Module =
748	748
	781	+
749	749	(((
750	750	Users can directly access the AT command set of the NB-IoT module.
751	751	)))
...	...	@@ -752,19 +752,23 @@
752	752
753	753	(((
754	754	The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]]
	788	+
	789	+
755	755	)))
756	756
757		-[[image:1657261278785-153.png]]
	792	+[[image:1657333200519-600.png]]
758	758
759	759
760	760
761	761	= 4.  Using the AT Commands =
762	762
	798	+
763	763	== 4.1  Access AT Commands ==
764	764
765		-See this link for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
766	766
	802	+See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]]
767	767
	804	+
768	768	AT+<CMD>?  : Help on <CMD>
769	769
770	770	AT+<CMD>         : Run <CMD>
...	...	@@ -838,6 +838,7 @@
838	838
839	839	= ​5.  FAQ =
840	840
	878	+
841	841	== 5.1 ​ How to Upgrade Firmware ==
842	842
843	843
...	...	@@ -850,20 +850,18 @@
850	850	)))
851	851
852	852	(((
853		-(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
854		-)))
	891	+
855	855
856		-
857		-
858		-== 5.2  Can I calibrate NSE01 to different soil types? ==
859		-
860	860	(((
861		-NSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].
	894	+(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
862	862	)))
	896	+)))
863	863
864	864
	899	+
865	865	= 6.  Trouble Shooting =
866	866
	902	+
867	867	== 6.1  ​Connection problem when uploading firmware ==
868	868
869	869
...	...	@@ -879,6 +879,7 @@
879	879
880	880	== 6.2  AT Command input doesn't work ==
881	881
	918	+
882	882	(((
883	883	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.
884	884
...	...	@@ -889,7 +889,7 @@
889	889	= 7. ​ Order Info =
890	890
891	891
892		-Part Number**:** (% style="color:#4f81bd" %)**NSE01**
	929	+Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
893	893
894	894
895	895	(% class="wikigeneratedid" %)
...	...	@@ -904,7 +904,7 @@
904	904
905	905	(% style="color:#037691" %)**Package Includes**:
906	906
907		-* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
	944	+* N95S31B NB-IoT Temperature and Humidity Sensor
908	908	* External antenna x 1
909	909	)))
910	910
...	...	@@ -913,8 +913,10 @@
913	913
914	914	(% style="color:#037691" %)**Dimension and weight**:
915	915
916		-* Size: 195 x 125 x 55 mm
917		-* Weight:   420g
	953	+* Device Size: 13.0 x 5 x 4.5 cm
	954	+* Device Weight: 150g
	955	+* Package Size / pcs : 14.0 x 8x 5 cm
	956	+* Weight / pcs : 180g
918	918	)))
919	919
920	920	(((
...	...	@@ -926,5 +926,9 @@
926	926
927	927	= 9.  Support =
928	928
	968	+
929	929	* 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.
930	930	* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
	971	+
	972	+
	973	+

1657332990863-496.png

Author

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

Size

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

Content

1657333200519-600.png

Author

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

Size

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

Content

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-20220709100028-1.png

Author

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

Size

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

Content

image-20220709101450-2.png

Author

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

Size

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

Content

image-20220709110451-3.png

Author

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

Size

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