Skip to Content
Last modified by Bei Jinggeng on 2025/07/23 11:03
From version 185.1
edited by Bei Jinggeng
on 2022/12/15 10:00
Change comment: There is no comment for this version
To version 140.1
edited by Bei Jinggeng
on 2022/11/22 10:00
Change comment: Uploaded new attachment "image-20221122100004-3.png", version {1}

Summary

Details

Page properties
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  
... ... @@ -12,9 +12,9 @@
12 12  
13 13  
14 14  
15 -
16 16  = 1.  Introduction =
17 17  
17 +
18 18  == 1.1  What is TrackerD ==
19 19  
20 20  
... ... @@ -32,17 +32,21 @@
32 32  (((
33 33  The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
34 34  )))
35 +)))
35 35  
36 36  (((
37 37  TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.
39 +
40 +
38 38  )))
39 39  
40 -[[image:1664499921684-770.png||_mstalt="298194"]]
43 +[[image:1664499921684-770.png]]
41 41  
42 42  
43 43  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
44 44  
45 45  
49 +
46 46  == 1.2 Specifications ==
47 47  
48 48  
... ... @@ -93,7 +93,6 @@
93 93  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94 94  * Tracking: max: 38mA
95 95  
96 -
97 97  == 1.3  Features ==
98 98  
99 99  
... ... @@ -112,7 +112,6 @@
112 112  * Tri-color LED, Alarm button
113 113  * Datalog
114 114  
115 -
116 116  == 1.4  Applications ==
117 117  
118 118  
... ... @@ -119,9 +119,9 @@
119 119  * Logistics and Supply Chain Management
120 120  * Human tracking
121 121  
122 -
123 123  = 2.  Use TrackerD =
124 124  
126 +
125 125  == 2.1 How it works? ==
126 126  
127 127  
... ... @@ -128,6 +128,7 @@
128 128  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.
129 129  
130 130  
133 +
131 131  == 2.2 Quick guide to connect to LoRaWAN server ==
132 132  
133 133  
... ... @@ -134,7 +134,7 @@
134 134  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. 
135 135  
136 136  
137 -[[image:1664501652064-326.png||_mstalt="293306"]]
140 +[[image:1664501652064-326.png]]
138 138  
139 139  
140 140  
... ... @@ -146,7 +146,7 @@
146 146  Each TrackerD is shipped with a sticker with the default device EUI as below:
147 147  
148 148  
149 -[[image:1664501677253-891.png||_mstalt="296569"]]
152 +[[image:1664501677253-891.png]]
150 150  
151 151  
152 152  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -155,14 +155,14 @@
155 155  **__Add APP EUI in the application:__**
156 156  
157 157  
158 -[[image:1664501711466-918.png||_mstalt="295828"]]
161 +[[image:1664501711466-918.png]]
159 159  
160 160  
161 161  
162 -[[image:1664501721248-725.png||_mstalt="294450"]]
165 +[[image:1664501721248-725.png]]
163 163  
164 164  
165 -[[image:1664501734705-405.png||_mstalt="293306"]]
168 +[[image:1664501734705-405.png]]
166 166  
167 167  
168 168  
... ... @@ -169,20 +169,21 @@
169 169  **__Add APP KEY and DEV EUI:__**
170 170  
171 171  
172 -[[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"]]
173 173  
174 174  
175 175  
176 176  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
177 177  
178 -(% 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]]
179 179  
180 -[[image:1664502835802-546.png||_mstalt="295061"]]
183 +[[image:1664502835802-546.png]]
181 181  
182 182  
183 183  (% 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.
184 184  
185 185  
189 +
186 186  == 2.3  Positioning Mode(SMOD) ==
187 187  
188 188  
... ... @@ -195,8 +195,10 @@
195 195  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
196 196  
197 197  
202 +
198 198  == 2.4  Uplink Payload ==
199 199  
205 +
200 200  === 2.4.1 Uplink FPORT~=5, Device Status ===
201 201  
202 202  
... ... @@ -209,7 +209,7 @@
209 209  |=(% 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
210 210  |=(% 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
211 211  
212 -[[image:1665301570342-765.png||_mstalt="294580"]]
218 +[[image:1665301570342-765.png]]
213 213  
214 214  
215 215  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -276,7 +276,7 @@
276 276  
277 277  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
278 278  
279 -(% _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)(%%)  
280 280  
281 281  
282 282  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -285,7 +285,6 @@
285 285  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit
286 286  |=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
287 287  
288 -
289 289  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
290 290  
291 291  
... ... @@ -304,7 +304,7 @@
304 304  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
305 305  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
306 306  
307 -[[image:1665301636888-168.png||_mstalt="298012"]]
312 +[[image:1665301636888-168.png]]
308 308  
309 309  
310 310  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -334,12 +334,12 @@
334 334  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:
335 335  
336 336  
337 -[[image:1664502116362-706.png||_mstalt="293306"]]
342 +[[image:1664502116362-706.png]]
338 338  
339 339  
340 340  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
341 341  
342 -[[image:1664502166010-515.png||_mstalt="291395"]]
347 +[[image:1664502166010-515.png]]
343 343  
344 344  
345 345  
... ... @@ -402,6 +402,7 @@
402 402  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
403 403  
404 404  
410 +
405 405  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
406 406  
407 407  
... ... @@ -417,13 +417,14 @@
417 417  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
418 418  
419 419  (% class="wikigeneratedid" %)
420 -[[image:1665301687277-443.png||_mstalt="296140"]]
426 +[[image:1665301687277-443.png]]
421 421  
422 422  
429 +
423 423  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
424 424  
425 425  
426 -Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
433 +Set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
427 427  
428 428  
429 429  (% style="color:red" %)**Note for this mode:**
... ... @@ -440,9 +440,10 @@
440 440  )))|4|4|2|1|1|1|1|1
441 441  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
442 442  
443 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
450 +[[image:image-20221009160309-2.png]]
444 444  
445 445  
453 +
446 446  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
447 447  
448 448  
... ... @@ -467,7 +467,7 @@
467 467  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
468 468  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
469 469  
470 -[[image:1664502425687-834.png||_mstalt="296738"]]
478 +[[image:1664502425687-834.png]]
471 471  
472 472  
473 473  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -478,7 +478,6 @@
478 478  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
479 479  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
480 480  
481 -
482 482  === 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
483 483  
484 484  
... ... @@ -494,7 +494,7 @@
494 494  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
495 495  
496 496  (% class="wikigeneratedid" %)
497 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
504 +[[image:1667288597595-714.png||height="212" width="1151"]]
498 498  
499 499  
500 500  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -501,7 +501,6 @@
501 501  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
502 502  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
503 503  
504 -
505 505  === 2.4.7  Add Payload format in TTN V3 ===
506 506  
507 507  
... ... @@ -510,10 +510,9 @@
510 510  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
511 511  
512 512  
513 -[[image:1664502649601-895.png||_mstalt="296985"]]
519 +[[image:1664502649601-895.png]]
514 514  
515 515  
516 -
517 517  Add the decoder from this link: 
518 518  
519 519  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -520,9 +520,10 @@
520 520  
521 521  Save the change the uplink message will be parsed. As below:
522 522  
523 -[[image:1664502676891-606.png||_mstalt="296673"]]
528 +[[image:1664502676891-606.png]]
524 524  
525 525  
531 +
526 526  == 2.5 Integrate with Datacake ==
527 527  
528 528  
... ... @@ -531,9 +531,10 @@
531 531  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]]
532 532  
533 533  
534 -[[image:1664502695771-538.png||_mstalt="297349"]]
540 +[[image:1664502695771-538.png]]
535 535  
536 536  
543 +
537 537  == 2.6 Integrate with Tago ==
538 538  
539 539  
... ... @@ -542,24 +542,26 @@
542 542  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]]
543 543  
544 544  
545 -[[image:1664502715371-321.png||_mstalt="292162"]]
552 +[[image:1664502715371-321.png]]
546 546  
547 547  
555 +
548 548  == 2.7  Datalog Feature ==
549 549  
550 550  
551 551  total 273 entries,by default,
552 552  
553 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
561 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
554 554  
555 555  Example use case.
556 556  
557 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
565 +[[image:image-20221009234703-2.png||height="328" width="899"]]
558 558  
559 559  
560 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
568 +[[image:image-20221009234629-1.png||height="390" width="577"]]
561 561  
562 562  
571 +
563 563  == 2.8 Alarm Mode ==
564 564  
565 565  
... ... @@ -574,7 +574,7 @@
574 574  
575 575  
576 576  (((
577 -**Two ways to exit alarm mode:**
586 +Two ways to exit alarm mode:
578 578  )))
579 579  
580 580  * Server sends a downlink command to exit.
... ... @@ -585,14 +585,12 @@
585 585  )))
586 586  
587 587  
597 +
588 588  == 2.9 Transport Mode ==
589 589  
590 590  
591 591  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.
592 592  
593 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
594 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
595 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
596 596  
597 597  
598 598  == 2.10 LED Status ==
... ... @@ -612,13 +612,12 @@
612 612  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
613 613  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
614 614  
615 -
616 616  == 2.11 Button Function ==
617 617  
618 618  
619 619  (% style="color:blue" %)**RESET button:**
620 620  
621 -[[image:1664502835802-546.png||_mstalt="295061"]]
627 +[[image:1664502835802-546.png]]
622 622  
623 623  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
624 624  
... ... @@ -625,7 +625,7 @@
625 625  
626 626  (% style="color:red" %)**RED button:**
627 627  
628 -[[image:1664502854406-763.png||_mstalt="295568"]]
634 +[[image:1664502854406-763.png]]
629 629  
630 630  
631 631  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -634,7 +634,6 @@
634 634  |(% style="width:135px" %)Exit Alarm Mode|(% style="width:220px" %)Fast press the (% style="color:red" %)**RED** (%%)button 10 times|(% style="width:265px" %)Exit Alarm Mode
635 635  |(% style="width:135px" %)Enter Deep Sleep Mode|(% style="width:220px" %)Press and hold the button for 10 seconds, then quickly press the device 3 times to enter deep sleep|(% style="width:265px" %)This is the mode ship out from factory. CPU will be complete in sleep mode and no LoRa activity, only use before deploy.
636 636  
637 -
638 638  == 2.12 USB Port Function ==
639 639  
640 640  
... ... @@ -645,7 +645,6 @@
645 645  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
646 646  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
647 647  
648 -
649 649  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
650 650  
651 651  
... ... @@ -654,6 +654,7 @@
654 654  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
655 655  
656 656  
661 +
657 657  == 3.1 Access AT Command ==
658 658  
659 659  
... ... @@ -660,23 +660,25 @@
660 660  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.
661 661  
662 662  
663 -[[image:1664502999401-486.png||_mstalt="296985"]]
668 +[[image:1664502999401-486.png]]
664 664  
665 665  
666 666  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:
667 667  
668 668  
669 -[[image:1664503022490-662.png||_mstalt="293332"]]
674 +[[image:1664503022490-662.png]]
670 670  
671 671  
672 -[[image:1664503035713-500.png||_mstalt="291096"]]
677 +[[image:1664503035713-500.png]]
673 673  
674 674  
675 -[[image:1664503047675-651.png||_mstalt="295386"]]
680 +[[image:1664503047675-651.png]]
676 676  
677 677  
683 +
678 678  == 3.2 Command Set ==
679 679  
686 +
680 680  === 3.2.1 Set Transmit Interval ===
681 681  
682 682  
... ... @@ -694,6 +694,7 @@
694 694  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
695 695  
696 696  
704 +
697 697  === 3.2.2 Set Alarm Packet transmission interval ===
698 698  
699 699  
... ... @@ -711,6 +711,7 @@
711 711  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
712 712  
713 713  
722 +
714 714  === 3.2.3 Set Transport Mode Packet transmission interval ===
715 715  
716 716  
... ... @@ -728,6 +728,7 @@
728 728  (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
729 729  
730 730  
740 +
731 731  === 3.2.4 Exit Alarm ===
732 732  
733 733  
... ... @@ -740,6 +740,7 @@
740 740  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
741 741  
742 742  
753 +
743 743  === 3.2.5 Disable/Enable LED flash ===
744 744  
745 745  
... ... @@ -757,6 +757,7 @@
757 757  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
758 758  
759 759  
771 +
760 760  === 3.2.6 Disable/Enable Transport Mode ===
761 761  
762 762  
... ... @@ -774,6 +774,7 @@
774 774  (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
775 775  
776 776  
789 +
777 777  === 3.2.7 Set Positioning Mode ===
778 778  
779 779  
... ... @@ -800,9 +800,9 @@
800 800  
801 801  (% style="color:#037691" %)**cc:   **
802 802  
803 -* (% _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  
804 804  
805 -* (% _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(%%))  
806 806  
807 807  (% style="color:blue" %)**Example:**
808 808  
... ... @@ -820,6 +820,7 @@
820 820  (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
821 821  
822 822  
836 +
823 823  === 3.2.8 Set MAX GPS position time ===
824 824  
825 825  
... ... @@ -826,7 +826,7 @@
826 826  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.
827 827  
828 828  
829 -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.
830 830  
831 831  
832 832  * (% style="color:blue" %)**AT Command:**
... ... @@ -841,6 +841,7 @@
841 841  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
842 842  
843 843  
858 +
844 844  === 3.2.9 Set PDOP value for GPS fix accuracy ===
845 845  
846 846  
... ... @@ -864,8 +864,8 @@
864 864  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
865 865  
866 866  
867 -=== 3.2.10 Disable/Enable the confirmation mode ===
868 868  
883 +Disable/Enable the confirmation mode
869 869  
870 870  * (% style="color:blue" %)**AT Command:**
871 871  
... ... @@ -884,9 +884,10 @@
884 884  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
885 885  
886 886  
887 -=== 3.2.11  Auto Send None-ACK messages ===
888 888  
903 +=== 3.2.10  Auto Send None-ACK messages ===
889 889  
905 +
890 890  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.
891 891  
892 892  
... ... @@ -902,12 +902,13 @@
902 902  
903 903  * (% style="color:blue" %)**Downlink Command: 0x34**
904 904  
905 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
921 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
906 906  
907 907  
908 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
909 909  
925 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
910 910  
927 +
911 911  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.
912 912  
913 913  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -914,18 +914,19 @@
914 914  
915 915  (% style="color:blue" %)**AT Command:**
916 916  
917 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
934 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
918 918  
919 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
936 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
920 920  
921 921  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
922 922  
923 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
940 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
924 924  
925 925  
926 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
927 927  
944 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
928 928  
946 +
929 929  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.
930 930  
931 931  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
... ... @@ -932,61 +932,44 @@
932 932  
933 933  (% style="color:blue" %)**AT Command:**
934 934  
935 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
953 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
936 936  
937 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
955 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
938 938  
939 939  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
940 940  
941 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
959 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
942 942  
943 943  
944 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
945 945  
963 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
946 946  
965 +
947 947  Users can use this feature to enable/disable Information printing.
948 948  
949 949  (% style="color:blue" %)**AT Command:**
950 950  
951 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
970 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
952 952  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
953 953  
954 954  
955 -=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
956 956  
975 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
957 957  
977 +
958 958  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
959 959  
960 960  (% style="color:blue" %)**AT Command:**
961 961  
962 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
982 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
963 963  
964 964  
965 965  (% style="color:blue" %)**Downlink Payload:0X24**
966 966  
967 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
987 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
968 968  
969 969  
970 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
971 971  
972 -
973 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
974 -
975 -(% style="color:blue" %)**AT Command:**
976 -
977 -(% style="color:#037691" %)**AT+PT=xx**
978 -
979 - Example:
980 -
981 - AT+PT=14    ~-~->    Set to detect car motion.
982 -
983 - AT+PT=41  ~-~->    set to detect walk motion.
984 -
985 -
986 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
987 -0xB4 14          ~/~/  Same as AT+PT=14
988 -
989 -
990 990  = 4. Setting for Different Scenarios =
991 991  
992 992  
... ... @@ -993,6 +993,7 @@
993 993  
994 994  = 5. Upload Firmware =
995 995  
997 +
996 996  == 5.1 Firmware Change Log ==
997 997  
998 998  
... ... @@ -999,6 +999,7 @@
999 999  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1000 1000  
1001 1001  
1004 +
1002 1002  == 5.2 How to upgrade firmware ==
1003 1003  
1004 1004  
... ... @@ -1019,10 +1019,10 @@
1019 1019  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1020 1020  
1021 1021  
1022 -[[image:1664503563660-578.png||_mstalt="296777"]]
1025 +[[image:1664503563660-578.png]]
1023 1023  
1024 1024  
1025 -[[image:1664503574618-659.png||_mstalt="297986"]]
1028 +[[image:1664503574618-659.png]]
1026 1026  
1027 1027  
1028 1028  
... ... @@ -1031,7 +1031,7 @@
1031 1031  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1032 1032  
1033 1033  
1034 -**Users need to use below files:**
1037 +Users need to use below files:
1035 1035  
1036 1036  boot_app0.bin @0e000
1037 1037  
... ... @@ -1038,19 +1038,22 @@
1038 1038  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1039 1039  
1040 1040  
1041 -[[image:image-20221207120501-1.png]]
1044 +[[image:image-20221118105220-2.png]]
1042 1042  
1043 1043  
1044 1044  
1045 1045  After upgrade finish, it will show finish as below:
1046 1046  
1047 -[[image:image-20221207133911-7.png]]
1050 +[[image:image-20221118105402-4.png]]
1048 1048  
1049 1049  
1053 +
1050 1050  = 6. Developer Guide =
1051 1051  
1056 +
1052 1052  == 6.1 Compile Source Code ==
1053 1053  
1059 +
1054 1054  === 6.1.1 Set up ARDUINO compile environment ===
1055 1055  
1056 1056  
... ... @@ -1059,71 +1059,24 @@
1059 1059  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]]
1060 1060  
1061 1061  
1062 -[[image:1664503635019-941.png||_mstalt="294658"]]
1068 +[[image:1664503635019-941.png]]
1063 1063  
1064 1064  
1065 1065  
1066 1066  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1067 1067  
1068 -[[image:1664503715811-892.png||_mstalt="295698"]]
1074 +[[image:1664503715811-892.png]]
1069 1069  
1070 1070  
1071 -=== 6.1.2 Build the development environment ===
1072 -
1073 -~1. Download and install arduino IDE
1074 -
1075 -[[https:~~/~~/www.arduino.cn/thread-5838-1-1.html>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fwww.arduino.cn%2Fthread-5838-1-1.html]]
1076 -
1077 -
1078 -2. Download the ESP32 development package in the arduino IDE
1079 -
1080 -[[image:image-20221213100007-1.png]]
1081 -
1082 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1083 -
1084 -[[image:image-20221213100626-2.png]]
1085 -
1086 -Restart the IDE after the addition is complete, then:
1087 -
1088 -[[image:image-20221213100808-3.png||height="679" width="649"]]
1089 -
1090 -[[image:image-20221213101040-4.png]]
1091 -
1092 -**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1093 -Don't quit halfway.~~! If you quit halfway, there is a high probability that it will freeze, and you will need to download again next time. (If you click to continue downloading, an error will be reported after completion)**
1094 -
1095 -Then enter a long waiting process. If you don't want to wait, you can go to the Internet to download directly, and then import:
1096 -
1097 -Methods as below:
1098 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1099 -
1100 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1101 -
1102 1102  (% 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.
1103 1103  
1104 -[[image:image-20221213102311-5.png||height="582" width="711"]]
1079 +[[image:image-20221024105643-1.png]]
1105 1105  
1106 -3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)
1107 -
1108 -[[image:image-20221213102334-6.png]]
1109 -
1110 -**Note: This step requires a python environment**
1111 -
1112 -Either way, in the end:
1113 -The final effect is to open the arduino and you can see the esp32
1114 -
1115 -[[image:image-20221213110952-8.png||height="866" width="711"]]
1116 -
1117 -
1118 -
1119 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1120 -
1121 1121  **~ Figure1**
1122 1122  
1123 1123  
1084 +[[image:image-20221024105643-2.png]]
1124 1124  
1125 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1126 -
1127 1127   **Figure2**
1128 1128  
1129 1129  
... ... @@ -1132,31 +1132,34 @@
1132 1132  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1133 1133  
1134 1134  
1135 -[[image:1664503752288-974.png||_mstalt="298194"]]
1094 +[[image:1664503752288-974.png]]
1136 1136  
1137 1137  
1097 +
1138 1138  == 6.2 Source Code ==
1139 1139  
1140 1140  
1141 1141  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1142 1142  
1143 -[[image:1664503794261-827.png||_mstalt="296387"]]
1103 +[[image:1664503794261-827.png]]
1144 1144  
1145 1145  
1146 1146  
1147 1147  * (% style="color:blue" %)**Click to upload**
1148 1148  
1149 -[[image:1664503808294-336.png||_mstalt="295711"]]
1109 +[[image:1664503808294-336.png]]
1150 1150  
1151 1151  
1152 1152  
1153 1153  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1154 1154  
1155 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1115 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1156 1156  
1157 1157  
1118 +
1158 1158  = 7.  FAQ =
1159 1159  
1121 +
1160 1160  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1161 1161  
1162 1162  
... ... @@ -1163,10 +1163,11 @@
1163 1163  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1164 1164  
1165 1165  
1128 +
1166 1166  == 7.2 What is the pin mapping for the USB program cable? ==
1167 1167  
1168 1168  
1169 -[[image:1664499635206-262.png||_mstalt="295360"]]
1132 +[[image:1664499635206-262.png]]
1170 1170  
1171 1171  
1172 1172  
... ... @@ -1181,9 +1181,9 @@
1181 1181  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1182 1182  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1183 1183  
1184 -
1185 1185  == 7.3 Notes on using different serial port tools for TrackerD ==
1186 1186  
1149 +
1187 1187  === 7.3.1  Serial port utility ===
1188 1188  
1189 1189  
... ... @@ -1191,16 +1191,18 @@
1191 1191  
1192 1192  Need to adjust the data stream to RTS/CTS on physical restart.
1193 1193  
1157 +
1194 1194  (% class="wikigeneratedid" %)
1195 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1159 +[[image:image-20221102140621-1.png]]
1196 1196  
1197 1197  
1198 -
1199 1199  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1200 1200  
1201 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1202 1202  
1165 +[[image:image-20221102140638-2.png]]
1203 1203  
1167 +
1168 +
1204 1204  === 7.3.2  SecureCRT ===
1205 1205  
1206 1206  
... ... @@ -1207,22 +1207,23 @@
1207 1207  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.
1208 1208  
1209 1209  
1210 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1175 +[[image:image-20221102140704-3.png]]
1211 1211  
1212 1212  
1213 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1178 +[[image:image-20221102140712-4.png]]
1214 1214  
1215 1215  
1181 +
1216 1216  === 7.3.3  PUTTY ===
1217 1217  
1218 1218  
1219 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1185 +[[image:image-20221102140748-5.png]]
1220 1220  
1221 1221  
1222 1222  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.
1223 1223  
1224 1224  
1225 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1191 +[[image:image-20221102140801-6.png]]
1226 1226  
1227 1227  
1228 1228  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1234,46 +1234,38 @@
1234 1234  See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1235 1235  )))
1236 1236  
1237 -**~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.
1238 1238  
1205 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1239 1239  
1240 -[[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).
1241 1241  
1209 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1242 1242  
1211 +3.Compile the AS923_JP band, please refer to the intention shown
1243 1243  
1244 -**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"]]
1245 1245  
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.
1246 1246  
1247 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1217 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1248 1248  
1219 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1249 1249  
1250 1250  
1251 -**3. Compile the AS923_JP band, please refer to the intention shown**
1252 1252  
1253 -
1254 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1255 -
1256 -
1257 -
1258 -**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.**
1259 -
1260 -
1261 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1262 -
1263 -
1264 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1265 -
1266 -
1267 1267  = 8  Trouble Shooting =
1268 1268  
1225 +
1269 1269  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1270 1270  
1271 1271  
1272 1272  (((
1273 -Before firmware v1.4.0: When the Transport Mode is enabled ((% style="color:blue" %)**AT+INTWK=1**(%%)), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1230 +Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1274 1274  )))
1275 1275  
1276 1276  
1234 +
1277 1277  == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1278 1278  
1279 1279  
... ... @@ -1282,151 +1282,46 @@
1282 1282  )))
1283 1283  
1284 1284  
1243 +
1285 1285  == 8.3  Problem after Upgrading Firmware ==
1286 1286  
1287 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1246 +=== 8.3.1 Continue Restart after upgrading ===
1288 1288  
1289 1289  
1290 -**Error Output**
1291 -
1292 -
1293 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1294 -
1295 -
1296 1296  (((
1297 -Some partition is missed during upgrade, please upgrade below four files as example:
1298 -
1299 -[[image:image-20221207120524-2.png]]
1250 +If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
1300 1300  )))
1301 1301  
1302 1302  
1303 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1254 +[[image:image-20221118105249-3.png]]
1304 1304  
1305 1305  
1257 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1258 +
1306 1306  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
1307 1307  
1308 1308  
1309 -=== 8.3.3 "flash read err" after upgrade firmware ===
1262 +(((
1263 +== 8.5 How to deal with unsuccessful GPS positioning? ==
1310 1310  
1311 -
1312 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1313 -
1314 -
1315 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1316 -
1317 -
1318 -User need to upgrade again with below four files to solve this issue.
1319 -
1320 - [[image:image-20221207120530-3.png]]
1321 -
1322 - **Figure 2**
1323 -
1324 -
1325 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1326 -
1327 -
1328 -User might erase the entire flash include keys and default settings which cause this issue.
1329 -
1330 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1331 -
1332 -
1333 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1334 -
1335 -
1336 -Please (% style="color:blue" %)**AT+FDR**(%%) which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1337 -
1338 -After AT+FDR. please set
1339 -
1340 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1341 -
1342 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1343 -
1344 -**Example:**
1345 -
1346 -AT+PDOP=7.00
1347 -
1348 -AT+FTIME=180
1349 -
1350 -AT+DEUI=70B3D57ED0053981  
1351 -
1352 -AT+APPEUI=D23345667BCBCCAF
1353 -
1354 -AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1355 -
1356 -AT+DADDR=260b4dce    ( no need for OTAA)
1357 -
1358 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1359 -
1360 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1361 -
1362 -
1363 -== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1364 -
1365 -
1366 -Please download version 1.4.2 again
1367 -
1368 -
1369 -== 8.5  How to deal with unsuccessful GPS positioning? ==
1370 -
1371 -
1372 -1） Make Sure the device is in Open Area where can see the sky.
1373 -
1265 +1） Make Sure the device is in Open Area where can see the sky. 
1374 1374  2)  Set PDOP to a higher value.
1375 1375  
1376 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1268 + AT+PDOP=2(can be positioned precisely.）
1377 1377  
1378 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1270 + AT+PDOP=7(Quickly locate in open spaces）
1379 1379  
1380 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1272 + AT+PDOP=14.7(Positioning can be acquired in complex environments）
1381 1381  
1382 1382  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 +)))
1383 1383  
1384 1384  
1385 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1278 +== 8.6 When positioning, it will restart or the PDOP setting is unsuccessful ==
1386 1386  
1280 +Please download version 1.4.2 again
1387 1387  
1388 -When upgrading, use the erase button to upgrade
1389 1389  
1390 -[[image:image-20221207120536-4.png]]
1391 -
1392 -
1393 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1394 -
1395 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1396 -
1397 -
1398 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1399 -
1400 -[[image:image-20221207134028-8.png]]
1401 -
1402 -
1403 -Reboot information after upgrade
1404 -
1405 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1406 -
1407 -
1408 -Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal
1409 -
1410 -[[image:image-20221128111850-5.png]]
1411 -
1412 -
1413 -After the parameters return to normal, upgrade to the version you need again
1414 -
1415 -[[image:image-20221207120601-5.png]]
1416 -
1417 -
1418 -At this point, the parameters return to normal after running AT+FDR again
1419 -
1420 -[[image:image-20221128112035-7.png]]
1421 -
1422 -
1423 -== 8.7 If you encounter the following problems, please upgrade to the latest version ==
1424 -
1425 -~1. At present, the trackerD has been set up and connected to the server. You can regularly see the reported power/temperature and other information on the TTN, but press and hold the red button (more than 5 seconds), and the device and server do not respond.
1426 -
1427 -2.Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1428 -
1429 -
1430 1430  = 9.  Order Info =
1431 1431  
1432 1432  
... ... @@ -1435,20 +1435,13 @@
1435 1435  (% style="color:blue" %)**XXX**(%%): The default frequency band
1436 1436  
1437 1437  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1438 -
1439 1439  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1440 -
1441 1441  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1442 -
1443 1443  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1444 -
1445 1445  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1446 -
1447 1447  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1448 -
1449 1449  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1450 1450  
1451 -
1452 1452  = 10.  Packing Info =
1453 1453  
1454 1454  
... ... @@ -1455,30 +1455,22 @@
1455 1455  (% style="color:#037691" %)**Package Includes**:
1456 1456  
1457 1457  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1458 -
1459 1459  * USB recharge & program cable x 1
1460 1460  
1461 1461  (% style="color:#037691" %)**Dimensions and Weight**:
1462 1462  
1463 1463  * Device Size: 85 x 48 x 15 mm
1464 -
1465 1465  * Weight: 50g
1466 1466  
1467 -
1468 1468  = 11. Support =
1469 1469  
1470 1470  
1471 1471  * 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.
1472 -
1473 1473  * 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]].
1474 1474  
1475 -
1476 1476  = 12.  Reference =
1477 1477  
1478 1478  
1479 1479  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1480 -
1481 1481  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1482 -
1483 1483  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1484 -)))
image-20221122100004-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -22.3 KB
Content
image-20221128102938-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -41.3 KB
Content
image-20221128103040-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -19.2 KB
Content
image-20221128110503-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.6 KB
Content
image-20221128111443-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -15.6 KB
Content
image-20221128111850-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.5 KB
Content
image-20221128111951-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.4 KB
Content
image-20221128112035-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.7 KB
Content
image-20221207120501-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120524-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120530-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120536-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120601-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207133836-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.1 KB
Content
image-20221207133911-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -46.3 KB
Content
image-20221207134028-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.3 KB
Content
image-20221213100007-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -32.7 KB
Content
image-20221213100626-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -35.7 KB
Content
image-20221213100808-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -91.3 KB
Content
image-20221213101040-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -26.3 KB
Content
image-20221213102311-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.7 KB
Content
image-20221213102334-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.5 KB
Content
image-20221213102718-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -116.5 KB
Content
image-20221213110952-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -152.8 KB
Content