Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 208.3
edited by Xiaoling
on 2023/04/26 08:58
Change comment: There is no comment for this version
To version 144.1
edited by Edwin Chen
on 2022/11/22 12:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
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,7 +12,6 @@
12 12  
13 13  
14 14  
15 -
16 16  = 1.  Introduction =
17 17  
18 18  == 1.1  What is TrackerD ==
... ... @@ -32,12 +32,15 @@
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  )))
34 +)))
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.
38 +
39 +
38 38  )))
39 39  
40 -[[image:image-20230213110119-1.png||height="382" width="834"]]
42 +[[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.**
... ... @@ -93,9 +93,7 @@
93 93  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94 94  * Tracking: max: 38mA
95 95  
96 -(% style="display:none" %)
97 97  
98 -
99 99  == 1.3  Features ==
100 100  
101 101  
... ... @@ -114,9 +114,7 @@
114 114  * Tri-color LED, Alarm button
115 115  * Datalog
116 116  
117 -(% style="display:none" %)
118 118  
119 -
120 120  == 1.4  Applications ==
121 121  
122 122  
... ... @@ -123,9 +123,7 @@
123 123  * Logistics and Supply Chain Management
124 124  * Human tracking
125 125  
126 -(% style="display:none" %)
127 127  
128 -
129 129  = 2.  Use TrackerD =
130 130  
131 131  == 2.1 How it works? ==
... ... @@ -140,7 +140,7 @@
140 140  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. 
141 141  
142 142  
143 -[[image:image-20230213110214-2.png||height="388" width="847"]]
139 +[[image:1664501652064-326.png]]
144 144  
145 145  
146 146  
... ... @@ -152,7 +152,7 @@
152 152  Each TrackerD is shipped with a sticker with the default device EUI as below:
153 153  
154 154  
155 -[[image:image-20230426085815-1.png]]
151 +[[image:1664501677253-891.png]]
156 156  
157 157  
158 158  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -161,14 +161,14 @@
161 161  **__Add APP EUI in the application:__**
162 162  
163 163  
164 -[[image:1664501711466-918.png||_mstalt="295828"]]
160 +[[image:1664501711466-918.png]]
165 165  
166 166  
167 167  
168 -[[image:1664501721248-725.png||_mstalt="294450"]]
164 +[[image:1664501721248-725.png]]
169 169  
170 170  
171 -[[image:1664501734705-405.png||_mstalt="293306"]]
167 +[[image:1664501734705-405.png]]
172 172  
173 173  
174 174  
... ... @@ -175,15 +175,15 @@
175 175  **__Add APP KEY and DEV EUI:__**
176 176  
177 177  
178 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]]
174 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]]
179 179  
180 180  
181 181  
182 182  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
183 183  
184 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
180 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
185 185  
186 -[[image:1664502835802-546.png||_mstalt="295061"]]
182 +[[image:1664502835802-546.png]]
187 187  
188 188  
189 189  (% 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.
... ... @@ -212,10 +212,10 @@
212 212  
213 213  
214 214  (% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
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;" %)1|=(% style="width: 40px;" %)1
211 +|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1
216 216  |=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
217 217  
218 -[[image:1665301570342-765.png||_mstalt="294580"]]
214 +[[image:1665301570342-765.png]]
219 219  
220 220  
221 221  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -259,7 +259,7 @@
259 259  (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
260 260  
261 261  (% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
262 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)1bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
258 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
263 263  |=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
264 264  
265 265  (% style="color:blue" %)** SMOD：**
... ... @@ -282,18 +282,16 @@
282 282  
283 283  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
284 284  
285 -(% _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)(%%)  
281 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
286 286  
287 287  
288 288  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
289 289  
290 -(% border="1.5" style="background-color:#ffffcc; color:green; width:412.222px" %)
291 -|=(% 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
292 -|=(% 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"]]
286 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
287 +|=(% 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
288 +|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
293 293  
294 -(% style="display:none" %)
295 295  
296 -
297 297  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
298 298  
299 299  
... ... @@ -312,23 +312,21 @@
312 312  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
313 313  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
314 314  
315 -[[image:1665301636888-168.png||_mstalt="298012"]]
309 +[[image:1665301636888-168.png]]
316 316  
317 317  
318 318  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
319 319  
320 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:279.222px" %)
321 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:69px" %)1 bit|(% style="width:63px" %)14 bits
322 -|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:69px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
314 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
315 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
316 +|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
323 323  
324 -(% style="display:none" %)
325 325  
326 -
327 327  ==== (% style="color:blue" %)**FLAG:**(%%) ====
328 328  
329 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:183.222px" %)
330 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2 bits|(% style="width:52px" %)1 bit
331 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:52px" %)[[LON>>||anchor="HLON:"]]
321 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
322 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
323 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
332 332  
333 333  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
334 334  
... ... @@ -345,12 +345,12 @@
345 345  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:
346 346  
347 347  
348 -[[image:1664502116362-706.png||_mstalt="293306"]]
340 +[[image:1664502116362-706.png]]
349 349  
350 350  
351 351  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
352 352  
353 -[[image:1664502166010-515.png||_mstalt="291395"]]
345 +[[image:1664502166010-515.png]]
354 354  
355 355  
356 356  
... ... @@ -373,9 +373,7 @@
373 373  * 3.40v ~~ 3.69v:  20% ~~ 40%
374 374  * < 3.39v:  0~~20%
375 375  
376 -(% style="display:none" %) (%%)
377 377  
378 -
379 379  ==== (% style="color:blue" %)**MOD:**(%%) ====
380 380  
381 381  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -431,13 +431,13 @@
431 431  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
432 432  
433 433  (% class="wikigeneratedid" %)
434 -[[image:1665301687277-443.png||_mstalt="296140"]]
424 +[[image:1665301687277-443.png]]
435 435  
436 436  
437 437  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
438 438  
439 439  
440 -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.
430 +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.
441 441  
442 442  
443 443  (% style="color:red" %)**Note for this mode:**
... ... @@ -454,7 +454,7 @@
454 454  )))|4|4|2|1|1|1|1|1
455 455  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
456 456  
457 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
447 +[[image:image-20221009160309-2.png]]
458 458  
459 459  
460 460  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
... ... @@ -481,7 +481,7 @@
481 481  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
482 482  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
483 483  
484 -[[image:1664502425687-834.png||_mstalt="296738"]]
474 +[[image:1664502425687-834.png]]
485 485  
486 486  
487 487  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -492,32 +492,10 @@
492 492  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
493 493  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
494 494  
495 -(% style="display:none" %) (%%)
496 496  
486 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
497 497  
498 -=== 2.4.6  Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
499 499  
500 -
501 -The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
502 -
503 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
504 -|**Size(bytes)**|2|1
505 -|**Value**|[[Alarm & BAT>>path:#HAlarm26BAT:]]|Mod+lon
506 -
507 - [[image:image-20230302145315-1.png]]
508 -
509 -**alarm**=(bytes[0] & 0x40)  ~/~/ Alarm status
510 -
511 -**batV**=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;  ~/~/ Battery,units:V
512 -
513 -**mod** = bytes[2] & 0xC0;
514 -
515 -**Lon**=(bytes[2] & 0x20)
516 -
517 -
518 -=== 2.4.7  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
519 -
520 -
521 521  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.
522 522  
523 523  
... ... @@ -530,7 +530,7 @@
530 530  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
531 531  
532 532  (% class="wikigeneratedid" %)
533 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
501 +[[image:1667288597595-714.png||height="212" width="1151"]]
534 534  
535 535  
536 536  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -537,18 +537,16 @@
537 537  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
538 538  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
539 539  
540 -(% style="display:none" %) (%%)
541 541  
509 +=== 2.4.7  Add Payload format in TTN V3 ===
542 542  
543 -=== 2.4.8  Add Payload format in TTN V3 ===
544 544  
545 -
546 546  In TTN V3, user can add a custom payload so it shows friendly.
547 547  
548 548  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
549 549  
550 550  
551 -[[image:1664502649601-895.png||_mstalt="296985"]]
517 +[[image:1664502649601-895.png]]
552 552  
553 553  
554 554  
... ... @@ -558,7 +558,7 @@
558 558  
559 559  Save the change the uplink message will be parsed. As below:
560 560  
561 -[[image:1664502676891-606.png||_mstalt="296673"]]
527 +[[image:1664502676891-606.png]]
562 562  
563 563  
564 564  == 2.5 Integrate with Datacake ==
... ... @@ -569,7 +569,7 @@
569 569  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]]
570 570  
571 571  
572 -[[image:1664502695771-538.png||_mstalt="297349"]]
538 +[[image:1664502695771-538.png]]
573 573  
574 574  
575 575  == 2.6 Integrate with Tago ==
... ... @@ -580,70 +580,29 @@
580 580  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]]
581 581  
582 582  
583 -[[image:1664502715371-321.png||_mstalt="292162"]]
549 +[[image:1664502715371-321.png]]
584 584  
585 585  
586 -== 2.7  Integrate with Node-red ==
552 +== 2.7  Datalog Feature ==
587 587  
588 588  
589 -~1. Install node-red, please refer to the installation method in the link:
590 -
591 - [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
592 -
593 -
594 -2. Import the created flow template, please refer to the import method in the link:
595 -
596 - [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
597 - The address of the flow template:
598 -
599 - [[dragino-end-node-decoder/TrackerD.json at main · dragino/dragino-end-node-decoder · GitHub>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/TrackerD.json]]
600 -
601 -(% style="color:red" %)**Note: If you are using NODE-RED for the first time, please search and install the two plug-ins in the figure below in node-red to fully use the flow template.**
602 -
603 -[[image:image-20230307135914-1.png||height="527" width="1045"]]
604 -
605 -
606 -[[image:image-20230307135932-2.png||height="527" width="1044"]]
607 -
608 -
609 -3. Display the map
610 - Enter the link to the map:
611 -
612 - Change its suffix to ditu：http:~/~/119.91.62.30:1880/**ditu/**
613 -
614 -**~ **[[image:image-20230308115430-1.png||height="548" width="1041"]]
615 -
616 -
617 - Hit all input in input stream
618 -
619 - [[image:image-20230308115616-2.png||height="563" width="1070"]]
620 -
621 -
622 - View map again
623 -
624 -[[image:image-20230308115701-3.png||height="571" width="1085"]]
625 -
626 -
627 -== 2.8  Datalog Feature ==
628 -
629 -
630 630  total 273 entries,by default,
631 631  
632 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
557 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
633 633  
634 634  Example use case.
635 635  
636 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
561 +[[image:image-20221009234703-2.png||height="328" width="899"]]
637 637  
638 638  
639 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
564 +[[image:image-20221009234629-1.png||height="390" width="577"]]
640 640  
641 641  
642 -== 2.9  Alarm Mode ==
567 +== 2.8 Alarm Mode ==
643 643  
644 644  
645 645  (((
646 -User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. Alarm Mode is used to send SOS info to IoT platform.
571 +User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
647 647  )))
648 648  
649 649  
... ... @@ -664,23 +664,15 @@
664 664  )))
665 665  
666 666  
667 -== 2.10  Transport Mode ==
592 +== 2.9 Transport Mode ==
668 668  
669 669  
670 -In Transport Mode, TrackerD will check if there is motion (threldhold defined by **[[PT)>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** . If there is no motion, device will send uplinks every 20 minutes (Defined by **[[TDC)>>||anchor="H3.2.1SetTransmitInterval"]]** . If there is motion, device will send uplink every 5 minutes(defined by **[[MTDC)>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]**.
595 +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.
671 671  
672 -When device is set in Transport Mode, it will uplink more frequenctly during moving.
673 673  
674 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
675 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
676 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
598 +== 2.10 LED Status ==
677 677  
678 -(% style="display:none" %) (%%)
679 679  
680 -
681 -== 2.11  LED Status ==
682 -
683 -
684 684  (% border="1.5" style="background-color:#ffffcc; width:500px" %)
685 685  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
686 686  |(% 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
... ... @@ -695,15 +695,13 @@
695 695  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
696 696  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
697 697  
698 -(% style="display:none" %) (%%)
699 699  
616 +== 2.11 Button Function ==
700 700  
701 -== 2.12  Button Function ==
702 702  
703 -
704 704  (% style="color:blue" %)**RESET button:**
705 705  
706 -[[image:1664502835802-546.png||_mstalt="295061"]]
621 +[[image:1664502835802-546.png]]
707 707  
708 708  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
709 709  
... ... @@ -710,9 +710,8 @@
710 710  
711 711  (% style="color:red" %)**RED button:**
712 712  
713 -[[image:image-20230213110506-3.png]](% style="display:none" %)
628 +[[image:1664502854406-763.png]]
714 714  
715 -(% style="display:none" %) (%%)
716 716  
717 717  (% border="1" style="background-color:#ffffcc; width:510px" %)
718 718  |=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
... ... @@ -720,12 +720,10 @@
720 720  |(% 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
721 721  |(% 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.
722 722  
723 -(% style="display:none" %) (%%)
724 724  
638 +== 2.12 USB Port Function ==
725 725  
726 -== 2.13  USB Port Function ==
727 727  
728 -
729 729  The USB interface of TrackerD has below functions:
730 730  
731 731  * Power on the device
... ... @@ -733,19 +733,7 @@
733 733  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
734 734  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
735 735  
736 -(% style="display:none" %) (%%)
737 737  
738 -
739 -== 2.14  Sleep Mode ==
740 -
741 -
742 -(% style="color:blue" %)**Sleep Mode:**(%%) To prevent accidental touch of the red button during transportation or assembly, so the peripherals of the device are turned off and enter deep sleep.
743 -
744 -In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**.
745 -
746 -Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep.
747 -
748 -
749 749  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
750 750  
751 751  
... ... @@ -760,22 +760,22 @@
760 760  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.
761 761  
762 762  
763 -[[image:1664502999401-486.png||_mstalt="296985"]]
663 +[[image:1664502999401-486.png]]
764 764  
765 765  
766 766  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:
767 767  
768 768  
769 -[[image:1664503022490-662.png||_mstalt="293332"]]
669 +[[image:1664503022490-662.png]]
770 770  
771 771  
772 -[[image:1664503035713-500.png||_mstalt="291096"]]
672 +[[image:1664503035713-500.png]]
773 773  
774 774  
775 -[[image:1664503047675-651.png||_mstalt="295386"]]
675 +[[image:1664503047675-651.png]]
776 776  
777 -(% style="display:none" %) (%%)
778 778  
678 +
779 779  == 3.2 Command Set ==
780 780  
781 781  === 3.2.1 Set Transmit Interval ===
... ... @@ -841,7 +841,7 @@
841 841  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
842 842  
843 843  
844 -=== 3.2.5 Disable/Enable LED flash and buzzer ===
744 +=== 3.2.5 Disable/Enable LED flash ===
845 845  
846 846  
847 847  Disable/Enable LED for position, downlink and uplink
... ... @@ -901,9 +901,9 @@
901 901  
902 902  (% style="color:#037691" %)**cc:   **
903 903  
904 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
804 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
905 905  
906 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
806 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
907 907  
908 908  (% style="color:blue" %)**Example:**
909 909  
... ... @@ -965,8 +965,8 @@
965 965  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
966 966  
967 967  
968 -=== 3.2.10 Disable/Enable the confirmation mode ===
969 969  
869 +**Disable/Enable the confirmation mode**
970 970  
971 971  * (% style="color:blue" %)**AT Command:**
972 972  
... ... @@ -985,7 +985,7 @@
985 985  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
986 986  
987 987  
988 -=== 3.2.11  Auto Send None-ACK messages ===
888 +=== 3.2.10  Auto Send None-ACK messages ===
989 989  
990 990  
991 991  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.
... ... @@ -1003,10 +1003,10 @@
1003 1003  
1004 1004  * (% style="color:blue" %)**Downlink Command: 0x34**
1005 1005  
1006 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
906 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
1007 1007  
1008 1008  
1009 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
909 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
1010 1010  
1011 1011  
1012 1012  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.
... ... @@ -1015,16 +1015,16 @@
1015 1015  
1016 1016  (% style="color:blue" %)**AT Command:**
1017 1017  
1018 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
918 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
1019 1019  
1020 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
920 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
1021 1021  
1022 1022  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
1023 1023  
1024 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
924 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
1025 1025  
1026 1026  
1027 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
927 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
1028 1028  
1029 1029  
1030 1030  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.
... ... @@ -1033,16 +1033,16 @@
1033 1033  
1034 1034  (% style="color:blue" %)**AT Command:**
1035 1035  
1036 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
936 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
1037 1037  
1038 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
938 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
1039 1039  
1040 1040  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
1041 1041  
1042 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
942 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
1043 1043  
1044 1044  
1045 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
945 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
1046 1046  
1047 1047  
1048 1048  Users can use this feature to enable/disable Information printing.
... ... @@ -1049,11 +1049,11 @@
1049 1049  
1050 1050  (% style="color:blue" %)**AT Command:**
1051 1051  
1052 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
952 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
1053 1053  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
1054 1054  
1055 1055  
1056 -=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
956 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
1057 1057  
1058 1058  
1059 1059  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -1060,85 +1060,14 @@
1060 1060  
1061 1061  (% style="color:blue" %)**AT Command:**
1062 1062  
1063 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
963 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
1064 1064  
1065 1065  
1066 1066  (% style="color:blue" %)**Downlink Payload:0X24**
1067 1067  
1068 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
968 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
1069 1069  
1070 1070  
1071 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
1072 -
1073 -
1074 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
1075 -
1076 -(% style="color:blue" %)**AT Command:**
1077 -
1078 -(% style="color:#037691" %)**AT+PT=xx**
1079 -
1080 - Example:
1081 -
1082 - AT+PT=14    ~-~->    Set to detect car motion.
1083 -
1084 - AT+PT=41  ~-~->    set to detect walk motion.
1085 -
1086 -
1087 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
1088 -0xB4 14          ~/~/  Same as AT+PT=14
1089 -
1090 -
1091 -=== **3.2.17  Set AT command window time（Since firmware 1.4.5）** ===
1092 -
1093 -AT command window time setting, customers can set the required time according to their own operation mode.The unit is second.
1094 -
1095 -(% style="color:blue" %)**AT Command:**
1096 -
1097 -(% style="color:#037691" %)**AT+ATST=XX**
1098 -
1099 - Example:
1100 -
1101 - AT+ATST=15    ~-~-> Set the time to 15 seconds
1102 -
1103 -(% style="color:blue" %)**Downlink Payload:0XB5**(%%)
1104 -0xB5 0F          ~/~/  Same as AT+ATST=15
1105 -
1106 -=== **3.2.18  Set the stepmeter mode（Since firmware 1.4.5）** ===
1107 -
1108 -After setting the step counting mode, it cannot be interrupted by motion. This mode is very power consuming. Used on some special occasions.
1109 -
1110 -(% style="color:blue" %)**AT Command:**
1111 -
1112 -(% style="color:#037691" %)**AT+PM=xx**
1113 -
1114 - Example:
1115 -
1116 - AT+PM=1    ~-~->  Turn on step counting mode
1117 -
1118 -AT+PM=0    ~-~->  Turn OFF step counting mode
1119 -
1120 -(% style="color:blue" %)**Downlink Payload:0XB6**(%%)
1121 -0xB6 01          ~/~/  Same as AT+PM=1
1122 -
1123 -
1124 -=== 3.2.19  Set down the decline detection mode（Since firmware 1.4.5） ===
1125 -
1126 -This mode is used in conjunction with AT+PT(The recommended threshold is between 50 and 70, you need to set it according to the environment yourself). This function is used in hospitals, nursing homes, nursing homes and other places to prevent the elderly and patients from falling. No one knows.
1127 -
1128 -(% style="color:blue" %)**AT Command:**
1129 -
1130 -(% style="color:#037691" %)**AT+FD=xx**
1131 -
1132 - Example:
1133 -
1134 - AT+FD=1    ~-~->  Turn on the Fall detection
1135 -
1136 -AT+FD=0    ~-~->  Turn OFF the Fall detection
1137 -
1138 -(% style="color:blue" %)**Downlink Payload:0XB7**(%%)
1139 -0xB7 01          ~/~/  Same as AT+PM=1
1140 -
1141 -
1142 1142  = 4. Setting for Different Scenarios =
1143 1143  
1144 1144  
... ... @@ -1171,10 +1171,10 @@
1171 1171  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1172 1172  
1173 1173  
1174 -[[image:1664503563660-578.png||_mstalt="296777"]]
1003 +[[image:1664503563660-578.png]]
1175 1175  
1176 1176  
1177 -[[image:1664503574618-659.png||_mstalt="297986"]]
1006 +[[image:1664503574618-659.png]]
1178 1178  
1179 1179  
1180 1180  
... ... @@ -1190,15 +1190,16 @@
1190 1190  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1191 1191  
1192 1192  
1193 -[[image:image-20221207120501-1.png]]
1022 +[[image:image-20221118105220-2.png]]
1194 1194  
1195 1195  
1196 1196  
1197 1197  After upgrade finish, it will show finish as below:
1198 1198  
1199 -[[image:image-20221207133911-7.png]]
1028 +[[image:image-20221118105402-4.png]]
1200 1200  
1201 1201  
1031 +
1202 1202  = 6. Developer Guide =
1203 1203  
1204 1204  == 6.1 Compile Source Code ==
... ... @@ -1211,81 +1211,24 @@
1211 1211  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]]
1212 1212  
1213 1213  
1214 -[[image:1664503635019-941.png||_mstalt="294658"]]
1044 +[[image:1664503635019-941.png]]
1215 1215  
1216 1216  
1217 1217  
1218 1218  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1219 1219  
1220 -[[image:1664503715811-892.png||_mstalt="295698"]]
1050 +[[image:1664503715811-892.png]]
1221 1221  
1222 1222  
1223 -=== 6.1.2  Build the development environment ===
1224 -
1225 -
1226 -**~1. Download and install arduino IDE**
1227 -
1228 -[[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]]
1229 -
1230 -
1231 -**2. Download the ESP32 development package in the arduino IDE**
1232 -
1233 -[[image:image-20221213100007-1.png]]
1234 -
1235 -
1236 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1237 -
1238 -[[image:image-20221213100626-2.png]]
1239 -
1240 -
1241 -Restart the IDE after the addition is complete, then:
1242 -
1243 -[[image:image-20221213100808-3.png||height="679" width="649"]]
1244 -
1245 -
1246 -[[image:image-20221213101040-4.png]]
1247 -
1248 -
1249 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1250 -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)**
1251 -
1252 -
1253 -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:
1254 -
1255 -(% style="color:blue" %)**Methods as below:**
1256 -
1257 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1258 -
1259 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1260 -
1261 1261  (% 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.
1262 1262  
1263 -[[image:image-20221213102311-5.png||height="582" width="711"]]
1055 +[[image:image-20221024105643-1.png]]
1264 1264  
1265 -
1266 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1267 -
1268 -[[image:image-20221213102334-6.png]]
1269 -
1270 -(% style="color:red" %)**Note: This step requires a python environment**
1271 -
1272 -
1273 -Either way, in the end:
1274 -
1275 -The final effect is to open the arduino and you can see the esp32
1276 -
1277 -[[image:image-20221213110952-8.png||height="866" width="711"]]
1278 -
1279 -
1280 -
1281 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1282 -
1283 1283  **~ Figure1**
1284 1284  
1285 1285  
1060 +[[image:image-20221024105643-2.png]]
1286 1286  
1287 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1288 -
1289 1289   **Figure2**
1290 1290  
1291 1291  
... ... @@ -1294,7 +1294,7 @@
1294 1294  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1295 1295  
1296 1296  
1297 -[[image:1664503752288-974.png||_mstalt="298194"]]
1070 +[[image:1664503752288-974.png]]
1298 1298  
1299 1299  
1300 1300  == 6.2 Source Code ==
... ... @@ -1302,19 +1302,19 @@
1302 1302  
1303 1303  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1304 1304  
1305 -[[image:1664503794261-827.png||_mstalt="296387"]]
1078 +[[image:1664503794261-827.png]]
1306 1306  
1307 1307  
1308 1308  
1309 1309  * (% style="color:blue" %)**Click to upload**
1310 1310  
1311 -[[image:1664503808294-336.png||_mstalt="295711"]]
1084 +[[image:1664503808294-336.png]]
1312 1312  
1313 1313  
1314 1314  
1315 1315  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1316 1316  
1317 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1090 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1318 1318  
1319 1319  
1320 1320  = 7.  FAQ =
... ... @@ -1328,7 +1328,7 @@
1328 1328  == 7.2 What is the pin mapping for the USB program cable? ==
1329 1329  
1330 1330  
1331 -[[image:1664499635206-262.png||_mstalt="295360"]]
1104 +[[image:1664499635206-262.png]]
1332 1332  
1333 1333  
1334 1334  
... ... @@ -1343,9 +1343,7 @@
1343 1343  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1344 1344  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1345 1345  
1346 -(% style="display:none" %) (%%)
1347 1347  
1348 -
1349 1349  == 7.3 Notes on using different serial port tools for TrackerD ==
1350 1350  
1351 1351  === 7.3.1  Serial port utility ===
... ... @@ -1356,13 +1356,13 @@
1356 1356  Need to adjust the data stream to RTS/CTS on physical restart.
1357 1357  
1358 1358  (% class="wikigeneratedid" %)
1359 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1130 +[[image:image-20221102140621-1.png]]
1360 1360  
1361 1361  
1362 1362  
1363 1363  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1364 1364  
1365 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1136 +[[image:image-20221102140638-2.png]]
1366 1366  
1367 1367  
1368 1368  === 7.3.2  SecureCRT ===
... ... @@ -1371,22 +1371,22 @@
1371 1371  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.
1372 1372  
1373 1373  
1374 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1145 +[[image:image-20221102140704-3.png]]
1375 1375  
1376 1376  
1377 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1148 +[[image:image-20221102140712-4.png]]
1378 1378  
1379 1379  
1380 1380  === 7.3.3  PUTTY ===
1381 1381  
1382 1382  
1383 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1154 +[[image:image-20221102140748-5.png]]
1384 1384  
1385 1385  
1386 1386  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.
1387 1387  
1388 1388  
1389 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1160 +[[image:image-20221102140801-6.png]]
1390 1390  
1391 1391  
1392 1392  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1401,7 +1401,7 @@
1401 1401  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1402 1402  
1403 1403  
1404 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1175 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1405 1405  
1406 1406  
1407 1407  
... ... @@ -1408,7 +1408,7 @@
1408 1408  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1409 1409  
1410 1410  
1411 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1182 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1412 1412  
1413 1413  
1414 1414  
... ... @@ -1415,7 +1415,7 @@
1415 1415  **3. Compile the AS923_JP band, please refer to the intention shown**
1416 1416  
1417 1417  
1418 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1189 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1419 1419  
1420 1420  
1421 1421  
... ... @@ -1422,24 +1422,12 @@
1422 1422  **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.**
1423 1423  
1424 1424  
1425 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1196 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1426 1426  
1427 1427  
1428 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1199 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1429 1429  
1430 1430  
1431 -== 7.5 Are there example python example for BLE Indoor Positioning? ==
1432 -
1433 -
1434 -[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1435 -
1436 -
1437 -== 7.6 Can alert mode and transport mode be used together? ==
1438 -
1439 -
1440 -Yes, you can also press the panic button to sound the alarm if set to transport mode
1441 -
1442 -
1443 1443  = 8  Trouble Shooting =
1444 1444  
1445 1445  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
... ... @@ -1446,7 +1446,7 @@
1446 1446  
1447 1447  
1448 1448  (((
1449 -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
1208 +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
1450 1450  )))
1451 1451  
1452 1452  
... ... @@ -1460,69 +1460,50 @@
1460 1460  
1461 1461  == 8.3  Problem after Upgrading Firmware ==
1462 1462  
1463 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1222 +=== 8.3.1 Continue Restart after upgrading ===
1464 1464  
1465 1465  
1466 -**Error Output**
1467 -
1468 -
1469 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1470 -
1471 -
1472 1472  (((
1473 -Some partition is missed during upgrade, please upgrade below four files as example:
1474 -
1475 -[[image:image-20221207120524-2.png]]
1226 +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
1476 1476  )))
1477 1477  
1478 1478  
1479 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1230 +[[image:image-20221118105249-3.png]]
1480 1480  
1481 1481  
1482 -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
1233 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1483 1483  
1484 1484  
1485 -=== 8.3.3 "flash read err" after upgrade firmware ===
1236 +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
1486 1486  
1487 1487  
1239 +=== 8.3.3 "flash read err" after upgrade firmware ===
1240 +
1488 1488  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1489 1489  
1243 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1490 1490  
1491 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1492 1492  
1493 -
1494 1494  User need to upgrade again with below four files to solve this issue.
1495 1495  
1496 - [[image:image-20221207120530-3.png]]
1248 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1497 1497  
1498 1498   **Figure 2**
1499 1499  
1500 1500  
1501 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1253 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1502 1502  
1503 -
1504 1504  User might erase the entire flash include keys and default settings which cause this issue.
1505 1505  
1506 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1257 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1507 1507  
1259 +[[image:image-20221122100004-3.png]]
1508 1508  
1509 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1261 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1510 1510  
1511 1511  
1512 -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.
1264 +Example:
1513 1513  
1514 -After AT+FDR. please set
1515 -
1516 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1517 -
1518 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1519 -
1520 -**Example:**
1521 -
1522 -AT+PDOP=7.00
1523 -
1524 -AT+FTIME=180
1525 -
1526 1526  AT+DEUI=70B3D57ED0053981  
1527 1527  
1528 1528  AT+APPEUI=D23345667BCBCCAF
... ... @@ -1536,6 +1536,13 @@
1536 1536  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1537 1537  
1538 1538  
1279 +
1280 +==== 8.3.4  If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ====
1281 +
1282 +
1283 +[[image:image-20221122100004-4.png]]
1284 +
1285 +
1539 1539  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1540 1540  
1541 1541  
... ... @@ -1549,61 +1549,15 @@
1549 1549  
1550 1550  2)  Set PDOP to a higher value.
1551 1551  
1552 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1299 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1553 1553  
1554 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1301 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1555 1555  
1556 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1303 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1557 1557  
1558 1558  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
1559 1559  
1560 1560  
1561 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1562 -
1563 -
1564 -When upgrading, use the erase button to upgrade
1565 -
1566 -[[image:image-20221207120536-4.png]]
1567 -
1568 -
1569 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1570 -
1571 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1572 -
1573 -
1574 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1575 -
1576 -[[image:image-20221207134028-8.png]]
1577 -
1578 -
1579 -Reboot information after upgrade
1580 -
1581 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1582 -
1583 -
1584 -Use **AT+FDR** command to reset and then use **AT+CFG** to check whether the configuration is back to normal
1585 -
1586 -[[image:image-20221128111850-5.png]]
1587 -
1588 -
1589 -After the parameters return to normal, upgrade to the version you need again
1590 -
1591 -[[image:image-20221207120601-5.png]]
1592 -
1593 -
1594 -At this point, the parameters return to normal after running AT+FDR again
1595 -
1596 -[[image:image-20221128112035-7.png]]
1597 -
1598 -
1599 -== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1600 -
1601 -
1602 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1603 -
1604 -2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1605 -
1606 -
1607 1607  = 9.  Order Info =
1608 1608  
1609 1609  
... ... @@ -1625,9 +1625,7 @@
1625 1625  
1626 1626  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1627 1627  
1628 -(% style="display:none" %) (%%)
1629 1629  
1630 -
1631 1631  = 10.  Packing Info =
1632 1632  
1633 1633  
... ... @@ -1643,9 +1643,7 @@
1643 1643  
1644 1644  * Weight: 50g
1645 1645  
1646 -(% style="display:none" %) (%%)
1647 1647  
1648 -
1649 1649  = 11. Support =
1650 1650  
1651 1651  
... ... @@ -1653,9 +1653,7 @@
1653 1653  
1654 1654  * 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]].
1655 1655  
1656 -(% style="display:none" %) (%%)
1657 1657  
1658 -
1659 1659  = 12.  Reference =
1660 1660  
1661 1661  
... ... @@ -1664,6 +1664,3 @@
1664 1664  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1665 1665  
1666 1666  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1667 -
1668 -
1669 -)))
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
image-20230308115430-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -2.4 MB
Content
image-20230308115616-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -152.7 KB
Content
image-20230308115701-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -2.4 MB
Content
image-20230426085815-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -190.0 KB
Content