Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 95.1
edited by Xiaoling
on 2022/07/09 10:20
Change comment: Uploaded new attachment "1657333200519-600.png", version {1}
To version 124.1
edited by David Huang
on 2022/09/08 16:38
Change comment: There is no comment for this version

Summary

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.David
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,19 +43,16 @@
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  
58 -
59 59  == 1.3  Specification ==
60 60  
61 61  
... ... @@ -81,15 +81,9 @@
81 81  * Max continuously current: 130mA
82 82  * Max boost current: 2A, 1 second
83 83  
84 -(% style="color:#037691" %)**Power Consumption**
85 -
86 -* STOP Mode: 10uA @ 3.3v
87 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
88 -
89 -
90 -
91 91  == ​1.4  Applications ==
92 92  
98 +
93 93  * Smart Buildings & Home Automation
94 94  * Logistics and Supply Chain Management
95 95  * Smart Metering
... ... @@ -102,24 +102,64 @@
102 102  
103 103  
104 104  
105 -== 1.5  Pin Definitions ==
111 +== 1.5  Pin Definitions & Switch ==
106 106  
107 107  
108 -[[image:1657328609906-564.png]]
114 +N95S31B use the mother board from NBSN95 which as below.
109 109  
110 110  
117 +[[image:image-20220709144723-1.png]]
111 111  
112 -= 2.  Use NDDS75 to communicate with IoT Server =
113 113  
120 +
121 +=== 1.5.1 Jumper JP2 ===
122 +
123 +
124 +Power on Device when put this jumper.
125 +
126 +
127 +
128 +=== 1.5.2 BOOT MODE / SW1 ===
129 +
130 +
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 +)))
134 +
135 +(((
136 +2) Flash: work mode, device starts to work and send out console output for further debug
137 +)))
138 +
139 +
140 +
141 +=== 1.5.3 Reset Button ===
142 +
143 +
144 +Press to reboot the device.
145 +
146 +
147 +
148 +=== 1.5.4 LED ===
149 +
150 +
151 +It will flash:
152 +
153 +1. When boot the device in flash mode
154 +1. Send an uplink packet
155 +
156 += 2.  Use N95S31B to communicate with IoT Server =
157 +
158 +
114 114  == 2.1  How it works ==
115 115  
161 +
116 116  (((
117 -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.
163 +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.
118 118  )))
119 119  
120 120  
121 121  (((
122 -The diagram below shows the working flow in default firmware of NDDS75:
168 +The diagram below shows the working flow in default firmware of N95S31B:
123 123  )))
124 124  
125 125  (((
... ... @@ -126,7 +126,7 @@
126 126  
127 127  )))
128 128  
129 -[[image:1657328659945-416.png]]
175 +[[image:1657520100595-569.png]]
130 130  
131 131  (((
132 132  
... ... @@ -133,30 +133,69 @@
133 133  )))
134 134  
135 135  
136 -== 2.2 ​ Configure the NDDS75 ==
182 +== 2.2 ​ Configure the N95S31B ==
137 137  
138 138  
185 +=== 2.2.1  Power On N95S31B ===
186 +
187 +
188 +[[image:image-20220709150546-2.png]]
189 +
190 +
191 +
139 139  === 2.2.1 Test Requirement ===
140 140  
194 +
141 141  (((
142 -To use NDDS75 in your city, make sure meet below requirements:
196 +To use N95S31B in your city, make sure meet below requirements:
143 143  )))
144 144  
145 -* Your local operator has already distributed a NB-IoT Network there.
146 -* The local NB-IoT network used the band that NSE01 supports.
147 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
199 +* (((
200 +Your local operator has already distributed a NB-IoT Network there.
201 +)))
202 +* (((
203 +The local NB-IoT network used the band that N95S31B supports.
204 +)))
205 +* (((
206 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
207 +)))
148 148  
149 149  (((
150 -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
210 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
151 151  )))
152 152  
213 +(((
214 +N95S31B supports different communication protocol such as :
215 +)))
153 153  
154 -[[image:1657328756309-230.png]]
217 +(((
218 +* (((
219 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
220 +)))
221 +* (((
222 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
223 +)))
224 +* (((
225 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
226 +)))
227 +* (((
228 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
229 +)))
155 155  
231 +(((
232 +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.
233 +)))
156 156  
235 +
236 +)))
157 157  
158 -=== 2.2.2 Insert SIM card ===
238 +[[image:1657350625843-586.png]]
159 159  
240 +
241 +
242 +=== 2.2.3  Insert SIM card ===
243 +
244 +
160 160  (((
161 161  Insert the NB-IoT Card get from your provider.
162 162  )))
... ... @@ -166,20 +166,24 @@
166 166  )))
167 167  
168 168  
169 -[[image:1657328884227-504.png]]
254 +[[image:1657351240556-536.png]]
170 170  
171 171  
172 172  
173 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
258 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
174 174  
260 +
175 175  (((
176 176  (((
177 -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.
263 +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.
264 +
265 +
178 178  )))
179 179  )))
180 180  
181 -[[image:image-20220709092052-2.png]]
269 +[[image:1657351312545-300.png]]
182 182  
271 +
183 183  **Connection:**
184 184  
185 185   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -198,253 +198,323 @@
198 198  * Flow Control: (% style="color:green" %)**None**
199 199  
200 200  (((
201 -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.
290 +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.
202 202  )))
203 203  
204 204  [[image:1657329814315-101.png]]
205 205  
295 +
206 206  (((
207 -(% 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/]]
297 +(% 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]]**
208 208  )))
209 209  
210 210  
211 211  
212 -=== 2.2.4 Use CoAP protocol to uplink data ===
302 +=== 2.2.5  Use CoAP protocol to uplink data ===
213 213  
214 -(% 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/]]
215 215  
305 +(% 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/]]**
216 216  
307 +
308 +(((
217 217  **Use below commands:**
310 +)))
218 218  
219 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
220 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
221 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
312 +* (((
313 +(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
314 +)))
315 +* (((
316 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
317 +)))
318 +* (((
319 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
320 +)))
222 222  
322 +(((
323 +
324 +
223 223  For parameter description, please refer to AT command set
326 +)))
224 224  
225 -[[image:1657330452568-615.png]]
328 +[[image:1657352146020-183.png]]
226 226  
227 227  
331 +(((
228 228  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.
333 +)))
229 229  
230 -[[image:1657330472797-498.png]]
335 +[[image:1657352185396-303.png]]
231 231  
232 232  
233 233  
234 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
339 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
235 235  
236 236  
237 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
342 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
238 238  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
239 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
344 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
240 240  
241 -[[image:1657330501006-241.png]]
346 +[[image:1657352391268-297.png]]
242 242  
243 243  
244 -[[image:1657330533775-472.png]]
349 +[[image:1657352403317-397.png]]
245 245  
246 246  
247 247  
248 -=== 2.2.6 Use MQTT protocol to uplink data ===
353 +=== 2.2.7  Use MQTT protocol to uplink data ===
249 249  
250 250  
251 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
252 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
253 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
254 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
255 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
256 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
257 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
356 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
258 258  
259 -[[image:1657249978444-674.png]]
358 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
359 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
360 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
361 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
362 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
363 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
364 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
260 260  
366 +[[image:1657352634421-276.png]]
261 261  
262 -[[image:1657330723006-866.png]]
263 263  
369 +[[image:1657352645687-385.png]]
264 264  
371 +
265 265  (((
266 -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.
373 +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.
267 267  )))
268 268  
269 269  
377 +(((
378 +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.
379 +)))
270 270  
271 -=== 2.2.7 Use TCP protocol to uplink data ===
272 272  
273 273  
383 +=== 2.2.8  Use TCP protocol to uplink data ===
384 +
385 +
386 +This feature is supported since firmware version v110
387 +
274 274  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
275 275  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
276 276  
277 -[[image:image-20220709093918-1.png]]
391 +[[image:1657352898400-901.png]]
278 278  
279 279  
280 -[[image:image-20220709093918-2.png]]
394 +[[image:1657352914475-252.png]]
281 281  
282 282  
283 283  
284 -=== 2.2.8 Change Update Interval ===
398 +=== 2.2.9  Change Update Interval ===
285 285  
400 +
286 286  User can use below command to change the (% style="color:green" %)**uplink interval**.
287 287  
288 288  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
289 289  
290 290  (((
291 -(% style="color:red" %)**NOTE:**
406 +
292 292  )))
293 293  
294 -(((
295 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
296 -)))
409 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
297 297  
411 +**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).**
298 298  
299 299  
300 300  == 2.3  Uplink Payload ==
301 301  
302 -In this mode, uplink payload includes in total 14 bytes
303 303  
417 +(((
418 +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.
419 +)))
304 304  
305 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
306 -|=(% style="width: 60px;" %)(((
307 -**Size(bytes)**
308 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**1**
309 -|(% 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"]]
310 310  
311 311  (((
312 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
423 +For example:
313 313  )))
314 314  
426 +(((
427 + (% 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.
428 +)))
315 315  
316 -[[image:1657331036973-987.png]]
317 317  
318 318  (((
319 -The payload is ASCII string, representative same HEX:
432 +The uplink payloads are composed in  ASCII String. For example:
320 320  )))
321 321  
322 322  (((
323 -0x72403155615900640c6c19029200 where:
436 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
324 324  )))
325 325  
326 -* (((
327 -Device ID: 0x724031556159 = 724031556159
439 +(((
440 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
328 328  )))
329 -* (((
330 -Version: 0x0064=100=1.0.0
442 +
443 +
444 +(((
445 +(% style="color:red" %)**NOTE:**
331 331  )))
332 332  
333 -* (((
334 -BAT: 0x0c6c = 3180 mV = 3.180V
448 +(% style="color:red" %)
449 +1. (((
450 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
335 335  )))
336 -* (((
337 -Signal: 0x19 = 25
452 +1. (((
453 +**By default, the device will send an uplink message every 1 hour.**
454 +
455 +
456 +
457 +
338 338  )))
339 -* (((
340 -Distance: 0x0292= 658 mm
341 -)))
342 -* (((
343 -Interrupt: 0x00 = 0
344 -)))
345 345  
460 +=== 2.3.1  Payload Analyze ===
346 346  
347 -== 2.4  Payload Explanation and Sensor Interface ==
348 348  
463 +N95S31B uplink payload includes in total 21 bytes
349 349  
350 -=== 2.4.1  Device ID ===
351 351  
466 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
467 +|=(% style="width: 60px;" %)(((
468 +**Size(bytes)**
469 +)))|=(% 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**
470 +|(% 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.
472 +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
476 +No function here.
358 358  )))
478 +)))|(% style="width:77px" %)(((
479 +(((
480 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
481 +)))
359 359  
360 360  (((
361 -**Example:**
484 +By SHT31
362 362  )))
486 +)))|(% style="width:80px" %)(((
487 +(((
488 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
489 +)))
363 363  
364 364  (((
365 -AT+DEUI=A84041F15612
492 +By SHT31
366 366  )))
494 +)))
367 367  
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.
497 +
498 +
499 +(((
500 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
370 370  )))
502 +)))
371 371  
372 372  
505 +[[image:1657354294009-643.png]]
373 373  
374 -=== 2.4.2  Version Info ===
375 375  
508 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
509 +
510 +* Device ID: 0x724031607457 = 724031607457
511 +* Version: 0x006e=110=1.1.0
512 +
513 +* BAT: 0x0ccd = 3277 mV = 3.277V
514 +* Signal: 0x1b = 27
515 +* Model: 0x01 = 1
516 +* 0x00dc000ccc= reserve, ignore in N95S31B
517 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
518 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
519 +
376 376  (((
377 -Specify the software version: 0x64=100, means firmware version 1.00.
521 +
378 378  )))
379 379  
380 380  (((
381 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
525 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
382 382  )))
383 383  
528 +In this mode, uplink payload includes 91 bytes in total by default.
384 384  
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.
385 385  
386 -=== 2.4.3  Battery Info ===
532 +|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4
533 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp .....
387 387  
388 -(((
389 -Check the battery voltage for LSE01.
390 -)))
535 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
391 391  
392 -(((
393 -Ex1: 0x0B45 = 2885mV
394 -)))
537 +[[image:image-20220908154949-1.png]]
395 395  
396 -(((
397 -Ex2: 0x0B49 = 2889mV
398 -)))
539 +The payload is ASCII string, representative same HEX:
399 399  
541 +0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where:
400 400  
543 +* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782
544 +* (% style="color:blue" %) Version: 0x000c=120=1.2
545 +* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V
546 +* (% style="color:red" %) Singal: 0x0c = 12
547 +* (% style="color:blue" %) Mod: 0x01 = 1
548 +* TemDS18B20: 0x0000= 0 = 0
549 +* (% style="color:green" %)Interrupt: 0x00= 0
550 +* (% style="color:green" %)adc: 0x0030= 48
551 +* SHTTEM: 0x0114= 276 = 27.6
552 +* SHTHUM:0x0231 =561=56.1%
553 +* (% style="color:red" %) Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
554 +* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
555 +* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,.......
401 401  
402 -=== 2.4.4  Signal Strength ===
557 +=== 2.3.2  Device ID ===
403 403  
404 -(((
405 -NB-IoT Network signal Strength.
406 -)))
407 407  
408 408  (((
409 -**Ex1: 0x1d = 29**
561 +By default, the Device ID equal to the last 6 bytes of IMEI.
410 410  )))
411 411  
412 412  (((
413 -(% style="color:blue" %)**0**(%%)  -113dBm or less
565 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
414 414  )))
415 415  
416 416  (((
417 -(% style="color:blue" %)**1**(%%)  -111dBm
569 +**Example:**
418 418  )))
419 419  
420 420  (((
421 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
573 +AT+DEUI=A84041F15612
422 422  )))
423 423  
424 424  (((
425 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
426 -)))
577 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
427 427  
428 -(((
429 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
579 +
430 430  )))
431 431  
582 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
432 432  
433 433  
434 -=== 2.4.5  Soil Moisture ===
585 +By default, the Device ID equal to the last 15 bits of IMEI.
435 435  
436 -Get the distance. Flat object range 280mm - 7500mm.
587 +User can use **AT+DEUI** to set Device ID
437 437  
438 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
589 +**Example:**
439 439  
591 +AT+DEUI=868411056754138
592 +
593 +
594 +=== 2.3.3  Version Info ===
595 +
596 +
440 440  (((
598 +These bytes include the hardware and software version.
599 +)))
600 +
441 441  (((
442 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
602 +Higher byte: Specify hardware version: always 0x00 for N95S31B
443 443  )))
444 -)))
445 445  
446 446  (((
447 -
606 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
448 448  )))
449 449  
450 450  (((
... ... @@ -451,65 +451,85 @@
451 451  
452 452  )))
453 453  
454 -=== 2.4.6  Digital Interrupt ===
455 -
456 456  (((
457 -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.
614 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
458 458  )))
459 459  
460 460  (((
461 -The command is:
618 +
462 462  )))
463 463  
621 +
622 +=== 2.3.4  Battery Info ===
623 +
624 +
464 464  (((
465 -(% 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]])**.**
626 +Ex1: 0x0B45 = 2885mV
466 466  )))
467 467  
468 -
469 469  (((
470 -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.
630 +Ex2: 0x0B49 = 2889mV
471 471  )))
472 472  
473 473  
634 +
635 +=== 2.3.5  Signal Strength ===
636 +
637 +
474 474  (((
475 -Example:
639 +NB-IoT Network signal Strength.
476 476  )))
477 477  
478 478  (((
479 -0x(00): Normal uplink packet.
643 +**Ex1: 0x1d = 29**
480 480  )))
481 481  
482 482  (((
483 -0x(01): Interrupt Uplink Packet.
647 +(% style="color:blue" %)**0**(%%)  -113dBm or less
484 484  )))
485 485  
486 -
487 -
488 -=== 2.4.7  ​+5V Output ===
489 -
490 490  (((
491 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
651 +(% style="color:blue" %)**1**(%%)  -111dBm
492 492  )))
493 493  
494 -
495 495  (((
496 -The 5V output time can be controlled by AT Command.
655 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
497 497  )))
498 498  
499 499  (((
500 -(% style="color:blue" %)**AT+5VT=1000**
659 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
501 501  )))
502 502  
503 503  (((
504 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
663 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
505 505  )))
506 506  
507 507  
508 508  
509 -== 2.5  Downlink Payload ==
668 +=== 2.3.6  Temperature & Humidity ===
510 510  
511 -By default, NDDS75 prints the downlink payload to console port.
512 512  
671 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
672 +
673 +[[image:image-20220709161741-3.png]]
674 +
675 +
676 +Convert the read byte to decimal and divide it by ten.
677 +
678 +
679 +**Example:**
680 +
681 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
682 +
683 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
684 +
685 +
686 +
687 +== 2.4  Downlink Payload ==
688 +
689 +
690 +By default, N95S31B prints the downlink payload to console port.
691 +
513 513  [[image:image-20220709100028-1.png]]
514 514  
515 515  
... ... @@ -546,7 +546,7 @@
546 546  )))
547 547  
548 548  (((
549 -If payload = 0x04FF, it will reset the NDDS75
728 +If payload = 0x04FF, it will reset the N95S31B
550 550  )))
551 551  
552 552  
... ... @@ -557,53 +557,67 @@
557 557  )))
558 558  
559 559  
739 +== 2.5 Humidity and Temperature alarm function ==
560 560  
561 -== 2.6  ​LED Indicator ==
741 +➢ AT Command:
562 562  
743 +AT+ SHHUM=min,max
563 563  
564 -The NDDS75 has an internal LED which is to show the status of different state.
745 +² When min=0, and max≠0, Alarm higher than max
565 565  
747 +² When min≠0, and max=0, Alarm lower than min
566 566  
567 -* 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)
568 -* Then the LED will be on for 1 second means device is boot normally.
569 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
570 -* For each uplink probe, LED will be on for 500ms.
749 +² When min≠0 and max≠0, Alarm higher than max or lower than min
571 571  
572 -(((
573 -
574 -)))
751 +Example:
575 575  
753 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
576 576  
577 577  
578 -== 2.7  ​Firmware Change Log ==
756 +AT+ SHTEMP=min,max
579 579  
758 +² When min=0, and max≠0, Alarm higher than max
580 580  
581 -Download URL & Firmware Change log
760 +² When min≠0, and max=0, Alarm lower than min
582 582  
583 -(((
584 -[[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/]]
585 -)))
762 +² When min≠0 and max≠0, Alarm higher than max or lower than min
586 586  
764 +Example:
587 587  
588 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
766 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
589 589  
768 +== 2.6 Set the number of data to be uploaded and the recording time ==
590 590  
770 +➢ AT Command:
591 591  
592 -== 2.9  ​Battery Analysis ==
772 +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)
593 593  
594 -=== 2.9.1  ​Battery Type ===
774 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
595 595  
776 +== 2.7 Read or Clear cached data ==
596 596  
778 +➢ AT Command:
779 +
780 +AT+CDP ~/~/ Read cached data
781 +
782 +[[image:image-20220908163102-2.png]]
783 +
784 +AT+CDP=0 ~/~/ Clear cached data
785 +
786 +== 2.8  ​Battery Analysis ==
787 +
788 +
789 +=== 2.8.1  ​Battery Type ===
790 +
791 +
597 597  (((
598 -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.
793 +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.
599 599  )))
600 600  
601 -
602 602  (((
603 603  The battery is designed to last for several years depends on the actually use environment and update interval. 
604 604  )))
605 605  
606 -
607 607  (((
608 608  The battery related documents as below:
609 609  )))
... ... @@ -613,61 +613,42 @@
613 613  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
614 614  
615 615  (((
616 -[[image:image-20220708140453-6.png]]
809 +[[image:image-20220709101450-2.png]]
617 617  )))
618 618  
619 619  
620 620  
621 -=== 2.9.2  Power consumption Analyze ===
814 +=== 2.8.2  Power consumption Analyze ===
622 622  
623 -(((
624 -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.
625 -)))
626 626  
627 -
628 628  (((
629 -Instruction to use as below:
818 +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.
630 630  )))
631 631  
632 632  (((
633 -(% 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/]]
822 +
634 634  )))
635 635  
636 636  
637 -(((
638 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
639 -)))
826 +=== 2.8.3  ​Battery Note ===
640 640  
641 -* (((
642 -Product Model
643 -)))
644 -* (((
645 -Uplink Interval
646 -)))
647 -* (((
648 -Working Mode
649 -)))
650 650  
651 651  (((
652 -And the Life expectation in difference case will be shown on the right.
830 +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.
653 653  )))
654 654  
655 -[[image:image-20220708141352-7.jpeg]]
656 656  
657 657  
835 +=== 2.8.4  Replace the battery ===
658 658  
659 -=== 2.9.3  ​Battery Note ===
660 660  
661 661  (((
662 -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.
839 +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.
663 663  )))
664 664  
665 665  
666 -
667 -=== 2.9.4  Replace the battery ===
668 -
669 669  (((
670 -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).
844 +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).
671 671  )))
672 672  
673 673  
... ... @@ -674,6 +674,7 @@
674 674  
675 675  = 3. ​ Access NB-IoT Module =
676 676  
851 +
677 677  (((
678 678  Users can directly access the AT command set of the NB-IoT module.
679 679  )))
... ... @@ -680,19 +680,23 @@
680 680  
681 681  (((
682 682  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/]] 
858 +
859 +
683 683  )))
684 684  
685 -[[image:1657261278785-153.png]]
862 +[[image:1657333200519-600.png]]
686 686  
687 687  
688 688  
689 689  = 4.  Using the AT Commands =
690 690  
868 +
691 691  == 4.1  Access AT Commands ==
692 692  
693 -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/]]
694 694  
872 +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]]
695 695  
874 +
696 696  AT+<CMD>?  : Help on <CMD>
697 697  
698 698  AT+<CMD>         : Run <CMD>
... ... @@ -732,7 +732,24 @@
732 732  
733 733  AT+SERVADDR  : Server Address
734 734  
914 +AT+TR      : Get or Set record time
735 735  
916 +AT+APN     : Get or set the APN
917 +
918 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
919 +
920 +AT+DNSCFG  : Get or Set DNS Server
921 +
922 +AT+GETSENSORVALUE   : Returns the current sensor measurement
923 +
924 +AT+NOUD      : Get or Set the number of data to be uploaded
925 +
926 +AT+CDP     : Read or Clear cached data
927 +
928 +AT+SHTEMP: Get or Set alarm of temp
929 +
930 +AT+SHHUM: Get or Set alarm of moisture
931 +
736 736  (% style="color:#037691" %)**COAP Management**      
737 737  
738 738  AT+URI            : Resource parameters
... ... @@ -766,6 +766,7 @@
766 766  
767 767  = ​5.  FAQ =
768 768  
965 +
769 769  == 5.1 ​ How to Upgrade Firmware ==
770 770  
771 771  
... ... @@ -778,20 +778,18 @@
778 778  )))
779 779  
780 780  (((
781 -(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
782 -)))
978 +
783 783  
784 -
785 -
786 -== 5.2  Can I calibrate NSE01 to different soil types? ==
787 -
788 788  (((
789 -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]].
981 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
790 790  )))
983 +)))
791 791  
792 792  
986 +
793 793  = 6.  Trouble Shooting =
794 794  
989 +
795 795  == 6.1  ​Connection problem when uploading firmware ==
796 796  
797 797  
... ... @@ -807,6 +807,7 @@
807 807  
808 808  == 6.2  AT Command input doesn't work ==
809 809  
1005 +
810 810  (((
811 811  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.
812 812  
... ... @@ -817,7 +817,7 @@
817 817  = 7. ​ Order Info =
818 818  
819 819  
820 -Part Number**:** (% style="color:#4f81bd" %)**NSE01**
1016 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
821 821  
822 822  
823 823  (% class="wikigeneratedid" %)
... ... @@ -832,7 +832,7 @@
832 832  
833 833  (% style="color:#037691" %)**Package Includes**:
834 834  
835 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
1031 +* N95S31B NB-IoT Temperature and Humidity Sensor
836 836  * External antenna x 1
837 837  )))
838 838  
... ... @@ -841,8 +841,10 @@
841 841  
842 842  (% style="color:#037691" %)**Dimension and weight**:
843 843  
844 -* Size: 195 x 125 x 55 mm
845 -* Weight:   420g
1040 +* Device Size: 13.0 x 5 x 4.5 cm
1041 +* Device Weight: 150g
1042 +* Package Size / pcs : 14.0 x 8x 5 cm
1043 +* Weight / pcs : 180g
846 846  )))
847 847  
848 848  (((
... ... @@ -854,5 +854,7 @@
854 854  
855 855  = 9.  Support =
856 856  
1055 +
857 857  * 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.
858 858  * 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]]
1058 +
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-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
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