Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 147.1
edited by Edwin Chen
on 2022/11/22 20:22
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  
... ... @@ -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  
586 +* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
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.
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 -**Disable/Enable the confirmation mode**
857 +=== 3.2.10 Disable/Enable the confirmation mode ===
859 859  
859 +
860 860  * (% style="color:blue" %)**AT Command:**
861 861  
862 862  (% style="color:#037691" %)**AT+CFM=xx**
... ... @@ -874,7 +874,7 @@
874 874  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
875 875  
876 876  
877 -=== 3.2.10  Auto Send None-ACK messages ===
877 +=== 3.2.11  Auto Send None-ACK messages ===
878 878  
879 879  
880 880  TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
... ... @@ -892,10 +892,10 @@
892 892  
893 893  * (% style="color:blue" %)**Downlink Command: 0x34**
894 894  
895 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
895 +Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
896 896  
897 897  
898 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
898 +=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
899 899  
900 900  
901 901  BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
... ... @@ -910,10 +910,10 @@
910 910  
911 911  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
912 912  
913 -Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
913 +Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
914 914  
915 915  
916 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
916 +=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
917 917  
918 918  
919 919  WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456 as prefix. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
... ... @@ -928,10 +928,10 @@
928 928  
929 929  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
930 930  
931 -Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
931 +Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
932 932  
933 933  
934 -=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
934 +=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
935 935  
936 936  
937 937  Users can use this feature to enable/disable Information printing.
... ... @@ -942,7 +942,7 @@
942 942  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
943 943  
944 944  
945 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
945 +=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
946 946  
947 947  
948 948  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -957,6 +957,26 @@
957 957  Example: 0x24 01 ~/~/ Same as AT+CHE=1
958 958  
959 959  
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 +
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
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
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 ===
1230 +=== 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 -)))
1233 +**Error Output**
1216 1216  
1217 1217  
1218 -[[image:image-20221118105249-3.png||_mstalt="430664"]]
1236 +[[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 ===
1239 +(((
1240 +Some partition is missed during upgrade, please upgrade below four files as example:
1222 1222  
1242 +[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1243 +)))
1223 1223  
1245 +
1246 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1247 +
1248 +
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 ===
1252 +=== 8.3.3 "flash read err" after upgrade firmware ===
1228 1228  
1254 +
1229 1229  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1230 1230  
1257 +
1231 1231  [[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1232 1232  
1233 1233  
... ... @@ -1238,23 +1238,26 @@
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 ===
1268 +=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1242 1242  
1270 +
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.
1273 +After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1246 1246  
1275 +
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  
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 +
1251 1251  After AT+FDR. please set
1252 1252  
1253 -* AT+PDOP=7
1254 -* AT+FTIME=180000
1283 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1255 1255  
1285 +* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1256 1256  
1257 -Example:
1287 +**Example:**
1258 1258  
1259 1259  AT+PDOP=7.00
1260 1260  
... ... @@ -1273,13 +1273,6 @@
1273 1273  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1274 1274  
1275 1275  
1276 -
1277 -=== 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 ===
1278 -
1279 -
1280 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1281 -
1282 -
1283 1283  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1284 1284  
1285 1285  
... ... @@ -1293,15 +1293,47 @@
1293 1293  
1294 1294  2)  Set PDOP to a higher value.
1295 1295  
1296 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1319 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1297 1297  
1298 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1321 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1299 1299  
1300 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1323 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1301 1301  
1302 1302  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
1303 1303  
1304 1304  
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 +
1305 1305  = 9.  Order Info =
1306 1306  
1307 1307  
... ... @@ -1353,3 +1353,4 @@
1353 1353  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1354 1354  
1355 1355  * [[**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