Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Xiaoling on 2025/04/27 16:48
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 4 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Edwin - Content
-
... ... @@ -1,3 +1,5 @@ 1 +== == 2 + 1 1 (% style="text-align:center" %) 2 2 [[image:1664505654417-133.png]] 3 3 ... ... @@ -199,17 +199,13 @@ 199 199 200 200 === 2.3.1 Uplink FPORT~=5, Device Status === 201 201 202 - 203 203 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. 204 204 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 205 205 206 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %) 207 -|=(% 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 208 -|=(% 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]] 209 209 210 -[[image:1665301570342-765.png]] 211 - 212 - 213 213 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"]] 214 214 215 215 **Sensor Model**: For TrackerD, this value is 0x13. ... ... @@ -247,11 +247,10 @@ 247 247 Use can also get the Device Status uplink through the downlink command: 248 248 249 249 250 - 251 251 === 2.3.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 252 252 253 253 254 -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 notethat15 bytes won't work on DR0 on US915/AU915 frequency band.251 +(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. ) 255 255 256 256 257 257 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) ... ... @@ -266,7 +266,7 @@ 266 266 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 267 267 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 268 268 269 -[[image:1665 301636888-168.png]]266 +[[image:1664501958445-288.png]] 270 270 271 271 272 272 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== ... ... @@ -278,8 +278,8 @@ 278 278 ==== (% style="color:blue" %)**FLAG:**(%%) ==== 279 279 280 280 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 281 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit 282 -|=(% 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 283 283 284 284 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 285 285 ... ... @@ -293,14 +293,15 @@ 293 293 294 294 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. 295 295 296 -2. Inthis mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:293 +2. When enable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below: 297 297 298 298 299 299 [[image:1664502116362-706.png]] 300 300 301 301 302 -3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 303 303 300 +4. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 301 + 304 304 [[image:1664502166010-515.png]] 305 305 306 306 ... ... @@ -315,7 +315,7 @@ 315 315 Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV). 316 316 317 317 ((( 318 -The battery info shows the battery voltage,User can usethebelow mapping to indicate the battery in percentage: \316 +The battery info shows the current voltage, for (% style="color:blue" %)**TrackerD**(%%) version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \ 319 319 ))) 320 320 321 321 * > 4.0v : 80% ~~ 100% ... ... @@ -347,10 +347,8 @@ 347 347 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree// 348 348 349 349 350 - 351 351 === 2.3.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) === 352 352 353 - 354 354 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) 355 355 356 356 ... ... @@ -363,37 +363,16 @@ 363 363 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 364 364 365 365 366 -(% class="wikigeneratedid" %) 367 -[[image:1665301687277-443.png]] 368 368 363 +=== 2.3. Uplink FPORT~= , History GNSS Positioning === 369 369 370 370 371 -=== 2.3.4 Uplink FPORT~=4, History GNSS Positioning === 372 372 367 +=== 2.3.4 BLE positioning Payload(Fport2) === 373 373 374 -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. 375 375 370 +Different MODE has different payload: (% style="color:blue" %)**MODE=2** 376 376 377 -**Note for this mode:** 378 - 379 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server. 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. 381 - 382 -The payload is 15 bytes, as below. 383 - 384 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %) 385 -|=(% scope="row" %)((( 386 -**Size(bytes)** 387 -)))|4|4|2|1|1|1|1|1 388 -|=**Value**|[[Latitude>>path:#Location]]|[[Longitude>>path:#Location]]|[[Year>>path:#Alarm]]|Month|Day|Hous|Min|[[Sen>>path:#Pitch]] 389 - 390 -[[image:1665301786397-168.png]] 391 - 392 - 393 - 394 -=== 2.3.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 395 - 396 - 397 397 (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 398 398 |=(% scope="row" style="width: 60px;" %)((( 399 399 **Size(bytes)** ... ... @@ -475,7 +475,6 @@ 475 475 476 476 == 2.6 Datalog Feature == 477 477 478 -total 273 entries,by default disable 479 479 480 480 == 2.6 Alarm Mode == 481 481 ... ... @@ -704,25 +704,9 @@ 704 704 705 705 * (% style="color:blue" %)**AT Command:** 706 706 707 -(% style="color:#037691" %)**AT+SMOD= aa,bb**681 +(% style="color:#037691" %)**AT+SMOD=xx. ** 708 708 709 -(% style="color:#037691" %)** aa:** 710 710 711 -* (% style="color:#037691" %)**1: GPS ONLY(Factory Settings): **(%%)only get and uplink GPS location info. 712 -* (% style="color:#037691" %)**2: BLE ONLY: **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking. 713 -* (% 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 714 - 715 -(% style="color:#037691" %)**bb:** 716 - 717 -(% style="color:#037691" %)** if aa = 1: ** 718 - 719 -* (% style="color:#037691" %)**0 : **(%%)GPS+ BAT+ State+Tem&Hum 720 -* (% style="color:#037691" %)**1 :**(%%) GPS +BAT State 721 - 722 -(% style="color:#037691" %)** if aa = 2: ** 723 - 724 -* (% style="color:#037691" %)**3 : **(%%)(iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 725 - 726 726 **Example:** 727 727 728 728 AT+ SMOD =1,0 **~-~-> ** GPS+ BAT+ State+Tem&Hum ... ... @@ -729,7 +729,7 @@ 729 729 730 730 AT+ SMOD =1,1 **~-~->** GPS +BAT State 731 731 732 - AT+ SMOD =2,3 **~-~->** (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 690 + AT+ SMOD =2,3 **~-~->** (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。 733 733 734 734 735 735 * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
- 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