Skip to Content
Last modified by Bei Jinggeng on 2025/08/01 17:45
From version 80.1
edited by Edwin Chen
on 2022/10/22 00:15
Change comment: There is no comment for this version
To version 143.2
edited by Xiaoling
on 2022/11/22 10:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
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,6 +97,8 @@
97 97  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
98 98  * Tracking: max: 38mA
99 99  
98 +
99 +
100 100  == 1.3  Features ==
101 101  
102 102  
... ... @@ -115,6 +115,8 @@
115 115  * Tri-color LED, Alarm button
116 116  * Datalog
117 117  
118 +
119 +
118 118  == 1.4  Applications ==
119 119  
120 120  
... ... @@ -121,9 +121,10 @@
121 121  * Logistics and Supply Chain Management
122 122  * Human tracking
123 123  
124 -= 2.1 Use TrackerD =
125 125  
126 126  
128 += 2.  Use TrackerD =
129 +
127 127  == 2.1 How it works? ==
128 128  
129 129  
... ... @@ -130,7 +130,6 @@
130 130  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.
131 131  
132 132  
133 -
134 134  == 2.2 Quick guide to connect to LoRaWAN server ==
135 135  
136 136  
... ... @@ -172,34 +172,34 @@
172 172  **__Add APP KEY and DEV EUI:__**
173 173  
174 174  
175 -[[image:1664501784668-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"]]
176 176  
177 177  
178 178  
181 +(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
179 179  
180 -(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
183 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
181 181  
185 +[[image:1664502835802-546.png]]
182 182  
187 +
183 183  (% 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.
184 184  
185 185  
186 -
187 187  == 2.3  Positioning Mode(SMOD) ==
188 188  
189 189  
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:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
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 -
200 200  == 2.4  Uplink Payload ==
201 201  
202 -
203 203  === 2.4.1 Uplink FPORT~=5, Device Status ===
204 204  
205 205  
... ... @@ -208,8 +208,8 @@
208 208  Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
209 209  
210 210  
211 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
212 -|=(% 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
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
213 213  |=(% 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
214 214  
215 215  [[image:1665301570342-765.png]]
... ... @@ -253,12 +253,11 @@
253 253  Use can also get the Device Status uplink through the downlink command:
254 254  
255 255  
256 -
257 257  (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
258 258  
259 -(% border="1.5" style="background-color:#ffffcc; color:green; width:420px" %)
260 -|(% style="width:75px" %)**Size(bit)**|(% style="width:64px" %)2bits|(% style="width:137px" %)2bit|(% style="width:142px" %)4bit
261 -|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:137px" %)GPS_Settings|(% style="width:142px" %)BLE_Settings
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
262 262  
263 263  (% style="color:blue" %)** SMOD：**
264 264  
... ... @@ -280,14 +280,17 @@
280 280  
281 281  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
282 282  
284 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
283 283  
284 284  
285 285  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
286 286  
287 -(% border="1.5" style="background-color:#ffffcc; color:green; width:417px" %)
288 -|(% 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
289 -|(% 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"]]
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"]]
290 290  
293 +
294 +
291 291  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
292 292  
293 293  
... ... @@ -294,12 +294,12 @@
294 294  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,
295 295  
296 296  
297 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
298 -|=(% scope="row" style="width: 50px;" %)(((
301 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
302 +|=(% scope="row" style="width: 60px;" %)(((
299 299  **Size(bytes)**
300 -)))|(% 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" %)(((
301 301  2
302 -)))|(% style="width:87px" %)(((
306 +)))|(% style="width:30px" %)(((
303 303  2
304 304  )))
305 305  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
... ... @@ -315,10 +315,12 @@
315 315  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
316 316  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
317 317  
322 +
323 +
318 318  ==== (% style="color:blue" %)**FLAG:**(%%) ====
319 319  
320 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
321 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit
326 +(% 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
322 322  |=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
323 323  
324 324  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
... ... @@ -364,6 +364,8 @@
364 364  * 3.40v ~~ 3.69v:  20% ~~ 40%
365 365  * < 3.39v:  0~~20%
366 366  
373 +
374 +
367 367  ==== (% style="color:blue" %)**MOD:**(%%) ====
368 368  
369 369  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -394,7 +394,6 @@
394 394  )))
395 395  
396 396  
397 -
398 398  ==== (% style="color:blue" %)**Hum:**(%%) ====
399 399  
400 400  0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
... ... @@ -405,7 +405,6 @@
405 405  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
406 406  
407 407  
408 -
409 409  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
410 410  
411 411  
... ... @@ -412,10 +412,10 @@
412 412  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)
413 413  
414 414  
415 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
416 -|=(% scope="row" style="width: 50px;" %)(((
421 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
422 +|=(% scope="row" style="width: 60px;" %)(((
417 417  **Size(bytes)**
418 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
424 +)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
419 419  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
420 420  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
421 421  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
... ... @@ -424,7 +424,6 @@
424 424  [[image:1665301687277-443.png]]
425 425  
426 426  
427 -
428 428  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
429 429  
430 430  
... ... @@ -434,12 +434,12 @@
434 434  (% style="color:red" %)**Note for this mode:**
435 435  
436 436  * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
437 -* 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.
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.
438 438  * 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
439 439  
440 440  The payload is 15 bytes, as below.
441 441  
442 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
447 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
443 443  |=(% scope="row" %)(((
444 444  **Size(bytes)**
445 445  )))|4|4|2|1|1|1|1|1
... ... @@ -448,12 +448,14 @@
448 448  [[image:image-20221009160309-2.png]]
449 449  
450 450  
451 -
452 452  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
453 453  
454 -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.
455 455  
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.
456 456  
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 +
457 457  (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
458 458  |=(% scope="row" style="width: 60px;" %)(((
459 459  **Size(bytes)**
... ... @@ -477,15 +477,41 @@
477 477  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
478 478  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
479 479  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
480 -* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
487 +* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
481 481  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
482 482  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
483 483  
484 -=== 2.4.6  Add Payload format in TTN V3 ===
485 485  
486 486  
487 -In TTN V3, use can add a custom payload so it shows friendly.
493 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
488 488  
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 +
489 489  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
490 490  
491 491  
... ... @@ -492,6 +492,7 @@
492 492  [[image:1664502649601-895.png]]
493 493  
494 494  
528 +
495 495  Add the decoder from this link: 
496 496  
497 497  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -501,39 +501,28 @@
501 501  [[image:1664502676891-606.png]]
502 502  
503 503  
504 -
505 505  == 2.5 Integrate with Datacake ==
506 506  
507 507  
508 -(((
509 509  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.
510 -)))
511 511  
512 -(((
513 513  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]]
514 -)))
515 515  
516 516  
517 517  [[image:1664502695771-538.png]]
518 518  
519 519  
520 -
521 521  == 2.6 Integrate with Tago ==
522 522  
523 523  
524 -(((
525 -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.
526 -)))
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.
527 527  
528 -(((
529 529  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]]
530 -)))
531 531  
532 532  
533 533  [[image:1664502715371-321.png]]
534 534  
535 535  
536 -
537 537  == 2.7  Datalog Feature ==
538 538  
539 539  
... ... @@ -549,7 +549,6 @@
549 549  [[image:image-20221009234629-1.png||height="390" width="577"]]
550 550  
551 551  
552 -
553 553  == 2.8 Alarm Mode ==
554 554  
555 555  
... ... @@ -559,15 +559,15 @@
559 559  
560 560  
561 561  (((
562 -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.
563 563  )))
564 564  
565 565  
566 566  (((
567 -Two ways to exit alarm mode:
589 +**Two ways to exit alarm mode:**
568 568  )))
569 569  
570 -* Server send a downlink command to exit.
592 +* Server sends a downlink command to exit.
571 571  * User fast press the RED button 10 times.
572 572  
573 573  (((
... ... @@ -575,7 +575,6 @@
575 575  )))
576 576  
577 577  
578 -
579 579  == 2.9 Transport Mode ==
580 580  
581 581  
... ... @@ -582,17 +582,16 @@
582 582  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.
583 583  
584 584  
585 -
586 586  == 2.10 LED Status ==
587 587  
588 588  
589 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
609 +(% border="1.5" style="background-color:#ffffcc; width:500px" %)
590 590  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
591 591  |(% 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
592 592  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
593 593  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
594 594  |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
595 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
615 +|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
596 596  |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
597 597  |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
598 598  |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
... ... @@ -600,6 +600,8 @@
600 600  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
601 601  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
602 602  
623 +
624 +
603 603  == 2.11 Button Function ==
604 604  
605 605  
... ... @@ -615,12 +615,14 @@
615 615  [[image:1664502854406-763.png]]
616 616  
617 617  
618 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
619 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
620 -|(% 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"]]
621 621  |(% 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
622 622  |(% 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.
623 623  
646 +
647 +
624 624  == 2.12 USB Port Function ==
625 625  
626 626  
... ... @@ -631,6 +631,8 @@
631 631  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
632 632  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
633 633  
658 +
659 +
634 634  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
635 635  
636 636  
... ... @@ -639,7 +639,6 @@
639 639  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
640 640  
641 641  
642 -
643 643  == 3.1 Access AT Command ==
644 644  
645 645  
... ... @@ -655,11 +655,9 @@
655 655  [[image:1664503022490-662.png]]
656 656  
657 657  
658 -
659 659  [[image:1664503035713-500.png]]
660 660  
661 661  
662 -
663 663  [[image:1664503047675-651.png]]
664 664  
665 665  
... ... @@ -666,7 +666,6 @@
666 666  
667 667  == 3.2 Command Set ==
668 668  
669 -
670 670  === 3.2.1 Set Transmit Interval ===
671 671  
672 672  
... ... @@ -684,7 +684,6 @@
684 684  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
685 685  
686 686  
687 -
688 688  === 3.2.2 Set Alarm Packet transmission interval ===
689 689  
690 690  
... ... @@ -702,7 +702,6 @@
702 702  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
703 703  
704 704  
705 -
706 706  === 3.2.3 Set Transport Mode Packet transmission interval ===
707 707  
708 708  
... ... @@ -717,10 +717,9 @@
717 717  
718 718  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
719 719  
720 -(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
740 +(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
721 721  
722 722  
723 -
724 724  === 3.2.4 Exit Alarm ===
725 725  
726 726  
... ... @@ -733,7 +733,6 @@
733 733  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
734 734  
735 735  
736 -
737 737  === 3.2.5 Disable/Enable LED flash ===
738 738  
739 739  
... ... @@ -751,7 +751,6 @@
751 751  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
752 752  
753 753  
754 -
755 755  === 3.2.6 Disable/Enable Transport Mode ===
756 756  
757 757  
... ... @@ -761,15 +761,14 @@
761 761  
762 762  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
763 763  
764 -Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
781 +Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
765 765  
766 766  
767 767  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
768 768  
769 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
786 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
770 770  
771 771  
772 -
773 773  === 3.2.7 Set Positioning Mode ===
774 774  
775 775  
... ... @@ -782,32 +782,40 @@
782 782  
783 783  (% style="color:#037691" %)** aa:**
784 784  
785 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
786 -* (% style="color:red" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
787 -* (% 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.
801 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
788 788  
803 +* (% style="color:red" %)**2: BLE or WiFi ONLY:                     **(%%)Only obtain iBeacon info via BLE and uplink  or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking.
804 +
805 +* (% style="color:red" %)**3: GPS/BLE Hybrid:                       **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
806 +
789 789  (% style="color:#037691" %)**bb:**
790 790  
791 791  * (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
810 +
792 792  * (% style="color:red" %)**1 :**(%%)  GPS +BAT State
793 793  
794 794  (% style="color:#037691" %)**cc:   **
795 795  
796 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
815 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
816 +
817 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
797 797  
798 798  (% style="color:blue" %)**Example:**
799 799  
800 - AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
801 - AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
802 - AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
821 + AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
803 803  
823 + AT+SMOD=1,1,0 ~-~->  GPS +BAT State
804 804  
805 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
825 + AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
806 806  
807 -(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
827 + AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
808 808  
809 809  
830 +* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
810 810  
832 +(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
833 +
834 +
811 811  === 3.2.8 Set MAX GPS position time ===
812 812  
813 813  
... ... @@ -814,7 +814,7 @@
814 814  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.
815 815  
816 816  
817 -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.
818 818  
819 819  
820 820  * (% style="color:blue" %)**AT Command:**
... ... @@ -829,7 +829,6 @@
829 829  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
830 830  
831 831  
832 -
833 833  === 3.2.9 Set PDOP value for GPS fix accuracy ===
834 834  
835 835  
... ... @@ -854,7 +854,7 @@
854 854  
855 855  
856 856  
857 -Disable/Enable the confirmation mode
880 +**Disable/Enable the confirmation mode**
858 858  
859 859  * (% style="color:blue" %)**AT Command:**
860 860  
... ... @@ -863,17 +863,16 @@
863 863  
864 864  **~ Example:**
865 865  
866 - AT+ CFM=0    **~-~->   ** Disable confirmation
889 + AT+CFM=0    **~-~->   ** Disable confirmation
867 867  
868 - AT+ CFM=1    **~-~->  ** Enable confirmation
891 + AT+CFM=1    **~-~->  ** Enable confirmation
869 869  
870 870  
871 871  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
872 872  
873 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
896 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
874 874  
875 875  
876 -
877 877  === 3.2.10  Auto Send None-ACK messages ===
878 878  
879 879  
... ... @@ -897,21 +897,66 @@
897 897  
898 898  === 3.2.11  Set BLEMASK to filter BLE iBeacon ===
899 899  
900 -BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. LBT1 will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
901 901  
902 -Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.
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.
903 903  
904 -(% style="color:blue" %)**AT Command:**(%%)
905 - AT+BLEMASK=123456     ~/~/ Set BLEMASK = 123456
906 - AT+BLEMASK=0  ~/~/ disable BLEMASK
925 +(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
907 907  
927 +(% style="color:blue" %)**AT Command:**
908 908  
909 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**(%%)
910 -Example:
911 -0xA5010203040506    ~/~/ Set BLEMASK to 123456
929 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
912 912  
931 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
913 913  
933 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
914 914  
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 +
915 915  = 4. Setting for Different Scenarios =
916 916  
917 917  
... ... @@ -918,7 +918,6 @@
918 918  
919 919  = 5. Upload Firmware =
920 920  
921 -
922 922  == 5.1 Firmware Change Log ==
923 923  
924 924  
... ... @@ -925,7 +925,6 @@
925 925  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
926 926  
927 927  
928 -
929 929  == 5.2 How to upgrade firmware ==
930 930  
931 931  
... ... @@ -952,34 +952,33 @@
952 952  [[image:1664503574618-659.png]]
953 953  
954 954  
1020 +
955 955  (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
956 956  
957 957  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
958 958  
959 959  
960 -Users need to use below files:
1026 +**Users need to use below files:**
961 961  
962 962  boot_app0.bin @0e000
963 963  
964 -ESP_LORA-eeprom-class.bin @ 0x10000
1030 +US915.bin @ 0x10000(Select the bin file of the frequency band you need)
965 965  
966 966  
967 -[[image:1664503593459-435.png]]
1033 +[[image:image-20221118105220-2.png]]
968 968  
969 969  
970 970  
971 971  After upgrade finish, it will show finish as below:
972 972  
973 -[[image:1664503611848-385.png]]
1039 +[[image:image-20221118105402-4.png]]
974 974  
975 975  
976 976  
977 977  = 6. Developer Guide =
978 978  
979 -
980 980  == 6.1 Compile Source Code ==
981 981  
982 -
983 983  === 6.1.1 Set up ARDUINO compile environment ===
984 984  
985 985  
... ... @@ -997,7 +997,18 @@
997 997  [[image:1664503715811-892.png]]
998 998  
999 999  
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.
1000 1000  
1066 +[[image:image-20221024105643-1.png]]
1067 +
1068 +**~ Figure1**
1069 +
1070 +
1071 +[[image:image-20221024105643-2.png]]
1072 +
1073 + **Figure2**
1074 +
1075 +
1001 1001  * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
1002 1002  
1003 1003  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
... ... @@ -1006,7 +1006,6 @@
1006 1006  [[image:1664503752288-974.png]]
1007 1007  
1008 1008  
1009 -
1010 1010  == 6.2 Source Code ==
1011 1011  
1012 1012  
... ... @@ -1027,10 +1027,8 @@
1027 1027  [[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1028 1028  
1029 1029  
1030 -
1031 1031  = 7.  FAQ =
1032 1032  
1033 -
1034 1034  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1035 1035  
1036 1036  
... ... @@ -1037,7 +1037,6 @@
1037 1037  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1038 1038  
1039 1039  
1040 -
1041 1041  == 7.2 What is the pin mapping for the USB program cable? ==
1042 1042  
1043 1043  
... ... @@ -1056,45 +1056,245 @@
1056 1056  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1057 1057  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1058 1058  
1059 -= 8.  Order Info =
1060 1060  
1061 1061  
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 +
1062 1062  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1063 1063  
1064 1064  (% style="color:blue" %)**XXX**(%%): The default frequency band
1065 1065  
1066 1066  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1323 +
1067 1067  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1325 +
1068 1068  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1327 +
1069 1069  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1329 +
1070 1070  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1331 +
1071 1071  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1333 +
1072 1072  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1073 1073  
1074 -= 9.  Packing Info =
1075 1075  
1076 1076  
1338 += 10.  Packing Info =
1339 +
1340 +
1077 1077  (% style="color:#037691" %)**Package Includes**:
1078 1078  
1079 1079  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1344 +
1080 1080  * USB recharge & program cable x 1
1081 1081  
1082 1082  (% style="color:#037691" %)**Dimensions and Weight**:
1083 1083  
1084 -* Device Size: 85 x 48 x 15 cm
1349 +* Device Size: 85 x 48 x 15 mm
1350 +
1085 1085  * Weight: 50g
1086 1086  
1087 -= 10. Support =
1088 1088  
1089 1089  
1355 += 11. Support =
1356 +
1357 +
1090 1090  * 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 +
1091 1091  * 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]].
1092 1092  
1093 -= 11.  Reference =
1094 1094  
1095 1095  
1364 += 12.  Reference =
1365 +
1366 +
1096 1096  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1368 +
1097 1097  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1098 -* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1099 1099  
1100 -
1371 +* [[**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