Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 89.1
edited by Kilight Cao
on 2022/11/01 16:00
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.Kilight
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(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  
... ... @@ -433,7 +433,7 @@
433 433  (% style="color:red" %)**Note for this mode:**
434 434  
435 435  * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
436 -* b) TrackerD will send data in (% style="color:blue" %)**CONFIRMED Mode**(%%) when PNACKMD=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
430 +* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
437 437  * c) the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes of payload. In this case (DR0 of US915/AU915), the payload on server will show NULL
438 438  
439 439  The payload is 15 bytes, as below.
... ... @@ -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,17 +479,16 @@
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  
479 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
486 486  
487 -=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID ===
488 488  
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.
489 489  
490 -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.
491 491  
492 -
493 493  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
494 494  |=(% scope="row" style="width: 60px;" %)(((
495 495  **Size(bytes)**
... ... @@ -499,7 +499,7 @@
499 499  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
500 500  
501 501  (% class="wikigeneratedid" %)
502 -[[image:1667288597595-714.png||height="212" width="1151"]]
494 +[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
503 503  
504 504  
505 505  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -506,7 +506,6 @@
506 506  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
507 507  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
508 508  
509 -
510 510  === 2.4.7  Add Payload format in TTN V3 ===
511 511  
512 512  
... ... @@ -515,9 +515,10 @@
515 515  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
516 516  
517 517  
518 -[[image:1664502649601-895.png]]
509 +[[image:1664502649601-895.png||_mstalt="296985"]]
519 519  
520 520  
512 +
521 521  Add the decoder from this link: 
522 522  
523 523  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -524,10 +524,9 @@
524 524  
525 525  Save the change the uplink message will be parsed. As below:
526 526  
527 -[[image:1664502676891-606.png]]
519 +[[image:1664502676891-606.png||_mstalt="296673"]]
528 528  
529 529  
530 -
531 531  == 2.5 Integrate with Datacake ==
532 532  
533 533  
... ... @@ -535,8 +535,8 @@
535 535  
536 536  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]]
537 537  
538 -[[image:1664502695771-538.png]]
539 539  
530 +[[image:1664502695771-538.png||_mstalt="297349"]]
540 540  
541 541  
542 542  == 2.6 Integrate with Tago ==
... ... @@ -547,11 +547,9 @@
547 547  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]]
548 548  
549 549  
541 +[[image:1664502715371-321.png||_mstalt="292162"]]
550 550  
551 -[[image:1664502715371-321.png]]
552 552  
553 -
554 -
555 555  == 2.7  Datalog Feature ==
556 556  
557 557  
... ... @@ -561,13 +561,12 @@
561 561  
562 562  Example use case.
563 563  
564 -[[image:image-20221009234703-2.png||height="328" width="899"]]
553 +[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
565 565  
566 566  
567 -[[image:image-20221009234629-1.png||height="390" width="577"]]
556 +[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
568 568  
569 569  
570 -
571 571  == 2.8 Alarm Mode ==
572 572  
573 573  
... ... @@ -582,7 +582,7 @@
582 582  
583 583  
584 584  (((
585 -Two ways to exit alarm mode:
573 +**Two ways to exit alarm mode:**
586 586  )))
587 587  
588 588  * Server sends a downlink command to exit.
... ... @@ -593,24 +593,26 @@
593 593  )))
594 594  
595 595  
596 -
597 597  == 2.9 Transport Mode ==
598 598  
599 599  
600 600  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.
601 601  
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.
602 602  
603 603  
604 604  == 2.10 LED Status ==
605 605  
606 606  
607 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
597 +(% border="1.5" style="background-color:#ffffcc; width:500px" %)
608 608  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
609 609  |(% 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
610 610  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
611 611  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
612 612  |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
613 -|(% 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
614 614  |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
615 615  |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
616 616  |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
... ... @@ -623,7 +623,7 @@
623 623  
624 624  (% style="color:blue" %)**RESET button:**
625 625  
626 -[[image:1664502835802-546.png]]
616 +[[image:1664502835802-546.png||_mstalt="295061"]]
627 627  
628 628  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
629 629  
... ... @@ -630,12 +630,12 @@
630 630  
631 631  (% style="color:red" %)**RED button:**
632 632  
633 -[[image:1664502854406-763.png]]
623 +[[image:1664502854406-763.png||_mstalt="295568"]]
634 634  
635 635  
636 -(% border="1" style="background-color:#ffffcc; color:green; width:510px" %)
626 +(% border="1" style="background-color:#ffffcc; width:510px" %)
637 637  |=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
638 -|(% 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"]]
639 639  |(% 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
640 640  |(% 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.
641 641  
... ... @@ -657,7 +657,6 @@
657 657  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
658 658  
659 659  
660 -
661 661  == 3.1 Access AT Command ==
662 662  
663 663  
... ... @@ -664,25 +664,24 @@
664 664  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.
665 665  
666 666  
667 -[[image:1664502999401-486.png]]
656 +[[image:1664502999401-486.png||_mstalt="296985"]]
668 668  
669 669  
670 670  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:
671 671  
672 672  
673 -[[image:1664503022490-662.png]]
662 +[[image:1664503022490-662.png||_mstalt="293332"]]
674 674  
675 675  
676 -[[image:1664503035713-500.png]]
665 +[[image:1664503035713-500.png||_mstalt="291096"]]
677 677  
678 678  
679 -[[image:1664503047675-651.png]]
668 +[[image:1664503047675-651.png||_mstalt="295386"]]
680 680  
681 681  
682 682  
683 683  == 3.2 Command Set ==
684 684  
685 -
686 686  === 3.2.1 Set Transmit Interval ===
687 687  
688 688  
... ... @@ -700,7 +700,6 @@
700 700  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
701 701  
702 702  
703 -
704 704  === 3.2.2 Set Alarm Packet transmission interval ===
705 705  
706 706  
... ... @@ -718,7 +718,6 @@
718 718  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
719 719  
720 720  
721 -
722 722  === 3.2.3 Set Transport Mode Packet transmission interval ===
723 723  
724 724  
... ... @@ -733,10 +733,9 @@
733 733  
734 734  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
735 735  
736 -(% 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
737 737  
738 738  
739 -
740 740  === 3.2.4 Exit Alarm ===
741 741  
742 742  
... ... @@ -749,7 +749,6 @@
749 749  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
750 750  
751 751  
752 -
753 753  === 3.2.5 Disable/Enable LED flash ===
754 754  
755 755  
... ... @@ -767,7 +767,6 @@
767 767  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
768 768  
769 769  
770 -
771 771  === 3.2.6 Disable/Enable Transport Mode ===
772 772  
773 773  
... ... @@ -777,15 +777,14 @@
777 777  
778 778  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
779 779  
780 -Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
763 +Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
781 781  
782 782  
783 783  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
784 784  
785 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
768 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
786 786  
787 787  
788 -
789 789  === 3.2.7 Set Positioning Mode ===
790 790  
791 791  
... ... @@ -799,33 +799,39 @@
799 799  (% style="color:#037691" %)** aa:**
800 800  
801 801  * (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
784 +
802 802  * (% 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.
803 -* (% 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.
804 804  
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 +
805 805  (% style="color:#037691" %)**bb:**
806 806  
807 807  * (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
792 +
808 808  * (% style="color:red" %)**1 :**(%%)  GPS +BAT State
809 809  
810 810  (% style="color:#037691" %)**cc:   **
811 811  
812 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
813 -* (% 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(%%))  
814 814  
815 815  (% style="color:blue" %)**Example:**
816 816  
817 - AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
818 - AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
819 - AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
820 - AT+ SMOD =2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
803 + AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
821 821  
805 + AT+SMOD=1,1,0 ~-~->  GPS +BAT State
822 822  
823 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
807 + AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
824 824  
825 -(% 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
826 826  
827 827  
812 +* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
828 828  
814 +(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
815 +
816 +
829 829  === 3.2.8 Set MAX GPS position time ===
830 830  
831 831  
... ... @@ -832,7 +832,7 @@
832 832  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.
833 833  
834 834  
835 -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.
836 836  
837 837  
838 838  * (% style="color:blue" %)**AT Command:**
... ... @@ -847,7 +847,6 @@
847 847  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
848 848  
849 849  
850 -
851 851  === 3.2.9 Set PDOP value for GPS fix accuracy ===
852 852  
853 853  
... ... @@ -872,7 +872,7 @@
872 872  
873 873  
874 874  
875 -Disable/Enable the confirmation mode
862 +=== 3.2.10 Disable/Enable the confirmation mode ===
876 876  
877 877  * (% style="color:blue" %)**AT Command:**
878 878  
... ... @@ -881,20 +881,19 @@
881 881  
882 882  **~ Example:**
883 883  
884 - AT+ CFM=0    **~-~->   ** Disable confirmation
871 + AT+CFM=0    **~-~->   ** Disable confirmation
885 885  
886 - AT+ CFM=1    **~-~->  ** Enable confirmation
873 + AT+CFM=1    **~-~->  ** Enable confirmation
887 887  
888 888  
889 889  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
890 890  
891 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
878 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
892 892  
893 893  
881 +=== 3.2.11  Auto Send None-ACK messages ===
894 894  
895 -=== 3.2.10  Auto Send None-ACK messages ===
896 896  
897 -
898 898  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.
899 899  
900 900  
... ... @@ -910,13 +910,12 @@
910 910  
911 911  * (% style="color:blue" %)**Downlink Command: 0x34**
912 912  
913 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
899 +Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
914 914  
915 915  
902 +=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
916 916  
917 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
918 918  
919 -
920 920  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.
921 921  
922 922  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -923,35 +923,79 @@
923 923  
924 924  (% style="color:blue" %)**AT Command:**
925 925  
926 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
911 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
927 927  
928 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
913 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
929 929  
915 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
930 930  
931 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**
917 +Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
932 932  
933 -Example: 0xA5010203040506    ~/~/ Set BLEMASK to 123456
934 934  
920 +=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
935 935  
936 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID ===
937 937  
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.
938 938  
939 -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.
940 -
941 941  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
942 942  
943 943  (% style="color:blue" %)**AT Command:**
944 944  
945 - (% style="color:#037691" %)**AT+ WiFiMASK =123456**    (%%) ~/~/ Set WiFiMASK = 123456
929 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
946 946  
947 - (% style="color:#037691" %)**AT+ WiFiMASK =0**       (%%) ~/~/ disable WiFiMASK
931 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
948 948  
933 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
949 949  
950 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**
935 +Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
951 951  
952 -Example: 0xA5010203040506    ~/~/ Set WiFiMASK to 123456
953 953  
938 +=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
954 954  
940 +
941 +Users can use this feature to enable/disable Information printing.
942 +
943 +(% style="color:blue" %)**AT Command:**
944 +
945 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
946 +\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
947 +
948 +
949 +=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
950 +
951 +
952 +The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
953 +
954 +(% style="color:blue" %)**AT Command:**
955 +
956 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
957 +
958 +
959 +(% style="color:blue" %)**Downlink Payload:0X24**
960 +
961 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
962 +
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 +
955 955  = 4. Setting for Different Scenarios =
956 956  
957 957  
... ... @@ -958,7 +958,6 @@
958 958  
959 959  = 5. Upload Firmware =
960 960  
961 -
962 962  == 5.1 Firmware Change Log ==
963 963  
964 964  
... ... @@ -965,7 +965,6 @@
965 965  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
966 966  
967 967  
968 -
969 969  == 5.2 How to upgrade firmware ==
970 970  
971 971  
... ... @@ -986,10 +986,10 @@
986 986  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
987 987  
988 988  
989 -[[image:1664503563660-578.png]]
1016 +[[image:1664503563660-578.png||_mstalt="296777"]]
990 990  
991 991  
992 -[[image:1664503574618-659.png]]
1019 +[[image:1664503574618-659.png||_mstalt="297986"]]
993 993  
994 994  
995 995  
... ... @@ -998,29 +998,27 @@
998 998  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
999 999  
1000 1000  
1001 -Users need to use below files:
1028 +**Users need to use below files:**
1002 1002  
1003 1003  boot_app0.bin @0e000
1004 1004  
1005 -ESP_LORA-eeprom-class.bin @ 0x10000
1032 +US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1006 1006  
1007 1007  
1008 -[[image:1664503593459-435.png]]
1035 +[[image:image-20221118105220-2.png||_mstalt="426608"]]
1009 1009  
1010 1010  
1011 1011  
1012 1012  After upgrade finish, it will show finish as below:
1013 1013  
1014 -[[image:1664503611848-385.png]]
1041 +[[image:image-20221118105402-4.png||_mstalt="427986"]]
1015 1015  
1016 1016  
1017 1017  
1018 1018  = 6. Developer Guide =
1019 1019  
1020 -
1021 1021  == 6.1 Compile Source Code ==
1022 1022  
1023 -
1024 1024  === 6.1.1 Set up ARDUINO compile environment ===
1025 1025  
1026 1026  
... ... @@ -1029,23 +1029,23 @@
1029 1029  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]]
1030 1030  
1031 1031  
1032 -[[image:1664503635019-941.png]]
1057 +[[image:1664503635019-941.png||_mstalt="294658"]]
1033 1033  
1034 1034  
1035 1035  
1036 1036  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1037 1037  
1038 -[[image:1664503715811-892.png]]
1063 +[[image:1664503715811-892.png||_mstalt="295698"]]
1039 1039  
1040 1040  
1041 1041  (% 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.
1042 1042  
1043 -[[image:image-20221024105643-1.png]]
1068 +[[image:image-20221024105643-1.png||_mstalt="428129"]]
1044 1044  
1045 1045  **~ Figure1**
1046 1046  
1047 1047  
1048 -[[image:image-20221024105643-2.png]]
1073 +[[image:image-20221024105643-2.png||_mstalt="428493"]]
1049 1049  
1050 1050   **Figure2**
1051 1051  
... ... @@ -1055,34 +1055,31 @@
1055 1055  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1056 1056  
1057 1057  
1058 -[[image:1664503752288-974.png]]
1083 +[[image:1664503752288-974.png||_mstalt="298194"]]
1059 1059  
1060 1060  
1061 -
1062 1062  == 6.2 Source Code ==
1063 1063  
1064 1064  
1065 1065  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1066 1066  
1067 -[[image:1664503794261-827.png]]
1091 +[[image:1664503794261-827.png||_mstalt="296387"]]
1068 1068  
1069 1069  
1070 1070  
1071 1071  * (% style="color:blue" %)**Click to upload**
1072 1072  
1073 -[[image:1664503808294-336.png]]
1097 +[[image:1664503808294-336.png||_mstalt="295711"]]
1074 1074  
1075 1075  
1076 1076  
1077 1077  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1078 1078  
1079 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1103 +[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1080 1080  
1081 1081  
1082 -
1083 1083  = 7.  FAQ =
1084 1084  
1085 -
1086 1086  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1087 1087  
1088 1088  
... ... @@ -1089,11 +1089,10 @@
1089 1089  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1090 1090  
1091 1091  
1092 -
1093 1093  == 7.2 What is the pin mapping for the USB program cable? ==
1094 1094  
1095 1095  
1096 -[[image:1664499635206-262.png]]
1117 +[[image:1664499635206-262.png||_mstalt="295360"]]
1097 1097  
1098 1098  
1099 1099  
... ... @@ -1108,43 +1108,250 @@
1108 1108  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1109 1109  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1110 1110  
1111 -= 8.  Order Info =
1132 +== 7.3 Notes on using different serial port tools for TrackerD ==
1112 1112  
1134 +=== 7.3.1  Serial port utility ===
1113 1113  
1136 +
1137 +Serial port utility requires you to automatically add data streams.
1138 +
1139 +Need to adjust the data stream to RTS/CTS on physical restart.
1140 +
1141 +(% class="wikigeneratedid" %)
1142 +[[image:image-20221102140621-1.png||_mstalt="425672"]]
1143 +
1144 +
1145 +
1146 +When using AT commands, the data flow needs to be adjusted to XON/XOFF
1147 +
1148 +[[image:image-20221102140638-2.png||_mstalt="428727"]]
1149 +
1150 +
1151 +=== 7.3.2  SecureCRT ===
1152 +
1153 +
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.
1155 +
1156 +
1157 +[[image:image-20221102140704-3.png||_mstalt="427076"]]
1158 +
1159 +
1160 +[[image:image-20221102140712-4.png||_mstalt="427089"]]
1161 +
1162 +
1163 +=== 7.3.3  PUTTY ===
1164 +
1165 +
1166 +[[image:image-20221102140748-5.png||_mstalt="430456"]]
1167 +
1168 +
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.
1170 +
1171 +
1172 +[[image:image-20221102140801-6.png||_mstalt="427466"]]
1173 +
1174 +
1175 +== 7.4 How to modify source code to compile different frequency band bin file? ==
1176 +
1177 +
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 +)))
1183 +
1184 +**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1185 +
1186 +
1187 +[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1188 +
1189 +
1190 +
1191 +**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1192 +
1193 +
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 +
1114 1114  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1115 1115  
1116 1116  (% style="color:blue" %)**XXX**(%%): The default frequency band
1117 1117  
1118 1118  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1336 +
1119 1119  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1338 +
1120 1120  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1340 +
1121 1121  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1342 +
1122 1122  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1344 +
1123 1123  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1346 +
1124 1124  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1125 1125  
1126 -= 9.  Packing Info =
1349 += 10.  Packing Info =
1127 1127  
1128 1128  
1129 1129  (% style="color:#037691" %)**Package Includes**:
1130 1130  
1131 1131  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1355 +
1132 1132  * USB recharge & program cable x 1
1133 1133  
1134 1134  (% style="color:#037691" %)**Dimensions and Weight**:
1135 1135  
1136 -* Device Size: 85 x 48 x 15 cm
1360 +* Device Size: 85 x 48 x 15 mm
1361 +
1137 1137  * Weight: 50g
1138 1138  
1139 -= 10. Support =
1364 += 11. Support =
1140 1140  
1141 1141  
1142 1142  * 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 +
1143 1143  * 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]].
1144 1144  
1145 -= 11.  Reference =
1371 += 12.  Reference =
1146 1146  
1147 1147  
1148 1148  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1375 +
1149 1149  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1377 +
1150 1150  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
image-20221102140621-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +46.1 KB
Content
image-20221102140638-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +40.8 KB
Content
image-20221102140704-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +15.5 KB
Content
image-20221102140712-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +73.2 KB
Content
image-20221102140748-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +56.0 KB
Content
image-20221102140801-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +21.0 KB
Content
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