Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Bei Jinggeng on 2025/07/23 11:03
From version 113.6
edited by Xiaoling
on 2022/11/09 16:59
on 2022/11/09 16:59
Change comment:
There is no comment for this version
To version 53.1
edited by Edwin Chen
on 2022/10/06 18:13
on 2022/10/06 18:13
Change comment:
Uploaded new attachment "image-20221006181316-1.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 19 removed)
- 1665301570342-765.png
- 1665301636888-168.png
- 1665301687277-443.png
- 1665301786397-168.png
- 1667288597595-714.png
- image-20221006181357-2.png
- image-20221009160220-1.png
- image-20221009160309-2.png
- image-20221009234629-1.png
- image-20221009234703-2.png
- image-20221024105643-1.png
- image-20221024105643-2.png
- image-20221102140621-1.png
- image-20221102140638-2.png
- image-20221102140704-3.png
- image-20221102140712-4.png
- image-20221102140748-5.png
- image-20221102140801-6.png
- image-20221107145243-1.png
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Edwin - Content
-
... ... @@ -124,7 +124,7 @@ 124 124 * Human tracking 125 125 126 126 127 -= 2. 127 += 2.1 Use TrackerD = 128 128 129 129 130 130 == 2.1 How it works? == ... ... @@ -175,10 +175,11 @@ 175 175 **__Add APP KEY and DEV EUI:__** 176 176 177 177 178 -[[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 +[[image:1664501784668-703.png]] 179 179 180 180 181 181 182 + 182 182 (% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch. 183 183 184 184 ... ... @@ -185,131 +185,42 @@ 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 189 += 2.3 Positioning Mode(SMOD) = 188 188 189 -== 2.3 Positioning Mode(SMOD) == 191 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)only get GPS location info. 192 +* (% style="color:#037691" %)**BLE ONLY: **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking. 193 +* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking. 190 190 195 +User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 191 191 192 -Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 193 193 194 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 195 -* (% 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. 196 -* (% 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. 197 197 198 - Userscanswitchmodes by [[changingSMOD>>||anchor="H3.2.7SetPositioningMode"]].199 +== 2.3 Uplink Payload == 199 199 200 200 202 +=== 2.3.1 Uplink FPORT~=5, Device Status === 201 201 202 -== 2.4 Uplink Payload == 203 203 204 204 205 -=== 2. 4.1Uplink FPORT~=5,Device Status ===206 +=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning === 206 206 207 207 208 - Uplink the deviceconfigureswithFPORT=5.OnceTrackerDJoinedthenetwork, itwilluplinkthismessage totheserver.Afterthe firstuplink,TrackerDwilluplink DeviceStatusevery12hours.209 +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. ) 209 209 210 -Use can also get the Device Status uplink through the downlink command: **Downlink: 0x2301** 211 211 212 - 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 216 - 217 -[[image:1665301570342-765.png]] 218 - 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 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 295 - 296 - 297 -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, 298 - 299 - 300 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %) 301 -|=(% scope="row" style="width: 60px;" %)((( 212 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) 213 +|=(% scope="row" style="width: 50px;" %)((( 302 302 **Size(bytes)** 303 -)))|(% style="width: 50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((304 -2 305 -)))|(% style="width: 30px" %)(((306 -2 215 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)((( 216 +2(optional) 217 +)))|(% style="width:87px" %)((( 218 +2(optional) 307 307 ))) 308 308 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 309 309 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 310 -)))|(% style="width: 73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]222 +)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 311 311 312 -[[image:1665 301636888-168.png]]224 +[[image:1664501958445-288.png]] 313 313 314 314 315 315 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== ... ... @@ -318,12 +318,11 @@ 318 318 |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits 319 319 |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 320 320 321 - 322 322 ==== (% style="color:blue" %)**FLAG:**(%%) ==== 323 323 324 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width: 120px" %)325 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width: 30px" %)2bits|(% style="width:30px" %)1bit326 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] 235 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 236 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits 237 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version 327 327 328 328 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 329 329 ... ... @@ -333,18 +333,22 @@ 333 333 * Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976// 334 334 * Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 335 335 247 + 336 336 (% style="color:red" %)**Important note:** 337 337 338 338 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. 339 339 340 -2. In thismode, the total payloadwill be15 bytes, whileUS915/AU915DR0 acceptsonly 11 bytes payload.Inthiscase, the payloadon server willbeignore andshows as below:252 +2. In firmware version v1.5, Roll & Pitch is disabled by default. 341 341 254 +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: 342 342 256 + 343 343 [[image:1664502116362-706.png]] 344 344 345 345 346 -3. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 347 347 261 +4. While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 262 + 348 348 [[image:1664502166010-515.png]] 349 349 350 350 ... ... @@ -351,15 +351,15 @@ 351 351 352 352 ==== (% style="color:blue" %)**Alarm:**(%%) ==== 353 353 354 - **Example:**0x4B & 0x40 >> 6 = 0x01269 +Example: 0x4B & 0x40 >> 6 = 0x01 355 355 356 356 357 357 ==== (% style="color:blue" %)**BAT:**(%%) ==== 358 358 359 - **Example:**0x4B45& 0x3FFF ⇒ 2885(mV).274 +Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV). 360 360 361 361 ((( 362 -The battery info shows the battery voltage,User can usethebelow mapping to indicate the battery in percentage: \277 +The battery info shows the current voltage, for (% style="color:blue" %)**TrackerD**(%%) version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \ 363 363 ))) 364 364 365 365 * > 4.0v : 80% ~~ 100% ... ... @@ -369,33 +369,17 @@ 369 369 * < 3.39v: 0~~20% 370 370 371 371 372 -==== (% style="color:blue" %)**MOD:**(%%) ==== 373 - 374 -**Example: ** (0x60>>6) & 0x3f =1 375 - 376 -**Set the format of GPS data uplink link:** 377 - 378 -(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values 379 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values 380 - 381 - 382 -**Set the format of BLE data uplink link:** 383 - 384 -(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon 385 - 386 - 387 387 ==== (% style="color:blue" %)**LON:**(%%) ==== 388 388 389 -**Example:** (0x60>>5) & 0x01=1. 390 390 391 391 Enable/Disable LED activity for uplink 392 392 393 393 ((( 394 - (% style="color:#037691" %)**0x00:**(%%)Disable LED indicator.293 +0x00: Disable LED indicator. 395 395 ))) 396 396 397 397 ((( 398 - (% style="color:#037691" %)**0x01:**(%%)Enable LED indicator (Default Value)297 +0x01: Enable LED indicator (Default Value) 399 399 ))) 400 400 401 401 ... ... @@ -410,57 +410,15 @@ 410 410 411 411 412 412 413 -=== 2. 4.33,RealtimeGNSS Positioning(Default Mode)===312 +=== 2.3.3 Uplink FPORT~= , History GNSS Positioning === 414 414 415 415 416 -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) 417 417 316 +=== 2.3.4 BLE positioning Payload(Fport2) === 418 418 419 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %) 420 -|=(% scope="row" style="width: 60px;" %)((( 421 -**Size(bytes)** 422 -)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1 423 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 424 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 425 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 426 426 427 -(% class="wikigeneratedid" %) 428 -[[image:1665301687277-443.png]] 319 +Different MODE has different payload: (% style="color:blue" %)**MODE=2** 429 429 430 - 431 - 432 -=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 433 - 434 - 435 -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. 436 - 437 - 438 -(% style="color:red" %)**Note for this mode:** 439 - 440 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server. 441 -* 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. 442 -* 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 443 - 444 -The payload is 15 bytes, as below. 445 - 446 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 447 -|=(% scope="row" %)((( 448 -**Size(bytes)** 449 -)))|4|4|2|1|1|1|1|1 450 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 451 - 452 -[[image:image-20221009160309-2.png]] 453 - 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 - 464 464 (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 465 465 |=(% scope="row" style="width: 60px;" %)((( 466 466 **Size(bytes)** ... ... @@ -480,7 +480,7 @@ 480 480 [[image:1664502425687-834.png]] 481 481 482 482 483 -* (% style="color:#037691" %)**BAT: ** (%%) 340 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV). 484 484 * (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 485 485 * (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 486 486 * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. ... ... @@ -489,34 +489,11 @@ 489 489 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 490 490 491 491 492 -=== 2. 4.6UplinkFPORT~=8,WiFiPositioningwith StrongestWiFi SSID(Sincefirmware1.4.1)===349 +=== 2.3.5 Add Payload format in TTN V3 === 493 493 494 494 495 -T rackerDsupportsWiFi scansfor indoorpositioning. User canset[[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]]to**WiFi**soTrackerDwillscanWiFi andfind thestrongest WiFi info anduplink.352 +In TTN V3, use can add a custom payload so it shows friendly. 496 496 497 - 498 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %) 499 -|=(% scope="row" style="width: 60px;" %)((( 500 -**Size(bytes)** 501 -)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1 502 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)((( 503 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 504 -)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 505 - 506 -(% class="wikigeneratedid" %) 507 -[[image:1667288597595-714.png||height="212" width="1151"]] 508 - 509 - 510 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 511 -* (% style="color:#037691" %)**SSID: **(%%)WiFi name. 512 -* (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 513 - 514 - 515 -=== 2.4.7 Add Payload format in TTN V3 === 516 - 517 - 518 -In TTN V3, user can add a custom payload so it shows friendly. 519 - 520 520 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 521 521 522 522 ... ... @@ -523,9 +523,8 @@ 523 523 [[image:1664502649601-895.png]] 524 524 525 525 526 -Add the decoder from this link: 360 +Add the decoder from this link: 527 527 528 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] 529 529 530 530 Save the change the uplink message will be parsed. As below: 531 531 ... ... @@ -533,12 +533,16 @@ 533 533 534 534 535 535 536 -== 2. 5Integrate with Datacake ==369 +== 2.4 Integrate with Datacake == 537 537 538 538 372 +((( 539 539 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. 374 +))) 540 540 376 +((( 541 541 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]] 378 +))) 542 542 543 543 544 544 [[image:1664502695771-538.png]] ... ... @@ -545,12 +545,16 @@ 545 545 546 546 547 547 548 -== 2. 6Integrate with Tago ==385 +== 2.5 Integrate with Tago == 549 549 550 550 551 -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. 388 +((( 389 +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. 390 +))) 552 552 392 +((( 553 553 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]] 394 +))) 554 554 555 555 556 556 [[image:1664502715371-321.png]] ... ... @@ -557,25 +557,9 @@ 557 557 558 558 559 559 560 -== 2. 7DatalogFeature ==401 +== 2.6 Alarm Mode == 561 561 562 562 563 -total 273 entries,by default, 564 - 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 - 576 -== 2.8 Alarm Mode == 577 - 578 - 579 579 ((( 580 580 User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 581 581 ))) ... ... @@ -582,7 +582,7 @@ 582 582 583 583 584 584 ((( 585 -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 salert mode.410 +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. 586 586 ))) 587 587 588 588 ... ... @@ -590,7 +590,7 @@ 590 590 Two ways to exit alarm mode: 591 591 ))) 592 592 593 -* Server send sa downlink command to exit.418 +* Server send a downlink command to exit. 594 594 * User fast press the RED button 10 times. 595 595 596 596 ((( ... ... @@ -599,16 +599,13 @@ 599 599 600 600 601 601 602 -== 2. 9Transport Mode ==427 +== 2.7 Sports Mode == 603 603 604 604 605 -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. 606 606 431 +== 2.8 LED Status == 607 607 608 608 609 -== 2.10 LED Status == 610 - 611 - 612 612 (% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 613 613 |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 614 614 |(% 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 ... ... @@ -624,7 +624,7 @@ 624 624 |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 625 625 626 626 627 -== 2. 11Button Function ==449 +== 2.9 Button Function == 628 628 629 629 630 630 (% style="color:blue" %)**RESET button:** ... ... @@ -639,14 +639,14 @@ 639 639 [[image:1664502854406-763.png]] 640 640 641 641 642 -(% border="1" style="background-color:#ffffcc; color:green; width:5 10px" %)643 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 20 5px;" %)**Action**|=(% style="width: 205px;" %)**Description**644 -|(% 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"]]464 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %) 465 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description** 466 +|(% 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"]] 645 645 |(% 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 646 646 |(% 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. 647 647 648 648 649 -== 2.1 2USB Port Function ==471 +== 2.10 USB Port Function == 650 650 651 651 652 652 The USB interface of TrackerD has below functions: ... ... @@ -681,9 +681,11 @@ 681 681 [[image:1664503022490-662.png]] 682 682 683 683 506 + 684 684 [[image:1664503035713-500.png]] 685 685 686 686 510 + 687 687 [[image:1664503047675-651.png]] 688 688 689 689 ... ... @@ -727,21 +727,21 @@ 727 727 728 728 729 729 730 -=== 3.2.3 Set Transport Mode Packet transmission interval ===554 +=== 3.2.3 Set Sports Mode Packet transmission interval === 731 731 732 732 733 -Set TransportModepacket transmit interval557 +Set sports packet transmit interval 734 734 735 735 * (% style="color:blue" %)**AT Command:** 736 736 737 737 (% style="color:#037691" %)**AT+MTDC=xx. ** 738 738 739 -Example: AT+MTDC=300000 **~-~-> ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds inTransport mode, Default Value: 300000563 +Example: AT+MTDC=300000 **~-~-> ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000 740 740 741 741 742 742 * (% style="color:blue" %)**Downlink Payload (prefix 0x03):** 743 743 744 -(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+MTDC=3000000 568 +(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+ MTDC=3000000 745 745 746 746 747 747 ... ... @@ -776,21 +776,21 @@ 776 776 777 777 778 778 779 -=== 3.2.6 Disable/Enable TransportMode ===603 +=== 3.2.6 Disable/Enable movement detect (Debug Only) === 780 780 781 781 782 -User scan use this feature to enable/disableTransportMode.606 +User can use this feature to check and set thread hole of movement detect 783 783 784 784 * (% style="color:blue" %)**AT Command:** 785 785 786 786 (% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)** 787 787 788 -Example: AT+INTWK=1 **~-~-> ** Enable TransportMode.612 +Example: AT+ INTWK =1 **~-~-> ** Enable detect movement. 789 789 790 790 791 791 * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):** 792 792 793 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+INTWK=1 617 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/ Same as AT+ INTWK =1 794 794 795 795 796 796 ... ... @@ -797,47 +797,35 @@ 797 797 === 3.2.7 Set Positioning Mode === 798 798 799 799 800 -SMOD define how TrackerD scan and uplink dat a:624 +SMOD define the how TrackerD scan and uplink date. 801 801 626 +GPS室外定位模式: 设备默认模式,设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是3分钟定位,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。GPS还有一种logdata模式,在断网的情况下将数据存储下来,等到有网的时候,一次将数据以每10秒上报。 802 802 803 - *(%style="color:blue" %)**AT Command:**628 +BLE室内定位模式: 设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是5秒,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每3分钟发送一次)。 804 804 805 - (% style="color:#037691" %)**AT+SMOD=aa,bb,cc**630 +GPS和BLE混动模式:设备入网后会发送device当前模式下的信息,随后立即判断是否在室内,如果是就进行BLE定位,不是就GPS定位。如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。 806 806 807 - (%style="color:#037691" %)** aa:**632 +运动模式: 设备入网后会发送device当前模式下的信息,随后发送GPS定位数据,设备判断是否在运动,没有运动传感器没有检测到动作,立即进入静止状态(默认20分钟),如果产生运动,将每5分钟发送一次数据,再第五分钟后检测设备有误运动,无将切换到静止状态,有立即发送数据。 808 808 809 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 810 810 811 -* (% 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. 812 812 813 -* (% style="color: red" %)**3:GPS/BLE Hybrid: **(%%)Combinationfor 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.636 +* (% style="color:blue" %)**AT Command:** 814 814 815 -(% style="color:#037691" %)** bb:**638 +(% style="color:#037691" %)**AT+SMOD=xx. ** 816 816 817 -* (% style="color:red" %)**0 : **(%%)GPS+ BAT+ State+Tem&Hum 818 818 819 - *(% style="color:red" %)**1 :**(%%) GPS +BAT State641 + **Example:** 820 820 821 - (%style="color:#037691"%)**cc:**643 + AT+ SMOD =1,0 **~-~-> ** GPS+ BAT+ State+Tem&Hum 822 822 823 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 824 - 825 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%)) 645 + AT+ SMOD =1,1 **~-~->** GPS +BAT State 826 826 827 - (%style="color:blue"%)**Example:**647 + AT+ SMOD =2,3 **~-~->** (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。 828 828 829 - AT+SMOD=1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 830 830 831 - AT+SMOD=1,1,0 ~-~-> GPS +BAT State 832 - 833 - AT+SMOD=2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 834 - 835 - AT+SMOD=2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State 836 - 837 - 838 838 * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** 839 839 840 -(% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+SMOD=1,0,0652 +(% style="color:#037691" %)**0xA5 01 00** (%%) ~/~/ Same as AT+ SMOD =1,0 841 841 842 842 843 843 ... ... @@ -854,7 +854,7 @@ 854 854 855 855 (% style="color:#037691" %)**AT+FTIME=xx** (%%) **~-~-> ** Set to use xx as max fix time. 856 856 857 - **Example:**AT+FTIME=150669 +Example: AT+FTIME=150 858 858 859 859 860 860 * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):** ... ... @@ -863,7 +863,7 @@ 863 863 864 864 865 865 866 -=== 3. 2.9 Set PDOP value for GPS fix accuracy ===678 +=== 3.3.9 Set PDOP value for GPS fix accuracy === 867 867 868 868 869 869 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. ... ... @@ -891,110 +891,22 @@ 891 891 892 892 * (% style="color:blue" %)**AT Command:** 893 893 894 -(% style="color:#037691" %)**AT+CFM=xx** 706 +(% style="color:#037691" %)**AT+CFM=xx. ** 895 895 896 896 897 897 **~ Example:** 898 898 899 - AT+CFM=0 **~-~-> ** Disable confirmation 711 + AT+ CFM=0 **~-~-> ** Disable confirmation 900 900 901 - AT+CFM=1 **~-~-> ** Enable confirmation 713 + AT+ CFM=1 **~-~-> ** Enable confirmation 902 902 903 903 904 904 * (% style="color:blue" %)**Downlink Payload (prefix 0x05):** 905 905 906 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+ CFM=1718 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+ SMOD =1 907 907 908 908 909 909 910 -=== 3.2.10 Auto Send None-ACK messages === 911 - 912 - 913 -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. 914 - 915 - 916 -* (% style="color:blue" %)**AT Command: AT+PNACKMD** 917 - 918 -The default factory setting is 0. 919 - 920 - 921 -**Command Example Function Response:** 922 - 923 -(% style="color:#037691" %)**AT+PNACKMD=1** (%%) ~/~/ Poll None-ACK message OK 924 - 925 - 926 -* (% style="color:blue" %)**Downlink Command: 0x34** 927 - 928 -Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 929 - 930 - 931 - 932 -=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 933 - 934 - 935 -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. 936 - 937 -(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.** 938 - 939 -(% style="color:blue" %)**AT Command:** 940 - 941 - (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 942 - 943 - (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 944 - 945 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 946 - 947 -Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 948 - 949 - 950 - 951 -=== 3.2.12 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 952 - 953 - 954 -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. 955 - 956 -(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.** 957 - 958 -(% style="color:blue" %)**AT Command:** 959 - 960 - (% style="color:#037691" %)**AT+WiFiMASK=123456** (%%) ~/~/ Set WiFiMASK = 123456 961 - 962 - (% style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK 963 - 964 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)** 965 - 966 -Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 967 - 968 - 969 - 970 -=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 971 - 972 - 973 -Users can use this feature to enable/disable Information printing. 974 - 975 -(% style="color:blue" %)**AT Command:** 976 - 977 -(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/(Disable (0), Enable (1), default:0) 978 -\\Example: AT+SHOWID=1 ~-~-> Enable Information printing. 979 - 980 - 981 - 982 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 983 - 984 - 985 -The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. 986 - 987 -(% style="color:blue" %)**AT Command:** 988 - 989 -(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode 990 - 991 - 992 -(% style="color:blue" %)**Downlink Payload:0X24** 993 - 994 -Example: 0x24 01 ~/~/ Same as AT+CHE=1 995 - 996 - 997 - 998 998 = 4. Setting for Different Scenarios = 999 999 1000 1000 ... ... @@ -1035,10 +1035,9 @@ 1035 1035 [[image:1664503574618-659.png]] 1036 1036 1037 1037 1038 - 1039 1039 (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 1040 1040 1041 -[[https:~~/~~/ github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]764 +[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1042 1042 1043 1043 1044 1044 Users need to use below files: ... ... @@ -1075,24 +1075,12 @@ 1075 1075 [[image:1664503635019-941.png]] 1076 1076 1077 1077 1078 - 1079 1079 * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.** 1080 1080 1081 1081 [[image:1664503715811-892.png]] 1082 1082 1083 1083 1084 -(% 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. 1085 1085 1086 -[[image:image-20221024105643-1.png]] 1087 - 1088 -**~ Figure1** 1089 - 1090 - 1091 -[[image:image-20221024105643-2.png]] 1092 - 1093 - **Figure2** 1094 - 1095 - 1096 1096 * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]** 1097 1097 1098 1098 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: ... ... @@ -1152,90 +1152,10 @@ 1152 1152 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 1153 1153 1154 1154 1155 -== 7.3 Notes on using different serial port tools for TrackerD == 1156 1156 867 += 8. Order Info = 1157 1157 1158 -=== 7.3.1 Serial port utility === 1159 1159 1160 - 1161 -Serial port utility requires you to automatically add data streams. 1162 - 1163 -Need to adjust the data stream to RTS/CTS on physical restart. 1164 - 1165 - 1166 -(% class="wikigeneratedid" %) 1167 -[[image:image-20221102140621-1.png]] 1168 - 1169 - 1170 -When using AT commands, the data flow needs to be adjusted to XON/XOFF 1171 - 1172 - 1173 -[[image:image-20221102140638-2.png]] 1174 - 1175 - 1176 - 1177 -=== 7.3.2 SecureCRT === 1178 - 1179 - 1180 -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. 1181 - 1182 - 1183 -[[image:image-20221102140704-3.png]] 1184 - 1185 - 1186 -[[image:image-20221102140712-4.png]] 1187 - 1188 - 1189 - 1190 -=== 7.3.3 PUTTY === 1191 - 1192 - 1193 -[[image:image-20221102140748-5.png]] 1194 - 1195 - 1196 -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. 1197 - 1198 - 1199 -[[image:image-20221102140801-6.png]] 1200 - 1201 - 1202 - 1203 -= 8 Trouble Shooting = 1204 - 1205 - 1206 -== 8.1 TDC is changed to 4294947296 and cause no uplink. == 1207 - 1208 - 1209 -((( 1210 -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 1211 -))) 1212 - 1213 - 1214 - 1215 -== 8.2 Device not able get AT Command or show output after wake up from deep sleep mode == 1216 - 1217 - 1218 -((( 1219 -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. 1220 -))) 1221 - 1222 - 1223 - 1224 -== 8.3 The reason why it has been restarted after upgrading(V.1.4.1) == 1225 - 1226 - 1227 -((( 1228 -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 1229 -))) 1230 - 1231 - 1232 -[[image:image-20221107145243-1.png||height="695" width="443"]] 1233 - 1234 - 1235 - 1236 -= 9. Order Info = 1237 - 1238 - 1239 1239 Part Number: (% style="color:blue" %)**TrackerD-XXX** 1240 1240 1241 1241 (% style="color:blue" %)**XXX**(%%): The default frequency band ... ... @@ -1249,7 +1249,7 @@ 1249 1249 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1250 1250 1251 1251 1252 -= 10. Packing Info =883 += 9. Packing Info = 1253 1253 1254 1254 1255 1255 (% style="color:#037691" %)**Package Includes**: ... ... @@ -1259,11 +1259,11 @@ 1259 1259 1260 1260 (% style="color:#037691" %)**Dimensions and Weight**: 1261 1261 1262 -* Device Size: 85 x 48 x 15 m m893 +* Device Size: 85 x 48 x 15 cm 1263 1263 * Weight: 50g 1264 1264 1265 1265 1266 -= 1 1. Support =897 += 10. Support = 1267 1267 1268 1268 1269 1269 * 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. ... ... @@ -1270,7 +1270,7 @@ 1270 1270 * 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]]. 1271 1271 1272 1272 1273 -= 1 2. Reference =904 += 11. Reference = 1274 1274 1275 1275 1276 1276 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
- 1665301570342-765.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.6 KB - Content
- 1665301636888-168.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -36.6 KB - Content
- 1665301687277-443.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -22.6 KB - Content
- 1665301786397-168.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -22.6 KB - Content
- 1667288597595-714.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -27.9 KB - Content
- image-20221006181357-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -88.0 KB - Content
- image-20221009160220-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -46.4 KB - Content
- image-20221009160309-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -57.2 KB - Content
- image-20221009234629-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -222.9 KB - Content
- image-20221009234703-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -136.4 KB - Content
- image-20221024105643-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -11.3 KB - Content
- image-20221024105643-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -64.5 KB - Content
- image-20221102140621-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -46.1 KB - Content
- image-20221102140638-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -40.8 KB - Content
- image-20221102140704-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -15.5 KB - Content
- image-20221102140712-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -73.2 KB - Content
- image-20221102140748-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -56.0 KB - Content
- image-20221102140801-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -21.0 KB - Content
- image-20221107145243-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -107.3 KB - Content