Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 150.1
edited by Edwin Chen
on 2022/11/24 09:07
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,18 +581,14 @@
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 590  
591 -[[TDC>>||anchor="H3.2.1SetTransmitInterval"]] defines the uplink interval when TrackerD is stactic.
592 592  
593 -[[PT>>||anchor="H3.2.1SetTransmitInterval"]] defines the threldhold to detect a motion.
594 -
595 -
596 596  == 2.10 LED Status ==
597 597  
598 598  
... ... @@ -615,7 +615,7 @@
615 615  
616 616  (% style="color:blue" %)**RESET button:**
617 617  
618 -[[image:1664502835802-546.png||_mstalt="295061"]]
627 +[[image:1664502835802-546.png]]
619 619  
620 620  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
621 621  
... ... @@ -622,7 +622,7 @@
622 622  
623 623  (% style="color:red" %)**RED button:**
624 624  
625 -[[image:1664502854406-763.png||_mstalt="295568"]]
634 +[[image:1664502854406-763.png]]
626 626  
627 627  
628 628  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -649,6 +649,7 @@
649 649  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
650 650  
651 651  
661 +
652 652  == 3.1 Access AT Command ==
653 653  
654 654  
... ... @@ -655,24 +655,25 @@
655 655  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.
656 656  
657 657  
658 -[[image:1664502999401-486.png||_mstalt="296985"]]
668 +[[image:1664502999401-486.png]]
659 659  
660 660  
661 661  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:
662 662  
663 663  
664 -[[image:1664503022490-662.png||_mstalt="293332"]]
674 +[[image:1664503022490-662.png]]
665 665  
666 666  
667 -[[image:1664503035713-500.png||_mstalt="291096"]]
677 +[[image:1664503035713-500.png]]
668 668  
669 669  
670 -[[image:1664503047675-651.png||_mstalt="295386"]]
680 +[[image:1664503047675-651.png]]
671 671  
672 672  
673 673  
674 674  == 3.2 Command Set ==
675 675  
686 +
676 676  === 3.2.1 Set Transmit Interval ===
677 677  
678 678  
... ... @@ -690,6 +690,7 @@
690 690  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
691 691  
692 692  
704 +
693 693  === 3.2.2 Set Alarm Packet transmission interval ===
694 694  
695 695  
... ... @@ -707,6 +707,7 @@
707 707  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
708 708  
709 709  
722 +
710 710  === 3.2.3 Set Transport Mode Packet transmission interval ===
711 711  
712 712  
... ... @@ -724,6 +724,7 @@
724 724  (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
725 725  
726 726  
740 +
727 727  === 3.2.4 Exit Alarm ===
728 728  
729 729  
... ... @@ -736,6 +736,7 @@
736 736  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
737 737  
738 738  
753 +
739 739  === 3.2.5 Disable/Enable LED flash ===
740 740  
741 741  
... ... @@ -753,6 +753,7 @@
753 753  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
754 754  
755 755  
771 +
756 756  === 3.2.6 Disable/Enable Transport Mode ===
757 757  
758 758  
... ... @@ -770,6 +770,7 @@
770 770  (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
771 771  
772 772  
789 +
773 773  === 3.2.7 Set Positioning Mode ===
774 774  
775 775  
... ... @@ -796,9 +796,9 @@
796 796  
797 797  (% style="color:#037691" %)**cc:   **
798 798  
799 -* (% _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  
800 800  
801 -* (% _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(%%))  
802 802  
803 803  (% style="color:blue" %)**Example:**
804 804  
... ... @@ -816,6 +816,7 @@
816 816  (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
817 817  
818 818  
836 +
819 819  === 3.2.8 Set MAX GPS position time ===
820 820  
821 821  
... ... @@ -822,7 +822,7 @@
822 822  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.
823 823  
824 824  
825 -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.
826 826  
827 827  
828 828  * (% style="color:blue" %)**AT Command:**
... ... @@ -837,6 +837,7 @@
837 837  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
838 838  
839 839  
858 +
840 840  === 3.2.9 Set PDOP value for GPS fix accuracy ===
841 841  
842 842  
... ... @@ -861,7 +861,7 @@
861 861  
862 862  
863 863  
864 -=== 3.2.10 Disable/Enable the confirmation mode ===
883 +Disable/Enable the confirmation mode
865 865  
866 866  * (% style="color:blue" %)**AT Command:**
867 867  
... ... @@ -880,9 +880,10 @@
880 880  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
881 881  
882 882  
883 -=== 3.2.11  Auto Send None-ACK messages ===
884 884  
903 +=== 3.2.10  Auto Send None-ACK messages ===
885 885  
905 +
886 886  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.
887 887  
888 888  
... ... @@ -898,12 +898,13 @@
898 898  
899 899  * (% style="color:blue" %)**Downlink Command: 0x34**
900 900  
901 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
921 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
902 902  
903 903  
904 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
905 905  
925 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
906 906  
927 +
907 907  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.
908 908  
909 909  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -910,18 +910,19 @@
910 910  
911 911  (% style="color:blue" %)**AT Command:**
912 912  
913 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
934 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
914 914  
915 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
936 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
916 916  
917 917  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
918 918  
919 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
940 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
920 920  
921 921  
922 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
923 923  
944 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
924 924  
946 +
925 925  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.
926 926  
927 927  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
... ... @@ -928,18 +928,19 @@
928 928  
929 929  (% style="color:blue" %)**AT Command:**
930 930  
931 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
953 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
932 932  
933 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
955 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
934 934  
935 935  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
936 936  
937 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
959 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
938 938  
939 939  
940 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
941 941  
963 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
942 942  
965 +
943 943  Users can use this feature to enable/disable Information printing.
944 944  
945 945  (% style="color:blue" %)**AT Command:**
... ... @@ -948,9 +948,10 @@
948 948  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
949 949  
950 950  
951 -=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
952 952  
975 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
953 953  
977 +
954 954  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
955 955  
956 956  (% style="color:blue" %)**AT Command:**
... ... @@ -963,6 +963,7 @@
963 963  Example: 0x24 01 ~/~/ Same as AT+CHE=1
964 964  
965 965  
990 +
966 966  = 4. Setting for Different Scenarios =
967 967  
968 968  
... ... @@ -969,6 +969,7 @@
969 969  
970 970  = 5. Upload Firmware =
971 971  
997 +
972 972  == 5.1 Firmware Change Log ==
973 973  
974 974  
... ... @@ -975,6 +975,7 @@
975 975  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
976 976  
977 977  
1004 +
978 978  == 5.2 How to upgrade firmware ==
979 979  
980 980  
... ... @@ -995,10 +995,10 @@
995 995  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
996 996  
997 997  
998 -[[image:1664503563660-578.png||_mstalt="296777"]]
1025 +[[image:1664503563660-578.png]]
999 999  
1000 1000  
1001 -[[image:1664503574618-659.png||_mstalt="297986"]]
1028 +[[image:1664503574618-659.png]]
1002 1002  
1003 1003  
1004 1004  
... ... @@ -1007,7 +1007,7 @@
1007 1007  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1008 1008  
1009 1009  
1010 -**Users need to use below files:**
1037 +Users need to use below files:
1011 1011  
1012 1012  boot_app0.bin @0e000
1013 1013  
... ... @@ -1014,20 +1014,22 @@
1014 1014  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1015 1015  
1016 1016  
1017 -[[image:image-20221118105220-2.png||_mstalt="426608"]]
1044 +[[image:image-20221118105220-2.png]]
1018 1018  
1019 1019  
1020 1020  
1021 1021  After upgrade finish, it will show finish as below:
1022 1022  
1023 -[[image:image-20221118105402-4.png||_mstalt="427986"]]
1050 +[[image:image-20221118105402-4.png]]
1024 1024  
1025 1025  
1026 1026  
1027 1027  = 6. Developer Guide =
1028 1028  
1056 +
1029 1029  == 6.1 Compile Source Code ==
1030 1030  
1059 +
1031 1031  === 6.1.1 Set up ARDUINO compile environment ===
1032 1032  
1033 1033  
... ... @@ -1036,23 +1036,23 @@
1036 1036  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]]
1037 1037  
1038 1038  
1039 -[[image:1664503635019-941.png||_mstalt="294658"]]
1068 +[[image:1664503635019-941.png]]
1040 1040  
1041 1041  
1042 1042  
1043 1043  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1044 1044  
1045 -[[image:1664503715811-892.png||_mstalt="295698"]]
1074 +[[image:1664503715811-892.png]]
1046 1046  
1047 1047  
1048 1048  (% 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.
1049 1049  
1050 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1079 +[[image:image-20221024105643-1.png]]
1051 1051  
1052 1052  **~ Figure1**
1053 1053  
1054 1054  
1055 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1084 +[[image:image-20221024105643-2.png]]
1056 1056  
1057 1057   **Figure2**
1058 1058  
... ... @@ -1062,31 +1062,34 @@
1062 1062  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1063 1063  
1064 1064  
1065 -[[image:1664503752288-974.png||_mstalt="298194"]]
1094 +[[image:1664503752288-974.png]]
1066 1066  
1067 1067  
1097 +
1068 1068  == 6.2 Source Code ==
1069 1069  
1070 1070  
1071 1071  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1072 1072  
1073 -[[image:1664503794261-827.png||_mstalt="296387"]]
1103 +[[image:1664503794261-827.png]]
1074 1074  
1075 1075  
1076 1076  
1077 1077  * (% style="color:blue" %)**Click to upload**
1078 1078  
1079 -[[image:1664503808294-336.png||_mstalt="295711"]]
1109 +[[image:1664503808294-336.png]]
1080 1080  
1081 1081  
1082 1082  
1083 1083  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1084 1084  
1085 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1115 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1086 1086  
1087 1087  
1118 +
1088 1088  = 7.  FAQ =
1089 1089  
1121 +
1090 1090  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1091 1091  
1092 1092  
... ... @@ -1093,10 +1093,11 @@
1093 1093  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1094 1094  
1095 1095  
1128 +
1096 1096  == 7.2 What is the pin mapping for the USB program cable? ==
1097 1097  
1098 1098  
1099 -[[image:1664499635206-262.png||_mstalt="295360"]]
1132 +[[image:1664499635206-262.png]]
1100 1100  
1101 1101  
1102 1102  
... ... @@ -1113,6 +1113,7 @@
1113 1113  
1114 1114  == 7.3 Notes on using different serial port tools for TrackerD ==
1115 1115  
1149 +
1116 1116  === 7.3.1  Serial port utility ===
1117 1117  
1118 1118  
... ... @@ -1120,16 +1120,18 @@
1120 1120  
1121 1121  Need to adjust the data stream to RTS/CTS on physical restart.
1122 1122  
1157 +
1123 1123  (% class="wikigeneratedid" %)
1124 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1159 +[[image:image-20221102140621-1.png]]
1125 1125  
1126 1126  
1127 -
1128 1128  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1129 1129  
1130 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1131 1131  
1165 +[[image:image-20221102140638-2.png]]
1132 1132  
1167 +
1168 +
1133 1133  === 7.3.2  SecureCRT ===
1134 1134  
1135 1135  
... ... @@ -1136,22 +1136,23 @@
1136 1136  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.
1137 1137  
1138 1138  
1139 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1175 +[[image:image-20221102140704-3.png]]
1140 1140  
1141 1141  
1142 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1178 +[[image:image-20221102140712-4.png]]
1143 1143  
1144 1144  
1181 +
1145 1145  === 7.3.3  PUTTY ===
1146 1146  
1147 1147  
1148 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1185 +[[image:image-20221102140748-5.png]]
1149 1149  
1150 1150  
1151 1151  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.
1152 1152  
1153 1153  
1154 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1191 +[[image:image-20221102140801-6.png]]
1155 1155  
1156 1156  
1157 1157  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1163,38 +1163,29 @@
1163 1163  See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1164 1164  )))
1165 1165  
1166 -**~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.
1167 1167  
1205 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1168 1168  
1169 -[[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).
1170 1170  
1209 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1171 1171  
1211 +3.Compile the AS923_JP band, please refer to the intention shown
1172 1172  
1173 -**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"]]
1174 1174  
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.
1175 1175  
1176 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1217 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1177 1177  
1219 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1178 1178  
1179 1179  
1180 -**3. Compile the AS923_JP band, please refer to the intention shown**
1181 1181  
1182 -
1183 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1184 -
1185 -
1186 -
1187 -**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.**
1188 -
1189 -
1190 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1191 -
1192 -
1193 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1194 -
1195 -
1196 1196  = 8  Trouble Shooting =
1197 1197  
1225 +
1198 1198  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1199 1199  
1200 1200  
... ... @@ -1203,6 +1203,7 @@
1203 1203  )))
1204 1204  
1205 1205  
1234 +
1206 1206  == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1207 1207  
1208 1208  
... ... @@ -1211,6 +1211,7 @@
1211 1211  )))
1212 1212  
1213 1213  
1243 +
1214 1214  == 8.3  Problem after Upgrading Firmware ==
1215 1215  
1216 1216  === 8.3.1 Continue Restart after upgrading ===
... ... @@ -1221,92 +1221,74 @@
1221 1221  )))
1222 1222  
1223 1223  
1224 -[[image:image-20221118105249-3.png||_mstalt="430664"]]
1254 +[[image:image-20221118105249-3.png]]
1225 1225  
1226 1226  
1227 1227  === 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1228 1228  
1229 -
1230 1230  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
1231 1231  
1232 1232  
1233 -=== 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 ====
1234 1234  
1235 -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"]]
1236 1236  
1237 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1266 + Figure 1  
1238 1238  
1268 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1239 1239  
1240 -User need to upgrade again with below four files to solve this issue.
1270 + Figure 2
1241 1241  
1242 - [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1243 -
1244 - **Figure 2**
1245 -
1246 -
1247 -=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1248 -
1249 -User might erase the entire flash include keys and default settings which cause this issue.
1250 -
1251 1251  After the upgrade is completed, enter AT+CFG as shown in the figure below.
1252 1252  
1253 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1274 +[[image:image-20221122100004-3.png]]
1254 1254  
1255 -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
1256 1256  
1257 -After AT+FDR. please set
1278 +AT+DEUI=70B3D57ED0053981
1258 1258  
1259 -* AT+PDOP=7
1260 -* AT+FTIME=180000
1261 -
1262 -Example:
1263 -
1264 -AT+PDOP=7.00
1265 -
1266 -AT+FTIME=180
1267 -
1268 -AT+DEUI=70B3D57ED0053981  
1269 -
1270 1270  AT+APPEUI=D23345667BCBCCAF
1271 1271  
1272 1272  AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1273 1273  
1274 -AT+DADDR=260b4dce    ( no need for OTAA)
1284 +AT+DADDR=260b4dce
1275 1275  
1276 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1286 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1277 1277  
1278 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1288 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1279 1279  
1280 1280  
1281 1281  
1282 -=== 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 ====
1283 1283  
1294 +[[image:image-20221122100004-4.png]]
1284 1284  
1285 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1296 +== ==
1286 1286  
1298 +== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==
1287 1287  
1288 -== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1289 -
1290 -
1291 1291  Please download version 1.4.2 again
1292 1292  
1293 1293  
1294 -== 8.5  How to deal with unsuccessful GPS positioning? ==
1303 +(((
1304 +== 8.5 How to deal with unsuccessful GPS positioning? ==
1295 1295  
1296 -
1297 -1） Make Sure the device is in Open Area where can see the sky.
1298 -
1306 +1） Make Sure the device is in Open Area where can see the sky. 
1299 1299  2)  Set PDOP to a higher value.
1300 1300  
1301 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1309 + AT+PDOP=2(can be positioned precisely.）
1302 1302  
1303 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1311 + AT+PDOP=7(Quickly locate in open spaces）
1304 1304  
1305 -* (% _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）
1306 1306  
1307 1307  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 +)))
1308 1308  
1309 1309  
1319 +== ==
1320 +
1321 +
1310 1310  = 9.  Order Info =
1311 1311  
1312 1312  
... ... @@ -1315,17 +1315,11 @@
1315 1315  (% style="color:blue" %)**XXX**(%%): The default frequency band
1316 1316  
1317 1317  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1318 -
1319 1319  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1320 -
1321 1321  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1322 -
1323 1323  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1324 -
1325 1325  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1326 -
1327 1327  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1328 -
1329 1329  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1330 1330  
1331 1331  = 10.  Packing Info =
... ... @@ -1334,13 +1334,11 @@
1334 1334  (% style="color:#037691" %)**Package Includes**:
1335 1335  
1336 1336  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1337 -
1338 1338  * USB recharge & program cable x 1
1339 1339  
1340 1340  (% style="color:#037691" %)**Dimensions and Weight**:
1341 1341  
1342 1342  * Device Size: 85 x 48 x 15 mm
1343 -
1344 1344  * Weight: 50g
1345 1345  
1346 1346  = 11. Support =
... ... @@ -1347,7 +1347,6 @@
1347 1347  
1348 1348  
1349 1349  * 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.
1350 -
1351 1351  * 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]].
1352 1352  
1353 1353  = 12.  Reference =
... ... @@ -1354,7 +1354,5 @@
1354 1354  
1355 1355  
1356 1356  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1357 -
1358 1358  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1359 -
1360 1360  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]