Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 113.4
edited by Xiaoling
on 2022/11/09 15:51
Change comment: There is no comment for this version
To version 160.1
edited by Bei Jinggeng
on 2022/11/28 11:18
Change comment: Uploaded new attachment "image-20221128111850-5.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  
... ... @@ -129,7 +129,6 @@
129 129  
130 130  = 2.  Use TrackerD =
131 131  
132 -
133 133  == 2.1 How it works? ==
134 134  
135 135  
... ... @@ -136,7 +136,6 @@
136 136  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.
137 137  
138 138  
139 -
140 140  == 2.2 Quick guide to connect to LoRaWAN server ==
141 141  
142 142  
... ... @@ -143,7 +143,7 @@
143 143  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. 
144 144  
145 145  
146 -[[image:1664501652064-326.png]]
139 +[[image:1664501652064-326.png||_mstalt="293306"]]
147 147  
148 148  
149 149  
... ... @@ -155,7 +155,7 @@
155 155  Each TrackerD is shipped with a sticker with the default device EUI as below:
156 156  
157 157  
158 -[[image:1664501677253-891.png]]
151 +[[image:1664501677253-891.png||_mstalt="296569"]]
159 159  
160 160  
161 161  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -164,14 +164,14 @@
164 164  **__Add APP EUI in the application:__**
165 165  
166 166  
167 -[[image:1664501711466-918.png]]
160 +[[image:1664501711466-918.png||_mstalt="295828"]]
168 168  
169 169  
170 170  
171 -[[image:1664501721248-725.png]]
164 +[[image:1664501721248-725.png||_mstalt="294450"]]
172 172  
173 173  
174 -[[image:1664501734705-405.png]]
167 +[[image:1664501734705-405.png||_mstalt="293306"]]
175 175  
176 176  
177 177  
... ... @@ -178,18 +178,20 @@
178 178  **__Add APP KEY and DEV EUI:__**
179 179  
180 180  
181 -[[image:1664501784668-703.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"]]
182 182  
183 183  
184 184  
178 +(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
185 185  
186 -(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
180 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
187 187  
182 +[[image:1664502835802-546.png||_mstalt="295061"]]
188 188  
184 +
189 189  (% 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.
190 190  
191 191  
192 -
193 193  == 2.3  Positioning Mode(SMOD) ==
194 194  
195 195  
... ... @@ -202,10 +202,8 @@
202 202  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
203 203  
204 204  
205 -
206 206  == 2.4  Uplink Payload ==
207 207  
208 -
209 209  === 2.4.1 Uplink FPORT~=5, Device Status ===
210 210  
211 211  
... ... @@ -218,7 +218,7 @@
218 218  |=(% 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
219 219  |=(% 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
220 220  
221 -[[image:1665301570342-765.png]]
214 +[[image:1665301570342-765.png||_mstalt="294580"]]
222 222  
223 223  
224 224  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -285,7 +285,7 @@
285 285  
286 286  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
287 287  
288 -(% 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)(%%)  
289 289  
290 290  
291 291  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
... ... @@ -314,7 +314,7 @@
314 314  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
315 315  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
316 316  
317 -[[image:1665301636888-168.png]]
310 +[[image:1665301636888-168.png||_mstalt="298012"]]
318 318  
319 319  
320 320  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -323,8 +323,6 @@
323 323  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
324 324  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
325 325  
326 -
327 -
328 328  ==== (% style="color:blue" %)**FLAG:**(%%) ====
329 329  
330 330  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
... ... @@ -346,12 +346,12 @@
346 346  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:
347 347  
348 348  
349 -[[image:1664502116362-706.png]]
340 +[[image:1664502116362-706.png||_mstalt="293306"]]
350 350  
351 351  
352 352  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
353 353  
354 -[[image:1664502166010-515.png]]
345 +[[image:1664502166010-515.png||_mstalt="291395"]]
355 355  
356 356  
357 357  
... ... @@ -416,7 +416,6 @@
416 416  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
417 417  
418 418  
419 -
420 420  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
421 421  
422 422  
... ... @@ -432,14 +432,13 @@
432 432  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
433 433  
434 434  (% class="wikigeneratedid" %)
435 -[[image:1665301687277-443.png]]
425 +[[image:1665301687277-443.png||_mstalt="296140"]]
436 436  
437 437  
438 -
439 439  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
440 440  
441 441  
442 -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.
443 443  
444 444  
445 445  (% style="color:red" %)**Note for this mode:**
... ... @@ -456,10 +456,9 @@
456 456  )))|4|4|2|1|1|1|1|1
457 457  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
458 458  
459 -[[image:image-20221009160309-2.png]]
448 +[[image:image-20221009160309-2.png||_mstalt="429312"]]
460 460  
461 461  
462 -
463 463  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
464 464  
465 465  
... ... @@ -484,7 +484,7 @@
484 484  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
485 485  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
486 486  
487 -[[image:1664502425687-834.png]]
475 +[[image:1664502425687-834.png||_mstalt="296738"]]
488 488  
489 489  
490 490  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -491,7 +491,7 @@
491 491  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
492 492  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
493 493  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
494 -* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
482 +* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
495 495  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
496 496  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
497 497  
... ... @@ -512,7 +512,7 @@
512 512  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
513 513  
514 514  (% class="wikigeneratedid" %)
515 -[[image:1667288597595-714.png||height="212" width="1151"]]
503 +[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
516 516  
517 517  
518 518  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -529,9 +529,10 @@
529 529  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
530 530  
531 531  
532 -[[image:1664502649601-895.png]]
520 +[[image:1664502649601-895.png||_mstalt="296985"]]
533 533  
534 534  
523 +
535 535  Add the decoder from this link: 
536 536  
537 537  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -538,10 +538,9 @@
538 538  
539 539  Save the change the uplink message will be parsed. As below:
540 540  
541 -[[image:1664502676891-606.png]]
530 +[[image:1664502676891-606.png||_mstalt="296673"]]
542 542  
543 543  
544 -
545 545  == 2.5 Integrate with Datacake ==
546 546  
547 547  
... ... @@ -550,10 +550,9 @@
550 550  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]]
551 551  
552 552  
553 -[[image:1664502695771-538.png]]
541 +[[image:1664502695771-538.png||_mstalt="297349"]]
554 554  
555 555  
556 -
557 557  == 2.6 Integrate with Tago ==
558 558  
559 559  
... ... @@ -562,26 +562,24 @@
562 562  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]]
563 563  
564 564  
565 -[[image:1664502715371-321.png]]
552 +[[image:1664502715371-321.png||_mstalt="292162"]]
566 566  
567 567  
568 -
569 569  == 2.7  Datalog Feature ==
570 570  
571 571  
572 572  total 273 entries,by default,
573 573  
574 -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.
575 575  
576 576  Example use case.
577 577  
578 -[[image:image-20221009234703-2.png||height="328" width="899"]]
564 +[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
579 579  
580 580  
581 -[[image:image-20221009234629-1.png||height="390" width="577"]]
567 +[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
582 582  
583 583  
584 -
585 585  == 2.8 Alarm Mode ==
586 586  
587 587  
... ... @@ -596,7 +596,7 @@
596 596  
597 597  
598 598  (((
599 -Two ways to exit alarm mode:
584 +**Two ways to exit alarm mode:**
600 600  )))
601 601  
602 602  * Server sends a downlink command to exit.
... ... @@ -607,24 +607,27 @@
607 607  )))
608 608  
609 609  
610 -
611 611  == 2.9 Transport Mode ==
612 612  
613 613  
614 614  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.
615 615  
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.
616 616  
617 617  
605 +
618 618  == 2.10 LED Status ==
619 619  
620 620  
621 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
609 +(% border="1.5" style="background-color:#ffffcc; width:500px" %)
622 622  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
623 623  |(% style="width:157px" %)**Power On**|(% style="width:271px" %)(% style="color:blue" %)**BLUE, **(% style="color:red" %)**RED , **(% style="color:green" %)**Green** flash once|(% style="width:202px" %)N/A
624 624  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
625 625  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
626 626  |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
627 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
615 +|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
628 628  |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
629 629  |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
630 630  |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
... ... @@ -639,7 +639,7 @@
639 639  
640 640  (% style="color:blue" %)**RESET button:**
641 641  
642 -[[image:1664502835802-546.png]]
630 +[[image:1664502835802-546.png||_mstalt="295061"]]
643 643  
644 644  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
645 645  
... ... @@ -646,12 +646,12 @@
646 646  
647 647  (% style="color:red" %)**RED button:**
648 648  
649 -[[image:1664502854406-763.png]]
637 +[[image:1664502854406-763.png||_mstalt="295568"]]
650 650  
651 651  
652 -(% border="1" style="background-color:#ffffcc; color:green; width:510px" %)
640 +(% border="1" style="background-color:#ffffcc; width:510px" %)
653 653  |=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
654 -|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode.  See [[Alarm Mode>>||anchor="H2.6AlarmMode"]]
642 +|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode.  See [[Alarm Mode>>||anchor="H2.8AlarmMode"]]
655 655  |(% 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
656 656  |(% 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.
657 657  
... ... @@ -677,7 +677,6 @@
677 677  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
678 678  
679 679  
680 -
681 681  == 3.1 Access AT Command ==
682 682  
683 683  
... ... @@ -684,25 +684,23 @@
684 684  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.
685 685  
686 686  
687 -[[image:1664502999401-486.png]]
674 +[[image:1664502999401-486.png||_mstalt="296985"]]
688 688  
689 689  
690 690  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:
691 691  
692 692  
693 -[[image:1664503022490-662.png]]
680 +[[image:1664503022490-662.png||_mstalt="293332"]]
694 694  
695 695  
696 -[[image:1664503035713-500.png]]
683 +[[image:1664503035713-500.png||_mstalt="291096"]]
697 697  
698 698  
699 -[[image:1664503047675-651.png]]
686 +[[image:1664503047675-651.png||_mstalt="295386"]]
700 700  
701 701  
702 -
703 703  == 3.2 Command Set ==
704 704  
705 -
706 706  === 3.2.1 Set Transmit Interval ===
707 707  
708 708  
... ... @@ -720,7 +720,6 @@
720 720  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
721 721  
722 722  
723 -
724 724  === 3.2.2 Set Alarm Packet transmission interval ===
725 725  
726 726  
... ... @@ -738,7 +738,6 @@
738 738  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
739 739  
740 740  
741 -
742 742  === 3.2.3 Set Transport Mode Packet transmission interval ===
743 743  
744 744  
... ... @@ -756,7 +756,6 @@
756 756  (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
757 757  
758 758  
759 -
760 760  === 3.2.4 Exit Alarm ===
761 761  
762 762  
... ... @@ -769,7 +769,6 @@
769 769  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
770 770  
771 771  
772 -
773 773  === 3.2.5 Disable/Enable LED flash ===
774 774  
775 775  
... ... @@ -787,7 +787,6 @@
787 787  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
788 788  
789 789  
790 -
791 791  === 3.2.6 Disable/Enable Transport Mode ===
792 792  
793 793  
... ... @@ -805,7 +805,6 @@
805 805  (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
806 806  
807 807  
808 -
809 809  === 3.2.7 Set Positioning Mode ===
810 810  
811 811  
... ... @@ -832,9 +832,9 @@
832 832  
833 833  (% style="color:#037691" %)**cc:   **
834 834  
835 -* (% 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 
836 836  
837 -* (% 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(%%))  
838 838  
839 839  (% style="color:blue" %)**Example:**
840 840  
... ... @@ -852,7 +852,6 @@
852 852  (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
853 853  
854 854  
855 -
856 856  === 3.2.8 Set MAX GPS position time ===
857 857  
858 858  
... ... @@ -859,7 +859,7 @@
859 859  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.
860 860  
861 861  
862 -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.
863 863  
864 864  
865 865  * (% style="color:blue" %)**AT Command:**
... ... @@ -874,7 +874,6 @@
874 874  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
875 875  
876 876  
877 -
878 878  === 3.2.9 Set PDOP value for GPS fix accuracy ===
879 879  
880 880  
... ... @@ -899,8 +899,9 @@
899 899  
900 900  
901 901  
902 -Disable/Enable the confirmation mode
879 +=== 3.2.10 Disable/Enable the confirmation mode ===
903 903  
881 +
904 904  * (% style="color:blue" %)**AT Command:**
905 905  
906 906  (% style="color:#037691" %)**AT+CFM=xx**
... ... @@ -918,10 +918,9 @@
918 918  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
919 919  
920 920  
899 +=== 3.2.11  Auto Send None-ACK messages ===
921 921  
922 -=== 3.2.10  Auto Send None-ACK messages ===
923 923  
924 -
925 925  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.
926 926  
927 927  
... ... @@ -937,13 +937,12 @@
937 937  
938 938  * (% style="color:blue" %)**Downlink Command: 0x34**
939 939  
940 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
917 +Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
941 941  
942 942  
920 +=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
943 943  
944 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
945 945  
946 -
947 947  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.
948 948  
949 949  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -950,19 +950,18 @@
950 950  
951 951  (% style="color:blue" %)**AT Command:**
952 952  
953 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
929 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
954 954  
955 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
931 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
956 956  
957 957  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
958 958  
959 -Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
935 +Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
960 960  
961 961  
938 +=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
962 962  
963 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
964 964  
965 -
966 966  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.
967 967  
968 968  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
... ... @@ -969,19 +969,18 @@
969 969  
970 970  (% style="color:blue" %)**AT Command:**
971 971  
972 - (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
947 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
973 973  
974 - (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
949 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
975 975  
976 976  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
977 977  
978 -Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
953 +Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
979 979  
980 980  
956 +=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
981 981  
982 -=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
983 983  
984 -
985 985  Users can use this feature to enable/disable Information printing.
986 986  
987 987  (% style="color:blue" %)**AT Command:**
... ... @@ -990,10 +990,9 @@
990 990  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
991 991  
992 992  
967 +=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
993 993  
994 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
995 995  
996 -
997 997  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
998 998  
999 999  (% style="color:blue" %)**AT Command:**
... ... @@ -1006,7 +1006,26 @@
1006 1006  Example: 0x24 01 ~/~/ Same as AT+CHE=1
1007 1007  
1008 1008  
982 +=== 3.2.16 Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
1009 1009  
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 +
1010 1010  = 4. Setting for Different Scenarios =
1011 1011  
1012 1012  
... ... @@ -1013,7 +1013,6 @@
1013 1013  
1014 1014  = 5. Upload Firmware =
1015 1015  
1016 -
1017 1017  == 5.1 Firmware Change Log ==
1018 1018  
1019 1019  
... ... @@ -1020,7 +1020,6 @@
1020 1020  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1021 1021  
1022 1022  
1023 -
1024 1024  == 5.2 How to upgrade firmware ==
1025 1025  
1026 1026  
... ... @@ -1041,10 +1041,10 @@
1041 1041  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1042 1042  
1043 1043  
1044 -[[image:1664503563660-578.png]]
1034 +[[image:1664503563660-578.png||_mstalt="296777"]]
1045 1045  
1046 1046  
1047 -[[image:1664503574618-659.png]]
1037 +[[image:1664503574618-659.png||_mstalt="297986"]]
1048 1048  
1049 1049  
1050 1050  
... ... @@ -1053,29 +1053,27 @@
1053 1053  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1054 1054  
1055 1055  
1056 -Users need to use below files:
1046 +**Users need to use below files:**
1057 1057  
1058 1058  boot_app0.bin @0e000
1059 1059  
1060 -ESP_LORA-eeprom-class.bin @ 0x10000
1050 +US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1061 1061  
1062 1062  
1063 -[[image:1664503593459-435.png]]
1053 +[[image:image-20221118105220-2.png||_mstalt="426608"]]
1064 1064  
1065 1065  
1066 1066  
1067 1067  After upgrade finish, it will show finish as below:
1068 1068  
1069 -[[image:1664503611848-385.png]]
1059 +[[image:image-20221118105402-4.png||_mstalt="427986"]]
1070 1070  
1071 1071  
1072 1072  
1073 1073  = 6. Developer Guide =
1074 1074  
1075 -
1076 1076  == 6.1 Compile Source Code ==
1077 1077  
1078 -
1079 1079  === 6.1.1 Set up ARDUINO compile environment ===
1080 1080  
1081 1081  
... ... @@ -1084,23 +1084,23 @@
1084 1084  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]]
1085 1085  
1086 1086  
1087 -[[image:1664503635019-941.png]]
1075 +[[image:1664503635019-941.png||_mstalt="294658"]]
1088 1088  
1089 1089  
1090 1090  
1091 1091  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1092 1092  
1093 -[[image:1664503715811-892.png]]
1081 +[[image:1664503715811-892.png||_mstalt="295698"]]
1094 1094  
1095 1095  
1096 1096  (% 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.
1097 1097  
1098 -[[image:image-20221024105643-1.png]]
1086 +[[image:image-20221024105643-1.png||_mstalt="428129"]]
1099 1099  
1100 1100  **~ Figure1**
1101 1101  
1102 1102  
1103 -[[image:image-20221024105643-2.png]]
1091 +[[image:image-20221024105643-2.png||_mstalt="428493"]]
1104 1104  
1105 1105   **Figure2**
1106 1106  
... ... @@ -1110,34 +1110,31 @@
1110 1110  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1111 1111  
1112 1112  
1113 -[[image:1664503752288-974.png]]
1101 +[[image:1664503752288-974.png||_mstalt="298194"]]
1114 1114  
1115 1115  
1116 -
1117 1117  == 6.2 Source Code ==
1118 1118  
1119 1119  
1120 1120  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1121 1121  
1122 -[[image:1664503794261-827.png]]
1109 +[[image:1664503794261-827.png||_mstalt="296387"]]
1123 1123  
1124 1124  
1125 1125  
1126 1126  * (% style="color:blue" %)**Click to upload**
1127 1127  
1128 -[[image:1664503808294-336.png]]
1115 +[[image:1664503808294-336.png||_mstalt="295711"]]
1129 1129  
1130 1130  
1131 1131  
1132 1132  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1133 1133  
1134 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1121 +[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1135 1135  
1136 1136  
1137 -
1138 1138  = 7.  FAQ =
1139 1139  
1140 -
1141 1141  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1142 1142  
1143 1143  
... ... @@ -1144,11 +1144,10 @@
1144 1144  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1145 1145  
1146 1146  
1147 -
1148 1148  == 7.2 What is the pin mapping for the USB program cable? ==
1149 1149  
1150 1150  
1151 -[[image:1664499635206-262.png]]
1135 +[[image:1664499635206-262.png||_mstalt="295360"]]
1152 1152  
1153 1153  
1154 1154  
... ... @@ -1167,7 +1167,6 @@
1167 1167  
1168 1168  == 7.3 Notes on using different serial port tools for TrackerD ==
1169 1169  
1170 -
1171 1171  === 7.3.1  Serial port utility ===
1172 1172  
1173 1173  
... ... @@ -1175,18 +1175,16 @@
1175 1175  
1176 1176  Need to adjust the data stream to RTS/CTS on physical restart.
1177 1177  
1178 -
1179 1179  (% class="wikigeneratedid" %)
1180 -[[image:image-20221102140621-1.png]]
1162 +[[image:image-20221102140621-1.png||_mstalt="425672"]]
1181 1181  
1182 1182  
1165 +
1183 1183  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1184 1184  
1168 +[[image:image-20221102140638-2.png||_mstalt="428727"]]
1185 1185  
1186 -[[image:image-20221102140638-2.png]]
1187 1187  
1188 -
1189 -
1190 1190  === 7.3.2  SecureCRT ===
1191 1191  
1192 1192  
... ... @@ -1193,38 +1193,73 @@
1193 1193  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.
1194 1194  
1195 1195  
1196 -[[image:image-20221102140704-3.png]]
1177 +[[image:image-20221102140704-3.png||_mstalt="427076"]]
1197 1197  
1198 1198  
1199 -[[image:image-20221102140712-4.png]]
1180 +[[image:image-20221102140712-4.png||_mstalt="427089"]]
1200 1200  
1201 1201  
1202 -
1203 1203  === 7.3.3  PUTTY ===
1204 1204  
1205 1205  
1206 -[[image:image-20221102140748-5.png]]
1186 +[[image:image-20221102140748-5.png||_mstalt="430456"]]
1207 1207  
1208 1208  
1209 1209  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.
1210 1210  
1211 1211  
1212 -[[image:image-20221102140801-6.png]]
1192 +[[image:image-20221102140801-6.png||_mstalt="427466"]]
1213 1213  
1214 1214  
1195 +== 7.4 How to modify source code to compile different frequency band bin file? ==
1215 1215  
1216 -= 8  Trouble Shooting =
1217 1217  
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 +)))
1218 1218  
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 +
1219 1219  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1220 1220  
1221 1221  
1222 1222  (((
1223 -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
1224 1224  )))
1225 1225  
1226 1226  
1227 -
1228 1228  == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1229 1229  
1230 1230  
... ... @@ -1233,19 +1233,106 @@
1233 1233  )))
1234 1234  
1235 1235  
1252 +== 8.3  Problem after Upgrading Firmware ==
1236 1236  
1237 -== 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 ===
1238 1238  
1239 1239  
1257 +**Error Output**
1258 +
1259 +
1260 +[[image:image-20221122100004-4.png||_mstalt="424606"]]
1261 +
1262 +
1240 1240  (((
1241 -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"]]
1242 1242  )))
1243 1243  
1244 1244  
1245 -[[image:image-20221107145243-1.png||height="695" width="443"]]
1270 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1246 1246  
1247 1247  
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
1248 1248  
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 +
1249 1249  = 9.  Order Info =
1250 1250  
1251 1251  
... ... @@ -1254,11 +1254,17 @@
1254 1254  (% style="color:blue" %)**XXX**(%%): The default frequency band
1255 1255  
1256 1256  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1360 +
1257 1257  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1362 +
1258 1258  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1364 +
1259 1259  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1366 +
1260 1260  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1368 +
1261 1261  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1370 +
1262 1262  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1263 1263  
1264 1264  
... ... @@ -1269,11 +1269,13 @@
1269 1269  (% style="color:#037691" %)**Package Includes**:
1270 1270  
1271 1271  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1381 +
1272 1272  * USB recharge & program cable x 1
1273 1273  
1274 1274  (% style="color:#037691" %)**Dimensions and Weight**:
1275 1275  
1276 1276  * Device Size: 85 x 48 x 15 mm
1387 +
1277 1277  * Weight: 50g
1278 1278  
1279 1279  
... ... @@ -1282,6 +1282,7 @@
1282 1282  
1283 1283  
1284 1284  * 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 +
1285 1285  * 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]].
1286 1286  
1287 1287  
... ... @@ -1290,7 +1290,8 @@
1290 1290  
1291 1291  
1292 1292  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1405 +
1293 1293  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1294 -* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1295 1295  
1296 -
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
image-20221128111850-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +14.5 KB
Content