Skip to Content
Last modified by Xiaoling on 2025/04/27 16:48
From version 166.1
edited by Bei Jinggeng
on 2022/12/07 12:05
Change comment: Uploaded new attachment "image-20221207120524-2.png", version {1}
To version 144.1
edited by Edwin Chen
on 2022/11/22 12:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Edwin
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:1664505654417-133.png||_mstalt="293696"]]
2 +[[image:1664505654417-133.png]]
3 3  
4 4  
5 5  
... ... @@ -31,12 +31,15 @@
31 31  (((
32 32  The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
33 33  )))
34 +)))
34 34  
35 35  (((
36 36  TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.
38 +
39 +
37 37  )))
38 38  
39 -[[image:1664499921684-770.png||_mstalt="298194"]]
42 +[[image:1664499921684-770.png]]
40 40  
41 41  
42 42  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
... ... @@ -93,7 +93,6 @@
93 93  * Tracking: max: 38mA
94 94  
95 95  
96 -
97 97  == 1.3  Features ==
98 98  
99 99  
... ... @@ -113,7 +113,6 @@
113 113  * Datalog
114 114  
115 115  
116 -
117 117  == 1.4  Applications ==
118 118  
119 119  
... ... @@ -121,7 +121,6 @@
121 121  * Human tracking
122 122  
123 123  
124 -
125 125  = 2.  Use TrackerD =
126 126  
127 127  == 2.1 How it works? ==
... ... @@ -136,7 +136,7 @@
136 136  Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example. 
137 137  
138 138  
139 -[[image:1664501652064-326.png||_mstalt="293306"]]
139 +[[image:1664501652064-326.png]]
140 140  
141 141  
142 142  
... ... @@ -148,7 +148,7 @@
148 148  Each TrackerD is shipped with a sticker with the default device EUI as below:
149 149  
150 150  
151 -[[image:1664501677253-891.png||_mstalt="296569"]]
151 +[[image:1664501677253-891.png]]
152 152  
153 153  
154 154  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -157,14 +157,14 @@
157 157  **__Add APP EUI in the application:__**
158 158  
159 159  
160 -[[image:1664501711466-918.png||_mstalt="295828"]]
160 +[[image:1664501711466-918.png]]
161 161  
162 162  
163 163  
164 -[[image:1664501721248-725.png||_mstalt="294450"]]
164 +[[image:1664501721248-725.png]]
165 165  
166 166  
167 -[[image:1664501734705-405.png||_mstalt="293306"]]
167 +[[image:1664501734705-405.png]]
168 168  
169 169  
170 170  
... ... @@ -171,15 +171,15 @@
171 171  **__Add APP KEY and DEV EUI:__**
172 172  
173 173  
174 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]]
174 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]]
175 175  
176 176  
177 177  
178 178  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
179 179  
180 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
180 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
181 181  
182 -[[image:1664502835802-546.png||_mstalt="295061"]]
182 +[[image:1664502835802-546.png]]
183 183  
184 184  
185 185  (% 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.
... ... @@ -211,7 +211,7 @@
211 211  |=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1
212 212  |=(% 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
213 213  
214 -[[image:1665301570342-765.png||_mstalt="294580"]]
214 +[[image:1665301570342-765.png]]
215 215  
216 216  
217 217  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -278,7 +278,7 @@
278 278  
279 279  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
280 280  
281 -(% _mstmutation="1" style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
281 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
282 282  
283 283  
284 284  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -287,6 +287,7 @@
287 287  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit
288 288  |=(% 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"]]
289 289  
290 +
290 290  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
291 291  
292 292  
... ... @@ -305,7 +305,7 @@
305 305  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
306 306  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
307 307  
308 -[[image:1665301636888-168.png||_mstalt="298012"]]
309 +[[image:1665301636888-168.png]]
309 309  
310 310  
311 311  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -336,12 +336,12 @@
336 336  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:
337 337  
338 338  
339 -[[image:1664502116362-706.png||_mstalt="293306"]]
340 +[[image:1664502116362-706.png]]
340 340  
341 341  
342 342  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
343 343  
344 -[[image:1664502166010-515.png||_mstalt="291395"]]
345 +[[image:1664502166010-515.png]]
345 345  
346 346  
347 347  
... ... @@ -365,7 +365,6 @@
365 365  * < 3.39v:  0~~20%
366 366  
367 367  
368 -
369 369  ==== (% style="color:blue" %)**MOD:**(%%) ====
370 370  
371 371  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -421,13 +421,13 @@
421 421  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
422 422  
423 423  (% class="wikigeneratedid" %)
424 -[[image:1665301687277-443.png||_mstalt="296140"]]
424 +[[image:1665301687277-443.png]]
425 425  
426 426  
427 427  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
428 428  
429 429  
430 -Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-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.
430 +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.
431 431  
432 432  
433 433  (% style="color:red" %)**Note for this mode:**
... ... @@ -444,7 +444,7 @@
444 444  )))|4|4|2|1|1|1|1|1
445 445  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
446 446  
447 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
447 +[[image:image-20221009160309-2.png]]
448 448  
449 449  
450 450  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
... ... @@ -471,7 +471,7 @@
471 471  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
472 472  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
473 473  
474 -[[image:1664502425687-834.png||_mstalt="296738"]]
474 +[[image:1664502425687-834.png]]
475 475  
476 476  
477 477  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -483,7 +483,6 @@
483 483  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
484 484  
485 485  
486 -
487 487  === 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
488 488  
489 489  
... ... @@ -499,7 +499,7 @@
499 499  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
500 500  
501 501  (% class="wikigeneratedid" %)
502 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
501 +[[image:1667288597595-714.png||height="212" width="1151"]]
503 503  
504 504  
505 505  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -507,7 +507,6 @@
507 507  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
508 508  
509 509  
510 -
511 511  === 2.4.7  Add Payload format in TTN V3 ===
512 512  
513 513  
... ... @@ -516,7 +516,7 @@
516 516  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
517 517  
518 518  
519 -[[image:1664502649601-895.png||_mstalt="296985"]]
517 +[[image:1664502649601-895.png]]
520 520  
521 521  
522 522  
... ... @@ -526,7 +526,7 @@
526 526  
527 527  Save the change the uplink message will be parsed. As below:
528 528  
529 -[[image:1664502676891-606.png||_mstalt="296673"]]
527 +[[image:1664502676891-606.png]]
530 530  
531 531  
532 532  == 2.5 Integrate with Datacake ==
... ... @@ -537,7 +537,7 @@
537 537  Instruction is here:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example~~-~~-AddTrackerDGPSTrackingInDataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example--AddTrackerDGPSTrackingInDataCake]]
538 538  
539 539  
540 -[[image:1664502695771-538.png||_mstalt="297349"]]
538 +[[image:1664502695771-538.png]]
541 541  
542 542  
543 543  == 2.6 Integrate with Tago ==
... ... @@ -548,7 +548,7 @@
548 548  Instruction is here: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget]]
549 549  
550 550  
551 -[[image:1664502715371-321.png||_mstalt="292162"]]
549 +[[image:1664502715371-321.png]]
552 552  
553 553  
554 554  == 2.7  Datalog Feature ==
... ... @@ -556,14 +556,14 @@
556 556  
557 557  total 273 entries,by default,
558 558  
559 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
557 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
560 560  
561 561  Example use case.
562 562  
563 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
561 +[[image:image-20221009234703-2.png||height="328" width="899"]]
564 564  
565 565  
566 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
564 +[[image:image-20221009234629-1.png||height="390" width="577"]]
567 567  
568 568  
569 569  == 2.8 Alarm Mode ==
... ... @@ -596,12 +596,7 @@
596 596  
597 597  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.
598 598  
599 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
600 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
601 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
602 602  
603 -
604 -
605 605  == 2.10 LED Status ==
606 606  
607 607  
... ... @@ -620,13 +620,12 @@
620 620  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
621 621  
622 622  
623 -
624 624  == 2.11 Button Function ==
625 625  
626 626  
627 627  (% style="color:blue" %)**RESET button:**
628 628  
629 -[[image:1664502835802-546.png||_mstalt="295061"]]
621 +[[image:1664502835802-546.png]]
630 630  
631 631  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
632 632  
... ... @@ -633,7 +633,7 @@
633 633  
634 634  (% style="color:red" %)**RED button:**
635 635  
636 -[[image:1664502854406-763.png||_mstalt="295568"]]
628 +[[image:1664502854406-763.png]]
637 637  
638 638  
639 639  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -643,7 +643,6 @@
643 643  |(% 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.
644 644  
645 645  
646 -
647 647  == 2.12 USB Port Function ==
648 648  
649 649  
... ... @@ -655,7 +655,6 @@
655 655  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
656 656  
657 657  
658 -
659 659  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
660 660  
661 661  
... ... @@ -670,21 +670,22 @@
670 670  TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below.
671 671  
672 672  
673 -[[image:1664502999401-486.png||_mstalt="296985"]]
663 +[[image:1664502999401-486.png]]
674 674  
675 675  
676 676  In PC, User needs to set serial tool baud rate to (% style="color:green" %)**115200**(%%) to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands:
677 677  
678 678  
679 -[[image:1664503022490-662.png||_mstalt="293332"]]
669 +[[image:1664503022490-662.png]]
680 680  
681 681  
682 -[[image:1664503035713-500.png||_mstalt="291096"]]
672 +[[image:1664503035713-500.png]]
683 683  
684 684  
685 -[[image:1664503047675-651.png||_mstalt="295386"]]
675 +[[image:1664503047675-651.png]]
686 686  
687 687  
678 +
688 688  == 3.2 Command Set ==
689 689  
690 690  === 3.2.1 Set Transmit Interval ===
... ... @@ -810,9 +810,9 @@
810 810  
811 811  (% style="color:#037691" %)**cc:   **
812 812  
813 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
804 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
814 814  
815 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
806 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
816 816  
817 817  (% style="color:blue" %)**Example:**
818 818  
... ... @@ -875,9 +875,8 @@
875 875  
876 876  
877 877  
878 -=== 3.2.10 Disable/Enable the confirmation mode ===
869 +**Disable/Enable the confirmation mode**
879 879  
880 -
881 881  * (% style="color:blue" %)**AT Command:**
882 882  
883 883  (% style="color:#037691" %)**AT+CFM=xx**
... ... @@ -895,7 +895,7 @@
895 895  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
896 896  
897 897  
898 -=== 3.2.11  Auto Send None-ACK messages ===
888 +=== 3.2.10  Auto Send None-ACK messages ===
899 899  
900 900  
901 901  TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
... ... @@ -913,10 +913,10 @@
913 913  
914 914  * (% style="color:blue" %)**Downlink Command: 0x34**
915 915  
916 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
906 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
917 917  
918 918  
919 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
909 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
920 920  
921 921  
922 922  BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
... ... @@ -925,16 +925,16 @@
925 925  
926 926  (% style="color:blue" %)**AT Command:**
927 927  
928 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
918 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
929 929  
930 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
920 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
931 931  
932 932  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
933 933  
934 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
924 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
935 935  
936 936  
937 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
927 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
938 938  
939 939  
940 940  WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456 as prefix. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
... ... @@ -943,16 +943,16 @@
943 943  
944 944  (% style="color:blue" %)**AT Command:**
945 945  
946 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
936 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
947 947  
948 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
938 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
949 949  
950 950  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
951 951  
952 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
942 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
953 953  
954 954  
955 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
945 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
956 956  
957 957  
958 958  Users can use this feature to enable/disable Information printing.
... ... @@ -959,11 +959,11 @@
959 959  
960 960  (% style="color:blue" %)**AT Command:**
961 961  
962 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
952 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
963 963  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
964 964  
965 965  
966 -=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
956 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
967 967  
968 968  
969 969  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -970,34 +970,14 @@
970 970  
971 971  (% style="color:blue" %)**AT Command:**
972 972  
973 -(% style="color:#037691" %)**AT+CHE=1  **(%%) ~/~/ set one channels mode
963 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
974 974  
975 975  
976 976  (% style="color:blue" %)**Downlink Payload:0X24**
977 977  
978 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
968 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
979 979  
980 980  
981 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
982 -
983 -
984 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
985 -
986 -(% style="color:blue" %)**AT Command:**
987 -
988 -(% style="color:#037691" %)**AT+PT=xx**
989 -
990 - Example:
991 -
992 - AT+PT=14    ~-~->    Set to detect car motion.
993 -
994 - AT+PT=41  ~-~->    set to detect walk motion.
995 -
996 -
997 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
998 -0xB4 14          ~/~/  Same as AT+PT=14
999 -
1000 -
1001 1001  = 4. Setting for Different Scenarios =
1002 1002  
1003 1003  
... ... @@ -1030,10 +1030,10 @@
1030 1030  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1031 1031  
1032 1032  
1033 -[[image:1664503563660-578.png||_mstalt="296777"]]
1003 +[[image:1664503563660-578.png]]
1034 1034  
1035 1035  
1036 -[[image:1664503574618-659.png||_mstalt="297986"]]
1006 +[[image:1664503574618-659.png]]
1037 1037  
1038 1038  
1039 1039  
... ... @@ -1049,13 +1049,13 @@
1049 1049  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1050 1050  
1051 1051  
1052 -[[image:image-20221118105220-2.png||_mstalt="426608"]]
1022 +[[image:image-20221118105220-2.png]]
1053 1053  
1054 1054  
1055 1055  
1056 1056  After upgrade finish, it will show finish as below:
1057 1057  
1058 -[[image:image-20221118105402-4.png||_mstalt="427986"]]
1028 +[[image:image-20221118105402-4.png]]
1059 1059  
1060 1060  
1061 1061  
... ... @@ -1071,23 +1071,23 @@
1071 1071  Install IDE on PC, open and click (% style="color:#037691" %)**File ~-~-> Preference**,(%%) add the following URL:  [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fdl.espressif.com%2Fdl%2Fpackage_esp32_index.json]]
1072 1072  
1073 1073  
1074 -[[image:1664503635019-941.png||_mstalt="294658"]]
1044 +[[image:1664503635019-941.png]]
1075 1075  
1076 1076  
1077 1077  
1078 1078  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1079 1079  
1080 -[[image:1664503715811-892.png||_mstalt="295698"]]
1050 +[[image:1664503715811-892.png]]
1081 1081  
1082 1082  
1083 1083  (% id="cke_bm_4554S" style="display:none" %) (%%)Find the path of SP32 installation, find the file as shown in Figure 1, and change the SPI pin to the shown in Figure 2.
1084 1084  
1085 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1055 +[[image:image-20221024105643-1.png]]
1086 1086  
1087 1087  **~ Figure1**
1088 1088  
1089 1089  
1090 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1060 +[[image:image-20221024105643-2.png]]
1091 1091  
1092 1092   **Figure2**
1093 1093  
... ... @@ -1097,7 +1097,7 @@
1097 1097  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1098 1098  
1099 1099  
1100 -[[image:1664503752288-974.png||_mstalt="298194"]]
1070 +[[image:1664503752288-974.png]]
1101 1101  
1102 1102  
1103 1103  == 6.2 Source Code ==
... ... @@ -1105,19 +1105,19 @@
1105 1105  
1106 1106  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1107 1107  
1108 -[[image:1664503794261-827.png||_mstalt="296387"]]
1078 +[[image:1664503794261-827.png]]
1109 1109  
1110 1110  
1111 1111  
1112 1112  * (% style="color:blue" %)**Click to upload**
1113 1113  
1114 -[[image:1664503808294-336.png||_mstalt="295711"]]
1084 +[[image:1664503808294-336.png]]
1115 1115  
1116 1116  
1117 1117  
1118 1118  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1119 1119  
1120 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1090 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1121 1121  
1122 1122  
1123 1123  = 7.  FAQ =
... ... @@ -1131,7 +1131,7 @@
1131 1131  == 7.2 What is the pin mapping for the USB program cable? ==
1132 1132  
1133 1133  
1134 -[[image:1664499635206-262.png||_mstalt="295360"]]
1104 +[[image:1664499635206-262.png]]
1135 1135  
1136 1136  
1137 1137  
... ... @@ -1147,7 +1147,6 @@
1147 1147  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1148 1148  
1149 1149  
1150 -
1151 1151  == 7.3 Notes on using different serial port tools for TrackerD ==
1152 1152  
1153 1153  === 7.3.1  Serial port utility ===
... ... @@ -1158,13 +1158,13 @@
1158 1158  Need to adjust the data stream to RTS/CTS on physical restart.
1159 1159  
1160 1160  (% class="wikigeneratedid" %)
1161 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1130 +[[image:image-20221102140621-1.png]]
1162 1162  
1163 1163  
1164 1164  
1165 1165  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1166 1166  
1167 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1136 +[[image:image-20221102140638-2.png]]
1168 1168  
1169 1169  
1170 1170  === 7.3.2  SecureCRT ===
... ... @@ -1173,22 +1173,22 @@
1173 1173  The default command window of SecureCRT is not displayed. Entering a command requires a complete input of the entire command. You can open the command window in the view.
1174 1174  
1175 1175  
1176 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1145 +[[image:image-20221102140704-3.png]]
1177 1177  
1178 1178  
1179 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1148 +[[image:image-20221102140712-4.png]]
1180 1180  
1181 1181  
1182 1182  === 7.3.3  PUTTY ===
1183 1183  
1184 1184  
1185 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1154 +[[image:image-20221102140748-5.png]]
1186 1186  
1187 1187  
1188 1188  Since putty does not have a command window, you need to fill in the complete command externally, and then copy it to putty.The information copied outside can be pasted by right-clicking the mouse in putty.
1189 1189  
1190 1190  
1191 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1160 +[[image:image-20221102140801-6.png]]
1192 1192  
1193 1193  
1194 1194  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1203,7 +1203,7 @@
1203 1203  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1204 1204  
1205 1205  
1206 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1175 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1207 1207  
1208 1208  
1209 1209  
... ... @@ -1210,7 +1210,7 @@
1210 1210  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1211 1211  
1212 1212  
1213 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1182 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1214 1214  
1215 1215  
1216 1216  
... ... @@ -1217,7 +1217,7 @@
1217 1217  **3. Compile the AS923_JP band, please refer to the intention shown**
1218 1218  
1219 1219  
1220 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1189 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1221 1221  
1222 1222  
1223 1223  
... ... @@ -1224,10 +1224,10 @@
1224 1224  **4. In other frequency bands in AS923, you need to find Lorabase_as923.H, path arduino-lmic \ src \ lmic, as shown in the figure below.**
1225 1225  
1226 1226  
1227 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1196 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1228 1228  
1229 1229  
1230 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1199 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1231 1231  
1232 1232  
1233 1233  = 8  Trouble Shooting =
... ... @@ -1236,7 +1236,7 @@
1236 1236  
1237 1237  
1238 1238  (((
1239 -Before firmware v1.4.0: When the Transport Mode is enabled ((% style="color:blue" %)**AT+INTWK=1**(%%)), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1208 +Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1240 1240  )))
1241 1241  
1242 1242  
... ... @@ -1250,69 +1250,50 @@
1250 1250  
1251 1251  == 8.3  Problem after Upgrading Firmware ==
1252 1252  
1253 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1222 +=== 8.3.1 Continue Restart after upgrading ===
1254 1254  
1255 1255  
1256 -**Error Output**
1257 -
1258 -
1259 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1260 -
1261 -
1262 1262  (((
1263 -Some partition is missed during upgrade, please upgrade below four files as example:
1264 -
1265 -[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1226 +If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
1266 1266  )))
1267 1267  
1268 1268  
1269 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1230 +[[image:image-20221118105249-3.png]]
1270 1270  
1271 1271  
1272 -It is because the partitions are different when upgrading versions above 1.4.1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1
1233 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1273 1273  
1274 1274  
1275 -=== 8.3.3 "flash read err" after upgrade firmware ===
1236 +It is because the partitions are different when upgrading versions above 1.4.1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1
1276 1276  
1277 1277  
1239 +=== 8.3.3 "flash read err" after upgrade firmware ===
1240 +
1278 1278  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1279 1279  
1243 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1280 1280  
1281 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1282 1282  
1283 -
1284 1284  User need to upgrade again with below four files to solve this issue.
1285 1285  
1286 - [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1248 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1287 1287  
1288 1288   **Figure 2**
1289 1289  
1290 1290  
1291 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1253 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1292 1292  
1293 -
1294 1294  User might erase the entire flash include keys and default settings which cause this issue.
1295 1295  
1296 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1257 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1297 1297  
1259 +[[image:image-20221122100004-3.png]]
1298 1298  
1299 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1261 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1300 1300  
1301 1301  
1302 -Please (% style="color:blue" %)**AT+FDR**(%%) which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1264 +Example:
1303 1303  
1304 -After AT+FDR. please set
1305 -
1306 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1307 -
1308 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1309 -
1310 -**Example:**
1311 -
1312 -AT+PDOP=7.00
1313 -
1314 -AT+FTIME=180
1315 -
1316 1316  AT+DEUI=70B3D57ED0053981  
1317 1317  
1318 1318  AT+APPEUI=D23345667BCBCCAF
... ... @@ -1326,6 +1326,13 @@
1326 1326  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1327 1327  
1328 1328  
1279 +
1280 +==== 8.3.4  If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ====
1281 +
1282 +
1283 +[[image:image-20221122100004-4.png]]
1284 +
1285 +
1329 1329  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1330 1330  
1331 1331  
... ... @@ -1339,53 +1339,15 @@
1339 1339  
1340 1340  2)  Set PDOP to a higher value.
1341 1341  
1342 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1299 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1343 1343  
1344 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1301 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1345 1345  
1346 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1303 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1347 1347  
1348 1348  Please refer to this [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H3.2.9SetPDOPvalueforGPSfixaccuracy]] on how to set up PDOP
1349 1349  
1350 1350  
1351 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1352 -
1353 -
1354 -When upgrading, use the erase button to upgrade
1355 -
1356 -[[image:image-20221128102938-1.png||height="537" width="335"]]
1357 -
1358 -
1359 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1360 -
1361 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1362 -
1363 -
1364 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1365 -
1366 -[[image:image-20221128110503-3.png||height="647" width="410"]]
1367 -
1368 -
1369 -Reboot information after upgrade
1370 -
1371 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1372 -
1373 -
1374 -Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal
1375 -
1376 -[[image:image-20221128111850-5.png]]
1377 -
1378 -
1379 -After the parameters return to normal, upgrade to the version you need again
1380 -
1381 -[[image:image-20221128111951-6.png||height="620" width="389"]]
1382 -
1383 -
1384 -At this point, the parameters return to normal after running AT+FDR again
1385 -
1386 -[[image:image-20221128112035-7.png]]
1387 -
1388 -
1389 1389  = 9.  Order Info =
1390 1390  
1391 1391  
... ... @@ -1408,7 +1408,6 @@
1408 1408  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1409 1409  
1410 1410  
1411 -
1412 1412  = 10.  Packing Info =
1413 1413  
1414 1414  
... ... @@ -1425,7 +1425,6 @@
1425 1425  * Weight: 50g
1426 1426  
1427 1427  
1428 -
1429 1429  = 11. Support =
1430 1430  
1431 1431  
... ... @@ -1434,7 +1434,6 @@
1434 1434  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].
1435 1435  
1436 1436  
1437 -
1438 1438  = 12.  Reference =
1439 1439  
1440 1440  
... ... @@ -1443,4 +1443,3 @@
1443 1443  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1444 1444  
1445 1445  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1446 -)))
image-20221128102938-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -41.3 KB
Content
image-20221128103040-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -19.2 KB
Content
image-20221128110503-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.6 KB
Content
image-20221128111443-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -15.6 KB
Content
image-20221128111850-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.5 KB
Content
image-20221128111951-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.4 KB
Content
image-20221128112035-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.7 KB
Content
image-20221207120501-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120524-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content