Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Xiaoling on 2025/04/27 16:48
From version 164.1
edited by Bei Jinggeng
on 2022/11/28 14:10
on 2022/11/28 14:10
Change comment:
There is no comment for this version
To version 142.1
edited by Bei Jinggeng
on 2022/11/22 10:02
on 2022/11/22 10:02
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 7 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,5 +1,5 @@ 1 1 (% style="text-align:center" %) 2 -[[image:1664505654417-133.png ||_mstalt="293696"]]2 +[[image:1664505654417-133.png]] 3 3 4 4 5 5 ... ... @@ -14,6 +14,7 @@ 14 14 15 15 = 1. Introduction = 16 16 17 + 17 17 == 1.1 What is TrackerD == 18 18 19 19 ... ... @@ -31,17 +31,21 @@ 31 31 ((( 32 32 The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services. 33 33 ))) 35 +))) 34 34 35 35 ((( 36 36 TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network. 39 + 40 + 37 37 ))) 38 38 39 -[[image:1664499921684-770.png ||_mstalt="298194"]]43 +[[image:1664499921684-770.png]] 40 40 41 41 42 42 (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.** 43 43 44 44 49 + 45 45 == 1.2 Specifications == 46 46 47 47 ... ... @@ -118,6 +118,7 @@ 118 118 119 119 = 2. Use TrackerD = 120 120 126 + 121 121 == 2.1 How it works? == 122 122 123 123 ... ... @@ -124,6 +124,7 @@ 124 124 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. 125 125 126 126 133 + 127 127 == 2.2 Quick guide to connect to LoRaWAN server == 128 128 129 129 ... ... @@ -130,7 +130,7 @@ 130 130 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. 131 131 132 132 133 -[[image:1664501652064-326.png ||_mstalt="293306"]]140 +[[image:1664501652064-326.png]] 134 134 135 135 136 136 ... ... @@ -142,7 +142,7 @@ 142 142 Each TrackerD is shipped with a sticker with the default device EUI as below: 143 143 144 144 145 -[[image:1664501677253-891.png ||_mstalt="296569"]]152 +[[image:1664501677253-891.png]] 146 146 147 147 148 148 Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot: ... ... @@ -151,14 +151,14 @@ 151 151 **__Add APP EUI in the application:__** 152 152 153 153 154 -[[image:1664501711466-918.png ||_mstalt="295828"]]161 +[[image:1664501711466-918.png]] 155 155 156 156 157 157 158 -[[image:1664501721248-725.png ||_mstalt="294450"]]165 +[[image:1664501721248-725.png]] 159 159 160 160 161 -[[image:1664501734705-405.png ||_mstalt="293306"]]168 +[[image:1664501734705-405.png]] 162 162 163 163 164 164 ... ... @@ -165,20 +165,21 @@ 165 165 **__Add APP KEY and DEV EUI:__** 166 166 167 167 168 -[[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"]]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"]] 169 169 170 170 171 171 172 172 (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device. 173 173 174 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png ||_mstalt="295061"]]181 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]] 175 175 176 -[[image:1664502835802-546.png ||_mstalt="295061"]]183 +[[image:1664502835802-546.png]] 177 177 178 178 179 179 (% 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. 180 180 181 181 189 + 182 182 == 2.3 Positioning Mode(SMOD) == 183 183 184 184 ... ... @@ -191,8 +191,10 @@ 191 191 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 192 192 193 193 202 + 194 194 == 2.4 Uplink Payload == 195 195 205 + 196 196 === 2.4.1 Uplink FPORT~=5, Device Status === 197 197 198 198 ... ... @@ -205,7 +205,7 @@ 205 205 |=(% 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 206 206 |=(% 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 207 207 208 -[[image:1665301570342-765.png ||_mstalt="294580"]]218 +[[image:1665301570342-765.png]] 209 209 210 210 211 211 (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002 ... ... @@ -272,7 +272,7 @@ 272 272 273 273 (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 274 274 275 -(% _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 +(% style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%) 276 276 277 277 278 278 (% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 ... ... @@ -299,7 +299,7 @@ 299 299 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 300 300 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 301 301 302 -[[image:1665301636888-168.png ||_mstalt="298012"]]312 +[[image:1665301636888-168.png]] 303 303 304 304 305 305 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== ... ... @@ -329,12 +329,12 @@ 329 329 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: 330 330 331 331 332 -[[image:1664502116362-706.png ||_mstalt="293306"]]342 +[[image:1664502116362-706.png]] 333 333 334 334 335 335 3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 336 336 337 -[[image:1664502166010-515.png ||_mstalt="291395"]]347 +[[image:1664502166010-515.png]] 338 338 339 339 340 340 ... ... @@ -397,6 +397,7 @@ 397 397 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree// 398 398 399 399 410 + 400 400 === 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) === 401 401 402 402 ... ... @@ -412,13 +412,14 @@ 412 412 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 413 413 414 414 (% class="wikigeneratedid" %) 415 -[[image:1665301687277-443.png ||_mstalt="296140"]]426 +[[image:1665301687277-443.png]] 416 416 417 417 429 + 418 418 === 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 419 419 420 420 421 -Set [[PNACKMD=1>>||anchor="H3.2.1 1A0A0AutoSendNone-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.433 +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. 422 422 423 423 424 424 (% style="color:red" %)**Note for this mode:** ... ... @@ -435,9 +435,10 @@ 435 435 )))|4|4|2|1|1|1|1|1 436 436 |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 437 437 438 -[[image:image-20221009160309-2.png ||_mstalt="429312"]]450 +[[image:image-20221009160309-2.png]] 439 439 440 440 453 + 441 441 === 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 442 442 443 443 ... ... @@ -462,7 +462,7 @@ 462 462 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 463 463 )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 464 464 465 -[[image:1664502425687-834.png ||_mstalt="296738"]]478 +[[image:1664502425687-834.png]] 466 466 467 467 468 468 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). ... ... @@ -488,7 +488,7 @@ 488 488 )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 489 489 490 490 (% class="wikigeneratedid" %) 491 -[[image:1667288597595-714.png|| _mstalt="299598"height="212" width="1151"]]504 +[[image:1667288597595-714.png||height="212" width="1151"]] 492 492 493 493 494 494 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). ... ... @@ -503,10 +503,9 @@ 503 503 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 504 504 505 505 506 -[[image:1664502649601-895.png ||_mstalt="296985"]]519 +[[image:1664502649601-895.png]] 507 507 508 508 509 - 510 510 Add the decoder from this link: 511 511 512 512 [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] ... ... @@ -513,9 +513,10 @@ 513 513 514 514 Save the change the uplink message will be parsed. As below: 515 515 516 -[[image:1664502676891-606.png ||_mstalt="296673"]]528 +[[image:1664502676891-606.png]] 517 517 518 518 531 + 519 519 == 2.5 Integrate with Datacake == 520 520 521 521 ... ... @@ -524,9 +524,10 @@ 524 524 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]] 525 525 526 526 527 -[[image:1664502695771-538.png ||_mstalt="297349"]]540 +[[image:1664502695771-538.png]] 528 528 529 529 543 + 530 530 == 2.6 Integrate with Tago == 531 531 532 532 ... ... @@ -535,24 +535,26 @@ 535 535 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]] 536 536 537 537 538 -[[image:1664502715371-321.png ||_mstalt="292162"]]552 +[[image:1664502715371-321.png]] 539 539 540 540 555 + 541 541 == 2.7 Datalog Feature == 542 542 543 543 544 544 total 273 entries,by default, 545 545 546 -User can set [[PNACKMD=1>>||anchor="H3.2.1 1A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.561 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 547 547 548 548 Example use case. 549 549 550 -[[image:image-20221009234703-2.png|| _mstalt="429143"height="328" width="899"]]565 +[[image:image-20221009234703-2.png||height="328" width="899"]] 551 551 552 552 553 -[[image:image-20221009234629-1.png|| _mstalt="431145"height="390" width="577"]]568 +[[image:image-20221009234629-1.png||height="390" width="577"]] 554 554 555 555 571 + 556 556 == 2.8 Alarm Mode == 557 557 558 558 ... ... @@ -567,7 +567,7 @@ 567 567 568 568 569 569 ((( 570 - **Two ways to exit alarm mode:**586 +Two ways to exit alarm mode: 571 571 ))) 572 572 573 573 * Server sends a downlink command to exit. ... ... @@ -578,15 +578,14 @@ 578 578 ))) 579 579 580 580 597 + 581 581 == 2.9 Transport Mode == 582 582 583 583 584 584 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. 585 585 586 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation. 587 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic. 588 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion. 589 589 604 + 590 590 == 2.10 LED Status == 591 591 592 592 ... ... @@ -609,7 +609,7 @@ 609 609 610 610 (% style="color:blue" %)**RESET button:** 611 611 612 -[[image:1664502835802-546.png ||_mstalt="295061"]]627 +[[image:1664502835802-546.png]] 613 613 614 614 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server. 615 615 ... ... @@ -616,7 +616,7 @@ 616 616 617 617 (% style="color:red" %)**RED button:** 618 618 619 -[[image:1664502854406-763.png ||_mstalt="295568"]]634 +[[image:1664502854406-763.png]] 620 620 621 621 622 622 (% border="1" style="background-color:#ffffcc; width:510px" %) ... ... @@ -643,6 +643,7 @@ 643 643 LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] 644 644 645 645 661 + 646 646 == 3.1 Access AT Command == 647 647 648 648 ... ... @@ -649,23 +649,25 @@ 649 649 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. 650 650 651 651 652 -[[image:1664502999401-486.png ||_mstalt="296985"]]668 +[[image:1664502999401-486.png]] 653 653 654 654 655 655 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: 656 656 657 657 658 -[[image:1664503022490-662.png ||_mstalt="293332"]]674 +[[image:1664503022490-662.png]] 659 659 660 660 661 -[[image:1664503035713-500.png ||_mstalt="291096"]]677 +[[image:1664503035713-500.png]] 662 662 663 663 664 -[[image:1664503047675-651.png ||_mstalt="295386"]]680 +[[image:1664503047675-651.png]] 665 665 666 666 683 + 667 667 == 3.2 Command Set == 668 668 686 + 669 669 === 3.2.1 Set Transmit Interval === 670 670 671 671 ... ... @@ -683,6 +683,7 @@ 683 683 (% style="color:#037691" %)**0x01 00 01 2C** (%%) ~/~/ Same as AT+TDC=300000 684 684 685 685 704 + 686 686 === 3.2.2 Set Alarm Packet transmission interval === 687 687 688 688 ... ... @@ -700,6 +700,7 @@ 700 700 (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/ Same as AT+ATDC=60000 701 701 702 702 722 + 703 703 === 3.2.3 Set Transport Mode Packet transmission interval === 704 704 705 705 ... ... @@ -717,6 +717,7 @@ 717 717 (% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+MTDC=3000000 718 718 719 719 740 + 720 720 === 3.2.4 Exit Alarm === 721 721 722 722 ... ... @@ -729,6 +729,7 @@ 729 729 (% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 730 730 731 731 753 + 732 732 === 3.2.5 Disable/Enable LED flash === 733 733 734 734 ... ... @@ -746,6 +746,7 @@ 746 746 (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/ Same as AT+LON=0 747 747 748 748 771 + 749 749 === 3.2.6 Disable/Enable Transport Mode === 750 750 751 751 ... ... @@ -763,6 +763,7 @@ 763 763 (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+INTWK=1 764 764 765 765 789 + 766 766 === 3.2.7 Set Positioning Mode === 767 767 768 768 ... ... @@ -789,9 +789,9 @@ 789 789 790 790 (% style="color:#037691" %)**cc: ** 791 791 792 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State816 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 793 793 794 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((%_mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))818 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%)) 795 795 796 796 (% style="color:blue" %)**Example:** 797 797 ... ... @@ -809,6 +809,7 @@ 809 809 (% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+SMOD=1,0,0 810 810 811 811 836 + 812 812 === 3.2.8 Set MAX GPS position time === 813 813 814 814 ... ... @@ -815,7 +815,7 @@ 815 815 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. 816 816 817 817 818 -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.843 +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. 819 819 820 820 821 821 * (% style="color:blue" %)**AT Command:** ... ... @@ -830,6 +830,7 @@ 830 830 (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/ Set AT+FTIME=150 831 831 832 832 858 + 833 833 === 3.2.9 Set PDOP value for GPS fix accuracy === 834 834 835 835 ... ... @@ -854,9 +854,8 @@ 854 854 855 855 856 856 857 - === 3.2.10Disable/Enable the confirmation mode===883 +Disable/Enable the confirmation mode 858 858 859 - 860 860 * (% style="color:blue" %)**AT Command:** 861 861 862 862 (% style="color:#037691" %)**AT+CFM=xx** ... ... @@ -874,9 +874,10 @@ 874 874 (% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1 875 875 876 876 877 -=== 3.2.11 Auto Send None-ACK messages === 878 878 903 +=== 3.2.10 Auto Send None-ACK messages === 879 879 905 + 880 880 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. 881 881 882 882 ... ... @@ -892,12 +892,13 @@ 892 892 893 893 * (% style="color:blue" %)**Downlink Command: 0x34** 894 894 895 -Example: 0x34 921 +Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 896 896 897 897 898 -=== 3.2.12 Set BLEMASK to filter BLE iBeacon === 899 899 925 +=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 900 900 927 + 901 901 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. 902 902 903 903 (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.** ... ... @@ -904,18 +904,19 @@ 904 904 905 905 (% style="color:blue" %)**AT Command:** 906 906 907 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456934 + (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 908 908 909 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK936 + (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 910 910 911 911 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 912 912 913 -Example: 0xB2 940 +Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 914 914 915 915 916 -=== 3.2.13 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 917 917 944 +=== 3.2.12 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 918 918 946 + 919 919 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. 920 920 921 921 (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.** ... ... @@ -922,18 +922,19 @@ 922 922 923 923 (% style="color:blue" %)**AT Command:** 924 924 925 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456953 + (% style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456 926 926 927 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK955 + (% style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK 928 928 929 929 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)** 930 930 931 -Example: 0xB3 959 +Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 932 932 933 933 934 -=== 3.2.14 Disable/Enable Information printing(Since firmware 1.4.1) === 935 935 963 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 936 936 965 + 937 937 Users can use this feature to enable/disable Information printing. 938 938 939 939 (% style="color:blue" %)**AT Command:** ... ... @@ -942,9 +942,10 @@ 942 942 \\Example: AT+SHOWID=1 ~-~-> Enable Information printing. 943 943 944 944 945 -=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 946 946 975 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 947 947 977 + 948 948 The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. 949 949 950 950 (% style="color:blue" %)**AT Command:** ... ... @@ -957,26 +957,7 @@ 957 957 Example: 0x24 01 ~/~/ Same as AT+CHE=1 958 958 959 959 960 -=== 3.2.16 Get or Set Threshold for motion detect(Since firmware 1.4.3) === 961 961 962 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event. 963 - 964 -(% style="color:blue" %)**AT Command:** 965 - 966 -(% style="color:#037691" %)**AT+PT=xx** 967 - 968 - Example: 969 - 970 - AT+PT=14 ~-~-> Set to detect car motion. 971 - 972 - AT+PT=41 ~-~-> set to detect walk motion. 973 - 974 - 975 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%) 976 -0xB4 14 ~/~/ Same as AT+PT=14 977 - 978 - 979 - 980 980 = 4. Setting for Different Scenarios = 981 981 982 982 ... ... @@ -983,6 +983,7 @@ 983 983 984 984 = 5. Upload Firmware = 985 985 997 + 986 986 == 5.1 Firmware Change Log == 987 987 988 988 ... ... @@ -989,6 +989,7 @@ 989 989 **[[See this link>>url:https://github.com/dragino/TrackerD]]** 990 990 991 991 1004 + 992 992 == 5.2 How to upgrade firmware == 993 993 994 994 ... ... @@ -1009,10 +1009,10 @@ 1009 1009 (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32 1010 1010 1011 1011 1012 -[[image:1664503563660-578.png ||_mstalt="296777"]]1025 +[[image:1664503563660-578.png]] 1013 1013 1014 1014 1015 -[[image:1664503574618-659.png ||_mstalt="297986"]]1028 +[[image:1664503574618-659.png]] 1016 1016 1017 1017 1018 1018 ... ... @@ -1021,7 +1021,7 @@ 1021 1021 [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]] 1022 1022 1023 1023 1024 - **Users need to use below files:**1037 +Users need to use below files: 1025 1025 1026 1026 boot_app0.bin @0e000 1027 1027 ... ... @@ -1028,20 +1028,22 @@ 1028 1028 US915.bin @ 0x10000(Select the bin file of the frequency band you need) 1029 1029 1030 1030 1031 -[[image:image-20221118105220-2.png ||_mstalt="426608"]]1044 +[[image:image-20221118105220-2.png]] 1032 1032 1033 1033 1034 1034 1035 1035 After upgrade finish, it will show finish as below: 1036 1036 1037 -[[image:image-20221118105402-4.png ||_mstalt="427986"]]1050 +[[image:image-20221118105402-4.png]] 1038 1038 1039 1039 1040 1040 1041 1041 = 6. Developer Guide = 1042 1042 1056 + 1043 1043 == 6.1 Compile Source Code == 1044 1044 1059 + 1045 1045 === 6.1.1 Set up ARDUINO compile environment === 1046 1046 1047 1047 ... ... @@ -1050,23 +1050,23 @@ 1050 1050 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]] 1051 1051 1052 1052 1053 -[[image:1664503635019-941.png ||_mstalt="294658"]]1068 +[[image:1664503635019-941.png]] 1054 1054 1055 1055 1056 1056 1057 1057 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 1058 1058 1059 -[[image:1664503715811-892.png ||_mstalt="295698"]]1074 +[[image:1664503715811-892.png]] 1060 1060 1061 1061 1062 1062 (% 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. 1063 1063 1064 -[[image:image-20221024105643-1.png ||_mstalt="428129"]]1079 +[[image:image-20221024105643-1.png]] 1065 1065 1066 1066 **~ Figure1** 1067 1067 1068 1068 1069 -[[image:image-20221024105643-2.png ||_mstalt="428493"]]1084 +[[image:image-20221024105643-2.png]] 1070 1070 1071 1071 **Figure2** 1072 1072 ... ... @@ -1076,31 +1076,34 @@ 1076 1076 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: 1077 1077 1078 1078 1079 -[[image:1664503752288-974.png ||_mstalt="298194"]]1094 +[[image:1664503752288-974.png]] 1080 1080 1081 1081 1097 + 1082 1082 == 6.2 Source Code == 1083 1083 1084 1084 1085 1085 * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:** 1086 1086 1087 -[[image:1664503794261-827.png ||_mstalt="296387"]]1103 +[[image:1664503794261-827.png]] 1088 1088 1089 1089 1090 1090 1091 1091 * (% style="color:blue" %)**Click to upload** 1092 1092 1093 -[[image:1664503808294-336.png ||_mstalt="295711"]]1109 +[[image:1664503808294-336.png]] 1094 1094 1095 1095 1096 1096 1097 1097 * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 1098 1098 1099 -[[image:1664503824081-592.png ||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]1115 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 1100 1100 1101 1101 1118 + 1102 1102 = 7. FAQ = 1103 1103 1121 + 1104 1104 == 7.1 How to change the LoRa Frequency Bands/Region? == 1105 1105 1106 1106 ... ... @@ -1107,10 +1107,11 @@ 1107 1107 User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download. 1108 1108 1109 1109 1128 + 1110 1110 == 7.2 What is the pin mapping for the USB program cable? == 1111 1111 1112 1112 1113 -[[image:1664499635206-262.png ||_mstalt="295360"]]1132 +[[image:1664499635206-262.png]] 1114 1114 1115 1115 1116 1116 ... ... @@ -1127,6 +1127,7 @@ 1127 1127 1128 1128 == 7.3 Notes on using different serial port tools for TrackerD == 1129 1129 1149 + 1130 1130 === 7.3.1 Serial port utility === 1131 1131 1132 1132 ... ... @@ -1134,16 +1134,18 @@ 1134 1134 1135 1135 Need to adjust the data stream to RTS/CTS on physical restart. 1136 1136 1157 + 1137 1137 (% class="wikigeneratedid" %) 1138 -[[image:image-20221102140621-1.png ||_mstalt="425672"]]1159 +[[image:image-20221102140621-1.png]] 1139 1139 1140 1140 1141 - 1142 1142 When using AT commands, the data flow needs to be adjusted to XON/XOFF 1143 1143 1144 -[[image:image-20221102140638-2.png||_mstalt="428727"]] 1145 1145 1165 +[[image:image-20221102140638-2.png]] 1146 1146 1167 + 1168 + 1147 1147 === 7.3.2 SecureCRT === 1148 1148 1149 1149 ... ... @@ -1150,22 +1150,23 @@ 1150 1150 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. 1151 1151 1152 1152 1153 -[[image:image-20221102140704-3.png ||_mstalt="427076"]]1175 +[[image:image-20221102140704-3.png]] 1154 1154 1155 1155 1156 -[[image:image-20221102140712-4.png ||_mstalt="427089"]]1178 +[[image:image-20221102140712-4.png]] 1157 1157 1158 1158 1181 + 1159 1159 === 7.3.3 PUTTY === 1160 1160 1161 1161 1162 -[[image:image-20221102140748-5.png ||_mstalt="430456"]]1185 +[[image:image-20221102140748-5.png]] 1163 1163 1164 1164 1165 1165 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. 1166 1166 1167 1167 1168 -[[image:image-20221102140801-6.png ||_mstalt="427466"]]1191 +[[image:image-20221102140801-6.png]] 1169 1169 1170 1170 1171 1171 == 7.4 How to modify source code to compile different frequency band bin file? == ... ... @@ -1177,46 +1177,38 @@ 1177 1177 See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]] 1178 1178 ))) 1179 1179 1180 - **~1.**1203 +1.When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file. 1181 1181 1205 +[[image:image-20221116111844-1.png||height="227" width="782"]] 1182 1182 1183 - [[image:image-20221116111844-1.png||_mstalt="428688"height="227"width="782"]]1207 +2.Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except). 1184 1184 1209 +[[image:image-20221116111844-2.png||height="262" width="781"]] 1185 1185 1211 +3.Compile the AS923_JP band, please refer to the intention shown 1186 1186 1187 - **2. Open LMIC_PROJECT_CONFIG.H, find the correspondingmacro definitionand open it(AS923_2,AS923_3,AS923_4except).**1213 +[[image:image-20221116111844-3.png||height="338" width="746"]] 1188 1188 1215 +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. 1189 1189 1190 -[[image:image-20221116111844- 2.png||_mstalt="429052"height="262" width="781"]]1217 +[[image:image-20221116111844-4.png||height="641" width="739"]] 1191 1191 1219 +[[image:image-20221116111844-5.png||height="551" width="708"]] 1192 1192 1193 1193 1194 -**3. Compile the AS923_JP band, please refer to the intention shown** 1195 1195 1196 - 1197 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]] 1198 - 1199 - 1200 - 1201 -**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.** 1202 - 1203 - 1204 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]] 1205 - 1206 - 1207 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]] 1208 - 1209 - 1210 1210 = 8 Trouble Shooting = 1211 1211 1225 + 1212 1212 == 8.1 TDC is changed to 4294947296 and cause no uplink. == 1213 1213 1214 1214 1215 1215 ((( 1216 -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.11230 +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 1217 1217 ))) 1218 1218 1219 1219 1234 + 1220 1220 == 8.2 Device not able get AT Command or show output after wake up from deep sleep mode == 1221 1221 1222 1222 ... ... @@ -1225,138 +1225,86 @@ 1225 1225 ))) 1226 1226 1227 1227 1243 + 1228 1228 == 8.3 Problem after Upgrading Firmware == 1229 1229 1230 -=== 8.3.1 "rst: (0x3 SW_RESET)" andContinue Restart after upgrading ===1246 +=== 8.3.1 Continue Restart after upgrading === 1231 1231 1232 1232 1233 -**Error Output** 1234 - 1235 - 1236 -[[image:image-20221122100004-4.png||_mstalt="424606"]] 1237 - 1238 - 1239 1239 ((( 1240 -Some partition is missed during upgrade, please upgrade below four files as example: 1241 - 1242 -[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]] 1250 +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 1243 1243 ))) 1244 1244 1245 1245 1246 - === 8.3.2 TrackerD's led light isalways GREEN on after upgrading===1254 +[[image:image-20221118105249-3.png]] 1247 1247 1248 1248 1257 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1258 + 1249 1249 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 1250 1250 1251 1251 1252 -=== 8.3. 3"flashread err"afterupgradefirmware ===1262 +==== 8.3.2.1 If there is a situation in Figure 1,and a new partition file and bootloader file needs to be added. Please refer to the operation steps in Figure 2 ==== 1253 1253 1264 +[[image:image-20221122100004-1.png||height="497" width="534"]] 1254 1254 1255 - Errorshowsbelow,usermighterasetheentireflashincludeu-bootpartitionwhichcausethisissue.1266 + Figure 1 1256 1256 1268 + [[image:image-20221122100004-2.png||height="619" width="389"]] 1257 1257 1258 - [[image:image-20221122100004-1.png||_mstalt="423514"height="497" width="534"]]1270 + Figure 2 1259 1259 1272 +After the upgrade is completed, enter AT+CFG as shown in the figure below. 1260 1260 1261 - User need to upgradeain with below four files to solve this issue.1274 +[[image:image-20221122100004-3.png]] 1262 1262 1263 - [[image:image-20221122100004-2.png||_mstalt="423878"height="619" width="389"]]1276 +Please at+FDR, and then enter the following instructions by the information on the label 1264 1264 1265 - **Figure 2**1278 +AT+DEUI=70B3D57ED0053981 1266 1266 1267 - 1268 -=== 8.3.4 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware === 1269 - 1270 - 1271 -User might erase the entire flash include keys and default settings which cause this issue. 1272 - 1273 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below. 1274 - 1275 - 1276 -[[image:image-20221122100004-3.png||_mstalt="424242"]] 1277 - 1278 - 1279 -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. 1280 - 1281 -After AT+FDR. please set 1282 - 1283 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7** 1284 - 1285 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000** 1286 - 1287 -**Example:** 1288 - 1289 -AT+PDOP=7.00 1290 - 1291 -AT+FTIME=180 1292 - 1293 -AT+DEUI=70B3D57ED0053981 1294 - 1295 1295 AT+APPEUI=D23345667BCBCCAF 1296 1296 1297 1297 AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1 1298 1298 1299 -AT+DADDR=260b4dce ( no need for OTAA)1284 +AT+DADDR=260b4dce 1300 1300 1301 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d ( no need for OTAA)1286 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d 1302 1302 1303 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA)1288 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 1304 1304 1305 1305 1306 -== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1307 1307 1292 +==== 8.3.2.2 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ==== 1308 1308 1309 - Pleasedownload version1.4.2 again1294 +[[image:image-20221122100004-4.png]] 1310 1310 1296 +(% class="wikigeneratedid" %) 1297 +== == 1311 1311 1312 -== 8. 5Howtodealwith unsuccessfulGPS positioning?==1299 +== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1313 1313 1301 +Please download version 1.4.2 again 1314 1314 1315 -1) Make Sure the device is in Open Area where can see the sky. 1316 1316 1304 +((( 1305 +== 8.5 How to deal with unsuccessful GPS positioning? == 1306 + 1307 +1) Make Sure the device is in Open Area where can see the sky. 1317 1317 2) Set PDOP to a higher value. 1318 1318 1319 - *(%_mstmutation="1"style="color:blue"%)**AT+PDOP=2**(%%)(can be positioned precisely.)1310 + AT+PDOP=2(can be positioned precisely.) 1320 1320 1321 - *(%_mstmutation="1"style="color:blue"%)**AT+PDOP=7**(%%)(Quickly locate in open spaces)1312 + AT+PDOP=7(Quickly locate in open spaces) 1322 1322 1323 - *(%_mstmutation="1"style="color:blue"%)**AT+PDOP=14.7**(%%)(Positioning can be acquired in complex environments)1314 + AT+PDOP=14.7(Positioning can be acquired in complex environments) 1324 1324 1325 1325 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 1317 +))) 1326 1326 1327 1327 1328 -== 8.6Whenupgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets==1320 +== == 1329 1329 1330 -When upgrading, use the erase button to upgrade 1331 1331 1332 -[[image:image-20221128102938-1.png||height="537" width="335"]] 1333 - 1334 - 1335 -The parameters are displayed abnormally and cannot be fixed using AT+FDR 1336 - 1337 -[[image:image-20221128103040-2.png||height="431" width="525"]] 1338 - 1339 -Please upgrade these four files,link(The boot_app0 file is in the version folder you need) 1340 - 1341 -[[image:image-20221128110503-3.png||height="647" width="410"]] 1342 - 1343 -Reboot information after upgrade 1344 - 1345 -[[image:image-20221128111443-4.png||height="432" width="546"]] 1346 - 1347 -Use AT+FDR command to reset and then use AT+CFG to check whether the configuration is back to normal 1348 - 1349 -[[image:image-20221128111850-5.png]] 1350 - 1351 -After the parameters return to normal, upgrade to the version you need again 1352 - 1353 -[[image:image-20221128111951-6.png||height="620" width="389"]] 1354 - 1355 -At this point, the parameters return to normal after running AT+FDR again 1356 - 1357 -[[image:image-20221128112035-7.png]] 1358 - 1359 - 1360 1360 = 9. Order Info = 1361 1361 1362 1362 ... ... @@ -1365,17 +1365,11 @@ 1365 1365 (% style="color:blue" %)**XXX**(%%): The default frequency band 1366 1366 1367 1367 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433 1368 - 1369 1369 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868 1370 - 1371 1371 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865 1372 - 1373 1373 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920 1374 - 1375 1375 * (% style="color:red" %)**AS923**(%%): Default frequency band AS923 1376 - 1377 1377 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 1378 - 1379 1379 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1380 1380 1381 1381 = 10. Packing Info = ... ... @@ -1384,13 +1384,11 @@ 1384 1384 (% style="color:#037691" %)**Package Includes**: 1385 1385 1386 1386 * TrackerD LoRaWAN GPS/BLE Tracker x 1 1387 - 1388 1388 * USB recharge & program cable x 1 1389 1389 1390 1390 (% style="color:#037691" %)**Dimensions and Weight**: 1391 1391 1392 1392 * Device Size: 85 x 48 x 15 mm 1393 - 1394 1394 * Weight: 50g 1395 1395 1396 1396 = 11. Support = ... ... @@ -1397,7 +1397,6 @@ 1397 1397 1398 1398 1399 1399 * 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. 1400 - 1401 1401 * 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]]. 1402 1402 1403 1403 = 12. Reference = ... ... @@ -1404,8 +1404,5 @@ 1404 1404 1405 1405 1406 1406 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1407 - 1408 1408 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1409 - 1410 1410 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 1411 -)))
- image-20221128102938-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -41.3 KB - Content
- image-20221128103040-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -19.2 KB - Content
- image-20221128110503-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -45.6 KB - Content
- image-20221128111443-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -15.6 KB - Content
- image-20221128111850-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -14.5 KB - Content
- image-20221128111951-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -45.4 KB - Content
- image-20221128112035-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -14.7 KB - Content