Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)
Last modified by Xiaoling on 2023/12/27 09:15
From version 153.1
edited by Edwin Chen
on 2022/11/24 09:16
on 2022/11/24 09:16
Change comment:
There is no comment for this version
To version 164.1
edited by Bei Jinggeng
on 2022/11/28 14:10
on 2022/11/28 14:10
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. Edwin1 +XWiki.Bei - 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.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. 425 425 426 426 427 427 (% style="color:red" %)**Note for this mode:** ... ... @@ -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.546 +User can set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 550 550 551 551 Example use case. 552 552 ... ... @@ -590,7 +590,6 @@ 590 590 * **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic. 591 591 * **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion. 592 592 593 - 594 594 == 2.10 LED Status == 595 595 596 596 ... ... @@ -668,7 +668,6 @@ 668 668 [[image:1664503047675-651.png||_mstalt="295386"]] 669 669 670 670 671 - 672 672 == 3.2 Command Set == 673 673 674 674 === 3.2.1 Set Transmit Interval === ... ... @@ -859,8 +859,9 @@ 859 859 860 860 861 861 862 -=== 3.2.10 Disable/Enable the confirmation mode === 857 +=== 3.2.10 Disable/Enable the confirmation mode === 863 863 859 + 864 864 * (% style="color:blue" %)**AT Command:** 865 865 866 866 (% style="color:#037691" %)**AT+CFM=xx** ... ... @@ -1217,7 +1217,7 @@ 1217 1217 1218 1218 1219 1219 ((( 1220 -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 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 1221 1221 ))) 1222 1222 1223 1223 ... ... @@ -1231,27 +1231,34 @@ 1231 1231 1232 1232 == 8.3 Problem after Upgrading Firmware == 1233 1233 1234 -=== 8.3.1 Continue Restart after upgrading === 1230 +=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading === 1235 1235 1236 1236 1237 -((( 1238 -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 1239 -))) 1233 +**Error Output** 1240 1240 1241 1241 1242 -[[image:image-2022111 8105249-3.png||_mstalt="430664"]]1236 +[[image:image-20221122100004-4.png||_mstalt="424606"]] 1243 1243 1244 1244 1245 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1239 +((( 1240 +Some partition is missed during upgrade, please upgrade below four files as example: 1246 1246 1242 +[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]] 1243 +))) 1247 1247 1245 + 1246 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1247 + 1248 + 1248 1248 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 1249 1249 1250 1250 1251 -=== 8.3.3 "flash read err" after upgrade firmware === 1252 +=== 8.3.3 "flash read err" after upgrade firmware === 1252 1252 1254 + 1253 1253 Error shows below, user might erase the entire flash include u-boot partition which cause this issue. 1254 1254 1257 + 1255 1255 [[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]] 1256 1256 1257 1257 ... ... @@ -1262,23 +1262,27 @@ 1262 1262 **Figure 2** 1263 1263 1264 1264 1265 -=== 8.3. 3"Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===1268 +=== 8.3.4 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware === 1266 1266 1270 + 1267 1267 User might erase the entire flash include keys and default settings which cause this issue. 1268 1268 1269 -After the upgrade is completed, enter AT+CFG as shown in the figure below. 1273 +After the upgrade is completed, enter **AT+CFG** as shown in the figure below. 1270 1270 1275 + 1271 1271 [[image:image-20221122100004-3.png||_mstalt="424242"]] 1272 1272 1273 -Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label. 1274 1274 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. 1280 + 1275 1275 After AT+FDR. please set 1276 1276 1277 -* AT+PDOP=7 1278 -* AT+FTIME=180000 1283 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7** 1279 1279 1280 - Example:1285 +* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000** 1281 1281 1287 +**Example:** 1288 + 1282 1282 AT+PDOP=7.00 1283 1283 1284 1284 AT+FTIME=180 ... ... @@ -1296,13 +1296,6 @@ 1296 1296 AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA) 1297 1297 1298 1298 1299 - 1300 -=== 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 === 1301 - 1302 - 1303 -[[image:image-20221122100004-4.png||_mstalt="424606"]] 1304 - 1305 - 1306 1306 == 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1307 1307 1308 1308 ... ... @@ -1325,6 +1325,38 @@ 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 + 1328 1328 = 9. Order Info = 1329 1329 1330 1330 ... ... @@ -1376,3 +1376,4 @@ 1376 1376 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1377 1377 1378 1378 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 1411 +)))
- 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