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 ... ... @@ -46,7 +46,6 @@ 46 46 (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.** 47 47 48 48 49 - 50 50 == 1.2 Specifications == 51 51 52 52 ... ... @@ -61,13 +61,11 @@ 61 61 * EEPROM: 520 KB 62 62 * Clock Speed: 32Mhz 63 63 64 - 65 65 (% style="color:blue" %)**Common DC Characteristics:** 66 66 67 67 * Supply Voltage: 5V via USB port or Internal li-on battery 68 68 * Operating Temperature: -40 ~~ 60°C 69 69 70 - 71 71 (% style="color:blue" %)**LoRa Spec:** 72 72 73 73 * Frequency Range, ... ... @@ -89,12 +89,10 @@ 89 89 * Packet engine up to 256 bytes with CRC. 90 90 * LoRaWAN 1.0.3 Specification 91 91 92 - 93 93 (% style="color:blue" %)**Battery:** 94 94 95 95 * 1000mA Li-on Battery power (for model TrackerD) 96 96 97 - 98 98 (% style="color:blue" %)**Power Consumption** 99 99 100 100 * Sleeping Mode: 200uA ... ... @@ -131,9 +131,8 @@ 131 131 132 132 133 133 134 -= 2. 1128 += 2. Use TrackerD = 135 135 136 - 137 137 == 2.1 How it works? == 138 138 139 139 ... ... @@ -140,7 +140,6 @@ 140 140 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. 141 141 142 142 143 - 144 144 == 2.2 Quick guide to connect to LoRaWAN server == 145 145 146 146 ... ... @@ -182,53 +182,143 @@ 182 182 **__Add APP KEY and DEV EUI:__** 183 183 184 184 185 -[[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"]] 186 186 187 187 188 188 181 +(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device. 189 189 190 -(% style=" color:blue" %)**Step2**:(%%) Power on TrackerD by usingtheon board switch.183 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]] 191 191 185 +[[image:1664502835802-546.png]] 192 192 187 + 193 193 (% 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. 194 194 195 195 196 - (% style="color:blue"%)**Positioning Mode(SMOD):**191 +== 2.3 Positioning Mode(SMOD) == 197 197 198 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)only get GPS location info. 199 -* (% style="color:#037691" %)**BLE ONLY: **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking. 200 -* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking. 201 201 202 -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. 203 203 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. 204 204 200 +Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 205 205 206 -== 2.3 Uplink Payload == 207 207 203 +== 2.4 Uplink Payload == 208 208 209 -=== 2. 3.1 Uplink FPORT~=5, Device Status ===205 +=== 2.4.1 Uplink FPORT~=5, Device Status === 210 210 211 211 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. 212 212 213 - ===2.3.2UplinkFPORT~=, RealtimeGNSS Positioning===210 +Use can also get the Device Status uplink through the downlink command: **Downlink: 0x2301** 214 214 215 215 216 -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 217 217 217 +[[image:1665301570342-765.png]] 218 218 219 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) 220 -|=(% scope="row" style="width: 50px;" %)((( 219 + 220 +(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002 221 + 222 +(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13 223 + 224 +(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version 225 + 226 +(% style="color:#037691" %)**Frequency Band**: 227 + 228 +*0x01: EU868 229 + 230 +*0x02: US915 231 + 232 +*0x03: IN865 233 + 234 +*0x04: AU915 235 + 236 +*0x05: KZ865 237 + 238 +*0x06: RU864 239 + 240 +*0x07: AS923 241 + 242 +*0x08: AS923-1 243 + 244 +*0x09: AS923-2 245 + 246 +*0x0a: AS923-3 247 + 248 +Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF) 249 + 250 +(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD. 251 + 252 + 253 +(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV 254 + 255 +Use can also get the Device Status uplink through the downlink command: 256 + 257 + 258 +(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40 259 + 260 +(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %) 261 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit 262 +|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings 263 + 264 +(% style="color:blue" %)** SMOD:** 265 + 266 +(% style="color:red" %)** 1 :** (%%) GPS ONLY 267 + 268 +(% style="color:red" %)** 2 :** (%%) BLE ONLY 269 + 270 +(% style="color:red" %)** 3 :** (%%) GPS/BLE Hybrid 271 + 272 + 273 +(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload** 274 + 275 +(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values 276 + 277 +(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values 278 + 279 + 280 +(% style="color:blue" %)** BLE_Settings:** 281 + 282 +(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 283 + 284 +(% style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%) 285 + 286 + 287 +(% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 288 + 289 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %) 290 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit 291 +|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]] 292 + 293 + 294 + 295 +=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 296 + 297 + 298 +Users can use **AT+SMOD=1,0,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes, 299 + 300 + 301 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %) 302 +|=(% scope="row" style="width: 60px;" %)((( 221 221 **Size(bytes)** 222 -)))|(% style="width: 60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)(((223 -2 (optional)224 -)))|(% style="width: 87px" %)(((225 -2 (optional)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 226 226 ))) 227 227 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 228 228 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 229 -)))|(% style="width: 52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]311 +)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 230 230 231 -[[image:166 4501958445-288.png]]313 +[[image:1665301636888-168.png]] 232 232 233 233 234 234 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== ... ... @@ -237,11 +237,13 @@ 237 237 |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits 238 238 |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 239 239 322 + 323 + 240 240 ==== (% style="color:blue" %)**FLAG:**(%%) ==== 241 241 242 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:2 50px" %)243 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width: 50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits244 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] |(% style="width:140px" %)Firmware version326 +(% 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:"]] 245 245 246 246 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 247 247 ... ... @@ -251,23 +251,18 @@ 251 251 * Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976// 252 252 * Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 253 253 254 - 255 - 256 256 (% style="color:red" %)**Important note:** 257 257 258 258 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. 259 259 260 -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: 261 261 262 -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: 263 263 264 - 265 265 [[image:1664502116362-706.png]] 266 266 267 267 348 +3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 268 268 269 -4. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 270 - 271 271 [[image:1664502166010-515.png]] 272 272 273 273 ... ... @@ -274,15 +274,15 @@ 274 274 275 275 ==== (% style="color:blue" %)**Alarm:**(%%) ==== 276 276 277 -Example: 356 +**Example: ** 0x4B & 0x40 >> 6 = 0x01 278 278 279 279 280 280 ==== (% style="color:blue" %)**BAT:**(%%) ==== 281 281 282 -Example: 0CDD& 0x3FFF ⇒3293(mV).361 +**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV). 283 283 284 284 ((( 285 -The battery info shows the currentvoltage, for(% style="color:blue"%)**TrackerD**(%%)version which powered byli-on battery.User can use below mapping to indicate the battery in percentage: \364 +The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \ 286 286 ))) 287 287 288 288 * > 4.0v : 80% ~~ 100% ... ... @@ -293,17 +293,33 @@ 293 293 294 294 295 295 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 + 296 296 ==== (% style="color:blue" %)**LON:**(%%) ==== 297 297 392 +**Example:** (0x60>>5) & 0x01=1. 298 298 299 299 Enable/Disable LED activity for uplink 300 300 301 301 ((( 302 -0x00: Disable LED indicator. 397 +(% style="color:#037691" %)**0x00:** (%%) Disable LED indicator. 303 303 ))) 304 304 305 305 ((( 306 -0x01: Enable LED indicator (Default Value) 401 +(% style="color:#037691" %)**0x01:** (%%) Enable LED indicator (Default Value) 307 307 ))) 308 308 309 309 ... ... @@ -317,16 +317,55 @@ 317 317 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree// 318 318 319 319 415 +=== 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) === 320 320 321 -=== 2.3.3 Uplink FPORT~= , History GNSS Positioning === 322 322 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) 323 323 324 324 325 -=== 2.3.4 BLE positioning Payload(Fport2) === 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:"]] 326 326 429 +(% class="wikigeneratedid" %) 430 +[[image:1665301687277-443.png]] 327 327 328 -Different MODE has different payload: (% style="color:blue" %)**MODE=2** 329 329 433 +=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 434 + 435 + 436 +Set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery. 437 + 438 + 439 +(% style="color:red" %)**Note for this mode:** 440 + 441 +* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server. 442 +* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages. 443 +* c) the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes of payload. In this case (DR0 of US915/AU915), the payload on server will show NULL 444 + 445 +The payload is 15 bytes, as below. 446 + 447 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 448 +|=(% scope="row" %)((( 449 +**Size(bytes)** 450 +)))|4|4|2|1|1|1|1|1 451 +|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 452 + 453 +[[image:image-20221009160309-2.png]] 454 + 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 + 330 330 (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 331 331 |=(% scope="row" style="width: 60px;" %)((( 332 332 **Size(bytes)** ... ... @@ -346,21 +346,45 @@ 346 346 [[image:1664502425687-834.png]] 347 347 348 348 349 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 483 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 350 350 * (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 351 351 * (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 352 352 * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. 353 -* (% style="color:#037691" %)**MINOR:** (%%)The M AJOR487 +* (% style="color:#037691" %)**MINOR:** (%%)The MINOR from the strongest iBeacon. 354 354 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 355 355 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 356 356 357 357 358 358 359 -=== 2. 3.5AddPayload format inTTNV3===493 +=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 360 360 361 361 362 - InTTNV3,usecanaddacustompayloadso itshows friendly.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. 363 363 498 + 499 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %) 500 +|=(% scope="row" style="width: 60px;" %)((( 501 +**Size(bytes)** 502 +)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1 503 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)((( 504 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 505 +)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 506 + 507 +(% class="wikigeneratedid" %) 508 +[[image:1667288597595-714.png||height="212" width="1151"]] 509 + 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 + 364 364 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 365 365 366 366 ... ... @@ -367,50 +367,56 @@ 367 367 [[image:1664502649601-895.png]] 368 368 369 369 370 -Add the decoder from this link: 371 371 529 +Add the decoder from this link: 372 372 531 +[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] 532 + 373 373 Save the change the uplink message will be parsed. As below: 374 374 375 375 [[image:1664502676891-606.png]] 376 376 377 377 538 +== 2.5 Integrate with Datacake == 378 378 379 -== 2.4 Integrate with Datacake == 380 380 381 - 382 -((( 383 383 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. 384 -))) 385 385 386 -((( 387 387 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]] 388 -))) 389 389 390 390 391 391 [[image:1664502695771-538.png]] 392 392 393 393 549 +== 2.6 Integrate with Tago == 394 394 395 -== 2.5 Integrate with Tago == 396 396 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. 397 397 398 -((( 399 -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. 400 -))) 401 - 402 -((( 403 403 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]] 404 -))) 405 405 406 406 407 407 [[image:1664502715371-321.png]] 408 408 409 409 560 +== 2.7 Datalog Feature == 410 410 411 -== 2.6 Alarm Mode == 412 412 563 +total 273 entries,by default, 413 413 565 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 566 + 567 +Example use case. 568 + 569 +[[image:image-20221009234703-2.png||height="328" width="899"]] 570 + 571 + 572 +[[image:image-20221009234629-1.png||height="390" width="577"]] 573 + 574 + 575 +== 2.8 Alarm Mode == 576 + 577 + 414 414 ((( 415 415 User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 416 416 ))) ... ... @@ -417,15 +417,15 @@ 417 417 418 418 419 419 ((( 420 -Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exit alert mode. 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. 421 421 ))) 422 422 423 423 424 424 ((( 425 -Two ways to exit alarm mode: 589 +**Two ways to exit alarm mode:** 426 426 ))) 427 427 428 -* Server send a downlink command to exit. 592 +* Server sends a downlink command to exit. 429 429 * User fast press the RED button 10 times. 430 430 431 431 ((( ... ... @@ -433,21 +433,22 @@ 433 433 ))) 434 434 435 435 600 +== 2.9 Transport Mode == 436 436 437 -== 2.7 Sports Mode == 438 438 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. 439 439 440 440 441 -== 2. 8LED Status ==606 +== 2.10 LED Status == 442 442 443 443 444 -(% border="1.5" style="background-color:#ffffcc; color:green;width:500px" %)609 +(% border="1.5" style="background-color:#ffffcc; width:500px" %) 445 445 |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 446 446 |(% 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 447 447 |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes 448 448 |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A 449 449 |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes 450 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ** *(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes615 +|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes 451 451 |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes 452 452 |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes 453 453 |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes ... ... @@ -457,7 +457,7 @@ 457 457 458 458 459 459 460 -== 2. 9Button Function ==625 +== 2.11 Button Function == 461 461 462 462 463 463 (% style="color:blue" %)**RESET button:** ... ... @@ -472,15 +472,15 @@ 472 472 [[image:1664502854406-763.png]] 473 473 474 474 475 -(% border="1 .5" style="background-color:#ffffcc;color:green;width:520px" %)476 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 2 10px;" %)**Action**|=(% style="width: 210px;" %)**Description**477 -|(% 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"]]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"]] 478 478 |(% 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 479 479 |(% 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. 480 480 481 481 482 482 483 -== 2.1 0USB Port Function ==648 +== 2.12 USB Port Function == 484 484 485 485 486 486 The USB interface of TrackerD has below functions: ... ... @@ -500,7 +500,6 @@ 500 500 LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] 501 501 502 502 503 - 504 504 == 3.1 Access AT Command == 505 505 506 506 ... ... @@ -516,11 +516,9 @@ 516 516 [[image:1664503022490-662.png]] 517 517 518 518 519 - 520 520 [[image:1664503035713-500.png]] 521 521 522 522 523 - 524 524 [[image:1664503047675-651.png]] 525 525 526 526 ... ... @@ -527,7 +527,6 @@ 527 527 528 528 == 3.2 Command Set == 529 529 530 - 531 531 === 3.2.1 Set Transmit Interval === 532 532 533 533 ... ... @@ -545,7 +545,6 @@ 545 545 (% style="color:#037691" %)**0x01 00 01 2C** (%%) ~/~/ Same as AT+TDC=300000 546 546 547 547 548 - 549 549 === 3.2.2 Set Alarm Packet transmission interval === 550 550 551 551 ... ... @@ -563,25 +563,23 @@ 563 563 (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/ Same as AT+ATDC=60000 564 564 565 565 726 +=== 3.2.3 Set Transport Mode Packet transmission interval === 566 566 567 -=== 3.2.3 Set Sports Mode Packet transmission interval === 568 568 729 +Set Transport Mode packet transmit interval 569 569 570 -Set sports packet transmit interval 571 - 572 572 * (% style="color:blue" %)**AT Command:** 573 573 574 574 (% style="color:#037691" %)**AT+MTDC=xx. ** 575 575 576 -Example: AT+MTDC=300000 **~-~-> ** Set SportsMode Packet Interval to 300 seconds. TrackerD will send every 300 seconds inSportsmode, Default Value: 300000735 +Example: AT+MTDC=300000 **~-~-> ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000 577 577 578 578 579 579 * (% style="color:blue" %)**Downlink Payload (prefix 0x03):** 580 580 581 -(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+ 740 +(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+MTDC=3000000 582 582 583 583 584 - 585 585 === 3.2.4 Exit Alarm === 586 586 587 587 ... ... @@ -594,7 +594,6 @@ 594 594 (% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 595 595 596 596 597 - 598 598 === 3.2.5 Disable/Enable LED flash === 599 599 600 600 ... ... @@ -612,60 +612,69 @@ 612 612 (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/ Same as AT+LON=0 613 613 614 614 772 +=== 3.2.6 Disable/Enable Transport Mode === 615 615 616 -=== 3.2.6 Disable/Enable movement detect (Debug Only) === 617 617 775 +Users can use this feature to enable/disable Transport Mode. 618 618 619 -User can use this feature to check and set thread hole of movement detect 620 - 621 621 * (% style="color:blue" %)**AT Command:** 622 622 623 623 (% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)** 624 624 625 -Example: AT+ detectmovement.781 +Example: AT+INTWK=1 **~-~-> ** Enable Transport Mode. 626 626 627 627 628 628 * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):** 629 629 630 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+ 786 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+INTWK=1 631 631 632 632 633 - 634 634 === 3.2.7 Set Positioning Mode === 635 635 636 636 637 -SMOD define the how TrackerD scan and uplink date.792 +SMOD define how TrackerD scan and uplink data: 638 638 639 -GPS室外定位模式: 设备默认模式,设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是3分钟定位,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。GPS还有一种logdata模式,在断网的情况下将数据存储下来,等到有网的时候,一次将数据以每10秒上报。 640 640 641 - BLE室内定位模式:设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是5秒,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每3分钟发送一次)。795 +* (% style="color:blue" %)**AT Command:** 642 642 643 - GPS和BLE混动模式:设备入网后会发送device当前模式下的信息,随后立即判断是否在室内,如果是就进行BLE定位,不是就GPS定位。如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。797 +(% style="color:#037691" %)**AT+SMOD=aa,bb,cc** 644 644 645 - 运动模式:设备入网后会发送device当前模式下的信息,随后发送GPS定位数据,设备判断是否在运动,没有运动传感器没有检测到动作,立即进入静止状态(默认20分钟),如果产生运动,将每5分钟发送一次数据,再第五分钟后检测设备有误运动,无将切换到静止状态,有立即发送数据。799 +(% style="color:#037691" %)** aa:** 646 646 801 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 647 647 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. 648 648 649 -* (% style="color: blue" %)**ATCommand:**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. 650 650 651 -(% style="color:#037691" %)** AT+SMOD=xx.**807 +(% style="color:#037691" %)**bb:** 652 652 809 +* (% style="color:red" %)**0 : **(%%)GPS+ BAT+ State+Tem&Hum 653 653 654 - *Example:**811 +* (% style="color:red" %)**1 :**(%%) GPS +BAT State 655 655 656 - AT+ SMOD=1,0~-~->**GPS+ BAT+ State+Tem&Hum813 +(% style="color:#037691" %)**cc: ** 657 657 658 - AT+ SMOD =1,1 **~-~->** GPS +BAT State 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(%%)) 659 659 660 - AT+ SMOD =2,3 **~-~->**(iBeacon)UUID+ Major+ Minor+Power+Rssi+BAT+State。819 +(% style="color:blue" %)**Example:** 661 661 821 + AT+SMOD=1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 662 662 663 - *(%style="color:blue"%)**DownlinkPayload(prefix0xA5):**823 + AT+SMOD=1,1,0 ~-~-> GPS +BAT State 664 664 665 - (%style="color:#037691"%)**0xA50100**(%%)/~/Same asAT+MOD =1,0825 + AT+SMOD=2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 666 666 827 + AT+SMOD=2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State 667 667 668 668 830 +* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** 831 + 832 +(% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+SMOD=1,0,0 833 + 834 + 669 669 === 3.2.8 Set MAX GPS position time === 670 670 671 671 ... ... @@ -672,7 +672,7 @@ 672 672 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. 673 673 674 674 675 -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. 676 676 677 677 678 678 * (% style="color:blue" %)**AT Command:** ... ... @@ -679,7 +679,7 @@ 679 679 680 680 (% style="color:#037691" %)**AT+FTIME=xx** (%%) **~-~-> ** Set to use xx as max fix time. 681 681 682 -Example: AT+FTIME=150 848 +**Example:** AT+FTIME=150 683 683 684 684 685 685 * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):** ... ... @@ -687,10 +687,9 @@ 687 687 (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/ Set AT+FTIME=150 688 688 689 689 856 +=== 3.2.9 Set PDOP value for GPS fix accuracy === 690 690 691 -=== 3.3.9 Set PDOP value for GPS fix accuracy === 692 692 693 - 694 694 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. 695 695 696 696 ... ... @@ -712,26 +712,108 @@ 712 712 713 713 714 714 715 -Disable/Enable the confirmation mode 880 +**Disable/Enable the confirmation mode** 716 716 717 717 * (% style="color:blue" %)**AT Command:** 718 718 719 -(% style="color:#037691" %)**AT+CFM=xx .**884 +(% style="color:#037691" %)**AT+CFM=xx** 720 720 721 721 722 722 **~ Example:** 723 723 724 - AT+ 889 + AT+CFM=0 **~-~-> ** Disable confirmation 725 725 726 - AT+ 891 + AT+CFM=1 **~-~-> ** Enable confirmation 727 727 728 728 729 729 * (% style="color:blue" %)**Downlink Payload (prefix 0x05):** 730 730 731 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+ SMOD=1896 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1 732 732 733 733 899 +=== 3.2.10 Auto Send None-ACK messages === 734 734 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 + 735 735 = 4. Setting for Different Scenarios = 736 736 737 737 ... ... @@ -738,7 +738,6 @@ 738 738 739 739 = 5. Upload Firmware = 740 740 741 - 742 742 == 5.1 Firmware Change Log == 743 743 744 744 ... ... @@ -745,7 +745,6 @@ 745 745 **[[See this link>>url:https://github.com/dragino/TrackerD]]** 746 746 747 747 748 - 749 749 == 5.2 How to upgrade firmware == 750 750 751 751 ... ... @@ -772,34 +772,33 @@ 772 772 [[image:1664503574618-659.png]] 773 773 774 774 1020 + 775 775 (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 776 776 777 -[[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]] 778 778 779 779 780 -Users need to use below files: 1026 +**Users need to use below files:** 781 781 782 782 boot_app0.bin @0e000 783 783 784 - ESP_LORA-eeprom-class.bin @ 0x100001030 +US915.bin @ 0x10000(Select the bin file of the frequency band you need) 785 785 786 786 787 -[[image:1 664503593459-435.png]]1033 +[[image:image-20221118105220-2.png]] 788 788 789 789 790 790 791 791 After upgrade finish, it will show finish as below: 792 792 793 -[[image: 1664503611848-385.png]]1039 +[[image:image-20221118105402-4.png]] 794 794 795 795 796 796 797 797 = 6. Developer Guide = 798 798 799 - 800 800 == 6.1 Compile Source Code == 801 801 802 - 803 803 === 6.1.1 Set up ARDUINO compile environment === 804 804 805 805 ... ... @@ -811,12 +811,24 @@ 811 811 [[image:1664503635019-941.png]] 812 812 813 813 1058 + 814 814 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 815 815 816 816 [[image:1664503715811-892.png]] 817 817 818 818 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. 819 819 1066 +[[image:image-20221024105643-1.png]] 1067 + 1068 +**~ Figure1** 1069 + 1070 + 1071 +[[image:image-20221024105643-2.png]] 1072 + 1073 + **Figure2** 1074 + 1075 + 820 820 * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]** 821 821 822 822 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: ... ... @@ -825,7 +825,6 @@ 825 825 [[image:1664503752288-974.png]] 826 826 827 827 828 - 829 829 == 6.2 Source Code == 830 830 831 831 ... ... @@ -846,10 +846,8 @@ 846 846 [[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 847 847 848 848 849 - 850 850 = 7. FAQ = 851 851 852 - 853 853 == 7.1 How to change the LoRa Frequency Bands/Region? == 854 854 855 855 ... ... @@ -856,7 +856,6 @@ 856 856 User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download. 857 857 858 858 859 - 860 860 == 7.2 What is the pin mapping for the USB program cable? == 861 861 862 862 ... ... @@ -877,52 +877,243 @@ 877 877 878 878 879 879 1132 +== 7.3 Notes on using different serial port tools for TrackerD == 880 880 881 -= 8.OrderInfo =1134 +=== 7.3.1 Serial port utility === 882 882 883 883 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 + 884 884 Part Number: (% style="color:blue" %)**TrackerD-XXX** 885 885 886 886 (% style="color:blue" %)**XXX**(%%): The default frequency band 887 887 888 888 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433 1323 + 889 889 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868 1325 + 890 890 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865 1327 + 891 891 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920 1329 + 892 892 * (% style="color:red" %)**AS923**(%%): Default frequency band AS923 1331 + 893 893 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 1333 + 894 894 * (% style="color:red" %)**US915**(%%): Default frequency band US915 895 895 896 896 897 897 898 -= 9. Packing Info =1338 += 10. Packing Info = 899 899 900 900 901 901 (% style="color:#037691" %)**Package Includes**: 902 902 903 903 * TrackerD LoRaWAN GPS/BLE Tracker x 1 1344 + 904 904 * USB recharge & program cable x 1 905 905 906 906 (% style="color:#037691" %)**Dimensions and Weight**: 907 907 908 -* Device Size: 85 x 48 x 15 cm 1349 +* Device Size: 85 x 48 x 15 mm 1350 + 909 909 * Weight: 50g 910 910 911 911 912 912 913 -= 1 0. Support =1355 += 11. Support = 914 914 915 915 916 916 * 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. 1359 + 917 917 * 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]]. 918 918 919 919 920 920 921 -= 1 1. Reference =1364 += 12. Reference = 922 922 923 923 924 924 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1368 + 925 925 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 926 -* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 927 927 928 - 1371 +* [[**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