Skip to Content
Last modified by Xiaoling on 2025/04/27 16:48
From version 173.1
edited by Bei Jinggeng
on 2022/12/07 13:40
Change comment: There is no comment for this version
To version 145.1
edited by Edwin Chen
on 2022/11/22 12:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Edwin
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:1664505654417-133.png||_mstalt="293696"]]
2 +[[image:1664505654417-133.png]]
3 3  
4 4  
5 5  
... ... @@ -31,12 +31,15 @@
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 -[[image:1664499921684-770.png||_mstalt="298194"]]
42 +[[image:1664499921684-770.png]]
40 40  
41 41  
42 42  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
... ... @@ -92,7 +92,6 @@
92 92  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
93 93  * Tracking: max: 38mA
94 94  
95 -
96 96  == 1.3  Features ==
97 97  
98 98  
... ... @@ -111,7 +111,6 @@
111 111  * Tri-color LED, Alarm button
112 112  * Datalog
113 113  
114 -
115 115  == 1.4  Applications ==
116 116  
117 117  
... ... @@ -118,7 +118,6 @@
118 118  * Logistics and Supply Chain Management
119 119  * Human tracking
120 120  
121 -
122 122  = 2.  Use TrackerD =
123 123  
124 124  == 2.1 How it works? ==
... ... @@ -133,7 +133,7 @@
133 133  Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example. 
134 134  
135 135  
136 -[[image:1664501652064-326.png||_mstalt="293306"]]
136 +[[image:1664501652064-326.png]]
137 137  
138 138  
139 139  
... ... @@ -145,7 +145,7 @@
145 145  Each TrackerD is shipped with a sticker with the default device EUI as below:
146 146  
147 147  
148 -[[image:1664501677253-891.png||_mstalt="296569"]]
148 +[[image:1664501677253-891.png]]
149 149  
150 150  
151 151  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -154,14 +154,14 @@
154 154  **__Add APP EUI in the application:__**
155 155  
156 156  
157 -[[image:1664501711466-918.png||_mstalt="295828"]]
157 +[[image:1664501711466-918.png]]
158 158  
159 159  
160 160  
161 -[[image:1664501721248-725.png||_mstalt="294450"]]
161 +[[image:1664501721248-725.png]]
162 162  
163 163  
164 -[[image:1664501734705-405.png||_mstalt="293306"]]
164 +[[image:1664501734705-405.png]]
165 165  
166 166  
167 167  
... ... @@ -168,15 +168,15 @@
168 168  **__Add APP KEY and DEV EUI:__**
169 169  
170 170  
171 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]]
171 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]]
172 172  
173 173  
174 174  
175 175  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
176 176  
177 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
177 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
178 178  
179 -[[image:1664502835802-546.png||_mstalt="295061"]]
179 +[[image:1664502835802-546.png]]
180 180  
181 181  
182 182  (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
... ... @@ -208,7 +208,7 @@
208 208  |=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1
209 209  |=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
210 210  
211 -[[image:1665301570342-765.png||_mstalt="294580"]]
211 +[[image:1665301570342-765.png]]
212 212  
213 213  
214 214  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -275,7 +275,7 @@
275 275  
276 276  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
277 277  
278 -(% _mstmutation="1" style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
278 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
279 279  
280 280  
281 281  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -302,7 +302,7 @@
302 302  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
303 303  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
304 304  
305 -[[image:1665301636888-168.png||_mstalt="298012"]]
305 +[[image:1665301636888-168.png]]
306 306  
307 307  
308 308  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -332,12 +332,12 @@
332 332  2.  In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
333 333  
334 334  
335 -[[image:1664502116362-706.png||_mstalt="293306"]]
335 +[[image:1664502116362-706.png]]
336 336  
337 337  
338 338  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
339 339  
340 -[[image:1664502166010-515.png||_mstalt="291395"]]
340 +[[image:1664502166010-515.png]]
341 341  
342 342  
343 343  
... ... @@ -360,7 +360,6 @@
360 360  * 3.40v ~~ 3.69v:  20% ~~ 40%
361 361  * < 3.39v:  0~~20%
362 362  
363 -
364 364  ==== (% style="color:blue" %)**MOD:**(%%) ====
365 365  
366 366  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -416,13 +416,13 @@
416 416  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
417 417  
418 418  (% class="wikigeneratedid" %)
419 -[[image:1665301687277-443.png||_mstalt="296140"]]
418 +[[image:1665301687277-443.png]]
420 420  
421 421  
422 422  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
423 423  
424 424  
425 -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.
426 426  
427 427  
428 428  (% style="color:red" %)**Note for this mode:**
... ... @@ -439,7 +439,7 @@
439 439  )))|4|4|2|1|1|1|1|1
440 440  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
441 441  
442 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
441 +[[image:image-20221009160309-2.png]]
443 443  
444 444  
445 445  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
... ... @@ -466,7 +466,7 @@
466 466  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
467 467  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
468 468  
469 -[[image:1664502425687-834.png||_mstalt="296738"]]
468 +[[image:1664502425687-834.png]]
470 470  
471 471  
472 472  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -477,7 +477,6 @@
477 477  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
478 478  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
479 479  
480 -
481 481  === 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
482 482  
483 483  
... ... @@ -493,7 +493,7 @@
493 493  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
494 494  
495 495  (% class="wikigeneratedid" %)
496 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
494 +[[image:1667288597595-714.png||height="212" width="1151"]]
497 497  
498 498  
499 499  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -500,7 +500,6 @@
500 500  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
501 501  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
502 502  
503 -
504 504  === 2.4.7  Add Payload format in TTN V3 ===
505 505  
506 506  
... ... @@ -509,7 +509,7 @@
509 509  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
510 510  
511 511  
512 -[[image:1664502649601-895.png||_mstalt="296985"]]
509 +[[image:1664502649601-895.png]]
513 513  
514 514  
515 515  
... ... @@ -519,7 +519,7 @@
519 519  
520 520  Save the change the uplink message will be parsed. As below:
521 521  
522 -[[image:1664502676891-606.png||_mstalt="296673"]]
519 +[[image:1664502676891-606.png]]
523 523  
524 524  
525 525  == 2.5 Integrate with Datacake ==
... ... @@ -530,7 +530,7 @@
530 530  Instruction is here:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example~~-~~-AddTrackerDGPSTrackingInDataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example--AddTrackerDGPSTrackingInDataCake]]
531 531  
532 532  
533 -[[image:1664502695771-538.png||_mstalt="297349"]]
530 +[[image:1664502695771-538.png]]
534 534  
535 535  
536 536  == 2.6 Integrate with Tago ==
... ... @@ -541,7 +541,7 @@
541 541  Instruction is here: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget]]
542 542  
543 543  
544 -[[image:1664502715371-321.png||_mstalt="292162"]]
541 +[[image:1664502715371-321.png]]
545 545  
546 546  
547 547  == 2.7  Datalog Feature ==
... ... @@ -549,14 +549,14 @@
549 549  
550 550  total 273 entries,by default,
551 551  
552 -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.
553 553  
554 554  Example use case.
555 555  
556 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
553 +[[image:image-20221009234703-2.png||height="328" width="899"]]
557 557  
558 558  
559 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
556 +[[image:image-20221009234629-1.png||height="390" width="577"]]
560 560  
561 561  
562 562  == 2.8 Alarm Mode ==
... ... @@ -589,11 +589,7 @@
589 589  
590 590  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.
591 591  
592 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
593 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
594 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
595 595  
596 -
597 597  == 2.10 LED Status ==
598 598  
599 599  
... ... @@ -611,13 +611,12 @@
611 611  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
612 612  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
613 613  
614 -
615 615  == 2.11 Button Function ==
616 616  
617 617  
618 618  (% style="color:blue" %)**RESET button:**
619 619  
620 -[[image:1664502835802-546.png||_mstalt="295061"]]
612 +[[image:1664502835802-546.png]]
621 621  
622 622  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
623 623  
... ... @@ -624,7 +624,7 @@
624 624  
625 625  (% style="color:red" %)**RED button:**
626 626  
627 -[[image:1664502854406-763.png||_mstalt="295568"]]
619 +[[image:1664502854406-763.png]]
628 628  
629 629  
630 630  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -633,7 +633,6 @@
633 633  |(% 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
634 634  |(% 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.
635 635  
636 -
637 637  == 2.12 USB Port Function ==
638 638  
639 639  
... ... @@ -644,7 +644,6 @@
644 644  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
645 645  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
646 646  
647 -
648 648  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
649 649  
650 650  
... ... @@ -659,21 +659,22 @@
659 659  TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below.
660 660  
661 661  
662 -[[image:1664502999401-486.png||_mstalt="296985"]]
652 +[[image:1664502999401-486.png]]
663 663  
664 664  
665 665  In PC, User needs to set serial tool baud rate to (% style="color:green" %)**115200**(%%) to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands:
666 666  
667 667  
668 -[[image:1664503022490-662.png||_mstalt="293332"]]
658 +[[image:1664503022490-662.png]]
669 669  
670 670  
671 -[[image:1664503035713-500.png||_mstalt="291096"]]
661 +[[image:1664503035713-500.png]]
672 672  
673 673  
674 -[[image:1664503047675-651.png||_mstalt="295386"]]
664 +[[image:1664503047675-651.png]]
675 675  
676 676  
667 +
677 677  == 3.2 Command Set ==
678 678  
679 679  === 3.2.1 Set Transmit Interval ===
... ... @@ -799,9 +799,9 @@
799 799  
800 800  (% style="color:#037691" %)**cc:   **
801 801  
802 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
793 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
803 803  
804 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
795 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
805 805  
806 806  (% style="color:blue" %)**Example:**
807 807  
... ... @@ -864,9 +864,8 @@
864 864  
865 865  
866 866  
867 -=== 3.2.10 Disable/Enable the confirmation mode ===
858 +**Disable/Enable the confirmation mode**
868 868  
869 -
870 870  * (% style="color:blue" %)**AT Command:**
871 871  
872 872  (% style="color:#037691" %)**AT+CFM=xx**
... ... @@ -884,7 +884,7 @@
884 884  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
885 885  
886 886  
887 -=== 3.2.11  Auto Send None-ACK messages ===
877 +=== 3.2.10  Auto Send None-ACK messages ===
888 888  
889 889  
890 890  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.
... ... @@ -902,10 +902,10 @@
902 902  
903 903  * (% style="color:blue" %)**Downlink Command: 0x34**
904 904  
905 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
895 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
906 906  
907 907  
908 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
898 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
909 909  
910 910  
911 911  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.
... ... @@ -914,16 +914,16 @@
914 914  
915 915  (% style="color:blue" %)**AT Command:**
916 916  
917 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
907 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
918 918  
919 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
909 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
920 920  
921 921  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
922 922  
923 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
913 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
924 924  
925 925  
926 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
916 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
927 927  
928 928  
929 929  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.
... ... @@ -932,16 +932,16 @@
932 932  
933 933  (% style="color:blue" %)**AT Command:**
934 934  
935 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
925 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
936 936  
937 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
927 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
938 938  
939 939  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
940 940  
941 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
931 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
942 942  
943 943  
944 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
934 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
945 945  
946 946  
947 947  Users can use this feature to enable/disable Information printing.
... ... @@ -948,11 +948,11 @@
948 948  
949 949  (% style="color:blue" %)**AT Command:**
950 950  
951 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
941 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
952 952  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
953 953  
954 954  
955 -=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
945 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
956 956  
957 957  
958 958  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -959,34 +959,14 @@
959 959  
960 960  (% style="color:blue" %)**AT Command:**
961 961  
962 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
952 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
963 963  
964 964  
965 965  (% style="color:blue" %)**Downlink Payload:0X24**
966 966  
967 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
957 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
968 968  
969 969  
970 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
971 -
972 -
973 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
974 -
975 -(% style="color:blue" %)**AT Command:**
976 -
977 -(% style="color:#037691" %)**AT+PT=xx**
978 -
979 - Example:
980 -
981 - AT+PT=14    ~-~->    Set to detect car motion.
982 -
983 - AT+PT=41  ~-~->    set to detect walk motion.
984 -
985 -
986 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
987 -0xB4 14          ~/~/  Same as AT+PT=14
988 -
989 -
990 990  = 4. Setting for Different Scenarios =
991 991  
992 992  
... ... @@ -1019,10 +1019,10 @@
1019 1019  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1020 1020  
1021 1021  
1022 -[[image:1664503563660-578.png||_mstalt="296777"]]
992 +[[image:1664503563660-578.png]]
1023 1023  
1024 1024  
1025 -[[image:1664503574618-659.png||_mstalt="297986"]]
995 +[[image:1664503574618-659.png]]
1026 1026  
1027 1027  
1028 1028  
... ... @@ -1038,13 +1038,13 @@
1038 1038  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1039 1039  
1040 1040  
1041 -[[image:image-20221207120501-1.png]]
1011 +[[image:image-20221118105220-2.png]]
1042 1042  
1043 1043  
1044 1044  
1045 1045  After upgrade finish, it will show finish as below:
1046 1046  
1047 -[[image:image-20221207133911-7.png]]
1017 +[[image:image-20221118105402-4.png]]
1048 1048  
1049 1049  
1050 1050  
... ... @@ -1060,23 +1060,23 @@
1060 1060  Install IDE on PC, open and click (% style="color:#037691" %)**File ~-~-> Preference**,(%%) add the following URL:  [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fdl.espressif.com%2Fdl%2Fpackage_esp32_index.json]]
1061 1061  
1062 1062  
1063 -[[image:1664503635019-941.png||_mstalt="294658"]]
1033 +[[image:1664503635019-941.png]]
1064 1064  
1065 1065  
1066 1066  
1067 1067  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1068 1068  
1069 -[[image:1664503715811-892.png||_mstalt="295698"]]
1039 +[[image:1664503715811-892.png]]
1070 1070  
1071 1071  
1072 1072  (% id="cke_bm_4554S" style="display:none" %) (%%)Find the path of SP32 installation, find the file as shown in Figure 1, and change the SPI pin to the shown in Figure 2.
1073 1073  
1074 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1044 +[[image:image-20221024105643-1.png]]
1075 1075  
1076 1076  **~ Figure1**
1077 1077  
1078 1078  
1079 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1049 +[[image:image-20221024105643-2.png]]
1080 1080  
1081 1081   **Figure2**
1082 1082  
... ... @@ -1086,7 +1086,7 @@
1086 1086  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1087 1087  
1088 1088  
1089 -[[image:1664503752288-974.png||_mstalt="298194"]]
1059 +[[image:1664503752288-974.png]]
1090 1090  
1091 1091  
1092 1092  == 6.2 Source Code ==
... ... @@ -1094,19 +1094,19 @@
1094 1094  
1095 1095  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1096 1096  
1097 -[[image:1664503794261-827.png||_mstalt="296387"]]
1067 +[[image:1664503794261-827.png]]
1098 1098  
1099 1099  
1100 1100  
1101 1101  * (% style="color:blue" %)**Click to upload**
1102 1102  
1103 -[[image:1664503808294-336.png||_mstalt="295711"]]
1073 +[[image:1664503808294-336.png]]
1104 1104  
1105 1105  
1106 1106  
1107 1107  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1108 1108  
1109 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1079 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1110 1110  
1111 1111  
1112 1112  = 7.  FAQ =
... ... @@ -1120,7 +1120,7 @@
1120 1120  == 7.2 What is the pin mapping for the USB program cable? ==
1121 1121  
1122 1122  
1123 -[[image:1664499635206-262.png||_mstalt="295360"]]
1093 +[[image:1664499635206-262.png]]
1124 1124  
1125 1125  
1126 1126  
... ... @@ -1135,7 +1135,6 @@
1135 1135  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1136 1136  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1137 1137  
1138 -
1139 1139  == 7.3 Notes on using different serial port tools for TrackerD ==
1140 1140  
1141 1141  === 7.3.1  Serial port utility ===
... ... @@ -1146,13 +1146,13 @@
1146 1146  Need to adjust the data stream to RTS/CTS on physical restart.
1147 1147  
1148 1148  (% class="wikigeneratedid" %)
1149 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1118 +[[image:image-20221102140621-1.png]]
1150 1150  
1151 1151  
1152 1152  
1153 1153  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1154 1154  
1155 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1124 +[[image:image-20221102140638-2.png]]
1156 1156  
1157 1157  
1158 1158  === 7.3.2  SecureCRT ===
... ... @@ -1161,22 +1161,22 @@
1161 1161  The default command window of SecureCRT is not displayed. Entering a command requires a complete input of the entire command. You can open the command window in the view.
1162 1162  
1163 1163  
1164 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1133 +[[image:image-20221102140704-3.png]]
1165 1165  
1166 1166  
1167 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1136 +[[image:image-20221102140712-4.png]]
1168 1168  
1169 1169  
1170 1170  === 7.3.3  PUTTY ===
1171 1171  
1172 1172  
1173 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1142 +[[image:image-20221102140748-5.png]]
1174 1174  
1175 1175  
1176 1176  Since putty does not have a command window, you need to fill in the complete command externally, and then copy it to putty.The information copied outside can be pasted by right-clicking the mouse in putty.
1177 1177  
1178 1178  
1179 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1148 +[[image:image-20221102140801-6.png]]
1180 1180  
1181 1181  
1182 1182  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1191,7 +1191,7 @@
1191 1191  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1192 1192  
1193 1193  
1194 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1163 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1195 1195  
1196 1196  
1197 1197  
... ... @@ -1198,7 +1198,7 @@
1198 1198  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1199 1199  
1200 1200  
1201 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1170 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1202 1202  
1203 1203  
1204 1204  
... ... @@ -1205,7 +1205,7 @@
1205 1205  **3. Compile the AS923_JP band, please refer to the intention shown**
1206 1206  
1207 1207  
1208 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1177 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1209 1209  
1210 1210  
1211 1211  
... ... @@ -1212,10 +1212,10 @@
1212 1212  **4. In other frequency bands in AS923, you need to find Lorabase_as923.H, path arduino-lmic \ src \ lmic, as shown in the figure below.**
1213 1213  
1214 1214  
1215 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1184 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1216 1216  
1217 1217  
1218 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1187 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1219 1219  
1220 1220  
1221 1221  = 8  Trouble Shooting =
... ... @@ -1224,7 +1224,7 @@
1224 1224  
1225 1225  
1226 1226  (((
1227 -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
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
1228 1228  )))
1229 1229  
1230 1230  
... ... @@ -1238,69 +1238,50 @@
1238 1238  
1239 1239  == 8.3  Problem after Upgrading Firmware ==
1240 1240  
1241 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1210 +=== 8.3.1 Continue Restart after upgrading ===
1242 1242  
1243 1243  
1244 -**Error Output**
1245 -
1246 -
1247 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1248 -
1249 -
1250 1250  (((
1251 -Some partition is missed during upgrade, please upgrade below four files as example:
1252 -
1253 -[[image:image-20221207120524-2.png]]
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
1254 1254  )))
1255 1255  
1256 1256  
1257 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1218 +[[image:image-20221118105249-3.png]]
1258 1258  
1259 1259  
1260 -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
1221 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1261 1261  
1262 1262  
1263 -=== 8.3.3 "flash read err" after upgrade firmware ===
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
1264 1264  
1265 1265  
1227 +=== 8.3.3 "flash read err" after upgrade firmware ===
1228 +
1266 1266  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1267 1267  
1231 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1268 1268  
1269 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1270 1270  
1271 -
1272 1272  User need to upgrade again with below four files to solve this issue.
1273 1273  
1274 - [[image:image-20221207120530-3.png]]
1236 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1275 1275  
1276 1276   **Figure 2**
1277 1277  
1278 1278  
1279 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1241 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1280 1280  
1281 -
1282 1282  User might erase the entire flash include keys and default settings which cause this issue.
1283 1283  
1284 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1245 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1285 1285  
1247 +[[image:image-20221122100004-3.png]]
1286 1286  
1287 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1249 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1288 1288  
1289 1289  
1290 -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.
1252 +Example:
1291 1291  
1292 -After AT+FDR. please set
1293 -
1294 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1295 -
1296 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1297 -
1298 -**Example:**
1299 -
1300 -AT+PDOP=7.00
1301 -
1302 -AT+FTIME=180
1303 -
1304 1304  AT+DEUI=70B3D57ED0053981  
1305 1305  
1306 1306  AT+APPEUI=D23345667BCBCCAF
... ... @@ -1314,6 +1314,13 @@
1314 1314  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1315 1315  
1316 1316  
1267 +
1268 +=== 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 ===
1269 +
1270 +
1271 +[[image:image-20221122100004-4.png]]
1272 +
1273 +
1317 1317  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1318 1318  
1319 1319  
... ... @@ -1327,53 +1327,15 @@
1327 1327  
1328 1328  2)  Set PDOP to a higher value.
1329 1329  
1330 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1287 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1331 1331  
1332 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1289 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1333 1333  
1334 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1291 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1335 1335  
1336 1336  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
1337 1337  
1338 1338  
1339 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1340 -
1341 -
1342 -When upgrading, use the erase button to upgrade
1343 -
1344 -[[image:image-20221207120536-4.png]]
1345 -
1346 -
1347 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1348 -
1349 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1350 -
1351 -
1352 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1353 -
1354 -[[image:image-20221207134028-8.png]]
1355 -
1356 -
1357 -Reboot information after upgrade
1358 -
1359 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1360 -
1361 -
1362 -Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal
1363 -
1364 -[[image:image-20221128111850-5.png]]
1365 -
1366 -
1367 -After the parameters return to normal, upgrade to the version you need again
1368 -
1369 -[[image:image-20221207120601-5.png]]
1370 -
1371 -
1372 -At this point, the parameters return to normal after running AT+FDR again
1373 -
1374 -[[image:image-20221128112035-7.png]]
1375 -
1376 -
1377 1377  = 9.  Order Info =
1378 1378  
1379 1379  
... ... @@ -1395,7 +1395,6 @@
1395 1395  
1396 1396  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1397 1397  
1398 -
1399 1399  = 10.  Packing Info =
1400 1400  
1401 1401  
... ... @@ -1411,7 +1411,6 @@
1411 1411  
1412 1412  * Weight: 50g
1413 1413  
1414 -
1415 1415  = 11. Support =
1416 1416  
1417 1417  
... ... @@ -1419,7 +1419,6 @@
1419 1419  
1420 1420  * 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]].
1421 1421  
1422 -
1423 1423  = 12.  Reference =
1424 1424  
1425 1425  
... ... @@ -1428,4 +1428,3 @@
1428 1428  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1429 1429  
1430 1430  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1431 -)))
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
image-20221207120501-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120524-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120530-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120536-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120601-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207133836-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.1 KB
Content
image-20221207133911-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -46.3 KB
Content
image-20221207134028-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.3 KB
Content