Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)
Last modified by Xiaoling on 2023/12/27 09:15
From version 152.1
edited by Edwin Chen
on 2022/11/24 09:15
on 2022/11/24 09:15
Change comment:
There is no comment for this version
To version 145.1
edited by Edwin Chen
on 2022/11/22 12:21
on 2022/11/22 12:21
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- 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 ... ... @@ -39,7 +39,7 @@ 39 39 40 40 ))) 41 41 42 -[[image:1664499921684-770.png ||_mstalt="298194"]]42 +[[image:1664499921684-770.png]] 43 43 44 44 45 45 (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.** ... ... @@ -133,7 +133,7 @@ 133 133 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. 134 134 135 135 136 -[[image:1664501652064-326.png ||_mstalt="293306"]]136 +[[image:1664501652064-326.png]] 137 137 138 138 139 139 ... ... @@ -145,7 +145,7 @@ 145 145 Each TrackerD is shipped with a sticker with the default device EUI as below: 146 146 147 147 148 -[[image:1664501677253-891.png ||_mstalt="296569"]]148 +[[image:1664501677253-891.png]] 149 149 150 150 151 151 Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot: ... ... @@ -154,14 +154,14 @@ 154 154 **__Add APP EUI in the application:__** 155 155 156 156 157 -[[image:1664501711466-918.png ||_mstalt="295828"]]157 +[[image:1664501711466-918.png]] 158 158 159 159 160 160 161 -[[image:1664501721248-725.png ||_mstalt="294450"]]161 +[[image:1664501721248-725.png]] 162 162 163 163 164 -[[image:1664501734705-405.png ||_mstalt="293306"]]164 +[[image:1664501734705-405.png]] 165 165 166 166 167 167 ... ... @@ -168,15 +168,15 @@ 168 168 **__Add APP KEY and DEV EUI:__** 169 169 170 170 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|| _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"]] 172 172 173 173 174 174 175 175 (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device. 176 176 177 -(% 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]] 178 178 179 -[[image:1664502835802-546.png ||_mstalt="295061"]]179 +[[image:1664502835802-546.png]] 180 180 181 181 182 182 (% 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. ... ... @@ -208,7 +208,7 @@ 208 208 |=(% 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 209 209 |=(% 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 210 210 211 -[[image:1665301570342-765.png ||_mstalt="294580"]]211 +[[image:1665301570342-765.png]] 212 212 213 213 214 214 (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002 ... ... @@ -275,7 +275,7 @@ 275 275 276 276 (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 277 277 278 -(% _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)(%%) 279 279 280 280 281 281 (% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 ... ... @@ -302,7 +302,7 @@ 302 302 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 303 303 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 304 304 305 -[[image:1665301636888-168.png ||_mstalt="298012"]]305 +[[image:1665301636888-168.png]] 306 306 307 307 308 308 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== ... ... @@ -332,12 +332,12 @@ 332 332 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: 333 333 334 334 335 -[[image:1664502116362-706.png ||_mstalt="293306"]]335 +[[image:1664502116362-706.png]] 336 336 337 337 338 338 3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 339 339 340 -[[image:1664502166010-515.png ||_mstalt="291395"]]340 +[[image:1664502166010-515.png]] 341 341 342 342 343 343 ... ... @@ -415,7 +415,7 @@ 415 415 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 416 416 417 417 (% class="wikigeneratedid" %) 418 -[[image:1665301687277-443.png ||_mstalt="296140"]]418 +[[image:1665301687277-443.png]] 419 419 420 420 421 421 === 2.4.4 Uplink FPORT~=4, History GNSS Positioning === ... ... @@ -438,7 +438,7 @@ 438 438 )))|4|4|2|1|1|1|1|1 439 439 |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 440 440 441 -[[image:image-20221009160309-2.png ||_mstalt="429312"]]441 +[[image:image-20221009160309-2.png]] 442 442 443 443 444 444 === 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === ... ... @@ -465,7 +465,7 @@ 465 465 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 466 466 )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 467 467 468 -[[image:1664502425687-834.png ||_mstalt="296738"]]468 +[[image:1664502425687-834.png]] 469 469 470 470 471 471 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). ... ... @@ -491,7 +491,7 @@ 491 491 )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 492 492 493 493 (% class="wikigeneratedid" %) 494 -[[image:1667288597595-714.png|| _mstalt="299598"height="212" width="1151"]]494 +[[image:1667288597595-714.png||height="212" width="1151"]] 495 495 496 496 497 497 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). ... ... @@ -506,7 +506,7 @@ 506 506 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 507 507 508 508 509 -[[image:1664502649601-895.png ||_mstalt="296985"]]509 +[[image:1664502649601-895.png]] 510 510 511 511 512 512 ... ... @@ -516,7 +516,7 @@ 516 516 517 517 Save the change the uplink message will be parsed. As below: 518 518 519 -[[image:1664502676891-606.png ||_mstalt="296673"]]519 +[[image:1664502676891-606.png]] 520 520 521 521 522 522 == 2.5 Integrate with Datacake == ... ... @@ -527,7 +527,7 @@ 527 527 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]] 528 528 529 529 530 -[[image:1664502695771-538.png ||_mstalt="297349"]]530 +[[image:1664502695771-538.png]] 531 531 532 532 533 533 == 2.6 Integrate with Tago == ... ... @@ -538,7 +538,7 @@ 538 538 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]] 539 539 540 540 541 -[[image:1664502715371-321.png ||_mstalt="292162"]]541 +[[image:1664502715371-321.png]] 542 542 543 543 544 544 == 2.7 Datalog Feature == ... ... @@ -550,10 +550,10 @@ 550 550 551 551 Example use case. 552 552 553 -[[image:image-20221009234703-2.png|| _mstalt="429143"height="328" width="899"]]553 +[[image:image-20221009234703-2.png||height="328" width="899"]] 554 554 555 555 556 -[[image:image-20221009234629-1.png|| _mstalt="431145"height="390" width="577"]]556 +[[image:image-20221009234629-1.png||height="390" width="577"]] 557 557 558 558 559 559 == 2.8 Alarm Mode == ... ... @@ -586,9 +586,6 @@ 586 586 587 587 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. 588 588 589 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation. 590 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic. 591 -* **[[PT>>||anchor="H3.2.1SetTransmitInterval"]]** defines the threldhold to detect a motion. 592 592 593 593 == 2.10 LED Status == 594 594 ... ... @@ -612,7 +612,7 @@ 612 612 613 613 (% style="color:blue" %)**RESET button:** 614 614 615 -[[image:1664502835802-546.png ||_mstalt="295061"]]612 +[[image:1664502835802-546.png]] 616 616 617 617 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server. 618 618 ... ... @@ -619,7 +619,7 @@ 619 619 620 620 (% style="color:red" %)**RED button:** 621 621 622 -[[image:1664502854406-763.png ||_mstalt="295568"]]619 +[[image:1664502854406-763.png]] 623 623 624 624 625 625 (% border="1" style="background-color:#ffffcc; width:510px" %) ... ... @@ -652,19 +652,19 @@ 652 652 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. 653 653 654 654 655 -[[image:1664502999401-486.png ||_mstalt="296985"]]652 +[[image:1664502999401-486.png]] 656 656 657 657 658 658 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: 659 659 660 660 661 -[[image:1664503022490-662.png ||_mstalt="293332"]]658 +[[image:1664503022490-662.png]] 662 662 663 663 664 -[[image:1664503035713-500.png ||_mstalt="291096"]]661 +[[image:1664503035713-500.png]] 665 665 666 666 667 -[[image:1664503047675-651.png ||_mstalt="295386"]]664 +[[image:1664503047675-651.png]] 668 668 669 669 670 670 ... ... @@ -793,9 +793,9 @@ 793 793 794 794 (% style="color:#037691" %)**cc: ** 795 795 796 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State793 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 797 797 798 -* (% _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(%%)) 799 799 800 800 (% style="color:blue" %)**Example:** 801 801 ... ... @@ -858,7 +858,7 @@ 858 858 859 859 860 860 861 - === 3.2.10Disable/Enable the confirmation mode===858 +**Disable/Enable the confirmation mode** 862 862 863 863 * (% style="color:blue" %)**AT Command:** 864 864 ... ... @@ -877,7 +877,7 @@ 877 877 (% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1 878 878 879 879 880 -=== 3.2.1 1877 +=== 3.2.10 Auto Send None-ACK messages === 881 881 882 882 883 883 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. ... ... @@ -895,10 +895,10 @@ 895 895 896 896 * (% style="color:blue" %)**Downlink Command: 0x34** 897 897 898 -Example: 0x34 895 +Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 899 899 900 900 901 -=== 3.2.1 2Set BLEMASK to filter BLE iBeacon ===898 +=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 902 902 903 903 904 904 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. ... ... @@ -907,16 +907,16 @@ 907 907 908 908 (% style="color:blue" %)**AT Command:** 909 909 910 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456907 + (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 911 911 912 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK909 + (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 913 913 914 914 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 915 915 916 -Example: 0xB2 913 +Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 917 917 918 918 919 -=== 3.2.1 3Set 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) === 920 920 921 921 922 922 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. ... ... @@ -925,16 +925,16 @@ 925 925 926 926 (% style="color:blue" %)**AT Command:** 927 927 928 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456925 + (% style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456 929 929 930 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK927 + (% style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK 931 931 932 932 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)** 933 933 934 -Example: 0xB3 931 +Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 935 935 936 936 937 -=== 3.2.1 4Disable/Enable Information printing(Since firmware 1.4.1) ===934 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 938 938 939 939 940 940 Users can use this feature to enable/disable Information printing. ... ... @@ -945,7 +945,7 @@ 945 945 \\Example: AT+SHOWID=1 ~-~-> Enable Information printing. 946 946 947 947 948 -=== 3.2.1 5Get 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) === 949 949 950 950 951 951 The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. ... ... @@ -960,26 +960,6 @@ 960 960 Example: 0x24 01 ~/~/ Same as AT+CHE=1 961 961 962 962 963 -=== 3.2.16 Get or Set Threshold for motion detect(Since firmware 1.4.3) === 964 - 965 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event. 966 - 967 -(% style="color:blue" %)**AT Command:** 968 - 969 -(% style="color:#037691" %)**AT+PT=xx** 970 - 971 - Example: 972 - 973 - AT+PT=14 ~-~-> Set to detect car motion. 974 - 975 - AT+PT=41 ~-~-> set to detect walk motion. 976 - 977 - 978 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%) 979 -0xB4 14 ~/~/ Same as AT+PT=14 980 - 981 - 982 - 983 983 = 4. Setting for Different Scenarios = 984 984 985 985 ... ... @@ -1012,10 +1012,10 @@ 1012 1012 (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32 1013 1013 1014 1014 1015 -[[image:1664503563660-578.png ||_mstalt="296777"]]992 +[[image:1664503563660-578.png]] 1016 1016 1017 1017 1018 -[[image:1664503574618-659.png ||_mstalt="297986"]]995 +[[image:1664503574618-659.png]] 1019 1019 1020 1020 1021 1021 ... ... @@ -1031,13 +1031,13 @@ 1031 1031 US915.bin @ 0x10000(Select the bin file of the frequency band you need) 1032 1032 1033 1033 1034 -[[image:image-20221118105220-2.png ||_mstalt="426608"]]1011 +[[image:image-20221118105220-2.png]] 1035 1035 1036 1036 1037 1037 1038 1038 After upgrade finish, it will show finish as below: 1039 1039 1040 -[[image:image-20221118105402-4.png ||_mstalt="427986"]]1017 +[[image:image-20221118105402-4.png]] 1041 1041 1042 1042 1043 1043 ... ... @@ -1053,23 +1053,23 @@ 1053 1053 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]] 1054 1054 1055 1055 1056 -[[image:1664503635019-941.png ||_mstalt="294658"]]1033 +[[image:1664503635019-941.png]] 1057 1057 1058 1058 1059 1059 1060 1060 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 1061 1061 1062 -[[image:1664503715811-892.png ||_mstalt="295698"]]1039 +[[image:1664503715811-892.png]] 1063 1063 1064 1064 1065 1065 (% 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. 1066 1066 1067 -[[image:image-20221024105643-1.png ||_mstalt="428129"]]1044 +[[image:image-20221024105643-1.png]] 1068 1068 1069 1069 **~ Figure1** 1070 1070 1071 1071 1072 -[[image:image-20221024105643-2.png ||_mstalt="428493"]]1049 +[[image:image-20221024105643-2.png]] 1073 1073 1074 1074 **Figure2** 1075 1075 ... ... @@ -1079,7 +1079,7 @@ 1079 1079 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: 1080 1080 1081 1081 1082 -[[image:1664503752288-974.png ||_mstalt="298194"]]1059 +[[image:1664503752288-974.png]] 1083 1083 1084 1084 1085 1085 == 6.2 Source Code == ... ... @@ -1087,19 +1087,19 @@ 1087 1087 1088 1088 * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:** 1089 1089 1090 -[[image:1664503794261-827.png ||_mstalt="296387"]]1067 +[[image:1664503794261-827.png]] 1091 1091 1092 1092 1093 1093 1094 1094 * (% style="color:blue" %)**Click to upload** 1095 1095 1096 -[[image:1664503808294-336.png ||_mstalt="295711"]]1073 +[[image:1664503808294-336.png]] 1097 1097 1098 1098 1099 1099 1100 1100 * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 1101 1101 1102 -[[image:1664503824081-592.png ||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]1079 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 1103 1103 1104 1104 1105 1105 = 7. FAQ = ... ... @@ -1113,7 +1113,7 @@ 1113 1113 == 7.2 What is the pin mapping for the USB program cable? == 1114 1114 1115 1115 1116 -[[image:1664499635206-262.png ||_mstalt="295360"]]1093 +[[image:1664499635206-262.png]] 1117 1117 1118 1118 1119 1119 ... ... @@ -1138,13 +1138,13 @@ 1138 1138 Need to adjust the data stream to RTS/CTS on physical restart. 1139 1139 1140 1140 (% class="wikigeneratedid" %) 1141 -[[image:image-20221102140621-1.png ||_mstalt="425672"]]1118 +[[image:image-20221102140621-1.png]] 1142 1142 1143 1143 1144 1144 1145 1145 When using AT commands, the data flow needs to be adjusted to XON/XOFF 1146 1146 1147 -[[image:image-20221102140638-2.png ||_mstalt="428727"]]1124 +[[image:image-20221102140638-2.png]] 1148 1148 1149 1149 1150 1150 === 7.3.2 SecureCRT === ... ... @@ -1153,22 +1153,22 @@ 1153 1153 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. 1154 1154 1155 1155 1156 -[[image:image-20221102140704-3.png ||_mstalt="427076"]]1133 +[[image:image-20221102140704-3.png]] 1157 1157 1158 1158 1159 -[[image:image-20221102140712-4.png ||_mstalt="427089"]]1136 +[[image:image-20221102140712-4.png]] 1160 1160 1161 1161 1162 1162 === 7.3.3 PUTTY === 1163 1163 1164 1164 1165 -[[image:image-20221102140748-5.png ||_mstalt="430456"]]1142 +[[image:image-20221102140748-5.png]] 1166 1166 1167 1167 1168 1168 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. 1169 1169 1170 1170 1171 -[[image:image-20221102140801-6.png ||_mstalt="427466"]]1148 +[[image:image-20221102140801-6.png]] 1172 1172 1173 1173 1174 1174 == 7.4 How to modify source code to compile different frequency band bin file? == ... ... @@ -1183,7 +1183,7 @@ 1183 1183 **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.** 1184 1184 1185 1185 1186 -[[image:image-20221116111844-1.png|| _mstalt="428688"height="227" width="782"]]1163 +[[image:image-20221116111844-1.png||height="227" width="782"]] 1187 1187 1188 1188 1189 1189 ... ... @@ -1190,7 +1190,7 @@ 1190 1190 **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).** 1191 1191 1192 1192 1193 -[[image:image-20221116111844-2.png|| _mstalt="429052"height="262" width="781"]]1170 +[[image:image-20221116111844-2.png||height="262" width="781"]] 1194 1194 1195 1195 1196 1196 ... ... @@ -1197,7 +1197,7 @@ 1197 1197 **3. Compile the AS923_JP band, please refer to the intention shown** 1198 1198 1199 1199 1200 -[[image:image-20221116111844-3.png|| _mstalt="429416"height="338" width="746"]]1177 +[[image:image-20221116111844-3.png||height="338" width="746"]] 1201 1201 1202 1202 1203 1203 ... ... @@ -1204,10 +1204,10 @@ 1204 1204 **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.** 1205 1205 1206 1206 1207 -[[image:image-20221116111844-4.png|| _mstalt="429780"height="641" width="739"]]1184 +[[image:image-20221116111844-4.png||height="641" width="739"]] 1208 1208 1209 1209 1210 -[[image:image-20221116111844-5.png|| _mstalt="430144"height="551" width="708"]]1187 +[[image:image-20221116111844-5.png||height="551" width="708"]] 1211 1211 1212 1212 1213 1213 = 8 Trouble Shooting = ... ... @@ -1238,7 +1238,7 @@ 1238 1238 ))) 1239 1239 1240 1240 1241 -[[image:image-20221118105249-3.png ||_mstalt="430664"]]1218 +[[image:image-20221118105249-3.png]] 1242 1242 1243 1243 1244 1244 === 8.3.2 TrackerD's led light is always GREEN on after upgrading === ... ... @@ -1251,12 +1251,12 @@ 1251 1251 1252 1252 Error shows below, user might erase the entire flash include u-boot partition which cause this issue. 1253 1253 1254 -[[image:image-20221122100004-1.png|| _mstalt="423514"height="497" width="534"]]1231 +[[image:image-20221122100004-1.png||height="497" width="534"]] 1255 1255 1256 1256 1257 1257 User need to upgrade again with below four files to solve this issue. 1258 1258 1259 - [[image:image-20221122100004-2.png|| _mstalt="423878"height="619" width="389"]]1236 + [[image:image-20221122100004-2.png||height="619" width="389"]] 1260 1260 1261 1261 **Figure 2** 1262 1262 ... ... @@ -1267,21 +1267,13 @@ 1267 1267 1268 1268 After the upgrade is completed, enter AT+CFG as shown in the figure below. 1269 1269 1270 -[[image:image-20221122100004-3.png ||_mstalt="424242"]]1247 +[[image:image-20221122100004-3.png]] 1271 1271 1272 1272 Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label. 1273 1273 1274 -After AT+FDR. please set 1275 1275 1276 -* AT+PDOP=7 1277 -* AT+FTIME=180000 1278 - 1279 1279 Example: 1280 1280 1281 -AT+PDOP=7.00 1282 - 1283 -AT+FTIME=180 1284 - 1285 1285 AT+DEUI=70B3D57ED0053981 1286 1286 1287 1287 AT+APPEUI=D23345667BCBCCAF ... ... @@ -1299,7 +1299,7 @@ 1299 1299 === 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 === 1300 1300 1301 1301 1302 -[[image:image-20221122100004-4.png ||_mstalt="424606"]]1271 +[[image:image-20221122100004-4.png]] 1303 1303 1304 1304 1305 1305 == 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == ... ... @@ -1315,11 +1315,11 @@ 1315 1315 1316 1316 2) Set PDOP to a higher value. 1317 1317 1318 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.)1287 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.) 1319 1319 1320 -* (% _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) 1321 1321 1322 -* (% _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) 1323 1323 1324 1324 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 1325 1325