Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Bei Jinggeng on 2025/08/01 17:45
From version 59.2
edited by Edwin Chen
on 2022/10/08 17:55
on 2022/10/08 17:55
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 31 added, 0 removed)
- 1665301570342-765.png
- 1665301636888-168.png
- 1665301687277-443.png
- 1665301786397-168.png
- 1667288597595-714.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
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.Xiaoling - Content
-
... ... @@ -1,5 +3,3 @@ 1 -== == 2 - 3 3 (% style="text-align:center" %) 4 4 [[image:1664505654417-133.png]] 5 5 ... ... @@ -16,7 +16,6 @@ 16 16 17 17 = 1. Introduction = 18 18 19 - 20 20 == 1.1 What is TrackerD == 21 21 22 22 ... ... @@ -48,7 +48,6 @@ 48 48 (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.** 49 49 50 50 51 - 52 52 == 1.2 Specifications == 53 53 54 54 ... ... @@ -99,6 +99,8 @@ 99 99 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm 100 100 * Tracking: max: 38mA 101 101 98 + 99 + 102 102 == 1.3 Features == 103 103 104 104 ... ... @@ -117,6 +117,8 @@ 117 117 * Tri-color LED, Alarm button 118 118 * Datalog 119 119 118 + 119 + 120 120 == 1.4 Applications == 121 121 122 122 ... ... @@ -123,9 +123,10 @@ 123 123 * Logistics and Supply Chain Management 124 124 * Human tracking 125 125 126 -= 2.1 Use TrackerD = 127 127 128 128 128 += 2. Use TrackerD = 129 + 129 129 == 2.1 How it works? == 130 130 131 131 ... ... @@ -132,7 +132,6 @@ 132 132 TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA. 133 133 134 134 135 - 136 136 == 2.2 Quick guide to connect to LoRaWAN server == 137 137 138 138 ... ... @@ -174,48 +174,57 @@ 174 174 **__Add APP KEY and DEV EUI:__** 175 175 176 176 177 -[[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"]] 178 178 179 179 180 180 181 +(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device. 181 181 182 -(% style=" color:blue" %)**Step2**:(%%) Power on TrackerD by usingtheon board switch.183 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]] 183 183 185 +[[image:1664502835802-546.png]] 184 184 187 + 185 185 (% 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. 186 186 187 187 188 -== 2.3 Positioning Mode(SMOD) == 191 +== 2.3 Positioning Mode(SMOD) == 189 189 193 + 190 190 Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 191 191 192 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%) only get and uplink GPS location info.193 -* (% style="color:#037691" %)**BLE ONLY: 194 -* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 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. 195 195 196 196 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 197 197 198 198 199 -== 2. 3203 +== 2.4 Uplink Payload == 200 200 205 +=== 2.4.1 Uplink FPORT~=5, Device Status === 201 201 202 -=== 2.3.1 Uplink FPORT~=5, Device Status === 203 203 204 -Uplink the device configures with FPORT=5. Once LGT92Joined the network, it will uplink this message to the server. After first uplink,LHT52will uplink Device Status every 12 hours.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. 205 205 206 -|=(% style="width: 150px;" %)**Size (bytes)**|=(% style="width: 233px;" %)**1**|=(% style="width: 150px;" %)**2**|=(% style="width: 164px;" %)**1**|=(% style="width: 215px;" %)**1**|=(% style="width: 94px;" %)2|=(% style="width: 516px;" %)**2**|=(% style="width: 516px;" %)1 207 -|(% style="width:150px" %)**Value**|(% style="width:233px" %)Sensor Model|(% style="width:150px" %)Firmware Version|(% style="width:164px" %)Frequency Band|(% style="width:215px" %)Sub-band|(% style="width:94px" %)BAT|(% style="width:516px" %)SMOD|(% style="width:516px" %)Status 210 +Use can also get the Device Status uplink through the downlink command: **Downlink: 0x2301** 208 208 209 -[[image:image-20221006181357-2.png]] 210 210 211 -Example Payload (FPort=5): [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT52%20-%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20User%20Manual/WebHome/image-20220621105116-11.png?rev=1.1||alt="image-20220621105116-11.png"]] 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 212 212 213 - **Sensor Model**: For TrackerD, this valueis0x13.217 +[[image:1665301570342-765.png]] 214 214 215 -**Firmware Version**: 0x0100, Means: v1.0.0 version. 216 216 217 -** FrequencyBand**:220 +(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002 218 218 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 + 219 219 *0x01: EU868 220 220 221 221 *0x02: US915 ... ... @@ -236,27 +236,65 @@ 236 236 237 237 *0x0a: AS923-3 238 238 239 - **Sub-Band**:CN470,AU915,US915.Others are0x00)248 +Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF) 240 240 241 -**BAT** :shows the battery voltage for TrackerD.250 +(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD. 242 242 243 -Ex1: 0x0B3A = 2874mV 244 244 253 +(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV 254 + 245 245 Use can also get the Device Status uplink through the downlink command: 246 246 247 247 248 - ===2.3.2 Uplink FPORT~=2, RealtimeGNSSPositioning + Temperature&Humidity===258 +(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40 249 249 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 250 250 251 -( Usercan use AT+SMOD=1,0to enable uploading on-board Temperature and humidityvalue, and totalpayload willbe 15 bytes, pleasenote15byteswon'tworkon DR0 on US915/AU915 frequency band. )264 +(% style="color:blue" %)** SMOD:** 252 252 266 +(% style="color:red" %)** 1 :** (%%) GPS ONLY 253 253 254 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) 255 -|=(% scope="row" style="width: 50px;" %)((( 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;" %)((( 256 256 **Size(bytes)** 257 -)))|(% style="width: 60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((304 +)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)((( 258 258 2 259 -)))|(% style="width: 87px" %)(((306 +)))|(% style="width:30px" %)((( 260 260 2 261 261 ))) 262 262 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( ... ... @@ -263,7 +263,7 @@ 263 263 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 264 264 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 265 265 266 -[[image:166 4501958445-288.png]]313 +[[image:1665301636888-168.png]] 267 267 268 268 269 269 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== ... ... @@ -272,11 +272,13 @@ 272 272 |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits 273 273 |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 274 274 322 + 323 + 275 275 ==== (% style="color:blue" %)**FLAG:**(%%) ==== 276 276 277 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:2 50px" %)278 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width: 50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits279 -|=(% 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:"]] 280 280 281 281 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 282 282 ... ... @@ -290,15 +290,14 @@ 290 290 291 291 1. When power is low (<2.84v), GPS won't be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF. 292 292 293 -2. Whenenable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below: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: 294 294 295 295 296 296 [[image:1664502116362-706.png]] 297 297 298 298 348 +3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 299 299 300 -4. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 301 - 302 302 [[image:1664502166010-515.png]] 303 303 304 304 ... ... @@ -305,15 +305,15 @@ 305 305 306 306 ==== (% style="color:blue" %)**Alarm:**(%%) ==== 307 307 308 -Example: 356 +**Example: ** 0x4B & 0x40 >> 6 = 0x01 309 309 310 310 311 311 ==== (% style="color:blue" %)**BAT:**(%%) ==== 312 312 313 -Example: 0CDD& 0x3FFF ⇒3293(mV).361 +**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV). 314 314 315 315 ((( 316 -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: \ 317 317 ))) 318 318 319 319 * > 4.0v : 80% ~~ 100% ... ... @@ -322,16 +322,35 @@ 322 322 * 3.40v ~~ 3.69v: 20% ~~ 40% 323 323 * < 3.39v: 0~~20% 324 324 373 + 374 + 375 +==== (% style="color:blue" %)**MOD:**(%%) ==== 376 + 377 +**Example: ** (0x60>>6) & 0x3f =1 378 + 379 +**Set the format of GPS data uplink link:** 380 + 381 +(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values 382 +(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values 383 + 384 + 385 +**Set the format of BLE data uplink link:** 386 + 387 +(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon 388 + 389 + 325 325 ==== (% style="color:blue" %)**LON:**(%%) ==== 326 326 392 +**Example:** (0x60>>5) & 0x01=1. 393 + 327 327 Enable/Disable LED activity for uplink 328 328 329 329 ((( 330 -0x00: Disable LED indicator. 397 +(% style="color:#037691" %)**0x00:** (%%) Disable LED indicator. 331 331 ))) 332 332 333 333 ((( 334 -0x01: Enable LED indicator (Default Value) 401 +(% style="color:#037691" %)**0x01:** (%%) Enable LED indicator (Default Value) 335 335 ))) 336 336 337 337 ... ... @@ -345,30 +345,55 @@ 345 345 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree// 346 346 347 347 348 -=== 2. 3.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===415 +=== 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) === 349 349 350 -The default uplink payload includes totally 11 bytes. The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity) 351 351 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) 352 352 353 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) 354 -|=(% scope="row" style="width: 50px;" %)((( 420 + 421 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %) 422 +|=(% scope="row" style="width: 60px;" %)((( 355 355 **Size(bytes)** 356 -)))|(% style="width:60px" %)4|(% style="width: 70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1424 +)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1 357 357 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 358 358 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 359 359 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 360 360 429 +(% class="wikigeneratedid" %) 430 +[[image:1665301687277-443.png]] 361 361 362 362 363 -=== 2. 3. Uplink FPORT~=433 +=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 364 364 365 365 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. 366 366 367 -=== 2.3.4 BLE positioning Payload(Fport2) === 368 368 439 +(% style="color:red" %)**Note for this mode:** 369 369 370 -Different MODE has different payload: (% style="color:blue" %)**MODE=2** 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 371 371 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 + 372 372 (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 373 373 |=(% scope="row" style="width: 60px;" %)((( 374 374 **Size(bytes)** ... ... @@ -388,19 +388,45 @@ 388 388 [[image:1664502425687-834.png]] 389 389 390 390 391 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 483 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 392 392 * (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 393 393 * (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 394 394 * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. 395 -* (% style="color:#037691" %)**MINOR:** (%%)The M AJOR487 +* (% style="color:#037691" %)**MINOR:** (%%)The MINOR from the strongest iBeacon. 396 396 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 397 397 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 398 398 399 -=== 2.3.5 Add Payload format in TTN V3 === 400 400 401 401 402 - In TTN V3,usecan add a custompayload soitshows friendly.493 +=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 403 403 495 + 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. 497 + 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 + 404 404 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 405 405 406 406 ... ... @@ -407,53 +407,56 @@ 407 407 [[image:1664502649601-895.png]] 408 408 409 409 410 -Add the decoder from this link: 411 411 529 +Add the decoder from this link: 412 412 531 +[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] 532 + 413 413 Save the change the uplink message will be parsed. As below: 414 414 415 415 [[image:1664502676891-606.png]] 416 416 417 417 538 +== 2.5 Integrate with Datacake == 418 418 419 -== 2.4 Integrate with Datacake == 420 420 421 - 422 -((( 423 423 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. 424 -))) 425 425 426 -((( 427 427 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]] 428 -))) 429 429 430 430 431 431 [[image:1664502695771-538.png]] 432 432 433 433 549 +== 2.6 Integrate with Tago == 434 434 435 -== 2.5 Integrate with Tago == 436 436 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. 437 437 438 -((( 439 -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. 440 -))) 441 - 442 -((( 443 443 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]] 444 -))) 445 445 446 446 447 447 [[image:1664502715371-321.png]] 448 448 449 449 560 +== 2.7 Datalog Feature == 450 450 451 -== 2.6 Datalog Feature == 452 452 563 +total 273 entries,by default, 453 453 454 - ==2.6AlarmMode==565 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature. 455 455 567 +Example use case. 456 456 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 + 457 457 ((( 458 458 User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 459 459 ))) ... ... @@ -460,15 +460,15 @@ 460 460 461 461 462 462 ((( 463 -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. 464 464 ))) 465 465 466 466 467 467 ((( 468 -Two ways to exit alarm mode: 589 +**Two ways to exit alarm mode:** 469 469 ))) 470 470 471 -* Server send a downlink command to exit. 592 +* Server sends a downlink command to exit. 472 472 * User fast press the RED button 10 times. 473 473 474 474 ((( ... ... @@ -476,23 +476,22 @@ 476 476 ))) 477 477 478 478 600 +== 2.9 Transport Mode == 479 479 480 -== 2.7 Transport Mode == 481 481 482 - 483 483 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. 484 484 485 485 486 -== 2. 8LED Status ==606 +== 2.10 LED Status == 487 487 488 488 489 -(% border="1.5" style="background-color:#ffffcc; color:green;width:500px" %)609 +(% border="1.5" style="background-color:#ffffcc; width:500px" %) 490 490 |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 491 491 |(% 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 492 492 |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes 493 493 |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A 494 494 |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes 495 -|(% 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 496 496 |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes 497 497 |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes 498 498 |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes ... ... @@ -500,9 +500,11 @@ 500 500 |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 501 501 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 502 502 503 -== 2.9 Button Function == 504 504 505 505 625 +== 2.11 Button Function == 626 + 627 + 506 506 (% style="color:blue" %)**RESET button:** 507 507 508 508 [[image:1664502835802-546.png]] ... ... @@ -515,15 +515,17 @@ 515 515 [[image:1664502854406-763.png]] 516 516 517 517 518 -(% border="1 .5" style="background-color:#ffffcc;color:green;width:520px" %)519 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 2 10px;" %)**Action**|=(% style="width: 210px;" %)**Description**520 -|(% 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"]] 521 521 |(% 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 522 522 |(% 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. 523 523 524 -== 2.10 USB Port Function == 525 525 526 526 648 +== 2.12 USB Port Function == 649 + 650 + 527 527 The USB interface of TrackerD has below functions: 528 528 529 529 * Power on the device ... ... @@ -531,6 +531,8 @@ 531 531 * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]] 532 532 * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]] 533 533 658 + 659 + 534 534 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 535 535 536 536 ... ... @@ -539,7 +539,6 @@ 539 539 LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] 540 540 541 541 542 - 543 543 == 3.1 Access AT Command == 544 544 545 545 ... ... @@ -555,11 +555,9 @@ 555 555 [[image:1664503022490-662.png]] 556 556 557 557 558 - 559 559 [[image:1664503035713-500.png]] 560 560 561 561 562 - 563 563 [[image:1664503047675-651.png]] 564 564 565 565 ... ... @@ -566,7 +566,6 @@ 566 566 567 567 == 3.2 Command Set == 568 568 569 - 570 570 === 3.2.1 Set Transmit Interval === 571 571 572 572 ... ... @@ -584,7 +584,6 @@ 584 584 (% style="color:#037691" %)**0x01 00 01 2C** (%%) ~/~/ Same as AT+TDC=300000 585 585 586 586 587 - 588 588 === 3.2.2 Set Alarm Packet transmission interval === 589 589 590 590 ... ... @@ -602,7 +602,6 @@ 602 602 (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/ Same as AT+ATDC=60000 603 603 604 604 605 - 606 606 === 3.2.3 Set Transport Mode Packet transmission interval === 607 607 608 608 ... ... @@ -617,10 +617,9 @@ 617 617 618 618 * (% style="color:blue" %)**Downlink Payload (prefix 0x03):** 619 619 620 -(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+ 740 +(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+MTDC=3000000 621 621 622 622 623 - 624 624 === 3.2.4 Exit Alarm === 625 625 626 626 ... ... @@ -633,7 +633,6 @@ 633 633 (% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 634 634 635 635 636 - 637 637 === 3.2.5 Disable/Enable LED flash === 638 638 639 639 ... ... @@ -651,7 +651,6 @@ 651 651 (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/ Same as AT+LON=0 652 652 653 653 654 - 655 655 === 3.2.6 Disable/Enable Transport Mode === 656 656 657 657 ... ... @@ -661,41 +661,60 @@ 661 661 662 662 (% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)** 663 663 664 -Example: AT+ 781 +Example: AT+INTWK=1 **~-~-> ** Enable Transport Mode. 665 665 666 666 667 667 * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):** 668 668 669 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+ 786 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+INTWK=1 670 670 671 671 672 - 673 673 === 3.2.7 Set Positioning Mode === 674 674 675 675 676 -SMOD define the how TrackerD scan and uplink data:792 +SMOD define how TrackerD scan and uplink data: 677 677 678 678 679 679 * (% style="color:blue" %)**AT Command:** 680 680 681 -(% style="color:#037691" %)**AT+SMOD= xx.**797 +(% style="color:#037691" %)**AT+SMOD=aa,bb,cc** 682 682 799 +(% style="color:#037691" %)** aa:** 683 683 684 - ** Example:**801 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 685 685 686 - AT+SMOD=1,0**~-~->**GPS+BAT+State+Tem&Hum803 +* (% 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. 687 687 688 - AT+SMOD=1,1**~-~->**GPS+BATState805 +* (% 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. 689 689 690 - AT+ SMOD=2,3~-~->**(iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。807 +(% style="color:#037691" %)**bb:** 691 691 809 +* (% style="color:red" %)**0 : **(%%)GPS+ BAT+ State+Tem&Hum 692 692 693 -* (% style="color: blue" %)**DownlinkPayload (prefix 0xA5):**811 +* (% style="color:red" %)**1 :**(%%) GPS +BAT State 694 694 695 -(% style="color:#037691" %)** 0xA5 01 00**(%%) ~/~/ Same as AT+ SMOD =1,0813 +(% style="color:#037691" %)**cc: ** 696 696 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(%%)) 697 697 819 +(% style="color:blue" %)**Example:** 698 698 821 + AT+SMOD=1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 822 + 823 + AT+SMOD=1,1,0 ~-~-> GPS +BAT State 824 + 825 + AT+SMOD=2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 826 + 827 + AT+SMOD=2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State 828 + 829 + 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 + 699 699 === 3.2.8 Set MAX GPS position time === 700 700 701 701 ... ... @@ -702,7 +702,7 @@ 702 702 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. 703 703 704 704 705 -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. 706 706 707 707 708 708 * (% style="color:blue" %)**AT Command:** ... ... @@ -709,7 +709,7 @@ 709 709 710 710 (% style="color:#037691" %)**AT+FTIME=xx** (%%) **~-~-> ** Set to use xx as max fix time. 711 711 712 -Example: AT+FTIME=150 848 +**Example:** AT+FTIME=150 713 713 714 714 715 715 * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):** ... ... @@ -717,10 +717,9 @@ 717 717 (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/ Set AT+FTIME=150 718 718 719 719 856 +=== 3.2.9 Set PDOP value for GPS fix accuracy === 720 720 721 -=== 3.3.9 Set PDOP value for GPS fix accuracy === 722 722 723 - 724 724 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. 725 725 726 726 ... ... @@ -742,26 +742,108 @@ 742 742 743 743 744 744 745 -Disable/Enable the confirmation mode 880 +**Disable/Enable the confirmation mode** 746 746 747 747 * (% style="color:blue" %)**AT Command:** 748 748 749 -(% style="color:#037691" %)**AT+CFM=xx .**884 +(% style="color:#037691" %)**AT+CFM=xx** 750 750 751 751 752 752 **~ Example:** 753 753 754 - AT+ 889 + AT+CFM=0 **~-~-> ** Disable confirmation 755 755 756 - AT+ 891 + AT+CFM=1 **~-~-> ** Enable confirmation 757 757 758 758 759 759 * (% style="color:blue" %)**Downlink Payload (prefix 0x05):** 760 760 761 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+ SMOD=1896 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM=1 762 762 763 763 899 +=== 3.2.10 Auto Send None-ACK messages === 764 764 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 + 765 765 = 4. Setting for Different Scenarios = 766 766 767 767 ... ... @@ -768,7 +768,6 @@ 768 768 769 769 = 5. Upload Firmware = 770 770 771 - 772 772 == 5.1 Firmware Change Log == 773 773 774 774 ... ... @@ -775,7 +775,6 @@ 775 775 **[[See this link>>url:https://github.com/dragino/TrackerD]]** 776 776 777 777 778 - 779 779 == 5.2 How to upgrade firmware == 780 780 781 781 ... ... @@ -802,34 +802,33 @@ 802 802 [[image:1664503574618-659.png]] 803 803 804 804 1020 + 805 805 (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 806 806 807 -[[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]] 808 808 809 809 810 -Users need to use below files: 1026 +**Users need to use below files:** 811 811 812 812 boot_app0.bin @0e000 813 813 814 - ESP_LORA-eeprom-class.bin @ 0x100001030 +US915.bin @ 0x10000(Select the bin file of the frequency band you need) 815 815 816 816 817 -[[image:1 664503593459-435.png]]1033 +[[image:image-20221118105220-2.png]] 818 818 819 819 820 820 821 821 After upgrade finish, it will show finish as below: 822 822 823 -[[image: 1664503611848-385.png]]1039 +[[image:image-20221118105402-4.png]] 824 824 825 825 826 826 827 827 = 6. Developer Guide = 828 828 829 - 830 830 == 6.1 Compile Source Code == 831 831 832 - 833 833 === 6.1.1 Set up ARDUINO compile environment === 834 834 835 835 ... ... @@ -841,12 +841,24 @@ 841 841 [[image:1664503635019-941.png]] 842 842 843 843 1058 + 844 844 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 845 845 846 846 [[image:1664503715811-892.png]] 847 847 848 848 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. 849 849 1066 +[[image:image-20221024105643-1.png]] 1067 + 1068 +**~ Figure1** 1069 + 1070 + 1071 +[[image:image-20221024105643-2.png]] 1072 + 1073 + **Figure2** 1074 + 1075 + 850 850 * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]** 851 851 852 852 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: ... ... @@ -855,7 +855,6 @@ 855 855 [[image:1664503752288-974.png]] 856 856 857 857 858 - 859 859 == 6.2 Source Code == 860 860 861 861 ... ... @@ -876,10 +876,8 @@ 876 876 [[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 877 877 878 878 879 - 880 880 = 7. FAQ = 881 881 882 - 883 883 == 7.1 How to change the LoRa Frequency Bands/Region? == 884 884 885 885 ... ... @@ -886,7 +886,6 @@ 886 886 User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download. 887 887 888 888 889 - 890 890 == 7.2 What is the pin mapping for the USB program cable? == 891 891 892 892 ... ... @@ -905,45 +905,245 @@ 905 905 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 906 906 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 907 907 908 -= 8. Order Info = 909 909 910 910 1132 +== 7.3 Notes on using different serial port tools for TrackerD == 1133 + 1134 +=== 7.3.1 Serial port utility === 1135 + 1136 + 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 + 911 911 Part Number: (% style="color:blue" %)**TrackerD-XXX** 912 912 913 913 (% style="color:blue" %)**XXX**(%%): The default frequency band 914 914 915 915 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433 1323 + 916 916 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868 1325 + 917 917 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865 1327 + 918 918 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920 1329 + 919 919 * (% style="color:red" %)**AS923**(%%): Default frequency band AS923 1331 + 920 920 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 1333 + 921 921 * (% style="color:red" %)**US915**(%%): Default frequency band US915 922 922 923 -= 9. Packing Info = 924 924 925 925 1338 += 10. Packing Info = 1339 + 1340 + 926 926 (% style="color:#037691" %)**Package Includes**: 927 927 928 928 * TrackerD LoRaWAN GPS/BLE Tracker x 1 1344 + 929 929 * USB recharge & program cable x 1 930 930 931 931 (% style="color:#037691" %)**Dimensions and Weight**: 932 932 933 -* Device Size: 85 x 48 x 15 cm 1349 +* Device Size: 85 x 48 x 15 mm 1350 + 934 934 * Weight: 50g 935 935 936 -= 10. Support = 937 937 938 938 1355 += 11. Support = 1356 + 1357 + 939 939 * 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 + 940 940 * 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]]. 941 941 942 -= 11. Reference = 943 943 944 944 1364 += 12. Reference = 1365 + 1366 + 945 945 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1368 + 946 946 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 947 -* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 948 948 949 - 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-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