Skip to Content
Last modified by Xiaoling on 2025/04/27 16:48
From version 164.1
edited by Bei Jinggeng
on 2022/11/28 14:10
Change comment: There is no comment for this version
To version 145.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.**
... ... @@ -130,7 +130,7 @@
130 130  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. 
131 131  
132 132  
133 -[[image:1664501652064-326.png||_mstalt="293306"]]
136 +[[image:1664501652064-326.png]]
134 134  
135 135  
136 136  
... ... @@ -142,7 +142,7 @@
142 142  Each TrackerD is shipped with a sticker with the default device EUI as below:
143 143  
144 144  
145 -[[image:1664501677253-891.png||_mstalt="296569"]]
148 +[[image:1664501677253-891.png]]
146 146  
147 147  
148 148  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -151,14 +151,14 @@
151 151  **__Add APP EUI in the application:__**
152 152  
153 153  
154 -[[image:1664501711466-918.png||_mstalt="295828"]]
157 +[[image:1664501711466-918.png]]
155 155  
156 156  
157 157  
158 -[[image:1664501721248-725.png||_mstalt="294450"]]
161 +[[image:1664501721248-725.png]]
159 159  
160 160  
161 -[[image:1664501734705-405.png||_mstalt="293306"]]
164 +[[image:1664501734705-405.png]]
162 162  
163 163  
164 164  
... ... @@ -165,15 +165,15 @@
165 165  **__Add APP KEY and DEV EUI:__**
166 166  
167 167  
168 -[[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"]]
171 +[[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"]]
169 169  
170 170  
171 171  
172 172  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
173 173  
174 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
177 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
175 175  
176 -[[image:1664502835802-546.png||_mstalt="295061"]]
179 +[[image:1664502835802-546.png]]
177 177  
178 178  
179 179  (% 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.
... ... @@ -205,7 +205,7 @@
205 205  |=(% 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
206 206  |=(% 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
207 207  
208 -[[image:1665301570342-765.png||_mstalt="294580"]]
211 +[[image:1665301570342-765.png]]
209 209  
210 210  
211 211  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -272,7 +272,7 @@
272 272  
273 273  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
274 274  
275 -(% _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)(%%)  
278 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
276 276  
277 277  
278 278  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -299,7 +299,7 @@
299 299  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
300 300  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
301 301  
302 -[[image:1665301636888-168.png||_mstalt="298012"]]
305 +[[image:1665301636888-168.png]]
303 303  
304 304  
305 305  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -329,12 +329,12 @@
329 329  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:
330 330  
331 331  
332 -[[image:1664502116362-706.png||_mstalt="293306"]]
335 +[[image:1664502116362-706.png]]
333 333  
334 334  
335 335  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
336 336  
337 -[[image:1664502166010-515.png||_mstalt="291395"]]
340 +[[image:1664502166010-515.png]]
338 338  
339 339  
340 340  
... ... @@ -412,13 +412,13 @@
412 412  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
413 413  
414 414  (% class="wikigeneratedid" %)
415 -[[image:1665301687277-443.png||_mstalt="296140"]]
418 +[[image:1665301687277-443.png]]
416 416  
417 417  
418 418  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
419 419  
420 420  
421 -Set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-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.
424 +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.
422 422  
423 423  
424 424  (% style="color:red" %)**Note for this mode:**
... ... @@ -435,7 +435,7 @@
435 435  )))|4|4|2|1|1|1|1|1
436 436  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
437 437  
438 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
441 +[[image:image-20221009160309-2.png]]
439 439  
440 440  
441 441  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
... ... @@ -462,7 +462,7 @@
462 462  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
463 463  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
464 464  
465 -[[image:1664502425687-834.png||_mstalt="296738"]]
468 +[[image:1664502425687-834.png]]
466 466  
467 467  
468 468  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -488,7 +488,7 @@
488 488  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
489 489  
490 490  (% class="wikigeneratedid" %)
491 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
494 +[[image:1667288597595-714.png||height="212" width="1151"]]
492 492  
493 493  
494 494  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -503,7 +503,7 @@
503 503  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
504 504  
505 505  
506 -[[image:1664502649601-895.png||_mstalt="296985"]]
509 +[[image:1664502649601-895.png]]
507 507  
508 508  
509 509  
... ... @@ -513,7 +513,7 @@
513 513  
514 514  Save the change the uplink message will be parsed. As below:
515 515  
516 -[[image:1664502676891-606.png||_mstalt="296673"]]
519 +[[image:1664502676891-606.png]]
517 517  
518 518  
519 519  == 2.5 Integrate with Datacake ==
... ... @@ -524,7 +524,7 @@
524 524  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]]
525 525  
526 526  
527 -[[image:1664502695771-538.png||_mstalt="297349"]]
530 +[[image:1664502695771-538.png]]
528 528  
529 529  
530 530  == 2.6 Integrate with Tago ==
... ... @@ -535,7 +535,7 @@
535 535  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]]
536 536  
537 537  
538 -[[image:1664502715371-321.png||_mstalt="292162"]]
541 +[[image:1664502715371-321.png]]
539 539  
540 540  
541 541  == 2.7  Datalog Feature ==
... ... @@ -543,14 +543,14 @@
543 543  
544 544  total 273 entries,by default,
545 545  
546 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
549 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
547 547  
548 548  Example use case.
549 549  
550 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
553 +[[image:image-20221009234703-2.png||height="328" width="899"]]
551 551  
552 552  
553 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
556 +[[image:image-20221009234629-1.png||height="390" width="577"]]
554 554  
555 555  
556 556  == 2.8 Alarm Mode ==
... ... @@ -583,9 +583,6 @@
583 583  
584 584  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.
585 585  
586 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
587 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
588 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
589 589  
590 590  == 2.10 LED Status ==
591 591  
... ... @@ -609,7 +609,7 @@
609 609  
610 610  (% style="color:blue" %)**RESET button:**
611 611  
612 -[[image:1664502835802-546.png||_mstalt="295061"]]
612 +[[image:1664502835802-546.png]]
613 613  
614 614  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
615 615  
... ... @@ -616,7 +616,7 @@
616 616  
617 617  (% style="color:red" %)**RED button:**
618 618  
619 -[[image:1664502854406-763.png||_mstalt="295568"]]
619 +[[image:1664502854406-763.png]]
620 620  
621 621  
622 622  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -649,21 +649,22 @@
649 649  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.
650 650  
651 651  
652 -[[image:1664502999401-486.png||_mstalt="296985"]]
652 +[[image:1664502999401-486.png]]
653 653  
654 654  
655 655  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:
656 656  
657 657  
658 -[[image:1664503022490-662.png||_mstalt="293332"]]
658 +[[image:1664503022490-662.png]]
659 659  
660 660  
661 -[[image:1664503035713-500.png||_mstalt="291096"]]
661 +[[image:1664503035713-500.png]]
662 662  
663 663  
664 -[[image:1664503047675-651.png||_mstalt="295386"]]
664 +[[image:1664503047675-651.png]]
665 665  
666 666  
667 +
667 667  == 3.2 Command Set ==
668 668  
669 669  === 3.2.1 Set Transmit Interval ===
... ... @@ -789,9 +789,9 @@
789 789  
790 790  (% style="color:#037691" %)**cc:   **
791 791  
792 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
793 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
793 793  
794 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
795 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
795 795  
796 796  (% style="color:blue" %)**Example:**
797 797  
... ... @@ -854,9 +854,8 @@
854 854  
855 855  
856 856  
857 -=== 3.2.10 Disable/Enable the confirmation mode ===
858 +**Disable/Enable the confirmation mode**
858 858  
859 -
860 860  * (% style="color:blue" %)**AT Command:**
861 861  
862 862  (% style="color:#037691" %)**AT+CFM=xx**
... ... @@ -874,7 +874,7 @@
874 874  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
875 875  
876 876  
877 -=== 3.2.11  Auto Send None-ACK messages ===
877 +=== 3.2.10  Auto Send None-ACK messages ===
878 878  
879 879  
880 880  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.
... ... @@ -892,10 +892,10 @@
892 892  
893 893  * (% style="color:blue" %)**Downlink Command: 0x34**
894 894  
895 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
895 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
896 896  
897 897  
898 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
898 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
899 899  
900 900  
901 901  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.
... ... @@ -904,16 +904,16 @@
904 904  
905 905  (% style="color:blue" %)**AT Command:**
906 906  
907 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
907 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
908 908  
909 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
909 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
910 910  
911 911  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
912 912  
913 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
913 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
914 914  
915 915  
916 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
916 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
917 917  
918 918  
919 919  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.
... ... @@ -922,16 +922,16 @@
922 922  
923 923  (% style="color:blue" %)**AT Command:**
924 924  
925 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
925 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
926 926  
927 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
927 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
928 928  
929 929  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
930 930  
931 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
931 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
932 932  
933 933  
934 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
934 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
935 935  
936 936  
937 937  Users can use this feature to enable/disable Information printing.
... ... @@ -942,7 +942,7 @@
942 942  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
943 943  
944 944  
945 -=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
945 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
946 946  
947 947  
948 948  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -957,26 +957,6 @@
957 957  Example: 0x24 01 ~/~/ Same as AT+CHE=1
958 958  
959 959  
960 -=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
961 -
962 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
963 -
964 -(% style="color:blue" %)**AT Command:**
965 -
966 -(% style="color:#037691" %)**AT+PT=xx**
967 -
968 - Example:
969 -
970 - AT+PT=14    ~-~->    Set to detect car motion.
971 -
972 - AT+PT=41   ~-~->    set to detect walk motion.
973 -
974 -
975 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
976 -0xB4 14          ~/~/  Same as AT+PT=14
977 -
978 -
979 -
980 980  = 4. Setting for Different Scenarios =
981 981  
982 982  
... ... @@ -1009,10 +1009,10 @@
1009 1009  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1010 1010  
1011 1011  
1012 -[[image:1664503563660-578.png||_mstalt="296777"]]
992 +[[image:1664503563660-578.png]]
1013 1013  
1014 1014  
1015 -[[image:1664503574618-659.png||_mstalt="297986"]]
995 +[[image:1664503574618-659.png]]
1016 1016  
1017 1017  
1018 1018  
... ... @@ -1028,13 +1028,13 @@
1028 1028  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1029 1029  
1030 1030  
1031 -[[image:image-20221118105220-2.png||_mstalt="426608"]]
1011 +[[image:image-20221118105220-2.png]]
1032 1032  
1033 1033  
1034 1034  
1035 1035  After upgrade finish, it will show finish as below:
1036 1036  
1037 -[[image:image-20221118105402-4.png||_mstalt="427986"]]
1017 +[[image:image-20221118105402-4.png]]
1038 1038  
1039 1039  
1040 1040  
... ... @@ -1050,23 +1050,23 @@
1050 1050  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]]
1051 1051  
1052 1052  
1053 -[[image:1664503635019-941.png||_mstalt="294658"]]
1033 +[[image:1664503635019-941.png]]
1054 1054  
1055 1055  
1056 1056  
1057 1057  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1058 1058  
1059 -[[image:1664503715811-892.png||_mstalt="295698"]]
1039 +[[image:1664503715811-892.png]]
1060 1060  
1061 1061  
1062 1062  (% 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.
1063 1063  
1064 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1044 +[[image:image-20221024105643-1.png]]
1065 1065  
1066 1066  **~ Figure1**
1067 1067  
1068 1068  
1069 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1049 +[[image:image-20221024105643-2.png]]
1070 1070  
1071 1071   **Figure2**
1072 1072  
... ... @@ -1076,7 +1076,7 @@
1076 1076  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1077 1077  
1078 1078  
1079 -[[image:1664503752288-974.png||_mstalt="298194"]]
1059 +[[image:1664503752288-974.png]]
1080 1080  
1081 1081  
1082 1082  == 6.2 Source Code ==
... ... @@ -1084,19 +1084,19 @@
1084 1084  
1085 1085  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1086 1086  
1087 -[[image:1664503794261-827.png||_mstalt="296387"]]
1067 +[[image:1664503794261-827.png]]
1088 1088  
1089 1089  
1090 1090  
1091 1091  * (% style="color:blue" %)**Click to upload**
1092 1092  
1093 -[[image:1664503808294-336.png||_mstalt="295711"]]
1073 +[[image:1664503808294-336.png]]
1094 1094  
1095 1095  
1096 1096  
1097 1097  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1098 1098  
1099 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1079 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1100 1100  
1101 1101  
1102 1102  = 7.  FAQ =
... ... @@ -1110,7 +1110,7 @@
1110 1110  == 7.2 What is the pin mapping for the USB program cable? ==
1111 1111  
1112 1112  
1113 -[[image:1664499635206-262.png||_mstalt="295360"]]
1093 +[[image:1664499635206-262.png]]
1114 1114  
1115 1115  
1116 1116  
... ... @@ -1135,13 +1135,13 @@
1135 1135  Need to adjust the data stream to RTS/CTS on physical restart.
1136 1136  
1137 1137  (% class="wikigeneratedid" %)
1138 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1118 +[[image:image-20221102140621-1.png]]
1139 1139  
1140 1140  
1141 1141  
1142 1142  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1143 1143  
1144 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1124 +[[image:image-20221102140638-2.png]]
1145 1145  
1146 1146  
1147 1147  === 7.3.2  SecureCRT ===
... ... @@ -1150,22 +1150,22 @@
1150 1150  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.
1151 1151  
1152 1152  
1153 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1133 +[[image:image-20221102140704-3.png]]
1154 1154  
1155 1155  
1156 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1136 +[[image:image-20221102140712-4.png]]
1157 1157  
1158 1158  
1159 1159  === 7.3.3  PUTTY ===
1160 1160  
1161 1161  
1162 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1142 +[[image:image-20221102140748-5.png]]
1163 1163  
1164 1164  
1165 1165  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.
1166 1166  
1167 1167  
1168 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1148 +[[image:image-20221102140801-6.png]]
1169 1169  
1170 1170  
1171 1171  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1180,7 +1180,7 @@
1180 1180  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1181 1181  
1182 1182  
1183 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1163 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1184 1184  
1185 1185  
1186 1186  
... ... @@ -1187,7 +1187,7 @@
1187 1187  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1188 1188  
1189 1189  
1190 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1170 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1191 1191  
1192 1192  
1193 1193  
... ... @@ -1194,7 +1194,7 @@
1194 1194  **3. Compile the AS923_JP band, please refer to the intention shown**
1195 1195  
1196 1196  
1197 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1177 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1198 1198  
1199 1199  
1200 1200  
... ... @@ -1201,10 +1201,10 @@
1201 1201  **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.**
1202 1202  
1203 1203  
1204 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1184 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1205 1205  
1206 1206  
1207 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1187 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1208 1208  
1209 1209  
1210 1210  = 8  Trouble Shooting =
... ... @@ -1213,7 +1213,7 @@
1213 1213  
1214 1214  
1215 1215  (((
1216 -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
1196 +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
1217 1217  )))
1218 1218  
1219 1219  
... ... @@ -1227,69 +1227,50 @@
1227 1227  
1228 1228  == 8.3  Problem after Upgrading Firmware ==
1229 1229  
1230 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1210 +=== 8.3.1 Continue Restart after upgrading ===
1231 1231  
1232 1232  
1233 -**Error Output**
1234 -
1235 -
1236 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1237 -
1238 -
1239 1239  (((
1240 -Some partition is missed during upgrade, please upgrade below four files as example:
1241 -
1242 -[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1214 +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
1243 1243  )))
1244 1244  
1245 1245  
1246 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1218 +[[image:image-20221118105249-3.png]]
1247 1247  
1248 1248  
1249 -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
1221 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1250 1250  
1251 1251  
1252 -=== 8.3.3 "flash read err" after upgrade firmware ===
1224 +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
1253 1253  
1254 1254  
1227 +=== 8.3.3 "flash read err" after upgrade firmware ===
1228 +
1255 1255  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1256 1256  
1231 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1257 1257  
1258 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1259 1259  
1260 -
1261 1261  User need to upgrade again with below four files to solve this issue.
1262 1262  
1263 - [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1236 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1264 1264  
1265 1265   **Figure 2**
1266 1266  
1267 1267  
1268 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1241 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1269 1269  
1270 -
1271 1271  User might erase the entire flash include keys and default settings which cause this issue.
1272 1272  
1273 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1245 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1274 1274  
1247 +[[image:image-20221122100004-3.png]]
1275 1275  
1276 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1249 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1277 1277  
1278 1278  
1279 -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.
1252 +Example:
1280 1280  
1281 -After AT+FDR. please set
1282 -
1283 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1284 -
1285 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1286 -
1287 -**Example:**
1288 -
1289 -AT+PDOP=7.00
1290 -
1291 -AT+FTIME=180
1292 -
1293 1293  AT+DEUI=70B3D57ED0053981  
1294 1294  
1295 1295  AT+APPEUI=D23345667BCBCCAF
... ... @@ -1303,6 +1303,13 @@
1303 1303  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1304 1304  
1305 1305  
1267 +
1268 +=== 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 ===
1269 +
1270 +
1271 +[[image:image-20221122100004-4.png]]
1272 +
1273 +
1306 1306  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1307 1307  
1308 1308  
... ... @@ -1316,47 +1316,15 @@
1316 1316  
1317 1317  2)  Set PDOP to a higher value.
1318 1318  
1319 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1287 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1320 1320  
1321 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1289 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1322 1322  
1323 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1291 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1324 1324  
1325 1325  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
1326 1326  
1327 1327  
1328 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1329 -
1330 -When upgrading, use the erase button to upgrade
1331 -
1332 -[[image:image-20221128102938-1.png||height="537" width="335"]]
1333 -
1334 -
1335 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1336 -
1337 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1338 -
1339 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1340 -
1341 -[[image:image-20221128110503-3.png||height="647" width="410"]]
1342 -
1343 -Reboot information after upgrade
1344 -
1345 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1346 -
1347 -Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal
1348 -
1349 -[[image:image-20221128111850-5.png]]
1350 -
1351 -After the parameters return to normal, upgrade to the version you need again
1352 -
1353 -[[image:image-20221128111951-6.png||height="620" width="389"]]
1354 -
1355 -At this point, the parameters return to normal after running AT+FDR again
1356 -
1357 -[[image:image-20221128112035-7.png]]
1358 -
1359 -
1360 1360  = 9.  Order Info =
1361 1361  
1362 1362  
... ... @@ -1408,4 +1408,3 @@
1408 1408  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1409 1409  
1410 1410  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1411 -)))
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