<
From version < 80.1 >
edited by Edwin Chen
on 2022/10/22 00:15
To version < 77.1 >
edited by Edwin Chen
on 2022/10/13 23:15
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -284,16 +284,20 @@
284 284  
285 285  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
286 286  
287 -(% border="1.5" style="background-color:#ffffcc; color:green; width:417px" %)
288 -|(% 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
289 -|(% 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"]]
287 +(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
288 +|(% style="width:77px" %)**Size(bit)**|(% style="width:82px" %)5 Bits|(% style="width:106px" %)1 Bit|(% style="width:67px" %)1 Bit|(% style="width:121px" %)1 Bit
289 +|(% style="width:77px" %)**Value**|(% style="width:82px" %)Reserve|(% style="width:106px" %)PNACKMD|(% style="width:67px" %)LON|(% style="width:121px" %)Transport** **Mode
290 290  
291 +
292 +
291 291  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
292 292  
293 293  
294 294  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,
295 295  
298 +(% style="color:red" %)Please note that 15 bytes won't work on DR0 on US915/AU915 frequency band. IoT server will see NULL payload in this case.(%%)
296 296  
300 +
297 297  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
298 298  |=(% scope="row" style="width: 50px;" %)(((
299 299  **Size(bytes)**
... ... @@ -366,7 +366,7 @@
366 366  
367 367  ==== (% style="color:blue" %)**MOD:**(%%) ====
368 368  
369 -**Example: ** (0x60>>6) & 0x3f =1
373 +**Example: ** (0x60>>6)& 0x3f =1.
370 370  
371 371  **Set the format of GPS data uplink link:**
372 372  
... ... @@ -409,7 +409,7 @@
409 409  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
410 410  
411 411  
412 -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)
416 +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)
413 413  
414 414  
415 415  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
... ... @@ -428,7 +428,7 @@
428 428  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
429 429  
430 430  
431 -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 +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.
432 432  
433 433  
434 434  (% style="color:red" %)**Note for this mode:**
... ... @@ -435,7 +435,6 @@
435 435  
436 436  * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
437 437  * 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.
438 -* 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
439 439  
440 440  The payload is 15 bytes, as below.
441 441  
... ... @@ -451,9 +451,7 @@
451 451  
452 452  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
453 453  
454 -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.
455 455  
456 -
457 457  (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
458 458  |=(% scope="row" style="width: 60px;" %)(((
459 459  **Size(bytes)**
... ... @@ -473,7 +473,7 @@
473 473  [[image:1664502425687-834.png]]
474 474  
475 475  
476 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
477 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
477 477  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
478 478  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
479 479  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
... ... @@ -492,9 +492,8 @@
492 492  [[image:1664502649601-895.png]]
493 493  
494 494  
495 -Add the decoder from this link: 
496 +Add the decoder from this link:
496 496  
497 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
498 498  
499 499  Save the change the uplink message will be parsed. As below:
500 500  
... ... @@ -537,9 +537,8 @@
537 537  == 2.7  Datalog Feature ==
538 538  
539 539  
540 -total 273 entries,by default,
540 +total 273 entries,by default disable
541 541  
542 -User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
543 543  
544 544  Example use case.
545 545  
... ... @@ -773,7 +773,7 @@
773 773  === 3.2.7 Set Positioning Mode ===
774 774  
775 775  
776 -SMOD define how TrackerD scan and uplink data:
775 +SMOD define the how TrackerD scan and uplink data:
777 777  
778 778  
779 779  * (% style="color:blue" %)**AT Command:**
... ... @@ -797,7 +797,7 @@
797 797  
798 798  (% style="color:blue" %)**Example:**
799 799  
800 - AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
799 + AT+ SMOD =1,0 ,0 ~-~->  GPS+ BAT+ State+Tem&Hum
801 801   AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
802 802   AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
803 803  
... ... @@ -895,23 +895,6 @@
895 895  Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
896 896  
897 897  
898 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
899 -
900 -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.
901 -
902 -Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.
903 -
904 -(% style="color:blue" %)**AT Command:**(%%)
905 - AT+BLEMASK=123456     ~/~/ Set BLEMASK = 123456
906 - AT+BLEMASK=0  ~/~/ disable BLEMASK
907 -
908 -
909 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**(%%)
910 -Example:
911 -0xA5010203040506    ~/~/ Set BLEMASK to 123456
912 -
913 -
914 -
915 915  = 4. Setting for Different Scenarios =
916 916  
917 917  
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0