Skip to Content
Last modified by Bei Jinggeng on 2025/07/23 11:03
From version 187.4
edited by Xiaoling
on 2022/12/21 16:09
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  
... ... @@ -367,6 +367,7 @@
367 367  * < 3.39v:  0~~20%
368 368  
369 369  
374 +
370 370  ==== (% style="color:blue" %)**MOD:**(%%) ====
371 371  
372 372  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -422,13 +422,13 @@
422 422  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
423 423  
424 424  (% class="wikigeneratedid" %)
425 -[[image:1665301687277-443.png||_mstalt="296140"]]
430 +[[image:1665301687277-443.png]]
426 426  
427 427  
428 428  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
429 429  
430 430  
431 -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.
432 432  
433 433  
434 434  (% style="color:red" %)**Note for this mode:**
... ... @@ -445,7 +445,7 @@
445 445  )))|4|4|2|1|1|1|1|1
446 446  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
447 447  
448 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
453 +[[image:image-20221009160309-2.png]]
449 449  
450 450  
451 451  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
... ... @@ -472,7 +472,7 @@
472 472  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
473 473  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
474 474  
475 -[[image:1664502425687-834.png||_mstalt="296738"]]
480 +[[image:1664502425687-834.png]]
476 476  
477 477  
478 478  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -500,7 +500,7 @@
500 500  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
501 501  
502 502  (% class="wikigeneratedid" %)
503 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
508 +[[image:1667288597595-714.png||height="212" width="1151"]]
504 504  
505 505  
506 506  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -517,7 +517,7 @@
517 517  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
518 518  
519 519  
520 -[[image:1664502649601-895.png||_mstalt="296985"]]
525 +[[image:1664502649601-895.png]]
521 521  
522 522  
523 523  
... ... @@ -527,7 +527,7 @@
527 527  
528 528  Save the change the uplink message will be parsed. As below:
529 529  
530 -[[image:1664502676891-606.png||_mstalt="296673"]]
535 +[[image:1664502676891-606.png]]
531 531  
532 532  
533 533  == 2.5 Integrate with Datacake ==
... ... @@ -538,7 +538,7 @@
538 538  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]]
539 539  
540 540  
541 -[[image:1664502695771-538.png||_mstalt="297349"]]
546 +[[image:1664502695771-538.png]]
542 542  
543 543  
544 544  == 2.6 Integrate with Tago ==
... ... @@ -549,7 +549,7 @@
549 549  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]]
550 550  
551 551  
552 -[[image:1664502715371-321.png||_mstalt="292162"]]
557 +[[image:1664502715371-321.png]]
553 553  
554 554  
555 555  == 2.7  Datalog Feature ==
... ... @@ -557,14 +557,14 @@
557 557  
558 558  total 273 entries,by default,
559 559  
560 -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.
561 561  
562 562  Example use case.
563 563  
564 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
569 +[[image:image-20221009234703-2.png||height="328" width="899"]]
565 565  
566 566  
567 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
572 +[[image:image-20221009234629-1.png||height="390" width="577"]]
568 568  
569 569  
570 570  == 2.8 Alarm Mode ==
... ... @@ -597,12 +597,7 @@
597 597  
598 598  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.
599 599  
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.
603 603  
604 -
605 -
606 606  == 2.10 LED Status ==
607 607  
608 608  
... ... @@ -627,7 +627,7 @@
627 627  
628 628  (% style="color:blue" %)**RESET button:**
629 629  
630 -[[image:1664502835802-546.png||_mstalt="295061"]]
630 +[[image:1664502835802-546.png]]
631 631  
632 632  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
633 633  
... ... @@ -634,7 +634,7 @@
634 634  
635 635  (% style="color:red" %)**RED button:**
636 636  
637 -[[image:1664502854406-763.png||_mstalt="295568"]]
637 +[[image:1664502854406-763.png]]
638 638  
639 639  
640 640  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -671,21 +671,22 @@
671 671  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.
672 672  
673 673  
674 -[[image:1664502999401-486.png||_mstalt="296985"]]
674 +[[image:1664502999401-486.png]]
675 675  
676 676  
677 677  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:
678 678  
679 679  
680 -[[image:1664503022490-662.png||_mstalt="293332"]]
680 +[[image:1664503022490-662.png]]
681 681  
682 682  
683 -[[image:1664503035713-500.png||_mstalt="291096"]]
683 +[[image:1664503035713-500.png]]
684 684  
685 685  
686 -[[image:1664503047675-651.png||_mstalt="295386"]]
686 +[[image:1664503047675-651.png]]
687 687  
688 688  
689 +
689 689  == 3.2 Command Set ==
690 690  
691 691  === 3.2.1 Set Transmit Interval ===
... ... @@ -811,9 +811,9 @@
811 811  
812 812  (% style="color:#037691" %)**cc:   **
813 813  
814 -* (% _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  
815 815  
816 -* (% _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(%%))  
817 817  
818 818  (% style="color:blue" %)**Example:**
819 819  
... ... @@ -875,8 +875,8 @@
875 875  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
876 876  
877 877  
878 -=== 3.2.10 Disable/Enable the confirmation mode ===
879 879  
880 +**Disable/Enable the confirmation mode**
880 880  
881 881  * (% style="color:blue" %)**AT Command:**
882 882  
... ... @@ -895,7 +895,7 @@
895 895  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
896 896  
897 897  
898 -=== 3.2.11  Auto Send None-ACK messages ===
899 +=== 3.2.10  Auto Send None-ACK messages ===
899 899  
900 900  
901 901  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.
... ... @@ -913,10 +913,10 @@
913 913  
914 914  * (% style="color:blue" %)**Downlink Command: 0x34**
915 915  
916 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
917 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
917 917  
918 918  
919 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
920 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
920 920  
921 921  
922 922  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.
... ... @@ -925,16 +925,16 @@
925 925  
926 926  (% style="color:blue" %)**AT Command:**
927 927  
928 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
929 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
929 929  
930 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
931 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
931 931  
932 932  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
933 933  
934 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
935 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
935 935  
936 936  
937 -=== 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） ===
938 938  
939 939  
940 940  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.
... ... @@ -943,16 +943,16 @@
943 943  
944 944  (% style="color:blue" %)**AT Command:**
945 945  
946 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
947 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
947 947  
948 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
949 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
949 949  
950 950  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
951 951  
952 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
953 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
953 953  
954 954  
955 -=== 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） ===
956 956  
957 957  
958 958  Users can use this feature to enable/disable Information printing.
... ... @@ -959,11 +959,11 @@
959 959  
960 960  (% style="color:blue" %)**AT Command:**
961 961  
962 -(% 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)
963 963  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
964 964  
965 965  
966 -=== 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） ===
967 967  
968 968  
969 969  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -970,34 +970,14 @@
970 970  
971 971  (% style="color:blue" %)**AT Command:**
972 972  
973 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
974 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
974 974  
975 975  
976 976  (% style="color:blue" %)**Downlink Payload:0X24**
977 977  
978 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
979 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
979 979  
980 980  
981 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
982 -
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 1001  = 4. Setting for Different Scenarios =
1002 1002  
1003 1003  
... ... @@ -1030,10 +1030,10 @@
1030 1030  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1031 1031  
1032 1032  
1033 -[[image:1664503563660-578.png||_mstalt="296777"]]
1014 +[[image:1664503563660-578.png]]
1034 1034  
1035 1035  
1036 -[[image:1664503574618-659.png||_mstalt="297986"]]
1017 +[[image:1664503574618-659.png]]
1037 1037  
1038 1038  
1039 1039  
... ... @@ -1049,15 +1049,16 @@
1049 1049  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1050 1050  
1051 1051  
1052 -[[image:image-20221207120501-1.png]]
1033 +[[image:image-20221118105220-2.png]]
1053 1053  
1054 1054  
1055 1055  
1056 1056  After upgrade finish, it will show finish as below:
1057 1057  
1058 -[[image:image-20221207133911-7.png]]
1039 +[[image:image-20221118105402-4.png]]
1059 1059  
1060 1060  
1042 +
1061 1061  = 6. Developer Guide =
1062 1062  
1063 1063  == 6.1 Compile Source Code ==
... ... @@ -1070,80 +1070,24 @@
1070 1070  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]]
1071 1071  
1072 1072  
1073 -[[image:1664503635019-941.png||_mstalt="294658"]]
1055 +[[image:1664503635019-941.png]]
1074 1074  
1075 1075  
1076 1076  
1077 1077  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1078 1078  
1079 -[[image:1664503715811-892.png||_mstalt="295698"]]
1061 +[[image:1664503715811-892.png]]
1080 1080  
1081 1081  
1082 -=== 6.1.2  Build the development environment ===
1083 -
1084 -
1085 -**~1. Download and install arduino IDE**
1086 -
1087 -[[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]]
1088 -
1089 -
1090 -**2. Download the ESP32 development package in the arduino IDE**
1091 -
1092 -[[image:image-20221213100007-1.png]]
1093 -
1094 -
1095 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1096 -
1097 -[[image:image-20221213100626-2.png]]
1098 -
1099 -
1100 -Restart the IDE after the addition is complete, then:
1101 -
1102 -[[image:image-20221213100808-3.png||height="679" width="649"]]
1103 -
1104 -
1105 -[[image:image-20221213101040-4.png]]
1106 -
1107 -
1108 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1109 -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)**
1110 -
1111 -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:
1112 -
1113 -(% style="color:blue" %)**Methods as below:**
1114 -
1115 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1116 -
1117 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1118 -
1119 1119  (% 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.
1120 1120  
1121 -[[image:image-20221213102311-5.png||height="582" width="711"]]
1066 +[[image:image-20221024105643-1.png]]
1122 1122  
1123 -
1124 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1125 -
1126 -[[image:image-20221213102334-6.png]]
1127 -
1128 -(% style="color:red" %)**Note: This step requires a python environment**
1129 -
1130 -
1131 -Either way, in the end:
1132 -
1133 -The final effect is to open the arduino and you can see the esp32
1134 -
1135 -[[image:image-20221213110952-8.png||height="866" width="711"]]
1136 -
1137 -
1138 -
1139 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1140 -
1141 1141  **~ Figure1**
1142 1142  
1143 1143  
1071 +[[image:image-20221024105643-2.png]]
1144 1144  
1145 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1146 -
1147 1147   **Figure2**
1148 1148  
1149 1149  
... ... @@ -1152,7 +1152,7 @@
1152 1152  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1153 1153  
1154 1154  
1155 -[[image:1664503752288-974.png||_mstalt="298194"]]
1081 +[[image:1664503752288-974.png]]
1156 1156  
1157 1157  
1158 1158  == 6.2 Source Code ==
... ... @@ -1160,19 +1160,19 @@
1160 1160  
1161 1161  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1162 1162  
1163 -[[image:1664503794261-827.png||_mstalt="296387"]]
1089 +[[image:1664503794261-827.png]]
1164 1164  
1165 1165  
1166 1166  
1167 1167  * (% style="color:blue" %)**Click to upload**
1168 1168  
1169 -[[image:1664503808294-336.png||_mstalt="295711"]]
1095 +[[image:1664503808294-336.png]]
1170 1170  
1171 1171  
1172 1172  
1173 1173  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1174 1174  
1175 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1101 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1176 1176  
1177 1177  
1178 1178  = 7.  FAQ =
... ... @@ -1186,7 +1186,7 @@
1186 1186  == 7.2 What is the pin mapping for the USB program cable? ==
1187 1187  
1188 1188  
1189 -[[image:1664499635206-262.png||_mstalt="295360"]]
1115 +[[image:1664499635206-262.png]]
1190 1190  
1191 1191  
1192 1192  
... ... @@ -1213,13 +1213,13 @@
1213 1213  Need to adjust the data stream to RTS/CTS on physical restart.
1214 1214  
1215 1215  (% class="wikigeneratedid" %)
1216 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1142 +[[image:image-20221102140621-1.png]]
1217 1217  
1218 1218  
1219 1219  
1220 1220  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1221 1221  
1222 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1148 +[[image:image-20221102140638-2.png]]
1223 1223  
1224 1224  
1225 1225  === 7.3.2  SecureCRT ===
... ... @@ -1228,22 +1228,22 @@
1228 1228  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.
1229 1229  
1230 1230  
1231 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1157 +[[image:image-20221102140704-3.png]]
1232 1232  
1233 1233  
1234 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1160 +[[image:image-20221102140712-4.png]]
1235 1235  
1236 1236  
1237 1237  === 7.3.3  PUTTY ===
1238 1238  
1239 1239  
1240 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1166 +[[image:image-20221102140748-5.png]]
1241 1241  
1242 1242  
1243 1243  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.
1244 1244  
1245 1245  
1246 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1172 +[[image:image-20221102140801-6.png]]
1247 1247  
1248 1248  
1249 1249  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1258,7 +1258,7 @@
1258 1258  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1259 1259  
1260 1260  
1261 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1187 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1262 1262  
1263 1263  
1264 1264  
... ... @@ -1265,7 +1265,7 @@
1265 1265  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1266 1266  
1267 1267  
1268 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1194 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1269 1269  
1270 1270  
1271 1271  
... ... @@ -1272,7 +1272,7 @@
1272 1272  **3. Compile the AS923_JP band, please refer to the intention shown**
1273 1273  
1274 1274  
1275 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1201 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1276 1276  
1277 1277  
1278 1278  
... ... @@ -1279,18 +1279,12 @@
1279 1279  **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.**
1280 1280  
1281 1281  
1282 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1208 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1283 1283  
1284 1284  
1285 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1211 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1286 1286  
1287 1287  
1288 -== 7.5 Are there example python example for BLE Indoor Positioning? ==
1289 -
1290 -
1291 -[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1292 -
1293 -
1294 1294  = 8  Trouble Shooting =
1295 1295  
1296 1296  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
... ... @@ -1297,7 +1297,7 @@
1297 1297  
1298 1298  
1299 1299  (((
1300 -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
1301 1301  )))
1302 1302  
1303 1303  
... ... @@ -1311,82 +1311,65 @@
1311 1311  
1312 1312  == 8.3  Problem after Upgrading Firmware ==
1313 1313  
1314 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1234 +=== 8.3.1 Continue Restart after upgrading ===
1315 1315  
1316 1316  
1317 -**Error Output**
1318 -
1319 -
1320 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1321 -
1322 -
1323 1323  (((
1324 -Some partition is missed during upgrade, please upgrade below four files as example:
1325 -
1326 -[[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
1327 1327  )))
1328 1328  
1329 1329  
1330 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1242 +[[image:image-20221118105249-3.png]]
1331 1331  
1332 1332  
1333 -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 ===
1334 1334  
1335 1335  
1336 -=== 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
1337 1337  
1338 1338  
1339 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1340 1340  
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 ====
1341 1341  
1342 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1343 1343  
1255 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1344 1344  
1345 -User need to upgrade again with below four files to solve this issue.
1257 + ** Figure 1  **
1346 1346  
1347 - [[image:image-20221207120530-3.png]]
1348 1348  
1260 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1261 +
1349 1349   **Figure 2**
1350 1350  
1351 1351  
1352 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1353 1353  
1266 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1354 1354  
1355 -User might erase the entire flash include keys and default settings which cause this issue.
1356 1356  
1357 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1269 +[[image:image-20221122100004-3.png]]
1358 1358  
1271 +Please AT+FDR, and then enter the following instructions by the information on the label
1359 1359  
1360 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1273 +AT+DEUI=70B3D57ED0053981
1361 1361  
1275 +AT+APPEUI=D23345667BCBCCAF
1362 1362  
1363 -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
1364 1364  
1365 -After AT+FDR. please set
1279 +AT+DADDR=260b4dce
1366 1366  
1367 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1281 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1368 1368  
1369 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1283 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1370 1370  
1371 -**Example:**
1372 1372  
1373 -AT+PDOP=7.00
1374 1374  
1375 -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 ====
1376 1376  
1377 -AT+DEUI=70B3D57ED0053981  
1378 1378  
1379 -AT+APPEUI=D23345667BCBCCAF
1290 +[[image:image-20221122100004-4.png]]
1380 1380  
1381 -AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1382 1382  
1383 -AT+DADDR=260b4dce    ( no need for OTAA)
1384 -
1385 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1386 -
1387 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1388 -
1389 -
1390 1390  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1391 1391  
1392 1392  
... ... @@ -1400,61 +1400,15 @@
1400 1400  
1401 1401  2)  Set PDOP to a higher value.
1402 1402  
1403 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1306 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1404 1404  
1405 -* (% _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）
1406 1406  
1407 -* (% _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）
1408 1408  
1409 1409  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
1410 1410  
1411 1411  
1412 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1413 -
1414 -
1415 -When upgrading, use the erase button to upgrade
1416 -
1417 -[[image:image-20221207120536-4.png]]
1418 -
1419 -
1420 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1421 -
1422 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1423 -
1424 -
1425 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1426 -
1427 -[[image:image-20221207134028-8.png]]
1428 -
1429 -
1430 -Reboot information after upgrade
1431 -
1432 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1433 -
1434 -
1435 -Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal
1436 -
1437 -[[image:image-20221128111850-5.png]]
1438 -
1439 -
1440 -After the parameters return to normal, upgrade to the version you need again
1441 -
1442 -[[image:image-20221207120601-5.png]]
1443 -
1444 -
1445 -At this point, the parameters return to normal after running AT+FDR again
1446 -
1447 -[[image:image-20221128112035-7.png]]
1448 -
1449 -
1450 -== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1451 -
1452 -
1453 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1454 -
1455 -2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1456 -
1457 -
1458 1458  = 9.  Order Info =
1459 1459  
1460 1460  
... ... @@ -1512,4 +1512,3 @@
1512 1512  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1513 1513  
1514 1514  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1515 -)))
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