Skip to Content
Last modified by Xiaoling on 2025/04/27 16:48
From version 164.2
edited by Xiaoling
on 2022/11/28 15:32
Change comment: There is no comment for this version
To version 143.1
edited by Bei Jinggeng
on 2022/11/22 10:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:1664505654417-133.png||_mstalt="293696"]]
2 +[[image:1664505654417-133.png]]
3 3  
4 4  
5 5  
... ... @@ -14,6 +14,7 @@
14 14  
15 15  = 1.  Introduction =
16 16  
17 +
17 17  == 1.1  What is TrackerD ==
18 18  
19 19  
... ... @@ -31,17 +31,21 @@
31 31  (((
32 32  The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
33 33  )))
35 +)))
34 34  
35 35  (((
36 36  TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.
39 +
40 +
37 37  )))
38 38  
39 -[[image:1664499921684-770.png||_mstalt="298194"]]
43 +[[image:1664499921684-770.png]]
40 40  
41 41  
42 42  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
43 43  
44 44  
49 +
45 45  == 1.2 Specifications ==
46 46  
47 47  
... ... @@ -118,6 +118,7 @@
118 118  
119 119  = 2.  Use TrackerD =
120 120  
126 +
121 121  == 2.1 How it works? ==
122 122  
123 123  
... ... @@ -124,6 +124,7 @@
124 124  TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.
125 125  
126 126  
133 +
127 127  == 2.2 Quick guide to connect to LoRaWAN server ==
128 128  
129 129  
... ... @@ -130,7 +130,7 @@
130 130  Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example. 
131 131  
132 132  
133 -[[image:1664501652064-326.png||_mstalt="293306"]]
140 +[[image:1664501652064-326.png]]
134 134  
135 135  
136 136  
... ... @@ -142,7 +142,7 @@
142 142  Each TrackerD is shipped with a sticker with the default device EUI as below:
143 143  
144 144  
145 -[[image:1664501677253-891.png||_mstalt="296569"]]
152 +[[image:1664501677253-891.png]]
146 146  
147 147  
148 148  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -151,14 +151,14 @@
151 151  **__Add APP EUI in the application:__**
152 152  
153 153  
154 -[[image:1664501711466-918.png||_mstalt="295828"]]
161 +[[image:1664501711466-918.png]]
155 155  
156 156  
157 157  
158 -[[image:1664501721248-725.png||_mstalt="294450"]]
165 +[[image:1664501721248-725.png]]
159 159  
160 160  
161 -[[image:1664501734705-405.png||_mstalt="293306"]]
168 +[[image:1664501734705-405.png]]
162 162  
163 163  
164 164  
... ... @@ -165,20 +165,21 @@
165 165  **__Add APP KEY and DEV EUI:__**
166 166  
167 167  
168 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]]
175 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]]
169 169  
170 170  
171 171  
172 172  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
173 173  
174 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
181 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
175 175  
176 -[[image:1664502835802-546.png||_mstalt="295061"]]
183 +[[image:1664502835802-546.png]]
177 177  
178 178  
179 179  (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
180 180  
181 181  
189 +
182 182  == 2.3  Positioning Mode(SMOD) ==
183 183  
184 184  
... ... @@ -191,8 +191,10 @@
191 191  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
192 192  
193 193  
202 +
194 194  == 2.4  Uplink Payload ==
195 195  
205 +
196 196  === 2.4.1 Uplink FPORT~=5, Device Status ===
197 197  
198 198  
... ... @@ -205,7 +205,7 @@
205 205  |=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1
206 206  |=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
207 207  
208 -[[image:1665301570342-765.png||_mstalt="294580"]]
218 +[[image:1665301570342-765.png]]
209 209  
210 210  
211 211  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -272,7 +272,7 @@
272 272  
273 273  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
274 274  
275 -(% _mstmutation="1" style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
285 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
276 276  
277 277  
278 278  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -299,7 +299,7 @@
299 299  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
300 300  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
301 301  
302 -[[image:1665301636888-168.png||_mstalt="298012"]]
312 +[[image:1665301636888-168.png]]
303 303  
304 304  
305 305  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -329,12 +329,12 @@
329 329  2.  In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
330 330  
331 331  
332 -[[image:1664502116362-706.png||_mstalt="293306"]]
342 +[[image:1664502116362-706.png]]
333 333  
334 334  
335 335  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
336 336  
337 -[[image:1664502166010-515.png||_mstalt="291395"]]
347 +[[image:1664502166010-515.png]]
338 338  
339 339  
340 340  
... ... @@ -397,6 +397,7 @@
397 397  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
398 398  
399 399  
410 +
400 400  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
401 401  
402 402  
... ... @@ -412,13 +412,14 @@
412 412  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
413 413  
414 414  (% class="wikigeneratedid" %)
415 -[[image:1665301687277-443.png||_mstalt="296140"]]
426 +[[image:1665301687277-443.png]]
416 416  
417 417  
429 +
418 418  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
419 419  
420 420  
421 -Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
433 +Set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
422 422  
423 423  
424 424  (% style="color:red" %)**Note for this mode:**
... ... @@ -435,9 +435,10 @@
435 435  )))|4|4|2|1|1|1|1|1
436 436  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
437 437  
438 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
450 +[[image:image-20221009160309-2.png]]
439 439  
440 440  
453 +
441 441  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
442 442  
443 443  
... ... @@ -462,7 +462,7 @@
462 462  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
463 463  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
464 464  
465 -[[image:1664502425687-834.png||_mstalt="296738"]]
478 +[[image:1664502425687-834.png]]
466 466  
467 467  
468 468  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -488,7 +488,7 @@
488 488  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
489 489  
490 490  (% class="wikigeneratedid" %)
491 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
504 +[[image:1667288597595-714.png||height="212" width="1151"]]
492 492  
493 493  
494 494  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -495,8 +495,6 @@
495 495  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
496 496  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
497 497  
498 -
499 -
500 500  === 2.4.7  Add Payload format in TTN V3 ===
501 501  
502 502  
... ... @@ -505,10 +505,9 @@
505 505  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
506 506  
507 507  
508 -[[image:1664502649601-895.png||_mstalt="296985"]]
519 +[[image:1664502649601-895.png]]
509 509  
510 510  
511 -
512 512  Add the decoder from this link: 
513 513  
514 514  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -515,9 +515,10 @@
515 515  
516 516  Save the change the uplink message will be parsed. As below:
517 517  
518 -[[image:1664502676891-606.png||_mstalt="296673"]]
528 +[[image:1664502676891-606.png]]
519 519  
520 520  
531 +
521 521  == 2.5 Integrate with Datacake ==
522 522  
523 523  
... ... @@ -526,9 +526,10 @@
526 526  Instruction is here:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example~~-~~-AddTrackerDGPSTrackingInDataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example--AddTrackerDGPSTrackingInDataCake]]
527 527  
528 528  
529 -[[image:1664502695771-538.png||_mstalt="297349"]]
540 +[[image:1664502695771-538.png]]
530 530  
531 531  
543 +
532 532  == 2.6 Integrate with Tago ==
533 533  
534 534  
... ... @@ -537,24 +537,26 @@
537 537  Instruction is here: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget]]
538 538  
539 539  
540 -[[image:1664502715371-321.png||_mstalt="292162"]]
552 +[[image:1664502715371-321.png]]
541 541  
542 542  
555 +
543 543  == 2.7  Datalog Feature ==
544 544  
545 545  
546 546  total 273 entries,by default,
547 547  
548 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
561 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
549 549  
550 550  Example use case.
551 551  
552 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
565 +[[image:image-20221009234703-2.png||height="328" width="899"]]
553 553  
554 554  
555 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
568 +[[image:image-20221009234629-1.png||height="390" width="577"]]
556 556  
557 557  
571 +
558 558  == 2.8 Alarm Mode ==
559 559  
560 560  
... ... @@ -569,7 +569,7 @@
569 569  
570 570  
571 571  (((
572 -**Two ways to exit alarm mode:**
586 +Two ways to exit alarm mode:
573 573  )))
574 574  
575 575  * Server sends a downlink command to exit.
... ... @@ -580,15 +580,14 @@
580 580  )))
581 581  
582 582  
597 +
583 583  == 2.9 Transport Mode ==
584 584  
585 585  
586 586  In Transport Mode, TrackerD will check if there is motion. If there is no motion, device will send uplinks every 20 minutes. If there is motion, device will send uplink every 5 minutes.
587 587  
588 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
589 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
590 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
591 591  
604 +
592 592  == 2.10 LED Status ==
593 593  
594 594  
... ... @@ -611,7 +611,7 @@
611 611  
612 612  (% style="color:blue" %)**RESET button:**
613 613  
614 -[[image:1664502835802-546.png||_mstalt="295061"]]
627 +[[image:1664502835802-546.png]]
615 615  
616 616  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
617 617  
... ... @@ -618,7 +618,7 @@
618 618  
619 619  (% style="color:red" %)**RED button:**
620 620  
621 -[[image:1664502854406-763.png||_mstalt="295568"]]
634 +[[image:1664502854406-763.png]]
622 622  
623 623  
624 624  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -645,6 +645,7 @@
645 645  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
646 646  
647 647  
661 +
648 648  == 3.1 Access AT Command ==
649 649  
650 650  
... ... @@ -651,23 +651,25 @@
651 651  TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below.
652 652  
653 653  
654 -[[image:1664502999401-486.png||_mstalt="296985"]]
668 +[[image:1664502999401-486.png]]
655 655  
656 656  
657 657  In PC, User needs to set serial tool baud rate to (% style="color:green" %)**115200**(%%) to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands:
658 658  
659 659  
660 -[[image:1664503022490-662.png||_mstalt="293332"]]
674 +[[image:1664503022490-662.png]]
661 661  
662 662  
663 -[[image:1664503035713-500.png||_mstalt="291096"]]
677 +[[image:1664503035713-500.png]]
664 664  
665 665  
666 -[[image:1664503047675-651.png||_mstalt="295386"]]
680 +[[image:1664503047675-651.png]]
667 667  
668 668  
683 +
669 669  == 3.2 Command Set ==
670 670  
686 +
671 671  === 3.2.1 Set Transmit Interval ===
672 672  
673 673  
... ... @@ -685,6 +685,7 @@
685 685  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
686 686  
687 687  
704 +
688 688  === 3.2.2 Set Alarm Packet transmission interval ===
689 689  
690 690  
... ... @@ -702,6 +702,7 @@
702 702  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
703 703  
704 704  
722 +
705 705  === 3.2.3 Set Transport Mode Packet transmission interval ===
706 706  
707 707  
... ... @@ -719,6 +719,7 @@
719 719  (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
720 720  
721 721  
740 +
722 722  === 3.2.4 Exit Alarm ===
723 723  
724 724  
... ... @@ -731,6 +731,7 @@
731 731  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
732 732  
733 733  
753 +
734 734  === 3.2.5 Disable/Enable LED flash ===
735 735  
736 736  
... ... @@ -748,6 +748,7 @@
748 748  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
749 749  
750 750  
771 +
751 751  === 3.2.6 Disable/Enable Transport Mode ===
752 752  
753 753  
... ... @@ -765,6 +765,7 @@
765 765  (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
766 766  
767 767  
789 +
768 768  === 3.2.7 Set Positioning Mode ===
769 769  
770 770  
... ... @@ -791,9 +791,9 @@
791 791  
792 792  (% style="color:#037691" %)**cc:   **
793 793  
794 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
816 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
795 795  
796 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
818 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
797 797  
798 798  (% style="color:blue" %)**Example:**
799 799  
... ... @@ -811,6 +811,7 @@
811 811  (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
812 812  
813 813  
836 +
814 814  === 3.2.8 Set MAX GPS position time ===
815 815  
816 816  
... ... @@ -817,7 +817,7 @@
817 817  Set max positioning time, default is 150 seconds. TrackerD will try to get location info within this period. If fail to get position data within this time, TrackerD will use 000000 for latitude and longitude.
818 818  
819 819  
820 -If **AT+FTIME=0**. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.
843 +If AT+FTIME=0. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.
821 821  
822 822  
823 823  * (% style="color:blue" %)**AT Command:**
... ... @@ -832,6 +832,7 @@
832 832  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
833 833  
834 834  
858 +
835 835  === 3.2.9 Set PDOP value for GPS fix accuracy ===
836 836  
837 837  
... ... @@ -856,9 +856,8 @@
856 856  
857 857  
858 858  
859 -=== 3.2.10 Disable/Enable the confirmation mode ===
883 +Disable/Enable the confirmation mode
860 860  
861 -
862 862  * (% style="color:blue" %)**AT Command:**
863 863  
864 864  (% style="color:#037691" %)**AT+CFM=xx**
... ... @@ -876,9 +876,10 @@
876 876  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
877 877  
878 878  
879 -=== 3.2.11  Auto Send None-ACK messages ===
880 880  
903 +=== 3.2.10  Auto Send None-ACK messages ===
881 881  
905 +
882 882  TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
883 883  
884 884  
... ... @@ -894,12 +894,13 @@
894 894  
895 895  * (% style="color:blue" %)**Downlink Command: 0x34**
896 896  
897 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
921 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
898 898  
899 899  
900 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
901 901  
925 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
902 902  
927 +
903 903  BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
904 904  
905 905  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -906,18 +906,19 @@
906 906  
907 907  (% style="color:blue" %)**AT Command:**
908 908  
909 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
934 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
910 910  
911 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
936 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
912 912  
913 913  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
914 914  
915 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
940 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
916 916  
917 917  
918 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
919 919  
944 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
920 920  
946 +
921 921  WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456 as prefix. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
922 922  
923 923  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
... ... @@ -924,18 +924,19 @@
924 924  
925 925  (% style="color:blue" %)**AT Command:**
926 926  
927 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
953 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
928 928  
929 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
955 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
930 930  
931 931  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
932 932  
933 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
959 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
934 934  
935 935  
936 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
937 937  
963 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
938 938  
965 +
939 939  Users can use this feature to enable/disable Information printing.
940 940  
941 941  (% style="color:blue" %)**AT Command:**
... ... @@ -944,9 +944,10 @@
944 944  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
945 945  
946 946  
947 -=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
948 948  
975 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
949 949  
977 +
950 950  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
951 951  
952 952  (% style="color:blue" %)**AT Command:**
... ... @@ -959,26 +959,7 @@
959 959  Example: 0x24 01 ~/~/ Same as AT+CHE=1
960 960  
961 961  
962 -=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
963 963  
964 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
965 -
966 -(% style="color:blue" %)**AT Command:**
967 -
968 -(% style="color:#037691" %)**AT+PT=xx**
969 -
970 - Example:
971 -
972 - AT+PT=14    ~-~->    Set to detect car motion.
973 -
974 - AT+PT=41   ~-~->    set to detect walk motion.
975 -
976 -
977 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
978 -0xB4 14          ~/~/  Same as AT+PT=14
979 -
980 -
981 -
982 982  = 4. Setting for Different Scenarios =
983 983  
984 984  
... ... @@ -985,6 +985,7 @@
985 985  
986 986  = 5. Upload Firmware =
987 987  
997 +
988 988  == 5.1 Firmware Change Log ==
989 989  
990 990  
... ... @@ -991,6 +991,7 @@
991 991  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
992 992  
993 993  
1004 +
994 994  == 5.2 How to upgrade firmware ==
995 995  
996 996  
... ... @@ -1011,10 +1011,10 @@
1011 1011  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1012 1012  
1013 1013  
1014 -[[image:1664503563660-578.png||_mstalt="296777"]]
1025 +[[image:1664503563660-578.png]]
1015 1015  
1016 1016  
1017 -[[image:1664503574618-659.png||_mstalt="297986"]]
1028 +[[image:1664503574618-659.png]]
1018 1018  
1019 1019  
1020 1020  
... ... @@ -1023,7 +1023,7 @@
1023 1023  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1024 1024  
1025 1025  
1026 -**Users need to use below files:**
1037 +Users need to use below files:
1027 1027  
1028 1028  boot_app0.bin @0e000
1029 1029  
... ... @@ -1030,20 +1030,22 @@
1030 1030  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1031 1031  
1032 1032  
1033 -[[image:image-20221118105220-2.png||_mstalt="426608"]]
1044 +[[image:image-20221118105220-2.png]]
1034 1034  
1035 1035  
1036 1036  
1037 1037  After upgrade finish, it will show finish as below:
1038 1038  
1039 -[[image:image-20221118105402-4.png||_mstalt="427986"]]
1050 +[[image:image-20221118105402-4.png]]
1040 1040  
1041 1041  
1042 1042  
1043 1043  = 6. Developer Guide =
1044 1044  
1056 +
1045 1045  == 6.1 Compile Source Code ==
1046 1046  
1059 +
1047 1047  === 6.1.1 Set up ARDUINO compile environment ===
1048 1048  
1049 1049  
... ... @@ -1052,23 +1052,23 @@
1052 1052  Install IDE on PC, open and click (% style="color:#037691" %)**File ~-~-> Preference**,(%%) add the following URL:  [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fdl.espressif.com%2Fdl%2Fpackage_esp32_index.json]]
1053 1053  
1054 1054  
1055 -[[image:1664503635019-941.png||_mstalt="294658"]]
1068 +[[image:1664503635019-941.png]]
1056 1056  
1057 1057  
1058 1058  
1059 1059  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1060 1060  
1061 -[[image:1664503715811-892.png||_mstalt="295698"]]
1074 +[[image:1664503715811-892.png]]
1062 1062  
1063 1063  
1064 1064  (% id="cke_bm_4554S" style="display:none" %) (%%)Find the path of SP32 installation, find the file as shown in Figure 1, and change the SPI pin to the shown in Figure 2.
1065 1065  
1066 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1079 +[[image:image-20221024105643-1.png]]
1067 1067  
1068 1068  **~ Figure1**
1069 1069  
1070 1070  
1071 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1084 +[[image:image-20221024105643-2.png]]
1072 1072  
1073 1073   **Figure2**
1074 1074  
... ... @@ -1078,31 +1078,34 @@
1078 1078  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1079 1079  
1080 1080  
1081 -[[image:1664503752288-974.png||_mstalt="298194"]]
1094 +[[image:1664503752288-974.png]]
1082 1082  
1083 1083  
1097 +
1084 1084  == 6.2 Source Code ==
1085 1085  
1086 1086  
1087 1087  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1088 1088  
1089 -[[image:1664503794261-827.png||_mstalt="296387"]]
1103 +[[image:1664503794261-827.png]]
1090 1090  
1091 1091  
1092 1092  
1093 1093  * (% style="color:blue" %)**Click to upload**
1094 1094  
1095 -[[image:1664503808294-336.png||_mstalt="295711"]]
1109 +[[image:1664503808294-336.png]]
1096 1096  
1097 1097  
1098 1098  
1099 1099  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1100 1100  
1101 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1115 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1102 1102  
1103 1103  
1118 +
1104 1104  = 7.  FAQ =
1105 1105  
1121 +
1106 1106  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1107 1107  
1108 1108  
... ... @@ -1109,10 +1109,11 @@
1109 1109  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1110 1110  
1111 1111  
1128 +
1112 1112  == 7.2 What is the pin mapping for the USB program cable? ==
1113 1113  
1114 1114  
1115 -[[image:1664499635206-262.png||_mstalt="295360"]]
1132 +[[image:1664499635206-262.png]]
1116 1116  
1117 1117  
1118 1118  
... ... @@ -1129,6 +1129,7 @@
1129 1129  
1130 1130  == 7.3 Notes on using different serial port tools for TrackerD ==
1131 1131  
1149 +
1132 1132  === 7.3.1  Serial port utility ===
1133 1133  
1134 1134  
... ... @@ -1136,16 +1136,18 @@
1136 1136  
1137 1137  Need to adjust the data stream to RTS/CTS on physical restart.
1138 1138  
1157 +
1139 1139  (% class="wikigeneratedid" %)
1140 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1159 +[[image:image-20221102140621-1.png]]
1141 1141  
1142 1142  
1143 -
1144 1144  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1145 1145  
1146 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1147 1147  
1165 +[[image:image-20221102140638-2.png]]
1148 1148  
1167 +
1168 +
1149 1149  === 7.3.2  SecureCRT ===
1150 1150  
1151 1151  
... ... @@ -1152,22 +1152,23 @@
1152 1152  The default command window of SecureCRT is not displayed. Entering a command requires a complete input of the entire command. You can open the command window in the view.
1153 1153  
1154 1154  
1155 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1175 +[[image:image-20221102140704-3.png]]
1156 1156  
1157 1157  
1158 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1178 +[[image:image-20221102140712-4.png]]
1159 1159  
1160 1160  
1181 +
1161 1161  === 7.3.3  PUTTY ===
1162 1162  
1163 1163  
1164 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1185 +[[image:image-20221102140748-5.png]]
1165 1165  
1166 1166  
1167 1167  Since putty does not have a command window, you need to fill in the complete command externally, and then copy it to putty.The information copied outside can be pasted by right-clicking the mouse in putty.
1168 1168  
1169 1169  
1170 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1191 +[[image:image-20221102140801-6.png]]
1171 1171  
1172 1172  
1173 1173  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1179,46 +1179,38 @@
1179 1179  See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1180 1180  )))
1181 1181  
1182 -**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1203 +1.When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.
1183 1183  
1205 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1184 1184  
1185 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1207 +2.Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).
1186 1186  
1209 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1187 1187  
1211 +3.Compile the AS923_JP band, please refer to the intention shown
1188 1188  
1189 -**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1213 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1190 1190  
1215 +4.In other frequency bands in AS923, you need to find Lorabase_as923.H, path arduino-lmic \ src \ lmic, as shown in the figure below.
1191 1191  
1192 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1217 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1193 1193  
1219 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1194 1194  
1195 1195  
1196 -**3. Compile the AS923_JP band, please refer to the intention shown**
1197 1197  
1198 -
1199 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1200 -
1201 -
1202 -
1203 -**4. In other frequency bands in AS923, you need to find Lorabase_as923.H, path arduino-lmic \ src \ lmic, as shown in the figure below.**
1204 -
1205 -
1206 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1207 -
1208 -
1209 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1210 -
1211 -
1212 1212  = 8  Trouble Shooting =
1213 1213  
1225 +
1214 1214  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1215 1215  
1216 1216  
1217 1217  (((
1218 -Before firmware v1.4.0: When the Transport Mode is enabled ((% style="color:blue" %)**AT+INTWK=1**(%%)), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1230 +Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1219 1219  )))
1220 1220  
1221 1221  
1234 +
1222 1222  == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1223 1223  
1224 1224  
... ... @@ -1227,138 +1227,85 @@
1227 1227  )))
1228 1228  
1229 1229  
1243 +
1230 1230  == 8.3  Problem after Upgrading Firmware ==
1231 1231  
1232 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1246 +=== 8.3.1 Continue Restart after upgrading ===
1233 1233  
1234 1234  
1235 -**Error Output**
1236 -
1237 -
1238 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1239 -
1240 -
1241 1241  (((
1242 -Some partition is missed during upgrade, please upgrade below four files as example:
1243 -
1244 -[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1250 +If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
1245 1245  )))
1246 1246  
1247 1247  
1248 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1254 +[[image:image-20221118105249-3.png]]
1249 1249  
1250 1250  
1257 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1258 +
1251 1251  It is because the partitions are different when upgrading versions above 1.4.1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1
1252 1252  
1253 1253  
1254 -=== 8.3.3 "flash read err" after upgrade firmware ===
1262 +==== 8.3.2.1 If there is a situation in Figure 1,and a new partition file and bootloader file needs to be added. Please refer to the operation steps in Figure 2 ====
1255 1255  
1264 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1256 1256  
1257 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1266 + Figure 1  
1258 1258  
1268 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1259 1259  
1260 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1270 + Figure 2
1261 1261  
1272 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1262 1262  
1263 -User need to upgrade again with below four files to solve this issue.
1274 +[[image:image-20221122100004-3.png]]
1264 1264  
1265 - [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1276 +Please AT+FDR, and then enter the following instructions by the information on the label
1266 1266  
1267 - **Figure 2**
1278 +AT+DEUI=70B3D57ED0053981
1268 1268  
1269 -
1270 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1271 -
1272 -
1273 -User might erase the entire flash include keys and default settings which cause this issue.
1274 -
1275 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1276 -
1277 -
1278 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1279 -
1280 -
1281 -Please (% style="color:blue" %)**AT+FDR**(%%) which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1282 -
1283 -After AT+FDR. please set
1284 -
1285 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1286 -
1287 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1288 -
1289 -**Example:**
1290 -
1291 -AT+PDOP=7.00
1292 -
1293 -AT+FTIME=180
1294 -
1295 -AT+DEUI=70B3D57ED0053981  
1296 -
1297 1297  AT+APPEUI=D23345667BCBCCAF
1298 1298  
1299 1299  AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1300 1300  
1301 -AT+DADDR=260b4dce    ( no need for OTAA)
1284 +AT+DADDR=260b4dce
1302 1302  
1303 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1286 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1304 1304  
1305 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1288 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1306 1306  
1307 1307  
1308 -== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1309 1309  
1292 +==== 8.3.2.2 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ====
1310 1310  
1311 -Please download version 1.4.2 again
1294 +[[image:image-20221122100004-4.png]]
1312 1312  
1296 +== ==
1313 1313  
1314 -== 8.5  How to deal with unsuccessful GPS positioning? ==
1298 +== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==
1315 1315  
1300 +Please download version 1.4.2 again
1316 1316  
1317 -1） Make Sure the device is in Open Area where can see the sky.
1318 1318  
1303 +(((
1304 +== 8.5 How to deal with unsuccessful GPS positioning? ==
1305 +
1306 +1） Make Sure the device is in Open Area where can see the sky. 
1319 1319  2)  Set PDOP to a higher value.
1320 1320  
1321 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1309 + AT+PDOP=2(can be positioned precisely.）
1322 1322  
1323 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1311 + AT+PDOP=7(Quickly locate in open spaces）
1324 1324  
1325 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1313 + AT+PDOP=14.7(Positioning can be acquired in complex environments）
1326 1326  
1327 1327  Please refer to this [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H3.2.9SetPDOPvalueforGPSfixaccuracy]] on how to set up PDOP
1316 +)))
1328 1328  
1329 1329  
1330 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1319 +== ==
1331 1331  
1332 -When upgrading, use the erase button to upgrade
1333 1333  
1334 -[[image:image-20221128102938-1.png||height="537" width="335"]]
1335 -
1336 -
1337 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1338 -
1339 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1340 -
1341 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1342 -
1343 -[[image:image-20221128110503-3.png||height="647" width="410"]]
1344 -
1345 -Reboot information after upgrade
1346 -
1347 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1348 -
1349 -Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal
1350 -
1351 -[[image:image-20221128111850-5.png]]
1352 -
1353 -After the parameters return to normal, upgrade to the version you need again
1354 -
1355 -[[image:image-20221128111951-6.png||height="620" width="389"]]
1356 -
1357 -At this point, the parameters return to normal after running AT+FDR again
1358 -
1359 -[[image:image-20221128112035-7.png]]
1360 -
1361 -
1362 1362  = 9.  Order Info =
1363 1363  
1364 1364  
... ... @@ -1367,17 +1367,11 @@
1367 1367  (% style="color:blue" %)**XXX**(%%): The default frequency band
1368 1368  
1369 1369  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1370 -
1371 1371  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1372 -
1373 1373  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1374 -
1375 1375  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1376 -
1377 1377  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1378 -
1379 1379  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1380 -
1381 1381  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1382 1382  
1383 1383  = 10.  Packing Info =
... ... @@ -1386,13 +1386,11 @@
1386 1386  (% style="color:#037691" %)**Package Includes**:
1387 1387  
1388 1388  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1389 -
1390 1390  * USB recharge & program cable x 1
1391 1391  
1392 1392  (% style="color:#037691" %)**Dimensions and Weight**:
1393 1393  
1394 1394  * Device Size: 85 x 48 x 15 mm
1395 -
1396 1396  * Weight: 50g
1397 1397  
1398 1398  = 11. Support =
... ... @@ -1399,7 +1399,6 @@
1399 1399  
1400 1400  
1401 1401  * 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.
1402 -
1403 1403  * 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:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].
1404 1404  
1405 1405  = 12.  Reference =
... ... @@ -1406,8 +1406,5 @@
1406 1406  
1407 1407  
1408 1408  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1409 -
1410 1410  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1411 -
1412 1412  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1413 -)))
image-20221128102938-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -41.3 KB
Content
image-20221128103040-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -19.2 KB
Content
image-20221128110503-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.6 KB
Content
image-20221128111443-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -15.6 KB
Content
image-20221128111850-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.5 KB
Content
image-20221128111951-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.4 KB
Content
image-20221128112035-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.7 KB
Content