Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Xiaoling on 2025/04/27 16:48
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 32 removed)
- 1664501652064-326.png
- 1664501677253-891.png
- 1664501711466-918.png
- 1664501721248-725.png
- 1664501734705-405.png
- 1664501784668-703.png
- 1664501958445-288.png
- 1664502116362-706.png
- 1664502166010-515.png
- 1664502425687-834.png
- 1664502649601-895.png
- 1664502676891-606.png
- 1664502695771-538.png
- 1664502715371-321.png
- 1664502835802-546.png
- 1664502854406-763.png
- 1664502999401-486.png
- 1664503022490-662.png
- 1664503035713-500.png
- 1664503047675-651.png
- 1664503563660-578.png
- 1664503574618-659.png
- 1664503593459-435.png
- 1664503611848-385.png
- 1664503635019-941.png
- 1664503715811-892.png
- 1664503752288-974.png
- 1664503794261-827.png
- 1664503808294-336.png
- 1664503824081-592.png
- 1664503831430-500.png
- 1664505654417-133.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,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 ... ... @@ -62,7 +62,6 @@ 62 62 * Clock Speed: 32Mhz 63 63 64 64 65 - 66 66 (% style="color:blue" %)**Common DC Characteristics:** 67 67 68 68 * Supply Voltage: 5V via USB port or Internal li-on battery ... ... @@ -69,7 +69,6 @@ 69 69 * Operating Temperature: -40 ~~ 60°C 70 70 71 71 72 - 73 73 (% style="color:blue" %)**LoRa Spec:** 74 74 75 75 * Frequency Range, ... ... @@ -92,13 +92,11 @@ 92 92 * LoRaWAN 1.0.3 Specification 93 93 94 94 95 - 96 96 (% style="color:blue" %)**Battery:** 97 97 98 98 * 1000mA Li-on Battery power (for model TrackerD) 99 99 100 100 101 - 102 102 (% style="color:blue" %)**Power Consumption** 103 103 104 104 * Sleeping Mode: 200uA ... ... @@ -114,7 +114,7 @@ 114 114 * LoRaWAN 1.0.3 Class A 115 115 * ESP32 PICO D4 116 116 * SX1276/78 Wireless Chip 117 -* *Arduino IDE Compatible100 +* Arduino IDE Compatible 118 118 * Open source hardware / software 119 119 * Regular/ Real-time GPS,BLE,WIFI tracking 120 120 * Built-in3 axis accelerometer (LIS3DH) ... ... @@ -128,7 +128,6 @@ 128 128 129 129 130 130 131 - 132 132 == 1.4 Applications == 133 133 134 134 ... ... @@ -138,266 +138,261 @@ 138 138 139 139 140 140 141 -= 2.1 Use TrackerD = 123 +1. Use TrackerD 124 +11. How it works? 142 142 143 143 144 -== 2.1 How it works? == 145 - 146 - 147 147 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. 148 148 149 149 130 +1. 131 +11. Quick guide to connect to LoRaWAN server 150 150 151 - ==2.2Quickguideto connect to LoRaWAN server==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. 152 152 153 153 154 - Hereisanexamplefor how to join the[[TTNv3RaWAN Network>>url:https://eu1.cloud.thethings.network]]. Belowis the network structure, we use LPS8Nas LoRaWANgateway in this example.136 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]] 155 155 156 156 157 -[[image:1664501652064-326.png]] 158 - 159 - 160 - 161 161 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: 162 162 141 +**Step 1**: Create a device in TTN V3 with the OTAA keys from TrackerD. 163 163 164 -(% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD. 165 - 166 166 Each TrackerD is shipped with a sticker with the default device EUI as below: 167 167 145 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]] 168 168 169 -[[image:1664501677253-891.png]] 170 170 171 171 149 + 172 172 Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot: 173 173 174 174 175 - **__Add APP EUI in the application:__**153 +Add APP EUI in the application 176 176 155 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]] 177 177 178 -[[image: 1664501711466-918.png]]157 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]] 179 179 180 180 160 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]] 181 181 182 -[[image:1664501721248-725.png]] 183 183 184 184 185 - [[image:1664501734705-405.png]]164 +Add APP KEY and DEV EUI 186 186 166 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]] 187 187 188 188 189 -**__Add APP KEY and DEV EUI:__** 190 190 191 191 192 - [[image:1664501784668-703.png]]171 +**Step 2**: Power on TrackerD by using the on board switch. 193 193 194 194 174 +**Step 3:** TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server. 195 195 196 196 197 - (% style="color:blue" %)**Step 2**:(%%)PoweronTrackerD by usingtheon boardswitch.177 +**Positioning Mode(SMOD):** 198 198 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. 199 199 200 - (%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]]. 201 201 202 202 203 -(% style="color:blue" %)**Positioning Mode(SMOD):** 186 +1. 187 +11. Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~- 204 204 205 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)only get GPS location info. 206 -* (% style="color:#037691" %)**BLE ONLY: **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking. 207 -* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking. 208 208 209 -User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 190 +1. 191 +11. 192 +111. Uplink FPORT=5, Device Status 210 210 211 211 212 212 213 -== 2.3 Uplink Payload == 196 +1. 197 +11. 198 +111. Uplink FPORT= , Realtime GNSS Positioning 214 214 200 +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. ) 215 215 216 -=== 2.3.1 Uplink FPORT~=5, Device Status === 217 217 218 - 219 - 220 -=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning === 221 - 222 - 223 -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. ) 224 - 225 - 226 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:520px" %) 227 -|=(% scope="row" style="width: 69px;" %)((( 203 +|((( 228 228 **Size** 229 229 230 230 **(bytes)** 231 -)))| (% style="width:76px" %)4|(% style="width:87px" %)4|(% style="width:76px" %)2|(% style="width:52px" %)1|(% style="width:88px" %)(((207 +)))|4|4|2|1|((( 232 232 2 233 233 234 234 (optional ) 235 -)))|( % style="width:83px" %)(((211 +)))|((( 236 236 2 237 237 238 238 (optional) 239 239 ))) 240 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 241 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 242 -)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:83px" %)[[Tem>>||anchor="HTem:"]] 216 +|**Value**|[[Latitude>>path:#Location]]|[[Longitude>>path:#Location]]|((( 217 +[[Alarm &>>path:#Alarm]] 243 243 244 -[[image:1664501958445-288.png]] 219 +[[BAT>>path:#Alarm]] 220 +)))|[[FLAG>>path:#Flag]]|Hum|[[Tem>>path:#Pitch]] 245 245 246 246 247 - ==== (%style="color:blue" %)Alarm& BAT:(%%) ====223 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]] 248 248 249 -(% border="2" style="background-color:#ffffcc; color:green; width:329px" %) 250 -|(% style="width:72px" %)**Size(bit)**|(% style="width:67px" %)1 bit|(% style="width:118px" %)1bit|(% style="width:63px" %)14 bits 251 -|(% style="width:72px" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 252 252 253 - ==== (% style="color:blue"%)FLAG:(%%) ====226 +**Alarm & BAT:** 254 254 255 -(% border="2" style="background-color:#ffffcc; color:green; width:332px" %) 256 -|(% style="width:79px" %)**Size(bit)**|(% style="width:55px" %)2 bits|(% style="width:47px" %)1bit|(% style="width:140px" %)5 bits 257 -|(% style="width:79px" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H2.3.4BLEpositioningPayload28Fport229"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version 228 +|**Size(bit)**|1 bit|1bit|14 bits 229 +|**Value**|reserve|Alarm Indicate|[[BAT>>path:#BAT]] 258 258 259 -** Example:**Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A231 +**FLAG:** 260 260 233 +|**Size(bit)**|2 bits|1bit|5 bits 234 +|**Value**|[[MOD>>path:#MD]]|[[LON>>path:#LON]]|Firmware version 261 261 262 -==== (% style="color:blue" %)Location info:(%%) ==== 263 263 264 -* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976// 265 -* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 266 266 267 - (% style="color:red" %)**Importantnote:**238 +**Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A ** 268 268 269 -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. 270 270 271 - 2. In firmware versionv1.5, Roll & Pitch is disabled by default.241 +**Location info:** 272 272 273 - 3.When enable 9-axis motion sensor,the total payloadwill be15bytes, whileUS915/AU915DR0acceptonly11 bytes payload. In this case, the payload on server will be ignore and shows as below:243 +* Latitude: 02863D68⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// 274 274 245 +//value = 02863D68 /1000000 = 42.351976// 275 275 276 - [[image:1664502116362-706.png]]247 +* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// 277 277 249 +//value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 278 278 279 279 280 - 4. While GPS can't get location info after timeout(FTIME Parameter), the latitudeand longitudewill be filled with all 0x00:252 +Important note: 281 281 282 -[[image:1664502166010-515.png]] 254 +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. 255 +1. In firmware version v1.5, Roll & Pitch is disabled by default. 256 +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: 283 283 258 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]] 284 284 285 285 286 - ====(%style="color:blue"%)Alarm:(%%)====261 +1. While GPS can’t get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 287 287 263 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]] 288 288 289 -Example: 0x4B & 0x40 >> 6 = 0x01 265 +* **Alarm**: Example: 0x4B & 0x40 >> 6 = 0x01 266 +* **BAT**: Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV). 290 290 268 +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: \ 291 291 292 -==== (% style="color:blue" %)BAT:(%%) ==== 293 293 271 +* > 4.0v : 80% ~~ 100% 272 +* 3.85v ~~3.99v: 60% ~~ 80% 273 +* 3.70v ~~ 3.84v: 40% ~~ 60% 274 +* 3.40v ~~ 3.69v: 20% ~~ 40% 275 +* < 3.39v: 0~~20% 294 294 295 -Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV). 296 296 297 - Thebattery info shows the current voltage, for (% style="color:blue"%)**TrackerD**(%%) versionwhich poweredbyli-on battery. User can usebelowmappingtoindicatethe batteryinpercentage: \278 +* **LON: **Enable/Disable LED activity for uplink 298 298 280 +0x00: Disable LED indicator. 299 299 300 -* > 4.0v : 80% ~~ 100% 301 -* 3.85v ~~3.99v: 60% ~~ 80% 302 -* 3.70v ~~ 3.84v: 40% ~~ 60% 303 -* 3.40v ~~ 3.69v: 20% ~~ 40% 304 -* < 3.39v: 0~~20% 282 +0x01: Enable LED indicator (Default Value) 305 305 306 -==== (% style="color:blue" %)LON:(%%) ==== 307 307 308 - 309 - Enable/DisableLEDactivityforuplink285 +* **Hum**: 0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree 286 +* **//Tem//**//: 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree 310 310 311 -0x00: Disable LED indicator. 312 312 313 -0x01: Enable LED indicator (Default Value) 314 314 290 +1. 291 +11. 292 +111. Uplink FPORT= , History GNSS Positioning 315 315 316 -==== (% style="color:blue" %)Hum:(%%) ==== 317 317 318 -0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree 319 319 296 +1. 297 +11. 298 +111. BLE positioning Payload(Fport=2) 320 320 321 - ====(%style="color:blue" %)Tem:(%%) ====300 +Different MODE has different payload: 322 322 323 - 011A=if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//302 +**MODE=2** 324 324 304 +|((( 305 +**Size** 325 325 307 +**(bytes)** 308 +)))|16|4|4|2|4|2|1 309 +|**Value**|[[UUID>>path:#Location]]|((( 310 +iBeacon 326 326 312 +MAJOR 313 +)))|((( 314 +iBeacon 327 327 328 -=== 2.3.3 Uplink FPORT~= , History GNSS Positioning === 316 +MINOR 317 +)))|((( 318 +iBeacon Measured 329 329 320 +Power 321 +)))|((( 322 +iBeacon 330 330 324 +RSSI 325 +)))|((( 326 +[[Alarm &>>path:#Alarm]] 331 331 332 -=== 2.3.4 BLE positioning Payload(Fport2) === 328 +[[BAT>>path:#Alarm]] 329 +)))|[[FLAG>>path:#Flag]] 333 333 334 334 335 - Different MODE hasdifferentpayload:332 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]] 336 336 337 -**MODE=2** 338 338 339 -(% border="2" style="background-color:#ffffcc; color:green; width:491px" %) 340 -|(% style="width:70px" %)((( 341 -**Size** 335 +* **BAT**: Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV). 336 +* **MODE: **Define the payload format. 337 +* **UUID: **The uuid from the strongest iBeacon. 338 +* **MAJOR**: The MAJOR from the strongest iBeacon. 339 +* **MINOR**: The MAJOR from the strongest iBeacon. 340 +* **Measured** **Power**: The Measured Power from the strongest iBeacon. 341 +* **RSSI**: The RSSI from the strongest iBeacon. 342 342 343 -**(bytes)** 344 -)))|(% style="width:44px" %)16|(% style="width:61px" %)4|(% style="width:63px" %)4|(% style="width:71px" %)2|(% style="width:50px" %)4|(% style="width:47px" %)2|(% style="width:15px" %)1 345 -|(% style="width:70px" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)((( 346 -iBeacon MAJOR 347 -)))|(% style="width:63px" %)((( 348 -iBeacon MINOR 349 -)))|(% style="width:71px" %)((( 350 -iBeacon Measured Power 351 -)))|(% style="width:50px" %)((( 352 -iBeacon RSSI 353 -)))|(% style="width:47px" %)((( 354 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 355 -)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 356 356 357 -[[image:1664502425687-834.png]] 344 +1. 345 +11. 346 +111. Add Payload format in TTN V3 358 358 359 - 360 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV). 361 -* (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 362 -* (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 363 -* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. 364 -* (% style="color:#037691" %)**MINOR:** (%%)The MAJOR from the strongest iBeacon. 365 -* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 366 -* (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 367 - 368 -=== 2.3.5 Add Payload format in TTN V3 === 369 - 370 - 371 371 In TTN V3, use can add a custom payload so it shows friendly. 372 372 373 -In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**350 +In the page Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder 374 374 352 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]] 375 375 376 -[[image:1664502649601-895.png]] 377 - 378 - 379 379 Add the decoder from this link: 380 380 381 381 382 382 Save the change the uplink message will be parsed. As below: 383 383 384 -[[image: 1664502676891-606.png]]359 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]] 385 385 386 386 387 387 388 -== 2.4 Integrate with Datacake == 389 389 390 390 391 -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. 365 +1. 366 +11. Integrate with Datacake 392 392 393 -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]] 394 394 369 +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. 395 395 396 -[[image: 1664502695771-538.png]]371 +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]] 397 397 373 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]] 398 398 399 399 400 -== 2.5 Integrate with Tago == 376 +1. 377 +11. Integrate with Tago 401 401 402 402 403 403 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. ... ... @@ -404,18 +404,19 @@ 404 404 405 405 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]] 406 406 384 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]] 407 407 408 -[[image:1664502715371-321.png]] 409 409 410 410 411 411 412 -== 2.6 Alarm Mode == 389 +1. 390 +11. Alarm Mode 413 413 414 414 415 -User can push the (% style="color:red" %)**RED button**(%%)by more than 5 seconds to enter Alarm Mode.393 +User can push the **RED button** by more than 5 seconds to enter Alarm Mode. 416 416 417 417 418 -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 exit alert mode.396 +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. 419 419 420 420 421 421 Two ways to exit alarm mode: ... ... @@ -423,244 +423,252 @@ 423 423 * Server send a downlink command to exit. 424 424 * User fast press the RED button 10 times. 425 425 426 -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.404 +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. 427 427 428 428 407 +1. 408 +11. Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- 429 429 430 -== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- == 431 431 432 432 412 +1. 413 +11. LED Status 433 433 434 -== 2.8 LED Status == 435 435 416 +|**Event**|**Action**|**AT+LON to control on/off** 417 +|**Power On**|**BLUE, RED , Green** flash once|N/A 418 +|**Join request**|**Green** led fast blink once (200ms)|Yes 419 +|**Join Success**|**Green** led on 5 second|N/A 420 +|**Fixing Location**|**BLUE **blinks 200ms per second|Yes 421 +|**Fixed and uplink**|**GREEN **blinks twice (200ms per blink)|Yes 422 +|**Fail Fix and uplink**|**RED **blinks twice (200ms per blink)|Yes 423 +|**Enter Alarm mode**|**RED **on for 3 seconds|Yes 424 +|**Uplink under Alarm**|**RED **on for 1 second|Yes 425 +|**Exit Alarm**|**BLUE **led on 5 second|Yes 426 +|**Get Downlink**|**GREEN** led on 1 second|Yes 427 +|**Movement Detect**|**RED **on 500ms|N/A 436 436 437 -(% border="2" style="background-color:#ffffcc; color:green; width:636px" %) 438 -|(% style="width:157px" %)**Event**|(% style="width:271px" %)**Action**|(% style="width:202px" %)**AT+LON to control on/off** 439 -|(% 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 440 -|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes 441 -|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A 442 -|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes 443 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes 444 -|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes 445 -|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes 446 -|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes 447 -|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes 448 -|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 449 -|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 450 450 451 -== 2.9 Button Function == 452 452 453 453 454 -(% style="color:green" %)**RESET button:** 455 455 456 -[[image:1664502835802-546.png]] 433 +1. 434 +11. Button Function 457 457 458 - Pushthisbuttonwill reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.436 +**RESET button:** 459 459 438 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]] 460 460 461 - (%style="color:red"%)**REDbutton:**440 +Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server. 462 462 463 -[[image:1664502854406-763.png]] 464 464 443 +**RED button:** 465 465 466 -(% border="2" style="background-color:#ffffcc; color:green; width:627px" %) 467 -|(% style="width:135px" %)**Function**|(% style="width:220px" %)**Action**|(% style="width:265px" %)**Description** 468 -|(% 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"]] 469 -|(% 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 470 -|(% 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. 445 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]] 471 471 447 +|**Function**|**Action**|**Description** 448 +|Send Alarm|Keep Pressing **RED** button for more than 5 seconds|Enter Alarm Mode. See [[Alarm Mode>>path:#Alarm_Mode]] 449 +|Exit Alarm Mode|Fast press the **RED** button 10 times|Exit Alarm Mode 450 +|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. 472 472 473 473 474 -== 2.10 USB Port Function == 475 475 476 476 455 +1. 456 +11. USB Port Function 457 + 477 477 The USB interface of TrackerD has below functions: 478 478 479 479 * Power on the device 480 480 * Recharge the battery 481 -* [[Configure Device>> ||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]482 -* [[Upgrade Firmware>> ||anchor="H5.UploadFirmware"]]462 +* [[Configure Device>>path:#AT_Command]] 463 +* [[Upgrade Firmware>>path:#upgrade_image]] 483 483 484 484 485 485 486 -= 3. Configure TrackerD via AT command or LoRaWAN downlink = 487 487 488 488 489 - Usercan configure TrackerD via ATCommand or LoRaWANDownlink.469 +1. Configure TrackerD via AT command or LoRaWAN downlink 490 490 491 -LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] 492 492 472 +User can configure TrackerD via AT Command or LoRaWAN Downlink. 493 493 474 +LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]] 494 494 495 -== 3.1 Access AT Command == 496 496 477 +1. 478 +11. Access AT Command 497 497 498 -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. 480 +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. ... 499 499 482 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]] 500 500 501 -[[image:1664502999401-486.png]] 502 502 485 +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: 503 503 504 -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: 505 505 488 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]] 506 506 507 -[[image:1664503022490-662.png]] 508 508 509 509 492 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]] 510 510 511 -[[image: 1664503035713-500.png]]494 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]] 512 512 513 513 497 +1. 498 +11. Command Set 514 514 515 -[[image:1664503047675-651.png]] 516 516 501 +1. 502 +11. 503 +111. Set Transmit Interval 517 517 518 - 519 -== 3.2 Command Set == 520 - 521 - 522 -=== 3.2.1 Set Transmit Interval === 523 - 524 - 525 525 Set device uplink interval. 526 526 527 -* (% style="color:blue" %)**AT Command:**507 +* AT Command: 528 528 529 - (% style="color:#037691" %)**AT+TDC=xxx**509 +AT+TDC=xxx 530 530 531 -Example: 511 +Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds) 532 532 533 533 534 -* (% style="color:blue" %)**Downlink Payload (prefix 0x01):**514 +* Downlink Payload (prefix 0x01): 535 535 536 - (% style="color:#037691" %)**0x01 00 01 2C**(%%)~/~/516 +0x01 00 01 2C ~/~/ Same as AT+TDC=300000 537 537 538 538 519 +1. 520 +11. 521 +111. Set Alarm Packet transmission interval 539 539 540 -=== 3.2.2 Set Alarm Packet transmission interval === 541 - 542 - 543 543 Set alarm packet transmit interval 544 544 545 -* (% style="color:blue" %)**AT Command:**525 +* AT Command: 546 546 547 - (% style="color:#037691" %)**AT+ATDC=xx.**527 +AT+ATDC=xx. 548 548 549 -Example: **~-~-> **Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000529 +Example: AT+ATDC=60000 à Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000 550 550 551 551 552 -* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**532 +* Downlink Payload (prefix 0xB1): 553 553 554 - (% style="color:#037691" %)**0xB1 00 00 3C** (%%)~/~/534 +0xB1 00 00 3C ~/~/Same as AT+ATDC=60000 555 555 556 556 537 +1. 538 +11. 539 +111. Set Sports Mode Packet transmission interval 557 557 558 -=== 3.2.3 Set Sports Mode Packet transmission interval === 559 - 560 - 561 561 Set sports packet transmit interval 562 562 563 -* (% style="color:blue" %)**AT Command:**543 +* AT Command: 564 564 565 - (% style="color:#037691" %)**AT+MTDC=xx.**545 +AT+MTDC=xx. 566 566 567 - Example: **~-~-> **Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000547 + Example: AT+MTDC=300000 à Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000 568 568 569 569 570 -* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**550 +* Downlink Payload (prefix 0x03): 571 571 572 - (% style="color:#037691" %)**0x03 00 01 2C**(%%)~/~/552 +0x03 00 01 2C ~/~/Same as AT+ MTDC=3000000 573 573 574 574 575 575 576 -=== 3.2.4 Exit Alarm === 556 +1. 557 +11. 558 +111. Exit Alarm 577 577 578 - 579 579 Server send downlink command to exit Alarm mode 580 580 581 -* (% style="color:blue" %)**AT Command:No AT Command**562 +* AT Command: 582 582 564 +No AT Command 583 583 584 -* (% style="color:blue" %)**Downlink Payload (prefix 0x02):** 585 585 586 - (%style="color:#037691"%)**0x0201** (%%)~/~/ Exit Alarm Mode567 +* Downlink Payload (prefix 0x02): 587 587 569 +0x02 01 ~/~/ Exit Alarm Mode 588 588 589 589 590 -=== 3.2.5 Disable/Enable LED flash === 572 +1. 573 +11. 574 +111. Disable/Enable LED flash 591 591 592 - 593 593 Disable/Enable LED for position, downlink and uplink 594 594 595 -* (% style="color:blue" %)**AT Command:**578 +* AT Command: 596 596 597 - (% style="color:#037691" %)**AT+LON=xx. (Disable (0), Enable (1), default:1)**580 +AT+LON=xx. (Disable (0), Enable (1), default:1) 598 598 599 - Example: AT+LON=0 **~-~-> **Disable LED for position, downlink and uplink.582 + Example: AT+LON=0 à Disable LED for position, downlink and uplink. 600 600 601 601 602 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**585 +* Downlink Payload (prefix 0xAE): 603 603 604 - (% style="color:#037691" %)**0xAE 00** (%%)~/~/587 +0xAE 00 ~/~/Same as AT+LON=0 605 605 606 606 607 607 608 -=== 3.2.6 Disable/Enable movement detect (Debug Only) === 609 609 592 +1. 593 +11. 594 +111. Disable/Enable movement detect (Debug Only) 610 610 611 611 User can use this feature to check and set thread hole of movement detect 612 612 613 -* (% style="color:blue" %)**AT Command:**598 +* AT Command: 614 614 615 - (% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)**600 +AT+INTWK=xx. (Disable (0), Enable (1), default:0) 616 616 617 - Example: **~-~-> **Enable detect movement.602 + Example: AT+ INTWK =1 à Enable detect movement. 618 618 619 619 620 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**605 +* Downlink Payload (prefix 0xAF): 621 621 622 - (% style="color:#037691" %)**0xAF 01** (%%)~/~/607 +0xAF 01 ~/~/Same as AT+ INTWK =1 623 623 624 624 625 625 626 -=== 3.2.7 Set Positioning Mode === 611 +1. 612 +11. 613 +111. Set Positioning Mode 627 627 628 - 629 629 SMOD define the how TrackerD scan and uplink date. 630 630 631 -GPS室外定位模式: 617 +GPS室外定位模式:设备默认模式,设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是3分钟定位,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。GPS还有一种logdata模式,在断网的情况下将数据存储下来,等到有网的时候,一次将数据以每10秒上报。 632 632 633 -BLE室内定位模式: 619 + BLE室内定位模式:设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是5秒,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每3分钟发送一次)。 634 634 635 -GPS和BLE混动模式:设备入网后会发送device当前模式下的信息,随后立即判断是否在室内,如果是就进行BLE定位,不是就GPS定位。如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。 621 + GPS和BLE混动模式:设备入网后会发送device当前模式下的信息,随后立即判断是否在室内,如果是就进行BLE定位,不是就GPS定位。如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。 636 636 637 -运动模式: 623 +运动模式:设备入网后会发送device当前模式下的信息,随后发送GPS定位数据,设备判断是否在运动,没有运动传感器没有检测到动作,立即进入静止状态(默认20分钟),如果产生运动,将每5分钟发送一次数据,再第五分钟后检测设备有误运动,无将切换到静止状态,有立即发送数据。 638 638 639 639 640 640 641 -* (% style="color:blue" %)**AT Command:** 642 642 643 - (% style="color:#037691" %)**AT+SMOD=xx.**628 +* AT Command: 644 644 630 +AT+SMOD=xx. 645 645 646 - **Example:**632 + Example: 647 647 648 - AT+ SMOD =1,0 **~-~-> **GPS+ BAT+ State+Tem&Hum634 + AT+ SMOD =1,0 à GPS+ BAT+ State+Tem&Hum 649 649 650 - AT+ SMOD =1,1 **~-~->**GPS +BAT State636 + AT+ SMOD =1,1 à GPS +BAT State 651 651 652 - AT+ SMOD =2,3 **~-~->**(iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。638 + AT+ SMOD =2,3 à (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。 653 653 654 654 655 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**641 +* Downlink Payload (prefix 0xA5): 656 656 657 - (% style="color:#037691" %)**0xA5 01 00**(%%)~/~/643 +0xA5 01 00 ~/~/ Same as AT+ SMOD =1,0 658 658 659 659 646 +1. 647 +11. 648 +111. Set MAX GPS position time 660 660 661 -=== 3.2.8 Set MAX GPS position time === 662 - 663 - 664 664 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. 665 665 666 666 ... ... @@ -667,105 +667,102 @@ 667 667 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. 668 668 669 669 670 -* (% style="color:blue" %)**AT Command:**656 +* AT Command: 671 671 672 - (% style="color:#037691" %)**AT+FTIME=xx**(%%)**~-~-> **Set to use xx as max fix time.658 +AT+FTIME=xx à Set to use xx as max fix time. 673 673 674 -Example: 660 +Example: AT+FTIME=150 675 675 676 676 677 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**663 +* Downlink Payload (prefix 0xAA): 678 678 679 - (% style="color:#037691" %)**0xAA 00 96** (%%)~/~/665 +0xAA 00 96 ~/~/Set AT+FTIME=150 680 680 681 681 682 682 683 -=== 3.3.9 Set PDOP value for GPS fix accuracy === 684 684 670 +1. 671 +11. 672 +111. Set PDOP value for GPS fix accuracy 685 685 686 -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.674 +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. 687 687 688 688 689 689 A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0 690 690 691 691 692 -* (% style="color:blue" %)**AT Command:**680 +* AT Command: 693 693 694 - (% style="color:#037691" %)**AT+PDOP=2.5** (%%) **~-~->**Set PDOP to 2.5682 +AT+PDOP=2.5 à Set PDOP to 2.5 695 695 696 696 697 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**685 +* Downlink Payload (prefix 0xAD): 698 698 699 - (% style="color:#037691" %)**0xAD 00 0A**(%%)~/~/687 +0xAD 00 0A ~/~/Set AT+PDOP=1 (0x0A / 10 =1) 700 700 701 - (% style="color:#037691" %)**0xAD 00 19**(%%)~/~/689 +0xAD 00 19 ~/~/Set AT+PDOP=2.5 (0x19 / 10 =2.5) 702 702 703 - (% style="color:#037691" %)**0xAD 00 46**(%%)691 +0xAD 00 46 ~/~/Set AT+PDOP=7 (0x46 / 10 =7) 704 704 705 - 706 - 707 707 Disable/Enable the confirmation mode 708 708 709 -* (% style="color:blue" %)**AT Command:**695 +* AT Command: 710 710 711 - (% style="color:#037691" %)**AT+CFM=xx.**697 +AT+CFM=xx. 712 712 699 + Example: 713 713 714 - **~Example:**701 + AT+ CFM=0 à Disable confirmation 715 715 716 - AT+ CFM= 0**~-~->** Disable confirmation703 + AT+ CFM=1 à Enable confirmation 717 717 718 - AT+ CFM=1 **~-~-> ** Enable confirmation 719 719 706 +* Downlink Payload (prefix 0x05): 720 720 721 - *(%style="color:blue"%)**Downlink Payload(prefix0x05):**708 +0x05 01 ~/~/ Same as AT+ SMOD =1 722 722 723 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+ SMOD =1 724 724 725 725 726 726 727 -= 4. Setting for Different Scenarios = 728 728 729 729 715 +1. Setting for Different Scenarios 730 730 731 -= 5. Upload Firmware = 732 732 733 733 734 -== 5.1 Firmware Change Log == 719 +1. Upload Firmware 720 +11. Firmware Change Log 735 735 736 - 737 737 **[[See this link>>url:https://github.com/dragino/TrackerD]]** 738 738 739 739 725 +1. 726 +11. How to upgrade firmware 740 740 741 - ==5.2How to upgrade firmware==728 +User can use the TrackerD ’s USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below: 742 742 743 743 744 - UsercanuseheTrackerD'sUSB port to upgradefirmwareintoit. The hardwareconnection for upgradefirmwareisas below:731 +**Step1: **Connect TrackerD and PC via USB cable shipped with TrackerD. 745 745 733 +**Step2:** Install CH9102 driver in the PC. 746 746 747 -(% style="color:blue" %)**Step1: **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD. 748 - 749 - 750 -(% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC. 751 - 752 752 After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager. 753 753 754 754 755 - (% 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]]738 +**Step3:** Download and Install Flash Tool: 756 756 740 +[[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]] 757 757 758 - (% style="color:blue" %)**Step4:**(%%)Run Flash Download Tool and configure chip type to ESP32742 +**Step4:** Run Flash Download Tool and configure chip type to ESP32 759 759 760 760 761 -[[image: 1664503563660-578.png]]745 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png||alt="image-20220712083115-1.png"]] 762 762 747 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png||alt="image-20220712083115-2.png"]] 763 763 764 -[[image:1664503574618-659.png]] 765 765 750 +**Step5:** Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 766 766 767 -(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 768 - 769 769 [[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 770 770 771 771 ... ... @@ -775,77 +775,75 @@ 775 775 776 776 ESP_LORA-eeprom-class.bin @ 0x10000 777 777 761 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png||alt="image-20220712083115-3.png"]] 778 778 779 -[[image:1664503593459-435.png]] 780 - 781 - 782 - 783 783 After upgrade finish, it will show finish as below: 784 784 785 -[[image: 1664503611848-385.png]]765 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png||alt="image-20220712083115-4.png"]] 786 786 787 787 788 788 789 -= 6. Developer Guide = 790 790 791 791 792 - == 6.1CompileSourceCode==771 +1. Developer Guide 793 793 794 794 795 -=== 6.1.1 Set up ARDUINO compile environment === 774 +* 775 +*1. Compile Source Code 776 +*11. Set up ARDUINO compile environment 777 +* Download the latest Arduino software (IDE) from the Arduino official website 796 796 779 +[[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]] 797 797 798 - *DownloadthelatestArduinosoftware(IDE)fromtheArduino officialebsite:[[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]]781 +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]] 799 799 800 - 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]]783 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]] 801 801 785 +* Go to tools ~-~-> Boards ~-~-> Boards Manager, find the esp32 information and install it. 802 802 803 -[[image: 1664503635019-941.png]]787 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]] 804 804 805 805 806 -* (% style="color:#037691"%)**Gototools ~-~-> Boards~-~-> Boards Manager**,(%%)findtheesp32 informationandinstall it.790 +* Download the latest TrackerD from the dragino github 807 807 808 -[[image: 1664503715811-892.png]]792 +[[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]] 809 809 810 810 795 +Put the Library in the TrackerD directory into the libraries file in the Arduino directory 811 811 812 - * Download theatest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]797 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]] 813 813 814 -Put the Library in the TrackerD directory into the libraries file in the Arduino directory: 815 815 816 816 817 -[[image:1664503752288-974.png]] 818 818 802 +* 803 +*1. Source Code 804 +* Open the example in the TrackerD file, please select the correct port in the IDE, as shown below: 819 819 806 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]] 820 820 821 - ==6.2SourceCode ==808 +* Click to upload 822 822 810 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]] 823 823 824 -* (% style="color:blue"%)**Openthe exampleintheTrackerDfile,pleaseselectthecorrectport intheIDE,as shown below:**812 +* Check the result, if the upload is successful, as shown below, open the serial port to view the data 825 825 826 -[[image:1664503794261-827.png]] 827 827 815 +[[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]] 828 828 829 829 830 -* (% style="color:blue" %)**Click to upload** 831 831 832 -[[image:1664503808294-336.png]] 833 833 834 834 835 835 836 -* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 837 - 838 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 839 - 840 - 841 - 842 842 = 7. FAQ = 843 843 844 844 825 + 845 845 == 7.1 How to change the LoRa Frequency Bands/Region? == 846 846 847 847 848 -User can follow the introduction for [[how to upgrade image>> ||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.829 +User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download. 849 849 850 850 851 851 ... ... @@ -875,6 +875,7 @@ 875 875 (% style="color:blue" %)**XXX**(%%): The default frequency band 876 876 877 877 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433 859 +* (% style="color:red" %)**CN470**(%%): Default frequency band CN470 878 878 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868 879 879 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865 880 880 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920 ... ... @@ -882,25 +882,33 @@ 882 882 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 883 883 * (% style="color:red" %)**US915**(%%): Default frequency band US915 884 884 867 + 885 885 = 9. Packing Info = 886 886 887 887 888 888 **Package Includes**: 889 889 890 -* TrackerD LoRaWAN GPS/BLE Tracker x 1 891 -* USB recharge & program cable x 1 873 +* TrackerD x 1 874 +* Rechargeable cable x 1 875 +* Program Cable x 1 892 892 893 893 **Dimensions and Weight**: 894 894 895 -* Device Size: 85 x 48 x 15 cm896 -* Weight: 5 0g879 +* Device Size: 85 x 48 x 15 mm/pcs 880 +* Weight: 55g/pcs 897 897 898 -= 10. Support = 899 899 900 900 884 += 10. Support = 885 + 901 901 * 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. 902 -* 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]]887 +* 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 903 903 889 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]] 890 + 891 + 892 + 893 + 904 904 = 11. Reference = 905 905 906 906
- 1664501652064-326.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -143.9 KB - Content
- 1664501677253-891.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -202.7 KB - Content
- 1664501711466-918.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -62.0 KB - Content
- 1664501721248-725.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -55.6 KB - Content
- 1664501734705-405.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -64.1 KB - Content
- 1664501784668-703.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -62.0 KB - Content
- 1664501958445-288.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -74.1 KB - Content
- 1664502116362-706.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -56.0 KB - Content
- 1664502166010-515.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -41.3 KB - Content
- 1664502425687-834.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -38.2 KB - Content
- 1664502649601-895.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -59.2 KB - Content
- 1664502676891-606.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -64.3 KB - Content
- 1664502695771-538.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -54.7 KB - Content
- 1664502715371-321.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -79.9 KB - Content
- 1664502835802-546.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -37.8 KB - Content
- 1664502854406-763.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -14.3 KB - Content
- 1664502999401-486.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -916.7 KB - Content
- 1664503022490-662.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -133.6 KB - Content
- 1664503035713-500.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -354.0 KB - Content
- 1664503047675-651.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -199.1 KB - Content
- 1664503563660-578.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -38.1 KB - Content
- 1664503574618-659.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -139.8 KB - Content
- 1664503593459-435.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -183.3 KB - Content
- 1664503611848-385.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -175.9 KB - Content
- 1664503635019-941.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -161.8 KB - Content
- 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