Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)
Last modified by Xiaoling on 2023/12/27 09:15
From 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
To version 148.1
edited by Bei Jinggeng
on 2022/11/24 09:06
on 2022/11/24 09:06
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.Bei - Content
-
... ... @@ -1,5 +1,5 @@ 1 1 (% style="text-align:center" %) 2 -[[image:1664505654417-133.png]] 2 +[[image:1664505654417-133.png||_mstalt="293696"]] 3 3 4 4 5 5 ... ... @@ -39,7 +39,7 @@ 39 39 40 40 ))) 41 41 42 -[[image:1664499921684-770.png]] 42 +[[image:1664499921684-770.png||_mstalt="298194"]] 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]] 136 +[[image:1664501652064-326.png||_mstalt="293306"]] 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]] 148 +[[image:1664501677253-891.png||_mstalt="296569"]] 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]] 157 +[[image:1664501711466-918.png||_mstalt="295828"]] 158 158 159 159 160 160 161 -[[image:1664501721248-725.png]] 161 +[[image:1664501721248-725.png||_mstalt="294450"]] 162 162 163 163 164 -[[image:1664501734705-405.png]] 164 +[[image:1664501734705-405.png||_mstalt="293306"]] 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||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||_mstalt="298233" 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]] 177 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]] 178 178 179 -[[image:1664502835802-546.png]] 179 +[[image:1664502835802-546.png||_mstalt="295061"]] 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]] 211 +[[image:1665301570342-765.png||_mstalt="294580"]] 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 -(% style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%) 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)(%%) 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]] 305 +[[image:1665301636888-168.png||_mstalt="298012"]] 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]] 335 +[[image:1664502116362-706.png||_mstalt="293306"]] 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]] 340 +[[image:1664502166010-515.png||_mstalt="291395"]] 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]] 418 +[[image:1665301687277-443.png||_mstalt="296140"]] 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]] 441 +[[image:image-20221009160309-2.png||_mstalt="429312"]] 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]] 468 +[[image:1664502425687-834.png||_mstalt="296738"]] 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||height="212" width="1151"]] 494 +[[image:1667288597595-714.png||_mstalt="299598" 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]] 509 +[[image:1664502649601-895.png||_mstalt="296985"]] 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]] 519 +[[image:1664502676891-606.png||_mstalt="296673"]] 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]] 530 +[[image:1664502695771-538.png||_mstalt="297349"]] 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]] 541 +[[image:1664502715371-321.png||_mstalt="292162"]] 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||height="328" width="899"]] 553 +[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]] 554 554 555 555 556 -[[image:image-20221009234629-1.png||height="390" width="577"]] 556 +[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]] 557 557 558 558 559 559 == 2.8 Alarm Mode == ... ... @@ -609,7 +609,7 @@ 609 609 610 610 (% style="color:blue" %)**RESET button:** 611 611 612 -[[image:1664502835802-546.png]] 612 +[[image:1664502835802-546.png||_mstalt="295061"]] 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]] 619 +[[image:1664502854406-763.png||_mstalt="295568"]] 620 620 621 621 622 622 (% border="1" style="background-color:#ffffcc; width:510px" %) ... ... @@ -649,19 +649,19 @@ 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]] 652 +[[image:1664502999401-486.png||_mstalt="296985"]] 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]] 658 +[[image:1664503022490-662.png||_mstalt="293332"]] 659 659 660 660 661 -[[image:1664503035713-500.png]] 661 +[[image:1664503035713-500.png||_mstalt="291096"]] 662 662 663 663 664 -[[image:1664503047675-651.png]] 664 +[[image:1664503047675-651.png||_mstalt="295386"]] 665 665 666 666 667 667 ... ... @@ -790,9 +790,9 @@ 790 790 791 791 (% style="color:#037691" %)**cc: ** 792 792 793 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 793 +* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 794 794 795 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%)) 795 +* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%)) 796 796 797 797 (% style="color:blue" %)**Example:** 798 798 ... ... @@ -855,7 +855,7 @@ 855 855 856 856 857 857 858 - **Disable/Enable the confirmation mode**858 +=== 3.2.10 Disable/Enable the confirmation mode === 859 859 860 860 * (% style="color:blue" %)**AT Command:** 861 861 ... ... @@ -874,7 +874,7 @@ 874 874 (% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1 875 875 876 876 877 -=== 3.2.1 0877 +=== 3.2.11 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: 0x3401 ~/~/ Same as AT+PNACKMD=1 895 +Example: 0x34 01 ~/~/ Same as AT+PNACKMD=1 896 896 897 897 898 -=== 3.2.1 1Set BLEMASK to filter BLE iBeacon ===898 +=== 3.2.12 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 - (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 907 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 908 908 909 - (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 909 + (% _mstmutation="1" 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: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 913 +Example: 0xB2 01 02 03 04 05 06 ~/~/ Set BLEMASK to 123456 914 914 915 915 916 -=== 3.2.1 2Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) ===916 +=== 3.2.13 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 - (% style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456 925 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456 926 926 927 - (% style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK 927 + (% _mstmutation="1" 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: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 931 +Example: 0xB3 01 02 03 04 05 06 ~/~/ Set WiFiMASK to 123456 932 932 933 933 934 -=== 3.2.1 3934 +=== 3.2.14 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.1 4Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) ===945 +=== 3.2.15 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. ... ... @@ -989,10 +989,10 @@ 989 989 (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32 990 990 991 991 992 -[[image:1664503563660-578.png]] 992 +[[image:1664503563660-578.png||_mstalt="296777"]] 993 993 994 994 995 -[[image:1664503574618-659.png]] 995 +[[image:1664503574618-659.png||_mstalt="297986"]] 996 996 997 997 998 998 ... ... @@ -1008,13 +1008,13 @@ 1008 1008 US915.bin @ 0x10000(Select the bin file of the frequency band you need) 1009 1009 1010 1010 1011 -[[image:image-20221118105220-2.png]] 1011 +[[image:image-20221118105220-2.png||_mstalt="426608"]] 1012 1012 1013 1013 1014 1014 1015 1015 After upgrade finish, it will show finish as below: 1016 1016 1017 -[[image:image-20221118105402-4.png]] 1017 +[[image:image-20221118105402-4.png||_mstalt="427986"]] 1018 1018 1019 1019 1020 1020 ... ... @@ -1030,23 +1030,23 @@ 1030 1030 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]] 1031 1031 1032 1032 1033 -[[image:1664503635019-941.png]] 1033 +[[image:1664503635019-941.png||_mstalt="294658"]] 1034 1034 1035 1035 1036 1036 1037 1037 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 1038 1038 1039 -[[image:1664503715811-892.png]] 1039 +[[image:1664503715811-892.png||_mstalt="295698"]] 1040 1040 1041 1041 1042 1042 (% 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. 1043 1043 1044 -[[image:image-20221024105643-1.png]] 1044 +[[image:image-20221024105643-1.png||_mstalt="428129"]] 1045 1045 1046 1046 **~ Figure1** 1047 1047 1048 1048 1049 -[[image:image-20221024105643-2.png]] 1049 +[[image:image-20221024105643-2.png||_mstalt="428493"]] 1050 1050 1051 1051 **Figure2** 1052 1052 ... ... @@ -1056,7 +1056,7 @@ 1056 1056 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: 1057 1057 1058 1058 1059 -[[image:1664503752288-974.png]] 1059 +[[image:1664503752288-974.png||_mstalt="298194"]] 1060 1060 1061 1061 1062 1062 == 6.2 Source Code == ... ... @@ -1064,19 +1064,19 @@ 1064 1064 1065 1065 * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:** 1066 1066 1067 -[[image:1664503794261-827.png]] 1067 +[[image:1664503794261-827.png||_mstalt="296387"]] 1068 1068 1069 1069 1070 1070 1071 1071 * (% style="color:blue" %)**Click to upload** 1072 1072 1073 -[[image:1664503808294-336.png]] 1073 +[[image:1664503808294-336.png||_mstalt="295711"]] 1074 1074 1075 1075 1076 1076 1077 1077 * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 1078 1078 1079 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 1079 +[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]] 1080 1080 1081 1081 1082 1082 = 7. FAQ = ... ... @@ -1090,7 +1090,7 @@ 1090 1090 == 7.2 What is the pin mapping for the USB program cable? == 1091 1091 1092 1092 1093 -[[image:1664499635206-262.png]] 1093 +[[image:1664499635206-262.png||_mstalt="295360"]] 1094 1094 1095 1095 1096 1096 ... ... @@ -1115,13 +1115,13 @@ 1115 1115 Need to adjust the data stream to RTS/CTS on physical restart. 1116 1116 1117 1117 (% class="wikigeneratedid" %) 1118 -[[image:image-20221102140621-1.png]] 1118 +[[image:image-20221102140621-1.png||_mstalt="425672"]] 1119 1119 1120 1120 1121 1121 1122 1122 When using AT commands, the data flow needs to be adjusted to XON/XOFF 1123 1123 1124 -[[image:image-20221102140638-2.png]] 1124 +[[image:image-20221102140638-2.png||_mstalt="428727"]] 1125 1125 1126 1126 1127 1127 === 7.3.2 SecureCRT === ... ... @@ -1130,22 +1130,22 @@ 1130 1130 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. 1131 1131 1132 1132 1133 -[[image:image-20221102140704-3.png]] 1133 +[[image:image-20221102140704-3.png||_mstalt="427076"]] 1134 1134 1135 1135 1136 -[[image:image-20221102140712-4.png]] 1136 +[[image:image-20221102140712-4.png||_mstalt="427089"]] 1137 1137 1138 1138 1139 1139 === 7.3.3 PUTTY === 1140 1140 1141 1141 1142 -[[image:image-20221102140748-5.png]] 1142 +[[image:image-20221102140748-5.png||_mstalt="430456"]] 1143 1143 1144 1144 1145 1145 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. 1146 1146 1147 1147 1148 -[[image:image-20221102140801-6.png]] 1148 +[[image:image-20221102140801-6.png||_mstalt="427466"]] 1149 1149 1150 1150 1151 1151 == 7.4 How to modify source code to compile different frequency band bin file? == ... ... @@ -1160,7 +1160,7 @@ 1160 1160 **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.** 1161 1161 1162 1162 1163 -[[image:image-20221116111844-1.png||height="227" width="782"]] 1163 +[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]] 1164 1164 1165 1165 1166 1166 ... ... @@ -1167,7 +1167,7 @@ 1167 1167 **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).** 1168 1168 1169 1169 1170 -[[image:image-20221116111844-2.png||height="262" width="781"]] 1170 +[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]] 1171 1171 1172 1172 1173 1173 ... ... @@ -1174,7 +1174,7 @@ 1174 1174 **3. Compile the AS923_JP band, please refer to the intention shown** 1175 1175 1176 1176 1177 -[[image:image-20221116111844-3.png||height="338" width="746"]] 1177 +[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]] 1178 1178 1179 1179 1180 1180 ... ... @@ -1181,10 +1181,10 @@ 1181 1181 **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.** 1182 1182 1183 1183 1184 -[[image:image-20221116111844-4.png||height="641" width="739"]] 1184 +[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]] 1185 1185 1186 1186 1187 -[[image:image-20221116111844-5.png||height="551" width="708"]] 1187 +[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]] 1188 1188 1189 1189 1190 1190 = 8 Trouble Shooting = ... ... @@ -1215,7 +1215,7 @@ 1215 1215 ))) 1216 1216 1217 1217 1218 -[[image:image-20221118105249-3.png]] 1218 +[[image:image-20221118105249-3.png||_mstalt="430664"]] 1219 1219 1220 1220 1221 1221 === 8.3.2 TrackerD's led light is always GREEN on after upgrading === ... ... @@ -1228,12 +1228,12 @@ 1228 1228 1229 1229 Error shows below, user might erase the entire flash include u-boot partition which cause this issue. 1230 1230 1231 -[[image:image-20221122100004-1.png||height="497" width="534"]] 1231 +[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]] 1232 1232 1233 1233 1234 1234 User need to upgrade again with below four files to solve this issue. 1235 1235 1236 - [[image:image-20221122100004-2.png||height="619" width="389"]] 1236 + [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]] 1237 1237 1238 1238 **Figure 2** 1239 1239 ... ... @@ -1244,13 +1244,21 @@ 1244 1244 1245 1245 After the upgrade is completed, enter AT+CFG as shown in the figure below. 1246 1246 1247 -[[image:image-20221122100004-3.png]] 1247 +[[image:image-20221122100004-3.png||_mstalt="424242"]] 1248 1248 1249 1249 Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label. 1250 1250 1251 +After AT+FDR. please set 1251 1251 1253 +* AT+PDOP=7 1254 +* AT+FTIME=180000 1255 + 1252 1252 Example: 1253 1253 1258 +AT+PDOP=7.00 1259 + 1260 +AT+FTIME=180 1261 + 1254 1254 AT+DEUI=70B3D57ED0053981 1255 1255 1256 1256 AT+APPEUI=D23345667BCBCCAF ... ... @@ -1268,7 +1268,7 @@ 1268 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 1269 1270 1270 1271 -[[image:image-20221122100004-4.png]] 1279 +[[image:image-20221122100004-4.png||_mstalt="424606"]] 1272 1272 1273 1273 1274 1274 == 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == ... ... @@ -1284,11 +1284,11 @@ 1284 1284 1285 1285 2) Set PDOP to a higher value. 1286 1286 1287 -* 1295 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.) 1288 1288 1289 -* 1297 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces) 1290 1290 1291 -* 1299 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments) 1292 1292 1293 1293 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 1294 1294