Skip to Content
Last modified by Bei Jinggeng on 2025/07/23 11:03
From version 187.2
edited by Xiaoling
on 2022/12/21 16:01
Change comment: There is no comment for this version
To version 143.2
edited by Xiaoling
on 2022/11/22 10:54
Change comment: There is no comment for this version

Summary

Details

Page properties
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  
... ... @@ -12,7 +12,6 @@
12 12  
13 13  
14 14  
15 -
16 16  = 1.  Introduction =
17 17  
18 18  == 1.1  What is TrackerD ==
... ... @@ -32,12 +32,15 @@
32 32  (((
33 33  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.
34 34  )))
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 +
38 38  )))
39 39  
40 -[[image:1664499921684-770.png||_mstalt="298194"]]
42 +[[image:1664499921684-770.png]]
41 41  
42 42  
43 43  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
... ... @@ -137,7 +137,7 @@
137 137  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. 
138 138  
139 139  
140 -[[image:1664501652064-326.png||_mstalt="293306"]]
142 +[[image:1664501652064-326.png]]
141 141  
142 142  
143 143  
... ... @@ -149,7 +149,7 @@
149 149  Each TrackerD is shipped with a sticker with the default device EUI as below:
150 150  
151 151  
152 -[[image:1664501677253-891.png||_mstalt="296569"]]
154 +[[image:1664501677253-891.png]]
153 153  
154 154  
155 155  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -158,14 +158,14 @@
158 158  **__Add APP EUI in the application:__**
159 159  
160 160  
161 -[[image:1664501711466-918.png||_mstalt="295828"]]
163 +[[image:1664501711466-918.png]]
162 162  
163 163  
164 164  
165 -[[image:1664501721248-725.png||_mstalt="294450"]]
167 +[[image:1664501721248-725.png]]
166 166  
167 167  
168 -[[image:1664501734705-405.png||_mstalt="293306"]]
170 +[[image:1664501734705-405.png]]
169 169  
170 170  
171 171  
... ... @@ -172,15 +172,15 @@
172 172  **__Add APP KEY and DEV EUI:__**
173 173  
174 174  
175 -[[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"]]
177 +[[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"]]
176 176  
177 177  
178 178  
179 179  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
180 180  
181 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
183 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
182 182  
183 -[[image:1664502835802-546.png||_mstalt="295061"]]
185 +[[image:1664502835802-546.png]]
184 184  
185 185  
186 186  (% 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.
... ... @@ -212,7 +212,7 @@
212 212  |=(% 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
213 213  |=(% 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
214 214  
215 -[[image:1665301570342-765.png||_mstalt="294580"]]
217 +[[image:1665301570342-765.png]]
216 216  
217 217  
218 218  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -279,7 +279,7 @@
279 279  
280 280  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
281 281  
282 -(% _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)(%%)  
284 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
283 283  
284 284  
285 285  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -308,7 +308,7 @@
308 308  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
309 309  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
310 310  
311 -[[image:1665301636888-168.png||_mstalt="298012"]]
313 +[[image:1665301636888-168.png]]
312 312  
313 313  
314 314  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -317,6 +317,8 @@
317 317  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
318 318  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
319 319  
322 +
323 +
320 320  ==== (% style="color:blue" %)**FLAG:**(%%) ====
321 321  
322 322  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
... ... @@ -338,12 +338,12 @@
338 338  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:
339 339  
340 340  
341 -[[image:1664502116362-706.png||_mstalt="293306"]]
345 +[[image:1664502116362-706.png]]
342 342  
343 343  
344 344  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
345 345  
346 -[[image:1664502166010-515.png||_mstalt="291395"]]
350 +[[image:1664502166010-515.png]]
347 347  
348 348  
349 349  
... ... @@ -423,13 +423,13 @@
423 423  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
424 424  
425 425  (% class="wikigeneratedid" %)
426 -[[image:1665301687277-443.png||_mstalt="296140"]]
430 +[[image:1665301687277-443.png]]
427 427  
428 428  
429 429  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
430 430  
431 431  
432 -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.
436 +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.
433 433  
434 434  
435 435  (% style="color:red" %)**Note for this mode:**
... ... @@ -446,7 +446,7 @@
446 446  )))|4|4|2|1|1|1|1|1
447 447  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
448 448  
449 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
453 +[[image:image-20221009160309-2.png]]
450 450  
451 451  
452 452  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
... ... @@ -473,7 +473,7 @@
473 473  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
474 474  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
475 475  
476 -[[image:1664502425687-834.png||_mstalt="296738"]]
480 +[[image:1664502425687-834.png]]
477 477  
478 478  
479 479  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -501,7 +501,7 @@
501 501  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
502 502  
503 503  (% class="wikigeneratedid" %)
504 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
508 +[[image:1667288597595-714.png||height="212" width="1151"]]
505 505  
506 506  
507 507  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -518,7 +518,7 @@
518 518  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
519 519  
520 520  
521 -[[image:1664502649601-895.png||_mstalt="296985"]]
525 +[[image:1664502649601-895.png]]
522 522  
523 523  
524 524  
... ... @@ -528,7 +528,7 @@
528 528  
529 529  Save the change the uplink message will be parsed. As below:
530 530  
531 -[[image:1664502676891-606.png||_mstalt="296673"]]
535 +[[image:1664502676891-606.png]]
532 532  
533 533  
534 534  == 2.5 Integrate with Datacake ==
... ... @@ -539,7 +539,7 @@
539 539  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]]
540 540  
541 541  
542 -[[image:1664502695771-538.png||_mstalt="297349"]]
546 +[[image:1664502695771-538.png]]
543 543  
544 544  
545 545  == 2.6 Integrate with Tago ==
... ... @@ -550,7 +550,7 @@
550 550  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]]
551 551  
552 552  
553 -[[image:1664502715371-321.png||_mstalt="292162"]]
557 +[[image:1664502715371-321.png]]
554 554  
555 555  
556 556  == 2.7  Datalog Feature ==
... ... @@ -558,14 +558,14 @@
558 558  
559 559  total 273 entries,by default,
560 560  
561 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
565 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
562 562  
563 563  Example use case.
564 564  
565 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
569 +[[image:image-20221009234703-2.png||height="328" width="899"]]
566 566  
567 567  
568 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
572 +[[image:image-20221009234629-1.png||height="390" width="577"]]
569 569  
570 570  
571 571  == 2.8 Alarm Mode ==
... ... @@ -598,12 +598,7 @@
598 598  
599 599  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.
600 600  
601 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
602 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
603 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
604 604  
605 -
606 -
607 607  == 2.10 LED Status ==
608 608  
609 609  
... ... @@ -628,7 +628,7 @@
628 628  
629 629  (% style="color:blue" %)**RESET button:**
630 630  
631 -[[image:1664502835802-546.png||_mstalt="295061"]]
630 +[[image:1664502835802-546.png]]
632 632  
633 633  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
634 634  
... ... @@ -635,7 +635,7 @@
635 635  
636 636  (% style="color:red" %)**RED button:**
637 637  
638 -[[image:1664502854406-763.png||_mstalt="295568"]]
637 +[[image:1664502854406-763.png]]
639 639  
640 640  
641 641  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -672,21 +672,22 @@
672 672  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.
673 673  
674 674  
675 -[[image:1664502999401-486.png||_mstalt="296985"]]
674 +[[image:1664502999401-486.png]]
676 676  
677 677  
678 678  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:
679 679  
680 680  
681 -[[image:1664503022490-662.png||_mstalt="293332"]]
680 +[[image:1664503022490-662.png]]
682 682  
683 683  
684 -[[image:1664503035713-500.png||_mstalt="291096"]]
683 +[[image:1664503035713-500.png]]
685 685  
686 686  
687 -[[image:1664503047675-651.png||_mstalt="295386"]]
686 +[[image:1664503047675-651.png]]
688 688  
689 689  
689 +
690 690  == 3.2 Command Set ==
691 691  
692 692  === 3.2.1 Set Transmit Interval ===
... ... @@ -812,9 +812,9 @@
812 812  
813 813  (% style="color:#037691" %)**cc:   **
814 814  
815 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
815 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
816 816  
817 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
817 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
818 818  
819 819  (% style="color:blue" %)**Example:**
820 820  
... ... @@ -876,8 +876,8 @@
876 876  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
877 877  
878 878  
879 -=== 3.2.10 Disable/Enable the confirmation mode ===
880 880  
880 +**Disable/Enable the confirmation mode**
881 881  
882 882  * (% style="color:blue" %)**AT Command:**
883 883  
... ... @@ -896,7 +896,7 @@
896 896  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
897 897  
898 898  
899 -=== 3.2.11  Auto Send None-ACK messages ===
899 +=== 3.2.10  Auto Send None-ACK messages ===
900 900  
901 901  
902 902  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.
... ... @@ -914,10 +914,10 @@
914 914  
915 915  * (% style="color:blue" %)**Downlink Command: 0x34**
916 916  
917 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
917 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
918 918  
919 919  
920 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
920 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
921 921  
922 922  
923 923  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.
... ... @@ -926,16 +926,16 @@
926 926  
927 927  (% style="color:blue" %)**AT Command:**
928 928  
929 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
929 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
930 930  
931 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
931 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
932 932  
933 933  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
934 934  
935 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
935 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
936 936  
937 937  
938 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
938 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
939 939  
940 940  
941 941  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.
... ... @@ -944,16 +944,16 @@
944 944  
945 945  (% style="color:blue" %)**AT Command:**
946 946  
947 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
947 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
948 948  
949 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
949 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
950 950  
951 951  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
952 952  
953 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
953 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
954 954  
955 955  
956 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
956 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
957 957  
958 958  
959 959  Users can use this feature to enable/disable Information printing.
... ... @@ -960,11 +960,11 @@
960 960  
961 961  (% style="color:blue" %)**AT Command:**
962 962  
963 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
963 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
964 964  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
965 965  
966 966  
967 -=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
967 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
968 968  
969 969  
970 970  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -971,34 +971,14 @@
971 971  
972 972  (% style="color:blue" %)**AT Command:**
973 973  
974 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
974 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
975 975  
976 976  
977 977  (% style="color:blue" %)**Downlink Payload:0X24**
978 978  
979 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
979 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
980 980  
981 981  
982 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
983 -
984 -
985 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
986 -
987 -(% style="color:blue" %)**AT Command:**
988 -
989 -(% style="color:#037691" %)**AT+PT=xx**
990 -
991 - Example:
992 -
993 - AT+PT=14    ~-~->    Set to detect car motion.
994 -
995 - AT+PT=41  ~-~->    set to detect walk motion.
996 -
997 -
998 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
999 -0xB4 14          ~/~/  Same as AT+PT=14
1000 -
1001 -
1002 1002  = 4. Setting for Different Scenarios =
1003 1003  
1004 1004  
... ... @@ -1031,10 +1031,10 @@
1031 1031  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1032 1032  
1033 1033  
1034 -[[image:1664503563660-578.png||_mstalt="296777"]]
1014 +[[image:1664503563660-578.png]]
1035 1035  
1036 1036  
1037 -[[image:1664503574618-659.png||_mstalt="297986"]]
1017 +[[image:1664503574618-659.png]]
1038 1038  
1039 1039  
1040 1040  
... ... @@ -1050,15 +1050,16 @@
1050 1050  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1051 1051  
1052 1052  
1053 -[[image:image-20221207120501-1.png]]
1033 +[[image:image-20221118105220-2.png]]
1054 1054  
1055 1055  
1056 1056  
1057 1057  After upgrade finish, it will show finish as below:
1058 1058  
1059 -[[image:image-20221207133911-7.png]]
1039 +[[image:image-20221118105402-4.png]]
1060 1060  
1061 1061  
1042 +
1062 1062  = 6. Developer Guide =
1063 1063  
1064 1064  == 6.1 Compile Source Code ==
... ... @@ -1071,80 +1071,24 @@
1071 1071  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]]
1072 1072  
1073 1073  
1074 -[[image:1664503635019-941.png||_mstalt="294658"]]
1055 +[[image:1664503635019-941.png]]
1075 1075  
1076 1076  
1077 1077  
1078 1078  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1079 1079  
1080 -[[image:1664503715811-892.png||_mstalt="295698"]]
1061 +[[image:1664503715811-892.png]]
1081 1081  
1082 1082  
1083 -=== 6.1.2  Build the development environment ===
1084 -
1085 -
1086 -**~1. Download and install arduino IDE**
1087 -
1088 -[[https:~~/~~/www.arduino.cn/thread-5838-1-1.html>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fwww.arduino.cn%2Fthread-5838-1-1.html]]
1089 -
1090 -
1091 -**2. Download the ESP32 development package in the arduino IDE**
1092 -
1093 -[[image:image-20221213100007-1.png]]
1094 -
1095 -
1096 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1097 -
1098 -[[image:image-20221213100626-2.png]]
1099 -
1100 -
1101 -Restart the IDE after the addition is complete, then:
1102 -
1103 -[[image:image-20221213100808-3.png||height="679" width="649"]]
1104 -
1105 -
1106 -[[image:image-20221213101040-4.png]]
1107 -
1108 -
1109 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1110 -Don't quit halfway.~~! If you quit halfway, there is a high probability that it will freeze, and you will need to download again next time. (If you click to continue downloading, an error will be reported after completion)**
1111 -
1112 -Then enter a long waiting process. If you don't want to wait, you can go to the Internet to download directly, and then import:
1113 -
1114 -(% style="color:blue" %)**Methods as below:**
1115 -
1116 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1117 -
1118 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1119 -
1120 1120  (% 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.
1121 1121  
1122 -[[image:image-20221213102311-5.png||height="582" width="711"]]
1066 +[[image:image-20221024105643-1.png]]
1123 1123  
1124 -
1125 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1126 -
1127 -[[image:image-20221213102334-6.png]]
1128 -
1129 -(% style="color:red" %)**Note: This step requires a python environment**
1130 -
1131 -
1132 -Either way, in the end:
1133 -
1134 -The final effect is to open the arduino and you can see the esp32
1135 -
1136 -[[image:image-20221213110952-8.png||height="866" width="711"]]
1137 -
1138 -
1139 -
1140 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1141 -
1142 1142  **~ Figure1**
1143 1143  
1144 1144  
1071 +[[image:image-20221024105643-2.png]]
1145 1145  
1146 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1147 -
1148 1148   **Figure2**
1149 1149  
1150 1150  
... ... @@ -1153,7 +1153,7 @@
1153 1153  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1154 1154  
1155 1155  
1156 -[[image:1664503752288-974.png||_mstalt="298194"]]
1081 +[[image:1664503752288-974.png]]
1157 1157  
1158 1158  
1159 1159  == 6.2 Source Code ==
... ... @@ -1161,19 +1161,19 @@
1161 1161  
1162 1162  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1163 1163  
1164 -[[image:1664503794261-827.png||_mstalt="296387"]]
1089 +[[image:1664503794261-827.png]]
1165 1165  
1166 1166  
1167 1167  
1168 1168  * (% style="color:blue" %)**Click to upload**
1169 1169  
1170 -[[image:1664503808294-336.png||_mstalt="295711"]]
1095 +[[image:1664503808294-336.png]]
1171 1171  
1172 1172  
1173 1173  
1174 1174  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1175 1175  
1176 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1101 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1177 1177  
1178 1178  
1179 1179  = 7.  FAQ =
... ... @@ -1187,7 +1187,7 @@
1187 1187  == 7.2 What is the pin mapping for the USB program cable? ==
1188 1188  
1189 1189  
1190 -[[image:1664499635206-262.png||_mstalt="295360"]]
1115 +[[image:1664499635206-262.png]]
1191 1191  
1192 1192  
1193 1193  
... ... @@ -1214,13 +1214,13 @@
1214 1214  Need to adjust the data stream to RTS/CTS on physical restart.
1215 1215  
1216 1216  (% class="wikigeneratedid" %)
1217 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1142 +[[image:image-20221102140621-1.png]]
1218 1218  
1219 1219  
1220 1220  
1221 1221  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1222 1222  
1223 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1148 +[[image:image-20221102140638-2.png]]
1224 1224  
1225 1225  
1226 1226  === 7.3.2  SecureCRT ===
... ... @@ -1229,22 +1229,22 @@
1229 1229  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.
1230 1230  
1231 1231  
1232 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1157 +[[image:image-20221102140704-3.png]]
1233 1233  
1234 1234  
1235 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1160 +[[image:image-20221102140712-4.png]]
1236 1236  
1237 1237  
1238 1238  === 7.3.3  PUTTY ===
1239 1239  
1240 1240  
1241 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1166 +[[image:image-20221102140748-5.png]]
1242 1242  
1243 1243  
1244 1244  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.
1245 1245  
1246 1246  
1247 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1172 +[[image:image-20221102140801-6.png]]
1248 1248  
1249 1249  
1250 1250  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1259,7 +1259,7 @@
1259 1259  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1260 1260  
1261 1261  
1262 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1187 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1263 1263  
1264 1264  
1265 1265  
... ... @@ -1266,7 +1266,7 @@
1266 1266  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1267 1267  
1268 1268  
1269 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1194 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1270 1270  
1271 1271  
1272 1272  
... ... @@ -1273,7 +1273,7 @@
1273 1273  **3. Compile the AS923_JP band, please refer to the intention shown**
1274 1274  
1275 1275  
1276 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1201 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1277 1277  
1278 1278  
1279 1279  
... ... @@ -1280,18 +1280,12 @@
1280 1280  **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.**
1281 1281  
1282 1282  
1283 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1208 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1284 1284  
1285 1285  
1286 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1211 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1287 1287  
1288 1288  
1289 -== 7.5 Are there example python example for BLE Indoor Positioning? ==
1290 -
1291 -
1292 -[[Operating instructions for BLE indoor positioning>>Operating instructions for BLE indoor positioning]]
1293 -
1294 -
1295 1295  = 8  Trouble Shooting =
1296 1296  
1297 1297  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
... ... @@ -1298,7 +1298,7 @@
1298 1298  
1299 1299  
1300 1300  (((
1301 -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
1220 +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
1302 1302  )))
1303 1303  
1304 1304  
... ... @@ -1312,82 +1312,65 @@
1312 1312  
1313 1313  == 8.3  Problem after Upgrading Firmware ==
1314 1314  
1315 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1234 +=== 8.3.1 Continue Restart after upgrading ===
1316 1316  
1317 1317  
1318 -**Error Output**
1319 -
1320 -
1321 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1322 -
1323 -
1324 1324  (((
1325 -Some partition is missed during upgrade, please upgrade below four files as example:
1326 -
1327 -[[image:image-20221207120524-2.png]]
1238 +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
1328 1328  )))
1329 1329  
1330 1330  
1331 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1242 +[[image:image-20221118105249-3.png]]
1332 1332  
1333 1333  
1334 -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
1245 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1335 1335  
1336 1336  
1337 -=== 8.3.3 "flash read err" after upgrade firmware ===
1248 +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
1338 1338  
1339 1339  
1340 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1341 1341  
1252 +==== 8.3.2.1 If there is a situation in Figure 1,and a new partition file and bootloader file needs to be added. Please refer to the operation steps in Figure 2 ====
1342 1342  
1343 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1344 1344  
1255 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1345 1345  
1346 -User need to upgrade again with below four files to solve this issue.
1257 + ** Figure 1  **
1347 1347  
1348 - [[image:image-20221207120530-3.png]]
1349 1349  
1260 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1261 +
1350 1350   **Figure 2**
1351 1351  
1352 1352  
1353 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1354 1354  
1266 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1355 1355  
1356 -User might erase the entire flash include keys and default settings which cause this issue.
1357 1357  
1358 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1269 +[[image:image-20221122100004-3.png]]
1359 1359  
1271 +Please AT+FDR, and then enter the following instructions by the information on the label
1360 1360  
1361 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1273 +AT+DEUI=70B3D57ED0053981
1362 1362  
1275 +AT+APPEUI=D23345667BCBCCAF
1363 1363  
1364 -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.
1277 +AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1365 1365  
1366 -After AT+FDR. please set
1279 +AT+DADDR=260b4dce
1367 1367  
1368 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1281 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1369 1369  
1370 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1283 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1371 1371  
1372 -**Example:**
1373 1373  
1374 -AT+PDOP=7.00
1375 1375  
1376 -AT+FTIME=180
1287 +==== 8.3.2.2 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 ====
1377 1377  
1378 -AT+DEUI=70B3D57ED0053981  
1379 1379  
1380 -AT+APPEUI=D23345667BCBCCAF
1290 +[[image:image-20221122100004-4.png]]
1381 1381  
1382 -AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1383 1383  
1384 -AT+DADDR=260b4dce    ( no need for OTAA)
1385 -
1386 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1387 -
1388 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1389 -
1390 -
1391 1391  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1392 1392  
1393 1393  
... ... @@ -1401,61 +1401,15 @@
1401 1401  
1402 1402  2)  Set PDOP to a higher value.
1403 1403  
1404 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1306 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1405 1405  
1406 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1308 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1407 1407  
1408 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1310 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1409 1409  
1410 1410  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
1411 1411  
1412 1412  
1413 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1414 -
1415 -
1416 -When upgrading, use the erase button to upgrade
1417 -
1418 -[[image:image-20221207120536-4.png]]
1419 -
1420 -
1421 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1422 -
1423 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1424 -
1425 -
1426 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1427 -
1428 -[[image:image-20221207134028-8.png]]
1429 -
1430 -
1431 -Reboot information after upgrade
1432 -
1433 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1434 -
1435 -
1436 -Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal
1437 -
1438 -[[image:image-20221128111850-5.png]]
1439 -
1440 -
1441 -After the parameters return to normal, upgrade to the version you need again
1442 -
1443 -[[image:image-20221207120601-5.png]]
1444 -
1445 -
1446 -At this point, the parameters return to normal after running AT+FDR again
1447 -
1448 -[[image:image-20221128112035-7.png]]
1449 -
1450 -
1451 -== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1452 -
1453 -
1454 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1455 -
1456 -2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1457 -
1458 -
1459 1459  = 9.  Order Info =
1460 1460  
1461 1461  
... ... @@ -1513,4 +1513,3 @@
1513 1513  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1514 1514  
1515 1515  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1516 -)))
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
image-20221213100007-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -32.7 KB
Content
image-20221213100626-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -35.7 KB
Content
image-20221213100808-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -91.3 KB
Content
image-20221213101040-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -26.3 KB
Content
image-20221213102311-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.7 KB
Content
image-20221213102334-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.5 KB
Content
image-20221213102718-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -116.5 KB
Content
image-20221213110952-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -152.8 KB
Content