Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)
Last modified by Xiaoling on 2023/12/27 09:15
From 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)
-
Attachments (0 modified, 7 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Bei1 +XWiki.Xiaoling - Content
-
... ... @@ -31,12 +31,9 @@ 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 -))) 35 35 36 36 ((( 37 37 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 - 40 40 ))) 41 41 42 42 [[image:1664499921684-770.png||_mstalt="298194"]] ... ... @@ -421,7 +421,7 @@ 421 421 === 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 422 422 423 423 424 -Set [[PNACKMD=1>>||anchor="H3.2.1 0A0A0AutoSendNone-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.421 +Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery. 425 425 426 426 427 427 (% style="color:red" %)**Note for this mode:** ... ... @@ -498,6 +498,8 @@ 498 498 * (% style="color:#037691" %)**SSID: **(%%)WiFi name. 499 499 * (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 500 500 498 + 499 + 501 501 === 2.4.7 Add Payload format in TTN V3 === 502 502 503 503 ... ... @@ -546,7 +546,7 @@ 546 546 547 547 total 273 entries,by default, 548 548 549 -User can set [[PNACKMD=1>>||anchor="H3.2.1 0A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.548 +User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 550 550 551 551 Example use case. 552 552 ... ... @@ -586,6 +586,9 @@ 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 588 +* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation. 589 +* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic. 590 +* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion. 589 589 590 590 == 2.10 LED Status == 591 591 ... ... @@ -664,7 +664,6 @@ 664 664 [[image:1664503047675-651.png||_mstalt="295386"]] 665 665 666 666 667 - 668 668 == 3.2 Command Set == 669 669 670 670 === 3.2.1 Set Transmit Interval === ... ... @@ -855,8 +855,9 @@ 855 855 856 856 857 857 858 -=== 3.2.10 Disable/Enable the confirmation mode === 859 +=== 3.2.10 Disable/Enable the confirmation mode === 859 859 861 + 860 860 * (% style="color:blue" %)**AT Command:** 861 861 862 862 (% style="color:#037691" %)**AT+CFM=xx** ... ... @@ -957,6 +957,26 @@ 957 957 Example: 0x24 01 ~/~/ Same as AT+CHE=1 958 958 959 959 962 +=== 3.2.16 Get or Set Threshold for motion detect(Since firmware 1.4.3) === 963 + 964 +User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event. 965 + 966 +(% style="color:blue" %)**AT Command:** 967 + 968 +(% style="color:#037691" %)**AT+PT=xx** 969 + 970 + Example: 971 + 972 + AT+PT=14 ~-~-> Set to detect car motion. 973 + 974 + AT+PT=41 ~-~-> set to detect walk motion. 975 + 976 + 977 +(% style="color:blue" %)**Downlink Payload:0xB4**(%%) 978 +0xB4 14 ~/~/ Same as AT+PT=14 979 + 980 + 981 + 960 960 = 4. Setting for Different Scenarios = 961 961 962 962 ... ... @@ -1193,7 +1193,7 @@ 1193 1193 1194 1194 1195 1195 ((( 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 1218 +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 1197 1197 ))) 1198 1198 1199 1199 ... ... @@ -1207,27 +1207,34 @@ 1207 1207 1208 1208 == 8.3 Problem after Upgrading Firmware == 1209 1209 1210 -=== 8.3.1 Continue Restart after upgrading === 1232 +=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading === 1211 1211 1212 1212 1213 -((( 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 1215 -))) 1235 +**Error Output** 1216 1216 1217 1217 1218 -[[image:image-2022111 8105249-3.png||_mstalt="430664"]]1238 +[[image:image-20221122100004-4.png||_mstalt="424606"]] 1219 1219 1220 1220 1221 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1241 +((( 1242 +Some partition is missed during upgrade, please upgrade below four files as example: 1222 1222 1244 +[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]] 1245 +))) 1223 1223 1247 + 1248 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1249 + 1250 + 1224 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 1225 1225 1226 1226 1227 -=== 8.3.3 "flash read err" after upgrade firmware === 1254 +=== 8.3.3 "flash read err" after upgrade firmware === 1228 1228 1256 + 1229 1229 Error shows below, user might erase the entire flash include u-boot partition which cause this issue. 1230 1230 1259 + 1231 1231 [[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]] 1232 1232 1233 1233 ... ... @@ -1238,23 +1238,27 @@ 1238 1238 **Figure 2** 1239 1239 1240 1240 1241 -=== 8.3. 3"Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===1270 +=== 8.3.4 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware === 1242 1242 1272 + 1243 1243 User might erase the entire flash include keys and default settings which cause this issue. 1244 1244 1245 -After the upgrade is completed, enter AT+CFG as shown in the figure below. 1275 +After the upgrade is completed, enter **AT+CFG** as shown in the figure below. 1246 1246 1277 + 1247 1247 [[image:image-20221122100004-3.png||_mstalt="424242"]] 1248 1248 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 1281 +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. 1282 + 1251 1251 After AT+FDR. please set 1252 1252 1253 -* AT+PDOP=7 1254 -* AT+FTIME=180000 1285 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7** 1255 1255 1256 - Example:1287 +* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000** 1257 1257 1289 +**Example:** 1290 + 1258 1258 AT+PDOP=7.00 1259 1259 1260 1260 AT+FTIME=180 ... ... @@ -1272,13 +1272,6 @@ 1272 1272 AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA) 1273 1273 1274 1274 1275 - 1276 -=== 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 === 1277 - 1278 - 1279 -[[image:image-20221122100004-4.png||_mstalt="424606"]] 1280 - 1281 - 1282 1282 == 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1283 1283 1284 1284 ... ... @@ -1301,6 +1301,38 @@ 1301 1301 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 1302 1302 1303 1303 1330 +== 8.6 When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets == 1331 + 1332 +When upgrading, use the erase button to upgrade 1333 + 1334 +[[image:image-20221128102938-1.png||height="537" width="335"]] 1335 + 1336 + 1337 +The parameters are displayed abnormally and cannot be fixed using AT+FDR 1338 + 1339 +[[image:image-20221128103040-2.png||height="431" width="525"]] 1340 + 1341 +Please upgrade these four files,link(The boot_app0 file is in the version folder you need) 1342 + 1343 +[[image:image-20221128110503-3.png||height="647" width="410"]] 1344 + 1345 +Reboot information after upgrade 1346 + 1347 +[[image:image-20221128111443-4.png||height="432" width="546"]] 1348 + 1349 +Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal 1350 + 1351 +[[image:image-20221128111850-5.png]] 1352 + 1353 +After the parameters return to normal, upgrade to the version you need again 1354 + 1355 +[[image:image-20221128111951-6.png||height="620" width="389"]] 1356 + 1357 +At this point, the parameters return to normal after running AT+FDR again 1358 + 1359 +[[image:image-20221128112035-7.png]] 1360 + 1361 + 1304 1304 = 9. Order Info = 1305 1305 1306 1306 ... ... @@ -1352,3 +1352,4 @@ 1352 1352 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1353 1353 1354 1354 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 1413 +)))
- image-20221128102938-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +41.3 KB - Content
- image-20221128103040-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +19.2 KB - Content
- image-20221128110503-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +45.6 KB - Content
- image-20221128111443-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +15.6 KB - Content
- image-20221128111850-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +14.5 KB - Content
- image-20221128111951-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +45.4 KB - Content
- image-20221128112035-7.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +14.7 KB - Content