Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 196.1
edited by Bei Jinggeng
on 2023/03/07 13:59
Change comment: Uploaded new attachment "image-20230307135932-2.png", version {1}
To version 141.1
edited by Bei Jinggeng
on 2022/11/22 10:00
Change comment: Uploaded new attachment "image-20221122100004-4.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:1664505654417-133.png||_mstalt="293696"]]
2 +[[image:1664505654417-133.png]]
3 3  
4 4  
5 5  
... ... @@ -12,9 +12,9 @@
12 12  
13 13  
14 14  
15 -
16 16  = 1.  Introduction =
17 17  
17 +
18 18  == 1.1  What is TrackerD ==
19 19  
20 20  
... ... @@ -32,17 +32,21 @@
32 32  (((
33 33  The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
34 34  )))
35 +)))
35 35  
36 36  (((
37 37  TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.
39 +
40 +
38 38  )))
39 39  
40 -[[image:image-20230213110119-1.png||height="382" width="834"]]
43 +[[image:1664499921684-770.png]]
41 41  
42 42  
43 43  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
44 44  
45 45  
49 +
46 46  == 1.2 Specifications ==
47 47  
48 48  
... ... @@ -93,8 +93,6 @@
93 93  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94 94  * Tracking: max: 38mA
95 95  
96 -
97 -
98 98  == 1.3  Features ==
99 99  
100 100  
... ... @@ -113,8 +113,6 @@
113 113  * Tri-color LED, Alarm button
114 114  * Datalog
115 115  
116 -
117 -
118 118  == 1.4  Applications ==
119 119  
120 120  
... ... @@ -121,10 +121,9 @@
121 121  * Logistics and Supply Chain Management
122 122  * Human tracking
123 123  
124 -
125 -
126 126  = 2.  Use TrackerD =
127 127  
126 +
128 128  == 2.1 How it works? ==
129 129  
130 130  
... ... @@ -131,6 +131,7 @@
131 131  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.
132 132  
133 133  
133 +
134 134  == 2.2 Quick guide to connect to LoRaWAN server ==
135 135  
136 136  
... ... @@ -137,7 +137,7 @@
137 137  Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example. 
138 138  
139 139  
140 -[[image:image-20230213110214-2.png||height="388" width="847"]]
140 +[[image:1664501652064-326.png]]
141 141  
142 142  
143 143  
... ... @@ -149,7 +149,7 @@
149 149  Each TrackerD is shipped with a sticker with the default device EUI as below:
150 150  
151 151  
152 -[[image:1664501677253-891.png||_mstalt="296569"]]
152 +[[image:1664501677253-891.png]]
153 153  
154 154  
155 155  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -158,14 +158,14 @@
158 158  **__Add APP EUI in the application:__**
159 159  
160 160  
161 -[[image:1664501711466-918.png||_mstalt="295828"]]
161 +[[image:1664501711466-918.png]]
162 162  
163 163  
164 164  
165 -[[image:1664501721248-725.png||_mstalt="294450"]]
165 +[[image:1664501721248-725.png]]
166 166  
167 167  
168 -[[image:1664501734705-405.png||_mstalt="293306"]]
168 +[[image:1664501734705-405.png]]
169 169  
170 170  
171 171  
... ... @@ -172,20 +172,21 @@
172 172  **__Add APP KEY and DEV EUI:__**
173 173  
174 174  
175 -[[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||_mstalt="298233" alt="1654671889112-678.png"]]
175 +[[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  
179 179  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
180 180  
181 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
181 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
182 182  
183 -[[image:1664502835802-546.png||_mstalt="295061"]]
183 +[[image:1664502835802-546.png]]
184 184  
185 185  
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 +
189 189  == 2.3  Positioning Mode(SMOD) ==
190 190  
191 191  
... ... @@ -198,8 +198,10 @@
198 198  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
199 199  
200 200  
202 +
201 201  == 2.4  Uplink Payload ==
202 202  
205 +
203 203  === 2.4.1 Uplink FPORT~=5, Device Status ===
204 204  
205 205  
... ... @@ -209,10 +209,10 @@
209 209  
210 210  
211 211  (% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
212 -|=(% 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;" %)1|=(% style="width: 40px;" %)1
215 +|=(% 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 -[[image:1665301570342-765.png||_mstalt="294580"]]
218 +[[image:1665301570342-765.png]]
216 216  
217 217  
218 218  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -256,7 +256,7 @@
256 256  (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
257 257  
258 258  (% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
259 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)1bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
262 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
260 260  |=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
261 261  
262 262  (% style="color:blue" %)** SMOD：**
... ... @@ -279,17 +279,15 @@
279 279  
280 280  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
281 281  
282 -(% _mstmutation="1" style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
285 +(% 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:412.222px" %)
288 -|=(% scope="row" style="width: 75px;" %)**Size(bit)**|(% style="width:68px" %)5 Bits|(% style="width:87px" %)1 Bit|(% style="width:49px" %)1 Bit|(% style="width:126px" %)1 Bit
289 -|=(% style="width: 75px;" %)**Value**|(% style="width:68px" %)Reserve|(% style="width:87px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:49px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
290 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
291 +|=(% 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
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"]]
290 290  
291 -
292 -
293 293  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
294 294  
295 295  
... ... @@ -308,20 +308,20 @@
308 308  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
309 309  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
310 310  
311 -[[image:1665301636888-168.png||_mstalt="298012"]]
312 +[[image:1665301636888-168.png]]
312 312  
313 313  
314 314  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
315 315  
316 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:279.222px" %)
317 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:69px" %)1 bit|(% style="width:63px" %)14 bits
318 -|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:69px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
317 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
318 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
319 +|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
319 319  
320 320  ==== (% style="color:blue" %)**FLAG:**(%%) ====
321 321  
322 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:183.222px" %)
323 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2 bits|(% style="width:52px" %)1 bit
324 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:52px" %)[[LON>>||anchor="HLON:"]]
323 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
324 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
325 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
325 325  
326 326  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
327 327  
... ... @@ -338,12 +338,12 @@
338 338  2.  In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
339 339  
340 340  
341 -[[image:1664502116362-706.png||_mstalt="293306"]]
342 +[[image:1664502116362-706.png]]
342 342  
343 343  
344 344  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
345 345  
346 -[[image:1664502166010-515.png||_mstalt="291395"]]
347 +[[image:1664502166010-515.png]]
347 347  
348 348  
349 349  
... ... @@ -366,9 +366,6 @@
366 366  * 3.40v ~~ 3.69v:  20% ~~ 40%
367 367  * < 3.39v:  0~~20%
368 368  
369 -(% style="display:none" %) (%%)
370 -
371 -
372 372  ==== (% style="color:blue" %)**MOD:**(%%) ====
373 373  
374 374  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -409,6 +409,7 @@
409 409  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
410 410  
411 411  
410 +
412 412  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
413 413  
414 414  
... ... @@ -424,13 +424,14 @@
424 424  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
425 425  
426 426  (% class="wikigeneratedid" %)
427 -[[image:1665301687277-443.png||_mstalt="296140"]]
426 +[[image:1665301687277-443.png]]
428 428  
429 429  
429 +
430 430  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
431 431  
432 432  
433 -Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
433 +Set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
434 434  
435 435  
436 436  (% style="color:red" %)**Note for this mode:**
... ... @@ -447,9 +447,10 @@
447 447  )))|4|4|2|1|1|1|1|1
448 448  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
449 449  
450 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
450 +[[image:image-20221009160309-2.png]]
451 451  
452 452  
453 +
453 453  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
454 454  
455 455  
... ... @@ -474,7 +474,7 @@
474 474  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
475 475  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
476 476  
477 -[[image:1664502425687-834.png||_mstalt="296738"]]
478 +[[image:1664502425687-834.png]]
478 478  
479 479  
480 480  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -485,32 +485,9 @@
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  
488 -(% style="display:none" %) (%%)
489 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
489 489  
490 490  
491 -=== 2.4.6  Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
492 -
493 -
494 -The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
495 -
496 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
497 -|**Size(bytes)**|2|1
498 -|**Value**|[[Alarm & BAT>>path:#HAlarm26BAT:]]|Mod+lon
499 -
500 - [[image:image-20230302145315-1.png]]
501 -
502 -alarm=(bytes[0] & 0x40)  ~/~/ Alarm status
503 -
504 -batV=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;  ~/~/ Battery,units:V
505 -
506 -mod = bytes[2] & 0xC0;
507 -
508 -Lon=(bytes[2] & 0x20)
509 -
510 -
511 -=== 2.4.7  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
512 -
513 -
514 514  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.
515 515  
516 516  
... ... @@ -523,7 +523,7 @@
523 523  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
524 524  
525 525  (% class="wikigeneratedid" %)
526 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
504 +[[image:1667288597595-714.png||height="212" width="1151"]]
527 527  
528 528  
529 529  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -530,21 +530,17 @@
530 530  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
531 531  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
532 532  
533 -(% style="display:none" %) (%%)
511 +=== 2.4.7  Add Payload format in TTN V3 ===
534 534  
535 535  
536 -=== 2.4.8  Add Payload format in TTN V3 ===
537 -
538 -
539 539  In TTN V3, user can add a custom payload so it shows friendly.
540 540  
541 541  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
542 542  
543 543  
544 -[[image:1664502649601-895.png||_mstalt="296985"]]
519 +[[image:1664502649601-895.png]]
545 545  
546 546  
547 -
548 548  Add the decoder from this link: 
549 549  
550 550  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -551,9 +551,10 @@
551 551  
552 552  Save the change the uplink message will be parsed. As below:
553 553  
554 -[[image:1664502676891-606.png||_mstalt="296673"]]
528 +[[image:1664502676891-606.png]]
555 555  
556 556  
531 +
557 557  == 2.5 Integrate with Datacake ==
558 558  
559 559  
... ... @@ -562,9 +562,10 @@
562 562  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]]
563 563  
564 564  
565 -[[image:1664502695771-538.png||_mstalt="297349"]]
540 +[[image:1664502695771-538.png]]
566 566  
567 567  
543 +
568 568  == 2.6 Integrate with Tago ==
569 569  
570 570  
... ... @@ -573,24 +573,26 @@
573 573  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]]
574 574  
575 575  
576 -[[image:1664502715371-321.png||_mstalt="292162"]]
552 +[[image:1664502715371-321.png]]
577 577  
578 578  
555 +
579 579  == 2.7  Datalog Feature ==
580 580  
581 581  
582 582  total 273 entries,by default,
583 583  
584 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
561 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
585 585  
586 586  Example use case.
587 587  
588 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
565 +[[image:image-20221009234703-2.png||height="328" width="899"]]
589 589  
590 590  
591 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
568 +[[image:image-20221009234629-1.png||height="390" width="577"]]
592 592  
593 593  
571 +
594 594  == 2.8 Alarm Mode ==
595 595  
596 596  
... ... @@ -605,7 +605,7 @@
605 605  
606 606  
607 607  (((
608 -**Two ways to exit alarm mode:**
586 +Two ways to exit alarm mode:
609 609  )))
610 610  
611 611  * Server sends a downlink command to exit.
... ... @@ -616,18 +616,14 @@
616 616  )))
617 617  
618 618  
597 +
619 619  == 2.9 Transport Mode ==
620 620  
621 621  
622 622  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.
623 623  
624 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
625 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
626 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
627 627  
628 -(% style="display:none" %) (%%)
629 629  
630 -
631 631  == 2.10 LED Status ==
632 632  
633 633  
... ... @@ -645,15 +645,12 @@
645 645  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
646 646  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
647 647  
648 -(% style="display:none" %) (%%)
649 -
650 -
651 651  == 2.11 Button Function ==
652 652  
653 653  
654 654  (% style="color:blue" %)**RESET button:**
655 655  
656 -[[image:1664502835802-546.png||_mstalt="295061"]]
627 +[[image:1664502835802-546.png]]
657 657  
658 658  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
659 659  
... ... @@ -660,9 +660,8 @@
660 660  
661 661  (% style="color:red" %)**RED button:**
662 662  
663 -[[image:image-20230213110506-3.png]](% style="display:none" %)
634 +[[image:1664502854406-763.png]]
664 664  
665 -(% style="display:none" %) (%%)
666 666  
667 667  (% border="1" style="background-color:#ffffcc; width:510px" %)
668 668  |=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
... ... @@ -670,9 +670,6 @@
670 670  |(% 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
671 671  |(% 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.
672 672  
673 -(% style="display:none" %) (%%)
674 -
675 -
676 676  == 2.12 USB Port Function ==
677 677  
678 678  
... ... @@ -683,9 +683,6 @@
683 683  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
684 684  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
685 685  
686 -(% style="display:none" %) (%%)
687 -
688 -
689 689  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
690 690  
691 691  
... ... @@ -694,6 +694,7 @@
694 694  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
695 695  
696 696  
661 +
697 697  == 3.1 Access AT Command ==
698 698  
699 699  
... ... @@ -700,24 +700,25 @@
700 700  TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below.
701 701  
702 702  
703 -[[image:1664502999401-486.png||_mstalt="296985"]]
668 +[[image:1664502999401-486.png]]
704 704  
705 705  
706 706  In PC, User needs to set serial tool baud rate to (% style="color:green" %)**115200**(%%) to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands:
707 707  
708 708  
709 -[[image:1664503022490-662.png||_mstalt="293332"]]
674 +[[image:1664503022490-662.png]]
710 710  
711 711  
712 -[[image:1664503035713-500.png||_mstalt="291096"]]
677 +[[image:1664503035713-500.png]]
713 713  
714 714  
715 -[[image:1664503047675-651.png||_mstalt="295386"]]
680 +[[image:1664503047675-651.png]]
716 716  
717 -(% style="display:none" %) (%%)
718 718  
683 +
719 719  == 3.2 Command Set ==
720 720  
686 +
721 721  === 3.2.1 Set Transmit Interval ===
722 722  
723 723  
... ... @@ -735,6 +735,7 @@
735 735  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
736 736  
737 737  
704 +
738 738  === 3.2.2 Set Alarm Packet transmission interval ===
739 739  
740 740  
... ... @@ -752,6 +752,7 @@
752 752  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
753 753  
754 754  
722 +
755 755  === 3.2.3 Set Transport Mode Packet transmission interval ===
756 756  
757 757  
... ... @@ -769,6 +769,7 @@
769 769  (% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
770 770  
771 771  
740 +
772 772  === 3.2.4 Exit Alarm ===
773 773  
774 774  
... ... @@ -781,9 +781,10 @@
781 781  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
782 782  
783 783  
784 -=== 3.2.5 Disable/Enable LED flash and buzzer ===
785 785  
754 +=== 3.2.5 Disable/Enable LED flash ===
786 786  
756 +
787 787  Disable/Enable LED for position, downlink and uplink
788 788  
789 789  * (% style="color:blue" %)**AT Command:**
... ... @@ -798,6 +798,7 @@
798 798  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
799 799  
800 800  
771 +
801 801  === 3.2.6 Disable/Enable Transport Mode ===
802 802  
803 803  
... ... @@ -815,6 +815,7 @@
815 815  (% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
816 816  
817 817  
789 +
818 818  === 3.2.7 Set Positioning Mode ===
819 819  
820 820  
... ... @@ -841,9 +841,9 @@
841 841  
842 842  (% style="color:#037691" %)**cc:   **
843 843  
844 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
816 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
845 845  
846 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
818 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
847 847  
848 848  (% style="color:blue" %)**Example:**
849 849  
... ... @@ -861,6 +861,7 @@
861 861  (% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
862 862  
863 863  
836 +
864 864  === 3.2.8 Set MAX GPS position time ===
865 865  
866 866  
... ... @@ -867,7 +867,7 @@
867 867  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.
868 868  
869 869  
870 -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.
843 +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.
871 871  
872 872  
873 873  * (% style="color:blue" %)**AT Command:**
... ... @@ -882,6 +882,7 @@
882 882  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
883 883  
884 884  
858 +
885 885  === 3.2.9 Set PDOP value for GPS fix accuracy ===
886 886  
887 887  
... ... @@ -905,8 +905,8 @@
905 905  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
906 906  
907 907  
908 -=== 3.2.10 Disable/Enable the confirmation mode ===
909 909  
883 +Disable/Enable the confirmation mode
910 910  
911 911  * (% style="color:blue" %)**AT Command:**
912 912  
... ... @@ -925,9 +925,10 @@
925 925  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
926 926  
927 927  
928 -=== 3.2.11  Auto Send None-ACK messages ===
929 929  
903 +=== 3.2.10  Auto Send None-ACK messages ===
930 930  
905 +
931 931  TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
932 932  
933 933  
... ... @@ -943,12 +943,13 @@
943 943  
944 944  * (% style="color:blue" %)**Downlink Command: 0x34**
945 945  
946 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
921 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
947 947  
948 948  
949 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
950 950  
925 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
951 951  
927 +
952 952  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.
953 953  
954 954  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
... ... @@ -955,18 +955,19 @@
955 955  
956 956  (% style="color:blue" %)**AT Command:**
957 957  
958 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
934 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
959 959  
960 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
936 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
961 961  
962 962  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
963 963  
964 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
940 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
965 965  
966 966  
967 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
968 968  
944 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
969 969  
946 +
970 970  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.
971 971  
972 972  (% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
... ... @@ -973,61 +973,44 @@
973 973  
974 974  (% style="color:blue" %)**AT Command:**
975 975  
976 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
953 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
977 977  
978 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
955 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
979 979  
980 980  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
981 981  
982 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
959 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
983 983  
984 984  
985 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
986 986  
963 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
987 987  
965 +
988 988  Users can use this feature to enable/disable Information printing.
989 989  
990 990  (% style="color:blue" %)**AT Command:**
991 991  
992 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
970 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
993 993  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
994 994  
995 995  
996 -=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
997 997  
975 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
998 998  
977 +
999 999  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
1000 1000  
1001 1001  (% style="color:blue" %)**AT Command:**
1002 1002  
1003 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
982 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
1004 1004  
1005 1005  
1006 1006  (% style="color:blue" %)**Downlink Payload:0X24**
1007 1007  
1008 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
987 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
1009 1009  
1010 1010  
1011 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
1012 1012  
1013 -
1014 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
1015 -
1016 -(% style="color:blue" %)**AT Command:**
1017 -
1018 -(% style="color:#037691" %)**AT+PT=xx**
1019 -
1020 - Example:
1021 -
1022 - AT+PT=14    ~-~->    Set to detect car motion.
1023 -
1024 - AT+PT=41  ~-~->    set to detect walk motion.
1025 -
1026 -
1027 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
1028 -0xB4 14          ~/~/  Same as AT+PT=14
1029 -
1030 -
1031 1031  = 4. Setting for Different Scenarios =
1032 1032  
1033 1033  
... ... @@ -1034,6 +1034,7 @@
1034 1034  
1035 1035  = 5. Upload Firmware =
1036 1036  
997 +
1037 1037  == 5.1 Firmware Change Log ==
1038 1038  
1039 1039  
... ... @@ -1040,6 +1040,7 @@
1040 1040  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
1041 1041  
1042 1042  
1004 +
1043 1043  == 5.2 How to upgrade firmware ==
1044 1044  
1045 1045  
... ... @@ -1060,10 +1060,10 @@
1060 1060  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1061 1061  
1062 1062  
1063 -[[image:1664503563660-578.png||_mstalt="296777"]]
1025 +[[image:1664503563660-578.png]]
1064 1064  
1065 1065  
1066 -[[image:1664503574618-659.png||_mstalt="297986"]]
1028 +[[image:1664503574618-659.png]]
1067 1067  
1068 1068  
1069 1069  
... ... @@ -1072,7 +1072,7 @@
1072 1072  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
1073 1073  
1074 1074  
1075 -**Users need to use below files:**
1037 +Users need to use below files:
1076 1076  
1077 1077  boot_app0.bin @0e000
1078 1078  
... ... @@ -1079,19 +1079,22 @@
1079 1079  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1080 1080  
1081 1081  
1082 -[[image:image-20221207120501-1.png]]
1044 +[[image:image-20221118105220-2.png]]
1083 1083  
1084 1084  
1085 1085  
1086 1086  After upgrade finish, it will show finish as below:
1087 1087  
1088 -[[image:image-20221207133911-7.png]]
1050 +[[image:image-20221118105402-4.png]]
1089 1089  
1090 1090  
1053 +
1091 1091  = 6. Developer Guide =
1092 1092  
1056 +
1093 1093  == 6.1 Compile Source Code ==
1094 1094  
1059 +
1095 1095  === 6.1.1 Set up ARDUINO compile environment ===
1096 1096  
1097 1097  
... ... @@ -1100,81 +1100,24 @@
1100 1100  Install IDE on PC, open and click (% style="color:#037691" %)**File ~-~-> Preference**,(%%) add the following URL:  [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fdl.espressif.com%2Fdl%2Fpackage_esp32_index.json]]
1101 1101  
1102 1102  
1103 -[[image:1664503635019-941.png||_mstalt="294658"]]
1068 +[[image:1664503635019-941.png]]
1104 1104  
1105 1105  
1106 1106  
1107 1107  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1108 1108  
1109 -[[image:1664503715811-892.png||_mstalt="295698"]]
1074 +[[image:1664503715811-892.png]]
1110 1110  
1111 1111  
1112 -=== 6.1.2  Build the development environment ===
1113 -
1114 -
1115 -**~1. Download and install arduino IDE**
1116 -
1117 -[[https:~~/~~/www.arduino.cn/thread-5838-1-1.html>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fwww.arduino.cn%2Fthread-5838-1-1.html]]
1118 -
1119 -
1120 -**2. Download the ESP32 development package in the arduino IDE**
1121 -
1122 -[[image:image-20221213100007-1.png]]
1123 -
1124 -
1125 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1126 -
1127 -[[image:image-20221213100626-2.png]]
1128 -
1129 -
1130 -Restart the IDE after the addition is complete, then:
1131 -
1132 -[[image:image-20221213100808-3.png||height="679" width="649"]]
1133 -
1134 -
1135 -[[image:image-20221213101040-4.png]]
1136 -
1137 -
1138 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1139 -Don't quit halfway.~~! If you quit halfway, there is a high probability that it will freeze, and you will need to download again next time. (If you click to continue downloading, an error will be reported after completion)**
1140 -
1141 -
1142 -Then enter a long waiting process. If you don't want to wait, you can go to the Internet to download directly, and then import:
1143 -
1144 -(% style="color:blue" %)**Methods as below:**
1145 -
1146 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1147 -
1148 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1149 -
1150 1150  (% 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.
1151 1151  
1152 -[[image:image-20221213102311-5.png||height="582" width="711"]]
1079 +[[image:image-20221024105643-1.png]]
1153 1153  
1154 -
1155 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1156 -
1157 -[[image:image-20221213102334-6.png]]
1158 -
1159 -(% style="color:red" %)**Note: This step requires a python environment**
1160 -
1161 -
1162 -Either way, in the end:
1163 -
1164 -The final effect is to open the arduino and you can see the esp32
1165 -
1166 -[[image:image-20221213110952-8.png||height="866" width="711"]]
1167 -
1168 -
1169 -
1170 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1171 -
1172 1172  **~ Figure1**
1173 1173  
1174 1174  
1084 +[[image:image-20221024105643-2.png]]
1175 1175  
1176 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1177 -
1178 1178   **Figure2**
1179 1179  
1180 1180  
... ... @@ -1183,31 +1183,34 @@
1183 1183  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1184 1184  
1185 1185  
1186 -[[image:1664503752288-974.png||_mstalt="298194"]]
1094 +[[image:1664503752288-974.png]]
1187 1187  
1188 1188  
1097 +
1189 1189  == 6.2 Source Code ==
1190 1190  
1191 1191  
1192 1192  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1193 1193  
1194 -[[image:1664503794261-827.png||_mstalt="296387"]]
1103 +[[image:1664503794261-827.png]]
1195 1195  
1196 1196  
1197 1197  
1198 1198  * (% style="color:blue" %)**Click to upload**
1199 1199  
1200 -[[image:1664503808294-336.png||_mstalt="295711"]]
1109 +[[image:1664503808294-336.png]]
1201 1201  
1202 1202  
1203 1203  
1204 1204  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1205 1205  
1206 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1115 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1207 1207  
1208 1208  
1118 +
1209 1209  = 7.  FAQ =
1210 1210  
1121 +
1211 1211  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1212 1212  
1213 1213  
... ... @@ -1214,10 +1214,11 @@
1214 1214  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1215 1215  
1216 1216  
1128 +
1217 1217  == 7.2 What is the pin mapping for the USB program cable? ==
1218 1218  
1219 1219  
1220 -[[image:1664499635206-262.png||_mstalt="295360"]]
1132 +[[image:1664499635206-262.png]]
1221 1221  
1222 1222  
1223 1223  
... ... @@ -1232,11 +1232,9 @@
1232 1232  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1233 1233  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1234 1234  
1235 -(% style="display:none" %) (%%)
1236 -
1237 -
1238 1238  == 7.3 Notes on using different serial port tools for TrackerD ==
1239 1239  
1149 +
1240 1240  === 7.3.1  Serial port utility ===
1241 1241  
1242 1242  
... ... @@ -1244,16 +1244,18 @@
1244 1244  
1245 1245  Need to adjust the data stream to RTS/CTS on physical restart.
1246 1246  
1157 +
1247 1247  (% class="wikigeneratedid" %)
1248 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1159 +[[image:image-20221102140621-1.png]]
1249 1249  
1250 1250  
1251 -
1252 1252  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1253 1253  
1254 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1255 1255  
1165 +[[image:image-20221102140638-2.png]]
1256 1256  
1167 +
1168 +
1257 1257  === 7.3.2  SecureCRT ===
1258 1258  
1259 1259  
... ... @@ -1260,22 +1260,23 @@
1260 1260  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.
1261 1261  
1262 1262  
1263 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1175 +[[image:image-20221102140704-3.png]]
1264 1264  
1265 1265  
1266 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1178 +[[image:image-20221102140712-4.png]]
1267 1267  
1268 1268  
1181 +
1269 1269  === 7.3.3  PUTTY ===
1270 1270  
1271 1271  
1272 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1185 +[[image:image-20221102140748-5.png]]
1273 1273  
1274 1274  
1275 1275  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.
1276 1276  
1277 1277  
1278 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1191 +[[image:image-20221102140801-6.png]]
1279 1279  
1280 1280  
1281 1281  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1287,52 +1287,38 @@
1287 1287  See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1288 1288  )))
1289 1289  
1290 -**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1203 +1.When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.
1291 1291  
1205 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1292 1292  
1293 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1207 +2.Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).
1294 1294  
1209 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1295 1295  
1211 +3.Compile the AS923_JP band, please refer to the intention shown
1296 1296  
1297 -**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1213 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1298 1298  
1215 +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.
1299 1299  
1300 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1217 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1301 1301  
1219 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1302 1302  
1303 1303  
1304 -**3. Compile the AS923_JP band, please refer to the intention shown**
1305 1305  
1306 -
1307 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1308 -
1309 -
1310 -
1311 -**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.**
1312 -
1313 -
1314 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1315 -
1316 -
1317 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1318 -
1319 -
1320 -== 7.5 Are there example python example for BLE Indoor Positioning? ==
1321 -
1322 -
1323 -[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1324 -
1325 -
1326 1326  = 8  Trouble Shooting =
1327 1327  
1225 +
1328 1328  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1329 1329  
1330 1330  
1331 1331  (((
1332 -Before firmware v1.4.0: When the Transport Mode is enabled ((% style="color:blue" %)**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
1230 +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
1333 1333  )))
1334 1334  
1335 1335  
1234 +
1336 1336  == 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1337 1337  
1338 1338  
... ... @@ -1341,152 +1341,46 @@
1341 1341  )))
1342 1342  
1343 1343  
1243 +
1344 1344  == 8.3  Problem after Upgrading Firmware ==
1345 1345  
1346 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1246 +=== 8.3.1 Continue Restart after upgrading ===
1347 1347  
1348 1348  
1349 -**Error Output**
1350 -
1351 -
1352 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1353 -
1354 -
1355 1355  (((
1356 -Some partition is missed during upgrade, please upgrade below four files as example:
1357 -
1358 -[[image:image-20221207120524-2.png]]
1250 +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
1359 1359  )))
1360 1360  
1361 1361  
1362 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1254 +[[image:image-20221118105249-3.png]]
1363 1363  
1364 1364  
1257 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1258 +
1365 1365  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
1366 1366  
1367 1367  
1368 -=== 8.3.3 "flash read err" after upgrade firmware ===
1262 +(((
1263 +== 8.5 How to deal with unsuccessful GPS positioning? ==
1369 1369  
1370 -
1371 -Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1372 -
1373 -
1374 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1375 -
1376 -
1377 -User need to upgrade again with below four files to solve this issue.
1378 -
1379 - [[image:image-20221207120530-3.png]]
1380 -
1381 - **Figure 2**
1382 -
1383 -
1384 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1385 -
1386 -
1387 -User might erase the entire flash include keys and default settings which cause this issue.
1388 -
1389 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1390 -
1391 -
1392 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1393 -
1394 -
1395 -Please (% style="color:blue" %)**AT+FDR**(%%) which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1396 -
1397 -After AT+FDR. please set
1398 -
1399 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1400 -
1401 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1402 -
1403 -**Example:**
1404 -
1405 -AT+PDOP=7.00
1406 -
1407 -AT+FTIME=180
1408 -
1409 -AT+DEUI=70B3D57ED0053981  
1410 -
1411 -AT+APPEUI=D23345667BCBCCAF
1412 -
1413 -AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1414 -
1415 -AT+DADDR=260b4dce    ( no need for OTAA)
1416 -
1417 -AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1418 -
1419 -AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1420 -
1421 -
1422 -== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1423 -
1424 -
1425 -Please download version 1.4.2 again
1426 -
1427 -
1428 -== 8.5  How to deal with unsuccessful GPS positioning? ==
1429 -
1430 -
1431 -1） Make Sure the device is in Open Area where can see the sky.
1432 -
1265 +1） Make Sure the device is in Open Area where can see the sky. 
1433 1433  2)  Set PDOP to a higher value.
1434 1434  
1435 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1268 + AT+PDOP=2(can be positioned precisely.）
1436 1436  
1437 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1270 + AT+PDOP=7(Quickly locate in open spaces）
1438 1438  
1439 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1272 + AT+PDOP=14.7(Positioning can be acquired in complex environments）
1440 1440  
1441 1441  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
1275 +)))
1442 1442  
1443 1443  
1444 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1278 +== 8.6 When positioning, it will restart or the PDOP setting is unsuccessful ==
1445 1445  
1280 +Please download version 1.4.2 again
1446 1446  
1447 -When upgrading, use the erase button to upgrade
1448 1448  
1449 -[[image:image-20221207120536-4.png]]
1450 -
1451 -
1452 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1453 -
1454 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1455 -
1456 -
1457 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1458 -
1459 -[[image:image-20221207134028-8.png]]
1460 -
1461 -
1462 -Reboot information after upgrade
1463 -
1464 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1465 -
1466 -
1467 -Use **AT+FDR** command to reset and then use **AT+CFG** to check whether the configuration is back to normal
1468 -
1469 -[[image:image-20221128111850-5.png]]
1470 -
1471 -
1472 -After the parameters return to normal, upgrade to the version you need again
1473 -
1474 -[[image:image-20221207120601-5.png]]
1475 -
1476 -
1477 -At this point, the parameters return to normal after running AT+FDR again
1478 -
1479 -[[image:image-20221128112035-7.png]]
1480 -
1481 -
1482 -== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1483 -
1484 -
1485 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1486 -
1487 -2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1488 -
1489 -
1490 1490  = 9.  Order Info =
1491 1491  
1492 1492  
... ... @@ -1495,22 +1495,13 @@
1495 1495  (% style="color:blue" %)**XXX**(%%): The default frequency band
1496 1496  
1497 1497  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1498 -
1499 1499  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1500 -
1501 1501  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1502 -
1503 1503  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1504 -
1505 1505  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1506 -
1507 1507  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1508 -
1509 1509  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1510 1510  
1511 -(% style="display:none" %) (%%)
1512 -
1513 -
1514 1514  = 10.  Packing Info =
1515 1515  
1516 1516  
... ... @@ -1517,36 +1517,22 @@
1517 1517  (% style="color:#037691" %)**Package Includes**:
1518 1518  
1519 1519  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1520 -
1521 1521  * USB recharge & program cable x 1
1522 1522  
1523 1523  (% style="color:#037691" %)**Dimensions and Weight**:
1524 1524  
1525 1525  * Device Size: 85 x 48 x 15 mm
1526 -
1527 1527  * Weight: 50g
1528 1528  
1529 -(% style="display:none" %) (%%)
1530 -
1531 -
1532 1532  = 11. Support =
1533 1533  
1534 1534  
1535 1535  * 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.
1536 -
1537 1537  * 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]].
1538 1538  
1539 -(% style="display:none" %) (%%)
1540 -
1541 -
1542 1542  = 12.  Reference =
1543 1543  
1544 1544  
1545 1545  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1546 -
1547 1547  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1548 -
1549 1549  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1550 -
1551 -
1552 -)))
image-20221128102938-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -41.3 KB
Content
image-20221128103040-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -19.2 KB
Content
image-20221128110503-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.6 KB
Content
image-20221128111443-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -15.6 KB
Content
image-20221128111850-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.5 KB
Content
image-20221128111951-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -45.4 KB
Content
image-20221128112035-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -14.7 KB
Content
image-20221207120501-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120524-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120530-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120536-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207120601-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -44.5 KB
Content
image-20221207133836-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.1 KB
Content
image-20221207133911-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -46.3 KB
Content
image-20221207134028-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.3 KB
Content
image-20221213100007-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -32.7 KB
Content
image-20221213100626-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -35.7 KB
Content
image-20221213100808-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -91.3 KB
Content
image-20221213101040-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -26.3 KB
Content
image-20221213102311-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.7 KB
Content
image-20221213102334-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.5 KB
Content
image-20221213102718-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -116.5 KB
Content
image-20221213110952-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -152.8 KB
Content
image-20230213110119-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -182.3 KB
Content
image-20230213110214-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -182.3 KB
Content
image-20230213110506-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.8 KB
Content
image-20230302145315-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -35.1 KB
Content
image-20230307135914-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -131.8 KB
Content
image-20230307135932-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -109.7 KB
Content