Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 153.1
edited by Edwin Chen
on 2022/11/24 09:16
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.Edwin
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  
... ... @@ -39,12 +39,13 @@
39 39  
40 40  )))
41 41  
42 -[[image:1664499921684-770.png||_mstalt="298194"]]
43 +[[image:1664499921684-770.png]]
43 43  
44 44  
45 45  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
46 46  
47 47  
49 +
48 48  == 1.2 Specifications ==
49 49  
50 50  
... ... @@ -121,6 +121,7 @@
121 121  
122 122  = 2.  Use TrackerD =
123 123  
126 +
124 124  == 2.1 How it works? ==
125 125  
126 126  
... ... @@ -127,6 +127,7 @@
127 127  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.
128 128  
129 129  
133 +
130 130  == 2.2 Quick guide to connect to LoRaWAN server ==
131 131  
132 132  
... ... @@ -133,7 +133,7 @@
133 133  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. 
134 134  
135 135  
136 -[[image:1664501652064-326.png||_mstalt="293306"]]
140 +[[image:1664501652064-326.png]]
137 137  
138 138  
139 139  
... ... @@ -145,7 +145,7 @@
145 145  Each TrackerD is shipped with a sticker with the default device EUI as below:
146 146  
147 147  
148 -[[image:1664501677253-891.png||_mstalt="296569"]]
152 +[[image:1664501677253-891.png]]
149 149  
150 150  
151 151  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -154,14 +154,14 @@
154 154  **__Add APP EUI in the application:__**
155 155  
156 156  
157 -[[image:1664501711466-918.png||_mstalt="295828"]]
161 +[[image:1664501711466-918.png]]
158 158  
159 159  
160 160  
161 -[[image:1664501721248-725.png||_mstalt="294450"]]
165 +[[image:1664501721248-725.png]]
162 162  
163 163  
164 -[[image:1664501734705-405.png||_mstalt="293306"]]
168 +[[image:1664501734705-405.png]]
165 165  
166 166  
167 167  
... ... @@ -168,20 +168,21 @@
168 168  **__Add APP KEY and DEV EUI:__**
169 169  
170 170  
171 -[[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"]]
172 172  
173 173  
174 174  
175 175  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
176 176  
177 -(% 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]]
178 178  
179 -[[image:1664502835802-546.png||_mstalt="295061"]]
183 +[[image:1664502835802-546.png]]
180 180  
181 181  
182 182  (% 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.
183 183  
184 184  
189 +
185 185  == 2.3  Positioning Mode(SMOD) ==
186 186  
187 187  
... ... @@ -194,8 +194,10 @@
194 194  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
195 195  
196 196  
202 +
197 197  == 2.4  Uplink Payload ==
198 198  
205 +
199 199  === 2.4.1 Uplink FPORT~=5, Device Status ===
200 200  
201 201  
... ... @@ -208,7 +208,7 @@
208 208  |=(% 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
209 209  |=(% 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
210 210  
211 -[[image:1665301570342-765.png||_mstalt="294580"]]
218 +[[image:1665301570342-765.png]]
212 212  
213 213  
214 214  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -275,7 +275,7 @@
275 275  
276 276  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
277 277  
278 -(% _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)(%%)  
279 279  
280 280  
281 281  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -302,7 +302,7 @@
302 302  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
303 303  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
304 304  
305 -[[image:1665301636888-168.png||_mstalt="298012"]]
312 +[[image:1665301636888-168.png]]
306 306  
307 307  
308 308  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -332,12 +332,12 @@
332 332  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:
333 333  
334 334  
335 -[[image:1664502116362-706.png||_mstalt="293306"]]
342 +[[image:1664502116362-706.png]]
336 336  
337 337  
338 338  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
339 339  
340 -[[image:1664502166010-515.png||_mstalt="291395"]]
347 +[[image:1664502166010-515.png]]
341 341  
342 342  
343 343  
... ... @@ -400,6 +400,7 @@
400 400  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
401 401  
402 402  
410 +
403 403  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
404 404  
405 405  
... ... @@ -415,9 +415,10 @@
415 415  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
416 416  
417 417  (% class="wikigeneratedid" %)
418 -[[image:1665301687277-443.png||_mstalt="296140"]]
426 +[[image:1665301687277-443.png]]
419 419  
420 420  
429 +
421 421  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
422 422  
423 423  
... ... @@ -438,9 +438,10 @@
438 438  )))|4|4|2|1|1|1|1|1
439 439  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
440 440  
441 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
450 +[[image:image-20221009160309-2.png]]
442 442  
443 443  
453 +
444 444  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
445 445  
446 446  
... ... @@ -465,7 +465,7 @@
465 465  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
466 466  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
467 467  
468 -[[image:1664502425687-834.png||_mstalt="296738"]]
478 +[[image:1664502425687-834.png]]
469 469  
470 470  
471 471  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -491,7 +491,7 @@
491 491  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
492 492  
493 493  (% class="wikigeneratedid" %)
494 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
504 +[[image:1667288597595-714.png||height="212" width="1151"]]
495 495  
496 496  
497 497  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -506,10 +506,9 @@
506 506  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
507 507  
508 508  
509 -[[image:1664502649601-895.png||_mstalt="296985"]]
519 +[[image:1664502649601-895.png]]
510 510  
511 511  
512 -
513 513  Add the decoder from this link: 
514 514  
515 515  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -516,9 +516,10 @@
516 516  
517 517  Save the change the uplink message will be parsed. As below:
518 518  
519 -[[image:1664502676891-606.png||_mstalt="296673"]]
528 +[[image:1664502676891-606.png]]
520 520  
521 521  
531 +
522 522  == 2.5 Integrate with Datacake ==
523 523  
524 524  
... ... @@ -527,9 +527,10 @@
527 527  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]]
528 528  
529 529  
530 -[[image:1664502695771-538.png||_mstalt="297349"]]
540 +[[image:1664502695771-538.png]]
531 531  
532 532  
543 +
533 533  == 2.6 Integrate with Tago ==
534 534  
535 535  
... ... @@ -538,9 +538,10 @@
538 538  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]]
539 539  
540 540  
541 -[[image:1664502715371-321.png||_mstalt="292162"]]
552 +[[image:1664502715371-321.png]]
542 542  
543 543  
555 +
544 544  == 2.7  Datalog Feature ==
545 545  
546 546  
... ... @@ -550,12 +550,13 @@
550 550  
551 551  Example use case.
552 552  
553 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
565 +[[image:image-20221009234703-2.png||height="328" width="899"]]
554 554  
555 555  
556 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
568 +[[image:image-20221009234629-1.png||height="390" width="577"]]
557 557  
558 558  
571 +
559 559  == 2.8 Alarm Mode ==
560 560  
561 561  
... ... @@ -570,7 +570,7 @@
570 570  
571 571  
572 572  (((
573 -**Two ways to exit alarm mode:**
586 +Two ways to exit alarm mode:
574 574  )))
575 575  
576 576  * Server sends a downlink command to exit.
... ... @@ -581,14 +581,12 @@
581 581  )))
582 582  
583 583  
597 +
584 584  == 2.9 Transport Mode ==
585 585  
586 586  
587 587  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.
588 588  
589 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
590 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
591 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
592 592  
593 593  
594 594  == 2.10 LED Status ==
... ... @@ -613,7 +613,7 @@
613 613  
614 614  (% style="color:blue" %)**RESET button:**
615 615  
616 -[[image:1664502835802-546.png||_mstalt="295061"]]
627 +[[image:1664502835802-546.png]]
617 617  
618 618  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
619 619  
... ... @@ -620,7 +620,7 @@
620 620  
621 621  (% style="color:red" %)**RED button:**
622 622  
623 -[[image:1664502854406-763.png||_mstalt="295568"]]
634 +[[image:1664502854406-763.png]]
624 624  
625 625  
626 626  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -647,6 +647,7 @@
647 647  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
648 648  
649 649  
661 +
650 650  == 3.1 Access AT Command ==
651 651  
652 652  
... ... @@ -653,24 +653,25 @@
653 653  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.
654 654  
655 655  
656 -[[image:1664502999401-486.png||_mstalt="296985"]]
668 +[[image:1664502999401-486.png]]
657 657  
658 658  
659 659  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:
660 660  
661 661  
662 -[[image:1664503022490-662.png||_mstalt="293332"]]
674 +[[image:1664503022490-662.png]]
663 663  
664 664  
665 -[[image:1664503035713-500.png||_mstalt="291096"]]
677 +[[image:1664503035713-500.png]]
666 666  
667 667  
668 -[[image:1664503047675-651.png||_mstalt="295386"]]
680 +[[image:1664503047675-651.png]]
669 669  
670 670  
671 671  
672 672  == 3.2 Command Set ==
673 673  
686 +
674 674  === 3.2.1 Set Transmit Interval ===
675 675  
676 676  
... ... @@ -688,6 +688,7 @@
688 688  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
689 689  
690 690  
704 +
691 691  === 3.2.2 Set Alarm Packet transmission interval ===
692 692  
693 693  
... ... @@ -705,6 +705,7 @@
705 705  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
706 706  
707 707  
722 +
708 708  === 3.2.3 Set Transport Mode Packet transmission interval ===
709 709  
710 710  
... ... @@ -722,6 +722,7 @@
722 722  (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
723 723  
724 724  
740 +
725 725  === 3.2.4 Exit Alarm ===
726 726  
727 727  
... ... @@ -734,6 +734,7 @@
734 734  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
735 735  
736 736  
753 +
737 737  === 3.2.5 Disable/Enable LED flash ===
738 738  
739 739  
... ... @@ -751,6 +751,7 @@
751 751  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
752 752  
753 753  
771 +
754 754  === 3.2.6 Disable/Enable Transport Mode ===
755 755  
756 756  
... ... @@ -768,6 +768,7 @@
768 768  (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
769 769  
770 770  
789 +
771 771  === 3.2.7 Set Positioning Mode ===
772 772  
773 773  
... ... @@ -794,9 +794,9 @@
794 794  
795 795  (% style="color:#037691" %)**cc:   **
796 796  
797 -* (% _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  
798 798  
799 -* (% _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(%%))  
800 800  
801 801  (% style="color:blue" %)**Example:**
802 802  
... ... @@ -814,6 +814,7 @@
814 814  (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
815 815  
816 816  
836 +
817 817  === 3.2.8 Set MAX GPS position time ===
818 818  
819 819  
... ... @@ -820,7 +820,7 @@
820 820  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.
821 821  
822 822  
823 -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.
824 824  
825 825  
826 826  * (% style="color:blue" %)**AT Command:**
... ... @@ -835,6 +835,7 @@
835 835  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
836 836  
837 837  
858 +
838 838  === 3.2.9 Set PDOP value for GPS fix accuracy ===
839 839  
840 840  
... ... @@ -859,7 +859,7 @@
859 859  
860 860  
861 861  
862 -=== 3.2.10 Disable/Enable the confirmation mode ===
883 +Disable/Enable the confirmation mode
863 863  
864 864  * (% style="color:blue" %)**AT Command:**
865 865  
... ... @@ -878,9 +878,10 @@
878 878  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
879 879  
880 880  
881 -=== 3.2.11  Auto Send None-ACK messages ===
882 882  
903 +=== 3.2.10  Auto Send None-ACK messages ===
883 883  
905 +
884 884  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.
885 885  
886 886  
... ... @@ -896,12 +896,13 @@
896 896  
897 897  * (% style="color:blue" %)**Downlink Command: 0x34**
898 898  
899 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
921 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
900 900  
901 901  
902 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
903 903  
925 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
904 904  
927 +
905 905  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.
906 906  
907 907  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -908,18 +908,19 @@
908 908  
909 909  (% style="color:blue" %)**AT Command:**
910 910  
911 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
934 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
912 912  
913 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
936 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
914 914  
915 915  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
916 916  
917 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
940 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
918 918  
919 919  
920 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
921 921  
944 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
922 922  
946 +
923 923  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.
924 924  
925 925  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
... ... @@ -926,18 +926,19 @@
926 926  
927 927  (% style="color:blue" %)**AT Command:**
928 928  
929 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
953 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
930 930  
931 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
955 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
932 932  
933 933  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
934 934  
935 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
959 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
936 936  
937 937  
938 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
939 939  
963 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
940 940  
965 +
941 941  Users can use this feature to enable/disable Information printing.
942 942  
943 943  (% style="color:blue" %)**AT Command:**
... ... @@ -946,9 +946,10 @@
946 946  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
947 947  
948 948  
949 -=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
950 950  
975 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
951 951  
977 +
952 952  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
953 953  
954 954  (% style="color:blue" %)**AT Command:**
... ... @@ -961,26 +961,7 @@
961 961  Example: 0x24 01 ~/~/ Same as AT+CHE=1
962 962  
963 963  
964 -=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
965 965  
966 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
967 -
968 -(% style="color:blue" %)**AT Command:**
969 -
970 -(% style="color:#037691" %)**AT+PT=xx**
971 -
972 - Example:
973 -
974 - AT+PT=14    ~-~->    Set to detect car motion.
975 -
976 - AT+PT=41   ~-~->    set to detect walk motion.
977 -
978 -
979 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
980 -0xB4 14          ~/~/  Same as AT+PT=14
981 -
982 -
983 -
984 984  = 4. Setting for Different Scenarios =
985 985  
986 986  
... ... @@ -987,6 +987,7 @@
987 987  
988 988  = 5. Upload Firmware =
989 989  
997 +
990 990  == 5.1 Firmware Change Log ==
991 991  
992 992  
... ... @@ -993,6 +993,7 @@
993 993  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
994 994  
995 995  
1004 +
996 996  == 5.2 How to upgrade firmware ==
997 997  
998 998  
... ... @@ -1013,10 +1013,10 @@
1013 1013  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1014 1014  
1015 1015  
1016 -[[image:1664503563660-578.png||_mstalt="296777"]]
1025 +[[image:1664503563660-578.png]]
1017 1017  
1018 1018  
1019 -[[image:1664503574618-659.png||_mstalt="297986"]]
1028 +[[image:1664503574618-659.png]]
1020 1020  
1021 1021  
1022 1022  
... ... @@ -1025,7 +1025,7 @@
1025 1025  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1026 1026  
1027 1027  
1028 -**Users need to use below files:**
1037 +Users need to use below files:
1029 1029  
1030 1030  boot_app0.bin @0e000
1031 1031  
... ... @@ -1032,20 +1032,22 @@
1032 1032  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1033 1033  
1034 1034  
1035 -[[image:image-20221118105220-2.png||_mstalt="426608"]]
1044 +[[image:image-20221118105220-2.png]]
1036 1036  
1037 1037  
1038 1038  
1039 1039  After upgrade finish, it will show finish as below:
1040 1040  
1041 -[[image:image-20221118105402-4.png||_mstalt="427986"]]
1050 +[[image:image-20221118105402-4.png]]
1042 1042  
1043 1043  
1044 1044  
1045 1045  = 6. Developer Guide =
1046 1046  
1056 +
1047 1047  == 6.1 Compile Source Code ==
1048 1048  
1059 +
1049 1049  === 6.1.1 Set up ARDUINO compile environment ===
1050 1050  
1051 1051  
... ... @@ -1054,23 +1054,23 @@
1054 1054  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]]
1055 1055  
1056 1056  
1057 -[[image:1664503635019-941.png||_mstalt="294658"]]
1068 +[[image:1664503635019-941.png]]
1058 1058  
1059 1059  
1060 1060  
1061 1061  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1062 1062  
1063 -[[image:1664503715811-892.png||_mstalt="295698"]]
1074 +[[image:1664503715811-892.png]]
1064 1064  
1065 1065  
1066 1066  (% 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.
1067 1067  
1068 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1079 +[[image:image-20221024105643-1.png]]
1069 1069  
1070 1070  **~ Figure1**
1071 1071  
1072 1072  
1073 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1084 +[[image:image-20221024105643-2.png]]
1074 1074  
1075 1075   **Figure2**
1076 1076  
... ... @@ -1080,31 +1080,34 @@
1080 1080  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1081 1081  
1082 1082  
1083 -[[image:1664503752288-974.png||_mstalt="298194"]]
1094 +[[image:1664503752288-974.png]]
1084 1084  
1085 1085  
1097 +
1086 1086  == 6.2 Source Code ==
1087 1087  
1088 1088  
1089 1089  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1090 1090  
1091 -[[image:1664503794261-827.png||_mstalt="296387"]]
1103 +[[image:1664503794261-827.png]]
1092 1092  
1093 1093  
1094 1094  
1095 1095  * (% style="color:blue" %)**Click to upload**
1096 1096  
1097 -[[image:1664503808294-336.png||_mstalt="295711"]]
1109 +[[image:1664503808294-336.png]]
1098 1098  
1099 1099  
1100 1100  
1101 1101  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1102 1102  
1103 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1115 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1104 1104  
1105 1105  
1118 +
1106 1106  = 7.  FAQ =
1107 1107  
1121 +
1108 1108  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1109 1109  
1110 1110  
... ... @@ -1111,10 +1111,11 @@
1111 1111  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1112 1112  
1113 1113  
1128 +
1114 1114  == 7.2 What is the pin mapping for the USB program cable? ==
1115 1115  
1116 1116  
1117 -[[image:1664499635206-262.png||_mstalt="295360"]]
1132 +[[image:1664499635206-262.png]]
1118 1118  
1119 1119  
1120 1120  
... ... @@ -1131,6 +1131,7 @@
1131 1131  
1132 1132  == 7.3 Notes on using different serial port tools for TrackerD ==
1133 1133  
1149 +
1134 1134  === 7.3.1  Serial port utility ===
1135 1135  
1136 1136  
... ... @@ -1138,16 +1138,18 @@
1138 1138  
1139 1139  Need to adjust the data stream to RTS/CTS on physical restart.
1140 1140  
1157 +
1141 1141  (% class="wikigeneratedid" %)
1142 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1159 +[[image:image-20221102140621-1.png]]
1143 1143  
1144 1144  
1145 -
1146 1146  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1147 1147  
1148 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1149 1149  
1165 +[[image:image-20221102140638-2.png]]
1150 1150  
1167 +
1168 +
1151 1151  === 7.3.2  SecureCRT ===
1152 1152  
1153 1153  
... ... @@ -1154,22 +1154,23 @@
1154 1154  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.
1155 1155  
1156 1156  
1157 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1175 +[[image:image-20221102140704-3.png]]
1158 1158  
1159 1159  
1160 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1178 +[[image:image-20221102140712-4.png]]
1161 1161  
1162 1162  
1181 +
1163 1163  === 7.3.3  PUTTY ===
1164 1164  
1165 1165  
1166 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1185 +[[image:image-20221102140748-5.png]]
1167 1167  
1168 1168  
1169 1169  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.
1170 1170  
1171 1171  
1172 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1191 +[[image:image-20221102140801-6.png]]
1173 1173  
1174 1174  
1175 1175  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1181,38 +1181,29 @@
1181 1181  See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1182 1182  )))
1183 1183  
1184 -**~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.
1185 1185  
1205 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1186 1186  
1187 -[[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).
1188 1188  
1209 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1189 1189  
1211 +3.Compile the AS923_JP band, please refer to the intention shown
1190 1190  
1191 -**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"]]
1192 1192  
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.
1193 1193  
1194 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1217 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1195 1195  
1219 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1196 1196  
1197 1197  
1198 -**3. Compile the AS923_JP band, please refer to the intention shown**
1199 1199  
1200 -
1201 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1202 -
1203 -
1204 -
1205 -**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.**
1206 -
1207 -
1208 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1209 -
1210 -
1211 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1212 -
1213 -
1214 1214  = 8  Trouble Shooting =
1215 1215  
1225 +
1216 1216  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1217 1217  
1218 1218  
... ... @@ -1221,6 +1221,7 @@
1221 1221  )))
1222 1222  
1223 1223  
1234 +
1224 1224  == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1225 1225  
1226 1226  
... ... @@ -1229,6 +1229,7 @@
1229 1229  )))
1230 1230  
1231 1231  
1243 +
1232 1232  == 8.3  Problem after Upgrading Firmware ==
1233 1233  
1234 1234  === 8.3.1 Continue Restart after upgrading ===
... ... @@ -1239,92 +1239,74 @@
1239 1239  )))
1240 1240  
1241 1241  
1242 -[[image:image-20221118105249-3.png||_mstalt="430664"]]
1254 +[[image:image-20221118105249-3.png]]
1243 1243  
1244 1244  
1245 1245  === 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1246 1246  
1247 -
1248 1248  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
1249 1249  
1250 1250  
1251 -=== 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 ====
1252 1252  
1253 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1264 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1254 1254  
1255 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1266 + Figure 1  
1256 1256  
1268 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1257 1257  
1258 -User need to upgrade again with below four files to solve this issue.
1270 + Figure 2
1259 1259  
1260 - [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1261 -
1262 - **Figure 2**
1263 -
1264 -
1265 -=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1266 -
1267 -User might erase the entire flash include keys and default settings which cause this issue.
1268 -
1269 1269  After the upgrade is completed, enter AT+CFG as shown in the figure below.
1270 1270  
1271 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1274 +[[image:image-20221122100004-3.png]]
1272 1272  
1273 -Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1276 +Please AT+FDR, and then enter the following instructions by the information on the label
1274 1274  
1275 -After AT+FDR. please set
1278 +AT+DEUI=70B3D57ED0053981
1276 1276  
1277 -* AT+PDOP=7
1278 -* AT+FTIME=180000
1279 -
1280 -Example:
1281 -
1282 -AT+PDOP=7.00
1283 -
1284 -AT+FTIME=180
1285 -
1286 -AT+DEUI=70B3D57ED0053981  
1287 -
1288 1288  AT+APPEUI=D23345667BCBCCAF
1289 1289  
1290 1290  AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1291 1291  
1292 -AT+DADDR=260b4dce    ( no need for OTAA)
1284 +AT+DADDR=260b4dce
1293 1293  
1294 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1286 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1295 1295  
1296 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1288 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1297 1297  
1298 1298  
1299 1299  
1300 -=== 8.3.4  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 ===
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 ====
1301 1301  
1294 +[[image:image-20221122100004-4.png]]
1302 1302  
1303 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1296 +== ==
1304 1304  
1298 +== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==
1305 1305  
1306 -== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1307 -
1308 -
1309 1309  Please download version 1.4.2 again
1310 1310  
1311 1311  
1312 -== 8.5  How to deal with unsuccessful GPS positioning? ==
1303 +(((
1304 +== 8.5 How to deal with unsuccessful GPS positioning? ==
1313 1313  
1314 -
1315 -1） Make Sure the device is in Open Area where can see the sky.
1316 -
1306 +1） Make Sure the device is in Open Area where can see the sky. 
1317 1317  2)  Set PDOP to a higher value.
1318 1318  
1319 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1309 + AT+PDOP=2(can be positioned precisely.）
1320 1320  
1321 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1311 + AT+PDOP=7(Quickly locate in open spaces）
1322 1322  
1323 -* (% _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）
1324 1324  
1325 1325  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 +)))
1326 1326  
1327 1327  
1319 +== ==
1320 +
1321 +
1328 1328  = 9.  Order Info =
1329 1329  
1330 1330  
... ... @@ -1333,17 +1333,11 @@
1333 1333  (% style="color:blue" %)**XXX**(%%): The default frequency band
1334 1334  
1335 1335  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1336 -
1337 1337  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1338 -
1339 1339  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1340 -
1341 1341  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1342 -
1343 1343  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1344 -
1345 1345  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1346 -
1347 1347  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1348 1348  
1349 1349  = 10.  Packing Info =
... ... @@ -1352,13 +1352,11 @@
1352 1352  (% style="color:#037691" %)**Package Includes**:
1353 1353  
1354 1354  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1355 -
1356 1356  * USB recharge & program cable x 1
1357 1357  
1358 1358  (% style="color:#037691" %)**Dimensions and Weight**:
1359 1359  
1360 1360  * Device Size: 85 x 48 x 15 mm
1361 -
1362 1362  * Weight: 50g
1363 1363  
1364 1364  = 11. Support =
... ... @@ -1365,7 +1365,6 @@
1365 1365  
1366 1366  
1367 1367  * 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.
1368 -
1369 1369  * 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]].
1370 1370  
1371 1371  = 12.  Reference =
... ... @@ -1372,7 +1372,5 @@
1372 1372  
1373 1373  
1374 1374  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1375 -
1376 1376  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1377 -
1378 1378  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]