Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Bei Jinggeng on 2025/08/01 17:45
From version 182.1
edited by Bei Jinggeng
on 2022/12/13 10:38
on 2022/12/13 10:38
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 36 removed)
- image-20221107145243-1.png
- image-20221116111844-1.png
- image-20221116111844-2.png
- image-20221116111844-3.png
- image-20221116111844-4.png
- image-20221116111844-5.png
- image-20221118104359-1.png
- image-20221118105220-2.png
- image-20221118105249-3.png
- image-20221118105402-4.png
- image-20221122100004-1.png
- image-20221122100004-2.png
- image-20221122100004-3.png
- image-20221122100004-4.png
- image-20221128102938-1.png
- image-20221128103040-2.png
- image-20221128110503-3.png
- image-20221128111443-4.png
- image-20221128111850-5.png
- image-20221128111951-6.png
- image-20221128112035-7.png
- image-20221207120501-1.png
- image-20221207120524-2.png
- image-20221207120530-3.png
- image-20221207120536-4.png
- image-20221207120601-5.png
- image-20221207133836-6.png
- image-20221207133911-7.png
- image-20221207134028-8.png
- image-20221213100007-1.png
- image-20221213100626-2.png
- image-20221213100808-3.png
- image-20221213101040-4.png
- image-20221213102311-5.png
- image-20221213102334-6.png
- image-20221213102718-7.png
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Bei1 +XWiki.Xiaoling - 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,6 +93,8 @@ 93 93 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm 94 94 * Tracking: max: 38mA 95 95 100 + 101 + 96 96 == 1.3 Features == 97 97 98 98 ... ... @@ -111,6 +111,8 @@ 111 111 * Tri-color LED, Alarm button 112 112 * Datalog 113 113 120 + 121 + 114 114 == 1.4 Applications == 115 115 116 116 ... ... @@ -117,8 +117,11 @@ 117 117 * Logistics and Supply Chain Management 118 118 * Human tracking 119 119 128 + 129 + 120 120 = 2. Use TrackerD = 121 121 132 + 122 122 == 2.1 How it works? == 123 123 124 124 ... ... @@ -125,6 +125,7 @@ 125 125 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. 126 126 127 127 139 + 128 128 == 2.2 Quick guide to connect to LoRaWAN server == 129 129 130 130 ... ... @@ -131,7 +131,7 @@ 131 131 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. 132 132 133 133 134 -[[image:1664501652064-326.png ||_mstalt="293306"]]146 +[[image:1664501652064-326.png]] 135 135 136 136 137 137 ... ... @@ -143,7 +143,7 @@ 143 143 Each TrackerD is shipped with a sticker with the default device EUI as below: 144 144 145 145 146 -[[image:1664501677253-891.png ||_mstalt="296569"]]158 +[[image:1664501677253-891.png]] 147 147 148 148 149 149 Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot: ... ... @@ -152,14 +152,14 @@ 152 152 **__Add APP EUI in the application:__** 153 153 154 154 155 -[[image:1664501711466-918.png ||_mstalt="295828"]]167 +[[image:1664501711466-918.png]] 156 156 157 157 158 158 159 -[[image:1664501721248-725.png ||_mstalt="294450"]]171 +[[image:1664501721248-725.png]] 160 160 161 161 162 -[[image:1664501734705-405.png ||_mstalt="293306"]]174 +[[image:1664501734705-405.png]] 163 163 164 164 165 165 ... ... @@ -166,20 +166,18 @@ 166 166 **__Add APP KEY and DEV EUI:__** 167 167 168 168 169 -[[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"]]181 +[[image:1664501784668-703.png]] 170 170 171 171 172 172 173 -(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device. 174 174 175 -(% id="cke_bm_7709S"style="display:none" %)[[image:1664502835802-546.png||_mstalt="295061"]]186 +(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch. 176 176 177 -[[image:1664502835802-546.png||_mstalt="295061"]] 178 178 179 - 180 180 (% 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. 181 181 182 182 192 + 183 183 == 2.3 Positioning Mode(SMOD) == 184 184 185 185 ... ... @@ -192,8 +192,10 @@ 192 192 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 193 193 194 194 205 + 195 195 == 2.4 Uplink Payload == 196 196 208 + 197 197 === 2.4.1 Uplink FPORT~=5, Device Status === 198 198 199 199 ... ... @@ -206,7 +206,7 @@ 206 206 |=(% 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 207 207 |=(% 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 208 208 209 -[[image:1665301570342-765.png ||_mstalt="294580"]]221 +[[image:1665301570342-765.png]] 210 210 211 211 212 212 (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002 ... ... @@ -273,7 +273,7 @@ 273 273 274 274 (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 275 275 276 -(% _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)(%%)288 +(% style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%) 277 277 278 278 279 279 (% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 ... ... @@ -282,6 +282,8 @@ 282 282 |=(% 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 283 283 |=(% 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"]] 284 284 297 + 298 + 285 285 === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 286 286 287 287 ... ... @@ -300,7 +300,7 @@ 300 300 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 301 301 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 302 302 303 -[[image:1665301636888-168.png ||_mstalt="298012"]]317 +[[image:1665301636888-168.png]] 304 304 305 305 306 306 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== ... ... @@ -330,12 +330,12 @@ 330 330 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: 331 331 332 332 333 -[[image:1664502116362-706.png ||_mstalt="293306"]]347 +[[image:1664502116362-706.png]] 334 334 335 335 336 336 3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 337 337 338 -[[image:1664502166010-515.png ||_mstalt="291395"]]352 +[[image:1664502166010-515.png]] 339 339 340 340 341 341 ... ... @@ -358,6 +358,8 @@ 358 358 * 3.40v ~~ 3.69v: 20% ~~ 40% 359 359 * < 3.39v: 0~~20% 360 360 375 + 376 + 361 361 ==== (% style="color:blue" %)**MOD:**(%%) ==== 362 362 363 363 **Example: ** (0x60>>6) & 0x3f =1 ... ... @@ -398,6 +398,7 @@ 398 398 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree// 399 399 400 400 417 + 401 401 === 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) === 402 402 403 403 ... ... @@ -413,13 +413,14 @@ 413 413 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 414 414 415 415 (% class="wikigeneratedid" %) 416 -[[image:1665301687277-443.png ||_mstalt="296140"]]433 +[[image:1665301687277-443.png]] 417 417 418 418 436 + 419 419 === 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 420 420 421 421 422 -Set [[PNACKMD=1>>||anchor="H3.2.1 1A0AutoSendNone-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.440 +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. 423 423 424 424 425 425 (% style="color:red" %)**Note for this mode:** ... ... @@ -436,9 +436,10 @@ 436 436 )))|4|4|2|1|1|1|1|1 437 437 |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 438 438 439 -[[image:image-20221009160309-2.png ||_mstalt="429312"]]457 +[[image:image-20221009160309-2.png]] 440 440 441 441 460 + 442 442 === 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 443 443 444 444 ... ... @@ -463,7 +463,7 @@ 463 463 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 464 464 )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 465 465 466 -[[image:1664502425687-834.png ||_mstalt="296738"]]485 +[[image:1664502425687-834.png]] 467 467 468 468 469 469 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). ... ... @@ -470,16 +470,18 @@ 470 470 * (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 471 471 * (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 472 472 * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. 473 -* (% style="color:#037691" %)**MINOR:** (%%)The M INOR492 +* (% style="color:#037691" %)**MINOR:** (%%)The MAJOR from the strongest iBeacon. 474 474 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 475 475 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 476 476 477 -=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 478 478 479 479 480 - TrackerDsupportsWiFi scansforindoor positioning.User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]]to **WiFi** so TrackerDwill scan WiFi and findthestrongest WiFiinfoand uplink.498 +=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID === 481 481 482 482 501 +TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan WiFi and find the strongest WiFi info and uplink. 502 + 503 + 483 483 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %) 484 484 |=(% scope="row" style="width: 60px;" %)((( 485 485 **Size(bytes)** ... ... @@ -489,7 +489,7 @@ 489 489 )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 490 490 491 491 (% class="wikigeneratedid" %) 492 -[[image:1667288597595-714.png|| _mstalt="299598"height="212" width="1151"]]513 +[[image:1667288597595-714.png||height="212" width="1151"]] 493 493 494 494 495 495 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). ... ... @@ -496,6 +496,8 @@ 496 496 * (% style="color:#037691" %)**SSID: **(%%)WiFi name. 497 497 * (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 498 498 520 + 521 + 499 499 === 2.4.7 Add Payload format in TTN V3 === 500 500 501 501 ... ... @@ -504,10 +504,9 @@ 504 504 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 505 505 506 506 507 -[[image:1664502649601-895.png ||_mstalt="296985"]]530 +[[image:1664502649601-895.png]] 508 508 509 509 510 - 511 511 Add the decoder from this link: 512 512 513 513 [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] ... ... @@ -514,9 +514,10 @@ 514 514 515 515 Save the change the uplink message will be parsed. As below: 516 516 517 -[[image:1664502676891-606.png ||_mstalt="296673"]]539 +[[image:1664502676891-606.png]] 518 518 519 519 542 + 520 520 == 2.5 Integrate with Datacake == 521 521 522 522 ... ... @@ -524,8 +524,8 @@ 524 524 525 525 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]] 526 526 550 +[[image:1664502695771-538.png]] 527 527 528 -[[image:1664502695771-538.png||_mstalt="297349"]] 529 529 530 530 531 531 == 2.6 Integrate with Tago == ... ... @@ -536,24 +536,27 @@ 536 536 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]] 537 537 538 538 539 -[[image:1664502715371-321.png||_mstalt="292162"]] 540 540 563 +[[image:1664502715371-321.png]] 541 541 565 + 566 + 542 542 == 2.7 Datalog Feature == 543 543 544 544 545 545 total 273 entries,by default, 546 546 547 -User can set [[PNACKMD=1>>||anchor="H3.2.1 1A0AutoSendNone-ACKmessages"]], to enable Datalog feature.572 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 548 548 549 549 Example use case. 550 550 551 -[[image:image-20221009234703-2.png|| _mstalt="429143"height="328" width="899"]]576 +[[image:image-20221009234703-2.png||height="328" width="899"]] 552 552 553 553 554 -[[image:image-20221009234629-1.png|| _mstalt="431145"height="390" width="577"]]579 +[[image:image-20221009234629-1.png||height="390" width="577"]] 555 555 556 556 582 + 557 557 == 2.8 Alarm Mode == 558 558 559 559 ... ... @@ -568,7 +568,7 @@ 568 568 569 569 570 570 ((( 571 - **Two ways to exit alarm mode:**597 +Two ways to exit alarm mode: 572 572 ))) 573 573 574 574 * Server sends a downlink command to exit. ... ... @@ -579,25 +579,24 @@ 579 579 ))) 580 580 581 581 608 + 582 582 == 2.9 Transport Mode == 583 583 584 584 585 585 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. 586 586 587 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation. 588 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic. 589 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion. 590 590 615 + 591 591 == 2.10 LED Status == 592 592 593 593 594 -(% border="1.5" style="background-color:#ffffcc; width:500px" %) 619 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 595 595 |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 596 596 |(% style="width:157px" %)**Power On**|(% style="width:271px" %)(% style="color:blue" %)**BLUE, **(% style="color:red" %)**RED , **(% style="color:green" %)**Green** flash once|(% style="width:202px" %)N/A 597 597 |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes 598 598 |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A 599 599 |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes 600 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes 625 +|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes 601 601 |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes 602 602 |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes 603 603 |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes ... ... @@ -605,12 +605,14 @@ 605 605 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 606 606 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 607 607 633 + 634 + 608 608 == 2.11 Button Function == 609 609 610 610 611 611 (% style="color:blue" %)**RESET button:** 612 612 613 -[[image:1664502835802-546.png ||_mstalt="295061"]]640 +[[image:1664502835802-546.png]] 614 614 615 615 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server. 616 616 ... ... @@ -617,15 +617,17 @@ 617 617 618 618 (% style="color:red" %)**RED button:** 619 619 620 -[[image:1664502854406-763.png ||_mstalt="295568"]]647 +[[image:1664502854406-763.png]] 621 621 622 622 623 -(% border="1" style="background-color:#ffffcc; width:510px" %) 650 +(% border="1" style="background-color:#ffffcc; color:green; width:510px" %) 624 624 |=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description** 625 -|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode. See [[Alarm Mode>>||anchor="H2. 8AlarmMode"]]652 +|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode. See [[Alarm Mode>>||anchor="H2.6AlarmMode"]] 626 626 |(% 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 627 627 |(% 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. 628 628 656 + 657 + 629 629 == 2.12 USB Port Function == 630 630 631 631 ... ... @@ -636,6 +636,8 @@ 636 636 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 637 637 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 638 638 668 + 669 + 639 639 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 640 640 641 641 ... ... @@ -644,6 +644,7 @@ 644 644 LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] 645 645 646 646 678 + 647 647 == 3.1 Access AT Command == 648 648 649 649 ... ... @@ -650,23 +650,25 @@ 650 650 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. 651 651 652 652 653 -[[image:1664502999401-486.png ||_mstalt="296985"]]685 +[[image:1664502999401-486.png]] 654 654 655 655 656 656 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: 657 657 658 658 659 -[[image:1664503022490-662.png ||_mstalt="293332"]]691 +[[image:1664503022490-662.png]] 660 660 661 661 662 -[[image:1664503035713-500.png ||_mstalt="291096"]]694 +[[image:1664503035713-500.png]] 663 663 664 664 665 -[[image:1664503047675-651.png ||_mstalt="295386"]]697 +[[image:1664503047675-651.png]] 666 666 667 667 700 + 668 668 == 3.2 Command Set == 669 669 703 + 670 670 === 3.2.1 Set Transmit Interval === 671 671 672 672 ... ... @@ -684,6 +684,7 @@ 684 684 (% style="color:#037691" %)**0x01 00 01 2C** (%%) ~/~/ Same as AT+TDC=300000 685 685 686 686 721 + 687 687 === 3.2.2 Set Alarm Packet transmission interval === 688 688 689 689 ... ... @@ -701,6 +701,7 @@ 701 701 (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/ Same as AT+ATDC=60000 702 702 703 703 739 + 704 704 === 3.2.3 Set Transport Mode Packet transmission interval === 705 705 706 706 ... ... @@ -715,9 +715,10 @@ 715 715 716 716 * (% style="color:blue" %)**Downlink Payload (prefix 0x03):** 717 717 718 -(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+MTDC=3000000 754 +(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+ MTDC=3000000 719 719 720 720 757 + 721 721 === 3.2.4 Exit Alarm === 722 722 723 723 ... ... @@ -730,6 +730,7 @@ 730 730 (% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 731 731 732 732 770 + 733 733 === 3.2.5 Disable/Enable LED flash === 734 734 735 735 ... ... @@ -747,6 +747,7 @@ 747 747 (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/ Same as AT+LON=0 748 748 749 749 788 + 750 750 === 3.2.6 Disable/Enable Transport Mode === 751 751 752 752 ... ... @@ -756,14 +756,15 @@ 756 756 757 757 (% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)** 758 758 759 -Example: AT+INTWK=1 **~-~-> ** Enable Transport Mode. 798 +Example: AT+ INTWK =1 **~-~-> ** Enable Transport Mode. 760 760 761 761 762 762 * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):** 763 763 764 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+INTWK=1 803 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+ INTWK =1 765 765 766 766 806 + 767 767 === 3.2.7 Set Positioning Mode === 768 768 769 769 ... ... @@ -777,39 +777,33 @@ 777 777 (% style="color:#037691" %)** aa:** 778 778 779 779 * (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 780 - 781 781 * (% style="color:red" %)**2: BLE or WiFi ONLY: **(%%)Only obtain iBeacon info via BLE and uplink or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking. 821 +* (% style="color:red" %)**3: GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 782 782 783 -* (% style="color:red" %)**3: GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 784 - 785 785 (% style="color:#037691" %)**bb:** 786 786 787 787 * (% style="color:red" %)**0 : **(%%)GPS+ BAT+ State+Tem&Hum 788 - 789 789 * (% style="color:red" %)**1 :**(%%) GPS +BAT State 790 790 791 791 (% style="color:#037691" %)**cc: ** 792 792 793 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 794 - 795 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%)) 830 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 831 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%)) 796 796 797 797 (% style="color:blue" %)**Example:** 798 798 799 - AT+SMOD=1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 835 + AT+ SMOD =1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 836 + AT+ SMOD =1,1,0 ~-~-> GPS +BAT State 837 + AT+ SMOD =2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 838 + AT+ SMOD =2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State 800 800 801 - AT+SMOD=1,1,0 ~-~-> GPS +BAT State 802 802 803 - AT+SMOD=2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 804 - 805 - AT+SMOD=2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State 806 - 807 - 808 808 * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** 809 809 810 -(% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+SMOD=1,0,0 843 +(% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+ SMOD =1,0,0 811 811 812 812 846 + 813 813 === 3.2.8 Set MAX GPS position time === 814 814 815 815 ... ... @@ -816,7 +816,7 @@ 816 816 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. 817 817 818 818 819 -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.853 +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. 820 820 821 821 822 822 * (% style="color:blue" %)**AT Command:** ... ... @@ -831,6 +831,7 @@ 831 831 (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/ Set AT+FTIME=150 832 832 833 833 868 + 834 834 === 3.2.9 Set PDOP value for GPS fix accuracy === 835 835 836 836 ... ... @@ -854,8 +854,8 @@ 854 854 (% style="color:#037691" %)**0xAD 00 46** (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7) 855 855 856 856 857 -=== 3.2.10 Disable/Enable the confirmation mode === 858 858 893 +Disable/Enable the confirmation mode 859 859 860 860 * (% style="color:blue" %)**AT Command:** 861 861 ... ... @@ -864,19 +864,20 @@ 864 864 865 865 **~ Example:** 866 866 867 - AT+CFM=0 **~-~-> ** Disable confirmation 902 + AT+ CFM=0 **~-~-> ** Disable confirmation 868 868 869 - AT+CFM=1 **~-~-> ** Enable confirmation 904 + AT+ CFM=1 **~-~-> ** Enable confirmation 870 870 871 871 872 872 * (% style="color:blue" %)**Downlink Payload (prefix 0x05):** 873 873 874 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1 909 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+ CFM =1 875 875 876 876 877 -=== 3.2.11 Auto Send None-ACK messages === 878 878 913 +=== 3.2.10 Auto Send None-ACK messages === 879 879 915 + 880 880 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. 881 881 882 882 ... ... @@ -892,12 +892,13 @@ 892 892 893 893 * (% style="color:blue" %)**Downlink Command: 0x34** 894 894 895 -Example: 0x34 931 +Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 896 896 897 897 898 -=== 3.2.12 Set BLEMASK to filter BLE iBeacon === 899 899 935 +=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 900 900 937 + 901 901 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. 902 902 903 903 (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.** ... ... @@ -904,79 +904,61 @@ 904 904 905 905 (% style="color:blue" %)**AT Command:** 906 906 907 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456944 + (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 908 908 909 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK946 + (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 910 910 911 911 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 912 912 913 -Example: 0xB2 950 +Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 914 914 915 915 916 -=== 3.2.13 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 917 917 954 +=== 3.2.12 Set WiFIMASK to filter WiFi SSID === 918 918 919 -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. 920 920 957 +WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456. It will ignore all other WiFi which doesn’t contact 123456 in the SSID. 958 + 921 921 (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.** 922 922 923 923 (% style="color:blue" %)**AT Command:** 924 924 925 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456963 + (% style="color:#037691" %)**AT+ WiFiMASK =123456** (%%) ~/~/ Set WiFiMASK = 123456 926 926 927 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK965 + (% style="color:#037691" %)**AT+ WiFiMASK =0** (%%) ~/~/ disable WiFiMASK 928 928 929 929 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)** 930 930 931 -Example: 0xB3 969 +Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 932 932 933 933 934 -=== 3.2.14 Disable/Enable Information printing(Since firmware 1.4.1) === 935 935 973 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 936 936 975 + 937 937 Users can use this feature to enable/disable Information printing. 938 938 939 939 (% style="color:blue" %)**AT Command:** 940 940 941 -(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/ 942 -\\Example: AT+SHOWID=1 ~-~-> Enable Information printing. 980 +(% style="color:#037691" %)**AT+ SHOWID=XX **(%%) ~/~/(Disable (0), Enable (1), default:0) 981 +\\Example: AT+ SHOWID =1 ~-~-> Enable Information printing. 943 943 944 944 945 -=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 946 946 985 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 947 947 987 + 948 948 The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. 949 949 950 950 (% style="color:blue" %)**AT Command:** 951 951 952 -(% style="color:#037691" %)**AT+CHE=1 992 +(% style="color:#037691" %)**AT+ CHE=1**(%%) ~/~/ set one channels mode, 953 953 994 +(% style="color:blue" %)**Downlink Payload:0X24**(%%) 995 +Example: 0x24 01 ~/~/ Same as AT+ CHE= = 1 954 954 955 -(% style="color:blue" %)**Downlink Payload:0X24** 956 956 957 -Example: 0x24 01 ~/~/ Same as AT+CHE=1 958 958 959 - 960 -=== 3.2.16 Get or Set Threshold for motion detect(Since firmware 1.4.3) === 961 - 962 - 963 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event. 964 - 965 -(% style="color:blue" %)**AT Command:** 966 - 967 -(% style="color:#037691" %)**AT+PT=xx** 968 - 969 - Example: 970 - 971 - AT+PT=14 ~-~-> Set to detect car motion. 972 - 973 - AT+PT=41 ~-~-> set to detect walk motion. 974 - 975 - 976 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%) 977 -0xB4 14 ~/~/ Same as AT+PT=14 978 - 979 - 980 980 = 4. Setting for Different Scenarios = 981 981 982 982 ... ... @@ -983,6 +983,7 @@ 983 983 984 984 = 5. Upload Firmware = 985 985 1005 + 986 986 == 5.1 Firmware Change Log == 987 987 988 988 ... ... @@ -989,6 +989,7 @@ 989 989 **[[See this link>>url:https://github.com/dragino/TrackerD]]** 990 990 991 991 1012 + 992 992 == 5.2 How to upgrade firmware == 993 993 994 994 ... ... @@ -1009,10 +1009,10 @@ 1009 1009 (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32 1010 1010 1011 1011 1012 -[[image:1664503563660-578.png ||_mstalt="296777"]]1033 +[[image:1664503563660-578.png]] 1013 1013 1014 1014 1015 -[[image:1664503574618-659.png ||_mstalt="297986"]]1036 +[[image:1664503574618-659.png]] 1016 1016 1017 1017 1018 1018 ... ... @@ -1021,26 +1021,29 @@ 1021 1021 [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]] 1022 1022 1023 1023 1024 - **Users need to use below files:**1045 +Users need to use below files: 1025 1025 1026 1026 boot_app0.bin @0e000 1027 1027 1028 - US915.bin @ 0x10000(Select the bin file of the frequency band you need)1049 +ESP_LORA-eeprom-class.bin @ 0x10000 1029 1029 1030 1030 1031 -[[image: image-20221207120501-1.png]]1052 +[[image:1664503593459-435.png]] 1032 1032 1033 1033 1034 1034 1035 1035 After upgrade finish, it will show finish as below: 1036 1036 1037 -[[image: image-20221207133911-7.png]]1058 +[[image:1664503611848-385.png]] 1038 1038 1039 1039 1061 + 1040 1040 = 6. Developer Guide = 1041 1041 1064 + 1042 1042 == 6.1 Compile Source Code == 1043 1043 1067 + 1044 1044 === 6.1.1 Set up ARDUINO compile environment === 1045 1045 1046 1046 ... ... @@ -1049,71 +1049,24 @@ 1049 1049 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]] 1050 1050 1051 1051 1052 -[[image:1664503635019-941.png ||_mstalt="294658"]]1076 +[[image:1664503635019-941.png]] 1053 1053 1054 1054 1055 1055 1056 1056 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 1057 1057 1058 -[[image:1664503715811-892.png ||_mstalt="295698"]]1082 +[[image:1664503715811-892.png]] 1059 1059 1060 1060 1061 -=== 6.1.2 Build the development environment === 1062 - 1063 -~1. Download and install arduino IDE 1064 - 1065 -[[https:~~/~~/www.arduino.cn/thread-5838-1-1.html>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fwww.arduino.cn%2Fthread-5838-1-1.html]] 1066 - 1067 - 1068 -2. Download the ESP32 development package in the arduino IDE 1069 - 1070 -[[image:image-20221213100007-1.png]] 1071 - 1072 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]] 1073 - 1074 -[[image:image-20221213100626-2.png]] 1075 - 1076 -Restart the IDE after the addition is complete, then: 1077 - 1078 -[[image:image-20221213100808-3.png||height="679" width="649"]] 1079 - 1080 -[[image:image-20221213101040-4.png]] 1081 - 1082 -**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03. 1083 -Don't quit halfway.~~! If you quit halfway, there is a high probability that it will freeze, and you will need to download again next time. (If you click to continue downloading, an error will be reported after completion)** 1084 - 1085 -Then enter a long waiting process. If you don't want to wait, you can go to the Internet to download directly, and then import: 1086 - 1087 -Methods as below: 1088 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]] 1089 - 1090 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here. 1091 - 1092 1092 (% 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. 1093 1093 1094 -[[image:image-2022121 3102311-5.png||height="582" width="711"]]1087 +[[image:image-20221024105643-1.png]] 1095 1095 1096 -3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion) 1097 - 1098 -[[image:image-20221213102334-6.png]] 1099 - 1100 -**Note: This step requires a python environment** 1101 - 1102 -Either way, in the end: 1103 -The final effect is to open the arduino and you can see the esp32 1104 - 1105 -[[image:image-20221213102718-7.png||height="1053" width="803"]] 1106 - 1107 - 1108 - 1109 -[[image:image-20221024105643-1.png||_mstalt="428129"]] 1110 - 1111 1111 **~ Figure1** 1112 1112 1113 1113 1092 +[[image:image-20221024105643-2.png]] 1114 1114 1115 -[[image:image-20221024105643-2.png||_mstalt="428493"]] 1116 - 1117 1117 **Figure2** 1118 1118 1119 1119 ... ... @@ -1122,31 +1122,34 @@ 1122 1122 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: 1123 1123 1124 1124 1125 -[[image:1664503752288-974.png ||_mstalt="298194"]]1102 +[[image:1664503752288-974.png]] 1126 1126 1127 1127 1105 + 1128 1128 == 6.2 Source Code == 1129 1129 1130 1130 1131 1131 * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:** 1132 1132 1133 -[[image:1664503794261-827.png ||_mstalt="296387"]]1111 +[[image:1664503794261-827.png]] 1134 1134 1135 1135 1136 1136 1137 1137 * (% style="color:blue" %)**Click to upload** 1138 1138 1139 -[[image:1664503808294-336.png ||_mstalt="295711"]]1117 +[[image:1664503808294-336.png]] 1140 1140 1141 1141 1142 1142 1143 1143 * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 1144 1144 1145 -[[image:1664503824081-592.png ||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]1123 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 1146 1146 1147 1147 1126 + 1148 1148 = 7. FAQ = 1149 1149 1129 + 1150 1150 == 7.1 How to change the LoRa Frequency Bands/Region? == 1151 1151 1152 1152 ... ... @@ -1153,10 +1153,11 @@ 1153 1153 User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download. 1154 1154 1155 1155 1136 + 1156 1156 == 7.2 What is the pin mapping for the USB program cable? == 1157 1157 1158 1158 1159 -[[image:1664499635206-262.png ||_mstalt="295360"]]1140 +[[image:1664499635206-262.png]] 1160 1160 1161 1161 1162 1162 ... ... @@ -1171,293 +1171,109 @@ 1171 1171 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 1172 1172 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 1173 1173 1155 + 1156 + 1174 1174 == 7.3 Notes on using different serial port tools for TrackerD == 1175 1175 1176 -=== 7.3.1 Serial port utility === 1177 1177 1160 +=== **Serial port utility** === 1178 1178 1162 + 1179 1179 Serial port utility requires you to automatically add data streams. 1180 1180 1181 1181 Need to adjust the data stream to RTS/CTS on physical restart. 1182 1182 1167 + 1183 1183 (% class="wikigeneratedid" %) 1184 -[[image:image-20221102140621-1.png ||_mstalt="425672"]]1169 +[[image:image-20221102140621-1.png]] 1185 1185 1186 1186 1187 - 1188 1188 When using AT commands, the data flow needs to be adjusted to XON/XOFF 1189 1189 1190 -[[image:image-20221102140638-2.png||_mstalt="428727"]] 1191 1191 1175 +[[image:image-20221102140638-2.png]] 1192 1192 1193 -=== 7.3.2 SecureCRT === 1194 1194 1195 1195 1196 - Thedefault command window ofSecureCRTis not displayed. Entering a command requires a complete input of the entire command. You can open the command window in the view.1179 +=== **SecureCRT** === 1197 1197 1198 1198 1199 - [[image:image-20221102140704-3.png||_mstalt="427076"]]1182 +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. 1200 1200 1201 1201 1202 -[[image:image-202211021407 12-4.png||_mstalt="427089"]]1185 +[[image:image-20221102140704-3.png]] 1203 1203 1204 1204 1205 - ===7.3.3 PUTTY ===1188 +[[image:image-20221102140712-4.png]] 1206 1206 1207 1207 1208 -[[image:image-20221102140748-5.png||_mstalt="430456"]] 1209 1209 1192 +=== **PUTTY** === 1210 1210 1211 -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. 1212 1212 1195 +[[image:image-20221102140748-5.png]] 1213 1213 1214 -[[image:image-20221102140801-6.png||_mstalt="427466"]] 1215 1215 1198 +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. 1216 1216 1217 -== 7.4 How to modify source code to compile different frequency band bin file? == 1218 1218 1201 +[[image:image-20221102140801-6.png]] 1219 1219 1220 -(% class="box infomessage" %) 1221 -((( 1222 -(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings. 1223 -See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]] 1224 -))) 1225 1225 1226 - **~1.Whencompiling thefrequencyband, youneedtofindLMIC_PROJECT_CONFIG.H file.**1204 +== 7.4 TrackerD trouble shooting == 1227 1227 1228 1228 1229 - [[image:image-20221116111844-1.png||_mstalt="428688"height="227"width="782"]]1207 +V1.4.0: When the motion mode is turned on, the TDC needs to be greater than MTDC, otherwise TDC time will be confused 1230 1230 1231 1231 1232 1232 1233 - **2.Open LMIC_PROJECT_CONFIG.H,findthecorrespondingmacro definitionand open it(AS923_2,AS923_3,AS923_4 except).**1211 += 8. Order Info = 1234 1234 1235 1235 1236 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]] 1237 - 1238 - 1239 - 1240 -**3. Compile the AS923_JP band, please refer to the intention shown** 1241 - 1242 - 1243 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]] 1244 - 1245 - 1246 - 1247 -**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.** 1248 - 1249 - 1250 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]] 1251 - 1252 - 1253 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]] 1254 - 1255 - 1256 -= 8 Trouble Shooting = 1257 - 1258 -== 8.1 TDC is changed to 4294947296 and cause no uplink. == 1259 - 1260 - 1261 -((( 1262 -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 1263 -))) 1264 - 1265 - 1266 -== 8.2 Device not able get AT Command or show output after wake up from deep sleep mode == 1267 - 1268 - 1269 -((( 1270 -ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode. 1271 -))) 1272 - 1273 - 1274 -== 8.3 Problem after Upgrading Firmware == 1275 - 1276 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading === 1277 - 1278 - 1279 -**Error Output** 1280 - 1281 - 1282 -[[image:image-20221122100004-4.png||_mstalt="424606"]] 1283 - 1284 - 1285 -((( 1286 -Some partition is missed during upgrade, please upgrade below four files as example: 1287 - 1288 -[[image:image-20221207120524-2.png]] 1289 -))) 1290 - 1291 - 1292 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1293 - 1294 - 1295 -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 1296 - 1297 - 1298 -=== 8.3.3 "flash read err" after upgrade firmware === 1299 - 1300 - 1301 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue. 1302 - 1303 - 1304 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]] 1305 - 1306 - 1307 -User need to upgrade again with below four files to solve this issue. 1308 - 1309 - [[image:image-20221207120530-3.png]] 1310 - 1311 - **Figure 2** 1312 - 1313 - 1314 -=== 8.3.4 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware === 1315 - 1316 - 1317 -User might erase the entire flash include keys and default settings which cause this issue. 1318 - 1319 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below. 1320 - 1321 - 1322 -[[image:image-20221122100004-3.png||_mstalt="424242"]] 1323 - 1324 - 1325 -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. 1326 - 1327 -After AT+FDR. please set 1328 - 1329 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7** 1330 - 1331 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000** 1332 - 1333 -**Example:** 1334 - 1335 -AT+PDOP=7.00 1336 - 1337 -AT+FTIME=180 1338 - 1339 -AT+DEUI=70B3D57ED0053981 1340 - 1341 -AT+APPEUI=D23345667BCBCCAF 1342 - 1343 -AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1 1344 - 1345 -AT+DADDR=260b4dce ( no need for OTAA) 1346 - 1347 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d ( no need for OTAA) 1348 - 1349 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA) 1350 - 1351 - 1352 -== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1353 - 1354 - 1355 -Please download version 1.4.2 again 1356 - 1357 - 1358 -== 8.5 How to deal with unsuccessful GPS positioning? == 1359 - 1360 - 1361 -1) Make Sure the device is in Open Area where can see the sky. 1362 - 1363 -2) Set PDOP to a higher value. 1364 - 1365 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.) 1366 - 1367 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces) 1368 - 1369 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments) 1370 - 1371 -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 1372 - 1373 - 1374 -== 8.6 When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets == 1375 - 1376 - 1377 -When upgrading, use the erase button to upgrade 1378 - 1379 -[[image:image-20221207120536-4.png]] 1380 - 1381 - 1382 -The parameters are displayed abnormally and cannot be fixed using AT+FDR 1383 - 1384 -[[image:image-20221128103040-2.png||height="431" width="525"]] 1385 - 1386 - 1387 -Please upgrade these four files,link(The boot_app0 file is in the version folder you need) 1388 - 1389 -[[image:image-20221207134028-8.png]] 1390 - 1391 - 1392 -Reboot information after upgrade 1393 - 1394 -[[image:image-20221128111443-4.png||height="432" width="546"]] 1395 - 1396 - 1397 -Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal 1398 - 1399 -[[image:image-20221128111850-5.png]] 1400 - 1401 - 1402 -After the parameters return to normal, upgrade to the version you need again 1403 - 1404 -[[image:image-20221207120601-5.png]] 1405 - 1406 - 1407 -At this point, the parameters return to normal after running AT+FDR again 1408 - 1409 -[[image:image-20221128112035-7.png]] 1410 - 1411 - 1412 -= 9. Order Info = 1413 - 1414 - 1415 1415 Part Number: (% style="color:blue" %)**TrackerD-XXX** 1416 1416 1417 1417 (% style="color:blue" %)**XXX**(%%): The default frequency band 1418 1418 1419 1419 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433 1420 - 1421 1421 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868 1422 - 1423 1423 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865 1424 - 1425 1425 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920 1426 - 1427 1427 * (% style="color:red" %)**AS923**(%%): Default frequency band AS923 1428 - 1429 1429 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 1430 - 1431 1431 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1432 1432 1433 -= 10. Packing Info = 1434 1434 1435 1435 1228 += 9. Packing Info = 1229 + 1230 + 1436 1436 (% style="color:#037691" %)**Package Includes**: 1437 1437 1438 1438 * TrackerD LoRaWAN GPS/BLE Tracker x 1 1439 - 1440 1440 * USB recharge & program cable x 1 1441 1441 1442 1442 (% style="color:#037691" %)**Dimensions and Weight**: 1443 1443 1444 1444 * Device Size: 85 x 48 x 15 mm 1445 - 1446 1446 * Weight: 50g 1447 1447 1448 -= 11. Support = 1449 1449 1450 1450 1451 - *Support is provided Monday to Friday, from 09:00 to18:00 GMT+8.Dueto different timezones we cannot offer live support.However, your questions will be answered as soon as possible in the before-mentioned schedule.1243 += 10. Support = 1452 1452 1245 + 1246 +* 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. 1453 1453 * 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]]. 1454 1454 1455 -= 12. Reference = 1456 1456 1457 1457 1458 - *[[**Firmwarein Binformat**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]1251 += 11. Reference = 1459 1459 1460 -* **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1461 1461 1254 +* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1255 +* **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1462 1462 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 1463 -))) 1257 + 1258 + 1259 + 1260 +
- image-20221107145243-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -107.3 KB - Content
- image-20221116111844-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -15.8 KB - Content
- image-20221116111844-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -32.6 KB - Content
- image-20221116111844-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -37.0 KB - Content
- image-20221116111844-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -96.8 KB - Content
- image-20221116111844-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -78.0 KB - Content
- image-20221118104359-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -38.0 KB - Content
- image-20221118105220-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -40.2 KB - Content
- image-20221118105249-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -40.2 KB - Content
- image-20221118105402-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -43.7 KB - Content
- image-20221122100004-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -18.0 KB - Content
- image-20221122100004-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -127.2 KB - Content
- image-20221122100004-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -12.5 KB - Content
- image-20221122100004-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -22.3 KB - Content
- 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
- image-20221213100626-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -35.7 KB - Content
- image-20221213100808-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -91.3 KB - Content
- image-20221213101040-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -26.3 KB - Content
- image-20221213102311-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -49.7 KB - Content
- image-20221213102334-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -52.5 KB - Content
- image-20221213102718-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -116.5 KB - Content