Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 155.3
edited by Xiaoling
on 2022/11/24 17: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.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:1664505654417-133.png||_mstalt="293696"]]
2 +[[image:1664505654417-133.png]]
3 3  
4 4  
5 5  
... ... @@ -14,6 +14,7 @@
14 14  
15 15  = 1.  Introduction =
16 16  
17 +
17 17  == 1.1  What is TrackerD ==
18 18  
19 19  
... ... @@ -31,17 +31,21 @@
31 31  (((
32 32  The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
33 33  )))
35 +)))
34 34  
35 35  (((
36 36  TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.
39 +
40 +
37 37  )))
38 38  
39 -[[image:1664499921684-770.png||_mstalt="298194"]]
43 +[[image:1664499921684-770.png]]
40 40  
41 41  
42 42  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
43 43  
44 44  
49 +
45 45  == 1.2 Specifications ==
46 46  
47 47  
... ... @@ -56,13 +56,11 @@
56 56  * EEPROM: 520 KB
57 57  * Clock Speed: 32Mhz
58 58  
59 -
60 60  (% style="color:blue" %)**Common DC Characteristics:**
61 61  
62 62  * Supply Voltage: 5V via USB port or Internal li-on battery
63 63  * Operating Temperature: -40 ~~ 60°C
64 64  
65 -
66 66  (% style="color:blue" %)**LoRa Spec:**
67 67  
68 68  * Frequency Range,
... ... @@ -84,12 +84,10 @@
84 84  * Packet engine up to 256 bytes with CRC.
85 85  * LoRaWAN 1.0.3 Specification
86 86  
87 -
88 88  (% style="color:blue" %)**Battery:**
89 89  
90 90  * 1000mA Li-on Battery power (for model TrackerD)
91 91  
92 -
93 93  (% style="color:blue" %)**Power Consumption**
94 94  
95 95  * Sleeping Mode: 200uA
... ... @@ -96,9 +96,6 @@
96 96  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
97 97  * Tracking: max: 38mA
98 98  
99 -
100 -
101 -
102 102  == 1.3  Features ==
103 103  
104 104  
... ... @@ -117,10 +117,6 @@
117 117  * Tri-color LED, Alarm button
118 118  * Datalog
119 119  
120 -
121 -
122 -
123 -
124 124  == 1.4  Applications ==
125 125  
126 126  
... ... @@ -127,11 +127,9 @@
127 127  * Logistics and Supply Chain Management
128 128  * Human tracking
129 129  
130 -
131 -
132 -
133 133  = 2.  Use TrackerD =
134 134  
126 +
135 135  == 2.1 How it works? ==
136 136  
137 137  
... ... @@ -138,6 +138,7 @@
138 138  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.
139 139  
140 140  
133 +
141 141  == 2.2 Quick guide to connect to LoRaWAN server ==
142 142  
143 143  
... ... @@ -144,7 +144,7 @@
144 144  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. 
145 145  
146 146  
147 -[[image:1664501652064-326.png||_mstalt="293306"]]
140 +[[image:1664501652064-326.png]]
148 148  
149 149  
150 150  
... ... @@ -156,7 +156,7 @@
156 156  Each TrackerD is shipped with a sticker with the default device EUI as below:
157 157  
158 158  
159 -[[image:1664501677253-891.png||_mstalt="296569"]]
152 +[[image:1664501677253-891.png]]
160 160  
161 161  
162 162  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -165,14 +165,14 @@
165 165  **__Add APP EUI in the application:__**
166 166  
167 167  
168 -[[image:1664501711466-918.png||_mstalt="295828"]]
161 +[[image:1664501711466-918.png]]
169 169  
170 170  
171 171  
172 -[[image:1664501721248-725.png||_mstalt="294450"]]
165 +[[image:1664501721248-725.png]]
173 173  
174 174  
175 -[[image:1664501734705-405.png||_mstalt="293306"]]
168 +[[image:1664501734705-405.png]]
176 176  
177 177  
178 178  
... ... @@ -179,20 +179,21 @@
179 179  **__Add APP KEY and DEV EUI:__**
180 180  
181 181  
182 -[[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"]]
183 183  
184 184  
185 185  
186 186  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
187 187  
188 -(% 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]]
189 189  
190 -[[image:1664502835802-546.png||_mstalt="295061"]]
183 +[[image:1664502835802-546.png]]
191 191  
192 192  
193 193  (% 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.
194 194  
195 195  
189 +
196 196  == 2.3  Positioning Mode(SMOD) ==
197 197  
198 198  
... ... @@ -205,8 +205,10 @@
205 205  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
206 206  
207 207  
202 +
208 208  == 2.4  Uplink Payload ==
209 209  
205 +
210 210  === 2.4.1 Uplink FPORT~=5, Device Status ===
211 211  
212 212  
... ... @@ -219,7 +219,7 @@
219 219  |=(% 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
220 220  |=(% 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
221 221  
222 -[[image:1665301570342-765.png||_mstalt="294580"]]
218 +[[image:1665301570342-765.png]]
223 223  
224 224  
225 225  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -286,7 +286,7 @@
286 286  
287 287  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
288 288  
289 -(% _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)(%%)  
290 290  
291 291  
292 292  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -295,7 +295,6 @@
295 295  |=(% 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
296 296  |=(% 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"]]
297 297  
298 -
299 299  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
300 300  
301 301  
... ... @@ -314,7 +314,7 @@
314 314  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
315 315  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
316 316  
317 -[[image:1665301636888-168.png||_mstalt="298012"]]
312 +[[image:1665301636888-168.png]]
318 318  
319 319  
320 320  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -344,12 +344,12 @@
344 344  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:
345 345  
346 346  
347 -[[image:1664502116362-706.png||_mstalt="293306"]]
342 +[[image:1664502116362-706.png]]
348 348  
349 349  
350 350  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
351 351  
352 -[[image:1664502166010-515.png||_mstalt="291395"]]
347 +[[image:1664502166010-515.png]]
353 353  
354 354  
355 355  
... ... @@ -372,9 +372,6 @@
372 372  * 3.40v ~~ 3.69v:  20% ~~ 40%
373 373  * < 3.39v:  0~~20%
374 374  
375 -
376 -
377 -
378 378  ==== (% style="color:blue" %)**MOD:**(%%) ====
379 379  
380 380  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -415,6 +415,7 @@
415 415  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
416 416  
417 417  
410 +
418 418  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
419 419  
420 420  
... ... @@ -430,13 +430,14 @@
430 430  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
431 431  
432 432  (% class="wikigeneratedid" %)
433 -[[image:1665301687277-443.png||_mstalt="296140"]]
426 +[[image:1665301687277-443.png]]
434 434  
435 435  
429 +
436 436  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
437 437  
438 438  
439 -Set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-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.
440 440  
441 441  
442 442  (% style="color:red" %)**Note for this mode:**
... ... @@ -453,9 +453,10 @@
453 453  )))|4|4|2|1|1|1|1|1
454 454  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
455 455  
456 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
450 +[[image:image-20221009160309-2.png]]
457 457  
458 458  
453 +
459 459  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
460 460  
461 461  
... ... @@ -480,7 +480,7 @@
480 480  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
481 481  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
482 482  
483 -[[image:1664502425687-834.png||_mstalt="296738"]]
478 +[[image:1664502425687-834.png]]
484 484  
485 485  
486 486  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -491,9 +491,6 @@
491 491  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
492 492  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
493 493  
494 -
495 -
496 -
497 497  === 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
498 498  
499 499  
... ... @@ -509,7 +509,7 @@
509 509  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
510 510  
511 511  (% class="wikigeneratedid" %)
512 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
504 +[[image:1667288597595-714.png||height="212" width="1151"]]
513 513  
514 514  
515 515  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -516,9 +516,6 @@
516 516  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
517 517  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
518 518  
519 -
520 -
521 -
522 522  === 2.4.7  Add Payload format in TTN V3 ===
523 523  
524 524  
... ... @@ -527,10 +527,9 @@
527 527  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
528 528  
529 529  
530 -[[image:1664502649601-895.png||_mstalt="296985"]]
519 +[[image:1664502649601-895.png]]
531 531  
532 532  
533 -
534 534  Add the decoder from this link: 
535 535  
536 536  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -537,9 +537,10 @@
537 537  
538 538  Save the change the uplink message will be parsed. As below:
539 539  
540 -[[image:1664502676891-606.png||_mstalt="296673"]]
528 +[[image:1664502676891-606.png]]
541 541  
542 542  
531 +
543 543  == 2.5 Integrate with Datacake ==
544 544  
545 545  
... ... @@ -548,9 +548,10 @@
548 548  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]]
549 549  
550 550  
551 -[[image:1664502695771-538.png||_mstalt="297349"]]
540 +[[image:1664502695771-538.png]]
552 552  
553 553  
543 +
554 554  == 2.6 Integrate with Tago ==
555 555  
556 556  
... ... @@ -559,24 +559,26 @@
559 559  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]]
560 560  
561 561  
562 -[[image:1664502715371-321.png||_mstalt="292162"]]
552 +[[image:1664502715371-321.png]]
563 563  
564 564  
555 +
565 565  == 2.7  Datalog Feature ==
566 566  
567 567  
568 568  total 273 entries,by default,
569 569  
570 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
561 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
571 571  
572 572  Example use case.
573 573  
574 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
565 +[[image:image-20221009234703-2.png||height="328" width="899"]]
575 575  
576 576  
577 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
568 +[[image:image-20221009234629-1.png||height="390" width="577"]]
578 578  
579 579  
571 +
580 580  == 2.8 Alarm Mode ==
581 581  
582 582  
... ... @@ -591,7 +591,7 @@
591 591  
592 592  
593 593  (((
594 -**Two ways to exit alarm mode:**
586 +Two ways to exit alarm mode:
595 595  )))
596 596  
597 597  * Server sends a downlink command to exit.
... ... @@ -602,18 +602,14 @@
602 602  )))
603 603  
604 604  
597 +
605 605  == 2.9 Transport Mode ==
606 606  
607 607  
608 608  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.
609 609  
610 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
611 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
612 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
613 613  
614 614  
615 -
616 -
617 617  == 2.10 LED Status ==
618 618  
619 619  
... ... @@ -631,13 +631,12 @@
631 631  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
632 632  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
633 633  
634 -
635 635  == 2.11 Button Function ==
636 636  
637 637  
638 638  (% style="color:blue" %)**RESET button:**
639 639  
640 -[[image:1664502835802-546.png||_mstalt="295061"]]
627 +[[image:1664502835802-546.png]]
641 641  
642 642  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
643 643  
... ... @@ -644,7 +644,7 @@
644 644  
645 645  (% style="color:red" %)**RED button:**
646 646  
647 -[[image:1664502854406-763.png||_mstalt="295568"]]
634 +[[image:1664502854406-763.png]]
648 648  
649 649  
650 650  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -653,7 +653,6 @@
653 653  |(% 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
654 654  |(% 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.
655 655  
656 -
657 657  == 2.12 USB Port Function ==
658 658  
659 659  
... ... @@ -664,9 +664,6 @@
664 664  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
665 665  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
666 666  
667 -
668 -
669 -
670 670  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
671 671  
672 672  
... ... @@ -675,6 +675,7 @@
675 675  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
676 676  
677 677  
661 +
678 678  == 3.1 Access AT Command ==
679 679  
680 680  
... ... @@ -681,24 +681,25 @@
681 681  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.
682 682  
683 683  
684 -[[image:1664502999401-486.png||_mstalt="296985"]]
668 +[[image:1664502999401-486.png]]
685 685  
686 686  
687 687  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:
688 688  
689 689  
690 -[[image:1664503022490-662.png||_mstalt="293332"]]
674 +[[image:1664503022490-662.png]]
691 691  
692 692  
693 -[[image:1664503035713-500.png||_mstalt="291096"]]
677 +[[image:1664503035713-500.png]]
694 694  
695 695  
696 -[[image:1664503047675-651.png||_mstalt="295386"]]
680 +[[image:1664503047675-651.png]]
697 697  
698 698  
699 699  
700 700  == 3.2 Command Set ==
701 701  
686 +
702 702  === 3.2.1 Set Transmit Interval ===
703 703  
704 704  
... ... @@ -716,6 +716,7 @@
716 716  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
717 717  
718 718  
704 +
719 719  === 3.2.2 Set Alarm Packet transmission interval ===
720 720  
721 721  
... ... @@ -733,6 +733,7 @@
733 733  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
734 734  
735 735  
722 +
736 736  === 3.2.3 Set Transport Mode Packet transmission interval ===
737 737  
738 738  
... ... @@ -750,6 +750,7 @@
750 750  (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
751 751  
752 752  
740 +
753 753  === 3.2.4 Exit Alarm ===
754 754  
755 755  
... ... @@ -762,6 +762,7 @@
762 762  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
763 763  
764 764  
753 +
765 765  === 3.2.5 Disable/Enable LED flash ===
766 766  
767 767  
... ... @@ -779,6 +779,7 @@
779 779  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
780 780  
781 781  
771 +
782 782  === 3.2.6 Disable/Enable Transport Mode ===
783 783  
784 784  
... ... @@ -796,6 +796,7 @@
796 796  (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
797 797  
798 798  
789 +
799 799  === 3.2.7 Set Positioning Mode ===
800 800  
801 801  
... ... @@ -822,9 +822,9 @@
822 822  
823 823  (% style="color:#037691" %)**cc:   **
824 824  
825 -* (% _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  
826 826  
827 -* (% _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(%%))  
828 828  
829 829  (% style="color:blue" %)**Example:**
830 830  
... ... @@ -842,6 +842,7 @@
842 842  (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
843 843  
844 844  
836 +
845 845  === 3.2.8 Set MAX GPS position time ===
846 846  
847 847  
... ... @@ -848,7 +848,7 @@
848 848  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.
849 849  
850 850  
851 -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.
852 852  
853 853  
854 854  * (% style="color:blue" %)**AT Command:**
... ... @@ -863,6 +863,7 @@
863 863  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
864 864  
865 865  
858 +
866 866  === 3.2.9 Set PDOP value for GPS fix accuracy ===
867 867  
868 868  
... ... @@ -887,7 +887,7 @@
887 887  
888 888  
889 889  
890 -=== 3.2.10 Disable/Enable the confirmation mode ===
883 +Disable/Enable the confirmation mode
891 891  
892 892  * (% style="color:blue" %)**AT Command:**
893 893  
... ... @@ -906,9 +906,10 @@
906 906  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
907 907  
908 908  
909 -=== 3.2.11  Auto Send None-ACK messages ===
910 910  
903 +=== 3.2.10  Auto Send None-ACK messages ===
911 911  
905 +
912 912  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.
913 913  
914 914  
... ... @@ -924,12 +924,13 @@
924 924  
925 925  * (% style="color:blue" %)**Downlink Command: 0x34**
926 926  
927 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
921 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
928 928  
929 929  
930 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
931 931  
925 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
932 932  
927 +
933 933  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.
934 934  
935 935  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -936,18 +936,19 @@
936 936  
937 937  (% style="color:blue" %)**AT Command:**
938 938  
939 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
934 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
940 940  
941 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
936 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
942 942  
943 943  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
944 944  
945 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
940 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
946 946  
947 947  
948 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
949 949  
944 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
950 950  
946 +
951 951  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.
952 952  
953 953  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
... ... @@ -954,18 +954,19 @@
954 954  
955 955  (% style="color:blue" %)**AT Command:**
956 956  
957 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
953 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
958 958  
959 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
955 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
960 960  
961 961  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
962 962  
963 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
959 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
964 964  
965 965  
966 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
967 967  
963 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
968 968  
965 +
969 969  Users can use this feature to enable/disable Information printing.
970 970  
971 971  (% style="color:blue" %)**AT Command:**
... ... @@ -974,9 +974,10 @@
974 974  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
975 975  
976 976  
977 -=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
978 978  
975 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
979 979  
977 +
980 980  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
981 981  
982 982  (% style="color:blue" %)**AT Command:**
... ... @@ -989,26 +989,7 @@
989 989  Example: 0x24 01 ~/~/ Same as AT+CHE=1
990 990  
991 991  
992 -=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
993 993  
994 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
995 -
996 -(% style="color:blue" %)**AT Command:**
997 -
998 -(% style="color:#037691" %)**AT+PT=xx**
999 -
1000 - Example:
1001 -
1002 - AT+PT=14    ~-~->    Set to detect car motion.
1003 -
1004 - AT+PT=41   ~-~->    set to detect walk motion.
1005 -
1006 -
1007 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
1008 -0xB4 14          ~/~/  Same as AT+PT=14
1009 -
1010 -
1011 -
1012 1012  = 4. Setting for Different Scenarios =
1013 1013  
1014 1014  
... ... @@ -1015,6 +1015,7 @@
1015 1015  
1016 1016  = 5. Upload Firmware =
1017 1017  
997 +
1018 1018  == 5.1 Firmware Change Log ==
1019 1019  
1020 1020  
... ... @@ -1021,6 +1021,7 @@
1021 1021  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1022 1022  
1023 1023  
1004 +
1024 1024  == 5.2 How to upgrade firmware ==
1025 1025  
1026 1026  
... ... @@ -1041,10 +1041,10 @@
1041 1041  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1042 1042  
1043 1043  
1044 -[[image:1664503563660-578.png||_mstalt="296777"]]
1025 +[[image:1664503563660-578.png]]
1045 1045  
1046 1046  
1047 -[[image:1664503574618-659.png||_mstalt="297986"]]
1028 +[[image:1664503574618-659.png]]
1048 1048  
1049 1049  
1050 1050  
... ... @@ -1053,7 +1053,7 @@
1053 1053  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1054 1054  
1055 1055  
1056 -**Users need to use below files:**
1037 +Users need to use below files:
1057 1057  
1058 1058  boot_app0.bin @0e000
1059 1059  
... ... @@ -1060,20 +1060,22 @@
1060 1060  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1061 1061  
1062 1062  
1063 -[[image:image-20221118105220-2.png||_mstalt="426608"]]
1044 +[[image:image-20221118105220-2.png]]
1064 1064  
1065 1065  
1066 1066  
1067 1067  After upgrade finish, it will show finish as below:
1068 1068  
1069 -[[image:image-20221118105402-4.png||_mstalt="427986"]]
1050 +[[image:image-20221118105402-4.png]]
1070 1070  
1071 1071  
1072 1072  
1073 1073  = 6. Developer Guide =
1074 1074  
1056 +
1075 1075  == 6.1 Compile Source Code ==
1076 1076  
1059 +
1077 1077  === 6.1.1 Set up ARDUINO compile environment ===
1078 1078  
1079 1079  
... ... @@ -1082,23 +1082,23 @@
1082 1082  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]]
1083 1083  
1084 1084  
1085 -[[image:1664503635019-941.png||_mstalt="294658"]]
1068 +[[image:1664503635019-941.png]]
1086 1086  
1087 1087  
1088 1088  
1089 1089  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1090 1090  
1091 -[[image:1664503715811-892.png||_mstalt="295698"]]
1074 +[[image:1664503715811-892.png]]
1092 1092  
1093 1093  
1094 1094  (% 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.
1095 1095  
1096 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1079 +[[image:image-20221024105643-1.png]]
1097 1097  
1098 1098  **~ Figure1**
1099 1099  
1100 1100  
1101 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1084 +[[image:image-20221024105643-2.png]]
1102 1102  
1103 1103   **Figure2**
1104 1104  
... ... @@ -1108,31 +1108,34 @@
1108 1108  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1109 1109  
1110 1110  
1111 -[[image:1664503752288-974.png||_mstalt="298194"]]
1094 +[[image:1664503752288-974.png]]
1112 1112  
1113 1113  
1097 +
1114 1114  == 6.2 Source Code ==
1115 1115  
1116 1116  
1117 1117  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1118 1118  
1119 -[[image:1664503794261-827.png||_mstalt="296387"]]
1103 +[[image:1664503794261-827.png]]
1120 1120  
1121 1121  
1122 1122  
1123 1123  * (% style="color:blue" %)**Click to upload**
1124 1124  
1125 -[[image:1664503808294-336.png||_mstalt="295711"]]
1109 +[[image:1664503808294-336.png]]
1126 1126  
1127 1127  
1128 1128  
1129 1129  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1130 1130  
1131 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1115 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1132 1132  
1133 1133  
1118 +
1134 1134  = 7.  FAQ =
1135 1135  
1121 +
1136 1136  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1137 1137  
1138 1138  
... ... @@ -1139,10 +1139,11 @@
1139 1139  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1140 1140  
1141 1141  
1128 +
1142 1142  == 7.2 What is the pin mapping for the USB program cable? ==
1143 1143  
1144 1144  
1145 -[[image:1664499635206-262.png||_mstalt="295360"]]
1132 +[[image:1664499635206-262.png]]
1146 1146  
1147 1147  
1148 1148  
... ... @@ -1157,9 +1157,9 @@
1157 1157  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1158 1158  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1159 1159  
1160 -
1161 1161  == 7.3 Notes on using different serial port tools for TrackerD ==
1162 1162  
1149 +
1163 1163  === 7.3.1  Serial port utility ===
1164 1164  
1165 1165  
... ... @@ -1167,16 +1167,18 @@
1167 1167  
1168 1168  Need to adjust the data stream to RTS/CTS on physical restart.
1169 1169  
1157 +
1170 1170  (% class="wikigeneratedid" %)
1171 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1159 +[[image:image-20221102140621-1.png]]
1172 1172  
1173 1173  
1174 -
1175 1175  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1176 1176  
1177 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1178 1178  
1165 +[[image:image-20221102140638-2.png]]
1179 1179  
1167 +
1168 +
1180 1180  === 7.3.2  SecureCRT ===
1181 1181  
1182 1182  
... ... @@ -1183,22 +1183,23 @@
1183 1183  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.
1184 1184  
1185 1185  
1186 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1175 +[[image:image-20221102140704-3.png]]
1187 1187  
1188 1188  
1189 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1178 +[[image:image-20221102140712-4.png]]
1190 1190  
1191 1191  
1181 +
1192 1192  === 7.3.3  PUTTY ===
1193 1193  
1194 1194  
1195 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1185 +[[image:image-20221102140748-5.png]]
1196 1196  
1197 1197  
1198 1198  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.
1199 1199  
1200 1200  
1201 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1191 +[[image:image-20221102140801-6.png]]
1202 1202  
1203 1203  
1204 1204  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1210,38 +1210,29 @@
1210 1210  See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1211 1211  )))
1212 1212  
1213 -**~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.
1214 1214  
1205 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1215 1215  
1216 -[[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).
1217 1217  
1209 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1218 1218  
1211 +3.Compile the AS923_JP band, please refer to the intention shown
1219 1219  
1220 -**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"]]
1221 1221  
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.
1222 1222  
1223 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1217 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1224 1224  
1219 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1225 1225  
1226 1226  
1227 -**3. Compile the AS923_JP band, please refer to the intention shown**
1228 1228  
1229 -
1230 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1231 -
1232 -
1233 -
1234 -**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.**
1235 -
1236 -
1237 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1238 -
1239 -
1240 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1241 -
1242 -
1243 1243  = 8  Trouble Shooting =
1244 1244  
1225 +
1245 1245  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1246 1246  
1247 1247  
... ... @@ -1250,6 +1250,7 @@
1250 1250  )))
1251 1251  
1252 1252  
1234 +
1253 1253  == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1254 1254  
1255 1255  
... ... @@ -1258,98 +1258,85 @@
1258 1258  )))
1259 1259  
1260 1260  
1243 +
1261 1261  == 8.3  Problem after Upgrading Firmware ==
1262 1262  
1263 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1246 +=== 8.3.1 Continue Restart after upgrading ===
1264 1264  
1265 -Error Output
1266 1266  
1267 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1268 -
1269 1269  (((
1270 -Some partition is missed during upgrade, please upgrade below four files as example:
1271 -
1272 -[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1250 +If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
1273 1273  )))
1274 1274  
1275 1275  
1276 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1254 +[[image:image-20221118105249-3.png]]
1277 1277  
1278 1278  
1257 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1258 +
1279 1279  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
1280 1280  
1281 1281  
1282 -=== 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 ====
1283 1283  
1284 -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"]]
1285 1285  
1286 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1266 + Figure 1  
1287 1287  
1268 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1288 1288  
1289 -User need to upgrade again with below four files to solve this issue.
1270 + Figure 2
1290 1290  
1291 - [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1292 -
1293 - **Figure 2**
1294 -
1295 -
1296 -=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1297 -
1298 -User might erase the entire flash include keys and default settings which cause this issue.
1299 -
1300 1300  After the upgrade is completed, enter AT+CFG as shown in the figure below.
1301 1301  
1302 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1274 +[[image:image-20221122100004-3.png]]
1303 1303  
1304 -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.
1276 +Please AT+FDR, and then enter the following instructions by the information on the label
1305 1305  
1306 -After AT+FDR. please set
1278 +AT+DEUI=70B3D57ED0053981
1307 1307  
1308 -* AT+PDOP=7
1309 -
1310 -* AT+FTIME=180000
1311 -
1312 -Example:
1313 -
1314 -AT+PDOP=7.00
1315 -
1316 -AT+FTIME=180
1317 -
1318 -AT+DEUI=70B3D57ED0053981  
1319 -
1320 1320  AT+APPEUI=D23345667BCBCCAF
1321 1321  
1322 1322  AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1323 1323  
1324 -AT+DADDR=260b4dce    ( no need for OTAA)
1284 +AT+DADDR=260b4dce
1325 1325  
1326 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1286 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1327 1327  
1328 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1288 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1329 1329  
1330 1330  
1331 -== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1332 1332  
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 ====
1333 1333  
1334 -Please download version 1.4.2 again
1294 +[[image:image-20221122100004-4.png]]
1335 1335  
1296 +== ==
1336 1336  
1337 -== 8.5  How to deal with unsuccessful GPS positioning? ==
1298 +== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==
1338 1338  
1300 +Please download version 1.4.2 again
1339 1339  
1340 -1） Make Sure the device is in Open Area where can see the sky.
1341 1341  
1303 +(((
1304 +== 8.5 How to deal with unsuccessful GPS positioning? ==
1305 +
1306 +1） Make Sure the device is in Open Area where can see the sky. 
1342 1342  2)  Set PDOP to a higher value.
1343 1343  
1344 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1309 + AT+PDOP=2(can be positioned precisely.）
1345 1345  
1346 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1311 + AT+PDOP=7(Quickly locate in open spaces）
1347 1347  
1348 -* (% _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）
1349 1349  
1350 1350  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 +)))
1351 1351  
1352 1352  
1319 +== ==
1320 +
1321 +
1353 1353  = 9.  Order Info =
1354 1354  
1355 1355  
... ... @@ -1358,22 +1358,13 @@
1358 1358  (% style="color:blue" %)**XXX**(%%): The default frequency band
1359 1359  
1360 1360  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1361 -
1362 1362  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1363 -
1364 1364  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1365 -
1366 1366  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1367 -
1368 1368  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1369 -
1370 1370  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1371 -
1372 1372  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1373 1373  
1374 -
1375 -
1376 -
1377 1377  = 10.  Packing Info =
1378 1378  
1379 1379  
... ... @@ -1380,33 +1380,22 @@
1380 1380  (% style="color:#037691" %)**Package Includes**:
1381 1381  
1382 1382  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1383 -
1384 1384  * USB recharge & program cable x 1
1385 1385  
1386 1386  (% style="color:#037691" %)**Dimensions and Weight**:
1387 1387  
1388 1388  * Device Size: 85 x 48 x 15 mm
1389 -
1390 1390  * Weight: 50g
1391 1391  
1392 -
1393 -
1394 -
1395 1395  = 11. Support =
1396 1396  
1397 1397  
1398 1398  * 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.
1399 -
1400 1400  * 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]].
1401 1401  
1402 -
1403 -
1404 -
1405 1405  = 12.  Reference =
1406 1406  
1407 1407  
1408 1408  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1409 -
1410 1410  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1411 -
1412 1412  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]