Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Bei Jinggeng on 2025/07/23 11:03
From version 88.1
edited by Kilight Cao
on 2022/11/01 15:59
on 2022/11/01 15:59
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 14 removed)
- 1664505654417-133.png
- 1665301570342-765.png
- 1665301636888-168.png
- 1665301687277-443.png
- 1665301786397-168.png
- 1667288597595-714.png
- image-20221006181316-1.png
- image-20221006181357-2.png
- image-20221009160220-1.png
- image-20221009160309-2.png
- image-20221009234629-1.png
- image-20221009234703-2.png
- image-20221024105643-1.png
- image-20221024105643-2.png
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Kilight1 +XWiki.Xiaoling - Content
-
... ... @@ -1,13 +7,6 @@ 1 -(% style="text-align:center" %) 2 -[[image:1664505654417-133.png]] 3 - 4 - 5 - 6 - 7 7 (% class="wikigeneratedid" %) 8 8 **Table of Contents:** 9 9 10 -{{toc/}} 11 11 12 12 13 13 ... ... @@ -14,10 +14,9 @@ 14 14 15 15 = 1. Introduction = 16 16 10 +== 1.1 OverView == 17 17 18 -== 1.1 What is TrackerD == 19 19 20 - 21 21 ((( 22 22 TrackerD is an (% style="color:blue" %)**Open Source LoRaWAN Tracker**(%%) based on (% style="color:blue" %)**ESP32 MCU**(%%) and (% style="color:blue" %)**Semtech LoRa Wireless Chip**. 23 23 ))) ... ... @@ -25,14 +25,10 @@ 25 25 ((( 26 26 In TrackerD, there are various sensors such as GPS, WiFi, BLE, Temperature, Humidity, Motion Detection, and Buzzer. User can use TrackerD for different tracking scenario. 27 27 28 -((( 29 29 TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution. 30 -))) 31 31 32 -((( 33 33 The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services. 34 34 ))) 35 -))) 36 36 37 37 ((( 38 38 TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network. ... ... @@ -46,7 +46,6 @@ 46 46 (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.** 47 47 48 48 49 - 50 50 == 1.2 Specifications == 51 51 52 52 ... ... @@ -61,11 +61,13 @@ 61 61 * EEPROM: 520 KB 62 62 * Clock Speed: 32Mhz 63 63 51 + 64 64 (% style="color:blue" %)**Common DC Characteristics:** 65 65 66 66 * Supply Voltage: 5V via USB port or Internal li-on battery 67 67 * Operating Temperature: -40 ~~ 60°C 68 68 57 + 69 69 (% style="color:blue" %)**LoRa Spec:** 70 70 71 71 * Frequency Range, ... ... @@ -87,10 +87,12 @@ 87 87 * Packet engine up to 256 bytes with CRC. 88 88 * LoRaWAN 1.0.3 Specification 89 89 79 + 90 90 (% style="color:blue" %)**Battery:** 91 91 92 92 * 1000mA Li-on Battery power (for model TrackerD) 93 93 84 + 94 94 (% style="color:blue" %)**Power Consumption** 95 95 96 96 * Sleeping Mode: 200uA ... ... @@ -97,6 +97,9 @@ 97 97 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm 98 98 * Tracking: max: 38mA 99 99 91 + 92 + 93 + 100 100 == 1.3 Features == 101 101 102 102 ... ... @@ -103,7 +103,7 @@ 103 103 * LoRaWAN 1.0.3 Class A 104 104 * ESP32 PICO D4 105 105 * SX1276/78 Wireless Chip 106 -* Arduino IDE Compatible 100 +* Arduino IDE Compatible 107 107 * Open source hardware / software 108 108 * Regular/ Real-time GPS,BLE,WIFI tracking 109 109 * Built-in3 axis accelerometer (LIS3DH) ... ... @@ -115,6 +115,8 @@ 115 115 * Tri-color LED, Alarm button 116 116 * Datalog 117 117 112 + 113 + 118 118 == 1.4 Applications == 119 119 120 120 ... ... @@ -121,9 +121,11 @@ 121 121 * Logistics and Supply Chain Management 122 122 * Human tracking 123 123 124 -= 2.1 Use TrackerD = 125 125 126 126 122 + 123 += 2.1 Use TrackerD = 124 + 127 127 == 2.1 How it works? == 128 128 129 129 ... ... @@ -130,556 +130,352 @@ 130 130 TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA. 131 131 132 132 133 - 134 134 == 2.2 Quick guide to connect to LoRaWAN server == 135 135 133 +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. 136 136 137 -Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example. 138 138 136 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]] 139 139 140 -[[image:1664501652064-326.png]] 141 141 142 - 143 - 144 144 The LPS8N is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. What the rest need to is register this device in TTN V3: 145 145 141 +**(% style="color:blue" %)Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD. 146 146 147 -(% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD. 148 - 149 149 Each TrackerD is shipped with a sticker with the default device EUI as below: 150 150 145 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]] 151 151 152 -[[image:1664501677253-891.png]] 153 153 154 154 149 + 155 155 Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot: 156 156 157 157 158 - **__Add APP EUI in the application:__**153 +Add APP EUI in the application 159 159 155 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]] 160 160 161 -[[image: 1664501711466-918.png]]157 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]] 162 162 163 163 160 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]] 164 164 165 -[[image:1664501721248-725.png]] 166 166 167 167 168 - [[image:1664501734705-405.png]]164 +Add APP KEY and DEV EUI 169 169 166 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]] 170 170 171 171 172 -**__Add APP KEY and DEV EUI:__** 173 173 174 174 175 - [[image:1664501784668-703.png]]171 +**(% style="color:blue" %)Step 2**:(%%) Power on TrackerD by using the on board switch. 176 176 177 177 174 +**(% 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. 178 178 179 179 180 -(% style="color:blue" %) **Step 2**:(%%)PoweronTrackerD by usingtheon boardswitch.177 +**(% style="color:blue" %)Positioning Mode(SMOD):** 181 181 179 +* **GPS ONLY(Factory Settings): **only get GPS location info. 180 +* **BLE ONLY: **Only obtain iBeacon info via BLE. Design for Indoor tracking. 181 +* **GPS/BLE Hybrid: **Combination for Indoor and Outdoor tracking. 182 182 183 - (%style="color:blue"%)**Step 3:**(%%) TrackerDwill autojointothe LoRaWANnetwork. After joinsuccess, TrackerDwill starttoupload messagetoIoT server.183 +User can switch modes by [[changing SMOD>>path:#Positioning_Mode]]. 184 184 185 185 186 +== 2.3 Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~- == 186 186 187 -== 2.3 Positioning Mode(SMOD) == 188 188 189 +=== 2.3.1 Uplink FPORT=5, Device Status === 189 189 190 -Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 191 191 192 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 193 -* (% style="color:#037691" %)**BLE or WiFi ONLY: **(%%)** **Only obtain iBeacon info via BLE and uplink or obtain wifi ssid info via WiFi and uplink. Design for Indoor tracking. 194 -* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking. Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 195 195 196 - Userscanswitchmodesby[[changingSMOD>>||anchor="H3.2.7SetPositioningMode"]].193 +=== 2.3.2 Uplink FPORT= , Realtime GNSS Positioning === 197 197 195 +The default uplink payload includes totally 11 bytes. (User can use AT+MOD=0 to enable the Temperature and humidity sensor to hum/tem info from accelerometer. When accelerometer info is enable, total payload will be 15 bytes, please note 15 bytes won’t work on DR0 on US915/AU915 frequency band. ) 198 198 199 199 200 -== 2.4 Uplink Payload == 198 +|((( 199 +**Size** 201 201 201 +**(bytes)** 202 +)))|4|4|2|1|((( 203 +2 202 202 203 -=== 2.4.1 Uplink FPORT~=5, Device Status === 204 - 205 - 206 -Uplink the device configures with FPORT=5. Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours. 207 - 208 -Use can also get the Device Status uplink through the downlink command: **Downlink: 0x2301** 209 - 210 - 211 -(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %) 212 -|=(% 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 213 -|=(% 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 214 - 215 -[[image:1665301570342-765.png]] 216 - 217 - 218 -(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002 219 - 220 -(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13 221 - 222 -(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version 223 - 224 -(% style="color:#037691" %)**Frequency Band**: 225 - 226 -*0x01: EU868 227 - 228 -*0x02: US915 229 - 230 -*0x03: IN865 231 - 232 -*0x04: AU915 233 - 234 -*0x05: KZ865 235 - 236 -*0x06: RU864 237 - 238 -*0x07: AS923 239 - 240 -*0x08: AS923-1 241 - 242 -*0x09: AS923-2 243 - 244 -*0x0a: AS923-3 245 - 246 -Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF) 247 - 248 -(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD. 249 - 250 - 251 -(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV 252 - 253 -Use can also get the Device Status uplink through the downlink command: 254 - 255 - 256 -(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40 257 - 258 -(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %) 259 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit 260 -|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings 261 - 262 -(% style="color:blue" %)** SMOD:** 263 - 264 -(% style="color:red" %)** 1 :** (%%) GPS ONLY 265 - 266 -(% style="color:red" %)** 2 :** (%%) BLE ONLY 267 - 268 -(% style="color:red" %)** 3 :** (%%) GPS/BLE Hybrid 269 - 270 - 271 -(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload** 272 - 273 -(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values 274 - 275 -(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values 276 - 277 - 278 -(% style="color:blue" %)** BLE_Settings:** 279 - 280 -(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 281 - 282 -(% style="color:red" %)** 2:** (%%) WiFi Positioning with Strongest WiFi SSID(V1.4.1 Version support this function later) 283 - 284 - 285 -(% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 286 - 287 -(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %) 288 -|=(% 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 289 -|=(% 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"]] 290 - 291 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 292 - 293 - 294 -Users can use **AT+SMOD=1,0,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes, 295 - 296 - 297 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %) 298 -|=(% scope="row" style="width: 60px;" %)((( 299 -**Size(bytes)** 300 -)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)((( 205 +(optional ) 206 +)))|((( 301 301 2 302 -)))|(% style="width:30px" %)((( 303 -2 304 -))) 305 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 306 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 307 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 308 308 309 -[[image:1665301636888-168.png]] 310 - 311 - 312 -==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== 313 - 314 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 315 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits 316 -|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 317 - 318 -==== (% style="color:blue" %)**FLAG:**(%%) ==== 319 - 320 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %) 321 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit 322 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] 323 - 324 -**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 325 - 326 - 327 -==== (% style="color:blue" %)**Location info:**(%%) ==== 328 - 329 -* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976// 330 -* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 331 - 332 -(% style="color:red" %)**Important note:** 333 - 334 -1. When power is low (<2.84v), GPS won't be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF. 335 - 336 -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: 337 - 338 - 339 -[[image:1664502116362-706.png]] 340 - 341 - 342 -3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 343 - 344 -[[image:1664502166010-515.png]] 345 - 346 - 347 - 348 -==== (% style="color:blue" %)**Alarm:**(%%) ==== 349 - 350 -**Example: ** 0x4B & 0x40 >> 6 = 0x01 351 - 352 - 353 -==== (% style="color:blue" %)**BAT:**(%%) ==== 354 - 355 -**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV). 356 - 357 -((( 358 -The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \ 209 +(optional) 359 359 ))) 211 +|**Value**|[[Latitude>>path:#Location]]|[[Longitude>>path:#Location]]|((( 212 +[[Alarm &>>path:#Alarm]] 360 360 361 -* > 4.0v : 80% ~~ 100% 362 -* 3.85v ~~3.99v: 60% ~~ 80% 363 -* 3.70v ~~ 3.84v: 40% ~~ 60% 364 -* 3.40v ~~ 3.69v: 20% ~~ 40% 365 -* < 3.39v: 0~~20% 214 +[[BAT>>path:#Alarm]] 215 +)))|[[FLAG>>path:#Flag]]|Hum|[[Tem>>path:#Pitch]] 366 366 367 -==== (% style="color:blue" %)**MOD:**(%%) ==== 368 368 369 - **Example:** (0x60>>6) & 0x3f =1218 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]] 370 370 371 -**Set the format of GPS data uplink link:** 372 372 373 -(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values 374 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values 221 +**Alarm & BAT:** 375 375 223 +|**Size(bit)**|1 bit|1bit|14 bits 224 +|**Value**|reserve|Alarm Indicate|[[BAT>>path:#BAT]] 376 376 377 -** Set the format of BLE data uplink link:**226 +**FLAG:** 378 378 379 -(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon 228 +|**Size(bit)**|2 bits|1bit|5 bits 229 +|**Value**|[[MOD>>path:#MD]]|[[LON>>path:#LON]]|Firmware version 380 380 381 381 382 -==== (% style="color:blue" %)**LON:**(%%) ==== 383 383 384 -**Example: **(0x60>>5)&0x01=1.233 +**Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A ** 385 385 386 -Enable/Disable LED activity for uplink 387 387 388 -((( 389 -(% style="color:#037691" %)**0x00:** (%%) Disable LED indicator. 390 -))) 236 +**Location info:** 391 391 392 -((( 393 -(% style="color:#037691" %)**0x01:** (%%) Enable LED indicator (Default Value) 394 -))) 238 +* Latitude: 02863D68⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// 395 395 240 +//value = 02863D68 /1000000 = 42.351976// 396 396 397 - ====(% style="color:blue" %)**Hum:**(%%)====242 +* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// 398 398 399 - 0202 =//if(0x0202&0x8000=0): value =//0x0202/+514 ⇒ 51.4degree244 +//value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 400 400 401 401 402 - ==== (% style="color:blue"%)**Tem:**(%%) ====247 +Important note: 403 403 404 -011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree// 249 +1. When power is low (<2.84v), GPS won’t be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF. 250 +1. In firmware version v1.5, Roll & Pitch is disabled by default. 251 +1. When enable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accept only 11 bytes payload. In this case, the payload on server will be ignore and shows as below: 405 405 253 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]] 406 406 407 407 408 - === 2.4.3UplinkFPORT~=3,RealtimeGNSSPositioning(DefaultMode)===256 +1. While GPS can’t get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 409 409 258 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]] 410 410 411 -The default uplink payload includes total 11 bytes (**AT+SMOD=1,1,0**). The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity) 260 +* **Alarm**: Example: 0x4B & 0x40 >> 6 = 0x01 261 +* **BAT**: Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV). 412 412 263 +The battery info shows the current voltage, for **TrackerD** version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \ 413 413 414 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %) 415 -|=(% scope="row" style="width: 60px;" %)((( 416 -**Size(bytes)** 417 -)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1 418 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 419 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 420 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 421 421 422 -(% class="wikigeneratedid" %) 423 -[[image:1665301687277-443.png]] 266 +* > 4.0v : 80% ~~ 100% 267 +* 3.85v ~~3.99v: 60% ~~ 80% 268 +* 3.70v ~~ 3.84v: 40% ~~ 60% 269 +* 3.40v ~~ 3.69v: 20% ~~ 40% 270 +* < 3.39v: 0~~20% 424 424 425 425 273 +* **LON: **Enable/Disable LED activity for uplink 426 426 427 - ===2.4.4 Uplink FPORT~=4, HistoryGNSSPositioning ===275 +0x00: Disable LED indicator. 428 428 277 +0x01: Enable LED indicator (Default Value) 429 429 430 -Set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery. 431 431 280 +* **Hum**: 0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree 281 +* **//Tem//**//: 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree 432 432 433 -(% style="color:red" %)**Note for this mode:** 434 434 435 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server. 436 -* b) TrackerD will send data in (% style="color:blue" %)**CONFIRMED Mode**(%%) when PNACKMD=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages. 437 -* c) the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes of payload. In this case (DR0 of US915/AU915), the payload on server will show NULL 438 438 439 - Thepayloadis15bytes,asbelow.285 +=== 2.3.3 Uplink FPORT= , History GNSS Positioning === 440 440 441 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 442 -|=(% scope="row" %)((( 443 -**Size(bytes)** 444 -)))|4|4|2|1|1|1|1|1 445 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 446 446 447 -[[image:image-20221009160309-2.png]] 448 448 289 +=== 2.3.4 BLE positioning Payload(Fport=2) === 449 449 291 +Different MODE has different payload: 450 450 451 - === 2.4.5 Uplink FPORT~=6, BLEPositioning with Strongest iBeacon===293 +**MODE=2** 452 452 295 +|((( 296 +**Size** 453 453 454 -TrackerD supports BLE scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan BLE iBeacon and find the strongest iBeacon info and uplink. 298 +**(bytes)** 299 +)))|16|4|4|2|4|2|1 300 +|**Value**|[[UUID>>path:#Location]]|((( 301 +iBeacon 455 455 456 -User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings. 303 +MAJOR 304 +)))|((( 305 +iBeacon 457 457 307 +MINOR 308 +)))|((( 309 +iBeacon Measured 458 458 459 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 460 -|=(% scope="row" style="width: 60px;" %)((( 461 -**Size(bytes)** 462 -)))|(% style="width:30px" %)16|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:120px" %)2|(% style="width:50px" %)4|(% style="width:50px" %)2|(% style="width:30px" %)1 463 -|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)((( 464 -iBeacon MAJOR 465 -)))|(% style="width:63px" %)((( 466 -iBeacon MINOR 467 -)))|(% style="width:71px" %)((( 468 -iBeacon Measured Power 469 -)))|(% style="width:50px" %)((( 470 -iBeacon RSSI 471 -)))|(% style="width:47px" %)((( 472 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 473 -)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 311 +Power 312 +)))|((( 313 +iBeacon 474 474 475 -[[image:1664502425687-834.png]] 315 +RSSI 316 +)))|((( 317 +[[Alarm &>>path:#Alarm]] 476 476 319 +[[BAT>>path:#Alarm]] 320 +)))|[[FLAG>>path:#Flag]] 477 477 478 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 479 -* (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 480 -* (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 481 -* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. 482 -* (% style="color:#037691" %)**MINOR:** (%%)The MAJOR from the strongest iBeacon. 483 -* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 484 -* (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 485 485 323 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]] 486 486 487 487 488 -=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID === 326 +* **BAT**: Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV). 327 +* **MODE: **Define the payload format. 328 +* **UUID: **The uuid from the strongest iBeacon. 329 +* **MAJOR**: The MAJOR from the strongest iBeacon. 330 +* **MINOR**: The MAJOR from the strongest iBeacon. 331 +* **Measured** **Power**: The Measured Power from the strongest iBeacon. 332 +* **RSSI**: The RSSI from the strongest iBeacon. 489 489 490 490 491 -TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan WiFi and find the strongest WiFi info and uplink. 492 492 336 +=== 2.3.5 Add Payload format in TTN V3 === 493 493 494 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %) 495 -|=(% scope="row" style="width: 60px;" %)((( 496 -**Size(bytes)** 497 -)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1 498 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)((( 499 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 500 -)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 338 +In TTN V3, use can add a custom payload so it shows friendly. 501 501 502 -(% class="wikigeneratedid" %) 503 -[[image:1667288597595-714.png||height="212" width="1151"]] 340 +In the page Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder 504 504 342 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]] 505 505 506 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 507 -* (% style="color:#037691" %)**SSID: **(%%)WiFi name. 508 -* (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 344 +Add the decoder from this link: 509 509 510 510 347 +Save the change the uplink message will be parsed. As below: 511 511 512 - === 2.4.7Add Payload formatTTN V3 ===349 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]] 513 513 514 514 515 -In TTN V3, user can add a custom payload so it shows friendly. 516 516 517 -In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 518 518 519 519 520 - [[image:1664502649601-895.png]]355 +== 2.4 Integrate with Datacake == 521 521 522 522 523 -Add t hedecoderfromthislink:358 +After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot. 524 524 525 -[[http s:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]360 +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]] 526 526 527 - Savethehangethe uplinkmessagewill be parsed.As below:362 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]] 528 528 529 -[[image:1664502676891-606.png]] 530 530 365 +== 2.5 Integrate with Tago == 531 531 532 532 533 -== 2.5 Integrate with Datacake == 534 - 535 - 536 536 After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot. 537 537 538 -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]] 539 - 540 -[[image:1664502695771-538.png]] 541 - 542 - 543 - 544 -== 2.6 Integrate with Tago == 545 - 546 - 547 -After TrackerD sends data to LoRaWAN server such as TTN, user can pass the data to Datacake and plot out, currently only support GPS plot. 548 - 549 549 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]] 550 550 372 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]] 551 551 552 552 553 -[[image:1664502715371-321.png]] 554 554 555 555 377 +== 2.6 Alarm Mode == 556 556 557 -== 2.7 Datalog Feature == 558 558 380 +User can push the **RED button** by more than 5 seconds to enter Alarm Mode. 559 559 560 -total 273 entries,by default, 561 561 562 - Usercanset[[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]],toenableDatalogfeature.383 +Once enter Alarm mode, the **GREEN LED** will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exit alert mode. 563 563 564 -Example use case. 565 565 566 -[[image:image-20221009234703-2.png||height="328" width="899"]] 567 - 568 - 569 -[[image:image-20221009234629-1.png||height="390" width="577"]] 570 - 571 - 572 - 573 -== 2.8 Alarm Mode == 574 - 575 - 576 -((( 577 -User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 578 -))) 579 - 580 - 581 -((( 582 -Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exits alert mode. 583 -))) 584 - 585 - 586 -((( 587 587 Two ways to exit alarm mode: 588 -))) 589 589 590 -* Server send sa downlink command to exit.388 +* Server send a downlink command to exit. 591 591 * User fast press the RED button 10 times. 592 592 593 -((( 594 -When exit alarm mode, (% style="color:red" %)**RED LED**(%%) will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false. 595 -))) 391 +When exit alarm mode, **RED LED** will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false. 596 596 597 597 394 +== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- == 598 598 599 -== 2.9 Transport Mode == 600 600 601 601 602 - InTransportMode,TrackerDwill check ifthere is motion. If there is no motion, device will senduplinksevery 20 minutes. If there is motion, device will send uplink every 5 minutes.398 +== 2.8 LED Status == 603 603 604 604 401 +|**Event**|**Action**|**AT+LON to control on/off** 402 +|**Power On**|**BLUE, RED , Green** flash once|N/A 403 +|**Join request**|**Green** led fast blink once (200ms)|Yes 404 +|**Join Success**|**Green** led on 5 second|N/A 405 +|**Fixing Location**|**BLUE **blinks 200ms per second|Yes 406 +|**Fixed and uplink**|**GREEN **blinks twice (200ms per blink)|Yes 407 +|**Fail Fix and uplink**|**RED **blinks twice (200ms per blink)|Yes 408 +|**Enter Alarm mode**|**RED **on for 3 seconds|Yes 409 +|**Uplink under Alarm**|**RED **on for 1 second|Yes 410 +|**Exit Alarm**|**BLUE **led on 5 second|Yes 411 +|**Get Downlink**|**GREEN** led on 1 second|Yes 412 +|**Movement Detect**|**RED **on 500ms|N/A 605 605 606 -== 2.10 LED Status == 607 607 608 608 609 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 610 -|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 611 -|(% 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 612 -|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes 613 -|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A 614 -|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes 615 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes 616 -|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes 617 -|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes 618 -|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes 619 -|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes 620 -|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 621 -|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 622 622 623 -== 2.11 Button Function == 624 624 418 +== 2.9 Button Function == 625 625 626 - (% style="color:blue" %)**RESET button:**420 +**RESET button:** 627 627 628 -[[image: 1664502835802-546.png]]422 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]] 629 629 630 630 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server. 631 631 632 632 633 - (% style="color:red" %)**RED button:**427 +**RED button:** 634 634 635 -[[image: 1664502854406-763.png]]429 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]] 636 636 431 +|**Function**|**Action**|**Description** 432 +|Send Alarm|Keep Pressing **RED** button for more than 5 seconds|Enter Alarm Mode. See [[Alarm Mode>>path:#Alarm_Mode]] 433 +|Exit Alarm Mode|Fast press the **RED** button 10 times|Exit Alarm Mode 434 +|Enter Deep Sleep Mode|Press and hold the button for 10 seconds, then quickly press the device 3 times to enter deep sleep|This is the mode ship out from factory. CPU will be complete in sleep mode and no LoRa activity, only use before deploy. 637 637 638 -(% border="1" style="background-color:#ffffcc; color:green; width:510px" %) 639 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description** 640 -|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode. See [[Alarm Mode>>||anchor="H2.6AlarmMode"]] 641 -|(% 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 642 -|(% 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. 643 643 644 -== 2.12 USB Port Function == 645 645 646 646 439 +== 2.10 USB Port Function == 440 + 647 647 The USB interface of TrackerD has below functions: 648 648 649 649 * Power on the device 650 650 * Recharge the battery 651 -* [[Configure Device>> ||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]652 -* [[Upgrade Firmware>> ||anchor="H5.UploadFirmware"]]445 +* [[Configure Device>>path:#AT_Command]] 446 +* [[Upgrade Firmware>>path:#upgrade_image]] 653 653 654 -= 3. Configure TrackerD via AT command or LoRaWAN downlink = 655 655 656 656 657 -User can configure TrackerD via AT Command or LoRaWAN Downlink. 658 658 659 -LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] 660 660 452 += 3. Configure TrackerD via AT command or LoRaWAN downlink = 661 661 662 662 663 - ==3.1AccessAT Command==455 +User can configure TrackerD via AT Command or LoRaWAN Downlink. 664 664 457 +LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]] 665 665 666 -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. 667 667 460 +== 3.1 Access AT Command == 668 668 669 - [[image:1664502999401-486.png]]462 +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. ... 670 670 464 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]] 671 671 672 -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: 673 673 467 +In PC, User needs to set serial tool baud rate to **115200** to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands: 674 674 675 -[[image:1664503022490-662.png]] 676 676 470 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]] 677 677 678 -[[image:1664503035713-500.png]] 679 679 680 680 681 -[[image: 1664503047675-651.png]]474 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]] 682 682 476 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]] 683 683 684 684 685 685 == 3.2 Command Set == ... ... @@ -687,150 +687,137 @@ 687 687 688 688 === 3.2.1 Set Transmit Interval === 689 689 690 - 691 691 Set device uplink interval. 692 692 693 -* (% style="color:blue" %)**AT Command:**486 +* AT Command: 694 694 695 - (% style="color:#037691" %)**AT+TDC=xxx**488 +AT+TDC=xxx 696 696 697 -Example: 490 +Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds) 698 698 699 699 700 -* (% style="color:blue" %)**Downlink Payload (prefix 0x01):**493 +* Downlink Payload (prefix 0x01): 701 701 702 - (% style="color:#037691" %)**0x01 00 01 2C**(%%)~/~/495 +0x01 00 01 2C ~/~/ Same as AT+TDC=300000 703 703 704 704 705 - 706 706 === 3.2.2 Set Alarm Packet transmission interval === 707 707 708 - 709 709 Set alarm packet transmit interval 710 710 711 -* (% style="color:blue" %)**AT Command:**502 +* AT Command: 712 712 713 - (% style="color:#037691" %)**AT+ATDC=xx.**504 +AT+ATDC=xx. 714 714 715 -Example: **~-~-> **Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000506 +Example: AT+ATDC=60000 à Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000 716 716 717 717 718 -* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**509 +* Downlink Payload (prefix 0xB1): 719 719 720 - (% style="color:#037691" %)**0xB1 00 00 3C** (%%)~/~/511 +0xB1 00 00 3C ~/~/Same as AT+ATDC=60000 721 721 722 722 514 +=== 3.3.3 Set Sports Mode Packet transmission interval === 723 723 724 - === 3.2.3SetTransportMode Packet transmissioninterval===516 +Set sports packet transmit interval 725 725 518 +* AT Command: 726 726 727 - SetTransportModepacket transmit interval520 +AT+MTDC=xx. 728 728 729 - *(%style="color:blue"%)**ATCommand:**522 + Example: AT+MTDC=300000 à Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000 730 730 731 -(% style="color:#037691" %)**AT+MTDC=xx. ** 732 732 733 - Example: AT+MTDC=300000**~-~->** Set Transport Mode Packet Intervalto 300 seconds. TrackerDwill send every300 secondsin Transport mode, DefaultValue: 300000525 +* Downlink Payload (prefix 0x03): 734 734 527 +0x03 00 01 2C ~/~/Same as AT+ MTDC=3000000 735 735 736 -* (% style="color:blue" %)**Downlink Payload (prefix 0x03):** 737 737 738 -(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+ MTDC=3000000 739 739 531 +=== 3.3.4 Exit Alarm === 740 740 741 - 742 -=== 3.2.4 Exit Alarm === 743 - 744 - 745 745 Server send downlink command to exit Alarm mode 746 746 747 -* (% style="color:blue" %)**AT Command:No AT Command**535 +* AT Command: 748 748 749 - * (% style="color:blue"%)**DownlinkPayload(prefix 0x02):**537 +No AT Command 750 750 751 -(% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 752 752 540 +* Downlink Payload (prefix 0x02): 753 753 542 +0x02 01 ~/~/ Exit Alarm Mode 754 754 755 -=== 3.2.5 Disable/Enable LED flash === 756 756 545 +=== 3.3.5 Disable/Enable LED flash === 757 757 758 758 Disable/Enable LED for position, downlink and uplink 759 759 760 -* (% style="color:blue" %)**AT Command:**549 +* AT Command: 761 761 762 - (% style="color:#037691" %)**AT+LON=xx. (Disable (0), Enable (1), default:1)**551 +AT+LON=xx. (Disable (0), Enable (1), default:1) 763 763 764 -Example: AT+LON=0 **~-~-> **Disable LED for position, downlink and uplink.553 + Example: AT+LON=0 à Disable LED for position, downlink and uplink. 765 765 766 766 767 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**556 +* Downlink Payload (prefix 0xAE): 768 768 769 - (% style="color:#037691" %)**0xAE 00** (%%)~/~/558 +0xAE 00 ~/~/Same as AT+LON=0 770 770 771 771 772 772 773 -=== 3.2.6 Disable/Enable Transport Mode === 774 774 563 +=== 3.3.6 Disable/Enable movement detect (Debug Only) === 775 775 776 -User scan use this feature to enable/disableTransportMode.565 +User can use this feature to check and set thread hole of movement detect 777 777 778 -* (% style="color:blue" %)**AT Command:**567 +* AT Command: 779 779 780 - (% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)**569 +AT+INTWK=xx. (Disable (0), Enable (1), default:0) 781 781 782 -Example: **~-~-> **EnableTransportMode.571 + Example: AT+ INTWK =1 à Enable detect movement. 783 783 784 784 785 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**574 +* Downlink Payload (prefix 0xAF): 786 786 787 - (% style="color:#037691" %)**0xAF 01** (%%)~/~/576 +0xAF 01 ~/~/Same as AT+ INTWK =1 788 788 789 789 790 790 791 -=== 3. 2.7 Set Positioning Mode ===580 +=== 3.3.7 Set Positioning Mode === 792 792 582 +SMOD define the how TrackerD scan and uplink date. 793 793 794 -S MODdefine how TrackerD scan and uplinkdata:584 +GPS室外定位模式:设备默认模式,设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是3分钟定位,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。GPS还有一种logdata模式,在断网的情况下将数据存储下来,等到有网的时候,一次将数据以每10秒上报。 795 795 586 + BLE室内定位模式:设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是5秒,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每3分钟发送一次)。 796 796 797 - *(%style="color:blue"%)**ATCommand:**588 + GPS和BLE混动模式:设备入网后会发送device当前模式下的信息,随后立即判断是否在室内,如果是就进行BLE定位,不是就GPS定位。如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。 798 798 799 - (% style="color:#037691" %)**AT+SMOD=aa,bb,cc**590 +运动模式:设备入网后会发送device当前模式下的信息,随后发送GPS定位数据,设备判断是否在运动,没有运动传感器没有检测到动作,立即进入静止状态(默认20分钟),如果产生运动,将每5分钟发送一次数据,再第五分钟后检测设备有误运动,无将切换到静止状态,有立即发送数据。 800 800 801 -(% style="color:#037691" %)** aa:** 802 802 803 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 804 -* (% style="color:red" %)**2: BLE or WiFi ONLY: **(%%)Only obtain iBeacon info via BLE and uplink or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking. 805 -* (% style="color:red" %)**3: GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 806 806 807 -(% style="color:#037691" %)**bb:** 808 808 809 -* (% style="color:red" %)**0 : **(%%)GPS+ BAT+ State+Tem&Hum 810 -* (% style="color:red" %)**1 :**(%%) GPS +BAT State 595 +* AT Command: 811 811 812 - (% style="color:#037691"%)**cc: **597 +AT+SMOD=xx. 813 813 814 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 815 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%)) 599 + Example: 816 816 817 - (%style="color:blue"%)**Example:**601 + AT+ SMOD =1,0 à GPS+ BAT+ State+Tem&Hum 818 818 819 - AT+ SMOD =1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 820 - AT+ SMOD =1,1,0 ~-~-> GPS +BAT State 821 - AT+ SMOD =2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 822 - AT+ SMOD =2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State 603 + AT+ SMOD =1,1 à GPS +BAT State 823 823 605 + AT+ SMOD =2,3 à (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。 824 824 825 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** 826 826 827 - (%style="color:#037691"%)**0xA501 00 00** (%%)~/~/ Same as AT+ SMOD =1,0,0608 +* Downlink Payload (prefix 0xA5): 828 828 610 +0xA5 01 00 ~/~/ Same as AT+ SMOD =1,0 829 829 830 830 831 -=== 3. 2.8 Set MAX GPS position time ===613 +=== 3.3.8 Set MAX GPS position time === 832 832 833 - 834 834 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. 835 835 836 836 ... ... @@ -837,123 +837,63 @@ 837 837 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. 838 838 839 839 840 -* (% style="color:blue" %)**AT Command:**621 +* AT Command: 841 841 842 - (% style="color:#037691" %)**AT+FTIME=xx**(%%)**~-~-> **Set to use xx as max fix time.623 +AT+FTIME=xx à Set to use xx as max fix time. 843 843 844 - **Example:**AT+FTIME=150625 +Example: AT+FTIME=150 845 845 846 846 847 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**628 +* Downlink Payload (prefix 0xAA): 848 848 849 - (% style="color:#037691" %)**0xAA 00 96** (%%)~/~/630 +0xAA 00 96 ~/~/Set AT+FTIME=150 850 850 851 851 852 852 853 -=== 3.2.9 Set PDOP value for GPS fix accuracy === 854 854 635 +=== 3.3.9 Set PDOP value for GPS fix accuracy === 855 855 856 -PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can 't get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server.637 +PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can’t get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server. 857 857 858 858 859 859 A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0 860 860 861 861 862 -* (% style="color:blue" %)**AT Command:**643 +* AT Command: 863 863 864 - (% style="color:#037691" %)**AT+PDOP=2.5** (%%) **~-~->**Set PDOP to 2.5645 +AT+PDOP=2.5 à Set PDOP to 2.5 865 865 866 866 867 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**648 +* Downlink Payload (prefix 0xAD): 868 868 869 - (% style="color:#037691" %)**0xAD 00 0A**(%%)~/~/650 +0xAD 00 0A ~/~/Set AT+PDOP=1 (0x0A / 10 =1) 870 870 871 - (% style="color:#037691" %)**0xAD 00 19**(%%)~/~/652 +0xAD 00 19 ~/~/Set AT+PDOP=2.5 (0x19 / 10 =2.5) 872 872 873 - (% style="color:#037691" %)**0xAD 00 46**(%%)654 +0xAD 00 46 ~/~/Set AT+PDOP=7 (0x46 / 10 =7) 874 874 875 - 876 - 877 877 Disable/Enable the confirmation mode 878 878 879 -* (% style="color:blue" %)**AT Command:**658 +* AT Command: 880 880 881 - (% style="color:#037691" %)**AT+CFM=xx**660 +AT+CFM=xx. 882 882 662 + Example: 883 883 884 - **~Example:**664 + AT+ CFM=0 à Disable confirmation 885 885 886 - AT+ CFM= 0**~-~->** Disable confirmation666 + AT+ CFM=1 à Enable confirmation 887 887 888 - AT+ CFM=1 **~-~-> ** Enable confirmation 889 889 669 +* Downlink Payload (prefix 0x05): 890 890 891 - *(%style="color:blue"%)**Downlink Payload(prefix0x05):**671 +0x05 01 ~/~/ Same as AT+ SMOD =1 892 892 893 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+ SMOD =1 894 894 895 895 896 896 897 -=== 3.2.10 Auto Send None-ACK messages === 898 898 899 899 900 -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. 901 - 902 - 903 -* (% style="color:blue" %)**AT Command: AT+PNACKMD** 904 - 905 -The default factory setting is 0. 906 - 907 - 908 -**Command Example Function Response:** 909 - 910 -(% style="color:#037691" %)**AT+PNACKMD=1** (%%) ~/~/ Poll None-ACK message OK 911 - 912 - 913 -* (% style="color:blue" %)**Downlink Command: 0x34** 914 - 915 -Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 916 - 917 - 918 - 919 -=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 920 - 921 - 922 -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. 923 - 924 -(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.** 925 - 926 -(% style="color:blue" %)**AT Command:** 927 - 928 - (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 929 - 930 - (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 931 - 932 - 933 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)** 934 - 935 -Example: 0xA5010203040506 ~/~/ Set BLEMASK to 123456 936 - 937 - 938 -=== 3.2.12 Set WiFIMASK to filter WiFi SSID === 939 - 940 - 941 -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. It will ignore all other WiFi which doesn’t contact 123456 in the SSID. 942 - 943 -(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.** 944 - 945 -(% style="color:blue" %)**AT Command:** 946 - 947 - (% style="color:#037691" %)**AT+ WiFiMASK =123456** (%%) ~/~/ Set WiFiMASK = 123456 948 - 949 - (% style="color:#037691" %)**AT+ WiFiMASK =0** (%%) ~/~/ disable WiFiMASK 950 - 951 - 952 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)** 953 - 954 -Example: 0xA5010203040506 ~/~/ Set WiFiMASK to 123456 955 - 956 - 957 957 = 4. Setting for Different Scenarios = 958 958 959 959 ... ... @@ -963,43 +963,38 @@ 963 963 964 964 == 5.1 Firmware Change Log == 965 965 966 - 967 967 **[[See this link>>url:https://github.com/dragino/TrackerD]]** 968 968 969 969 970 - 971 971 == 5.2 How to upgrade firmware == 972 972 692 +User can use the TrackerD ’s USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below: 973 973 974 -User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below: 975 975 695 +**(% style="color:blue" %)Step1: **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD. 976 976 977 -(% style="color:blue" %) **Step1:ConnectTrackerDand PCvia USB cableshippedwithTrackerD.697 +**(% style="color:blue" %)Step2:** (%%) Install CH9102 driver in the PC. 978 978 979 - 980 -(% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC. 981 - 982 982 After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager. 983 983 984 984 985 -(% style="color:blue" %) **Step3:**(%%)Download and Install Flash Tool:[[https:~~/~~/www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools]]702 +**(% style="color:blue" %)Step3:**(%%) Download and Install Flash Tool: 986 986 704 +[[https:~~/~~/www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools]] 987 987 988 -(% style="color:blue" %) **Step4:**706 +**(% style="color:blue" %)Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32 989 989 990 990 991 -[[image: 1664503563660-578.png]]709 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png||alt="image-20220712083115-1.png"]] 992 992 711 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png||alt="image-20220712083115-2.png"]] 993 993 994 -[[image:1664503574618-659.png]] 995 995 714 +**(% style="color:blue" %)Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 996 996 716 +[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 997 997 998 -(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 999 999 1000 -[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]] 1001 - 1002 - 1003 1003 Users need to use below files: 1004 1004 1005 1005 boot_app0.bin @0e000 ... ... @@ -1006,17 +1006,16 @@ 1006 1006 1007 1007 ESP_LORA-eeprom-class.bin @ 0x10000 1008 1008 725 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png||alt="image-20220712083115-3.png"]] 1009 1009 1010 - [[image:1664503593459-435.png]]727 +After upgrade finish, it will show finish as below: 1011 1011 729 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png||alt="image-20220712083115-4.png"]] 1012 1012 1013 1013 1014 -After upgrade finish, it will show finish as below: 1015 1015 1016 -[[image:1664503611848-385.png]] 1017 1017 1018 1018 1019 - 1020 1020 = 6. Developer Guide = 1021 1021 1022 1022 ... ... @@ -1026,59 +1026,49 @@ 1026 1026 === 6.1.1 Set up ARDUINO compile environment === 1027 1027 1028 1028 1029 -* **Download the latest Arduino software (IDE) from the Arduino official website: [[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]]**744 +* Download the latest Arduino software (IDE) from the Arduino official website 1030 1030 1031 - 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]]746 +[[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]] 1032 1032 748 +Install IDE on PC, open and click 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]] 1033 1033 1034 -[[image: 1664503635019-941.png]]750 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]] 1035 1035 752 +* Go to tools ~-~-> Boards ~-~-> Boards Manager, find the esp32 information and install it. 1036 1036 754 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]] 1037 1037 1038 -* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 1039 1039 1040 - [[image:1664503715811-892.png]]757 +* Download the latest TrackerD from the dragino github 1041 1041 759 +[[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]] 1042 1042 1043 -(% 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. 1044 1044 1045 - [[image:image-20221024105643-1.png]]762 +Put the Library in the TrackerD directory into the libraries file in the Arduino directory 1046 1046 1047 - **~ Figure1**764 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]] 1048 1048 1049 1049 1050 -[[image:image-20221024105643-2.png]] 1051 1051 1052 - **Figure2** 1053 1053 1054 - 1055 -* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]** 1056 - 1057 -Put the Library in the TrackerD directory into the libraries file in the Arduino directory: 1058 - 1059 - 1060 -[[image:1664503752288-974.png]] 1061 - 1062 - 1063 - 1064 1064 == 6.2 Source Code == 1065 1065 1066 1066 1067 -* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**772 +* Open the example in the TrackerD file, please select the correct port in the IDE, as shown below: 1068 1068 1069 -[[image: 1664503794261-827.png]]774 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]] 1070 1070 776 +* Click to upload 1071 1071 778 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]] 1072 1072 1073 -* (%style="color:blue"%)**Clicktoupload**780 +* Check the result, if the upload is successful, as shown below, open the serial port to view the data 1074 1074 1075 -[[image:1664503808294-336.png]] 1076 1076 783 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]] 1077 1077 1078 1078 1079 -* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 1080 1080 1081 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 1082 1082 1083 1083 1084 1084 ... ... @@ -1085,10 +1085,11 @@ 1085 1085 = 7. FAQ = 1086 1086 1087 1087 793 + 1088 1088 == 7.1 How to change the LoRa Frequency Bands/Region? == 1089 1089 1090 1090 1091 -User can follow the introduction for [[how to upgrade image>> ||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.797 +User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download. 1092 1092 1093 1093 1094 1094 ... ... @@ -1099,8 +1099,8 @@ 1099 1099 1100 1100 1101 1101 1102 -(% border=" 1.5"cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)1103 -| =(% style="width:;" %)**Pin**|=(% style="width:;" %)**Color**|=(% style="width:;" %)**USB Pin**808 +(% border="2" style="background-color:#ffffcc; color:green; width:314px" %) 809 +|(% style="width:118px" %)**Pin**|(% style="width:67px" %)**Color**|(% style="width:123px" %)**USB Pin** 1104 1104 |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC 1105 1105 |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A) 1106 1106 |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A) ... ... @@ -1118,6 +1118,7 @@ 1118 1118 (% style="color:blue" %)**XXX**(%%): The default frequency band 1119 1119 1120 1120 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433 827 +* (% style="color:red" %)**CN470**(%%): Default frequency band CN470 1121 1121 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868 1122 1122 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865 1123 1123 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920 ... ... @@ -1125,25 +1125,33 @@ 1125 1125 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 1126 1126 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1127 1127 835 + 1128 1128 = 9. Packing Info = 1129 1129 1130 1130 1131 - (% style="color:#037691" %)**Package Includes**:839 +**Package Includes**: 1132 1132 1133 -* TrackerD LoRaWAN GPS/BLE Tracker x 1 1134 -* USB recharge & program cable x 1 841 +* TrackerD x 1 842 +* Rechargeable cable x 1 843 +* Program Cable x 1 1135 1135 1136 - (% style="color:#037691" %)**Dimensions and Weight**:845 +**Dimensions and Weight**: 1137 1137 1138 -* Device Size: 85 x 48 x 15 cm1139 -* Weight: 5 0g847 +* Device Size: 85 x 48 x 15 mm/pcs 848 +* Weight: 55g/pcs 1140 1140 1141 -= 10. Support = 1142 1142 1143 1143 852 += 10. Support = 853 + 1144 1144 * 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. 1145 -* 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]].855 +* 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 1146 1146 857 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]] 858 + 859 + 860 + 861 + 1147 1147 = 11. Reference = 1148 1148 1149 1149
- 1664505654417-133.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -27.5 KB - Content
- 1665301570342-765.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.6 KB - Content
- 1665301636888-168.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -36.6 KB - Content
- 1665301687277-443.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -22.6 KB - Content
- 1665301786397-168.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -22.6 KB - Content
- 1667288597595-714.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -27.9 KB - Content
- image-20221006181316-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -17.7 KB - Content
- image-20221006181357-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -88.0 KB - Content
- image-20221009160220-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -46.4 KB - Content
- image-20221009160309-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -57.2 KB - Content
- image-20221009234629-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -222.9 KB - Content
- image-20221009234703-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -136.4 KB - Content
- image-20221024105643-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -11.3 KB - Content
- image-20221024105643-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -64.5 KB - Content