Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Xiaoling on 2025/04/27 16:48
From version 86.1
edited by Kilight Cao
on 2022/11/01 15:51
on 2022/11/01 15:51
Change comment:
There is no comment for this version
To version 112.1
edited by Bei Jinggeng
on 2022/11/07 14:52
on 2022/11/07 14:52
Change comment:
Uploaded new attachment "image-20221107145243-1.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 7 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Kilight1 +XWiki.Bei - Content
-
... ... @@ -121,7 +121,7 @@ 121 121 * Logistics and Supply Chain Management 122 122 * Human tracking 123 123 124 -= 2. 1124 += 2. Use TrackerD = 125 125 126 126 127 127 == 2.1 How it works? == ... ... @@ -189,9 +189,9 @@ 189 189 190 190 Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 191 191 192 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%) only get and uplink GPS location info.193 -* (% style="color:#037691" %)**BLE or WiFi ONLY: **(%%)** **Only obtain iBeacon info via BLE and uplink or obtain wifi ssid info via WiFi and uplink. Design for Indoor tracking. 194 -* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 192 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 193 +* (% style="color:#037691" %)**BLE or WiFi ONLY: **(%%)** **Only obtain iBeacon info via BLE and uplink or obtain wifi ssid info via WiFi and uplink. Design for Indoor tracking. 194 +* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking. Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 195 195 196 196 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 197 197 ... ... @@ -279,7 +279,9 @@ 279 279 280 280 (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 281 281 282 +(% style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%) 282 282 284 + 283 283 (% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 284 284 285 285 (% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %) ... ... @@ -431,7 +431,7 @@ 431 431 (% style="color:red" %)**Note for this mode:** 432 432 433 433 * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server. 434 -* b) TrackerD will send data in (% style="color:blue" %)**CONFIRMED Mode**(%%)when PNACKMD=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.436 +* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages. 435 435 * c) the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes of payload. In this case (DR0 of US915/AU915), the payload on server will show NULL 436 436 437 437 The payload is 15 bytes, as below. ... ... @@ -481,10 +481,10 @@ 481 481 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 482 482 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 483 483 484 -=== 2.4.6 Uplink FPORT~= 6, WiFi Positioning with Strongest WiFi SSID ===486 +=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 485 485 486 486 487 -TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to ** BLE pure** or **GPS/BLE hybrid** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.489 +TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **WiFi** so TrackerD will scan WiFi and find the strongest WiFi info and uplink. 488 488 489 489 490 490 (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %) ... ... @@ -729,7 +729,7 @@ 729 729 730 730 * (% style="color:blue" %)**Downlink Payload (prefix 0x03):** 731 731 732 -(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+ 734 +(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+MTDC=3000000 733 733 734 734 735 735 ... ... @@ -773,12 +773,12 @@ 773 773 774 774 (% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)** 775 775 776 -Example: AT+ 778 +Example: AT+INTWK=1 **~-~-> ** Enable Transport Mode. 777 777 778 778 779 779 * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):** 780 780 781 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+ 783 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+INTWK=1 782 782 783 783 784 784 ... ... @@ -794,9 +794,9 @@ 794 794 795 795 (% style="color:#037691" %)** aa:** 796 796 797 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%) only get and uplink GPS location info.798 -* (% style="color:red" %)**2: BLE or WiFi ONLY: **(%%)Only obtain iBeacon info via BLE and uplink or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking. 799 -* (% style="color:red" %)**3: GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 799 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 800 +* (% style="color:red" %)**2: BLE or WiFi ONLY: **(%%)Only obtain iBeacon info via BLE and uplink or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking. 801 +* (% style="color:red" %)**3: GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 800 800 801 801 (% style="color:#037691" %)**bb:** 802 802 ... ... @@ -810,15 +810,15 @@ 810 810 811 811 (% style="color:blue" %)**Example:** 812 812 813 - AT+ 814 - AT+ 815 - AT+ 816 - AT+ 815 + AT+SMOD=1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 816 + AT+SMOD=1,1,0 ~-~-> GPS +BAT State 817 + AT+SMOD=2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 818 + AT+SMOD=2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State 817 817 818 818 819 819 * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** 820 820 821 -(% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+ 823 +(% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+SMOD=1,0,0 822 822 823 823 824 824 ... ... @@ -877,14 +877,14 @@ 877 877 878 878 **~ Example:** 879 879 880 - AT+ 882 + AT+CFM=0 **~-~-> ** Disable confirmation 881 881 882 - AT+ 884 + AT+CFM=1 **~-~-> ** Enable confirmation 883 883 884 884 885 885 * (% style="color:blue" %)**Downlink Payload (prefix 0x05):** 886 886 887 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+ SMOD=1889 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1 888 888 889 889 890 890 ... ... @@ -923,31 +923,57 @@ 923 923 924 924 (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 925 925 928 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 926 926 927 - (% style="color:blue"%)**DownlinkPayload: (Prefix:0xA5)**930 +Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 928 928 929 -Example: 0xA5010203040506 ~/~/ Set BLEMASK to 123456 930 930 931 931 932 -=== 3.2.12 Set WiFIMASK to filter WiFi SSID === 934 +=== 3.2.12 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 933 933 934 934 935 -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. It will ignore all other WiFi which doesn’t contact 123456 in the SSID. 937 +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. 936 936 937 937 (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.** 938 938 939 939 (% style="color:blue" %)**AT Command:** 940 940 941 - (% style="color:#037691" %)**AT+ 943 + (% style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456 942 942 943 - (% style="color:#037691" %)**AT+ 945 + (% style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK 944 944 947 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)** 945 945 946 - (% style="color:blue"%)**DownlinkPayload:(Prefix:0xA5)**949 +Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 947 947 948 -Example: 0xA5010203040506 ~/~/ Set WiFiMASK to 123456 949 949 950 950 953 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 954 + 955 + 956 +Users can use this feature to enable/disable Information printing. 957 + 958 +(% style="color:blue" %)**AT Command:** 959 + 960 +(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/(Disable (0), Enable (1), default:0) 961 +\\Example: AT+SHOWID=1 ~-~-> Enable Information printing. 962 + 963 + 964 + 965 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 966 + 967 + 968 +The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. 969 + 970 +(% style="color:blue" %)**AT Command:** 971 + 972 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode, 973 + 974 +(% style="color:blue" %)**Downlink Payload:0X24**(%%) 975 +Example: 0x24 01 ~/~/ Same as AT+CHE=1 976 + 977 + 978 + 951 951 = 4. Setting for Different Scenarios = 952 952 953 953 ... ... @@ -1104,9 +1104,69 @@ 1104 1104 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 1105 1105 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 1106 1106 1107 -= 8.OrderInfo =1135 +== 7.3 Notes on using different serial port tools for TrackerD == 1108 1108 1109 1109 1138 +=== **Serial port utility** === 1139 + 1140 + 1141 +Serial port utility requires you to automatically add data streams. 1142 + 1143 +Need to adjust the data stream to RTS/CTS on physical restart. 1144 + 1145 + 1146 +(% class="wikigeneratedid" %) 1147 +[[image:image-20221102140621-1.png]] 1148 + 1149 + 1150 +When using AT commands, the data flow needs to be adjusted to XON/XOFF 1151 + 1152 + 1153 +[[image:image-20221102140638-2.png]] 1154 + 1155 + 1156 + 1157 +=== **SecureCRT** === 1158 + 1159 + 1160 +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. 1161 + 1162 + 1163 +[[image:image-20221102140704-3.png]] 1164 + 1165 + 1166 +[[image:image-20221102140712-4.png]] 1167 + 1168 + 1169 + 1170 +=== **PUTTY** === 1171 + 1172 + 1173 +[[image:image-20221102140748-5.png]] 1174 + 1175 + 1176 +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. 1177 + 1178 + 1179 +[[image:image-20221102140801-6.png]] 1180 + 1181 + 1182 += 8 Trouble Shooting = 1183 + 1184 +== 8.1 TDC is changed to 4294947296 and cause no uplink. == 1185 + 1186 +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 1187 + 1188 + 1189 +== 8.2 Device not able get AT Command or show output after wake up from deep sleep mode == 1190 + 1191 +ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode. 1192 + 1193 + 1194 + 1195 += 9. Order Info = 1196 + 1197 + 1110 1110 Part Number: (% style="color:blue" %)**TrackerD-XXX** 1111 1111 1112 1112 (% style="color:blue" %)**XXX**(%%): The default frequency band ... ... @@ -1119,7 +1119,7 @@ 1119 1119 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 1120 1120 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1121 1121 1122 -= 9. Packing Info =1210 += 10. Packing Info = 1123 1123 1124 1124 1125 1125 (% style="color:#037691" %)**Package Includes**: ... ... @@ -1129,16 +1129,16 @@ 1129 1129 1130 1130 (% style="color:#037691" %)**Dimensions and Weight**: 1131 1131 1132 -* Device Size: 85 x 48 x 15 cm1220 +* Device Size: 85 x 48 x 15 mm 1133 1133 * Weight: 50g 1134 1134 1135 -= 1 0. Support =1223 += 11. Support = 1136 1136 1137 1137 1138 1138 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 1139 1139 * 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]]. 1140 1140 1141 -= 1 1. Reference =1229 += 12. Reference = 1142 1142 1143 1143 1144 1144 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
- image-20221102140621-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +46.1 KB - Content
- image-20221102140638-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +40.8 KB - Content
- image-20221102140704-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +15.5 KB - Content
- image-20221102140712-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +73.2 KB - Content
- image-20221102140748-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +56.0 KB - Content
- image-20221102140801-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +21.0 KB - Content
- image-20221107145243-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +107.3 KB - Content