Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)
Last modified by Xiaoling on 2023/12/27 09:15
From version 205.1
edited by Edwin Chen
on 2023/04/12 23:49
on 2023/04/12 23:49
Change comment:
There is no comment for this version
To version 138.1
edited by Bei Jinggeng
on 2022/11/22 10:00
on 2022/11/22 10:00
Change comment:
Uploaded new attachment "image-20221122100004-1.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 35 removed)
- image-20221122100004-2.png
- image-20221122100004-3.png
- image-20221122100004-4.png
- image-20221128102938-1.png
- image-20221128103040-2.png
- image-20221128110503-3.png
- image-20221128111443-4.png
- image-20221128111850-5.png
- image-20221128111951-6.png
- image-20221128112035-7.png
- image-20221207120501-1.png
- image-20221207120524-2.png
- image-20221207120530-3.png
- image-20221207120536-4.png
- image-20221207120601-5.png
- image-20221207133836-6.png
- image-20221207133911-7.png
- image-20221207134028-8.png
- image-20221213100007-1.png
- image-20221213100626-2.png
- image-20221213100808-3.png
- image-20221213101040-4.png
- image-20221213102311-5.png
- image-20221213102334-6.png
- image-20221213102718-7.png
- image-20221213110952-8.png
- image-20230213110119-1.png
- image-20230213110214-2.png
- image-20230213110506-3.png
- image-20230302145315-1.png
- image-20230307135914-1.png
- image-20230307135932-2.png
- image-20230308115430-1.png
- image-20230308115616-2.png
- image-20230308115701-3.png
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.Bei - 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 ... ... @@ -12,9 +12,9 @@ 12 12 13 13 14 14 15 - 16 16 = 1. Introduction = 17 17 17 + 18 18 == 1.1 What is TrackerD == 19 19 20 20 ... ... @@ -32,17 +32,21 @@ 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 +))) 35 35 36 36 ((( 37 37 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 + 38 38 ))) 39 39 40 -[[image: image-20230213110119-1.png||height="382" width="834"]]43 +[[image:1664499921684-770.png]] 41 41 42 42 43 43 (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.** 44 44 45 45 49 + 46 46 == 1.2 Specifications == 47 47 48 48 ... ... @@ -93,7 +93,6 @@ 93 93 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm 94 94 * Tracking: max: 38mA 95 95 96 - 97 97 == 1.3 Features == 98 98 99 99 ... ... @@ -112,7 +112,6 @@ 112 112 * Tri-color LED, Alarm button 113 113 * Datalog 114 114 115 - 116 116 == 1.4 Applications == 117 117 118 118 ... ... @@ -119,9 +119,9 @@ 119 119 * Logistics and Supply Chain Management 120 120 * Human tracking 121 121 122 - 123 123 = 2. Use TrackerD = 124 124 126 + 125 125 == 2.1 How it works? == 126 126 127 127 ... ... @@ -128,6 +128,7 @@ 128 128 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. 129 129 130 130 133 + 131 131 == 2.2 Quick guide to connect to LoRaWAN server == 132 132 133 133 ... ... @@ -134,7 +134,7 @@ 134 134 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. 135 135 136 136 137 -[[image: image-20230213110214-2.png||height="388" width="847"]]140 +[[image:1664501652064-326.png]] 138 138 139 139 140 140 ... ... @@ -146,7 +146,7 @@ 146 146 Each TrackerD is shipped with a sticker with the default device EUI as below: 147 147 148 148 149 -[[image:1664501677253-891.png ||_mstalt="296569"]]152 +[[image:1664501677253-891.png]] 150 150 151 151 152 152 Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot: ... ... @@ -155,14 +155,14 @@ 155 155 **__Add APP EUI in the application:__** 156 156 157 157 158 -[[image:1664501711466-918.png ||_mstalt="295828"]]161 +[[image:1664501711466-918.png]] 159 159 160 160 161 161 162 -[[image:1664501721248-725.png ||_mstalt="294450"]]165 +[[image:1664501721248-725.png]] 163 163 164 164 165 -[[image:1664501734705-405.png ||_mstalt="293306"]]168 +[[image:1664501734705-405.png]] 166 166 167 167 168 168 ... ... @@ -169,20 +169,21 @@ 169 169 **__Add APP KEY and DEV EUI:__** 170 170 171 171 172 -[[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"]] 173 173 174 174 175 175 176 176 (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device. 177 177 178 -(% 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]] 179 179 180 -[[image:1664502835802-546.png ||_mstalt="295061"]]183 +[[image:1664502835802-546.png]] 181 181 182 182 183 183 (% 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. 184 184 185 185 189 + 186 186 == 2.3 Positioning Mode(SMOD) == 187 187 188 188 ... ... @@ -195,8 +195,10 @@ 195 195 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 196 196 197 197 202 + 198 198 == 2.4 Uplink Payload == 199 199 205 + 200 200 === 2.4.1 Uplink FPORT~=5, Device Status === 201 201 202 202 ... ... @@ -206,10 +206,10 @@ 206 206 207 207 208 208 (% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %) 209 -|=(% 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;" %) 1|=(% style="width: 40px;" %)1215 +|=(% 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 210 210 |=(% 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 211 211 212 -[[image:1665301570342-765.png ||_mstalt="294580"]]218 +[[image:1665301570342-765.png]] 213 213 214 214 215 215 (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002 ... ... @@ -253,7 +253,7 @@ 253 253 (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40 254 254 255 255 (% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %) 256 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %) 1bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit262 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit 257 257 |=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings 258 258 259 259 (% style="color:blue" %)** SMOD:** ... ... @@ -276,16 +276,15 @@ 276 276 277 277 (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 278 278 279 -(% _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)(%%) 280 280 281 281 282 282 (% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 283 283 284 -(% border="1.5" style="background-color:#ffffcc; color:green; width: 412.222px" %)285 -|=(% scope="row" style="width: 75px;" %)**Size(bit)**|(% style="width:68px" %)5 Bits|(% style="width:87px" %)1 Bit|(% style="width:49px" %)1 Bit|(% style="width:126px" %)1 Bit286 -|=(% style="width: 7 5px;" %)**Value**|(% style="width:68px" %)Reserve|(% style="width:87px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:49px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]290 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %) 291 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit 292 +|=(% 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"]] 287 287 288 - 289 289 === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 290 290 291 291 ... ... @@ -304,20 +304,20 @@ 304 304 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 305 305 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 306 306 307 -[[image:1665301636888-168.png ||_mstalt="298012"]]312 +[[image:1665301636888-168.png]] 308 308 309 309 310 310 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== 311 311 312 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:2 79.222px" %)313 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width: 69px" %)163px" %)14314 -|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width: 69px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]]317 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 318 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits 319 +|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 315 315 316 316 ==== (% style="color:blue" %)**FLAG:**(%%) ==== 317 317 318 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:1 83.222px" %)319 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2 52px" %)1320 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width: 52px" %)[[LON>>||anchor="HLON:"]]323 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %) 324 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit 325 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] 321 321 322 322 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 323 323 ... ... @@ -334,12 +334,12 @@ 334 334 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: 335 335 336 336 337 -[[image:1664502116362-706.png ||_mstalt="293306"]]342 +[[image:1664502116362-706.png]] 338 338 339 339 340 340 3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 341 341 342 -[[image:1664502166010-515.png ||_mstalt="291395"]]347 +[[image:1664502166010-515.png]] 343 343 344 344 345 345 ... ... @@ -362,9 +362,6 @@ 362 362 * 3.40v ~~ 3.69v: 20% ~~ 40% 363 363 * < 3.39v: 0~~20% 364 364 365 -(% style="display:none" %) (%%) 366 - 367 - 368 368 ==== (% style="color:blue" %)**MOD:**(%%) ==== 369 369 370 370 **Example: ** (0x60>>6) & 0x3f =1 ... ... @@ -405,6 +405,7 @@ 405 405 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree// 406 406 407 407 410 + 408 408 === 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) === 409 409 410 410 ... ... @@ -420,13 +420,14 @@ 420 420 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 421 421 422 422 (% class="wikigeneratedid" %) 423 -[[image:1665301687277-443.png ||_mstalt="296140"]]426 +[[image:1665301687277-443.png]] 424 424 425 425 429 + 426 426 === 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 427 427 428 428 429 -Set [[PNACKMD=1>>||anchor="H3.2.1 1A0AutoSendNone-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. 430 430 431 431 432 432 (% style="color:red" %)**Note for this mode:** ... ... @@ -443,9 +443,10 @@ 443 443 )))|4|4|2|1|1|1|1|1 444 444 |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 445 445 446 -[[image:image-20221009160309-2.png ||_mstalt="429312"]]450 +[[image:image-20221009160309-2.png]] 447 447 448 448 453 + 449 449 === 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 450 450 451 451 ... ... @@ -470,7 +470,7 @@ 470 470 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 471 471 )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 472 472 473 -[[image:1664502425687-834.png ||_mstalt="296738"]]478 +[[image:1664502425687-834.png]] 474 474 475 475 476 476 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). ... ... @@ -481,32 +481,9 @@ 481 481 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 482 482 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 483 483 484 - (%style="display:none"%)(%%)489 +=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 485 485 486 486 487 -=== 2.4.6 Uplink FPORT~=7, Alarm information status(Since firmware 1.4.4) === 488 - 489 - 490 -The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server. 491 - 492 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 493 -|**Size(bytes)**|2|1 494 -|**Value**|[[Alarm & BAT>>path:#HAlarm26BAT:]]|Mod+lon 495 - 496 - [[image:image-20230302145315-1.png]] 497 - 498 -alarm=(bytes[0] & 0x40) ~/~/ Alarm status 499 - 500 -batV=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000; ~/~/ Battery,units:V 501 - 502 -mod = bytes[2] & 0xC0; 503 - 504 -Lon=(bytes[2] & 0x20) 505 - 506 - 507 -=== 2.4.7 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 508 - 509 - 510 510 TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **WiFi** so TrackerD will scan WiFi and find the strongest WiFi info and uplink. 511 511 512 512 ... ... @@ -519,7 +519,7 @@ 519 519 )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 520 520 521 521 (% class="wikigeneratedid" %) 522 -[[image:1667288597595-714.png|| _mstalt="299598"height="212" width="1151"]]504 +[[image:1667288597595-714.png||height="212" width="1151"]] 523 523 524 524 525 525 * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). ... ... @@ -526,21 +526,17 @@ 526 526 * (% style="color:#037691" %)**SSID: **(%%)WiFi name. 527 527 * (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 528 528 529 - (%style="display:none"%)(%%)511 +=== 2.4.7 Add Payload format in TTN V3 === 530 530 531 531 532 -=== 2.4.8 Add Payload format in TTN V3 === 533 - 534 - 535 535 In TTN V3, user can add a custom payload so it shows friendly. 536 536 537 537 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 538 538 539 539 540 -[[image:1664502649601-895.png ||_mstalt="296985"]]519 +[[image:1664502649601-895.png]] 541 541 542 542 543 - 544 544 Add the decoder from this link: 545 545 546 546 [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] ... ... @@ -547,9 +547,10 @@ 547 547 548 548 Save the change the uplink message will be parsed. As below: 549 549 550 -[[image:1664502676891-606.png ||_mstalt="296673"]]528 +[[image:1664502676891-606.png]] 551 551 552 552 531 + 553 553 == 2.5 Integrate with Datacake == 554 554 555 555 ... ... @@ -558,9 +558,10 @@ 558 558 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]] 559 559 560 560 561 -[[image:1664502695771-538.png ||_mstalt="297349"]]540 +[[image:1664502695771-538.png]] 562 562 563 563 543 + 564 564 == 2.6 Integrate with Tago == 565 565 566 566 ... ... @@ -569,70 +569,31 @@ 569 569 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]] 570 570 571 571 572 -[[image:1664502715371-321.png ||_mstalt="292162"]]552 +[[image:1664502715371-321.png]] 573 573 574 574 575 -== 2.7 Integrate with Node-red == 576 576 556 +== 2.7 Datalog Feature == 577 577 578 -~1. Install node-red, please refer to the installation method in the link: 579 579 580 - [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]] 581 - 582 - 583 -2. Import the created flow template, please refer to the import method in the link: 584 - 585 - [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]] 586 - The address of the flow template: 587 - 588 - [[dragino-end-node-decoder/TrackerD.json at main · dragino/dragino-end-node-decoder · GitHub>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/TrackerD.json]] 589 - 590 -(% style="color:red" %)**Note: If you are using NODE-RED for the first time, please search and install the two plug-ins in the figure below in node-red to fully use the flow template.** 591 - 592 -[[image:image-20230307135914-1.png||height="527" width="1045"]] 593 - 594 - 595 -[[image:image-20230307135932-2.png||height="527" width="1044"]] 596 - 597 - 598 -3. Display the map 599 - Enter the link to the map: 600 - 601 - Change its suffix to ditu:http:~/~/119.91.62.30:1880/**ditu/** 602 - 603 -**~ **[[image:image-20230308115430-1.png||height="548" width="1041"]] 604 - 605 - 606 - Hit all input in input stream 607 - 608 - [[image:image-20230308115616-2.png||height="563" width="1070"]] 609 - 610 - 611 - View map again 612 - 613 -[[image:image-20230308115701-3.png||height="571" width="1085"]] 614 - 615 - 616 -== 2.8 Datalog Feature == 617 - 618 - 619 619 total 273 entries,by default, 620 620 621 -User can set [[PNACKMD=1>>||anchor="H3.2.1 1A0AutoSendNone-ACKmessages"]], to enable Datalog feature.561 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 622 622 623 623 Example use case. 624 624 625 -[[image:image-20221009234703-2.png|| _mstalt="429143"height="328" width="899"]]565 +[[image:image-20221009234703-2.png||height="328" width="899"]] 626 626 627 627 628 -[[image:image-20221009234629-1.png|| _mstalt="431145"height="390" width="577"]]568 +[[image:image-20221009234629-1.png||height="390" width="577"]] 629 629 630 630 631 -== 2.9 Alarm Mode == 632 632 572 +== 2.8 Alarm Mode == 633 633 574 + 634 634 ((( 635 -User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. Alarm Mode is used to send SOS info to IoT platform.576 +User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 636 636 ))) 637 637 638 638 ... ... @@ -642,7 +642,7 @@ 642 642 643 643 644 644 ((( 645 - **Two ways to exit alarm mode:**586 +Two ways to exit alarm mode: 646 646 ))) 647 647 648 648 * Server sends a downlink command to exit. ... ... @@ -653,23 +653,17 @@ 653 653 ))) 654 654 655 655 656 -== 2.10 Transport Mode == 657 657 598 +== 2.9 Transport Mode == 658 658 659 -In Transport Mode, TrackerD will check if there is motion (threldhold defined by **[[PT)>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** . If there is no motion, device will send uplinks every 20 minutes (Defined by **[[TDC)>>||anchor="H3.2.1SetTransmitInterval"]]** . If there is motion, device will send uplink every 5 minutes(defined by **[[MTDC)>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]**. 660 660 661 - When device isset inTransportMode, itwill uplinkmore frequenctlyduringmoving.601 +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. 662 662 663 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation. 664 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic. 665 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion. 666 666 667 -(% style="display:none" %) (%%) 668 668 605 +== 2.10 LED Status == 669 669 670 -== 2.11 LED Status == 671 671 672 - 673 673 (% border="1.5" style="background-color:#ffffcc; width:500px" %) 674 674 |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 675 675 |(% 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 ... ... @@ -684,15 +684,12 @@ 684 684 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 685 685 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 686 686 687 - (%style="display:none"%) (%%)622 +== 2.11 Button Function == 688 688 689 689 690 -== 2.12 Button Function == 691 - 692 - 693 693 (% style="color:blue" %)**RESET button:** 694 694 695 -[[image:1664502835802-546.png ||_mstalt="295061"]]627 +[[image:1664502835802-546.png]] 696 696 697 697 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server. 698 698 ... ... @@ -699,9 +699,8 @@ 699 699 700 700 (% style="color:red" %)**RED button:** 701 701 702 -[[image: image-20230213110506-3.png]](% style="display:none" %)634 +[[image:1664502854406-763.png]] 703 703 704 -(% style="display:none" %) (%%) 705 705 706 706 (% border="1" style="background-color:#ffffcc; width:510px" %) 707 707 |=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description** ... ... @@ -709,12 +709,9 @@ 709 709 |(% 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 710 710 |(% 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. 711 711 712 - (%style="display:none"%) (%%)643 +== 2.12 USB Port Function == 713 713 714 714 715 -== 2.13 USB Port Function == 716 - 717 - 718 718 The USB interface of TrackerD has below functions: 719 719 720 720 * Power on the device ... ... @@ -722,19 +722,6 @@ 722 722 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 723 723 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 724 724 725 -(% style="display:none" %) (%%) 726 - 727 - 728 -== 2.14 Sleep Mode == 729 - 730 - 731 -(% style="color:blue" %)**Sleep Mode:**(%%) To prevent accidental touch of the red button during transportation or assembly, so the peripherals of the device are turned off and enter deep sleep. 732 - 733 -In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**. 734 - 735 -Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep. 736 - 737 - 738 738 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 739 739 740 740 ... ... @@ -743,6 +743,7 @@ 743 743 LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] 744 744 745 745 661 + 746 746 == 3.1 Access AT Command == 747 747 748 748 ... ... @@ -749,24 +749,25 @@ 749 749 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. 750 750 751 751 752 -[[image:1664502999401-486.png ||_mstalt="296985"]]668 +[[image:1664502999401-486.png]] 753 753 754 754 755 755 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: 756 756 757 757 758 -[[image:1664503022490-662.png ||_mstalt="293332"]]674 +[[image:1664503022490-662.png]] 759 759 760 760 761 -[[image:1664503035713-500.png ||_mstalt="291096"]]677 +[[image:1664503035713-500.png]] 762 762 763 763 764 -[[image:1664503047675-651.png ||_mstalt="295386"]]680 +[[image:1664503047675-651.png]] 765 765 766 -(% style="display:none" %) (%%) 767 767 683 + 768 768 == 3.2 Command Set == 769 769 686 + 770 770 === 3.2.1 Set Transmit Interval === 771 771 772 772 ... ... @@ -784,6 +784,7 @@ 784 784 (% style="color:#037691" %)**0x01 00 01 2C** (%%) ~/~/ Same as AT+TDC=300000 785 785 786 786 704 + 787 787 === 3.2.2 Set Alarm Packet transmission interval === 788 788 789 789 ... ... @@ -801,6 +801,7 @@ 801 801 (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/ Same as AT+ATDC=60000 802 802 803 803 722 + 804 804 === 3.2.3 Set Transport Mode Packet transmission interval === 805 805 806 806 ... ... @@ -818,6 +818,7 @@ 818 818 (% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+MTDC=3000000 819 819 820 820 740 + 821 821 === 3.2.4 Exit Alarm === 822 822 823 823 ... ... @@ -830,9 +830,10 @@ 830 830 (% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 831 831 832 832 833 -=== 3.2.5 Disable/Enable LED flash and buzzer === 834 834 754 +=== 3.2.5 Disable/Enable LED flash === 835 835 756 + 836 836 Disable/Enable LED for position, downlink and uplink 837 837 838 838 * (% style="color:blue" %)**AT Command:** ... ... @@ -847,6 +847,7 @@ 847 847 (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/ Same as AT+LON=0 848 848 849 849 771 + 850 850 === 3.2.6 Disable/Enable Transport Mode === 851 851 852 852 ... ... @@ -864,6 +864,7 @@ 864 864 (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+INTWK=1 865 865 866 866 789 + 867 867 === 3.2.7 Set Positioning Mode === 868 868 869 869 ... ... @@ -890,9 +890,9 @@ 890 890 891 891 (% style="color:#037691" %)**cc: ** 892 892 893 -* (% _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 894 894 895 -* (% _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(%%)) 896 896 897 897 (% style="color:blue" %)**Example:** 898 898 ... ... @@ -910,6 +910,7 @@ 910 910 (% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+SMOD=1,0,0 911 911 912 912 836 + 913 913 === 3.2.8 Set MAX GPS position time === 914 914 915 915 ... ... @@ -916,7 +916,7 @@ 916 916 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. 917 917 918 918 919 -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. 920 920 921 921 922 922 * (% style="color:blue" %)**AT Command:** ... ... @@ -931,6 +931,7 @@ 931 931 (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/ Set AT+FTIME=150 932 932 933 933 858 + 934 934 === 3.2.9 Set PDOP value for GPS fix accuracy === 935 935 936 936 ... ... @@ -954,8 +954,8 @@ 954 954 (% style="color:#037691" %)**0xAD 00 46** (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7) 955 955 956 956 957 -=== 3.2.10 Disable/Enable the confirmation mode === 958 958 883 +Disable/Enable the confirmation mode 959 959 960 960 * (% style="color:blue" %)**AT Command:** 961 961 ... ... @@ -974,9 +974,10 @@ 974 974 (% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1 975 975 976 976 977 -=== 3.2.11 Auto Send None-ACK messages === 978 978 903 +=== 3.2.10 Auto Send None-ACK messages === 979 979 905 + 980 980 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. 981 981 982 982 ... ... @@ -992,12 +992,13 @@ 992 992 993 993 * (% style="color:blue" %)**Downlink Command: 0x34** 994 994 995 -Example: 0x34 921 +Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 996 996 997 997 998 -=== 3.2.12 Set BLEMASK to filter BLE iBeacon === 999 999 925 +=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 1000 1000 927 + 1001 1001 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. 1002 1002 1003 1003 (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.** ... ... @@ -1004,18 +1004,19 @@ 1004 1004 1005 1005 (% style="color:blue" %)**AT Command:** 1006 1006 1007 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456934 + (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 1008 1008 1009 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK936 + (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 1010 1010 1011 1011 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 1012 1012 1013 -Example: 0xB2 940 +Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 1014 1014 1015 1015 1016 -=== 3.2.13 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 1017 1017 944 +=== 3.2.12 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 1018 1018 946 + 1019 1019 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. 1020 1020 1021 1021 (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.** ... ... @@ -1022,61 +1022,44 @@ 1022 1022 1023 1023 (% style="color:blue" %)**AT Command:** 1024 1024 1025 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456953 + (% style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456 1026 1026 1027 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK955 + (% style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK 1028 1028 1029 1029 (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)** 1030 1030 1031 -Example: 0xB3 959 +Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 1032 1032 1033 1033 1034 -=== 3.2.14 Disable/Enable Information printing(Since firmware 1.4.1) === 1035 1035 963 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 1036 1036 965 + 1037 1037 Users can use this feature to enable/disable Information printing. 1038 1038 1039 1039 (% style="color:blue" %)**AT Command:** 1040 1040 1041 -(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/ 970 +(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/(Disable (0), Enable (1), default:0) 1042 1042 \\Example: AT+SHOWID=1 ~-~-> Enable Information printing. 1043 1043 1044 1044 1045 -=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 1046 1046 975 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 1047 1047 977 + 1048 1048 The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. 1049 1049 1050 1050 (% style="color:blue" %)**AT Command:** 1051 1051 1052 -(% style="color:#037691" %)**AT+CHE=1 982 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode 1053 1053 1054 1054 1055 1055 (% style="color:blue" %)**Downlink Payload:0X24** 1056 1056 1057 -Example: 0x24 01 987 +Example: 0x24 01 ~/~/ Same as AT+CHE=1 1058 1058 1059 1059 1060 -=== 3.2.16 Get or Set Threshold for motion detect(Since firmware 1.4.3) === 1061 1061 1062 - 1063 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event. 1064 - 1065 -(% style="color:blue" %)**AT Command:** 1066 - 1067 -(% style="color:#037691" %)**AT+PT=xx** 1068 - 1069 - Example: 1070 - 1071 - AT+PT=14 ~-~-> Set to detect car motion. 1072 - 1073 - AT+PT=41 ~-~-> set to detect walk motion. 1074 - 1075 - 1076 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%) 1077 -0xB4 14 ~/~/ Same as AT+PT=14 1078 - 1079 - 1080 1080 = 4. Setting for Different Scenarios = 1081 1081 1082 1082 ... ... @@ -1083,6 +1083,7 @@ 1083 1083 1084 1084 = 5. Upload Firmware = 1085 1085 997 + 1086 1086 == 5.1 Firmware Change Log == 1087 1087 1088 1088 ... ... @@ -1089,6 +1089,7 @@ 1089 1089 **[[See this link>>url:https://github.com/dragino/TrackerD]]** 1090 1090 1091 1091 1004 + 1092 1092 == 5.2 How to upgrade firmware == 1093 1093 1094 1094 ... ... @@ -1109,10 +1109,10 @@ 1109 1109 (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32 1110 1110 1111 1111 1112 -[[image:1664503563660-578.png ||_mstalt="296777"]]1025 +[[image:1664503563660-578.png]] 1113 1113 1114 1114 1115 -[[image:1664503574618-659.png ||_mstalt="297986"]]1028 +[[image:1664503574618-659.png]] 1116 1116 1117 1117 1118 1118 ... ... @@ -1121,7 +1121,7 @@ 1121 1121 [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]] 1122 1122 1123 1123 1124 - **Users need to use below files:**1037 +Users need to use below files: 1125 1125 1126 1126 boot_app0.bin @0e000 1127 1127 ... ... @@ -1128,19 +1128,22 @@ 1128 1128 US915.bin @ 0x10000(Select the bin file of the frequency band you need) 1129 1129 1130 1130 1131 -[[image:image-20221 207120501-1.png]]1044 +[[image:image-20221118105220-2.png]] 1132 1132 1133 1133 1134 1134 1135 1135 After upgrade finish, it will show finish as below: 1136 1136 1137 -[[image:image-20221 207133911-7.png]]1050 +[[image:image-20221118105402-4.png]] 1138 1138 1139 1139 1053 + 1140 1140 = 6. Developer Guide = 1141 1141 1056 + 1142 1142 == 6.1 Compile Source Code == 1143 1143 1059 + 1144 1144 === 6.1.1 Set up ARDUINO compile environment === 1145 1145 1146 1146 ... ... @@ -1149,81 +1149,24 @@ 1149 1149 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]] 1150 1150 1151 1151 1152 -[[image:1664503635019-941.png ||_mstalt="294658"]]1068 +[[image:1664503635019-941.png]] 1153 1153 1154 1154 1155 1155 1156 1156 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 1157 1157 1158 -[[image:1664503715811-892.png ||_mstalt="295698"]]1074 +[[image:1664503715811-892.png]] 1159 1159 1160 1160 1161 -=== 6.1.2 Build the development environment === 1162 - 1163 - 1164 -**~1. Download and install arduino IDE** 1165 - 1166 -[[https:~~/~~/www.arduino.cn/thread-5838-1-1.html>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fwww.arduino.cn%2Fthread-5838-1-1.html]] 1167 - 1168 - 1169 -**2. Download the ESP32 development package in the arduino IDE** 1170 - 1171 -[[image:image-20221213100007-1.png]] 1172 - 1173 - 1174 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]] 1175 - 1176 -[[image:image-20221213100626-2.png]] 1177 - 1178 - 1179 -Restart the IDE after the addition is complete, then: 1180 - 1181 -[[image:image-20221213100808-3.png||height="679" width="649"]] 1182 - 1183 - 1184 -[[image:image-20221213101040-4.png]] 1185 - 1186 - 1187 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03. 1188 -Don't quit halfway.~~! If you quit halfway, there is a high probability that it will freeze, and you will need to download again next time. (If you click to continue downloading, an error will be reported after completion)** 1189 - 1190 - 1191 -Then enter a long waiting process. If you don't want to wait, you can go to the Internet to download directly, and then import: 1192 - 1193 -(% style="color:blue" %)**Methods as below:** 1194 - 1195 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]] 1196 - 1197 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here. 1198 - 1199 1199 (% 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. 1200 1200 1201 -[[image:image-2022121 3102311-5.png||height="582" width="711"]]1079 +[[image:image-20221024105643-1.png]] 1202 1202 1203 - 1204 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)** 1205 - 1206 -[[image:image-20221213102334-6.png]] 1207 - 1208 -(% style="color:red" %)**Note: This step requires a python environment** 1209 - 1210 - 1211 -Either way, in the end: 1212 - 1213 -The final effect is to open the arduino and you can see the esp32 1214 - 1215 -[[image:image-20221213110952-8.png||height="866" width="711"]] 1216 - 1217 - 1218 - 1219 -[[image:image-20221024105643-1.png||_mstalt="428129"]] 1220 - 1221 1221 **~ Figure1** 1222 1222 1223 1223 1084 +[[image:image-20221024105643-2.png]] 1224 1224 1225 -[[image:image-20221024105643-2.png||_mstalt="428493"]] 1226 - 1227 1227 **Figure2** 1228 1228 1229 1229 ... ... @@ -1232,31 +1232,34 @@ 1232 1232 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: 1233 1233 1234 1234 1235 -[[image:1664503752288-974.png ||_mstalt="298194"]]1094 +[[image:1664503752288-974.png]] 1236 1236 1237 1237 1097 + 1238 1238 == 6.2 Source Code == 1239 1239 1240 1240 1241 1241 * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:** 1242 1242 1243 -[[image:1664503794261-827.png ||_mstalt="296387"]]1103 +[[image:1664503794261-827.png]] 1244 1244 1245 1245 1246 1246 1247 1247 * (% style="color:blue" %)**Click to upload** 1248 1248 1249 -[[image:1664503808294-336.png ||_mstalt="295711"]]1109 +[[image:1664503808294-336.png]] 1250 1250 1251 1251 1252 1252 1253 1253 * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 1254 1254 1255 -[[image:1664503824081-592.png ||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]1115 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 1256 1256 1257 1257 1118 + 1258 1258 = 7. FAQ = 1259 1259 1121 + 1260 1260 == 7.1 How to change the LoRa Frequency Bands/Region? == 1261 1261 1262 1262 ... ... @@ -1263,10 +1263,11 @@ 1263 1263 User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download. 1264 1264 1265 1265 1128 + 1266 1266 == 7.2 What is the pin mapping for the USB program cable? == 1267 1267 1268 1268 1269 -[[image:1664499635206-262.png ||_mstalt="295360"]]1132 +[[image:1664499635206-262.png]] 1270 1270 1271 1271 1272 1272 ... ... @@ -1281,11 +1281,9 @@ 1281 1281 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 1282 1282 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 1283 1283 1284 -(% style="display:none" %) (%%) 1285 - 1286 - 1287 1287 == 7.3 Notes on using different serial port tools for TrackerD == 1288 1288 1149 + 1289 1289 === 7.3.1 Serial port utility === 1290 1290 1291 1291 ... ... @@ -1293,16 +1293,18 @@ 1293 1293 1294 1294 Need to adjust the data stream to RTS/CTS on physical restart. 1295 1295 1157 + 1296 1296 (% class="wikigeneratedid" %) 1297 -[[image:image-20221102140621-1.png ||_mstalt="425672"]]1159 +[[image:image-20221102140621-1.png]] 1298 1298 1299 1299 1300 - 1301 1301 When using AT commands, the data flow needs to be adjusted to XON/XOFF 1302 1302 1303 -[[image:image-20221102140638-2.png||_mstalt="428727"]] 1304 1304 1165 +[[image:image-20221102140638-2.png]] 1305 1305 1167 + 1168 + 1306 1306 === 7.3.2 SecureCRT === 1307 1307 1308 1308 ... ... @@ -1309,22 +1309,23 @@ 1309 1309 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. 1310 1310 1311 1311 1312 -[[image:image-20221102140704-3.png ||_mstalt="427076"]]1175 +[[image:image-20221102140704-3.png]] 1313 1313 1314 1314 1315 -[[image:image-20221102140712-4.png ||_mstalt="427089"]]1178 +[[image:image-20221102140712-4.png]] 1316 1316 1317 1317 1181 + 1318 1318 === 7.3.3 PUTTY === 1319 1319 1320 1320 1321 -[[image:image-20221102140748-5.png ||_mstalt="430456"]]1185 +[[image:image-20221102140748-5.png]] 1322 1322 1323 1323 1324 1324 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. 1325 1325 1326 1326 1327 -[[image:image-20221102140801-6.png ||_mstalt="427466"]]1191 +[[image:image-20221102140801-6.png]] 1328 1328 1329 1329 1330 1330 == 7.4 How to modify source code to compile different frequency band bin file? == ... ... @@ -1336,58 +1336,38 @@ 1336 1336 See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]] 1337 1337 ))) 1338 1338 1339 - **~1.**1203 +1.When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file. 1340 1340 1205 +[[image:image-20221116111844-1.png||height="227" width="782"]] 1341 1341 1342 - [[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). 1343 1343 1209 +[[image:image-20221116111844-2.png||height="262" width="781"]] 1344 1344 1211 +3.Compile the AS923_JP band, please refer to the intention shown 1345 1345 1346 - **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"]] 1347 1347 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. 1348 1348 1349 -[[image:image-20221116111844- 2.png||_mstalt="429052"height="262" width="781"]]1217 +[[image:image-20221116111844-4.png||height="641" width="739"]] 1350 1350 1219 +[[image:image-20221116111844-5.png||height="551" width="708"]] 1351 1351 1352 1352 1353 -**3. Compile the AS923_JP band, please refer to the intention shown** 1354 1354 1355 - 1356 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]] 1357 - 1358 - 1359 - 1360 -**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.** 1361 - 1362 - 1363 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]] 1364 - 1365 - 1366 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]] 1367 - 1368 - 1369 -== 7.5 Are there example python example for BLE Indoor Positioning? == 1370 - 1371 - 1372 -[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]] 1373 - 1374 - 1375 -== 7.6 Can alert mode and transport mode be used together? == 1376 - 1377 - 1378 -Yes, you can also press the panic button to sound the alarm if set to transport mode 1379 - 1380 - 1381 1381 = 8 Trouble Shooting = 1382 1382 1225 + 1383 1383 == 8.1 TDC is changed to 4294947296 and cause no uplink. == 1384 1384 1385 1385 1386 1386 ((( 1387 -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 1388 1388 ))) 1389 1389 1390 1390 1234 + 1391 1391 == 8.2 Device not able get AT Command or show output after wake up from deep sleep mode == 1392 1392 1393 1393 ... ... @@ -1396,152 +1396,46 @@ 1396 1396 ))) 1397 1397 1398 1398 1243 + 1399 1399 == 8.3 Problem after Upgrading Firmware == 1400 1400 1401 -=== 8.3.1 "rst: (0x3 SW_RESET)" andContinue Restart after upgrading ===1246 +=== 8.3.1 Continue Restart after upgrading === 1402 1402 1403 1403 1404 -**Error Output** 1405 - 1406 - 1407 -[[image:image-20221122100004-4.png||_mstalt="424606"]] 1408 - 1409 - 1410 1410 ((( 1411 -Some partition is missed during upgrade, please upgrade below four files as example: 1412 - 1413 -[[image:image-20221207120524-2.png]] 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 1414 1414 ))) 1415 1415 1416 1416 1417 - === 8.3.2 TrackerD's led light isalways GREEN on after upgrading===1254 +[[image:image-20221118105249-3.png]] 1418 1418 1419 1419 1257 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1258 + 1420 1420 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 1421 1421 1422 1422 1423 -=== 8.3.3 "flash read err" after upgrade firmware === 1262 +((( 1263 +== 8.5 How to deal with unsuccessful GPS positioning? == 1424 1424 1425 - 1426 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue. 1427 - 1428 - 1429 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]] 1430 - 1431 - 1432 -User need to upgrade again with below four files to solve this issue. 1433 - 1434 - [[image:image-20221207120530-3.png]] 1435 - 1436 - **Figure 2** 1437 - 1438 - 1439 -=== 8.3.4 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware === 1440 - 1441 - 1442 -User might erase the entire flash include keys and default settings which cause this issue. 1443 - 1444 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below. 1445 - 1446 - 1447 -[[image:image-20221122100004-3.png||_mstalt="424242"]] 1448 - 1449 - 1450 -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. 1451 - 1452 -After AT+FDR. please set 1453 - 1454 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7** 1455 - 1456 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000** 1457 - 1458 -**Example:** 1459 - 1460 -AT+PDOP=7.00 1461 - 1462 -AT+FTIME=180 1463 - 1464 -AT+DEUI=70B3D57ED0053981 1465 - 1466 -AT+APPEUI=D23345667BCBCCAF 1467 - 1468 -AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1 1469 - 1470 -AT+DADDR=260b4dce ( no need for OTAA) 1471 - 1472 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d ( no need for OTAA) 1473 - 1474 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA) 1475 - 1476 - 1477 -== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1478 - 1479 - 1480 -Please download version 1.4.2 again 1481 - 1482 - 1483 -== 8.5 How to deal with unsuccessful GPS positioning? == 1484 - 1485 - 1486 -1) Make Sure the device is in Open Area where can see the sky. 1487 - 1265 +1) Make Sure the device is in Open Area where can see the sky. 1488 1488 2) Set PDOP to a higher value. 1489 1489 1490 - *(%_mstmutation="1"style="color:blue"%)**AT+PDOP=2**(%%)(can be positioned precisely.)1268 + AT+PDOP=2(can be positioned precisely.) 1491 1491 1492 - *(%_mstmutation="1"style="color:blue"%)**AT+PDOP=7**(%%)(Quickly locate in open spaces)1270 + AT+PDOP=7(Quickly locate in open spaces) 1493 1493 1494 - *(%_mstmutation="1"style="color:blue"%)**AT+PDOP=14.7**(%%)(Positioning can be acquired in complex environments)1272 + AT+PDOP=14.7(Positioning can be acquired in complex environments) 1495 1495 1496 1496 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 1275 +))) 1497 1497 1498 1498 1499 -== 8.6 upgrading thefirmware,the datais notcompletelyerased, andthe informationdoesnot returnto normal after multipleresets ==1278 +== 8.6 When positioning, it will restart or the PDOP setting is unsuccessful == 1500 1500 1280 +Please download version 1.4.2 again 1501 1501 1502 -When upgrading, use the erase button to upgrade 1503 1503 1504 -[[image:image-20221207120536-4.png]] 1505 - 1506 - 1507 -The parameters are displayed abnormally and cannot be fixed using AT+FDR 1508 - 1509 -[[image:image-20221128103040-2.png||height="431" width="525"]] 1510 - 1511 - 1512 -Please upgrade these four files,link(The boot_app0 file is in the version folder you need) 1513 - 1514 -[[image:image-20221207134028-8.png]] 1515 - 1516 - 1517 -Reboot information after upgrade 1518 - 1519 -[[image:image-20221128111443-4.png||height="432" width="546"]] 1520 - 1521 - 1522 -Use **AT+FDR** command to reset and then use **AT+CFG** to check whether the configuration is back to normal 1523 - 1524 -[[image:image-20221128111850-5.png]] 1525 - 1526 - 1527 -After the parameters return to normal, upgrade to the version you need again 1528 - 1529 -[[image:image-20221207120601-5.png]] 1530 - 1531 - 1532 -At this point, the parameters return to normal after running AT+FDR again 1533 - 1534 -[[image:image-20221128112035-7.png]] 1535 - 1536 - 1537 -== 8.7 If you encounter the following problems, please upgrade to the latest version == 1538 - 1539 - 1540 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond. 1541 - 1542 -2. Send some commands through the serial port to prompt an error (Example:AT+SMOD=1,0,1) 1543 - 1544 - 1545 1545 = 9. Order Info = 1546 1546 1547 1547 ... ... @@ -1550,22 +1550,13 @@ 1550 1550 (% style="color:blue" %)**XXX**(%%): The default frequency band 1551 1551 1552 1552 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433 1553 - 1554 1554 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868 1555 - 1556 1556 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865 1557 - 1558 1558 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920 1559 - 1560 1560 * (% style="color:red" %)**AS923**(%%): Default frequency band AS923 1561 - 1562 1562 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 1563 - 1564 1564 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1565 1565 1566 -(% style="display:none" %) (%%) 1567 - 1568 - 1569 1569 = 10. Packing Info = 1570 1570 1571 1571 ... ... @@ -1572,36 +1572,22 @@ 1572 1572 (% style="color:#037691" %)**Package Includes**: 1573 1573 1574 1574 * TrackerD LoRaWAN GPS/BLE Tracker x 1 1575 - 1576 1576 * USB recharge & program cable x 1 1577 1577 1578 1578 (% style="color:#037691" %)**Dimensions and Weight**: 1579 1579 1580 1580 * Device Size: 85 x 48 x 15 mm 1581 - 1582 1582 * Weight: 50g 1583 1583 1584 -(% style="display:none" %) (%%) 1585 - 1586 - 1587 1587 = 11. Support = 1588 1588 1589 1589 1590 1590 * 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. 1591 - 1592 1592 * 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]]. 1593 1593 1594 -(% style="display:none" %) (%%) 1595 - 1596 - 1597 1597 = 12. Reference = 1598 1598 1599 1599 1600 1600 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1601 - 1602 1602 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1603 - 1604 1604 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 1605 - 1606 - 1607 -)))
- image-20221122100004-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -127.2 KB - Content
- image-20221122100004-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -12.5 KB - Content
- image-20221122100004-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -22.3 KB - Content
- 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
- image-20221207120501-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -44.5 KB - Content
- image-20221207120524-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -44.5 KB - Content
- image-20221207120530-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -44.5 KB - Content
- image-20221207120536-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -44.5 KB - Content
- image-20221207120601-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -44.5 KB - Content
- image-20221207133836-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -52.1 KB - Content
- image-20221207133911-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -46.3 KB - Content
- image-20221207134028-8.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -49.3 KB - Content
- image-20221213100007-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -32.7 KB - Content
- image-20221213100626-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -35.7 KB - Content
- image-20221213100808-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -91.3 KB - Content
- image-20221213101040-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -26.3 KB - Content
- image-20221213102311-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -49.7 KB - Content
- image-20221213102334-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -52.5 KB - Content
- image-20221213102718-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -116.5 KB - Content
- image-20221213110952-8.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -152.8 KB - Content
- image-20230213110119-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -182.3 KB - Content
- image-20230213110214-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -182.3 KB - Content
- image-20230213110506-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -19.8 KB - Content
- image-20230302145315-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -35.1 KB - Content
- image-20230307135914-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -131.8 KB - Content
- image-20230307135932-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -109.7 KB - Content
- image-20230308115430-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -2.4 MB - Content
- image-20230308115616-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -152.7 KB - Content
- image-20230308115701-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -2.4 MB - Content