Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)
Last modified by Xiaoling on 2023/12/27 09:15
From version 147.1
edited by Edwin Chen
on 2022/11/22 20:22
on 2022/11/22 20:22
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.Xiaoling - 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"]] ... ... @@ -95,6 +95,8 @@ 95 95 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm 96 96 * Tracking: max: 38mA 97 97 95 + 96 + 98 98 == 1.3 Features == 99 99 100 100 ... ... @@ -113,6 +113,8 @@ 113 113 * Tri-color LED, Alarm button 114 114 * Datalog 115 115 115 + 116 + 116 116 == 1.4 Applications == 117 117 118 118 ... ... @@ -119,6 +119,8 @@ 119 119 * Logistics and Supply Chain Management 120 120 * Human tracking 121 121 123 + 124 + 122 122 = 2. Use TrackerD = 123 123 124 124 == 2.1 How it works? == ... ... @@ -284,6 +284,8 @@ 284 284 |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit 285 285 |=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]] 286 286 290 + 291 + 287 287 === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 288 288 289 289 ... ... @@ -360,6 +360,8 @@ 360 360 * 3.40v ~~ 3.69v: 20% ~~ 40% 361 361 * < 3.39v: 0~~20% 362 362 368 + 369 + 363 363 ==== (% style="color:blue" %)**MOD:**(%%) ==== 364 364 365 365 **Example: ** (0x60>>6) & 0x3f =1 ... ... @@ -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.431 +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:** ... ... @@ -476,6 +476,8 @@ 476 476 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 477 477 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 478 478 486 + 487 + 479 479 === 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 480 480 481 481 ... ... @@ -498,6 +498,8 @@ 498 498 * (% style="color:#037691" %)**SSID: **(%%)WiFi name. 499 499 * (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 500 500 510 + 511 + 501 501 === 2.4.7 Add Payload format in TTN V3 === 502 502 503 503 ... ... @@ -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.560 +User can set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 550 550 551 551 Example use case. 552 552 ... ... @@ -586,7 +586,12 @@ 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 600 +* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation. 601 +* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic. 602 +* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion. 589 589 604 + 605 + 590 590 == 2.10 LED Status == 591 591 592 592 ... ... @@ -604,6 +604,8 @@ 604 604 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 605 605 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 606 606 623 + 624 + 607 607 == 2.11 Button Function == 608 608 609 609 ... ... @@ -625,6 +625,8 @@ 625 625 |(% style="width:135px" %)Exit Alarm Mode|(% style="width:220px" %)Fast press the (% style="color:red" %)**RED** (%%)button 10 times|(% style="width:265px" %)Exit Alarm Mode 626 626 |(% style="width:135px" %)Enter Deep Sleep Mode|(% style="width:220px" %)Press and hold the button for 10 seconds, then quickly press the device 3 times to enter deep sleep|(% style="width:265px" %)This is the mode ship out from factory. CPU will be complete in sleep mode and no LoRa activity, only use before deploy. 627 627 646 + 647 + 628 628 == 2.12 USB Port Function == 629 629 630 630 ... ... @@ -635,6 +635,8 @@ 635 635 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 636 636 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 637 637 658 + 659 + 638 638 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 639 639 640 640 ... ... @@ -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**879 +=== 3.2.10 Disable/Enable the confirmation mode === 859 859 881 + 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.1 0899 +=== 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 917 +Example: 0x34 01 ~/~/ Same as AT+PNACKMD=1 896 896 897 897 898 -=== 3.2.1 1Set BLEMASK to filter BLE iBeacon ===920 +=== 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 935 +Example: 0xB2 01 02 03 04 05 06 ~/~/ Set BLEMASK to 123456 914 914 915 915 916 -=== 3.2.1 2Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) ===938 +=== 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 953 +Example: 0xB3 01 02 03 04 05 06 ~/~/ Set WiFiMASK to 123456 932 932 933 933 934 -=== 3.2.1 3956 +=== 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.1 4Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) ===967 +=== 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 982 +=== 3.2.16 Get or Set Threshold for motion detect(Since firmware 1.4.3) === 983 + 984 +User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event. 985 + 986 +(% style="color:blue" %)**AT Command:** 987 + 988 +(% style="color:#037691" %)**AT+PT=xx** 989 + 990 + Example: 991 + 992 + AT+PT=14 ~-~-> Set to detect car motion. 993 + 994 + AT+PT=41 ~-~-> set to detect walk motion. 995 + 996 + 997 +(% style="color:blue" %)**Downlink Payload:0xB4**(%%) 998 +0xB4 14 ~/~/ Same as AT+PT=14 999 + 1000 + 1001 + 960 960 = 4. Setting for Different Scenarios = 961 961 962 962 ... ... @@ -1105,6 +1105,8 @@ 1105 1105 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 1106 1106 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 1107 1107 1150 + 1151 + 1108 1108 == 7.3 Notes on using different serial port tools for TrackerD == 1109 1109 1110 1110 === 7.3.1 Serial port utility === ... ... @@ -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 1240 +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 === 1254 +=== 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 -))) 1257 +**Error Output** 1216 1216 1217 1217 1218 -[[image:image-2022111 8105249-3.png||_mstalt="430664"]]1260 +[[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 === 1263 +((( 1264 +Some partition is missed during upgrade, please upgrade below four files as example: 1222 1222 1266 +[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]] 1267 +))) 1223 1223 1269 + 1270 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1271 + 1272 + 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 === 1276 +=== 8.3.3 "flash read err" after upgrade firmware === 1228 1228 1278 + 1229 1229 Error shows below, user might erase the entire flash include u-boot partition which cause this issue. 1230 1230 1281 + 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 ===1292 +=== 8.3.4 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware === 1242 1242 1294 + 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. 1297 +After the upgrade is completed, enter **AT+CFG** as shown in the figure below. 1246 1246 1299 + 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 1303 +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. 1304 + 1251 1251 After AT+FDR. please set 1252 1252 1253 -* AT+PDOP=7 1254 -* AT+FTIME=180000 1307 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7** 1255 1255 1309 +* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000** 1256 1256 1257 -Example: 1311 +**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,11 +1293,11 @@ 1293 1293 1294 1294 2) Set PDOP to a higher value. 1295 1295 1296 -* 1343 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.) 1297 1297 1298 -* 1345 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces) 1299 1299 1300 -* 1347 +* (% _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 ... ... @@ -1323,6 +1323,8 @@ 1323 1323 1324 1324 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1325 1325 1373 + 1374 + 1326 1326 = 10. Packing Info = 1327 1327 1328 1328 ... ... @@ -1338,6 +1338,8 @@ 1338 1338 1339 1339 * Weight: 50g 1340 1340 1390 + 1391 + 1341 1341 = 11. Support = 1342 1342 1343 1343 ... ... @@ -1345,6 +1345,8 @@ 1345 1345 1346 1346 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]. 1347 1347 1399 + 1400 + 1348 1348 = 12. Reference = 1349 1349 1350 1350 ... ... @@ -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]] 1409 +)))