Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 164.1
edited by Bei Jinggeng
on 2022/11/28 14:10
Change comment: There is no comment for this version
To version 152.1
edited by Edwin Chen
on 2022/11/24 09:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Edwin
Content
... ... @@ -31,9 +31,12 @@
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 +)))
34 34  
35 35  (((
36 36  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 +
37 37  )))
38 38  
39 39  [[image:1664499921684-770.png||_mstalt="298194"]]
... ... @@ -418,7 +418,7 @@
418 418  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
419 419  
420 420  
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.
424 +Set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-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.
422 422  
423 423  
424 424  (% style="color:red" %)**Note for this mode:**
... ... @@ -543,7 +543,7 @@
543 543  
544 544  total 273 entries,by default,
545 545  
546 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
549 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
547 547  
548 548  Example use case.
549 549  
... ... @@ -585,7 +585,7 @@
585 585  
586 586  * **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
587 587  * **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
588 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
591 +* **[[PT>>||anchor="H3.2.1SetTransmitInterval"]]** defines the threldhold to detect a motion.
589 589  
590 590  == 2.10 LED Status ==
591 591  
... ... @@ -664,6 +664,7 @@
664 664  [[image:1664503047675-651.png||_mstalt="295386"]]
665 665  
666 666  
670 +
667 667  == 3.2 Command Set ==
668 668  
669 669  === 3.2.1 Set Transmit Interval ===
... ... @@ -854,9 +854,8 @@
854 854  
855 855  
856 856  
857 -=== 3.2.10 Disable/Enable the confirmation mode ===
861 +=== 3.2.10 Disable/Enable the confirmation mode ===
858 858  
859 -
860 860  * (% style="color:blue" %)**AT Command:**
861 861  
862 862  (% style="color:#037691" %)**AT+CFM=xx**
... ... @@ -1213,7 +1213,7 @@
1213 1213  
1214 1214  
1215 1215  (((
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
1219 +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
1217 1217  )))
1218 1218  
1219 1219  
... ... @@ -1227,34 +1227,27 @@
1227 1227  
1228 1228  == 8.3  Problem after Upgrading Firmware ==
1229 1229  
1230 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1233 +=== 8.3.1 Continue Restart after upgrading ===
1231 1231  
1232 1232  
1233 -**Error Output**
1234 -
1235 -
1236 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1237 -
1238 -
1239 1239  (((
1240 -Some partition is missed during upgrade, please upgrade below four files as example:
1241 -
1242 -[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1237 +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
1243 1243  )))
1244 1244  
1245 1245  
1246 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1241 +[[image:image-20221118105249-3.png||_mstalt="430664"]]
1247 1247  
1248 1248  
1249 -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
1244 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1250 1250  
1251 1251  
1252 -=== 8.3.3 "flash read err" after upgrade firmware ===
1247 +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
1253 1253  
1254 1254  
1250 +=== 8.3.3 "flash read err" after upgrade firmware ===
1251 +
1255 1255  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1256 1256  
1257 -
1258 1258  [[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1259 1259  
1260 1260  
... ... @@ -1265,27 +1265,23 @@
1265 1265   **Figure 2**
1266 1266  
1267 1267  
1268 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1264 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1269 1269  
1270 -
1271 1271  User might erase the entire flash include keys and default settings which cause this issue.
1272 1272  
1273 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1268 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1274 1274  
1275 -
1276 1276  [[image:image-20221122100004-3.png||_mstalt="424242"]]
1277 1277  
1272 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1278 1278  
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 -
1281 1281  After AT+FDR. please set
1282 1282  
1283 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1276 +* AT+PDOP=7
1277 +* AT+FTIME=180000
1284 1284  
1285 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1279 +Example:
1286 1286  
1287 -**Example:**
1288 -
1289 1289  AT+PDOP=7.00
1290 1290  
1291 1291  AT+FTIME=180
... ... @@ -1303,6 +1303,13 @@
1303 1303  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1304 1304  
1305 1305  
1298 +
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 +
1301 +
1302 +[[image:image-20221122100004-4.png||_mstalt="424606"]]
1303 +
1304 +
1306 1306  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1307 1307  
1308 1308  
... ... @@ -1325,38 +1325,6 @@
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 -
1360 1360  = 9.  Order Info =
1361 1361  
1362 1362  
... ... @@ -1408,4 +1408,3 @@
1408 1408  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1409 1409  
1410 1410  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1411 -)))
image-20221128102938-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -41.3 KB
Content
image-20221128103040-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -19.2 KB
Content
image-20221128110503-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.6 KB
Content
image-20221128111443-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -15.6 KB
Content
image-20221128111850-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.5 KB
Content
image-20221128111951-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.4 KB
Content
image-20221128112035-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.7 KB
Content