Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)
Last modified by Xiaoling on 2023/12/27 09:15
From version 201.1
edited by Bei Jinggeng
on 2023/03/08 11:57
on 2023/03/08 11:57
Change comment:
Uploaded new attachment "image-20230308115701-3.png", version {1}
To version 144.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, 32 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
- image-20230302145315-1.png
- image-20230307135914-1.png
- image-20230307135932-2.png
- image-20230308115430-1.png
- image-20230308115616-2.png
- image-20230308115701-3.png
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Bei1 +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.** ... ... @@ -94,7 +94,6 @@ 94 94 * Tracking: max: 38mA 95 95 96 96 97 - 98 98 == 1.3 Features == 99 99 100 100 ... ... @@ -114,7 +114,6 @@ 114 114 * Datalog 115 115 116 116 117 - 118 118 == 1.4 Applications == 119 119 120 120 ... ... @@ -122,7 +122,6 @@ 122 122 * Human tracking 123 123 124 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"]]139 +[[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"]]151 +[[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"]]160 +[[image:1664501711466-918.png]] 162 162 163 163 164 164 165 -[[image:1664501721248-725.png ||_mstalt="294450"]]164 +[[image:1664501721248-725.png]] 166 166 167 167 168 -[[image:1664501734705-405.png ||_mstalt="293306"]]167 +[[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"]]174 +[[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"]]180 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]] 182 182 183 -[[image:1664502835802-546.png ||_mstalt="295061"]]182 +[[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;" %)1211 +|=(% 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"]]214 +[[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" %)4bit258 +|=(% 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,16 @@ 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)(%%)281 +(% 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"]]286 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %) 287 +|=(% 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 288 +|=(% 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 291 292 - 293 293 === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 294 294 295 295 ... ... @@ -308,20 +308,21 @@ 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"]]309 +[[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:"]]314 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 315 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits 316 +|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 319 319 318 + 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:"]]321 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %) 322 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit 323 +|=(% 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 ... ... @@ -338,12 +338,12 @@ 338 338 2. In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below: 339 339 340 340 341 -[[image:1664502116362-706.png ||_mstalt="293306"]]340 +[[image:1664502116362-706.png]] 342 342 343 343 344 344 3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 345 345 346 -[[image:1664502166010-515.png ||_mstalt="291395"]]345 +[[image:1664502166010-515.png]] 347 347 348 348 349 349 ... ... @@ -366,9 +366,7 @@ 366 366 * 3.40v ~~ 3.69v: 20% ~~ 40% 367 367 * < 3.39v: 0~~20% 368 368 369 -(% style="display:none" %) (%%) 370 370 371 - 372 372 ==== (% style="color:blue" %)**MOD:**(%%) ==== 373 373 374 374 **Example: ** (0x60>>6) & 0x3f =1 ... ... @@ -424,13 +424,13 @@ 424 424 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 425 425 426 426 (% class="wikigeneratedid" %) 427 -[[image:1665301687277-443.png ||_mstalt="296140"]]424 +[[image:1665301687277-443.png]] 428 428 429 429 430 430 === 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 431 431 432 432 433 -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.430 +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. 434 434 435 435 436 436 (% style="color:red" %)**Note for this mode:** ... ... @@ -447,7 +447,7 @@ 447 447 )))|4|4|2|1|1|1|1|1 448 448 |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 449 449 450 -[[image:image-20221009160309-2.png ||_mstalt="429312"]]447 +[[image:image-20221009160309-2.png]] 451 451 452 452 453 453 === 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === ... ... @@ -474,7 +474,7 @@ 474 474 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 475 475 )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 476 476 477 -[[image:1664502425687-834.png ||_mstalt="296738"]]474 +[[image:1664502425687-834.png]] 478 478 479 479 480 480 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). ... ... @@ -485,32 +485,10 @@ 485 485 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 486 486 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 487 487 488 -(% style="display:none" %) (%%) 489 489 486 +=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 490 490 491 -=== 2.4.6 Uplink FPORT~=7, Alarm information status(Since firmware 1.4.4) === 492 492 493 - 494 -The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server. 495 - 496 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 497 -|**Size(bytes)**|2|1 498 -|**Value**|[[Alarm & BAT>>path:#HAlarm26BAT:]]|Mod+lon 499 - 500 - [[image:image-20230302145315-1.png]] 501 - 502 -alarm=(bytes[0] & 0x40) ~/~/ Alarm status 503 - 504 -batV=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000; ~/~/ Battery,units:V 505 - 506 -mod = bytes[2] & 0xC0; 507 - 508 -Lon=(bytes[2] & 0x20) 509 - 510 - 511 -=== 2.4.7 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 512 - 513 - 514 514 TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **WiFi** so TrackerD will scan WiFi and find the strongest WiFi info and uplink. 515 515 516 516 ... ... @@ -523,7 +523,7 @@ 523 523 )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 524 524 525 525 (% class="wikigeneratedid" %) 526 -[[image:1667288597595-714.png|| _mstalt="299598"height="212" width="1151"]]501 +[[image:1667288597595-714.png||height="212" width="1151"]] 527 527 528 528 529 529 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). ... ... @@ -530,18 +530,16 @@ 530 530 * (% style="color:#037691" %)**SSID: **(%%)WiFi name. 531 531 * (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 532 532 533 -(% style="display:none" %) (%%) 534 534 509 +=== 2.4.7 Add Payload format in TTN V3 === 535 535 536 -=== 2.4.8 Add Payload format in TTN V3 === 537 537 538 - 539 539 In TTN V3, user can add a custom payload so it shows friendly. 540 540 541 541 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 542 542 543 543 544 -[[image:1664502649601-895.png ||_mstalt="296985"]]517 +[[image:1664502649601-895.png]] 545 545 546 546 547 547 ... ... @@ -551,7 +551,7 @@ 551 551 552 552 Save the change the uplink message will be parsed. As below: 553 553 554 -[[image:1664502676891-606.png ||_mstalt="296673"]]527 +[[image:1664502676891-606.png]] 555 555 556 556 557 557 == 2.5 Integrate with Datacake == ... ... @@ -562,7 +562,7 @@ 562 562 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]] 563 563 564 564 565 -[[image:1664502695771-538.png ||_mstalt="297349"]]538 +[[image:1664502695771-538.png]] 566 566 567 567 568 568 == 2.6 Integrate with Tago == ... ... @@ -573,46 +573,25 @@ 573 573 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]] 574 574 575 575 576 -[[image:1664502715371-321.png ||_mstalt="292162"]]549 +[[image:1664502715371-321.png]] 577 577 578 578 579 -== 2.7 Integrate with Node-red==552 +== 2.7 Datalog Feature == 580 580 581 581 582 -~1. Install node-red, please refer to the installation method in the link: 583 - 584 - [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]] 585 -2. Import the created flow template, please refer to the import method in the link: 586 - 587 - [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]] 588 - The address of the flow template: 589 - 590 - [[dragino-end-node-decoder/TrackerD.json at main · dragino/dragino-end-node-decoder · GitHub>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/TrackerD.json]] 591 - 592 -(% style="color:red" %)**Note: If you are using NODE-RED for the first time, please search and install the two plug-ins in the figure below in node-red to fully use the flow template.** 593 - 594 -[[image:image-20230307135914-1.png||height="527" width="1045"]] 595 - 596 - 597 -[[image:image-20230307135932-2.png||height="527" width="1044"]] 598 - 599 - 600 -== 2.8 Datalog Feature == 601 - 602 - 603 603 total 273 entries,by default, 604 604 605 -User can set [[PNACKMD=1>>||anchor="H3.2.1 1A0AutoSendNone-ACKmessages"]], to enable Datalog feature.557 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 606 606 607 607 Example use case. 608 608 609 -[[image:image-20221009234703-2.png|| _mstalt="429143"height="328" width="899"]]561 +[[image:image-20221009234703-2.png||height="328" width="899"]] 610 610 611 611 612 -[[image:image-20221009234629-1.png|| _mstalt="431145"height="390" width="577"]]564 +[[image:image-20221009234629-1.png||height="390" width="577"]] 613 613 614 614 615 -== 2. 9Alarm Mode ==567 +== 2.8 Alarm Mode == 616 616 617 617 618 618 ((( ... ... @@ -637,21 +637,15 @@ 637 637 ))) 638 638 639 639 640 -== 2. 10Transport Mode ==592 +== 2.9 Transport Mode == 641 641 642 642 643 643 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. 644 644 645 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation. 646 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic. 647 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion. 648 648 649 - (% style="display:none"%)(%%)598 +== 2.10 LED Status == 650 650 651 651 652 -== 2.11 LED Status == 653 - 654 - 655 655 (% border="1.5" style="background-color:#ffffcc; width:500px" %) 656 656 |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 657 657 |(% 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 ... ... @@ -666,15 +666,13 @@ 666 666 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 667 667 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 668 668 669 -(% style="display:none" %) (%%) 670 670 616 +== 2.11 Button Function == 671 671 672 -== 2.12 Button Function == 673 673 674 - 675 675 (% style="color:blue" %)**RESET button:** 676 676 677 -[[image:1664502835802-546.png ||_mstalt="295061"]]621 +[[image:1664502835802-546.png]] 678 678 679 679 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server. 680 680 ... ... @@ -681,9 +681,8 @@ 681 681 682 682 (% style="color:red" %)**RED button:** 683 683 684 -[[image: image-20230213110506-3.png]](% style="display:none" %)628 +[[image:1664502854406-763.png]] 685 685 686 -(% style="display:none" %) (%%) 687 687 688 688 (% border="1" style="background-color:#ffffcc; width:510px" %) 689 689 |=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description** ... ... @@ -691,12 +691,10 @@ 691 691 |(% 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 692 692 |(% 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. 693 693 694 -(% style="display:none" %) (%%) 695 695 638 +== 2.12 USB Port Function == 696 696 697 -== 2.13 USB Port Function == 698 698 699 - 700 700 The USB interface of TrackerD has below functions: 701 701 702 702 * Power on the device ... ... @@ -704,9 +704,7 @@ 704 704 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 705 705 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 706 706 707 -(% style="display:none" %) (%%) 708 708 709 - 710 710 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 711 711 712 712 ... ... @@ -721,22 +721,22 @@ 721 721 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. 722 722 723 723 724 -[[image:1664502999401-486.png ||_mstalt="296985"]]663 +[[image:1664502999401-486.png]] 725 725 726 726 727 727 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: 728 728 729 729 730 -[[image:1664503022490-662.png ||_mstalt="293332"]]669 +[[image:1664503022490-662.png]] 731 731 732 732 733 -[[image:1664503035713-500.png ||_mstalt="291096"]]672 +[[image:1664503035713-500.png]] 734 734 735 735 736 -[[image:1664503047675-651.png ||_mstalt="295386"]]675 +[[image:1664503047675-651.png]] 737 737 738 -(% style="display:none" %) (%%) 739 739 678 + 740 740 == 3.2 Command Set == 741 741 742 742 === 3.2.1 Set Transmit Interval === ... ... @@ -802,7 +802,7 @@ 802 802 (% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 803 803 804 804 805 -=== 3.2.5 Disable/Enable LED flash and buzzer===744 +=== 3.2.5 Disable/Enable LED flash === 806 806 807 807 808 808 Disable/Enable LED for position, downlink and uplink ... ... @@ -862,9 +862,9 @@ 862 862 863 863 (% style="color:#037691" %)**cc: ** 864 864 865 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State804 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 866 866 867 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((%_mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))806 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%)) 868 868 869 869 (% style="color:blue" %)**Example:** 870 870 ... ... @@ -926,8 +926,8 @@ 926 926 (% style="color:#037691" %)**0xAD 00 46** (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7) 927 927 928 928 929 -=== 3.2.10 Disable/Enable the confirmation mode === 930 930 869 +**Disable/Enable the confirmation mode** 931 931 932 932 * (% style="color:blue" %)**AT Command:** 933 933 ... ... @@ -946,7 +946,7 @@ 946 946 (% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1 947 947 948 948 949 -=== 3.2.1 1888 +=== 3.2.10 Auto Send None-ACK messages === 950 950 951 951 952 952 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. ... ... @@ -964,10 +964,10 @@ 964 964 965 965 * (% style="color:blue" %)**Downlink Command: 0x34** 966 966 967 -Example: 0x34 906 +Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 968 968 969 969 970 -=== 3.2.1 2Set BLEMASK to filter BLE iBeacon ===909 +=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 971 971 972 972 973 973 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. ... ... @@ -976,16 +976,16 @@ 976 976 977 977 (% style="color:blue" %)**AT Command:** 978 978 979 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456918 + (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 980 980 981 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK920 + (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 982 982 983 983 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 984 984 985 -Example: 0xB2 924 +Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 986 986 987 987 988 -=== 3.2.1 3Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) ===927 +=== 3.2.12 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 989 989 990 990 991 991 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. ... ... @@ -994,16 +994,16 @@ 994 994 995 995 (% style="color:blue" %)**AT Command:** 996 996 997 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456936 + (% style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456 998 998 999 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK938 + (% style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK 1000 1000 1001 1001 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)** 1002 1002 1003 -Example: 0xB3 942 +Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 1004 1004 1005 1005 1006 -=== 3.2.1 4Disable/Enable Information printing(Since firmware 1.4.1) ===945 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 1007 1007 1008 1008 1009 1009 Users can use this feature to enable/disable Information printing. ... ... @@ -1010,11 +1010,11 @@ 1010 1010 1011 1011 (% style="color:blue" %)**AT Command:** 1012 1012 1013 -(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/ 952 +(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/(Disable (0), Enable (1), default:0) 1014 1014 \\Example: AT+SHOWID=1 ~-~-> Enable Information printing. 1015 1015 1016 1016 1017 -=== 3.2.1 5Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) ===956 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 1018 1018 1019 1019 1020 1020 The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. ... ... @@ -1021,34 +1021,14 @@ 1021 1021 1022 1022 (% style="color:blue" %)**AT Command:** 1023 1023 1024 -(% style="color:#037691" %)**AT+CHE=1 963 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode 1025 1025 1026 1026 1027 1027 (% style="color:blue" %)**Downlink Payload:0X24** 1028 1028 1029 -Example: 0x24 01 968 +Example: 0x24 01 ~/~/ Same as AT+CHE=1 1030 1030 1031 1031 1032 -=== 3.2.16 Get or Set Threshold for motion detect(Since firmware 1.4.3) === 1033 - 1034 - 1035 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event. 1036 - 1037 -(% style="color:blue" %)**AT Command:** 1038 - 1039 -(% style="color:#037691" %)**AT+PT=xx** 1040 - 1041 - Example: 1042 - 1043 - AT+PT=14 ~-~-> Set to detect car motion. 1044 - 1045 - AT+PT=41 ~-~-> set to detect walk motion. 1046 - 1047 - 1048 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%) 1049 -0xB4 14 ~/~/ Same as AT+PT=14 1050 - 1051 - 1052 1052 = 4. Setting for Different Scenarios = 1053 1053 1054 1054 ... ... @@ -1081,10 +1081,10 @@ 1081 1081 (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32 1082 1082 1083 1083 1084 -[[image:1664503563660-578.png ||_mstalt="296777"]]1003 +[[image:1664503563660-578.png]] 1085 1085 1086 1086 1087 -[[image:1664503574618-659.png ||_mstalt="297986"]]1006 +[[image:1664503574618-659.png]] 1088 1088 1089 1089 1090 1090 ... ... @@ -1100,15 +1100,16 @@ 1100 1100 US915.bin @ 0x10000(Select the bin file of the frequency band you need) 1101 1101 1102 1102 1103 -[[image:image-20221 207120501-1.png]]1022 +[[image:image-20221118105220-2.png]] 1104 1104 1105 1105 1106 1106 1107 1107 After upgrade finish, it will show finish as below: 1108 1108 1109 -[[image:image-20221 207133911-7.png]]1028 +[[image:image-20221118105402-4.png]] 1110 1110 1111 1111 1031 + 1112 1112 = 6. Developer Guide = 1113 1113 1114 1114 == 6.1 Compile Source Code == ... ... @@ -1121,81 +1121,24 @@ 1121 1121 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]] 1122 1122 1123 1123 1124 -[[image:1664503635019-941.png ||_mstalt="294658"]]1044 +[[image:1664503635019-941.png]] 1125 1125 1126 1126 1127 1127 1128 1128 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 1129 1129 1130 -[[image:1664503715811-892.png ||_mstalt="295698"]]1050 +[[image:1664503715811-892.png]] 1131 1131 1132 1132 1133 -=== 6.1.2 Build the development environment === 1134 - 1135 - 1136 -**~1. Download and install arduino IDE** 1137 - 1138 -[[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]] 1139 - 1140 - 1141 -**2. Download the ESP32 development package in the arduino IDE** 1142 - 1143 -[[image:image-20221213100007-1.png]] 1144 - 1145 - 1146 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]] 1147 - 1148 -[[image:image-20221213100626-2.png]] 1149 - 1150 - 1151 -Restart the IDE after the addition is complete, then: 1152 - 1153 -[[image:image-20221213100808-3.png||height="679" width="649"]] 1154 - 1155 - 1156 -[[image:image-20221213101040-4.png]] 1157 - 1158 - 1159 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03. 1160 -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)** 1161 - 1162 - 1163 -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: 1164 - 1165 -(% style="color:blue" %)**Methods as below:** 1166 - 1167 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]] 1168 - 1169 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here. 1170 - 1171 1171 (% 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. 1172 1172 1173 -[[image:image-2022121 3102311-5.png||height="582" width="711"]]1055 +[[image:image-20221024105643-1.png]] 1174 1174 1175 - 1176 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)** 1177 - 1178 -[[image:image-20221213102334-6.png]] 1179 - 1180 -(% style="color:red" %)**Note: This step requires a python environment** 1181 - 1182 - 1183 -Either way, in the end: 1184 - 1185 -The final effect is to open the arduino and you can see the esp32 1186 - 1187 -[[image:image-20221213110952-8.png||height="866" width="711"]] 1188 - 1189 - 1190 - 1191 -[[image:image-20221024105643-1.png||_mstalt="428129"]] 1192 - 1193 1193 **~ Figure1** 1194 1194 1195 1195 1060 +[[image:image-20221024105643-2.png]] 1196 1196 1197 -[[image:image-20221024105643-2.png||_mstalt="428493"]] 1198 - 1199 1199 **Figure2** 1200 1200 1201 1201 ... ... @@ -1204,7 +1204,7 @@ 1204 1204 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: 1205 1205 1206 1206 1207 -[[image:1664503752288-974.png ||_mstalt="298194"]]1070 +[[image:1664503752288-974.png]] 1208 1208 1209 1209 1210 1210 == 6.2 Source Code == ... ... @@ -1212,19 +1212,19 @@ 1212 1212 1213 1213 * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:** 1214 1214 1215 -[[image:1664503794261-827.png ||_mstalt="296387"]]1078 +[[image:1664503794261-827.png]] 1216 1216 1217 1217 1218 1218 1219 1219 * (% style="color:blue" %)**Click to upload** 1220 1220 1221 -[[image:1664503808294-336.png ||_mstalt="295711"]]1084 +[[image:1664503808294-336.png]] 1222 1222 1223 1223 1224 1224 1225 1225 * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 1226 1226 1227 -[[image:1664503824081-592.png ||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]1090 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 1228 1228 1229 1229 1230 1230 = 7. FAQ = ... ... @@ -1238,7 +1238,7 @@ 1238 1238 == 7.2 What is the pin mapping for the USB program cable? == 1239 1239 1240 1240 1241 -[[image:1664499635206-262.png ||_mstalt="295360"]]1104 +[[image:1664499635206-262.png]] 1242 1242 1243 1243 1244 1244 ... ... @@ -1253,9 +1253,7 @@ 1253 1253 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 1254 1254 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 1255 1255 1256 -(% style="display:none" %) (%%) 1257 1257 1258 - 1259 1259 == 7.3 Notes on using different serial port tools for TrackerD == 1260 1260 1261 1261 === 7.3.1 Serial port utility === ... ... @@ -1266,13 +1266,13 @@ 1266 1266 Need to adjust the data stream to RTS/CTS on physical restart. 1267 1267 1268 1268 (% class="wikigeneratedid" %) 1269 -[[image:image-20221102140621-1.png ||_mstalt="425672"]]1130 +[[image:image-20221102140621-1.png]] 1270 1270 1271 1271 1272 1272 1273 1273 When using AT commands, the data flow needs to be adjusted to XON/XOFF 1274 1274 1275 -[[image:image-20221102140638-2.png ||_mstalt="428727"]]1136 +[[image:image-20221102140638-2.png]] 1276 1276 1277 1277 1278 1278 === 7.3.2 SecureCRT === ... ... @@ -1281,22 +1281,22 @@ 1281 1281 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. 1282 1282 1283 1283 1284 -[[image:image-20221102140704-3.png ||_mstalt="427076"]]1145 +[[image:image-20221102140704-3.png]] 1285 1285 1286 1286 1287 -[[image:image-20221102140712-4.png ||_mstalt="427089"]]1148 +[[image:image-20221102140712-4.png]] 1288 1288 1289 1289 1290 1290 === 7.3.3 PUTTY === 1291 1291 1292 1292 1293 -[[image:image-20221102140748-5.png ||_mstalt="430456"]]1154 +[[image:image-20221102140748-5.png]] 1294 1294 1295 1295 1296 1296 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. 1297 1297 1298 1298 1299 -[[image:image-20221102140801-6.png ||_mstalt="427466"]]1160 +[[image:image-20221102140801-6.png]] 1300 1300 1301 1301 1302 1302 == 7.4 How to modify source code to compile different frequency band bin file? == ... ... @@ -1311,7 +1311,7 @@ 1311 1311 **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.** 1312 1312 1313 1313 1314 -[[image:image-20221116111844-1.png|| _mstalt="428688"height="227" width="782"]]1175 +[[image:image-20221116111844-1.png||height="227" width="782"]] 1315 1315 1316 1316 1317 1317 ... ... @@ -1318,7 +1318,7 @@ 1318 1318 **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).** 1319 1319 1320 1320 1321 -[[image:image-20221116111844-2.png|| _mstalt="429052"height="262" width="781"]]1182 +[[image:image-20221116111844-2.png||height="262" width="781"]] 1322 1322 1323 1323 1324 1324 ... ... @@ -1325,7 +1325,7 @@ 1325 1325 **3. Compile the AS923_JP band, please refer to the intention shown** 1326 1326 1327 1327 1328 -[[image:image-20221116111844-3.png|| _mstalt="429416"height="338" width="746"]]1189 +[[image:image-20221116111844-3.png||height="338" width="746"]] 1329 1329 1330 1330 1331 1331 ... ... @@ -1332,18 +1332,12 @@ 1332 1332 **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.** 1333 1333 1334 1334 1335 -[[image:image-20221116111844-4.png|| _mstalt="429780"height="641" width="739"]]1196 +[[image:image-20221116111844-4.png||height="641" width="739"]] 1336 1336 1337 1337 1338 -[[image:image-20221116111844-5.png|| _mstalt="430144"height="551" width="708"]]1199 +[[image:image-20221116111844-5.png||height="551" width="708"]] 1339 1339 1340 1340 1341 -== 7.5 Are there example python example for BLE Indoor Positioning? == 1342 - 1343 - 1344 -[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]] 1345 - 1346 - 1347 1347 = 8 Trouble Shooting = 1348 1348 1349 1349 == 8.1 TDC is changed to 4294947296 and cause no uplink. == ... ... @@ -1350,7 +1350,7 @@ 1350 1350 1351 1351 1352 1352 ((( 1353 -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.11208 +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 1354 1354 ))) 1355 1355 1356 1356 ... ... @@ -1364,69 +1364,50 @@ 1364 1364 1365 1365 == 8.3 Problem after Upgrading Firmware == 1366 1366 1367 -=== 8.3.1 "rst: (0x3 SW_RESET)" andContinue Restart after upgrading ===1222 +=== 8.3.1 Continue Restart after upgrading === 1368 1368 1369 1369 1370 -**Error Output** 1371 - 1372 - 1373 -[[image:image-20221122100004-4.png||_mstalt="424606"]] 1374 - 1375 - 1376 1376 ((( 1377 -Some partition is missed during upgrade, please upgrade below four files as example: 1378 - 1379 -[[image:image-20221207120524-2.png]] 1226 +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 1380 1380 ))) 1381 1381 1382 1382 1383 - === 8.3.2 TrackerD's led light isalways GREEN on after upgrading===1230 +[[image:image-20221118105249-3.png]] 1384 1384 1385 1385 1386 - Itisbecausethe partitionsareifferentwhen upgradingversions above 1.4.1,andanew partition file needsto beadded. Pleasereferto the operationsteps in chapter 8.3.11233 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1387 1387 1388 1388 1389 - ===8.3.3"flash read err"afterupgradefirmware===1236 +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 1390 1390 1391 1391 1239 +=== 8.3.3 "flash read err" after upgrade firmware === 1240 + 1392 1392 Error shows below, user might erase the entire flash include u-boot partition which cause this issue. 1393 1393 1243 +[[image:image-20221122100004-1.png||height="497" width="534"]] 1394 1394 1395 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]] 1396 1396 1397 - 1398 1398 User need to upgrade again with below four files to solve this issue. 1399 1399 1400 - [[image:image-20221 207120530-3.png]]1248 + [[image:image-20221122100004-2.png||height="619" width="389"]] 1401 1401 1402 1402 **Figure 2** 1403 1403 1404 1404 1405 -=== 8.3. 4"Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===1253 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware === 1406 1406 1407 - 1408 1408 User might erase the entire flash include keys and default settings which cause this issue. 1409 1409 1410 -After the upgrade is completed, enter **AT+CFG**as shown in the figure below.1257 +After the upgrade is completed, enter AT+CFG as shown in the figure below. 1411 1411 1259 +[[image:image-20221122100004-3.png]] 1412 1412 1413 - [[image:image-20221122100004-3.png||_mstalt="424242"]]1261 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label. 1414 1414 1415 1415 1416 - 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.1264 +Example: 1417 1417 1418 -After AT+FDR. please set 1419 - 1420 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7** 1421 - 1422 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000** 1423 - 1424 -**Example:** 1425 - 1426 -AT+PDOP=7.00 1427 - 1428 -AT+FTIME=180 1429 - 1430 1430 AT+DEUI=70B3D57ED0053981 1431 1431 1432 1432 AT+APPEUI=D23345667BCBCCAF ... ... @@ -1440,6 +1440,13 @@ 1440 1440 AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA) 1441 1441 1442 1442 1279 + 1280 +==== 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 ==== 1281 + 1282 + 1283 +[[image:image-20221122100004-4.png]] 1284 + 1285 + 1443 1443 == 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1444 1444 1445 1445 ... ... @@ -1453,61 +1453,15 @@ 1453 1453 1454 1454 2) Set PDOP to a higher value. 1455 1455 1456 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.)1299 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.) 1457 1457 1458 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces)1301 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces) 1459 1459 1460 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments)1303 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments) 1461 1461 1462 1462 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 1463 1463 1464 1464 1465 -== 8.6 When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets == 1466 - 1467 - 1468 -When upgrading, use the erase button to upgrade 1469 - 1470 -[[image:image-20221207120536-4.png]] 1471 - 1472 - 1473 -The parameters are displayed abnormally and cannot be fixed using AT+FDR 1474 - 1475 -[[image:image-20221128103040-2.png||height="431" width="525"]] 1476 - 1477 - 1478 -Please upgrade these four files,link(The boot_app0 file is in the version folder you need) 1479 - 1480 -[[image:image-20221207134028-8.png]] 1481 - 1482 - 1483 -Reboot information after upgrade 1484 - 1485 -[[image:image-20221128111443-4.png||height="432" width="546"]] 1486 - 1487 - 1488 -Use **AT+FDR** command to reset and then use **AT+CFG** to check whether the configuration is back to normal 1489 - 1490 -[[image:image-20221128111850-5.png]] 1491 - 1492 - 1493 -After the parameters return to normal, upgrade to the version you need again 1494 - 1495 -[[image:image-20221207120601-5.png]] 1496 - 1497 - 1498 -At this point, the parameters return to normal after running AT+FDR again 1499 - 1500 -[[image:image-20221128112035-7.png]] 1501 - 1502 - 1503 -== 8.7 If you encounter the following problems, please upgrade to the latest version == 1504 - 1505 - 1506 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond. 1507 - 1508 -2. Send some commands through the serial port to prompt an error (Example:AT+SMOD=1,0,1) 1509 - 1510 - 1511 1511 = 9. Order Info = 1512 1512 1513 1513 ... ... @@ -1529,9 +1529,7 @@ 1529 1529 1530 1530 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1531 1531 1532 -(% style="display:none" %) (%%) 1533 1533 1534 - 1535 1535 = 10. Packing Info = 1536 1536 1537 1537 ... ... @@ -1547,9 +1547,7 @@ 1547 1547 1548 1548 * Weight: 50g 1549 1549 1550 -(% style="display:none" %) (%%) 1551 1551 1552 - 1553 1553 = 11. Support = 1554 1554 1555 1555 ... ... @@ -1557,9 +1557,7 @@ 1557 1557 1558 1558 * 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]]. 1559 1559 1560 -(% style="display:none" %) (%%) 1561 1561 1562 - 1563 1563 = 12. Reference = 1564 1564 1565 1565 ... ... @@ -1568,6 +1568,3 @@ 1568 1568 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1569 1569 1570 1570 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 1571 - 1572 - 1573 -)))
- 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
- image-20230302145315-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -35.1 KB - Content
- image-20230307135914-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -131.8 KB - Content
- image-20230307135932-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -109.7 KB - Content
- image-20230308115430-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -2.4 MB - Content
- image-20230308115616-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -152.7 KB - Content
- image-20230308115701-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -2.4 MB - Content