Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 104.1
edited by Bei Jinggeng
on 2022/11/04 10:19
Change comment: There is no comment for this version
To version 149.1
edited by Edwin Chen
on 2022/11/24 09:07
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  
... ... @@ -121,9 +121,8 @@
121 121  * Logistics and Supply Chain Management
122 122  * Human tracking
123 123  
124 -= 2.1 Use TrackerD =
122 += 2.  Use TrackerD =
125 125  
126 -
127 127  == 2.1 How it works? ==
128 128  
129 129  
... ... @@ -130,7 +130,6 @@
130 130  TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.
131 131  
132 132  
133 -
134 134  == 2.2 Quick guide to connect to LoRaWAN server ==
135 135  
136 136  
... ... @@ -137,7 +137,7 @@
137 137  Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example. 
138 138  
139 139  
140 -[[image:1664501652064-326.png]]
136 +[[image:1664501652064-326.png||_mstalt="293306"]]
141 141  
142 142  
143 143  
... ... @@ -149,7 +149,7 @@
149 149  Each TrackerD is shipped with a sticker with the default device EUI as below:
150 150  
151 151  
152 -[[image:1664501677253-891.png]]
148 +[[image:1664501677253-891.png||_mstalt="296569"]]
153 153  
154 154  
155 155  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -158,14 +158,14 @@
158 158  **__Add APP EUI in the application:__**
159 159  
160 160  
161 -[[image:1664501711466-918.png]]
157 +[[image:1664501711466-918.png||_mstalt="295828"]]
162 162  
163 163  
164 164  
165 -[[image:1664501721248-725.png]]
161 +[[image:1664501721248-725.png||_mstalt="294450"]]
166 166  
167 167  
168 -[[image:1664501734705-405.png]]
164 +[[image:1664501734705-405.png||_mstalt="293306"]]
169 169  
170 170  
171 171  
... ... @@ -172,18 +172,20 @@
172 172  **__Add APP KEY and DEV EUI:__**
173 173  
174 174  
175 -[[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"]]
176 176  
177 177  
178 178  
175 +(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
179 179  
180 -(% 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"]]
181 181  
179 +[[image:1664502835802-546.png||_mstalt="295061"]]
182 182  
181 +
183 183  (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
184 184  
185 185  
186 -
187 187  == 2.3  Positioning Mode(SMOD) ==
188 188  
189 189  
... ... @@ -196,10 +196,8 @@
196 196  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
197 197  
198 198  
199 -
200 200  == 2.4  Uplink Payload ==
201 201  
202 -
203 203  === 2.4.1 Uplink FPORT~=5, Device Status ===
204 204  
205 205  
... ... @@ -212,7 +212,7 @@
212 212  |=(% 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
213 213  |=(% 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
214 214  
215 -[[image:1665301570342-765.png]]
211 +[[image:1665301570342-765.png||_mstalt="294580"]]
216 216  
217 217  
218 218  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -279,7 +279,7 @@
279 279  
280 280  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
281 281  
282 -(% 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)(%%)  
283 283  
284 284  
285 285  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -306,7 +306,7 @@
306 306  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
307 307  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
308 308  
309 -[[image:1665301636888-168.png]]
305 +[[image:1665301636888-168.png||_mstalt="298012"]]
310 310  
311 311  
312 312  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -336,12 +336,12 @@
336 336  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:
337 337  
338 338  
339 -[[image:1664502116362-706.png]]
335 +[[image:1664502116362-706.png||_mstalt="293306"]]
340 340  
341 341  
342 342  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
343 343  
344 -[[image:1664502166010-515.png]]
340 +[[image:1664502166010-515.png||_mstalt="291395"]]
345 345  
346 346  
347 347  
... ... @@ -404,7 +404,6 @@
404 404  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
405 405  
406 406  
407 -
408 408  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
409 409  
410 410  
... ... @@ -420,10 +420,9 @@
420 420  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
421 421  
422 422  (% class="wikigeneratedid" %)
423 -[[image:1665301687277-443.png]]
418 +[[image:1665301687277-443.png||_mstalt="296140"]]
424 424  
425 425  
426 -
427 427  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
428 428  
429 429  
... ... @@ -444,10 +444,9 @@
444 444  )))|4|4|2|1|1|1|1|1
445 445  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
446 446  
447 -[[image:image-20221009160309-2.png]]
441 +[[image:image-20221009160309-2.png||_mstalt="429312"]]
448 448  
449 449  
450 -
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]]
468 +[[image:1664502425687-834.png||_mstalt="296738"]]
476 476  
477 477  
478 478  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -479,14 +479,14 @@
479 479  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
480 480  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
481 481  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
482 -* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
475 +* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
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 -=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID ===
479 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
487 487  
488 488  
489 -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.
490 490  
491 491  
492 492  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
... ... @@ -498,7 +498,7 @@
498 498  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
499 499  
500 500  (% class="wikigeneratedid" %)
501 -[[image:1667288597595-714.png||height="212" width="1151"]]
494 +[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
502 502  
503 503  
504 504  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -513,9 +513,10 @@
513 513  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
514 514  
515 515  
516 -[[image:1664502649601-895.png]]
509 +[[image:1664502649601-895.png||_mstalt="296985"]]
517 517  
518 518  
512 +
519 519  Add the decoder from this link: 
520 520  
521 521  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -522,10 +522,9 @@
522 522  
523 523  Save the change the uplink message will be parsed. As below:
524 524  
525 -[[image:1664502676891-606.png]]
519 +[[image:1664502676891-606.png||_mstalt="296673"]]
526 526  
527 527  
528 -
529 529  == 2.5 Integrate with Datacake ==
530 530  
531 531  
... ... @@ -533,8 +533,8 @@
533 533  
534 534  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]]
535 535  
536 -[[image:1664502695771-538.png]]
537 537  
530 +[[image:1664502695771-538.png||_mstalt="297349"]]
538 538  
539 539  
540 540  == 2.6 Integrate with Tago ==
... ... @@ -545,11 +545,9 @@
545 545  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]]
546 546  
547 547  
541 +[[image:1664502715371-321.png||_mstalt="292162"]]
548 548  
549 -[[image:1664502715371-321.png]]
550 550  
551 -
552 -
553 553  == 2.7  Datalog Feature ==
554 554  
555 555  
... ... @@ -559,13 +559,12 @@
559 559  
560 560  Example use case.
561 561  
562 -[[image:image-20221009234703-2.png||height="328" width="899"]]
553 +[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
563 563  
564 564  
565 -[[image:image-20221009234629-1.png||height="390" width="577"]]
556 +[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
566 566  
567 567  
568 -
569 569  == 2.8 Alarm Mode ==
570 570  
571 571  
... ... @@ -580,7 +580,7 @@
580 580  
581 581  
582 582  (((
583 -Two ways to exit alarm mode:
573 +**Two ways to exit alarm mode:**
584 584  )))
585 585  
586 586  * Server sends a downlink command to exit.
... ... @@ -591,24 +591,28 @@
591 591  )))
592 592  
593 593  
594 -
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  
589 +~[~[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]] defines the Uplink Interval during transportation.
600 600  
591 +~[~[TDC>>||anchor="H3.2.1SetTransmitInterval"]] defines the uplink interval when TrackerD is stactic.
601 601  
593 +~[~[PT>>||anchor="H3.2.1SetTransmitInterval"]] defines the threldhold to detect a motion.
594 +
595 +
602 602  == 2.10 LED Status ==
603 603  
604 604  
605 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
599 +(% border="1.5" style="background-color:#ffffcc; width:500px" %)
606 606  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
607 607  |(% 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
608 608  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
609 609  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
610 610  |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
611 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
605 +|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
612 612  |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
613 613  |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
614 614  |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
... ... @@ -621,7 +621,7 @@
621 621  
622 622  (% style="color:blue" %)**RESET button:**
623 623  
624 -[[image:1664502835802-546.png]]
618 +[[image:1664502835802-546.png||_mstalt="295061"]]
625 625  
626 626  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
627 627  
... ... @@ -628,12 +628,12 @@
628 628  
629 629  (% style="color:red" %)**RED button:**
630 630  
631 -[[image:1664502854406-763.png]]
625 +[[image:1664502854406-763.png||_mstalt="295568"]]
632 632  
633 633  
634 -(% border="1" style="background-color:#ffffcc; color:green; width:510px" %)
628 +(% border="1" style="background-color:#ffffcc; width:510px" %)
635 635  |=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
636 -|(% 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"]]
630 +|(% 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"]]
637 637  |(% 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
638 638  |(% 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.
639 639  
... ... @@ -655,7 +655,6 @@
655 655  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
656 656  
657 657  
658 -
659 659  == 3.1 Access AT Command ==
660 660  
661 661  
... ... @@ -662,25 +662,24 @@
662 662  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.
663 663  
664 664  
665 -[[image:1664502999401-486.png]]
658 +[[image:1664502999401-486.png||_mstalt="296985"]]
666 666  
667 667  
668 668  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:
669 669  
670 670  
671 -[[image:1664503022490-662.png]]
664 +[[image:1664503022490-662.png||_mstalt="293332"]]
672 672  
673 673  
674 -[[image:1664503035713-500.png]]
667 +[[image:1664503035713-500.png||_mstalt="291096"]]
675 675  
676 676  
677 -[[image:1664503047675-651.png]]
670 +[[image:1664503047675-651.png||_mstalt="295386"]]
678 678  
679 679  
680 680  
681 681  == 3.2 Command Set ==
682 682  
683 -
684 684  === 3.2.1 Set Transmit Interval ===
685 685  
686 686  
... ... @@ -698,7 +698,6 @@
698 698  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
699 699  
700 700  
701 -
702 702  === 3.2.2 Set Alarm Packet transmission interval ===
703 703  
704 704  
... ... @@ -716,7 +716,6 @@
716 716  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
717 717  
718 718  
719 -
720 720  === 3.2.3 Set Transport Mode Packet transmission interval ===
721 721  
722 722  
... ... @@ -731,10 +731,9 @@
731 731  
732 732  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
733 733  
734 -(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
724 +(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
735 735  
736 736  
737 -
738 738  === 3.2.4 Exit Alarm ===
739 739  
740 740  
... ... @@ -747,7 +747,6 @@
747 747  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
748 748  
749 749  
750 -
751 751  === 3.2.5 Disable/Enable LED flash ===
752 752  
753 753  
... ... @@ -765,7 +765,6 @@
765 765  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
766 766  
767 767  
768 -
769 769  === 3.2.6 Disable/Enable Transport Mode ===
770 770  
771 771  
... ... @@ -775,15 +775,14 @@
775 775  
776 776  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
777 777  
778 -Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
765 +Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
779 779  
780 780  
781 781  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
782 782  
783 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
770 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
784 784  
785 785  
786 -
787 787  === 3.2.7 Set Positioning Mode ===
788 788  
789 789  
... ... @@ -797,33 +797,39 @@
797 797  (% style="color:#037691" %)** aa:**
798 798  
799 799  * (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
786 +
800 800  * (% 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.
801 -* (% 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.
802 802  
789 +* (% 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.
790 +
803 803  (% style="color:#037691" %)**bb:**
804 804  
805 805  * (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
794 +
806 806  * (% style="color:red" %)**1 :**(%%)  GPS +BAT State
807 807  
808 808  (% style="color:#037691" %)**cc:   **
809 809  
810 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
811 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
799 +* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
800 +
801 +* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
812 812  
813 813  (% style="color:blue" %)**Example:**
814 814  
815 - AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
816 - AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
817 - AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
818 - AT+ SMOD =2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
805 + AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
819 819  
807 + AT+SMOD=1,1,0 ~-~->  GPS +BAT State
820 820  
821 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
809 + AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
822 822  
823 -(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
811 + AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
824 824  
825 825  
814 +* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
826 826  
816 +(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
817 +
818 +
827 827  === 3.2.8 Set MAX GPS position time ===
828 828  
829 829  
... ... @@ -830,7 +830,7 @@
830 830  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.
831 831  
832 832  
833 -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.
825 +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.
834 834  
835 835  
836 836  * (% style="color:blue" %)**AT Command:**
... ... @@ -845,7 +845,6 @@
845 845  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
846 846  
847 847  
848 -
849 849  === 3.2.9 Set PDOP value for GPS fix accuracy ===
850 850  
851 851  
... ... @@ -870,7 +870,7 @@
870 870  
871 871  
872 872  
873 -Disable/Enable the confirmation mode
864 +=== 3.2.10 Disable/Enable the confirmation mode ===
874 874  
875 875  * (% style="color:blue" %)**AT Command:**
876 876  
... ... @@ -879,20 +879,19 @@
879 879  
880 880  **~ Example:**
881 881  
882 - AT+ CFM=0    **~-~->   ** Disable confirmation
873 + AT+CFM=0    **~-~->   ** Disable confirmation
883 883  
884 - AT+ CFM=1    **~-~->  ** Enable confirmation
875 + AT+CFM=1    **~-~->  ** Enable confirmation
885 885  
886 886  
887 887  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
888 888  
889 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ CFM =1
880 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
890 890  
891 891  
883 +=== 3.2.11  Auto Send None-ACK messages ===
892 892  
893 -=== 3.2.10  Auto Send None-ACK messages ===
894 894  
895 -
896 896  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.
897 897  
898 898  
... ... @@ -908,13 +908,12 @@
908 908  
909 909  * (% style="color:blue" %)**Downlink Command: 0x34**
910 910  
911 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
901 +Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
912 912  
913 913  
904 +=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
914 914  
915 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
916 916  
917 -
918 918  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.
919 919  
920 920  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -921,56 +921,59 @@
921 921  
922 922  (% style="color:blue" %)**AT Command:**
923 923  
924 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
913 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
925 925  
926 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
915 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
927 927  
928 928  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
929 929  
930 -Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
919 +Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
931 931  
932 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID ===
933 933  
922 +=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
934 934  
935 -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.
936 936  
925 +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.
926 +
937 937  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
938 938  
939 939  (% style="color:blue" %)**AT Command:**
940 940  
941 - (% style="color:#037691" %)**AT+ WiFiMASK =123456**    (%%) ~/~/ Set WiFiMASK = 123456
931 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
942 942  
943 - (% style="color:#037691" %)**AT+ WiFiMASK =0**       (%%) ~/~/ disable WiFiMASK
933 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
944 944  
945 945  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
946 946  
947 -Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
937 +Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
948 948  
949 -=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
950 950  
940 +=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
951 951  
942 +
952 952  Users can use this feature to enable/disable Information printing.
953 953  
954 954  (% style="color:blue" %)**AT Command:**
955 955  
947 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
948 +\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
956 956  
957 -(% style="color:#037691" %)**AT+ SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
958 -
959 -Example: AT+ SHOWID =1 ~-~-> Enable Information printing.
960 960  
951 +=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
961 961  
962 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
963 963  
964 964  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
965 965  
966 966  (% style="color:blue" %)**AT Command:**
967 967  
968 -(% style="color:#037691" %)**AT+ CHE=1**(%%) ~/~/ set one channels mode,
958 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
969 969  
970 -(% style="color:blue" %)**Downlink Payload:0X24**(%%)
971 -Example: 0x24 01 ~/~/ Same as AT+ CHE= = 1
972 972  
961 +(% style="color:blue" %)**Downlink Payload:0X24**
973 973  
963 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
964 +
965 +
974 974  = 4. Setting for Different Scenarios =
975 975  
976 976  
... ... @@ -977,7 +977,6 @@
977 977  
978 978  = 5. Upload Firmware =
979 979  
980 -
981 981  == 5.1 Firmware Change Log ==
982 982  
983 983  
... ... @@ -984,7 +984,6 @@
984 984  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
985 985  
986 986  
987 -
988 988  == 5.2 How to upgrade firmware ==
989 989  
990 990  
... ... @@ -1005,10 +1005,10 @@
1005 1005  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1006 1006  
1007 1007  
1008 -[[image:1664503563660-578.png]]
998 +[[image:1664503563660-578.png||_mstalt="296777"]]
1009 1009  
1010 1010  
1011 -[[image:1664503574618-659.png]]
1001 +[[image:1664503574618-659.png||_mstalt="297986"]]
1012 1012  
1013 1013  
1014 1014  
... ... @@ -1017,29 +1017,27 @@
1017 1017  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1018 1018  
1019 1019  
1020 -Users need to use below files:
1010 +**Users need to use below files:**
1021 1021  
1022 1022  boot_app0.bin @0e000
1023 1023  
1024 -ESP_LORA-eeprom-class.bin @ 0x10000
1014 +US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1025 1025  
1026 1026  
1027 -[[image:1664503593459-435.png]]
1017 +[[image:image-20221118105220-2.png||_mstalt="426608"]]
1028 1028  
1029 1029  
1030 1030  
1031 1031  After upgrade finish, it will show finish as below:
1032 1032  
1033 -[[image:1664503611848-385.png]]
1023 +[[image:image-20221118105402-4.png||_mstalt="427986"]]
1034 1034  
1035 1035  
1036 1036  
1037 1037  = 6. Developer Guide =
1038 1038  
1039 -
1040 1040  == 6.1 Compile Source Code ==
1041 1041  
1042 -
1043 1043  === 6.1.1 Set up ARDUINO compile environment ===
1044 1044  
1045 1045  
... ... @@ -1048,23 +1048,23 @@
1048 1048  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]]
1049 1049  
1050 1050  
1051 -[[image:1664503635019-941.png]]
1039 +[[image:1664503635019-941.png||_mstalt="294658"]]
1052 1052  
1053 1053  
1054 1054  
1055 1055  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1056 1056  
1057 -[[image:1664503715811-892.png]]
1045 +[[image:1664503715811-892.png||_mstalt="295698"]]
1058 1058  
1059 1059  
1060 1060  (% 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.
1061 1061  
1062 -[[image:image-20221024105643-1.png]]
1050 +[[image:image-20221024105643-1.png||_mstalt="428129"]]
1063 1063  
1064 1064  **~ Figure1**
1065 1065  
1066 1066  
1067 -[[image:image-20221024105643-2.png]]
1055 +[[image:image-20221024105643-2.png||_mstalt="428493"]]
1068 1068  
1069 1069   **Figure2**
1070 1070  
... ... @@ -1074,34 +1074,31 @@
1074 1074  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1075 1075  
1076 1076  
1077 -[[image:1664503752288-974.png]]
1065 +[[image:1664503752288-974.png||_mstalt="298194"]]
1078 1078  
1079 1079  
1080 -
1081 1081  == 6.2 Source Code ==
1082 1082  
1083 1083  
1084 1084  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1085 1085  
1086 -[[image:1664503794261-827.png]]
1073 +[[image:1664503794261-827.png||_mstalt="296387"]]
1087 1087  
1088 1088  
1089 1089  
1090 1090  * (% style="color:blue" %)**Click to upload**
1091 1091  
1092 -[[image:1664503808294-336.png]]
1079 +[[image:1664503808294-336.png||_mstalt="295711"]]
1093 1093  
1094 1094  
1095 1095  
1096 1096  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1097 1097  
1098 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1085 +[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1099 1099  
1100 1100  
1101 -
1102 1102  = 7.  FAQ =
1103 1103  
1104 -
1105 1105  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1106 1106  
1107 1107  
... ... @@ -1108,11 +1108,10 @@
1108 1108  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1109 1109  
1110 1110  
1111 -
1112 1112  == 7.2 What is the pin mapping for the USB program cable? ==
1113 1113  
1114 1114  
1115 -[[image:1664499635206-262.png]]
1099 +[[image:1664499635206-262.png||_mstalt="295360"]]
1116 1116  
1117 1117  
1118 1118  
... ... @@ -1129,89 +1129,248 @@
1129 1129  
1130 1130  == 7.3 Notes on using different serial port tools for TrackerD ==
1131 1131  
1116 +=== 7.3.1  Serial port utility ===
1132 1132  
1133 -=== **Serial port utility** ===
1134 1134  
1135 -
1136 1136  Serial port utility requires you to automatically add data streams.
1137 1137  
1138 1138  Need to adjust the data stream to RTS/CTS on physical restart.
1139 1139  
1140 -
1141 1141  (% class="wikigeneratedid" %)
1142 -[[image:image-20221102140621-1.png]]
1124 +[[image:image-20221102140621-1.png||_mstalt="425672"]]
1143 1143  
1144 1144  
1127 +
1145 1145  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1146 1146  
1130 +[[image:image-20221102140638-2.png||_mstalt="428727"]]
1147 1147  
1148 -[[image:image-20221102140638-2.png]]
1149 1149  
1133 +=== 7.3.2  SecureCRT ===
1150 1150  
1151 1151  
1152 -=== **SecureCRT** ===
1136 +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.
1153 1153  
1154 1154  
1155 -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.
1139 +[[image:image-20221102140704-3.png||_mstalt="427076"]]
1156 1156  
1157 1157  
1158 -[[image:image-20221102140704-3.png]]
1142 +[[image:image-20221102140712-4.png||_mstalt="427089"]]
1159 1159  
1160 1160  
1161 -[[image:image-20221102140712-4.png]]
1145 +=== 7.3.3  PUTTY ===
1162 1162  
1163 1163  
1148 +[[image:image-20221102140748-5.png||_mstalt="430456"]]
1164 1164  
1165 -=== **PUTTY** ===
1166 1166  
1151 +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.
1167 1167  
1168 -[[image:image-20221102140748-5.png]]
1169 1169  
1154 +[[image:image-20221102140801-6.png||_mstalt="427466"]]
1170 1170  
1171 -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.
1172 1172  
1157 +== 7.4 How to modify source code to compile different frequency band bin file? ==
1173 1173  
1174 -[[image:image-20221102140801-6.png]]
1175 1175  
1160 +(% class="box infomessage" %)
1161 +(((
1162 +(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1163 +See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1164 +)))
1176 1176  
1166 +**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1177 1177  
1178 -= 8.  Order Info =
1179 1179  
1169 +[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1180 1180  
1171 +
1172 +
1173 +**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1174 +
1175 +
1176 +[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1177 +
1178 +
1179 +
1180 +**3. Compile the AS923_JP band, please refer to the intention shown**
1181 +
1182 +
1183 +[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1184 +
1185 +
1186 +
1187 +**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.**
1188 +
1189 +
1190 +[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1191 +
1192 +
1193 +[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1194 +
1195 +
1196 += 8  Trouble Shooting =
1197 +
1198 +== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1199 +
1200 +
1201 +(((
1202 +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
1203 +)))
1204 +
1205 +
1206 +== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1207 +
1208 +
1209 +(((
1210 +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.
1211 +)))
1212 +
1213 +
1214 +== 8.3  Problem after Upgrading Firmware ==
1215 +
1216 +=== 8.3.1 Continue Restart after upgrading ===
1217 +
1218 +
1219 +(((
1220 +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
1221 +)))
1222 +
1223 +
1224 +[[image:image-20221118105249-3.png||_mstalt="430664"]]
1225 +
1226 +
1227 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1228 +
1229 +
1230 +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
1231 +
1232 +
1233 +=== 8.3.3 "flash read err" after upgrade firmware ===
1234 +
1235 +Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1236 +
1237 +[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1238 +
1239 +
1240 +User need to upgrade again with below four files to solve this issue.
1241 +
1242 + [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1243 +
1244 + **Figure 2**
1245 +
1246 +
1247 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1248 +
1249 +User might erase the entire flash include keys and default settings which cause this issue.
1250 +
1251 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1252 +
1253 +[[image:image-20221122100004-3.png||_mstalt="424242"]]
1254 +
1255 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1256 +
1257 +After AT+FDR. please set
1258 +
1259 +* AT+PDOP=7
1260 +* AT+FTIME=180000
1261 +
1262 +Example:
1263 +
1264 +AT+PDOP=7.00
1265 +
1266 +AT+FTIME=180
1267 +
1268 +AT+DEUI=70B3D57ED0053981  
1269 +
1270 +AT+APPEUI=D23345667BCBCCAF
1271 +
1272 +AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1273 +
1274 +AT+DADDR=260b4dce    ( no need for OTAA)
1275 +
1276 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1277 +
1278 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1279 +
1280 +
1281 +
1282 +=== 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 ===
1283 +
1284 +
1285 +[[image:image-20221122100004-4.png||_mstalt="424606"]]
1286 +
1287 +
1288 +== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1289 +
1290 +
1291 +Please download version 1.4.2 again
1292 +
1293 +
1294 +== 8.5  How to deal with unsuccessful GPS positioning? ==
1295 +
1296 +
1297 +1） Make Sure the device is in Open Area where can see the sky.
1298 +
1299 +2)  Set PDOP to a higher value.
1300 +
1301 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1302 +
1303 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1304 +
1305 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1306 +
1307 +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
1308 +
1309 +
1310 += 9.  Order Info =
1311 +
1312 +
1181 1181  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1182 1182  
1183 1183  (% style="color:blue" %)**XXX**(%%): The default frequency band
1184 1184  
1185 1185  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1318 +
1186 1186  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1320 +
1187 1187  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1322 +
1188 1188  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1324 +
1189 1189  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1326 +
1190 1190  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1328 +
1191 1191  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1192 1192  
1193 -= 9.  Packing Info =
1331 += 10.  Packing Info =
1194 1194  
1195 1195  
1196 1196  (% style="color:#037691" %)**Package Includes**:
1197 1197  
1198 1198  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1337 +
1199 1199  * USB recharge & program cable x 1
1200 1200  
1201 1201  (% style="color:#037691" %)**Dimensions and Weight**:
1202 1202  
1203 1203  * Device Size: 85 x 48 x 15 mm
1343 +
1204 1204  * Weight: 50g
1205 1205  
1206 -= 10. Support =
1346 += 11. Support =
1207 1207  
1208 1208  
1209 1209  * 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.
1350 +
1210 1210  * 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]].
1211 1211  
1212 -= 11.  Reference =
1353 += 12.  Reference =
1213 1213  
1214 1214  
1215 1215  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1357 +
1216 1216  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1359 +
1217 1217  * [[**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