Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)
Last modified by Xiaoling on 2023/12/27 09:15
From version 150.1
edited by Edwin Chen
on 2022/11/24 09:07
on 2022/11/24 09:07
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"]] ... ... @@ -59,11 +59,13 @@ 59 59 * EEPROM: 520 KB 60 60 * Clock Speed: 32Mhz 61 61 59 + 62 62 (% style="color:blue" %)**Common DC Characteristics:** 63 63 64 64 * Supply Voltage: 5V via USB port or Internal li-on battery 65 65 * Operating Temperature: -40 ~~ 60°C 66 66 65 + 67 67 (% style="color:blue" %)**LoRa Spec:** 68 68 69 69 * Frequency Range, ... ... @@ -85,10 +85,12 @@ 85 85 * Packet engine up to 256 bytes with CRC. 86 86 * LoRaWAN 1.0.3 Specification 87 87 87 + 88 88 (% style="color:blue" %)**Battery:** 89 89 90 90 * 1000mA Li-on Battery power (for model TrackerD) 91 91 92 + 92 92 (% style="color:blue" %)**Power Consumption** 93 93 94 94 * Sleeping Mode: 200uA ... ... @@ -95,6 +95,9 @@ 95 95 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm 96 96 * Tracking: max: 38mA 97 97 99 + 100 + 101 + 98 98 == 1.3 Features == 99 99 100 100 ... ... @@ -113,6 +113,10 @@ 113 113 * Tri-color LED, Alarm button 114 114 * Datalog 115 115 120 + 121 + 122 + 123 + 116 116 == 1.4 Applications == 117 117 118 118 ... ... @@ -119,6 +119,9 @@ 119 119 * Logistics and Supply Chain Management 120 120 * Human tracking 121 121 130 + 131 + 132 + 122 122 = 2. Use TrackerD = 123 123 124 124 == 2.1 How it works? == ... ... @@ -284,6 +284,7 @@ 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 298 + 287 287 === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 288 288 289 289 ... ... @@ -360,6 +360,9 @@ 360 360 * 3.40v ~~ 3.69v: 20% ~~ 40% 361 361 * < 3.39v: 0~~20% 362 362 375 + 376 + 377 + 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.439 +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,9 @@ 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 494 + 495 + 496 + 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,9 @@ 498 498 * (% style="color:#037691" %)**SSID: **(%%)WiFi name. 499 499 * (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 500 500 519 + 520 + 521 + 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.570 +User can set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 550 550 551 551 Example use case. 552 552 ... ... @@ -586,11 +586,11 @@ 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 589 -[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]] defines the Uplink Interval during transportation. 610 +* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation. 611 +* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic. 612 +* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion. 590 590 591 -[[TDC>>||anchor="H3.2.1SetTransmitInterval"]] defines the uplink interval when TrackerD is stactic. 592 592 593 -[[PT>>||anchor="H3.2.1SetTransmitInterval"]] defines the threldhold to detect a motion. 594 594 595 595 596 596 == 2.10 LED Status == ... ... @@ -610,6 +610,7 @@ 610 610 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 611 611 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 612 612 634 + 613 613 == 2.11 Button Function == 614 614 615 615 ... ... @@ -631,6 +631,7 @@ 631 631 |(% 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 632 632 |(% 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. 633 633 656 + 634 634 == 2.12 USB Port Function == 635 635 636 636 ... ... @@ -641,6 +641,9 @@ 641 641 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 642 642 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 643 643 667 + 668 + 669 + 644 644 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 645 645 646 646 ... ... @@ -861,7 +861,7 @@ 861 861 862 862 863 863 864 -=== 3.2.10 Disable/Enable the confirmation mode === 890 +=== 3.2.10 Disable/Enable the confirmation mode === 865 865 866 866 * (% style="color:blue" %)**AT Command:** 867 867 ... ... @@ -963,6 +963,26 @@ 963 963 Example: 0x24 01 ~/~/ Same as AT+CHE=1 964 964 965 965 992 +=== 3.2.16 Get or Set Threshold for motion detect(Since firmware 1.4.3) === 993 + 994 +User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event. 995 + 996 +(% style="color:blue" %)**AT Command:** 997 + 998 +(% style="color:#037691" %)**AT+PT=xx** 999 + 1000 + Example: 1001 + 1002 + AT+PT=14 ~-~-> Set to detect car motion. 1003 + 1004 + AT+PT=41 ~-~-> set to detect walk motion. 1005 + 1006 + 1007 +(% style="color:blue" %)**Downlink Payload:0xB4**(%%) 1008 +0xB4 14 ~/~/ Same as AT+PT=14 1009 + 1010 + 1011 + 966 966 = 4. Setting for Different Scenarios = 967 967 968 968 ... ... @@ -1111,6 +1111,7 @@ 1111 1111 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 1112 1112 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 1113 1113 1160 + 1114 1114 == 7.3 Notes on using different serial port tools for TrackerD == 1115 1115 1116 1116 === 7.3.1 Serial port utility === ... ... @@ -1213,24 +1213,26 @@ 1213 1213 1214 1214 == 8.3 Problem after Upgrading Firmware == 1215 1215 1216 -=== 8.3.1 Continue Restart after upgrading === 1263 +=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading === 1217 1217 1265 +Error Output 1218 1218 1267 +[[image:image-20221122100004-4.png||_mstalt="424606"]] 1268 + 1219 1219 ((( 1220 -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 1270 +Some partition is missed during upgrade, please upgrade below four files as example: 1271 + 1272 +[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]] 1221 1221 ))) 1222 1222 1223 1223 1224 - [[image:image-20221118105249-3.png||_mstalt="430664"]]1276 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1225 1225 1226 1226 1227 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1228 - 1229 - 1230 1230 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 1231 1231 1232 1232 1233 -=== 8.3.3 "flash read err" after upgrade firmware === 1282 +=== 8.3.3 "flash read err" after upgrade firmware === 1234 1234 1235 1235 Error shows below, user might erase the entire flash include u-boot partition which cause this issue. 1236 1236 ... ... @@ -1244,7 +1244,7 @@ 1244 1244 **Figure 2** 1245 1245 1246 1246 1247 -=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware === 1296 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware === 1248 1248 1249 1249 User might erase the entire flash include keys and default settings which cause this issue. 1250 1250 ... ... @@ -1252,11 +1252,12 @@ 1252 1252 1253 1253 [[image:image-20221122100004-3.png||_mstalt="424242"]] 1254 1254 1255 -Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label. 1304 +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. 1256 1256 1257 1257 After AT+FDR. please set 1258 1258 1259 1259 * AT+PDOP=7 1309 + 1260 1260 * AT+FTIME=180000 1261 1261 1262 1262 Example: ... ... @@ -1278,13 +1278,6 @@ 1278 1278 AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA) 1279 1279 1280 1280 1281 - 1282 -=== 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 === 1283 - 1284 - 1285 -[[image:image-20221122100004-4.png||_mstalt="424606"]] 1286 - 1287 - 1288 1288 == 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1289 1289 1290 1290 ... ... @@ -1328,6 +1328,9 @@ 1328 1328 1329 1329 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1330 1330 1374 + 1375 + 1376 + 1331 1331 = 10. Packing Info = 1332 1332 1333 1333 ... ... @@ -1343,6 +1343,9 @@ 1343 1343 1344 1344 * Weight: 50g 1345 1345 1392 + 1393 + 1394 + 1346 1346 = 11. Support = 1347 1347 1348 1348 ... ... @@ -1350,6 +1350,9 @@ 1350 1350 1351 1351 * 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]]. 1352 1352 1402 + 1403 + 1404 + 1353 1353 = 12. Reference = 1354 1354 1355 1355