Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 81.1
edited by Edwin Chen
on 2022/10/22 00:24
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.Edwin
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  
... ... @@ -97,6 +97,8 @@
97 97  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
98 98  * Tracking: max: 38mA
99 99  
95 +
96 +
100 100  == 1.3  Features ==
101 101  
102 102  
... ... @@ -115,6 +115,8 @@
115 115  * Tri-color LED, Alarm button
116 116  * Datalog
117 117  
115 +
116 +
118 118  == 1.4  Applications ==
119 119  
120 120  
... ... @@ -121,9 +121,10 @@
121 121  * Logistics and Supply Chain Management
122 122  * Human tracking
123 123  
124 -= 2.1 Use TrackerD =
125 125  
126 126  
125 += 2.  Use TrackerD =
126 +
127 127  == 2.1 How it works? ==
128 128  
129 129  
... ... @@ -130,7 +130,6 @@
130 130  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.
131 131  
132 132  
133 -
134 134  == 2.2 Quick guide to connect to LoRaWAN server ==
135 135  
136 136  
... ... @@ -137,7 +137,7 @@
137 137  Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example. 
138 138  
139 139  
140 -[[image:1664501652064-326.png]]
139 +[[image:1664501652064-326.png||_mstalt="293306"]]
141 141  
142 142  
143 143  
... ... @@ -149,7 +149,7 @@
149 149  Each TrackerD is shipped with a sticker with the default device EUI as below:
150 150  
151 151  
152 -[[image:1664501677253-891.png]]
151 +[[image:1664501677253-891.png||_mstalt="296569"]]
153 153  
154 154  
155 155  Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot:
... ... @@ -158,14 +158,14 @@
158 158  **__Add APP EUI in the application:__**
159 159  
160 160  
161 -[[image:1664501711466-918.png]]
160 +[[image:1664501711466-918.png||_mstalt="295828"]]
162 162  
163 163  
164 164  
165 -[[image:1664501721248-725.png]]
164 +[[image:1664501721248-725.png||_mstalt="294450"]]
166 166  
167 167  
168 -[[image:1664501734705-405.png]]
167 +[[image:1664501734705-405.png||_mstalt="293306"]]
169 169  
170 170  
171 171  
... ... @@ -172,34 +172,34 @@
172 172  **__Add APP KEY and DEV EUI:__**
173 173  
174 174  
175 -[[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"]]
176 176  
177 177  
178 178  
178 +(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
179 179  
180 -(% 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"]]
181 181  
182 +[[image:1664502835802-546.png||_mstalt="295061"]]
182 182  
184 +
183 183  (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
184 184  
185 185  
186 -
187 187  == 2.3  Positioning Mode(SMOD) ==
188 188  
189 189  
190 190  Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
191 191  
192 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
193 -* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
194 -* (% 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.
195 195  
196 196  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
197 197  
198 198  
199 -
200 200  == 2.4  Uplink Payload ==
201 201  
202 -
203 203  === 2.4.1 Uplink FPORT~=5, Device Status ===
204 204  
205 205  
... ... @@ -208,11 +208,11 @@
208 208  Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
209 209  
210 210  
211 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
212 -|=(% scope="row" style="width: 108px;" %)**Size(bytes)**|=(% style="width: 82px;" %)**1**|=(% style="width: 83px;" %)**2**|=(% style="width: 94px;" %)**1**|=(% style="width: 84px;" %)**1**|=(% style="width: 44px;" %)2|=(% style="width: 63px;" %)**2**|=(% style="width: 60px;" %)1
210 +(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
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
213 213  |=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
214 214  
215 -[[image:1665301570342-765.png]]
214 +[[image:1665301570342-765.png||_mstalt="294580"]]
216 216  
217 217  
218 218  (% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
... ... @@ -253,12 +253,11 @@
253 253  Use can also get the Device Status uplink through the downlink command:
254 254  
255 255  
256 -
257 257  (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
258 258  
259 -(% border="1.5" style="background-color:#ffffcc; color:green; width:420px" %)
260 -|(% style="width:75px" %)**Size(bit)**|(% style="width:64px" %)2bits|(% style="width:137px" %)2bit|(% style="width:142px" %)4bit
261 -|(% 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
262 262  
263 263  (% style="color:blue" %)** SMOD：**
264 264  
... ... @@ -280,14 +280,17 @@
280 280  
281 281  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
282 282  
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)(%%)  
283 283  
284 284  
285 285  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
286 286  
287 -(% border="1.5" style="background-color:#ffffcc; color:green; width:417px" %)
288 -|(% 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
289 -|(% 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"]]
290 290  
290 +
291 +
291 291  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
292 292  
293 293  
... ... @@ -294,12 +294,12 @@
294 294  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,
295 295  
296 296  
297 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
298 -|=(% 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;" %)(((
299 299  **Size(bytes)**
300 -)))|(% 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" %)(((
301 301  2
302 -)))|(% style="width:87px" %)(((
303 +)))|(% style="width:30px" %)(((
303 303  2
304 304  )))
305 305  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
... ... @@ -306,7 +306,7 @@
306 306  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
307 307  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
308 308  
309 -[[image:1665301636888-168.png]]
310 +[[image:1665301636888-168.png||_mstalt="298012"]]
310 310  
311 311  
312 312  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -317,8 +317,8 @@
317 317  
318 318  ==== (% style="color:blue" %)**FLAG:**(%%) ====
319 319  
320 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
321 -|=(% 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
322 322  |=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
323 323  
324 324  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
... ... @@ -336,12 +336,12 @@
336 336  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:
337 337  
338 338  
339 -[[image:1664502116362-706.png]]
340 +[[image:1664502116362-706.png||_mstalt="293306"]]
340 340  
341 341  
342 342  3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
343 343  
344 -[[image:1664502166010-515.png]]
345 +[[image:1664502166010-515.png||_mstalt="291395"]]
345 345  
346 346  
347 347  
... ... @@ -364,6 +364,8 @@
364 364  * 3.40v ~~ 3.69v:  20% ~~ 40%
365 365  * < 3.39v:  0~~20%
366 366  
368 +
369 +
367 367  ==== (% style="color:blue" %)**MOD:**(%%) ====
368 368  
369 369  **Example: ** (0x60>>6) & 0x3f =1
... ... @@ -394,7 +394,6 @@
394 394  )))
395 395  
396 396  
397 -
398 398  ==== (% style="color:blue" %)**Hum:**(%%) ====
399 399  
400 400  0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
... ... @@ -405,7 +405,6 @@
405 405  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
406 406  
407 407  
408 -
409 409  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
410 410  
411 411  
... ... @@ -412,48 +412,47 @@
412 412  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)
413 413  
414 414  
415 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
416 -|=(% 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;" %)(((
417 417  **Size(bytes)**
418 -)))|(% 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
419 419  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
420 420  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
421 421  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
422 422  
423 423  (% class="wikigeneratedid" %)
424 -[[image:1665301687277-443.png]]
425 +[[image:1665301687277-443.png||_mstalt="296140"]]
425 425  
426 426  
427 -
428 428  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
429 429  
430 430  
431 -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.
432 432  
433 433  
434 434  (% style="color:red" %)**Note for this mode:**
435 435  
436 436  * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
437 -* 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.
438 438  * 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
439 439  
440 440  The payload is 15 bytes, as below.
441 441  
442 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
442 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
443 443  |=(% scope="row" %)(((
444 444  **Size(bytes)**
445 445  )))|4|4|2|1|1|1|1|1
446 446  |=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
447 447  
448 -[[image:image-20221009160309-2.png]]
448 +[[image:image-20221009160309-2.png||_mstalt="429312"]]
449 449  
450 450  
451 -
452 452  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
453 453  
453 +
454 454  TrackerD supports BLE scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan BLE iBeacon and find the strongest iBeacon info and uplink.
455 455  
456 -User can set [[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]] so TrackerD will only search the iBeacons which have UUID match the BLEMASK.
456 +User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
457 457  
458 458  
459 459  (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
... ... @@ -472,7 +472,7 @@
472 472  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
473 473  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
474 474  
475 -[[image:1664502425687-834.png]]
475 +[[image:1664502425687-834.png||_mstalt="296738"]]
476 476  
477 477  
478 478  * (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
... ... @@ -479,21 +479,48 @@
479 479  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
480 480  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
481 481  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
482 -* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
482 +* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
483 483  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
484 484  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
485 485  
486 -=== 2.4.6  Add Payload format in TTN V3 ===
487 487  
488 488  
489 -In TTN V3, use can add a custom payload so it shows friendly.
488 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
490 490  
490 +
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 +
491 491  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
492 492  
493 493  
494 -[[image:1664502649601-895.png]]
520 +[[image:1664502649601-895.png||_mstalt="296985"]]
495 495  
496 496  
523 +
497 497  Add the decoder from this link: 
498 498  
499 499  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
... ... @@ -500,50 +500,46 @@
500 500  
501 501  Save the change the uplink message will be parsed. As below:
502 502  
503 -[[image:1664502676891-606.png]]
530 +[[image:1664502676891-606.png||_mstalt="296673"]]
504 504  
505 505  
506 -
507 507  == 2.5 Integrate with Datacake ==
508 508  
535 +
509 509  After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
510 510  
511 511  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]]
512 512  
513 -[[image:1664502695771-538.png]]
514 514  
541 +[[image:1664502695771-538.png||_mstalt="297349"]]
515 515  
516 516  
517 517  == 2.6 Integrate with Tago ==
518 518  
519 519  
520 -
521 521  After TrackerD sends data to LoRaWAN server such as TTN, user can pass the data to Datacake and plot out, currently only support GPS plot.
522 522  
523 523  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]]
524 524  
525 525  
552 +[[image:1664502715371-321.png||_mstalt="292162"]]
526 526  
527 -[[image:1664502715371-321.png]]
528 528  
529 -
530 -
531 531  == 2.7  Datalog Feature ==
532 532  
533 533  
534 534  total 273 entries,by default,
535 535  
536 -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.
537 537  
538 538  Example use case.
539 539  
540 -[[image:image-20221009234703-2.png||height="328" width="899"]]
564 +[[image:image-20221009234703-2.png||_mstalt="429143" height="328" width="899"]]
541 541  
542 542  
543 -[[image:image-20221009234629-1.png||height="390" width="577"]]
567 +[[image:image-20221009234629-1.png||_mstalt="431145" height="390" width="577"]]
544 544  
545 545  
546 -
547 547  == 2.8 Alarm Mode ==
548 548  
549 549  
... ... @@ -558,7 +558,7 @@
558 558  
559 559  
560 560  (((
561 -Two ways to exit alarm mode:
584 +**Two ways to exit alarm mode:**
562 562  )))
563 563  
564 564  * Server sends a downlink command to exit.
... ... @@ -569,24 +569,27 @@
569 569  )))
570 570  
571 571  
572 -
573 573  == 2.9 Transport Mode ==
574 574  
575 575  
576 576  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.
577 577  
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.
578 578  
579 579  
605 +
580 580  == 2.10 LED Status ==
581 581  
582 582  
583 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
609 +(% border="1.5" style="background-color:#ffffcc; width:500px" %)
584 584  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
585 585  |(% 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
586 586  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
587 587  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
588 588  |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
589 -|(% 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
590 590  |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
591 591  |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
592 592  |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
... ... @@ -594,12 +594,14 @@
594 594  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
595 595  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
596 596  
623 +
624 +
597 597  == 2.11 Button Function ==
598 598  
599 599  
600 600  (% style="color:blue" %)**RESET button:**
601 601  
602 -[[image:1664502835802-546.png]]
630 +[[image:1664502835802-546.png||_mstalt="295061"]]
603 603  
604 604  Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server.
605 605  
... ... @@ -606,15 +606,17 @@
606 606  
607 607  (% style="color:red" %)**RED button:**
608 608  
609 -[[image:1664502854406-763.png]]
637 +[[image:1664502854406-763.png||_mstalt="295568"]]
610 610  
611 611  
612 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
613 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
614 -|(% 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"]]
615 615  |(% 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
616 616  |(% 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.
617 617  
646 +
647 +
618 618  == 2.12 USB Port Function ==
619 619  
620 620  
... ... @@ -625,6 +625,8 @@
625 625  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
626 626  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
627 627  
658 +
659 +
628 628  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
629 629  
630 630  
... ... @@ -633,7 +633,6 @@
633 633  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
634 634  
635 635  
636 -
637 637  == 3.1 Access AT Command ==
638 638  
639 639  
... ... @@ -640,25 +640,23 @@
640 640  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.
641 641  
642 642  
643 -[[image:1664502999401-486.png]]
674 +[[image:1664502999401-486.png||_mstalt="296985"]]
644 644  
645 645  
646 646  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:
647 647  
648 648  
649 -[[image:1664503022490-662.png]]
680 +[[image:1664503022490-662.png||_mstalt="293332"]]
650 650  
651 651  
652 -[[image:1664503035713-500.png]]
683 +[[image:1664503035713-500.png||_mstalt="291096"]]
653 653  
654 654  
655 -[[image:1664503047675-651.png]]
686 +[[image:1664503047675-651.png||_mstalt="295386"]]
656 656  
657 657  
658 -
659 659  == 3.2 Command Set ==
660 660  
661 -
662 662  === 3.2.1 Set Transmit Interval ===
663 663  
664 664  
... ... @@ -676,7 +676,6 @@
676 676  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
677 677  
678 678  
679 -
680 680  === 3.2.2 Set Alarm Packet transmission interval ===
681 681  
682 682  
... ... @@ -694,7 +694,6 @@
694 694  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
695 695  
696 696  
697 -
698 698  === 3.2.3 Set Transport Mode Packet transmission interval ===
699 699  
700 700  
... ... @@ -709,10 +709,9 @@
709 709  
710 710  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
711 711  
712 -(% 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
713 713  
714 714  
715 -
716 716  === 3.2.4 Exit Alarm ===
717 717  
718 718  
... ... @@ -725,7 +725,6 @@
725 725  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
726 726  
727 727  
728 -
729 729  === 3.2.5 Disable/Enable LED flash ===
730 730  
731 731  
... ... @@ -743,7 +743,6 @@
743 743  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
744 744  
745 745  
746 -
747 747  === 3.2.6 Disable/Enable Transport Mode ===
748 748  
749 749  
... ... @@ -753,15 +753,14 @@
753 753  
754 754  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
755 755  
756 -Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
780 +Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
757 757  
758 758  
759 759  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
760 760  
761 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
785 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
762 762  
763 763  
764 -
765 765  === 3.2.7 Set Positioning Mode ===
766 766  
767 767  
... ... @@ -774,32 +774,40 @@
774 774  
775 775  (% style="color:#037691" %)** aa:**
776 776  
777 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
778 -* (% style="color:red" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
779 -* (% 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.
780 780  
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 +
781 781  (% style="color:#037691" %)**bb:**
782 782  
783 783  * (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
809 +
784 784  * (% style="color:red" %)**1 :**(%%)  GPS +BAT State
785 785  
786 786  (% style="color:#037691" %)**cc:   **
787 787  
788 -* (% 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(%%))  
789 789  
790 790  (% style="color:blue" %)**Example:**
791 791  
792 - AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
793 - AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
794 - AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
820 + AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
795 795  
822 + AT+SMOD=1,1,0 ~-~->  GPS +BAT State
796 796  
797 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
824 + AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
798 798  
799 -(% 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
800 800  
801 801  
829 +* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
802 802  
831 +(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
832 +
833 +
803 803  === 3.2.8 Set MAX GPS position time ===
804 804  
805 805  
... ... @@ -806,7 +806,7 @@
806 806  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.
807 807  
808 808  
809 -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.
810 810  
811 811  
812 812  * (% style="color:blue" %)**AT Command:**
... ... @@ -821,7 +821,6 @@
821 821  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
822 822  
823 823  
824 -
825 825  === 3.2.9 Set PDOP value for GPS fix accuracy ===
826 826  
827 827  
... ... @@ -846,8 +846,9 @@
846 846  
847 847  
848 848  
849 -Disable/Enable the confirmation mode
879 +=== 3.2.10 Disable/Enable the confirmation mode ===
850 850  
881 +
851 851  * (% style="color:blue" %)**AT Command:**
852 852  
853 853  (% style="color:#037691" %)**AT+CFM=xx**
... ... @@ -855,20 +855,19 @@
855 855  
856 856  **~ Example:**
857 857  
858 - AT+ CFM=0    **~-~->   ** Disable confirmation
889 + AT+CFM=0    **~-~->   ** Disable confirmation
859 859  
860 - AT+ CFM=1    **~-~->  ** Enable confirmation
891 + AT+CFM=1    **~-~->  ** Enable confirmation
861 861  
862 862  
863 863  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
864 864  
865 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
896 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
866 866  
867 867  
899 +=== 3.2.11  Auto Send None-ACK messages ===
868 868  
869 -=== 3.2.10  Auto Send None-ACK messages ===
870 870  
871 -
872 872  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.
873 873  
874 874  
... ... @@ -884,26 +884,91 @@
884 884  
885 885  * (% style="color:blue" %)**Downlink Command: 0x34**
886 886  
887 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
917 +Example: 0x34 01  ~/~/  Same as AT+PNACKMD=1
888 888  
889 889  
890 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
920 +=== 3.2.12  Set BLEMASK to filter BLE iBeacon ===
891 891  
892 -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.
893 893  
894 -Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.
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.
895 895  
896 -(% style="color:blue" %)**AT Command:**(%%)
897 - AT+BLEMASK=123456     ~/~/ Set BLEMASK = 123456
898 - AT+BLEMASK=0  ~/~/ disable BLEMASK
925 +(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
899 899  
927 +(% style="color:blue" %)**AT Command:**
900 900  
901 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**(%%)
902 -Example:
903 -0xA5010203040506    ~/~/ Set BLEMASK to 123456
929 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
904 904  
931 + (% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
905 905  
933 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
906 906  
935 +Example: 0xB2 01 02 03 04 05 06    ~/~/ Set BLEMASK to 123456
936 +
937 +
938 +=== 3.2.13  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
939 +
940 +
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 +
907 907  = 4. Setting for Different Scenarios =
908 908  
909 909  
... ... @@ -910,7 +910,6 @@
910 910  
911 911  = 5. Upload Firmware =
912 912  
913 -
914 914  == 5.1 Firmware Change Log ==
915 915  
916 916  
... ... @@ -917,7 +917,6 @@
917 917  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
918 918  
919 919  
920 -
921 921  == 5.2 How to upgrade firmware ==
922 922  
923 923  
... ... @@ -938,40 +938,39 @@
938 938  (% style="color:blue" %)**Step4:** (%%) Run Flash Download Tool and configure chip type to ESP32
939 939  
940 940  
941 -[[image:1664503563660-578.png]]
1034 +[[image:1664503563660-578.png||_mstalt="296777"]]
942 942  
943 943  
944 -[[image:1664503574618-659.png]]
1037 +[[image:1664503574618-659.png||_mstalt="297986"]]
945 945  
946 946  
1040 +
947 947  (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
948 948  
949 949  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
950 950  
951 951  
952 -Users need to use below files:
1046 +**Users need to use below files:**
953 953  
954 954  boot_app0.bin @0e000
955 955  
956 -ESP_LORA-eeprom-class.bin @ 0x10000
1050 +US915.bin @ 0x10000(Select the bin file of the frequency band you need)
957 957  
958 958  
959 -[[image:1664503593459-435.png]]
1053 +[[image:image-20221118105220-2.png||_mstalt="426608"]]
960 960  
961 961  
962 962  
963 963  After upgrade finish, it will show finish as below:
964 964  
965 -[[image:1664503611848-385.png]]
1059 +[[image:image-20221118105402-4.png||_mstalt="427986"]]
966 966  
967 967  
968 968  
969 969  = 6. Developer Guide =
970 970  
971 -
972 972  == 6.1 Compile Source Code ==
973 973  
974 -
975 975  === 6.1.1 Set up ARDUINO compile environment ===
976 976  
977 977  
... ... @@ -980,49 +980,57 @@
980 980  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]]
981 981  
982 982  
983 -[[image:1664503635019-941.png]]
1075 +[[image:1664503635019-941.png||_mstalt="294658"]]
984 984  
985 985  
986 986  
987 987  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
988 988  
989 -[[image:1664503715811-892.png]]
1081 +[[image:1664503715811-892.png||_mstalt="295698"]]
990 990  
991 991  
1084 +(% 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.
992 992  
1086 +[[image:image-20221024105643-1.png||_mstalt="428129"]]
1087 +
1088 +**~ Figure1**
1089 +
1090 +
1091 +[[image:image-20221024105643-2.png||_mstalt="428493"]]
1092 +
1093 + **Figure2**
1094 +
1095 +
993 993  * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
994 994  
995 995  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
996 996  
997 997  
998 -[[image:1664503752288-974.png]]
1101 +[[image:1664503752288-974.png||_mstalt="298194"]]
999 999  
1000 1000  
1001 -
1002 1002  == 6.2 Source Code ==
1003 1003  
1004 1004  
1005 1005  * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:**
1006 1006  
1007 -[[image:1664503794261-827.png]]
1109 +[[image:1664503794261-827.png||_mstalt="296387"]]
1008 1008  
1009 1009  
1010 1010  
1011 1011  * (% style="color:blue" %)**Click to upload**
1012 1012  
1013 -[[image:1664503808294-336.png]]
1115 +[[image:1664503808294-336.png||_mstalt="295711"]]
1014 1014  
1015 1015  
1016 1016  
1017 1017  * (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data**
1018 1018  
1019 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1121 +[[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]]
1020 1020  
1021 1021  
1022 -
1023 1023  = 7.  FAQ =
1024 1024  
1025 -
1026 1026  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1027 1027  
1028 1028  
... ... @@ -1029,11 +1029,10 @@
1029 1029  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1030 1030  
1031 1031  
1032 -
1033 1033  == 7.2 What is the pin mapping for the USB program cable? ==
1034 1034  
1035 1035  
1036 -[[image:1664499635206-262.png]]
1135 +[[image:1664499635206-262.png||_mstalt="295360"]]
1037 1037  
1038 1038  
1039 1039  
... ... @@ -1048,45 +1048,263 @@
1048 1048  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1049 1049  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1050 1050  
1051 -= 8.  Order Info =
1052 1052  
1053 1053  
1152 +== 7.3 Notes on using different serial port tools for TrackerD ==
1153 +
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 +
1054 1054  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1055 1055  
1056 1056  (% style="color:blue" %)**XXX**(%%): The default frequency band
1057 1057  
1058 1058  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1360 +
1059 1059  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1362 +
1060 1060  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1364 +
1061 1061  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1366 +
1062 1062  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1368 +
1063 1063  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1370 +
1064 1064  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1065 1065  
1066 -= 9.  Packing Info =
1067 1067  
1068 1068  
1375 += 10.  Packing Info =
1376 +
1377 +
1069 1069  (% style="color:#037691" %)**Package Includes**:
1070 1070  
1071 1071  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1381 +
1072 1072  * USB recharge & program cable x 1
1073 1073  
1074 1074  (% style="color:#037691" %)**Dimensions and Weight**:
1075 1075  
1076 -* Device Size: 85 x 48 x 15 cm
1386 +* Device Size: 85 x 48 x 15 mm
1387 +
1077 1077  * Weight: 50g
1078 1078  
1079 -= 10. Support =
1080 1080  
1081 1081  
1392 += 11. Support =
1393 +
1394 +
1082 1082  * 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 +
1083 1083  * 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]].
1084 1084  
1085 -= 11.  Reference =
1086 1086  
1087 1087  
1401 += 12.  Reference =
1402 +
1403 +
1088 1088  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1405 +
1089 1089  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1090 -* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1091 1091  
1092 -
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-20221024105643-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +11.3 KB
Content
image-20221024105643-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +64.5 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