Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 106.1
edited by Bei Jinggeng
on 2022/11/07 09:15
Change comment: There is no comment for this version
To version 153.1
edited by Edwin Chen
on 2022/11/24 09:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Edwin
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:1664505654417-133.png]]
2 +[[image:1664505654417-133.png||_mstalt="293696"]]
3 3  
4 4  
5 5  
... ... @@ -14,7 +14,6 @@
14 14  
15 15  = 1.  Introduction =
16 16  
17 -
18 18  == 1.1  What is TrackerD ==
19 19  
20 20  
... ... @@ -40,13 +40,12 @@
40 40  
41 41  )))
42 42  
43 -[[image:1664499921684-770.png]]
42 +[[image:1664499921684-770.png||_mstalt="298194"]]
44 44  
45 45  
46 46  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
47 47  
48 48  
49 -
50 50  == 1.2 Specifications ==
51 51  
52 52  
... ... @@ -97,7 +97,6 @@
97 97  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
98 98  * Tracking: max: 38mA
99 99  
100 -
101 101  == 1.3  Features ==
102 102  
103 103  
... ... @@ -116,7 +116,6 @@
116 116  * Tri-color LED, Alarm button
117 117  * Datalog
118 118  
119 -
120 120  == 1.4  Applications ==
121 121  
122 122  
... ... @@ -123,10 +123,8 @@
123 123  * Logistics and Supply Chain Management
124 124  * Human tracking
125 125  
126 -
127 127  = 2.  Use TrackerD =
128 128  
129 -
130 130  == 2.1 How it works? ==
131 131  
132 132  
... ... @@ -133,7 +133,6 @@
133 133  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.
134 134  
135 135  
136 -
137 137  == 2.2 Quick guide to connect to LoRaWAN server ==
138 138  
139 139  
... ... @@ -140,7 +140,7 @@
140 140  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. 
141 141  
142 142  
143 -[[image:1664501652064-326.png]]
136 +[[image:1664501652064-326.png||_mstalt="293306"]]
144 144  
145 145  
146 146  
... ... @@ -152,7 +152,7 @@
152 152  Each TrackerD is shipped with a sticker with the default device EUI as below:
153 153  
154 154  
155 -[[image:1664501677253-891.png]]
148 +[[image:1664501677253-891.png||_mstalt="296569"]]
156 156  
157 157  
158 158  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -161,14 +161,14 @@
161 161  **__Add APP EUI in the application:__**
162 162  
163 163  
164 -[[image:1664501711466-918.png]]
157 +[[image:1664501711466-918.png||_mstalt="295828"]]
165 165  
166 166  
167 167  
168 -[[image:1664501721248-725.png]]
161 +[[image:1664501721248-725.png||_mstalt="294450"]]
169 169  
170 170  
171 -[[image:1664501734705-405.png]]
164 +[[image:1664501734705-405.png||_mstalt="293306"]]
172 172  
173 173  
174 174  
... ... @@ -175,18 +175,20 @@
175 175  **__Add APP KEY and DEV EUI:__**
176 176  
177 177  
178 -[[image:1664501784668-703.png]]
171 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]]
179 179  
180 180  
181 181  
175 +(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
182 182  
183 -(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
177 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
184 184  
179 +[[image:1664502835802-546.png||_mstalt="295061"]]
185 185  
181 +
186 186  (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
187 187  
188 188  
189 -
190 190  == 2.3  Positioning Mode(SMOD) ==
191 191  
192 192  
... ... @@ -199,10 +199,8 @@
199 199  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
200 200  
201 201  
202 -
203 203  == 2.4  Uplink Payload ==
204 204  
205 -
206 206  === 2.4.1 Uplink FPORT~=5, Device Status ===
207 207  
208 208  
... ... @@ -215,7 +215,7 @@
215 215  |=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1
216 216  |=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
217 217  
218 -[[image:1665301570342-765.png]]
211 +[[image:1665301570342-765.png||_mstalt="294580"]]
219 219  
220 220  
221 221  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -282,7 +282,7 @@
282 282  
283 283  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
284 284  
285 -(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
278 +(% _mstmutation="1" style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
286 286  
287 287  
288 288  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -291,7 +291,6 @@
291 291  |=(% 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
292 292  |=(% 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"]]
293 293  
294 -
295 295  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
296 296  
297 297  
... ... @@ -310,7 +310,7 @@
310 310  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
311 311  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
312 312  
313 -[[image:1665301636888-168.png]]
305 +[[image:1665301636888-168.png||_mstalt="298012"]]
314 314  
315 315  
316 316  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -340,12 +340,12 @@
340 340  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:
341 341  
342 342  
343 -[[image:1664502116362-706.png]]
335 +[[image:1664502116362-706.png||_mstalt="293306"]]
344 344  
345 345  
346 346  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
347 347  
348 -[[image:1664502166010-515.png]]
340 +[[image:1664502166010-515.png||_mstalt="291395"]]
349 349  
350 350  
351 351  
... ... @@ -368,7 +368,6 @@
368 368  * 3.40v ~~ 3.69v:  20% ~~ 40%
369 369  * < 3.39v:  0~~20%
370 370  
371 -
372 372  ==== (% style="color:blue" %)**MOD:**(%%) ====
373 373  
374 374  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -409,7 +409,6 @@
409 409  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
410 410  
411 411  
412 -
413 413  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
414 414  
415 415  
... ... @@ -425,10 +425,9 @@
425 425  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
426 426  
427 427  (% class="wikigeneratedid" %)
428 -[[image:1665301687277-443.png]]
418 +[[image:1665301687277-443.png||_mstalt="296140"]]
429 429  
430 430  
431 -
432 432  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
433 433  
434 434  
... ... @@ -449,10 +449,9 @@
449 449  )))|4|4|2|1|1|1|1|1
450 450  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
451 451  
452 -[[image:image-20221009160309-2.png]]
441 +[[image:image-20221009160309-2.png||_mstalt="429312"]]
453 453  
454 454  
455 -
456 456  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
457 457  
458 458  
... ... @@ -477,7 +477,7 @@
477 477  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
478 478  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
479 479  
480 -[[image:1664502425687-834.png]]
468 +[[image:1664502425687-834.png||_mstalt="296738"]]
481 481  
482 482  
483 483  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -484,15 +484,14 @@
484 484  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
485 485  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
486 486  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
487 -* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
475 +* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
488 488  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
489 489  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
490 490  
491 -
492 492  === 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
493 493  
494 494  
495 -TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
482 +TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **WiFi** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
496 496  
497 497  
498 498  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
... ... @@ -504,7 +504,7 @@
504 504  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
505 505  
506 506  (% class="wikigeneratedid" %)
507 -[[image:1667288597595-714.png||height="212" width="1151"]]
494 +[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
508 508  
509 509  
510 510  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -511,7 +511,6 @@
511 511  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
512 512  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
513 513  
514 -
515 515  === 2.4.7  Add Payload format in TTN V3 ===
516 516  
517 517  
... ... @@ -520,9 +520,10 @@
520 520  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
521 521  
522 522  
523 -[[image:1664502649601-895.png]]
509 +[[image:1664502649601-895.png||_mstalt="296985"]]
524 524  
525 525  
512 +
526 526  Add the decoder from this link: 
527 527  
528 528  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -529,10 +529,9 @@
529 529  
530 530  Save the change the uplink message will be parsed. As below:
531 531  
532 -[[image:1664502676891-606.png]]
519 +[[image:1664502676891-606.png||_mstalt="296673"]]
533 533  
534 534  
535 -
536 536  == 2.5 Integrate with Datacake ==
537 537  
538 538  
... ... @@ -540,8 +540,8 @@
540 540  
541 541  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]]
542 542  
543 -[[image:1664502695771-538.png]]
544 544  
530 +[[image:1664502695771-538.png||_mstalt="297349"]]
545 545  
546 546  
547 547  == 2.6 Integrate with Tago ==
... ... @@ -552,11 +552,9 @@
552 552  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]]
553 553  
554 554  
541 +[[image:1664502715371-321.png||_mstalt="292162"]]
555 555  
556 -[[image:1664502715371-321.png]]
557 557  
558 -
559 -
560 560  == 2.7  Datalog Feature ==
561 561  
562 562  
... ... @@ -566,13 +566,12 @@
566 566  
567 567  Example use case.
568 568  
569 -[[image:image-20221009234703-2.png||height="328" width="899"]]
553 +[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
570 570  
571 571  
572 -[[image:image-20221009234629-1.png||height="390" width="577"]]
556 +[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
573 573  
574 574  
575 -
576 576  == 2.8 Alarm Mode ==
577 577  
578 578  
... ... @@ -587,7 +587,7 @@
587 587  
588 588  
589 589  (((
590 -Two ways to exit alarm mode:
573 +**Two ways to exit alarm mode:**
591 591  )))
592 592  
593 593  * Server sends a downlink command to exit.
... ... @@ -598,24 +598,26 @@
598 598  )))
599 599  
600 600  
601 -
602 602  == 2.9 Transport Mode ==
603 603  
604 604  
605 605  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.
606 606  
589 +* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
590 +* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
591 +* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
607 607  
608 608  
609 609  == 2.10 LED Status ==
610 610  
611 611  
612 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
597 +(% border="1.5" style="background-color:#ffffcc; width:500px" %)
613 613  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
614 614  |(% style="width:157px" %)**Power On**|(% style="width:271px" %)(% style="color:blue" %)**BLUE, **(% style="color:red" %)**RED , **(% style="color:green" %)**Green** flash once|(% style="width:202px" %)N/A
615 615  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
616 616  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
617 617  |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
618 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
603 +|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
619 619  |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
620 620  |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
621 621  |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
... ... @@ -623,13 +623,12 @@
623 623  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
624 624  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
625 625  
626 -
627 627  == 2.11 Button Function ==
628 628  
629 629  
630 630  (% style="color:blue" %)**RESET button:**
631 631  
632 -[[image:1664502835802-546.png]]
616 +[[image:1664502835802-546.png||_mstalt="295061"]]
633 633  
634 634  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
635 635  
... ... @@ -636,16 +636,15 @@
636 636  
637 637  (% style="color:red" %)**RED button:**
638 638  
639 -[[image:1664502854406-763.png]]
623 +[[image:1664502854406-763.png||_mstalt="295568"]]
640 640  
641 641  
642 -(% border="1" style="background-color:#ffffcc; color:green; width:510px" %)
626 +(% border="1" style="background-color:#ffffcc; width:510px" %)
643 643  |=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
644 -|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode.  See [[Alarm Mode>>||anchor="H2.6AlarmMode"]]
628 +|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode.  See [[Alarm Mode>>||anchor="H2.8AlarmMode"]]
645 645  |(% 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
646 646  |(% 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.
647 647  
648 -
649 649  == 2.12 USB Port Function ==
650 650  
651 651  
... ... @@ -656,7 +656,6 @@
656 656  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
657 657  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
658 658  
659 -
660 660  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
661 661  
662 662  
... ... @@ -665,7 +665,6 @@
665 665  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
666 666  
667 667  
668 -
669 669  == 3.1 Access AT Command ==
670 670  
671 671  
... ... @@ -672,25 +672,24 @@
672 672  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.
673 673  
674 674  
675 -[[image:1664502999401-486.png]]
656 +[[image:1664502999401-486.png||_mstalt="296985"]]
676 676  
677 677  
678 678  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:
679 679  
680 680  
681 -[[image:1664503022490-662.png]]
662 +[[image:1664503022490-662.png||_mstalt="293332"]]
682 682  
683 683  
684 -[[image:1664503035713-500.png]]
665 +[[image:1664503035713-500.png||_mstalt="291096"]]
685 685  
686 686  
687 -[[image:1664503047675-651.png]]
668 +[[image:1664503047675-651.png||_mstalt="295386"]]
688 688  
689 689  
690 690  
691 691  == 3.2 Command Set ==
692 692  
693 -
694 694  === 3.2.1 Set Transmit Interval ===
695 695  
696 696  
... ... @@ -708,7 +708,6 @@
708 708  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
709 709  
710 710  
711 -
712 712  === 3.2.2 Set Alarm Packet transmission interval ===
713 713  
714 714  
... ... @@ -726,7 +726,6 @@
726 726  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
727 727  
728 728  
729 -
730 730  === 3.2.3 Set Transport Mode Packet transmission interval ===
731 731  
732 732  
... ... @@ -741,10 +741,9 @@
741 741  
742 742  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
743 743  
744 -(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
722 +(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
745 745  
746 746  
747 -
748 748  === 3.2.4 Exit Alarm ===
749 749  
750 750  
... ... @@ -757,7 +757,6 @@
757 757  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
758 758  
759 759  
760 -
761 761  === 3.2.5 Disable/Enable LED flash ===
762 762  
763 763  
... ... @@ -775,7 +775,6 @@
775 775  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
776 776  
777 777  
778 -
779 779  === 3.2.6 Disable/Enable Transport Mode ===
780 780  
781 781  
... ... @@ -785,15 +785,14 @@
785 785  
786 786  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
787 787  
788 -Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
763 +Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
789 789  
790 790  
791 791  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
792 792  
793 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
768 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
794 794  
795 795  
796 -
797 797  === 3.2.7 Set Positioning Mode ===
798 798  
799 799  
... ... @@ -807,33 +807,39 @@
807 807  (% style="color:#037691" %)** aa:**
808 808  
809 809  * (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
784 +
810 810  * (% style="color:red" %)**2: BLE or WiFi ONLY:                     **(%%)Only obtain iBeacon info via BLE and uplink  or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking.
811 -* (% style="color:red" %)**3: GPS/BLE Hybrid:                        **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
812 812  
787 +* (% style="color:red" %)**3: GPS/BLE Hybrid:                       **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
788 +
813 813  (% style="color:#037691" %)**bb:**
814 814  
815 815  * (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
792 +
816 816  * (% style="color:red" %)**1 :**(%%)  GPS +BAT State
817 817  
818 818  (% style="color:#037691" %)**cc:   **
819 819  
820 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
821 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
797 +* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
798 +
799 +* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
822 822  
823 823  (% style="color:blue" %)**Example:**
824 824  
825 - AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
826 - AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
827 - AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
828 - AT+ SMOD =2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
803 + AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
829 829  
805 + AT+SMOD=1,1,0 ~-~->  GPS +BAT State
830 830  
831 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
807 + AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
832 832  
833 -(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
809 + AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
834 834  
835 835  
812 +* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
836 836  
814 +(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
815 +
816 +
837 837  === 3.2.8 Set MAX GPS position time ===
838 838  
839 839  
... ... @@ -840,7 +840,7 @@
840 840  Set max positioning time, default is 150 seconds. TrackerD will try to get location info within this period. If fail to get position data within this time, TrackerD will use 000000 for latitude and longitude.
841 841  
842 842  
843 -If AT+FTIME=0. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.
823 +If **AT+FTIME=0**. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.
844 844  
845 845  
846 846  * (% style="color:blue" %)**AT Command:**
... ... @@ -855,7 +855,6 @@
855 855  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
856 856  
857 857  
858 -
859 859  === 3.2.9 Set PDOP value for GPS fix accuracy ===
860 860  
861 861  
... ... @@ -880,7 +880,7 @@
880 880  
881 881  
882 882  
883 -Disable/Enable the confirmation mode
862 +=== 3.2.10 Disable/Enable the confirmation mode ===
884 884  
885 885  * (% style="color:blue" %)**AT Command:**
886 886  
... ... @@ -889,20 +889,19 @@
889 889  
890 890  **~ Example:**
891 891  
892 - AT+ CFM=0    **~-~->   ** Disable confirmation
871 + AT+CFM=0    **~-~->   ** Disable confirmation
893 893  
894 - AT+ CFM=1    **~-~->  ** Enable confirmation
873 + AT+CFM=1    **~-~->  ** Enable confirmation
895 895  
896 896  
897 897  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
898 898  
899 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ CFM =1
878 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
900 900  
901 901  
881 +=== 3.2.11  Auto Send None-ACK messages ===
902 902  
903 -=== 3.2.10  Auto Send None-ACK messages ===
904 904  
905 -
906 906  TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
907 907  
908 908  
... ... @@ -918,13 +918,12 @@
918 918  
919 919  * (% style="color:blue" %)**Downlink Command: 0x34**
920 920  
921 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
899 +Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
922 922  
923 923  
902 +=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
924 924  
925 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
926 926  
927 -
928 928  BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
929 929  
930 930  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -931,61 +931,79 @@
931 931  
932 932  (% style="color:blue" %)**AT Command:**
933 933  
934 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
911 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
935 935  
936 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
913 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
937 937  
938 938  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
939 939  
940 -Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
917 +Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
941 941  
942 942  
920 +=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
943 943  
944 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
945 945  
923 +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.
946 946  
947 -WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
948 -
949 949  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
950 950  
951 951  (% style="color:blue" %)**AT Command:**
952 952  
953 - (% style="color:#037691" %)**AT+WiFiMASK =123456**    (%%) ~/~/ Set WiFiMASK = 123456
929 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
954 954  
955 - (% style="color:#037691" %)**AT+WiFiMASK =0**       (%%) ~/~/ disable WiFiMASK
931 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
956 956  
957 957  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
958 958  
959 -Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
935 +Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
960 960  
961 961  
938 +=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
962 962  
963 -=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
964 964  
965 -
966 966  Users can use this feature to enable/disable Information printing.
967 967  
968 968  (% style="color:blue" %)**AT Command:**
969 969  
970 970  (% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
971 -\\Example: AT+SHOWID =1 ~-~-> Enable Information printing.
946 +\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
972 972  
973 973  
949 +=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
974 974  
975 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
976 976  
977 -
978 978  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
979 979  
980 980  (% style="color:blue" %)**AT Command:**
981 981  
982 -(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode,
956 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
983 983  
984 -(% style="color:blue" %)**Downlink Payload:0X24**(%%)
985 -Example: 0x24 01 ~/~/ Same as AT+CHE= = 1
986 986  
959 +(% style="color:blue" %)**Downlink Payload:0X24**
987 987  
961 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
988 988  
963 +
964 +=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
965 +
966 +User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
967 +
968 +(% style="color:blue" %)**AT Command:**
969 +
970 +(% style="color:#037691" %)**AT+PT=xx**
971 +
972 + Example:
973 +
974 + AT+PT=14    ~-~->    Set to detect car motion.
975 +
976 + AT+PT=41   ~-~->    set to detect walk motion.
977 +
978 +
979 +(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
980 +0xB4 14          ~/~/  Same as AT+PT=14
981 +
982 +
983 +
989 989  = 4. Setting for Different Scenarios =
990 990  
991 991  
... ... @@ -992,7 +992,6 @@
992 992  
993 993  = 5. Upload Firmware =
994 994  
995 -
996 996  == 5.1 Firmware Change Log ==
997 997  
998 998  
... ... @@ -999,7 +999,6 @@
999 999  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1000 1000  
1001 1001  
1002 -
1003 1003  == 5.2 How to upgrade firmware ==
1004 1004  
1005 1005  
... ... @@ -1020,10 +1020,10 @@
1020 1020  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1021 1021  
1022 1022  
1023 -[[image:1664503563660-578.png]]
1016 +[[image:1664503563660-578.png||_mstalt="296777"]]
1024 1024  
1025 1025  
1026 -[[image:1664503574618-659.png]]
1019 +[[image:1664503574618-659.png||_mstalt="297986"]]
1027 1027  
1028 1028  
1029 1029  
... ... @@ -1032,29 +1032,27 @@
1032 1032  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1033 1033  
1034 1034  
1035 -Users need to use below files:
1028 +**Users need to use below files:**
1036 1036  
1037 1037  boot_app0.bin @0e000
1038 1038  
1039 -ESP_LORA-eeprom-class.bin @ 0x10000
1032 +US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1040 1040  
1041 1041  
1042 -[[image:1664503593459-435.png]]
1035 +[[image:image-20221118105220-2.png||_mstalt="426608"]]
1043 1043  
1044 1044  
1045 1045  
1046 1046  After upgrade finish, it will show finish as below:
1047 1047  
1048 -[[image:1664503611848-385.png]]
1041 +[[image:image-20221118105402-4.png||_mstalt="427986"]]
1049 1049  
1050 1050  
1051 1051  
1052 1052  = 6. Developer Guide =
1053 1053  
1054 -
1055 1055  == 6.1 Compile Source Code ==
1056 1056  
1057 -
1058 1058  === 6.1.1 Set up ARDUINO compile environment ===
1059 1059  
1060 1060  
... ... @@ -1063,23 +1063,23 @@
1063 1063  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]]
1064 1064  
1065 1065  
1066 -[[image:1664503635019-941.png]]
1057 +[[image:1664503635019-941.png||_mstalt="294658"]]
1067 1067  
1068 1068  
1069 1069  
1070 1070  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1071 1071  
1072 -[[image:1664503715811-892.png]]
1063 +[[image:1664503715811-892.png||_mstalt="295698"]]
1073 1073  
1074 1074  
1075 1075  (% 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.
1076 1076  
1077 -[[image:image-20221024105643-1.png]]
1068 +[[image:image-20221024105643-1.png||_mstalt="428129"]]
1078 1078  
1079 1079  **~ Figure1**
1080 1080  
1081 1081  
1082 -[[image:image-20221024105643-2.png]]
1073 +[[image:image-20221024105643-2.png||_mstalt="428493"]]
1083 1083  
1084 1084   **Figure2**
1085 1085  
... ... @@ -1089,34 +1089,31 @@
1089 1089  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1090 1090  
1091 1091  
1092 -[[image:1664503752288-974.png]]
1083 +[[image:1664503752288-974.png||_mstalt="298194"]]
1093 1093  
1094 1094  
1095 -
1096 1096  == 6.2 Source Code ==
1097 1097  
1098 1098  
1099 1099  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1100 1100  
1101 -[[image:1664503794261-827.png]]
1091 +[[image:1664503794261-827.png||_mstalt="296387"]]
1102 1102  
1103 1103  
1104 1104  
1105 1105  * (% style="color:blue" %)**Click to upload**
1106 1106  
1107 -[[image:1664503808294-336.png]]
1097 +[[image:1664503808294-336.png||_mstalt="295711"]]
1108 1108  
1109 1109  
1110 1110  
1111 1111  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1112 1112  
1113 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1103 +[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1114 1114  
1115 1115  
1116 -
1117 1117  = 7.  FAQ =
1118 1118  
1119 -
1120 1120  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1121 1121  
1122 1122  
... ... @@ -1123,11 +1123,10 @@
1123 1123  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1124 1124  
1125 1125  
1126 -
1127 1127  == 7.2 What is the pin mapping for the USB program cable? ==
1128 1128  
1129 1129  
1130 -[[image:1664499635206-262.png]]
1117 +[[image:1664499635206-262.png||_mstalt="295360"]]
1131 1131  
1132 1132  
1133 1133  
... ... @@ -1142,104 +1142,250 @@
1142 1142  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1143 1143  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1144 1144  
1145 -
1146 1146  == 7.3 Notes on using different serial port tools for TrackerD ==
1147 1147  
1134 +=== 7.3.1  Serial port utility ===
1148 1148  
1149 -=== **Serial port utility** ===
1150 1150  
1151 -
1152 1152  Serial port utility requires you to automatically add data streams.
1153 1153  
1154 1154  Need to adjust the data stream to RTS/CTS on physical restart.
1155 1155  
1156 -
1157 1157  (% class="wikigeneratedid" %)
1158 -[[image:image-20221102140621-1.png]]
1142 +[[image:image-20221102140621-1.png||_mstalt="425672"]]
1159 1159  
1160 1160  
1145 +
1161 1161  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1162 1162  
1148 +[[image:image-20221102140638-2.png||_mstalt="428727"]]
1163 1163  
1164 -[[image:image-20221102140638-2.png]]
1165 1165  
1151 +=== 7.3.2  SecureCRT ===
1166 1166  
1167 1167  
1168 -=== **SecureCRT** ===
1154 +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.
1169 1169  
1170 1170  
1171 -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.
1157 +[[image:image-20221102140704-3.png||_mstalt="427076"]]
1172 1172  
1173 1173  
1174 -[[image:image-20221102140704-3.png]]
1160 +[[image:image-20221102140712-4.png||_mstalt="427089"]]
1175 1175  
1176 1176  
1177 -[[image:image-20221102140712-4.png]]
1163 +=== 7.3.3  PUTTY ===
1178 1178  
1179 1179  
1166 +[[image:image-20221102140748-5.png||_mstalt="430456"]]
1180 1180  
1181 -=== **PUTTY** ===
1182 1182  
1169 +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.
1183 1183  
1184 -[[image:image-20221102140748-5.png]]
1185 1185  
1172 +[[image:image-20221102140801-6.png||_mstalt="427466"]]
1186 1186  
1187 -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.
1188 1188  
1175 +== 7.4 How to modify source code to compile different frequency band bin file? ==
1189 1189  
1190 -[[image:image-20221102140801-6.png]]
1191 1191  
1178 +(% class="box infomessage" %)
1179 +(((
1180 +(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1181 +See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1182 +)))
1192 1192  
1193 -== 7.4 TrackerD trouble shooting ==
1184 +**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1194 1194  
1195 1195  
1196 -V1.4.0: When the motion mode is turned on, the TDC needs to be greater than MTDC, otherwise TDC time will be confused
1187 +[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1197 1197  
1198 1198  
1199 1199  
1200 -= 8.  Order Info =
1191 +**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1201 1201  
1202 1202  
1194 +[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1195 +
1196 +
1197 +
1198 +**3. Compile the AS923_JP band, please refer to the intention shown**
1199 +
1200 +
1201 +[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1202 +
1203 +
1204 +
1205 +**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.**
1206 +
1207 +
1208 +[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1209 +
1210 +
1211 +[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1212 +
1213 +
1214 += 8  Trouble Shooting =
1215 +
1216 +== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1217 +
1218 +
1219 +(((
1220 +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
1221 +)))
1222 +
1223 +
1224 +== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1225 +
1226 +
1227 +(((
1228 +ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode.
1229 +)))
1230 +
1231 +
1232 +== 8.3  Problem after Upgrading Firmware ==
1233 +
1234 +=== 8.3.1 Continue Restart after upgrading ===
1235 +
1236 +
1237 +(((
1238 +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
1239 +)))
1240 +
1241 +
1242 +[[image:image-20221118105249-3.png||_mstalt="430664"]]
1243 +
1244 +
1245 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1246 +
1247 +
1248 +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
1249 +
1250 +
1251 +=== 8.3.3 "flash read err" after upgrade firmware ===
1252 +
1253 +Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1254 +
1255 +[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1256 +
1257 +
1258 +User need to upgrade again with below four files to solve this issue.
1259 +
1260 + [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1261 +
1262 + **Figure 2**
1263 +
1264 +
1265 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1266 +
1267 +User might erase the entire flash include keys and default settings which cause this issue.
1268 +
1269 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1270 +
1271 +[[image:image-20221122100004-3.png||_mstalt="424242"]]
1272 +
1273 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1274 +
1275 +After AT+FDR. please set
1276 +
1277 +* AT+PDOP=7
1278 +* AT+FTIME=180000
1279 +
1280 +Example:
1281 +
1282 +AT+PDOP=7.00
1283 +
1284 +AT+FTIME=180
1285 +
1286 +AT+DEUI=70B3D57ED0053981  
1287 +
1288 +AT+APPEUI=D23345667BCBCCAF
1289 +
1290 +AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1291 +
1292 +AT+DADDR=260b4dce    ( no need for OTAA)
1293 +
1294 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1295 +
1296 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1297 +
1298 +
1299 +
1300 +=== 8.3.4  If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ===
1301 +
1302 +
1303 +[[image:image-20221122100004-4.png||_mstalt="424606"]]
1304 +
1305 +
1306 +== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1307 +
1308 +
1309 +Please download version 1.4.2 again
1310 +
1311 +
1312 +== 8.5  How to deal with unsuccessful GPS positioning? ==
1313 +
1314 +
1315 +1） Make Sure the device is in Open Area where can see the sky.
1316 +
1317 +2)  Set PDOP to a higher value.
1318 +
1319 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1320 +
1321 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1322 +
1323 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1324 +
1325 +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
1326 +
1327 +
1328 += 9.  Order Info =
1329 +
1330 +
1203 1203  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1204 1204  
1205 1205  (% style="color:blue" %)**XXX**(%%): The default frequency band
1206 1206  
1207 1207  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1336 +
1208 1208  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1338 +
1209 1209  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1340 +
1210 1210  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1342 +
1211 1211  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1344 +
1212 1212  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1346 +
1213 1213  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1214 1214  
1349 += 10.  Packing Info =
1215 1215  
1216 -= 9.  Packing Info =
1217 1217  
1218 -
1219 1219  (% style="color:#037691" %)**Package Includes**:
1220 1220  
1221 1221  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1355 +
1222 1222  * USB recharge & program cable x 1
1223 1223  
1224 1224  (% style="color:#037691" %)**Dimensions and Weight**:
1225 1225  
1226 1226  * Device Size: 85 x 48 x 15 mm
1361 +
1227 1227  * Weight: 50g
1228 1228  
1364 += 11. Support =
1229 1229  
1230 -= 10. Support =
1231 1231  
1232 -
1233 1233  * 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.
1368 +
1234 1234  * 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]].
1235 1235  
1371 += 12.  Reference =
1236 1236  
1237 -= 11.  Reference =
1238 1238  
1239 -
1240 1240  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1375 +
1241 1241  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1242 -* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1243 1243  
1244 -
1245 -
1378 +* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
image-20221107145243-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +107.3 KB
Content
image-20221116111844-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +15.8 KB
Content
image-20221116111844-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +32.6 KB
Content
image-20221116111844-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +37.0 KB
Content
image-20221116111844-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +96.8 KB
Content
image-20221116111844-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +78.0 KB
Content
image-20221118104359-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +38.0 KB
Content
image-20221118105220-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +40.2 KB
Content
image-20221118105249-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +40.2 KB
Content
image-20221118105402-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +43.7 KB
Content
image-20221122100004-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +18.0 KB
Content
image-20221122100004-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +127.2 KB
Content
image-20221122100004-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +12.5 KB
Content
image-20221122100004-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content