Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Xiaoling on 2025/04/27 16:48
From version 79.1
edited by Edwin Chen
on 2022/10/22 00:11
on 2022/10/22 00: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. Edwin1 +XWiki.Xiaoling - Content
-
... ... @@ -61,11 +61,13 @@ 61 61 * EEPROM: 520 KB 62 62 * Clock Speed: 32Mhz 63 63 64 + 64 64 (% style="color:blue" %)**Common DC Characteristics:** 65 65 66 66 * Supply Voltage: 5V via USB port or Internal li-on battery 67 67 * Operating Temperature: -40 ~~ 60°C 68 68 70 + 69 69 (% style="color:blue" %)**LoRa Spec:** 70 70 71 71 * Frequency Range, ... ... @@ -87,10 +87,12 @@ 87 87 * Packet engine up to 256 bytes with CRC. 88 88 * LoRaWAN 1.0.3 Specification 89 89 92 + 90 90 (% style="color:blue" %)**Battery:** 91 91 92 92 * 1000mA Li-on Battery power (for model TrackerD) 93 93 97 + 94 94 (% style="color:blue" %)**Power Consumption** 95 95 96 96 * Sleeping Mode: 200uA ... ... @@ -98,6 +98,7 @@ 98 98 * Tracking: max: 38mA 99 99 100 100 105 + 101 101 == 1.3 Features == 102 102 103 103 ... ... @@ -104,7 +104,7 @@ 104 104 * LoRaWAN 1.0.3 Class A 105 105 * ESP32 PICO D4 106 106 * SX1276/78 Wireless Chip 107 -* Arduino IDE Compatible 112 +** Arduino IDE Compatible 108 108 * Open source hardware / software 109 109 * Regular/ Real-time GPS,BLE,WIFI tracking 110 110 * Built-in3 axis accelerometer (LIS3DH) ... ... @@ -117,6 +117,7 @@ 117 117 * Datalog 118 118 119 119 125 + 120 120 == 1.4 Applications == 121 121 122 122 ... ... @@ -124,6 +124,7 @@ 124 124 * Human tracking 125 125 126 126 133 + 127 127 = 2.1 Use TrackerD = 128 128 129 129 ... ... @@ -186,131 +186,42 @@ 186 186 (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server. 187 187 188 188 196 +(% style="color:blue" %)**Positioning Mode(SMOD):** 189 189 190 -== 2.3 Positioning Mode(SMOD) == 198 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)only get GPS location info. 199 +* (% style="color:#037691" %)**BLE ONLY: **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking. 200 +* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking. 191 191 202 +User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 192 192 193 -Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 194 194 195 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)only get and uplink GPS location info. 196 -* (% style="color:#037691" %)**BLE ONLY: **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking. 197 -* (% 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. 198 198 199 - Userscanswitchmodes by [[changingSMOD>>||anchor="H3.2.7SetPositioningMode"]].206 +== 2.3 Uplink Payload == 200 200 201 201 209 +=== 2.3.1 Uplink FPORT~=5, Device Status === 202 202 203 -== 2.4 Uplink Payload == 204 204 205 205 206 -=== 2. 4.1Uplink FPORT~=5,Device Status ===213 +=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning === 207 207 208 208 209 - Uplink the deviceconfigureswithFPORT=5.OnceTrackerDJoinedthenetwork, itwilluplinkthismessage totheserver.Afterthe firstuplink,TrackerDwilluplink DeviceStatusevery12hours.216 +The default uplink payload includes totally 11 bytes. (User can use AT+MOD=0 to enable the Temperature and humidity sensor to hum/tem info from accelerometer. When accelerometer info is enable, total payload will be 15 bytes, please note 15 bytes won't work on DR0 on US915/AU915 frequency band. ) 210 210 211 -Use can also get the Device Status uplink through the downlink command: **Downlink: 0x2301** 212 212 213 - 214 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %) 215 -|=(% 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 216 -|=(% 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 217 - 218 -[[image:1665301570342-765.png]] 219 - 220 - 221 -(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002 222 - 223 -(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13 224 - 225 -(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version 226 - 227 -(% style="color:#037691" %)**Frequency Band**: 228 - 229 -*0x01: EU868 230 - 231 -*0x02: US915 232 - 233 -*0x03: IN865 234 - 235 -*0x04: AU915 236 - 237 -*0x05: KZ865 238 - 239 -*0x06: RU864 240 - 241 -*0x07: AS923 242 - 243 -*0x08: AS923-1 244 - 245 -*0x09: AS923-2 246 - 247 -*0x0a: AS923-3 248 - 249 -Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF) 250 - 251 -(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD. 252 - 253 - 254 -(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV 255 - 256 -Use can also get the Device Status uplink through the downlink command: 257 - 258 - 259 - 260 -(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40 261 - 262 -(% border="1.5" style="background-color:#ffffcc; color:green; width:420px" %) 263 -|(% style="width:75px" %)**Size(bit)**|(% style="width:64px" %)2bits|(% style="width:137px" %)2bit|(% style="width:142px" %)4bit 264 -|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:137px" %)GPS_Settings|(% style="width:142px" %)BLE_Settings 265 - 266 -(% style="color:blue" %)** SMOD:** 267 - 268 -(% style="color:red" %)** 1 :** (%%) GPS ONLY 269 - 270 -(% style="color:red" %)** 2 :** (%%) BLE ONLY 271 - 272 -(% style="color:red" %)** 3 :** (%%) GPS/BLE Hybrid 273 - 274 - 275 -(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload** 276 - 277 -(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values 278 - 279 -(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values 280 - 281 - 282 -(% style="color:blue" %)** BLE_Settings:** 283 - 284 -(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 285 - 286 - 287 - 288 -(% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 289 - 290 -(% border="1.5" style="background-color:#ffffcc; color:green; width:417px" %) 291 -|(% 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 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"]] 293 - 294 - 295 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 296 - 297 - 298 -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, 299 - 300 - 301 301 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) 302 302 |=(% scope="row" style="width: 50px;" %)((( 303 303 **Size(bytes)** 304 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width: 73px" %)1|(% style="width:40px" %)(((305 -2 222 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)((( 223 +2(optional) 306 306 )))|(% style="width:87px" %)((( 307 -2 225 +2(optional) 308 308 ))) 309 309 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 310 310 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 311 -)))|(% style="width: 73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]229 +)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 312 312 313 -[[image:1665 301636888-168.png]]231 +[[image:1664501958445-288.png]] 314 314 315 315 316 316 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== ... ... @@ -319,11 +319,12 @@ 319 319 |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits 320 320 |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 321 321 240 + 322 322 ==== (% style="color:blue" %)**FLAG:**(%%) ==== 323 323 324 324 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 325 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit 326 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] 244 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits 245 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version 327 327 328 328 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 329 329 ... ... @@ -333,18 +333,23 @@ 333 333 * Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976// 334 334 * Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 335 335 255 + 256 + 336 336 (% style="color:red" %)**Important note:** 337 337 338 338 1. When power is low (<2.84v), GPS won't be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF. 339 339 340 -2. In thismode, the total payloadwill be15 bytes, whileUS915/AU915DR0 acceptsonly 11 bytes payload.Inthiscase, the payloadon server willbeignore andshows as below:261 +2. In firmware version v1.5, Roll & Pitch is disabled by default. 341 341 263 +3. When enable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accept only 11 bytes payload. In this case, the payload on server will be ignore and shows as below: 342 342 265 + 343 343 [[image:1664502116362-706.png]] 344 344 345 345 346 -3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 347 347 270 +4. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 271 + 348 348 [[image:1664502166010-515.png]] 349 349 350 350 ... ... @@ -351,17 +351,18 @@ 351 351 352 352 ==== (% style="color:blue" %)**Alarm:**(%%) ==== 353 353 354 - **Example:**0x4B & 0x40 >> 6 = 0x01278 +Example: 0x4B & 0x40 >> 6 = 0x01 355 355 356 356 357 357 ==== (% style="color:blue" %)**BAT:**(%%) ==== 358 358 359 - **Example:**0x4B45& 0x3FFF ⇒ 2885(mV).283 +Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV). 360 360 361 361 ((( 362 -The battery info shows the battery voltage,User can usethebelow mapping to indicate the battery in percentage: \286 +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: \ 363 363 ))) 364 364 289 + 365 365 * > 4.0v : 80% ~~ 100% 366 366 * 3.85v ~~3.99v: 60% ~~ 80% 367 367 * 3.70v ~~ 3.84v: 40% ~~ 60% ... ... @@ -368,37 +368,21 @@ 368 368 * 3.40v ~~ 3.69v: 20% ~~ 40% 369 369 * < 3.39v: 0~~20% 370 370 371 -==== (% style="color:blue" %)**MOD:**(%%) ==== 372 372 373 -**Example: ** (0x60>>6) & 0x3f =1 374 - 375 -**Set the format of GPS data uplink link:** 376 - 377 -(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values 378 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values 379 - 380 - 381 -**Set the format of BLE data uplink link:** 382 - 383 -(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon 384 - 385 - 386 386 ==== (% style="color:blue" %)**LON:**(%%) ==== 387 387 388 -**Example:** (0x60>>5) & 0x01=1. 389 - 299 + 390 390 Enable/Disable LED activity for uplink 391 391 392 392 ((( 393 - (% style="color:#037691" %)**0x00:**(%%)Disable LED indicator.303 +0x00: Disable LED indicator. 394 394 ))) 395 395 396 396 ((( 397 - (% style="color:#037691" %)**0x01:**(%%)Enable LED indicator (Default Value)307 +0x01: Enable LED indicator (Default Value) 398 398 ))) 399 399 400 400 401 - 402 402 ==== (% style="color:blue" %)**Hum:**(%%) ==== 403 403 404 404 0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree ... ... @@ -410,54 +410,15 @@ 410 410 411 411 412 412 413 -=== 2. 4.33,RealtimeGNSS Positioning(Default Mode)===322 +=== 2.3.3 Uplink FPORT~= , History GNSS Positioning === 414 414 415 415 416 -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) 417 417 326 +=== 2.3.4 BLE positioning Payload(Fport2) === 418 418 419 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) 420 -|=(% scope="row" style="width: 50px;" %)((( 421 -**Size(bytes)** 422 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1 423 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 424 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 425 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 426 426 427 -(% class="wikigeneratedid" %) 428 -[[image:1665301687277-443.png]] 329 +Different MODE has different payload: (% style="color:blue" %)**MODE=2** 429 429 430 - 431 - 432 -=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 433 - 434 - 435 -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. 436 - 437 - 438 -(% style="color:red" %)**Note for this mode:** 439 - 440 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server. 441 -* 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. 442 -* 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 443 - 444 -The payload is 15 bytes, as below. 445 - 446 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %) 447 -|=(% scope="row" %)((( 448 -**Size(bytes)** 449 -)))|4|4|2|1|1|1|1|1 450 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 451 - 452 -[[image:image-20221009160309-2.png]] 453 - 454 - 455 - 456 -=== 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 457 - 458 -TrackerD supports BLE scans for indoor positioning. User can set **SMOD** to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan BLE iBeacon before each uplink. 459 - 460 - 461 461 (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 462 462 |=(% scope="row" style="width: 60px;" %)((( 463 463 **Size(bytes)** ... ... @@ -474,10 +474,11 @@ 474 474 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 475 475 )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 476 476 347 + 477 477 [[image:1664502425687-834.png]] 478 478 479 479 480 -* (% style="color:#037691" %)**BAT: ** (%%) 351 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV). 481 481 * (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 482 482 * (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 483 483 * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. ... ... @@ -486,9 +486,10 @@ 486 486 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 487 487 488 488 489 -=== 2.4.6 Add Payload format in TTN V3 === 490 490 361 +=== 2.3.5 Add Payload format in TTN V3 === 491 491 363 + 492 492 In TTN V3, use can add a custom payload so it shows friendly. 493 493 494 494 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** ... ... @@ -497,9 +497,8 @@ 497 497 [[image:1664502649601-895.png]] 498 498 499 499 500 -Add the decoder from this link: 372 +Add the decoder from this link: 501 501 502 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] 503 503 504 504 Save the change the uplink message will be parsed. As below: 505 505 ... ... @@ -507,7 +507,7 @@ 507 507 508 508 509 509 510 -== 2. 5Integrate with Datacake ==381 +== 2.4 Integrate with Datacake == 511 511 512 512 513 513 ((( ... ... @@ -523,7 +523,7 @@ 523 523 524 524 525 525 526 -== 2. 6Integrate with Tago ==397 +== 2.5 Integrate with Tago == 527 527 528 528 529 529 ((( ... ... @@ -539,25 +539,9 @@ 539 539 540 540 541 541 542 -== 2. 7DatalogFeature ==413 +== 2.6 Alarm Mode == 543 543 544 544 545 -total 273 entries,by default, 546 - 547 -User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 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 ))) ... ... @@ -575,6 +575,7 @@ 575 575 * Server send a downlink command to exit. 576 576 * User fast press the RED button 10 times. 577 577 433 + 578 578 ((( 579 579 When exit alarm mode, (% style="color:red" %)**RED LED**(%%) will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false. 580 580 ))) ... ... @@ -581,16 +581,13 @@ 581 581 582 582 583 583 584 -== 2. 9Transport Mode ==440 +== 2.7 Sports Mode == 585 585 586 586 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 444 +== 2.8 LED Status == 589 589 590 590 591 -== 2.10 LED Status == 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,9 +605,11 @@ 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 608 -== 2.11 Button Function == 609 609 610 610 463 +== 2.9 Button Function == 464 + 465 + 611 611 (% style="color:blue" %)**RESET button:** 612 612 613 613 [[image:1664502835802-546.png]] ... ... @@ -626,9 +626,11 @@ 626 626 |(% 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 627 627 |(% 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. 628 628 629 -== 2.12 USB Port Function == 630 630 631 631 486 +== 2.10 USB Port Function == 487 + 488 + 632 632 The USB interface of TrackerD has below functions: 633 633 634 634 * Power on the device ... ... @@ -636,6 +636,9 @@ 636 636 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 637 637 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 638 638 496 + 497 + 498 + 639 639 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 640 640 641 641 ... ... @@ -708,16 +708,16 @@ 708 708 709 709 710 710 711 -=== 3.2.3 Set Transport Mode Packet transmission interval ===571 +=== 3.2.3 Set Sports Mode Packet transmission interval === 712 712 713 713 714 -Set TransportModepacket transmit interval574 +Set sports packet transmit interval 715 715 716 716 * (% style="color:blue" %)**AT Command:** 717 717 718 718 (% style="color:#037691" %)**AT+MTDC=xx. ** 719 719 720 -Example: AT+MTDC=300000 **~-~-> ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds inTransport mode, Default Value: 300000580 +Example: AT+MTDC=300000 **~-~-> ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000 721 721 722 722 723 723 * (% style="color:blue" %)**Downlink Payload (prefix 0x03):** ... ... @@ -757,16 +757,16 @@ 757 757 758 758 759 759 760 -=== 3.2.6 Disable/Enable TransportMode ===620 +=== 3.2.6 Disable/Enable movement detect (Debug Only) === 761 761 762 762 763 -User scan use this feature to enable/disableTransportMode.623 +User can use this feature to check and set thread hole of movement detect 764 764 765 765 * (% style="color:blue" %)**AT Command:** 766 766 767 767 (% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)** 768 768 769 -Example: AT+ INTWK =1 **~-~-> ** Enable TransportMode.629 +Example: AT+ INTWK =1 **~-~-> ** Enable detect movement. 770 770 771 771 772 772 * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):** ... ... @@ -778,38 +778,35 @@ 778 778 === 3.2.7 Set Positioning Mode === 779 779 780 780 781 -SMOD define how TrackerD scan and uplink dat a:641 +SMOD define the how TrackerD scan and uplink date. 782 782 643 +GPS室外定位模式: 设备默认模式,设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是3分钟定位,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。GPS还有一种logdata模式,在断网的情况下将数据存储下来,等到有网的时候,一次将数据以每10秒上报。 783 783 784 - *(%style="color:blue" %)**AT Command:**645 +BLE室内定位模式: 设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是5秒,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每3分钟发送一次)。 785 785 786 - (% style="color:#037691" %)**AT+SMOD=aa,bb,cc**647 +GPS和BLE混动模式:设备入网后会发送device当前模式下的信息,随后立即判断是否在室内,如果是就进行BLE定位,不是就GPS定位。如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。 787 787 788 - (%style="color:#037691" %)** aa:**649 +运动模式: 设备入网后会发送device当前模式下的信息,随后发送GPS定位数据,设备判断是否在运动,没有运动传感器没有检测到动作,立即进入静止状态(默认20分钟),如果产生运动,将每5分钟发送一次数据,再第五分钟后检测设备有误运动,无将切换到静止状态,有立即发送数据。 789 789 790 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)only get and uplink GPS location info. 791 -* (% style="color:red" %)**2: BLE ONLY: **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking. 792 -* (% 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. 793 793 794 -(% style="color:#037691" %)**bb:** 795 795 796 -* (% style="color:red" %)**0 : **(%%)GPS+ BAT+ State+Tem&Hum 797 -* (% style="color:red" %)**1 :**(%%) GPS +BAT State 653 +* (% style="color:blue" %)**AT Command:** 798 798 799 -(% style="color:#037691" %)** cc:**655 +(% style="color:#037691" %)**AT+SMOD=xx. ** 800 800 801 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 802 802 803 - (%style="color:blue" %)**Example:**658 + **Example:** 804 804 805 - AT+ SMOD =1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 806 - AT+ SMOD =1,1,0 ~-~-> GPS +BAT State 807 - AT+ SMOD =2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 660 + AT+ SMOD =1,0 **~-~-> ** GPS+ BAT+ State+Tem&Hum 808 808 662 + AT+ SMOD =1,1 **~-~->** GPS +BAT State 809 809 664 + AT+ SMOD =2,3 **~-~->** (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。 665 + 666 + 810 810 * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** 811 811 812 -(% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+ SMOD =1,0,0669 +(% style="color:#037691" %)**0xA5 01 00** (%%) ~/~/ Same as AT+ SMOD =1,0 813 813 814 814 815 815 ... ... @@ -826,7 +826,7 @@ 826 826 827 827 (% style="color:#037691" %)**AT+FTIME=xx** (%%) **~-~-> ** Set to use xx as max fix time. 828 828 829 - **Example:**AT+FTIME=150686 +Example: AT+FTIME=150 830 830 831 831 832 832 * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):** ... ... @@ -835,7 +835,7 @@ 835 835 836 836 837 837 838 -=== 3. 2.9 Set PDOP value for GPS fix accuracy ===695 +=== 3.3.9 Set PDOP value for GPS fix accuracy === 839 839 840 840 841 841 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. ... ... @@ -863,7 +863,7 @@ 863 863 864 864 * (% style="color:blue" %)**AT Command:** 865 865 866 -(% style="color:#037691" %)**AT+CFM=xx** 723 +(% style="color:#037691" %)**AT+CFM=xx. ** 867 867 868 868 869 869 **~ Example:** ... ... @@ -879,27 +879,6 @@ 879 879 880 880 881 881 882 -=== 3.2.10 Auto Send None-ACK messages === 883 - 884 - 885 -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. 886 - 887 - 888 -* (% style="color:blue" %)**AT Command: AT+PNACKMD** 889 - 890 -The default factory setting is 0. 891 - 892 - 893 -**Command Example Function Response:** 894 - 895 -(% style="color:#037691" %)**AT+PNACKMD=1** (%%) ~/~/ Poll None-ACK message OK 896 - 897 - 898 -* (% style="color:blue" %)**Downlink Command: 0x34** 899 - 900 -Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 901 - 902 - 903 903 = 4. Setting for Different Scenarios = 904 904 905 905 ... ... @@ -942,7 +942,7 @@ 942 942 943 943 (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 944 944 945 -[[https:~~/~~/ github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]781 +[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 946 946 947 947 948 948 Users need to use below files: ... ... @@ -979,7 +979,6 @@ 979 979 [[image:1664503635019-941.png]] 980 980 981 981 982 - 983 983 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 984 984 985 985 [[image:1664503715811-892.png]] ... ... @@ -1045,6 +1045,7 @@ 1045 1045 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 1046 1046 1047 1047 883 + 1048 1048 = 8. Order Info = 1049 1049 1050 1050 ... ... @@ -1061,20 +1061,24 @@ 1061 1061 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1062 1062 1063 1063 900 + 901 + 1064 1064 = 9. Packing Info = 1065 1065 1066 1066 1067 -(% style="color:#037691" %) **Package Includes**:905 +**(% style="color:#037691" %)Package Includes**: 1068 1068 1069 1069 * TrackerD LoRaWAN GPS/BLE Tracker x 1 1070 1070 * USB recharge & program cable x 1 1071 1071 1072 -(% style="color:#037691" %) **Dimensions and Weight**:910 +**(% style="color:#037691" %)Dimensions and Weight**: 1073 1073 1074 1074 * Device Size: 85 x 48 x 15 cm 1075 1075 * Weight: 50g 1076 1076 1077 1077 916 + 917 + 1078 1078 = 10. Support = 1079 1079 1080 1080 ... ... @@ -1082,6 +1082,8 @@ 1082 1082 * 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]]. 1083 1083 1084 1084 925 + 926 + 1085 1085 = 11. Reference = 1086 1086 1087 1087 ... ... @@ -1089,4 +1089,5 @@ 1089 1089 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1090 1090 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 1091 1091 934 + 1092 1092
- 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-20221006181316-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -17.7 KB - Content
- image-20221006181357-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -88.0 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