Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 202.1
edited by Bei Jinggeng
on 2023/03/08 11:58
Change comment: There is no comment for this version
To version 145.1
edited by Edwin Chen
on 2022/11/22 12:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
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,7 +93,6 @@
93 93  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94 94  * Tracking: max: 38mA
95 95  
96 -
97 97  == 1.3  Features ==
98 98  
99 99  
... ... @@ -112,7 +112,6 @@
112 112  * Tri-color LED, Alarm button
113 113  * Datalog
114 114  
115 -
116 116  == 1.4  Applications ==
117 117  
118 118  
... ... @@ -119,7 +119,6 @@
119 119  * Logistics and Supply Chain Management
120 120  * Human tracking
121 121  
122 -
123 123  = 2.  Use TrackerD =
124 124  
125 125  == 2.1 How it works? ==
... ... @@ -134,7 +134,7 @@
134 134  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. 
135 135  
136 136  
137 -[[image:image-20230213110214-2.png||height="388" width="847"]]
136 +[[image:1664501652064-326.png]]
138 138  
139 139  
140 140  
... ... @@ -146,7 +146,7 @@
146 146  Each TrackerD is shipped with a sticker with the default device EUI as below:
147 147  
148 148  
149 -[[image:1664501677253-891.png||_mstalt="296569"]]
148 +[[image:1664501677253-891.png]]
150 150  
151 151  
152 152  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -155,14 +155,14 @@
155 155  **__Add APP EUI in the application:__**
156 156  
157 157  
158 -[[image:1664501711466-918.png||_mstalt="295828"]]
157 +[[image:1664501711466-918.png]]
159 159  
160 160  
161 161  
162 -[[image:1664501721248-725.png||_mstalt="294450"]]
161 +[[image:1664501721248-725.png]]
163 163  
164 164  
165 -[[image:1664501734705-405.png||_mstalt="293306"]]
164 +[[image:1664501734705-405.png]]
166 166  
167 167  
168 168  
... ... @@ -169,15 +169,15 @@
169 169  **__Add APP KEY and DEV EUI:__**
170 170  
171 171  
172 -[[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"]]
171 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||alt="1654671889112-678.png"]]
173 173  
174 174  
175 175  
176 176  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
177 177  
178 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
177 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
179 179  
180 -[[image:1664502835802-546.png||_mstalt="295061"]]
179 +[[image:1664502835802-546.png]]
181 181  
182 182  
183 183  (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
... ... @@ -206,10 +206,10 @@
206 206  
207 207  
208 208  (% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
209 -|=(% 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
208 +|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1
210 210  |=(% 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
211 211  
212 -[[image:1665301570342-765.png||_mstalt="294580"]]
211 +[[image:1665301570342-765.png]]
213 213  
214 214  
215 215  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -253,7 +253,7 @@
253 253  (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
254 254  
255 255  (% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
256 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)1bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
255 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
257 257  |=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
258 258  
259 259  (% style="color:blue" %)** SMOD：**
... ... @@ -276,16 +276,15 @@
276 276  
277 277  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
278 278  
279 -(% _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)(%%)  
278 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
280 280  
281 281  
282 282  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
283 283  
284 -(% border="1.5" style="background-color:#ffffcc; color:green; width:412.222px" %)
285 -|=(% 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
286 -|=(% 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"]]
283 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
284 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit
285 +|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
287 287  
288 -
289 289  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
290 290  
291 291  
... ... @@ -304,20 +304,20 @@
304 304  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
305 305  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
306 306  
307 -[[image:1665301636888-168.png||_mstalt="298012"]]
305 +[[image:1665301636888-168.png]]
308 308  
309 309  
310 310  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
311 311  
312 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:279.222px" %)
313 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:69px" %)1 bit|(% style="width:63px" %)14 bits
314 -|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:69px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
310 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
311 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
312 +|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
315 315  
316 316  ==== (% style="color:blue" %)**FLAG:**(%%) ====
317 317  
318 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:183.222px" %)
319 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2 bits|(% style="width:52px" %)1 bit
320 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:52px" %)[[LON>>||anchor="HLON:"]]
316 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
317 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
318 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
321 321  
322 322  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
323 323  
... ... @@ -334,12 +334,12 @@
334 334  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:
335 335  
336 336  
337 -[[image:1664502116362-706.png||_mstalt="293306"]]
335 +[[image:1664502116362-706.png]]
338 338  
339 339  
340 340  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
341 341  
342 -[[image:1664502166010-515.png||_mstalt="291395"]]
340 +[[image:1664502166010-515.png]]
343 343  
344 344  
345 345  
... ... @@ -362,9 +362,6 @@
362 362  * 3.40v ~~ 3.69v:  20% ~~ 40%
363 363  * < 3.39v:  0~~20%
364 364  
365 -(% style="display:none" %) (%%)
366 -
367 -
368 368  ==== (% style="color:blue" %)**MOD:**(%%) ====
369 369  
370 370  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -420,13 +420,13 @@
420 420  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
421 421  
422 422  (% class="wikigeneratedid" %)
423 -[[image:1665301687277-443.png||_mstalt="296140"]]
418 +[[image:1665301687277-443.png]]
424 424  
425 425  
426 426  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
427 427  
428 428  
429 -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.
424 +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.
430 430  
431 431  
432 432  (% style="color:red" %)**Note for this mode:**
... ... @@ -443,7 +443,7 @@
443 443  )))|4|4|2|1|1|1|1|1
444 444  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
445 445  
446 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
441 +[[image:image-20221009160309-2.png]]
447 447  
448 448  
449 449  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
... ... @@ -470,7 +470,7 @@
470 470  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
471 471  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
472 472  
473 -[[image:1664502425687-834.png||_mstalt="296738"]]
468 +[[image:1664502425687-834.png]]
474 474  
475 475  
476 476  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -481,32 +481,9 @@
481 481  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
482 482  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
483 483  
484 -(% style="display:none" %) (%%)
479 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
485 485  
486 486  
487 -=== 2.4.6  Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
488 -
489 -
490 -The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
491 -
492 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
493 -|**Size(bytes)**|2|1
494 -|**Value**|[[Alarm & BAT>>path:#HAlarm26BAT:]]|Mod+lon
495 -
496 - [[image:image-20230302145315-1.png]]
497 -
498 -alarm=(bytes[0] & 0x40)  ~/~/ Alarm status
499 -
500 -batV=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;  ~/~/ Battery,units:V
501 -
502 -mod = bytes[2] & 0xC0;
503 -
504 -Lon=(bytes[2] & 0x20)
505 -
506 -
507 -=== 2.4.7  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
508 -
509 -
510 510  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.
511 511  
512 512  
... ... @@ -519,7 +519,7 @@
519 519  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
520 520  
521 521  (% class="wikigeneratedid" %)
522 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
494 +[[image:1667288597595-714.png||height="212" width="1151"]]
523 523  
524 524  
525 525  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -526,18 +526,15 @@
526 526  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
527 527  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
528 528  
529 -(% style="display:none" %) (%%)
501 +=== 2.4.7  Add Payload format in TTN V3 ===
530 530  
531 531  
532 -=== 2.4.8  Add Payload format in TTN V3 ===
533 -
534 -
535 535  In TTN V3, user can add a custom payload so it shows friendly.
536 536  
537 537  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
538 538  
539 539  
540 -[[image:1664502649601-895.png||_mstalt="296985"]]
509 +[[image:1664502649601-895.png]]
541 541  
542 542  
543 543  
... ... @@ -547,7 +547,7 @@
547 547  
548 548  Save the change the uplink message will be parsed. As below:
549 549  
550 -[[image:1664502676891-606.png||_mstalt="296673"]]
519 +[[image:1664502676891-606.png]]
551 551  
552 552  
553 553  == 2.5 Integrate with Datacake ==
... ... @@ -558,7 +558,7 @@
558 558  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]]
559 559  
560 560  
561 -[[image:1664502695771-538.png||_mstalt="297349"]]
530 +[[image:1664502695771-538.png]]
562 562  
563 563  
564 564  == 2.6 Integrate with Tago ==
... ... @@ -569,59 +569,25 @@
569 569  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]]
570 570  
571 571  
572 -[[image:1664502715371-321.png||_mstalt="292162"]]
541 +[[image:1664502715371-321.png]]
573 573  
574 574  
575 -== 2.7  Integrate with Node-red ==
544 +== 2.7  Datalog Feature ==
576 576  
577 577  
578 -~1. Install node-red, please refer to the installation method in the link:
579 -
580 - [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
581 -2. Import the created flow template, please refer to the import method in the link:
582 -
583 - [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
584 - The address of the flow template:
585 -
586 - [[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]]
587 -
588 -(% 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.**
589 -
590 -[[image:image-20230307135914-1.png||height="527" width="1045"]]
591 -
592 -
593 -[[image:image-20230307135932-2.png||height="527" width="1044"]]
594 -
595 -3. Display the map
596 - Enter the link to the map:
597 -
598 - Change its suffix to ditu：http:~/~/119.91.62.30:1880/**ditu/**
599 -
600 -**~ **[[image:image-20230308115430-1.png||height="548" width="1041"]]
601 - Hit all input in input stream
602 -
603 - [[image:image-20230308115616-2.png||height="563" width="1070"]]
604 - View map again
605 -
606 -[[image:image-20230308115701-3.png||height="571" width="1085"]]
607 -
608 -
609 -== 2.8  Datalog Feature ==
610 -
611 -
612 612  total 273 entries,by default,
613 613  
614 -User can set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
549 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
615 615  
616 616  Example use case.
617 617  
618 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
553 +[[image:image-20221009234703-2.png||height="328" width="899"]]
619 619  
620 620  
621 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
556 +[[image:image-20221009234629-1.png||height="390" width="577"]]
622 622  
623 623  
624 -== 2.9  Alarm Mode ==
559 +== 2.8 Alarm Mode ==
625 625  
626 626  
627 627  (((
... ... @@ -646,21 +646,15 @@
646 646  )))
647 647  
648 648  
649 -== 2.10  Transport Mode ==
584 +== 2.9 Transport Mode ==
650 650  
651 651  
652 652  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.
653 653  
654 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
655 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
656 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
657 657  
658 -(% style="display:none" %) (%%)
590 +== 2.10 LED Status ==
659 659  
660 660  
661 -== 2.11  LED Status ==
662 -
663 -
664 664  (% border="1.5" style="background-color:#ffffcc; width:500px" %)
665 665  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
666 666  |(% 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
... ... @@ -675,15 +675,12 @@
675 675  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
676 676  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
677 677  
678 -(% style="display:none" %) (%%)
607 +== 2.11 Button Function ==
679 679  
680 680  
681 -== 2.12  Button Function ==
682 -
683 -
684 684  (% style="color:blue" %)**RESET button:**
685 685  
686 -[[image:1664502835802-546.png||_mstalt="295061"]]
612 +[[image:1664502835802-546.png]]
687 687  
688 688  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
689 689  
... ... @@ -690,9 +690,8 @@
690 690  
691 691  (% style="color:red" %)**RED button:**
692 692  
693 -[[image:image-20230213110506-3.png]](% style="display:none" %)
619 +[[image:1664502854406-763.png]]
694 694  
695 -(% style="display:none" %) (%%)
696 696  
697 697  (% border="1" style="background-color:#ffffcc; width:510px" %)
698 698  |=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
... ... @@ -700,12 +700,9 @@
700 700  |(% 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
701 701  |(% 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.
702 702  
703 -(% style="display:none" %) (%%)
628 +== 2.12 USB Port Function ==
704 704  
705 705  
706 -== 2.13  USB Port Function ==
707 -
708 -
709 709  The USB interface of TrackerD has below functions:
710 710  
711 711  * Power on the device
... ... @@ -713,9 +713,6 @@
713 713  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
714 714  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
715 715  
716 -(% style="display:none" %) (%%)
717 -
718 -
719 719  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
720 720  
721 721  
... ... @@ -730,22 +730,22 @@
730 730  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.
731 731  
732 732  
733 -[[image:1664502999401-486.png||_mstalt="296985"]]
652 +[[image:1664502999401-486.png]]
734 734  
735 735  
736 736  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:
737 737  
738 738  
739 -[[image:1664503022490-662.png||_mstalt="293332"]]
658 +[[image:1664503022490-662.png]]
740 740  
741 741  
742 -[[image:1664503035713-500.png||_mstalt="291096"]]
661 +[[image:1664503035713-500.png]]
743 743  
744 744  
745 -[[image:1664503047675-651.png||_mstalt="295386"]]
664 +[[image:1664503047675-651.png]]
746 746  
747 -(% style="display:none" %) (%%)
748 748  
667 +
749 749  == 3.2 Command Set ==
750 750  
751 751  === 3.2.1 Set Transmit Interval ===
... ... @@ -811,7 +811,7 @@
811 811  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
812 812  
813 813  
814 -=== 3.2.5 Disable/Enable LED flash and buzzer ===
733 +=== 3.2.5 Disable/Enable LED flash ===
815 815  
816 816  
817 817  Disable/Enable LED for position, downlink and uplink
... ... @@ -871,9 +871,9 @@
871 871  
872 872  (% style="color:#037691" %)**cc:   **
873 873  
874 -* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
793 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
875 875  
876 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
795 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
877 877  
878 878  (% style="color:blue" %)**Example:**
879 879  
... ... @@ -935,8 +935,8 @@
935 935  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
936 936  
937 937  
938 -=== 3.2.10 Disable/Enable the confirmation mode ===
939 939  
858 +**Disable/Enable the confirmation mode**
940 940  
941 941  * (% style="color:blue" %)**AT Command:**
942 942  
... ... @@ -955,7 +955,7 @@
955 955  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
956 956  
957 957  
958 -=== 3.2.11  Auto Send None-ACK messages ===
877 +=== 3.2.10  Auto Send None-ACK messages ===
959 959  
960 960  
961 961  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.
... ... @@ -973,10 +973,10 @@
973 973  
974 974  * (% style="color:blue" %)**Downlink Command: 0x34**
975 975  
976 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
895 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
977 977  
978 978  
979 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
898 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
980 980  
981 981  
982 982  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.
... ... @@ -985,16 +985,16 @@
985 985  
986 986  (% style="color:blue" %)**AT Command:**
987 987  
988 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
907 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
989 989  
990 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
909 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
991 991  
992 992  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
993 993  
994 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
913 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
995 995  
996 996  
997 -=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
916 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
998 998  
999 999  
1000 1000  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.
... ... @@ -1003,16 +1003,16 @@
1003 1003  
1004 1004  (% style="color:blue" %)**AT Command:**
1005 1005  
1006 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
925 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
1007 1007  
1008 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
927 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
1009 1009  
1010 1010  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
1011 1011  
1012 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
931 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
1013 1013  
1014 1014  
1015 -=== 3.2.14  Disable/Enable Information printing（Since firmware 1.4.1） ===
934 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
1016 1016  
1017 1017  
1018 1018  Users can use this feature to enable/disable Information printing.
... ... @@ -1019,11 +1019,11 @@
1019 1019  
1020 1020  (% style="color:blue" %)**AT Command:**
1021 1021  
1022 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/  (Disable (0), Enable (1), default:0)
941 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
1023 1023  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
1024 1024  
1025 1025  
1026 -=== 3.2.15  Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
945 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
1027 1027  
1028 1028  
1029 1029  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -1030,34 +1030,14 @@
1030 1030  
1031 1031  (% style="color:blue" %)**AT Command:**
1032 1032  
1033 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
952 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
1034 1034  
1035 1035  
1036 1036  (% style="color:blue" %)**Downlink Payload:0X24**
1037 1037  
1038 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
957 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
1039 1039  
1040 1040  
1041 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
1042 -
1043 -
1044 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
1045 -
1046 -(% style="color:blue" %)**AT Command:**
1047 -
1048 -(% style="color:#037691" %)**AT+PT=xx**
1049 -
1050 - Example:
1051 -
1052 - AT+PT=14    ~-~->    Set to detect car motion.
1053 -
1054 - AT+PT=41  ~-~->    set to detect walk motion.
1055 -
1056 -
1057 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
1058 -0xB4 14          ~/~/  Same as AT+PT=14
1059 -
1060 -
1061 1061  = 4. Setting for Different Scenarios =
1062 1062  
1063 1063  
... ... @@ -1090,10 +1090,10 @@
1090 1090  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1091 1091  
1092 1092  
1093 -[[image:1664503563660-578.png||_mstalt="296777"]]
992 +[[image:1664503563660-578.png]]
1094 1094  
1095 1095  
1096 -[[image:1664503574618-659.png||_mstalt="297986"]]
995 +[[image:1664503574618-659.png]]
1097 1097  
1098 1098  
1099 1099  
... ... @@ -1109,15 +1109,16 @@
1109 1109  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1110 1110  
1111 1111  
1112 -[[image:image-20221207120501-1.png]]
1011 +[[image:image-20221118105220-2.png]]
1113 1113  
1114 1114  
1115 1115  
1116 1116  After upgrade finish, it will show finish as below:
1117 1117  
1118 -[[image:image-20221207133911-7.png]]
1017 +[[image:image-20221118105402-4.png]]
1119 1119  
1120 1120  
1020 +
1121 1121  = 6. Developer Guide =
1122 1122  
1123 1123  == 6.1 Compile Source Code ==
... ... @@ -1130,81 +1130,24 @@
1130 1130  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]]
1131 1131  
1132 1132  
1133 -[[image:1664503635019-941.png||_mstalt="294658"]]
1033 +[[image:1664503635019-941.png]]
1134 1134  
1135 1135  
1136 1136  
1137 1137  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1138 1138  
1139 -[[image:1664503715811-892.png||_mstalt="295698"]]
1039 +[[image:1664503715811-892.png]]
1140 1140  
1141 1141  
1142 -=== 6.1.2  Build the development environment ===
1143 -
1144 -
1145 -**~1. Download and install arduino IDE**
1146 -
1147 -[[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]]
1148 -
1149 -
1150 -**2. Download the ESP32 development package in the arduino IDE**
1151 -
1152 -[[image:image-20221213100007-1.png]]
1153 -
1154 -
1155 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1156 -
1157 -[[image:image-20221213100626-2.png]]
1158 -
1159 -
1160 -Restart the IDE after the addition is complete, then:
1161 -
1162 -[[image:image-20221213100808-3.png||height="679" width="649"]]
1163 -
1164 -
1165 -[[image:image-20221213101040-4.png]]
1166 -
1167 -
1168 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1169 -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)**
1170 -
1171 -
1172 -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:
1173 -
1174 -(% style="color:blue" %)**Methods as below:**
1175 -
1176 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1177 -
1178 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1179 -
1180 1180  (% 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.
1181 1181  
1182 -[[image:image-20221213102311-5.png||height="582" width="711"]]
1044 +[[image:image-20221024105643-1.png]]
1183 1183  
1184 -
1185 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1186 -
1187 -[[image:image-20221213102334-6.png]]
1188 -
1189 -(% style="color:red" %)**Note: This step requires a python environment**
1190 -
1191 -
1192 -Either way, in the end:
1193 -
1194 -The final effect is to open the arduino and you can see the esp32
1195 -
1196 -[[image:image-20221213110952-8.png||height="866" width="711"]]
1197 -
1198 -
1199 -
1200 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1201 -
1202 1202  **~ Figure1**
1203 1203  
1204 1204  
1049 +[[image:image-20221024105643-2.png]]
1205 1205  
1206 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1207 -
1208 1208   **Figure2**
1209 1209  
1210 1210  
... ... @@ -1213,7 +1213,7 @@
1213 1213  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1214 1214  
1215 1215  
1216 -[[image:1664503752288-974.png||_mstalt="298194"]]
1059 +[[image:1664503752288-974.png]]
1217 1217  
1218 1218  
1219 1219  == 6.2 Source Code ==
... ... @@ -1221,19 +1221,19 @@
1221 1221  
1222 1222  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1223 1223  
1224 -[[image:1664503794261-827.png||_mstalt="296387"]]
1067 +[[image:1664503794261-827.png]]
1225 1225  
1226 1226  
1227 1227  
1228 1228  * (% style="color:blue" %)**Click to upload**
1229 1229  
1230 -[[image:1664503808294-336.png||_mstalt="295711"]]
1073 +[[image:1664503808294-336.png]]
1231 1231  
1232 1232  
1233 1233  
1234 1234  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1235 1235  
1236 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1079 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1237 1237  
1238 1238  
1239 1239  = 7.  FAQ =
... ... @@ -1247,7 +1247,7 @@
1247 1247  == 7.2 What is the pin mapping for the USB program cable? ==
1248 1248  
1249 1249  
1250 -[[image:1664499635206-262.png||_mstalt="295360"]]
1093 +[[image:1664499635206-262.png]]
1251 1251  
1252 1252  
1253 1253  
... ... @@ -1262,9 +1262,6 @@
1262 1262  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1263 1263  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1264 1264  
1265 -(% style="display:none" %) (%%)
1266 -
1267 -
1268 1268  == 7.3 Notes on using different serial port tools for TrackerD ==
1269 1269  
1270 1270  === 7.3.1  Serial port utility ===
... ... @@ -1275,13 +1275,13 @@
1275 1275  Need to adjust the data stream to RTS/CTS on physical restart.
1276 1276  
1277 1277  (% class="wikigeneratedid" %)
1278 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1118 +[[image:image-20221102140621-1.png]]
1279 1279  
1280 1280  
1281 1281  
1282 1282  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1283 1283  
1284 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1124 +[[image:image-20221102140638-2.png]]
1285 1285  
1286 1286  
1287 1287  === 7.3.2  SecureCRT ===
... ... @@ -1290,22 +1290,22 @@
1290 1290  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.
1291 1291  
1292 1292  
1293 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1133 +[[image:image-20221102140704-3.png]]
1294 1294  
1295 1295  
1296 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1136 +[[image:image-20221102140712-4.png]]
1297 1297  
1298 1298  
1299 1299  === 7.3.3  PUTTY ===
1300 1300  
1301 1301  
1302 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1142 +[[image:image-20221102140748-5.png]]
1303 1303  
1304 1304  
1305 1305  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.
1306 1306  
1307 1307  
1308 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1148 +[[image:image-20221102140801-6.png]]
1309 1309  
1310 1310  
1311 1311  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1320,7 +1320,7 @@
1320 1320  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1321 1321  
1322 1322  
1323 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1163 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1324 1324  
1325 1325  
1326 1326  
... ... @@ -1327,7 +1327,7 @@
1327 1327  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1328 1328  
1329 1329  
1330 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1170 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1331 1331  
1332 1332  
1333 1333  
... ... @@ -1334,7 +1334,7 @@
1334 1334  **3. Compile the AS923_JP band, please refer to the intention shown**
1335 1335  
1336 1336  
1337 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1177 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1338 1338  
1339 1339  
1340 1340  
... ... @@ -1341,18 +1341,12 @@
1341 1341  **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.**
1342 1342  
1343 1343  
1344 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1184 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1345 1345  
1346 1346  
1347 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1187 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1348 1348  
1349 1349  
1350 -== 7.5 Are there example python example for BLE Indoor Positioning? ==
1351 -
1352 -
1353 -[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1354 -
1355 -
1356 1356  = 8  Trouble Shooting =
1357 1357  
1358 1358  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
... ... @@ -1359,7 +1359,7 @@
1359 1359  
1360 1360  
1361 1361  (((
1362 -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
1196 +Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1363 1363  )))
1364 1364  
1365 1365  
... ... @@ -1373,69 +1373,50 @@
1373 1373  
1374 1374  == 8.3  Problem after Upgrading Firmware ==
1375 1375  
1376 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1210 +=== 8.3.1 Continue Restart after upgrading ===
1377 1377  
1378 1378  
1379 -**Error Output**
1380 -
1381 -
1382 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1383 -
1384 -
1385 1385  (((
1386 -Some partition is missed during upgrade, please upgrade below four files as example:
1387 -
1388 -[[image:image-20221207120524-2.png]]
1214 +If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
1389 1389  )))
1390 1390  
1391 1391  
1392 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1218 +[[image:image-20221118105249-3.png]]
1393 1393  
1394 1394  
1395 -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
1221 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1396 1396  
1397 1397  
1398 -=== 8.3.3 "flash read err" after upgrade firmware ===
1224 +It is because the partitions are different when upgrading versions above 1.4.1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1
1399 1399  
1400 1400  
1227 +=== 8.3.3 "flash read err" after upgrade firmware ===
1228 +
1401 1401  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1402 1402  
1231 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1403 1403  
1404 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1405 1405  
1406 -
1407 1407  User need to upgrade again with below four files to solve this issue.
1408 1408  
1409 - [[image:image-20221207120530-3.png]]
1236 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1410 1410  
1411 1411   **Figure 2**
1412 1412  
1413 1413  
1414 -=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1241 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1415 1415  
1416 -
1417 1417  User might erase the entire flash include keys and default settings which cause this issue.
1418 1418  
1419 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1245 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1420 1420  
1247 +[[image:image-20221122100004-3.png]]
1421 1421  
1422 -[[image:image-20221122100004-3.png||_mstalt="424242"]]
1249 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1423 1423  
1424 1424  
1425 -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.
1252 +Example:
1426 1426  
1427 -After AT+FDR. please set
1428 -
1429 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1430 -
1431 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1432 -
1433 -**Example:**
1434 -
1435 -AT+PDOP=7.00
1436 -
1437 -AT+FTIME=180
1438 -
1439 1439  AT+DEUI=70B3D57ED0053981  
1440 1440  
1441 1441  AT+APPEUI=D23345667BCBCCAF
... ... @@ -1449,6 +1449,13 @@
1449 1449  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1450 1450  
1451 1451  
1267 +
1268 +=== 8.3.4  If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ===
1269 +
1270 +
1271 +[[image:image-20221122100004-4.png]]
1272 +
1273 +
1452 1452  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1453 1453  
1454 1454  
... ... @@ -1462,61 +1462,15 @@
1462 1462  
1463 1463  2)  Set PDOP to a higher value.
1464 1464  
1465 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1287 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1466 1466  
1467 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1289 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1468 1468  
1469 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1291 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1470 1470  
1471 1471  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
1472 1472  
1473 1473  
1474 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1475 -
1476 -
1477 -When upgrading, use the erase button to upgrade
1478 -
1479 -[[image:image-20221207120536-4.png]]
1480 -
1481 -
1482 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1483 -
1484 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1485 -
1486 -
1487 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1488 -
1489 -[[image:image-20221207134028-8.png]]
1490 -
1491 -
1492 -Reboot information after upgrade
1493 -
1494 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1495 -
1496 -
1497 -Use **AT+FDR** command to reset and then use **AT+CFG** to check whether the configuration is back to normal
1498 -
1499 -[[image:image-20221128111850-5.png]]
1500 -
1501 -
1502 -After the parameters return to normal, upgrade to the version you need again
1503 -
1504 -[[image:image-20221207120601-5.png]]
1505 -
1506 -
1507 -At this point, the parameters return to normal after running AT+FDR again
1508 -
1509 -[[image:image-20221128112035-7.png]]
1510 -
1511 -
1512 -== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1513 -
1514 -
1515 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1516 -
1517 -2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1518 -
1519 -
1520 1520  = 9.  Order Info =
1521 1521  
1522 1522  
... ... @@ -1538,9 +1538,6 @@
1538 1538  
1539 1539  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1540 1540  
1541 -(% style="display:none" %) (%%)
1542 -
1543 -
1544 1544  = 10.  Packing Info =
1545 1545  
1546 1546  
... ... @@ -1556,9 +1556,6 @@
1556 1556  
1557 1557  * Weight: 50g
1558 1558  
1559 -(% style="display:none" %) (%%)
1560 -
1561 -
1562 1562  = 11. Support =
1563 1563  
1564 1564  
... ... @@ -1566,9 +1566,6 @@
1566 1566  
1567 1567  * 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]].
1568 1568  
1569 -(% style="display:none" %) (%%)
1570 -
1571 -
1572 1572  = 12.  Reference =
1573 1573  
1574 1574  
... ... @@ -1577,6 +1577,3 @@
1577 1577  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1578 1578  
1579 1579  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1580 -
1581 -
1582 -)))
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