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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +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.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.
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.10A0A0AutoSendNone-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  
... ... @@ -588,9 +588,8 @@
588 588  
589 589  * **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
590 590  * **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
591 -* **[[PT>>||anchor="H3.2.1SetTransmitInterval"]]** defines the threldhold to detect a motion.
588 +* **[[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**
... ... @@ -961,6 +961,26 @@
961 961  Example: 0x24 01 ~/~/ Same as AT+CHE=1
962 962  
963 963  
960 +=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
961 +
962 +User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
963 +
964 +(% style="color:blue" %)**AT Command:**
965 +
966 +(% style="color:#037691" %)**AT+PT=xx**
967 +
968 + Example:
969 +
970 + AT+PT=14    ~-~->    Set to detect car motion.
971 +
972 + AT+PT=41   ~-~->    set to detect walk motion.
973 +
974 +
975 +(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
976 +0xB4 14          ~/~/  Same as AT+PT=14
977 +
978 +
979 +
964 964  = 4. Setting for Different Scenarios =
965 965  
966 966  
... ... @@ -1197,7 +1197,7 @@
1197 1197  
1198 1198  
1199 1199  (((
1200 -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
1201 1201  )))
1202 1202  
1203 1203  
... ... @@ -1211,27 +1211,34 @@
1211 1211  
1212 1212  == 8.3  Problem after Upgrading Firmware ==
1213 1213  
1214 -=== 8.3.1 Continue Restart after upgrading ===
1230 +=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1215 1215  
1216 1216  
1217 -(((
1218 -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
1219 -)))
1233 +**Error Output**
1220 1220  
1221 1221  
1222 -[[image:image-20221118105249-3.png||_mstalt="430664"]]
1236 +[[image:image-20221122100004-4.png||_mstalt="424606"]]
1223 1223  
1224 1224  
1225 -=== 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:
1226 1226  
1242 +[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1243 +)))
1227 1227  
1245 +
1246 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1247 +
1248 +
1228 1228  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
1229 1229  
1230 1230  
1231 -=== 8.3.3 "flash read err" after upgrade firmware ===
1252 +=== 8.3.3 "flash read err" after upgrade firmware ===
1232 1232  
1254 +
1233 1233  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1234 1234  
1257 +
1235 1235  [[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1236 1236  
1237 1237  
... ... @@ -1242,23 +1242,27 @@
1242 1242   **Figure 2**
1243 1243  
1244 1244  
1245 -=== 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 ===
1246 1246  
1270 +
1247 1247  User might erase the entire flash include keys and default settings which cause this issue.
1248 1248  
1249 -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.
1250 1250  
1275 +
1251 1251  [[image:image-20221122100004-3.png||_mstalt="424242"]]
1252 1252  
1253 -Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1254 1254  
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 +
1255 1255  After AT+FDR. please set
1256 1256  
1257 -* AT+PDOP=7
1258 -* AT+FTIME=180000
1283 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1259 1259  
1260 -Example:
1285 +* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1261 1261  
1287 +**Example:**
1288 +
1262 1262  AT+PDOP=7.00
1263 1263  
1264 1264  AT+FTIME=180
... ... @@ -1276,13 +1276,6 @@
1276 1276  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1277 1277  
1278 1278  
1279 -
1280 -=== 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 ===
1281 -
1282 -
1283 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1284 -
1285 -
1286 1286  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1287 1287  
1288 1288  
... ... @@ -1305,6 +1305,38 @@
1305 1305  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
1306 1306  
1307 1307  
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 +
1308 1308  = 9.  Order Info =
1309 1309  
1310 1310  
... ... @@ -1356,3 +1356,4 @@
1356 1356  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1357 1357  
1358 1358  * [[**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