Skip to Content
Last modified by Bei Jinggeng on 2025/08/01 17:45
From version 79.1
edited by Edwin Chen
on 2022/10/22 00:11
Change comment: There is no comment for this version
To version 145.1
edited by Edwin Chen
on 2022/11/22 12:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,7 +14,6 @@
14 14  
15 15  = 1.  Introduction =
16 16  
17 -
18 18  == 1.1  What is TrackerD ==
19 19  
20 20  
... ... @@ -46,7 +46,6 @@
46 46  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
47 47  
48 48  
49 -
50 50  == 1.2 Specifications ==
51 51  
52 52  
... ... @@ -97,7 +97,6 @@
97 97  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
98 98  * Tracking: max: 38mA
99 99  
100 -
101 101  == 1.3  Features ==
102 102  
103 103  
... ... @@ -116,7 +116,6 @@
116 116  * Tri-color LED, Alarm button
117 117  * Datalog
118 118  
119 -
120 120  == 1.4  Applications ==
121 121  
122 122  
... ... @@ -123,10 +123,8 @@
123 123  * Logistics and Supply Chain Management
124 124  * Human tracking
125 125  
122 += 2.  Use TrackerD =
126 126  
127 -= 2.1 Use TrackerD =
128 -
129 -
130 130  == 2.1 How it works? ==
131 131  
132 132  
... ... @@ -133,7 +133,6 @@
133 133  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.
134 134  
135 135  
136 -
137 137  == 2.2 Quick guide to connect to LoRaWAN server ==
138 138  
139 139  
... ... @@ -175,34 +175,34 @@
175 175  **__Add APP KEY and DEV EUI:__**
176 176  
177 177  
178 -[[image:1664501784668-703.png]]
171 +[[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"]]
179 179  
180 180  
181 181  
175 +(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
182 182  
183 -(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
177 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
184 184  
179 +[[image:1664502835802-546.png]]
185 185  
181 +
186 186  (% 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.
187 187  
188 188  
189 -
190 190  == 2.3  Positioning Mode(SMOD) ==
191 191  
192 192  
193 193  Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
194 194  
195 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
196 -* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
197 -* (% 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.
190 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
191 +* (% 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.
192 +* (% 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.
198 198  
199 199  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
200 200  
201 201  
202 -
203 203  == 2.4  Uplink Payload ==
204 204  
205 -
206 206  === 2.4.1 Uplink FPORT~=5, Device Status ===
207 207  
208 208  
... ... @@ -211,8 +211,8 @@
211 211  Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
212 212  
213 213  
214 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
215 -|=(% scope="row" style="width: 108px;" %)**Size(bytes)**|=(% style="width: 82px;" %)**1**|=(% style="width: 83px;" %)**2**|=(% style="width: 94px;" %)**1**|=(% style="width: 84px;" %)**1**|=(% style="width: 44px;" %)2|=(% style="width: 63px;" %)**2**|=(% style="width: 60px;" %)1
207 +(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
208 +|=(% 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
216 216  |=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
217 217  
218 218  [[image:1665301570342-765.png]]
... ... @@ -256,12 +256,11 @@
256 256  Use can also get the Device Status uplink through the downlink command:
257 257  
258 258  
259 -
260 260  (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
261 261  
262 -(% border="1.5" style="background-color:#ffffcc; color:green; width:420px" %)
263 -|(% style="width:75px" %)**Size(bit)**|(% style="width:64px" %)2bits|(% style="width:137px" %)2bit|(% style="width:142px" %)4bit
264 -|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:137px" %)GPS_Settings|(% style="width:142px" %)BLE_Settings
254 +(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
255 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
256 +|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
265 265  
266 266  (% style="color:blue" %)** SMOD：**
267 267  
... ... @@ -283,15 +283,15 @@
283 283  
284 284  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
285 285  
278 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
286 286  
287 287  
288 288  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
289 289  
290 -(% border="1.5" style="background-color:#ffffcc; color:green; width:417px" %)
291 -|(% style="width:77px" %)**Size(bit)**|(% style="width:70px" %)5 Bits|(% style="width:92px" %)1 Bit|(% style="width:48px" %)1 Bit|(% style="width:126px" %)1 Bit
292 -|(% 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"]]
283 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
284 +|=(% 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
285 +|=(% 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"]]
293 293  
294 -
295 295  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
296 296  
297 297  
... ... @@ -298,12 +298,12 @@
298 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 299  
300 300  
301 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
302 -|=(% scope="row" style="width: 50px;" %)(((
293 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
294 +|=(% scope="row" style="width: 60px;" %)(((
303 303  **Size(bytes)**
304 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
296 +)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
305 305  2
306 -)))|(% style="width:87px" %)(((
298 +)))|(% style="width:30px" %)(((
307 307  2
308 308  )))
309 309  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
... ... @@ -321,8 +321,8 @@
321 321  
322 322  ==== (% style="color:blue" %)**FLAG:**(%%) ====
323 323  
324 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
325 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit
316 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
317 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
326 326  |=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
327 327  
328 328  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
... ... @@ -398,7 +398,6 @@
398 398  )))
399 399  
400 400  
401 -
402 402  ==== (% style="color:blue" %)**Hum:**(%%) ====
403 403  
404 404  0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
... ... @@ -409,7 +409,6 @@
409 409  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
410 410  
411 411  
412 -
413 413  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
414 414  
415 415  
... ... @@ -416,10 +416,10 @@
416 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  
418 418  
419 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
420 -|=(% scope="row" style="width: 50px;" %)(((
409 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
410 +|=(% scope="row" style="width: 60px;" %)(((
421 421  **Size(bytes)**
422 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
412 +)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
423 423  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
424 424  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
425 425  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
... ... @@ -428,7 +428,6 @@
428 428  [[image:1665301687277-443.png]]
429 429  
430 430  
431 -
432 432  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
433 433  
434 434  
... ... @@ -438,12 +438,12 @@
438 438  (% style="color:red" %)**Note for this mode:**
439 439  
440 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 (% style="color:blue" %)**CONFIRMED Mode**(%%) when PNACKMD=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.
430 +* 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 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 443  
444 444  The payload is 15 bytes, as below.
445 445  
446 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
435 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
447 447  |=(% scope="row" %)(((
448 448  **Size(bytes)**
449 449  )))|4|4|2|1|1|1|1|1
... ... @@ -452,12 +452,14 @@
452 452  [[image:image-20221009160309-2.png]]
453 453  
454 454  
455 -
456 456  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
457 457  
458 -TrackerD supports BLE scans for indoor positioning. User can set **SMOD** to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan BLE iBeacon before each uplink.
459 459  
447 +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 460  
449 +User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
450 +
451 +
461 461  (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
462 462  |=(% scope="row" style="width: 60px;" %)(((
463 463  **Size(bytes)**
... ... @@ -481,16 +481,37 @@
481 481  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
482 482  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
483 483  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
484 -* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
475 +* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
485 485  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
486 486  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
487 487  
479 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
488 488  
489 -=== 2.4.6  Add Payload format in TTN V3 ===
490 490  
482 +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.
491 491  
492 -In TTN V3, use can add a custom payload so it shows friendly.
493 493  
485 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
486 +|=(% scope="row" style="width: 60px;" %)(((
487 +**Size(bytes)**
488 +)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
489 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
490 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
491 +)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
492 +
493 +(% class="wikigeneratedid" %)
494 +[[image:1667288597595-714.png||height="212" width="1151"]]
495 +
496 +
497 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
498 +* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
499 +* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
500 +
501 +=== 2.4.7  Add Payload format in TTN V3 ===
502 +
503 +
504 +In TTN V3, user can add a custom payload so it shows friendly.
505 +
494 494  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
495 495  
496 496  
... ... @@ -497,6 +497,7 @@
497 497  [[image:1664502649601-895.png]]
498 498  
499 499  
512 +
500 500  Add the decoder from this link: 
501 501  
502 502  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -506,39 +506,28 @@
506 506  [[image:1664502676891-606.png]]
507 507  
508 508  
509 -
510 510  == 2.5 Integrate with Datacake ==
511 511  
512 512  
513 -(((
514 514  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.
515 -)))
516 516  
517 -(((
518 518  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]]
519 -)))
520 520  
521 521  
522 522  [[image:1664502695771-538.png]]
523 523  
524 524  
525 -
526 526  == 2.6 Integrate with Tago ==
527 527  
528 528  
529 -(((
530 -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.
531 -)))
536 +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.
532 532  
533 -(((
534 534  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]]
535 -)))
536 536  
537 537  
538 538  [[image:1664502715371-321.png]]
539 539  
540 540  
541 -
542 542  == 2.7  Datalog Feature ==
543 543  
544 544  
... ... @@ -554,7 +554,6 @@
554 554  [[image:image-20221009234629-1.png||height="390" width="577"]]
555 555  
556 556  
557 -
558 558  == 2.8 Alarm Mode ==
559 559  
560 560  
... ... @@ -564,15 +564,15 @@
564 564  
565 565  
566 566  (((
567 -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.
568 +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.
568 568  )))
569 569  
570 570  
571 571  (((
572 -Two ways to exit alarm mode:
573 +**Two ways to exit alarm mode:**
573 573  )))
574 574  
575 -* Server send a downlink command to exit.
576 +* Server sends a downlink command to exit.
576 576  * User fast press the RED button 10 times.
577 577  
578 578  (((
... ... @@ -580,7 +580,6 @@
580 580  )))
581 581  
582 582  
583 -
584 584  == 2.9 Transport Mode ==
585 585  
586 586  
... ... @@ -587,17 +587,16 @@
587 587  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.
588 588  
589 589  
590 -
591 591  == 2.10 LED Status ==
592 592  
593 593  
594 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
593 +(% border="1.5" style="background-color:#ffffcc; width:500px" %)
595 595  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
596 596  |(% 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
597 597  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
598 598  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
599 599  |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
600 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
599 +|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
601 601  |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
602 602  |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
603 603  |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
... ... @@ -620,9 +620,9 @@
620 620  [[image:1664502854406-763.png]]
621 621  
622 622  
623 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
624 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
625 -|(% 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"]]
622 +(% border="1" style="background-color:#ffffcc; width:510px" %)
623 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
624 +|(% 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"]]
626 626  |(% 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
627 627  |(% 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.
628 628  
... ... @@ -644,7 +644,6 @@
644 644  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
645 645  
646 646  
647 -
648 648  == 3.1 Access AT Command ==
649 649  
650 650  
... ... @@ -660,11 +660,9 @@
660 660  [[image:1664503022490-662.png]]
661 661  
662 662  
663 -
664 664  [[image:1664503035713-500.png]]
665 665  
666 666  
667 -
668 668  [[image:1664503047675-651.png]]
669 669  
670 670  
... ... @@ -671,7 +671,6 @@
671 671  
672 672  == 3.2 Command Set ==
673 673  
674 -
675 675  === 3.2.1 Set Transmit Interval ===
676 676  
677 677  
... ... @@ -689,7 +689,6 @@
689 689  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
690 690  
691 691  
692 -
693 693  === 3.2.2 Set Alarm Packet transmission interval ===
694 694  
695 695  
... ... @@ -707,7 +707,6 @@
707 707  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
708 708  
709 709  
710 -
711 711  === 3.2.3 Set Transport Mode Packet transmission interval ===
712 712  
713 713  
... ... @@ -722,10 +722,9 @@
722 722  
723 723  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
724 724  
725 -(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
718 +(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
726 726  
727 727  
728 -
729 729  === 3.2.4 Exit Alarm ===
730 730  
731 731  
... ... @@ -738,7 +738,6 @@
738 738  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
739 739  
740 740  
741 -
742 742  === 3.2.5 Disable/Enable LED flash ===
743 743  
744 744  
... ... @@ -756,7 +756,6 @@
756 756  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
757 757  
758 758  
759 -
760 760  === 3.2.6 Disable/Enable Transport Mode ===
761 761  
762 762  
... ... @@ -766,15 +766,14 @@
766 766  
767 767  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
768 768  
769 -Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
759 +Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
770 770  
771 771  
772 772  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
773 773  
774 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
764 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
775 775  
776 776  
777 -
778 778  === 3.2.7 Set Positioning Mode ===
779 779  
780 780  
... ... @@ -787,32 +787,40 @@
787 787  
788 788  (% style="color:#037691" %)** aa:**
789 789  
790 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
791 -* (% style="color:red" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
792 -* (% 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.
779 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
793 793  
781 +* (% 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.
782 +
783 +* (% 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.
784 +
794 794  (% style="color:#037691" %)**bb:**
795 795  
796 796  * (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
788 +
797 797  * (% style="color:red" %)**1 :**(%%)  GPS +BAT State
798 798  
799 799  (% style="color:#037691" %)**cc:   **
800 800  
801 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
793 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
794 +
795 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
802 802  
803 803  (% style="color:blue" %)**Example:**
804 804  
805 - AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
806 - AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
807 - AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
799 + AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
808 808  
801 + AT+SMOD=1,1,0 ~-~->  GPS +BAT State
809 809  
810 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
803 + AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
811 811  
812 -(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
805 + AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
813 813  
814 814  
808 +* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
815 815  
810 +(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
811 +
812 +
816 816  === 3.2.8 Set MAX GPS position time ===
817 817  
818 818  
... ... @@ -819,7 +819,7 @@
819 819  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.
820 820  
821 821  
822 -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.
819 +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.
823 823  
824 824  
825 825  * (% style="color:blue" %)**AT Command:**
... ... @@ -834,7 +834,6 @@
834 834  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
835 835  
836 836  
837 -
838 838  === 3.2.9 Set PDOP value for GPS fix accuracy ===
839 839  
840 840  
... ... @@ -859,7 +859,7 @@
859 859  
860 860  
861 861  
862 -Disable/Enable the confirmation mode
858 +**Disable/Enable the confirmation mode**
863 863  
864 864  * (% style="color:blue" %)**AT Command:**
865 865  
... ... @@ -868,17 +868,16 @@
868 868  
869 869  **~ Example:**
870 870  
871 - AT+ CFM=0    **~-~->   ** Disable confirmation
867 + AT+CFM=0    **~-~->   ** Disable confirmation
872 872  
873 - AT+ CFM=1    **~-~->  ** Enable confirmation
869 + AT+CFM=1    **~-~->  ** Enable confirmation
874 874  
875 875  
876 876  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
877 877  
878 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
874 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
879 879  
880 880  
881 -
882 882  === 3.2.10  Auto Send None-ACK messages ===
883 883  
884 884  
... ... @@ -900,6 +900,68 @@
900 900  Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
901 901  
902 902  
898 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
899 +
900 +
901 +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.
902 +
903 +(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
904 +
905 +(% style="color:blue" %)**AT Command:**
906 +
907 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
908 +
909 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
910 +
911 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
912 +
913 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
914 +
915 +
916 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
917 +
918 +
919 +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.
920 +
921 +(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
922 +
923 +(% style="color:blue" %)**AT Command:**
924 +
925 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
926 +
927 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
928 +
929 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
930 +
931 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
932 +
933 +
934 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
935 +
936 +
937 +Users can use this feature to enable/disable Information printing.
938 +
939 +(% style="color:blue" %)**AT Command:**
940 +
941 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
942 +\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
943 +
944 +
945 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
946 +
947 +
948 +The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
949 +
950 +(% style="color:blue" %)**AT Command:**
951 +
952 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
953 +
954 +
955 +(% style="color:blue" %)**Downlink Payload:0X24**
956 +
957 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
958 +
959 +
903 903  = 4. Setting for Different Scenarios =
904 904  
905 905  
... ... @@ -906,7 +906,6 @@
906 906  
907 907  = 5. Upload Firmware =
908 908  
909 -
910 910  == 5.1 Firmware Change Log ==
911 911  
912 912  
... ... @@ -913,7 +913,6 @@
913 913  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
914 914  
915 915  
916 -
917 917  == 5.2 How to upgrade firmware ==
918 918  
919 919  
... ... @@ -940,34 +940,33 @@
940 940  [[image:1664503574618-659.png]]
941 941  
942 942  
998 +
943 943  (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
944 944  
945 945  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
946 946  
947 947  
948 -Users need to use below files:
1004 +**Users need to use below files:**
949 949  
950 950  boot_app0.bin @0e000
951 951  
952 -ESP_LORA-eeprom-class.bin @ 0x10000
1008 +US915.bin @ 0x10000(Select the bin file of the frequency band you need)
953 953  
954 954  
955 -[[image:1664503593459-435.png]]
1011 +[[image:image-20221118105220-2.png]]
956 956  
957 957  
958 958  
959 959  After upgrade finish, it will show finish as below:
960 960  
961 -[[image:1664503611848-385.png]]
1017 +[[image:image-20221118105402-4.png]]
962 962  
963 963  
964 964  
965 965  = 6. Developer Guide =
966 966  
967 -
968 968  == 6.1 Compile Source Code ==
969 969  
970 -
971 971  === 6.1.1 Set up ARDUINO compile environment ===
972 972  
973 973  
... ... @@ -985,7 +985,18 @@
985 985  [[image:1664503715811-892.png]]
986 986  
987 987  
1042 +(% 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.
988 988  
1044 +[[image:image-20221024105643-1.png]]
1045 +
1046 +**~ Figure1**
1047 +
1048 +
1049 +[[image:image-20221024105643-2.png]]
1050 +
1051 + **Figure2**
1052 +
1053 +
989 989  * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
990 990  
991 991  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
... ... @@ -994,7 +994,6 @@
994 994  [[image:1664503752288-974.png]]
995 995  
996 996  
997 -
998 998  == 6.2 Source Code ==
999 999  
1000 1000  
... ... @@ -1015,10 +1015,8 @@
1015 1015  [[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1016 1016  
1017 1017  
1018 -
1019 1019  = 7.  FAQ =
1020 1020  
1021 -
1022 1022  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1023 1023  
1024 1024  
... ... @@ -1025,7 +1025,6 @@
1025 1025  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1026 1026  
1027 1027  
1028 -
1029 1029  == 7.2 What is the pin mapping for the USB program cable? ==
1030 1030  
1031 1031  
... ... @@ -1044,49 +1044,242 @@
1044 1044  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1045 1045  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1046 1046  
1108 +== 7.3 Notes on using different serial port tools for TrackerD ==
1047 1047  
1048 -= 8.  Order Info =
1110 +=== 7.3.1  Serial port utility ===
1049 1049  
1050 1050  
1113 +Serial port utility requires you to automatically add data streams.
1114 +
1115 +Need to adjust the data stream to RTS/CTS on physical restart.
1116 +
1117 +(% class="wikigeneratedid" %)
1118 +[[image:image-20221102140621-1.png]]
1119 +
1120 +
1121 +
1122 +When using AT commands, the data flow needs to be adjusted to XON/XOFF
1123 +
1124 +[[image:image-20221102140638-2.png]]
1125 +
1126 +
1127 +=== 7.3.2  SecureCRT ===
1128 +
1129 +
1130 +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.
1131 +
1132 +
1133 +[[image:image-20221102140704-3.png]]
1134 +
1135 +
1136 +[[image:image-20221102140712-4.png]]
1137 +
1138 +
1139 +=== 7.3.3  PUTTY ===
1140 +
1141 +
1142 +[[image:image-20221102140748-5.png]]
1143 +
1144 +
1145 +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.
1146 +
1147 +
1148 +[[image:image-20221102140801-6.png]]
1149 +
1150 +
1151 +== 7.4 How to modify source code to compile different frequency band bin file? ==
1152 +
1153 +
1154 +(% class="box infomessage" %)
1155 +(((
1156 +(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1157 +See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1158 +)))
1159 +
1160 +**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1161 +
1162 +
1163 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1164 +
1165 +
1166 +
1167 +**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1168 +
1169 +
1170 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1171 +
1172 +
1173 +
1174 +**3. Compile the AS923_JP band, please refer to the intention shown**
1175 +
1176 +
1177 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1178 +
1179 +
1180 +
1181 +**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.**
1182 +
1183 +
1184 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1185 +
1186 +
1187 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1188 +
1189 +
1190 += 8  Trouble Shooting =
1191 +
1192 +== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1193 +
1194 +
1195 +(((
1196 +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
1197 +)))
1198 +
1199 +
1200 +== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1201 +
1202 +
1203 +(((
1204 +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.
1205 +)))
1206 +
1207 +
1208 +== 8.3  Problem after Upgrading Firmware ==
1209 +
1210 +=== 8.3.1 Continue Restart after upgrading ===
1211 +
1212 +
1213 +(((
1214 +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
1215 +)))
1216 +
1217 +
1218 +[[image:image-20221118105249-3.png]]
1219 +
1220 +
1221 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1222 +
1223 +
1224 +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
1225 +
1226 +
1227 +=== 8.3.3 "flash read err" after upgrade firmware ===
1228 +
1229 +Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1230 +
1231 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1232 +
1233 +
1234 +User need to upgrade again with below four files to solve this issue.
1235 +
1236 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1237 +
1238 + **Figure 2**
1239 +
1240 +
1241 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1242 +
1243 +User might erase the entire flash include keys and default settings which cause this issue.
1244 +
1245 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1246 +
1247 +[[image:image-20221122100004-3.png]]
1248 +
1249 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1250 +
1251 +
1252 +Example:
1253 +
1254 +AT+DEUI=70B3D57ED0053981  
1255 +
1256 +AT+APPEUI=D23345667BCBCCAF
1257 +
1258 +AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1259 +
1260 +AT+DADDR=260b4dce    ( no need for OTAA)
1261 +
1262 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1263 +
1264 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1265 +
1266 +
1267 +
1268 +=== 8.3.4  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 ===
1269 +
1270 +
1271 +[[image:image-20221122100004-4.png]]
1272 +
1273 +
1274 +== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1275 +
1276 +
1277 +Please download version 1.4.2 again
1278 +
1279 +
1280 +== 8.5  How to deal with unsuccessful GPS positioning? ==
1281 +
1282 +
1283 +1） Make Sure the device is in Open Area where can see the sky.
1284 +
1285 +2)  Set PDOP to a higher value.
1286 +
1287 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1288 +
1289 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1290 +
1291 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1292 +
1293 +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
1294 +
1295 +
1296 += 9.  Order Info =
1297 +
1298 +
1051 1051  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1052 1052  
1053 1053  (% style="color:blue" %)**XXX**(%%): The default frequency band
1054 1054  
1055 1055  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1304 +
1056 1056  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1306 +
1057 1057  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1308 +
1058 1058  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1310 +
1059 1059  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1312 +
1060 1060  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1314 +
1061 1061  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1062 1062  
1317 += 10.  Packing Info =
1063 1063  
1064 -= 9.  Packing Info =
1065 1065  
1066 -
1067 1067  (% style="color:#037691" %)**Package Includes**:
1068 1068  
1069 1069  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1323 +
1070 1070  * USB recharge & program cable x 1
1071 1071  
1072 1072  (% style="color:#037691" %)**Dimensions and Weight**:
1073 1073  
1074 -* Device Size: 85 x 48 x 15 cm
1328 +* Device Size: 85 x 48 x 15 mm
1329 +
1075 1075  * Weight: 50g
1076 1076  
1332 += 11. Support =
1077 1077  
1078 -= 10. Support =
1079 1079  
1080 -
1081 1081  * 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.
1336 +
1082 1082  * 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]].
1083 1083  
1339 += 12.  Reference =
1084 1084  
1085 -= 11.  Reference =
1086 1086  
1087 -
1088 1088  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1343 +
1089 1089  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1090 -* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1091 1091  
1092 -
1346 +* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1667288597595-714.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +27.9 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