Skip to Content
Last modified by Bei Jinggeng on 2025/08/01 17:45
From version 74.8
edited by Xiaoling
on 2022/10/11 17:08
Change comment: There is no comment for this version
To version 143.2
edited by Xiaoling
on 2022/11/22 10:54
Change comment: There is no comment for this version

Summary

Details

Page properties
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  
... ... @@ -127,9 +127,8 @@
127 127  
128 128  
129 129  
130 -= 2.1 Use TrackerD =
128 += 2.  Use TrackerD =
131 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]]
177 +[[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  
181 +(% 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.
183 +(% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png]]
187 187  
185 +[[image:1664502835802-546.png]]
188 188  
187 +
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.
196 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
197 +* (% 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.
198 +* (% 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  
210 +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
212 +
213 +(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
214 +|=(% 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,43 +256,41 @@
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
258 +(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
264 264  
265 -(% style="color:blue" %)**SMOD：**
260 +(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
261 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
262 +|=(% 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
264 +(% style="color:blue" %)** SMOD：**
268 268  
269 -(% style="color:red" %)**2 :** (%%) BLE ONLY
266 +(% style="color:red" %)** 1 :** (%%) GPS ONLY
270 270  
271 -(% style="color:red" %)**3 :**  (%%) GPS/BLE Hybrid
268 +(% style="color:red" %)** 2 :** (%%) BLE ONLY
272 272  
270 +(% 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
273 +(% 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
275 +(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
279 279  
277 +(% 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
280 +(% style="color:blue" %)** BLE_Settings:**
284 284  
285 -TrackerD Status:  0x02
282 +(% 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
284 +(% 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
287 +(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
294 294  
295 -(% style="color:red" %)**2 : **(%%) Datalog Enable/Disable
289 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
290 +|=(% 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
291 +|=(% 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 298  
... ... @@ -299,15 +299,15 @@
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.
298 +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;" %)(((
301 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
302 +|=(% 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" %)(((
304 +)))|(% 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" %)(((
306 +)))|(% 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" %)(((
... ... @@ -327,8 +327,8 @@
327 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
326 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %)
327 +|=(% 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,7 +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 343  (% style="color:red" %)**Important note:**
344 344  
345 345  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.
... ... @@ -358,12 +358,12 @@
358 358  
359 359  ==== (% style="color:blue" %)**Alarm:**(%%) ====
360 360  
361 -Example:  0x4B & 0x40 >> 6 = 0x01
356 +**Example: ** 0x4B & 0x40 >> 6 = 0x01
362 362  
363 363  
364 364  ==== (% style="color:blue" %)**BAT:**(%%) ====
365 365  
366 -Example: 0x4B45 & 0x3FFF ⇒ 2885 (mV).
361 +**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
367 367  
368 368  (((
369 369  The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
... ... @@ -379,12 +379,12 @@
379 379  
380 380  ==== (% style="color:blue" %)**MOD:**(%%) ====
381 381  
382 -mod = (0x60>>6)& 0x3f;
377 +**Example: ** (0x60>>6) & 0x3f =1
383 383  
384 384  **Set the format of GPS data uplink link：**
385 385  
386 386  (% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
387 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
382 +(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
388 388  
389 389  
390 390  **Set the format of BLE data uplink link：**
... ... @@ -394,7 +394,7 @@
394 394  
395 395  ==== (% style="color:blue" %)**LON:**(%%) ====
396 396  
397 -lon=(0x60>>5) & 0x01;
392 +**Example:** (0x60>>5) & 0x01=1.
398 398  
399 399  Enable/Disable LED activity for uplink
400 400  
... ... @@ -417,17 +417,16 @@
417 417  011A =if (0x011A & 0x8000 = 1 ):  value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree//
418 418  
419 419  
420 -
421 421  === 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
422 422  
423 423  
424 -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)
418 +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)
425 425  
426 426  
427 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
428 -|=(% scope="row" style="width: 50px;" %)(((
421 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
422 +|=(% scope="row" style="width: 60px;" %)(((
429 429  **Size(bytes)**
430 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
424 +)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
431 431  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
432 432  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
433 433  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
... ... @@ -436,21 +436,21 @@
436 436  [[image:1665301687277-443.png]]
437 437  
438 438  
439 -
440 440  === 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
441 441  
442 442  
443 -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.
436 +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.
444 444  
445 445  
446 446  (% style="color:red" %)**Note for this mode:**
447 447  
448 448  * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
449 -* 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.
442 +* 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.
443 +* 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
450 450  
451 451  The payload is 15 bytes, as below.
452 452  
453 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
447 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
454 454  |=(% scope="row" %)(((
455 455  **Size(bytes)**
456 456  )))|4|4|2|1|1|1|1|1
... ... @@ -459,10 +459,14 @@
459 459  [[image:image-20221009160309-2.png]]
460 460  
461 461  
462 -
463 463  === 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
464 464  
465 465  
459 +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.
460 +
461 +User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
462 +
463 +
466 466  (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
467 467  |=(% scope="row" style="width: 60px;" %)(((
468 468  **Size(bytes)**
... ... @@ -482,21 +482,45 @@
482 482  [[image:1664502425687-834.png]]
483 483  
484 484  
485 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
483 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
486 486  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
487 487  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
488 488  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
489 -* (% style="color:#037691" %)**MINOR:**  (%%)The MAJOR from the strongest iBeacon.
487 +* (% style="color:#037691" %)**MINOR:**  (%%)The MINOR from the strongest iBeacon.
490 490  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
491 491  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
492 492  
493 493  
494 494  
495 -=== 2.4.6  Add Payload format in TTN V3 ===
493 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
496 496  
497 497  
498 -In TTN V3, use can add a custom payload so it shows friendly.
496 +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.
499 499  
498 +
499 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
500 +|=(% scope="row" style="width: 60px;" %)(((
501 +**Size(bytes)**
502 +)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
503 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
504 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
505 +)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
506 +
507 +(% class="wikigeneratedid" %)
508 +[[image:1667288597595-714.png||height="212" width="1151"]]
509 +
510 +
511 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
512 +* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
513 +* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
514 +
515 +
516 +
517 +=== 2.4.7  Add Payload format in TTN V3 ===
518 +
519 +
520 +In TTN V3, user can add a custom payload so it shows friendly.
521 +
500 500  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
501 501  
502 502  
... ... @@ -503,52 +503,44 @@
503 503  [[image:1664502649601-895.png]]
504 504  
505 505  
506 -Add the decoder from this link:
507 507  
529 +Add the decoder from this link: 
508 508  
531 +[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
532 +
509 509  Save the change the uplink message will be parsed. As below:
510 510  
511 511  [[image:1664502676891-606.png]]
512 512  
513 513  
514 -
515 515  == 2.5 Integrate with Datacake ==
516 516  
517 517  
518 -(((
519 519  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.
520 -)))
521 521  
522 -(((
523 523  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]]
524 -)))
525 525  
526 526  
527 527  [[image:1664502695771-538.png]]
528 528  
529 529  
530 -
531 531  == 2.6 Integrate with Tago ==
532 532  
533 533  
534 -(((
535 -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.
536 -)))
552 +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.
537 537  
538 -(((
539 539  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]]
540 -)))
541 541  
542 542  
543 543  [[image:1664502715371-321.png]]
544 544  
545 545  
546 -
547 547  == 2.7  Datalog Feature ==
548 548  
549 549  
550 -total 273 entries,by default disable
563 +total 273 entries,by default,
551 551  
565 +User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
552 552  
553 553  Example use case.
554 554  
... ... @@ -558,7 +558,6 @@
558 558  [[image:image-20221009234629-1.png||height="390" width="577"]]
559 559  
560 560  
561 -
562 562  == 2.8 Alarm Mode ==
563 563  
564 564  
... ... @@ -568,15 +568,15 @@
568 568  
569 569  
570 570  (((
571 -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.
584 +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.
572 572  )))
573 573  
574 574  
575 575  (((
576 -Two ways to exit alarm mode:
589 +**Two ways to exit alarm mode:**
577 577  )))
578 578  
579 -* Server send a downlink command to exit.
592 +* Server sends a downlink command to exit.
580 580  * User fast press the RED button 10 times.
581 581  
582 582  (((
... ... @@ -584,7 +584,6 @@
584 584  )))
585 585  
586 586  
587 -
588 588  == 2.9 Transport Mode ==
589 589  
590 590  
... ... @@ -591,17 +591,16 @@
591 591  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.
592 592  
593 593  
594 -
595 595  == 2.10 LED Status ==
596 596  
597 597  
598 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
609 +(% border="1.5" style="background-color:#ffffcc; width:500px" %)
599 599  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
600 600  |(% 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
601 601  |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes
602 602  |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A
603 603  |(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes
604 -|(% 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
605 605  |(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes
606 606  |(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes
607 607  |(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes
... ... @@ -611,7 +611,6 @@
611 611  
612 612  
613 613  
614 -
615 615  == 2.11 Button Function ==
616 616  
617 617  
... ... @@ -627,15 +627,14 @@
627 627  [[image:1664502854406-763.png]]
628 628  
629 629  
630 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
631 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
632 -|(% 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"]]
633 633  |(% 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
634 634  |(% 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.
635 635  
636 636  
637 637  
638 -
639 639  == 2.12 USB Port Function ==
640 640  
641 641  
... ... @@ -656,7 +656,6 @@
656 656  LoRaWAN Downlink instruction for different platforms:  [[IoT LoRaWAN Server>>doc:Main.WebHome]]
657 657  
658 658  
659 -
660 660  == 3.1 Access AT Command ==
661 661  
662 662  
... ... @@ -672,11 +672,9 @@
672 672  [[image:1664503022490-662.png]]
673 673  
674 674  
675 -
676 676  [[image:1664503035713-500.png]]
677 677  
678 678  
679 -
680 680  [[image:1664503047675-651.png]]
681 681  
682 682  
... ... @@ -683,7 +683,6 @@
683 683  
684 684  == 3.2 Command Set ==
685 685  
686 -
687 687  === 3.2.1 Set Transmit Interval ===
688 688  
689 689  
... ... @@ -701,7 +701,6 @@
701 701  (% style="color:#037691" %)**0x01 00 01 2C**  (%%) ~/~/  Same as AT+TDC=300000
702 702  
703 703  
704 -
705 705  === 3.2.2 Set Alarm Packet transmission interval ===
706 706  
707 707  
... ... @@ -719,7 +719,6 @@
719 719  (% style="color:#037691" %)**0xB1 00 00 3C ** (%%) ~/~/  Same as AT+ATDC=60000
720 720  
721 721  
722 -
723 723  === 3.2.3 Set Transport Mode Packet transmission interval ===
724 724  
725 725  
... ... @@ -734,10 +734,9 @@
734 734  
735 735  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
736 736  
737 -(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
740 +(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
738 738  
739 739  
740 -
741 741  === 3.2.4 Exit Alarm ===
742 742  
743 743  
... ... @@ -750,7 +750,6 @@
750 750  (% style="color:#037691" %)**0x02 01**    (%%) ~/~/  Exit Alarm Mode
751 751  
752 752  
753 -
754 754  === 3.2.5 Disable/Enable LED flash ===
755 755  
756 756  
... ... @@ -768,7 +768,6 @@
768 768  (% style="color:#037691" %)**0xAE 00 ** (%%) ~/~/  Same as AT+LON=0
769 769  
770 770  
771 -
772 772  === 3.2.6 Disable/Enable Transport Mode ===
773 773  
774 774  
... ... @@ -778,19 +778,18 @@
778 778  
779 779  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
780 780  
781 -Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
781 +Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
782 782  
783 783  
784 784  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
785 785  
786 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
786 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
787 787  
788 788  
789 -
790 790  === 3.2.7 Set Positioning Mode ===
791 791  
792 792  
793 -SMOD define the how TrackerD scan and uplink data:
792 +SMOD define how TrackerD scan and uplink data:
794 794  
795 795  
796 796  * (% style="color:blue" %)**AT Command:**
... ... @@ -799,32 +799,40 @@
799 799  
800 800  (% style="color:#037691" %)** aa:**
801 801  
802 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
803 -* (% style="color:red" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
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.
801 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
805 805  
803 +* (% 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.
804 +
805 +* (% 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.
806 +
806 806  (% style="color:#037691" %)**bb:**
807 807  
808 808  * (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
810 +
809 809  * (% style="color:red" %)**1 :**(%%)  GPS +BAT State
810 810  
811 811  (% style="color:#037691" %)**cc:   **
812 812  
813 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
815 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
816 +
817 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
814 814  
815 815  (% style="color:blue" %)**Example:**
816 816  
817 - AT+ SMOD =1,0 ,0 ~-~->  GPS+ BAT+ State+Tem&Hum
818 - AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
819 - AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
821 + AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
820 820  
823 + AT+SMOD=1,1,0 ~-~->  GPS +BAT State
821 821  
822 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
825 + AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
823 823  
824 -(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
827 + AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
825 825  
826 826  
830 +* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
827 827  
832 +(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
833 +
834 +
828 828  === 3.2.8 Set MAX GPS position time ===
829 829  
830 830  
... ... @@ -831,7 +831,7 @@
831 831  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.
832 832  
833 833  
834 -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.
841 +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.
835 835  
836 836  
837 837  * (% style="color:blue" %)**AT Command:**
... ... @@ -846,7 +846,6 @@
846 846  (% style="color:#037691" %)**0xAA 00 96 ** (%%) ~/~/  Set AT+FTIME=150
847 847  
848 848  
849 -
850 850  === 3.2.9 Set PDOP value for GPS fix accuracy ===
851 851  
852 852  
... ... @@ -871,7 +871,7 @@
871 871  
872 872  
873 873  
874 -Disable/Enable the confirmation mode
880 +**Disable/Enable the confirmation mode**
875 875  
876 876  * (% style="color:blue" %)**AT Command:**
877 877  
... ... @@ -880,17 +880,16 @@
880 880  
881 881  **~ Example:**
882 882  
883 - AT+ CFM=0    **~-~->   ** Disable confirmation
889 + AT+CFM=0    **~-~->   ** Disable confirmation
884 884  
885 - AT+ CFM=1    **~-~->  ** Enable confirmation
891 + AT+CFM=1    **~-~->  ** Enable confirmation
886 886  
887 887  
888 888  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
889 889  
890 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
896 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
891 891  
892 892  
893 -
894 894  === 3.2.10  Auto Send None-ACK messages ===
895 895  
896 896  
... ... @@ -912,6 +912,68 @@
912 912  Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
913 913  
914 914  
920 +=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
921 +
922 +
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.
924 +
925 +(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
926 +
927 +(% style="color:blue" %)**AT Command:**
928 +
929 + (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
930 +
931 + (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
932 +
933 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
934 +
935 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
936 +
937 +
938 +=== 3.2.12  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 + (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
948 +
949 + (% 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: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
954 +
955 +
956 +=== 3.2.13 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.14 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 +
915 915  = 4. Setting for Different Scenarios =
916 916  
917 917  
... ... @@ -918,7 +918,6 @@
918 918  
919 919  = 5. Upload Firmware =
920 920  
921 -
922 922  == 5.1 Firmware Change Log ==
923 923  
924 924  
... ... @@ -925,7 +925,6 @@
925 925  **[[See this link>>url:https://github.com/dragino/TrackerD]]**
926 926  
927 927  
928 -
929 929  == 5.2 How to upgrade firmware ==
930 930  
931 931  
... ... @@ -952,34 +952,33 @@
952 952  [[image:1664503574618-659.png]]
953 953  
954 954  
1020 +
955 955  (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
956 956  
957 957  [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
958 958  
959 959  
960 -Users need to use below files:
1026 +**Users need to use below files:**
961 961  
962 962  boot_app0.bin @0e000
963 963  
964 -ESP_LORA-eeprom-class.bin @ 0x10000
1030 +US915.bin @ 0x10000(Select the bin file of the frequency band you need)
965 965  
966 966  
967 -[[image:1664503593459-435.png]]
1033 +[[image:image-20221118105220-2.png]]
968 968  
969 969  
970 970  
971 971  After upgrade finish, it will show finish as below:
972 972  
973 -[[image:1664503611848-385.png]]
1039 +[[image:image-20221118105402-4.png]]
974 974  
975 975  
976 976  
977 977  = 6. Developer Guide =
978 978  
979 -
980 980  == 6.1 Compile Source Code ==
981 981  
982 -
983 983  === 6.1.1 Set up ARDUINO compile environment ===
984 984  
985 985  
... ... @@ -997,7 +997,18 @@
997 997  [[image:1664503715811-892.png]]
998 998  
999 999  
1064 +(% 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.
1000 1000  
1066 +[[image:image-20221024105643-1.png]]
1067 +
1068 +**~ Figure1**
1069 +
1070 +
1071 +[[image:image-20221024105643-2.png]]
1072 +
1073 + **Figure2**
1074 +
1075 +
1001 1001  * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
1002 1002  
1003 1003  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
... ... @@ -1006,7 +1006,6 @@
1006 1006  [[image:1664503752288-974.png]]
1007 1007  
1008 1008  
1009 -
1010 1010  == 6.2 Source Code ==
1011 1011  
1012 1012  
... ... @@ -1027,10 +1027,8 @@
1027 1027  [[image:1664503824081-592.png]] [[image:1664503831430-500.png]]
1028 1028  
1029 1029  
1030 -
1031 1031  = 7.  FAQ =
1032 1032  
1033 -
1034 1034  == 7.1 How to change the LoRa Frequency Bands/Region? ==
1035 1035  
1036 1036  
... ... @@ -1037,7 +1037,6 @@
1037 1037  User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.
1038 1038  
1039 1039  
1040 -
1041 1041  == 7.2 What is the pin mapping for the USB program cable? ==
1042 1042  
1043 1043  
... ... @@ -1058,52 +1058,243 @@
1058 1058  
1059 1059  
1060 1060  
1132 +== 7.3 Notes on using different serial port tools for TrackerD ==
1061 1061  
1062 -= 8.  Order Info =
1134 +=== 7.3.1  Serial port utility ===
1063 1063  
1064 1064  
1137 +Serial port utility requires you to automatically add data streams.
1138 +
1139 +Need to adjust the data stream to RTS/CTS on physical restart.
1140 +
1141 +(% class="wikigeneratedid" %)
1142 +[[image:image-20221102140621-1.png]]
1143 +
1144 +
1145 +
1146 +When using AT commands, the data flow needs to be adjusted to XON/XOFF
1147 +
1148 +[[image:image-20221102140638-2.png]]
1149 +
1150 +
1151 +=== 7.3.2  SecureCRT ===
1152 +
1153 +
1154 +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.
1155 +
1156 +
1157 +[[image:image-20221102140704-3.png]]
1158 +
1159 +
1160 +[[image:image-20221102140712-4.png]]
1161 +
1162 +
1163 +=== 7.3.3  PUTTY ===
1164 +
1165 +
1166 +[[image:image-20221102140748-5.png]]
1167 +
1168 +
1169 +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.
1170 +
1171 +
1172 +[[image:image-20221102140801-6.png]]
1173 +
1174 +
1175 +== 7.4 How to modify source code to compile different frequency band bin file? ==
1176 +
1177 +
1178 +(% class="box infomessage" %)
1179 +(((
1180 +(% style="color:red" %)**Important**(%%): Developer **MUST** follow the Arduino Environment Instruction exactly include change the SPI pin mappings.
1181 +See : [[**Set Up Arduino Compile Environment for TrackerD**. >>||anchor="H6.1.1SetupARDUINOcompileenvironment"]]
1182 +)))
1183 +
1184 +**~1. When compiling the frequency band, you need to find LMIC_PROJECT_CONFIG.H file.**
1185 +
1186 +
1187 +[[image:image-20221116111844-1.png||height="227" width="782"]]
1188 +
1189 +
1190 +
1191 +**2. Open LMIC_PROJECT_CONFIG.H, find the corresponding macro definition and open it(AS923_2,AS923_3,AS923_4 except).**
1192 +
1193 +
1194 +[[image:image-20221116111844-2.png||height="262" width="781"]]
1195 +
1196 +
1197 +
1198 +**3. Compile the AS923_JP band, please refer to the intention shown**
1199 +
1200 +
1201 +[[image:image-20221116111844-3.png||height="338" width="746"]]
1202 +
1203 +
1204 +
1205 +**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.**
1206 +
1207 +
1208 +[[image:image-20221116111844-4.png||height="641" width="739"]]
1209 +
1210 +
1211 +[[image:image-20221116111844-5.png||height="551" width="708"]]
1212 +
1213 +
1214 += 8  Trouble Shooting =
1215 +
1216 +== 8.1  TDC is changed to 4294947296 and cause no uplink. ==
1217 +
1218 +
1219 +(((
1220 +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
1221 +)))
1222 +
1223 +
1224 +== 8.2  Device not able get AT Command or show output after wake up from deep sleep mode ==
1225 +
1226 +
1227 +(((
1228 +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.
1229 +)))
1230 +
1231 +
1232 +== 8.3  Problem after Upgrading Firmware ==
1233 +
1234 +=== 8.3.1 Continue Restart after upgrading ===
1235 +
1236 +
1237 +(((
1238 +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
1239 +)))
1240 +
1241 +
1242 +[[image:image-20221118105249-3.png]]
1243 +
1244 +
1245 +=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===
1246 +
1247 +
1248 +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
1249 +
1250 +
1251 +
1252 +==== 8.3.2.1 If there is a situation in Figure 1,and a new partition file and bootloader file needs to be added. Please refer to the operation steps in Figure 2 ====
1253 +
1254 +
1255 +[[image:image-20221122100004-1.png||height="497" width="534"]]
1256 +
1257 + ** Figure 1  **
1258 +
1259 +
1260 + [[image:image-20221122100004-2.png||height="619" width="389"]]
1261 +
1262 + **Figure 2**
1263 +
1264 +
1265 +
1266 +After the upgrade is completed, enter AT+CFG as shown in the figure below.
1267 +
1268 +
1269 +[[image:image-20221122100004-3.png]]
1270 +
1271 +Please AT+FDR, and then enter the following instructions by the information on the label
1272 +
1273 +AT+DEUI=70B3D57ED0053981
1274 +
1275 +AT+APPEUI=D23345667BCBCCAF
1276 +
1277 +AT+APPKEY=F402A1A7A350445A7CD2DEA95511BFA1
1278 +
1279 +AT+DADDR=260b4dce
1280 +
1281 +AT+NWKSKEY=71cb7672441f573a53d4f34d307fc61d
1282 +
1283 +AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559
1284 +
1285 +
1286 +
1287 +==== 8.3.2.2 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 ====
1288 +
1289 +
1290 +[[image:image-20221122100004-4.png]]
1291 +
1292 +
1293 +== 8.4  When positioning, it will restart or the PDOP setting is unsuccessful ==
1294 +
1295 +
1296 +Please download version 1.4.2 again
1297 +
1298 +
1299 +== 8.5  How to deal with unsuccessful GPS positioning? ==
1300 +
1301 +
1302 +1） Make Sure the device is in Open Area where can see the sky.
1303 +
1304 +2)  Set PDOP to a higher value.
1305 +
1306 +* (% style="color:blue" %)**AT+PDOP=2 **(%%)(can be positioned precisely.）
1307 +
1308 +* (% style="color:blue" %)**AT+PDOP=7 **(%%)(Quickly locate in open spaces）
1309 +
1310 +* (% style="color:blue" %)**AT+PDOP=14.7** (%%)(Positioning can be acquired in complex environments）
1311 +
1312 +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
1313 +
1314 +
1315 += 9.  Order Info =
1316 +
1317 +
1065 1065  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1066 1066  
1067 1067  (% style="color:blue" %)**XXX**(%%): The default frequency band
1068 1068  
1069 1069  * (% style="color:red" %)**EU433**(%%): Default frequency band EU433
1323 +
1070 1070  * (% style="color:red" %)**EU868**(%%): Default frequency band EU868
1325 +
1071 1071  * (% style="color:red" %)**IN865**(%%): Default frequency band IN865
1327 +
1072 1072  * (% style="color:red" %)**KR920**(%%): Default frequency band KR920
1329 +
1073 1073  * (% style="color:red" %)**AS923**(%%): Default frequency band AS923
1331 +
1074 1074  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1333 +
1075 1075  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1076 1076  
1077 1077  
1078 1078  
1079 -= 9.  Packing Info =
1338 += 10.  Packing Info =
1080 1080  
1081 1081  
1082 1082  (% style="color:#037691" %)**Package Includes**:
1083 1083  
1084 1084  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1344 +
1085 1085  * USB recharge & program cable x 1
1086 1086  
1087 1087  (% style="color:#037691" %)**Dimensions and Weight**:
1088 1088  
1089 -* Device Size: 85 x 48 x 15 cm
1349 +* Device Size: 85 x 48 x 15 mm
1350 +
1090 1090  * Weight: 50g
1091 1091  
1092 1092  
1093 1093  
1094 -= 10. Support =
1355 += 11. Support =
1095 1095  
1096 1096  
1097 1097  * 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.
1359 +
1098 1098  * 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]].
1099 1099  
1100 1100  
1101 1101  
1102 -= 11.  Reference =
1364 += 12.  Reference =
1103 1103  
1104 1104  
1105 1105  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1368 +
1106 1106  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1107 -* [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1108 1108  
1109 -
1371 +* [[**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