Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Xiaoling on 2025/04/27 16:48
From version 55.1
edited by Edwin Chen
on 2022/10/06 18:45
on 2022/10/06 18:45
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 7 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.Xiaoling - Content
-
... ... @@ -1,15 +9,6 @@ 1 -== == 2 - 3 -(% style="text-align:center" %) 4 -[[image:1664505654417-133.png]] 5 - 6 - 7 - 8 - 9 9 (% class="wikigeneratedid" %) 10 10 **Table of Contents:** 11 11 12 -{{toc/}} 13 13 14 14 15 15 ... ... @@ -16,10 +16,9 @@ 16 16 17 17 = 1. Introduction = 18 18 10 +== 1.1 OverView == 19 19 20 -== 1.1 What is TrackerD == 21 21 22 - 23 23 ((( 24 24 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**. 25 25 ))) ... ... @@ -27,14 +27,10 @@ 27 27 ((( 28 28 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. 29 29 30 -((( 31 31 TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution. 32 -))) 33 33 34 -((( 35 35 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. 36 36 ))) 37 -))) 38 38 39 39 ((( 40 40 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. ... ... @@ -48,7 +48,6 @@ 48 48 (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.** 49 49 50 50 51 - 52 52 == 1.2 Specifications == 53 53 54 54 ... ... @@ -63,11 +63,13 @@ 63 63 * EEPROM: 520 KB 64 64 * Clock Speed: 32Mhz 65 65 51 + 66 66 (% style="color:blue" %)**Common DC Characteristics:** 67 67 68 68 * Supply Voltage: 5V via USB port or Internal li-on battery 69 69 * Operating Temperature: -40 ~~ 60°C 70 70 57 + 71 71 (% style="color:blue" %)**LoRa Spec:** 72 72 73 73 * Frequency Range, ... ... @@ -89,10 +89,12 @@ 89 89 * Packet engine up to 256 bytes with CRC. 90 90 * LoRaWAN 1.0.3 Specification 91 91 79 + 92 92 (% style="color:blue" %)**Battery:** 93 93 94 94 * 1000mA Li-on Battery power (for model TrackerD) 95 95 84 + 96 96 (% style="color:blue" %)**Power Consumption** 97 97 98 98 * Sleeping Mode: 200uA ... ... @@ -99,6 +99,9 @@ 99 99 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm 100 100 * Tracking: max: 38mA 101 101 91 + 92 + 93 + 102 102 == 1.3 Features == 103 103 104 104 ... ... @@ -105,7 +105,7 @@ 105 105 * LoRaWAN 1.0.3 Class A 106 106 * ESP32 PICO D4 107 107 * SX1276/78 Wireless Chip 108 -* Arduino IDE Compatible 100 +* Arduino IDE Compatible 109 109 * Open source hardware / software 110 110 * Regular/ Real-time GPS,BLE,WIFI tracking 111 111 * Built-in3 axis accelerometer (LIS3DH) ... ... @@ -117,6 +117,8 @@ 117 117 * Tri-color LED, Alarm button 118 118 * Datalog 119 119 112 + 113 + 120 120 == 1.4 Applications == 121 121 122 122 ... ... @@ -123,9 +123,11 @@ 123 123 * Logistics and Supply Chain Management 124 124 * Human tracking 125 125 126 -= 2.1 Use TrackerD = 127 127 128 128 122 + 123 += 2.1 Use TrackerD = 124 + 129 129 == 2.1 How it works? == 130 130 131 131 ... ... @@ -132,306 +132,249 @@ 132 132 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. 133 133 134 134 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:1664501784668-703.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 181 182 -(% style="color:blue" %) **Step 2**:(%%)PoweronTrackerD by usingtheon boardswitch.177 +**(% style="color:blue" %)Positioning Mode(SMOD):** 183 183 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. 184 184 185 - (%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]]. 186 186 187 187 188 -== 2.3 PositioningMode(SMOD)==186 +== 2.3 Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~- == 189 189 190 -Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 191 191 192 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)only get and uplink GPS location info. 193 -* (% style="color:#037691" %)**BLE ONLY: **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking. 194 -* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 189 +=== 2.3.1 Uplink FPORT=5, Device Status === 195 195 196 -Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 197 197 198 198 199 -== 2.3 Uplink Pa yload==193 +=== 2.3.2 Uplink FPORT= , Realtime GNSS Positioning === 200 200 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. ) 201 201 202 -=== 2.3.1 Uplink FPORT~=5, Device Status === 203 203 204 -Uplink the device configures with FPORT=5. Once LHT52 Joined the network, it will uplink this message to the server. After first uplink, LHT52 will uplink Device Status every 12 hours. 198 +|((( 199 +**Size** 205 205 206 -|=**Size (bytes)**|=**1**|=**2**|=**1**|=**1**|=**2** 207 -|**Value**|Sensor Model|Firmware Version|Frequency Band|Sub-band|BAT 201 +**(bytes)** 202 +)))|4|4|2|1|((( 203 +2 208 208 209 -[[image:image-20221006181357-2.png]] 205 +(optional ) 206 +)))|((( 207 +2 210 210 211 -Example Payload (FPort=5): [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT52%20-%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20User%20Manual/WebHome/image-20220621105116-11.png?rev=1.1||alt="image-20220621105116-11.png"]] 209 +(optional) 210 +))) 211 +|**Value**|[[Latitude>>path:#Location]]|[[Longitude>>path:#Location]]|((( 212 +[[Alarm &>>path:#Alarm]] 212 212 213 -**Sensor Model**: For TrackerD, this value is 0x13. 214 +[[BAT>>path:#Alarm]] 215 +)))|[[FLAG>>path:#Flag]]|Hum|[[Tem>>path:#Pitch]] 214 214 215 -**Firmware Version**: 0x0100, Means: v1.0.0 version. 216 216 217 - **Frequency Band**:218 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]] 218 218 219 -*0x01: EU868 220 220 221 -* 0x02:US915221 +**Alarm & BAT:** 222 222 223 -*0x03: IN865 223 +|**Size(bit)**|1 bit|1bit|14 bits 224 +|**Value**|reserve|Alarm Indicate|[[BAT>>path:#BAT]] 224 224 225 -* 0x04:AU915226 +**FLAG:** 226 226 227 -*0x05: KZ865 228 +|**Size(bit)**|2 bits|1bit|5 bits 229 +|**Value**|[[MOD>>path:#MD]]|[[LON>>path:#LON]]|Firmware version 228 228 229 -*0x06: RU864 230 230 231 -*0x07: AS923 232 232 233 -*0x08 :AS923-1233 +**Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A ** 234 234 235 -*0x09: AS923-2 236 236 237 -* 0x0a:AS923-3236 +**Location info:** 238 238 239 -* *Sub-Band**:value 0x00~~0x08(onlyfor CN470, AU915,US915. Others are0x00)238 +* Latitude: 02863D68⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// 240 240 241 - **BAT**: shows the batteryvoltageforTrackerD.240 +//value = 02863D68 /1000000 = 42.351976// 242 242 243 - Ex1: 0x0B3A=2874mV242 +* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// 244 244 245 - Use can also gettheDeviceStatusuplinkthroughthe downlink command:244 +//value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 246 246 247 247 248 - === 2.3.2 Uplink FPORT~=2, RealtimeGNSS Positioning ===247 +Important note: 249 249 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: 250 250 251 - Thedefault uplink payload includes totally 11 bytes. (Usercan useAT+SMOD=1,0to enable uploading on-boardTemperature and humidity value, and totalpayload will be 15 bytes,please note15 bytes won't work on DR0on US915/AU915 frequency band.)253 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]] 252 252 253 253 254 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) 255 -|=(% scope="row" style="width: 50px;" %)((( 256 -**Size(bytes)** 257 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)((( 258 -2(optional) 259 -)))|(% style="width:87px" %)((( 260 -2(optional) 261 -))) 262 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 263 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 264 -)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 256 +1. While GPS can’t get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 265 265 266 -[[image: 1664501958445-288.png]]258 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]] 267 267 260 +* **Alarm**: Example: 0x4B & 0x40 >> 6 = 0x01 261 +* **BAT**: Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV). 268 268 269 - ====(%style="color:blue"%)**Alarm&BAT:**(%%)====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: \ 270 270 271 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 272 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits 273 -|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 274 274 275 -==== (% style="color:blue" %)**FLAG:**(%%) ==== 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% 276 276 277 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 278 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits 279 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version 280 280 281 -** Example:**Payload:0x02863D68FAC29BAF4B4560 0202 011A273 +* **LON: **Enable/Disable LED activity for uplink 282 282 275 +0x00: Disable LED indicator. 283 283 284 - ==== (% style="color:blue"%)**Locationinfo:**(%%)====277 +0x01: Enable LED indicator (Default Value) 285 285 286 -* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976// 287 -* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 288 288 289 -(% style="color:red" %)**Important note:** 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 290 290 291 -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. 292 292 293 -2. When enable 9-axis motion sensor, 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: 294 294 285 +=== 2.3.3 Uplink FPORT= , History GNSS Positioning === 295 295 296 -[[image:1664502116362-706.png]] 297 297 298 298 289 +=== 2.3.4 BLE positioning Payload(Fport=2) === 299 299 300 - 4. While GPS can't get location info aftertimeout(FTIMEParameter), the latitudeandlongitude will befilled withall 0x00:291 +Different MODE has different payload: 301 301 302 - [[image:1664502166010-515.png]]293 +**MODE=2** 303 303 295 +|((( 296 +**Size** 304 304 298 +**(bytes)** 299 +)))|16|4|4|2|4|2|1 300 +|**Value**|[[UUID>>path:#Location]]|((( 301 +iBeacon 305 305 306 -==== (% style="color:blue" %)**Alarm:**(%%) ==== 303 +MAJOR 304 +)))|((( 305 +iBeacon 307 307 308 -Example: 0x4B & 0x40 >> 6 = 0x01 307 +MINOR 308 +)))|((( 309 +iBeacon Measured 309 309 311 +Power 312 +)))|((( 313 +iBeacon 310 310 311 -==== (% style="color:blue" %)**BAT:**(%%) ==== 315 +RSSI 316 +)))|((( 317 +[[Alarm &>>path:#Alarm]] 312 312 313 -Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV). 319 +[[BAT>>path:#Alarm]] 320 +)))|[[FLAG>>path:#Flag]] 314 314 315 -((( 316 -The battery info shows the current voltage, for (% style="color:blue" %)**TrackerD**(%%) version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \ 317 -))) 318 318 319 -* > 4.0v : 80% ~~ 100% 320 -* 3.85v ~~3.99v: 60% ~~ 80% 321 -* 3.70v ~~ 3.84v: 40% ~~ 60% 322 -* 3.40v ~~ 3.69v: 20% ~~ 40% 323 -* < 3.39v: 0~~20% 323 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]] 324 324 325 325 326 -==== (% style="color:blue" %)**LON:**(%%) ==== 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. 327 327 328 -Enable/Disable LED activity for uplink 329 329 330 -((( 331 -0x00: Disable LED indicator. 332 -))) 333 333 334 -((( 335 -0x01: Enable LED indicator (Default Value) 336 -))) 337 - 338 - 339 -==== (% style="color:blue" %)**Hum:**(%%) ==== 340 - 341 -0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree 342 - 343 - 344 -==== (% style="color:blue" %)**Tem:**(%%) ==== 345 - 346 -011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree// 347 - 348 - 349 - 350 -=== 2.3.3 Uplink FPORT~= , History GNSS Positioning === 351 - 352 - 353 - 354 -=== 2.3.4 BLE positioning Payload(Fport2) === 355 - 356 - 357 -Different MODE has different payload: (% style="color:blue" %)**MODE=2** 358 - 359 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 360 -|=(% scope="row" style="width: 60px;" %)((( 361 -**Size(bytes)** 362 -)))|(% 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 363 -|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)((( 364 -iBeacon MAJOR 365 -)))|(% style="width:63px" %)((( 366 -iBeacon MINOR 367 -)))|(% style="width:71px" %)((( 368 -iBeacon Measured Power 369 -)))|(% style="width:50px" %)((( 370 -iBeacon RSSI 371 -)))|(% style="width:47px" %)((( 372 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 373 -)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 374 - 375 -[[image:1664502425687-834.png]] 376 - 377 - 378 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV). 379 -* (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 380 -* (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 381 -* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. 382 -* (% style="color:#037691" %)**MINOR:** (%%)The MAJOR from the strongest iBeacon. 383 -* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 384 -* (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 385 - 386 386 === 2.3.5 Add Payload format in TTN V3 === 387 387 388 - 389 389 In TTN V3, use can add a custom payload so it shows friendly. 390 390 391 -In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**340 +In the page Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder 392 392 342 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]] 393 393 394 -[[image:1664502649601-895.png]] 395 - 396 - 397 397 Add the decoder from this link: 398 398 399 399 400 400 Save the change the uplink message will be parsed. As below: 401 401 402 -[[image: 1664502676891-606.png]]349 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]] 403 403 404 404 405 405 353 + 354 + 406 406 == 2.4 Integrate with Datacake == 407 407 408 408 409 -((( 410 410 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. 411 -))) 412 412 413 -((( 414 -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]] 415 -))) 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]] 416 416 362 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]] 417 417 418 -[[image:1664502695771-538.png]] 419 419 420 - 421 - 422 422 == 2.5 Integrate with Tago == 423 423 424 424 425 -((( 426 426 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. 427 -))) 428 428 429 -((( 430 430 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]] 431 -))) 432 432 372 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]] 433 433 434 -[[image:1664502715371-321.png]] 435 435 436 436 437 437 ... ... @@ -438,251 +438,241 @@ 438 438 == 2.6 Alarm Mode == 439 439 440 440 441 -((( 442 -User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 443 -))) 380 +User can push the **RED button** by more than 5 seconds to enter Alarm Mode. 444 444 445 445 446 -((( 447 -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. 448 -))) 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. 449 449 450 450 451 -((( 452 452 Two ways to exit alarm mode: 453 -))) 454 454 455 455 * Server send a downlink command to exit. 456 456 * User fast press the RED button 10 times. 457 457 458 -((( 459 -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. 460 -))) 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. 461 461 462 462 394 +== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- == 463 463 464 -== 2.7 Sports Mode == 465 465 466 466 467 - InSportsMode,TrackerDwill check ifthere is motion. If there is no motion, device will senduplinksevery 20 minutes. If there is motion, device will send uplink every 5 minutes.398 +== 2.8 LED Status == 468 468 469 469 470 -== 2.8 LED Status == 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 471 471 472 472 473 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 474 -|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 475 -|(% 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 476 -|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes 477 -|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A 478 -|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes 479 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes 480 -|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes 481 -|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes 482 -|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes 483 -|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes 484 -|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 485 -|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 486 486 487 -== 2.9 Button Function == 488 488 489 489 490 - (% style="color:blue"%)**RESETbutton:**418 +== 2.9 Button Function == 491 491 492 - [[image:1664502835802-546.png]]420 +**RESET button:** 493 493 422 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]] 423 + 494 494 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server. 495 495 496 496 497 - (% style="color:red" %)**RED button:**427 +**RED button:** 498 498 499 -[[image: 1664502854406-763.png]]429 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]] 500 500 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. 501 501 502 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %) 503 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description** 504 -|(% 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"]] 505 -|(% 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 506 -|(% 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. 507 507 508 -== 2.10 USB Port Function == 509 509 510 510 439 +== 2.10 USB Port Function == 440 + 511 511 The USB interface of TrackerD has below functions: 512 512 513 513 * Power on the device 514 514 * Recharge the battery 515 -* [[Configure Device>> ||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]516 -* [[Upgrade Firmware>> ||anchor="H5.UploadFirmware"]]445 +* [[Configure Device>>path:#AT_Command]] 446 +* [[Upgrade Firmware>>path:#upgrade_image]] 517 517 518 -= 3. Configure TrackerD via AT command or LoRaWAN downlink = 519 519 520 520 521 -User can configure TrackerD via AT Command or LoRaWAN Downlink. 522 522 523 -LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] 524 524 452 += 3. Configure TrackerD via AT command or LoRaWAN downlink = 525 525 526 526 527 - ==3.1AccessAT Command==455 +User can configure TrackerD via AT Command or LoRaWAN Downlink. 528 528 457 +LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]] 529 529 530 -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. 531 531 460 +== 3.1 Access AT Command == 532 532 533 - [[image:1664502999401-486.png]]462 +TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below. ... 534 534 464 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]] 535 535 536 -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: 537 537 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: 538 538 539 -[[image:1664503022490-662.png]] 540 540 470 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]] 541 541 542 542 543 -[[image:1664503035713-500.png]] 544 544 474 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]] 545 545 476 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]] 546 546 547 -[[image:1664503047675-651.png]] 548 548 549 - 550 - 551 551 == 3.2 Command Set == 552 552 553 553 554 554 === 3.2.1 Set Transmit Interval === 555 555 556 - 557 557 Set device uplink interval. 558 558 559 -* (% style="color:blue" %)**AT Command:**486 +* AT Command: 560 560 561 - (% style="color:#037691" %)**AT+TDC=xxx**488 +AT+TDC=xxx 562 562 563 -Example: 490 +Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds) 564 564 565 565 566 -* (% style="color:blue" %)**Downlink Payload (prefix 0x01):**493 +* Downlink Payload (prefix 0x01): 567 567 568 - (% style="color:#037691" %)**0x01 00 01 2C**(%%)~/~/495 +0x01 00 01 2C ~/~/ Same as AT+TDC=300000 569 569 570 570 571 - 572 572 === 3.2.2 Set Alarm Packet transmission interval === 573 573 574 - 575 575 Set alarm packet transmit interval 576 576 577 -* (% style="color:blue" %)**AT Command:**502 +* AT Command: 578 578 579 - (% style="color:#037691" %)**AT+ATDC=xx.**504 +AT+ATDC=xx. 580 580 581 -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 582 582 583 583 584 -* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**509 +* Downlink Payload (prefix 0xB1): 585 585 586 - (% style="color:#037691" %)**0xB1 00 00 3C** (%%)~/~/511 +0xB1 00 00 3C ~/~/Same as AT+ATDC=60000 587 587 588 588 514 +=== 3.3.3 Set Sports Mode Packet transmission interval === 589 589 590 -=== 3.2.3 Set Sports Mode Packet transmission interval === 591 - 592 - 593 593 Set sports packet transmit interval 594 594 595 -* (% style="color:blue" %)**AT Command:**518 +* AT Command: 596 596 597 - (% style="color:#037691" %)**AT+MTDC=xx.**520 +AT+MTDC=xx. 598 598 599 -Example: **~-~-> **Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000522 + Example: AT+MTDC=300000 à Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000 600 600 601 601 602 -* (% style="color:blue" %)**Downlink Payload (prefix 0x03):**525 +* Downlink Payload (prefix 0x03): 603 603 604 - (% style="color:#037691" %)**0x03 00 01 2C**(%%)~/~/527 +0x03 00 01 2C ~/~/Same as AT+ MTDC=3000000 605 605 606 606 607 607 608 -=== 3. 2.4 Exit Alarm ===531 +=== 3.3.4 Exit Alarm === 609 609 610 - 611 611 Server send downlink command to exit Alarm mode 612 612 613 -* (% style="color:blue" %)**AT Command:No AT Command**535 +* AT Command: 614 614 615 - * (% style="color:blue"%)**DownlinkPayload(prefix 0x02):**537 +No AT Command 616 616 617 -(% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 618 618 540 +* Downlink Payload (prefix 0x02): 619 619 542 +0x02 01 ~/~/ Exit Alarm Mode 620 620 621 -=== 3.2.5 Disable/Enable LED flash === 622 622 545 +=== 3.3.5 Disable/Enable LED flash === 623 623 624 624 Disable/Enable LED for position, downlink and uplink 625 625 626 -* (% style="color:blue" %)**AT Command:**549 +* AT Command: 627 627 628 - (% style="color:#037691" %)**AT+LON=xx. (Disable (0), Enable (1), default:1)**551 +AT+LON=xx. (Disable (0), Enable (1), default:1) 629 629 630 -Example: AT+LON=0 **~-~-> **Disable LED for position, downlink and uplink.553 + Example: AT+LON=0 à Disable LED for position, downlink and uplink. 631 631 632 632 633 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**556 +* Downlink Payload (prefix 0xAE): 634 634 635 - (% style="color:#037691" %)**0xAE 00** (%%)~/~/558 +0xAE 00 ~/~/Same as AT+LON=0 636 636 637 637 638 638 639 -=== 3.2.6 Disable/Enable movement detect (Debug Only) === 640 640 563 +=== 3.3.6 Disable/Enable movement detect (Debug Only) === 641 641 642 642 User can use this feature to check and set thread hole of movement detect 643 643 644 -* (% style="color:blue" %)**AT Command:**567 +* AT Command: 645 645 646 - (% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)**569 +AT+INTWK=xx. (Disable (0), Enable (1), default:0) 647 647 648 -Example: **~-~-> **Enable detect movement.571 + Example: AT+ INTWK =1 à Enable detect movement. 649 649 650 650 651 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**574 +* Downlink Payload (prefix 0xAF): 652 652 653 - (% style="color:#037691" %)**0xAF 01** (%%)~/~/576 +0xAF 01 ~/~/Same as AT+ INTWK =1 654 654 655 655 656 656 657 -=== 3. 2.7 Set Positioning Mode ===580 +=== 3.3.7 Set Positioning Mode === 658 658 582 +SMOD define the how TrackerD scan and uplink date. 659 659 660 -S MODdefine the how TrackerD scan and uplinkdata:584 +GPS室外定位模式:设备默认模式,设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是3分钟定位,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。GPS还有一种logdata模式,在断网的情况下将数据存储下来,等到有网的时候,一次将数据以每10秒上报。 661 661 586 + BLE室内定位模式:设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是5秒,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每3分钟发送一次)。 662 662 663 - *(%style="color:blue"%)**ATCommand:**588 + GPS和BLE混动模式:设备入网后会发送device当前模式下的信息,随后立即判断是否在室内,如果是就进行BLE定位,不是就GPS定位。如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。 664 664 665 - (% style="color:#037691" %)**AT+SMOD=xx. **590 +运动模式:设备入网后会发送device当前模式下的信息,随后发送GPS定位数据,设备判断是否在运动,没有运动传感器没有检测到动作,立即进入静止状态(默认20分钟),如果产生运动,将每5分钟发送一次数据,再第五分钟后检测设备有误运动,无将切换到静止状态,有立即发送数据。 666 666 667 667 668 - **Example:** 669 669 670 - AT+ SMOD =1,0 **~-~-> ** GPS+ BAT+ State+Tem&Hum 671 671 672 - AT+ SMOD =1,1**~-~->**GPS +BATState595 +* AT Command: 673 673 674 - 2,3**~-~->** (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。597 +AT+SMOD=xx. 675 675 599 + Example: 676 676 677 - *(%style="color:blue"%)**DownlinkPayload(prefix0xA5):**601 + AT+ SMOD =1,0 à GPS+ BAT+ State+Tem&Hum 678 678 679 - (%style="color:#037691"%)**0xA50100**(%%)~/~/SameasAT+SMOD =1,0603 + AT+ SMOD =1,1 à GPS +BAT State 680 680 605 + AT+ SMOD =2,3 à (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。 681 681 682 682 683 - ===3.2.8Set MAX GPSpositiontime ===608 +* Downlink Payload (prefix 0xA5): 684 684 610 +0xA5 01 00 ~/~/ Same as AT+ SMOD =1,0 685 685 612 + 613 +=== 3.3.8 Set MAX GPS position time === 614 + 686 686 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. 687 687 688 688 ... ... @@ -689,60 +689,60 @@ 689 689 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. 690 690 691 691 692 -* (% style="color:blue" %)**AT Command:**621 +* AT Command: 693 693 694 - (% 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. 695 695 696 -Example: 625 +Example: AT+FTIME=150 697 697 698 698 699 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**628 +* Downlink Payload (prefix 0xAA): 700 700 701 - (% style="color:#037691" %)**0xAA 00 96** (%%)~/~/630 +0xAA 00 96 ~/~/Set AT+FTIME=150 702 702 703 703 704 704 634 + 705 705 === 3.3.9 Set PDOP value for GPS fix accuracy === 706 706 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. 707 707 708 -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. 709 709 710 - 711 711 A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0 712 712 713 713 714 -* (% style="color:blue" %)**AT Command:**643 +* AT Command: 715 715 716 - (% style="color:#037691" %)**AT+PDOP=2.5** (%%) **~-~->**Set PDOP to 2.5645 +AT+PDOP=2.5 à Set PDOP to 2.5 717 717 718 718 719 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**648 +* Downlink Payload (prefix 0xAD): 720 720 721 - (% style="color:#037691" %)**0xAD 00 0A**(%%)~/~/650 +0xAD 00 0A ~/~/Set AT+PDOP=1 (0x0A / 10 =1) 722 722 723 - (% style="color:#037691" %)**0xAD 00 19**(%%)~/~/652 +0xAD 00 19 ~/~/Set AT+PDOP=2.5 (0x19 / 10 =2.5) 724 724 725 - (% style="color:#037691" %)**0xAD 00 46**(%%)654 +0xAD 00 46 ~/~/Set AT+PDOP=7 (0x46 / 10 =7) 726 726 656 +Disable/Enable the confirmation mode 727 727 658 +* AT Command: 728 728 729 - Disable/Enablethe confirmation mode660 +AT+CFM=xx. 730 730 731 - *(% style="color:blue" %)**AT Command:**662 + Example: 732 732 733 - (%style="color:#037691"%)**AT+CFM=xx.**664 + AT+ CFM=0 à Disable confirmation 734 734 666 + AT+ CFM=1 à Enable confirmation 735 735 736 -**~ Example:** 737 737 738 - AT+ CFM=0**~-~->**Disable confirmation669 +* Downlink Payload (prefix 0x05): 739 739 740 - AT+ CFM=1**~-~->** Enableconfirmation671 +0x05 01 ~/~/ Same as AT+ SMOD =1 741 741 742 742 743 -* (% style="color:blue" %)**Downlink Payload (prefix 0x05):** 744 744 745 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+ SMOD =1 746 746 747 747 748 748 ... ... @@ -755,39 +755,35 @@ 755 755 756 756 == 5.1 Firmware Change Log == 757 757 758 - 759 759 **[[See this link>>url:https://github.com/dragino/TrackerD]]** 760 760 761 761 762 - 763 763 == 5.2 How to upgrade firmware == 764 764 692 +User can use the TrackerD ’s USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below: 765 765 766 -User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below: 767 767 695 +**(% style="color:blue" %)Step1: **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD. 768 768 769 -(% style="color:blue" %) **Step1:ConnectTrackerDand PCvia USB cableshippedwithTrackerD.697 +**(% style="color:blue" %)Step2:** (%%) Install CH9102 driver in the PC. 770 770 771 - 772 -(% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC. 773 - 774 774 After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager. 775 775 776 776 777 -(% 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: 778 778 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]] 779 779 780 -(% style="color:blue" %) **Step4:**706 +**(% style="color:blue" %)Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32 781 781 782 782 783 -[[image: 1664503563660-578.png]]709 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png||alt="image-20220712083115-1.png"]] 784 784 711 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png||alt="image-20220712083115-2.png"]] 785 785 786 -[[image:1664503574618-659.png]] 787 787 714 +**(% style="color:blue" %)Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 788 788 789 -(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 790 - 791 791 [[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 792 792 793 793 ... ... @@ -797,17 +797,16 @@ 797 797 798 798 ESP_LORA-eeprom-class.bin @ 0x10000 799 799 725 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png||alt="image-20220712083115-3.png"]] 800 800 801 - [[image:1664503593459-435.png]]727 +After upgrade finish, it will show finish as below: 802 802 729 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png||alt="image-20220712083115-4.png"]] 803 803 804 804 805 -After upgrade finish, it will show finish as below: 806 806 807 -[[image:1664503611848-385.png]] 808 808 809 809 810 - 811 811 = 6. Developer Guide = 812 812 813 813 ... ... @@ -817,26 +817,28 @@ 817 817 === 6.1.1 Set up ARDUINO compile environment === 818 818 819 819 820 -* **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 821 821 822 - 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]] 823 823 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]] 824 824 825 -[[image: 1664503635019-941.png]]750 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]] 826 826 752 +* Go to tools ~-~-> Boards ~-~-> Boards Manager, find the esp32 information and install it. 827 827 828 - * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find thep32 informationand installt.**754 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]] 829 829 830 -[[image:1664503715811-892.png]] 831 831 757 +* Download the latest TrackerD from the dragino github 832 832 759 +[[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]] 833 833 834 -* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]** 835 835 836 -Put the Library in the TrackerD directory into the libraries file in the Arduino directory :762 +Put the Library in the TrackerD directory into the libraries file in the Arduino directory 837 837 764 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]] 838 838 839 -[[image:1664503752288-974.png]] 840 840 841 841 842 842 ... ... @@ -843,21 +843,21 @@ 843 843 == 6.2 Source Code == 844 844 845 845 846 -* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**772 +* Open the example in the TrackerD file, please select the correct port in the IDE, as shown below: 847 847 848 -[[image: 1664503794261-827.png]]774 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]] 849 849 776 +* Click to upload 850 850 778 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]] 851 851 852 -* (%style="color:blue"%)**Clicktoupload**780 +* Check the result, if the upload is successful, as shown below, open the serial port to view the data 853 853 854 -[[image:1664503808294-336.png]] 855 855 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]] 856 856 857 857 858 -* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 859 859 860 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 861 861 862 862 863 863 ... ... @@ -864,10 +864,11 @@ 864 864 = 7. FAQ = 865 865 866 866 793 + 867 867 == 7.1 How to change the LoRa Frequency Bands/Region? == 868 868 869 869 870 -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. 871 871 872 872 873 873 ... ... @@ -878,8 +878,8 @@ 878 878 879 879 880 880 881 -(% border=" 1.5"cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)882 -| =(% 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** 883 883 |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC 884 884 |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A) 885 885 |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A) ... ... @@ -889,7 +889,6 @@ 889 889 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 890 890 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 891 891 892 - 893 893 = 8. Order Info = 894 894 895 895 ... ... @@ -898,6 +898,7 @@ 898 898 (% style="color:blue" %)**XXX**(%%): The default frequency band 899 899 900 900 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433 827 +* (% style="color:red" %)**CN470**(%%): Default frequency band CN470 901 901 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868 902 902 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865 903 903 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920 ... ... @@ -905,25 +905,33 @@ 905 905 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 906 906 * (% style="color:red" %)**US915**(%%): Default frequency band US915 907 907 835 + 908 908 = 9. Packing Info = 909 909 910 910 911 - (% style="color:#037691" %)**Package Includes**:839 +**Package Includes**: 912 912 913 -* TrackerD LoRaWAN GPS/BLE Tracker x 1 914 -* USB recharge & program cable x 1 841 +* TrackerD x 1 842 +* Rechargeable cable x 1 843 +* Program Cable x 1 915 915 916 - (% style="color:#037691" %)**Dimensions and Weight**:845 +**Dimensions and Weight**: 917 917 918 -* Device Size: 85 x 48 x 15 cm919 -* Weight: 5 0g847 +* Device Size: 85 x 48 x 15 mm/pcs 848 +* Weight: 55g/pcs 920 920 921 -= 10. Support = 922 922 923 923 852 += 10. Support = 853 + 924 924 * 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. 925 -* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].855 +* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to 926 926 857 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]] 858 + 859 + 860 + 861 + 927 927 = 11. Reference = 928 928 929 929 ... ... @@ -930,5 +930,3 @@ 930 930 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 931 931 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 932 932 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 933 - 934 -
- 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
- 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