Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)
Last modified by Xiaoling on 2023/12/27 09:15
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 12 added, 0 removed)
- 1665301570342-765.png
- 1665301636888-168.png
- 1665301687277-443.png
- 1665301786397-168.png
- image-20221006181316-1.png
- image-20221006181357-2.png
- image-20221009160220-1.png
- image-20221009160309-2.png
- image-20221009234629-1.png
- image-20221009234703-2.png
- image-20221024105643-1.png
- image-20221024105643-2.png
Details
- Page properties
-
- Content
-
... ... @@ -61,13 +61,11 @@ 61 61 * EEPROM: 520 KB 62 62 * Clock Speed: 32Mhz 63 63 64 - 65 65 (% style="color:blue" %)**Common DC Characteristics:** 66 66 67 67 * Supply Voltage: 5V via USB port or Internal li-on battery 68 68 * Operating Temperature: -40 ~~ 60°C 69 69 70 - 71 71 (% style="color:blue" %)**LoRa Spec:** 72 72 73 73 * Frequency Range, ... ... @@ -89,12 +89,10 @@ 89 89 * Packet engine up to 256 bytes with CRC. 90 90 * LoRaWAN 1.0.3 Specification 91 91 92 - 93 93 (% style="color:blue" %)**Battery:** 94 94 95 95 * 1000mA Li-on Battery power (for model TrackerD) 96 96 97 - 98 98 (% style="color:blue" %)**Power Consumption** 99 99 100 100 * Sleeping Mode: 200uA ... ... @@ -102,7 +102,6 @@ 102 102 * Tracking: max: 38mA 103 103 104 104 105 - 106 106 == 1.3 Features == 107 107 108 108 ... ... @@ -122,7 +122,6 @@ 122 122 * Datalog 123 123 124 124 125 - 126 126 == 1.4 Applications == 127 127 128 128 ... ... @@ -130,7 +130,6 @@ 130 130 * Human tracking 131 131 132 132 133 - 134 134 = 2.1 Use TrackerD = 135 135 136 136 ... ... @@ -193,42 +193,129 @@ 193 193 (% 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. 194 194 195 195 196 -(% style="color:blue" %)**Positioning Mode(SMOD):** 197 197 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. 190 +== 2.3 Positioning Mode(SMOD) == 201 201 202 -User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 203 203 193 +Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 204 204 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. 205 205 206 - ==2.3UplinkPayload==199 +Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 207 207 208 208 209 -=== 2.3.1 Uplink FPORT~=5, Device Status === 210 210 203 +== 2.4 Uplink Payload == 211 211 212 212 213 -=== 2. 3.2Uplink FPORT~=RealtimeGNSS Positioning===206 +=== 2.4.1 Uplink FPORT~=5, Device Status === 214 214 215 215 216 - The default uplinkpayloadincludes totally11 bytes.(User canuseAT+MOD=0toenable theTemperatureandhumiditysensortohum/teminfo from accelerometer.When accelerometerinfoisenable,totalpayloadwillbe 15 bytes,pleasenote 15 byteswon't workon DR0 on US915/AU915frequency band.)209 +Uplink the device configures with FPORT=5. Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours. 217 217 211 +Use can also get the Device Status uplink through the downlink command: **Downlink: 0x2301** 218 218 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 +(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40 260 + 261 +(% border="1.5" style="background-color:#ffffcc; color:green; width:420px" %) 262 +|(% style="width:75px" %)**Size(bit)**|(% style="width:64px" %)2bits|(% style="width:137px" %)2bit|(% style="width:142px" %)4bit 263 +|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:137px" %)GPS_Settings|(% style="width:142px" %)BLE_Settings 264 + 265 +(% style="color:blue" %)** SMOD:** 266 + 267 +(% style="color:red" %)** 1 :** (%%) GPS ONLY 268 + 269 +(% style="color:red" %)** 2 :** (%%) BLE ONLY 270 + 271 +(% style="color:red" %)** 3 :** (%%) GPS/BLE Hybrid 272 + 273 + 274 +(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload** 275 + 276 +(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values 277 + 278 +(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values 279 + 280 + 281 +(% style="color:blue" %)** BLE_Settings:** 282 + 283 +(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 284 + 285 + 286 +(% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 287 + 288 +(% border="1.5" style="background-color:#ffffcc; color:green; width:417px" %) 289 +|(% 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 290 +|(% 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"]] 291 + 292 + 293 +=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 294 + 295 + 296 +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, 297 + 298 + 219 219 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) 220 220 |=(% scope="row" style="width: 50px;" %)((( 221 221 **Size(bytes)** 222 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width: 50px" %)1|(% style="width:88px" %)(((223 -2 (optional)302 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)((( 303 +2 224 224 )))|(% style="width:87px" %)((( 225 -2 (optional)305 +2 226 226 ))) 227 227 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 228 228 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 229 -)))|(% style="width: 52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]309 +)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 230 230 231 -[[image:166 4501958445-288.png]]311 +[[image:1665301636888-168.png]] 232 232 233 233 234 234 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== ... ... @@ -240,8 +240,8 @@ 240 240 ==== (% style="color:blue" %)**FLAG:**(%%) ==== 241 241 242 242 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 243 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit |(% style="width:100px" %)5 bits244 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] |(% style="width:140px" %)Firmware version323 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit 324 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] 245 245 246 246 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 247 247 ... ... @@ -251,23 +251,18 @@ 251 251 * Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976// 252 252 * Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 253 253 254 - 255 - 256 256 (% style="color:red" %)**Important note:** 257 257 258 258 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. 259 259 260 -2. In firmwareversionv1.5,Roll&Pitchdisabled bydefault.338 +2. In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below: 261 261 262 -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: 263 263 264 - 265 265 [[image:1664502116362-706.png]] 266 266 267 267 344 +3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 268 268 269 -4. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 270 - 271 271 [[image:1664502166010-515.png]] 272 272 273 273 ... ... @@ -274,15 +274,15 @@ 274 274 275 275 ==== (% style="color:blue" %)**Alarm:**(%%) ==== 276 276 277 -Example: 352 +**Example: ** 0x4B & 0x40 >> 6 = 0x01 278 278 279 279 280 280 ==== (% style="color:blue" %)**BAT:**(%%) ==== 281 281 282 -Example: 0CDD& 0x3FFF ⇒3293(mV).357 +**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV). 283 283 284 284 ((( 285 -The battery info shows the currentvoltage, for(% style="color:blue"%)**TrackerD**(%%)version which powered byli-on battery.User can use below mapping to indicate the battery in percentage: \360 +The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \ 286 286 ))) 287 287 288 288 * > 4.0v : 80% ~~ 100% ... ... @@ -292,21 +292,37 @@ 292 292 * < 3.39v: 0~~20% 293 293 294 294 370 +==== (% style="color:blue" %)**MOD:**(%%) ==== 295 295 372 +**Example: ** (0x60>>6) & 0x3f =1 373 + 374 +**Set the format of GPS data uplink link:** 375 + 376 +(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values 377 +(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values 378 + 379 + 380 +**Set the format of BLE data uplink link:** 381 + 382 +(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon 383 + 384 + 296 296 ==== (% style="color:blue" %)**LON:**(%%) ==== 297 297 387 +**Example:** (0x60>>5) & 0x01=1. 298 298 299 299 Enable/Disable LED activity for uplink 300 300 301 301 ((( 302 -0x00: Disable LED indicator. 392 +(% style="color:#037691" %)**0x00:** (%%) Disable LED indicator. 303 303 ))) 304 304 305 305 ((( 306 -0x01: Enable LED indicator (Default Value) 396 +(% style="color:#037691" %)**0x01:** (%%) Enable LED indicator (Default Value) 307 307 ))) 308 308 309 309 400 + 310 310 ==== (% style="color:blue" %)**Hum:**(%%) ==== 311 311 312 312 0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree ... ... @@ -318,15 +318,57 @@ 318 318 319 319 320 320 321 -=== 2. 3.3HistoryGNSS Positioning ===412 +=== 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) === 322 322 323 323 415 +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) 324 324 325 -=== 2.3.4 BLE positioning Payload(Fport2) === 326 326 418 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) 419 +|=(% scope="row" style="width: 50px;" %)((( 420 +**Size(bytes)** 421 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1 422 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 423 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 424 +)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 327 327 328 -Different MODE has different payload: (% style="color:blue" %)**MODE=2** 426 +(% class="wikigeneratedid" %) 427 +[[image:1665301687277-443.png]] 329 329 429 + 430 + 431 +=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 432 + 433 + 434 +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 + 436 + 437 +(% style="color:red" %)**Note for this mode:** 438 + 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. 441 +* 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 442 + 443 +The payload is 15 bytes, as below. 444 + 445 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %) 446 +|=(% scope="row" %)((( 447 +**Size(bytes)** 448 +)))|4|4|2|1|1|1|1|1 449 +|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 450 + 451 +[[image:image-20221009160309-2.png]] 452 + 453 + 454 + 455 +=== 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 456 + 457 + 458 +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. 459 + 460 +User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings. 461 + 462 + 330 330 (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 331 331 |=(% scope="row" style="width: 60px;" %)((( 332 332 **Size(bytes)** ... ... @@ -346,7 +346,7 @@ 346 346 [[image:1664502425687-834.png]] 347 347 348 348 349 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 482 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 350 350 * (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 351 351 * (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 352 352 * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. ... ... @@ -355,10 +355,9 @@ 355 355 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 356 356 357 357 491 +=== 2.4.6 Add Payload format in TTN V3 === 358 358 359 -=== 2.3.5 Add Payload format in TTN V3 === 360 360 361 - 362 362 In TTN V3, use can add a custom payload so it shows friendly. 363 363 364 364 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** ... ... @@ -367,8 +367,9 @@ 367 367 [[image:1664502649601-895.png]] 368 368 369 369 370 -Add the decoder from this link: 502 +Add the decoder from this link: 371 371 504 +[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] 372 372 373 373 Save the change the uplink message will be parsed. As below: 374 374 ... ... @@ -376,41 +376,49 @@ 376 376 377 377 378 378 379 -== 2. 4Integrate with Datacake ==512 +== 2.5 Integrate with Datacake == 380 380 381 - 382 -((( 383 383 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. 384 -))) 385 385 386 -((( 387 387 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]] 388 -))) 389 389 390 - 391 391 [[image:1664502695771-538.png]] 392 392 393 393 394 394 395 -== 2. 5Integrate with Tago ==522 +== 2.6 Integrate with Tago == 396 396 397 397 398 -((( 399 -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. 400 -))) 401 401 402 -((( 526 +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 + 403 403 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]] 404 -))) 405 405 406 406 531 + 407 407 [[image:1664502715371-321.png]] 408 408 409 409 410 410 411 -== 2. 6Alarm Mode ==536 +== 2.7 Datalog Feature == 412 412 413 413 539 +total 273 entries,by default, 540 + 541 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 542 + 543 +Example use case. 544 + 545 +[[image:image-20221009234703-2.png||height="328" width="899"]] 546 + 547 + 548 +[[image:image-20221009234629-1.png||height="390" width="577"]] 549 + 550 + 551 + 552 +== 2.8 Alarm Mode == 553 + 554 + 414 414 ((( 415 415 User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 416 416 ))) ... ... @@ -417,7 +417,7 @@ 417 417 418 418 419 419 ((( 420 -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. 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 exits alert mode. 421 421 ))) 422 422 423 423 ... ... @@ -425,7 +425,7 @@ 425 425 Two ways to exit alarm mode: 426 426 ))) 427 427 428 -* Server send a downlink command to exit. 569 +* Server sends a downlink command to exit. 429 429 * User fast press the RED button 10 times. 430 430 431 431 ((( ... ... @@ -434,13 +434,16 @@ 434 434 435 435 436 436 437 -== 2. 7SportsMode ==578 +== 2.9 Transport Mode == 438 438 439 439 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. 440 440 441 -== 2.8 LED Status == 442 442 443 443 585 +== 2.10 LED Status == 586 + 587 + 444 444 (% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 445 445 |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 446 446 |(% 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 ... ... @@ -456,10 +456,9 @@ 456 456 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 457 457 458 458 603 +== 2.11 Button Function == 459 459 460 -== 2.9 Button Function == 461 461 462 - 463 463 (% style="color:blue" %)**RESET button:** 464 464 465 465 [[image:1664502835802-546.png]] ... ... @@ -479,10 +479,9 @@ 479 479 |(% 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. 480 480 481 481 625 +== 2.12 USB Port Function == 482 482 483 -== 2.10 USB Port Function == 484 484 485 - 486 486 The USB interface of TrackerD has below functions: 487 487 488 488 * Power on the device ... ... @@ -491,7 +491,6 @@ 491 491 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 492 492 493 493 494 - 495 495 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 496 496 497 497 ... ... @@ -516,11 +516,9 @@ 516 516 [[image:1664503022490-662.png]] 517 517 518 518 519 - 520 520 [[image:1664503035713-500.png]] 521 521 522 522 523 - 524 524 [[image:1664503047675-651.png]] 525 525 526 526 ... ... @@ -564,16 +564,16 @@ 564 564 565 565 566 566 567 -=== 3.2.3 Set SportsMode Packet transmission interval ===706 +=== 3.2.3 Set Transport Mode Packet transmission interval === 568 568 569 569 570 -Set sport spacket transmit interval709 +Set Transport Mode packet transmit interval 571 571 572 572 * (% style="color:blue" %)**AT Command:** 573 573 574 574 (% style="color:#037691" %)**AT+MTDC=xx. ** 575 575 576 -Example: AT+MTDC=300000 **~-~-> ** Set SportsMode Packet Interval to 300 seconds. TrackerD will send every 300 seconds inSportsmode, Default Value: 300000715 +Example: AT+MTDC=300000 **~-~-> ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000 577 577 578 578 579 579 * (% style="color:blue" %)**Downlink Payload (prefix 0x03):** ... ... @@ -613,16 +613,16 @@ 613 613 614 614 615 615 616 -=== 3.2.6 Disable/Enable movement detect(Debug Only)===755 +=== 3.2.6 Disable/Enable Transport Mode === 617 617 618 618 619 -User can use this feature to check andet thread holeof movement detect758 +Users can use this feature to enable/disable Transport Mode. 620 620 621 621 * (% style="color:blue" %)**AT Command:** 622 622 623 623 (% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)** 624 624 625 -Example: AT+ INTWK =1 **~-~-> ** Enable detectmovement.764 +Example: AT+ INTWK =1 **~-~-> ** Enable Transport Mode. 626 626 627 627 628 628 * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):** ... ... @@ -634,35 +634,38 @@ 634 634 === 3.2.7 Set Positioning Mode === 635 635 636 636 637 -SMOD define the how TrackerD scan and uplink date.776 +SMOD define how TrackerD scan and uplink data: 638 638 639 -GPS室外定位模式: 设备默认模式,设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是3分钟定位,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。GPS还有一种logdata模式,在断网的情况下将数据存储下来,等到有网的时候,一次将数据以每10秒上报。 640 640 641 - BLE室内定位模式:设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是5秒,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每3分钟发送一次)。779 +* (% style="color:blue" %)**AT Command:** 642 642 643 - GPS和BLE混动模式:设备入网后会发送device当前模式下的信息,随后立即判断是否在室内,如果是就进行BLE定位,不是就GPS定位。如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。781 +(% style="color:#037691" %)**AT+SMOD=aa,bb,cc** 644 644 645 - 运动模式:设备入网后会发送device当前模式下的信息,随后发送GPS定位数据,设备判断是否在运动,没有运动传感器没有检测到动作,立即进入静止状态(默认20分钟),如果产生运动,将每5分钟发送一次数据,再第五分钟后检测设备有误运动,无将切换到静止状态,有立即发送数据。783 +(% style="color:#037691" %)** aa:** 646 646 785 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)only get and uplink GPS location info. 786 +* (% style="color:red" %)**2: BLE ONLY: **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking. 787 +* (% 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. 647 647 789 +(% style="color:#037691" %)**bb:** 648 648 649 -* (% style="color:blue" %)**AT Command:** 791 +* (% style="color:red" %)**0 : **(%%)GPS+ BAT+ State+Tem&Hum 792 +* (% style="color:red" %)**1 :**(%%) GPS +BAT State 650 650 651 -(% style="color:#037691" %)** AT+SMOD=xx.**794 +(% style="color:#037691" %)**cc: ** 652 652 796 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 653 653 654 - **Example:** 798 +(% style="color:blue" %)**Example:** 655 655 656 - AT+ SMOD =1,0 **~-~-> ** GPS+ BAT+ State+Tem&Hum 800 + AT+ SMOD =1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 801 + AT+ SMOD =1,1,0 ~-~-> GPS +BAT State 802 + AT+ SMOD =2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 657 657 658 - AT+ SMOD =1,1 **~-~->** GPS +BAT State 659 659 660 - AT+ SMOD =2,3 **~-~->** (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。 661 - 662 - 663 663 * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** 664 664 665 -(% style="color:#037691" %)**0xA5 01 00** (%%) ~/~/ Same as AT+ SMOD =1,0 807 +(% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+ SMOD =1,0,0 666 666 667 667 668 668 ... ... @@ -679,7 +679,7 @@ 679 679 680 680 (% style="color:#037691" %)**AT+FTIME=xx** (%%) **~-~-> ** Set to use xx as max fix time. 681 681 682 -Example: AT+FTIME=150 824 +**Example:** AT+FTIME=150 683 683 684 684 685 685 * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):** ... ... @@ -688,7 +688,7 @@ 688 688 689 689 690 690 691 -=== 3. 3.9 Set PDOP value for GPS fix accuracy ===833 +=== 3.2.9 Set PDOP value for GPS fix accuracy === 692 692 693 693 694 694 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. ... ... @@ -716,7 +716,7 @@ 716 716 717 717 * (% style="color:blue" %)**AT Command:** 718 718 719 -(% style="color:#037691" %)**AT+CFM=xx .**861 +(% style="color:#037691" %)**AT+CFM=xx** 720 720 721 721 722 722 **~ Example:** ... ... @@ -732,6 +732,46 @@ 732 732 733 733 734 734 877 +=== 3.2.10 Auto Send None-ACK messages === 878 + 879 + 880 +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. 881 + 882 + 883 +* (% style="color:blue" %)**AT Command: AT+PNACKMD** 884 + 885 +The default factory setting is 0. 886 + 887 + 888 +**Command Example Function Response:** 889 + 890 +(% style="color:#037691" %)**AT+PNACKMD=1** (%%) ~/~/ Poll None-ACK message OK 891 + 892 + 893 +* (% style="color:blue" %)**Downlink Command: 0x34** 894 + 895 +Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 896 + 897 + 898 + 899 +=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 900 + 901 + 902 +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. 903 + 904 +Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled. 905 + 906 +(% style="color:blue" %)**AT Command:**(%%) 907 + AT+BLEMASK=123456 ~/~/ Set BLEMASK = 123456 908 + AT+BLEMASK=0 ~/~/ disable BLEMASK 909 + 910 + 911 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**(%%) 912 +Example: 913 +0xA5010203040506 ~/~/ Set BLEMASK to 123456 914 + 915 + 916 + 735 735 = 4. Setting for Different Scenarios = 736 736 737 737 ... ... @@ -772,9 +772,10 @@ 772 772 [[image:1664503574618-659.png]] 773 773 774 774 957 + 775 775 (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 776 776 777 -[[https:~~/~~/ www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]960 +[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]] 778 778 779 779 780 780 Users need to use below files: ... ... @@ -811,12 +811,24 @@ 811 811 [[image:1664503635019-941.png]] 812 812 813 813 997 + 814 814 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 815 815 816 816 [[image:1664503715811-892.png]] 817 817 818 818 1003 +(% 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. 819 819 1005 +[[image:image-20221024105643-1.png]] 1006 + 1007 +**~ Figure1** 1008 + 1009 + 1010 +[[image:image-20221024105643-2.png]] 1011 + 1012 + **Figure2** 1013 + 1014 + 820 820 * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]** 821 821 822 822 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: ... ... @@ -875,9 +875,6 @@ 875 875 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 876 876 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 877 877 878 - 879 - 880 - 881 881 = 8. Order Info = 882 882 883 883 ... ... @@ -894,7 +894,6 @@ 894 894 * (% style="color:red" %)**US915**(%%): Default frequency band US915 895 895 896 896 897 - 898 898 = 9. Packing Info = 899 899 900 900 ... ... @@ -909,7 +909,6 @@ 909 909 * Weight: 50g 910 910 911 911 912 - 913 913 = 10. Support = 914 914 915 915 ... ... @@ -917,7 +917,6 @@ 917 917 * 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]]. 918 918 919 919 920 - 921 921 = 11. Reference = 922 922 923 923
- 1665301570342-765.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +31.6 KB - Content
- 1665301636888-168.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +36.6 KB - Content
- 1665301687277-443.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +22.6 KB - Content
- 1665301786397-168.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +22.6 KB - Content
- image-20221006181316-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +17.7 KB - Content
- image-20221006181357-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +88.0 KB - Content
- image-20221009160220-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +46.4 KB - Content
- image-20221009160309-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +57.2 KB - Content
- image-20221009234629-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +222.9 KB - Content
- image-20221009234703-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +136.4 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