Last modified by Xiaoling on 2023/12/27 09:15

From version 84.8
edited by Xiaoling
on 2022/10/26 08:42
Change comment: There is no comment for this version
To version 158.1
edited by Bei Jinggeng
on 2022/11/28 11:05
Change comment: Uploaded new attachment "image-20221128110503-3.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:1664505654417-133.png]]
2 +[[image:1664505654417-133.png||_mstalt="293696"]]
3 3  
4 4  
5 5  
... ... @@ -14,7 +14,6 @@
14 14  
15 15  = 1.  Introduction =
16 16  
17 -
18 18  == 1.1  What is TrackerD ==
19 19  
20 20  
... ... @@ -32,21 +32,17 @@
32 32  (((
33 33  The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services.
34 34  )))
35 -)))
36 36  
37 37  (((
38 38  TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network.
39 -
40 -
41 41  )))
42 42  
43 -[[image:1664499921684-770.png]]
39 +[[image:1664499921684-770.png||_mstalt="298194"]]
44 44  
45 45  
46 46  (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.**
47 47  
48 48  
49 -
50 50  == 1.2 Specifications ==
51 51  
52 52  
... ... @@ -98,6 +98,7 @@
98 98  * Tracking: max: 38mA
99 99  
100 100  
96 +
101 101  == 1.3  Features ==
102 102  
103 103  
... ... @@ -117,6 +117,7 @@
117 117  * Datalog
118 118  
119 119  
116 +
120 120  == 1.4  Applications ==
121 121  
122 122  
... ... @@ -124,8 +124,8 @@
124 124  * Human tracking
125 125  
126 126  
127 -= 2.1 Use TrackerD =
128 128  
125 += 2.  Use TrackerD =
129 129  
130 130  == 2.1 How it works? ==
131 131  
... ... @@ -133,7 +133,6 @@
133 133  TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA.
134 134  
135 135  
136 -
137 137  == 2.2 Quick guide to connect to LoRaWAN server ==
138 138  
139 139  
... ... @@ -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:1664501652064-326.png]]
139 +[[image:1664501652064-326.png||_mstalt="293306"]]
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]]
151 +[[image:1664501677253-891.png||_mstalt="296569"]]
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]]
160 +[[image:1664501711466-918.png||_mstalt="295828"]]
165 165  
166 166  
167 167  
168 -[[image:1664501721248-725.png]]
164 +[[image:1664501721248-725.png||_mstalt="294450"]]
169 169  
170 170  
171 -[[image:1664501734705-405.png]]
167 +[[image:1664501734705-405.png||_mstalt="293306"]]
172 172  
173 173  
174 174  
... ... @@ -175,34 +175,34 @@
175 175  **__Add APP KEY and DEV EUI:__**
176 176  
177 177  
178 -[[image:1664501784668-703.png]]
174 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]]
179 179  
180 180  
181 181  
178 +(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
182 182  
183 -(% style="color:blue" %)**Step 2**:(%%) Power on TrackerD by using the on board switch.
180 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]]
184 184  
182 +[[image:1664502835802-546.png||_mstalt="295061"]]
185 185  
184 +
186 186  (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
187 187  
188 188  
189 -
190 190  == 2.3  Positioning Mode(SMOD) ==
191 191  
192 192  
193 193  Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
194 194  
195 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
196 -* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
197 -* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
193 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
194 +* (% style="color:#037691" %)**BLE or WiFi ONLY:            **(%%)** **Only obtain iBeacon info via BLE and uplink  or obtain wifi ssid info via WiFi and uplink. Design for Indoor tracking.
195 +* (% style="color:#037691" %)**GPS/BLE Hybrid:                        **(%%)Combination for Indoor and Outdoor tracking. Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
198 198  
199 199  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
200 200  
201 201  
202 -
203 203  == 2.4  Uplink Payload ==
204 204  
205 -
206 206  === 2.4.1 Uplink FPORT~=5, Device Status ===
207 207  
208 208  
... ... @@ -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;" %)**2**|=(% style="width: 40px;" %)1
211 +|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1
216 216  |=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
217 217  
218 -[[image:1665301570342-765.png]]
214 +[[image:1665301570342-765.png||_mstalt="294580"]]
219 219  
220 220  
221 221  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -258,9 +258,9 @@
258 258  
259 259  (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40
260 260  
261 -(% border="1.5" style="background-color:#ffffcc; color:green; width:420px" %)
262 -|(% style="width:75px" %)**Size(bit)**|(% style="width:64px" %)2bits|(% style="width:137px" %)2bit|(% style="width:142px" %)4bit
263 -|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:137px" %)GPS_Settings|(% style="width:142px" %)BLE_Settings
257 +(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
258 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
259 +|=(% 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:**
266 266  
... ... @@ -282,14 +282,17 @@
282 282  
283 283  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
284 284  
281 +(% _mstmutation="1" style="color:red" %)** 2:**  (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
285 285  
283 +
286 286  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
287 287  
288 -(% border="1.5" style="background-color:#ffffcc; color:green; width:417px" %)
289 -|(% style="width:77px" %)**Size(bit)**|(% style="width:70px" %)5 Bits|(% style="width:92px" %)1 Bit|(% style="width:48px" %)1 Bit|(% style="width:126px" %)1 Bit
290 -|(% 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"]]
286 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
287 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit
288 +|=(% style="width: 77px;" %)**Value**|(% style="width:70px" %)Reserve|(% style="width:92px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:48px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]
291 291  
292 292  
291 +
293 293  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
294 294  
295 295  
... ... @@ -296,12 +296,12 @@
296 296  Users can use **AT+SMOD=1,0,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes,
297 297  
298 298  
299 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
300 -|=(% scope="row" style="width: 50px;" %)(((
298 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
299 +|=(% scope="row" style="width: 60px;" %)(((
301 301  **Size(bytes)**
302 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
301 +)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
303 303  2
304 -)))|(% style="width:87px" %)(((
303 +)))|(% style="width:30px" %)(((
305 305  2
306 306  )))
307 307  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
... ... @@ -308,7 +308,7 @@
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]]
310 +[[image:1665301636888-168.png||_mstalt="298012"]]
312 312  
313 313  
314 314  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -319,8 +319,8 @@
319 319  
320 320  ==== (% style="color:blue" %)**FLAG:**(%%) ====
321 321  
322 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
323 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit
321 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
322 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit
324 324  |=(% 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 
... ... @@ -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]]
340 +[[image:1664502116362-706.png||_mstalt="293306"]]
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]]
345 +[[image:1664502166010-515.png||_mstalt="291395"]]
347 347  
348 348  
349 349  
... ... @@ -367,6 +367,7 @@
367 367  * < 3.39v:  0~~20%
368 368  
369 369  
369 +
370 370  ==== (% style="color:blue" %)**MOD:**(%%) ====
371 371  
372 372  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -397,7 +397,6 @@
397 397  )))
398 398  
399 399  
400 -
401 401  ==== (% style="color:blue" %)**Hum:**(%%) ====
402 402  
403 403  0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
... ... @@ -408,7 +408,6 @@
408 408  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
409 409  
410 410  
411 -
412 412  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
413 413  
414 414  
... ... @@ -415,43 +415,41 @@
415 415  The default uplink payload includes total 11 bytes (**AT+SMOD=1,1,0**). The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
416 416  
417 417  
418 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
419 -|=(% scope="row" style="width: 50px;" %)(((
416 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
417 +|=(% scope="row" style="width: 60px;" %)(((
420 420  **Size(bytes)**
421 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
419 +)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
422 422  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
423 423  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
424 424  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
425 425  
426 426  (% class="wikigeneratedid" %)
427 -[[image:1665301687277-443.png]]
425 +[[image:1665301687277-443.png||_mstalt="296140"]]
428 428  
429 429  
430 -
431 431  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
432 432  
433 433  
434 -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.
431 +Set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-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.
435 435  
436 436  
437 437  (% style="color:red" %)**Note for this mode:**
438 438  
439 439  * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
440 -* b) TrackerD will send data in (% style="color:blue" %)**CONFIRMED Mode**(%%) when PNACKMD=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
437 +* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
441 441  * c) the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes of payload. In this case (DR0 of US915/AU915), the payload on server will show NULL
442 442  
443 443  The payload is 15 bytes, as below.
444 444  
445 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
442 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
446 446  |=(% scope="row" %)(((
447 447  **Size(bytes)**
448 448  )))|4|4|2|1|1|1|1|1
449 449  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
450 450  
451 -[[image:image-20221009160309-2.png]]
448 +[[image:image-20221009160309-2.png||_mstalt="429312"]]
452 452  
453 453  
454 -
455 455  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
456 456  
457 457  
... ... @@ -476,7 +476,7 @@
476 476  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
477 477  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
478 478  
479 -[[image:1664502425687-834.png]]
475 +[[image:1664502425687-834.png||_mstalt="296738"]]
480 480  
481 481  
482 482  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -483,22 +483,48 @@
483 483  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
484 484  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
485 485  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
486 -* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
482 +* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
487 487  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
488 488  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
489 489  
490 490  
491 -=== 2.4.6  Add Payload format in TTN V3 ===
492 492  
488 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) ===
493 493  
494 -In TTN V3, use can add a custom payload so it shows friendly.
495 495  
491 +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.
492 +
493 +
494 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
495 +|=(% scope="row" style="width: 60px;" %)(((
496 +**Size(bytes)**
497 +)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
498 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
499 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
500 +)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
501 +
502 +(% class="wikigeneratedid" %)
503 +[[image:1667288597595-714.png||_mstalt="299598" height="212" width="1151"]]
504 +
505 +
506 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
507 +* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
508 +* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
509 +
510 +
511 +
512 +=== 2.4.7  Add Payload format in TTN V3 ===
513 +
514 +
515 +In TTN V3, user can add a custom payload so it shows friendly.
516 +
496 496  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
497 497  
498 498  
499 -[[image:1664502649601-895.png]]
520 +[[image:1664502649601-895.png||_mstalt="296985"]]
500 500  
501 501  
523 +
502 502  Add the decoder from this link: 
503 503  
504 504  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -505,10 +505,9 @@
505 505  
506 506  Save the change the uplink message will be parsed. As below:
507 507  
508 -[[image:1664502676891-606.png]]
530 +[[image:1664502676891-606.png||_mstalt="296673"]]
509 509  
510 510  
511 -
512 512  == 2.5 Integrate with Datacake ==
513 513  
514 514  
... ... @@ -516,8 +516,8 @@
516 516  
517 517  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]]
518 518  
519 -[[image:1664502695771-538.png]]
520 520  
541 +[[image:1664502695771-538.png||_mstalt="297349"]]
521 521  
522 522  
523 523  == 2.6 Integrate with Tago ==
... ... @@ -528,27 +528,24 @@
528 528  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]]
529 529  
530 530  
552 +[[image:1664502715371-321.png||_mstalt="292162"]]
531 531  
532 -[[image:1664502715371-321.png]]
533 533  
534 -
535 -
536 536  == 2.7  Datalog Feature ==
537 537  
538 538  
539 539  total 273 entries,by default,
540 540  
541 -User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
560 +User can set [[PNACKMD=1>>||anchor="H3.2.11A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
542 542  
543 543  Example use case.
544 544  
545 -[[image:image-20221009234703-2.png||height="328" width="899"]]
564 +[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
546 546  
547 547  
548 -[[image:image-20221009234629-1.png||height="390" width="577"]]
567 +[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
549 549  
550 550  
551 -
552 552  == 2.8 Alarm Mode ==
553 553  
554 554  
... ... @@ -563,7 +563,7 @@
563 563  
564 564  
565 565  (((
566 -Two ways to exit alarm mode:
584 +**Two ways to exit alarm mode:**
567 567  )))
568 568  
569 569  * Server sends a downlink command to exit.
... ... @@ -574,24 +574,27 @@
574 574  )))
575 575  
576 576  
577 -
578 578  == 2.9 Transport Mode ==
579 579  
580 580  
581 581  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.
582 582  
600 +* **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation.
601 +* **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic.
602 +* **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion.
583 583  
584 584  
605 +
585 585  == 2.10 LED Status ==
586 586  
587 587  
588 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
609 +(% border="1.5" style="background-color:#ffffcc; width:500px" %)
589 589  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
590 590  |(% 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
591 591  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
592 592  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
593 593  |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
594 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
615 +|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
595 595  |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
596 596  |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
597 597  |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
... ... @@ -600,12 +600,13 @@
600 600  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
601 601  
602 602  
624 +
603 603  == 2.11 Button Function ==
604 604  
605 605  
606 606  (% style="color:blue" %)**RESET button:**
607 607  
608 -[[image:1664502835802-546.png]]
630 +[[image:1664502835802-546.png||_mstalt="295061"]]
609 609  
610 610  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
611 611  
... ... @@ -612,16 +612,17 @@
612 612  
613 613  (% style="color:red" %)**RED button:**
614 614  
615 -[[image:1664502854406-763.png]]
637 +[[image:1664502854406-763.png||_mstalt="295568"]]
616 616  
617 617  
618 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
619 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
620 -|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode.  See [[Alarm Mode>>||anchor="H2.6AlarmMode"]]
640 +(% border="1" style="background-color:#ffffcc; width:510px" %)
641 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
642 +|(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode.  See [[Alarm Mode>>||anchor="H2.8AlarmMode"]]
621 621  |(% 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
622 622  |(% 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.
623 623  
624 624  
647 +
625 625  == 2.12 USB Port Function ==
626 626  
627 627  
... ... @@ -633,6 +633,7 @@
633 633  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
634 634  
635 635  
659 +
636 636  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
637 637  
638 638  
... ... @@ -641,7 +641,6 @@
641 641  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
642 642  
643 643  
644 -
645 645  == 3.1 Access AT Command ==
646 646  
647 647  
... ... @@ -648,25 +648,23 @@
648 648  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.
649 649  
650 650  
651 -[[image:1664502999401-486.png]]
674 +[[image:1664502999401-486.png||_mstalt="296985"]]
652 652  
653 653  
654 654  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:
655 655  
656 656  
657 -[[image:1664503022490-662.png]]
680 +[[image:1664503022490-662.png||_mstalt="293332"]]
658 658  
659 659  
660 -[[image:1664503035713-500.png]]
683 +[[image:1664503035713-500.png||_mstalt="291096"]]
661 661  
662 662  
663 -[[image:1664503047675-651.png]]
686 +[[image:1664503047675-651.png||_mstalt="295386"]]
664 664  
665 665  
666 -
667 667  == 3.2 Command Set ==
668 668  
669 -
670 670  === 3.2.1 Set Transmit Interval ===
671 671  
672 672  
... ... @@ -684,7 +684,6 @@
684 684  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
685 685  
686 686  
687 -
688 688  === 3.2.2 Set Alarm Packet transmission interval ===
689 689  
690 690  
... ... @@ -702,7 +702,6 @@
702 702  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
703 703  
704 704  
705 -
706 706  === 3.2.3 Set Transport Mode Packet transmission interval ===
707 707  
708 708  
... ... @@ -717,10 +717,9 @@
717 717  
718 718  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
719 719  
720 -(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
739 +(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
721 721  
722 722  
723 -
724 724  === 3.2.4 Exit Alarm ===
725 725  
726 726  
... ... @@ -733,7 +733,6 @@
733 733  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
734 734  
735 735  
736 -
737 737  === 3.2.5 Disable/Enable LED flash ===
738 738  
739 739  
... ... @@ -751,7 +751,6 @@
751 751  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
752 752  
753 753  
754 -
755 755  === 3.2.6 Disable/Enable Transport Mode ===
756 756  
757 757  
... ... @@ -761,15 +761,14 @@
761 761  
762 762  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
763 763  
764 -Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
780 +Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
765 765  
766 766  
767 767  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
768 768  
769 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
785 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
770 770  
771 771  
772 -
773 773  === 3.2.7 Set Positioning Mode ===
774 774  
775 775  
... ... @@ -782,32 +782,40 @@
782 782  
783 783  (% style="color:#037691" %)** aa:**
784 784  
785 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
786 -* (% style="color:red" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
787 -* (% style="color:red" %)**3: GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
800 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
788 788  
802 +* (% style="color:red" %)**2: BLE or WiFi ONLY:                     **(%%)Only obtain iBeacon info via BLE and uplink  or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking.
803 +
804 +* (% style="color:red" %)**3: GPS/BLE Hybrid:                       **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
805 +
789 789  (% style="color:#037691" %)**bb:**
790 790  
791 791  * (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
809 +
792 792  * (% style="color:red" %)**1 :**(%%)  GPS +BAT State
793 793  
794 794  (% style="color:#037691" %)**cc:   **
795 795  
796 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
814 +* (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 
815 +
816 +* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%))  
797 797  
798 798  (% style="color:blue" %)**Example:**
799 799  
800 - AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
801 - AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
802 - AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
820 + AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
803 803  
822 + AT+SMOD=1,1,0 ~-~->  GPS +BAT State
804 804  
805 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
824 + AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
806 806  
807 -(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
826 + AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
808 808  
809 809  
829 +* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
810 810  
831 +(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
832 +
833 +
811 811  === 3.2.8 Set MAX GPS position time ===
812 812  
813 813  
... ... @@ -814,7 +814,7 @@
814 814  Set max positioning time, default is 150 seconds. TrackerD will try to get location info within this period. If fail to get position data within this time, TrackerD will use 000000 for latitude and longitude.
815 815  
816 816  
817 -If AT+FTIME=0. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.
840 +If **AT+FTIME=0**. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink.
818 818  
819 819  
820 820  * (% style="color:blue" %)**AT Command:**
... ... @@ -829,7 +829,6 @@
829 829  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
830 830  
831 831  
832 -
833 833  === 3.2.9 Set PDOP value for GPS fix accuracy ===
834 834  
835 835  
... ... @@ -854,8 +854,9 @@
854 854  
855 855  
856 856  
857 -Disable/Enable the confirmation mode
879 +=== 3.2.10 Disable/Enable the confirmation mode ===
858 858  
881 +
859 859  * (% style="color:blue" %)**AT Command:**
860 860  
861 861  (% style="color:#037691" %)**AT+CFM=xx**
... ... @@ -863,20 +863,19 @@
863 863  
864 864  **~ Example:**
865 865  
866 - AT+ CFM=0    **~-~->   ** Disable confirmation
889 + AT+CFM=0    **~-~->   ** Disable confirmation
867 867  
868 - AT+ CFM=1    **~-~->  ** Enable confirmation
891 + AT+CFM=1    **~-~->  ** Enable confirmation
869 869  
870 870  
871 871  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
872 872  
873 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
896 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
874 874  
875 875  
899 +=== 3.2.11  Auto Send None-ACK messages ===
876 876  
877 -=== 3.2.10  Auto Send None-ACK messages ===
878 878  
879 -
880 880  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.
881 881  
882 882  
... ... @@ -892,30 +892,91 @@
892 892  
893 893  * (% style="color:blue" %)**Downlink Command: 0x34**
894 894  
895 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
917 +Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
896 896  
897 897  
920 +=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
898 898  
899 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
900 900  
923 +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.
901 901  
902 -BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. LBT1 will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
903 -
904 904  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
905 905  
906 906  (% style="color:blue" %)**AT Command:**
907 907  
908 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
929 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
909 909  
910 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
931 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
911 911  
933 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)**
912 912  
913 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**
935 +Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
914 914  
915 -Example: 0xA5010203040506    ~/~/ Set BLEMASK to 123456
916 916  
938 +=== 3.2.13  Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) ===
917 917  
918 918  
941 +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.
942 +
943 +(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
944 +
945 +(% style="color:blue" %)**AT Command:**
946 +
947 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
948 +
949 + (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
950 +
951 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)**
952 +
953 +Example: 0xB3 01 02 03 04 05 06    ~/~/ Set WiFiMASK to 123456
954 +
955 +
956 +=== 3.2.14  Disable/Enable Information printing(Since firmware 1.4.1) ===
957 +
958 +
959 +Users can use this feature to enable/disable Information printing.
960 +
961 +(% style="color:blue" %)**AT Command:**
962 +
963 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
964 +\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
965 +
966 +
967 +=== 3.2.15 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) ===
968 +
969 +
970 +The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
971 +
972 +(% style="color:blue" %)**AT Command:**
973 +
974 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
975 +
976 +
977 +(% style="color:blue" %)**Downlink Payload:0X24**
978 +
979 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
980 +
981 +
982 +=== 3.2.16 Get or Set Threshold for motion detect(Since firmware 1.4.3) ===
983 +
984 +User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event.
985 +
986 +(% style="color:blue" %)**AT Command:**
987 +
988 +(% style="color:#037691" %)**AT+PT=xx**
989 +
990 + Example:
991 +
992 + AT+PT=14    ~-~->    Set to detect car motion.
993 +
994 + AT+PT=41   ~-~->    set to detect walk motion.
995 +
996 +
997 +(% style="color:blue" %)**Downlink Payload:0xB4**(%%)
998 +0xB4 14          ~/~/  Same as AT+PT=14
999 +
1000 +
1001 +
919 919  = 4. Setting for Different Scenarios =
920 920  
921 921  
... ... @@ -922,7 +922,6 @@
922 922  
923 923  = 5. Upload Firmware =
924 924  
925 -
926 926  == 5.1 Firmware Change Log ==
927 927  
928 928  
... ... @@ -929,7 +929,6 @@
929 929  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
930 930  
931 931  
932 -
933 933  == 5.2 How to upgrade firmware ==
934 934  
935 935  
... ... @@ -950,10 +950,10 @@
950 950  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
951 951  
952 952  
953 -[[image:1664503563660-578.png]]
1034 +[[image:1664503563660-578.png||_mstalt="296777"]]
954 954  
955 955  
956 -[[image:1664503574618-659.png]]
1037 +[[image:1664503574618-659.png||_mstalt="297986"]]
957 957  
958 958  
959 959  
... ... @@ -962,29 +962,27 @@
962 962  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
963 963  
964 964  
965 -Users need to use below files:
1046 +**Users need to use below files:**
966 966  
967 967  boot_app0.bin @0e000
968 968  
969 -ESP_LORA-eeprom-class.bin @ 0x10000
1050 +US915.bin @ 0x10000(Select the bin file of the frequency band you need)
970 970  
971 971  
972 -[[image:1664503593459-435.png]]
1053 +[[image:image-20221118105220-2.png||_mstalt="426608"]]
973 973  
974 974  
975 975  
976 976  After upgrade finish, it will show finish as below:
977 977  
978 -[[image:1664503611848-385.png]]
1059 +[[image:image-20221118105402-4.png||_mstalt="427986"]]
979 979  
980 980  
981 981  
982 982  = 6. Developer Guide =
983 983  
984 -
985 985  == 6.1 Compile Source Code ==
986 986  
987 -
988 988  === 6.1.1 Set up ARDUINO compile environment ===
989 989  
990 990  
... ... @@ -993,23 +993,23 @@
993 993  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]]
994 994  
995 995  
996 -[[image:1664503635019-941.png]]
1075 +[[image:1664503635019-941.png||_mstalt="294658"]]
997 997  
998 998  
999 999  
1000 1000  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1001 1001  
1002 -[[image:1664503715811-892.png]]
1081 +[[image:1664503715811-892.png||_mstalt="295698"]]
1003 1003  
1004 1004  
1005 1005  (% 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.
1006 1006  
1007 -[[image:image-20221024105643-1.png]]
1086 +[[image:image-20221024105643-1.png||_mstalt="428129"]]
1008 1008  
1009 1009  **~ Figure1**
1010 1010  
1011 1011  
1012 -[[image:image-20221024105643-2.png]]
1091 +[[image:image-20221024105643-2.png||_mstalt="428493"]]
1013 1013  
1014 1014   **Figure2**
1015 1015  
... ... @@ -1019,34 +1019,31 @@
1019 1019  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
1020 1020  
1021 1021  
1022 -[[image:1664503752288-974.png]]
1101 +[[image:1664503752288-974.png||_mstalt="298194"]]
1023 1023  
1024 1024  
1025 -
1026 1026  == 6.2 Source Code ==
1027 1027  
1028 1028  
1029 1029  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1030 1030  
1031 -[[image:1664503794261-827.png]]
1109 +[[image:1664503794261-827.png||_mstalt="296387"]]
1032 1032  
1033 1033  
1034 1034  
1035 1035  * (% style="color:blue" %)**Click to upload**
1036 1036  
1037 -[[image:1664503808294-336.png]]
1115 +[[image:1664503808294-336.png||_mstalt="295711"]]
1038 1038  
1039 1039  
1040 1040  
1041 1041  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1042 1042  
1043 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1121 +[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1044 1044  
1045 1045  
1046 -
1047 1047  = 7.  FAQ =
1048 1048  
1049 -
1050 1050  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1051 1051  
1052 1052  
... ... @@ -1053,11 +1053,10 @@
1053 1053  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1054 1054  
1055 1055  
1056 -
1057 1057  == 7.2 What is the pin mapping for the USB program cable? ==
1058 1058  
1059 1059  
1060 -[[image:1664499635206-262.png]]
1135 +[[image:1664499635206-262.png||_mstalt="295360"]]
1061 1061  
1062 1062  
1063 1063  
... ... @@ -1073,48 +1073,262 @@
1073 1073  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1074 1074  
1075 1075  
1076 -= 8.  Order Info =
1077 1077  
1152 +== 7.3 Notes on using different serial port tools for TrackerD ==
1078 1078  
1154 +=== 7.3.1  Serial port utility ===
1155 +
1156 +
1157 +Serial port utility requires you to automatically add data streams.
1158 +
1159 +Need to adjust the data stream to RTS/CTS on physical restart.
1160 +
1161 +(% class="wikigeneratedid" %)
1162 +[[image:image-20221102140621-1.png||_mstalt="425672"]]
1163 +
1164 +
1165 +
1166 +When using AT commands, the data flow needs to be adjusted to XON/XOFF
1167 +
1168 +[[image:image-20221102140638-2.png||_mstalt="428727"]]
1169 +
1170 +
1171 +=== 7.3.2  SecureCRT ===
1172 +
1173 +
1174 +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.
1175 +
1176 +
1177 +[[image:image-20221102140704-3.png||_mstalt="427076"]]
1178 +
1179 +
1180 +[[image:image-20221102140712-4.png||_mstalt="427089"]]
1181 +
1182 +
1183 +=== 7.3.3  PUTTY ===
1184 +
1185 +
1186 +[[image:image-20221102140748-5.png||_mstalt="430456"]]
1187 +
1188 +
1189 +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.
1190 +
1191 +
1192 +[[image:image-20221102140801-6.png||_mstalt="427466"]]
1193 +
1194 +
1195 +== 7.4 How to modify source code to compile different frequency band bin file? ==
1196 +
1197 +
1198 +(% class="box infomessage" %)
1199 +(((
1200 +(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1201 +See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1202 +)))
1203 +
1204 +**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1205 +
1206 +
1207 +[[image:image-20221116111844-1.png||_mstalt="428688" height="227" width="782"]]
1208 +
1209 +
1210 +
1211 +**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1212 +
1213 +
1214 +[[image:image-20221116111844-2.png||_mstalt="429052" height="262" width="781"]]
1215 +
1216 +
1217 +
1218 +**3. Compile the AS923_JP band, please refer to the intention shown**
1219 +
1220 +
1221 +[[image:image-20221116111844-3.png||_mstalt="429416" height="338" width="746"]]
1222 +
1223 +
1224 +
1225 +**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.**
1226 +
1227 +
1228 +[[image:image-20221116111844-4.png||_mstalt="429780" height="641" width="739"]]
1229 +
1230 +
1231 +[[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]]
1232 +
1233 +
1234 += 8  Trouble Shooting =
1235 +
1236 +== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1237 +
1238 +
1239 +(((
1240 +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
1241 +)))
1242 +
1243 +
1244 +== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1245 +
1246 +
1247 +(((
1248 +ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode.
1249 +)))
1250 +
1251 +
1252 +== 8.3  Problem after Upgrading Firmware ==
1253 +
1254 +=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===
1255 +
1256 +
1257 +**Error Output**
1258 +
1259 +
1260 +[[image:image-20221122100004-4.png||_mstalt="424606"]]
1261 +
1262 +
1263 +(((
1264 +Some partition is missed during upgrade, please upgrade below four files as example:
1265 +
1266 +[[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1267 +)))
1268 +
1269 +
1270 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1271 +
1272 +
1273 +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
1274 +
1275 +
1276 +=== 8.3.3 "flash read err" after upgrade firmware ===
1277 +
1278 +
1279 +Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1280 +
1281 +
1282 +[[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]]
1283 +
1284 +
1285 +User need to upgrade again with below four files to solve this issue.
1286 +
1287 + [[image:image-20221122100004-2.png||_mstalt="423878" height="619" width="389"]]
1288 +
1289 + **Figure 2**
1290 +
1291 +
1292 +=== 8.3.4  "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1293 +
1294 +
1295 +User might erase the entire flash include keys and default settings which cause this issue.
1296 +
1297 +After the upgrade is completed, enter **AT+CFG** as shown in the figure below.
1298 +
1299 +
1300 +[[image:image-20221122100004-3.png||_mstalt="424242"]]
1301 +
1302 +
1303 +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.
1304 +
1305 +After AT+FDR. please set
1306 +
1307 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7**
1308 +
1309 +* (% _mstmutation="1" style="color:blue" %)**AT+FTIME=180000**
1310 +
1311 +**Example:**
1312 +
1313 +AT+PDOP=7.00
1314 +
1315 +AT+FTIME=180
1316 +
1317 +AT+DEUI=70B3D57ED0053981  
1318 +
1319 +AT+APPEUI=D23345667BCBCCAF
1320 +
1321 +AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1322 +
1323 +AT+DADDR=260b4dce    ( no need for OTAA)
1324 +
1325 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1326 +
1327 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1328 +
1329 +
1330 +== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1331 +
1332 +
1333 +Please download version 1.4.2 again
1334 +
1335 +
1336 +== 8.5  How to deal with unsuccessful GPS positioning? ==
1337 +
1338 +
1339 +1) Make Sure the device is in Open Area where can see the sky.
1340 +
1341 +2)  Set PDOP to a higher value.
1342 +
1343 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.)
1344 +
1345 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces)
1346 +
1347 +* (% _mstmutation="1" style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments)
1348 +
1349 +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
1350 +
1351 +
1352 += 9.  Order Info =
1353 +
1354 +
1079 1079  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1080 1080  
1081 1081  (% style="color:blue" %)**XXX**(%%): The default frequency band
1082 1082  
1083 1083  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1360 +
1084 1084  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1362 +
1085 1085  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1364 +
1086 1086  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1366 +
1087 1087  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1368 +
1088 1088  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1370 +
1089 1089  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1090 1090  
1091 1091  
1092 -= 9.  Packing Info =
1093 1093  
1375 += 10.  Packing Info =
1094 1094  
1377 +
1095 1095  (% style="color:#037691" %)**Package Includes**:
1096 1096  
1097 1097  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1381 +
1098 1098  * USB recharge & program cable x 1
1099 1099  
1100 1100  (% style="color:#037691" %)**Dimensions and Weight**:
1101 1101  
1102 -* Device Size: 85 x 48 x 15 cm
1386 +* Device Size: 85 x 48 x 15 mm
1387 +
1103 1103  * Weight: 50g
1104 1104  
1105 1105  
1106 -= 10. Support =
1107 1107  
1392 += 11. Support =
1108 1108  
1394 +
1109 1109  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1396 +
1110 1110  * 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]].
1111 1111  
1112 1112  
1113 -= 11.  Reference =
1114 1114  
1401 += 12.  Reference =
1115 1115  
1403 +
1116 1116  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1405 +
1117 1117  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1118 -* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1119 1119  
1120 -
1408 +* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1409 +)))
1667288597595-714.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +27.9 KB
Content
image-20221102140621-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +46.1 KB
Content
image-20221102140638-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +40.8 KB
Content
image-20221102140704-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +15.5 KB
Content
image-20221102140712-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +73.2 KB
Content
image-20221102140748-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +56.0 KB
Content
image-20221102140801-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +21.0 KB
Content
image-20221107145243-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +107.3 KB
Content
image-20221116111844-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +15.8 KB
Content
image-20221116111844-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +32.6 KB
Content
image-20221116111844-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +37.0 KB
Content
image-20221116111844-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +96.8 KB
Content
image-20221116111844-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +78.0 KB
Content
image-20221118104359-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +38.0 KB
Content
image-20221118105220-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +40.2 KB
Content
image-20221118105249-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +40.2 KB
Content
image-20221118105402-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +43.7 KB
Content
image-20221122100004-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +18.0 KB
Content
image-20221122100004-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +127.2 KB
Content
image-20221122100004-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +12.5 KB
Content
image-20221122100004-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20221128102938-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +41.3 KB
Content
image-20221128103040-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +19.2 KB
Content
image-20221128110503-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +45.6 KB
Content