Skip to Content
Last modified by Xiaoling on 2025/04/27 16:48
From version 174.1
edited by Bei Jinggeng
on 2022/12/13 10:00
Change comment: Uploaded new attachment "image-20221213100007-1.png", version {1}
To version 143.1
edited by Bei Jinggeng
on 2022/11/22 10:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:1664505654417-133.png||_mstalt="293696"]]
2 +[[image:1664505654417-133.png]]
3 3  
4 4  
5 5  
... ... @@ -12,9 +12,9 @@
12 12  
13 13  
14 14  
15 -
16 16  = 1.  Introduction =
17 17  
17 +
18 18  == 1.1  What is TrackerD ==
19 19  
20 20  
... ... @@ -32,17 +32,21 @@
32 32  (((
33 33  The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
34 34  )))
35 +)))
35 35  
36 36  (((
37 37  TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.
39 +
40 +
38 38  )))
39 39  
40 -[[image:1664499921684-770.png||_mstalt="298194"]]
43 +[[image:1664499921684-770.png]]
41 41  
42 42  
43 43  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
44 44  
45 45  
49 +
46 46  == 1.2 Specifications ==
47 47  
48 48  
... ... @@ -93,8 +93,6 @@
93 93  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94 94  * Tracking: max: 38mA
95 95  
96 -
97 -
98 98  == 1.3  Features ==
99 99  
100 100  
... ... @@ -113,8 +113,6 @@
113 113  * Tri-color LED, Alarm button
114 114  * Datalog
115 115  
116 -
117 -
118 118  == 1.4  Applications ==
119 119  
120 120  
... ... @@ -121,10 +121,9 @@
121 121  * Logistics and Supply Chain Management
122 122  * Human tracking
123 123  
124 -
125 -
126 126  = 2.  Use TrackerD =
127 127  
126 +
128 128  == 2.1 How it works? ==
129 129  
130 130  
... ... @@ -131,6 +131,7 @@
131 131  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.
132 132  
133 133  
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||_mstalt="293306"]]
140 +[[image:1664501652064-326.png]]
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||_mstalt="296569"]]
152 +[[image:1664501677253-891.png]]
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||_mstalt="295828"]]
161 +[[image:1664501711466-918.png]]
162 162  
163 163  
164 164  
165 -[[image:1664501721248-725.png||_mstalt="294450"]]
165 +[[image:1664501721248-725.png]]
166 166  
167 167  
168 -[[image:1664501734705-405.png||_mstalt="293306"]]
168 +[[image:1664501734705-405.png]]
169 169  
170 170  
171 171  
... ... @@ -172,20 +172,21 @@
172 172  **__Add APP KEY and DEV EUI:__**
173 173  
174 174  
175 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]]
175 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]]
176 176  
177 177  
178 178  
179 179  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
180 180  
181 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
181 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
182 182  
183 -[[image:1664502835802-546.png||_mstalt="295061"]]
183 +[[image:1664502835802-546.png]]
184 184  
185 185  
186 186  (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
187 187  
188 188  
189 +
189 189  == 2.3  Positioning Mode(SMOD) ==
190 190  
191 191  
... ... @@ -198,8 +198,10 @@
198 198  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
199 199  
200 200  
202 +
201 201  == 2.4  Uplink Payload ==
202 202  
205 +
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||_mstalt="294580"]]
218 +[[image:1665301570342-765.png]]
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 -(% _mstmutation="1" style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
285 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
283 283  
284 284  
285 285  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -288,8 +288,6 @@
288 288  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit
289 289  |=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
290 290  
291 -
292 -
293 293  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
294 294  
295 295  
... ... @@ -308,7 +308,7 @@
308 308  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
309 309  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
310 310  
311 -[[image:1665301636888-168.png||_mstalt="298012"]]
312 +[[image:1665301636888-168.png]]
312 312  
313 313  
314 314  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -338,12 +338,12 @@
338 338  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:
339 339  
340 340  
341 -[[image:1664502116362-706.png||_mstalt="293306"]]
342 +[[image:1664502116362-706.png]]
342 342  
343 343  
344 344  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
345 345  
346 -[[image:1664502166010-515.png||_mstalt="291395"]]
347 +[[image:1664502166010-515.png]]
347 347  
348 348  
349 349  
... ... @@ -366,8 +366,6 @@
366 366  * 3.40v ~~ 3.69v:  20% ~~ 40%
367 367  * < 3.39v:  0~~20%
368 368  
369 -
370 -
371 371  ==== (% style="color:blue" %)**MOD:**(%%) ====
372 372  
373 373  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -408,6 +408,7 @@
408 408  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
409 409  
410 410  
410 +
411 411  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
412 412  
413 413  
... ... @@ -423,13 +423,14 @@
423 423  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
424 424  
425 425  (% class="wikigeneratedid" %)
426 -[[image:1665301687277-443.png||_mstalt="296140"]]
426 +[[image:1665301687277-443.png]]
427 427  
428 428  
429 +
429 429  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
430 430  
431 431  
432 -Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
433 +Set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
433 433  
434 434  
435 435  (% style="color:red" %)**Note for this mode:**
... ... @@ -446,9 +446,10 @@
446 446  )))|4|4|2|1|1|1|1|1
447 447  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
448 448  
449 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
450 +[[image:image-20221009160309-2.png]]
450 450  
451 451  
453 +
452 452  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
453 453  
454 454  
... ... @@ -473,7 +473,7 @@
473 473  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
474 474  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
475 475  
476 -[[image:1664502425687-834.png||_mstalt="296738"]]
478 +[[image:1664502425687-834.png]]
477 477  
478 478  
479 479  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -484,8 +484,6 @@
484 484  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
485 485  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
486 486  
487 -
488 -
489 489  === 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
490 490  
491 491  
... ... @@ -501,7 +501,7 @@
501 501  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
502 502  
503 503  (% class="wikigeneratedid" %)
504 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
504 +[[image:1667288597595-714.png||height="212" width="1151"]]
505 505  
506 506  
507 507  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -508,8 +508,6 @@
508 508  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
509 509  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
510 510  
511 -
512 -
513 513  === 2.4.7  Add Payload format in TTN V3 ===
514 514  
515 515  
... ... @@ -518,10 +518,9 @@
518 518  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
519 519  
520 520  
521 -[[image:1664502649601-895.png||_mstalt="296985"]]
519 +[[image:1664502649601-895.png]]
522 522  
523 523  
524 -
525 525  Add the decoder from this link: 
526 526  
527 527  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -528,9 +528,10 @@
528 528  
529 529  Save the change the uplink message will be parsed. As below:
530 530  
531 -[[image:1664502676891-606.png||_mstalt="296673"]]
528 +[[image:1664502676891-606.png]]
532 532  
533 533  
531 +
534 534  == 2.5 Integrate with Datacake ==
535 535  
536 536  
... ... @@ -539,9 +539,10 @@
539 539  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]]
540 540  
541 541  
542 -[[image:1664502695771-538.png||_mstalt="297349"]]
540 +[[image:1664502695771-538.png]]
543 543  
544 544  
543 +
545 545  == 2.6 Integrate with Tago ==
546 546  
547 547  
... ... @@ -550,24 +550,26 @@
550 550  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]]
551 551  
552 552  
553 -[[image:1664502715371-321.png||_mstalt="292162"]]
552 +[[image:1664502715371-321.png]]
554 554  
555 555  
555 +
556 556  == 2.7  Datalog Feature ==
557 557  
558 558  
559 559  total 273 entries,by default,
560 560  
561 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
561 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
562 562  
563 563  Example use case.
564 564  
565 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
565 +[[image:image-20221009234703-2.png||height="328" width="899"]]
566 566  
567 567  
568 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
568 +[[image:image-20221009234629-1.png||height="390" width="577"]]
569 569  
570 570  
571 +
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:**
586 +Two ways to exit alarm mode:
586 586  )))
587 587  
588 588  * Server sends a downlink command to exit.
... ... @@ -593,17 +593,14 @@
593 593  )))
594 594  
595 595  
597 +
596 596  == 2.9 Transport Mode ==
597 597  
598 598  
599 599  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.
600 600  
601 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
602 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
603 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
604 604  
605 605  
606 -
607 607  == 2.10 LED Status ==
608 608  
609 609  
... ... @@ -621,14 +621,12 @@
621 621  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
622 622  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
623 623  
624 -
625 -
626 626  == 2.11 Button Function ==
627 627  
628 628  
629 629  (% style="color:blue" %)**RESET button:**
630 630  
631 -[[image:1664502835802-546.png||_mstalt="295061"]]
627 +[[image:1664502835802-546.png]]
632 632  
633 633  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
634 634  
... ... @@ -635,7 +635,7 @@
635 635  
636 636  (% style="color:red" %)**RED button:**
637 637  
638 -[[image:1664502854406-763.png||_mstalt="295568"]]
634 +[[image:1664502854406-763.png]]
639 639  
640 640  
641 641  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -644,8 +644,6 @@
644 644  |(% 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
645 645  |(% 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.
646 646  
647 -
648 -
649 649  == 2.12 USB Port Function ==
650 650  
651 651  
... ... @@ -656,8 +656,6 @@
656 656  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
657 657  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
658 658  
659 -
660 -
661 661  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
662 662  
663 663  
... ... @@ -666,6 +666,7 @@
666 666  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
667 667  
668 668  
661 +
669 669  == 3.1 Access AT Command ==
670 670  
671 671  
... ... @@ -672,23 +672,25 @@
672 672  TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below.
673 673  
674 674  
675 -[[image:1664502999401-486.png||_mstalt="296985"]]
668 +[[image:1664502999401-486.png]]
676 676  
677 677  
678 678  In PC, User needs to set serial tool baud rate to (% style="color:green" %)**115200**(%%) to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands:
679 679  
680 680  
681 -[[image:1664503022490-662.png||_mstalt="293332"]]
674 +[[image:1664503022490-662.png]]
682 682  
683 683  
684 -[[image:1664503035713-500.png||_mstalt="291096"]]
677 +[[image:1664503035713-500.png]]
685 685  
686 686  
687 -[[image:1664503047675-651.png||_mstalt="295386"]]
680 +[[image:1664503047675-651.png]]
688 688  
689 689  
683 +
690 690  == 3.2 Command Set ==
691 691  
686 +
692 692  === 3.2.1 Set Transmit Interval ===
693 693  
694 694  
... ... @@ -706,6 +706,7 @@
706 706  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
707 707  
708 708  
704 +
709 709  === 3.2.2 Set Alarm Packet transmission interval ===
710 710  
711 711  
... ... @@ -723,6 +723,7 @@
723 723  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
724 724  
725 725  
722 +
726 726  === 3.2.3 Set Transport Mode Packet transmission interval ===
727 727  
728 728  
... ... @@ -740,6 +740,7 @@
740 740  (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
741 741  
742 742  
740 +
743 743  === 3.2.4 Exit Alarm ===
744 744  
745 745  
... ... @@ -752,6 +752,7 @@
752 752  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
753 753  
754 754  
753 +
755 755  === 3.2.5 Disable/Enable LED flash ===
756 756  
757 757  
... ... @@ -769,6 +769,7 @@
769 769  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
770 770  
771 771  
771 +
772 772  === 3.2.6 Disable/Enable Transport Mode ===
773 773  
774 774  
... ... @@ -786,6 +786,7 @@
786 786  (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
787 787  
788 788  
789 +
789 789  === 3.2.7 Set Positioning Mode ===
790 790  
791 791  
... ... @@ -812,9 +812,9 @@
812 812  
813 813  (% style="color:#037691" %)**cc:   **
814 814  
815 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
816 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
816 816  
817 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
818 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
818 818  
819 819  (% style="color:blue" %)**Example:**
820 820  
... ... @@ -832,6 +832,7 @@
832 832  (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
833 833  
834 834  
836 +
835 835  === 3.2.8 Set MAX GPS position time ===
836 836  
837 837  
... ... @@ -838,7 +838,7 @@
838 838  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.
839 839  
840 840  
841 -If **AT+FTIME=0**. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.
843 +If AT+FTIME=0. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.
842 842  
843 843  
844 844  * (% style="color:blue" %)**AT Command:**
... ... @@ -853,6 +853,7 @@
853 853  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
854 854  
855 855  
858 +
856 856  === 3.2.9 Set PDOP value for GPS fix accuracy ===
857 857  
858 858  
... ... @@ -876,8 +876,8 @@
876 876  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
877 877  
878 878  
879 -=== 3.2.10 Disable/Enable the confirmation mode ===
880 880  
883 +Disable/Enable the confirmation mode
881 881  
882 882  * (% style="color:blue" %)**AT Command:**
883 883  
... ... @@ -896,9 +896,10 @@
896 896  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
897 897  
898 898  
899 -=== 3.2.11  Auto Send None-ACK messages ===
900 900  
903 +=== 3.2.10  Auto Send None-ACK messages ===
901 901  
905 +
902 902  TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
903 903  
904 904  
... ... @@ -914,12 +914,13 @@
914 914  
915 915  * (% style="color:blue" %)**Downlink Command: 0x34**
916 916  
917 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
921 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
918 918  
919 919  
920 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
921 921  
925 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
922 922  
927 +
923 923  BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
924 924  
925 925  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -926,18 +926,19 @@
926 926  
927 927  (% style="color:blue" %)**AT Command:**
928 928  
929 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
934 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
930 930  
931 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
936 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
932 932  
933 933  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
934 934  
935 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
940 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
936 936  
937 937  
938 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
939 939  
944 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
940 940  
946 +
941 941  WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456 as prefix. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
942 942  
943 943  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
... ... @@ -944,61 +944,44 @@
944 944  
945 945  (% style="color:blue" %)**AT Command:**
946 946  
947 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
953 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
948 948  
949 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
955 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
950 950  
951 951  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
952 952  
953 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
959 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
954 954  
955 955  
956 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
957 957  
963 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
958 958  
965 +
959 959  Users can use this feature to enable/disable Information printing.
960 960  
961 961  (% style="color:blue" %)**AT Command:**
962 962  
963 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
970 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
964 964  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
965 965  
966 966  
967 -=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
968 968  
975 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
969 969  
977 +
970 970  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
971 971  
972 972  (% style="color:blue" %)**AT Command:**
973 973  
974 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
982 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
975 975  
976 976  
977 977  (% style="color:blue" %)**Downlink Payload:0X24**
978 978  
979 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
987 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
980 980  
981 981  
982 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
983 983  
984 -
985 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
986 -
987 -(% style="color:blue" %)**AT Command:**
988 -
989 -(% style="color:#037691" %)**AT+PT=xx**
990 -
991 - Example:
992 -
993 - AT+PT=14    ~-~->    Set to detect car motion.
994 -
995 - AT+PT=41  ~-~->    set to detect walk motion.
996 -
997 -
998 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
999 -0xB4 14          ~/~/  Same as AT+PT=14
1000 -
1001 -
1002 1002  = 4. Setting for Different Scenarios =
1003 1003  
1004 1004  
... ... @@ -1005,6 +1005,7 @@
1005 1005  
1006 1006  = 5. Upload Firmware =
1007 1007  
997 +
1008 1008  == 5.1 Firmware Change Log ==
1009 1009  
1010 1010  
... ... @@ -1011,6 +1011,7 @@
1011 1011  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1012 1012  
1013 1013  
1004 +
1014 1014  == 5.2 How to upgrade firmware ==
1015 1015  
1016 1016  
... ... @@ -1031,10 +1031,10 @@
1031 1031  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1032 1032  
1033 1033  
1034 -[[image:1664503563660-578.png||_mstalt="296777"]]
1025 +[[image:1664503563660-578.png]]
1035 1035  
1036 1036  
1037 -[[image:1664503574618-659.png||_mstalt="297986"]]
1028 +[[image:1664503574618-659.png]]
1038 1038  
1039 1039  
1040 1040  
... ... @@ -1043,7 +1043,7 @@
1043 1043  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1044 1044  
1045 1045  
1046 -**Users need to use below files:**
1037 +Users need to use below files:
1047 1047  
1048 1048  boot_app0.bin @0e000
1049 1049  
... ... @@ -1050,19 +1050,22 @@
1050 1050  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1051 1051  
1052 1052  
1053 -[[image:image-20221207120501-1.png]]
1044 +[[image:image-20221118105220-2.png]]
1054 1054  
1055 1055  
1056 1056  
1057 1057  After upgrade finish, it will show finish as below:
1058 1058  
1059 -[[image:image-20221207133911-7.png]]
1050 +[[image:image-20221118105402-4.png]]
1060 1060  
1061 1061  
1053 +
1062 1062  = 6. Developer Guide =
1063 1063  
1056 +
1064 1064  == 6.1 Compile Source Code ==
1065 1065  
1059 +
1066 1066  === 6.1.1 Set up ARDUINO compile environment ===
1067 1067  
1068 1068  
... ... @@ -1071,23 +1071,23 @@
1071 1071  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]]
1072 1072  
1073 1073  
1074 -[[image:1664503635019-941.png||_mstalt="294658"]]
1068 +[[image:1664503635019-941.png]]
1075 1075  
1076 1076  
1077 1077  
1078 1078  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1079 1079  
1080 -[[image:1664503715811-892.png||_mstalt="295698"]]
1074 +[[image:1664503715811-892.png]]
1081 1081  
1082 1082  
1083 1083  (% 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.
1084 1084  
1085 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1079 +[[image:image-20221024105643-1.png]]
1086 1086  
1087 1087  **~ Figure1**
1088 1088  
1089 1089  
1090 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1084 +[[image:image-20221024105643-2.png]]
1091 1091  
1092 1092   **Figure2**
1093 1093  
... ... @@ -1097,31 +1097,34 @@
1097 1097  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1098 1098  
1099 1099  
1100 -[[image:1664503752288-974.png||_mstalt="298194"]]
1094 +[[image:1664503752288-974.png]]
1101 1101  
1102 1102  
1097 +
1103 1103  == 6.2 Source Code ==
1104 1104  
1105 1105  
1106 1106  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1107 1107  
1108 -[[image:1664503794261-827.png||_mstalt="296387"]]
1103 +[[image:1664503794261-827.png]]
1109 1109  
1110 1110  
1111 1111  
1112 1112  * (% style="color:blue" %)**Click to upload**
1113 1113  
1114 -[[image:1664503808294-336.png||_mstalt="295711"]]
1109 +[[image:1664503808294-336.png]]
1115 1115  
1116 1116  
1117 1117  
1118 1118  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1119 1119  
1120 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1115 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1121 1121  
1122 1122  
1118 +
1123 1123  = 7.  FAQ =
1124 1124  
1121 +
1125 1125  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1126 1126  
1127 1127  
... ... @@ -1128,10 +1128,11 @@
1128 1128  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1129 1129  
1130 1130  
1128 +
1131 1131  == 7.2 What is the pin mapping for the USB program cable? ==
1132 1132  
1133 1133  
1134 -[[image:1664499635206-262.png||_mstalt="295360"]]
1132 +[[image:1664499635206-262.png]]
1135 1135  
1136 1136  
1137 1137  
... ... @@ -1146,10 +1146,9 @@
1146 1146  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1147 1147  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1148 1148  
1149 -
1150 -
1151 1151  == 7.3 Notes on using different serial port tools for TrackerD ==
1152 1152  
1149 +
1153 1153  === 7.3.1  Serial port utility ===
1154 1154  
1155 1155  
... ... @@ -1157,16 +1157,18 @@
1157 1157  
1158 1158  Need to adjust the data stream to RTS/CTS on physical restart.
1159 1159  
1157 +
1160 1160  (% class="wikigeneratedid" %)
1161 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1159 +[[image:image-20221102140621-1.png]]
1162 1162  
1163 1163  
1164 -
1165 1165  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1166 1166  
1167 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1168 1168  
1165 +[[image:image-20221102140638-2.png]]
1169 1169  
1167 +
1168 +
1170 1170  === 7.3.2  SecureCRT ===
1171 1171  
1172 1172  
... ... @@ -1173,22 +1173,23 @@
1173 1173  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.
1174 1174  
1175 1175  
1176 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1175 +[[image:image-20221102140704-3.png]]
1177 1177  
1178 1178  
1179 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1178 +[[image:image-20221102140712-4.png]]
1180 1180  
1181 1181  
1181 +
1182 1182  === 7.3.3  PUTTY ===
1183 1183  
1184 1184  
1185 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1185 +[[image:image-20221102140748-5.png]]
1186 1186  
1187 1187  
1188 1188  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.
1189 1189  
1190 1190  
1191 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1191 +[[image:image-20221102140801-6.png]]
1192 1192  
1193 1193  
1194 1194  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1200,46 +1200,38 @@
1200 1200  See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1201 1201  )))
1202 1202  
1203 -**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1203 +1.When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.
1204 1204  
1205 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1205 1205  
1206 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1207 +2.Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).
1207 1207  
1209 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1208 1208  
1211 +3.Compile the AS923_JP band, please refer to the intention shown
1209 1209  
1210 -**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1213 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1211 1211  
1215 +4.In other frequency bands in AS923, you need to find Lorabase_as923.H, path arduino-lmic \ src \ lmic, as shown in the figure below.
1212 1212  
1213 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1217 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1214 1214  
1219 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1215 1215  
1216 1216  
1217 -**3. Compile the AS923_JP band, please refer to the intention shown**
1218 1218  
1219 -
1220 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1221 -
1222 -
1223 -
1224 -**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.**
1225 -
1226 -
1227 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1228 -
1229 -
1230 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1231 -
1232 -
1233 1233  = 8  Trouble Shooting =
1234 1234  
1225 +
1235 1235  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1236 1236  
1237 1237  
1238 1238  (((
1239 -Before firmware v1.4.0: When the Transport Mode is enabled ((% style="color:blue" %)**AT+INTWK=1**(%%)), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1230 +Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1240 1240  )))
1241 1241  
1242 1242  
1234 +
1243 1243  == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1244 1244  
1245 1245  
... ... @@ -1248,144 +1248,85 @@
1248 1248  )))
1249 1249  
1250 1250  
1243 +
1251 1251  == 8.3  Problem after Upgrading Firmware ==
1252 1252  
1253 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1246 +=== 8.3.1 Continue Restart after upgrading ===
1254 1254  
1255 1255  
1256 -**Error Output**
1257 -
1258 -
1259 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1260 -
1261 -
1262 1262  (((
1263 -Some partition is missed during upgrade, please upgrade below four files as example:
1264 -
1265 -[[image:image-20221207120524-2.png]]
1250 +If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
1266 1266  )))
1267 1267  
1268 1268  
1269 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1254 +[[image:image-20221118105249-3.png]]
1270 1270  
1271 1271  
1257 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1258 +
1272 1272  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
1273 1273  
1274 1274  
1275 -=== 8.3.3 "flash read err" after upgrade firmware ===
1262 +==== 8.3.2.1 If there is a situation in Figure 1,and a new partition file and bootloader file needs to be added. Please refer to the operation steps in Figure 2 ====
1276 1276  
1264 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1277 1277  
1278 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1266 + Figure 1  
1279 1279  
1268 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1280 1280  
1281 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1270 + Figure 2
1282 1282  
1272 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1283 1283  
1284 -User need to upgrade again with below four files to solve this issue.
1274 +[[image:image-20221122100004-3.png]]
1285 1285  
1286 - [[image:image-20221207120530-3.png]]
1276 +Please AT+FDR, and then enter the following instructions by the information on the label
1287 1287  
1288 - **Figure 2**
1278 +AT+DEUI=70B3D57ED0053981
1289 1289  
1290 -
1291 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1292 -
1293 -
1294 -User might erase the entire flash include keys and default settings which cause this issue.
1295 -
1296 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1297 -
1298 -
1299 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1300 -
1301 -
1302 -Please (% style="color:blue" %)**AT+FDR**(%%) which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1303 -
1304 -After AT+FDR. please set
1305 -
1306 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1307 -
1308 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1309 -
1310 -**Example:**
1311 -
1312 -AT+PDOP=7.00
1313 -
1314 -AT+FTIME=180
1315 -
1316 -AT+DEUI=70B3D57ED0053981  
1317 -
1318 1318  AT+APPEUI=D23345667BCBCCAF
1319 1319  
1320 1320  AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1321 1321  
1322 -AT+DADDR=260b4dce    ( no need for OTAA)
1284 +AT+DADDR=260b4dce
1323 1323  
1324 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1286 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1325 1325  
1326 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1288 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1327 1327  
1328 1328  
1329 -== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1330 1330  
1292 +==== 8.3.2.2 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ====
1331 1331  
1332 -Please download version 1.4.2 again
1294 +[[image:image-20221122100004-4.png]]
1333 1333  
1296 +== ==
1334 1334  
1335 -== 8.5  How to deal with unsuccessful GPS positioning? ==
1298 +== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==
1336 1336  
1300 +Please download version 1.4.2 again
1337 1337  
1338 -1） Make Sure the device is in Open Area where can see the sky.
1339 1339  
1303 +(((
1304 +== 8.5 How to deal with unsuccessful GPS positioning? ==
1305 +
1306 +1） Make Sure the device is in Open Area where can see the sky. 
1340 1340  2)  Set PDOP to a higher value.
1341 1341  
1342 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1309 + AT+PDOP=2(can be positioned precisely.）
1343 1343  
1344 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1311 + AT+PDOP=7(Quickly locate in open spaces）
1345 1345  
1346 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1313 + AT+PDOP=14.7(Positioning can be acquired in complex environments）
1347 1347  
1348 1348  Please refer to this [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H3.2.9SetPDOPvalueforGPSfixaccuracy]] on how to set up PDOP
1316 +)))
1349 1349  
1350 1350  
1351 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1319 +== ==
1352 1352  
1353 1353  
1354 -When upgrading, use the erase button to upgrade
1355 -
1356 -[[image:image-20221207120536-4.png]]
1357 -
1358 -
1359 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1360 -
1361 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1362 -
1363 -
1364 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1365 -
1366 -[[image:image-20221207134028-8.png]]
1367 -
1368 -
1369 -Reboot information after upgrade
1370 -
1371 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1372 -
1373 -
1374 -Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal
1375 -
1376 -[[image:image-20221128111850-5.png]]
1377 -
1378 -
1379 -After the parameters return to normal, upgrade to the version you need again
1380 -
1381 -[[image:image-20221207120601-5.png]]
1382 -
1383 -
1384 -At this point, the parameters return to normal after running AT+FDR again
1385 -
1386 -[[image:image-20221128112035-7.png]]
1387 -
1388 -
1389 1389  = 9.  Order Info =
1390 1390  
1391 1391  
... ... @@ -1394,21 +1394,13 @@
1394 1394  (% style="color:blue" %)**XXX**(%%): The default frequency band
1395 1395  
1396 1396  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1397 -
1398 1398  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1399 -
1400 1400  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1401 -
1402 1402  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1403 -
1404 1404  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1405 -
1406 1406  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1407 -
1408 1408  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1409 1409  
1410 -
1411 -
1412 1412  = 10.  Packing Info =
1413 1413  
1414 1414  
... ... @@ -1415,32 +1415,22 @@
1415 1415  (% style="color:#037691" %)**Package Includes**:
1416 1416  
1417 1417  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1418 -
1419 1419  * USB recharge & program cable x 1
1420 1420  
1421 1421  (% style="color:#037691" %)**Dimensions and Weight**:
1422 1422  
1423 1423  * Device Size: 85 x 48 x 15 mm
1424 -
1425 1425  * Weight: 50g
1426 1426  
1427 -
1428 -
1429 1429  = 11. Support =
1430 1430  
1431 1431  
1432 1432  * 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.
1433 -
1434 1434  * 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]].
1435 1435  
1436 -
1437 -
1438 1438  = 12.  Reference =
1439 1439  
1440 1440  
1441 1441  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1442 -
1443 1443  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1444 -
1445 1445  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1446 -)))
image-20221128102938-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -41.3 KB
Content
image-20221128103040-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -19.2 KB
Content
image-20221128110503-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.6 KB
Content
image-20221128111443-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -15.6 KB
Content
image-20221128111850-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.5 KB
Content
image-20221128111951-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.4 KB
Content
image-20221128112035-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.7 KB
Content
image-20221207120501-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120524-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120530-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120536-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120601-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207133836-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.1 KB
Content
image-20221207133911-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -46.3 KB
Content
image-20221207134028-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.3 KB
Content
image-20221213100007-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -32.7 KB
Content