Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 97.19 >
edited by Xiaoling
on 2022/07/09 13:53
To version < 104.6 >
edited by Xiaoling
on 2022/09/09 13:35
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,6 +16,7 @@
16 16  
17 17  = 1.  Introduction =
18 18  
19 +
19 19  == 1.1 ​ What is NDDS75 Distance Detection Sensor ==
20 20  
21 21  (((
... ... @@ -56,6 +56,7 @@
56 56  
57 57  == 1.2 ​ Features ==
58 58  
60 +
59 59  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
60 60  * Ultra low power consumption
61 61  * Distance Detection by Ultrasonic technology
... ... @@ -71,6 +71,8 @@
71 71  
72 72  
73 73  
76 +
77 +
74 74  == 1.3  Specification ==
75 75  
76 76  
... ... @@ -103,8 +103,11 @@
103 103  
104 104  
105 105  
110 +
111 +
106 106  == ​1.4  Applications ==
107 107  
114 +
108 108  * Smart Buildings & Home Automation
109 109  * Logistics and Supply Chain Management
110 110  * Smart Metering
... ... @@ -116,6 +116,8 @@
116 116  ​
117 117  
118 118  
126 +
127 +
119 119  == 1.5  Pin Definitions ==
120 120  
121 121  
... ... @@ -125,8 +125,10 @@
125 125  
126 126  = 2.  Use NDDS75 to communicate with IoT Server =
127 127  
137 +
128 128  == 2.1  How it works ==
129 129  
140 +
130 130  (((
131 131  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.
132 132  )))
... ... @@ -152,16 +152,17 @@
152 152  
153 153  === 2.2.1 Test Requirement ===
154 154  
166 +
155 155  (((
156 156  To use NDDS75 in your city, make sure meet below requirements:
157 157  )))
158 158  
159 159  * Your local operator has already distributed a NB-IoT Network there.
160 -* The local NB-IoT network used the band that NSE01 supports.
172 +* The local NB-IoT network used the band that NDDS75 supports.
161 161  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
162 162  
163 163  (((
164 -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
176 +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.
165 165  )))
166 166  
167 167  
... ... @@ -171,6 +171,7 @@
171 171  
172 172  === 2.2.2 Insert SIM card ===
173 173  
186 +
174 174  (((
175 175  Insert the NB-IoT Card get from your provider.
176 176  )))
... ... @@ -186,6 +186,7 @@
186 186  
187 187  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
188 188  
202 +
189 189  (((
190 190  (((
191 191  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.
... ... @@ -194,6 +194,7 @@
194 194  
195 195  [[image:image-20220709092052-2.png]]
196 196  
211 +
197 197  **Connection:**
198 198  
199 199   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -217,8 +217,9 @@
217 217  
218 218  [[image:1657329814315-101.png]]
219 219  
235 +
220 220  (((
221 -(% 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/]]
237 +(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]**
222 222  )))
223 223  
224 224  
... ... @@ -225,9 +225,10 @@
225 225  
226 226  === 2.2.4 Use CoAP protocol to uplink data ===
227 227  
228 -(% 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/]]
229 229  
245 +(% 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/]]**
230 230  
247 +
231 231  (((
232 232  **Use below commands:**
233 233  )))
... ... @@ -240,17 +240,25 @@
240 240  )))
241 241  * (((
242 242  (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
260 +
261 +
262 +
243 243  )))
244 244  
245 245  (((
246 246  For parameter description, please refer to AT command set
267 +
268 +
247 247  )))
248 248  
249 249  [[image:1657330452568-615.png]]
250 250  
251 251  
274 +
252 252  (((
253 253  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.
277 +
278 +
254 254  )))
255 255  
256 256  [[image:1657330472797-498.png]]
... ... @@ -309,25 +309,34 @@
309 309  
310 310  === 2.2.8 Change Update Interval ===
311 311  
337 +
312 312  User can use below command to change the (% style="color:green" %)**uplink interval**.
313 313  
314 314  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
315 315  
316 316  (((
343 +
344 +
345 +
317 317  (% style="color:red" %)**NOTE:**
318 -)))
319 319  
320 -(((
321 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
348 +(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
349 +
350 +(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
322 322  )))
323 323  
353 +(% 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).**
324 324  
325 325  
356 +
326 326  == 2.3  Uplink Payload ==
327 327  
328 -In this mode, uplink payload includes in total 14 bytes
329 329  
360 +=== 2.3.1  Before Firmware 1.3.2 ===
330 330  
362 +
363 +In this mode, uplink payload includes in total 14 bytes
364 +
331 331  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
332 332  |=(% style="width: 60px;" %)(((
333 333  **Size(bytes)**
... ... @@ -341,8 +341,9 @@
341 341  
342 342  [[image:1657331036973-987.png]]
343 343  
378 +
344 344  (((
345 -The payload is ASCII string, representative same HEX:
380 +The payload is **ASCII** string, representative same HEX:
346 346  )))
347 347  
348 348  (((
... ... @@ -353,11 +353,11 @@
353 353  Device ID: 0x724031556159 = 724031556159
354 354  )))
355 355  * (((
356 -Version: 0x0064=100=1.0.0
391 +Version:  0x0064=100=1.0.0
357 357  )))
358 358  
359 359  * (((
360 -BAT: 0x0c6c = 3180 mV = 3.180V
395 +BAT:  0x0c6c = 3180 mV = 3.180V
361 361  )))
362 362  * (((
363 363  Signal: 0x19 = 25
... ... @@ -370,14 +370,51 @@
370 370  
371 371  
372 372  
408 +
373 373  
374 374  )))
375 375  
412 +=== **2.3.2  Since firmware v1.3.2** ===
413 +
414 +
415 +In this mode, uplink payload includes 69 bytes in total by default.
416 +
417 +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.
418 +
419 +(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
420 +|(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4
421 +|(% style="width:95px" %)**Value**|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp.......
422 +
423 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
424 +
425 +[[image:image-20220908175246-1.png]]
426 +
427 +
428 +The payload is ASCII string, representative same HEX:
429 +
430 +0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where:
431 +
432 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
433 +* (% style="color:red" %)Version: 0x0084=132=1.3.2
434 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
435 +* (% style="color:blue" %)Singal: 0x1e = 30
436 +* (% style="color:red" %)Mod: 0x01 = 1
437 +* Interrupt: 0x00= 0
438 +* Distance: 0x0039= 57 = 57
439 +* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
440 +* Distance,Time stamp : 00396319baf0
441 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
442 +
443 +
444 +
445 +
446 +
376 376  == 2.4  Payload Explanation and Sensor Interface ==
377 377  
378 378  
379 379  === 2.4.1  Device ID ===
380 380  
452 +
381 381  (((
382 382  By default, the Device ID equal to the last 6 bytes of IMEI.
383 383  )))
... ... @@ -384,10 +384,12 @@
384 384  
385 385  (((
386 386  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
459 +
460 +
387 387  )))
388 388  
389 389  (((
390 -**Example:**
464 +(% style="color:blue" %)**Example :**
391 391  )))
392 392  
393 393  (((
... ... @@ -395,13 +395,26 @@
395 395  )))
396 396  
397 397  (((
398 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
472 +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.
399 399  )))
400 400  
401 401  
476 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
402 402  
478 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
479 +
480 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
481 +
482 +
483 +(% style="color:blue" %)**Example :**
484 +
485 +AT+DEUI=868411056754138
486 +
487 +
488 +
403 403  === 2.4.2  Version Info ===
404 404  
491 +
405 405  (((
406 406  Specify the software version: 0x64=100, means firmware version 1.00.
407 407  )))
... ... @@ -414,6 +414,7 @@
414 414  
415 415  === 2.4.3  Battery Info ===
416 416  
504 +
417 417  (((
418 418  Ex1: 0x0B45 = 2885mV
419 419  )))
... ... @@ -426,6 +426,7 @@
426 426  
427 427  === 2.4.4  Signal Strength ===
428 428  
517 +
429 429  (((
430 430  NB-IoT Network signal Strength.
431 431  )))
... ... @@ -458,6 +458,7 @@
458 458  
459 459  === 2.4.5  Distance ===
460 460  
550 +
461 461  Get the distance. Flat object range 280mm - 7500mm.
462 462  
463 463  (((
... ... @@ -480,6 +480,7 @@
480 480  
481 481  === 2.4.6  Digital Interrupt ===
482 482  
573 +
483 483  (((
484 484  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.
485 485  )))
... ... @@ -514,6 +514,7 @@
514 514  
515 515  === 2.4.7  ​+5V Output ===
516 516  
608 +
517 517  (((
518 518  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
519 519  )))
... ... @@ -521,10 +521,14 @@
521 521  
522 522  (((
523 523  The 5V output time can be controlled by AT Command.
616 +
617 +
524 524  )))
525 525  
526 526  (((
527 527  (% style="color:blue" %)**AT+5VT=1000**
622 +
623 +
528 528  )))
529 529  
530 530  (((
... ... @@ -535,6 +535,7 @@
535 535  
536 536  == 2.5  Downlink Payload ==
537 537  
634 +
538 538  By default, NDDS75 prints the downlink payload to console port.
539 539  
540 540  [[image:image-20220709100028-1.png]]
... ... @@ -585,9 +585,54 @@
585 585  
586 586  
587 587  
588 -== 2.6  ​LED Indicator ==
685 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
589 589  
590 590  
688 +(% style="color:blue" %)** ➢ AT Command:**
689 +
690 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
691 +
692 +² When min=0, and max≠0, Alarm higher than max
693 +
694 +² When min≠0, and max=0, Alarm lower than min
695 +
696 +² When min≠0 and max≠0, Alarm higher than max or lower than min
697 +
698 +
699 +(% style="color:blue" %)** Example:**
700 +
701 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
702 +
703 +
704 +
705 +== 2.7  Set the number of data to be uploaded and the recording time ==
706 +
707 +
708 +(% style="color:blue" %)** ➢ AT Command:**
709 +
710 +* (% 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)
711 +* (% 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.
712 +
713 +
714 +
715 +
716 +== 2.8  Read or Clear cached data ==
717 +
718 +
719 +(% style="color:blue" %)** ➢ AT Command:**
720 +
721 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data
722 +* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
723 +
724 +
725 +
726 +[[image:image-20220908175333-2.png]]
727 +
728 +
729 +
730 +== 2.9  ​LED Indicator ==
731 +
732 +
591 591  The NDDS75 has an internal LED which is to show the status of different state.
592 592  
593 593  
... ... @@ -602,29 +602,29 @@
602 602  
603 603  
604 604  
605 -== 2.7  ​Firmware Change Log ==
747 +== 2.10  ​Firmware Change Log ==
606 606  
607 607  
608 608  (((
609 -Download URL & Firmware Change log
751 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]]
610 610  )))
611 611  
612 612  (((
613 -[[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/]]
755 +
614 614  )))
615 615  
616 -
617 617  (((
618 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
759 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
619 619  )))
620 620  
621 621  
622 622  
623 -== 2.8  ​Battery Analysis ==
764 +== 2.11  ​Battery Analysis ==
624 624  
625 -=== 2.8.1  ​Battery Type ===
626 626  
767 +=== 2.11.1  ​Battery Type ===
627 627  
769 +
628 628  (((
629 629  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.
630 630  )))
... ... @@ -647,8 +647,9 @@
647 647  
648 648  
649 649  
650 -=== 2.8.2  Power consumption Analyze ===
792 +=== 2.11.2  Power consumption Analyze ===
651 651  
794 +
652 652  (((
653 653  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.
654 654  )))
... ... @@ -685,8 +685,9 @@
685 685  
686 686  
687 687  
688 -=== 2.8.3  ​Battery Note ===
831 +=== 2.11.3  ​Battery Note ===
689 689  
833 +
690 690  (((
691 691  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.
692 692  )))
... ... @@ -693,8 +693,9 @@
693 693  
694 694  
695 695  
696 -=== 2.8.4  Replace the battery ===
840 +=== 2.11.4  Replace the battery ===
697 697  
842 +
698 698  (((
699 699  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).
700 700  )))
... ... @@ -703,6 +703,7 @@
703 703  
704 704  = 3. ​ Access NB-IoT Module =
705 705  
851 +
706 706  (((
707 707  Users can directly access the AT command set of the NB-IoT module.
708 708  )))
... ... @@ -709,6 +709,8 @@
709 709  
710 710  (((
711 711  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 +
712 712  )))
713 713  
714 714  [[image:1657333200519-600.png]]
... ... @@ -717,11 +717,13 @@
717 717  
718 718  = 4.  Using the AT Commands =
719 719  
868 +
720 720  == 4.1  Access AT Commands ==
721 721  
722 -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/]]
723 723  
872 +See this link for detail:  [[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]
724 724  
874 +
725 725  AT+<CMD>?  : Help on <CMD>
726 726  
727 727  AT+<CMD>         : Run <CMD>
... ... @@ -761,7 +761,23 @@
761 761  
762 762  AT+SERVADDR  : Server Address
763 763  
914 +AT+TR      : Get or Set record time"
764 764  
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+LDDSALARM : Get or Set alarm of distance
929 +
930 +
765 765  (% style="color:#037691" %)**COAP Management**      
766 766  
767 767  AT+URI            : Resource parameters
... ... @@ -795,6 +795,7 @@
795 795  
796 796  = ​5.  FAQ =
797 797  
964 +
798 798  == 5.1 ​ How to Upgrade Firmware ==
799 799  
800 800  
... ... @@ -807,7 +807,7 @@
807 807  )))
808 808  
809 809  (((
810 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
977 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
811 811  )))
812 812  
813 813  
... ... @@ -814,6 +814,7 @@
814 814  
815 815  = 6.  Trouble Shooting =
816 816  
984 +
817 817  == 6.1  ​Connection problem when uploading firmware ==
818 818  
819 819  
... ... @@ -829,6 +829,7 @@
829 829  
830 830  == 6.2  AT Command input doesn't work ==
831 831  
1000 +
832 832  (((
833 833  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.
834 834  
... ... @@ -854,7 +854,7 @@
854 854  
855 855  (% style="color:#037691" %)**Package Includes**:
856 856  
857 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
1026 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
858 858  * External antenna x 1
859 859  )))
860 860  
... ... @@ -861,9 +861,9 @@
861 861  (((
862 862  
863 863  
1033 +
864 864  (% style="color:#037691" %)**Dimension and weight**:
865 865  
866 -
867 867  * Device Size: 13.0 x 5 x 4.5 cm
868 868  * Device Weight: 150g
869 869  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -879,5 +879,6 @@
879 879  
880 880  = 9.  Support =
881 881  
1051 +
882 882  * 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.
883 883  * 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]]
image-20220908175246-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +31.1 KB
Content

Applications

Navigation

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