Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Xiaoling on 2025/04/27 16:48
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -97,9 +97,6 @@ 97 97 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm 98 98 * Tracking: max: 38mA 99 99 100 - 101 - 102 - 103 103 == 1.3 Features == 104 104 105 105 ... ... @@ -118,9 +118,6 @@ 118 118 * Tri-color LED, Alarm button 119 119 * Datalog 120 120 121 - 122 - 123 - 124 124 == 1.4 Applications == 125 125 126 126 ... ... @@ -127,9 +127,6 @@ 127 127 * Logistics and Supply Chain Management 128 128 * Human tracking 129 129 130 - 131 - 132 - 133 133 = 2.1 Use TrackerD = 134 134 135 135 ... ... @@ -192,9 +192,8 @@ 192 192 (% 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. 193 193 194 194 195 -== 2.3 186 +== 2.3 Positioning Mode(SMOD) == 196 196 197 - 198 198 Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 199 199 200 200 * (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)only get and uplink GPS location info. ... ... @@ -204,13 +204,12 @@ 204 204 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 205 205 206 206 197 +== 2.3 Uplink Payload == 207 207 208 -== 2.4 Uplink Payload == 209 209 200 +=== 2.3.1 Uplink FPORT~=5, Device Status === 210 210 211 -=== 2.4.1 Uplink FPORT~=5, Device Status === 212 212 213 - 214 214 Uplink the device configures with FPORT=5. Once LGT92 Joined the network, it will uplink this message to the server. After first uplink, LHT52 will uplink Device Status every 12 hours. 215 215 216 216 ... ... @@ -259,7 +259,7 @@ 259 259 260 260 261 261 262 -=== 2. 4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===251 +=== 2.3.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 263 263 264 264 265 265 User can use **AT+SMOD=1,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes, please note that 15 bytes won't work on DR0 on US915/AU915 frequency band. ... ... @@ -359,7 +359,7 @@ 359 359 360 360 361 361 362 -=== 2. 4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===351 +=== 2.3.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) === 363 363 364 364 365 365 The default uplink payload includes totally 11 bytes. The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity) ... ... @@ -373,21 +373,22 @@ 373 373 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 374 374 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 375 375 365 + 376 376 (% class="wikigeneratedid" %) 377 377 [[image:1665301687277-443.png]] 378 378 379 379 380 380 381 -=== 2. 4.4 Uplink FPORT~=4, History GNSS Positioning ===371 +=== 2.3.4 Uplink FPORT~=4, History GNSS Positioning === 382 382 383 383 384 384 Set [[PNACKMD=1>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/#H4.13AutoSendNone-ACKmessages]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery. 385 385 386 386 387 - (% style="color:red" %)**Note for this mode:**377 +**Note for this mode:** 388 388 389 389 * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server. 390 -* 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.380 +* b) TrackerD will send data in **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. 391 391 392 392 The payload is 15 bytes, as below. 393 393 ... ... @@ -395,13 +395,13 @@ 395 395 |=(% scope="row" %)((( 396 396 **Size(bytes)** 397 397 )))|4|4|2|1|1|1|1|1 398 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 388 +|=**Value**|[[Latitude>>path:#Location]]|[[Longitude>>path:#Location]]|[[Year>>path:#Alarm]]|Month|Day|Hous|Min|[[Sen>>path:#Pitch]] 399 399 400 400 [[image:1665301786397-168.png]] 401 401 402 402 403 403 404 -=== 2. 4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===394 +=== 2.3.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 405 405 406 406 407 407 (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) ... ... @@ -431,7 +431,7 @@ 431 431 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 432 432 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 433 433 434 -=== 2. 4.5 Add Payload format in TTN V3 ===424 +=== 2.3.5 Add Payload format in TTN V3 === 435 435 436 436 437 437 In TTN V3, use can add a custom payload so it shows friendly. ... ... @@ -451,7 +451,7 @@ 451 451 452 452 453 453 454 -== 2. 5Integrate with Datacake ==444 +== 2.4 Integrate with Datacake == 455 455 456 456 457 457 ((( ... ... @@ -467,7 +467,7 @@ 467 467 468 468 469 469 470 -== 2. 6Integrate with Tago ==460 +== 2.5 Integrate with Tago == 471 471 472 472 473 473 ((( ... ... @@ -483,11 +483,11 @@ 483 483 484 484 485 485 486 -== 2. 7Datalog Feature ==476 +== 2.6 Datalog Feature == 487 487 488 488 total 273 entries,by default disable 489 489 490 -== 2. 8Alarm Mode ==480 +== 2.6 Alarm Mode == 491 491 492 492 493 493 ((( ... ... @@ -513,13 +513,13 @@ 513 513 514 514 515 515 516 -== 2. 9Transport Mode ==506 +== 2.7 Transport Mode == 517 517 518 518 519 519 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. 520 520 521 521 522 -== 2. 10LED Status ==512 +== 2.8 LED Status == 523 523 524 524 525 525 (% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) ... ... @@ -536,7 +536,7 @@ 536 536 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 537 537 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 538 538 539 -== 2. 11Button Function ==529 +== 2.9 Button Function == 540 540 541 541 542 542 (% style="color:blue" %)**RESET button:** ... ... @@ -557,7 +557,7 @@ 557 557 |(% 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 558 558 |(% 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. 559 559 560 -== 2.1 2USB Port Function ==550 +== 2.10 USB Port Function == 561 561 562 562 563 563 The USB interface of TrackerD has below functions: