Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 114.1
edited by Bei Jinggeng
on 2022/11/15 14:30
Change comment: There is no comment for this version
To version 155.4
edited by Xiaoling
on 2022/11/24 17:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Xiaoling
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  
... ... @@ -98,6 +98,7 @@
98 98  * Tracking: max: 38mA
99 99  
100 100  
96 +
101 101  == 1.3  Features ==
102 102  
103 103  
... ... @@ -117,6 +117,7 @@
117 117  * Datalog
118 118  
119 119  
116 +
120 120  == 1.4  Applications ==
121 121  
122 122  
... ... @@ -124,9 +124,9 @@
124 124  * Human tracking
125 125  
126 126  
124 +
127 127  = 2.  Use TrackerD =
128 128  
129 -
130 130  == 2.1 How it works? ==
131 131  
132 132  
... ... @@ -133,7 +133,6 @@
133 133  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.
134 134  
135 135  
136 -
137 137  == 2.2 Quick guide to connect to LoRaWAN server ==
138 138  
139 139  
... ... @@ -140,7 +140,7 @@
140 140  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. 
141 141  
142 142  
143 -[[image:1664501652064-326.png]]
139 +[[image:1664501652064-326.png||_mstalt="293306"]]
144 144  
145 145  
146 146  
... ... @@ -152,7 +152,7 @@
152 152  Each TrackerD is shipped with a sticker with the default device EUI as below:
153 153  
154 154  
155 -[[image:1664501677253-891.png]]
151 +[[image:1664501677253-891.png||_mstalt="296569"]]
156 156  
157 157  
158 158  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -161,14 +161,14 @@
161 161  **__Add APP EUI in the application:__**
162 162  
163 163  
164 -[[image:1664501711466-918.png]]
160 +[[image:1664501711466-918.png||_mstalt="295828"]]
165 165  
166 166  
167 167  
168 -[[image:1664501721248-725.png]]
164 +[[image:1664501721248-725.png||_mstalt="294450"]]
169 169  
170 170  
171 -[[image:1664501734705-405.png]]
167 +[[image:1664501734705-405.png||_mstalt="293306"]]
172 172  
173 173  
174 174  
... ... @@ -175,17 +175,20 @@
175 175  **__Add APP KEY and DEV EUI:__**
176 176  
177 177  
178 -[[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"]]
179 179  
180 180  
181 181  
182 -(% 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.
183 183  
180 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
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.
182 +[[image:1664502835802-546.png||_mstalt="295061"]]
186 186  
187 187  
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.
188 188  
187 +
189 189  == 2.3  Positioning Mode(SMOD) ==
190 190  
191 191  
... ... @@ -198,10 +198,8 @@
198 198  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
199 199  
200 200  
201 -
202 202  == 2.4  Uplink Payload ==
203 203  
204 -
205 205  === 2.4.1 Uplink FPORT~=5, Device Status ===
206 206  
207 207  
... ... @@ -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]]
214 +[[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)(%%)  
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)(%%)  
285 285  
286 286  
287 287  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -291,6 +291,7 @@
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 293  
291 +
294 294  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
295 295  
296 296  
... ... @@ -309,7 +309,7 @@
309 309  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
310 310  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
311 311  
312 -[[image:1665301636888-168.png]]
310 +[[image:1665301636888-168.png||_mstalt="298012"]]
313 313  
314 314  
315 315  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -318,7 +318,6 @@
318 318  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
319 319  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
320 320  
321 -
322 322  ==== (% style="color:blue" %)**FLAG:**(%%) ====
323 323  
324 324  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
... ... @@ -340,12 +340,12 @@
340 340  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:
341 341  
342 342  
343 -[[image:1664502116362-706.png]]
340 +[[image:1664502116362-706.png||_mstalt="293306"]]
344 344  
345 345  
346 346  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
347 347  
348 -[[image:1664502166010-515.png]]
345 +[[image:1664502166010-515.png||_mstalt="291395"]]
349 349  
350 350  
351 351  
... ... @@ -369,6 +369,7 @@
369 369  * < 3.39v:  0~~20%
370 370  
371 371  
369 +
372 372  ==== (% style="color:blue" %)**MOD:**(%%) ====
373 373  
374 374  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -409,7 +409,6 @@
409 409  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
410 410  
411 411  
412 -
413 413  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
414 414  
415 415  
... ... @@ -425,14 +425,13 @@
425 425  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
426 426  
427 427  (% class="wikigeneratedid" %)
428 -[[image:1665301687277-443.png]]
425 +[[image:1665301687277-443.png||_mstalt="296140"]]
429 429  
430 430  
431 -
432 432  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
433 433  
434 434  
435 -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.
436 436  
437 437  
438 438  (% style="color:red" %)**Note for this mode:**
... ... @@ -449,10 +449,9 @@
449 449  )))|4|4|2|1|1|1|1|1
450 450  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
451 451  
452 -[[image:image-20221009160309-2.png]]
448 +[[image:image-20221009160309-2.png||_mstalt="429312"]]
453 453  
454 454  
455 -
456 456  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
457 457  
458 458  
... ... @@ -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]]
475 +[[image:1664502425687-834.png||_mstalt="296738"]]
481 481  
482 482  
483 483  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -489,6 +489,7 @@
489 489  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
490 490  
491 491  
487 +
492 492  === 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
493 493  
494 494  
... ... @@ -504,7 +504,7 @@
504 504  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
505 505  
506 506  (% class="wikigeneratedid" %)
507 -[[image:1667288597595-714.png||height="212" width="1151"]]
503 +[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
508 508  
509 509  
510 510  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -512,6 +512,7 @@
512 512  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
513 513  
514 514  
511 +
515 515  === 2.4.7  Add Payload format in TTN V3 ===
516 516  
517 517  
... ... @@ -520,9 +520,10 @@
520 520  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
521 521  
522 522  
523 -[[image:1664502649601-895.png]]
520 +[[image:1664502649601-895.png||_mstalt="296985"]]
524 524  
525 525  
523 +
526 526  Add the decoder from this link: 
527 527  
528 528  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -529,10 +529,9 @@
529 529  
530 530  Save the change the uplink message will be parsed. As below:
531 531  
532 -[[image:1664502676891-606.png]]
530 +[[image:1664502676891-606.png||_mstalt="296673"]]
533 533  
534 534  
535 -
536 536  == 2.5 Integrate with Datacake ==
537 537  
538 538  
... ... @@ -541,10 +541,9 @@
541 541  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]]
542 542  
543 543  
544 -[[image:1664502695771-538.png]]
541 +[[image:1664502695771-538.png||_mstalt="297349"]]
545 545  
546 546  
547 -
548 548  == 2.6 Integrate with Tago ==
549 549  
550 550  
... ... @@ -553,26 +553,24 @@
553 553  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]]
554 554  
555 555  
556 -[[image:1664502715371-321.png]]
552 +[[image:1664502715371-321.png||_mstalt="292162"]]
557 557  
558 558  
559 -
560 560  == 2.7  Datalog Feature ==
561 561  
562 562  
563 563  total 273 entries,by default,
564 564  
565 -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.
566 566  
567 567  Example use case.
568 568  
569 -[[image:image-20221009234703-2.png||height="328" width="899"]]
564 +[[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"]]
567 +[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
573 573  
574 574  
575 -
576 576  == 2.8 Alarm Mode ==
577 577  
578 578  
... ... @@ -587,7 +587,7 @@
587 587  
588 588  
589 589  (((
590 -Two ways to exit alarm mode:
584 +**Two ways to exit alarm mode:**
591 591  )))
592 592  
593 593  * Server sends a downlink command to exit.
... ... @@ -598,14 +598,17 @@
598 598  )))
599 599  
600 600  
601 -
602 602  == 2.9 Transport Mode ==
603 603  
604 604  
605 605  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.
606 606  
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.
607 607  
608 608  
605 +
609 609  == 2.10 LED Status ==
610 610  
611 611  
... ... @@ -624,12 +624,13 @@
624 624  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
625 625  
626 626  
624 +
627 627  == 2.11 Button Function ==
628 628  
629 629  
630 630  (% style="color:blue" %)**RESET button:**
631 631  
632 -[[image:1664502835802-546.png]]
630 +[[image:1664502835802-546.png||_mstalt="295061"]]
633 633  
634 634  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
635 635  
... ... @@ -636,7 +636,7 @@
636 636  
637 637  (% style="color:red" %)**RED button:**
638 638  
639 -[[image:1664502854406-763.png]]
637 +[[image:1664502854406-763.png||_mstalt="295568"]]
640 640  
641 641  
642 642  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -646,6 +646,7 @@
646 646  |(% 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.
647 647  
648 648  
647 +
649 649  == 2.12 USB Port Function ==
650 650  
651 651  
... ... @@ -657,6 +657,7 @@
657 657  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
658 658  
659 659  
659 +
660 660  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
661 661  
662 662  
... ... @@ -665,7 +665,6 @@
665 665  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
666 666  
667 667  
668 -
669 669  == 3.1 Access AT Command ==
670 670  
671 671  
... ... @@ -672,25 +672,23 @@
672 672  TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below.
673 673  
674 674  
675 -[[image:1664502999401-486.png]]
674 +[[image:1664502999401-486.png||_mstalt="296985"]]
676 676  
677 677  
678 678  In PC, User needs to set serial tool baud rate to (% style="color:green" %)**115200**(%%) to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands:
679 679  
680 680  
681 -[[image:1664503022490-662.png]]
680 +[[image:1664503022490-662.png||_mstalt="293332"]]
682 682  
683 683  
684 -[[image:1664503035713-500.png]]
683 +[[image:1664503035713-500.png||_mstalt="291096"]]
685 685  
686 686  
687 -[[image:1664503047675-651.png]]
686 +[[image:1664503047675-651.png||_mstalt="295386"]]
688 688  
689 689  
690 -
691 691  == 3.2 Command Set ==
692 692  
693 -
694 694  === 3.2.1 Set Transmit Interval ===
695 695  
696 696  
... ... @@ -708,7 +708,6 @@
708 708  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
709 709  
710 710  
711 -
712 712  === 3.2.2 Set Alarm Packet transmission interval ===
713 713  
714 714  
... ... @@ -726,7 +726,6 @@
726 726  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
727 727  
728 728  
729 -
730 730  === 3.2.3 Set Transport Mode Packet transmission interval ===
731 731  
732 732  
... ... @@ -744,7 +744,6 @@
744 744  (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
745 745  
746 746  
747 -
748 748  === 3.2.4 Exit Alarm ===
749 749  
750 750  
... ... @@ -757,7 +757,6 @@
757 757  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
758 758  
759 759  
760 -
761 761  === 3.2.5 Disable/Enable LED flash ===
762 762  
763 763  
... ... @@ -775,7 +775,6 @@
775 775  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
776 776  
777 777  
778 -
779 779  === 3.2.6 Disable/Enable Transport Mode ===
780 780  
781 781  
... ... @@ -793,7 +793,6 @@
793 793  (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
794 794  
795 795  
796 -
797 797  === 3.2.7 Set Positioning Mode ===
798 798  
799 799  
... ... @@ -820,9 +820,9 @@
820 820  
821 821  (% style="color:#037691" %)**cc:   **
822 822  
823 -* (% 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 
824 824  
825 -* (% 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(%%))  
826 826  
827 827  (% style="color:blue" %)**Example:**
828 828  
... ... @@ -840,7 +840,6 @@
840 840  (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
841 841  
842 842  
843 -
844 844  === 3.2.8 Set MAX GPS position time ===
845 845  
846 846  
... ... @@ -847,7 +847,7 @@
847 847  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.
848 848  
849 849  
850 -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.
851 851  
852 852  
853 853  * (% style="color:blue" %)**AT Command:**
... ... @@ -862,7 +862,6 @@
862 862  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
863 863  
864 864  
865 -
866 866  === 3.2.9 Set PDOP value for GPS fix accuracy ===
867 867  
868 868  
... ... @@ -887,8 +887,9 @@
887 887  
888 888  
889 889  
890 -Disable/Enable the confirmation mode
879 +=== 3.2.10 Disable/Enable the confirmation mode ===
891 891  
881 +
892 892  * (% style="color:blue" %)**AT Command:**
893 893  
894 894  (% style="color:#037691" %)**AT+CFM=xx**
... ... @@ -906,10 +906,9 @@
906 906  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
907 907  
908 908  
899 +=== 3.2.11  Auto Send None-ACK messages ===
909 909  
910 -=== 3.2.10  Auto Send None-ACK messages ===
911 911  
912 -
913 913  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 914  
915 915  
... ... @@ -925,13 +925,12 @@
925 925  
926 926  * (% style="color:blue" %)**Downlink Command: 0x34**
927 927  
928 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
917 +Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
929 929  
930 930  
920 +=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
931 931  
932 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
933 933  
934 -
935 935  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.
936 936  
937 937  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -938,19 +938,18 @@
938 938  
939 939  (% style="color:blue" %)**AT Command:**
940 940  
941 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
929 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
942 942  
943 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
931 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
944 944  
945 945  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
946 946  
947 -Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
935 +Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
948 948  
949 949  
938 +=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
950 950  
951 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
952 952  
953 -
954 954  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.
955 955  
956 956  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
... ... @@ -957,19 +957,18 @@
957 957  
958 958  (% style="color:blue" %)**AT Command:**
959 959  
960 - (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
947 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
961 961  
962 - (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
949 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
963 963  
964 964  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
965 965  
966 -Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
953 +Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
967 967  
968 968  
956 +=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
969 969  
970 -=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
971 971  
972 -
973 973  Users can use this feature to enable/disable Information printing.
974 974  
975 975  (% style="color:blue" %)**AT Command:**
... ... @@ -978,10 +978,9 @@
978 978  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
979 979  
980 980  
967 +=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
981 981  
982 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
983 983  
984 -
985 985  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
986 986  
987 987  (% style="color:blue" %)**AT Command:**
... ... @@ -994,7 +994,26 @@
994 994  Example: 0x24 01 ~/~/ Same as AT+CHE=1
995 995  
996 996  
982 +=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
997 997  
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 +
998 998  = 4. Setting for Different Scenarios =
999 999  
1000 1000  
... ... @@ -1001,7 +1001,6 @@
1001 1001  
1002 1002  = 5. Upload Firmware =
1003 1003  
1004 -
1005 1005  == 5.1 Firmware Change Log ==
1006 1006  
1007 1007  
... ... @@ -1008,7 +1008,6 @@
1008 1008  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1009 1009  
1010 1010  
1011 -
1012 1012  == 5.2 How to upgrade firmware ==
1013 1013  
1014 1014  
... ... @@ -1029,10 +1029,10 @@
1029 1029  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1030 1030  
1031 1031  
1032 -[[image:1664503563660-578.png]]
1034 +[[image:1664503563660-578.png||_mstalt="296777"]]
1033 1033  
1034 1034  
1035 -[[image:1664503574618-659.png]]
1037 +[[image:1664503574618-659.png||_mstalt="297986"]]
1036 1036  
1037 1037  
1038 1038  
... ... @@ -1041,29 +1041,27 @@
1041 1041  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1042 1042  
1043 1043  
1044 -Users need to use below files:
1046 +**Users need to use below files:**
1045 1045  
1046 1046  boot_app0.bin @0e000
1047 1047  
1048 -ESP_LORA-eeprom-class.bin @ 0x10000
1050 +US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1049 1049  
1050 1050  
1051 -[[image:1664503593459-435.png]]
1053 +[[image:image-20221118105220-2.png||_mstalt="426608"]]
1052 1052  
1053 1053  
1054 1054  
1055 1055  After upgrade finish, it will show finish as below:
1056 1056  
1057 -[[image:1664503611848-385.png]]
1059 +[[image:image-20221118105402-4.png||_mstalt="427986"]]
1058 1058  
1059 1059  
1060 1060  
1061 1061  = 6. Developer Guide =
1062 1062  
1063 -
1064 1064  == 6.1 Compile Source Code ==
1065 1065  
1066 -
1067 1067  === 6.1.1 Set up ARDUINO compile environment ===
1068 1068  
1069 1069  
... ... @@ -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]]
1075 +[[image:1664503635019-941.png||_mstalt="294658"]]
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]]
1081 +[[image:1664503715811-892.png||_mstalt="295698"]]
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]]
1086 +[[image:image-20221024105643-1.png||_mstalt="428129"]]
1087 1087  
1088 1088  **~ Figure1**
1089 1089  
1090 1090  
1091 -[[image:image-20221024105643-2.png]]
1091 +[[image:image-20221024105643-2.png||_mstalt="428493"]]
1092 1092  
1093 1093   **Figure2**
1094 1094  
... ... @@ -1098,34 +1098,31 @@
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]]
1101 +[[image:1664503752288-974.png||_mstalt="298194"]]
1102 1102  
1103 1103  
1104 -
1105 1105  == 6.2 Source Code ==
1106 1106  
1107 1107  
1108 1108  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1109 1109  
1110 -[[image:1664503794261-827.png]]
1109 +[[image:1664503794261-827.png||_mstalt="296387"]]
1111 1111  
1112 1112  
1113 1113  
1114 1114  * (% style="color:blue" %)**Click to upload**
1115 1115  
1116 -[[image:1664503808294-336.png]]
1115 +[[image:1664503808294-336.png||_mstalt="295711"]]
1117 1117  
1118 1118  
1119 1119  
1120 1120  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1121 1121  
1122 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1121 +[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1123 1123  
1124 1124  
1125 -
1126 1126  = 7.  FAQ =
1127 1127  
1128 -
1129 1129  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1130 1130  
1131 1131  
... ... @@ -1132,11 +1132,10 @@
1132 1132  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1133 1133  
1134 1134  
1135 -
1136 1136  == 7.2 What is the pin mapping for the USB program cable? ==
1137 1137  
1138 1138  
1139 -[[image:1664499635206-262.png]]
1135 +[[image:1664499635206-262.png||_mstalt="295360"]]
1140 1140  
1141 1141  
1142 1142  
... ... @@ -1152,9 +1152,9 @@
1152 1152  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1153 1153  
1154 1154  
1151 +
1155 1155  == 7.3 Notes on using different serial port tools for TrackerD ==
1156 1156  
1157 -
1158 1158  === 7.3.1  Serial port utility ===
1159 1159  
1160 1160  
... ... @@ -1162,18 +1162,16 @@
1162 1162  
1163 1163  Need to adjust the data stream to RTS/CTS on physical restart.
1164 1164  
1165 -
1166 1166  (% class="wikigeneratedid" %)
1167 -[[image:image-20221102140621-1.png]]
1162 +[[image:image-20221102140621-1.png||_mstalt="425672"]]
1168 1168  
1169 1169  
1165 +
1170 1170  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1171 1171  
1168 +[[image:image-20221102140638-2.png||_mstalt="428727"]]
1172 1172  
1173 -[[image:image-20221102140638-2.png]]
1174 1174  
1175 -
1176 -
1177 1177  === 7.3.2  SecureCRT ===
1178 1178  
1179 1179  
... ... @@ -1180,38 +1180,73 @@
1180 1180  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.
1181 1181  
1182 1182  
1183 -[[image:image-20221102140704-3.png]]
1177 +[[image:image-20221102140704-3.png||_mstalt="427076"]]
1184 1184  
1185 1185  
1186 -[[image:image-20221102140712-4.png]]
1180 +[[image:image-20221102140712-4.png||_mstalt="427089"]]
1187 1187  
1188 1188  
1189 -
1190 1190  === 7.3.3  PUTTY ===
1191 1191  
1192 1192  
1193 -[[image:image-20221102140748-5.png]]
1186 +[[image:image-20221102140748-5.png||_mstalt="430456"]]
1194 1194  
1195 1195  
1196 1196  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.
1197 1197  
1198 1198  
1199 -[[image:image-20221102140801-6.png]]
1192 +[[image:image-20221102140801-6.png||_mstalt="427466"]]
1200 1200  
1201 1201  
1195 +== 7.4 How to modify source code to compile different frequency band bin file? ==
1202 1202  
1203 -= 8  Trouble Shooting =
1204 1204  
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 +)))
1205 1205  
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 +
1206 1206  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1207 1207  
1208 1208  
1209 1209  (((
1210 -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
1211 1211  )))
1212 1212  
1213 1213  
1214 -
1215 1215  == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1216 1216  
1217 1217  
... ... @@ -1220,23 +1220,106 @@
1220 1220  )))
1221 1221  
1222 1222  
1252 +== 8.3  Problem after Upgrading Firmware ==
1223 1223  
1224 -== 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 ===
1225 1225  
1226 1226  
1257 +**Error Output**
1258 +
1259 +
1260 +[[image:image-20221122100004-4.png||_mstalt="424606"]]
1261 +
1262 +
1227 1227  (((
1228 -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"]]
1229 1229  )))
1230 1230  
1231 1231  
1232 -[[image:image-20221107145243-1.png||height="695" width="443"]]
1270 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1233 1233  
1234 1234  
1235 -== 8.4 If the device's led light is always on when upgrading（since firmware 1.4.1） ==
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
1236 1236  
1237 -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.
1238 1238  
1276 +=== 8.3.3 "flash read err" after upgrade firmware ===
1239 1239  
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 +
1240 1240  = 9.  Order Info =
1241 1241  
1242 1242  
... ... @@ -1245,14 +1245,21 @@
1245 1245  (% style="color:blue" %)**XXX**(%%): The default frequency band
1246 1246  
1247 1247  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1360 +
1248 1248  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1362 +
1249 1249  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1364 +
1250 1250  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1366 +
1251 1251  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1368 +
1252 1252  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1370 +
1253 1253  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1254 1254  
1255 1255  
1374 +
1256 1256  = 10.  Packing Info =
1257 1257  
1258 1258  
... ... @@ -1259,26 +1259,32 @@
1259 1259  (% style="color:#037691" %)**Package Includes**:
1260 1260  
1261 1261  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1381 +
1262 1262  * USB recharge & program cable x 1
1263 1263  
1264 1264  (% style="color:#037691" %)**Dimensions and Weight**:
1265 1265  
1266 1266  * Device Size: 85 x 48 x 15 mm
1387 +
1267 1267  * Weight: 50g
1268 1268  
1269 1269  
1391 +
1270 1270  = 11. Support =
1271 1271  
1272 1272  
1273 1273  * 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 +
1274 1274  * 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]].
1275 1275  
1276 1276  
1400 +
1277 1277  = 12.  Reference =
1278 1278  
1279 1279  
1280 1280  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1405 +
1281 1281  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1282 -* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1283 1283  
1284 -
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