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, 52 added, 0 removed)
- 1664501652064-326.png
- 1664501677253-891.png
- 1664501711466-918.png
- 1664501721248-725.png
- 1664501734705-405.png
- 1664501784668-703.png
- 1664501958445-288.png
- 1664502116362-706.png
- 1664502166010-515.png
- 1664502425687-834.png
- 1664502649601-895.png
- 1664502676891-606.png
- 1664502695771-538.png
- 1664502715371-321.png
- 1664502835802-546.png
- 1664502854406-763.png
- 1664502999401-486.png
- 1664503022490-662.png
- 1664503035713-500.png
- 1664503047675-651.png
- 1664503563660-578.png
- 1664503574618-659.png
- 1664503593459-435.png
- 1664503611848-385.png
- 1664503635019-941.png
- 1664503715811-892.png
- 1664503752288-974.png
- 1664503794261-827.png
- 1664503808294-336.png
- 1664503824081-592.png
- 1664503831430-500.png
- 1664505654417-133.png
- 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
Details
- Page properties
-
- Content
-
... ... @@ -1,6 +1,13 @@ 1 +(% style="text-align:center" %) 2 +[[image:1664505654417-133.png]] 3 + 4 + 5 + 6 + 1 1 (% class="wikigeneratedid" %) 2 2 **Table of Contents:** 3 3 10 +{{toc/}} 4 4 5 5 6 6 ... ... @@ -7,9 +7,10 @@ 7 7 8 8 = 1. Introduction = 9 9 10 -== 1.1 OverView == 11 11 18 +== 1.1 What is TrackerD == 12 12 20 + 13 13 ((( 14 14 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**. 15 15 ))) ... ... @@ -17,10 +17,14 @@ 17 17 ((( 18 18 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. 19 19 28 +((( 20 20 TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution. 30 +))) 21 21 32 +((( 22 22 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. 23 23 ))) 35 +))) 24 24 25 25 ((( 26 26 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. ... ... @@ -34,6 +34,7 @@ 34 34 (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.** 35 35 36 36 49 + 37 37 == 1.2 Specifications == 38 38 39 39 ... ... @@ -48,13 +48,11 @@ 48 48 * EEPROM: 520 KB 49 49 * Clock Speed: 32Mhz 50 50 51 - 52 52 (% style="color:blue" %)**Common DC Characteristics:** 53 53 54 54 * Supply Voltage: 5V via USB port or Internal li-on battery 55 55 * Operating Temperature: -40 ~~ 60°C 56 56 57 - 58 58 (% style="color:blue" %)**LoRa Spec:** 59 59 60 60 * Frequency Range, ... ... @@ -76,12 +76,10 @@ 76 76 * Packet engine up to 256 bytes with CRC. 77 77 * LoRaWAN 1.0.3 Specification 78 78 79 - 80 80 (% style="color:blue" %)**Battery:** 81 81 82 82 * 1000mA Li-on Battery power (for model TrackerD) 83 83 84 - 85 85 (% style="color:blue" %)**Power Consumption** 86 86 87 87 * Sleeping Mode: 200uA ... ... @@ -90,7 +90,6 @@ 90 90 91 91 92 92 93 - 94 94 == 1.3 Features == 95 95 96 96 ... ... @@ -97,7 +97,7 @@ 97 97 * LoRaWAN 1.0.3 Class A 98 98 * ESP32 PICO D4 99 99 * SX1276/78 Wireless Chip 100 -* 108 +* Arduino IDE Compatible 101 101 * Open source hardware / software 102 102 * Regular/ Real-time GPS,BLE,WIFI tracking 103 103 * Built-in3 axis accelerometer (LIS3DH) ... ... @@ -119,534 +119,734 @@ 119 119 120 120 121 121 130 += 2. Use TrackerD = 122 122 123 -1. Use TrackerD 124 -11. How it works? 125 125 133 +== 2.1 How it works? == 126 126 135 + 127 127 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. 128 128 129 129 130 -1. 131 -11. Quick guide to connect to LoRaWAN server 132 132 133 - Hereisanexample for how to jointhe[[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]].Below isthe networkstructure, we useLPS8N as LoRaWANgateway in thisxample.140 +== 2.2 Quick guide to connect to LoRaWAN server == 134 134 135 135 136 - [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]143 +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. 137 137 138 138 146 +[[image:1664501652064-326.png]] 147 + 148 + 149 + 139 139 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: 140 140 141 -**Step 1**: Create a device in TTN V3 with the OTAA keys from TrackerD. 142 142 153 +(% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD. 154 + 143 143 Each TrackerD is shipped with a sticker with the default device EUI as below: 144 144 145 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]] 146 146 158 +[[image:1664501677253-891.png]] 147 147 148 148 149 - 150 150 Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot: 151 151 152 152 153 -Add APP EUI in the application 164 +**__Add APP EUI in the application:__** 154 154 155 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]] 156 156 157 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]]167 +[[image:1664501711466-918.png]] 158 158 159 159 160 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]] 161 161 171 +[[image:1664501721248-725.png]] 162 162 163 163 164 - Add APP KEYand DEV EUI174 +[[image:1664501734705-405.png]] 165 165 166 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]] 167 167 168 168 178 +**__Add APP KEY and DEV EUI:__** 169 169 170 170 171 - **Step2**:Poweron TrackerDby using theonboardwitch.181 +[[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"]] 172 172 173 173 174 -**Step 3:** TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server. 175 175 185 +(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch. 176 176 177 -**Positioning Mode(SMOD):** 178 178 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. 188 +(% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server. 182 182 183 -User can switch modes by [[changing SMOD>>path:#Positioning_Mode]]. 184 184 185 185 186 -1. 187 -11. Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~- 192 +== 2.3 Positioning Mode(SMOD) == 188 188 189 189 190 -1. 191 -11. 192 -111. Uplink FPORT=5, Device Status 195 +Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 193 193 197 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 198 +* (% 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. 199 +* (% 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. 194 194 201 +Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 195 195 196 -1. 197 -11. 198 -111. Uplink FPORT= , Realtime GNSS Positioning 199 199 200 -The default uplink payload includes totally 11 bytes. (User can use AT+MOD=0 to enable the Temperature and humidity sensor to hum/tem info from accelerometer. When accelerometer info is enable, total payload will be 15 bytes, please note 15 bytes won’t work on DR0 on US915/AU915 frequency band. ) 201 201 205 +== 2.4 Uplink Payload == 202 202 203 -|((( 204 -**Size** 205 205 206 -**(bytes)** 207 -)))|4|4|2|1|((( 208 -2 208 +=== 2.4.1 Uplink FPORT~=5, Device Status === 209 209 210 -(optional ) 211 -)))|((( 210 + 211 +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. 212 + 213 +Use can also get the Device Status uplink through the downlink command: **Downlink: 0x2301** 214 + 215 + 216 +(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %) 217 +|=(% 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 218 +|=(% 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 219 + 220 +[[image:1665301570342-765.png]] 221 + 222 + 223 +(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002 224 + 225 +(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13 226 + 227 +(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version 228 + 229 +(% style="color:#037691" %)**Frequency Band**: 230 + 231 +*0x01: EU868 232 + 233 +*0x02: US915 234 + 235 +*0x03: IN865 236 + 237 +*0x04: AU915 238 + 239 +*0x05: KZ865 240 + 241 +*0x06: RU864 242 + 243 +*0x07: AS923 244 + 245 +*0x08: AS923-1 246 + 247 +*0x09: AS923-2 248 + 249 +*0x0a: AS923-3 250 + 251 +Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF) 252 + 253 +(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD. 254 + 255 + 256 +(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV 257 + 258 +Use can also get the Device Status uplink through the downlink command: 259 + 260 + 261 +(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40 262 + 263 +(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %) 264 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit 265 +|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings 266 + 267 +(% style="color:blue" %)** SMOD:** 268 + 269 +(% style="color:red" %)** 1 :** (%%) GPS ONLY 270 + 271 +(% style="color:red" %)** 2 :** (%%) BLE ONLY 272 + 273 +(% style="color:red" %)** 3 :** (%%) GPS/BLE Hybrid 274 + 275 + 276 +(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload** 277 + 278 +(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values 279 + 280 +(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values 281 + 282 + 283 +(% style="color:blue" %)** BLE_Settings:** 284 + 285 +(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 286 + 287 +(% style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%) 288 + 289 + 290 +(% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 291 + 292 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %) 293 +|=(% 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 294 +|=(% 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"]] 295 + 296 + 297 + 298 +=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 299 + 300 + 301 +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, 302 + 303 + 304 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %) 305 +|=(% scope="row" style="width: 60px;" %)((( 306 +**Size(bytes)** 307 +)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)((( 212 212 2 309 +)))|(% style="width:30px" %)((( 310 +2 311 +))) 312 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 313 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 314 +)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 213 213 214 -(optional) 316 +[[image:1665301636888-168.png]] 317 + 318 + 319 +==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== 320 + 321 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 322 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits 323 +|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 324 + 325 + 326 + 327 +==== (% style="color:blue" %)**FLAG:**(%%) ==== 328 + 329 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %) 330 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit 331 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] 332 + 333 +**Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 334 + 335 + 336 +==== (% style="color:blue" %)**Location info:**(%%) ==== 337 + 338 +* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976// 339 +* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 340 + 341 +(% style="color:red" %)**Important note:** 342 + 343 +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. 344 + 345 +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: 346 + 347 + 348 +[[image:1664502116362-706.png]] 349 + 350 + 351 +3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 352 + 353 +[[image:1664502166010-515.png]] 354 + 355 + 356 + 357 +==== (% style="color:blue" %)**Alarm:**(%%) ==== 358 + 359 +**Example: ** 0x4B & 0x40 >> 6 = 0x01 360 + 361 + 362 +==== (% style="color:blue" %)**BAT:**(%%) ==== 363 + 364 +**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV). 365 + 366 +((( 367 +The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \ 215 215 ))) 216 -|**Value**|[[Latitude>>path:#Location]]|[[Longitude>>path:#Location]]|((( 217 -[[Alarm &>>path:#Alarm]] 218 218 219 -[[BAT>>path:#Alarm]] 220 -)))|[[FLAG>>path:#Flag]]|Hum|[[Tem>>path:#Pitch]] 370 +* > 4.0v : 80% ~~ 100% 371 +* 3.85v ~~3.99v: 60% ~~ 80% 372 +* 3.70v ~~ 3.84v: 40% ~~ 60% 373 +* 3.40v ~~ 3.69v: 20% ~~ 40% 374 +* < 3.39v: 0~~20% 221 221 222 222 223 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]] 224 224 378 +==== (% style="color:blue" %)**MOD:**(%%) ==== 225 225 226 -** Alarm& BAT:**380 +**Example: ** (0x60>>6) & 0x3f =1 227 227 228 -|**Size(bit)**|1 bit|1bit|14 bits 229 -|**Value**|reserve|Alarm Indicate|[[BAT>>path:#BAT]] 382 +**Set the format of GPS data uplink link:** 230 230 231 -**FLAG:** 384 +(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values 385 +(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values 232 232 233 -|**Size(bit)**|2 bits|1bit|5 bits 234 -|**Value**|[[MOD>>path:#MD]]|[[LON>>path:#LON]]|Firmware version 235 235 388 +**Set the format of BLE data uplink link:** 236 236 390 +(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon 237 237 238 -**Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A ** 239 239 393 +==== (% style="color:blue" %)**LON:**(%%) ==== 240 240 241 -** Location info:**395 +**Example:** (0x60>>5) & 0x01=1. 242 242 243 - * Latitude:02863D68⇒//if(0x//02863D68//& 0x80000000 = 0 )~://397 +Enable/Disable LED activity for uplink 244 244 245 -//value = 02863D68 /1000000 = 42.351976// 399 +((( 400 +(% style="color:#037691" %)**0x00:** (%%) Disable LED indicator. 401 +))) 246 246 247 -* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// 403 +((( 404 +(% style="color:#037691" %)**0x01:** (%%) Enable LED indicator (Default Value) 405 +))) 248 248 249 -//value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 250 250 408 +==== (% style="color:blue" %)**Hum:**(%%) ==== 251 251 252 - Importantnote:410 +0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree 253 253 254 -1. When power is low (<2.84v), GPS won’t be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF. 255 -1. In firmware version v1.5, Roll & Pitch is disabled by default. 256 -1. When enable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accept only 11 bytes payload. In this case, the payload on server will be ignore and shows as below: 257 257 258 - [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]]413 +==== (% style="color:blue" %)**Tem:**(%%) ==== 259 259 415 +011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree// 260 260 261 -1. While GPS can’t get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 262 262 263 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]] 264 264 265 -* **Alarm**: Example: 0x4B & 0x40 >> 6 = 0x01 266 -* **BAT**: Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV). 419 +=== 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) === 267 267 268 -The battery info shows the current voltage, for **TrackerD** version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \ 269 269 422 +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) 270 270 271 -* > 4.0v : 80% ~~ 100% 272 -* 3.85v ~~3.99v: 60% ~~ 80% 273 -* 3.70v ~~ 3.84v: 40% ~~ 60% 274 -* 3.40v ~~ 3.69v: 20% ~~ 40% 275 -* < 3.39v: 0~~20% 276 276 425 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %) 426 +|=(% scope="row" style="width: 60px;" %)((( 427 +**Size(bytes)** 428 +)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1 429 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 430 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 431 +)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 277 277 278 -* **LON: **Enable/Disable LED activity for uplink 433 +(% class="wikigeneratedid" %) 434 +[[image:1665301687277-443.png]] 279 279 280 -0x00: Disable LED indicator. 281 281 282 -0x01: Enable LED indicator (Default Value) 283 283 438 +=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 284 284 285 -* **Hum**: 0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree 286 -* **//Tem//**//: 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree 287 287 441 +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. 288 288 289 289 290 -1. 291 -11. 292 -111. Uplink FPORT= , History GNSS Positioning 444 +(% style="color:red" %)**Note for this mode:** 293 293 446 +* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server. 447 +* 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. 448 +* 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 294 294 450 +The payload is 15 bytes, as below. 295 295 296 -1. 297 -11. 298 -111. BLE positioning Payload(Fport=2) 452 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 453 +|=(% scope="row" %)((( 454 +**Size(bytes)** 455 +)))|4|4|2|1|1|1|1|1 456 +|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 299 299 300 - Different MODE has differentpayload:458 +[[image:image-20221009160309-2.png]] 301 301 302 -**MODE=2** 303 303 304 -|((( 305 -**Size** 306 306 307 -**(bytes)** 308 -)))|16|4|4|2|4|2|1 309 -|**Value**|[[UUID>>path:#Location]]|((( 310 -iBeacon 462 +=== 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 311 311 312 -MAJOR 313 -)))|((( 314 -iBeacon 315 315 316 -MINOR 317 -)))|((( 318 -iBeacon Measured 465 +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. 319 319 320 -Power 321 -)))|((( 322 -iBeacon 467 +User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings. 323 323 324 -RSSI 325 -)))|((( 326 -[[Alarm &>>path:#Alarm]] 327 327 328 -[[BAT>>path:#Alarm]] 329 -)))|[[FLAG>>path:#Flag]] 470 +(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 471 +|=(% scope="row" style="width: 60px;" %)((( 472 +**Size(bytes)** 473 +)))|(% 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 474 +|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)((( 475 +iBeacon MAJOR 476 +)))|(% style="width:63px" %)((( 477 +iBeacon MINOR 478 +)))|(% style="width:71px" %)((( 479 +iBeacon Measured Power 480 +)))|(% style="width:50px" %)((( 481 +iBeacon RSSI 482 +)))|(% style="width:47px" %)((( 483 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 484 +)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 330 330 486 +[[image:1664502425687-834.png]] 331 331 332 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]] 333 333 489 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 490 +* (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 491 +* (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 492 +* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. 493 +* (% style="color:#037691" %)**MINOR:** (%%)The MAJOR from the strongest iBeacon. 494 +* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 495 +* (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 334 334 335 -* **BAT**: Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV). 336 -* **MODE: **Define the payload format. 337 -* **UUID: **The uuid from the strongest iBeacon. 338 -* **MAJOR**: The MAJOR from the strongest iBeacon. 339 -* **MINOR**: The MAJOR from the strongest iBeacon. 340 -* **Measured** **Power**: The Measured Power from the strongest iBeacon. 341 -* **RSSI**: The RSSI from the strongest iBeacon. 342 342 343 343 344 -1. 345 -11. 346 -111. Add Payload format in TTN V3 499 +=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 347 347 348 -In TTN V3, use can add a custom payload so it shows friendly. 349 349 350 - In the pageApplications~-~->Payload Formats~-~->Custom~-~->decoder502 +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. 351 351 352 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]] 353 353 354 -Add the decoder from this link: 505 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %) 506 +|=(% scope="row" style="width: 60px;" %)((( 507 +**Size(bytes)** 508 +)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1 509 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)((( 510 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 511 +)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 355 355 513 +(% class="wikigeneratedid" %) 514 +[[image:1667288597595-714.png||height="212" width="1151"]] 356 356 357 -Save the change the uplink message will be parsed. As below: 358 358 359 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]] 517 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 518 +* (% style="color:#037691" %)**SSID: **(%%)WiFi name. 519 +* (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 360 360 361 361 362 362 523 +=== 2.4.7 Add Payload format in TTN V3 === 363 363 364 364 365 -1. 366 -11. Integrate with Datacake 526 +In TTN V3, user can add a custom payload so it shows friendly. 367 367 528 +In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 368 368 369 -After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot. 370 370 371 - Instruction is here:[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example~~-~~-AddTrackerDGPSTrackingInDataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example--AddTrackerDGPSTrackingInDataCake]]531 +[[image:1664502649601-895.png]] 372 372 373 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]] 374 374 534 +Add the decoder from this link: 375 375 376 -1. 377 -11. Integrate with Tago 536 +[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] 378 378 538 +Save the change the uplink message will be parsed. As below: 379 379 540 +[[image:1664502676891-606.png]] 541 + 542 + 543 + 544 +== 2.5 Integrate with Datacake == 545 + 546 + 380 380 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. 381 381 549 +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]] 550 + 551 + 552 +[[image:1664502695771-538.png]] 553 + 554 + 555 + 556 +== 2.6 Integrate with Tago == 557 + 558 + 559 +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. 560 + 382 382 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]] 383 383 384 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]] 385 385 564 +[[image:1664502715371-321.png]] 386 386 387 387 388 388 389 -1. 390 -11. Alarm Mode 568 +== 2.7 Datalog Feature == 391 391 392 392 393 - User can pushthe **RED button** by morethan5secondsto enterAlarm Mode.571 +total 273 entries,by default, 394 394 573 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 395 395 396 - Once enter Alarm mode, the **GREEN LED** will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send apacket withoutlocation info and thensenda data packet with GPS positioning information. After that, the device willsend 60 packets at 1-minute intervals.The Alarm flag in the payload will be set for the next 60 packets unless exit alert mode.575 +Example use case. 397 397 577 +[[image:image-20221009234703-2.png||height="328" width="899"]] 398 398 579 + 580 +[[image:image-20221009234629-1.png||height="390" width="577"]] 581 + 582 + 583 + 584 +== 2.8 Alarm Mode == 585 + 586 + 587 +((( 588 +User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 589 +))) 590 + 591 + 592 +((( 593 +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. 594 +))) 595 + 596 + 597 +((( 399 399 Two ways to exit alarm mode: 599 +))) 400 400 401 -* Server send a downlink command to exit. 601 +* Server sends a downlink command to exit. 402 402 * User fast press the RED button 10 times. 403 403 404 -When exit alarm mode, **RED LED** will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false. 604 +((( 605 +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. 606 +))) 405 405 406 406 407 -1. 408 -11. Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- 409 409 610 +== 2.9 Transport Mode == 410 410 411 411 412 -1. 413 -11. LED Status 613 +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. 414 414 415 415 416 -|**Event**|**Action**|**AT+LON to control on/off** 417 -|**Power On**|**BLUE, RED , Green** flash once|N/A 418 -|**Join request**|**Green** led fast blink once (200ms)|Yes 419 -|**Join Success**|**Green** led on 5 second|N/A 420 -|**Fixing Location**|**BLUE **blinks 200ms per second|Yes 421 -|**Fixed and uplink**|**GREEN **blinks twice (200ms per blink)|Yes 422 -|**Fail Fix and uplink**|**RED **blinks twice (200ms per blink)|Yes 423 -|**Enter Alarm mode**|**RED **on for 3 seconds|Yes 424 -|**Uplink under Alarm**|**RED **on for 1 second|Yes 425 -|**Exit Alarm**|**BLUE **led on 5 second|Yes 426 -|**Get Downlink**|**GREEN** led on 1 second|Yes 427 -|**Movement Detect**|**RED **on 500ms|N/A 428 428 617 +== 2.10 LED Status == 429 429 430 430 620 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 621 +|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 622 +|(% 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 623 +|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes 624 +|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A 625 +|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes 626 +|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes 627 +|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes 628 +|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes 629 +|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes 630 +|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes 631 +|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 632 +|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 431 431 432 432 433 -1. 434 -11. Button Function 435 435 436 - **RESETbutton:**636 +== 2.11 Button Function == 437 437 438 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]] 439 439 639 +(% style="color:blue" %)**RESET button:** 640 + 641 +[[image:1664502835802-546.png]] 642 + 440 440 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server. 441 441 442 442 443 -**RED button:** 646 +(% style="color:red" %)**RED button:** 444 444 445 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]648 +[[image:1664502854406-763.png]] 446 446 447 -|**Function**|**Action**|**Description** 448 -|Send Alarm|Keep Pressing **RED** button for more than 5 seconds|Enter Alarm Mode. See [[Alarm Mode>>path:#Alarm_Mode]] 449 -|Exit Alarm Mode|Fast press the **RED** button 10 times|Exit Alarm Mode 450 -|Enter Deep Sleep Mode|Press and hold the button for 10 seconds, then quickly press the device 3 times to enter deep sleep|This is the mode ship out from factory. CPU will be complete in sleep mode and no LoRa activity, only use before deploy. 451 451 651 +(% border="1" style="background-color:#ffffcc; color:green; width:510px" %) 652 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description** 653 +|(% 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"]] 654 +|(% 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 655 +|(% 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. 452 452 453 453 454 454 455 -1. 456 -11. USB Port Function 659 +== 2.12 USB Port Function == 457 457 661 + 458 458 The USB interface of TrackerD has below functions: 459 459 460 460 * Power on the device 461 461 * Recharge the battery 462 -* [[Configure Device>> path:#AT_Command]]463 -* [[Upgrade Firmware>> path:#upgrade_image]]666 +* [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 667 +* [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 464 464 465 465 466 466 671 += 3. Configure TrackerD via AT command or LoRaWAN downlink = 467 467 468 468 469 - 1.Configure TrackerD via ATcommand or LoRaWANdownlink674 +User can configure TrackerD via AT Command or LoRaWAN Downlink. 470 470 676 +LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] 471 471 472 -User can configure TrackerD via AT Command or LoRaWAN Downlink. 473 473 474 -LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]] 475 475 680 +== 3.1 Access AT Command == 476 476 477 -1. 478 -11. Access AT Command 479 479 480 -TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below. ...683 +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. 481 481 482 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]] 483 483 686 +[[image:1664502999401-486.png]] 484 484 485 -In PC, User needs to set serial tool baud rate to **115200** to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands: 486 486 689 +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: 487 487 488 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]] 489 489 692 +[[image:1664503022490-662.png]] 490 490 491 491 492 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]695 +[[image:1664503035713-500.png]] 493 493 494 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]] 495 495 698 +[[image:1664503047675-651.png]] 496 496 497 -1. 498 -11. Command Set 499 499 500 500 501 -1. 502 -11. 503 -111. Set Transmit Interval 702 +== 3.2 Command Set == 504 504 704 + 705 +=== 3.2.1 Set Transmit Interval === 706 + 707 + 505 505 Set device uplink interval. 506 506 507 -* AT Command: 710 +* (% style="color:blue" %)**AT Command:** 508 508 509 -AT+TDC=xxx 712 +(% style="color:#037691" %)**AT+TDC=xxx ** 510 510 511 -Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds) 714 +Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds) 512 512 513 513 514 -* Downlink Payload (prefix 0x01): 717 +* (% style="color:blue" %)**Downlink Payload (prefix 0x01):** 515 515 516 -0x01 00 01 2C 719 +(% style="color:#037691" %)**0x01 00 01 2C** (%%) ~/~/ Same as AT+TDC=300000 517 517 518 518 519 -1. 520 -11. 521 -111. Set Alarm Packet transmission interval 522 522 723 +=== 3.2.2 Set Alarm Packet transmission interval === 724 + 725 + 523 523 Set alarm packet transmit interval 524 524 525 -* AT Command: 728 +* (% style="color:blue" %)**AT Command:** 526 526 527 -AT+ATDC=xx. 730 +(% style="color:#037691" %)**AT+ATDC=xx. ** 528 528 529 -Example: AT+ATDC=60000 àSet Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000732 +Example: AT+ATDC=60000 **~-~-> ** Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000 530 530 531 531 532 -* Downlink Payload (prefix 0xB1): 735 +* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):** 533 533 534 -0xB1 00 00 3C 737 +(% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/ Same as AT+ATDC=60000 535 535 536 536 537 -1. 538 -11. 539 -111. Set Sports Mode Packet transmission interval 540 540 541 -Set sport spacket transmitinterval741 +=== 3.2.3 Set Transport Mode Packet transmission interval === 542 542 543 -* AT Command: 544 544 545 - AT+MTDC=xx.744 +Set Transport Mode packet transmit interval 546 546 547 - Example:AT+MTDC=300000 à Set SportsMode PacketIntervalto 300 seconds. TrackerD will sendevery300 seconds in Sportsmode, Default Value:300000746 +* (% style="color:blue" %)**AT Command:** 548 548 748 +(% style="color:#037691" %)**AT+MTDC=xx. ** 549 549 550 - *DownlinkPayload(prefix0x03):750 +Example: AT+MTDC=300000 **~-~-> ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000 551 551 552 -0x03 00 01 2C ~/~/Same as AT+ MTDC=3000000 553 553 753 +* (% style="color:blue" %)**Downlink Payload (prefix 0x03):** 554 554 755 +(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+MTDC=3000000 555 555 556 -1. 557 -11. 558 -111. Exit Alarm 559 559 758 + 759 +=== 3.2.4 Exit Alarm === 760 + 761 + 560 560 Server send downlink command to exit Alarm mode 561 561 562 -* AT Command: 764 +* (% style="color:blue" %)**AT Command: No AT Command** 563 563 564 - NoATCommand766 +* (% style="color:blue" %)**Downlink Payload (prefix 0x02):** 565 565 768 +(% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 566 566 567 -* Downlink Payload (prefix 0x02): 568 568 569 -0x02 01 ~/~/ Exit Alarm Mode 570 570 772 +=== 3.2.5 Disable/Enable LED flash === 571 571 572 -1. 573 -11. 574 -111. Disable/Enable LED flash 575 575 576 576 Disable/Enable LED for position, downlink and uplink 577 577 578 -* AT Command: 777 +* (% style="color:blue" %)**AT Command:** 579 579 580 -AT+LON=xx. (Disable (0), Enable (1), default:1) 779 +(% style="color:#037691" %)**AT+LON=xx. (Disable (0), Enable (1), default:1)** 581 581 582 - àDisable LED for position, downlink and uplink.781 +Example: AT+LON=0 **~-~-> ** Disable LED for position, downlink and uplink. 583 583 584 584 585 -* Downlink Payload (prefix 0xAE): 784 +* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):** 586 586 587 -0xAE 00 786 +(% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/ Same as AT+LON=0 588 588 589 589 590 590 790 +=== 3.2.6 Disable/Enable Transport Mode === 591 591 592 -1. 593 -11. 594 -111. Disable/Enable movement detect (Debug Only) 595 595 596 -User can use this feature to check andet thread holeof movement detect793 +Users can use this feature to enable/disable Transport Mode. 597 597 598 -* AT Command: 795 +* (% style="color:blue" %)**AT Command:** 599 599 600 -AT+INTWK=xx. (Disable (0), Enable (1), default:0) 797 +(% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)** 601 601 602 - àEnabledetectmovement.799 +Example: AT+INTWK=1 **~-~-> ** Enable Transport Mode. 603 603 604 604 605 -* Downlink Payload (prefix 0xAF): 802 +* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):** 606 606 607 -0xAF 01 804 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+INTWK=1 608 608 609 609 610 610 611 -1. 612 -11. 613 -111. Set Positioning Mode 808 +=== 3.2.7 Set Positioning Mode === 614 614 615 -SMOD define the how TrackerD scan and uplink date. 616 616 617 - GPS室外定位模式:设备默认模式,设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是3分钟定位,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。GPS还有一种logdata模式,在断网的情况下将数据存储下来,等到有网的时候,一次将数据以每10秒上报。811 +SMOD define how TrackerD scan and uplink data: 618 618 619 - BLE室内定位模式:设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是5秒,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每3分钟发送一次)。 620 620 621 - GPS和BLE混动模式:设备入网后会发送device当前模式下的信息,随后立即判断是否在室内,如果是就进行BLE定位,不是就GPS定位。如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。814 +* (% style="color:blue" %)**AT Command:** 622 622 623 - 运动模式:设备入网后会发送device当前模式下的信息,随后发送GPS定位数据,设备判断是否在运动,没有运动传感器没有检测到动作,立即进入静止状态(默认20分钟),如果产生运动,将每5分钟发送一次数据,再第五分钟后检测设备有误运动,无将切换到静止状态,有立即发送数据。816 +(% style="color:#037691" %)**AT+SMOD=aa,bb,cc** 624 624 818 +(% style="color:#037691" %)** aa:** 625 625 820 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 626 626 822 +* (% 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. 627 627 628 -* ATCommand:824 +* (% 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 630 - AT+SMOD=xx.826 +(% style="color:#037691" %)**bb:** 631 631 632 - Example:828 +* (% style="color:red" %)**0 : **(%%)GPS+ BAT+ State+Tem&Hum 633 633 634 - AT+ SMOD=1,0àGPS+BAT+State+Tem&Hum830 +* (% style="color:red" %)**1 :**(%%) GPS +BAT State 635 635 636 - AT+ SMOD=1,1à GPS +BAT State832 +(% style="color:#037691" %)**cc: ** 637 637 638 - AT+ SMOD =2,3 à (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。 834 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 835 + 836 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%)) 639 639 838 +(% style="color:blue" %)**Example:** 640 640 641 - *DownlinkPayload(prefix0xA5):840 + AT+SMOD=1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 642 642 643 - 0xA50100 ~/~/ Same asAT+842 + AT+SMOD=1,1,0 ~-~-> GPS +BAT State 644 644 844 + AT+SMOD=2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 645 645 646 -1. 647 -11. 648 -111. Set MAX GPS position time 846 + AT+SMOD=2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State 649 649 848 + 849 +* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** 850 + 851 +(% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+SMOD=1,0,0 852 + 853 + 854 + 855 +=== 3.2.8 Set MAX GPS position time === 856 + 857 + 650 650 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. 651 651 652 652 ... ... @@ -653,105 +653,197 @@ 653 653 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. 654 654 655 655 656 -* AT Command: 864 +* (% style="color:blue" %)**AT Command:** 657 657 658 -AT+FTIME=xx àSet to use xx as max fix time.866 +(% style="color:#037691" %)**AT+FTIME=xx** (%%) **~-~-> ** Set to use xx as max fix time. 659 659 660 -Example: AT+FTIME=150 868 +**Example:** AT+FTIME=150 661 661 662 662 663 -* Downlink Payload (prefix 0xAA): 871 +* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):** 664 664 665 -0xAA 00 96 873 +(% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/ Set AT+FTIME=150 666 666 667 667 668 668 877 +=== 3.2.9 Set PDOP value for GPS fix accuracy === 669 669 670 -1. 671 -11. 672 -111. Set PDOP value for GPS fix accuracy 673 673 674 -PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can ’t get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server.880 +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. 675 675 676 676 677 677 A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0 678 678 679 679 680 -* AT Command: 886 +* (% style="color:blue" %)**AT Command:** 681 681 682 -AT+PDOP=2.5 àSet PDOP to 2.5888 +(% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~-> ** Set PDOP to 2.5 683 683 684 684 685 -* Downlink Payload (prefix 0xAD): 891 +* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):** 686 686 687 -0xAD 00 0A 893 +(% style="color:#037691" %)**0xAD 00 0A** (%%) ~/~/ Set AT+PDOP=1 (0x0A / 10 =1) 688 688 689 -0xAD 00 19 895 +(% style="color:#037691" %)**0xAD 00 19** (%%) ~/~/ Set AT+PDOP=2.5 (0x19 / 10 =2.5) 690 690 691 -0xAD 00 46 ~/~/Set AT+PDOP=7 897 +(% style="color:#037691" %)**0xAD 00 46** (%%) ~/~/ Set AT+PDOP=7 (0x46 / 10 =7) 692 692 899 + 900 + 693 693 Disable/Enable the confirmation mode 694 694 695 -* AT Command: 903 +* (% style="color:blue" %)**AT Command:** 696 696 697 -AT+CFM=xx .905 +(% style="color:#037691" %)**AT+CFM=xx** 698 698 699 - Example: 700 700 701 - AT+ CFM=0 à Disableconfirmation908 +**~ Example:** 702 702 703 - AT+ 1àEnable confirmation910 + AT+CFM=0 **~-~-> ** Disable confirmation 704 704 912 + AT+CFM=1 **~-~-> ** Enable confirmation 705 705 706 -* Downlink Payload (prefix 0x05): 707 707 708 - 0x0501~/~/ Same asAT+SMOD =1915 +* (% style="color:blue" %)**Downlink Payload (prefix 0x05):** 709 709 917 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1 710 710 711 711 712 712 921 +=== 3.2.10 Auto Send None-ACK messages === 713 713 714 714 715 - 1.Settingfor DifferentScenarios924 +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. 716 716 717 717 927 +* (% style="color:blue" %)**AT Command: AT+PNACKMD** 718 718 719 -1. Upload Firmware 720 -11. Firmware Change Log 929 +The default factory setting is 0. 721 721 931 + 932 +**Command Example Function Response:** 933 + 934 +(% style="color:#037691" %)**AT+PNACKMD=1** (%%) ~/~/ Poll None-ACK message OK 935 + 936 + 937 +* (% style="color:blue" %)**Downlink Command: 0x34** 938 + 939 +Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 940 + 941 + 942 + 943 +=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 944 + 945 + 946 +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. 947 + 948 +(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.** 949 + 950 +(% style="color:blue" %)**AT Command:** 951 + 952 + (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 953 + 954 + (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 955 + 956 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 957 + 958 +Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 959 + 960 + 961 + 962 +=== 3.2.12 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 963 + 964 + 965 +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. 966 + 967 +(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.** 968 + 969 +(% style="color:blue" %)**AT Command:** 970 + 971 + (% style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456 972 + 973 + (% style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK 974 + 975 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)** 976 + 977 +Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 978 + 979 + 980 + 981 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 982 + 983 + 984 +Users can use this feature to enable/disable Information printing. 985 + 986 +(% style="color:blue" %)**AT Command:** 987 + 988 +(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/(Disable (0), Enable (1), default:0) 989 +\\Example: AT+SHOWID=1 ~-~-> Enable Information printing. 990 + 991 + 992 + 993 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 994 + 995 + 996 +The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. 997 + 998 +(% style="color:blue" %)**AT Command:** 999 + 1000 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode 1001 + 1002 + 1003 +(% style="color:blue" %)**Downlink Payload:0X24** 1004 + 1005 +Example: 0x24 01 ~/~/ Same as AT+CHE=1 1006 + 1007 + 1008 + 1009 += 4. Setting for Different Scenarios = 1010 + 1011 + 1012 + 1013 += 5. Upload Firmware = 1014 + 1015 + 1016 +== 5.1 Firmware Change Log == 1017 + 1018 + 722 722 **[[See this link>>url:https://github.com/dragino/TrackerD]]** 723 723 724 724 725 -1. 726 -11. How to upgrade firmware 727 727 728 - Usercanusethe TrackerD ’s USB port to upgrade firmwareintoit. The hardware connection forupgrade firmwareis as below:1023 +== 5.2 How to upgrade firmware == 729 729 730 730 731 - **Step1:**Connect TrackerDand PC viaUSBcableshippedwithTrackerD.1026 +User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below: 732 732 733 -**Step2:** Install CH9102 driver in the PC. 734 734 1029 +(% style="color:blue" %)**Step1: **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD. 1030 + 1031 + 1032 +(% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC. 1033 + 735 735 After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager. 736 736 737 737 738 -**Step3 :**1037 +(% 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]] 739 739 740 -[[https:~~/~~/www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools]] 741 741 742 -**Step4:** 1040 +(% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32 743 743 744 744 745 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png||alt="image-20220712083115-1.png"]]1043 +[[image:1664503563660-578.png]] 746 746 747 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png||alt="image-20220712083115-2.png"]] 748 748 1046 +[[image:1664503574618-659.png]] 749 749 750 -**Step5:** Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 751 751 752 -[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 753 753 1050 +(% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 754 754 1052 +[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]] 1053 + 1054 + 755 755 Users need to use below files: 756 756 757 757 boot_app0.bin @0e000 ... ... @@ -758,75 +758,89 @@ 758 758 759 759 ESP_LORA-eeprom-class.bin @ 0x10000 760 760 761 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png||alt="image-20220712083115-3.png"]] 762 762 1062 +[[image:1664503593459-435.png]] 1063 + 1064 + 1065 + 763 763 After upgrade finish, it will show finish as below: 764 764 765 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png||alt="image-20220712083115-4.png"]]1068 +[[image:1664503611848-385.png]] 766 766 767 767 768 768 1072 += 6. Developer Guide = 769 769 770 770 771 - 1.DeveloperGuide1075 +== 6.1 Compile Source Code == 772 772 773 773 774 -* 775 -*1. Compile Source Code 776 -*11. Set up ARDUINO compile environment 777 -* Download the latest Arduino software (IDE) from the Arduino official website 1078 +=== 6.1.1 Set up ARDUINO compile environment === 778 778 779 -[[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]] 780 780 781 - InstallIDEonPC,openandclickFile~-~-> Preference,addthefollowingURL[[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]]1081 +* **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]]** 782 782 783 - [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]1083 +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]] 784 784 785 -* Go to tools ~-~-> Boards ~-~-> Boards Manager, find the esp32 information and install it. 786 786 787 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]1086 +[[image:1664503635019-941.png]] 788 788 789 789 790 -* Download the latest TrackerD from the dragino github 791 791 792 - [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]1090 +* (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 793 793 1092 +[[image:1664503715811-892.png]] 794 794 795 -Put the Library in the TrackerD directory into the libraries file in the Arduino directory 796 796 797 - [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]1095 +(% 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. 798 798 1097 +[[image:image-20221024105643-1.png]] 799 799 1099 +**~ Figure1** 800 800 801 801 802 -* 803 -*1. Source Code 804 -* Open the example in the TrackerD file, please select the correct port in the IDE, as shown below: 1102 +[[image:image-20221024105643-2.png]] 805 805 806 - [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]1104 + **Figure2** 807 807 808 -* Click to upload 809 809 810 - [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]1107 +* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]** 811 811 812 - *Checkthe result,iftheuploadis successful, as shown below,open theserial portto viewthe data1109 +Put the Library in the TrackerD directory into the libraries file in the Arduino directory: 813 813 814 814 815 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]]1112 +[[image:1664503752288-974.png]] 816 816 817 817 818 818 1116 +== 6.2 Source Code == 819 819 820 820 1119 +* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:** 821 821 822 - =7.FAQ =1121 +[[image:1664503794261-827.png]] 823 823 824 824 825 825 1125 +* (% style="color:blue" %)**Click to upload** 1126 + 1127 +[[image:1664503808294-336.png]] 1128 + 1129 + 1130 + 1131 +* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 1132 + 1133 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 1134 + 1135 + 1136 + 1137 += 7. FAQ = 1138 + 1139 + 826 826 == 7.1 How to change the LoRa Frequency Bands/Region? == 827 827 828 828 829 -User can follow the introduction for [[how to upgrade image>> path:#upgrade_image]]. When download the images, choose the required image file for download.1143 +User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download. 830 830 831 831 832 832 ... ... @@ -837,8 +837,8 @@ 837 837 838 838 839 839 840 -(% border=" 2" style="background-color:#ffffcc; color:green; width:314px" %)841 -|(% style="width:118px" %)**Pin**|(% style="width:67px" %)**Color**|(% style="width:123px" %)**USB Pin** 1154 +(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %) 1155 +|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin** 842 842 |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC 843 843 |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A) 844 844 |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A) ... ... @@ -848,15 +848,97 @@ 848 848 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 849 849 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 850 850 851 -= 8. Order Info = 852 852 853 853 1167 +== 7.3 Notes on using different serial port tools for TrackerD == 1168 + 1169 + 1170 +=== 7.3.1 Serial port utility === 1171 + 1172 + 1173 +Serial port utility requires you to automatically add data streams. 1174 + 1175 +Need to adjust the data stream to RTS/CTS on physical restart. 1176 + 1177 + 1178 +(% class="wikigeneratedid" %) 1179 +[[image:image-20221102140621-1.png]] 1180 + 1181 + 1182 +When using AT commands, the data flow needs to be adjusted to XON/XOFF 1183 + 1184 + 1185 +[[image:image-20221102140638-2.png]] 1186 + 1187 + 1188 + 1189 +=== 7.3.2 SecureCRT === 1190 + 1191 + 1192 +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. 1193 + 1194 + 1195 +[[image:image-20221102140704-3.png]] 1196 + 1197 + 1198 +[[image:image-20221102140712-4.png]] 1199 + 1200 + 1201 + 1202 +=== 7.3.3 PUTTY === 1203 + 1204 + 1205 +[[image:image-20221102140748-5.png]] 1206 + 1207 + 1208 +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. 1209 + 1210 + 1211 +[[image:image-20221102140801-6.png]] 1212 + 1213 + 1214 + 1215 += 8 Trouble Shooting = 1216 + 1217 + 1218 +== 8.1 TDC is changed to 4294947296 and cause no uplink. == 1219 + 1220 + 1221 +((( 1222 +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 1223 +))) 1224 + 1225 + 1226 + 1227 +== 8.2 Device not able get AT Command or show output after wake up from deep sleep mode == 1228 + 1229 + 1230 +((( 1231 +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. 1232 +))) 1233 + 1234 + 1235 + 1236 +== 8.3 The reason why it has been restarted after upgrading(V.1.4.1) == 1237 + 1238 + 1239 +((( 1240 +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 1241 +))) 1242 + 1243 + 1244 +[[image:image-20221107145243-1.png||height="695" width="443"]] 1245 + 1246 + 1247 + 1248 += 9. Order Info = 1249 + 1250 + 854 854 Part Number: (% style="color:blue" %)**TrackerD-XXX** 855 855 856 856 (% style="color:blue" %)**XXX**(%%): The default frequency band 857 857 858 858 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433 859 -* (% style="color:red" %)**CN470**(%%): Default frequency band CN470 860 860 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868 861 861 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865 862 862 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920 ... ... @@ -865,35 +865,35 @@ 865 865 * (% style="color:red" %)**US915**(%%): Default frequency band US915 866 866 867 867 868 -= 9. Packing Info = 869 869 1265 += 10. Packing Info = 870 870 871 -**Package Includes**: 872 872 873 -* TrackerD x 1 874 -* Rechargeable cable x 1 875 -* Program Cable x 1 1268 +(% style="color:#037691" %)**Package Includes**: 876 876 877 -**Dimensions and Weight**: 1270 +* TrackerD LoRaWAN GPS/BLE Tracker x 1 1271 +* USB recharge & program cable x 1 878 878 879 -* Device Size: 85 x 48 x 15 mm/pcs 880 -* Weight: 55g/pcs 1273 +(% style="color:#037691" %)**Dimensions and Weight**: 881 881 1275 +* Device Size: 85 x 48 x 15 mm 1276 +* Weight: 50g 882 882 883 883 884 -= 10. Support = 885 885 886 -* 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. 887 -* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to 1280 += 11. Support = 888 888 889 -[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]] 890 890 1283 +* 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. 1284 +* 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]]. 891 891 892 892 893 893 894 -= 1 1. Reference =1288 += 12. Reference = 895 895 896 896 897 897 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 898 898 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 899 899 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 1294 + 1295 +
- 1664501652064-326.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +143.9 KB - Content
- 1664501677253-891.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +202.7 KB - Content
- 1664501711466-918.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +62.0 KB - Content
- 1664501721248-725.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +55.6 KB - Content
- 1664501734705-405.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +64.1 KB - Content
- 1664501784668-703.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +62.0 KB - Content
- 1664501958445-288.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +74.1 KB - Content
- 1664502116362-706.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +56.0 KB - Content
- 1664502166010-515.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +41.3 KB - Content
- 1664502425687-834.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +38.2 KB - Content
- 1664502649601-895.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +59.2 KB - Content
- 1664502676891-606.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +64.3 KB - Content
- 1664502695771-538.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +54.7 KB - Content
- 1664502715371-321.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +79.9 KB - Content
- 1664502835802-546.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +37.8 KB - Content
- 1664502854406-763.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +14.3 KB - Content
- 1664502999401-486.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +916.7 KB - Content
- 1664503022490-662.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +133.6 KB - Content
- 1664503035713-500.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +354.0 KB - Content
- 1664503047675-651.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +199.1 KB - Content
- 1664503563660-578.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +38.1 KB - Content
- 1664503574618-659.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +139.8 KB - Content
- 1664503593459-435.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +183.3 KB - Content
- 1664503611848-385.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +175.9 KB - Content
- 1664503635019-941.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +161.8 KB - Content
- 1664503715811-892.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +36.6 KB - Content
- 1664503752288-974.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +112.6 KB - Content
- 1664503794261-827.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +119.5 KB - Content
- 1664503808294-336.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +161.6 KB - Content
- 1664503824081-592.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +77.4 KB - Content
- 1664503831430-500.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +147.8 KB - Content
- 1664505654417-133.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +27.5 KB - Content
- 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