Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Bei Jinggeng on 2025/08/01 17:45
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 33 added, 0 removed)
- 1665301570342-765.png
- 1665301636888-168.png
- 1665301687277-443.png
- 1665301786397-168.png
- 1667288597595-714.png
- image-20221006181316-1.png
- image-20221006181357-2.png
- image-20221009160220-1.png
- image-20221009160309-2.png
- image-20221009234629-1.png
- image-20221009234703-2.png
- image-20221024105643-1.png
- image-20221024105643-2.png
- image-20221102140621-1.png
- image-20221102140638-2.png
- image-20221102140704-3.png
- image-20221102140712-4.png
- image-20221102140748-5.png
- image-20221102140801-6.png
- image-20221107145243-1.png
- image-20221116111844-1.png
- image-20221116111844-2.png
- image-20221116111844-3.png
- image-20221116111844-4.png
- image-20221116111844-5.png
- image-20221118104359-1.png
- image-20221118105220-2.png
- image-20221118105249-3.png
- image-20221118105402-4.png
- image-20221122100004-1.png
- image-20221122100004-2.png
- image-20221122100004-3.png
- image-20221122100004-4.png
Details
- Page properties
-
- Content
-
... ... @@ -14,7 +14,6 @@ 14 14 15 15 = 1. Introduction = 16 16 17 - 18 18 == 1.1 What is TrackerD == 19 19 20 20 ... ... @@ -25,10 +25,14 @@ 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 27 +((( 28 28 TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution. 29 +))) 29 29 31 +((( 30 30 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. 31 31 ))) 34 +))) 32 32 33 33 ((( 34 34 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. ... ... @@ -42,7 +42,6 @@ 42 42 (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.** 43 43 44 44 45 - 46 46 == 1.2 Specifications == 47 47 48 48 ... ... @@ -94,6 +94,7 @@ 94 94 * Tracking: max: 38mA 95 95 96 96 99 + 97 97 == 1.3 Features == 98 98 99 99 ... ... @@ -100,7 +100,7 @@ 100 100 * LoRaWAN 1.0.3 Class A 101 101 * ESP32 PICO D4 102 102 * SX1276/78 Wireless Chip 103 -* 106 +* Arduino IDE Compatible 104 104 * Open source hardware / software 105 105 * Regular/ Real-time GPS,BLE,WIFI tracking 106 106 * Built-in3 axis accelerometer (LIS3DH) ... ... @@ -112,6 +112,8 @@ 112 112 * Tri-color LED, Alarm button 113 113 * Datalog 114 114 118 + 119 + 115 115 == 1.4 Applications == 116 116 117 117 ... ... @@ -119,8 +119,8 @@ 119 119 * Human tracking 120 120 121 121 122 -= 2.1 Use TrackerD = 123 123 128 += 2. Use TrackerD = 124 124 125 125 == 2.1 How it works? == 126 126 ... ... @@ -128,7 +128,6 @@ 128 128 TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA. 129 129 130 130 131 - 132 132 == 2.2 Quick guide to connect to LoRaWAN server == 133 133 134 134 ... ... @@ -170,109 +170,196 @@ 170 170 **__Add APP KEY and DEV EUI:__** 171 171 172 172 173 -[[image:16 64501784668-703.png]]177 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]] 174 174 175 175 176 176 181 +(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device. 177 177 178 -(% style=" color:blue" %)**Step2**:(%%) Power on TrackerD by usingtheon board switch.183 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]] 179 179 185 +[[image:1664502835802-546.png]] 180 180 187 + 181 181 (% 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. 182 182 183 183 184 - (% style="color:blue"%)**Positioning Mode(SMOD):**191 +== 2.3 Positioning Mode(SMOD) == 185 185 186 -* **(% style="color:#037691" %)GPS ONLY(Factory Settings): **(%%)only get GPS location info. 187 -* **(% style="color:#037691" %)BLE ONLY: **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking. 188 -* **(% style="color:#037691" %)GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking. 189 189 190 -User can s witchmodesby [[changingSMOD>>||anchor="H3.2.7SetPositioningMode"]].194 +Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 191 191 196 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 197 +* (% style="color:#037691" %)**BLE or WiFi ONLY: **(%%)** **Only obtain iBeacon info via BLE and uplink or obtain wifi ssid info via WiFi and uplink. Design for Indoor tracking. 198 +* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking. Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 192 192 200 +Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 193 193 194 -== 2.3 Uplink Payload == 195 195 203 +== 2.4 Uplink Payload == 196 196 197 -=== 2. 3.1 Uplink FPORT~=5, Device Status ===205 +=== 2.4.1 Uplink FPORT~=5, Device Status === 198 198 199 199 208 +Uplink the device configures with FPORT=5. Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours. 200 200 201 - ===2.3.2UplinkFPORT~=, RealtimeGNSS Positioning===210 +Use can also get the Device Status uplink through the downlink command: **Downlink: 0x2301** 202 202 203 203 204 -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. ) 213 +(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %) 214 +|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1 215 +|=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status 205 205 217 +[[image:1665301570342-765.png]] 206 206 207 -(% border="2" style="background-color:#ffffcc; color:green; width:537px" %) 208 -|(% style="width:69px" %)((( 209 -**Size** 210 210 211 -**(bytes)** 212 -)))|(% style="width:76px" %)4|(% style="width:87px" %)4|(% style="width:76px" %)2|(% style="width:52px" %)1|(% style="width:88px" %)((( 213 -2 220 +(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002 214 214 215 -(optional ) 216 -)))|(% style="width:83px" %)((( 217 -2 222 +(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13 218 218 219 -(optional) 224 +(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version 225 + 226 +(% style="color:#037691" %)**Frequency Band**: 227 + 228 +*0x01: EU868 229 + 230 +*0x02: US915 231 + 232 +*0x03: IN865 233 + 234 +*0x04: AU915 235 + 236 +*0x05: KZ865 237 + 238 +*0x06: RU864 239 + 240 +*0x07: AS923 241 + 242 +*0x08: AS923-1 243 + 244 +*0x09: AS923-2 245 + 246 +*0x0a: AS923-3 247 + 248 +Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF) 249 + 250 +(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD. 251 + 252 + 253 +(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV 254 + 255 +Use can also get the Device Status uplink through the downlink command: 256 + 257 + 258 +(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40 259 + 260 +(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %) 261 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit 262 +|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings 263 + 264 +(% style="color:blue" %)** SMOD:** 265 + 266 +(% style="color:red" %)** 1 :** (%%) GPS ONLY 267 + 268 +(% style="color:red" %)** 2 :** (%%) BLE ONLY 269 + 270 +(% style="color:red" %)** 3 :** (%%) GPS/BLE Hybrid 271 + 272 + 273 +(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload** 274 + 275 +(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values 276 + 277 +(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values 278 + 279 + 280 +(% style="color:blue" %)** BLE_Settings:** 281 + 282 +(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 283 + 284 +(% style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%) 285 + 286 + 287 +(% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 288 + 289 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %) 290 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit 291 +|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]] 292 + 293 + 294 + 295 +=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 296 + 297 + 298 +Users can use **AT+SMOD=1,0,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes, 299 + 300 + 301 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %) 302 +|=(% scope="row" style="width: 60px;" %)((( 303 +**Size(bytes)** 304 +)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)((( 305 +2 306 +)))|(% style="width:30px" %)((( 307 +2 220 220 ))) 221 -|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 309 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 222 222 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 311 +)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 223 223 224 - )))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:83px" %)[[Tem>>||anchor="HTem:"]]313 +[[image:1665301636888-168.png]] 225 225 226 226 227 - [[image:1664501958445-288.png]]316 +==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== 228 228 318 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 319 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits 320 +|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 229 229 230 -==== Alarm & BAT: ==== 231 231 232 -(% border="2" style="background-color:#ffffcc; color:green; width:329px" %) 233 -|(% style="width:72px" %)**Size(bit)**|(% style="width:67px" %)1 bit|(% style="width:118px" %)1bit|(% style="width:63px" %)14 bits 234 -|(% style="width:72px" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>path:#BAT]] 235 235 324 +==== (% style="color:blue" %)**FLAG:**(%%) ==== 236 236 237 -==== FLAG: ==== 326 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %) 327 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit 328 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] 238 238 239 -(% border="2" style="background-color:#ffffcc; color:green; width:332px" %) 240 -|(% style="width:79px" %)**Size(bit)**|(% style="width:55px" %)2 bits|(% style="width:47px" %)1bit|(% style="width:140px" %)5 bits 241 -|(% style="width:79px" %)**Value**|(% style="width:55px" %)[[MOD>>path:#MD]]|(% style="width:47px" %)[[LON>>path:#LON]]|(% style="width:140px" %)Firmware version 330 +**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 242 242 243 -**Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A ** 244 244 333 +==== (% style="color:blue" %)**Location info:**(%%) ==== 245 245 246 -==== Location info: ==== 335 +* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976// 336 +* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 247 247 248 -* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976// 249 -* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 338 +(% style="color:red" %)**Important note:** 250 250 251 -**Important note:** 252 - 253 253 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. 254 254 255 -2. In firmwareversionv1.5,Roll&Pitchdisabled bydefault.342 +2. In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below: 256 256 257 -3. 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: 258 258 259 - 260 260 [[image:1664502116362-706.png]] 261 261 262 262 348 +3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 263 263 264 -4. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 265 - 266 266 [[image:1664502166010-515.png]] 267 267 268 268 269 269 270 -* **Alarm**: Example: 0x4B & 0x40 >> 6 = 0x01 271 -* **BAT**: Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV). 354 +==== (% style="color:blue" %)**Alarm:**(%%) ==== 272 272 273 - The battery info shows the current voltage, for**TrackerD** version whichpowered byli-on battery.Usercanusebelowmappingtoindicatethe battery in percentage: \356 +**Example: ** 0x4B & 0x40 >> 6 = 0x01 274 274 275 275 359 +==== (% style="color:blue" %)**BAT:**(%%) ==== 360 + 361 +**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV). 362 + 363 +((( 364 +The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \ 365 +))) 366 + 276 276 * > 4.0v : 80% ~~ 100% 277 277 * 3.85v ~~3.99v: 60% ~~ 80% 278 278 * 3.70v ~~ 3.84v: 40% ~~ 60% ... ... @@ -280,101 +280,173 @@ 280 280 * < 3.39v: 0~~20% 281 281 282 282 283 -==== LON: ==== 374 + 375 +==== (% style="color:blue" %)**MOD:**(%%) ==== 376 + 377 +**Example: ** (0x60>>6) & 0x3f =1 378 + 379 +**Set the format of GPS data uplink link:** 380 + 381 +(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values 382 +(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values 383 + 384 + 385 +**Set the format of BLE data uplink link:** 386 + 387 +(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon 388 + 389 + 390 +==== (% style="color:blue" %)**LON:**(%%) ==== 391 + 392 +**Example:** (0x60>>5) & 0x01=1. 393 + 284 284 Enable/Disable LED activity for uplink 285 285 286 -0x00: Disable LED indicator. 396 +((( 397 +(% style="color:#037691" %)**0x00:** (%%) Disable LED indicator. 398 +))) 287 287 288 -0x01: Enable LED indicator (Default Value) 400 +((( 401 +(% style="color:#037691" %)**0x01:** (%%) Enable LED indicator (Default Value) 402 +))) 289 289 290 290 291 -==== Hum: ==== 405 +==== (% style="color:blue" %)**Hum:**(%%) ==== 292 292 293 293 0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree 294 294 295 295 296 -==== Tem: ==== 410 +==== (% style="color:blue" %)**Tem:**(%%) ==== 297 297 298 -011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree 412 +011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree// 299 299 300 300 415 +=== 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) === 301 301 302 302 303 - ===2.3.3Uplink FPORT~=HistoryGNSSPositioning===418 +The default uplink payload includes total 11 bytes (**AT+SMOD=1,1,0**). The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity) 304 304 305 305 421 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %) 422 +|=(% scope="row" style="width: 60px;" %)((( 423 +**Size(bytes)** 424 +)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1 425 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 426 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 427 +)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 306 306 307 -=== 2.3.4 BLE positioning Payload(Fport2) === 429 +(% class="wikigeneratedid" %) 430 +[[image:1665301687277-443.png]] 308 308 309 309 310 - DifferentMODEhasdifferentpayload:433 +=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 311 311 312 -**MODE=2** 313 313 314 -(% border="2" style="background-color:#ffffcc; color:green; width:620px" %) 315 -|(% style="width:70px" %)((( 316 -**Size** 436 +Set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery. 317 317 318 -**(bytes)** 319 -)))|(% style="width:54px" %)16|(% style="width:72px" %)4|(% style="width:71px" %)4|(% style="width:145px" %)2|(% style="width:72px" %)4|(% style="width:76px" %)2|(% style="width:54px" %)1 320 -|(% style="width:70px" %)**Value**|(% style="width:54px" %)[[UUID>>path:#Location]]|(% style="width:72px" %)((( 321 -iBeacon 322 322 323 -MAJOR 324 -)))|(% style="width:71px" %)((( 325 -iBeacon 439 +(% style="color:red" %)**Note for this mode:** 326 326 327 - MINOR328 -) ))|(%style="width:145px"%)(((329 -i BeaconMeasured441 +* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server. 442 +* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages. 443 +* c) the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes of payload. In this case (DR0 of US915/AU915), the payload on server will show NULL 330 330 331 -Power 332 -)))|(% style="width:72px" %)((( 333 -iBeacon 445 +The payload is 15 bytes, as below. 334 334 335 -RSSI 336 -)))|(% style="width:76px" %)((( 337 -[[Alarm &>>path:#Alarm]] 447 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 448 +|=(% scope="row" %)((( 449 +**Size(bytes)** 450 +)))|4|4|2|1|1|1|1|1 451 +|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 338 338 339 -[[BAT>>path:#Alarm]] 340 -)))|(% style="width:54px" %)[[FLAG>>path:#Flag]] 453 +[[image:image-20221009160309-2.png]] 341 341 455 + 456 +=== 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 457 + 458 + 459 +TrackerD supports BLE scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan BLE iBeacon and find the strongest iBeacon info and uplink. 460 + 461 +User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings. 462 + 463 + 464 +(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 465 +|=(% scope="row" style="width: 60px;" %)((( 466 +**Size(bytes)** 467 +)))|(% style="width:30px" %)16|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:120px" %)2|(% style="width:50px" %)4|(% style="width:50px" %)2|(% style="width:30px" %)1 468 +|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)((( 469 +iBeacon MAJOR 470 +)))|(% style="width:63px" %)((( 471 +iBeacon MINOR 472 +)))|(% style="width:71px" %)((( 473 +iBeacon Measured Power 474 +)))|(% style="width:50px" %)((( 475 +iBeacon RSSI 476 +)))|(% style="width:47px" %)((( 477 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 478 +)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 479 + 342 342 [[image:1664502425687-834.png]] 343 343 344 344 345 -* **BAT** :Ex1:346 -* **MODE: **Define the payload format. 347 -* **UUID: **The uuid from the strongest iBeacon. 348 -* **MAJOR** :The MAJOR from the strongest iBeacon.349 -* **MINOR** :The MAJOR350 -* **Measured ****Power**:The Measured Power from the strongest iBeacon.351 -* **RSSI **: The RSSI from the strongest iBeacon.483 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 484 +* (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 485 +* (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 486 +* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. 487 +* (% style="color:#037691" %)**MINOR:** (%%)The MINOR from the strongest iBeacon. 488 +* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 489 +* (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 352 352 353 353 354 354 493 +=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 355 355 356 -=== 2.3.5 Add Payload format in TTN V3 === 357 357 496 +TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **WiFi** so TrackerD will scan WiFi and find the strongest WiFi info and uplink. 358 358 359 -In TTN V3, use can add a custom payload so it shows friendly. 360 360 361 -In the page Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder 499 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %) 500 +|=(% scope="row" style="width: 60px;" %)((( 501 +**Size(bytes)** 502 +)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1 503 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)((( 504 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 505 +)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 362 362 507 +(% class="wikigeneratedid" %) 508 +[[image:1667288597595-714.png||height="212" width="1151"]] 363 363 510 + 511 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 512 +* (% style="color:#037691" %)**SSID: **(%%)WiFi name. 513 +* (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 514 + 515 + 516 + 517 +=== 2.4.7 Add Payload format in TTN V3 === 518 + 519 + 520 +In TTN V3, user can add a custom payload so it shows friendly. 521 + 522 +In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 523 + 524 + 364 364 [[image:1664502649601-895.png]] 365 365 366 -Add the decoder from this link: 367 367 368 368 529 +Add the decoder from this link: 530 + 531 +[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] 532 + 369 369 Save the change the uplink message will be parsed. As below: 370 370 371 371 [[image:1664502676891-606.png]] 372 372 373 373 538 +== 2.5 Integrate with Datacake == 374 374 375 -== 2.4 Integrate with Datacake == 376 376 377 - 378 378 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. 379 379 380 380 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]] ... ... @@ -383,12 +383,11 @@ 383 383 [[image:1664502695771-538.png]] 384 384 385 385 549 +== 2.6 Integrate with Tago == 386 386 387 -== 2.5 Integrate with Tago == 388 388 552 +After TrackerD sends data to LoRaWAN server such as TTN, user can pass the data to Datacake and plot out, currently only support GPS plot. 389 389 390 -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. 391 - 392 392 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]] 393 393 394 394 ... ... @@ -395,52 +395,75 @@ 395 395 [[image:1664502715371-321.png]] 396 396 397 397 560 +== 2.7 Datalog Feature == 398 398 399 -== 2.6 Alarm Mode == 400 400 563 +total 273 entries,by default, 401 401 402 -User can push the**REDbutton** by more than5seconds to enterAlarm Mode.565 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 403 403 567 +Example use case. 404 404 405 - Once enter Alarm mode, the **GREEN LED** will flash 3 times, the buzzer willalarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioninginformation. After that, the device will send 60packets at1-minute intervals.The Alarm flag inthepayload will be set for the next60 packets unless exit alert mode.569 +[[image:image-20221009234703-2.png||height="328" width="899"]] 406 406 407 407 408 - Two ways toexitalarm mode:572 +[[image:image-20221009234629-1.png||height="390" width="577"]] 409 409 410 -* Server send a downlink command to exit. 574 + 575 +== 2.8 Alarm Mode == 576 + 577 + 578 +((( 579 +User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 580 +))) 581 + 582 + 583 +((( 584 +Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exits alert mode. 585 +))) 586 + 587 + 588 +((( 589 +**Two ways to exit alarm mode:** 590 +))) 591 + 592 +* Server sends a downlink command to exit. 411 411 * User fast press the RED button 10 times. 412 412 413 -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. 595 +((( 596 +When exit alarm mode, (% style="color:red" %)**RED LED**(%%) will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false. 597 +))) 414 414 415 415 600 +== 2.9 Transport Mode == 416 416 417 -== 2.7 Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- == 418 418 603 +In Transport Mode, TrackerD will check if there is motion. If there is no motion, device will send uplinks every 20 minutes. If there is motion, device will send uplink every 5 minutes. 419 419 420 420 421 -== 2. 8LED Status ==606 +== 2.10 LED Status == 422 422 423 423 424 -(% border=" 2" style="background-color:#ffffcc;color:green;width:636px" %)425 -|(% style="width:15 7px" %)**Event**|(% style="width:271px" %)**Action**|(% style="width:202px" %)**AT+LON to control on/off**426 -|(% style="width:157px" %)**Power On**|(% style="width:271px" %)**BLUE, RED , Green** 427 -|(% style="width:157px" %)**Join request**|(% style="width:271px" %)**Green** led fast blink once (200ms)|(% style="width:202px" %)Yes 428 -|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)**Green** led on 5 second|(% style="width:202px" %)N/A 429 -|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)**BLUE **blinks 200ms per second|(% style="width:202px" %)Yes 430 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)**GREEN **blinks twice (200ms per blink)|(% style="width:202px" %)Yes 431 -|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)**RED **blinks twice (200ms per blink)|(% style="width:202px" %)Yes 432 -|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)**RED **on for 3 seconds|(% style="width:202px" %)Yes 433 -|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)**RED **on for 1 second|(% style="width:202px" %)Yes 434 -|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)**BLUE **led on 5 second|(% style="width:202px" %)Yes 435 -|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)**GREEN** led on 1 second|(% style="width:202px" %)Yes 436 -|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)**RED **on 500ms|(% style="width:202px" %)N/A 609 +(% border="1.5" style="background-color:#ffffcc; width:500px" %) 610 +|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 611 +|(% style="width:157px" %)**Power On**|(% style="width:271px" %)(% style="color:blue" %)**BLUE, **(% style="color:red" %)**RED , **(% style="color:green" %)**Green** flash once|(% style="width:202px" %)N/A 612 +|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes 613 +|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A 614 +|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes 615 +|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes 616 +|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes 617 +|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes 618 +|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes 619 +|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes 620 +|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 621 +|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 437 437 438 438 439 439 440 -== 2. 9Button Function ==625 +== 2.11 Button Function == 441 441 442 442 443 -**RESET button:** 628 +(% style="color:blue" %)**RESET button:** 444 444 445 445 [[image:1664502835802-546.png]] 446 446 ... ... @@ -447,27 +447,28 @@ 447 447 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server. 448 448 449 449 450 -**RED button:** 635 +(% style="color:red" %)**RED button:** 451 451 452 452 [[image:1664502854406-763.png]] 453 453 454 454 455 -(% border=" 2" style="background-color:#ffffcc;color:green;width:627px" %)456 -|(% style="width:1 35px" %)**Function**|(% style="width:220px" %)**Action**|(% style="width:265px" %)**Description**457 -|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing **RED** button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode. See [[Alarm Mode>> path:#Alarm_Mode]]458 -|(% style="width:135px" %)Exit Alarm Mode|(% style="width:220px" %)Fast press the **RED** button 10 times|(% style="width:265px" %)Exit Alarm Mode 640 +(% border="1" style="background-color:#ffffcc; width:510px" %) 641 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description** 642 +|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode. See [[Alarm Mode>>||anchor="H2.8AlarmMode"]] 643 +|(% style="width:135px" %)Exit Alarm Mode|(% style="width:220px" %)Fast press the (% style="color:red" %)**RED** (%%)button 10 times|(% style="width:265px" %)Exit Alarm Mode 459 459 |(% 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. 460 460 461 461 462 -== 2.10 USB Port Function == 463 463 648 +== 2.12 USB Port Function == 464 464 650 + 465 465 The USB interface of TrackerD has below functions: 466 466 467 467 * Power on the device 468 468 * Recharge the battery 469 -* [[Configure Device>> path:#AT_Command]]470 -* [[Upgrade Firmware>> path:#upgrade_image]]655 +* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 656 +* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 471 471 472 472 473 473 ... ... @@ -476,10 +476,9 @@ 476 476 477 477 User can configure TrackerD via AT Command or LoRaWAN Downlink. 478 478 479 -LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>> url:http://wiki.dragino.com/xwiki/bin/view/Main/]]665 +LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] 480 480 481 481 482 - 483 483 == 3.1 Access AT Command == 484 484 485 485 ... ... @@ -489,17 +489,15 @@ 489 489 [[image:1664502999401-486.png]] 490 490 491 491 492 -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: 677 +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: 493 493 494 494 495 495 [[image:1664503022490-662.png]] 496 496 497 497 498 - 499 499 [[image:1664503035713-500.png]] 500 500 501 501 502 - 503 503 [[image:1664503047675-651.png]] 504 504 505 505 ... ... @@ -506,148 +506,149 @@ 506 506 507 507 == 3.2 Command Set == 508 508 509 - 510 510 === 3.2.1 Set Transmit Interval === 511 511 512 512 513 513 Set device uplink interval. 514 514 515 -* AT Command: 697 +* (% style="color:blue" %)**AT Command:** 516 516 517 -AT+TDC=xxx 699 +(% style="color:#037691" %)**AT+TDC=xxx ** 518 518 519 519 Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds) 520 520 521 521 522 -* Downlink Payload (prefix 0x01): 704 +* (% style="color:blue" %)**Downlink Payload (prefix 0x01):** 523 523 524 -0x01 00 01 2C 706 +(% style="color:#037691" %)**0x01 00 01 2C** (%%) ~/~/ Same as AT+TDC=300000 525 525 526 526 527 - 528 528 === 3.2.2 Set Alarm Packet transmission interval === 529 529 530 530 531 531 Set alarm packet transmit interval 532 532 533 -* AT Command: 714 +* (% style="color:blue" %)**AT Command:** 534 534 535 -AT+ATDC=xx. 716 +(% style="color:#037691" %)**AT+ATDC=xx. ** 536 536 537 537 Example: AT+ATDC=60000 **~-~-> ** Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000 538 538 539 539 540 -* Downlink Payload (prefix 0xB1): 721 +* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):** 541 541 542 -0xB1 00 00 3C 723 +(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/ Same as AT+ATDC=60000 543 543 544 544 726 +=== 3.2.3 Set Transport Mode Packet transmission interval === 545 545 546 -=== 3.2.3 Set Sports Mode Packet transmission interval === 547 547 729 +Set Transport Mode packet transmit interval 548 548 549 - Setsports packettransmitinterval731 +* (% style="color:blue" %)**AT Command:** 550 550 551 - *ATommand:733 +(% style="color:#037691" %)**AT+MTDC=xx. ** 552 552 553 -AT+MTDC= xx.735 +Example: AT+MTDC=300000 **~-~-> ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000 554 554 555 - Example: AT+MTDC=300000 **~-~-> ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000 556 556 738 +* (% style="color:blue" %)**Downlink Payload (prefix 0x03):** 557 557 558 - *Downlink Payload (prefix0x03):740 +(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+MTDC=3000000 559 559 560 -0x03 00 01 2C ~/~/ Same as AT+ MTDC=3000000 561 561 562 - 563 - 564 564 === 3.2.4 Exit Alarm === 565 565 566 566 567 567 Server send downlink command to exit Alarm mode 568 568 569 -* AT Command: 748 +* (% style="color:blue" %)**AT Command: No AT Command** 570 570 571 - NoATCommand750 +* (% style="color:blue" %)**Downlink Payload (prefix 0x02):** 572 572 752 +(% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 573 573 574 -* Downlink Payload (prefix 0x02): 575 575 576 -0x02 01 ~/~/ Exit Alarm Mode 577 - 578 - 579 - 580 580 === 3.2.5 Disable/Enable LED flash === 581 581 582 582 583 583 Disable/Enable LED for position, downlink and uplink 584 584 585 -* AT Command: 760 +* (% style="color:blue" %)**AT Command:** 586 586 587 -AT+LON=xx. (Disable (0), Enable (1), default:1) 762 +(% style="color:#037691" %)**AT+LON=xx. (Disable (0), Enable (1), default:1)** 588 588 589 - 764 +Example: AT+LON=0 **~-~-> ** Disable LED for position, downlink and uplink. 590 590 591 591 592 -* Downlink Payload (prefix 0xAE): 767 +* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):** 593 593 594 -0xAE 00 769 +(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/ Same as AT+LON=0 595 595 596 596 772 +=== 3.2.6 Disable/Enable Transport Mode === 597 597 598 -=== 3.2.6 Disable/Enable movement detect (Debug Only) === 599 599 775 +Users can use this feature to enable/disable Transport Mode. 600 600 601 - Usercanusethis feature tocheck and set thread holeofmovementdetect777 +* (% style="color:blue" %)**AT Command:** 602 602 603 - *ATCommand:779 +(% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)** 604 604 605 -AT+INTWK= xx.(Disable(0),Enable(1),default:0)781 +Example: AT+INTWK=1 **~-~-> ** Enable Transport Mode. 606 606 607 - Example: AT+ INTWK =1 **~-~-> ** Enable detect movement. 608 608 784 +* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):** 609 609 610 - *Downlink Payload (prefix0xAF):786 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+INTWK=1 611 611 612 -0xAF 01 ~/~/ Same as AT+ INTWK =1 613 613 789 +=== 3.2.7 Set Positioning Mode === 614 614 615 615 616 - ===3.2.7SetPositioningMode ===792 +SMOD define how TrackerD scan and uplink data: 617 617 618 618 619 - SMODdefinethehow TrackerDscananduplink date.795 +* (% style="color:blue" %)**AT Command:** 620 620 621 - GPS室外定位模式:设备默认模式,设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是3分钟定位,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。GPS还有一种logdata模式,在断网的情况下将数据存储下来,等到有网的时候,一次将数据以每10秒上报。797 +(% style="color:#037691" %)**AT+SMOD=aa,bb,cc** 622 622 623 - BLE室内定位模式:设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是5秒,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每3分钟发送一次)。799 +(% style="color:#037691" %)** aa:** 624 624 625 -GPS 和BLE混动模式:设备入网后会发送device当前模式下的信息,随后立即判断是否在室内,如果是就进行BLE定位,不是就GPS定位。如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。801 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 626 626 627 - 运动模式:设备入网后会发送device当前模式下的信息,随后发送GPS定位数据,设备判断是否在运动,没有运动传感器没有检测到动作,立即进入静止状态(默认20分钟),如果产生运动,将每5分钟发送一次数据,再第五分钟后检测设备有误运动,无将切换到静止状态,有立即发送数据。803 +* (% style="color:red" %)**2: BLE or WiFi ONLY: **(%%)Only obtain iBeacon info via BLE and uplink or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking. 628 628 805 +* (% style="color:red" %)**3: GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 629 629 807 +(% style="color:#037691" %)**bb:** 630 630 631 -* AT Command:809 +* (% style="color:red" %)**0 : **(%%)GPS+ BAT+ State+Tem&Hum 632 632 633 -AT +SMOD=xx.811 +* (% style="color:red" %)**1 :**(%%) GPS +BAT State 634 634 813 +(% style="color:#037691" %)**cc: ** 635 635 636 - **Example:** 815 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 816 + 817 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%)) 637 637 638 - AT+ SMOD=1,0~-~-> ** GPS+ BAT+ State+Tem&Hum819 +(% style="color:blue" %)**Example:** 639 639 640 - AT+ 1**~-~->**GPS821 + AT+SMOD=1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 641 641 642 - AT+ 2,3**~-~->**(iBeacon)UUID+Major+Minor+Power+Rssi+BAT+State。823 + AT+SMOD=1,1,0 ~-~-> GPS +BAT State 643 643 825 + AT+SMOD=2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 644 644 645 - *DownlinkPayload(prefix 0xA5):827 + AT+SMOD=2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State 646 646 647 -0xA5 01 00 ~/~/ Same as AT+ SMOD =1,0 648 648 830 +* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** 649 649 832 +(% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+SMOD=1,0,0 650 650 834 + 651 651 === 3.2.8 Set MAX GPS position time === 652 652 653 653 ... ... @@ -654,25 +654,24 @@ 654 654 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. 655 655 656 656 657 -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. 841 +If **AT+FTIME=0**. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink. 658 658 659 659 660 -* AT Command: 844 +* (% style="color:blue" %)**AT Command:** 661 661 662 -AT+FTIME=xx **~-~-> ** Set to use xx as max fix time. 846 +(% style="color:#037691" %)**AT+FTIME=xx** (%%) **~-~-> ** Set to use xx as max fix time. 663 663 664 -Example: AT+FTIME=150 848 +**Example:** AT+FTIME=150 665 665 666 666 667 -* Downlink Payload (prefix 0xAA): 851 +* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):** 668 668 669 -0xAA 00 96 853 +(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/ Set AT+FTIME=150 670 670 671 671 856 +=== 3.2.9 Set PDOP value for GPS fix accuracy === 672 672 673 -=== 3.3.9 Set PDOP value for GPS fix accuracy === 674 674 675 - 676 676 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. 677 677 678 678 ... ... @@ -679,40 +679,123 @@ 679 679 A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0 680 680 681 681 682 -* AT Command: 865 +* (% style="color:blue" %)**AT Command:** 683 683 684 -AT+PDOP=2.5 867 +(% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~-> ** Set PDOP to 2.5 685 685 686 686 687 -* Downlink Payload (prefix 0xAD): 870 +* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):** 688 688 689 -0xAD 00 0A 872 +(% style="color:#037691" %)**0xAD 00 0A** (%%) ~/~/ Set AT+PDOP=1 (0x0A / 10 =1) 690 690 691 -0xAD 00 19 874 +(% style="color:#037691" %)**0xAD 00 19** (%%) ~/~/ Set AT+PDOP=2.5 (0x19 / 10 =2.5) 692 692 693 -0xAD 00 46 876 +(% style="color:#037691" %)**0xAD 00 46** (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7) 694 694 695 695 696 -Disable/Enable the confirmation mode 697 697 698 -* ATCommand:880 +**Disable/Enable the confirmation mode** 699 699 700 -AT +CFM=xx.882 +* (% style="color:blue" %)**AT Command:** 701 701 884 +(% style="color:#037691" %)**AT+CFM=xx** 702 702 886 + 703 703 **~ Example:** 704 704 705 - AT+ 889 + AT+CFM=0 **~-~-> ** Disable confirmation 706 706 707 - AT+ 891 + AT+CFM=1 **~-~-> ** Enable confirmation 708 708 709 709 710 -* Downlink Payload (prefix 0x05): 894 +* (% style="color:blue" %)**Downlink Payload (prefix 0x05):** 711 711 712 -0x05 01 SMOD=1896 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1 713 713 714 714 899 +=== 3.2.10 Auto Send None-ACK messages === 715 715 901 + 902 +TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message. 903 + 904 + 905 +* (% style="color:blue" %)**AT Command: AT+PNACKMD** 906 + 907 +The default factory setting is 0. 908 + 909 + 910 +**Command Example Function Response:** 911 + 912 +(% style="color:#037691" %)**AT+PNACKMD=1** (%%) ~/~/ Poll None-ACK message OK 913 + 914 + 915 +* (% style="color:blue" %)**Downlink Command: 0x34** 916 + 917 +Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 918 + 919 + 920 +=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 921 + 922 + 923 +BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID. 924 + 925 +(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.** 926 + 927 +(% style="color:blue" %)**AT Command:** 928 + 929 + (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 930 + 931 + (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 932 + 933 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 934 + 935 +Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 936 + 937 + 938 +=== 3.2.12 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 939 + 940 + 941 +WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456 as prefix. It will ignore all other WiFi which doesn’t contact 123456 in the SSID. 942 + 943 +(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.** 944 + 945 +(% style="color:blue" %)**AT Command:** 946 + 947 + (% style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456 948 + 949 + (% style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK 950 + 951 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)** 952 + 953 +Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 954 + 955 + 956 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 957 + 958 + 959 +Users can use this feature to enable/disable Information printing. 960 + 961 +(% style="color:blue" %)**AT Command:** 962 + 963 +(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/(Disable (0), Enable (1), default:0) 964 +\\Example: AT+SHOWID=1 ~-~-> Enable Information printing. 965 + 966 + 967 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 968 + 969 + 970 +The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. 971 + 972 +(% style="color:blue" %)**AT Command:** 973 + 974 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode 975 + 976 + 977 +(% style="color:blue" %)**Downlink Payload:0X24** 978 + 979 +Example: 0x24 01 ~/~/ Same as AT+CHE=1 980 + 981 + 716 716 = 4. Setting for Different Scenarios = 717 717 718 718 ... ... @@ -719,7 +719,6 @@ 719 719 720 720 = 5. Upload Firmware = 721 721 722 - 723 723 == 5.1 Firmware Change Log == 724 724 725 725 ... ... @@ -726,7 +726,6 @@ 726 726 **[[See this link>>url:https://github.com/dragino/TrackerD]]** 727 727 728 728 729 - 730 730 == 5.2 How to upgrade firmware == 731 731 732 732 ... ... @@ -741,11 +741,9 @@ 741 741 After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager. 742 742 743 743 744 -(% style="color:blue" %)**Step3 :**(%%)1008 +(% style="color:blue" %)**Step3: **(%%)Download and Install Flash Tool: [[https:~~/~~/www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools]] 745 745 746 -[[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]] 747 747 748 - 749 749 (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32 750 750 751 751 ... ... @@ -755,54 +755,64 @@ 755 755 [[image:1664503574618-659.png]] 756 756 757 757 1020 + 758 758 (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 759 759 760 -[[https:~~/~~/ www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]1023 +[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]] 761 761 762 762 763 -Users need to use below files: 1026 +**Users need to use below files:** 764 764 765 765 boot_app0.bin @0e000 766 766 767 - ESP_LORA-eeprom-class.bin @ 0x100001030 +US915.bin @ 0x10000(Select the bin file of the frequency band you need) 768 768 769 769 770 -[[image:1 664503593459-435.png]]1033 +[[image:image-20221118105220-2.png]] 771 771 772 772 773 773 774 774 After upgrade finish, it will show finish as below: 775 775 776 -[[image: 1664503611848-385.png]]1039 +[[image:image-20221118105402-4.png]] 777 777 778 778 779 779 780 780 = 6. Developer Guide = 781 781 782 - 783 783 == 6.1 Compile Source Code == 784 784 785 - 786 786 === 6.1.1 Set up ARDUINO compile environment === 787 787 788 788 789 -* 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]] 1050 +* **Download the latest Arduino software (IDE) from the Arduino official website: [[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]]** 790 790 791 -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]] 1052 +Install IDE on PC, open and click (% style="color:#037691" %)**File ~-~-> Preference**,(%%) add the following URL: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fdl.espressif.com%2Fdl%2Fpackage_esp32_index.json]] 792 792 793 793 794 794 [[image:1664503635019-941.png]] 795 795 796 796 797 -* Go to tools ~-~-> Boards ~-~-> Boards Manager, find the esp32 information and install it. 798 798 1059 +* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 799 799 800 800 [[image:1664503715811-892.png]] 801 801 802 802 1064 +(% id="cke_bm_4554S" style="display:none" %) (%%)Find the path of SP32 installation, find the file as shown in Figure 1, and change the SPI pin to the shown in Figure 2. 803 803 804 - * Download the latest TrackerD from the dragino github:[[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]1066 +[[image:image-20221024105643-1.png]] 805 805 1068 +**~ Figure1** 1069 + 1070 + 1071 +[[image:image-20221024105643-2.png]] 1072 + 1073 + **Figure2** 1074 + 1075 + 1076 +* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]** 1077 + 806 806 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: 807 807 808 808 ... ... @@ -809,38 +809,34 @@ 809 809 [[image:1664503752288-974.png]] 810 810 811 811 812 - 813 813 == 6.2 Source Code == 814 814 815 815 816 -* Open the example in the TrackerD file, please select the correct port in the IDE, as shown below: 1087 +* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:** 817 817 818 818 [[image:1664503794261-827.png]] 819 819 820 820 821 821 822 -* Click to upload 1093 +* (% style="color:blue" %)**Click to upload** 823 823 824 824 [[image:1664503808294-336.png]] 825 825 826 826 827 827 828 -* Check the result, if the upload is successful, as shown below, open the serial port to view the data 1099 +* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 829 829 830 830 [[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 831 831 832 832 833 - 834 834 = 7. FAQ = 835 835 836 - 837 837 == 7.1 How to change the LoRa Frequency Bands/Region? == 838 838 839 839 840 -User can follow the introduction for [[how to upgrade image>> path:#upgrade_image]]. When download the images, choose the required image file for download.1109 +User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download. 841 841 842 842 843 - 844 844 == 7.2 What is the pin mapping for the USB program cable? == 845 845 846 846 ... ... @@ -848,8 +848,8 @@ 848 848 849 849 850 850 851 -(% border=" 2" style="background-color:#ffffcc; color:green; width:314px" %)852 -|(% style="width:118px" %)**Pin**|(% style="width:67px" %)**Color**|(% style="width:123px" %)**USB Pin** 1119 +(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %) 1120 +|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin** 853 853 |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC 854 854 |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A) 855 855 |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A) ... ... @@ -861,51 +861,243 @@ 861 861 862 862 863 863 1132 +== 7.3 Notes on using different serial port tools for TrackerD == 864 864 865 -= 8.OrderInfo =1134 +=== 7.3.1 Serial port utility === 866 866 867 867 1137 +Serial port utility requires you to automatically add data streams. 1138 + 1139 +Need to adjust the data stream to RTS/CTS on physical restart. 1140 + 1141 +(% class="wikigeneratedid" %) 1142 +[[image:image-20221102140621-1.png]] 1143 + 1144 + 1145 + 1146 +When using AT commands, the data flow needs to be adjusted to XON/XOFF 1147 + 1148 +[[image:image-20221102140638-2.png]] 1149 + 1150 + 1151 +=== 7.3.2 SecureCRT === 1152 + 1153 + 1154 +The default command window of SecureCRT is not displayed. Entering a command requires a complete input of the entire command. You can open the command window in the view. 1155 + 1156 + 1157 +[[image:image-20221102140704-3.png]] 1158 + 1159 + 1160 +[[image:image-20221102140712-4.png]] 1161 + 1162 + 1163 +=== 7.3.3 PUTTY === 1164 + 1165 + 1166 +[[image:image-20221102140748-5.png]] 1167 + 1168 + 1169 +Since putty does not have a command window, you need to fill in the complete command externally, and then copy it to putty.The information copied outside can be pasted by right-clicking the mouse in putty. 1170 + 1171 + 1172 +[[image:image-20221102140801-6.png]] 1173 + 1174 + 1175 +== 7.4 How to modify source code to compile different frequency band bin file? == 1176 + 1177 + 1178 +(% class="box infomessage" %) 1179 +((( 1180 +(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings. 1181 +See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]] 1182 +))) 1183 + 1184 +**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.** 1185 + 1186 + 1187 +[[image:image-20221116111844-1.png||height="227" width="782"]] 1188 + 1189 + 1190 + 1191 +**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).** 1192 + 1193 + 1194 +[[image:image-20221116111844-2.png||height="262" width="781"]] 1195 + 1196 + 1197 + 1198 +**3. Compile the AS923_JP band, please refer to the intention shown** 1199 + 1200 + 1201 +[[image:image-20221116111844-3.png||height="338" width="746"]] 1202 + 1203 + 1204 + 1205 +**4. In other frequency bands in AS923, you need to find Lorabase_as923.H, path arduino-lmic \ src \ lmic, as shown in the figure below.** 1206 + 1207 + 1208 +[[image:image-20221116111844-4.png||height="641" width="739"]] 1209 + 1210 + 1211 +[[image:image-20221116111844-5.png||height="551" width="708"]] 1212 + 1213 + 1214 += 8 Trouble Shooting = 1215 + 1216 +== 8.1 TDC is changed to 4294947296 and cause no uplink. == 1217 + 1218 + 1219 +((( 1220 +Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1 1221 +))) 1222 + 1223 + 1224 +== 8.2 Device not able get AT Command or show output after wake up from deep sleep mode == 1225 + 1226 + 1227 +((( 1228 +ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode. 1229 +))) 1230 + 1231 + 1232 +== 8.3 Problem after Upgrading Firmware == 1233 + 1234 +=== 8.3.1 Continue Restart after upgrading === 1235 + 1236 + 1237 +((( 1238 +If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure 1239 +))) 1240 + 1241 + 1242 +[[image:image-20221118105249-3.png]] 1243 + 1244 + 1245 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading === 1246 + 1247 + 1248 +It is because the partitions are different when upgrading versions above 1.4.1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 1249 + 1250 + 1251 + 1252 +==== 8.3.2.1 If there is a situation in Figure 1,and a new partition file and bootloader file needs to be added. Please refer to the operation steps in Figure 2 ==== 1253 + 1254 + 1255 +[[image:image-20221122100004-1.png||height="497" width="534"]] 1256 + 1257 + ** Figure 1 ** 1258 + 1259 + 1260 + [[image:image-20221122100004-2.png||height="619" width="389"]] 1261 + 1262 + **Figure 2** 1263 + 1264 + 1265 + 1266 +After the upgrade is completed, enter AT+CFG as shown in the figure below. 1267 + 1268 + 1269 +[[image:image-20221122100004-3.png]] 1270 + 1271 +Please AT+FDR, and then enter the following instructions by the information on the label 1272 + 1273 +AT+DEUI=70B3D57ED0053981 1274 + 1275 +AT+APPEUI=D23345667BCBCCAF 1276 + 1277 +AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1 1278 + 1279 +AT+DADDR=260b4dce 1280 + 1281 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d 1282 + 1283 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 1284 + 1285 + 1286 + 1287 +==== 8.3.2.2 If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ==== 1288 + 1289 + 1290 +[[image:image-20221122100004-4.png]] 1291 + 1292 + 1293 +== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1294 + 1295 + 1296 +Please download version 1.4.2 again 1297 + 1298 + 1299 +== 8.5 How to deal with unsuccessful GPS positioning? == 1300 + 1301 + 1302 +1) Make Sure the device is in Open Area where can see the sky. 1303 + 1304 +2) Set PDOP to a higher value. 1305 + 1306 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.) 1307 + 1308 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces) 1309 + 1310 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments) 1311 + 1312 +Please refer to this [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H3.2.9SetPDOPvalueforGPSfixaccuracy]] on how to set up PDOP 1313 + 1314 + 1315 += 9. Order Info = 1316 + 1317 + 868 868 Part Number: (% style="color:blue" %)**TrackerD-XXX** 869 869 870 870 (% style="color:blue" %)**XXX**(%%): The default frequency band 871 871 872 872 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433 1323 + 873 873 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868 1325 + 874 874 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865 1327 + 875 875 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920 1329 + 876 876 * (% style="color:red" %)**AS923**(%%): Default frequency band AS923 1331 + 877 877 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 1333 + 878 878 * (% style="color:red" %)**US915**(%%): Default frequency band US915 879 879 880 880 881 881 1338 += 10. Packing Info = 882 882 883 -= 9. Packing Info = 884 884 1341 +(% style="color:#037691" %)**Package Includes**: 885 885 886 -**Package Includes**: 887 - 888 888 * TrackerD LoRaWAN GPS/BLE Tracker x 1 1344 + 889 889 * USB recharge & program cable x 1 890 890 891 -**Dimensions and Weight**: 1347 +(% style="color:#037691" %)**Dimensions and Weight**: 892 892 893 -* Device Size: 85 x 48 x 15 cm 1349 +* Device Size: 85 x 48 x 15 mm 1350 + 894 894 * Weight: 50g 895 895 896 896 897 897 898 -= 1 0. Support =1355 += 11. Support = 899 899 900 900 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]] 903 903 1360 +* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]. 904 904 905 905 906 -= 11. Reference = 907 907 1364 += 12. Reference = 908 908 1366 + 909 909 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1368 + 910 910 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1370 + 911 911 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
- 1665301570342-765.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +31.6 KB - Content
- 1665301636888-168.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +36.6 KB - Content
- 1665301687277-443.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +22.6 KB - Content
- 1665301786397-168.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +22.6 KB - Content
- 1667288597595-714.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +27.9 KB - Content
- image-20221006181316-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +17.7 KB - Content
- image-20221006181357-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +88.0 KB - Content
- image-20221009160220-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +46.4 KB - Content
- image-20221009160309-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +57.2 KB - Content
- image-20221009234629-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +222.9 KB - Content
- image-20221009234703-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +136.4 KB - Content
- image-20221024105643-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +11.3 KB - Content
- image-20221024105643-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +64.5 KB - Content
- image-20221102140621-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +46.1 KB - Content
- image-20221102140638-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +40.8 KB - Content
- image-20221102140704-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +15.5 KB - Content
- image-20221102140712-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +73.2 KB - Content
- image-20221102140748-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +56.0 KB - Content
- image-20221102140801-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +21.0 KB - Content
- image-20221107145243-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +107.3 KB - Content
- image-20221116111844-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +15.8 KB - Content
- image-20221116111844-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +32.6 KB - Content
- image-20221116111844-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +37.0 KB - Content
- image-20221116111844-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +96.8 KB - Content
- image-20221116111844-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +78.0 KB - Content
- image-20221118104359-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +38.0 KB - Content
- image-20221118105220-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +40.2 KB - Content
- image-20221118105249-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +40.2 KB - Content
- image-20221118105402-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +43.7 KB - Content
- image-20221122100004-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +18.0 KB - Content
- image-20221122100004-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +127.2 KB - Content
- image-20221122100004-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +12.5 KB - Content
- image-20221122100004-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +22.3 KB - Content