Last modified by Xiaoling on 2023/12/27 09:15

From version 75.1
edited by Edwin Chen
on 2022/10/13 23:07
Change comment: There is no comment for this version
To version 78.5
edited by Xiaoling
on 2022/10/14 14:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -98,6 +98,7 @@
98 98  * Tracking: max: 38mA
99 99  
100 100  
101 +
101 101  == 1.3  Features ==
102 102  
103 103  
... ... @@ -117,6 +117,7 @@
117 117  * Datalog
118 118  
119 119  
121 +
120 120  == 1.4  Applications ==
121 121  
122 122  
... ... @@ -124,6 +124,7 @@
124 124  * Human tracking
125 125  
126 126  
129 +
127 127  = 2.1 Use TrackerD =
128 128  
129 129  
... ... @@ -208,7 +208,9 @@
208 208  
209 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.
210 210  
214 +Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
211 211  
216 +
212 212  (% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
213 213  |=(% 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
214 214  |=(% 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
... ... @@ -285,19 +285,15 @@
285 285  
286 286  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
287 287  
288 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
289 -|(% 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
290 -|(% style="width:77px" %)**Value**|(% style="width:82px" %)Reserve|(% style="width:106px" %)PNACKMD|(% style="width:67px" %)LON|(% style="width:121px" %)Transport** **Mode
293 +(% border="1.5" style="background-color:#ffffcc; color:green; width:417px" %)
294 +|(% 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
295 +|(% 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 291  
292 -
293 293  
294 -
295 -
296 -
297 297  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
298 298  
299 299  
300 -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.
301 +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,
301 301  
302 302  
303 303  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
... ... @@ -336,6 +336,7 @@
336 336  * Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
337 337  * Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
338 338  
340 +
339 339  (% style="color:red" %)**Important note:**
340 340  
341 341  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.
... ... @@ -372,6 +372,7 @@
372 372  * < 3.39v:  0~~20%
373 373  
374 374  
377 +
375 375  ==== (% style="color:blue" %)**MOD:**(%%) ====
376 376  
377 377  **Example: ** (0x60>>6)& 0x3f =1.
... ... @@ -417,7 +417,7 @@
417 417  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
418 418  
419 419  
420 -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)
423 +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)
421 421  
422 422  
423 423  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
... ... @@ -436,7 +436,7 @@
436 436  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
437 437  
438 438  
439 -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.
442 +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.
440 440  
441 441  
442 442  (% style="color:red" %)**Note for this mode:**
... ... @@ -443,6 +443,7 @@
443 443  
444 444  * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
445 445  * 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.
449 +* 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
446 446  
447 447  The payload is 15 bytes, as below.
448 448  
... ... @@ -543,8 +543,9 @@
543 543  == 2.7  Datalog Feature ==
544 544  
545 545  
546 -total 273 entries,by default disable
550 +total 273 entries,by default,
547 547  
552 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
548 548  
549 549  Example use case.
550 550  
... ... @@ -606,7 +606,6 @@
606 606  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
607 607  
608 608  
609 -
610 610  == 2.11 Button Function ==
611 611  
612 612  
... ... @@ -629,7 +629,6 @@
629 629  |(% 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.
630 630  
631 631  
632 -
633 633  == 2.12 USB Port Function ==
634 634  
635 635  
... ... @@ -641,7 +641,6 @@
641 641  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
642 642  
643 643  
644 -
645 645  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
646 646  
647 647