Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Bei Jinggeng on 2025/08/01 17:45
From version 76.1
edited by Edwin Chen
on 2022/10/13 23:11
on 2022/10/13 23:11
Change comment:
There is no comment for this version
To version 145.1
edited by Edwin Chen
on 2022/11/22 12:21
on 2022/11/22 12:21
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 23 added, 0 removed)
- 1667288597595-714.png
- image-20221024105643-1.png
- image-20221024105643-2.png
- image-20221102140621-1.png
- image-20221102140638-2.png
- image-20221102140704-3.png
- image-20221102140712-4.png
- image-20221102140748-5.png
- image-20221102140801-6.png
- image-20221107145243-1.png
- image-20221116111844-1.png
- image-20221116111844-2.png
- image-20221116111844-3.png
- image-20221116111844-4.png
- image-20221116111844-5.png
- image-20221118104359-1.png
- image-20221118105220-2.png
- image-20221118105249-3.png
- image-20221118105402-4.png
- image-20221122100004-1.png
- image-20221122100004-2.png
- image-20221122100004-3.png
- image-20221122100004-4.png
Details
- Page properties
-
- Content
-
... ... @@ -14,7 +14,6 @@ 14 14 15 15 = 1. Introduction = 16 16 17 - 18 18 == 1.1 What is TrackerD == 19 19 20 20 ... ... @@ -46,7 +46,6 @@ 46 46 (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.** 47 47 48 48 49 - 50 50 == 1.2 Specifications == 51 51 52 52 ... ... @@ -121,9 +121,8 @@ 121 121 * Logistics and Supply Chain Management 122 122 * Human tracking 123 123 124 -= 2. 1122 += 2. Use TrackerD = 125 125 126 - 127 127 == 2.1 How it works? == 128 128 129 129 ... ... @@ -130,7 +130,6 @@ 130 130 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. 131 131 132 132 133 - 134 134 == 2.2 Quick guide to connect to LoRaWAN server == 135 135 136 136 ... ... @@ -172,34 +172,34 @@ 172 172 **__Add APP KEY and DEV EUI:__** 173 173 174 174 175 -[[image:16 64501784668-703.png]]171 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]] 176 176 177 177 178 178 175 +(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device. 179 179 180 -(% style=" color:blue" %)**Step2**:(%%) Power on TrackerD by usingtheon board switch.177 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]] 181 181 179 +[[image:1664502835802-546.png]] 182 182 181 + 183 183 (% 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. 184 184 185 185 186 - 187 187 == 2.3 Positioning Mode(SMOD) == 188 188 189 189 190 190 Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 191 191 192 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%) only get and uplink GPS location info.193 -* (% style="color:#037691" %)**BLE ONLY: 194 -* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 190 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 191 +* (% style="color:#037691" %)**BLE or WiFi ONLY: **(%%)** **Only obtain iBeacon info via BLE and uplink or obtain wifi ssid info via WiFi and uplink. Design for Indoor tracking. 192 +* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking. Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 195 195 196 196 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 197 197 198 198 199 - 200 200 == 2.4 Uplink Payload == 201 201 202 - 203 203 === 2.4.1 Uplink FPORT~=5, Device Status === 204 204 205 205 ... ... @@ -208,8 +208,8 @@ 208 208 Use can also get the Device Status uplink through the downlink command: **Downlink: 0x2301** 209 209 210 210 211 -(% border="1.5" style="background-color:#ffffcc; color:green; width: 520px" %)212 -|=(% s cope="row" style="width:108px;" %)**Size(bytes)**|=(% style="width:82px;" %)**1**|=(% style="width:83px;" %)**2**|=(% style="width:94px;" %)**1**|=(% style="width:84px;" %)**1**|=(% style="width:44px;" %)2|=(% style="width:63px;" %)**2**|=(% style="width:60px;" %)1207 +(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %) 208 +|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1 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 215 [[image:1665301570342-765.png]] ... ... @@ -253,12 +253,11 @@ 253 253 Use can also get the Device Status uplink through the downlink command: 254 254 255 255 256 - 257 257 (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40 258 258 259 -(% border="1.5" style="background-color:#ffffcc; color:green; width: 420px" %)260 -|(% style="width: 75px" %)**Size(bit)**|(% style="width:64px" %)2bits|(% style="width:137px" %)2bit|(% style="width:142px" %)4bit261 -|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:1 37px" %)GPS_Settings|(% style="width:142px" %)BLE_Settings254 +(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %) 255 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit 256 +|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings 262 262 263 263 (% style="color:blue" %)** SMOD:** 264 264 ... ... @@ -280,29 +280,27 @@ 280 280 281 281 (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 282 282 278 +(% style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%) 283 283 284 284 285 285 (% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 286 286 287 -(% border="1.5" style="background-color:#ffffcc; color:green; width: 450px" %)288 -|(% style="width: 77px" %)**Size(bit)**|(% style="width:82px" %)5 Bits|(% style="width:106px" %)1 Bit|(% style="width:67px" %)1 Bit|(% style="width:121px" %)1 Bit289 -|(% style="width:77px" %)**Value**|(% style="width: 82px" %)Reserve|(% style="width:106px" %)PNACKMD|(% style="width:67px" %)LON|(% style="width:121px" %)Transport****Mode283 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %) 284 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit 285 +|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]] 290 290 291 - 292 - 293 - 294 294 === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 295 295 296 296 297 -User can use **AT+SMOD=1,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes, please note that 15 bytes won't work on DR0 on US915/AU915 frequency band.290 +Users can use **AT+SMOD=1,0,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes, 298 298 299 299 300 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width: 480px" %)301 -|=(% scope="row" style="width: 50px;" %)(((293 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %) 294 +|=(% scope="row" style="width: 60px;" %)((( 302 302 **Size(bytes)** 303 -)))|(% style="width: 60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((296 +)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)((( 304 304 2 305 -)))|(% style="width: 87px" %)(((298 +)))|(% style="width:30px" %)((( 306 306 2 307 307 ))) 308 308 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( ... ... @@ -320,8 +320,8 @@ 320 320 321 321 ==== (% style="color:blue" %)**FLAG:**(%%) ==== 322 322 323 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:2 50px" %)324 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width: 50px" %)2bits|(% style="width:50px" %)1bit316 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %) 317 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit 325 325 |=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] 326 326 327 327 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A ... ... @@ -369,7 +369,7 @@ 369 369 370 370 ==== (% style="color:blue" %)**MOD:**(%%) ==== 371 371 372 -**Example: ** (0x60>>6)& 0x3f =1 .365 +**Example: ** (0x60>>6) & 0x3f =1 373 373 374 374 **Set the format of GPS data uplink link:** 375 375 ... ... @@ -397,7 +397,6 @@ 397 397 ))) 398 398 399 399 400 - 401 401 ==== (% style="color:blue" %)**Hum:**(%%) ==== 402 402 403 403 0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree ... ... @@ -408,17 +408,16 @@ 408 408 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree// 409 409 410 410 411 - 412 412 === 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) === 413 413 414 414 415 -The default uplink payload includes total ly11 bytes. The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)406 +The default uplink payload includes total 11 bytes (**AT+SMOD=1,1,0**). The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity) 416 416 417 417 418 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width: 480px" %)419 -|=(% scope="row" style="width: 50px;" %)(((409 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %) 410 +|=(% scope="row" style="width: 60px;" %)((( 420 420 **Size(bytes)** 421 -)))|(% style="width:60px" %)4|(% style="width: 70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1412 +)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1 422 422 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 423 423 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 424 424 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] ... ... @@ -427,21 +427,21 @@ 427 427 [[image:1665301687277-443.png]] 428 428 429 429 430 - 431 431 === 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 432 432 433 433 434 -Set [[PNACKMD=1>> url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/#H4.13AutoSendNone-ACKmessages]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.424 +Set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery. 435 435 436 436 437 437 (% style="color:red" %)**Note for this mode:** 438 438 439 439 * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server. 440 -* b) TrackerD will send data in (% style="color:blue" %)**CONFIRMED Mode**(%%) when PNACKMD=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages. 430 +* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages. 431 +* c) the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes of payload. In this case (DR0 of US915/AU915), the payload on server will show NULL 441 441 442 442 The payload is 15 bytes, as below. 443 443 444 -(% border="1.5" style="background-color:#ffffcc; color:green; width:5 20px" %)435 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 445 445 |=(% scope="row" %)((( 446 446 **Size(bytes)** 447 447 )))|4|4|2|1|1|1|1|1 ... ... @@ -450,10 +450,14 @@ 450 450 [[image:image-20221009160309-2.png]] 451 451 452 452 453 - 454 454 === 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 455 455 456 456 447 +TrackerD supports BLE scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan BLE iBeacon and find the strongest iBeacon info and uplink. 448 + 449 +User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings. 450 + 451 + 457 457 (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 458 458 |=(% scope="row" style="width: 60px;" %)((( 459 459 **Size(bytes)** ... ... @@ -473,20 +473,41 @@ 473 473 [[image:1664502425687-834.png]] 474 474 475 475 476 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 471 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 477 477 * (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 478 478 * (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 479 479 * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. 480 -* (% style="color:#037691" %)**MINOR:** (%%)The M AJOR475 +* (% style="color:#037691" %)**MINOR:** (%%)The MINOR from the strongest iBeacon. 481 481 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 482 482 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 483 483 479 +=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 484 484 485 -=== 2.4.6 Add Payload format in TTN V3 === 486 486 482 +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. 487 487 488 -In TTN V3, use can add a custom payload so it shows friendly. 489 489 485 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %) 486 +|=(% scope="row" style="width: 60px;" %)((( 487 +**Size(bytes)** 488 +)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1 489 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)((( 490 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 491 +)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 492 + 493 +(% class="wikigeneratedid" %) 494 +[[image:1667288597595-714.png||height="212" width="1151"]] 495 + 496 + 497 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 498 +* (% style="color:#037691" %)**SSID: **(%%)WiFi name. 499 +* (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 500 + 501 +=== 2.4.7 Add Payload format in TTN V3 === 502 + 503 + 504 +In TTN V3, user can add a custom payload so it shows friendly. 505 + 490 490 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 491 491 492 492 ... ... @@ -493,52 +493,44 @@ 493 493 [[image:1664502649601-895.png]] 494 494 495 495 496 -Add the decoder from this link: 497 497 513 +Add the decoder from this link: 498 498 515 +[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] 516 + 499 499 Save the change the uplink message will be parsed. As below: 500 500 501 501 [[image:1664502676891-606.png]] 502 502 503 503 504 - 505 505 == 2.5 Integrate with Datacake == 506 506 507 507 508 -((( 509 509 After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot. 510 -))) 511 511 512 -((( 513 513 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]] 514 -))) 515 515 516 516 517 517 [[image:1664502695771-538.png]] 518 518 519 519 520 - 521 521 == 2.6 Integrate with Tago == 522 522 523 523 524 -((( 525 -After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot. 526 -))) 536 +After TrackerD sends data to LoRaWAN server such as TTN, user can pass the data to Datacake and plot out, currently only support GPS plot. 527 527 528 -((( 529 529 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]] 530 -))) 531 531 532 532 533 533 [[image:1664502715371-321.png]] 534 534 535 535 536 - 537 537 == 2.7 Datalog Feature == 538 538 539 539 540 -total 273 entries,by default disable547 +total 273 entries,by default, 541 541 549 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 542 542 543 543 Example use case. 544 544 ... ... @@ -548,7 +548,6 @@ 548 548 [[image:image-20221009234629-1.png||height="390" width="577"]] 549 549 550 550 551 - 552 552 == 2.8 Alarm Mode == 553 553 554 554 ... ... @@ -558,15 +558,15 @@ 558 558 559 559 560 560 ((( 561 -Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exit alert mode. 568 +Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exits alert mode. 562 562 ))) 563 563 564 564 565 565 ((( 566 -Two ways to exit alarm mode: 573 +**Two ways to exit alarm mode:** 567 567 ))) 568 568 569 -* Server send a downlink command to exit. 576 +* Server sends a downlink command to exit. 570 570 * User fast press the RED button 10 times. 571 571 572 572 ((( ... ... @@ -574,7 +574,6 @@ 574 574 ))) 575 575 576 576 577 - 578 578 == 2.9 Transport Mode == 579 579 580 580 ... ... @@ -581,17 +581,16 @@ 581 581 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. 582 582 583 583 584 - 585 585 == 2.10 LED Status == 586 586 587 587 588 -(% border="1.5" style="background-color:#ffffcc; color:green;width:500px" %)593 +(% border="1.5" style="background-color:#ffffcc; width:500px" %) 589 589 |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 590 590 |(% 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 591 591 |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes 592 592 |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A 593 593 |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes 594 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ** *(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes599 +|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes 595 595 |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes 596 596 |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes 597 597 |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes ... ... @@ -599,7 +599,6 @@ 599 599 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 600 600 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 601 601 602 - 603 603 == 2.11 Button Function == 604 604 605 605 ... ... @@ -615,13 +615,12 @@ 615 615 [[image:1664502854406-763.png]] 616 616 617 617 618 -(% border="1 .5" style="background-color:#ffffcc;color:green;width:520px" %)619 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 2 10px;" %)**Action**|=(% style="width: 210px;" %)**Description**620 -|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode. See [[Alarm Mode>>||anchor="H2. 6AlarmMode"]]622 +(% border="1" style="background-color:#ffffcc; width:510px" %) 623 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description** 624 +|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode. See [[Alarm Mode>>||anchor="H2.8AlarmMode"]] 621 621 |(% 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 622 622 |(% 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. 623 623 624 - 625 625 == 2.12 USB Port Function == 626 626 627 627 ... ... @@ -632,7 +632,6 @@ 632 632 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 633 633 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 634 634 635 - 636 636 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 637 637 638 638 ... ... @@ -641,7 +641,6 @@ 641 641 LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] 642 642 643 643 644 - 645 645 == 3.1 Access AT Command == 646 646 647 647 ... ... @@ -657,11 +657,9 @@ 657 657 [[image:1664503022490-662.png]] 658 658 659 659 660 - 661 661 [[image:1664503035713-500.png]] 662 662 663 663 664 - 665 665 [[image:1664503047675-651.png]] 666 666 667 667 ... ... @@ -668,7 +668,6 @@ 668 668 669 669 == 3.2 Command Set == 670 670 671 - 672 672 === 3.2.1 Set Transmit Interval === 673 673 674 674 ... ... @@ -686,7 +686,6 @@ 686 686 (% style="color:#037691" %)**0x01 00 01 2C** (%%) ~/~/ Same as AT+TDC=300000 687 687 688 688 689 - 690 690 === 3.2.2 Set Alarm Packet transmission interval === 691 691 692 692 ... ... @@ -704,7 +704,6 @@ 704 704 (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/ Same as AT+ATDC=60000 705 705 706 706 707 - 708 708 === 3.2.3 Set Transport Mode Packet transmission interval === 709 709 710 710 ... ... @@ -719,10 +719,9 @@ 719 719 720 720 * (% style="color:blue" %)**Downlink Payload (prefix 0x03):** 721 721 722 -(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+ 718 +(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+MTDC=3000000 723 723 724 724 725 - 726 726 === 3.2.4 Exit Alarm === 727 727 728 728 ... ... @@ -735,7 +735,6 @@ 735 735 (% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 736 736 737 737 738 - 739 739 === 3.2.5 Disable/Enable LED flash === 740 740 741 741 ... ... @@ -753,7 +753,6 @@ 753 753 (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/ Same as AT+LON=0 754 754 755 755 756 - 757 757 === 3.2.6 Disable/Enable Transport Mode === 758 758 759 759 ... ... @@ -763,19 +763,18 @@ 763 763 764 764 (% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)** 765 765 766 -Example: AT+ 759 +Example: AT+INTWK=1 **~-~-> ** Enable Transport Mode. 767 767 768 768 769 769 * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):** 770 770 771 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+ 764 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+INTWK=1 772 772 773 773 774 - 775 775 === 3.2.7 Set Positioning Mode === 776 776 777 777 778 -SMOD define the how TrackerD scan and uplink data:770 +SMOD define how TrackerD scan and uplink data: 779 779 780 780 781 781 * (% style="color:blue" %)**AT Command:** ... ... @@ -784,32 +784,40 @@ 784 784 785 785 (% style="color:#037691" %)** aa:** 786 786 787 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)only get and uplink GPS location info. 788 -* (% style="color:red" %)**2: BLE ONLY: **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking. 789 -* (% style="color:red" %)**3: GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 779 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 790 790 781 +* (% style="color:red" %)**2: BLE or WiFi ONLY: **(%%)Only obtain iBeacon info via BLE and uplink or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking. 782 + 783 +* (% style="color:red" %)**3: GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 784 + 791 791 (% style="color:#037691" %)**bb:** 792 792 793 793 * (% style="color:red" %)**0 : **(%%)GPS+ BAT+ State+Tem&Hum 788 + 794 794 * (% style="color:red" %)**1 :**(%%) GPS +BAT State 795 795 796 796 (% style="color:#037691" %)**cc: ** 797 797 798 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 793 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 794 + 795 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%)) 799 799 800 800 (% style="color:blue" %)**Example:** 801 801 802 - AT+ SMOD =1,0 ,0 ~-~-> GPS+ BAT+ State+Tem&Hum 803 - AT+ SMOD =1,1,0 ~-~-> GPS +BAT State 804 - AT+ SMOD =2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 799 + AT+SMOD=1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 805 805 801 + AT+SMOD=1,1,0 ~-~-> GPS +BAT State 806 806 807 - *(%style="color:blue" %)**DownlinkPayload(prefix 0xA5):**803 + AT+SMOD=2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 808 808 809 - (%style="color:#037691"%)**0xA5010000**(%%)/~/SameasAT+MOD=1,0,0805 + AT+SMOD=2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State 810 810 811 811 808 +* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** 812 812 810 +(% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+SMOD=1,0,0 811 + 812 + 813 813 === 3.2.8 Set MAX GPS position time === 814 814 815 815 ... ... @@ -816,7 +816,7 @@ 816 816 Set max positioning time, default is 150 seconds. TrackerD will try to get location info within this period. If fail to get position data within this time, TrackerD will use 000000 for latitude and longitude. 817 817 818 818 819 -If AT+FTIME=0. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink. 819 +If **AT+FTIME=0**. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink. 820 820 821 821 822 822 * (% style="color:blue" %)**AT Command:** ... ... @@ -831,7 +831,6 @@ 831 831 (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/ Set AT+FTIME=150 832 832 833 833 834 - 835 835 === 3.2.9 Set PDOP value for GPS fix accuracy === 836 836 837 837 ... ... @@ -856,7 +856,7 @@ 856 856 857 857 858 858 859 -Disable/Enable the confirmation mode 858 +**Disable/Enable the confirmation mode** 860 860 861 861 * (% style="color:blue" %)**AT Command:** 862 862 ... ... @@ -865,17 +865,16 @@ 865 865 866 866 **~ Example:** 867 867 868 - AT+ 867 + AT+CFM=0 **~-~-> ** Disable confirmation 869 869 870 - AT+ 869 + AT+CFM=1 **~-~-> ** Enable confirmation 871 871 872 872 873 873 * (% style="color:blue" %)**Downlink Payload (prefix 0x05):** 874 874 875 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+ SMOD=1874 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1 876 876 877 877 878 - 879 879 === 3.2.10 Auto Send None-ACK messages === 880 880 881 881 ... ... @@ -897,6 +897,68 @@ 897 897 Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 898 898 899 899 898 +=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 899 + 900 + 901 +BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID. 902 + 903 +(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.** 904 + 905 +(% style="color:blue" %)**AT Command:** 906 + 907 + (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 908 + 909 + (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 910 + 911 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 912 + 913 +Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 914 + 915 + 916 +=== 3.2.12 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 917 + 918 + 919 +WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456 as prefix. It will ignore all other WiFi which doesn’t contact 123456 in the SSID. 920 + 921 +(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.** 922 + 923 +(% style="color:blue" %)**AT Command:** 924 + 925 + (% style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456 926 + 927 + (% style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK 928 + 929 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)** 930 + 931 +Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 932 + 933 + 934 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 935 + 936 + 937 +Users can use this feature to enable/disable Information printing. 938 + 939 +(% style="color:blue" %)**AT Command:** 940 + 941 +(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/(Disable (0), Enable (1), default:0) 942 +\\Example: AT+SHOWID=1 ~-~-> Enable Information printing. 943 + 944 + 945 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 946 + 947 + 948 +The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. 949 + 950 +(% style="color:blue" %)**AT Command:** 951 + 952 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode 953 + 954 + 955 +(% style="color:blue" %)**Downlink Payload:0X24** 956 + 957 +Example: 0x24 01 ~/~/ Same as AT+CHE=1 958 + 959 + 900 900 = 4. Setting for Different Scenarios = 901 901 902 902 ... ... @@ -903,7 +903,6 @@ 903 903 904 904 = 5. Upload Firmware = 905 905 906 - 907 907 == 5.1 Firmware Change Log == 908 908 909 909 ... ... @@ -910,7 +910,6 @@ 910 910 **[[See this link>>url:https://github.com/dragino/TrackerD]]** 911 911 912 912 913 - 914 914 == 5.2 How to upgrade firmware == 915 915 916 916 ... ... @@ -937,34 +937,33 @@ 937 937 [[image:1664503574618-659.png]] 938 938 939 939 998 + 940 940 (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 941 941 942 942 [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]] 943 943 944 944 945 -Users need to use below files: 1004 +**Users need to use below files:** 946 946 947 947 boot_app0.bin @0e000 948 948 949 - ESP_LORA-eeprom-class.bin @ 0x100001008 +US915.bin @ 0x10000(Select the bin file of the frequency band you need) 950 950 951 951 952 -[[image:1 664503593459-435.png]]1011 +[[image:image-20221118105220-2.png]] 953 953 954 954 955 955 956 956 After upgrade finish, it will show finish as below: 957 957 958 -[[image: 1664503611848-385.png]]1017 +[[image:image-20221118105402-4.png]] 959 959 960 960 961 961 962 962 = 6. Developer Guide = 963 963 964 - 965 965 == 6.1 Compile Source Code == 966 966 967 - 968 968 === 6.1.1 Set up ARDUINO compile environment === 969 969 970 970 ... ... @@ -982,7 +982,18 @@ 982 982 [[image:1664503715811-892.png]] 983 983 984 984 1042 +(% 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. 985 985 1044 +[[image:image-20221024105643-1.png]] 1045 + 1046 +**~ Figure1** 1047 + 1048 + 1049 +[[image:image-20221024105643-2.png]] 1050 + 1051 + **Figure2** 1052 + 1053 + 986 986 * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]** 987 987 988 988 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: ... ... @@ -991,7 +991,6 @@ 991 991 [[image:1664503752288-974.png]] 992 992 993 993 994 - 995 995 == 6.2 Source Code == 996 996 997 997 ... ... @@ -1012,10 +1012,8 @@ 1012 1012 [[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 1013 1013 1014 1014 1015 - 1016 1016 = 7. FAQ = 1017 1017 1018 - 1019 1019 == 7.1 How to change the LoRa Frequency Bands/Region? == 1020 1020 1021 1021 ... ... @@ -1022,7 +1022,6 @@ 1022 1022 User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download. 1023 1023 1024 1024 1025 - 1026 1026 == 7.2 What is the pin mapping for the USB program cable? == 1027 1027 1028 1028 ... ... @@ -1041,49 +1041,242 @@ 1041 1041 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 1042 1042 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 1043 1043 1108 +== 7.3 Notes on using different serial port tools for TrackerD == 1044 1044 1045 -= 8.OrderInfo =1110 +=== 7.3.1 Serial port utility === 1046 1046 1047 1047 1113 +Serial port utility requires you to automatically add data streams. 1114 + 1115 +Need to adjust the data stream to RTS/CTS on physical restart. 1116 + 1117 +(% class="wikigeneratedid" %) 1118 +[[image:image-20221102140621-1.png]] 1119 + 1120 + 1121 + 1122 +When using AT commands, the data flow needs to be adjusted to XON/XOFF 1123 + 1124 +[[image:image-20221102140638-2.png]] 1125 + 1126 + 1127 +=== 7.3.2 SecureCRT === 1128 + 1129 + 1130 +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. 1131 + 1132 + 1133 +[[image:image-20221102140704-3.png]] 1134 + 1135 + 1136 +[[image:image-20221102140712-4.png]] 1137 + 1138 + 1139 +=== 7.3.3 PUTTY === 1140 + 1141 + 1142 +[[image:image-20221102140748-5.png]] 1143 + 1144 + 1145 +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. 1146 + 1147 + 1148 +[[image:image-20221102140801-6.png]] 1149 + 1150 + 1151 +== 7.4 How to modify source code to compile different frequency band bin file? == 1152 + 1153 + 1154 +(% class="box infomessage" %) 1155 +((( 1156 +(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings. 1157 +See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]] 1158 +))) 1159 + 1160 +**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.** 1161 + 1162 + 1163 +[[image:image-20221116111844-1.png||height="227" width="782"]] 1164 + 1165 + 1166 + 1167 +**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).** 1168 + 1169 + 1170 +[[image:image-20221116111844-2.png||height="262" width="781"]] 1171 + 1172 + 1173 + 1174 +**3. Compile the AS923_JP band, please refer to the intention shown** 1175 + 1176 + 1177 +[[image:image-20221116111844-3.png||height="338" width="746"]] 1178 + 1179 + 1180 + 1181 +**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.** 1182 + 1183 + 1184 +[[image:image-20221116111844-4.png||height="641" width="739"]] 1185 + 1186 + 1187 +[[image:image-20221116111844-5.png||height="551" width="708"]] 1188 + 1189 + 1190 += 8 Trouble Shooting = 1191 + 1192 +== 8.1 TDC is changed to 4294947296 and cause no uplink. == 1193 + 1194 + 1195 +((( 1196 +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 1197 +))) 1198 + 1199 + 1200 +== 8.2 Device not able get AT Command or show output after wake up from deep sleep mode == 1201 + 1202 + 1203 +((( 1204 +ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode. 1205 +))) 1206 + 1207 + 1208 +== 8.3 Problem after Upgrading Firmware == 1209 + 1210 +=== 8.3.1 Continue Restart after upgrading === 1211 + 1212 + 1213 +((( 1214 +If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure 1215 +))) 1216 + 1217 + 1218 +[[image:image-20221118105249-3.png]] 1219 + 1220 + 1221 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1222 + 1223 + 1224 +It is because the partitions are different when upgrading versions above 1.4.1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 1225 + 1226 + 1227 +=== 8.3.3 "flash read err" after upgrade firmware === 1228 + 1229 +Error shows below, user might erase the entire flash include u-boot partition which cause this issue. 1230 + 1231 +[[image:image-20221122100004-1.png||height="497" width="534"]] 1232 + 1233 + 1234 +User need to upgrade again with below four files to solve this issue. 1235 + 1236 + [[image:image-20221122100004-2.png||height="619" width="389"]] 1237 + 1238 + **Figure 2** 1239 + 1240 + 1241 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware === 1242 + 1243 +User might erase the entire flash include keys and default settings which cause this issue. 1244 + 1245 +After the upgrade is completed, enter AT+CFG as shown in the figure below. 1246 + 1247 +[[image:image-20221122100004-3.png]] 1248 + 1249 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label. 1250 + 1251 + 1252 +Example: 1253 + 1254 +AT+DEUI=70B3D57ED0053981 1255 + 1256 +AT+APPEUI=D23345667BCBCCAF 1257 + 1258 +AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1 1259 + 1260 +AT+DADDR=260b4dce ( no need for OTAA) 1261 + 1262 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d ( no need for OTAA) 1263 + 1264 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA) 1265 + 1266 + 1267 + 1268 +=== 8.3.4 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 === 1269 + 1270 + 1271 +[[image:image-20221122100004-4.png]] 1272 + 1273 + 1274 +== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1275 + 1276 + 1277 +Please download version 1.4.2 again 1278 + 1279 + 1280 +== 8.5 How to deal with unsuccessful GPS positioning? == 1281 + 1282 + 1283 +1) Make Sure the device is in Open Area where can see the sky. 1284 + 1285 +2) Set PDOP to a higher value. 1286 + 1287 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.) 1288 + 1289 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces) 1290 + 1291 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments) 1292 + 1293 +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 1294 + 1295 + 1296 += 9. Order Info = 1297 + 1298 + 1048 1048 Part Number: (% style="color:blue" %)**TrackerD-XXX** 1049 1049 1050 1050 (% style="color:blue" %)**XXX**(%%): The default frequency band 1051 1051 1052 1052 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433 1304 + 1053 1053 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868 1306 + 1054 1054 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865 1308 + 1055 1055 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920 1310 + 1056 1056 * (% style="color:red" %)**AS923**(%%): Default frequency band AS923 1312 + 1057 1057 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 1314 + 1058 1058 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1059 1059 1317 += 10. Packing Info = 1060 1060 1061 -= 9. Packing Info = 1062 1062 1063 - 1064 1064 (% style="color:#037691" %)**Package Includes**: 1065 1065 1066 1066 * TrackerD LoRaWAN GPS/BLE Tracker x 1 1323 + 1067 1067 * USB recharge & program cable x 1 1068 1068 1069 1069 (% style="color:#037691" %)**Dimensions and Weight**: 1070 1070 1071 -* Device Size: 85 x 48 x 15 cm 1328 +* Device Size: 85 x 48 x 15 mm 1329 + 1072 1072 * Weight: 50g 1073 1073 1332 += 11. Support = 1074 1074 1075 -= 10. Support = 1076 1076 1077 - 1078 1078 * 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. 1336 + 1079 1079 * 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]]. 1080 1080 1339 += 12. Reference = 1081 1081 1082 -= 11. Reference = 1083 1083 1084 - 1085 1085 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1343 + 1086 1086 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1087 -* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 1088 1088 1089 - 1346 +* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
- 1667288597595-714.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +27.9 KB - Content
- image-20221024105643-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +11.3 KB - Content
- image-20221024105643-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +64.5 KB - Content
- image-20221102140621-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +46.1 KB - Content
- image-20221102140638-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +40.8 KB - Content
- image-20221102140704-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +15.5 KB - Content
- image-20221102140712-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +73.2 KB - Content
- image-20221102140748-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +56.0 KB - Content
- image-20221102140801-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +21.0 KB - Content
- image-20221107145243-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +107.3 KB - Content
- image-20221116111844-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +15.8 KB - Content
- image-20221116111844-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +32.6 KB - Content
- image-20221116111844-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +37.0 KB - Content
- image-20221116111844-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +96.8 KB - Content
- image-20221116111844-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +78.0 KB - Content
- image-20221118104359-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +38.0 KB - Content
- image-20221118105220-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +40.2 KB - Content
- image-20221118105249-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +40.2 KB - Content
- image-20221118105402-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +43.7 KB - Content
- image-20221122100004-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +18.0 KB - Content
- image-20221122100004-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +127.2 KB - Content
- image-20221122100004-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +12.5 KB - Content
- image-20221122100004-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +22.3 KB - Content