Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 143.2
edited by Xiaoling
on 2022/11/22 10:54
Change comment: There is no comment for this version
To version 150.1
edited by Edwin Chen
on 2022/11/24 09:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:1664505654417-133.png]]
2 +[[image:1664505654417-133.png||_mstalt="293696"]]
3 3  
4 4  
5 5  
... ... @@ -39,7 +39,7 @@
39 39  
40 40  )))
41 41  
42 -[[image:1664499921684-770.png]]
42 +[[image:1664499921684-770.png||_mstalt="298194"]]
43 43  
44 44  
45 45  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
... ... @@ -95,8 +95,6 @@
95 95  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
96 96  * Tracking: max: 38mA
97 97  
98 -
99 -
100 100  == 1.3  Features ==
101 101  
102 102  
... ... @@ -115,8 +115,6 @@
115 115  * Tri-color LED, Alarm button
116 116  * Datalog
117 117  
118 -
119 -
120 120  == 1.4  Applications ==
121 121  
122 122  
... ... @@ -123,8 +123,6 @@
123 123  * Logistics and Supply Chain Management
124 124  * Human tracking
125 125  
126 -
127 -
128 128  = 2.  Use TrackerD =
129 129  
130 130  == 2.1 How it works? ==
... ... @@ -139,7 +139,7 @@
139 139  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. 
140 140  
141 141  
142 -[[image:1664501652064-326.png]]
136 +[[image:1664501652064-326.png||_mstalt="293306"]]
143 143  
144 144  
145 145  
... ... @@ -151,7 +151,7 @@
151 151  Each TrackerD is shipped with a sticker with the default device EUI as below:
152 152  
153 153  
154 -[[image:1664501677253-891.png]]
148 +[[image:1664501677253-891.png||_mstalt="296569"]]
155 155  
156 156  
157 157  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -160,14 +160,14 @@
160 160  **__Add APP EUI in the application:__**
161 161  
162 162  
163 -[[image:1664501711466-918.png]]
157 +[[image:1664501711466-918.png||_mstalt="295828"]]
164 164  
165 165  
166 166  
167 -[[image:1664501721248-725.png]]
161 +[[image:1664501721248-725.png||_mstalt="294450"]]
168 168  
169 169  
170 -[[image:1664501734705-405.png]]
164 +[[image:1664501734705-405.png||_mstalt="293306"]]
171 171  
172 172  
173 173  
... ... @@ -174,15 +174,15 @@
174 174  **__Add APP KEY and DEV EUI:__**
175 175  
176 176  
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"]]
171 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]]
178 178  
179 179  
180 180  
181 181  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
182 182  
183 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
177 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
184 184  
185 -[[image:1664502835802-546.png]]
179 +[[image:1664502835802-546.png||_mstalt="295061"]]
186 186  
187 187  
188 188  (% 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.
... ... @@ -214,7 +214,7 @@
214 214  |=(% 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
215 215  |=(% 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
216 216  
217 -[[image:1665301570342-765.png]]
211 +[[image:1665301570342-765.png||_mstalt="294580"]]
218 218  
219 219  
220 220  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -281,7 +281,7 @@
281 281  
282 282  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
283 283  
284 -(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
278 +(% _mstmutation="1" style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
285 285  
286 286  
287 287  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -290,8 +290,6 @@
290 290  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit
291 291  |=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
292 292  
293 -
294 -
295 295  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
296 296  
297 297  
... ... @@ -310,7 +310,7 @@
310 310  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
311 311  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
312 312  
313 -[[image:1665301636888-168.png]]
305 +[[image:1665301636888-168.png||_mstalt="298012"]]
314 314  
315 315  
316 316  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -319,8 +319,6 @@
319 319  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
320 320  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
321 321  
322 -
323 -
324 324  ==== (% style="color:blue" %)**FLAG:**(%%) ====
325 325  
326 326  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
... ... @@ -342,12 +342,12 @@
342 342  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:
343 343  
344 344  
345 -[[image:1664502116362-706.png]]
335 +[[image:1664502116362-706.png||_mstalt="293306"]]
346 346  
347 347  
348 348  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
349 349  
350 -[[image:1664502166010-515.png]]
340 +[[image:1664502166010-515.png||_mstalt="291395"]]
351 351  
352 352  
353 353  
... ... @@ -370,8 +370,6 @@
370 370  * 3.40v ~~ 3.69v:  20% ~~ 40%
371 371  * < 3.39v:  0~~20%
372 372  
373 -
374 -
375 375  ==== (% style="color:blue" %)**MOD:**(%%) ====
376 376  
377 377  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -427,7 +427,7 @@
427 427  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
428 428  
429 429  (% class="wikigeneratedid" %)
430 -[[image:1665301687277-443.png]]
418 +[[image:1665301687277-443.png||_mstalt="296140"]]
431 431  
432 432  
433 433  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
... ... @@ -450,7 +450,7 @@
450 450  )))|4|4|2|1|1|1|1|1
451 451  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
452 452  
453 -[[image:image-20221009160309-2.png]]
441 +[[image:image-20221009160309-2.png||_mstalt="429312"]]
454 454  
455 455  
456 456  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
... ... @@ -477,7 +477,7 @@
477 477  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
478 478  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
479 479  
480 -[[image:1664502425687-834.png]]
468 +[[image:1664502425687-834.png||_mstalt="296738"]]
481 481  
482 482  
483 483  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -488,8 +488,6 @@
488 488  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
489 489  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
490 490  
491 -
492 -
493 493  === 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
494 494  
495 495  
... ... @@ -505,7 +505,7 @@
505 505  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
506 506  
507 507  (% class="wikigeneratedid" %)
508 -[[image:1667288597595-714.png||height="212" width="1151"]]
494 +[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
509 509  
510 510  
511 511  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -512,8 +512,6 @@
512 512  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
513 513  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
514 514  
515 -
516 -
517 517  === 2.4.7  Add Payload format in TTN V3 ===
518 518  
519 519  
... ... @@ -522,7 +522,7 @@
522 522  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
523 523  
524 524  
525 -[[image:1664502649601-895.png]]
509 +[[image:1664502649601-895.png||_mstalt="296985"]]
526 526  
527 527  
528 528  
... ... @@ -532,7 +532,7 @@
532 532  
533 533  Save the change the uplink message will be parsed. As below:
534 534  
535 -[[image:1664502676891-606.png]]
519 +[[image:1664502676891-606.png||_mstalt="296673"]]
536 536  
537 537  
538 538  == 2.5 Integrate with Datacake ==
... ... @@ -543,7 +543,7 @@
543 543  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]]
544 544  
545 545  
546 -[[image:1664502695771-538.png]]
530 +[[image:1664502695771-538.png||_mstalt="297349"]]
547 547  
548 548  
549 549  == 2.6 Integrate with Tago ==
... ... @@ -554,7 +554,7 @@
554 554  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]]
555 555  
556 556  
557 -[[image:1664502715371-321.png]]
541 +[[image:1664502715371-321.png||_mstalt="292162"]]
558 558  
559 559  
560 560  == 2.7  Datalog Feature ==
... ... @@ -566,10 +566,10 @@
566 566  
567 567  Example use case.
568 568  
569 -[[image:image-20221009234703-2.png||height="328" width="899"]]
553 +[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
570 570  
571 571  
572 -[[image:image-20221009234629-1.png||height="390" width="577"]]
556 +[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
573 573  
574 574  
575 575  == 2.8 Alarm Mode ==
... ... @@ -602,7 +602,13 @@
602 602  
603 603  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.
604 604  
589 +[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]] defines the Uplink Interval during transportation.
605 605  
591 +[[TDC>>||anchor="H3.2.1SetTransmitInterval"]] defines the uplink interval when TrackerD is stactic.
592 +
593 +[[PT>>||anchor="H3.2.1SetTransmitInterval"]] defines the threldhold to detect a motion.
594 +
595 +
606 606  == 2.10 LED Status ==
607 607  
608 608  
... ... @@ -620,14 +620,12 @@
620 620  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
621 621  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
622 622  
623 -
624 -
625 625  == 2.11 Button Function ==
626 626  
627 627  
628 628  (% style="color:blue" %)**RESET button:**
629 629  
630 -[[image:1664502835802-546.png]]
618 +[[image:1664502835802-546.png||_mstalt="295061"]]
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]]
625 +[[image:1664502854406-763.png||_mstalt="295568"]]
638 638  
639 639  
640 640  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -643,8 +643,6 @@
643 643  |(% style="width:135px" %)Exit Alarm Mode|(% style="width:220px" %)Fast press the (% style="color:red" %)**RED** (%%)button 10 times|(% style="width:265px" %)Exit Alarm Mode
644 644  |(% style="width:135px" %)Enter Deep Sleep Mode|(% style="width:220px" %)Press and hold the button for 10 seconds, then quickly press the device 3 times to enter deep sleep|(% style="width:265px" %)This is the mode ship out from factory. CPU will be complete in sleep mode and no LoRa activity, only use before deploy.
645 645  
646 -
647 -
648 648  == 2.12 USB Port Function ==
649 649  
650 650  
... ... @@ -655,8 +655,6 @@
655 655  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
656 656  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
657 657  
658 -
659 -
660 660  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
661 661  
662 662  
... ... @@ -671,19 +671,19 @@
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]]
658 +[[image:1664502999401-486.png||_mstalt="296985"]]
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]]
664 +[[image:1664503022490-662.png||_mstalt="293332"]]
681 681  
682 682  
683 -[[image:1664503035713-500.png]]
667 +[[image:1664503035713-500.png||_mstalt="291096"]]
684 684  
685 685  
686 -[[image:1664503047675-651.png]]
670 +[[image:1664503047675-651.png||_mstalt="295386"]]
687 687  
688 688  
689 689  
... ... @@ -812,9 +812,9 @@
812 812  
813 813  (% style="color:#037691" %)**cc:   **
814 814  
815 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
799 +* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
816 816  
817 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
801 +* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
818 818  
819 819  (% style="color:blue" %)**Example:**
820 820  
... ... @@ -877,7 +877,7 @@
877 877  
878 878  
879 879  
880 -**Disable/Enable the confirmation mode**
864 +=== 3.2.10 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.10  Auto Send None-ACK messages ===
883 +=== 3.2.11  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: 0x3401  ~/~/  Same as AT+PNACKMD=1
901 +Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
918 918  
919 919  
920 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
904 +=== 3.2.12  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 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
913 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
930 930  
931 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
915 + (% _mstmutation="1" 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: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
919 +Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
936 936  
937 937  
938 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
922 +=== 3.2.13  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 - (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
931 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
948 948  
949 - (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
933 + (% _mstmutation="1" 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: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
937 +Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
954 954  
955 955  
956 -=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
940 +=== 3.2.14  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.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
951 +=== 3.2.15 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.
... ... @@ -1011,10 +1011,10 @@
1011 1011  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1012 1012  
1013 1013  
1014 -[[image:1664503563660-578.png]]
998 +[[image:1664503563660-578.png||_mstalt="296777"]]
1015 1015  
1016 1016  
1017 -[[image:1664503574618-659.png]]
1001 +[[image:1664503574618-659.png||_mstalt="297986"]]
1018 1018  
1019 1019  
1020 1020  
... ... @@ -1030,13 +1030,13 @@
1030 1030  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1031 1031  
1032 1032  
1033 -[[image:image-20221118105220-2.png]]
1017 +[[image:image-20221118105220-2.png||_mstalt="426608"]]
1034 1034  
1035 1035  
1036 1036  
1037 1037  After upgrade finish, it will show finish as below:
1038 1038  
1039 -[[image:image-20221118105402-4.png]]
1023 +[[image:image-20221118105402-4.png||_mstalt="427986"]]
1040 1040  
1041 1041  
1042 1042  
... ... @@ -1052,23 +1052,23 @@
1052 1052  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]]
1053 1053  
1054 1054  
1055 -[[image:1664503635019-941.png]]
1039 +[[image:1664503635019-941.png||_mstalt="294658"]]
1056 1056  
1057 1057  
1058 1058  
1059 1059  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1060 1060  
1061 -[[image:1664503715811-892.png]]
1045 +[[image:1664503715811-892.png||_mstalt="295698"]]
1062 1062  
1063 1063  
1064 1064  (% 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.
1065 1065  
1066 -[[image:image-20221024105643-1.png]]
1050 +[[image:image-20221024105643-1.png||_mstalt="428129"]]
1067 1067  
1068 1068  **~ Figure1**
1069 1069  
1070 1070  
1071 -[[image:image-20221024105643-2.png]]
1055 +[[image:image-20221024105643-2.png||_mstalt="428493"]]
1072 1072  
1073 1073   **Figure2**
1074 1074  
... ... @@ -1078,7 +1078,7 @@
1078 1078  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1079 1079  
1080 1080  
1081 -[[image:1664503752288-974.png]]
1065 +[[image:1664503752288-974.png||_mstalt="298194"]]
1082 1082  
1083 1083  
1084 1084  == 6.2 Source Code ==
... ... @@ -1086,19 +1086,19 @@
1086 1086  
1087 1087  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1088 1088  
1089 -[[image:1664503794261-827.png]]
1073 +[[image:1664503794261-827.png||_mstalt="296387"]]
1090 1090  
1091 1091  
1092 1092  
1093 1093  * (% style="color:blue" %)**Click to upload**
1094 1094  
1095 -[[image:1664503808294-336.png]]
1079 +[[image:1664503808294-336.png||_mstalt="295711"]]
1096 1096  
1097 1097  
1098 1098  
1099 1099  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1100 1100  
1101 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1085 +[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1102 1102  
1103 1103  
1104 1104  = 7.  FAQ =
... ... @@ -1112,7 +1112,7 @@
1112 1112  == 7.2 What is the pin mapping for the USB program cable? ==
1113 1113  
1114 1114  
1115 -[[image:1664499635206-262.png]]
1099 +[[image:1664499635206-262.png||_mstalt="295360"]]
1116 1116  
1117 1117  
1118 1118  
... ... @@ -1127,8 +1127,6 @@
1127 1127  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1128 1128  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1129 1129  
1130 -
1131 -
1132 1132  == 7.3 Notes on using different serial port tools for TrackerD ==
1133 1133  
1134 1134  === 7.3.1  Serial port utility ===
... ... @@ -1139,13 +1139,13 @@
1139 1139  Need to adjust the data stream to RTS/CTS on physical restart.
1140 1140  
1141 1141  (% class="wikigeneratedid" %)
1142 -[[image:image-20221102140621-1.png]]
1124 +[[image:image-20221102140621-1.png||_mstalt="425672"]]
1143 1143  
1144 1144  
1145 1145  
1146 1146  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1147 1147  
1148 -[[image:image-20221102140638-2.png]]
1130 +[[image:image-20221102140638-2.png||_mstalt="428727"]]
1149 1149  
1150 1150  
1151 1151  === 7.3.2  SecureCRT ===
... ... @@ -1154,22 +1154,22 @@
1154 1154  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.
1155 1155  
1156 1156  
1157 -[[image:image-20221102140704-3.png]]
1139 +[[image:image-20221102140704-3.png||_mstalt="427076"]]
1158 1158  
1159 1159  
1160 -[[image:image-20221102140712-4.png]]
1142 +[[image:image-20221102140712-4.png||_mstalt="427089"]]
1161 1161  
1162 1162  
1163 1163  === 7.3.3  PUTTY ===
1164 1164  
1165 1165  
1166 -[[image:image-20221102140748-5.png]]
1148 +[[image:image-20221102140748-5.png||_mstalt="430456"]]
1167 1167  
1168 1168  
1169 1169  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.
1170 1170  
1171 1171  
1172 -[[image:image-20221102140801-6.png]]
1154 +[[image:image-20221102140801-6.png||_mstalt="427466"]]
1173 1173  
1174 1174  
1175 1175  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1184,7 +1184,7 @@
1184 1184  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1185 1185  
1186 1186  
1187 -[[image:image-20221116111844-1.png||height="227" width="782"]]
1169 +[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1188 1188  
1189 1189  
1190 1190  
... ... @@ -1191,7 +1191,7 @@
1191 1191  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1192 1192  
1193 1193  
1194 -[[image:image-20221116111844-2.png||height="262" width="781"]]
1176 +[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1195 1195  
1196 1196  
1197 1197  
... ... @@ -1198,7 +1198,7 @@
1198 1198  **3. Compile the AS923_JP band, please refer to the intention shown**
1199 1199  
1200 1200  
1201 -[[image:image-20221116111844-3.png||height="338" width="746"]]
1183 +[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1202 1202  
1203 1203  
1204 1204  
... ... @@ -1205,10 +1205,10 @@
1205 1205  **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.**
1206 1206  
1207 1207  
1208 -[[image:image-20221116111844-4.png||height="641" width="739"]]
1190 +[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1209 1209  
1210 1210  
1211 -[[image:image-20221116111844-5.png||height="551" width="708"]]
1193 +[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1212 1212  
1213 1213  
1214 1214  = 8  Trouble Shooting =
... ... @@ -1239,7 +1239,7 @@
1239 1239  )))
1240 1240  
1241 1241  
1242 -[[image:image-20221118105249-3.png]]
1224 +[[image:image-20221118105249-3.png||_mstalt="430664"]]
1243 1243  
1244 1244  
1245 1245  === 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
... ... @@ -1248,46 +1248,59 @@
1248 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
1249 1249  
1250 1250  
1233 +=== 8.3.3 "flash read err" after upgrade firmware ===
1251 1251  
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 ====
1235 +Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1253 1253  
1237 +[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1254 1254  
1255 -[[image:image-20221122100004-1.png||height="497" width="534"]]
1256 1256  
1257 - ** Figure 1  **
1240 +User need to upgrade again with below four files to solve this issue.
1258 1258  
1242 + [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1259 1259  
1260 - [[image:image-20221122100004-2.png||height="619" width="389"]]
1261 -
1262 1262   **Figure 2**
1263 1263  
1264 1264  
1247 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1265 1265  
1249 +User might erase the entire flash include keys and default settings which cause this issue.
1250 +
1266 1266  After the upgrade is completed, enter AT+CFG as shown in the figure below.
1267 1267  
1253 +[[image:image-20221122100004-3.png||_mstalt="424242"]]
1268 1268  
1269 -[[image:image-20221122100004-3.png]]
1255 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1270 1270  
1271 -Please AT+FDR, and then enter the following instructions by the information on the label
1257 +After AT+FDR. please set
1272 1272  
1273 -AT+DEUI=70B3D57ED0053981
1259 +* AT+PDOP=7
1260 +* AT+FTIME=180000
1274 1274  
1262 +Example:
1263 +
1264 +AT+PDOP=7.00
1265 +
1266 +AT+FTIME=180
1267 +
1268 +AT+DEUI=70B3D57ED0053981  
1269 +
1275 1275  AT+APPEUI=D23345667BCBCCAF
1276 1276  
1277 1277  AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1278 1278  
1279 -AT+DADDR=260b4dce
1274 +AT+DADDR=260b4dce    ( no need for OTAA)
1280 1280  
1281 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1276 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1282 1282  
1283 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1278 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1284 1284  
1285 1285  
1286 1286  
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 ====
1282 +=== 8.3.4  If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ===
1288 1288  
1289 1289  
1290 -[[image:image-20221122100004-4.png]]
1285 +[[image:image-20221122100004-4.png||_mstalt="424606"]]
1291 1291  
1292 1292  
1293 1293  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
... ... @@ -1303,11 +1303,11 @@
1303 1303  
1304 1304  2)  Set PDOP to a higher value.
1305 1305  
1306 -* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1301 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1307 1307  
1308 -* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1303 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1309 1309  
1310 -* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1305 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1311 1311  
1312 1312  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
1313 1313  
... ... @@ -1333,8 +1333,6 @@
1333 1333  
1334 1334  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1335 1335  
1336 -
1337 -
1338 1338  = 10.  Packing Info =
1339 1339  
1340 1340  
... ... @@ -1350,8 +1350,6 @@
1350 1350  
1351 1351  * Weight: 50g
1352 1352  
1353 -
1354 -
1355 1355  = 11. Support =
1356 1356  
1357 1357  
... ... @@ -1359,8 +1359,6 @@
1359 1359  
1360 1360  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].
1361 1361  
1362 -
1363 -
1364 1364  = 12.  Reference =
1365 1365  
1366 1366