Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 202.3
edited by Xiaoling
on 2023/03/18 16:25
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.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,8 +93,6 @@
93 93  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
94 94  * Tracking: max: 38mA
95 95  
96 -
97 -
98 98  == 1.3  Features ==
99 99  
100 100  
... ... @@ -113,8 +113,6 @@
113 113  * Tri-color LED, Alarm button
114 114  * Datalog
115 115  
116 -
117 -
118 118  == 1.4  Applications ==
119 119  
120 120  
... ... @@ -121,8 +121,6 @@
121 121  * Logistics and Supply Chain Management
122 122  * Human tracking
123 123  
124 -
125 -
126 126  = 2.  Use TrackerD =
127 127  
128 128  == 2.1 How it works? ==
... ... @@ -137,7 +137,7 @@
137 137  Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example. 
138 138  
139 139  
140 -[[image:image-20230213110214-2.png||height="388" width="847"]]
136 +[[image:1664501652064-326.png]]
141 141  
142 142  
143 143  
... ... @@ -149,7 +149,7 @@
149 149  Each TrackerD is shipped with a sticker with the default device EUI as below:
150 150  
151 151  
152 -[[image:1664501677253-891.png||_mstalt="296569"]]
148 +[[image:1664501677253-891.png]]
153 153  
154 154  
155 155  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -158,14 +158,14 @@
158 158  **__Add APP EUI in the application:__**
159 159  
160 160  
161 -[[image:1664501711466-918.png||_mstalt="295828"]]
157 +[[image:1664501711466-918.png]]
162 162  
163 163  
164 164  
165 -[[image:1664501721248-725.png||_mstalt="294450"]]
161 +[[image:1664501721248-725.png]]
166 166  
167 167  
168 -[[image:1664501734705-405.png||_mstalt="293306"]]
164 +[[image:1664501734705-405.png]]
169 169  
170 170  
171 171  
... ... @@ -172,15 +172,15 @@
172 172  **__Add APP KEY and DEV EUI:__**
173 173  
174 174  
175 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]]
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"]]
176 176  
177 177  
178 178  
179 179  (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
180 180  
181 -(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
177 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
182 182  
183 -[[image:1664502835802-546.png||_mstalt="295061"]]
179 +[[image:1664502835802-546.png]]
184 184  
185 185  
186 186  (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
... ... @@ -209,10 +209,10 @@
209 209  
210 210  
211 211  (% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
212 -|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)1|=(% style="width: 40px;" %)1
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
213 213  |=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
214 214  
215 -[[image:1665301570342-765.png||_mstalt="294580"]]
211 +[[image:1665301570342-765.png]]
216 216  
217 217  
218 218  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -256,7 +256,7 @@
256 256  (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
257 257  
258 258  (% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
259 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)1bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
255 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
260 260  |=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
261 261  
262 262  (% style="color:blue" %)** SMOD：**
... ... @@ -279,17 +279,15 @@
279 279  
280 280  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
281 281  
282 -(% _mstmutation="1" style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
278 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
283 283  
284 284  
285 285  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
286 286  
287 -(% border="1.5" style="background-color:#ffffcc; color:green; width:412.222px" %)
288 -|=(% scope="row" style="width: 75px;" %)**Size(bit)**|(% style="width:68px" %)5 Bits|(% style="width:87px" %)1 Bit|(% style="width:49px" %)1 Bit|(% style="width:126px" %)1 Bit
289 -|=(% style="width: 75px;" %)**Value**|(% style="width:68px" %)Reserve|(% style="width:87px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:49px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
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"]]
290 290  
291 -
292 -
293 293  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
294 294  
295 295  
... ... @@ -308,20 +308,20 @@
308 308  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
309 309  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
310 310  
311 -[[image:1665301636888-168.png||_mstalt="298012"]]
305 +[[image:1665301636888-168.png]]
312 312  
313 313  
314 314  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
315 315  
316 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:279.222px" %)
317 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:69px" %)1 bit|(% style="width:63px" %)14 bits
318 -|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:69px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
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:"]] 
319 319  
320 320  ==== (% style="color:blue" %)**FLAG:**(%%) ====
321 321  
322 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:183.222px" %)
323 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2 bits|(% style="width:52px" %)1 bit
324 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:52px" %)[[LON>>||anchor="HLON:"]]
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:"]]
325 325  
326 326  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
327 327  
... ... @@ -338,12 +338,12 @@
338 338  2.  In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
339 339  
340 340  
341 -[[image:1664502116362-706.png||_mstalt="293306"]]
335 +[[image:1664502116362-706.png]]
342 342  
343 343  
344 344  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
345 345  
346 -[[image:1664502166010-515.png||_mstalt="291395"]]
340 +[[image:1664502166010-515.png]]
347 347  
348 348  
349 349  
... ... @@ -366,9 +366,6 @@
366 366  * 3.40v ~~ 3.69v:  20% ~~ 40%
367 367  * < 3.39v:  0~~20%
368 368  
369 -(% style="display:none" %) (%%)
370 -
371 -
372 372  ==== (% style="color:blue" %)**MOD:**(%%) ====
373 373  
374 374  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -424,13 +424,13 @@
424 424  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
425 425  
426 426  (% class="wikigeneratedid" %)
427 -[[image:1665301687277-443.png||_mstalt="296140"]]
418 +[[image:1665301687277-443.png]]
428 428  
429 429  
430 430  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
431 431  
432 432  
433 -Set [[PNACKMD=1>>||anchor="H3.2.11A0AutoSendNone-ACKmessages"]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
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.
434 434  
435 435  
436 436  (% style="color:red" %)**Note for this mode:**
... ... @@ -447,7 +447,7 @@
447 447  )))|4|4|2|1|1|1|1|1
448 448  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
449 449  
450 -[[image:image-20221009160309-2.png||_mstalt="429312"]]
441 +[[image:image-20221009160309-2.png]]
451 451  
452 452  
453 453  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
... ... @@ -474,7 +474,7 @@
474 474  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
475 475  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
476 476  
477 -[[image:1664502425687-834.png||_mstalt="296738"]]
468 +[[image:1664502425687-834.png]]
478 478  
479 479  
480 480  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -485,32 +485,9 @@
485 485  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
486 486  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
487 487  
488 -(% style="display:none" %) (%%)
479 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
489 489  
490 490  
491 -=== 2.4.6  Uplink FPORT~=7, Alarm information status（Since firmware 1.4.4） ===
492 -
493 -
494 -The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server.
495 -
496 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
497 -|**Size(bytes)**|2|1
498 -|**Value**|[[Alarm & BAT>>path:#HAlarm26BAT:]]|Mod+lon
499 -
500 - [[image:image-20230302145315-1.png]]
501 -
502 -alarm=(bytes[0] & 0x40)  ~/~/ Alarm status
503 -
504 -batV=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000;  ~/~/ Battery,units:V
505 -
506 -mod = bytes[2] & 0xC0;
507 -
508 -Lon=(bytes[2] & 0x20)
509 -
510 -
511 -=== 2.4.7  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
512 -
513 -
514 514  TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **WiFi** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
515 515  
516 516  
... ... @@ -523,7 +523,7 @@
523 523  )))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
524 524  
525 525  (% class="wikigeneratedid" %)
526 -[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
494 +[[image:1667288597595-714.png||height="212" width="1151"]]
527 527  
528 528  
529 529  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -530,18 +530,15 @@
530 530  * (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
531 531  * (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
532 532  
533 -(% style="display:none" %) (%%)
501 +=== 2.4.7  Add Payload format in TTN V3 ===
534 534  
535 535  
536 -=== 2.4.8  Add Payload format in TTN V3 ===
537 -
538 -
539 539  In TTN V3, user can add a custom payload so it shows friendly.
540 540  
541 541  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
542 542  
543 543  
544 -[[image:1664502649601-895.png||_mstalt="296985"]]
509 +[[image:1664502649601-895.png]]
545 545  
546 546  
547 547  
... ... @@ -551,7 +551,7 @@
551 551  
552 552  Save the change the uplink message will be parsed. As below:
553 553  
554 -[[image:1664502676891-606.png||_mstalt="296673"]]
519 +[[image:1664502676891-606.png]]
555 555  
556 556  
557 557  == 2.5 Integrate with Datacake ==
... ... @@ -562,7 +562,7 @@
562 562  Instruction is here:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example~~-~~-AddTrackerDGPSTrackingInDataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example--AddTrackerDGPSTrackingInDataCake]]
563 563  
564 564  
565 -[[image:1664502695771-538.png||_mstalt="297349"]]
530 +[[image:1664502695771-538.png]]
566 566  
567 567  
568 568  == 2.6 Integrate with Tago ==
... ... @@ -573,66 +573,25 @@
573 573  Instruction is here: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Tago.IO/#H3.A0Example-CreateTrackerD2FLGT92positioningwidget]]
574 574  
575 575  
576 -[[image:1664502715371-321.png||_mstalt="292162"]]
541 +[[image:1664502715371-321.png]]
577 577  
578 578  
579 -== 2.7  Integrate with Node-red ==
544 +== 2.7  Datalog Feature ==
580 580  
581 581  
582 -~1. Install node-red, please refer to the installation method in the link:
583 -
584 - [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]]
585 -
586 -
587 -2. Import the created flow template, please refer to the import method in the link:
588 -
589 - [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]]
590 - The address of the flow template:
591 -
592 - [[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]]
593 -
594 -(% 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.**
595 -
596 -[[image:image-20230307135914-1.png||height="527" width="1045"]]
597 -
598 -
599 -[[image:image-20230307135932-2.png||height="527" width="1044"]]
600 -
601 -
602 -3. Display the map
603 - Enter the link to the map:
604 -
605 - Change its suffix to ditu：http:~/~/119.91.62.30:1880/**ditu/**
606 -
607 -**~ **[[image:image-20230308115430-1.png||height="548" width="1041"]]
608 -
609 -
610 - Hit all input in input stream
611 -
612 - [[image:image-20230308115616-2.png||height="563" width="1070"]]
613 -
614 -
615 - View map again
616 -
617 -[[image:image-20230308115701-3.png||height="571" width="1085"]]
618 -
619 -
620 -== 2.8  Datalog Feature ==
621 -
622 -
623 623  total 273 entries,by default,
624 624  
625 -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.
626 626  
627 627  Example use case.
628 628  
629 -[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
553 +[[image:image-20221009234703-2.png||height="328" width="899"]]
630 630  
631 631  
632 -[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
556 +[[image:image-20221009234629-1.png||height="390" width="577"]]
633 633  
634 634  
635 -== 2.9  Alarm Mode ==
559 +== 2.8 Alarm Mode ==
636 636  
637 637  
638 638  (((
... ... @@ -657,21 +657,15 @@
657 657  )))
658 658  
659 659  
660 -== 2.10  Transport Mode ==
584 +== 2.9 Transport Mode ==
661 661  
662 662  
663 663  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.
664 664  
665 -* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
666 -* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
667 -* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
668 668  
669 -(% style="display:none" %) (%%)
590 +== 2.10 LED Status ==
670 670  
671 671  
672 -== 2.11  LED Status ==
673 -
674 -
675 675  (% border="1.5" style="background-color:#ffffcc; width:500px" %)
676 676  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
677 677  |(% 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
... ... @@ -686,15 +686,12 @@
686 686  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
687 687  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
688 688  
689 -(% style="display:none" %) (%%)
607 +== 2.11 Button Function ==
690 690  
691 691  
692 -== 2.12  Button Function ==
693 -
694 -
695 695  (% style="color:blue" %)**RESET button:**
696 696  
697 -[[image:1664502835802-546.png||_mstalt="295061"]]
612 +[[image:1664502835802-546.png]]
698 698  
699 699  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
700 700  
... ... @@ -701,9 +701,8 @@
701 701  
702 702  (% style="color:red" %)**RED button:**
703 703  
704 -[[image:image-20230213110506-3.png]](% style="display:none" %)
619 +[[image:1664502854406-763.png]]
705 705  
706 -(% style="display:none" %) (%%)
707 707  
708 708  (% border="1" style="background-color:#ffffcc; width:510px" %)
709 709  |=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
... ... @@ -711,12 +711,9 @@
711 711  |(% 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
712 712  |(% 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.
713 713  
714 -(% style="display:none" %) (%%)
628 +== 2.12 USB Port Function ==
715 715  
716 716  
717 -== 2.13  USB Port Function ==
718 -
719 -
720 720  The USB interface of TrackerD has below functions:
721 721  
722 722  * Power on the device
... ... @@ -724,19 +724,6 @@
724 724  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
725 725  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
726 726  
727 -(% style="display:none" %) (%%)
728 -
729 -
730 -== 2.14  Sleep Mode ==
731 -
732 -
733 -(% 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.
734 -
735 -In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**.
736 -
737 -Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep.
738 -
739 -
740 740  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
741 741  
742 742  
... ... @@ -751,22 +751,22 @@
751 751  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.
752 752  
753 753  
754 -[[image:1664502999401-486.png||_mstalt="296985"]]
652 +[[image:1664502999401-486.png]]
755 755  
756 756  
757 757  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:
758 758  
759 759  
760 -[[image:1664503022490-662.png||_mstalt="293332"]]
658 +[[image:1664503022490-662.png]]
761 761  
762 762  
763 -[[image:1664503035713-500.png||_mstalt="291096"]]
661 +[[image:1664503035713-500.png]]
764 764  
765 765  
766 -[[image:1664503047675-651.png||_mstalt="295386"]]
664 +[[image:1664503047675-651.png]]
767 767  
768 -(% style="display:none" %) (%%)
769 769  
667 +
770 770  == 3.2 Command Set ==
771 771  
772 772  === 3.2.1 Set Transmit Interval ===
... ... @@ -832,7 +832,7 @@
832 832  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
833 833  
834 834  
835 -=== 3.2.5 Disable/Enable LED flash and buzzer ===
733 +=== 3.2.5 Disable/Enable LED flash ===
836 836  
837 837  
838 838  Disable/Enable LED for position, downlink and uplink
... ... @@ -892,9 +892,9 @@
892 892  
893 893  (% style="color:#037691" %)**cc:   **
894 894  
895 -* (% _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  
896 896  
897 -* (% _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(%%))  
898 898  
899 899  (% style="color:blue" %)**Example:**
900 900  
... ... @@ -956,8 +956,8 @@
956 956  (% style="color:#037691" %)**0xAD 00 46**    (%%) ~/~/  Set AT+PDOP=7  (0x46 / 10 =7)
957 957  
958 958  
959 -=== 3.2.10 Disable/Enable the confirmation mode ===
960 960  
858 +**Disable/Enable the confirmation mode**
961 961  
962 962  * (% style="color:blue" %)**AT Command:**
963 963  
... ... @@ -976,7 +976,7 @@
976 976  (% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
977 977  
978 978  
979 -=== 3.2.11  Auto Send None-ACK messages ===
877 +=== 3.2.10  Auto Send None-ACK messages ===
980 980  
981 981  
982 982  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.
... ... @@ -994,10 +994,10 @@
994 994  
995 995  * (% style="color:blue" %)**Downlink Command: 0x34**
996 996  
997 -Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
895 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
998 998  
999 999  
1000 -=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
898 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
1001 1001  
1002 1002  
1003 1003  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.
... ... @@ -1006,16 +1006,16 @@
1006 1006  
1007 1007  (% style="color:blue" %)**AT Command:**
1008 1008  
1009 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
907 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
1010 1010  
1011 - (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
909 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
1012 1012  
1013 1013  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
1014 1014  
1015 -Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
913 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
1016 1016  
1017 1017  
1018 -=== 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） ===
1019 1019  
1020 1020  
1021 1021  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.
... ... @@ -1024,16 +1024,16 @@
1024 1024  
1025 1025  (% style="color:blue" %)**AT Command:**
1026 1026  
1027 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
925 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
1028 1028  
1029 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
927 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
1030 1030  
1031 1031  (% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
1032 1032  
1033 -Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
931 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
1034 1034  
1035 1035  
1036 -=== 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） ===
1037 1037  
1038 1038  
1039 1039  Users can use this feature to enable/disable Information printing.
... ... @@ -1040,11 +1040,11 @@
1040 1040  
1041 1041  (% style="color:blue" %)**AT Command:**
1042 1042  
1043 -(% 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)
1044 1044  \\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
1045 1045  
1046 1046  
1047 -=== 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） ===
1048 1048  
1049 1049  
1050 1050  The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
... ... @@ -1051,34 +1051,14 @@
1051 1051  
1052 1052  (% style="color:blue" %)**AT Command:**
1053 1053  
1054 -(% style="color:#037691" %)**AT+CHE=1      **(%%) ~/~/ set one channels mode
952 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
1055 1055  
1056 1056  
1057 1057  (% style="color:blue" %)**Downlink Payload:0X24**
1058 1058  
1059 -Example: 0x24 01  ~/~/ Same as AT+CHE=1
957 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
1060 1060  
1061 1061  
1062 -=== 3.2.16  Get or Set Threshold for motion detect（Since firmware 1.4.3） ===
1063 -
1064 -
1065 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
1066 -
1067 -(% style="color:blue" %)**AT Command:**
1068 -
1069 -(% style="color:#037691" %)**AT+PT=xx**
1070 -
1071 - Example:
1072 -
1073 - AT+PT=14    ~-~->    Set to detect car motion.
1074 -
1075 - AT+PT=41  ~-~->    set to detect walk motion.
1076 -
1077 -
1078 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
1079 -0xB4 14          ~/~/  Same as AT+PT=14
1080 -
1081 -
1082 1082  = 4. Setting for Different Scenarios =
1083 1083  
1084 1084  
... ... @@ -1111,10 +1111,10 @@
1111 1111  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
1112 1112  
1113 1113  
1114 -[[image:1664503563660-578.png||_mstalt="296777"]]
992 +[[image:1664503563660-578.png]]
1115 1115  
1116 1116  
1117 -[[image:1664503574618-659.png||_mstalt="297986"]]
995 +[[image:1664503574618-659.png]]
1118 1118  
1119 1119  
1120 1120  
... ... @@ -1130,15 +1130,16 @@
1130 1130  US915.bin @ 0x10000(Select the bin file of the frequency band you need)
1131 1131  
1132 1132  
1133 -[[image:image-20221207120501-1.png]]
1011 +[[image:image-20221118105220-2.png]]
1134 1134  
1135 1135  
1136 1136  
1137 1137  After upgrade finish, it will show finish as below:
1138 1138  
1139 -[[image:image-20221207133911-7.png]]
1017 +[[image:image-20221118105402-4.png]]
1140 1140  
1141 1141  
1020 +
1142 1142  = 6. Developer Guide =
1143 1143  
1144 1144  == 6.1 Compile Source Code ==
... ... @@ -1151,81 +1151,24 @@
1151 1151  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]]
1152 1152  
1153 1153  
1154 -[[image:1664503635019-941.png||_mstalt="294658"]]
1033 +[[image:1664503635019-941.png]]
1155 1155  
1156 1156  
1157 1157  
1158 1158  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1159 1159  
1160 -[[image:1664503715811-892.png||_mstalt="295698"]]
1039 +[[image:1664503715811-892.png]]
1161 1161  
1162 1162  
1163 -=== 6.1.2  Build the development environment ===
1164 -
1165 -
1166 -**~1. Download and install arduino IDE**
1167 -
1168 -[[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]]
1169 -
1170 -
1171 -**2. Download the ESP32 development package in the arduino IDE**
1172 -
1173 -[[image:image-20221213100007-1.png]]
1174 -
1175 -
1176 -Input: [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>https://dl.espressif.com/dl/package_esp32_index.json]]
1177 -
1178 -[[image:image-20221213100626-2.png]]
1179 -
1180 -
1181 -Restart the IDE after the addition is complete, then:
1182 -
1183 -[[image:image-20221213100808-3.png||height="679" width="649"]]
1184 -
1185 -
1186 -[[image:image-20221213101040-4.png]]
1187 -
1188 -
1189 -(% style="color:red" %)**Note: Currently version 1.04 is almost impossible to download, you can choose version 1.03.
1190 -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)**
1191 -
1192 -
1193 -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:
1194 -
1195 -(% style="color:blue" %)**Methods as below:**
1196 -
1197 -~1. Download: [[https:~~/~~/github.com/dragino/TrackerD/releases/tag/v1.4.4>>https://github.com/dragino/TrackerD/releases/tag/v1.4.4]]
1198 -
1199 -2. Find the arduino installation path, hardware → create a new espressif folder → create a new esp32 folder, unzip the compressed package here.
1200 -
1201 1201  (% 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.
1202 1202  
1203 -[[image:image-20221213102311-5.png||height="582" width="711"]]
1044 +[[image:image-20221024105643-1.png]]
1204 1204  
1205 -
1206 -**3. Find tools→get.exe in the decompressed file and run it (it will close automatically after completion)**
1207 -
1208 -[[image:image-20221213102334-6.png]]
1209 -
1210 -(% style="color:red" %)**Note: This step requires a python environment**
1211 -
1212 -
1213 -Either way, in the end:
1214 -
1215 -The final effect is to open the arduino and you can see the esp32
1216 -
1217 -[[image:image-20221213110952-8.png||height="866" width="711"]]
1218 -
1219 -
1220 -
1221 -[[image:image-20221024105643-1.png||_mstalt="428129"]]
1222 -
1223 1223  **~ Figure1**
1224 1224  
1225 1225  
1049 +[[image:image-20221024105643-2.png]]
1226 1226  
1227 -[[image:image-20221024105643-2.png||_mstalt="428493"]]
1228 -
1229 1229   **Figure2**
1230 1230  
1231 1231  
... ... @@ -1234,7 +1234,7 @@
1234 1234  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1235 1235  
1236 1236  
1237 -[[image:1664503752288-974.png||_mstalt="298194"]]
1059 +[[image:1664503752288-974.png]]
1238 1238  
1239 1239  
1240 1240  == 6.2 Source Code ==
... ... @@ -1242,19 +1242,19 @@
1242 1242  
1243 1243  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1244 1244  
1245 -[[image:1664503794261-827.png||_mstalt="296387"]]
1067 +[[image:1664503794261-827.png]]
1246 1246  
1247 1247  
1248 1248  
1249 1249  * (% style="color:blue" %)**Click to upload**
1250 1250  
1251 -[[image:1664503808294-336.png||_mstalt="295711"]]
1073 +[[image:1664503808294-336.png]]
1252 1252  
1253 1253  
1254 1254  
1255 1255  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1256 1256  
1257 -[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1079 +[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1258 1258  
1259 1259  
1260 1260  = 7.  FAQ =
... ... @@ -1268,7 +1268,7 @@
1268 1268  == 7.2 What is the pin mapping for the USB program cable? ==
1269 1269  
1270 1270  
1271 -[[image:1664499635206-262.png||_mstalt="295360"]]
1093 +[[image:1664499635206-262.png]]
1272 1272  
1273 1273  
1274 1274  
... ... @@ -1283,9 +1283,6 @@
1283 1283  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1284 1284  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1285 1285  
1286 -(% style="display:none" %) (%%)
1287 -
1288 -
1289 1289  == 7.3 Notes on using different serial port tools for TrackerD ==
1290 1290  
1291 1291  === 7.3.1  Serial port utility ===
... ... @@ -1296,13 +1296,13 @@
1296 1296  Need to adjust the data stream to RTS/CTS on physical restart.
1297 1297  
1298 1298  (% class="wikigeneratedid" %)
1299 -[[image:image-20221102140621-1.png||_mstalt="425672"]]
1118 +[[image:image-20221102140621-1.png]]
1300 1300  
1301 1301  
1302 1302  
1303 1303  When using AT commands, the data flow needs to be adjusted to XON/XOFF
1304 1304  
1305 -[[image:image-20221102140638-2.png||_mstalt="428727"]]
1124 +[[image:image-20221102140638-2.png]]
1306 1306  
1307 1307  
1308 1308  === 7.3.2  SecureCRT ===
... ... @@ -1311,22 +1311,22 @@
1311 1311  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.
1312 1312  
1313 1313  
1314 -[[image:image-20221102140704-3.png||_mstalt="427076"]]
1133 +[[image:image-20221102140704-3.png]]
1315 1315  
1316 1316  
1317 -[[image:image-20221102140712-4.png||_mstalt="427089"]]
1136 +[[image:image-20221102140712-4.png]]
1318 1318  
1319 1319  
1320 1320  === 7.3.3  PUTTY ===
1321 1321  
1322 1322  
1323 -[[image:image-20221102140748-5.png||_mstalt="430456"]]
1142 +[[image:image-20221102140748-5.png]]
1324 1324  
1325 1325  
1326 1326  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.
1327 1327  
1328 1328  
1329 -[[image:image-20221102140801-6.png||_mstalt="427466"]]
1148 +[[image:image-20221102140801-6.png]]
1330 1330  
1331 1331  
1332 1332  == 7.4 How to modify source code to compile different frequency band bin file? ==
... ... @@ -1341,7 +1341,7 @@
1341 1341  **~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1342 1342  
1343 1343  
1344 -[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1163 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1345 1345  
1346 1346  
1347 1347  
... ... @@ -1348,7 +1348,7 @@
1348 1348  **2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1349 1349  
1350 1350  
1351 -[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1170 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1352 1352  
1353 1353  
1354 1354  
... ... @@ -1355,7 +1355,7 @@
1355 1355  **3. Compile the AS923_JP band, please refer to the intention shown**
1356 1356  
1357 1357  
1358 -[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1177 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1359 1359  
1360 1360  
1361 1361  
... ... @@ -1362,18 +1362,12 @@
1362 1362  **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.**
1363 1363  
1364 1364  
1365 -[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1184 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1366 1366  
1367 1367  
1368 -[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1187 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1369 1369  
1370 1370  
1371 -== 7.5 Are there example python example for BLE Indoor Positioning? ==
1372 -
1373 -
1374 -[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]]
1375 -
1376 -
1377 1377  = 8  Trouble Shooting =
1378 1378  
1379 1379  == 8.1  TDC is changed to 4294947296 and cause no uplink. ==
... ... @@ -1380,7 +1380,7 @@
1380 1380  
1381 1381  
1382 1382  (((
1383 -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
1384 1384  )))
1385 1385  
1386 1386  
... ... @@ -1394,69 +1394,50 @@
1394 1394  
1395 1395  == 8.3  Problem after Upgrading Firmware ==
1396 1396  
1397 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1210 +=== 8.3.1 Continue Restart after upgrading ===
1398 1398  
1399 1399  
1400 -**Error Output**
1401 -
1402 -
1403 -[[image:image-20221122100004-4.png||_mstalt="424606"]]
1404 -
1405 -
1406 1406  (((
1407 -Some partition is missed during upgrade, please upgrade below four files as example:
1408 -
1409 -[[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
1410 1410  )))
1411 1411  
1412 1412  
1413 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1218 +[[image:image-20221118105249-3.png]]
1414 1414  
1415 1415  
1416 -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 ===
1417 1417  
1418 1418  
1419 -=== 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
1420 1420  
1421 1421  
1227 +=== 8.3.3 "flash read err" after upgrade firmware ===
1228 +
1422 1422  Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1423 1423  
1231 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1424 1424  
1425 -[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1426 1426  
1427 -
1428 1428  User need to upgrade again with below four files to solve this issue.
1429 1429  
1430 - [[image:image-20221207120530-3.png]]
1236 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1431 1431  
1432 1432   **Figure 2**
1433 1433  
1434 1434  
1435 -=== 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 ===
1436 1436  
1437 -
1438 1438  User might erase the entire flash include keys and default settings which cause this issue.
1439 1439  
1440 -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.
1441 1441  
1247 +[[image:image-20221122100004-3.png]]
1442 1442  
1443 -[[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.
1444 1444  
1445 1445  
1446 -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:
1447 1447  
1448 -After AT+FDR. please set
1449 -
1450 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1451 -
1452 -* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1453 -
1454 -**Example:**
1455 -
1456 -AT+PDOP=7.00
1457 -
1458 -AT+FTIME=180
1459 -
1460 1460  AT+DEUI=70B3D57ED0053981  
1461 1461  
1462 1462  AT+APPEUI=D23345667BCBCCAF
... ... @@ -1470,6 +1470,13 @@
1470 1470  AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1471 1471  
1472 1472  
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 +
1473 1473  == 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1474 1474  
1475 1475  
... ... @@ -1483,61 +1483,15 @@
1483 1483  
1484 1484  2)  Set PDOP to a higher value.
1485 1485  
1486 -* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1287 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1487 1487  
1488 -* (% _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）
1489 1489  
1490 -* (% _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）
1491 1491  
1492 1492  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
1493 1493  
1494 1494  
1495 -== 8.6  When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==
1496 -
1497 -
1498 -When upgrading, use the erase button to upgrade
1499 -
1500 -[[image:image-20221207120536-4.png]]
1501 -
1502 -
1503 -The parameters are displayed abnormally and cannot be fixed using AT+FDR
1504 -
1505 -[[image:image-20221128103040-2.png||height="431" width="525"]]
1506 -
1507 -
1508 -Please upgrade these four files,link（The boot_app0 file is in the version folder you need)
1509 -
1510 -[[image:image-20221207134028-8.png]]
1511 -
1512 -
1513 -Reboot information after upgrade
1514 -
1515 -[[image:image-20221128111443-4.png||height="432" width="546"]]
1516 -
1517 -
1518 -Use **AT+FDR** command to reset and then use **AT+CFG** to check whether the configuration is back to normal
1519 -
1520 -[[image:image-20221128111850-5.png]]
1521 -
1522 -
1523 -After the parameters return to normal, upgrade to the version you need again
1524 -
1525 -[[image:image-20221207120601-5.png]]
1526 -
1527 -
1528 -At this point, the parameters return to normal after running AT+FDR again
1529 -
1530 -[[image:image-20221128112035-7.png]]
1531 -
1532 -
1533 -== 8.7  If you encounter the following problems, please upgrade to the latest version ==
1534 -
1535 -
1536 -~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond.
1537 -
1538 -2. Send some commands through the serial port to prompt an error (Example：AT+SMOD=1,0,1)
1539 -
1540 -
1541 1541  = 9.  Order Info =
1542 1542  
1543 1543  
... ... @@ -1559,9 +1559,6 @@
1559 1559  
1560 1560  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1561 1561  
1562 -(% style="display:none" %) (%%)
1563 -
1564 -
1565 1565  = 10.  Packing Info =
1566 1566  
1567 1567  
... ... @@ -1577,9 +1577,6 @@
1577 1577  
1578 1578  * Weight: 50g
1579 1579  
1580 -(% style="display:none" %) (%%)
1581 -
1582 -
1583 1583  = 11. Support =
1584 1584  
1585 1585  
... ... @@ -1587,9 +1587,6 @@
1587 1587  
1588 1588  * 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]].
1589 1589  
1590 -(% style="display:none" %) (%%)
1591 -
1592 -
1593 1593  = 12.  Reference =
1594 1594  
1595 1595  
... ... @@ -1598,6 +1598,3 @@
1598 1598  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1599 1599  
1600 1600  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1601 -
1602 -
1603 -)))
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