Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 113.7
edited by Xiaoling
on 2022/11/09 17:02
Change comment: There is no comment for this version
To version 159.1
edited by Bei Jinggeng
on 2022/11/28 11:14
Change comment: Uploaded new attachment "image-20221128111443-4.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
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  
... ... @@ -14,7 +14,6 @@
14 14  
15 15  = 1.  Introduction =
16 16  
17 -
18 18  == 1.1  What is TrackerD ==
19 19  
20 20  
... ... @@ -32,21 +32,17 @@
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  )))
35 -)))
36 36  
37 37  (((
38 38  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.
39 -
40 -
41 41  )))
42 42  
43 -[[image:1664499921684-770.png]]
39 +[[image:1664499921684-770.png||_mstalt="298194"]]
44 44  
45 45  
46 46  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
47 47  
48 48  
49 -
50 50  == 1.2 Specifications ==
51 51  
52 52  
... ... @@ -97,6 +97,8 @@
97 97  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
98 98  * Tracking: max: 38mA
99 99  
95 +
96 +
100 100  == 1.3  Features ==
101 101  
102 102  
... ... @@ -115,6 +115,8 @@
115 115  * Tri-color LED, Alarm button
116 116  * Datalog
117 117  
115 +
116 +
118 118  == 1.4  Applications ==
119 119  
120 120  
... ... @@ -121,9 +121,10 @@
121 121  * Logistics and Supply Chain Management
122 122  * Human tracking
123 123  
124 -= 2.  Use TrackerD =
125 125  
126 126  
125 += 2.  Use TrackerD =
126 +
127 127  == 2.1 How it works? ==
128 128  
129 129  
... ... @@ -130,7 +130,6 @@
130 130  TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.
131 131  
132 132  
133 -
134 134  == 2.2 Quick guide to connect to LoRaWAN server ==
135 135  
136 136  
... ... @@ -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]]
139 +[[image:1664501652064-326.png||_mstalt="293306"]]
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]]
151 +[[image:1664501677253-891.png||_mstalt="296569"]]
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]]
160 +[[image:1664501711466-918.png||_mstalt="295828"]]
162 162  
163 163  
164 164  
165 -[[image:1664501721248-725.png]]
164 +[[image:1664501721248-725.png||_mstalt="294450"]]
166 166  
167 167  
168 -[[image:1664501734705-405.png]]
167 +[[image:1664501734705-405.png||_mstalt="293306"]]
169 169  
170 170  
171 171  
... ... @@ -172,17 +172,20 @@
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||alt="1654671889112-678.png"]]
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"]]
176 176  
177 177  
178 178  
179 -(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
178 +(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
180 180  
180 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
181 181  
182 -(% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
182 +[[image:1664502835802-546.png||_mstalt="295061"]]
183 183  
184 184  
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.
185 185  
187 +
186 186  == 2.3  Positioning Mode(SMOD) ==
187 187  
188 188  
... ... @@ -195,10 +195,8 @@
195 195  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
196 196  
197 197  
198 -
199 199  == 2.4  Uplink Payload ==
200 200  
201 -
202 202  === 2.4.1 Uplink FPORT~=5, Device Status ===
203 203  
204 204  
... ... @@ -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]]
214 +[[image:1665301570342-765.png||_mstalt="294580"]]
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 -(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
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)(%%)  
282 282  
283 283  
284 284  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -287,6 +287,8 @@
287 287  |=(% 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
288 288  |=(% 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"]]
289 289  
290 +
291 +
290 290  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
291 291  
292 292  
... ... @@ -305,7 +305,7 @@
305 305  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
306 306  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
307 307  
308 -[[image:1665301636888-168.png]]
310 +[[image:1665301636888-168.png||_mstalt="298012"]]
309 309  
310 310  
311 311  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -335,12 +335,12 @@
335 335  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:
336 336  
337 337  
338 -[[image:1664502116362-706.png]]
340 +[[image:1664502116362-706.png||_mstalt="293306"]]
339 339  
340 340  
341 341  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
342 342  
343 -[[image:1664502166010-515.png]]
345 +[[image:1664502166010-515.png||_mstalt="291395"]]
344 344  
345 345  
346 346  
... ... @@ -363,6 +363,8 @@
363 363  * 3.40v ~~ 3.69v:  20% ~~ 40%
364 364  * < 3.39v:  0~~20%
365 365  
368 +
369 +
366 366  ==== (% style="color:blue" %)**MOD:**(%%) ====
367 367  
368 368  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -403,7 +403,6 @@
403 403  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
404 404  
405 405  
406 -
407 407  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
408 408  
409 409  
... ... @@ -419,14 +419,13 @@
419 419  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
420 420  
421 421  (% class="wikigeneratedid" %)
422 -[[image:1665301687277-443.png]]
425 +[[image:1665301687277-443.png||_mstalt="296140"]]
423 423  
424 424  
425 -
426 426  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
427 427  
428 428  
429 -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.
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.
430 430  
431 431  
432 432  (% style="color:red" %)**Note for this mode:**
... ... @@ -443,10 +443,9 @@
443 443  )))|4|4|2|1|1|1|1|1
444 444  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
445 445  
446 -[[image:image-20221009160309-2.png]]
448 +[[image:image-20221009160309-2.png||_mstalt="429312"]]
447 447  
448 448  
449 -
450 450  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
451 451  
452 452  
... ... @@ -471,7 +471,7 @@
471 471  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
472 472  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
473 473  
474 -[[image:1664502425687-834.png]]
475 +[[image:1664502425687-834.png||_mstalt="296738"]]
475 475  
476 476  
477 477  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -478,10 +478,12 @@
478 478  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
479 479  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
480 480  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
481 -* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
482 +* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
482 482  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
483 483  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
484 484  
486 +
487 +
485 485  === 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
486 486  
487 487  
... ... @@ -497,7 +497,7 @@
497 497  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
498 498  
499 499  (% class="wikigeneratedid" %)
500 -[[image:1667288597595-714.png||height="212" width="1151"]]
503 +[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
501 501  
502 502  
503 503  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -504,6 +504,8 @@
504 504  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
505 505  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
506 506  
510 +
511 +
507 507  === 2.4.7  Add Payload format in TTN V3 ===
508 508  
509 509  
... ... @@ -512,9 +512,10 @@
512 512  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
513 513  
514 514  
515 -[[image:1664502649601-895.png]]
520 +[[image:1664502649601-895.png||_mstalt="296985"]]
516 516  
517 517  
523 +
518 518  Add the decoder from this link: 
519 519  
520 520  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -521,10 +521,9 @@
521 521  
522 522  Save the change the uplink message will be parsed. As below:
523 523  
524 -[[image:1664502676891-606.png]]
530 +[[image:1664502676891-606.png||_mstalt="296673"]]
525 525  
526 526  
527 -
528 528  == 2.5 Integrate with Datacake ==
529 529  
530 530  
... ... @@ -533,10 +533,9 @@
533 533  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]]
534 534  
535 535  
536 -[[image:1664502695771-538.png]]
541 +[[image:1664502695771-538.png||_mstalt="297349"]]
537 537  
538 538  
539 -
540 540  == 2.6 Integrate with Tago ==
541 541  
542 542  
... ... @@ -545,26 +545,24 @@
545 545  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]]
546 546  
547 547  
548 -[[image:1664502715371-321.png]]
552 +[[image:1664502715371-321.png||_mstalt="292162"]]
549 549  
550 550  
551 -
552 552  == 2.7  Datalog Feature ==
553 553  
554 554  
555 555  total 273 entries,by default,
556 556  
557 -User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
560 +User can set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
558 558  
559 559  Example use case.
560 560  
561 -[[image:image-20221009234703-2.png||height="328" width="899"]]
564 +[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
562 562  
563 563  
564 -[[image:image-20221009234629-1.png||height="390" width="577"]]
567 +[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
565 565  
566 566  
567 -
568 568  == 2.8 Alarm Mode ==
569 569  
570 570  
... ... @@ -579,7 +579,7 @@
579 579  
580 580  
581 581  (((
582 -Two ways to exit alarm mode:
584 +**Two ways to exit alarm mode:**
583 583  )))
584 584  
585 585  * Server sends a downlink command to exit.
... ... @@ -590,14 +590,17 @@
590 590  )))
591 591  
592 592  
593 -
594 594  == 2.9 Transport Mode ==
595 595  
596 596  
597 597  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.
598 598  
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.
599 599  
600 600  
605 +
601 601  == 2.10 LED Status ==
602 602  
603 603  
... ... @@ -615,12 +615,14 @@
615 615  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
616 616  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
617 617  
623 +
624 +
618 618  == 2.11 Button Function ==
619 619  
620 620  
621 621  (% style="color:blue" %)**RESET button:**
622 622  
623 -[[image:1664502835802-546.png]]
630 +[[image:1664502835802-546.png||_mstalt="295061"]]
624 624  
625 625  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
626 626  
... ... @@ -627,7 +627,7 @@
627 627  
628 628  (% style="color:red" %)**RED button:**
629 629  
630 -[[image:1664502854406-763.png]]
637 +[[image:1664502854406-763.png||_mstalt="295568"]]
631 631  
632 632  
633 633  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -648,6 +648,8 @@
648 648  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
649 649  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
650 650  
658 +
659 +
651 651  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
652 652  
653 653  
... ... @@ -656,7 +656,6 @@
656 656  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
657 657  
658 658  
659 -
660 660  == 3.1 Access AT Command ==
661 661  
662 662  
... ... @@ -663,25 +663,23 @@
663 663  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.
664 664  
665 665  
666 -[[image:1664502999401-486.png]]
674 +[[image:1664502999401-486.png||_mstalt="296985"]]
667 667  
668 668  
669 669  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:
670 670  
671 671  
672 -[[image:1664503022490-662.png]]
680 +[[image:1664503022490-662.png||_mstalt="293332"]]
673 673  
674 674  
675 -[[image:1664503035713-500.png]]
683 +[[image:1664503035713-500.png||_mstalt="291096"]]
676 676  
677 677  
678 -[[image:1664503047675-651.png]]
686 +[[image:1664503047675-651.png||_mstalt="295386"]]
679 679  
680 680  
681 -
682 682  == 3.2 Command Set ==
683 683  
684 -
685 685  === 3.2.1 Set Transmit Interval ===
686 686  
687 687  
... ... @@ -699,7 +699,6 @@
699 699  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
700 700  
701 701  
702 -
703 703  === 3.2.2 Set Alarm Packet transmission interval ===
704 704  
705 705  
... ... @@ -717,7 +717,6 @@
717 717  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
718 718  
719 719  
720 -
721 721  === 3.2.3 Set Transport Mode Packet transmission interval ===
722 722  
723 723  
... ... @@ -735,7 +735,6 @@
735 735  (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
736 736  
737 737  
738 -
739 739  === 3.2.4 Exit Alarm ===
740 740  
741 741  
... ... @@ -748,7 +748,6 @@
748 748  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
749 749  
750 750  
751 -
752 752  === 3.2.5 Disable/Enable LED flash ===
753 753  
754 754  
... ... @@ -766,7 +766,6 @@
766 766  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
767 767  
768 768  
769 -
770 770  === 3.2.6 Disable/Enable Transport Mode ===
771 771  
772 772  
... ... @@ -784,7 +784,6 @@
784 784  (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
785 785  
786 786  
787 -
788 788  === 3.2.7 Set Positioning Mode ===
789 789  
790 790  
... ... @@ -811,9 +811,9 @@
811 811  
812 812  (% style="color:#037691" %)**cc:   **
813 813  
814 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
814 +* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
815 815  
816 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
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 817  
818 818  (% style="color:blue" %)**Example:**
819 819  
... ... @@ -831,7 +831,6 @@
831 831  (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
832 832  
833 833  
834 -
835 835  === 3.2.8 Set MAX GPS position time ===
836 836  
837 837  
... ... @@ -838,7 +838,7 @@
838 838  Set max positioning time, default is 150 seconds. TrackerD will try to get location info within this period. If fail to get position data within this time, TrackerD will use 000000 for latitude and longitude.
839 839  
840 840  
841 -If AT+FTIME=0. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.
840 +If **AT+FTIME=0**. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.
842 842  
843 843  
844 844  * (% style="color:blue" %)**AT Command:**
... ... @@ -853,7 +853,6 @@
853 853  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
854 854  
855 855  
856 -
857 857  === 3.2.9 Set PDOP value for GPS fix accuracy ===
858 858  
859 859  
... ... @@ -878,8 +878,9 @@
878 878  
879 879  
880 880  
881 -Disable/Enable the confirmation mode
879 +=== 3.2.10 Disable/Enable the confirmation mode ===
882 882  
881 +
883 883  * (% style="color:blue" %)**AT Command:**
884 884  
885 885  (% style="color:#037691" %)**AT+CFM=xx**
... ... @@ -897,10 +897,9 @@
897 897  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
898 898  
899 899  
899 +=== 3.2.11  Auto Send None-ACK messages ===
900 900  
901 -=== 3.2.10  Auto Send None-ACK messages ===
902 902  
903 -
904 904  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.
905 905  
906 906  
... ... @@ -916,13 +916,12 @@
916 916  
917 917  * (% style="color:blue" %)**Downlink Command: 0x34**
918 918  
919 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
917 +Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
920 920  
921 921  
920 +=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
922 922  
923 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
924 924  
925 -
926 926  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.
927 927  
928 928  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -929,19 +929,18 @@
929 929  
930 930  (% style="color:blue" %)**AT Command:**
931 931  
932 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
929 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
933 933  
934 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
931 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
935 935  
936 936  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
937 937  
938 -Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
935 +Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
939 939  
940 940  
938 +=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
941 941  
942 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
943 943  
944 -
945 945  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.
946 946  
947 947  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
... ... @@ -948,19 +948,18 @@
948 948  
949 949  (% style="color:blue" %)**AT Command:**
950 950  
951 - (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
947 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
952 952  
953 - (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
949 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
954 954  
955 955  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
956 956  
957 -Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
953 +Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
958 958  
959 959  
956 +=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
960 960  
961 -=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
962 962  
963 -
964 964  Users can use this feature to enable/disable Information printing.
965 965  
966 966  (% style="color:blue" %)**AT Command:**
... ... @@ -969,10 +969,9 @@
969 969  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
970 970  
971 971  
967 +=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
972 972  
973 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
974 974  
975 -
976 976  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
977 977  
978 978  (% style="color:blue" %)**AT Command:**
... ... @@ -985,7 +985,26 @@
985 985  Example: 0x24 01 ~/~/ Same as AT+CHE=1
986 986  
987 987  
982 +=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
988 988  
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 +
989 989  = 4. Setting for Different Scenarios =
990 990  
991 991  
... ... @@ -992,7 +992,6 @@
992 992  
993 993  = 5. Upload Firmware =
994 994  
995 -
996 996  == 5.1 Firmware Change Log ==
997 997  
998 998  
... ... @@ -999,7 +999,6 @@
999 999  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1000 1000  
1001 1001  
1002 -
1003 1003  == 5.2 How to upgrade firmware ==
1004 1004  
1005 1005  
... ... @@ -1020,10 +1020,10 @@
1020 1020  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1021 1021  
1022 1022  
1023 -[[image:1664503563660-578.png]]
1034 +[[image:1664503563660-578.png||_mstalt="296777"]]
1024 1024  
1025 1025  
1026 -[[image:1664503574618-659.png]]
1037 +[[image:1664503574618-659.png||_mstalt="297986"]]
1027 1027  
1028 1028  
1029 1029  
... ... @@ -1032,29 +1032,27 @@
1032 1032  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1033 1033  
1034 1034  
1035 -Users need to use below files:
1046 +**Users need to use below files:**
1036 1036  
1037 1037  boot_app0.bin @0e000
1038 1038  
1039 -ESP_LORA-eeprom-class.bin @ 0x10000
1050 +US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1040 1040  
1041 1041  
1042 -[[image:1664503593459-435.png]]
1053 +[[image:image-20221118105220-2.png||_mstalt="426608"]]
1043 1043  
1044 1044  
1045 1045  
1046 1046  After upgrade finish, it will show finish as below:
1047 1047  
1048 -[[image:1664503611848-385.png]]
1059 +[[image:image-20221118105402-4.png||_mstalt="427986"]]
1049 1049  
1050 1050  
1051 1051  
1052 1052  = 6. Developer Guide =
1053 1053  
1054 -
1055 1055  == 6.1 Compile Source Code ==
1056 1056  
1057 -
1058 1058  === 6.1.1 Set up ARDUINO compile environment ===
1059 1059  
1060 1060  
... ... @@ -1063,23 +1063,23 @@
1063 1063  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]]
1064 1064  
1065 1065  
1066 -[[image:1664503635019-941.png]]
1075 +[[image:1664503635019-941.png||_mstalt="294658"]]
1067 1067  
1068 1068  
1069 1069  
1070 1070  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1071 1071  
1072 -[[image:1664503715811-892.png]]
1081 +[[image:1664503715811-892.png||_mstalt="295698"]]
1073 1073  
1074 1074  
1075 1075  (% 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.
1076 1076  
1077 -[[image:image-20221024105643-1.png]]
1086 +[[image:image-20221024105643-1.png||_mstalt="428129"]]
1078 1078  
1079 1079  **~ Figure1**
1080 1080  
1081 1081  
1082 -[[image:image-20221024105643-2.png]]
1091 +[[image:image-20221024105643-2.png||_mstalt="428493"]]
1083 1083  
1084 1084   **Figure2**
1085 1085  
... ... @@ -1089,34 +1089,31 @@
1089 1089  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1090 1090  
1091 1091  
1092 -[[image:1664503752288-974.png]]
1101 +[[image:1664503752288-974.png||_mstalt="298194"]]
1093 1093  
1094 1094  
1095 -
1096 1096  == 6.2 Source Code ==
1097 1097  
1098 1098  
1099 1099  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1100 1100  
1101 -[[image:1664503794261-827.png]]
1109 +[[image:1664503794261-827.png||_mstalt="296387"]]
1102 1102  
1103 1103  
1104 1104  
1105 1105  * (% style="color:blue" %)**Click to upload**
1106 1106  
1107 -[[image:1664503808294-336.png]]
1115 +[[image:1664503808294-336.png||_mstalt="295711"]]
1108 1108  
1109 1109  
1110 1110  
1111 1111  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1112 1112  
1113 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1121 +[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1114 1114  
1115 1115  
1116 -
1117 1117  = 7.  FAQ =
1118 1118  
1119 -
1120 1120  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1121 1121  
1122 1122  
... ... @@ -1123,11 +1123,10 @@
1123 1123  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1124 1124  
1125 1125  
1126 -
1127 1127  == 7.2 What is the pin mapping for the USB program cable? ==
1128 1128  
1129 1129  
1130 -[[image:1664499635206-262.png]]
1135 +[[image:1664499635206-262.png||_mstalt="295360"]]
1131 1131  
1132 1132  
1133 1133  
... ... @@ -1142,9 +1142,10 @@
1142 1142  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1143 1143  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1144 1144  
1145 -== 7.3 Notes on using different serial port tools for TrackerD ==
1146 1146  
1147 1147  
1152 +== 7.3 Notes on using different serial port tools for TrackerD ==
1153 +
1148 1148  === 7.3.1  Serial port utility ===
1149 1149  
1150 1150  
... ... @@ -1152,18 +1152,16 @@
1152 1152  
1153 1153  Need to adjust the data stream to RTS/CTS on physical restart.
1154 1154  
1155 -
1156 1156  (% class="wikigeneratedid" %)
1157 -[[image:image-20221102140621-1.png]]
1162 +[[image:image-20221102140621-1.png||_mstalt="425672"]]
1158 1158  
1159 1159  
1165 +
1160 1160  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1161 1161  
1168 +[[image:image-20221102140638-2.png||_mstalt="428727"]]
1162 1162  
1163 -[[image:image-20221102140638-2.png]]
1164 1164  
1165 -
1166 -
1167 1167  === 7.3.2  SecureCRT ===
1168 1168  
1169 1169  
... ... @@ -1170,38 +1170,73 @@
1170 1170  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.
1171 1171  
1172 1172  
1173 -[[image:image-20221102140704-3.png]]
1177 +[[image:image-20221102140704-3.png||_mstalt="427076"]]
1174 1174  
1175 1175  
1176 -[[image:image-20221102140712-4.png]]
1180 +[[image:image-20221102140712-4.png||_mstalt="427089"]]
1177 1177  
1178 1178  
1179 -
1180 1180  === 7.3.3  PUTTY ===
1181 1181  
1182 1182  
1183 -[[image:image-20221102140748-5.png]]
1186 +[[image:image-20221102140748-5.png||_mstalt="430456"]]
1184 1184  
1185 1185  
1186 1186  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.
1187 1187  
1188 1188  
1189 -[[image:image-20221102140801-6.png]]
1192 +[[image:image-20221102140801-6.png||_mstalt="427466"]]
1190 1190  
1191 1191  
1195 +== 7.4 How to modify source code to compile different frequency band bin file? ==
1192 1192  
1193 -= 8  Trouble Shooting =
1194 1194  
1198 +(% class="box infomessage" %)
1199 +(((
1200 +(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1201 +See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1202 +)))
1195 1195  
1204 +**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1205 +
1206 +
1207 +[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1208 +
1209 +
1210 +
1211 +**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1212 +
1213 +
1214 +[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1215 +
1216 +
1217 +
1218 +**3. Compile the AS923_JP band, please refer to the intention shown**
1219 +
1220 +
1221 +[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1222 +
1223 +
1224 +
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 +
1227 +
1228 +[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1229 +
1230 +
1231 +[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1232 +
1233 +
1234 += 8  Trouble Shooting =
1235 +
1196 1196  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1197 1197  
1198 1198  
1199 1199  (((
1200 -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
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
1201 1201  )))
1202 1202  
1203 1203  
1204 -
1205 1205  == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1206 1206  
1207 1207  
... ... @@ -1210,19 +1210,106 @@
1210 1210  )))
1211 1211  
1212 1212  
1252 +== 8.3  Problem after Upgrading Firmware ==
1213 1213  
1214 -== 8.3  The reason why it has been restarted after upgrading（V.1.4.1） ==
1254 +=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1215 1215  
1216 1216  
1257 +**Error Output**
1258 +
1259 +
1260 +[[image:image-20221122100004-4.png||_mstalt="424606"]]
1261 +
1262 +
1217 1217  (((
1218 -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
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"]]
1219 1219  )))
1220 1220  
1221 1221  
1222 -[[image:image-20221107145243-1.png||height="695" width="443"]]
1270 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1223 1223  
1224 1224  
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
1225 1225  
1275 +
1276 +=== 8.3.3 "flash read err" after upgrade firmware ===
1277 +
1278 +
1279 +Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1280 +
1281 +
1282 +[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1283 +
1284 +
1285 +User need to upgrade again with below four files to solve this issue.
1286 +
1287 + [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1288 +
1289 + **Figure 2**
1290 +
1291 +
1292 +=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1293 +
1294 +
1295 +User might erase the entire flash include keys and default settings which cause this issue.
1296 +
1297 +After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1298 +
1299 +
1300 +[[image:image-20221122100004-3.png||_mstalt="424242"]]
1301 +
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.
1304 +
1305 +After AT+FDR. please set
1306 +
1307 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1308 +
1309 +* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1310 +
1311 +**Example:**
1312 +
1313 +AT+PDOP=7.00
1314 +
1315 +AT+FTIME=180
1316 +
1317 +AT+DEUI=70B3D57ED0053981  
1318 +
1319 +AT+APPEUI=D23345667BCBCCAF
1320 +
1321 +AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
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 +== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1331 +
1332 +
1333 +Please download version 1.4.2 again
1334 +
1335 +
1336 +== 8.5  How to deal with unsuccessful GPS positioning? ==
1337 +
1338 +
1339 +1） Make Sure the device is in Open Area where can see the sky.
1340 +
1341 +2)  Set PDOP to a higher value.
1342 +
1343 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1344 +
1345 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1346 +
1347 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1348 +
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 +
1351 +
1226 1226  = 9.  Order Info =
1227 1227  
1228 1228  
... ... @@ -1231,13 +1231,21 @@
1231 1231  (% style="color:blue" %)**XXX**(%%): The default frequency band
1232 1232  
1233 1233  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1360 +
1234 1234  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1362 +
1235 1235  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1364 +
1236 1236  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1366 +
1237 1237  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1368 +
1238 1238  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1370 +
1239 1239  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1240 1240  
1373 +
1374 +
1241 1241  = 10.  Packing Info =
1242 1242  
1243 1243  
... ... @@ -1244,24 +1244,32 @@
1244 1244  (% style="color:#037691" %)**Package Includes**:
1245 1245  
1246 1246  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1381 +
1247 1247  * USB recharge & program cable x 1
1248 1248  
1249 1249  (% style="color:#037691" %)**Dimensions and Weight**:
1250 1250  
1251 1251  * Device Size: 85 x 48 x 15 mm
1387 +
1252 1252  * Weight: 50g
1253 1253  
1390 +
1391 +
1254 1254  = 11. Support =
1255 1255  
1256 1256  
1257 1257  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1396 +
1258 1258  * 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]].
1259 1259  
1399 +
1400 +
1260 1260  = 12.  Reference =
1261 1261  
1262 1262  
1263 1263  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1405 +
1264 1264  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1265 -* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1266 1266  
1267 -
1408 +* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1409 +)))
image-20221116111844-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +15.8 KB
Content
image-20221116111844-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +32.6 KB
Content
image-20221116111844-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +37.0 KB
Content
image-20221116111844-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +96.8 KB
Content
image-20221116111844-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +78.0 KB
Content
image-20221118104359-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +38.0 KB
Content
image-20221118105220-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +40.2 KB
Content
image-20221118105249-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +40.2 KB
Content
image-20221118105402-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +43.7 KB
Content
image-20221122100004-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +18.0 KB
Content
image-20221122100004-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +127.2 KB
Content
image-20221122100004-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +12.5 KB
Content
image-20221122100004-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20221128102938-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +41.3 KB
Content
image-20221128103040-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +19.2 KB
Content
image-20221128110503-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +45.6 KB
Content
image-20221128111443-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +15.6 KB
Content