Last modified by Xiaoling on 2023/12/27 09:15

From version 164.2
edited by Xiaoling
on 2022/11/28 15:32
Change comment: There is no comment for this version
To version 153.1
edited by Edwin Chen
on 2022/11/24 09:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
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.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.
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:**
... ... @@ -495,8 +495,6 @@
495 495  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
496 496  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
497 497  
498 -
499 -
500 500  === 2.4.7  Add Payload format in TTN V3 ===
501 501  
502 502  
... ... @@ -545,7 +545,7 @@
545 545  
546 546  total 273 entries,by default,
547 547  
548 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
549 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
549 549  
550 550  Example use case.
551 551  
... ... @@ -589,6 +589,7 @@
589 589  * **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
590 590  * **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
591 591  
593 +
592 592  == 2.10 LED Status ==
593 593  
594 594  
... ... @@ -666,6 +666,7 @@
666 666  [[image:1664503047675-651.png||_mstalt="295386"]]
667 667  
668 668  
671 +
669 669  == 3.2 Command Set ==
670 670  
671 671  === 3.2.1 Set Transmit Interval ===
... ... @@ -856,9 +856,8 @@
856 856  
857 857  
858 858  
859 -=== 3.2.10 Disable/Enable the confirmation mode ===
862 +=== 3.2.10 Disable/Enable the confirmation mode ===
860 860  
861 -
862 862  * (% style="color:blue" %)**AT Command:**
863 863  
864 864  (% style="color:#037691" %)**AT+CFM=xx**
... ... @@ -1215,7 +1215,7 @@
1215 1215  
1216 1216  
1217 1217  (((
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
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
1219 1219  )))
1220 1220  
1221 1221  
... ... @@ -1229,34 +1229,27 @@
1229 1229  
1230 1230  == 8.3  Problem after Upgrading Firmware ==
1231 1231  
1232 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1234 +=== 8.3.1 Continue Restart after upgrading ===
1233 1233  
1234 1234  
1235 -**Error Output**
1236 -
1237 -
1238 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1239 -
1240 -
1241 1241  (((
1242 -Some partition is missed during upgrade, please upgrade below four files as example:
1243 -
1244 -[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
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
1245 1245  )))
1246 1246  
1247 1247  
1248 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1242 +[[image:image-20221118105249-3.png||_mstalt="430664"]]
1249 1249  
1250 1250  
1251 -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
1245 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1252 1252  
1253 1253  
1254 -=== 8.3.3 "flash read err" after upgrade firmware ===
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
1255 1255  
1256 1256  
1251 +=== 8.3.3 "flash read err" after upgrade firmware ===
1252 +
1257 1257  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1258 1258  
1259 -
1260 1260  [[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1261 1261  
1262 1262  
... ... @@ -1267,27 +1267,23 @@
1267 1267   **Figure 2**
1268 1268  
1269 1269  
1270 -=== 8.3. "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1265 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1271 1271  
1272 -
1273 1273  User might erase the entire flash include keys and default settings which cause this issue.
1274 1274  
1275 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1269 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1276 1276  
1277 -
1278 1278  [[image:image-20221122100004-3.png||_mstalt="424242"]]
1279 1279  
1273 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1280 1280  
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 -
1283 1283  After AT+FDR. please set
1284 1284  
1285 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1277 +* AT+PDOP=7
1278 +* AT+FTIME=180000
1286 1286  
1287 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1280 +Example:
1288 1288  
1289 -**Example:**
1290 -
1291 1291  AT+PDOP=7.00
1292 1292  
1293 1293  AT+FTIME=180
... ... @@ -1305,6 +1305,13 @@
1305 1305  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1306 1306  
1307 1307  
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 +
1308 1308  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1309 1309  
1310 1310  
... ... @@ -1327,38 +1327,6 @@
1327 1327  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
1328 1328  
1329 1329  
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 -
1362 1362  = 9.  Order Info =
1363 1363  
1364 1364  
... ... @@ -1410,4 +1410,3 @@
1410 1410  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1411 1411  
1412 1412  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1413 -)))
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