Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Xiaoling on 2025/04/27 16:48
From version 163.1
edited by Bei Jinggeng
on 2022/11/28 11:20
on 2022/11/28 11:20
Change comment:
There is no comment for this version
To version 142.1
edited by Bei Jinggeng
on 2022/11/22 10:02
on 2022/11/22 10:02
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 7 removed)
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 ... ... @@ -14,6 +14,7 @@ 14 14 15 15 = 1. Introduction = 16 16 17 + 17 17 == 1.1 What is TrackerD == 18 18 19 19 ... ... @@ -31,17 +31,21 @@ 31 31 ((( 32 32 The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services. 33 33 ))) 35 +))) 34 34 35 35 ((( 36 36 TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network. 39 + 40 + 37 37 ))) 38 38 39 -[[image:1664499921684-770.png ||_mstalt="298194"]]43 +[[image:1664499921684-770.png]] 40 40 41 41 42 42 (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.** 43 43 44 44 49 + 45 45 == 1.2 Specifications == 46 46 47 47 ... ... @@ -92,7 +92,6 @@ 92 92 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm 93 93 * Tracking: max: 38mA 94 94 95 - 96 96 == 1.3 Features == 97 97 98 98 ... ... @@ -111,7 +111,6 @@ 111 111 * Tri-color LED, Alarm button 112 112 * Datalog 113 113 114 - 115 115 == 1.4 Applications == 116 116 117 117 ... ... @@ -118,9 +118,9 @@ 118 118 * Logistics and Supply Chain Management 119 119 * Human tracking 120 120 121 - 122 122 = 2. Use TrackerD = 123 123 126 + 124 124 == 2.1 How it works? == 125 125 126 126 ... ... @@ -127,6 +127,7 @@ 127 127 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. 128 128 129 129 133 + 130 130 == 2.2 Quick guide to connect to LoRaWAN server == 131 131 132 132 ... ... @@ -133,7 +133,7 @@ 133 133 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. 134 134 135 135 136 -[[image:1664501652064-326.png ||_mstalt="293306"]]140 +[[image:1664501652064-326.png]] 137 137 138 138 139 139 ... ... @@ -145,7 +145,7 @@ 145 145 Each TrackerD is shipped with a sticker with the default device EUI as below: 146 146 147 147 148 -[[image:1664501677253-891.png ||_mstalt="296569"]]152 +[[image:1664501677253-891.png]] 149 149 150 150 151 151 Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot: ... ... @@ -154,14 +154,14 @@ 154 154 **__Add APP EUI in the application:__** 155 155 156 156 157 -[[image:1664501711466-918.png ||_mstalt="295828"]]161 +[[image:1664501711466-918.png]] 158 158 159 159 160 160 161 -[[image:1664501721248-725.png ||_mstalt="294450"]]165 +[[image:1664501721248-725.png]] 162 162 163 163 164 -[[image:1664501734705-405.png ||_mstalt="293306"]]168 +[[image:1664501734705-405.png]] 165 165 166 166 167 167 ... ... @@ -168,20 +168,21 @@ 168 168 **__Add APP KEY and DEV EUI:__** 169 169 170 170 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"]]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"]] 172 172 173 173 174 174 175 175 (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device. 176 176 177 -(% 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]] 178 178 179 -[[image:1664502835802-546.png ||_mstalt="295061"]]183 +[[image:1664502835802-546.png]] 180 180 181 181 182 182 (% 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. 183 183 184 184 189 + 185 185 == 2.3 Positioning Mode(SMOD) == 186 186 187 187 ... ... @@ -194,8 +194,10 @@ 194 194 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 195 195 196 196 202 + 197 197 == 2.4 Uplink Payload == 198 198 205 + 199 199 === 2.4.1 Uplink FPORT~=5, Device Status === 200 200 201 201 ... ... @@ -208,7 +208,7 @@ 208 208 |=(% 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 209 209 |=(% 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 210 210 211 -[[image:1665301570342-765.png ||_mstalt="294580"]]218 +[[image:1665301570342-765.png]] 212 212 213 213 214 214 (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002 ... ... @@ -275,7 +275,7 @@ 275 275 276 276 (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 277 277 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)(%%)285 +(% style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%) 279 279 280 280 281 281 (% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 ... ... @@ -284,7 +284,6 @@ 284 284 |=(% 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 285 285 |=(% 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"]] 286 286 287 - 288 288 === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 289 289 290 290 ... ... @@ -303,7 +303,7 @@ 303 303 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 304 304 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 305 305 306 -[[image:1665301636888-168.png ||_mstalt="298012"]]312 +[[image:1665301636888-168.png]] 307 307 308 308 309 309 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== ... ... @@ -333,12 +333,12 @@ 333 333 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: 334 334 335 335 336 -[[image:1664502116362-706.png ||_mstalt="293306"]]342 +[[image:1664502116362-706.png]] 337 337 338 338 339 339 3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 340 340 341 -[[image:1664502166010-515.png ||_mstalt="291395"]]347 +[[image:1664502166010-515.png]] 342 342 343 343 344 344 ... ... @@ -361,7 +361,6 @@ 361 361 * 3.40v ~~ 3.69v: 20% ~~ 40% 362 362 * < 3.39v: 0~~20% 363 363 364 - 365 365 ==== (% style="color:blue" %)**MOD:**(%%) ==== 366 366 367 367 **Example: ** (0x60>>6) & 0x3f =1 ... ... @@ -402,6 +402,7 @@ 402 402 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree// 403 403 404 404 410 + 405 405 === 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) === 406 406 407 407 ... ... @@ -417,13 +417,14 @@ 417 417 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 418 418 419 419 (% class="wikigeneratedid" %) 420 -[[image:1665301687277-443.png ||_mstalt="296140"]]426 +[[image:1665301687277-443.png]] 421 421 422 422 429 + 423 423 === 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 424 424 425 425 426 -Set [[PNACKMD=1>>||anchor="H3.2.1 1A0A0AutoSendNone-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. 427 427 428 428 429 429 (% style="color:red" %)**Note for this mode:** ... ... @@ -440,9 +440,10 @@ 440 440 )))|4|4|2|1|1|1|1|1 441 441 |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 442 442 443 -[[image:image-20221009160309-2.png ||_mstalt="429312"]]450 +[[image:image-20221009160309-2.png]] 444 444 445 445 453 + 446 446 === 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 447 447 448 448 ... ... @@ -467,7 +467,7 @@ 467 467 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 468 468 )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 469 469 470 -[[image:1664502425687-834.png ||_mstalt="296738"]]478 +[[image:1664502425687-834.png]] 471 471 472 472 473 473 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). ... ... @@ -478,7 +478,6 @@ 478 478 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 479 479 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 480 480 481 - 482 482 === 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 483 483 484 484 ... ... @@ -494,7 +494,7 @@ 494 494 )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 495 495 496 496 (% class="wikigeneratedid" %) 497 -[[image:1667288597595-714.png|| _mstalt="299598"height="212" width="1151"]]504 +[[image:1667288597595-714.png||height="212" width="1151"]] 498 498 499 499 500 500 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). ... ... @@ -501,7 +501,6 @@ 501 501 * (% style="color:#037691" %)**SSID: **(%%)WiFi name. 502 502 * (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 503 503 504 - 505 505 === 2.4.7 Add Payload format in TTN V3 === 506 506 507 507 ... ... @@ -510,10 +510,9 @@ 510 510 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 511 511 512 512 513 -[[image:1664502649601-895.png ||_mstalt="296985"]]519 +[[image:1664502649601-895.png]] 514 514 515 515 516 - 517 517 Add the decoder from this link: 518 518 519 519 [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] ... ... @@ -520,9 +520,10 @@ 520 520 521 521 Save the change the uplink message will be parsed. As below: 522 522 523 -[[image:1664502676891-606.png ||_mstalt="296673"]]528 +[[image:1664502676891-606.png]] 524 524 525 525 531 + 526 526 == 2.5 Integrate with Datacake == 527 527 528 528 ... ... @@ -531,9 +531,10 @@ 531 531 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]] 532 532 533 533 534 -[[image:1664502695771-538.png ||_mstalt="297349"]]540 +[[image:1664502695771-538.png]] 535 535 536 536 543 + 537 537 == 2.6 Integrate with Tago == 538 538 539 539 ... ... @@ -542,24 +542,26 @@ 542 542 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]] 543 543 544 544 545 -[[image:1664502715371-321.png ||_mstalt="292162"]]552 +[[image:1664502715371-321.png]] 546 546 547 547 555 + 548 548 == 2.7 Datalog Feature == 549 549 550 550 551 551 total 273 entries,by default, 552 552 553 -User can set [[PNACKMD=1>>||anchor="H3.2.1 1A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.561 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 554 554 555 555 Example use case. 556 556 557 -[[image:image-20221009234703-2.png|| _mstalt="429143"height="328" width="899"]]565 +[[image:image-20221009234703-2.png||height="328" width="899"]] 558 558 559 559 560 -[[image:image-20221009234629-1.png|| _mstalt="431145"height="390" width="577"]]568 +[[image:image-20221009234629-1.png||height="390" width="577"]] 561 561 562 562 571 + 563 563 == 2.8 Alarm Mode == 564 564 565 565 ... ... @@ -574,7 +574,7 @@ 574 574 575 575 576 576 ((( 577 - **Two ways to exit alarm mode:**586 +Two ways to exit alarm mode: 578 578 ))) 579 579 580 580 * Server sends a downlink command to exit. ... ... @@ -585,14 +585,12 @@ 585 585 ))) 586 586 587 587 597 + 588 588 == 2.9 Transport Mode == 589 589 590 590 591 591 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. 592 592 593 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation. 594 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic. 595 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion. 596 596 597 597 598 598 == 2.10 LED Status == ... ... @@ -612,13 +612,12 @@ 612 612 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 613 613 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 614 614 615 - 616 616 == 2.11 Button Function == 617 617 618 618 619 619 (% style="color:blue" %)**RESET button:** 620 620 621 -[[image:1664502835802-546.png ||_mstalt="295061"]]627 +[[image:1664502835802-546.png]] 622 622 623 623 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server. 624 624 ... ... @@ -625,7 +625,7 @@ 625 625 626 626 (% style="color:red" %)**RED button:** 627 627 628 -[[image:1664502854406-763.png ||_mstalt="295568"]]634 +[[image:1664502854406-763.png]] 629 629 630 630 631 631 (% border="1" style="background-color:#ffffcc; width:510px" %) ... ... @@ -634,7 +634,6 @@ 634 634 |(% 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 635 635 |(% 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. 636 636 637 - 638 638 == 2.12 USB Port Function == 639 639 640 640 ... ... @@ -645,7 +645,6 @@ 645 645 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 646 646 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 647 647 648 - 649 649 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 650 650 651 651 ... ... @@ -654,6 +654,7 @@ 654 654 LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] 655 655 656 656 661 + 657 657 == 3.1 Access AT Command == 658 658 659 659 ... ... @@ -660,23 +660,25 @@ 660 660 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. 661 661 662 662 663 -[[image:1664502999401-486.png ||_mstalt="296985"]]668 +[[image:1664502999401-486.png]] 664 664 665 665 666 666 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: 667 667 668 668 669 -[[image:1664503022490-662.png ||_mstalt="293332"]]674 +[[image:1664503022490-662.png]] 670 670 671 671 672 -[[image:1664503035713-500.png ||_mstalt="291096"]]677 +[[image:1664503035713-500.png]] 673 673 674 674 675 -[[image:1664503047675-651.png ||_mstalt="295386"]]680 +[[image:1664503047675-651.png]] 676 676 677 677 683 + 678 678 == 3.2 Command Set == 679 679 686 + 680 680 === 3.2.1 Set Transmit Interval === 681 681 682 682 ... ... @@ -694,6 +694,7 @@ 694 694 (% style="color:#037691" %)**0x01 00 01 2C** (%%) ~/~/ Same as AT+TDC=300000 695 695 696 696 704 + 697 697 === 3.2.2 Set Alarm Packet transmission interval === 698 698 699 699 ... ... @@ -711,6 +711,7 @@ 711 711 (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/ Same as AT+ATDC=60000 712 712 713 713 722 + 714 714 === 3.2.3 Set Transport Mode Packet transmission interval === 715 715 716 716 ... ... @@ -728,6 +728,7 @@ 728 728 (% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+MTDC=3000000 729 729 730 730 740 + 731 731 === 3.2.4 Exit Alarm === 732 732 733 733 ... ... @@ -740,6 +740,7 @@ 740 740 (% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 741 741 742 742 753 + 743 743 === 3.2.5 Disable/Enable LED flash === 744 744 745 745 ... ... @@ -757,6 +757,7 @@ 757 757 (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/ Same as AT+LON=0 758 758 759 759 771 + 760 760 === 3.2.6 Disable/Enable Transport Mode === 761 761 762 762 ... ... @@ -774,6 +774,7 @@ 774 774 (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+INTWK=1 775 775 776 776 789 + 777 777 === 3.2.7 Set Positioning Mode === 778 778 779 779 ... ... @@ -800,9 +800,9 @@ 800 800 801 801 (% style="color:#037691" %)**cc: ** 802 802 803 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State816 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 804 804 805 -* (% _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(%%)) 806 806 807 807 (% style="color:blue" %)**Example:** 808 808 ... ... @@ -820,6 +820,7 @@ 820 820 (% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+SMOD=1,0,0 821 821 822 822 836 + 823 823 === 3.2.8 Set MAX GPS position time === 824 824 825 825 ... ... @@ -826,7 +826,7 @@ 826 826 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. 827 827 828 828 829 -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. 830 830 831 831 832 832 * (% style="color:blue" %)**AT Command:** ... ... @@ -841,6 +841,7 @@ 841 841 (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/ Set AT+FTIME=150 842 842 843 843 858 + 844 844 === 3.2.9 Set PDOP value for GPS fix accuracy === 845 845 846 846 ... ... @@ -865,9 +865,8 @@ 865 865 866 866 867 867 868 - === 3.2.10Disable/Enable the confirmation mode===883 +Disable/Enable the confirmation mode 869 869 870 - 871 871 * (% style="color:blue" %)**AT Command:** 872 872 873 873 (% style="color:#037691" %)**AT+CFM=xx** ... ... @@ -885,9 +885,10 @@ 885 885 (% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1 886 886 887 887 888 -=== 3.2.11 Auto Send None-ACK messages === 889 889 903 +=== 3.2.10 Auto Send None-ACK messages === 890 890 905 + 891 891 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. 892 892 893 893 ... ... @@ -903,12 +903,13 @@ 903 903 904 904 * (% style="color:blue" %)**Downlink Command: 0x34** 905 905 906 -Example: 0x34 921 +Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 907 907 908 908 909 -=== 3.2.12 Set BLEMASK to filter BLE iBeacon === 910 910 925 +=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 911 911 927 + 912 912 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. 913 913 914 914 (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.** ... ... @@ -915,18 +915,19 @@ 915 915 916 916 (% style="color:blue" %)**AT Command:** 917 917 918 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456934 + (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 919 919 920 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK936 + (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 921 921 922 922 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 923 923 924 -Example: 0xB2 940 +Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 925 925 926 926 927 -=== 3.2.13 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 928 928 944 +=== 3.2.12 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 929 929 946 + 930 930 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. 931 931 932 932 (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.** ... ... @@ -933,18 +933,19 @@ 933 933 934 934 (% style="color:blue" %)**AT Command:** 935 935 936 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456953 + (% style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456 937 937 938 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK955 + (% style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK 939 939 940 940 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)** 941 941 942 -Example: 0xB3 959 +Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 943 943 944 944 945 -=== 3.2.14 Disable/Enable Information printing(Since firmware 1.4.1) === 946 946 963 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 947 947 965 + 948 948 Users can use this feature to enable/disable Information printing. 949 949 950 950 (% style="color:blue" %)**AT Command:** ... ... @@ -953,9 +953,10 @@ 953 953 \\Example: AT+SHOWID=1 ~-~-> Enable Information printing. 954 954 955 955 956 -=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 957 957 975 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 958 958 977 + 959 959 The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. 960 960 961 961 (% style="color:blue" %)**AT Command:** ... ... @@ -968,26 +968,7 @@ 968 968 Example: 0x24 01 ~/~/ Same as AT+CHE=1 969 969 970 970 971 -=== 3.2.16 Get or Set Threshold for motion detect(Since firmware 1.4.3) === 972 972 973 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event. 974 - 975 -(% style="color:blue" %)**AT Command:** 976 - 977 -(% style="color:#037691" %)**AT+PT=xx** 978 - 979 - Example: 980 - 981 - AT+PT=14 ~-~-> Set to detect car motion. 982 - 983 - AT+PT=41 ~-~-> set to detect walk motion. 984 - 985 - 986 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%) 987 -0xB4 14 ~/~/ Same as AT+PT=14 988 - 989 - 990 - 991 991 = 4. Setting for Different Scenarios = 992 992 993 993 ... ... @@ -994,6 +994,7 @@ 994 994 995 995 = 5. Upload Firmware = 996 996 997 + 997 997 == 5.1 Firmware Change Log == 998 998 999 999 ... ... @@ -1000,6 +1000,7 @@ 1000 1000 **[[See this link>>url:https://github.com/dragino/TrackerD]]** 1001 1001 1002 1002 1004 + 1003 1003 == 5.2 How to upgrade firmware == 1004 1004 1005 1005 ... ... @@ -1020,10 +1020,10 @@ 1020 1020 (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32 1021 1021 1022 1022 1023 -[[image:1664503563660-578.png ||_mstalt="296777"]]1025 +[[image:1664503563660-578.png]] 1024 1024 1025 1025 1026 -[[image:1664503574618-659.png ||_mstalt="297986"]]1028 +[[image:1664503574618-659.png]] 1027 1027 1028 1028 1029 1029 ... ... @@ -1032,7 +1032,7 @@ 1032 1032 [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]] 1033 1033 1034 1034 1035 - **Users need to use below files:**1037 +Users need to use below files: 1036 1036 1037 1037 boot_app0.bin @0e000 1038 1038 ... ... @@ -1039,20 +1039,22 @@ 1039 1039 US915.bin @ 0x10000(Select the bin file of the frequency band you need) 1040 1040 1041 1041 1042 -[[image:image-20221118105220-2.png ||_mstalt="426608"]]1044 +[[image:image-20221118105220-2.png]] 1043 1043 1044 1044 1045 1045 1046 1046 After upgrade finish, it will show finish as below: 1047 1047 1048 -[[image:image-20221118105402-4.png ||_mstalt="427986"]]1050 +[[image:image-20221118105402-4.png]] 1049 1049 1050 1050 1051 1051 1052 1052 = 6. Developer Guide = 1053 1053 1056 + 1054 1054 == 6.1 Compile Source Code == 1055 1055 1059 + 1056 1056 === 6.1.1 Set up ARDUINO compile environment === 1057 1057 1058 1058 ... ... @@ -1061,23 +1061,23 @@ 1061 1061 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]] 1062 1062 1063 1063 1064 -[[image:1664503635019-941.png ||_mstalt="294658"]]1068 +[[image:1664503635019-941.png]] 1065 1065 1066 1066 1067 1067 1068 1068 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 1069 1069 1070 -[[image:1664503715811-892.png ||_mstalt="295698"]]1074 +[[image:1664503715811-892.png]] 1071 1071 1072 1072 1073 1073 (% 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. 1074 1074 1075 -[[image:image-20221024105643-1.png ||_mstalt="428129"]]1079 +[[image:image-20221024105643-1.png]] 1076 1076 1077 1077 **~ Figure1** 1078 1078 1079 1079 1080 -[[image:image-20221024105643-2.png ||_mstalt="428493"]]1084 +[[image:image-20221024105643-2.png]] 1081 1081 1082 1082 **Figure2** 1083 1083 ... ... @@ -1087,31 +1087,34 @@ 1087 1087 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: 1088 1088 1089 1089 1090 -[[image:1664503752288-974.png ||_mstalt="298194"]]1094 +[[image:1664503752288-974.png]] 1091 1091 1092 1092 1097 + 1093 1093 == 6.2 Source Code == 1094 1094 1095 1095 1096 1096 * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:** 1097 1097 1098 -[[image:1664503794261-827.png ||_mstalt="296387"]]1103 +[[image:1664503794261-827.png]] 1099 1099 1100 1100 1101 1101 1102 1102 * (% style="color:blue" %)**Click to upload** 1103 1103 1104 -[[image:1664503808294-336.png ||_mstalt="295711"]]1109 +[[image:1664503808294-336.png]] 1105 1105 1106 1106 1107 1107 1108 1108 * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 1109 1109 1110 -[[image:1664503824081-592.png ||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]1115 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 1111 1111 1112 1112 1118 + 1113 1113 = 7. FAQ = 1114 1114 1121 + 1115 1115 == 7.1 How to change the LoRa Frequency Bands/Region? == 1116 1116 1117 1117 ... ... @@ -1118,10 +1118,11 @@ 1118 1118 User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download. 1119 1119 1120 1120 1128 + 1121 1121 == 7.2 What is the pin mapping for the USB program cable? == 1122 1122 1123 1123 1124 -[[image:1664499635206-262.png ||_mstalt="295360"]]1132 +[[image:1664499635206-262.png]] 1125 1125 1126 1126 1127 1127 ... ... @@ -1136,9 +1136,9 @@ 1136 1136 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 1137 1137 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 1138 1138 1139 - 1140 1140 == 7.3 Notes on using different serial port tools for TrackerD == 1141 1141 1149 + 1142 1142 === 7.3.1 Serial port utility === 1143 1143 1144 1144 ... ... @@ -1146,16 +1146,18 @@ 1146 1146 1147 1147 Need to adjust the data stream to RTS/CTS on physical restart. 1148 1148 1157 + 1149 1149 (% class="wikigeneratedid" %) 1150 -[[image:image-20221102140621-1.png ||_mstalt="425672"]]1159 +[[image:image-20221102140621-1.png]] 1151 1151 1152 1152 1153 - 1154 1154 When using AT commands, the data flow needs to be adjusted to XON/XOFF 1155 1155 1156 -[[image:image-20221102140638-2.png||_mstalt="428727"]] 1157 1157 1165 +[[image:image-20221102140638-2.png]] 1158 1158 1167 + 1168 + 1159 1159 === 7.3.2 SecureCRT === 1160 1160 1161 1161 ... ... @@ -1162,22 +1162,23 @@ 1162 1162 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. 1163 1163 1164 1164 1165 -[[image:image-20221102140704-3.png ||_mstalt="427076"]]1175 +[[image:image-20221102140704-3.png]] 1166 1166 1167 1167 1168 -[[image:image-20221102140712-4.png ||_mstalt="427089"]]1178 +[[image:image-20221102140712-4.png]] 1169 1169 1170 1170 1181 + 1171 1171 === 7.3.3 PUTTY === 1172 1172 1173 1173 1174 -[[image:image-20221102140748-5.png ||_mstalt="430456"]]1185 +[[image:image-20221102140748-5.png]] 1175 1175 1176 1176 1177 1177 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. 1178 1178 1179 1179 1180 -[[image:image-20221102140801-6.png ||_mstalt="427466"]]1191 +[[image:image-20221102140801-6.png]] 1181 1181 1182 1182 1183 1183 == 7.4 How to modify source code to compile different frequency band bin file? == ... ... @@ -1189,46 +1189,38 @@ 1189 1189 See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]] 1190 1190 ))) 1191 1191 1192 - **~1.**1203 +1.When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file. 1193 1193 1205 +[[image:image-20221116111844-1.png||height="227" width="782"]] 1194 1194 1195 - [[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). 1196 1196 1209 +[[image:image-20221116111844-2.png||height="262" width="781"]] 1197 1197 1211 +3.Compile the AS923_JP band, please refer to the intention shown 1198 1198 1199 - **2. Open LMIC_PROJECT_CONFIG.H, find the correspondingmacro definitionand open it(AS923_2,AS923_3,AS923_4except).**1213 +[[image:image-20221116111844-3.png||height="338" width="746"]] 1200 1200 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. 1201 1201 1202 -[[image:image-20221116111844- 2.png||_mstalt="429052"height="262" width="781"]]1217 +[[image:image-20221116111844-4.png||height="641" width="739"]] 1203 1203 1219 +[[image:image-20221116111844-5.png||height="551" width="708"]] 1204 1204 1205 1205 1206 -**3. Compile the AS923_JP band, please refer to the intention shown** 1207 1207 1208 - 1209 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]] 1210 - 1211 - 1212 - 1213 -**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.** 1214 - 1215 - 1216 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]] 1217 - 1218 - 1219 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]] 1220 - 1221 - 1222 1222 = 8 Trouble Shooting = 1223 1223 1225 + 1224 1224 == 8.1 TDC is changed to 4294947296 and cause no uplink. == 1225 1225 1226 1226 1227 1227 ((( 1228 -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.11230 +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 1229 1229 ))) 1230 1230 1231 1231 1234 + 1232 1232 == 8.2 Device not able get AT Command or show output after wake up from deep sleep mode == 1233 1233 1234 1234 ... ... @@ -1237,138 +1237,86 @@ 1237 1237 ))) 1238 1238 1239 1239 1243 + 1240 1240 == 8.3 Problem after Upgrading Firmware == 1241 1241 1242 -=== 8.3.1 "rst: (0x3 SW_RESET)" andContinue Restart after upgrading ===1246 +=== 8.3.1 Continue Restart after upgrading === 1243 1243 1244 1244 1245 -**Error Output** 1246 - 1247 - 1248 -[[image:image-20221122100004-4.png||_mstalt="424606"]] 1249 - 1250 - 1251 1251 ((( 1252 -Some partition is missed during upgrade, please upgrade below four files as example: 1253 - 1254 -[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]] 1250 +If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure 1255 1255 ))) 1256 1256 1257 1257 1258 - === 8.3.2 TrackerD's led light isalways GREEN on after upgrading===1254 +[[image:image-20221118105249-3.png]] 1259 1259 1260 1260 1257 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1258 + 1261 1261 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 1262 1262 1263 1263 1264 -=== 8.3. 3"flashread err"afterupgradefirmware ===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 ==== 1265 1265 1264 +[[image:image-20221122100004-1.png||height="497" width="534"]] 1266 1266 1267 - Errorshowsbelow,usermighterasetheentireflashincludeu-bootpartitionwhichcausethisissue.1266 + Figure 1 1268 1268 1268 + [[image:image-20221122100004-2.png||height="619" width="389"]] 1269 1269 1270 - [[image:image-20221122100004-1.png||_mstalt="423514"height="497" width="534"]]1270 + Figure 2 1271 1271 1272 +After the upgrade is completed, enter AT+CFG as shown in the figure below. 1272 1272 1273 - User need to upgradeain with below four files to solve this issue.1274 +[[image:image-20221122100004-3.png]] 1274 1274 1275 - [[image:image-20221122100004-2.png||_mstalt="423878"height="619" width="389"]]1276 +Please at+FDR, and then enter the following instructions by the information on the label 1276 1276 1277 - **Figure 2**1278 +AT+DEUI=70B3D57ED0053981 1278 1278 1279 - 1280 -=== 8.3.4 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware === 1281 - 1282 - 1283 -User might erase the entire flash include keys and default settings which cause this issue. 1284 - 1285 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below. 1286 - 1287 - 1288 -[[image:image-20221122100004-3.png||_mstalt="424242"]] 1289 - 1290 - 1291 -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. 1292 - 1293 -After AT+FDR. please set 1294 - 1295 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7** 1296 - 1297 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000** 1298 - 1299 -**Example:** 1300 - 1301 -AT+PDOP=7.00 1302 - 1303 -AT+FTIME=180 1304 - 1305 -AT+DEUI=70B3D57ED0053981 1306 - 1307 1307 AT+APPEUI=D23345667BCBCCAF 1308 1308 1309 1309 AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1 1310 1310 1311 -AT+DADDR=260b4dce ( no need for OTAA)1284 +AT+DADDR=260b4dce 1312 1312 1313 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d ( no need for OTAA)1286 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d 1314 1314 1315 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA)1288 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 1316 1316 1317 1317 1318 -== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1319 1319 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 ==== 1320 1320 1321 - Pleasedownload version1.4.2 again1294 +[[image:image-20221122100004-4.png]] 1322 1322 1296 +(% class="wikigeneratedid" %) 1297 +== == 1323 1323 1324 -== 8. 5Howtodealwith unsuccessfulGPS positioning?==1299 +== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1325 1325 1301 +Please download version 1.4.2 again 1326 1326 1327 -1) Make Sure the device is in Open Area where can see the sky. 1328 1328 1304 +((( 1305 +== 8.5 How to deal with unsuccessful GPS positioning? == 1306 + 1307 +1) Make Sure the device is in Open Area where can see the sky. 1329 1329 2) Set PDOP to a higher value. 1330 1330 1331 - *(%_mstmutation="1"style="color:blue"%)**AT+PDOP=2**(%%)(can be positioned precisely.)1310 + AT+PDOP=2(can be positioned precisely.) 1332 1332 1333 - *(%_mstmutation="1"style="color:blue"%)**AT+PDOP=7**(%%)(Quickly locate in open spaces)1312 + AT+PDOP=7(Quickly locate in open spaces) 1334 1334 1335 - *(%_mstmutation="1"style="color:blue"%)**AT+PDOP=14.7**(%%)(Positioning can be acquired in complex environments)1314 + AT+PDOP=14.7(Positioning can be acquired in complex environments) 1336 1336 1337 1337 Please refer to this [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H3.2.9SetPDOPvalueforGPSfixaccuracy]] on how to set up PDOP 1317 +))) 1338 1338 1339 1339 1340 -== 8.6Whenupgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets==1320 +== == 1341 1341 1342 -When upgrading, use the erase button to upgrade 1343 1343 1344 -[[image:image-20221128102938-1.png||height="537" width="335"]] 1345 - 1346 - 1347 -The parameters are displayed abnormally and cannot be fixed using AT+FDR 1348 - 1349 -[[image:image-20221128103040-2.png||height="431" width="525"]] 1350 - 1351 -Please upgrade these four files,link(The boot_app0 file is in the version folder you need) 1352 - 1353 -[[image:image-20221128110503-3.png||height="647" width="410"]] 1354 - 1355 -Reboot information after upgrade 1356 - 1357 -[[image:image-20221128111443-4.png||height="432" width="546"]] 1358 - 1359 -Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal 1360 - 1361 -[[image:image-20221128111850-5.png]] 1362 - 1363 -After the parameters return to normal, upgrade to the version you need again 1364 - 1365 -[[image:image-20221128111951-6.png||height="620" width="389"]] 1366 - 1367 -At this point the parameters return to normal 1368 - 1369 -[[image:image-20221128112035-7.png]] 1370 - 1371 - 1372 1372 = 9. Order Info = 1373 1373 1374 1374 ... ... @@ -1377,20 +1377,13 @@ 1377 1377 (% style="color:blue" %)**XXX**(%%): The default frequency band 1378 1378 1379 1379 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433 1380 - 1381 1381 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868 1382 - 1383 1383 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865 1384 - 1385 1385 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920 1386 - 1387 1387 * (% style="color:red" %)**AS923**(%%): Default frequency band AS923 1388 - 1389 1389 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 1390 - 1391 1391 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1392 1392 1393 - 1394 1394 = 10. Packing Info = 1395 1395 1396 1396 ... ... @@ -1397,30 +1397,22 @@ 1397 1397 (% style="color:#037691" %)**Package Includes**: 1398 1398 1399 1399 * TrackerD LoRaWAN GPS/BLE Tracker x 1 1400 - 1401 1401 * USB recharge & program cable x 1 1402 1402 1403 1403 (% style="color:#037691" %)**Dimensions and Weight**: 1404 1404 1405 1405 * Device Size: 85 x 48 x 15 mm 1406 - 1407 1407 * Weight: 50g 1408 1408 1409 - 1410 1410 = 11. Support = 1411 1411 1412 1412 1413 1413 * 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. 1414 - 1415 1415 * 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]]. 1416 1416 1417 - 1418 1418 = 12. Reference = 1419 1419 1420 1420 1421 1421 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1422 - 1423 1423 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1424 - 1425 1425 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 1426 -)))
- 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