Skip to Content
Last modified by Bei Jinggeng on 2025/08/01 17:45
From version 74.7
edited by Xiaoling
on 2022/10/11 16:29
Change comment: There is no comment for this version
To version 144.1
edited by Edwin Chen
on 2022/11/22 12:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -14,7 +14,6 @@
14 14  
15 15  = 1.  Introduction =
16 16  
17 -
18 18  == 1.1  What is TrackerD ==
19 19  
20 20  
... ... @@ -46,7 +46,6 @@
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,7 +98,6 @@
98 98  * Tracking: max: 38mA
99 99  
100 100  
101 -
102 102  == 1.3  Features ==
103 103  
104 104  
... ... @@ -118,7 +118,6 @@
118 118  * Datalog
119 119  
120 120  
121 -
122 122  == 1.4  Applications ==
123 123  
124 124  
... ... @@ -126,10 +126,8 @@
126 126  * Human tracking
127 127  
128 128  
125 += 2.  Use TrackerD =
129 129  
130 -= 2.1 Use TrackerD =
131 -
132 -
133 133  == 2.1 How it works? ==
134 134  
135 135  
... ... @@ -136,7 +136,6 @@
136 136  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.
137 137  
138 138  
139 -
140 140  == 2.2 Quick guide to connect to LoRaWAN server ==
141 141  
142 142  
... ... @@ -178,42 +178,44 @@
178 178  **__Add APP KEY and DEV EUI:__**
179 179  
180 180  
181 -[[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||alt="1654671889112-678.png"]]
182 182  
183 183  
184 184  
178 +(% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device.
185 185  
186 -(% 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]]
187 187  
182 +[[image:1664502835802-546.png]]
188 188  
184 +
189 189  (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
190 190  
191 191  
192 -
193 193  == 2.3  Positioning Mode(SMOD) ==
194 194  
195 195  
196 196  Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
197 197  
198 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
199 -* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
200 -* (% 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.
201 201  
202 202  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
203 203  
204 204  
205 -
206 206  == 2.4  Uplink Payload ==
207 207  
208 -
209 209  === 2.4.1 Uplink FPORT~=5, Device Status ===
210 210  
211 211  
212 212  Uplink the device configures with FPORT=5. Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours.
213 213  
207 +Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
214 214  
215 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
216 -|=(% 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
209 +
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
217 217  |=(% 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
218 218  
219 219  [[image:1665301570342-765.png]]
... ... @@ -256,58 +256,55 @@
256 256  
257 257  Use can also get the Device Status uplink through the downlink command:
258 258  
259 -TrackerD Model：0x40
260 260  
261 -(% border="1.5" style="background-color:#ffffcc; color:green; width:314px" %)
262 -|(% style="width:75px" %)**Size(bit)**|(% style="width:64px" %)2bits|(% style="width:88px" %)2bit|(% style="width:84px" %)4bit
263 -|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:88px" %)GPS_MOD|(% style="width:84px" %)BLE_MOD
255 +(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
264 264  
265 -(% style="color:blue" %)**SMOD：**
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
266 266  
267 -(% style="color:red" %)**1 :** (%%) GPS ONLY
261 +(% style="color:blue" %)** SMOD：**
268 268  
269 -(% style="color:red" %)**2 :** (%%) BLE ONLY
263 +(% style="color:red" %)** 1 :** (%%) GPS ONLY
270 270  
271 -(% style="color:red" %)**3 :**  (%%) GPS/BLE Hybrid
265 +(% style="color:red" %)** 2 :** (%%) BLE ONLY
272 272  
267 +(% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
273 273  
274 -(% style="color:blue" %)**GPS MOD:**
275 275  
276 -(% style="color:red" %)**0 : ** (%%) Enable uploading on-board Temperature and humidity values
270 +(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
277 277  
278 -(% style="color:red" %)**1 :** (%%) Disable uploading on-board Temperature and humidity values
272 +(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
279 279  
274 +(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values
280 280  
281 -(% style="color:blue" %)**BLE MOD:**
282 282  
283 -(% style="color:red" %)**1: ** (%%) BLE Positioning with Strongest iBeacon
277 +(% style="color:blue" %)** BLE_Settings:**
284 284  
285 -TrackerD Status:  0x02
279 +(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
286 286  
287 -(% border="1.5" style="background-color:#ffffcc; color:green; width:345px" %)
288 -|(% style="width:77px" %)**Size(bit)**|(% style="width:91px" %)1bits|(% style="width:48px" %)1bit|(% style="width:126px" %)1bit
289 -|(% style="width:77px" %)**Value**|(% style="width:91px" %)PNACKMD|(% style="width:48px" %)LON|(% style="width:126px" %)Transport** **Mode
281 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
290 290  
291 -(% style="color:red" %)**0 : **(%%) Transport Mode
292 292  
293 -(% style="color:red" %)**1 :  **(%%) AT+LON
284 +(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
294 294  
295 -(% style="color:red" %)**2 : **(%%) Datalog Enable/Disable
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"]]
296 296  
297 297  
298 -
299 299  === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
300 300  
301 301  
302 -User can use **AT+SMOD=1,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes, please note that 15 bytes won't work on DR0 on US915/AU915 frequency band.
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,
303 303  
304 304  
305 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
306 -|=(% scope="row" style="width: 50px;" %)(((
297 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
298 +|=(% scope="row" style="width: 60px;" %)(((
307 307  **Size(bytes)**
308 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
300 +)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
309 309  2
310 -)))|(% style="width:87px" %)(((
302 +)))|(% style="width:30px" %)(((
311 311  2
312 312  )))
313 313  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
... ... @@ -324,11 +324,10 @@
324 324  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
325 325  
326 326  
327 -
328 328  ==== (% style="color:blue" %)**FLAG:**(%%) ====
329 329  
330 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
331 -|=(% 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
332 332  |=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
333 333  
334 334  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
... ... @@ -339,8 +339,6 @@
339 339  * Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
340 340  * Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
341 341  
342 -
343 -
344 344  (% style="color:red" %)**Important note:**
345 345  
346 346  1.  When power is low (<2.84v), GPS won't be able to get location info and GPS feature will be disabled and the location field will be filled with 0x0FFFFFFF, 0x0FFFFFFF.
... ... @@ -359,12 +359,12 @@
359 359  
360 360  ==== (% style="color:blue" %)**Alarm:**(%%) ====
361 361  
362 -Example:  0x4B & 0x40 >> 6 = 0x01
351 +**Example: ** 0x4B & 0x40 >> 6 = 0x01
363 363  
364 364  
365 365  ==== (% style="color:blue" %)**BAT:**(%%) ====
366 366  
367 -Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
356 +**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
368 368  
369 369  (((
370 370  The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
... ... @@ -377,13 +377,14 @@
377 377  * < 3.39v:  0~~20%
378 378  
379 379  
380 -
381 381  ==== (% style="color:blue" %)**MOD:**(%%) ====
382 382  
371 +**Example: ** (0x60>>6) & 0x3f =1
372 +
383 383  **Set the format of GPS data uplink link：**
384 384  
385 385  (% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
386 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
376 +(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
387 387  
388 388  
389 389  **Set the format of BLE data uplink link：**
... ... @@ -393,6 +393,8 @@
393 393  
394 394  ==== (% style="color:blue" %)**LON:**(%%) ====
395 395  
386 +**Example:** (0x60>>5) & 0x01=1.
387 +
396 396  Enable/Disable LED activity for uplink
397 397  
398 398  (((
... ... @@ -414,17 +414,16 @@
414 414  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
415 415  
416 416  
417 -
418 418  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
419 419  
420 420  
421 -The default uplink payload includes totally 11 bytes. The payload is the first 11 bytes of Uplink FPORT=2, real-time GNSS positioning, (remove the temp and humidity)
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)
422 422  
423 423  
424 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
425 -|=(% scope="row" style="width: 50px;" %)(((
415 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
416 +|=(% scope="row" style="width: 60px;" %)(((
426 426  **Size(bytes)**
427 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
418 +)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
428 428  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
429 429  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
430 430  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
... ... @@ -433,21 +433,21 @@
433 433  [[image:1665301687277-443.png]]
434 434  
435 435  
436 -
437 437  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
438 438  
439 439  
440 -Set [[PNACKMD=1>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/#H4.13AutoSendNone-ACKmessages]], and TrackerD will wait for ACK for every uplink, when there is no LoRaWAN network, TrackerD will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
430 +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.
441 441  
442 442  
443 443  (% style="color:red" %)**Note for this mode:**
444 444  
445 445  * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
446 -* 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.
436 +* 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.
437 +* 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
447 447  
448 448  The payload is 15 bytes, as below.
449 449  
450 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
441 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
451 451  |=(% scope="row" %)(((
452 452  **Size(bytes)**
453 453  )))|4|4|2|1|1|1|1|1
... ... @@ -456,10 +456,14 @@
456 456  [[image:image-20221009160309-2.png]]
457 457  
458 458  
459 -
460 460  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
461 461  
462 462  
453 +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.
454 +
455 +User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
456 +
457 +
463 463  (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
464 464  |=(% scope="row" style="width: 60px;" %)(((
465 465  **Size(bytes)**
... ... @@ -479,21 +479,43 @@
479 479  [[image:1664502425687-834.png]]
480 480  
481 481  
482 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
477 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
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.
481 +* (% 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  
486 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
491 491  
492 -=== 2.4.6  Add Payload format in TTN V3 ===
493 493  
489 +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.
494 494  
495 -In TTN V3, use can add a custom payload so it shows friendly.
496 496  
492 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
493 +|=(% scope="row" style="width: 60px;" %)(((
494 +**Size(bytes)**
495 +)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
496 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
497 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
498 +)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
499 +
500 +(% class="wikigeneratedid" %)
501 +[[image:1667288597595-714.png||height="212" width="1151"]]
502 +
503 +
504 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
505 +* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
506 +* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
507 +
508 +
509 +=== 2.4.7  Add Payload format in TTN V3 ===
510 +
511 +
512 +In TTN V3, user can add a custom payload so it shows friendly.
513 +
497 497  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
498 498  
499 499  
... ... @@ -500,52 +500,44 @@
500 500  [[image:1664502649601-895.png]]
501 501  
502 502  
503 -Add the decoder from this link:
504 504  
521 +Add the decoder from this link: 
505 505  
523 +[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
524 +
506 506  Save the change the uplink message will be parsed. As below:
507 507  
508 508  [[image:1664502676891-606.png]]
509 509  
510 510  
511 -
512 512  == 2.5 Integrate with Datacake ==
513 513  
514 514  
515 -(((
516 516  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.
517 -)))
518 518  
519 -(((
520 520  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]]
521 -)))
522 522  
523 523  
524 524  [[image:1664502695771-538.png]]
525 525  
526 526  
527 -
528 528  == 2.6 Integrate with Tago ==
529 529  
530 530  
531 -(((
532 -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.
533 -)))
544 +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.
534 534  
535 -(((
536 536  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]]
537 -)))
538 538  
539 539  
540 540  [[image:1664502715371-321.png]]
541 541  
542 542  
543 -
544 544  == 2.7  Datalog Feature ==
545 545  
546 546  
547 -total 273 entries,by default disable
555 +total 273 entries,by default,
548 548  
557 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
549 549  
550 550  Example use case.
551 551  
... ... @@ -555,7 +555,6 @@
555 555  [[image:image-20221009234629-1.png||height="390" width="577"]]
556 556  
557 557  
558 -
559 559  == 2.8 Alarm Mode ==
560 560  
561 561  
... ... @@ -565,15 +565,15 @@
565 565  
566 566  
567 567  (((
568 -Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exit alert mode.
576 +Once enter Alarm mode, the (% style="color:green" %)**GREEN LED**(%%) will flash 3 times, the buzzer will alarm for 5 seconds, then TrackerD will immediately send a packet without location info and then send a data packet with GPS positioning information. After that, the device will send 60 packets at 1-minute intervals. The Alarm flag in the payload will be set for the next 60 packets unless exits alert mode.
569 569  )))
570 570  
571 571  
572 572  (((
573 -Two ways to exit alarm mode:
581 +**Two ways to exit alarm mode:**
574 574  )))
575 575  
576 -* Server send a downlink command to exit.
584 +* Server sends a downlink command to exit.
577 577  * User fast press the RED button 10 times.
578 578  
579 579  (((
... ... @@ -581,7 +581,6 @@
581 581  )))
582 582  
583 583  
584 -
585 585  == 2.9 Transport Mode ==
586 586  
587 587  
... ... @@ -588,17 +588,16 @@
588 588  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.
589 589  
590 590  
591 -
592 592  == 2.10 LED Status ==
593 593  
594 594  
595 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
601 +(% border="1.5" style="background-color:#ffffcc; width:500px" %)
596 596  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
597 597  |(% 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
598 598  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
599 599  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
600 600  |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
601 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes
607 +|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
602 602  |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
603 603  |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
604 604  |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
... ... @@ -607,8 +607,6 @@
607 607  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
608 608  
609 609  
610 -
611 -
612 612  == 2.11 Button Function ==
613 613  
614 614  
... ... @@ -624,15 +624,13 @@
624 624  [[image:1664502854406-763.png]]
625 625  
626 626  
627 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
628 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
629 -|(% 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"]]
631 +(% border="1" style="background-color:#ffffcc; width:510px" %)
632 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
633 +|(% 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"]]
630 630  |(% 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
631 631  |(% 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.
632 632  
633 633  
634 -
635 -
636 636  == 2.12 USB Port Function ==
637 637  
638 638  
... ... @@ -644,8 +644,6 @@
644 644  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
645 645  
646 646  
647 -
648 -
649 649  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
650 650  
651 651  
... ... @@ -654,7 +654,6 @@
654 654  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
655 655  
656 656  
657 -
658 658  == 3.1 Access AT Command ==
659 659  
660 660  
... ... @@ -670,11 +670,9 @@
670 670  [[image:1664503022490-662.png]]
671 671  
672 672  
673 -
674 674  [[image:1664503035713-500.png]]
675 675  
676 676  
677 -
678 678  [[image:1664503047675-651.png]]
679 679  
680 680  
... ... @@ -681,7 +681,6 @@
681 681  
682 682  == 3.2 Command Set ==
683 683  
684 -
685 685  === 3.2.1 Set Transmit Interval ===
686 686  
687 687  
... ... @@ -699,7 +699,6 @@
699 699  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
700 700  
701 701  
702 -
703 703  === 3.2.2 Set Alarm Packet transmission interval ===
704 704  
705 705  
... ... @@ -717,7 +717,6 @@
717 717  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
718 718  
719 719  
720 -
721 721  === 3.2.3 Set Transport Mode Packet transmission interval ===
722 722  
723 723  
... ... @@ -732,10 +732,9 @@
732 732  
733 733  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
734 734  
735 -(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
729 +(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
736 736  
737 737  
738 -
739 739  === 3.2.4 Exit Alarm ===
740 740  
741 741  
... ... @@ -748,7 +748,6 @@
748 748  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
749 749  
750 750  
751 -
752 752  === 3.2.5 Disable/Enable LED flash ===
753 753  
754 754  
... ... @@ -766,7 +766,6 @@
766 766  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
767 767  
768 768  
769 -
770 770  === 3.2.6 Disable/Enable Transport Mode ===
771 771  
772 772  
... ... @@ -776,19 +776,18 @@
776 776  
777 777  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
778 778  
779 -Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
770 +Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
780 780  
781 781  
782 782  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
783 783  
784 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
775 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
785 785  
786 786  
787 -
788 788  === 3.2.7 Set Positioning Mode ===
789 789  
790 790  
791 -SMOD define the how TrackerD scan and uplink data:
781 +SMOD define how TrackerD scan and uplink data:
792 792  
793 793  
794 794  * (% style="color:blue" %)**AT Command:**
... ... @@ -797,32 +797,40 @@
797 797  
798 798  (% style="color:#037691" %)** aa:**
799 799  
800 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
801 -* (% style="color:red" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
802 -* (% 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.
790 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
803 803  
792 +* (% 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.
793 +
794 +* (% 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.
795 +
804 804  (% style="color:#037691" %)**bb:**
805 805  
806 806  * (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
799 +
807 807  * (% style="color:red" %)**1 :**(%%)  GPS +BAT State
808 808  
809 809  (% style="color:#037691" %)**cc:   **
810 810  
811 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
804 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
805 +
806 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
812 812  
813 813  (% style="color:blue" %)**Example:**
814 814  
815 - AT+ SMOD =1,0 ,0 ~-~->  GPS+ BAT+ State+Tem&Hum
816 - AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
817 - AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
810 + AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
818 818  
812 + AT+SMOD=1,1,0 ~-~->  GPS +BAT State
819 819  
820 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
814 + AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
821 821  
822 -(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
816 + AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
823 823  
824 824  
819 +* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
825 825  
821 +(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
822 +
823 +
826 826  === 3.2.8 Set MAX GPS position time ===
827 827  
828 828  
... ... @@ -829,7 +829,7 @@
829 829  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.
830 830  
831 831  
832 -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.
830 +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.
833 833  
834 834  
835 835  * (% style="color:blue" %)**AT Command:**
... ... @@ -844,7 +844,6 @@
844 844  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
845 845  
846 846  
847 -
848 848  === 3.2.9 Set PDOP value for GPS fix accuracy ===
849 849  
850 850  
... ... @@ -869,7 +869,7 @@
869 869  
870 870  
871 871  
872 -Disable/Enable the confirmation mode
869 +**Disable/Enable the confirmation mode**
873 873  
874 874  * (% style="color:blue" %)**AT Command:**
875 875  
... ... @@ -878,17 +878,16 @@
878 878  
879 879  **~ Example:**
880 880  
881 - AT+ CFM=0    **~-~->   ** Disable confirmation
878 + AT+CFM=0    **~-~->   ** Disable confirmation
882 882  
883 - AT+ CFM=1    **~-~->  ** Enable confirmation
880 + AT+CFM=1    **~-~->  ** Enable confirmation
884 884  
885 885  
886 886  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
887 887  
888 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
885 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
889 889  
890 890  
891 -
892 892  === 3.2.10  Auto Send None-ACK messages ===
893 893  
894 894  
... ... @@ -910,6 +910,68 @@
910 910  Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
911 911  
912 912  
909 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
910 +
911 +
912 +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.
913 +
914 +(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
915 +
916 +(% style="color:blue" %)**AT Command:**
917 +
918 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
919 +
920 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
921 +
922 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
923 +
924 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
925 +
926 +
927 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
928 +
929 +
930 +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.
931 +
932 +(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
933 +
934 +(% style="color:blue" %)**AT Command:**
935 +
936 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
937 +
938 + (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
939 +
940 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
941 +
942 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
943 +
944 +
945 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
946 +
947 +
948 +Users can use this feature to enable/disable Information printing.
949 +
950 +(% style="color:blue" %)**AT Command:**
951 +
952 +(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
953 +\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
954 +
955 +
956 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
957 +
958 +
959 +The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
960 +
961 +(% style="color:blue" %)**AT Command:**
962 +
963 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
964 +
965 +
966 +(% style="color:blue" %)**Downlink Payload:0X24**
967 +
968 +Example: 0x24 01 ~/~/ Same as AT+CHE=1
969 +
970 +
913 913  = 4. Setting for Different Scenarios =
914 914  
915 915  
... ... @@ -916,7 +916,6 @@
916 916  
917 917  = 5. Upload Firmware =
918 918  
919 -
920 920  == 5.1 Firmware Change Log ==
921 921  
922 922  
... ... @@ -923,7 +923,6 @@
923 923  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
924 924  
925 925  
926 -
927 927  == 5.2 How to upgrade firmware ==
928 928  
929 929  
... ... @@ -950,34 +950,33 @@
950 950  [[image:1664503574618-659.png]]
951 951  
952 952  
1009 +
953 953  (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
954 954  
955 955  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
956 956  
957 957  
958 -Users need to use below files:
1015 +**Users need to use below files:**
959 959  
960 960  boot_app0.bin @0e000
961 961  
962 -ESP_LORA-eeprom-class.bin @ 0x10000
1019 +US915.bin @ 0x10000(Select the bin file of the frequency band you need)
963 963  
964 964  
965 -[[image:1664503593459-435.png]]
1022 +[[image:image-20221118105220-2.png]]
966 966  
967 967  
968 968  
969 969  After upgrade finish, it will show finish as below:
970 970  
971 -[[image:1664503611848-385.png]]
1028 +[[image:image-20221118105402-4.png]]
972 972  
973 973  
974 974  
975 975  = 6. Developer Guide =
976 976  
977 -
978 978  == 6.1 Compile Source Code ==
979 979  
980 -
981 981  === 6.1.1 Set up ARDUINO compile environment ===
982 982  
983 983  
... ... @@ -995,7 +995,18 @@
995 995  [[image:1664503715811-892.png]]
996 996  
997 997  
1053 +(% 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.
998 998  
1055 +[[image:image-20221024105643-1.png]]
1056 +
1057 +**~ Figure1**
1058 +
1059 +
1060 +[[image:image-20221024105643-2.png]]
1061 +
1062 + **Figure2**
1063 +
1064 +
999 999  * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
1000 1000  
1001 1001  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
... ... @@ -1004,7 +1004,6 @@
1004 1004  [[image:1664503752288-974.png]]
1005 1005  
1006 1006  
1007 -
1008 1008  == 6.2 Source Code ==
1009 1009  
1010 1010  
... ... @@ -1025,10 +1025,8 @@
1025 1025  [[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1026 1026  
1027 1027  
1028 -
1029 1029  = 7.  FAQ =
1030 1030  
1031 -
1032 1032  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1033 1033  
1034 1034  
... ... @@ -1035,7 +1035,6 @@
1035 1035  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1036 1036  
1037 1037  
1038 -
1039 1039  == 7.2 What is the pin mapping for the USB program cable? ==
1040 1040  
1041 1041  
... ... @@ -1055,53 +1055,245 @@
1055 1055  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1056 1056  
1057 1057  
1120 +== 7.3 Notes on using different serial port tools for TrackerD ==
1058 1058  
1122 +=== 7.3.1  Serial port utility ===
1059 1059  
1060 -= 8.  Order Info =
1061 1061  
1125 +Serial port utility requires you to automatically add data streams.
1062 1062  
1127 +Need to adjust the data stream to RTS/CTS on physical restart.
1128 +
1129 +(% class="wikigeneratedid" %)
1130 +[[image:image-20221102140621-1.png]]
1131 +
1132 +
1133 +
1134 +When using AT commands, the data flow needs to be adjusted to XON/XOFF
1135 +
1136 +[[image:image-20221102140638-2.png]]
1137 +
1138 +
1139 +=== 7.3.2  SecureCRT ===
1140 +
1141 +
1142 +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.
1143 +
1144 +
1145 +[[image:image-20221102140704-3.png]]
1146 +
1147 +
1148 +[[image:image-20221102140712-4.png]]
1149 +
1150 +
1151 +=== 7.3.3  PUTTY ===
1152 +
1153 +
1154 +[[image:image-20221102140748-5.png]]
1155 +
1156 +
1157 +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.
1158 +
1159 +
1160 +[[image:image-20221102140801-6.png]]
1161 +
1162 +
1163 +== 7.4 How to modify source code to compile different frequency band bin file? ==
1164 +
1165 +
1166 +(% class="box infomessage" %)
1167 +(((
1168 +(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1169 +See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1170 +)))
1171 +
1172 +**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1173 +
1174 +
1175 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1176 +
1177 +
1178 +
1179 +**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1180 +
1181 +
1182 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1183 +
1184 +
1185 +
1186 +**3. Compile the AS923_JP band, please refer to the intention shown**
1187 +
1188 +
1189 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1190 +
1191 +
1192 +
1193 +**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.**
1194 +
1195 +
1196 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1197 +
1198 +
1199 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1200 +
1201 +
1202 += 8  Trouble Shooting =
1203 +
1204 +== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1205 +
1206 +
1207 +(((
1208 +Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1209 +)))
1210 +
1211 +
1212 +== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1213 +
1214 +
1215 +(((
1216 +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.
1217 +)))
1218 +
1219 +
1220 +== 8.3  Problem after Upgrading Firmware ==
1221 +
1222 +=== 8.3.1 Continue Restart after upgrading ===
1223 +
1224 +
1225 +(((
1226 +If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
1227 +)))
1228 +
1229 +
1230 +[[image:image-20221118105249-3.png]]
1231 +
1232 +
1233 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1234 +
1235 +
1236 +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
1237 +
1238 +
1239 +=== 8.3.3 "flash read err" after upgrade firmware ===
1240 +
1241 +Error shows below, user might erase the entire flash include u-boot partition which cause this issue.
1242 +
1243 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1244 +
1245 +
1246 +User need to upgrade again with below four files to solve this issue.
1247 +
1248 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1249 +
1250 + **Figure 2**
1251 +
1252 +
1253 +=== 8.3.3 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===
1254 +
1255 +User might erase the entire flash include keys and default settings which cause this issue.
1256 +
1257 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1258 +
1259 +[[image:image-20221122100004-3.png]]
1260 +
1261 +Please **AT+FDR** which will reset all settings to factory settings. , and then input the following keys by the information on the label.
1262 +
1263 +
1264 +Example:
1265 +
1266 +AT+DEUI=70B3D57ED0053981  
1267 +
1268 +AT+APPEUI=D23345667BCBCCAF
1269 +
1270 +AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1271 +
1272 +AT+DADDR=260b4dce    ( no need for OTAA)
1273 +
1274 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d  ( no need for OTAA)
1275 +
1276 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559   ( no need for OTAA)
1277 +
1278 +
1279 +
1280 +==== 8.3.4  If there is a situation in Figure 1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 ====
1281 +
1282 +
1283 +[[image:image-20221122100004-4.png]]
1284 +
1285 +
1286 +== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1287 +
1288 +
1289 +Please download version 1.4.2 again
1290 +
1291 +
1292 +== 8.5  How to deal with unsuccessful GPS positioning? ==
1293 +
1294 +
1295 +1） Make Sure the device is in Open Area where can see the sky.
1296 +
1297 +2)  Set PDOP to a higher value.
1298 +
1299 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1300 +
1301 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1302 +
1303 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1304 +
1305 +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
1306 +
1307 +
1308 += 9.  Order Info =
1309 +
1310 +
1063 1063  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1064 1064  
1065 1065  (% style="color:blue" %)**XXX**(%%): The default frequency band
1066 1066  
1067 1067  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1316 +
1068 1068  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1318 +
1069 1069  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1320 +
1070 1070  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1322 +
1071 1071  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1324 +
1072 1072  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1326 +
1073 1073  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1074 1074  
1075 1075  
1330 += 10.  Packing Info =
1076 1076  
1077 -= 9.  Packing Info =
1078 1078  
1079 -
1080 1080  (% style="color:#037691" %)**Package Includes**:
1081 1081  
1082 1082  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1336 +
1083 1083  * USB recharge & program cable x 1
1084 1084  
1085 1085  (% style="color:#037691" %)**Dimensions and Weight**:
1086 1086  
1087 -* Device Size: 85 x 48 x 15 cm
1341 +* Device Size: 85 x 48 x 15 mm
1342 +
1088 1088  * Weight: 50g
1089 1089  
1090 1090  
1346 += 11. Support =
1091 1091  
1092 -= 10. Support =
1093 1093  
1094 -
1095 1095  * 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.
1350 +
1096 1096  * 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]].
1097 1097  
1098 1098  
1354 += 12.  Reference =
1099 1099  
1100 -= 11.  Reference =
1101 1101  
1102 -
1103 1103  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1358 +
1104 1104  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1105 -* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1106 1106  
1107 -
1361 +* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
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