Last modified by Xiaoling on 2023/12/27 09:15

From version 155.4
edited by Xiaoling
on 2022/11/24 17:21
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  
... ... @@ -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.**
... ... @@ -136,7 +136,7 @@
136 136  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. 
137 137  
138 138  
139 -[[image:1664501652064-326.png||_mstalt="293306"]]
142 +[[image:1664501652064-326.png]]
140 140  
141 141  
142 142  
... ... @@ -148,7 +148,7 @@
148 148  Each TrackerD is shipped with a sticker with the default device EUI as below:
149 149  
150 150  
151 -[[image:1664501677253-891.png||_mstalt="296569"]]
154 +[[image:1664501677253-891.png]]
152 152  
153 153  
154 154  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -157,14 +157,14 @@
157 157  **__Add APP EUI in the application:__**
158 158  
159 159  
160 -[[image:1664501711466-918.png||_mstalt="295828"]]
163 +[[image:1664501711466-918.png]]
161 161  
162 162  
163 163  
164 -[[image:1664501721248-725.png||_mstalt="294450"]]
167 +[[image:1664501721248-725.png]]
165 165  
166 166  
167 -[[image:1664501734705-405.png||_mstalt="293306"]]
170 +[[image:1664501734705-405.png]]
168 168  
169 169  
170 170  
... ... @@ -171,15 +171,15 @@
171 171  **__Add APP KEY and DEV EUI:__**
172 172  
173 173  
174 -[[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"]]
175 175  
176 176  
177 177  
178 178  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
179 179  
180 -(% 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]]
181 181  
182 -[[image:1664502835802-546.png||_mstalt="295061"]]
185 +[[image:1664502835802-546.png]]
183 183  
184 184  
185 185  (% 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.
... ... @@ -211,7 +211,7 @@
211 211  |=(% 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
212 212  |=(% 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
213 213  
214 -[[image:1665301570342-765.png||_mstalt="294580"]]
217 +[[image:1665301570342-765.png]]
215 215  
216 216  
217 217  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -278,7 +278,7 @@
278 278  
279 279  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
280 280  
281 -(% _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)(%%)  
282 282  
283 283  
284 284  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -307,7 +307,7 @@
307 307  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
308 308  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
309 309  
310 -[[image:1665301636888-168.png||_mstalt="298012"]]
313 +[[image:1665301636888-168.png]]
311 311  
312 312  
313 313  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -316,6 +316,8 @@
316 316  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
317 317  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
318 318  
322 +
323 +
319 319  ==== (% style="color:blue" %)**FLAG:**(%%) ====
320 320  
321 321  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
... ... @@ -337,12 +337,12 @@
337 337  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:
338 338  
339 339  
340 -[[image:1664502116362-706.png||_mstalt="293306"]]
345 +[[image:1664502116362-706.png]]
341 341  
342 342  
343 343  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
344 344  
345 -[[image:1664502166010-515.png||_mstalt="291395"]]
350 +[[image:1664502166010-515.png]]
346 346  
347 347  
348 348  
... ... @@ -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.11A0A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
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.11A0A0AutoSendNone-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  
... ... @@ -876,9 +876,8 @@
876 876  
877 877  
878 878  
879 -=== 3.2.10 Disable/Enable the confirmation mode ===
880 +**Disable/Enable the confirmation mode**
880 880  
881 -
882 882  * (% style="color:blue" %)**AT Command:**
883 883  
884 884  (% style="color:#037691" %)**AT+CFM=xx**
... ... @@ -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.1 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.
... ... @@ -964,7 +964,7 @@
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.
... ... @@ -979,26 +979,6 @@
979 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 -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 -
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,13 +1050,13 @@
1050 1050  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1051 1051  
1052 1052  
1053 -[[image:image-20221118105220-2.png||_mstalt="426608"]]
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-20221118105402-4.png||_mstalt="427986"]]
1039 +[[image:image-20221118105402-4.png]]
1060 1060  
1061 1061  
1062 1062  
... ... @@ -1072,23 +1072,23 @@
1072 1072  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]]
1073 1073  
1074 1074  
1075 -[[image:1664503635019-941.png||_mstalt="294658"]]
1055 +[[image:1664503635019-941.png]]
1076 1076  
1077 1077  
1078 1078  
1079 1079  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1080 1080  
1081 -[[image:1664503715811-892.png||_mstalt="295698"]]
1061 +[[image:1664503715811-892.png]]
1082 1082  
1083 1083  
1084 1084  (% 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.
1085 1085  
1086 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1066 +[[image:image-20221024105643-1.png]]
1087 1087  
1088 1088  **~ Figure1**
1089 1089  
1090 1090  
1091 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1071 +[[image:image-20221024105643-2.png]]
1092 1092  
1093 1093   **Figure2**
1094 1094  
... ... @@ -1098,7 +1098,7 @@
1098 1098  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1099 1099  
1100 1100  
1101 -[[image:1664503752288-974.png||_mstalt="298194"]]
1081 +[[image:1664503752288-974.png]]
1102 1102  
1103 1103  
1104 1104  == 6.2 Source Code ==
... ... @@ -1106,19 +1106,19 @@
1106 1106  
1107 1107  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1108 1108  
1109 -[[image:1664503794261-827.png||_mstalt="296387"]]
1089 +[[image:1664503794261-827.png]]
1110 1110  
1111 1111  
1112 1112  
1113 1113  * (% style="color:blue" %)**Click to upload**
1114 1114  
1115 -[[image:1664503808294-336.png||_mstalt="295711"]]
1095 +[[image:1664503808294-336.png]]
1116 1116  
1117 1117  
1118 1118  
1119 1119  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1120 1120  
1121 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1101 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1122 1122  
1123 1123  
1124 1124  = 7.  FAQ =
... ... @@ -1132,7 +1132,7 @@
1132 1132  == 7.2 What is the pin mapping for the USB program cable? ==
1133 1133  
1134 1134  
1135 -[[image:1664499635206-262.png||_mstalt="295360"]]
1115 +[[image:1664499635206-262.png]]
1136 1136  
1137 1137  
1138 1138  
... ... @@ -1159,13 +1159,13 @@
1159 1159  Need to adjust the data stream to RTS/CTS on physical restart.
1160 1160  
1161 1161  (% class="wikigeneratedid" %)
1162 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1142 +[[image:image-20221102140621-1.png]]
1163 1163  
1164 1164  
1165 1165  
1166 1166  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1167 1167  
1168 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1148 +[[image:image-20221102140638-2.png]]
1169 1169  
1170 1170  
1171 1171  === 7.3.2  SecureCRT ===
... ... @@ -1174,22 +1174,22 @@
1174 1174  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.
1175 1175  
1176 1176  
1177 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1157 +[[image:image-20221102140704-3.png]]
1178 1178  
1179 1179  
1180 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1160 +[[image:image-20221102140712-4.png]]
1181 1181  
1182 1182  
1183 1183  === 7.3.3  PUTTY ===
1184 1184  
1185 1185  
1186 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1166 +[[image:image-20221102140748-5.png]]
1187 1187  
1188 1188  
1189 1189  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.
1190 1190  
1191 1191  
1192 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1172 +[[image:image-20221102140801-6.png]]
1193 1193  
1194 1194  
1195 1195  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1204,7 +1204,7 @@
1204 1204  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1205 1205  
1206 1206  
1207 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1187 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1208 1208  
1209 1209  
1210 1210  
... ... @@ -1211,7 +1211,7 @@
1211 1211  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1212 1212  
1213 1213  
1214 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1194 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1215 1215  
1216 1216  
1217 1217  
... ... @@ -1218,7 +1218,7 @@
1218 1218  **3. Compile the AS923_JP band, please refer to the intention shown**
1219 1219  
1220 1220  
1221 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1201 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1222 1222  
1223 1223  
1224 1224  
... ... @@ -1225,10 +1225,10 @@
1225 1225  **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.**
1226 1226  
1227 1227  
1228 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1208 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1229 1229  
1230 1230  
1231 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1211 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1232 1232  
1233 1233  
1234 1234  = 8  Trouble Shooting =
... ... @@ -1237,7 +1237,7 @@
1237 1237  
1238 1238  
1239 1239  (((
1240 -Before firmware v1.4.0: When the Transport Mode is enabled ((% style="color:blue" %)**AT+INTWK=1**(%%)), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
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
1241 1241  )))
1242 1242  
1243 1243  
... ... @@ -1251,82 +1251,65 @@
1251 1251  
1252 1252  == 8.3  Problem after Upgrading Firmware ==
1253 1253  
1254 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1234 +=== 8.3.1 Continue Restart after upgrading ===
1255 1255  
1256 1256  
1257 -**Error Output**
1258 -
1259 -
1260 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1261 -
1262 -
1263 1263  (((
1264 -Some partition is missed during upgrade, please upgrade below four files as example:
1265 -
1266 -[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
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
1267 1267  )))
1268 1268  
1269 1269  
1270 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1242 +[[image:image-20221118105249-3.png]]
1271 1271  
1272 1272  
1273 -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 ===
1274 1274  
1275 1275  
1276 -=== 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
1277 1277  
1278 1278  
1279 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1280 1280  
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 ====
1281 1281  
1282 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1283 1283  
1255 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1284 1284  
1285 -User need to upgrade again with below four files to solve this issue.
1257 + ** Figure 1  **
1286 1286  
1287 - [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1288 1288  
1260 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1261 +
1289 1289   **Figure 2**
1290 1290  
1291 1291  
1292 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1293 1293  
1266 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1294 1294  
1295 -User might erase the entire flash include keys and default settings which cause this issue.
1296 1296  
1297 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1269 +[[image:image-20221122100004-3.png]]
1298 1298  
1271 +Please AT+FDR, and then enter the following instructions by the information on the label
1299 1299  
1300 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1273 +AT+DEUI=70B3D57ED0053981
1301 1301  
1275 +AT+APPEUI=D23345667BCBCCAF
1302 1302  
1303 -Please (% style="color:blue" %)**AT+FDR**(%%) which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1277 +AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1304 1304  
1305 -After AT+FDR. please set
1279 +AT+DADDR=260b4dce
1306 1306  
1307 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1281 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1308 1308  
1309 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1283 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1310 1310  
1311 -**Example:**
1312 1312  
1313 -AT+PDOP=7.00
1314 1314  
1315 -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 ====
1316 1316  
1317 -AT+DEUI=70B3D57ED0053981  
1318 1318  
1319 -AT+APPEUI=D23345667BCBCCAF
1290 +[[image:image-20221122100004-4.png]]
1320 1320  
1321 -AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1322 1322  
1323 -AT+DADDR=260b4dce    ( no need for OTAA)
1324 -
1325 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1326 -
1327 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1328 -
1329 -
1330 1330  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1331 1331  
1332 1332  
... ... @@ -1340,11 +1340,11 @@
1340 1340  
1341 1341  2)  Set PDOP to a higher value.
1342 1342  
1343 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.)
1306 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.)
1344 1344  
1345 -* (% _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)
1346 1346  
1347 -* (% _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)
1348 1348  
1349 1349  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
1350 1350  
... ... @@ -1406,4 +1406,3 @@
1406 1406  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1407 1407  
1408 1408  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1409 -)))