Skip to Content
Last modified by Xiaoling on 2025/04/27 16:48
From version 72.1
edited by Edwin Chen
on 2022/10/09 23:47
Change comment: There is no comment for this version
To version 58.1
edited by Edwin Chen
on 2022/10/08 17:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,3 +1,5 @@
1 +== ==
2 +
1 1  (% style="text-align:center" %)
2 2  [[image:1664505654417-133.png]]
3 3  
... ... @@ -183,10 +183,8 @@
183 183  (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
184 184  
185 185  
188 +== 2.3 Positioning Mode(SMOD) ==
186 186  
187 -== 2.3  Positioning Mode(SMOD) ==
188 -
189 -
190 190  Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
191 191  
192 192  * (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
... ... @@ -196,23 +196,18 @@
196 196  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
197 197  
198 198  
199 +== 2.3 Uplink Payload ==
199 199  
200 -== 2.4  Uplink Payload ==
201 201  
202 +=== 2.3.1 Uplink FPORT~=5, Device Status ===
202 202  
203 -=== 2.4.1 Uplink FPORT~=5, Device Status ===
204 -
205 -
206 206  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.
207 207  
206 +|=(% style="width: 150px;" %)**Size (bytes)**|=(% style="width: 233px;" %)**1**|=(% style="width: 150px;" %)**2**|=(% style="width: 164px;" %)**1**|=(% style="width: 215px;" %)**1**|=(% style="width: 94px;" %)2|=(% style="width: 516px;" %)**2**|=(% style="width: 516px;" %)1
207 +|(% style="width:150px" %)**Value**|(% style="width:233px" %)Sensor Model|(% style="width:150px" %)Firmware Version|(% style="width:164px" %)Frequency Band|(% style="width:215px" %)Sub-band|(% style="width:94px" %)BAT|(% style="width:516px" %)SMOD|(% style="width:516px" %)Status
208 208  
209 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
210 -|=(% 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
211 -|=(% 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
209 +[[image:image-20221006181357-2.png]]
212 212  
213 -[[image:1665301570342-765.png]]
214 -
215 -
216 216  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"]]
217 217  
218 218  **Sensor Model**: For TrackerD, this value is 0x13.
... ... @@ -250,26 +250,25 @@
250 250  Use can also get the Device Status uplink through the downlink command:
251 251  
252 252  
248 +=== 2.3.2 Uplink FPORT~=2, Realtime GNSS Positioning ===
253 253  
254 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
255 255  
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. )
256 256  
257 -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.
258 258  
259 -
260 260  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
261 261  |=(% scope="row" style="width: 50px;" %)(((
262 262  **Size(bytes)**
263 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
264 -2
257 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)(((
258 +2(optional)
265 265  )))|(% style="width:87px" %)(((
266 -2
260 +2(optional)
267 267  )))
268 268  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
269 269  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
270 -)))|(% 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:"]]
271 271  
272 -[[image:1665301636888-168.png]]
266 +[[image:1664501958445-288.png]]
273 273  
274 274  
275 275  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -278,15 +278,11 @@
278 278  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
279 279  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
280 280  
281 -==== ====
282 -
283 -==== ====
284 -
285 285  ==== (% style="color:blue" %)**FLAG:**(%%) ====
286 286  
287 287  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
288 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit
289 -|=(% 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 
290 290  
291 291  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
292 292  
... ... @@ -300,14 +300,15 @@
300 300  
301 301  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.
302 302  
303 -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:
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:
304 304  
305 305  
306 306  [[image:1664502116362-706.png]]
307 307  
308 308  
309 -3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
310 310  
300 +4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
301 +
311 311  [[image:1664502166010-515.png]]
312 312  
313 313  
... ... @@ -317,13 +317,12 @@
317 317  Example:  0x4B & 0x40 >> 6 = 0x01
318 318  
319 319  
320 -
321 321  ==== (% style="color:blue" %)**BAT:**(%%) ====
322 322  
323 323  Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
324 324  
325 325  (((
326 -The battery info shows the battery voltage, User can use the below 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: \
327 327  )))
328 328  
329 329  * > 4.0v :  80% ~~ 100%
... ... @@ -356,51 +356,15 @@
356 356  
357 357  
358 358  
359 -=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
349 +=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
360 360  
361 361  
362 -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)
363 363  
353 +=== 2.3.4 BLE positioning Payload(Fport2) ===
364 364  
365 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
366 -|=(% scope="row" style="width: 50px;" %)(((
367 -**Size(bytes)**
368 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
369 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
370 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
371 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
372 372  
373 -(% class="wikigeneratedid" %)
374 -[[image:1665301687277-443.png]]
356 +Different MODE has different payload:  (% style="color:blue" %)**MODE=2**
375 375  
376 -
377 -
378 -=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
379 -
380 -
381 -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.
382 -
383 -
384 -(% style="color:red" %)**Note for this mode:**
385 -
386 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
387 -* 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.
388 -
389 -The payload is 15 bytes, as below.
390 -
391 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
392 -|=(% scope="row" %)(((
393 -**Size(bytes)**
394 -)))|4|4|2|1|1|1|1|1
395 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
396 -
397 -[[image:image-20221009160309-2.png]]
398 -
399 -
400 -
401 -=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
402 -
403 -
404 404  (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
405 405  |=(% scope="row" style="width: 60px;" %)(((
406 406  **Size(bytes)**
... ... @@ -428,10 +428,9 @@
428 428  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
429 429  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
430 430  
385 +=== 2.3.5 Add Payload format in TTN V3 ===
431 431  
432 -=== 2.4.6  Add Payload format in TTN V3 ===
433 433  
434 -
435 435  In TTN V3, use can add a custom payload so it shows friendly.
436 436  
437 437  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
... ... @@ -449,7 +449,7 @@
449 449  
450 450  
451 451  
452 -== 2.5 Integrate with Datacake ==
405 +== 2.4 Integrate with Datacake ==
453 453  
454 454  
455 455  (((
... ... @@ -465,7 +465,7 @@
465 465  
466 466  
467 467  
468 -== 2.6 Integrate with Tago ==
421 +== 2.5 Integrate with Tago ==
469 469  
470 470  
471 471  (((
... ... @@ -481,24 +481,12 @@
481 481  
482 482  
483 483  
484 -== 2.7  Datalog Feature ==
437 +== 2.6 Datalog Feature ==
485 485  
486 486  
487 -total 273 entries,by default disable
440 +== 2.6 Alarm Mode ==
488 488  
489 489  
490 -Example use case.
491 -
492 -[[image:image-20221009234703-2.png||height="328" width="899"]]
493 -
494 -
495 -[[image:image-20221009234629-1.png||height="390" width="577"]]
496 -
497 -
498 -
499 -== 2.8 Alarm Mode ==
500 -
501 -
502 502  (((
503 503  User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
504 504  )))
... ... @@ -522,16 +522,15 @@
522 522  
523 523  
524 524  
525 -== 2.9 Transport Mode ==
466 +== 2.7 Transport Mode ==
526 526  
527 527  
528 528  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.
529 529  
530 530  
472 +== 2.8 LED Status ==
531 531  
532 -== 2.10 LED Status ==
533 533  
534 -
535 535  (% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
536 536  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
537 537  |(% 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
... ... @@ -546,10 +546,9 @@
546 546  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
547 547  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
548 548  
489 +== 2.9 Button Function ==
549 549  
550 -== 2.11 Button Function ==
551 551  
552 -
553 553  (% style="color:blue" %)**RESET button:**
554 554  
555 555  [[image:1664502835802-546.png]]
... ... @@ -568,10 +568,9 @@
568 568  |(% 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
569 569  |(% 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.
570 570  
510 +== 2.10 USB Port Function ==
571 571  
572 -== 2.12 USB Port Function ==
573 573  
574 -
575 575  The USB interface of TrackerD has below functions:
576 576  
577 577  * Power on the device
... ... @@ -579,7 +579,6 @@
579 579  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
580 580  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
581 581  
582 -
583 583  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
584 584  
585 585  
... ... @@ -701,16 +701,16 @@
701 701  
702 702  
703 703  
704 -=== 3.2.6 Disable/Enable Transport Mode ===
641 +=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
705 705  
706 706  
707 -Users can use this feature to enable/disable Transport Mode.
644 +User can use this feature to check and set thread hole of movement detect
708 708  
709 709  * (% style="color:blue" %)**AT Command:**
710 710  
711 711  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
712 712  
713 -Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
650 +Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
714 714  
715 715  
716 716  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
... ... @@ -727,25 +727,9 @@
727 727  
728 728  * (% style="color:blue" %)**AT Command:**
729 729  
730 -(% style="color:#037691" %)**AT+SMOD=aa,bb**
667 +(% style="color:#037691" %)**AT+SMOD=xx. **
731 731  
732 -(% style="color:#037691" %)** aa:**
733 733  
734 -* (% style="color:#037691" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
735 -* (% style="color:#037691" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
736 -* (% style="color:#037691" %)**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
737 -
738 -(% style="color:#037691" %)**bb:**
739 -
740 -(% style="color:#037691" %)** if aa = 1: **
741 -
742 -* (% style="color:#037691" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
743 -* (% style="color:#037691" %)**1 :**(%%)  GPS +BAT State
744 -
745 -(% style="color:#037691" %)** if aa = 2: **
746 -
747 -* (% style="color:#037691" %)**3 :  **(%%)(iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
748 -
749 749   **Example:**
750 750  
751 751   AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
... ... @@ -752,7 +752,7 @@
752 752  
753 753   AT+ SMOD =1,1    **~-~->**  GPS +BAT State
754 754  
755 - AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
676 + AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
756 756  
757 757  
758 758  * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
... ... @@ -783,7 +783,7 @@
783 783  
784 784  
785 785  
786 -=== 3.2.9 Set PDOP value for GPS fix accuracy ===
707 +=== 3.3.9 Set PDOP value for GPS fix accuracy ===
787 787  
788 788  
789 789  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.
... ... @@ -906,7 +906,6 @@
906 906  [[image:1664503635019-941.png]]
907 907  
908 908  
909 -
910 910  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
911 911  
912 912  [[image:1664503715811-892.png]]
... ... @@ -971,7 +971,6 @@
971 971  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
972 972  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
973 973  
974 -
975 975  = 8.  Order Info =
976 976  
977 977  
... ... @@ -987,7 +987,6 @@
987 987  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
988 988  * (% style="color:red" %)**US915**(%%): Default frequency band US915
989 989  
990 -
991 991  = 9.  Packing Info =
992 992  
993 993  
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