Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)
Last modified by Xiaoling on 2023/12/27 09:15
From version 192.2
edited by Xiaoling
on 2023/03/02 08:53
on 2023/03/02 08:53
Change comment:
There is no comment for this version
To version 145.1
edited by Edwin Chen
on 2022/11/22 12:21
on 2022/11/22 12:21
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 26 removed)
- 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
- image-20221213110952-8.png
- image-20230213110119-1.png
- image-20230213110214-2.png
- image-20230213110506-3.png
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Edwin - 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,7 +12,6 @@ 12 12 13 13 14 14 15 - 16 16 = 1. Introduction = 17 17 18 18 == 1.1 What is TrackerD == ... ... @@ -32,12 +32,15 @@ 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 ))) 34 +))) 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. 38 + 39 + 38 38 ))) 39 39 40 -[[image: image-20230213110119-1.png||height="382" width="834"]]42 +[[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.** ... ... @@ -93,8 +93,6 @@ 93 93 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm 94 94 * Tracking: max: 38mA 95 95 96 - 97 - 98 98 == 1.3 Features == 99 99 100 100 ... ... @@ -113,8 +113,6 @@ 113 113 * Tri-color LED, Alarm button 114 114 * Datalog 115 115 116 - 117 - 118 118 == 1.4 Applications == 119 119 120 120 ... ... @@ -121,8 +121,6 @@ 121 121 * Logistics and Supply Chain Management 122 122 * Human tracking 123 123 124 - 125 - 126 126 = 2. Use TrackerD = 127 127 128 128 == 2.1 How it works? == ... ... @@ -137,7 +137,7 @@ 137 137 Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example. 138 138 139 139 140 -[[image: image-20230213110214-2.png||height="388" width="847"]]136 +[[image:1664501652064-326.png]] 141 141 142 142 143 143 ... ... @@ -149,7 +149,7 @@ 149 149 Each TrackerD is shipped with a sticker with the default device EUI as below: 150 150 151 151 152 -[[image:1664501677253-891.png ||_mstalt="296569"]]148 +[[image:1664501677253-891.png]] 153 153 154 154 155 155 Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot: ... ... @@ -158,14 +158,14 @@ 158 158 **__Add APP EUI in the application:__** 159 159 160 160 161 -[[image:1664501711466-918.png ||_mstalt="295828"]]157 +[[image:1664501711466-918.png]] 162 162 163 163 164 164 165 -[[image:1664501721248-725.png ||_mstalt="294450"]]161 +[[image:1664501721248-725.png]] 166 166 167 167 168 -[[image:1664501734705-405.png ||_mstalt="293306"]]164 +[[image:1664501734705-405.png]] 169 169 170 170 171 171 ... ... @@ -172,15 +172,15 @@ 172 172 **__Add APP KEY and DEV EUI:__** 173 173 174 174 175 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1|| _mstalt="298233" alt="1654671889112-678.png"]]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||alt="1654671889112-678.png"]] 176 176 177 177 178 178 179 179 (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device. 180 180 181 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png ||_mstalt="295061"]]177 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]] 182 182 183 -[[image:1664502835802-546.png ||_mstalt="295061"]]179 +[[image:1664502835802-546.png]] 184 184 185 185 186 186 (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server. ... ... @@ -209,10 +209,10 @@ 209 209 210 210 211 211 (% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %) 212 -|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %) 1|=(% style="width: 40px;" %)1208 +|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1 213 213 |=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status 214 214 215 -[[image:1665301570342-765.png ||_mstalt="294580"]]211 +[[image:1665301570342-765.png]] 216 216 217 217 218 218 (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002 ... ... @@ -256,7 +256,7 @@ 256 256 (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40 257 257 258 258 (% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %) 259 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %) 1bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit255 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit 260 260 |=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings 261 261 262 262 (% style="color:blue" %)** SMOD:** ... ... @@ -279,17 +279,15 @@ 279 279 280 280 (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 281 281 282 -(% _mstmutation="1" style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(%_mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)278 +(% style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%) 283 283 284 284 285 285 (% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 286 286 287 -(% border="1.5" style="background-color:#ffffcc; color:green; width: 412.222px" %)288 -|=(% scope="row" style="width: 75px;" %)**Size(bit)**|(% style="width:68px" %)5 Bits|(% style="width:87px" %)1 Bit|(% style="width:49px" %)1 Bit|(% style="width:126px" %)1 Bit289 -|=(% style="width: 7 5px;" %)**Value**|(% style="width:68px" %)Reserve|(% style="width:87px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:49px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]283 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %) 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 +|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]] 290 290 291 - 292 - 293 293 === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 294 294 295 295 ... ... @@ -308,20 +308,20 @@ 308 308 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 309 309 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 310 310 311 -[[image:1665301636888-168.png ||_mstalt="298012"]]305 +[[image:1665301636888-168.png]] 312 312 313 313 314 314 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== 315 315 316 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:2 79.222px" %)317 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width: 69px" %)163px" %)14318 -|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width: 69px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]]310 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 311 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits 312 +|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 319 319 320 320 ==== (% style="color:blue" %)**FLAG:**(%%) ==== 321 321 322 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:1 83.222px" %)323 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2 52px" %)1324 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width: 52px" %)[[LON>>||anchor="HLON:"]]316 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %) 317 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit 318 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] 325 325 326 326 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 327 327 ... ... @@ -331,7 +331,6 @@ 331 331 * Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976// 332 332 * Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 333 333 334 - 335 335 (% style="color:red" %)**Important note:** 336 336 337 337 1. When power is low (<2.84v), GPS won't be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF. ... ... @@ -339,12 +339,12 @@ 339 339 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: 340 340 341 341 342 -[[image:1664502116362-706.png ||_mstalt="293306"]]335 +[[image:1664502116362-706.png]] 343 343 344 344 345 345 3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 346 346 347 -[[image:1664502166010-515.png ||_mstalt="291395"]]340 +[[image:1664502166010-515.png]] 348 348 349 349 350 350 ... ... @@ -367,9 +367,6 @@ 367 367 * 3.40v ~~ 3.69v: 20% ~~ 40% 368 368 * < 3.39v: 0~~20% 369 369 370 -(% style="display:none" %) (%%) 371 - 372 - 373 373 ==== (% style="color:blue" %)**MOD:**(%%) ==== 374 374 375 375 **Example: ** (0x60>>6) & 0x3f =1 ... ... @@ -425,13 +425,13 @@ 425 425 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 426 426 427 427 (% class="wikigeneratedid" %) 428 -[[image:1665301687277-443.png ||_mstalt="296140"]]418 +[[image:1665301687277-443.png]] 429 429 430 430 431 431 === 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 432 432 433 433 434 -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.424 +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. 435 435 436 436 437 437 (% style="color:red" %)**Note for this mode:** ... ... @@ -448,7 +448,7 @@ 448 448 )))|4|4|2|1|1|1|1|1 449 449 |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 450 450 451 -[[image:image-20221009160309-2.png ||_mstalt="429312"]]441 +[[image:image-20221009160309-2.png]] 452 452 453 453 454 454 === 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === ... ... @@ -475,7 +475,7 @@ 475 475 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 476 476 )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 477 477 478 -[[image:1664502425687-834.png ||_mstalt="296738"]]468 +[[image:1664502425687-834.png]] 479 479 480 480 481 481 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). ... ... @@ -486,9 +486,6 @@ 486 486 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 487 487 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 488 488 489 -(% style="display:none" %) (%%) 490 - 491 - 492 492 === 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 493 493 494 494 ... ... @@ -504,7 +504,7 @@ 504 504 )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 505 505 506 506 (% class="wikigeneratedid" %) 507 -[[image:1667288597595-714.png|| _mstalt="299598"height="212" width="1151"]]494 +[[image:1667288597595-714.png||height="212" width="1151"]] 508 508 509 509 510 510 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). ... ... @@ -511,9 +511,6 @@ 511 511 * (% style="color:#037691" %)**SSID: **(%%)WiFi name. 512 512 * (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 513 513 514 -(% style="display:none" %) (%%) 515 - 516 - 517 517 === 2.4.7 Add Payload format in TTN V3 === 518 518 519 519 ... ... @@ -522,7 +522,7 @@ 522 522 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 523 523 524 524 525 -[[image:1664502649601-895.png ||_mstalt="296985"]]509 +[[image:1664502649601-895.png]] 526 526 527 527 528 528 ... ... @@ -532,7 +532,7 @@ 532 532 533 533 Save the change the uplink message will be parsed. As below: 534 534 535 -[[image:1664502676891-606.png ||_mstalt="296673"]]519 +[[image:1664502676891-606.png]] 536 536 537 537 538 538 == 2.5 Integrate with Datacake == ... ... @@ -543,7 +543,7 @@ 543 543 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]] 544 544 545 545 546 -[[image:1664502695771-538.png ||_mstalt="297349"]]530 +[[image:1664502695771-538.png]] 547 547 548 548 549 549 == 2.6 Integrate with Tago == ... ... @@ -554,7 +554,7 @@ 554 554 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]] 555 555 556 556 557 -[[image:1664502715371-321.png ||_mstalt="292162"]]541 +[[image:1664502715371-321.png]] 558 558 559 559 560 560 == 2.7 Datalog Feature == ... ... @@ -562,14 +562,14 @@ 562 562 563 563 total 273 entries,by default, 564 564 565 -User can set [[PNACKMD=1>>||anchor="H3.2.1 1A0AutoSendNone-ACKmessages"]], to enable Datalog feature.549 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 566 566 567 567 Example use case. 568 568 569 -[[image:image-20221009234703-2.png|| _mstalt="429143"height="328" width="899"]]553 +[[image:image-20221009234703-2.png||height="328" width="899"]] 570 570 571 571 572 -[[image:image-20221009234629-1.png|| _mstalt="431145"height="390" width="577"]]556 +[[image:image-20221009234629-1.png||height="390" width="577"]] 573 573 574 574 575 575 == 2.8 Alarm Mode == ... ... @@ -602,13 +602,7 @@ 602 602 603 603 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. 604 604 605 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation. 606 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic. 607 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion. 608 608 609 -(% style="display:none" %) (%%) 610 - 611 - 612 612 == 2.10 LED Status == 613 613 614 614 ... ... @@ -626,15 +626,12 @@ 626 626 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 627 627 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 628 628 629 -(% style="display:none" %) (%%) 630 - 631 - 632 632 == 2.11 Button Function == 633 633 634 634 635 635 (% style="color:blue" %)**RESET button:** 636 636 637 -[[image:1664502835802-546.png ||_mstalt="295061"]]612 +[[image:1664502835802-546.png]] 638 638 639 639 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server. 640 640 ... ... @@ -641,9 +641,8 @@ 641 641 642 642 (% style="color:red" %)**RED button:** 643 643 644 -[[image: image-20230213110506-3.png]](% style="display:none" %)619 +[[image:1664502854406-763.png]] 645 645 646 -(% style="display:none" %) (%%) 647 647 648 648 (% border="1" style="background-color:#ffffcc; width:510px" %) 649 649 |=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description** ... ... @@ -651,9 +651,6 @@ 651 651 |(% 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 652 652 |(% 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. 653 653 654 -(% style="display:none" %) (%%) 655 - 656 - 657 657 == 2.12 USB Port Function == 658 658 659 659 ... ... @@ -664,9 +664,6 @@ 664 664 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 665 665 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 666 666 667 -(% style="display:none" %) (%%) 668 - 669 - 670 670 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 671 671 672 672 ... ... @@ -681,22 +681,22 @@ 681 681 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. 682 682 683 683 684 -[[image:1664502999401-486.png ||_mstalt="296985"]]652 +[[image:1664502999401-486.png]] 685 685 686 686 687 687 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: 688 688 689 689 690 -[[image:1664503022490-662.png ||_mstalt="293332"]]658 +[[image:1664503022490-662.png]] 691 691 692 692 693 -[[image:1664503035713-500.png ||_mstalt="291096"]]661 +[[image:1664503035713-500.png]] 694 694 695 695 696 -[[image:1664503047675-651.png ||_mstalt="295386"]]664 +[[image:1664503047675-651.png]] 697 697 698 -(% style="display:none" %) (%%) 699 699 667 + 700 700 == 3.2 Command Set == 701 701 702 702 === 3.2.1 Set Transmit Interval === ... ... @@ -762,7 +762,7 @@ 762 762 (% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 763 763 764 764 765 -=== 3.2.5 Disable/Enable LED flash and buzzer===733 +=== 3.2.5 Disable/Enable LED flash === 766 766 767 767 768 768 Disable/Enable LED for position, downlink and uplink ... ... @@ -822,9 +822,9 @@ 822 822 823 823 (% style="color:#037691" %)**cc: ** 824 824 825 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State793 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 826 826 827 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((%_mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))795 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%)) 828 828 829 829 (% style="color:blue" %)**Example:** 830 830 ... ... @@ -886,8 +886,8 @@ 886 886 (% style="color:#037691" %)**0xAD 00 46** (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7) 887 887 888 888 889 -=== 3.2.10 Disable/Enable the confirmation mode === 890 890 858 +**Disable/Enable the confirmation mode** 891 891 892 892 * (% style="color:blue" %)**AT Command:** 893 893 ... ... @@ -906,7 +906,7 @@ 906 906 (% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1 907 907 908 908 909 -=== 3.2.1 1877 +=== 3.2.10 Auto Send None-ACK messages === 910 910 911 911 912 912 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. ... ... @@ -924,10 +924,10 @@ 924 924 925 925 * (% style="color:blue" %)**Downlink Command: 0x34** 926 926 927 -Example: 0x34 895 +Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 928 928 929 929 930 -=== 3.2.1 2Set BLEMASK to filter BLE iBeacon ===898 +=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 931 931 932 932 933 933 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. ... ... @@ -936,16 +936,16 @@ 936 936 937 937 (% style="color:blue" %)**AT Command:** 938 938 939 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456907 + (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 940 940 941 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK909 + (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 942 942 943 943 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 944 944 945 -Example: 0xB2 913 +Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 946 946 947 947 948 -=== 3.2.1 3Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) ===916 +=== 3.2.12 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 949 949 950 950 951 951 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. ... ... @@ -954,16 +954,16 @@ 954 954 955 955 (% style="color:blue" %)**AT Command:** 956 956 957 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456925 + (% style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456 958 958 959 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK927 + (% style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK 960 960 961 961 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)** 962 962 963 -Example: 0xB3 931 +Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 964 964 965 965 966 -=== 3.2.1 4Disable/Enable Information printing(Since firmware 1.4.1) ===934 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 967 967 968 968 969 969 Users can use this feature to enable/disable Information printing. ... ... @@ -970,11 +970,11 @@ 970 970 971 971 (% style="color:blue" %)**AT Command:** 972 972 973 -(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/ 941 +(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/(Disable (0), Enable (1), default:0) 974 974 \\Example: AT+SHOWID=1 ~-~-> Enable Information printing. 975 975 976 976 977 -=== 3.2.1 5Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) ===945 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 978 978 979 979 980 980 The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. ... ... @@ -981,34 +981,14 @@ 981 981 982 982 (% style="color:blue" %)**AT Command:** 983 983 984 -(% style="color:#037691" %)**AT+CHE=1 952 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode 985 985 986 986 987 987 (% style="color:blue" %)**Downlink Payload:0X24** 988 988 989 -Example: 0x24 01 957 +Example: 0x24 01 ~/~/ Same as AT+CHE=1 990 990 991 991 992 -=== 3.2.16 Get or Set Threshold for motion detect(Since firmware 1.4.3) === 993 - 994 - 995 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event. 996 - 997 -(% style="color:blue" %)**AT Command:** 998 - 999 -(% style="color:#037691" %)**AT+PT=xx** 1000 - 1001 - Example: 1002 - 1003 - AT+PT=14 ~-~-> Set to detect car motion. 1004 - 1005 - AT+PT=41 ~-~-> set to detect walk motion. 1006 - 1007 - 1008 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%) 1009 -0xB4 14 ~/~/ Same as AT+PT=14 1010 - 1011 - 1012 1012 = 4. Setting for Different Scenarios = 1013 1013 1014 1014 ... ... @@ -1041,10 +1041,10 @@ 1041 1041 (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32 1042 1042 1043 1043 1044 -[[image:1664503563660-578.png ||_mstalt="296777"]]992 +[[image:1664503563660-578.png]] 1045 1045 1046 1046 1047 -[[image:1664503574618-659.png ||_mstalt="297986"]]995 +[[image:1664503574618-659.png]] 1048 1048 1049 1049 1050 1050 ... ... @@ -1060,15 +1060,16 @@ 1060 1060 US915.bin @ 0x10000(Select the bin file of the frequency band you need) 1061 1061 1062 1062 1063 -[[image:image-20221 207120501-1.png]]1011 +[[image:image-20221118105220-2.png]] 1064 1064 1065 1065 1066 1066 1067 1067 After upgrade finish, it will show finish as below: 1068 1068 1069 -[[image:image-20221 207133911-7.png]]1017 +[[image:image-20221118105402-4.png]] 1070 1070 1071 1071 1020 + 1072 1072 = 6. Developer Guide = 1073 1073 1074 1074 == 6.1 Compile Source Code == ... ... @@ -1081,81 +1081,24 @@ 1081 1081 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]] 1082 1082 1083 1083 1084 -[[image:1664503635019-941.png ||_mstalt="294658"]]1033 +[[image:1664503635019-941.png]] 1085 1085 1086 1086 1087 1087 1088 1088 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 1089 1089 1090 -[[image:1664503715811-892.png ||_mstalt="295698"]]1039 +[[image:1664503715811-892.png]] 1091 1091 1092 1092 1093 -=== 6.1.2 Build the development environment === 1094 - 1095 - 1096 -**~1. Download and install arduino IDE** 1097 - 1098 -[[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]] 1099 - 1100 - 1101 -**2. Download the ESP32 development package in the arduino IDE** 1102 - 1103 -[[image:image-20221213100007-1.png]] 1104 - 1105 - 1106 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]] 1107 - 1108 -[[image:image-20221213100626-2.png]] 1109 - 1110 - 1111 -Restart the IDE after the addition is complete, then: 1112 - 1113 -[[image:image-20221213100808-3.png||height="679" width="649"]] 1114 - 1115 - 1116 -[[image:image-20221213101040-4.png]] 1117 - 1118 - 1119 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03. 1120 -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)** 1121 - 1122 - 1123 -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: 1124 - 1125 -(% style="color:blue" %)**Methods as below:** 1126 - 1127 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]] 1128 - 1129 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here. 1130 - 1131 1131 (% 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. 1132 1132 1133 -[[image:image-2022121 3102311-5.png||height="582" width="711"]]1044 +[[image:image-20221024105643-1.png]] 1134 1134 1135 - 1136 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)** 1137 - 1138 -[[image:image-20221213102334-6.png]] 1139 - 1140 -(% style="color:red" %)**Note: This step requires a python environment** 1141 - 1142 - 1143 -Either way, in the end: 1144 - 1145 -The final effect is to open the arduino and you can see the esp32 1146 - 1147 -[[image:image-20221213110952-8.png||height="866" width="711"]] 1148 - 1149 - 1150 - 1151 -[[image:image-20221024105643-1.png||_mstalt="428129"]] 1152 - 1153 1153 **~ Figure1** 1154 1154 1155 1155 1049 +[[image:image-20221024105643-2.png]] 1156 1156 1157 -[[image:image-20221024105643-2.png||_mstalt="428493"]] 1158 - 1159 1159 **Figure2** 1160 1160 1161 1161 ... ... @@ -1164,7 +1164,7 @@ 1164 1164 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: 1165 1165 1166 1166 1167 -[[image:1664503752288-974.png ||_mstalt="298194"]]1059 +[[image:1664503752288-974.png]] 1168 1168 1169 1169 1170 1170 == 6.2 Source Code == ... ... @@ -1172,19 +1172,19 @@ 1172 1172 1173 1173 * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:** 1174 1174 1175 -[[image:1664503794261-827.png ||_mstalt="296387"]]1067 +[[image:1664503794261-827.png]] 1176 1176 1177 1177 1178 1178 1179 1179 * (% style="color:blue" %)**Click to upload** 1180 1180 1181 -[[image:1664503808294-336.png ||_mstalt="295711"]]1073 +[[image:1664503808294-336.png]] 1182 1182 1183 1183 1184 1184 1185 1185 * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 1186 1186 1187 -[[image:1664503824081-592.png ||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]1079 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 1188 1188 1189 1189 1190 1190 = 7. FAQ = ... ... @@ -1198,7 +1198,7 @@ 1198 1198 == 7.2 What is the pin mapping for the USB program cable? == 1199 1199 1200 1200 1201 -[[image:1664499635206-262.png ||_mstalt="295360"]]1093 +[[image:1664499635206-262.png]] 1202 1202 1203 1203 1204 1204 ... ... @@ -1213,9 +1213,6 @@ 1213 1213 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 1214 1214 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 1215 1215 1216 -(% style="display:none" %) (%%) 1217 - 1218 - 1219 1219 == 7.3 Notes on using different serial port tools for TrackerD == 1220 1220 1221 1221 === 7.3.1 Serial port utility === ... ... @@ -1226,13 +1226,13 @@ 1226 1226 Need to adjust the data stream to RTS/CTS on physical restart. 1227 1227 1228 1228 (% class="wikigeneratedid" %) 1229 -[[image:image-20221102140621-1.png ||_mstalt="425672"]]1118 +[[image:image-20221102140621-1.png]] 1230 1230 1231 1231 1232 1232 1233 1233 When using AT commands, the data flow needs to be adjusted to XON/XOFF 1234 1234 1235 -[[image:image-20221102140638-2.png ||_mstalt="428727"]]1124 +[[image:image-20221102140638-2.png]] 1236 1236 1237 1237 1238 1238 === 7.3.2 SecureCRT === ... ... @@ -1241,22 +1241,22 @@ 1241 1241 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. 1242 1242 1243 1243 1244 -[[image:image-20221102140704-3.png ||_mstalt="427076"]]1133 +[[image:image-20221102140704-3.png]] 1245 1245 1246 1246 1247 -[[image:image-20221102140712-4.png ||_mstalt="427089"]]1136 +[[image:image-20221102140712-4.png]] 1248 1248 1249 1249 1250 1250 === 7.3.3 PUTTY === 1251 1251 1252 1252 1253 -[[image:image-20221102140748-5.png ||_mstalt="430456"]]1142 +[[image:image-20221102140748-5.png]] 1254 1254 1255 1255 1256 1256 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. 1257 1257 1258 1258 1259 -[[image:image-20221102140801-6.png ||_mstalt="427466"]]1148 +[[image:image-20221102140801-6.png]] 1260 1260 1261 1261 1262 1262 == 7.4 How to modify source code to compile different frequency band bin file? == ... ... @@ -1271,7 +1271,7 @@ 1271 1271 **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.** 1272 1272 1273 1273 1274 -[[image:image-20221116111844-1.png|| _mstalt="428688"height="227" width="782"]]1163 +[[image:image-20221116111844-1.png||height="227" width="782"]] 1275 1275 1276 1276 1277 1277 ... ... @@ -1278,7 +1278,7 @@ 1278 1278 **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).** 1279 1279 1280 1280 1281 -[[image:image-20221116111844-2.png|| _mstalt="429052"height="262" width="781"]]1170 +[[image:image-20221116111844-2.png||height="262" width="781"]] 1282 1282 1283 1283 1284 1284 ... ... @@ -1285,7 +1285,7 @@ 1285 1285 **3. Compile the AS923_JP band, please refer to the intention shown** 1286 1286 1287 1287 1288 -[[image:image-20221116111844-3.png|| _mstalt="429416"height="338" width="746"]]1177 +[[image:image-20221116111844-3.png||height="338" width="746"]] 1289 1289 1290 1290 1291 1291 ... ... @@ -1292,18 +1292,12 @@ 1292 1292 **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.** 1293 1293 1294 1294 1295 -[[image:image-20221116111844-4.png|| _mstalt="429780"height="641" width="739"]]1184 +[[image:image-20221116111844-4.png||height="641" width="739"]] 1296 1296 1297 1297 1298 -[[image:image-20221116111844-5.png|| _mstalt="430144"height="551" width="708"]]1187 +[[image:image-20221116111844-5.png||height="551" width="708"]] 1299 1299 1300 1300 1301 -== 7.5 Are there example python example for BLE Indoor Positioning? == 1302 - 1303 - 1304 -[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]] 1305 - 1306 - 1307 1307 = 8 Trouble Shooting = 1308 1308 1309 1309 == 8.1 TDC is changed to 4294947296 and cause no uplink. == ... ... @@ -1310,7 +1310,7 @@ 1310 1310 1311 1311 1312 1312 ((( 1313 -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.11196 +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 1314 1314 ))) 1315 1315 1316 1316 ... ... @@ -1324,69 +1324,50 @@ 1324 1324 1325 1325 == 8.3 Problem after Upgrading Firmware == 1326 1326 1327 -=== 8.3.1 "rst: (0x3 SW_RESET)" andContinue Restart after upgrading ===1210 +=== 8.3.1 Continue Restart after upgrading === 1328 1328 1329 1329 1330 -**Error Output** 1331 - 1332 - 1333 -[[image:image-20221122100004-4.png||_mstalt="424606"]] 1334 - 1335 - 1336 1336 ((( 1337 -Some partition is missed during upgrade, please upgrade below four files as example: 1338 - 1339 -[[image:image-20221207120524-2.png]] 1214 +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 1340 1340 ))) 1341 1341 1342 1342 1343 - === 8.3.2 TrackerD's led light isalways GREEN on after upgrading===1218 +[[image:image-20221118105249-3.png]] 1344 1344 1345 1345 1346 - Itisbecausethe partitionsareifferentwhen upgradingversions above 1.4.1,andanew partition file needsto beadded. Pleasereferto the operationsteps in chapter 8.3.11221 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1347 1347 1348 1348 1349 - ===8.3.3"flash read err"afterupgradefirmware===1224 +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 1350 1350 1351 1351 1227 +=== 8.3.3 "flash read err" after upgrade firmware === 1228 + 1352 1352 Error shows below, user might erase the entire flash include u-boot partition which cause this issue. 1353 1353 1231 +[[image:image-20221122100004-1.png||height="497" width="534"]] 1354 1354 1355 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]] 1356 1356 1357 - 1358 1358 User need to upgrade again with below four files to solve this issue. 1359 1359 1360 - [[image:image-20221 207120530-3.png]]1236 + [[image:image-20221122100004-2.png||height="619" width="389"]] 1361 1361 1362 1362 **Figure 2** 1363 1363 1364 1364 1365 -=== 8.3. 4"Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===1241 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware === 1366 1366 1367 - 1368 1368 User might erase the entire flash include keys and default settings which cause this issue. 1369 1369 1370 -After the upgrade is completed, enter **AT+CFG**as shown in the figure below.1245 +After the upgrade is completed, enter AT+CFG as shown in the figure below. 1371 1371 1247 +[[image:image-20221122100004-3.png]] 1372 1372 1373 - [[image:image-20221122100004-3.png||_mstalt="424242"]]1249 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label. 1374 1374 1375 1375 1376 - 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.1252 +Example: 1377 1377 1378 -After AT+FDR. please set 1379 - 1380 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7** 1381 - 1382 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000** 1383 - 1384 -**Example:** 1385 - 1386 -AT+PDOP=7.00 1387 - 1388 -AT+FTIME=180 1389 - 1390 1390 AT+DEUI=70B3D57ED0053981 1391 1391 1392 1392 AT+APPEUI=D23345667BCBCCAF ... ... @@ -1400,6 +1400,13 @@ 1400 1400 AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA) 1401 1401 1402 1402 1267 + 1268 +=== 8.3.4 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 === 1269 + 1270 + 1271 +[[image:image-20221122100004-4.png]] 1272 + 1273 + 1403 1403 == 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1404 1404 1405 1405 ... ... @@ -1413,61 +1413,15 @@ 1413 1413 1414 1414 2) Set PDOP to a higher value. 1415 1415 1416 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.)1287 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.) 1417 1417 1418 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces)1289 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces) 1419 1419 1420 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments)1291 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments) 1421 1421 1422 1422 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 1423 1423 1424 1424 1425 -== 8.6 When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets == 1426 - 1427 - 1428 -When upgrading, use the erase button to upgrade 1429 - 1430 -[[image:image-20221207120536-4.png]] 1431 - 1432 - 1433 -The parameters are displayed abnormally and cannot be fixed using AT+FDR 1434 - 1435 -[[image:image-20221128103040-2.png||height="431" width="525"]] 1436 - 1437 - 1438 -Please upgrade these four files,link(The boot_app0 file is in the version folder you need) 1439 - 1440 -[[image:image-20221207134028-8.png]] 1441 - 1442 - 1443 -Reboot information after upgrade 1444 - 1445 -[[image:image-20221128111443-4.png||height="432" width="546"]] 1446 - 1447 - 1448 -Use **AT+FDR** command to reset and then use **AT+CFG** to check whether the configuration is back to normal 1449 - 1450 -[[image:image-20221128111850-5.png]] 1451 - 1452 - 1453 -After the parameters return to normal, upgrade to the version you need again 1454 - 1455 -[[image:image-20221207120601-5.png]] 1456 - 1457 - 1458 -At this point, the parameters return to normal after running AT+FDR again 1459 - 1460 -[[image:image-20221128112035-7.png]] 1461 - 1462 - 1463 -== 8.7 If you encounter the following problems, please upgrade to the latest version == 1464 - 1465 - 1466 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond. 1467 - 1468 -2. Send some commands through the serial port to prompt an error (Example:AT+SMOD=1,0,1) 1469 - 1470 - 1471 1471 = 9. Order Info = 1472 1472 1473 1473 ... ... @@ -1489,9 +1489,6 @@ 1489 1489 1490 1490 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1491 1491 1492 -(% style="display:none" %) (%%) 1493 - 1494 - 1495 1495 = 10. Packing Info = 1496 1496 1497 1497 ... ... @@ -1507,9 +1507,6 @@ 1507 1507 1508 1508 * Weight: 50g 1509 1509 1510 -(% style="display:none" %) (%%) 1511 - 1512 - 1513 1513 = 11. Support = 1514 1514 1515 1515 ... ... @@ -1517,9 +1517,6 @@ 1517 1517 1518 1518 * 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]]. 1519 1519 1520 -(% style="display:none" %) (%%) 1521 - 1522 - 1523 1523 = 12. Reference = 1524 1524 1525 1525 ... ... @@ -1528,6 +1528,3 @@ 1528 1528 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1529 1529 1530 1530 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 1531 - 1532 - 1533 -)))
- 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
- image-20221213110952-8.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -152.8 KB - Content
- image-20230213110119-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -182.3 KB - Content
- image-20230213110214-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -182.3 KB - Content
- image-20230213110506-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -19.8 KB - Content