Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)
Last modified by Xiaoling on 2023/12/27 09:15
From version 198.1
edited by Bei Jinggeng
on 2023/03/07 14:31
on 2023/03/07 14:31
Change comment:
There is no comment for this version
To version 143.1
edited by Bei Jinggeng
on 2022/11/22 10:04
on 2022/11/22 10:04
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 29 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
Details
- Page properties
-
- Content
-
... ... @@ -1,5 +1,5 @@ 1 1 (% style="text-align:center" %) 2 -[[image:1664505654417-133.png ||_mstalt="293696"]]2 +[[image:1664505654417-133.png]] 3 3 4 4 5 5 ... ... @@ -12,9 +12,9 @@ 12 12 13 13 14 14 15 - 16 16 = 1. Introduction = 17 17 17 + 18 18 == 1.1 What is TrackerD == 19 19 20 20 ... ... @@ -32,17 +32,21 @@ 32 32 ((( 33 33 The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services. 34 34 ))) 35 +))) 35 35 36 36 ((( 37 37 TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network. 39 + 40 + 38 38 ))) 39 39 40 -[[image: image-20230213110119-1.png||height="382" width="834"]]43 +[[image:1664499921684-770.png]] 41 41 42 42 43 43 (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.** 44 44 45 45 49 + 46 46 == 1.2 Specifications == 47 47 48 48 ... ... @@ -119,6 +119,7 @@ 119 119 120 120 = 2. Use TrackerD = 121 121 126 + 122 122 == 2.1 How it works? == 123 123 124 124 ... ... @@ -125,6 +125,7 @@ 125 125 TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA. 126 126 127 127 133 + 128 128 == 2.2 Quick guide to connect to LoRaWAN server == 129 129 130 130 ... ... @@ -131,7 +131,7 @@ 131 131 Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example. 132 132 133 133 134 -[[image: image-20230213110214-2.png||height="388" width="847"]]140 +[[image:1664501652064-326.png]] 135 135 136 136 137 137 ... ... @@ -143,7 +143,7 @@ 143 143 Each TrackerD is shipped with a sticker with the default device EUI as below: 144 144 145 145 146 -[[image:1664501677253-891.png ||_mstalt="296569"]]152 +[[image:1664501677253-891.png]] 147 147 148 148 149 149 Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot: ... ... @@ -152,14 +152,14 @@ 152 152 **__Add APP EUI in the application:__** 153 153 154 154 155 -[[image:1664501711466-918.png ||_mstalt="295828"]]161 +[[image:1664501711466-918.png]] 156 156 157 157 158 158 159 -[[image:1664501721248-725.png ||_mstalt="294450"]]165 +[[image:1664501721248-725.png]] 160 160 161 161 162 -[[image:1664501734705-405.png ||_mstalt="293306"]]168 +[[image:1664501734705-405.png]] 163 163 164 164 165 165 ... ... @@ -166,20 +166,21 @@ 166 166 **__Add APP KEY and DEV EUI:__** 167 167 168 168 169 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1|| _mstalt="298233" alt="1654671889112-678.png"]]175 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]] 170 170 171 171 172 172 173 173 (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device. 174 174 175 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png ||_mstalt="295061"]]181 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]] 176 176 177 -[[image:1664502835802-546.png ||_mstalt="295061"]]183 +[[image:1664502835802-546.png]] 178 178 179 179 180 180 (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server. 181 181 182 182 189 + 183 183 == 2.3 Positioning Mode(SMOD) == 184 184 185 185 ... ... @@ -192,8 +192,10 @@ 192 192 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 193 193 194 194 202 + 195 195 == 2.4 Uplink Payload == 196 196 205 + 197 197 === 2.4.1 Uplink FPORT~=5, Device Status === 198 198 199 199 ... ... @@ -203,10 +203,10 @@ 203 203 204 204 205 205 (% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %) 206 -|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %) 1|=(% style="width: 40px;" %)1215 +|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1 207 207 |=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status 208 208 209 -[[image:1665301570342-765.png ||_mstalt="294580"]]218 +[[image:1665301570342-765.png]] 210 210 211 211 212 212 (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002 ... ... @@ -250,7 +250,7 @@ 250 250 (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40 251 251 252 252 (% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %) 253 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %) 1bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit262 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit 254 254 |=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings 255 255 256 256 (% style="color:blue" %)** SMOD:** ... ... @@ -273,14 +273,14 @@ 273 273 274 274 (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 275 275 276 -(% _mstmutation="1" style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(%_mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)285 +(% style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%) 277 277 278 278 279 279 (% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 280 280 281 -(% border="1.5" style="background-color:#ffffcc; color:green; width: 412.222px" %)282 -|=(% 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 Bit283 -|=(% 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"]]290 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %) 291 +|=(% 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 292 +|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]] 284 284 285 285 === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 286 286 ... ... @@ -300,20 +300,20 @@ 300 300 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 301 301 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 302 302 303 -[[image:1665301636888-168.png ||_mstalt="298012"]]312 +[[image:1665301636888-168.png]] 304 304 305 305 306 306 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== 307 307 308 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:2 79.222px" %)309 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width: 69px" %)163px" %)14310 -|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width: 69px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]]317 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 318 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits 319 +|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 311 311 312 312 ==== (% style="color:blue" %)**FLAG:**(%%) ==== 313 313 314 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:1 83.222px" %)315 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2 52px" %)1316 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width: 52px" %)[[LON>>||anchor="HLON:"]]323 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %) 324 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit 325 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] 317 317 318 318 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 319 319 ... ... @@ -330,12 +330,12 @@ 330 330 2. In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below: 331 331 332 332 333 -[[image:1664502116362-706.png ||_mstalt="293306"]]342 +[[image:1664502116362-706.png]] 334 334 335 335 336 336 3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 337 337 338 -[[image:1664502166010-515.png ||_mstalt="291395"]]347 +[[image:1664502166010-515.png]] 339 339 340 340 341 341 ... ... @@ -358,9 +358,6 @@ 358 358 * 3.40v ~~ 3.69v: 20% ~~ 40% 359 359 * < 3.39v: 0~~20% 360 360 361 -(% style="display:none" %) (%%) 362 - 363 - 364 364 ==== (% style="color:blue" %)**MOD:**(%%) ==== 365 365 366 366 **Example: ** (0x60>>6) & 0x3f =1 ... ... @@ -401,6 +401,7 @@ 401 401 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree// 402 402 403 403 410 + 404 404 === 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) === 405 405 406 406 ... ... @@ -416,13 +416,14 @@ 416 416 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 417 417 418 418 (% class="wikigeneratedid" %) 419 -[[image:1665301687277-443.png ||_mstalt="296140"]]426 +[[image:1665301687277-443.png]] 420 420 421 421 429 + 422 422 === 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 423 423 424 424 425 -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.433 +Set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery. 426 426 427 427 428 428 (% style="color:red" %)**Note for this mode:** ... ... @@ -439,9 +439,10 @@ 439 439 )))|4|4|2|1|1|1|1|1 440 440 |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 441 441 442 -[[image:image-20221009160309-2.png ||_mstalt="429312"]]450 +[[image:image-20221009160309-2.png]] 443 443 444 444 453 + 445 445 === 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 446 446 447 447 ... ... @@ -466,7 +466,7 @@ 466 466 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 467 467 )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 468 468 469 -[[image:1664502425687-834.png ||_mstalt="296738"]]478 +[[image:1664502425687-834.png]] 470 470 471 471 472 472 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). ... ... @@ -477,32 +477,9 @@ 477 477 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 478 478 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 479 479 480 - (%style="display:none"%)(%%)489 +=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 481 481 482 482 483 -=== 2.4.6 Uplink FPORT~=7, Alarm information status(Since firmware 1.4.4) === 484 - 485 - 486 -The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server. 487 - 488 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 489 -|**Size(bytes)**|2|1 490 -|**Value**|[[Alarm & BAT>>path:#HAlarm26BAT:]]|Mod+lon 491 - 492 - [[image:image-20230302145315-1.png]] 493 - 494 -alarm=(bytes[0] & 0x40) ~/~/ Alarm status 495 - 496 -batV=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000; ~/~/ Battery,units:V 497 - 498 -mod = bytes[2] & 0xC0; 499 - 500 -Lon=(bytes[2] & 0x20) 501 - 502 - 503 -=== 2.4.7 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 504 - 505 - 506 506 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. 507 507 508 508 ... ... @@ -515,7 +515,7 @@ 515 515 )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 516 516 517 517 (% class="wikigeneratedid" %) 518 -[[image:1667288597595-714.png|| _mstalt="299598"height="212" width="1151"]]504 +[[image:1667288597595-714.png||height="212" width="1151"]] 519 519 520 520 521 521 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). ... ... @@ -522,21 +522,17 @@ 522 522 * (% style="color:#037691" %)**SSID: **(%%)WiFi name. 523 523 * (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 524 524 525 - (%style="display:none"%)(%%)511 +=== 2.4.7 Add Payload format in TTN V3 === 526 526 527 527 528 -=== 2.4.8 Add Payload format in TTN V3 === 529 - 530 - 531 531 In TTN V3, user can add a custom payload so it shows friendly. 532 532 533 533 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 534 534 535 535 536 -[[image:1664502649601-895.png ||_mstalt="296985"]]519 +[[image:1664502649601-895.png]] 537 537 538 538 539 - 540 540 Add the decoder from this link: 541 541 542 542 [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] ... ... @@ -543,9 +543,10 @@ 543 543 544 544 Save the change the uplink message will be parsed. As below: 545 545 546 -[[image:1664502676891-606.png ||_mstalt="296673"]]528 +[[image:1664502676891-606.png]] 547 547 548 548 531 + 549 549 == 2.5 Integrate with Datacake == 550 550 551 551 ... ... @@ -554,9 +554,10 @@ 554 554 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]] 555 555 556 556 557 -[[image:1664502695771-538.png ||_mstalt="297349"]]540 +[[image:1664502695771-538.png]] 558 558 559 559 543 + 560 560 == 2.6 Integrate with Tago == 561 561 562 562 ... ... @@ -565,45 +565,29 @@ 565 565 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]] 566 566 567 567 568 -[[image:1664502715371-321.png ||_mstalt="292162"]]552 +[[image:1664502715371-321.png]] 569 569 570 570 571 -== 2.7 Integrate with Node-red == 572 572 573 - ~1.Install node-red,pleasereferto the installation method in the link:556 +== 2.7 Datalog Feature == 574 574 575 - [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]] 576 -2. Import the created flow template, please refer to the import method in the link: 577 577 578 - [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]] 579 - The address of the flow template: 580 - 581 - [[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]] 582 - 583 -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 584 - 585 -[[image:image-20230307135914-1.png||height="527" width="1045"]] 586 - 587 -[[image:image-20230307135932-2.png||height="527" width="1044"]] 588 - 589 -== 2.8 Datalog Feature == 590 - 591 - 592 592 total 273 entries,by default, 593 593 594 -User can set [[PNACKMD=1>>||anchor="H3.2.1 1A0AutoSendNone-ACKmessages"]], to enable Datalog feature.561 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 595 595 596 596 Example use case. 597 597 598 -[[image:image-20221009234703-2.png|| _mstalt="429143"height="328" width="899"]]565 +[[image:image-20221009234703-2.png||height="328" width="899"]] 599 599 600 600 601 -[[image:image-20221009234629-1.png|| _mstalt="431145"height="390" width="577"]]568 +[[image:image-20221009234629-1.png||height="390" width="577"]] 602 602 603 603 604 -== 2.9 Alarm Mode == 605 605 572 +== 2.8 Alarm Mode == 606 606 574 + 607 607 ((( 608 608 User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 609 609 ))) ... ... @@ -615,7 +615,7 @@ 615 615 616 616 617 617 ((( 618 - **Two ways to exit alarm mode:**586 +Two ways to exit alarm mode: 619 619 ))) 620 620 621 621 * Server sends a downlink command to exit. ... ... @@ -626,21 +626,17 @@ 626 626 ))) 627 627 628 628 629 -== 2.10 Transport Mode == 630 630 598 +== 2.9 Transport Mode == 631 631 600 + 632 632 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. 633 633 634 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation. 635 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic. 636 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion. 637 637 638 -(% style="display:none" %) (%%) 639 639 605 +== 2.10 LED Status == 640 640 641 -== 2.11 LED Status == 642 642 643 - 644 644 (% border="1.5" style="background-color:#ffffcc; width:500px" %) 645 645 |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 646 646 |(% 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 ... ... @@ -655,15 +655,12 @@ 655 655 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 656 656 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 657 657 658 - (%style="display:none"%) (%%)622 +== 2.11 Button Function == 659 659 660 660 661 -== 2.12 Button Function == 662 - 663 - 664 664 (% style="color:blue" %)**RESET button:** 665 665 666 -[[image:1664502835802-546.png ||_mstalt="295061"]]627 +[[image:1664502835802-546.png]] 667 667 668 668 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server. 669 669 ... ... @@ -670,9 +670,8 @@ 670 670 671 671 (% style="color:red" %)**RED button:** 672 672 673 -[[image: image-20230213110506-3.png]](% style="display:none" %)634 +[[image:1664502854406-763.png]] 674 674 675 -(% style="display:none" %) (%%) 676 676 677 677 (% border="1" style="background-color:#ffffcc; width:510px" %) 678 678 |=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description** ... ... @@ -680,12 +680,9 @@ 680 680 |(% 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 681 681 |(% 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. 682 682 683 - (%style="display:none"%) (%%)643 +== 2.12 USB Port Function == 684 684 685 685 686 -== 2.13 USB Port Function == 687 - 688 - 689 689 The USB interface of TrackerD has below functions: 690 690 691 691 * Power on the device ... ... @@ -693,9 +693,6 @@ 693 693 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 694 694 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 695 695 696 -(% style="display:none" %) (%%) 697 - 698 - 699 699 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 700 700 701 701 ... ... @@ -704,6 +704,7 @@ 704 704 LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] 705 705 706 706 661 + 707 707 == 3.1 Access AT Command == 708 708 709 709 ... ... @@ -710,24 +710,25 @@ 710 710 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. 711 711 712 712 713 -[[image:1664502999401-486.png ||_mstalt="296985"]]668 +[[image:1664502999401-486.png]] 714 714 715 715 716 716 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: 717 717 718 718 719 -[[image:1664503022490-662.png ||_mstalt="293332"]]674 +[[image:1664503022490-662.png]] 720 720 721 721 722 -[[image:1664503035713-500.png ||_mstalt="291096"]]677 +[[image:1664503035713-500.png]] 723 723 724 724 725 -[[image:1664503047675-651.png ||_mstalt="295386"]]680 +[[image:1664503047675-651.png]] 726 726 727 -(% style="display:none" %) (%%) 728 728 683 + 729 729 == 3.2 Command Set == 730 730 686 + 731 731 === 3.2.1 Set Transmit Interval === 732 732 733 733 ... ... @@ -745,6 +745,7 @@ 745 745 (% style="color:#037691" %)**0x01 00 01 2C** (%%) ~/~/ Same as AT+TDC=300000 746 746 747 747 704 + 748 748 === 3.2.2 Set Alarm Packet transmission interval === 749 749 750 750 ... ... @@ -762,6 +762,7 @@ 762 762 (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/ Same as AT+ATDC=60000 763 763 764 764 722 + 765 765 === 3.2.3 Set Transport Mode Packet transmission interval === 766 766 767 767 ... ... @@ -779,6 +779,7 @@ 779 779 (% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+MTDC=3000000 780 780 781 781 740 + 782 782 === 3.2.4 Exit Alarm === 783 783 784 784 ... ... @@ -791,9 +791,10 @@ 791 791 (% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 792 792 793 793 794 -=== 3.2.5 Disable/Enable LED flash and buzzer === 795 795 754 +=== 3.2.5 Disable/Enable LED flash === 796 796 756 + 797 797 Disable/Enable LED for position, downlink and uplink 798 798 799 799 * (% style="color:blue" %)**AT Command:** ... ... @@ -808,6 +808,7 @@ 808 808 (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/ Same as AT+LON=0 809 809 810 810 771 + 811 811 === 3.2.6 Disable/Enable Transport Mode === 812 812 813 813 ... ... @@ -825,6 +825,7 @@ 825 825 (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+INTWK=1 826 826 827 827 789 + 828 828 === 3.2.7 Set Positioning Mode === 829 829 830 830 ... ... @@ -851,9 +851,9 @@ 851 851 852 852 (% style="color:#037691" %)**cc: ** 853 853 854 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State816 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 855 855 856 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((%_mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))818 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%)) 857 857 858 858 (% style="color:blue" %)**Example:** 859 859 ... ... @@ -871,6 +871,7 @@ 871 871 (% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+SMOD=1,0,0 872 872 873 873 836 + 874 874 === 3.2.8 Set MAX GPS position time === 875 875 876 876 ... ... @@ -877,7 +877,7 @@ 877 877 Set max positioning time, default is 150 seconds. TrackerD will try to get location info within this period. If fail to get position data within this time, TrackerD will use 000000 for latitude and longitude. 878 878 879 879 880 -If **AT+FTIME=0**. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.843 +If AT+FTIME=0. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink. 881 881 882 882 883 883 * (% style="color:blue" %)**AT Command:** ... ... @@ -892,6 +892,7 @@ 892 892 (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/ Set AT+FTIME=150 893 893 894 894 858 + 895 895 === 3.2.9 Set PDOP value for GPS fix accuracy === 896 896 897 897 ... ... @@ -915,8 +915,8 @@ 915 915 (% style="color:#037691" %)**0xAD 00 46** (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7) 916 916 917 917 918 -=== 3.2.10 Disable/Enable the confirmation mode === 919 919 883 +Disable/Enable the confirmation mode 920 920 921 921 * (% style="color:blue" %)**AT Command:** 922 922 ... ... @@ -935,9 +935,10 @@ 935 935 (% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1 936 936 937 937 938 -=== 3.2.11 Auto Send None-ACK messages === 939 939 903 +=== 3.2.10 Auto Send None-ACK messages === 940 940 905 + 941 941 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. 942 942 943 943 ... ... @@ -953,12 +953,13 @@ 953 953 954 954 * (% style="color:blue" %)**Downlink Command: 0x34** 955 955 956 -Example: 0x34 921 +Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 957 957 958 958 959 -=== 3.2.12 Set BLEMASK to filter BLE iBeacon === 960 960 925 +=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 961 961 927 + 962 962 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. 963 963 964 964 (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.** ... ... @@ -965,18 +965,19 @@ 965 965 966 966 (% style="color:blue" %)**AT Command:** 967 967 968 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456934 + (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 969 969 970 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK936 + (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 971 971 972 972 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 973 973 974 -Example: 0xB2 940 +Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 975 975 976 976 977 -=== 3.2.13 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 978 978 944 +=== 3.2.12 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 979 979 946 + 980 980 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. 981 981 982 982 (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.** ... ... @@ -983,61 +983,44 @@ 983 983 984 984 (% style="color:blue" %)**AT Command:** 985 985 986 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456953 + (% style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456 987 987 988 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK955 + (% style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK 989 989 990 990 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)** 991 991 992 -Example: 0xB3 959 +Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 993 993 994 994 995 -=== 3.2.14 Disable/Enable Information printing(Since firmware 1.4.1) === 996 996 963 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 997 997 965 + 998 998 Users can use this feature to enable/disable Information printing. 999 999 1000 1000 (% style="color:blue" %)**AT Command:** 1001 1001 1002 -(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/ 970 +(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/(Disable (0), Enable (1), default:0) 1003 1003 \\Example: AT+SHOWID=1 ~-~-> Enable Information printing. 1004 1004 1005 1005 1006 -=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 1007 1007 975 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 1008 1008 977 + 1009 1009 The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. 1010 1010 1011 1011 (% style="color:blue" %)**AT Command:** 1012 1012 1013 -(% style="color:#037691" %)**AT+CHE=1 982 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode 1014 1014 1015 1015 1016 1016 (% style="color:blue" %)**Downlink Payload:0X24** 1017 1017 1018 -Example: 0x24 01 987 +Example: 0x24 01 ~/~/ Same as AT+CHE=1 1019 1019 1020 1020 1021 -=== 3.2.16 Get or Set Threshold for motion detect(Since firmware 1.4.3) === 1022 1022 1023 - 1024 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event. 1025 - 1026 -(% style="color:blue" %)**AT Command:** 1027 - 1028 -(% style="color:#037691" %)**AT+PT=xx** 1029 - 1030 - Example: 1031 - 1032 - AT+PT=14 ~-~-> Set to detect car motion. 1033 - 1034 - AT+PT=41 ~-~-> set to detect walk motion. 1035 - 1036 - 1037 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%) 1038 -0xB4 14 ~/~/ Same as AT+PT=14 1039 - 1040 - 1041 1041 = 4. Setting for Different Scenarios = 1042 1042 1043 1043 ... ... @@ -1044,6 +1044,7 @@ 1044 1044 1045 1045 = 5. Upload Firmware = 1046 1046 997 + 1047 1047 == 5.1 Firmware Change Log == 1048 1048 1049 1049 ... ... @@ -1050,6 +1050,7 @@ 1050 1050 **[[See this link>>url:https://github.com/dragino/TrackerD]]** 1051 1051 1052 1052 1004 + 1053 1053 == 5.2 How to upgrade firmware == 1054 1054 1055 1055 ... ... @@ -1070,10 +1070,10 @@ 1070 1070 (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32 1071 1071 1072 1072 1073 -[[image:1664503563660-578.png ||_mstalt="296777"]]1025 +[[image:1664503563660-578.png]] 1074 1074 1075 1075 1076 -[[image:1664503574618-659.png ||_mstalt="297986"]]1028 +[[image:1664503574618-659.png]] 1077 1077 1078 1078 1079 1079 ... ... @@ -1082,7 +1082,7 @@ 1082 1082 [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]] 1083 1083 1084 1084 1085 - **Users need to use below files:**1037 +Users need to use below files: 1086 1086 1087 1087 boot_app0.bin @0e000 1088 1088 ... ... @@ -1089,19 +1089,22 @@ 1089 1089 US915.bin @ 0x10000(Select the bin file of the frequency band you need) 1090 1090 1091 1091 1092 -[[image:image-20221 207120501-1.png]]1044 +[[image:image-20221118105220-2.png]] 1093 1093 1094 1094 1095 1095 1096 1096 After upgrade finish, it will show finish as below: 1097 1097 1098 -[[image:image-20221 207133911-7.png]]1050 +[[image:image-20221118105402-4.png]] 1099 1099 1100 1100 1053 + 1101 1101 = 6. Developer Guide = 1102 1102 1056 + 1103 1103 == 6.1 Compile Source Code == 1104 1104 1059 + 1105 1105 === 6.1.1 Set up ARDUINO compile environment === 1106 1106 1107 1107 ... ... @@ -1110,81 +1110,24 @@ 1110 1110 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]] 1111 1111 1112 1112 1113 -[[image:1664503635019-941.png ||_mstalt="294658"]]1068 +[[image:1664503635019-941.png]] 1114 1114 1115 1115 1116 1116 1117 1117 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 1118 1118 1119 -[[image:1664503715811-892.png ||_mstalt="295698"]]1074 +[[image:1664503715811-892.png]] 1120 1120 1121 1121 1122 -=== 6.1.2 Build the development environment === 1123 - 1124 - 1125 -**~1. Download and install arduino IDE** 1126 - 1127 -[[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]] 1128 - 1129 - 1130 -**2. Download the ESP32 development package in the arduino IDE** 1131 - 1132 -[[image:image-20221213100007-1.png]] 1133 - 1134 - 1135 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]] 1136 - 1137 -[[image:image-20221213100626-2.png]] 1138 - 1139 - 1140 -Restart the IDE after the addition is complete, then: 1141 - 1142 -[[image:image-20221213100808-3.png||height="679" width="649"]] 1143 - 1144 - 1145 -[[image:image-20221213101040-4.png]] 1146 - 1147 - 1148 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03. 1149 -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)** 1150 - 1151 - 1152 -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: 1153 - 1154 -(% style="color:blue" %)**Methods as below:** 1155 - 1156 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]] 1157 - 1158 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here. 1159 - 1160 1160 (% 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. 1161 1161 1162 -[[image:image-2022121 3102311-5.png||height="582" width="711"]]1079 +[[image:image-20221024105643-1.png]] 1163 1163 1164 - 1165 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)** 1166 - 1167 -[[image:image-20221213102334-6.png]] 1168 - 1169 -(% style="color:red" %)**Note: This step requires a python environment** 1170 - 1171 - 1172 -Either way, in the end: 1173 - 1174 -The final effect is to open the arduino and you can see the esp32 1175 - 1176 -[[image:image-20221213110952-8.png||height="866" width="711"]] 1177 - 1178 - 1179 - 1180 -[[image:image-20221024105643-1.png||_mstalt="428129"]] 1181 - 1182 1182 **~ Figure1** 1183 1183 1184 1184 1084 +[[image:image-20221024105643-2.png]] 1185 1185 1186 -[[image:image-20221024105643-2.png||_mstalt="428493"]] 1187 - 1188 1188 **Figure2** 1189 1189 1190 1190 ... ... @@ -1193,31 +1193,34 @@ 1193 1193 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: 1194 1194 1195 1195 1196 -[[image:1664503752288-974.png ||_mstalt="298194"]]1094 +[[image:1664503752288-974.png]] 1197 1197 1198 1198 1097 + 1199 1199 == 6.2 Source Code == 1200 1200 1201 1201 1202 1202 * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:** 1203 1203 1204 -[[image:1664503794261-827.png ||_mstalt="296387"]]1103 +[[image:1664503794261-827.png]] 1205 1205 1206 1206 1207 1207 1208 1208 * (% style="color:blue" %)**Click to upload** 1209 1209 1210 -[[image:1664503808294-336.png ||_mstalt="295711"]]1109 +[[image:1664503808294-336.png]] 1211 1211 1212 1212 1213 1213 1214 1214 * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 1215 1215 1216 -[[image:1664503824081-592.png ||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]1115 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 1217 1217 1218 1218 1118 + 1219 1219 = 7. FAQ = 1220 1220 1121 + 1221 1221 == 7.1 How to change the LoRa Frequency Bands/Region? == 1222 1222 1223 1223 ... ... @@ -1224,10 +1224,11 @@ 1224 1224 User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download. 1225 1225 1226 1226 1128 + 1227 1227 == 7.2 What is the pin mapping for the USB program cable? == 1228 1228 1229 1229 1230 -[[image:1664499635206-262.png ||_mstalt="295360"]]1132 +[[image:1664499635206-262.png]] 1231 1231 1232 1232 1233 1233 ... ... @@ -1242,11 +1242,9 @@ 1242 1242 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 1243 1243 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 1244 1244 1245 -(% style="display:none" %) (%%) 1246 - 1247 - 1248 1248 == 7.3 Notes on using different serial port tools for TrackerD == 1249 1249 1149 + 1250 1250 === 7.3.1 Serial port utility === 1251 1251 1252 1252 ... ... @@ -1254,16 +1254,18 @@ 1254 1254 1255 1255 Need to adjust the data stream to RTS/CTS on physical restart. 1256 1256 1157 + 1257 1257 (% class="wikigeneratedid" %) 1258 -[[image:image-20221102140621-1.png ||_mstalt="425672"]]1159 +[[image:image-20221102140621-1.png]] 1259 1259 1260 1260 1261 - 1262 1262 When using AT commands, the data flow needs to be adjusted to XON/XOFF 1263 1263 1264 -[[image:image-20221102140638-2.png||_mstalt="428727"]] 1265 1265 1165 +[[image:image-20221102140638-2.png]] 1266 1266 1167 + 1168 + 1267 1267 === 7.3.2 SecureCRT === 1268 1268 1269 1269 ... ... @@ -1270,22 +1270,23 @@ 1270 1270 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. 1271 1271 1272 1272 1273 -[[image:image-20221102140704-3.png ||_mstalt="427076"]]1175 +[[image:image-20221102140704-3.png]] 1274 1274 1275 1275 1276 -[[image:image-20221102140712-4.png ||_mstalt="427089"]]1178 +[[image:image-20221102140712-4.png]] 1277 1277 1278 1278 1181 + 1279 1279 === 7.3.3 PUTTY === 1280 1280 1281 1281 1282 -[[image:image-20221102140748-5.png ||_mstalt="430456"]]1185 +[[image:image-20221102140748-5.png]] 1283 1283 1284 1284 1285 1285 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. 1286 1286 1287 1287 1288 -[[image:image-20221102140801-6.png ||_mstalt="427466"]]1191 +[[image:image-20221102140801-6.png]] 1289 1289 1290 1290 1291 1291 == 7.4 How to modify source code to compile different frequency band bin file? == ... ... @@ -1297,52 +1297,38 @@ 1297 1297 See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]] 1298 1298 ))) 1299 1299 1300 - **~1.**1203 +1.When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file. 1301 1301 1205 +[[image:image-20221116111844-1.png||height="227" width="782"]] 1302 1302 1303 - [[image:image-20221116111844-1.png||_mstalt="428688"height="227"width="782"]]1207 +2.Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except). 1304 1304 1209 +[[image:image-20221116111844-2.png||height="262" width="781"]] 1305 1305 1211 +3.Compile the AS923_JP band, please refer to the intention shown 1306 1306 1307 - **2. Open LMIC_PROJECT_CONFIG.H, find the correspondingmacro definitionand open it(AS923_2,AS923_3,AS923_4except).**1213 +[[image:image-20221116111844-3.png||height="338" width="746"]] 1308 1308 1215 +4.In other frequency bands in AS923, you need to find Lorabase_as923.H, path arduino-lmic \ src \ lmic, as shown in the figure below. 1309 1309 1310 -[[image:image-20221116111844- 2.png||_mstalt="429052"height="262" width="781"]]1217 +[[image:image-20221116111844-4.png||height="641" width="739"]] 1311 1311 1219 +[[image:image-20221116111844-5.png||height="551" width="708"]] 1312 1312 1313 1313 1314 -**3. Compile the AS923_JP band, please refer to the intention shown** 1315 1315 1316 - 1317 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]] 1318 - 1319 - 1320 - 1321 -**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.** 1322 - 1323 - 1324 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]] 1325 - 1326 - 1327 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]] 1328 - 1329 - 1330 -== 7.5 Are there example python example for BLE Indoor Positioning? == 1331 - 1332 - 1333 -[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]] 1334 - 1335 - 1336 1336 = 8 Trouble Shooting = 1337 1337 1225 + 1338 1338 == 8.1 TDC is changed to 4294947296 and cause no uplink. == 1339 1339 1340 1340 1341 1341 ((( 1342 -Before firmware v1.4.0: When the Transport Mode is enabled ( (% style="color:blue" %)**AT+INTWK=1**(%%)), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.11230 +Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1 1343 1343 ))) 1344 1344 1345 1345 1234 + 1346 1346 == 8.2 Device not able get AT Command or show output after wake up from deep sleep mode == 1347 1347 1348 1348 ... ... @@ -1351,152 +1351,85 @@ 1351 1351 ))) 1352 1352 1353 1353 1243 + 1354 1354 == 8.3 Problem after Upgrading Firmware == 1355 1355 1356 -=== 8.3.1 "rst: (0x3 SW_RESET)" andContinue Restart after upgrading ===1246 +=== 8.3.1 Continue Restart after upgrading === 1357 1357 1358 1358 1359 -**Error Output** 1360 - 1361 - 1362 -[[image:image-20221122100004-4.png||_mstalt="424606"]] 1363 - 1364 - 1365 1365 ((( 1366 -Some partition is missed during upgrade, please upgrade below four files as example: 1367 - 1368 -[[image:image-20221207120524-2.png]] 1250 +If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure 1369 1369 ))) 1370 1370 1371 1371 1372 - === 8.3.2 TrackerD's led light isalways GREEN on after upgrading===1254 +[[image:image-20221118105249-3.png]] 1373 1373 1374 1374 1257 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1258 + 1375 1375 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 1376 1376 1377 1377 1378 -=== 8.3. 3"flashread err"afterupgradefirmware ===1262 +==== 8.3.2.1 If there is a situation in Figure 1,and a new partition file and bootloader file needs to be added. Please refer to the operation steps in Figure 2 ==== 1379 1379 1264 +[[image:image-20221122100004-1.png||height="497" width="534"]] 1380 1380 1381 - Errorshowsbelow,usermighterasetheentireflashincludeu-bootpartitionwhichcausethisissue.1266 + Figure 1 1382 1382 1268 + [[image:image-20221122100004-2.png||height="619" width="389"]] 1383 1383 1384 - [[image:image-20221122100004-1.png||_mstalt="423514"height="497" width="534"]]1270 + Figure 2 1385 1385 1272 +After the upgrade is completed, enter AT+CFG as shown in the figure below. 1386 1386 1387 - User need to upgradeain with below four files to solve this issue.1274 +[[image:image-20221122100004-3.png]] 1388 1388 1389 - [[image:image-20221207120530-3.png]]1276 +Please AT+FDR, and then enter the following instructions by the information on the label 1390 1390 1391 - **Figure 2**1278 +AT+DEUI=70B3D57ED0053981 1392 1392 1393 - 1394 -=== 8.3.4 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware === 1395 - 1396 - 1397 -User might erase the entire flash include keys and default settings which cause this issue. 1398 - 1399 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below. 1400 - 1401 - 1402 -[[image:image-20221122100004-3.png||_mstalt="424242"]] 1403 - 1404 - 1405 -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. 1406 - 1407 -After AT+FDR. please set 1408 - 1409 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7** 1410 - 1411 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000** 1412 - 1413 -**Example:** 1414 - 1415 -AT+PDOP=7.00 1416 - 1417 -AT+FTIME=180 1418 - 1419 -AT+DEUI=70B3D57ED0053981 1420 - 1421 1421 AT+APPEUI=D23345667BCBCCAF 1422 1422 1423 1423 AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1 1424 1424 1425 -AT+DADDR=260b4dce ( no need for OTAA)1284 +AT+DADDR=260b4dce 1426 1426 1427 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d ( no need for OTAA)1286 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d 1428 1428 1429 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA)1288 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 1430 1430 1431 1431 1432 -== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1433 1433 1292 +==== 8.3.2.2 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ==== 1434 1434 1435 - Pleasedownload version1.4.2 again1294 +[[image:image-20221122100004-4.png]] 1436 1436 1296 +== == 1437 1437 1438 -== 8. 5Howtodealwith unsuccessfulGPS positioning?==1298 +== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1439 1439 1300 +Please download version 1.4.2 again 1440 1440 1441 -1) Make Sure the device is in Open Area where can see the sky. 1442 1442 1303 +((( 1304 +== 8.5 How to deal with unsuccessful GPS positioning? == 1305 + 1306 +1) Make Sure the device is in Open Area where can see the sky. 1443 1443 2) Set PDOP to a higher value. 1444 1444 1445 - *(%_mstmutation="1"style="color:blue"%)**AT+PDOP=2**(%%)(can be positioned precisely.)1309 + AT+PDOP=2(can be positioned precisely.) 1446 1446 1447 - *(%_mstmutation="1"style="color:blue"%)**AT+PDOP=7**(%%)(Quickly locate in open spaces)1311 + AT+PDOP=7(Quickly locate in open spaces) 1448 1448 1449 - *(%_mstmutation="1"style="color:blue"%)**AT+PDOP=14.7**(%%)(Positioning can be acquired in complex environments)1313 + AT+PDOP=14.7(Positioning can be acquired in complex environments) 1450 1450 1451 1451 Please refer to this [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H3.2.9SetPDOPvalueforGPSfixaccuracy]] on how to set up PDOP 1316 +))) 1452 1452 1453 1453 1454 -== 8.6Whenupgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets==1319 +== == 1455 1455 1456 1456 1457 -When upgrading, use the erase button to upgrade 1458 - 1459 -[[image:image-20221207120536-4.png]] 1460 - 1461 - 1462 -The parameters are displayed abnormally and cannot be fixed using AT+FDR 1463 - 1464 -[[image:image-20221128103040-2.png||height="431" width="525"]] 1465 - 1466 - 1467 -Please upgrade these four files,link(The boot_app0 file is in the version folder you need) 1468 - 1469 -[[image:image-20221207134028-8.png]] 1470 - 1471 - 1472 -Reboot information after upgrade 1473 - 1474 -[[image:image-20221128111443-4.png||height="432" width="546"]] 1475 - 1476 - 1477 -Use **AT+FDR** command to reset and then use **AT+CFG** to check whether the configuration is back to normal 1478 - 1479 -[[image:image-20221128111850-5.png]] 1480 - 1481 - 1482 -After the parameters return to normal, upgrade to the version you need again 1483 - 1484 -[[image:image-20221207120601-5.png]] 1485 - 1486 - 1487 -At this point, the parameters return to normal after running AT+FDR again 1488 - 1489 -[[image:image-20221128112035-7.png]] 1490 - 1491 - 1492 -== 8.7 If you encounter the following problems, please upgrade to the latest version == 1493 - 1494 - 1495 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond. 1496 - 1497 -2. Send some commands through the serial port to prompt an error (Example:AT+SMOD=1,0,1) 1498 - 1499 - 1500 1500 = 9. Order Info = 1501 1501 1502 1502 ... ... @@ -1505,22 +1505,13 @@ 1505 1505 (% style="color:blue" %)**XXX**(%%): The default frequency band 1506 1506 1507 1507 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433 1508 - 1509 1509 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868 1510 - 1511 1511 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865 1512 - 1513 1513 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920 1514 - 1515 1515 * (% style="color:red" %)**AS923**(%%): Default frequency band AS923 1516 - 1517 1517 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 1518 - 1519 1519 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1520 1520 1521 -(% style="display:none" %) (%%) 1522 - 1523 - 1524 1524 = 10. Packing Info = 1525 1525 1526 1526 ... ... @@ -1527,36 +1527,22 @@ 1527 1527 (% style="color:#037691" %)**Package Includes**: 1528 1528 1529 1529 * TrackerD LoRaWAN GPS/BLE Tracker x 1 1530 - 1531 1531 * USB recharge & program cable x 1 1532 1532 1533 1533 (% style="color:#037691" %)**Dimensions and Weight**: 1534 1534 1535 1535 * Device Size: 85 x 48 x 15 mm 1536 - 1537 1537 * Weight: 50g 1538 1538 1539 -(% style="display:none" %) (%%) 1540 - 1541 - 1542 1542 = 11. Support = 1543 1543 1544 1544 1545 1545 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 1546 - 1547 1547 * 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]]. 1548 1548 1549 -(% style="display:none" %) (%%) 1550 - 1551 - 1552 1552 = 12. Reference = 1553 1553 1554 1554 1555 1555 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1556 - 1557 1557 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1558 - 1559 1559 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 1560 - 1561 - 1562 -)))
- 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