Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 130.1 >
edited by Bei Jinggeng
on 2023/04/19 14:36
To version < 100.1 >
edited by Xiaoling
on 2022/07/09 14:47
>
Change comment: Uploaded new attachment "image-20220709144723-1.png", version {1}

Summary

Details

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

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0