Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Xiaoling on 2025/04/27 16:48
From version 84.2
edited by Xiaoling
on 2022/10/24 10:58
on 2022/10/24 10:58
Change comment:
There is no comment for this version
To version 57.1
edited by Edwin Chen
on 2022/10/08 17:11
on 2022/10/08 17:11
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 10 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Edwin - Content
-
... ... @@ -1,3 +1,5 @@ 1 +== == 2 + 1 1 (% style="text-align:center" %) 2 2 [[image:1664505654417-133.png]] 3 3 ... ... @@ -97,8 +97,6 @@ 97 97 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm 98 98 * Tracking: max: 38mA 99 99 100 - 101 - 102 102 == 1.3 Features == 103 103 104 104 ... ... @@ -117,8 +117,6 @@ 117 117 * Tri-color LED, Alarm button 118 118 * Datalog 119 119 120 - 121 - 122 122 == 1.4 Applications == 123 123 124 124 ... ... @@ -125,8 +125,6 @@ 125 125 * Logistics and Supply Chain Management 126 126 * Human tracking 127 127 128 - 129 - 130 130 = 2.1 Use TrackerD = 131 131 132 132 ... ... @@ -189,10 +189,8 @@ 189 189 (% 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. 190 190 191 191 188 +== 2.3 Positioning Mode(SMOD) == 192 192 193 -== 2.3 Positioning Mode(SMOD) == 194 - 195 - 196 196 Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 197 197 198 198 * (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)only get and uplink GPS location info. ... ... @@ -202,33 +202,26 @@ 202 202 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 203 203 204 204 199 +== 2.3 Uplink Payload == 205 205 206 -== 2.4 Uplink Payload == 207 207 202 +=== 2.3.1 Uplink FPORT~=5, Device Status === 208 208 209 - === 2.4.1Uplink FPORT~=5, Device Status===204 +Uplink the device configures with FPORT=5. Once LHT52 Joined the network, it will uplink this message to the server. After first uplink, LHT52 will uplink Device Status every 12 hours. 210 210 206 +|=**Size (bytes)**|=**1**|=**2**|=**1**|=**1**|=**2** 207 +|**Value**|Sensor Model|Firmware Version|Frequency Band|Sub-band|BAT 211 211 212 - Uplink the device configures with FPORT=5. Once TrackerD Joined the network, it will uplink thismessageto the server. After the first uplink, TrackerD will uplink Device Status every12hours.209 +[[image:image-20221006181357-2.png]] 213 213 214 - Usecan alsogetthe DeviceStatus uplinkthrough thedownlink command: **Downlink:0x2301**211 +Example Payload (FPort=5): [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT52%20-%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20User%20Manual/WebHome/image-20220621105116-11.png?rev=1.1||alt="image-20220621105116-11.png"]] 215 215 213 +**Sensor Model**: For TrackerD, this value is 0x13. 216 216 217 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %) 218 -|=(% scope="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;" %)1 219 -|=(% 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 215 +**Firmware Version**: 0x0100, Means: v1.0.0 version. 220 220 221 - [[image:1665301570342-765.png]]217 +**Frequency Band**: 222 222 223 - 224 -(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002 225 - 226 -(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13 227 - 228 -(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version 229 - 230 -(% style="color:#037691" %)**Frequency Band**: 231 - 232 232 *0x01: EU868 233 233 234 234 *0x02: US915 ... ... @@ -249,70 +249,34 @@ 249 249 250 250 *0x0a: AS923-3 251 251 252 -Sub- ,Others areFF)239 +**Sub-Band**: value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00) 253 253 254 - (% style="color:#037691" %)**BAT:**(%%)shows the battery voltage for TrackerD.241 +**BAT**: shows the battery voltage for TrackerD. 255 255 243 +Ex1: 0x0B3A = 2874mV 256 256 257 -(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV 258 - 259 259 Use can also get the Device Status uplink through the downlink command: 260 260 261 261 262 - (% style="color:#037691"%)**SMODField(total1byte)**(%%):0x40248 +=== 2.3.2 Uplink FPORT~=2, Realtime GNSS Positioning === 263 263 264 -(% border="1.5" style="background-color:#ffffcc; color:green; width:420px" %) 265 -|(% style="width:75px" %)**Size(bit)**|(% style="width:64px" %)2bits|(% style="width:137px" %)2bit|(% style="width:142px" %)4bit 266 -|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:137px" %)GPS_Settings|(% style="width:142px" %)BLE_Settings 267 267 268 - (%style="color:blue"%)**SMOD:**251 +The default uplink payload includes totally 11 bytes. (User can use AT+SMOD=1,0 to enable uploading on-board Temperature and humidity value, and total payload will be 15 bytes, please note 15 bytes won't work on DR0 on US915/AU915 frequency band. ) 269 269 270 -(% style="color:red" %)** 1 :** (%%) GPS ONLY 271 271 272 -(% style="color:red" %)** 2 :** (%%) BLE ONLY 273 - 274 -(% style="color:red" %)** 3 :** (%%) GPS/BLE Hybrid 275 - 276 - 277 -(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload** 278 - 279 -(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values 280 - 281 -(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values 282 - 283 - 284 -(% style="color:blue" %)** BLE_Settings:** 285 - 286 -(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 287 - 288 - 289 -(% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 290 - 291 -(% border="1.5" style="background-color:#ffffcc; color:green; width:417px" %) 292 -|(% style="width:77px" %)**Size(bit)**|(% style="width:70px" %)5 Bits|(% style="width:92px" %)1 Bit|(% style="width:48px" %)1 Bit|(% style="width:126px" %)1 Bit 293 -|(% 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"]] 294 - 295 - 296 - 297 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 298 - 299 - 300 -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, 301 - 302 - 303 303 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) 304 304 |=(% scope="row" style="width: 50px;" %)((( 305 305 **Size(bytes)** 306 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width: 73px" %)1|(% style="width:40px" %)(((307 -2 257 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)((( 258 +2(optional) 308 308 )))|(% style="width:87px" %)((( 309 -2 260 +2(optional) 310 310 ))) 311 311 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 312 312 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 313 -)))|(% style="width: 73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]264 +)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 314 314 315 -[[image:1665 301636888-168.png]]266 +[[image:1664501958445-288.png]] 316 316 317 317 318 318 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== ... ... @@ -324,8 +324,8 @@ 324 324 ==== (% style="color:blue" %)**FLAG:**(%%) ==== 325 325 326 326 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 327 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit 328 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] 278 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits 279 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version 329 329 330 330 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 331 331 ... ... @@ -339,14 +339,15 @@ 339 339 340 340 1. When power is low (<2.84v), GPS won't be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF. 341 341 342 -2. Inthis 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:293 +2. When enable 9-axis motion sensor, 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: 343 343 344 344 345 345 [[image:1664502116362-706.png]] 346 346 347 347 348 -3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 349 349 300 +4. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 301 + 350 350 [[image:1664502166010-515.png]] 351 351 352 352 ... ... @@ -353,15 +353,15 @@ 353 353 354 354 ==== (% style="color:blue" %)**Alarm:**(%%) ==== 355 355 356 - **Example:**0x4B & 0x40 >> 6 = 0x01308 +Example: 0x4B & 0x40 >> 6 = 0x01 357 357 358 358 359 359 ==== (% style="color:blue" %)**BAT:**(%%) ==== 360 360 361 - **Example:**0x4B45& 0x3FFF ⇒ 2885(mV).313 +Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV). 362 362 363 363 ((( 364 -The battery info shows the battery voltage,User can usethebelow mapping to indicate the battery in percentage: \316 +The battery info shows the current voltage, for (% style="color:blue" %)**TrackerD**(%%) version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \ 365 365 ))) 366 366 367 367 * > 4.0v : 80% ~~ 100% ... ... @@ -370,39 +370,19 @@ 370 370 * 3.40v ~~ 3.69v: 20% ~~ 40% 371 371 * < 3.39v: 0~~20% 372 372 373 - 374 - 375 -==== (% style="color:blue" %)**MOD:**(%%) ==== 376 - 377 -**Example: ** (0x60>>6) & 0x3f =1 378 - 379 -**Set the format of GPS data uplink link:** 380 - 381 -(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values 382 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values 383 - 384 - 385 -**Set the format of BLE data uplink link:** 386 - 387 -(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon 388 - 389 - 390 390 ==== (% style="color:blue" %)**LON:**(%%) ==== 391 391 392 -**Example:** (0x60>>5) & 0x01=1. 393 - 394 394 Enable/Disable LED activity for uplink 395 395 396 396 ((( 397 - (% style="color:#037691" %)**0x00:**(%%)Disable LED indicator.330 +0x00: Disable LED indicator. 398 398 ))) 399 399 400 400 ((( 401 - (% style="color:#037691" %)**0x01:**(%%)Enable LED indicator (Default Value)334 +0x01: Enable LED indicator (Default Value) 402 402 ))) 403 403 404 404 405 - 406 406 ==== (% style="color:blue" %)**Hum:**(%%) ==== 407 407 408 408 0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree ... ... @@ -414,57 +414,15 @@ 414 414 415 415 416 416 417 -=== 2. 4.33,RealtimeGNSS Positioning(Default Mode)===349 +=== 2.3.3 Uplink FPORT~= , History GNSS Positioning === 418 418 419 419 420 -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) 421 421 353 +=== 2.3.4 BLE positioning Payload(Fport2) === 422 422 423 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) 424 -|=(% scope="row" style="width: 50px;" %)((( 425 -**Size(bytes)** 426 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1 427 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 428 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 429 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 430 430 431 -(% class="wikigeneratedid" %) 432 -[[image:1665301687277-443.png]] 356 +Different MODE has different payload: (% style="color:blue" %)**MODE=2** 433 433 434 - 435 - 436 -=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 437 - 438 - 439 -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. 440 - 441 - 442 -(% style="color:red" %)**Note for this mode:** 443 - 444 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server. 445 -* 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. 446 -* 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 447 - 448 -The payload is 15 bytes, as below. 449 - 450 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %) 451 -|=(% scope="row" %)((( 452 -**Size(bytes)** 453 -)))|4|4|2|1|1|1|1|1 454 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 455 - 456 -[[image:image-20221009160309-2.png]] 457 - 458 - 459 - 460 -=== 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 461 - 462 - 463 -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. 464 - 465 -User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings. 466 - 467 - 468 468 (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 469 469 |=(% scope="row" style="width: 60px;" %)((( 470 470 **Size(bytes)** ... ... @@ -484,7 +484,7 @@ 484 484 [[image:1664502425687-834.png]] 485 485 486 486 487 -* (% style="color:#037691" %)**BAT: ** (%%) 377 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV). 488 488 * (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 489 489 * (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 490 490 * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. ... ... @@ -492,11 +492,9 @@ 492 492 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 493 493 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 494 494 385 +=== 2.3.5 Add Payload format in TTN V3 === 495 495 496 496 497 -=== 2.4.6 Add Payload format in TTN V3 === 498 - 499 - 500 500 In TTN V3, use can add a custom payload so it shows friendly. 501 501 502 502 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** ... ... @@ -505,9 +505,8 @@ 505 505 [[image:1664502649601-895.png]] 506 506 507 507 508 -Add the decoder from this link: 396 +Add the decoder from this link: 509 509 510 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] 511 511 512 512 Save the change the uplink message will be parsed. As below: 513 513 ... ... @@ -515,49 +515,44 @@ 515 515 516 516 517 517 518 -== 2. 5Integrate with Datacake ==405 +== 2.4 Integrate with Datacake == 519 519 407 + 408 +((( 520 520 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. 410 +))) 521 521 412 +((( 522 522 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]] 414 +))) 523 523 416 + 524 524 [[image:1664502695771-538.png]] 525 525 526 526 527 527 528 -== 2. 6Integrate with Tago ==421 +== 2.5 Integrate with Tago == 529 529 530 530 424 +((( 425 +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. 426 +))) 531 531 532 -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. 533 - 428 +((( 534 534 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]] 430 +))) 535 535 536 536 537 - 538 538 [[image:1664502715371-321.png]] 539 539 540 540 541 541 542 -== 2. 7Datalog Feature ==437 +== 2.6 Datalog Feature == 543 543 544 544 545 - total273entries,bydefault,440 +== 2.6 Alarm Mode == 546 546 547 -User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 548 548 549 -Example use case. 550 - 551 -[[image:image-20221009234703-2.png||height="328" width="899"]] 552 - 553 - 554 -[[image:image-20221009234629-1.png||height="390" width="577"]] 555 - 556 - 557 - 558 -== 2.8 Alarm Mode == 559 - 560 - 561 561 ((( 562 562 User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 563 563 ))) ... ... @@ -564,7 +564,7 @@ 564 564 565 565 566 566 ((( 567 -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 salert mode.449 +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 568 ))) 569 569 570 570 ... ... @@ -572,7 +572,7 @@ 572 572 Two ways to exit alarm mode: 573 573 ))) 574 574 575 -* Server send sa downlink command to exit.457 +* Server send a downlink command to exit. 576 576 * User fast press the RED button 10 times. 577 577 578 578 ((( ... ... @@ -581,16 +581,15 @@ 581 581 582 582 583 583 584 -== 2. 9Transport Mode ==466 +== 2.7 Transport Mode == 585 585 586 586 587 587 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. 588 588 589 589 472 +== 2.8 LED Status == 590 590 591 -== 2.10 LED Status == 592 592 593 - 594 594 (% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 595 595 |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 596 596 |(% style="width:157px" %)**Power On**|(% style="width:271px" %)(% style="color:blue" %)**BLUE, **(% style="color:red" %)**RED , **(% style="color:green" %)**Green** flash once|(% style="width:202px" %)N/A ... ... @@ -605,11 +605,9 @@ 605 605 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 606 606 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 607 607 489 +== 2.9 Button Function == 608 608 609 609 610 -== 2.11 Button Function == 611 - 612 - 613 613 (% style="color:blue" %)**RESET button:** 614 614 615 615 [[image:1664502835802-546.png]] ... ... @@ -628,11 +628,9 @@ 628 628 |(% 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 629 629 |(% 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. 630 630 510 +== 2.10 USB Port Function == 631 631 632 632 633 -== 2.12 USB Port Function == 634 - 635 - 636 636 The USB interface of TrackerD has below functions: 637 637 638 638 * Power on the device ... ... @@ -640,8 +640,6 @@ 640 640 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 641 641 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 642 642 643 - 644 - 645 645 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 646 646 647 647 ... ... @@ -666,9 +666,11 @@ 666 666 [[image:1664503022490-662.png]] 667 667 668 668 544 + 669 669 [[image:1664503035713-500.png]] 670 670 671 671 548 + 672 672 [[image:1664503047675-651.png]] 673 673 674 674 ... ... @@ -761,16 +761,16 @@ 761 761 762 762 763 763 764 -=== 3.2.6 Disable/Enable TransportMode ===641 +=== 3.2.6 Disable/Enable movement detect (Debug Only) === 765 765 766 766 767 -User scan use this feature to enable/disableTransportMode.644 +User can use this feature to check and set thread hole of movement detect 768 768 769 769 * (% style="color:blue" %)**AT Command:** 770 770 771 771 (% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)** 772 772 773 -Example: AT+ INTWK =1 **~-~-> ** Enable TransportMode.650 +Example: AT+ INTWK =1 **~-~-> ** Enable detect movement. 774 774 775 775 776 776 * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):** ... ... @@ -782,38 +782,26 @@ 782 782 === 3.2.7 Set Positioning Mode === 783 783 784 784 785 -SMOD define how TrackerD scan and uplink data: 662 +SMOD define the how TrackerD scan and uplink data: 786 786 787 787 788 788 * (% style="color:blue" %)**AT Command:** 789 789 790 -(% style="color:#037691" %)**AT+SMOD= aa,bb,cc**667 +(% style="color:#037691" %)**AT+SMOD=xx. ** 791 791 792 -(% style="color:#037691" %)** aa:** 793 793 794 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)only get and uplink GPS location info. 795 -* (% style="color:red" %)**2: BLE ONLY: **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking. 796 -* (% 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. 670 + **Example:** 797 797 798 - (%style="color:#037691"%)**bb:**672 + AT+ SMOD =1,0 **~-~-> ** GPS+ BAT+ State+Tem&Hum 799 799 800 -* (% style="color:red" %)**0 : **(%%)GPS+ BAT+ State+Tem&Hum 801 -* (% style="color:red" %)**1 :**(%%) GPS +BAT State 674 + AT+ SMOD =1,1 **~-~->** GPS +BAT State 802 802 803 - (%style="color:#037691" %)**cc:**676 + AT+ SMOD =2,3 **~-~->** (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。 804 804 805 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 806 806 807 -(% style="color:blue" %)**Example:** 808 - 809 - AT+ SMOD =1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 810 - AT+ SMOD =1,1,0 ~-~-> GPS +BAT State 811 - AT+ SMOD =2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 812 - 813 - 814 814 * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** 815 815 816 -(% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+ SMOD =1,0,0681 +(% style="color:#037691" %)**0xA5 01 00** (%%) ~/~/ Same as AT+ SMOD =1,0 817 817 818 818 819 819 ... ... @@ -830,7 +830,7 @@ 830 830 831 831 (% style="color:#037691" %)**AT+FTIME=xx** (%%) **~-~-> ** Set to use xx as max fix time. 832 832 833 - **Example:**AT+FTIME=150698 +Example: AT+FTIME=150 834 834 835 835 836 836 * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):** ... ... @@ -839,7 +839,7 @@ 839 839 840 840 841 841 842 -=== 3. 2.9 Set PDOP value for GPS fix accuracy ===707 +=== 3.3.9 Set PDOP value for GPS fix accuracy === 843 843 844 844 845 845 PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can't get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server. ... ... @@ -867,7 +867,7 @@ 867 867 868 868 * (% style="color:blue" %)**AT Command:** 869 869 870 -(% style="color:#037691" %)**AT+CFM=xx** 735 +(% style="color:#037691" %)**AT+CFM=xx. ** 871 871 872 872 873 873 **~ Example:** ... ... @@ -883,46 +883,6 @@ 883 883 884 884 885 885 886 -=== 3.2.10 Auto Send None-ACK messages === 887 - 888 - 889 -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. 890 - 891 - 892 -* (% style="color:blue" %)**AT Command: AT+PNACKMD** 893 - 894 -The default factory setting is 0. 895 - 896 - 897 -**Command Example Function Response:** 898 - 899 -(% style="color:#037691" %)**AT+PNACKMD=1** (%%) ~/~/ Poll None-ACK message OK 900 - 901 - 902 -* (% style="color:blue" %)**Downlink Command: 0x34** 903 - 904 -Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 905 - 906 - 907 - 908 -=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 909 - 910 - 911 -BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. LBT1 will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID. 912 - 913 -Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled. 914 - 915 -(% style="color:blue" %)**AT Command:**(%%) 916 - AT+BLEMASK=123456 ~/~/ Set BLEMASK = 123456 917 - AT+BLEMASK=0 ~/~/ disable BLEMASK 918 - 919 - 920 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**(%%) 921 -Example: 922 -0xA5010203040506 ~/~/ Set BLEMASK to 123456 923 - 924 - 925 - 926 926 = 4. Setting for Different Scenarios = 927 927 928 928 ... ... @@ -963,21 +963,9 @@ 963 963 [[image:1664503574618-659.png]] 964 964 965 965 966 -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. 967 - 968 -[[image:image-20221024105643-1.png]] 969 - 970 - Figure1 971 - 972 - 973 -[[image:image-20221024105643-2.png]] 974 - 975 - Figure2 976 - 977 - 978 978 (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 979 979 980 -[[https:~~/~~/ github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]793 +[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 981 981 982 982 983 983 Users need to use below files: ... ... @@ -1014,7 +1014,6 @@ 1014 1014 [[image:1664503635019-941.png]] 1015 1015 1016 1016 1017 - 1018 1018 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 1019 1019 1020 1020 [[image:1664503715811-892.png]] ... ... @@ -1094,8 +1094,6 @@ 1094 1094 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 1095 1095 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1096 1096 1097 - 1098 - 1099 1099 = 9. Packing Info = 1100 1100 1101 1101 ... ... @@ -1109,8 +1109,6 @@ 1109 1109 * Device Size: 85 x 48 x 15 cm 1110 1110 * Weight: 50g 1111 1111 1112 - 1113 - 1114 1114 = 10. Support = 1115 1115 1116 1116 ... ... @@ -1117,8 +1117,6 @@ 1117 1117 * 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. 1118 1118 * 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]]. 1119 1119 1120 - 1121 - 1122 1122 = 11. Reference = 1123 1123 1124 1124
- 1665301570342-765.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.6 KB - Content
- 1665301636888-168.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -36.6 KB - Content
- 1665301687277-443.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -22.6 KB - Content
- 1665301786397-168.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -22.6 KB - Content
- image-20221009160220-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -46.4 KB - Content
- image-20221009160309-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -57.2 KB - Content
- image-20221009234629-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -222.9 KB - Content
- image-20221009234703-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -136.4 KB - Content
- image-20221024105643-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -11.3 KB - Content
- image-20221024105643-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -64.5 KB - Content