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