Last modified by Xiaoling on 2023/12/27 09:15

From version 141.1
edited by Bei Jinggeng
on 2022/11/22 10:00
Change comment: Uploaded new attachment "image-20221122100004-4.png", version {1}
To version 148.1
edited by Bei Jinggeng
on 2022/11/24 09:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:1664505654417-133.png]]
2 +[[image:1664505654417-133.png||_mstalt="293696"]]
3 3  
4 4  
5 5  
... ... @@ -14,7 +14,6 @@
14 14  
15 15  = 1.  Introduction =
16 16  
17 -
18 18  == 1.1  What is TrackerD ==
19 19  
20 20  
... ... @@ -40,13 +40,12 @@
40 40  
41 41  )))
42 42  
43 -[[image:1664499921684-770.png]]
42 +[[image:1664499921684-770.png||_mstalt="298194"]]
44 44  
45 45  
46 46  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
47 47  
48 48  
49 -
50 50  == 1.2 Specifications ==
51 51  
52 52  
... ... @@ -123,7 +123,6 @@
123 123  
124 124  = 2.  Use TrackerD =
125 125  
126 -
127 127  == 2.1 How it works? ==
128 128  
129 129  
... ... @@ -130,7 +130,6 @@
130 130  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.
131 131  
132 132  
133 -
134 134  == 2.2 Quick guide to connect to LoRaWAN server ==
135 135  
136 136  
... ... @@ -137,7 +137,7 @@
137 137  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. 
138 138  
139 139  
140 -[[image:1664501652064-326.png]]
136 +[[image:1664501652064-326.png||_mstalt="293306"]]
141 141  
142 142  
143 143  
... ... @@ -149,7 +149,7 @@
149 149  Each TrackerD is shipped with a sticker with the default device EUI as below:
150 150  
151 151  
152 -[[image:1664501677253-891.png]]
148 +[[image:1664501677253-891.png||_mstalt="296569"]]
153 153  
154 154  
155 155  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -158,14 +158,14 @@
158 158  **__Add APP EUI in the application:__**
159 159  
160 160  
161 -[[image:1664501711466-918.png]]
157 +[[image:1664501711466-918.png||_mstalt="295828"]]
162 162  
163 163  
164 164  
165 -[[image:1664501721248-725.png]]
161 +[[image:1664501721248-725.png||_mstalt="294450"]]
166 166  
167 167  
168 -[[image:1664501734705-405.png]]
164 +[[image:1664501734705-405.png||_mstalt="293306"]]
169 169  
170 170  
171 171  
... ... @@ -172,21 +172,20 @@
172 172  **__Add APP KEY and DEV EUI:__**
173 173  
174 174  
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"]]
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"]]
176 176  
177 177  
178 178  
179 179  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
180 180  
181 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
177 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
182 182  
183 -[[image:1664502835802-546.png]]
179 +[[image:1664502835802-546.png||_mstalt="295061"]]
184 184  
185 185  
186 186  (% 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.
187 187  
188 188  
189 -
190 190  == 2.3  Positioning Mode(SMOD) ==
191 191  
192 192  
... ... @@ -199,10 +199,8 @@
199 199  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
200 200  
201 201  
202 -
203 203  == 2.4  Uplink Payload ==
204 204  
205 -
206 206  === 2.4.1 Uplink FPORT~=5, Device Status ===
207 207  
208 208  
... ... @@ -215,7 +215,7 @@
215 215  |=(% 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
216 216  |=(% 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
217 217  
218 -[[image:1665301570342-765.png]]
211 +[[image:1665301570342-765.png||_mstalt="294580"]]
219 219  
220 220  
221 221  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -282,7 +282,7 @@
282 282  
283 283  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
284 284  
285 -(% style="color:red" %)** 2:**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
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)(%%)  
286 286  
287 287  
288 288  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -309,7 +309,7 @@
309 309  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
310 310  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
311 311  
312 -[[image:1665301636888-168.png]]
305 +[[image:1665301636888-168.png||_mstalt="298012"]]
313 313  
314 314  
315 315  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -339,12 +339,12 @@
339 339  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:
340 340  
341 341  
342 -[[image:1664502116362-706.png]]
335 +[[image:1664502116362-706.png||_mstalt="293306"]]
343 343  
344 344  
345 345  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
346 346  
347 -[[image:1664502166010-515.png]]
340 +[[image:1664502166010-515.png||_mstalt="291395"]]
348 348  
349 349  
350 350  
... ... @@ -407,7 +407,6 @@
407 407  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
408 408  
409 409  
410 -
411 411  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
412 412  
413 413  
... ... @@ -423,10 +423,9 @@
423 423  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
424 424  
425 425  (% class="wikigeneratedid" %)
426 -[[image:1665301687277-443.png]]
418 +[[image:1665301687277-443.png||_mstalt="296140"]]
427 427  
428 428  
429 -
430 430  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
431 431  
432 432  
... ... @@ -447,10 +447,9 @@
447 447  )))|4|4|2|1|1|1|1|1
448 448  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
449 449  
450 -[[image:image-20221009160309-2.png]]
441 +[[image:image-20221009160309-2.png||_mstalt="429312"]]
451 451  
452 452  
453 -
454 454  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
455 455  
456 456  
... ... @@ -475,7 +475,7 @@
475 475  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
476 476  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
477 477  
478 -[[image:1664502425687-834.png]]
468 +[[image:1664502425687-834.png||_mstalt="296738"]]
479 479  
480 480  
481 481  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -501,7 +501,7 @@
501 501  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
502 502  
503 503  (% class="wikigeneratedid" %)
504 -[[image:1667288597595-714.png||height="212" width="1151"]]
494 +[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
505 505  
506 506  
507 507  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -516,9 +516,10 @@
516 516  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
517 517  
518 518  
519 -[[image:1664502649601-895.png]]
509 +[[image:1664502649601-895.png||_mstalt="296985"]]
520 520  
521 521  
512 +
522 522  Add the decoder from this link: 
523 523  
524 524  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -525,10 +525,9 @@
525 525  
526 526  Save the change the uplink message will be parsed. As below:
527 527  
528 -[[image:1664502676891-606.png]]
519 +[[image:1664502676891-606.png||_mstalt="296673"]]
529 529  
530 530  
531 -
532 532  == 2.5 Integrate with Datacake ==
533 533  
534 534  
... ... @@ -537,10 +537,9 @@
537 537  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]]
538 538  
539 539  
540 -[[image:1664502695771-538.png]]
530 +[[image:1664502695771-538.png||_mstalt="297349"]]
541 541  
542 542  
543 -
544 544  == 2.6 Integrate with Tago ==
545 545  
546 546  
... ... @@ -549,10 +549,9 @@
549 549  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]]
550 550  
551 551  
552 -[[image:1664502715371-321.png]]
541 +[[image:1664502715371-321.png||_mstalt="292162"]]
553 553  
554 554  
555 -
556 556  == 2.7  Datalog Feature ==
557 557  
558 558  
... ... @@ -562,13 +562,12 @@
562 562  
563 563  Example use case.
564 564  
565 -[[image:image-20221009234703-2.png||height="328" width="899"]]
553 +[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
566 566  
567 567  
568 -[[image:image-20221009234629-1.png||height="390" width="577"]]
556 +[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
569 569  
570 570  
571 -
572 572  == 2.8 Alarm Mode ==
573 573  
574 574  
... ... @@ -583,7 +583,7 @@
583 583  
584 584  
585 585  (((
586 -Two ways to exit alarm mode:
573 +**Two ways to exit alarm mode:**
587 587  )))
588 588  
589 589  * Server sends a downlink command to exit.
... ... @@ -594,7 +594,6 @@
594 594  )))
595 595  
596 596  
597 -
598 598  == 2.9 Transport Mode ==
599 599  
600 600  
... ... @@ -601,7 +601,6 @@
601 601  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.
602 602  
603 603  
604 -
605 605  == 2.10 LED Status ==
606 606  
607 607  
... ... @@ -624,7 +624,7 @@
624 624  
625 625  (% style="color:blue" %)**RESET button:**
626 626  
627 -[[image:1664502835802-546.png]]
612 +[[image:1664502835802-546.png||_mstalt="295061"]]
628 628  
629 629  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
630 630  
... ... @@ -631,7 +631,7 @@
631 631  
632 632  (% style="color:red" %)**RED button:**
633 633  
634 -[[image:1664502854406-763.png]]
619 +[[image:1664502854406-763.png||_mstalt="295568"]]
635 635  
636 636  
637 637  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -658,7 +658,6 @@
658 658  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
659 659  
660 660  
661 -
662 662  == 3.1 Access AT Command ==
663 663  
664 664  
... ... @@ -665,25 +665,24 @@
665 665  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.
666 666  
667 667  
668 -[[image:1664502999401-486.png]]
652 +[[image:1664502999401-486.png||_mstalt="296985"]]
669 669  
670 670  
671 671  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:
672 672  
673 673  
674 -[[image:1664503022490-662.png]]
658 +[[image:1664503022490-662.png||_mstalt="293332"]]
675 675  
676 676  
677 -[[image:1664503035713-500.png]]
661 +[[image:1664503035713-500.png||_mstalt="291096"]]
678 678  
679 679  
680 -[[image:1664503047675-651.png]]
664 +[[image:1664503047675-651.png||_mstalt="295386"]]
681 681  
682 682  
683 683  
684 684  == 3.2 Command Set ==
685 685  
686 -
687 687  === 3.2.1 Set Transmit Interval ===
688 688  
689 689  
... ... @@ -701,7 +701,6 @@
701 701  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
702 702  
703 703  
704 -
705 705  === 3.2.2 Set Alarm Packet transmission interval ===
706 706  
707 707  
... ... @@ -719,7 +719,6 @@
719 719  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
720 720  
721 721  
722 -
723 723  === 3.2.3 Set Transport Mode Packet transmission interval ===
724 724  
725 725  
... ... @@ -737,7 +737,6 @@
737 737  (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
738 738  
739 739  
740 -
741 741  === 3.2.4 Exit Alarm ===
742 742  
743 743  
... ... @@ -750,7 +750,6 @@
750 750  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
751 751  
752 752  
753 -
754 754  === 3.2.5 Disable/Enable LED flash ===
755 755  
756 756  
... ... @@ -768,7 +768,6 @@
768 768  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
769 769  
770 770  
771 -
772 772  === 3.2.6 Disable/Enable Transport Mode ===
773 773  
774 774  
... ... @@ -786,7 +786,6 @@
786 786  (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
787 787  
788 788  
789 -
790 790  === 3.2.7 Set Positioning Mode ===
791 791  
792 792  
... ... @@ -813,9 +813,9 @@
813 813  
814 814  (% style="color:#037691" %)**cc:   **
815 815  
816 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
793 +* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
817 817  
818 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
795 +* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
819 819  
820 820  (% style="color:blue" %)**Example:**
821 821  
... ... @@ -833,7 +833,6 @@
833 833  (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
834 834  
835 835  
836 -
837 837  === 3.2.8 Set MAX GPS position time ===
838 838  
839 839  
... ... @@ -840,7 +840,7 @@
840 840  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.
841 841  
842 842  
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.
819 +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.
844 844  
845 845  
846 846  * (% style="color:blue" %)**AT Command:**
... ... @@ -855,7 +855,6 @@
855 855  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
856 856  
857 857  
858 -
859 859  === 3.2.9 Set PDOP value for GPS fix accuracy ===
860 860  
861 861  
... ... @@ -880,7 +880,7 @@
880 880  
881 881  
882 882  
883 -Disable/Enable the confirmation mode
858 +=== 3.2.10 Disable/Enable the confirmation mode ===
884 884  
885 885  * (% style="color:blue" %)**AT Command:**
886 886  
... ... @@ -899,10 +899,9 @@
899 899  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
900 900  
901 901  
877 +=== 3.2.11  Auto Send None-ACK messages ===
902 902  
903 -=== 3.2.10  Auto Send None-ACK messages ===
904 904  
905 -
906 906  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.
907 907  
908 908  
... ... @@ -918,13 +918,12 @@
918 918  
919 919  * (% style="color:blue" %)**Downlink Command: 0x34**
920 920  
921 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
895 +Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
922 922  
923 923  
898 +=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
924 924  
925 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
926 926  
927 -
928 928  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.
929 929  
930 930  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -931,19 +931,18 @@
931 931  
932 932  (% style="color:blue" %)**AT Command:**
933 933  
934 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
907 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
935 935  
936 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
909 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
937 937  
938 938  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)**
939 939  
940 -Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
913 +Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
941 941  
942 942  
916 +=== 3.2.13  Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) ===
943 943  
944 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) ===
945 945  
946 -
947 947  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.
948 948  
949 949  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
... ... @@ -950,19 +950,18 @@
950 950  
951 951  (% style="color:blue" %)**AT Command:**
952 952  
953 - (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
925 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
954 954  
955 - (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
927 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
956 956  
957 957  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)**
958 958  
959 -Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
931 +Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
960 960  
961 961  
934 +=== 3.2.14  Disable/Enable Information printing(Since firmware 1.4.1) ===
962 962  
963 -=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) ===
964 964  
965 -
966 966  Users can use this feature to enable/disable Information printing.
967 967  
968 968  (% style="color:blue" %)**AT Command:**
... ... @@ -971,10 +971,9 @@
971 971  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
972 972  
973 973  
945 +=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) ===
974 974  
975 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) ===
976 976  
977 -
978 978  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
979 979  
980 980  (% style="color:blue" %)**AT Command:**
... ... @@ -987,7 +987,6 @@
987 987  Example: 0x24 01 ~/~/ Same as AT+CHE=1
988 988  
989 989  
990 -
991 991  = 4. Setting for Different Scenarios =
992 992  
993 993  
... ... @@ -994,7 +994,6 @@
994 994  
995 995  = 5. Upload Firmware =
996 996  
997 -
998 998  == 5.1 Firmware Change Log ==
999 999  
1000 1000  
... ... @@ -1001,7 +1001,6 @@
1001 1001  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1002 1002  
1003 1003  
1004 -
1005 1005  == 5.2 How to upgrade firmware ==
1006 1006  
1007 1007  
... ... @@ -1022,10 +1022,10 @@
1022 1022  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1023 1023  
1024 1024  
1025 -[[image:1664503563660-578.png]]
992 +[[image:1664503563660-578.png||_mstalt="296777"]]
1026 1026  
1027 1027  
1028 -[[image:1664503574618-659.png]]
995 +[[image:1664503574618-659.png||_mstalt="297986"]]
1029 1029  
1030 1030  
1031 1031  
... ... @@ -1034,7 +1034,7 @@
1034 1034  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1035 1035  
1036 1036  
1037 -Users need to use below files:
1004 +**Users need to use below files:**
1038 1038  
1039 1039  boot_app0.bin @0e000
1040 1040  
... ... @@ -1041,22 +1041,20 @@
1041 1041  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1042 1042  
1043 1043  
1044 -[[image:image-20221118105220-2.png]]
1011 +[[image:image-20221118105220-2.png||_mstalt="426608"]]
1045 1045  
1046 1046  
1047 1047  
1048 1048  After upgrade finish, it will show finish as below:
1049 1049  
1050 -[[image:image-20221118105402-4.png]]
1017 +[[image:image-20221118105402-4.png||_mstalt="427986"]]
1051 1051  
1052 1052  
1053 1053  
1054 1054  = 6. Developer Guide =
1055 1055  
1056 -
1057 1057  == 6.1 Compile Source Code ==
1058 1058  
1059 -
1060 1060  === 6.1.1 Set up ARDUINO compile environment ===
1061 1061  
1062 1062  
... ... @@ -1065,23 +1065,23 @@
1065 1065  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]]
1066 1066  
1067 1067  
1068 -[[image:1664503635019-941.png]]
1033 +[[image:1664503635019-941.png||_mstalt="294658"]]
1069 1069  
1070 1070  
1071 1071  
1072 1072  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1073 1073  
1074 -[[image:1664503715811-892.png]]
1039 +[[image:1664503715811-892.png||_mstalt="295698"]]
1075 1075  
1076 1076  
1077 1077  (% 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.
1078 1078  
1079 -[[image:image-20221024105643-1.png]]
1044 +[[image:image-20221024105643-1.png||_mstalt="428129"]]
1080 1080  
1081 1081  **~ Figure1**
1082 1082  
1083 1083  
1084 -[[image:image-20221024105643-2.png]]
1049 +[[image:image-20221024105643-2.png||_mstalt="428493"]]
1085 1085  
1086 1086   **Figure2**
1087 1087  
... ... @@ -1091,34 +1091,31 @@
1091 1091  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1092 1092  
1093 1093  
1094 -[[image:1664503752288-974.png]]
1059 +[[image:1664503752288-974.png||_mstalt="298194"]]
1095 1095  
1096 1096  
1097 -
1098 1098  == 6.2 Source Code ==
1099 1099  
1100 1100  
1101 1101  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1102 1102  
1103 -[[image:1664503794261-827.png]]
1067 +[[image:1664503794261-827.png||_mstalt="296387"]]
1104 1104  
1105 1105  
1106 1106  
1107 1107  * (% style="color:blue" %)**Click to upload**
1108 1108  
1109 -[[image:1664503808294-336.png]]
1073 +[[image:1664503808294-336.png||_mstalt="295711"]]
1110 1110  
1111 1111  
1112 1112  
1113 1113  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1114 1114  
1115 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1079 +[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1116 1116  
1117 1117  
1118 -
1119 1119  = 7.  FAQ =
1120 1120  
1121 -
1122 1122  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1123 1123  
1124 1124  
... ... @@ -1125,11 +1125,10 @@
1125 1125  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1126 1126  
1127 1127  
1128 -
1129 1129  == 7.2 What is the pin mapping for the USB program cable? ==
1130 1130  
1131 1131  
1132 -[[image:1664499635206-262.png]]
1093 +[[image:1664499635206-262.png||_mstalt="295360"]]
1133 1133  
1134 1134  
1135 1135  
... ... @@ -1146,7 +1146,6 @@
1146 1146  
1147 1147  == 7.3 Notes on using different serial port tools for TrackerD ==
1148 1148  
1149 -
1150 1150  === 7.3.1  Serial port utility ===
1151 1151  
1152 1152  
... ... @@ -1154,18 +1154,16 @@
1154 1154  
1155 1155  Need to adjust the data stream to RTS/CTS on physical restart.
1156 1156  
1157 -
1158 1158  (% class="wikigeneratedid" %)
1159 -[[image:image-20221102140621-1.png]]
1118 +[[image:image-20221102140621-1.png||_mstalt="425672"]]
1160 1160  
1161 1161  
1121 +
1162 1162  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1163 1163  
1124 +[[image:image-20221102140638-2.png||_mstalt="428727"]]
1164 1164  
1165 -[[image:image-20221102140638-2.png]]
1166 1166  
1167 -
1168 -
1169 1169  === 7.3.2  SecureCRT ===
1170 1170  
1171 1171  
... ... @@ -1172,23 +1172,22 @@
1172 1172  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.
1173 1173  
1174 1174  
1175 -[[image:image-20221102140704-3.png]]
1133 +[[image:image-20221102140704-3.png||_mstalt="427076"]]
1176 1176  
1177 1177  
1178 -[[image:image-20221102140712-4.png]]
1136 +[[image:image-20221102140712-4.png||_mstalt="427089"]]
1179 1179  
1180 1180  
1181 -
1182 1182  === 7.3.3  PUTTY ===
1183 1183  
1184 1184  
1185 -[[image:image-20221102140748-5.png]]
1142 +[[image:image-20221102140748-5.png||_mstalt="430456"]]
1186 1186  
1187 1187  
1188 1188  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.
1189 1189  
1190 1190  
1191 -[[image:image-20221102140801-6.png]]
1148 +[[image:image-20221102140801-6.png||_mstalt="427466"]]
1192 1192  
1193 1193  
1194 1194  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1200,29 +1200,38 @@
1200 1200  See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1201 1201  )))
1202 1202  
1203 -1.When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.
1160 +**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1204 1204  
1205 -[[image:image-20221116111844-1.png||height="227" width="782"]]
1206 1206  
1207 -2.Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).
1163 +[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1208 1208  
1209 -[[image:image-20221116111844-2.png||height="262" width="781"]]
1210 1210  
1211 -3.Compile the AS923_JP band, please refer to the intention shown
1212 1212  
1213 -[[image:image-20221116111844-3.png||height="338" width="746"]]
1167 +**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1214 1214  
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.
1216 1216  
1217 -[[image:image-20221116111844-4.png||height="641" width="739"]]
1170 +[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1218 1218  
1219 -[[image:image-20221116111844-5.png||height="551" width="708"]]
1220 1220  
1221 1221  
1174 +**3. Compile the AS923_JP band, please refer to the intention shown**
1222 1222  
1223 -= 8  Trouble Shooting =
1224 1224  
1177 +[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1225 1225  
1179 +
1180 +
1181 +**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.**
1182 +
1183 +
1184 +[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1185 +
1186 +
1187 +[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1188 +
1189 +
1190 += 8  Trouble Shooting =
1191 +
1226 1226  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1227 1227  
1228 1228  
... ... @@ -1231,7 +1231,6 @@
1231 1231  )))
1232 1232  
1233 1233  
1234 -
1235 1235  == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1236 1236  
1237 1237  
... ... @@ -1240,7 +1240,6 @@
1240 1240  )))
1241 1241  
1242 1242  
1243 -
1244 1244  == 8.3  Problem after Upgrading Firmware ==
1245 1245  
1246 1246  === 8.3.1 Continue Restart after upgrading ===
... ... @@ -1251,35 +1251,92 @@
1251 1251  )))
1252 1252  
1253 1253  
1254 -[[image:image-20221118105249-3.png]]
1218 +[[image:image-20221118105249-3.png||_mstalt="430664"]]
1255 1255  
1256 1256  
1257 1257  === 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1258 1258  
1223 +
1259 1259  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
1260 1260  
1261 1261  
1262 -(((
1263 -== 8.5 How to deal with unsuccessful GPS positioning? ==
1227 +=== 8.3.3 "flash read err" after upgrade firmware ===
1264 1264  
1265 -1) Make Sure the device is in Open Area where can see the sky. 
1266 -2)  Set PDOP to a higher value.
1229 +Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1267 1267  
1268 - AT+PDOP=2(can be positioned precisely.)
1231 +[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1269 1269  
1270 - AT+PDOP=7(Quickly locate in open spaces)
1271 1271  
1272 - AT+PDOP=14.7(Positioning can be acquired in complex environments
1234 +User need to upgrade again with below four files to solve this issue.
1273 1273  
1274 -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
1275 -)))
1236 + [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1276 1276  
1238 + **Figure 2**
1277 1277  
1278 -== 8.6 When positioning, it will restart or the PDOP setting is unsuccessful ==
1279 1279  
1241 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1242 +
1243 +User might erase the entire flash include keys and default settings which cause this issue.
1244 +
1245 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1246 +
1247 +[[image:image-20221122100004-3.png||_mstalt="424242"]]
1248 +
1249 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1250 +
1251 +After AT+FDR. please set
1252 +
1253 +* AT+PDOP=7
1254 +* AT+FTIME=180000
1255 +
1256 +Example:
1257 +
1258 +AT+PDOP=7.00
1259 +
1260 +AT+FTIME=180
1261 +
1262 +AT+DEUI=70B3D57ED0053981  
1263 +
1264 +AT+APPEUI=D23345667BCBCCAF
1265 +
1266 +AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1267 +
1268 +AT+DADDR=260b4dce    ( no need for OTAA)
1269 +
1270 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1271 +
1272 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1273 +
1274 +
1275 +
1276 +=== 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 ===
1277 +
1278 +
1279 +[[image:image-20221122100004-4.png||_mstalt="424606"]]
1280 +
1281 +
1282 +== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1283 +
1284 +
1280 1280  Please download version 1.4.2 again
1281 1281  
1282 1282  
1288 +== 8.5  How to deal with unsuccessful GPS positioning? ==
1289 +
1290 +
1291 +1) Make Sure the device is in Open Area where can see the sky.
1292 +
1293 +2)  Set PDOP to a higher value.
1294 +
1295 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.)
1296 +
1297 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces)
1298 +
1299 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments)
1300 +
1301 +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
1302 +
1303 +
1283 1283  = 9.  Order Info =
1284 1284  
1285 1285  
... ... @@ -1288,11 +1288,17 @@
1288 1288  (% style="color:blue" %)**XXX**(%%): The default frequency band
1289 1289  
1290 1290  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1312 +
1291 1291  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1314 +
1292 1292  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1316 +
1293 1293  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1318 +
1294 1294  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1320 +
1295 1295  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1322 +
1296 1296  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1297 1297  
1298 1298  = 10.  Packing Info =
... ... @@ -1301,11 +1301,13 @@
1301 1301  (% style="color:#037691" %)**Package Includes**:
1302 1302  
1303 1303  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1331 +
1304 1304  * USB recharge & program cable x 1
1305 1305  
1306 1306  (% style="color:#037691" %)**Dimensions and Weight**:
1307 1307  
1308 1308  * Device Size: 85 x 48 x 15 mm
1337 +
1309 1309  * Weight: 50g
1310 1310  
1311 1311  = 11. Support =
... ... @@ -1312,6 +1312,7 @@
1312 1312  
1313 1313  
1314 1314  * 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.
1344 +
1315 1315  * 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]].
1316 1316  
1317 1317  = 12.  Reference =
... ... @@ -1318,5 +1318,7 @@
1318 1318  
1319 1319  
1320 1320  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1351 +
1321 1321  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1353 +
1322 1322  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]