Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.2 >
edited by Xiaoling
on 2022/07/09 16:18
To version < 99.3 >
edited by Xiaoling
on 2022/07/09 14:37
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -41,19 +41,19 @@
41 41  
42 42  == 1.2 ​ Features ==
43 43  
44 -
45 45  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
46 -* 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
47 47  * AT Commands to change parameters
48 48  * Uplink on periodically
49 49  * Downlink to change configure
50 50  * IP66 Waterproof Enclosure
51 -* Ultra-Low Power consumption
52 -* AT Commands to change parameters
53 53  * Micro SIM card slot for NB-IoT SIM
54 54  * 8500mAh Battery for long term use
55 55  
56 -
57 57  == 1.3  Specification ==
58 58  
59 59  
... ... @@ -73,7 +73,6 @@
73 73  
74 74  (% style="color:#037691" %)**Battery:**
75 75  
76 -
77 77  * Li/SOCI2 un-chargeable battery
78 78  * Capacity: 8500mAh
79 79  * Self Discharge: <1% / Year @ 25°C
... ... @@ -80,7 +80,11 @@
80 80  * Max continuously current: 130mA
81 81  * Max boost current: 2A, 1 second
82 82  
82 +(% style="color:#037691" %)**Power Consumption**
83 83  
84 +* STOP Mode: 10uA @ 3.3v
85 +* Max transmit power: 350mA@3.3v
86 +
84 84  == ​1.4  Applications ==
85 85  
86 86  * Smart Buildings & Home Automation
... ... @@ -96,52 +96,22 @@
96 96  
97 97  == 1.5  Pin Definitions ==
98 98  
99 -N95S31B use the mother board from NBSN95 which as below.
100 100  
101 -[[image:image-20220709144723-1.png]]
103 +[[image:1657328609906-564.png]]
102 102  
103 103  
104 -=== 1.5.1 Jumper JP2 ===
105 105  
106 -Power on Device when put this jumper.
107 += 2.  Use NDDS75 to communicate with IoT Server =
107 107  
108 -
109 -
110 -=== 1.5.2 BOOT MODE / SW1 ===
111 -
112 -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.
113 -
114 -2) Flash: work mode, device starts to work and send out console output for further debug
115 -
116 -
117 -
118 -=== 1.5.3 Reset Button ===
119 -
120 -Press to reboot the device.
121 -
122 -
123 -
124 -=== 1.5.4 LED ===
125 -
126 -It will flash:
127 -
128 -1. When boot the device in flash mode
129 -1. Send an uplink packet
130 -
131 -
132 -
133 -= 2.  Use N95S31B to communicate with IoT Server =
134 -
135 135  == 2.1  How it works ==
136 136  
137 -
138 138  (((
139 -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.
140 140  )))
141 141  
142 142  
143 143  (((
144 -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:
145 145  )))
146 146  
147 147  (((
... ... @@ -148,7 +148,7 @@
148 148  
149 149  )))
150 150  
151 -[[image:1657350248151-650.png]]
124 +[[image:1657328659945-416.png]]
152 152  
153 153  (((
154 154  
... ... @@ -155,45 +155,30 @@
155 155  )))
156 156  
157 157  
158 -== 2.2 ​ Configure the N95S31B ==
131 +== 2.2 ​ Configure the NDDS75 ==
159 159  
160 160  
161 -=== 2.2.1  Power On N95S31B ===
162 -
163 -
164 -[[image:image-20220709150546-2.png]]
165 -
166 -
167 167  === 2.2.1 Test Requirement ===
168 168  
136 +(((
137 +To use NDDS75 in your city, make sure meet below requirements:
138 +)))
169 169  
170 -To use N95S31B in your city, make sure meet below requirements:
171 -
172 172  * Your local operator has already distributed a NB-IoT Network there.
173 -* The local NB-IoT network used the band that N95S31B supports.
141 +* The local NB-IoT network used the band that NSE01 supports.
174 174  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
175 175  
176 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
177 -
178 -N95S31B supports different communication protocol such as :
179 -
180 180  (((
181 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
182 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
183 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
184 -* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
185 -
186 -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.
187 -
188 -
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
189 189  )))
190 190  
191 -[[image:1657350625843-586.png]]
192 192  
149 +[[image:1657328756309-230.png]]
193 193  
194 194  
195 -=== 2.2.3  Insert SIM card ===
196 196  
153 +=== 2.2.2 Insert SIM card ===
154 +
197 197  (((
198 198  Insert the NB-IoT Card get from your provider.
199 199  )))
... ... @@ -203,19 +203,19 @@
203 203  )))
204 204  
205 205  
206 -[[image:1657351240556-536.png]]
164 +[[image:1657328884227-504.png]]
207 207  
208 208  
209 209  
210 -=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
168 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
211 211  
212 212  (((
213 213  (((
214 -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.
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.
215 215  )))
216 216  )))
217 217  
218 -[[image:1657351312545-300.png]]
176 +[[image:image-20220709092052-2.png]]
219 219  
220 220  **Connection:**
221 221  
... ... @@ -235,18 +235,18 @@
235 235  * Flow Control: (% style="color:green" %)**None**
236 236  
237 237  (((
238 -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.
239 239  )))
240 240  
241 241  [[image:1657329814315-101.png]]
242 242  
243 243  (((
244 -(% style="color:red" %)Note: the valid AT Commands can be found at:  (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]
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/]]
245 245  )))
246 246  
247 247  
248 248  
249 -=== 2.2.5  Use CoAP protocol to uplink data ===
207 +=== 2.2.4 Use CoAP protocol to uplink data ===
250 250  
251 251  (% 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/]]
252 252  
... ... @@ -266,12 +266,10 @@
266 266  )))
267 267  
268 268  (((
269 -
270 -
271 271  For parameter description, please refer to AT command set
272 272  )))
273 273  
274 -[[image:1657352146020-183.png]]
230 +[[image:1657330452568-615.png]]
275 275  
276 276  
277 277  (((
... ... @@ -278,11 +278,11 @@
278 278  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.
279 279  )))
280 280  
281 -[[image:1657352185396-303.png]]
237 +[[image:1657330472797-498.png]]
282 282  
283 283  
284 284  
285 -=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
241 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
286 286  
287 287  
288 288  * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
... ... @@ -289,16 +289,15 @@
289 289  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
290 290  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
291 291  
292 -[[image:1657352391268-297.png]]
248 +[[image:1657330501006-241.png]]
293 293  
294 294  
295 -[[image:1657352403317-397.png]]
251 +[[image:1657330533775-472.png]]
296 296  
297 297  
298 298  
299 -=== 2.2.7  Use MQTT protocol to uplink data ===
255 +=== 2.2.6 Use MQTT protocol to uplink data ===
300 300  
301 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
302 302  
303 303  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
304 304  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -305,40 +305,35 @@
305 305  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
306 306  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
307 307  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
308 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
309 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic 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
310 310  
311 -[[image:1657352634421-276.png]]
266 +[[image:1657249978444-674.png]]
312 312  
313 313  
314 -[[image:1657352645687-385.png]]
269 +[[image:1657330723006-866.png]]
315 315  
316 -(((
317 -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.
318 -)))
319 319  
320 -
321 321  (((
322 -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.
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.
323 323  )))
324 324  
325 325  
326 326  
327 -=== 2.2.8  Use TCP protocol to uplink data ===
278 +=== 2.2.7 Use TCP protocol to uplink data ===
328 328  
329 -This feature is supported since firmware version v110
330 330  
331 331  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
332 332  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
333 333  
334 -[[image:1657352898400-901.png]]
284 +[[image:image-20220709093918-1.png]]
335 335  
336 336  
337 -[[image:1657352914475-252.png]]
287 +[[image:image-20220709093918-2.png]]
338 338  
339 339  
340 340  
341 -=== 2.2.9  Change Update Interval ===
291 +=== 2.2.8 Change Update Interval ===
342 342  
343 343  User can use below command to change the (% style="color:green" %)**uplink interval**.
344 344  
... ... @@ -345,93 +345,69 @@
345 345  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
346 346  
347 347  (((
348 -
298 +(% style="color:red" %)**NOTE:**
349 349  )))
350 350  
301 +(((
302 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
303 +)))
351 351  
352 352  
306 +
353 353  == 2.3  Uplink Payload ==
354 354  
309 +In this mode, uplink payload includes in total 14 bytes
355 355  
356 -NBSN95 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.
357 357  
358 -
359 -For example:
360 -
361 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
362 -
363 -
364 -The uplink payloads are composed in  ASCII String. For example:
365 -
366 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
367 -
368 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
369 -
370 -
371 -(% style="color:red" %)**NOTE:**
372 -
373 -(% style="color:red" %)
374 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
375 -1. By default, the device will send an uplink message every 1 hour.
376 -
377 -
378 -
379 -
380 -=== 2.3.1  Payload Analyze ===
381 -
382 -N95S31B uplink payload includes in total 21 bytes
383 -
384 -
385 385  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
386 386  |=(% style="width: 60px;" %)(((
387 387  **Size(bytes)**
388 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1**
389 -|(% 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:123px" %)MOD 0X01|(% style="width:99px" %)(((
390 -Reserve/ Same as NBSN95 CFGMOD=1
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"]]
391 391  
392 -No function here.
393 -)))|(% style="width:77px" %)(((
394 -[[Temperature >>||anchor="H2.4.5A0Distance"]]
318 +(((
319 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
320 +)))
395 395  
396 -By SHT31
397 -)))|(% style="width:80px" %)(((
398 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
399 399  
400 -By SHT31
323 +[[image:1657331036973-987.png]]
324 +
325 +(((
326 +The payload is ASCII string, representative same HEX:
401 401  )))
402 402  
403 403  (((
404 -(((
405 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
330 +0x72403155615900640c6c19029200 where:
406 406  )))
332 +
333 +* (((
334 +Device ID: 0x724031556159 = 724031556159
407 407  )))
336 +* (((
337 +Version: 0x0064=100=1.0.0
338 +)))
408 408  
340 +* (((
341 +BAT: 0x0c6c = 3180 mV = 3.180V
342 +)))
343 +* (((
344 +Signal: 0x19 = 25
345 +)))
346 +* (((
347 +Distance: 0x0292= 658 mm
348 +)))
349 +* (((
350 +Interrupt: 0x00 = 0
409 409  
410 -[[image:1657354294009-643.png]]
411 411  
412 412  
413 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
414 -
415 -* Device ID: 0x724031607457 = 724031607457
416 -* Version: 0x006e=110=1.1.0
417 -
418 -* BAT: 0x0ccd = 3277 mV = 3.277V
419 -* Signal: 0x1b = 27
420 -* Model: 0x01 = 1
421 -* 0x00dc000ccc= reserve, ignore in N95S31B
422 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
423 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
424 -
425 -(((
426 426  
427 427  )))
428 428  
429 -(((
430 -
431 -)))
357 +== 2.4  Payload Explanation and Sensor Interface ==
432 432  
433 433  
434 -=== 2.3.2  Device ID ===
360 +=== 2.4.1  Device ID ===
435 435  
436 436  (((
437 437  By default, the Device ID equal to the last 6 bytes of IMEI.
... ... @@ -455,25 +455,20 @@
455 455  
456 456  
457 457  
458 -=== 2.3.3  Version Info ===
384 +=== 2.4.2  Version Info ===
459 459  
386 +(((
387 +Specify the software version: 0x64=100, means firmware version 1.00.
388 +)))
460 460  
461 -These bytes include the hardware and software version.
462 -
463 -Higher byte: Specify hardware version: always 0x00 for N95S31B
464 -
465 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
466 -
467 -
468 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
469 -
470 470  (((
471 -
391 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
472 472  )))
473 473  
474 474  
475 -=== 2.3.4  Battery Info ===
476 476  
396 +=== 2.4.3  Battery Info ===
397 +
477 477  (((
478 478  Ex1: 0x0B45 = 2885mV
479 479  )))
... ... @@ -484,7 +484,7 @@
484 484  
485 485  
486 486  
487 -=== 2.3.5  Signal Strength ===
408 +=== 2.4.4  Signal Strength ===
488 488  
489 489  (((
490 490  NB-IoT Network signal Strength.
... ... @@ -516,24 +516,83 @@
516 516  
517 517  
518 518  
519 -=== 2.3.6  Temperature & Humidity ===
440 +=== 2.4.5  Distance ===
520 520  
521 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
442 +Get the distance. Flat object range 280mm - 7500mm.
522 522  
523 -[[image:image-20220709161741-3.png]]
444 +(((
445 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
446 +)))
524 524  
448 +(((
449 +(((
450 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
451 +)))
452 +)))
525 525  
526 -Convert the read byte to decimal and divide it by ten.
454 +(((
455 +
456 +)))
527 527  
458 +(((
459 +
460 +)))
528 528  
529 -**Example:**
462 +=== 2.4.6  Digital Interrupt ===
530 530  
531 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
464 +(((
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.
466 +)))
532 532  
533 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
468 +(((
469 +The command is:
470 +)))
534 534  
472 +(((
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]])**.**
474 +)))
535 535  
536 536  
477 +(((
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.
479 +)))
480 +
481 +
482 +(((
483 +Example:
484 +)))
485 +
486 +(((
487 +0x(00): Normal uplink packet.
488 +)))
489 +
490 +(((
491 +0x(01): Interrupt Uplink Packet.
492 +)))
493 +
494 +
495 +
496 +=== 2.4.7  ​+5V Output ===
497 +
498 +(((
499 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
500 +)))
501 +
502 +
503 +(((
504 +The 5V output time can be controlled by AT Command.
505 +)))
506 +
507 +(((
508 +(% style="color:blue" %)**AT+5VT=1000**
509 +)))
510 +
511 +(((
512 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
513 +)))
514 +
515 +
516 +
537 537  == 2.5  Downlink Payload ==
538 538  
539 539  By default, NDDS75 prints the downlink payload to console port.
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
image-20220709144723-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -413.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

Applications

Navigation

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