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

From version 155.4
edited by Xiaoling
on 2022/11/24 17:21
Change comment: There is no comment for this version
To version 142.1
edited by Bei Jinggeng
on 2022/11/22 10:02
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  
... ... @@ -92,8 +92,6 @@
92 92  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
93 93  * Tracking: max: 38mA
94 94  
95 -
96 -
97 97  == 1.3  Features ==
98 98  
99 99  
... ... @@ -112,8 +112,6 @@
112 112  * Tri-color LED, Alarm button
113 113  * Datalog
114 114  
115 -
116 -
117 117  == 1.4  Applications ==
118 118  
119 119  
... ... @@ -120,10 +120,9 @@
120 120  * Logistics and Supply Chain Management
121 121  * Human tracking
122 122  
123 -
124 -
125 125  = 2.  Use TrackerD =
126 126  
126 +
127 127  == 2.1 How it works? ==
128 128  
129 129  
... ... @@ -130,6 +130,7 @@
130 130  TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.
131 131  
132 132  
133 +
133 133  == 2.2 Quick guide to connect to LoRaWAN server ==
134 134  
135 135  
... ... @@ -136,7 +136,7 @@
136 136  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. 
137 137  
138 138  
139 -[[image:1664501652064-326.png||_mstalt="293306"]]
140 +[[image:1664501652064-326.png]]
140 140  
141 141  
142 142  
... ... @@ -148,7 +148,7 @@
148 148  Each TrackerD is shipped with a sticker with the default device EUI as below:
149 149  
150 150  
151 -[[image:1664501677253-891.png||_mstalt="296569"]]
152 +[[image:1664501677253-891.png]]
152 152  
153 153  
154 154  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -157,14 +157,14 @@
157 157  **__Add APP EUI in the application:__**
158 158  
159 159  
160 -[[image:1664501711466-918.png||_mstalt="295828"]]
161 +[[image:1664501711466-918.png]]
161 161  
162 162  
163 163  
164 -[[image:1664501721248-725.png||_mstalt="294450"]]
165 +[[image:1664501721248-725.png]]
165 165  
166 166  
167 -[[image:1664501734705-405.png||_mstalt="293306"]]
168 +[[image:1664501734705-405.png]]
168 168  
169 169  
170 170  
... ... @@ -171,20 +171,21 @@
171 171  **__Add APP KEY and DEV EUI:__**
172 172  
173 173  
174 -[[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"]]
175 175  
176 176  
177 177  
178 178  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
179 179  
180 -(% 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]]
181 181  
182 -[[image:1664502835802-546.png||_mstalt="295061"]]
183 +[[image:1664502835802-546.png]]
183 183  
184 184  
185 185  (% 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.
186 186  
187 187  
189 +
188 188  == 2.3  Positioning Mode(SMOD) ==
189 189  
190 190  
... ... @@ -197,8 +197,10 @@
197 197  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
198 198  
199 199  
202 +
200 200  == 2.4  Uplink Payload ==
201 201  
205 +
202 202  === 2.4.1 Uplink FPORT~=5, Device Status ===
203 203  
204 204  
... ... @@ -211,7 +211,7 @@
211 211  |=(% 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
212 212  |=(% 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
213 213  
214 -[[image:1665301570342-765.png||_mstalt="294580"]]
218 +[[image:1665301570342-765.png]]
215 215  
216 216  
217 217  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -278,7 +278,7 @@
278 278  
279 279  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
280 280  
281 -(% _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)(%%)  
282 282  
283 283  
284 284  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -287,8 +287,6 @@
287 287  |=(% 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
288 288  |=(% 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"]]
289 289  
290 -
291 -
292 292  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
293 293  
294 294  
... ... @@ -307,7 +307,7 @@
307 307  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
308 308  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
309 309  
310 -[[image:1665301636888-168.png||_mstalt="298012"]]
312 +[[image:1665301636888-168.png]]
311 311  
312 312  
313 313  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -337,12 +337,12 @@
337 337  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:
338 338  
339 339  
340 -[[image:1664502116362-706.png||_mstalt="293306"]]
342 +[[image:1664502116362-706.png]]
341 341  
342 342  
343 343  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
344 344  
345 -[[image:1664502166010-515.png||_mstalt="291395"]]
347 +[[image:1664502166010-515.png]]
346 346  
347 347  
348 348  
... ... @@ -365,8 +365,6 @@
365 365  * 3.40v ~~ 3.69v:  20% ~~ 40%
366 366  * < 3.39v:  0~~20%
367 367  
368 -
369 -
370 370  ==== (% style="color:blue" %)**MOD:**(%%) ====
371 371  
372 372  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -407,6 +407,7 @@
407 407  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
408 408  
409 409  
410 +
410 410  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
411 411  
412 412  
... ... @@ -422,13 +422,14 @@
422 422  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
423 423  
424 424  (% class="wikigeneratedid" %)
425 -[[image:1665301687277-443.png||_mstalt="296140"]]
426 +[[image:1665301687277-443.png]]
426 426  
427 427  
429 +
428 428  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
429 429  
430 430  
431 -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.
432 432  
433 433  
434 434  (% style="color:red" %)**Note for this mode:**
... ... @@ -445,9 +445,10 @@
445 445  )))|4|4|2|1|1|1|1|1
446 446  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
447 447  
448 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
450 +[[image:image-20221009160309-2.png]]
449 449  
450 450  
453 +
451 451  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
452 452  
453 453  
... ... @@ -472,7 +472,7 @@
472 472  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
473 473  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
474 474  
475 -[[image:1664502425687-834.png||_mstalt="296738"]]
478 +[[image:1664502425687-834.png]]
476 476  
477 477  
478 478  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -483,8 +483,6 @@
483 483  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
484 484  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
485 485  
486 -
487 -
488 488  === 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) ===
489 489  
490 490  
... ... @@ -500,7 +500,7 @@
500 500  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
501 501  
502 502  (% class="wikigeneratedid" %)
503 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
504 +[[image:1667288597595-714.png||height="212" width="1151"]]
504 504  
505 505  
506 506  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -507,8 +507,6 @@
507 507  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
508 508  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
509 509  
510 -
511 -
512 512  === 2.4.7  Add Payload format in TTN V3 ===
513 513  
514 514  
... ... @@ -517,10 +517,9 @@
517 517  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
518 518  
519 519  
520 -[[image:1664502649601-895.png||_mstalt="296985"]]
519 +[[image:1664502649601-895.png]]
521 521  
522 522  
523 -
524 524  Add the decoder from this link: 
525 525  
526 526  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -527,9 +527,10 @@
527 527  
528 528  Save the change the uplink message will be parsed. As below:
529 529  
530 -[[image:1664502676891-606.png||_mstalt="296673"]]
528 +[[image:1664502676891-606.png]]
531 531  
532 532  
531 +
533 533  == 2.5 Integrate with Datacake ==
534 534  
535 535  
... ... @@ -538,9 +538,10 @@
538 538  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]]
539 539  
540 540  
541 -[[image:1664502695771-538.png||_mstalt="297349"]]
540 +[[image:1664502695771-538.png]]
542 542  
543 543  
543 +
544 544  == 2.6 Integrate with Tago ==
545 545  
546 546  
... ... @@ -549,24 +549,26 @@
549 549  Instruction is here: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget]]
550 550  
551 551  
552 -[[image:1664502715371-321.png||_mstalt="292162"]]
552 +[[image:1664502715371-321.png]]
553 553  
554 554  
555 +
555 555  == 2.7  Datalog Feature ==
556 556  
557 557  
558 558  total 273 entries,by default,
559 559  
560 -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.
561 561  
562 562  Example use case.
563 563  
564 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
565 +[[image:image-20221009234703-2.png||height="328" width="899"]]
565 565  
566 566  
567 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
568 +[[image:image-20221009234629-1.png||height="390" width="577"]]
568 568  
569 569  
571 +
570 570  == 2.8 Alarm Mode ==
571 571  
572 572  
... ... @@ -581,7 +581,7 @@
581 581  
582 582  
583 583  (((
584 -**Two ways to exit alarm mode:**
586 +Two ways to exit alarm mode:
585 585  )))
586 586  
587 587  * Server sends a downlink command to exit.
... ... @@ -592,17 +592,14 @@
592 592  )))
593 593  
594 594  
597 +
595 595  == 2.9 Transport Mode ==
596 596  
597 597  
598 598  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.
599 599  
600 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
601 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
602 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
603 603  
604 604  
605 -
606 606  == 2.10 LED Status ==
607 607  
608 608  
... ... @@ -620,14 +620,12 @@
620 620  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
621 621  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
622 622  
623 -
624 -
625 625  == 2.11 Button Function ==
626 626  
627 627  
628 628  (% style="color:blue" %)**RESET button:**
629 629  
630 -[[image:1664502835802-546.png||_mstalt="295061"]]
627 +[[image:1664502835802-546.png]]
631 631  
632 632  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
633 633  
... ... @@ -634,7 +634,7 @@
634 634  
635 635  (% style="color:red" %)**RED button:**
636 636  
637 -[[image:1664502854406-763.png||_mstalt="295568"]]
634 +[[image:1664502854406-763.png]]
638 638  
639 639  
640 640  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -643,8 +643,6 @@
643 643  |(% 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
644 644  |(% 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.
645 645  
646 -
647 -
648 648  == 2.12 USB Port Function ==
649 649  
650 650  
... ... @@ -655,8 +655,6 @@
655 655  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
656 656  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
657 657  
658 -
659 -
660 660  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
661 661  
662 662  
... ... @@ -665,6 +665,7 @@
665 665  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
666 666  
667 667  
661 +
668 668  == 3.1 Access AT Command ==
669 669  
670 670  
... ... @@ -671,23 +671,25 @@
671 671  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.
672 672  
673 673  
674 -[[image:1664502999401-486.png||_mstalt="296985"]]
668 +[[image:1664502999401-486.png]]
675 675  
676 676  
677 677  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:
678 678  
679 679  
680 -[[image:1664503022490-662.png||_mstalt="293332"]]
674 +[[image:1664503022490-662.png]]
681 681  
682 682  
683 -[[image:1664503035713-500.png||_mstalt="291096"]]
677 +[[image:1664503035713-500.png]]
684 684  
685 685  
686 -[[image:1664503047675-651.png||_mstalt="295386"]]
680 +[[image:1664503047675-651.png]]
687 687  
688 688  
683 +
689 689  == 3.2 Command Set ==
690 690  
686 +
691 691  === 3.2.1 Set Transmit Interval ===
692 692  
693 693  
... ... @@ -705,6 +705,7 @@
705 705  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
706 706  
707 707  
704 +
708 708  === 3.2.2 Set Alarm Packet transmission interval ===
709 709  
710 710  
... ... @@ -722,6 +722,7 @@
722 722  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
723 723  
724 724  
722 +
725 725  === 3.2.3 Set Transport Mode Packet transmission interval ===
726 726  
727 727  
... ... @@ -739,6 +739,7 @@
739 739  (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
740 740  
741 741  
740 +
742 742  === 3.2.4 Exit Alarm ===
743 743  
744 744  
... ... @@ -751,6 +751,7 @@
751 751  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
752 752  
753 753  
753 +
754 754  === 3.2.5 Disable/Enable LED flash ===
755 755  
756 756  
... ... @@ -768,6 +768,7 @@
768 768  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
769 769  
770 770  
771 +
771 771  === 3.2.6 Disable/Enable Transport Mode ===
772 772  
773 773  
... ... @@ -785,6 +785,7 @@
785 785  (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
786 786  
787 787  
789 +
788 788  === 3.2.7 Set Positioning Mode ===
789 789  
790 790  
... ... @@ -811,9 +811,9 @@
811 811  
812 812  (% style="color:#037691" %)**cc:   **
813 813  
814 -* (% _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  
815 815  
816 -* (% _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(%%))  
817 817  
818 818  (% style="color:blue" %)**Example:**
819 819  
... ... @@ -831,6 +831,7 @@
831 831  (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
832 832  
833 833  
836 +
834 834  === 3.2.8 Set MAX GPS position time ===
835 835  
836 836  
... ... @@ -837,7 +837,7 @@
837 837  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.
838 838  
839 839  
840 -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.
841 841  
842 842  
843 843  * (% style="color:blue" %)**AT Command:**
... ... @@ -852,6 +852,7 @@
852 852  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
853 853  
854 854  
858 +
855 855  === 3.2.9 Set PDOP value for GPS fix accuracy ===
856 856  
857 857  
... ... @@ -876,9 +876,8 @@
876 876  
877 877  
878 878  
879 -=== 3.2.10 Disable/Enable the confirmation mode ===
883 +Disable/Enable the confirmation mode
880 880  
881 -
882 882  * (% style="color:blue" %)**AT Command:**
883 883  
884 884  (% style="color:#037691" %)**AT+CFM=xx**
... ... @@ -896,9 +896,10 @@
896 896  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
897 897  
898 898  
899 -=== 3.2.11  Auto Send None-ACK messages ===
900 900  
903 +=== 3.2.10  Auto Send None-ACK messages ===
901 901  
905 +
902 902  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.
903 903  
904 904  
... ... @@ -914,12 +914,13 @@
914 914  
915 915  * (% style="color:blue" %)**Downlink Command: 0x34**
916 916  
917 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
921 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
918 918  
919 919  
920 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
921 921  
925 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
922 922  
927 +
923 923  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.
924 924  
925 925  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -926,18 +926,19 @@
926 926  
927 927  (% style="color:blue" %)**AT Command:**
928 928  
929 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
934 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
930 930  
931 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
936 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
932 932  
933 933  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)**
934 934  
935 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
940 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
936 936  
937 937  
938 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) ===
939 939  
944 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) ===
940 940  
946 +
941 941  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.
942 942  
943 943  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
... ... @@ -944,18 +944,19 @@
944 944  
945 945  (% style="color:blue" %)**AT Command:**
946 946  
947 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
953 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
948 948  
949 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
955 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
950 950  
951 951  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)**
952 952  
953 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
959 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
954 954  
955 955  
956 -=== 3.2.14  Disable/Enable Information printing(Since firmware 1.4.1) ===
957 957  
963 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) ===
958 958  
965 +
959 959  Users can use this feature to enable/disable Information printing.
960 960  
961 961  (% style="color:blue" %)**AT Command:**
... ... @@ -964,9 +964,10 @@
964 964  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
965 965  
966 966  
967 -=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) ===
968 968  
975 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) ===
969 969  
977 +
970 970  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
971 971  
972 972  (% style="color:blue" %)**AT Command:**
... ... @@ -979,26 +979,7 @@
979 979  Example: 0x24 01 ~/~/ Same as AT+CHE=1
980 980  
981 981  
982 -=== 3.2.16 Get or Set Threshold for motion detect(Since firmware 1.4.3) ===
983 983  
984 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
985 -
986 -(% style="color:blue" %)**AT Command:**
987 -
988 -(% style="color:#037691" %)**AT+PT=xx**
989 -
990 - Example:
991 -
992 - AT+PT=14    ~-~->    Set to detect car motion.
993 -
994 - AT+PT=41   ~-~->    set to detect walk motion.
995 -
996 -
997 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
998 -0xB4 14          ~/~/  Same as AT+PT=14
999 -
1000 -
1001 -
1002 1002  = 4. Setting for Different Scenarios =
1003 1003  
1004 1004  
... ... @@ -1005,6 +1005,7 @@
1005 1005  
1006 1006  = 5. Upload Firmware =
1007 1007  
997 +
1008 1008  == 5.1 Firmware Change Log ==
1009 1009  
1010 1010  
... ... @@ -1011,6 +1011,7 @@
1011 1011  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1012 1012  
1013 1013  
1004 +
1014 1014  == 5.2 How to upgrade firmware ==
1015 1015  
1016 1016  
... ... @@ -1031,10 +1031,10 @@
1031 1031  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1032 1032  
1033 1033  
1034 -[[image:1664503563660-578.png||_mstalt="296777"]]
1025 +[[image:1664503563660-578.png]]
1035 1035  
1036 1036  
1037 -[[image:1664503574618-659.png||_mstalt="297986"]]
1028 +[[image:1664503574618-659.png]]
1038 1038  
1039 1039  
1040 1040  
... ... @@ -1043,7 +1043,7 @@
1043 1043  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1044 1044  
1045 1045  
1046 -**Users need to use below files:**
1037 +Users need to use below files:
1047 1047  
1048 1048  boot_app0.bin @0e000
1049 1049  
... ... @@ -1050,20 +1050,22 @@
1050 1050  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1051 1051  
1052 1052  
1053 -[[image:image-20221118105220-2.png||_mstalt="426608"]]
1044 +[[image:image-20221118105220-2.png]]
1054 1054  
1055 1055  
1056 1056  
1057 1057  After upgrade finish, it will show finish as below:
1058 1058  
1059 -[[image:image-20221118105402-4.png||_mstalt="427986"]]
1050 +[[image:image-20221118105402-4.png]]
1060 1060  
1061 1061  
1062 1062  
1063 1063  = 6. Developer Guide =
1064 1064  
1056 +
1065 1065  == 6.1 Compile Source Code ==
1066 1066  
1059 +
1067 1067  === 6.1.1 Set up ARDUINO compile environment ===
1068 1068  
1069 1069  
... ... @@ -1072,23 +1072,23 @@
1072 1072  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]]
1073 1073  
1074 1074  
1075 -[[image:1664503635019-941.png||_mstalt="294658"]]
1068 +[[image:1664503635019-941.png]]
1076 1076  
1077 1077  
1078 1078  
1079 1079  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1080 1080  
1081 -[[image:1664503715811-892.png||_mstalt="295698"]]
1074 +[[image:1664503715811-892.png]]
1082 1082  
1083 1083  
1084 1084  (% 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.
1085 1085  
1086 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1079 +[[image:image-20221024105643-1.png]]
1087 1087  
1088 1088  **~ Figure1**
1089 1089  
1090 1090  
1091 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1084 +[[image:image-20221024105643-2.png]]
1092 1092  
1093 1093   **Figure2**
1094 1094  
... ... @@ -1098,31 +1098,34 @@
1098 1098  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1099 1099  
1100 1100  
1101 -[[image:1664503752288-974.png||_mstalt="298194"]]
1094 +[[image:1664503752288-974.png]]
1102 1102  
1103 1103  
1097 +
1104 1104  == 6.2 Source Code ==
1105 1105  
1106 1106  
1107 1107  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1108 1108  
1109 -[[image:1664503794261-827.png||_mstalt="296387"]]
1103 +[[image:1664503794261-827.png]]
1110 1110  
1111 1111  
1112 1112  
1113 1113  * (% style="color:blue" %)**Click to upload**
1114 1114  
1115 -[[image:1664503808294-336.png||_mstalt="295711"]]
1109 +[[image:1664503808294-336.png]]
1116 1116  
1117 1117  
1118 1118  
1119 1119  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1120 1120  
1121 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1115 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1122 1122  
1123 1123  
1118 +
1124 1124  = 7.  FAQ =
1125 1125  
1121 +
1126 1126  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1127 1127  
1128 1128  
... ... @@ -1129,10 +1129,11 @@
1129 1129  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1130 1130  
1131 1131  
1128 +
1132 1132  == 7.2 What is the pin mapping for the USB program cable? ==
1133 1133  
1134 1134  
1135 -[[image:1664499635206-262.png||_mstalt="295360"]]
1132 +[[image:1664499635206-262.png]]
1136 1136  
1137 1137  
1138 1138  
... ... @@ -1147,10 +1147,9 @@
1147 1147  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1148 1148  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1149 1149  
1150 -
1151 -
1152 1152  == 7.3 Notes on using different serial port tools for TrackerD ==
1153 1153  
1149 +
1154 1154  === 7.3.1  Serial port utility ===
1155 1155  
1156 1156  
... ... @@ -1158,16 +1158,18 @@
1158 1158  
1159 1159  Need to adjust the data stream to RTS/CTS on physical restart.
1160 1160  
1157 +
1161 1161  (% class="wikigeneratedid" %)
1162 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1159 +[[image:image-20221102140621-1.png]]
1163 1163  
1164 1164  
1165 -
1166 1166  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1167 1167  
1168 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1169 1169  
1165 +[[image:image-20221102140638-2.png]]
1170 1170  
1167 +
1168 +
1171 1171  === 7.3.2  SecureCRT ===
1172 1172  
1173 1173  
... ... @@ -1174,22 +1174,23 @@
1174 1174  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.
1175 1175  
1176 1176  
1177 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1175 +[[image:image-20221102140704-3.png]]
1178 1178  
1179 1179  
1180 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1178 +[[image:image-20221102140712-4.png]]
1181 1181  
1182 1182  
1181 +
1183 1183  === 7.3.3  PUTTY ===
1184 1184  
1185 1185  
1186 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1185 +[[image:image-20221102140748-5.png]]
1187 1187  
1188 1188  
1189 1189  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.
1190 1190  
1191 1191  
1192 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1191 +[[image:image-20221102140801-6.png]]
1193 1193  
1194 1194  
1195 1195  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1201,46 +1201,38 @@
1201 1201  See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1202 1202  )))
1203 1203  
1204 -**~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.
1205 1205  
1205 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1206 1206  
1207 -[[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).
1208 1208  
1209 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1209 1209  
1211 +3.Compile the AS923_JP band, please refer to the intention shown
1210 1210  
1211 -**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"]]
1212 1212  
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.
1213 1213  
1214 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1217 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1215 1215  
1219 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1216 1216  
1217 1217  
1218 -**3. Compile the AS923_JP band, please refer to the intention shown**
1219 1219  
1220 -
1221 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1222 -
1223 -
1224 -
1225 -**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.**
1226 -
1227 -
1228 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1229 -
1230 -
1231 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1232 -
1233 -
1234 1234  = 8  Trouble Shooting =
1235 1235  
1225 +
1236 1236  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1237 1237  
1238 1238  
1239 1239  (((
1240 -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
1241 1241  )))
1242 1242  
1243 1243  
1234 +
1244 1244  == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1245 1245  
1246 1246  
... ... @@ -1249,106 +1249,86 @@
1249 1249  )))
1250 1250  
1251 1251  
1243 +
1252 1252  == 8.3  Problem after Upgrading Firmware ==
1253 1253  
1254 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1246 +=== 8.3.1 Continue Restart after upgrading ===
1255 1255  
1256 1256  
1257 -**Error Output**
1258 -
1259 -
1260 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1261 -
1262 -
1263 1263  (((
1264 -Some partition is missed during upgrade, please upgrade below four files as example:
1265 -
1266 -[[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
1267 1267  )))
1268 1268  
1269 1269  
1270 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1254 +[[image:image-20221118105249-3.png]]
1271 1271  
1272 1272  
1257 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1258 +
1273 1273  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
1274 1274  
1275 1275  
1276 -=== 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 ====
1277 1277  
1264 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1278 1278  
1279 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1266 + Figure 1
1280 1280  
1268 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1281 1281  
1282 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1270 + Figure 2
1283 1283  
1272 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1284 1284  
1285 -User need to upgrade again with below four files to solve this issue.
1274 +[[image:image-20221122100004-3.png]]
1286 1286  
1287 - [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1276 +Please at+FDR, and then enter the following instructions by the information on the label
1288 1288  
1289 - **Figure 2**
1278 +AT+DEUI=70B3D57ED0053981
1290 1290  
1291 -
1292 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1293 -
1294 -
1295 -User might erase the entire flash include keys and default settings which cause this issue.
1296 -
1297 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1298 -
1299 -
1300 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1301 -
1302 -
1303 -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.
1304 -
1305 -After AT+FDR. please set
1306 -
1307 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1308 -
1309 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1310 -
1311 -**Example:**
1312 -
1313 -AT+PDOP=7.00
1314 -
1315 -AT+FTIME=180
1316 -
1317 -AT+DEUI=70B3D57ED0053981  
1318 -
1319 1319  AT+APPEUI=D23345667BCBCCAF
1320 1320  
1321 1321  AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1322 1322  
1323 -AT+DADDR=260b4dce    ( no need for OTAA)
1284 +AT+DADDR=260b4dce
1324 1324  
1325 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1286 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1326 1326  
1327 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1288 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1328 1328  
1329 1329  
1330 -== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1331 1331  
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 ====
1332 1332  
1333 -Please download version 1.4.2 again
1294 +[[image:image-20221122100004-4.png]]
1334 1334  
1296 +(% class="wikigeneratedid" %)
1297 +== ==
1335 1335  
1336 -== 8. How to deal with unsuccessful GPS positioning? ==
1299 +== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==
1337 1337  
1301 +Please download version 1.4.2 again
1338 1338  
1339 -1) Make Sure the device is in Open Area where can see the sky.
1340 1340  
1304 +(((
1305 +== 8.5 How to deal with unsuccessful GPS positioning? ==
1306 +
1307 +1) Make Sure the device is in Open Area where can see the sky. 
1341 1341  2)  Set PDOP to a higher value.
1342 1342  
1343 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.)
1310 + AT+PDOP=2(can be positioned precisely.)
1344 1344  
1345 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces)
1312 + AT+PDOP=7(Quickly locate in open spaces)
1346 1346  
1347 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments)
1314 + AT+PDOP=14.7(Positioning can be acquired in complex environments)
1348 1348  
1349 1349  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
1317 +)))
1350 1350  
1351 1351  
1320 +== ==
1321 +
1322 +
1352 1352  = 9.  Order Info =
1353 1353  
1354 1354  
... ... @@ -1357,21 +1357,13 @@
1357 1357  (% style="color:blue" %)**XXX**(%%): The default frequency band
1358 1358  
1359 1359  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1360 -
1361 1361  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1362 -
1363 1363  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1364 -
1365 1365  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1366 -
1367 1367  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1368 -
1369 1369  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1370 -
1371 1371  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1372 1372  
1373 -
1374 -
1375 1375  = 10.  Packing Info =
1376 1376  
1377 1377  
... ... @@ -1378,32 +1378,22 @@
1378 1378  (% style="color:#037691" %)**Package Includes**:
1379 1379  
1380 1380  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1381 -
1382 1382  * USB recharge & program cable x 1
1383 1383  
1384 1384  (% style="color:#037691" %)**Dimensions and Weight**:
1385 1385  
1386 1386  * Device Size: 85 x 48 x 15 mm
1387 -
1388 1388  * Weight: 50g
1389 1389  
1390 -
1391 -
1392 1392  = 11. Support =
1393 1393  
1394 1394  
1395 1395  * 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.
1396 -
1397 1397  * 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]].
1398 1398  
1399 -
1400 -
1401 1401  = 12.  Reference =
1402 1402  
1403 1403  
1404 1404  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1405 -
1406 1406  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1407 -
1408 1408  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1409 -)))