Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Bei Jinggeng on 2025/08/01 17:45
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 40 removed)
- 1664503715811-892.png
- 1664503752288-974.png
- 1664503794261-827.png
- 1664503808294-336.png
- 1664503824081-592.png
- 1664503831430-500.png
- 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
- image-20221102140621-1.png
- image-20221102140638-2.png
- image-20221102140704-3.png
- image-20221102140712-4.png
- image-20221102140748-5.png
- image-20221102140801-6.png
- image-20221107145243-1.png
- image-20221116111844-1.png
- image-20221116111844-2.png
- image-20221116111844-3.png
- image-20221116111844-4.png
- image-20221116111844-5.png
- image-20221118104359-1.png
- image-20221118105220-2.png
- image-20221118105249-3.png
- image-20221118105402-4.png
- image-20221122100004-1.png
- image-20221122100004-2.png
- image-20221122100004-3.png
- image-20221122100004-4.png
Details
- Page properties
-
- 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,7 +14,7 @@ 14 14 15 15 = 1. Introduction = 16 16 17 -== 1.1 What is TrackerD==10 +== 1.1 OverView == 18 18 19 19 20 20 ((( ... ... @@ -24,14 +24,10 @@ 24 24 ((( 25 25 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. 26 26 27 -((( 28 28 TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution. 29 -))) 30 30 31 -((( 32 32 The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services. 33 33 ))) 34 -))) 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. ... ... @@ -59,11 +59,13 @@ 59 59 * EEPROM: 520 KB 60 60 * Clock Speed: 32Mhz 61 61 51 + 62 62 (% style="color:blue" %)**Common DC Characteristics:** 63 63 64 64 * Supply Voltage: 5V via USB port or Internal li-on battery 65 65 * Operating Temperature: -40 ~~ 60°C 66 66 57 + 67 67 (% style="color:blue" %)**LoRa Spec:** 68 68 69 69 * Frequency Range, ... ... @@ -85,10 +85,12 @@ 85 85 * Packet engine up to 256 bytes with CRC. 86 86 * LoRaWAN 1.0.3 Specification 87 87 79 + 88 88 (% style="color:blue" %)**Battery:** 89 89 90 90 * 1000mA Li-on Battery power (for model TrackerD) 91 91 84 + 92 92 (% style="color:blue" %)**Power Consumption** 93 93 94 94 * Sleeping Mode: 200uA ... ... @@ -97,6 +97,7 @@ 97 97 98 98 99 99 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) ... ... @@ -125,8 +125,9 @@ 125 125 126 126 127 127 128 -= 2. Use TrackerD = 129 129 123 += 2.1 Use TrackerD = 124 + 130 130 == 2.1 How it works? == 131 131 132 132 ... ... @@ -135,850 +135,551 @@ 135 135 136 136 == 2.2 Quick guide to connect to LoRaWAN server == 137 137 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. 138 138 139 -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. 140 140 136 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]] 141 141 142 -[[image:1664501652064-326.png]] 143 143 144 - 145 - 146 146 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: 147 147 141 +**(% style="color:blue" %)Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD. 148 148 149 -(% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD. 150 - 151 151 Each TrackerD is shipped with a sticker with the default device EUI as below: 152 152 145 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]] 153 153 154 -[[image:1664501677253-891.png]] 155 155 156 156 149 + 157 157 Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot: 158 158 159 159 160 - **__Add APP EUI in the application:__**153 +Add APP EUI in the application 161 161 155 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]] 162 162 163 -[[image: 1664501711466-918.png]]157 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]] 164 164 165 165 160 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]] 166 166 167 -[[image:1664501721248-725.png]] 168 168 169 169 170 - [[image:1664501734705-405.png]]164 +Add APP KEY and DEV EUI 171 171 166 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]] 172 172 173 173 174 -**__Add APP KEY and DEV EUI:__** 175 175 176 176 177 - [[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"]]171 +**(% style="color:blue" %)Step 2**:(%%) Power on TrackerD by using the on board switch. 178 178 179 179 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. 180 180 181 -(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device. 182 182 183 -(% id="cke_bm_7709S"style="display:none" %)[[image:1664502835802-546.png]]177 +**(% style="color:blue" %)Positioning Mode(SMOD):** 184 184 185 -[[image:1664502835802-546.png]] 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. 186 186 183 +User can switch modes by [[changing SMOD>>path:#Positioning_Mode]]. 187 187 188 -(% 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. 189 189 186 +== 2.3 Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~- == 190 190 191 -== 2.3 Positioning Mode(SMOD) == 192 192 189 +=== 2.3.1 Uplink FPORT=5, Device Status === 193 193 194 -Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 195 195 196 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 197 -* (% 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. 198 -* (% 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. 199 199 200 - Userscanswitchmodesby[[changingSMOD>>||anchor="H3.2.7SetPositioningMode"]].193 +=== 2.3.2 Uplink FPORT= , Realtime GNSS Positioning === 201 201 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. ) 202 202 203 -== 2.4 Uplink Payload == 204 204 205 -=== 2.4.1 Uplink FPORT~=5, Device Status === 198 +|((( 199 +**Size** 206 206 201 +**(bytes)** 202 +)))|4|4|2|1|((( 203 +2 207 207 208 -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. 209 - 210 -Use can also get the Device Status uplink through the downlink command: **Downlink: 0x2301** 211 - 212 - 213 -(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %) 214 -|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1 215 -|=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status 216 - 217 -[[image:1665301570342-765.png]] 218 - 219 - 220 -(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002 221 - 222 -(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13 223 - 224 -(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version 225 - 226 -(% style="color:#037691" %)**Frequency Band**: 227 - 228 -*0x01: EU868 229 - 230 -*0x02: US915 231 - 232 -*0x03: IN865 233 - 234 -*0x04: AU915 235 - 236 -*0x05: KZ865 237 - 238 -*0x06: RU864 239 - 240 -*0x07: AS923 241 - 242 -*0x08: AS923-1 243 - 244 -*0x09: AS923-2 245 - 246 -*0x0a: AS923-3 247 - 248 -Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF) 249 - 250 -(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD. 251 - 252 - 253 -(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV 254 - 255 -Use can also get the Device Status uplink through the downlink command: 256 - 257 - 258 -(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40 259 - 260 -(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %) 261 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit 262 -|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings 263 - 264 -(% style="color:blue" %)** SMOD:** 265 - 266 -(% style="color:red" %)** 1 :** (%%) GPS ONLY 267 - 268 -(% style="color:red" %)** 2 :** (%%) BLE ONLY 269 - 270 -(% style="color:red" %)** 3 :** (%%) GPS/BLE Hybrid 271 - 272 - 273 -(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload** 274 - 275 -(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values 276 - 277 -(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values 278 - 279 - 280 -(% style="color:blue" %)** BLE_Settings:** 281 - 282 -(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 283 - 284 -(% style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%) 285 - 286 - 287 -(% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 288 - 289 -(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %) 290 -|=(% 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 291 -|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]] 292 - 293 - 294 - 295 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 296 - 297 - 298 -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, 299 - 300 - 301 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %) 302 -|=(% scope="row" style="width: 60px;" %)((( 303 -**Size(bytes)** 304 -)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)((( 205 +(optional ) 206 +)))|((( 305 305 2 306 -)))|(% style="width:30px" %)((( 307 -2 308 -))) 309 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 310 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 311 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 312 312 313 -[[image:1665301636888-168.png]] 314 - 315 - 316 -==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== 317 - 318 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 319 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits 320 -|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 321 - 322 - 323 - 324 -==== (% style="color:blue" %)**FLAG:**(%%) ==== 325 - 326 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %) 327 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit 328 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] 329 - 330 -**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 331 - 332 - 333 -==== (% style="color:blue" %)**Location info:**(%%) ==== 334 - 335 -* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976// 336 -* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 337 - 338 -(% style="color:red" %)**Important note:** 339 - 340 -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. 341 - 342 -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: 343 - 344 - 345 -[[image:1664502116362-706.png]] 346 - 347 - 348 -3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 349 - 350 -[[image:1664502166010-515.png]] 351 - 352 - 353 - 354 -==== (% style="color:blue" %)**Alarm:**(%%) ==== 355 - 356 -**Example: ** 0x4B & 0x40 >> 6 = 0x01 357 - 358 - 359 -==== (% style="color:blue" %)**BAT:**(%%) ==== 360 - 361 -**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV). 362 - 363 -((( 364 -The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \ 209 +(optional) 365 365 ))) 211 +|**Value**|[[Latitude>>path:#Location]]|[[Longitude>>path:#Location]]|((( 212 +[[Alarm &>>path:#Alarm]] 366 366 367 -* > 4.0v : 80% ~~ 100% 368 -* 3.85v ~~3.99v: 60% ~~ 80% 369 -* 3.70v ~~ 3.84v: 40% ~~ 60% 370 -* 3.40v ~~ 3.69v: 20% ~~ 40% 371 -* < 3.39v: 0~~20% 214 +[[BAT>>path:#Alarm]] 215 +)))|[[FLAG>>path:#Flag]]|Hum|[[Tem>>path:#Pitch]] 372 372 373 373 218 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]] 374 374 375 -==== (% style="color:blue" %)**MOD:**(%%) ==== 376 376 377 -** Example:** (0x60>>6)&0x3f =1221 +**Alarm & BAT:** 378 378 379 -**Set the format of GPS data uplink link:** 223 +|**Size(bit)**|1 bit|1bit|14 bits 224 +|**Value**|reserve|Alarm Indicate|[[BAT>>path:#BAT]] 380 380 381 -(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values 382 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values 226 +**FLAG:** 383 383 228 +|**Size(bit)**|2 bits|1bit|5 bits 229 +|**Value**|[[MOD>>path:#MD]]|[[LON>>path:#LON]]|Firmware version 384 384 385 -**Set the format of BLE data uplink link:** 386 386 387 -(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon 388 388 233 +**Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A ** 389 389 390 -==== (% style="color:blue" %)**LON:**(%%) ==== 391 391 392 -** Example:**(0x60>>5) & 0x01=1.236 +**Location info:** 393 393 394 - Enable/DisableLEDactivityforuplink238 +* Latitude: 02863D68⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// 395 395 396 -((( 397 -(% style="color:#037691" %)**0x00:** (%%) Disable LED indicator. 398 -))) 240 +//value = 02863D68 /1000000 = 42.351976// 399 399 400 -((( 401 -(% style="color:#037691" %)**0x01:** (%%) Enable LED indicator (Default Value) 402 -))) 242 +* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// 403 403 244 +//value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 404 404 405 -==== (% style="color:blue" %)**Hum:**(%%) ==== 406 406 407 - 0202 = //if (0x0202 & 0x8000 = 0 ): value=// 0x0202 / 100 = +514 ⇒ 51.4 degree247 +Important note: 408 408 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: 409 409 410 - ==== (%style="color:blue" %)**Tem:**(%%) ====253 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]] 411 411 412 -011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree// 413 413 256 +1. While GPS can’t get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 414 414 415 - === 2.4.3Uplink FPORT~=3, Realtime GNSS Positioning(Default Mode) ===258 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]] 416 416 260 +* **Alarm**: Example: 0x4B & 0x40 >> 6 = 0x01 261 +* **BAT**: Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV). 417 417 418 -The defaultuplinkpayloadincludestotal11 bytes(**AT+SMOD=1,1,0**).Thepayloadis thefirst11bytesof UplinkFPORT=2,real-timeGNSSpositioning, (removethe tempandhumidity)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: \ 419 419 420 420 421 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %) 422 -|=(% scope="row" style="width: 60px;" %)((( 423 -**Size(bytes)** 424 -)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1 425 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 426 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 427 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 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% 428 428 429 -(% class="wikigeneratedid" %) 430 -[[image:1665301687277-443.png]] 431 431 273 +* **LON: **Enable/Disable LED activity for uplink 432 432 433 - ===2.4.4 Uplink FPORT~=4, HistoryGNSSPositioning ===275 +0x00: Disable LED indicator. 434 434 277 +0x01: Enable LED indicator (Default Value) 435 435 436 -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. 437 437 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 438 438 439 -(% style="color:red" %)**Note for this mode:** 440 440 441 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server. 442 -* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=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. 443 -* 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 444 444 445 - Thepayloadis15bytes,asbelow.285 +=== 2.3.3 Uplink FPORT= , History GNSS Positioning === 446 446 447 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 448 -|=(% scope="row" %)((( 449 -**Size(bytes)** 450 -)))|4|4|2|1|1|1|1|1 451 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 452 452 453 -[[image:image-20221009160309-2.png]] 454 454 289 +=== 2.3.4 BLE positioning Payload(Fport=2) === 455 455 456 - === 2.4.5 UplinkFPORT~=6, BLEPositioningwith StrongestiBeacon ===291 +Different MODE has different payload: 457 457 293 +**MODE=2** 458 458 459 -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. 295 +|((( 296 +**Size** 460 460 461 -User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings. 298 +**(bytes)** 299 +)))|16|4|4|2|4|2|1 300 +|**Value**|[[UUID>>path:#Location]]|((( 301 +iBeacon 462 462 303 +MAJOR 304 +)))|((( 305 +iBeacon 463 463 464 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 465 -|=(% scope="row" style="width: 60px;" %)((( 466 -**Size(bytes)** 467 -)))|(% 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 468 -|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)((( 469 -iBeacon MAJOR 470 -)))|(% style="width:63px" %)((( 471 -iBeacon MINOR 472 -)))|(% style="width:71px" %)((( 473 -iBeacon Measured Power 474 -)))|(% style="width:50px" %)((( 475 -iBeacon RSSI 476 -)))|(% style="width:47px" %)((( 477 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 478 -)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 307 +MINOR 308 +)))|((( 309 +iBeacon Measured 479 479 480 -[[image:1664502425687-834.png]] 311 +Power 312 +)))|((( 313 +iBeacon 481 481 315 +RSSI 316 +)))|((( 317 +[[Alarm &>>path:#Alarm]] 482 482 483 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 484 -* (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 485 -* (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 486 -* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. 487 -* (% style="color:#037691" %)**MINOR:** (%%)The MINOR from the strongest iBeacon. 488 -* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 489 -* (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 319 +[[BAT>>path:#Alarm]] 320 +)))|[[FLAG>>path:#Flag]] 490 490 491 491 323 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]] 492 492 493 -=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 494 494 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. 495 495 496 -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. 497 497 498 498 499 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %) 500 -|=(% scope="row" style="width: 60px;" %)((( 501 -**Size(bytes)** 502 -)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1 503 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)((( 504 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 505 -)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 336 +=== 2.3.5 Add Payload format in TTN V3 === 506 506 507 -(% class="wikigeneratedid" %) 508 -[[image:1667288597595-714.png||height="212" width="1151"]] 338 +In TTN V3, use can add a custom payload so it shows friendly. 509 509 340 +In the page Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder 510 510 511 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 512 -* (% style="color:#037691" %)**SSID: **(%%)WiFi name. 513 -* (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 342 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]] 514 514 344 +Add the decoder from this link: 515 515 516 516 517 - ===2.4.7Add PayloadformatinTTNV3===347 +Save the change the uplink message will be parsed. As below: 518 518 349 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]] 519 519 520 -In TTN V3, user can add a custom payload so it shows friendly. 521 521 522 -In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 523 523 524 524 525 -[[image:1664502649601-895.png]] 526 526 355 +== 2.4 Integrate with Datacake == 527 527 528 528 529 -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. 530 530 531 -[[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]] 532 532 533 - Savethehangethe uplinkmessagewill be parsed.As below:362 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]] 534 534 535 -[[image:1664502676891-606.png]] 536 536 365 +== 2.5 Integrate with Tago == 537 537 538 -== 2.5 Integrate with Datacake == 539 539 540 - 541 541 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. 542 542 543 -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]] 544 - 545 - 546 -[[image:1664502695771-538.png]] 547 - 548 - 549 -== 2.6 Integrate with Tago == 550 - 551 - 552 -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. 553 - 554 554 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]] 555 555 372 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]] 556 556 557 -[[image:1664502715371-321.png]] 558 558 559 559 560 -== 2.7 Datalog Feature == 561 561 377 +== 2.6 Alarm Mode == 562 562 563 -total 273 entries,by default, 564 564 565 -User can s et[[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]],to enableDatalog feature.380 +User can push the **RED button** by more than 5 seconds to enter Alarm Mode. 566 566 567 -Example use case. 568 568 569 - [[image:image-20221009234703-2.png||height="328"width="899"]]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. 570 570 571 571 572 - [[image:image-20221009234629-1.png||height="390"width="577"]]386 +Two ways to exit alarm mode: 573 573 574 - 575 -== 2.8 Alarm Mode == 576 - 577 - 578 -((( 579 -User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 580 -))) 581 - 582 - 583 -((( 584 -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. 585 -))) 586 - 587 - 588 -((( 589 -**Two ways to exit alarm mode:** 590 -))) 591 - 592 -* Server sends a downlink command to exit. 388 +* Server send a downlink command to exit. 593 593 * User fast press the RED button 10 times. 594 594 595 -((( 596 -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. 597 -))) 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. 598 598 599 599 600 -== 2. 9Transport Mode ==394 +== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- == 601 601 602 602 603 -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. 604 604 398 +== 2.8 LED Status == 605 605 606 -== 2.10 LED Status == 607 607 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 608 608 609 -(% border="1.5" style="background-color:#ffffcc; 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 623 624 624 625 -== 2.11 Button Function == 626 626 418 +== 2.9 Button Function == 627 627 628 - (% style="color:blue" %)**RESET button:**420 +**RESET button:** 629 629 630 -[[image: 1664502835802-546.png]]422 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]] 631 631 632 632 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server. 633 633 634 634 635 - (% style="color:red" %)**RED button:**427 +**RED button:** 636 636 637 -[[image: 1664502854406-763.png]]429 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]] 638 638 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. 639 639 640 -(% border="1" style="background-color:#ffffcc; width:510px" %) 641 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description** 642 -|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode. See [[Alarm Mode>>||anchor="H2.8AlarmMode"]] 643 -|(% 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 644 -|(% 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. 645 645 646 646 647 647 648 -== 2.1 2USB Port Function ==439 +== 2.10 USB Port Function == 649 649 650 - 651 651 The USB interface of TrackerD has below functions: 652 652 653 653 * Power on the device 654 654 * Recharge the battery 655 -* [[Configure Device>> ||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]656 -* [[Upgrade Firmware>> ||anchor="H5.UploadFirmware"]]445 +* [[Configure Device>>path:#AT_Command]] 446 +* [[Upgrade Firmware>>path:#upgrade_image]] 657 657 658 658 659 659 450 + 451 + 660 660 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 661 661 662 662 663 663 User can configure TrackerD via AT Command or LoRaWAN Downlink. 664 664 665 -LoRaWAN Downlink instruction for different platforms: doc:Main.WebHome]]457 +LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]] 666 666 667 667 668 668 == 3.1 Access AT Command == 669 669 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 671 - TrackerD supports the AT command set in stockfirmware.Usercan connectto TrackerD with TYPE-C cableto use AT commands as shown below.464 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]] 672 672 673 673 674 - [[image:1664502999401-486.png]]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: 675 675 676 676 677 - In PC,Userneedsto set serialtool baud rateto (%style="color:green" %)**115200**(%%) to access serialconsole for TrackerD. TrackerD will output systeminfo onceower onanduser will be able to send AT commands:470 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]] 678 678 679 679 680 -[[image:1664503022490-662.png]] 681 681 474 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]] 682 682 683 -[[image: 1664503035713-500.png]]476 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]] 684 684 685 685 686 -[[image:1664503047675-651.png]] 687 - 688 - 689 - 690 690 == 3.2 Command Set == 691 691 481 + 692 692 === 3.2.1 Set Transmit Interval === 693 693 694 - 695 695 Set device uplink interval. 696 696 697 -* (% style="color:blue" %)**AT Command:**486 +* AT Command: 698 698 699 - (% style="color:#037691" %)**AT+TDC=xxx**488 +AT+TDC=xxx 700 700 701 -Example: 490 +Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds) 702 702 703 703 704 -* (% style="color:blue" %)**Downlink Payload (prefix 0x01):**493 +* Downlink Payload (prefix 0x01): 705 705 706 - (% style="color:#037691" %)**0x01 00 01 2C**(%%)~/~/495 +0x01 00 01 2C ~/~/ Same as AT+TDC=300000 707 707 708 708 709 709 === 3.2.2 Set Alarm Packet transmission interval === 710 710 711 - 712 712 Set alarm packet transmit interval 713 713 714 -* (% style="color:blue" %)**AT Command:**502 +* AT Command: 715 715 716 - (% style="color:#037691" %)**AT+ATDC=xx.**504 +AT+ATDC=xx. 717 717 718 -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 719 719 720 720 721 -* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**509 +* Downlink Payload (prefix 0xB1): 722 722 723 - (% style="color:#037691" %)**0xB1 00 00 3C** (%%)~/~/511 +0xB1 00 00 3C ~/~/Same as AT+ATDC=60000 724 724 725 725 726 -=== 3. 2.3 SetTransport Mode Packet transmission interval ===514 +=== 3.3.3 Set Sports Mode Packet transmission interval === 727 727 516 +Set sports packet transmit interval 728 728 729 - SetTransportMode packet transmit interval518 +* AT Command: 730 730 731 - * (% style="color:blue" %)**ATommand:**520 +AT+MTDC=xx. 732 732 733 - (%style="color:#037691"%)**AT+MTDC=xx.**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 734 734 735 -Example: AT+MTDC=300000 **~-~-> ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000 736 736 525 +* Downlink Payload (prefix 0x03): 737 737 738 - *(%style="color:blue"%)**DownlinkPayload(prefix0x03):**527 +0x03 00 01 2C ~/~/Same as AT+ MTDC=3000000 739 739 740 -(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+MTDC=3000000 741 741 742 742 743 -=== 3. 2.4 Exit Alarm ===531 +=== 3.3.4 Exit Alarm === 744 744 745 - 746 746 Server send downlink command to exit Alarm mode 747 747 748 -* (% style="color:blue" %)**AT Command:No AT Command**535 +* AT Command: 749 749 750 - * (% style="color:blue"%)**DownlinkPayload(prefix 0x02):**537 +No AT Command 751 751 752 -(% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 753 753 540 +* Downlink Payload (prefix 0x02): 754 754 755 - === 3.2.5Disable/EnableLEDflash===542 +0x02 01 ~/~/ Exit Alarm Mode 756 756 757 757 545 +=== 3.3.5 Disable/Enable LED flash === 546 + 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 -=== 3.2.6 Disable/Enable Transport Mode === 773 773 774 774 775 - Userscanusethisfeature to enable/disableTransportMode.563 +=== 3.3.6 Disable/Enable movement detect (Debug Only) === 776 776 777 - *(%style="color:blue"%)**ATCommand:**565 +User can use this feature to check and set thread hole of movement detect 778 778 779 - (% style="color:#037691" %)**AT+INTWK=xx.(Disable (0), Enable (1),default:0)**567 +* AT Command: 780 780 781 - Example:AT+INTWK=1**~-~->**EnableTransportMode.569 +AT+INTWK=xx. (Disable (0), Enable (1), default:0) 782 782 571 + Example: AT+ INTWK =1 à Enable detect movement. 783 783 784 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):** 785 785 786 - (%style="color:#037691"%)**0xAF01 ** (%%)~/~/ Same as AT+INTWK=1574 +* Downlink Payload (prefix 0xAF): 787 787 576 +0xAF 01 ~/~/Same as AT+ INTWK =1 788 788 789 -=== 3.2.7 Set Positioning Mode === 790 790 791 791 792 - SMODdefinehowTrackerDscanand uplinkdata:580 +=== 3.3.7 Set Positioning Mode === 793 793 582 +SMOD define the how TrackerD scan and uplink date. 794 794 795 - * (% style="color:blue" %)**AT Command:**584 +GPS室外定位模式:设备默认模式,设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是3分钟定位,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。GPS还有一种logdata模式,在断网的情况下将数据存储下来,等到有网的时候,一次将数据以每10秒上报。 796 796 797 - (%style="color:#037691" %)**AT+SMOD=aa,bb,cc**586 + BLE室内定位模式:设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是5秒,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每3分钟发送一次)。 798 798 799 - (%style="color:#037691" %)** aa:**588 + GPS和BLE混动模式:设备入网后会发送device当前模式下的信息,随后立即判断是否在室内,如果是就进行BLE定位,不是就GPS定位。如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。 800 800 801 - * (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)Only get and uplinkGPSlocation info.590 +运动模式:设备入网后会发送device当前模式下的信息,随后发送GPS定位数据,设备判断是否在运动,没有运动传感器没有检测到动作,立即进入静止状态(默认20分钟),如果产生运动,将每5分钟发送一次数据,再第五分钟后检测设备有误运动,无将切换到静止状态,有立即发送数据。 802 802 803 -* (% 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. 804 804 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&Hum595 +* AT Command: 810 810 811 - * (% style="color:red" %)**1 :**(%%) GPS +BATtate597 +AT+SMOD=xx. 812 812 813 - (%style="color:#037691" %)**cc: **599 + Example: 814 814 815 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 816 - 817 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%)) 601 + AT+ SMOD =1,0 à GPS+ BAT+ State+Tem&Hum 818 818 819 - (%style="color:blue"%)**Example:**603 + AT+ SMOD =1,1 à GPS +BAT State 820 820 821 - AT+SMOD= 1,0,0~-~->GPS++Tem&Hum605 + AT+ SMOD =2,3 à (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。 822 822 823 - AT+SMOD=1,1,0 ~-~-> GPS +BAT State 824 824 825 - AT+SMOD=2,0,1 ~-~-> (iBeacon)UUID+Major+ Minor+Power+Rssi+BAT+State608 +* Downlink Payload (prefix 0xA5): 826 826 827 - AT+SMOD=2,0,2-~->(WiFi)SSID+Rssi+BAT+State610 +0xA5 01 00 ~/~/ Same as AT+ SMOD =1,0 828 828 829 829 830 - *(%style="color:blue"%)**DownlinkPayload(prefix0xA5):**613 +=== 3.3.8 Set MAX GPS position time === 831 831 832 -(% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+SMOD=1,0,0 833 - 834 - 835 -=== 3.2.8 Set MAX GPS position time === 836 - 837 - 838 838 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. 839 839 840 840 841 -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.618 +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. 842 842 843 843 844 -* (% style="color:blue" %)**AT Command:**621 +* AT Command: 845 845 846 - (% 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. 847 847 848 - **Example:**AT+FTIME=150625 +Example: AT+FTIME=150 849 849 850 850 851 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**628 +* Downlink Payload (prefix 0xAA): 852 852 853 - (% style="color:#037691" %)**0xAA 00 96** (%%)~/~/630 +0xAA 00 96 ~/~/Set AT+FTIME=150 854 854 855 855 856 -=== 3.2.9 Set PDOP value for GPS fix accuracy === 857 857 858 858 859 - PDOP(PositionDilutionofPrecision) filter, TrackerD will only accept GPSdata with a lower PDOP valuethanpre-configurePDOP value.Ifdevice can't get a valid GPS packet within FTIME timeout,it will use theGPSdata withlowest PDOP value to server.635 +=== 3.3.9 Set PDOP value for GPS fix accuracy === 860 860 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. 861 861 639 + 862 862 A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0 863 863 864 864 865 -* (% style="color:blue" %)**AT Command:**643 +* AT Command: 866 866 867 - (% style="color:#037691" %)**AT+PDOP=2.5** (%%) **~-~->**Set PDOP to 2.5645 +AT+PDOP=2.5 à Set PDOP to 2.5 868 868 869 869 870 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**648 +* Downlink Payload (prefix 0xAD): 871 871 872 - (% style="color:#037691" %)**0xAD 00 0A**(%%)~/~/650 +0xAD 00 0A ~/~/Set AT+PDOP=1 (0x0A / 10 =1) 873 873 874 - (% style="color:#037691" %)**0xAD 00 19**(%%)~/~/652 +0xAD 00 19 ~/~/Set AT+PDOP=2.5 (0x19 / 10 =2.5) 875 875 876 - (% style="color:#037691" %)**0xAD 00 46**(%%)654 +0xAD 00 46 ~/~/Set AT+PDOP=7 (0x46 / 10 =7) 877 877 656 +Disable/Enable the confirmation mode 878 878 658 +* AT Command: 879 879 880 - **Disable/Enablethe confirmation mode**660 +AT+CFM=xx. 881 881 882 - *(% style="color:blue" %)**AT Command:**662 + Example: 883 883 884 - (%style="color:#037691"%)**AT+CFM=xx**664 + AT+ CFM=0 à Disable confirmation 885 885 666 + AT+ CFM=1 à Enable confirmation 886 886 887 -**~ Example:** 888 888 889 - AT+CFM=0**~-~->**Disable confirmation669 +* Downlink Payload (prefix 0x05): 890 890 891 - AT+CFM=1**~-~->** Enableconfirmation671 +0x05 01 ~/~/ Same as AT+ SMOD =1 892 892 893 893 894 -* (% style="color:blue" %)**Downlink Payload (prefix 0x05):** 895 895 896 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1 897 897 898 898 899 -=== 3.2.10 Auto Send None-ACK messages === 900 900 901 - 902 -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. 903 - 904 - 905 -* (% style="color:blue" %)**AT Command: AT+PNACKMD** 906 - 907 -The default factory setting is 0. 908 - 909 - 910 -**Command Example Function Response:** 911 - 912 -(% style="color:#037691" %)**AT+PNACKMD=1** (%%) ~/~/ Poll None-ACK message OK 913 - 914 - 915 -* (% style="color:blue" %)**Downlink Command: 0x34** 916 - 917 -Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 918 - 919 - 920 -=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 921 - 922 - 923 -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. 924 - 925 -(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.** 926 - 927 -(% style="color:blue" %)**AT Command:** 928 - 929 - (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 930 - 931 - (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 932 - 933 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 934 - 935 -Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 936 - 937 - 938 -=== 3.2.12 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 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 as prefix. 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 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)** 952 - 953 -Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 954 - 955 - 956 -=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 957 - 958 - 959 -Users can use this feature to enable/disable Information printing. 960 - 961 -(% style="color:blue" %)**AT Command:** 962 - 963 -(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/(Disable (0), Enable (1), default:0) 964 -\\Example: AT+SHOWID=1 ~-~-> Enable Information printing. 965 - 966 - 967 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 968 - 969 - 970 -The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. 971 - 972 -(% style="color:blue" %)**AT Command:** 973 - 974 -(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode 975 - 976 - 977 -(% style="color:blue" %)**Downlink Payload:0X24** 978 - 979 -Example: 0x24 01 ~/~/ Same as AT+CHE=1 980 - 981 - 982 982 = 4. Setting for Different Scenarios = 983 983 984 984 ... ... @@ -985,130 +985,123 @@ 985 985 986 986 = 5. Upload Firmware = 987 987 684 + 988 988 == 5.1 Firmware Change Log == 989 989 990 - 991 991 **[[See this link>>url:https://github.com/dragino/TrackerD]]** 992 992 993 993 994 994 == 5.2 How to upgrade firmware == 995 995 692 +User can use the TrackerD ’s USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below: 996 996 997 -User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below: 998 998 695 +**(% style="color:blue" %)Step1: **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD. 999 999 1000 -(% style="color:blue" %) **Step1:ConnectTrackerDand PCvia USB cableshippedwithTrackerD.697 +**(% style="color:blue" %)Step2:** (%%) Install CH9102 driver in the PC. 1001 1001 1002 - 1003 -(% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC. 1004 - 1005 1005 After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager. 1006 1006 1007 1007 1008 -(% 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: 1009 1009 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]] 1010 1010 1011 -(% style="color:blue" %) **Step4:**706 +**(% style="color:blue" %)Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32 1012 1012 1013 1013 1014 -[[image: 1664503563660-578.png]]709 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png||alt="image-20220712083115-1.png"]] 1015 1015 711 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png||alt="image-20220712083115-2.png"]] 1016 1016 1017 -[[image:1664503574618-659.png]] 1018 1018 714 +**(% style="color:blue" %)Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 1019 1019 716 +[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1020 1020 1021 -(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 1022 1022 1023 - [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]719 +Users need to use below files: 1024 1024 1025 - 1026 -**Users need to use below files:** 1027 - 1028 1028 boot_app0.bin @0e000 1029 1029 1030 - US915.bin @ 0x10000(Select the bin file of the frequency band you need)723 +ESP_LORA-eeprom-class.bin @ 0x10000 1031 1031 725 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png||alt="image-20220712083115-3.png"]] 1032 1032 1033 - [[image:image-20221118105220-2.png]]727 +After upgrade finish, it will show finish as below: 1034 1034 729 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png||alt="image-20220712083115-4.png"]] 1035 1035 1036 1036 1037 -After upgrade finish, it will show finish as below: 1038 1038 1039 -[[image:image-20221118105402-4.png]] 1040 1040 1041 1041 1042 - 1043 1043 = 6. Developer Guide = 1044 1044 737 + 1045 1045 == 6.1 Compile Source Code == 1046 1046 740 + 1047 1047 === 6.1.1 Set up ARDUINO compile environment === 1048 1048 1049 1049 1050 -* **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 1051 1051 1052 - 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]] 1053 1053 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]] 1054 1054 1055 -[[image: 1664503635019-941.png]]750 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]] 1056 1056 752 +* Go to tools ~-~-> Boards ~-~-> Boards Manager, find the esp32 information and install it. 1057 1057 754 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]] 1058 1058 1059 -* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 1060 1060 1061 - [[image:1664503715811-892.png]]757 +* Download the latest TrackerD from the dragino github 1062 1062 759 +[[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]] 1063 1063 1064 -(% 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. 1065 1065 1066 - [[image:image-20221024105643-1.png]]762 +Put the Library in the TrackerD directory into the libraries file in the Arduino directory 1067 1067 1068 - **~ Figure1**764 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]] 1069 1069 1070 1070 1071 -[[image:image-20221024105643-2.png]] 1072 1072 1073 - **Figure2** 1074 1074 769 +== 6.2 Source Code == 1075 1075 1076 -* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]** 1077 1077 1078 - PuttheLibraryin the TrackerDdirectoryinto thelibrariesfilein theArduinodirectory:772 +* Open the example in the TrackerD file, please select the correct port in the IDE, as shown below: 1079 1079 774 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]] 1080 1080 1081 - [[image:1664503752288-974.png]]776 +* Click to upload 1082 1082 778 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]] 1083 1083 1084 - ==6.2SourceCode==780 +* Check the result, if the upload is successful, as shown below, open the serial port to view the data 1085 1085 1086 1086 1087 - * (% style="color:blue" %)**Openthe exampleintheTrackerDfile, pleaseelectthe correctportn the IDE,as shown below:**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]] 1088 1088 1089 -[[image:1664503794261-827.png]] 1090 1090 1091 1091 1092 1092 1093 -* (% style="color:blue" %)**Click to upload** 1094 1094 1095 -[[image:1664503808294-336.png]] 1096 1096 790 += 7. FAQ = 1097 1097 1098 1098 1099 -* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 1100 1100 1101 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 1102 - 1103 - 1104 -= 7. FAQ = 1105 - 1106 1106 == 7.1 How to change the LoRa Frequency Bands/Region? == 1107 1107 1108 1108 1109 -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. 1110 1110 1111 1111 800 + 1112 1112 == 7.2 What is the pin mapping for the USB program cable? == 1113 1113 1114 1114 ... ... @@ -1116,8 +1116,8 @@ 1116 1116 1117 1117 1118 1118 1119 -(% border=" 1.5"cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)1120 -| =(% 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** 1121 1121 |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC 1122 1122 |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A) 1123 1123 |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A) ... ... @@ -1127,245 +1127,52 @@ 1127 1127 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 1128 1128 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 1129 1129 819 += 8. Order Info = 1130 1130 1131 1131 1132 -== 7.3 Notes on using different serial port tools for TrackerD == 1133 - 1134 -=== 7.3.1 Serial port utility === 1135 - 1136 - 1137 -Serial port utility requires you to automatically add data streams. 1138 - 1139 -Need to adjust the data stream to RTS/CTS on physical restart. 1140 - 1141 -(% class="wikigeneratedid" %) 1142 -[[image:image-20221102140621-1.png]] 1143 - 1144 - 1145 - 1146 -When using AT commands, the data flow needs to be adjusted to XON/XOFF 1147 - 1148 -[[image:image-20221102140638-2.png]] 1149 - 1150 - 1151 -=== 7.3.2 SecureCRT === 1152 - 1153 - 1154 -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. 1155 - 1156 - 1157 -[[image:image-20221102140704-3.png]] 1158 - 1159 - 1160 -[[image:image-20221102140712-4.png]] 1161 - 1162 - 1163 -=== 7.3.3 PUTTY === 1164 - 1165 - 1166 -[[image:image-20221102140748-5.png]] 1167 - 1168 - 1169 -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. 1170 - 1171 - 1172 -[[image:image-20221102140801-6.png]] 1173 - 1174 - 1175 -== 7.4 How to modify source code to compile different frequency band bin file? == 1176 - 1177 - 1178 -(% class="box infomessage" %) 1179 -((( 1180 -(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings. 1181 -See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]] 1182 -))) 1183 - 1184 -**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.** 1185 - 1186 - 1187 -[[image:image-20221116111844-1.png||height="227" width="782"]] 1188 - 1189 - 1190 - 1191 -**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).** 1192 - 1193 - 1194 -[[image:image-20221116111844-2.png||height="262" width="781"]] 1195 - 1196 - 1197 - 1198 -**3. Compile the AS923_JP band, please refer to the intention shown** 1199 - 1200 - 1201 -[[image:image-20221116111844-3.png||height="338" width="746"]] 1202 - 1203 - 1204 - 1205 -**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.** 1206 - 1207 - 1208 -[[image:image-20221116111844-4.png||height="641" width="739"]] 1209 - 1210 - 1211 -[[image:image-20221116111844-5.png||height="551" width="708"]] 1212 - 1213 - 1214 -= 8 Trouble Shooting = 1215 - 1216 -== 8.1 TDC is changed to 4294947296 and cause no uplink. == 1217 - 1218 - 1219 -((( 1220 -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 1221 -))) 1222 - 1223 - 1224 -== 8.2 Device not able get AT Command or show output after wake up from deep sleep mode == 1225 - 1226 - 1227 -((( 1228 -ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode. 1229 -))) 1230 - 1231 - 1232 -== 8.3 Problem after Upgrading Firmware == 1233 - 1234 -=== 8.3.1 Continue Restart after upgrading === 1235 - 1236 - 1237 -((( 1238 -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 1239 -))) 1240 - 1241 - 1242 -[[image:image-20221118105249-3.png]] 1243 - 1244 - 1245 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1246 - 1247 - 1248 -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 1249 - 1250 - 1251 - 1252 -==== 8.3.2.1 If there is a situation in Figure 1,and a new partition file and bootloader file needs to be added. Please refer to the operation steps in Figure 2 ==== 1253 - 1254 - 1255 -[[image:image-20221122100004-1.png||height="497" width="534"]] 1256 - 1257 - ** Figure 1 ** 1258 - 1259 - 1260 - [[image:image-20221122100004-2.png||height="619" width="389"]] 1261 - 1262 - **Figure 2** 1263 - 1264 - 1265 - 1266 -After the upgrade is completed, enter AT+CFG as shown in the figure below. 1267 - 1268 - 1269 -[[image:image-20221122100004-3.png]] 1270 - 1271 -Please AT+FDR, and then enter the following instructions by the information on the label 1272 - 1273 -AT+DEUI=70B3D57ED0053981 1274 - 1275 -AT+APPEUI=D23345667BCBCCAF 1276 - 1277 -AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1 1278 - 1279 -AT+DADDR=260b4dce 1280 - 1281 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d 1282 - 1283 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 1284 - 1285 - 1286 - 1287 -==== 8.3.2.2 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ==== 1288 - 1289 - 1290 -[[image:image-20221122100004-4.png]] 1291 - 1292 - 1293 -== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1294 - 1295 - 1296 -Please download version 1.4.2 again 1297 - 1298 - 1299 -== 8.5 How to deal with unsuccessful GPS positioning? == 1300 - 1301 - 1302 -1) Make Sure the device is in Open Area where can see the sky. 1303 - 1304 -2) Set PDOP to a higher value. 1305 - 1306 -* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.) 1307 - 1308 -* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces) 1309 - 1310 -* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments) 1311 - 1312 -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 1313 - 1314 - 1315 -= 9. Order Info = 1316 - 1317 - 1318 1318 Part Number: (% style="color:blue" %)**TrackerD-XXX** 1319 1319 1320 1320 (% style="color:blue" %)**XXX**(%%): The default frequency band 1321 1321 1322 1322 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433 1323 - 827 +* (% style="color:red" %)**CN470**(%%): Default frequency band CN470 1324 1324 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868 1325 - 1326 1326 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865 1327 - 1328 1328 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920 1329 - 1330 1330 * (% style="color:red" %)**AS923**(%%): Default frequency band AS923 1331 - 1332 1332 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 1333 - 1334 1334 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1335 1335 1336 1336 836 += 9. Packing Info = 1337 1337 1338 -= 10. Packing Info = 1339 1339 839 +**Package Includes**: 1340 1340 1341 -(% style="color:#037691" %)**Package Includes**: 841 +* TrackerD x 1 842 +* Rechargeable cable x 1 843 +* Program Cable x 1 1342 1342 1343 -* TrackerDLoRaWANGPS/BLE Trackerx 1845 +**Dimensions and Weight**: 1344 1344 1345 -* USB recharge & program cable x 1 847 +* Device Size: 85 x 48 x 15 mm/pcs 848 +* Weight: 55g/pcs 1346 1346 1347 -(% style="color:#037691" %)**Dimensions and Weight**: 1348 1348 1349 -* Device Size: 85 x 48 x 15 mm 1350 1350 1351 - *Weight:50g852 += 10. Support = 1352 1352 1353 - 1354 - 1355 -= 11. Support = 1356 - 1357 - 1358 1358 * 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. 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 1359 1359 1360 - * 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]].857 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]] 1361 1361 1362 1362 1363 1363 1364 -= 12. Reference = 1365 1365 862 += 11. Reference = 1366 1366 1367 -* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1368 1368 865 +* [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1369 1369 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1370 - 1371 1371 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
- 1664503715811-892.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -36.6 KB - Content
- 1664503752288-974.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -112.6 KB - Content
- 1664503794261-827.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -119.5 KB - Content
- 1664503808294-336.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -161.6 KB - Content
- 1664503824081-592.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -77.4 KB - Content
- 1664503831430-500.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -147.8 KB - Content
- 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
- image-20221102140621-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -46.1 KB - Content
- image-20221102140638-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -40.8 KB - Content
- image-20221102140704-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -15.5 KB - Content
- image-20221102140712-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -73.2 KB - Content
- image-20221102140748-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -56.0 KB - Content
- image-20221102140801-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -21.0 KB - Content
- image-20221107145243-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -107.3 KB - Content
- image-20221116111844-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -15.8 KB - Content
- image-20221116111844-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -32.6 KB - Content
- image-20221116111844-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -37.0 KB - Content
- image-20221116111844-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -96.8 KB - Content
- image-20221116111844-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -78.0 KB - Content
- image-20221118104359-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -38.0 KB - Content
- image-20221118105220-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -40.2 KB - Content
- image-20221118105249-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -40.2 KB - Content
- image-20221118105402-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -43.7 KB - Content
- image-20221122100004-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -18.0 KB - Content
- 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