Skip to Content
Last modified by Xiaoling on 2025/04/27 16:48
From version 84.9
edited by Xiaoling
on 2022/10/26 08:46
Change comment: There is no comment for this version
To version 51.29
edited by Xiaoling
on 2022/09/30 15:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -61,11 +61,13 @@
61 61  * EEPROM: 520 KB
62 62  * Clock Speed: 32Mhz
63 63  
64 +
64 64  (% style="color:blue" %)**Common DC Characteristics:**
65 65  
66 66  * Supply Voltage: 5V via USB port or Internal li-on battery
67 67  * Operating Temperature: -40 ~~ 60°C
68 68  
70 +
69 69  (% style="color:blue" %)**LoRa Spec:**
70 70  
71 71  * Frequency Range,
... ... @@ -87,10 +87,12 @@
87 87  * Packet engine up to 256 bytes with CRC.
88 88  * LoRaWAN 1.0.3 Specification
89 89  
92 +
90 90  (% style="color:blue" %)**Battery:**
91 91  
92 92  * 1000mA Li-on Battery power (for model TrackerD)
93 93  
97 +
94 94  (% style="color:blue" %)**Power Consumption**
95 95  
96 96  * Sleeping Mode: 200uA
... ... @@ -97,6 +97,8 @@
97 97  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
98 98  * Tracking: max: 38mA
99 99  
104 +
105 +
100 100  == 1.3  Features ==
101 101  
102 102  
... ... @@ -103,7 +103,7 @@
103 103  * LoRaWAN 1.0.3 Class A
104 104  * ESP32 PICO D4
105 105  * SX1276/78 Wireless Chip
106 -* Arduino IDE Compatible
112 +** Arduino IDE Compatible
107 107  * Open source hardware / software
108 108  * Regular/ Real-time GPS,BLE,WIFI tracking
109 109  * Built-in3 axis accelerometer (LIS3DH)
... ... @@ -115,6 +115,8 @@
115 115  * Tri-color LED, Alarm button
116 116  * Datalog
117 117  
124 +
125 +
118 118  == 1.4  Applications ==
119 119  
120 120  
... ... @@ -121,6 +121,8 @@
121 121  * Logistics and Supply Chain Management
122 122  * Human tracking
123 123  
132 +
133 +
124 124  = 2.1 Use TrackerD =
125 125  
126 126  
... ... @@ -183,128 +183,42 @@
183 183  (% style="color:blue" %)**Step 3:**(%%) TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server.
184 184  
185 185  
196 +(% style="color:blue" %)**Positioning Mode(SMOD):**
186 186  
187 -== 2.3  Positioning Mode(SMOD) ==
198 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get GPS location info.
199 +* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE. Design for Indoor tracking.
200 +* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.
188 188  
202 +User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
189 189  
190 -Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
191 191  
192 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
193 -* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
194 -* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
195 195  
196 -Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
206 +== 2.3 Uplink Payload ==
197 197  
198 198  
209 +=== 2.3.1 Uplink FPORT~=5, Device Status ===
199 199  
200 -== 2.4  Uplink Payload ==
201 201  
202 202  
203 -=== 2.4.1 Uplink FPORT~=5, Device Status ===
213 +=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning ===
204 204  
205 205  
206 -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.
216 +The default uplink payload includes totally 11 bytes. (User can use AT+MOD=0 to enable the Temperature and humidity sensor to hum/tem info from accelerometer. When accelerometer info is enable, total payload will be 15 bytes, please note 15 bytes won't work on DR0 on US915/AU915 frequency band. )
207 207  
208 -Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
209 209  
210 -
211 -(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %)
212 -|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1
213 -|=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status
214 -
215 -[[image:1665301570342-765.png]]
216 -
217 -
218 -(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
219 -
220 -(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13
221 -
222 -(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version
223 -
224 -(% style="color:#037691" %)**Frequency Band**:
225 -
226 -*0x01: EU868
227 -
228 -*0x02: US915
229 -
230 -*0x03: IN865
231 -
232 -*0x04: AU915
233 -
234 -*0x05: KZ865
235 -
236 -*0x06: RU864
237 -
238 -*0x07: AS923
239 -
240 -*0x08: AS923-1
241 -
242 -*0x09: AS923-2
243 -
244 -*0x0a: AS923-3
245 -
246 -Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
247 -
248 -(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
249 -
250 -
251 -(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
252 -
253 -Use can also get the Device Status uplink through the downlink command:
254 -
255 -
256 -(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
257 -
258 -(% border="1.5" style="background-color:#ffffcc; color:green; width:350px" %)
259 -|=(% scope="row" style="width: 75px;" %)**Size(bit)**|(% style="width:64px" %)2bits|(% style="width:104px" %)2bit|(% style="width:103px" %)4bit
260 -|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
261 -
262 -(% style="color:blue" %)** SMOD：**
263 -
264 -(% style="color:red" %)** 1 :** (%%) GPS ONLY
265 -
266 -(% style="color:red" %)** 2 :** (%%) BLE ONLY
267 -
268 -(% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
269 -
270 -
271 -(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
272 -
273 -(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
274 -
275 -(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values
276 -
277 -
278 -(% style="color:blue" %)** BLE_Settings:**
279 -
280 -(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
281 -
282 -
283 -(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
284 -
285 -(% border="1.5" style="background-color:#ffffcc; color:green; width:417px" %)
286 -|=(% scope="row" style="width: 77px;" %)**Size(bit)**|(% style="width:70px" %)5 Bits|(% style="width:92px" %)1 Bit|(% style="width:48px" %)1 Bit|(% style="width:126px" %)1 Bit
287 -|=(% 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"]]
288 -
289 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
290 -
291 -
292 -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,
293 -
294 -
295 295  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
296 296  |=(% scope="row" style="width: 50px;" %)(((
297 297  **Size(bytes)**
298 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
299 -2
222 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)(((
223 +2(optional)
300 300  )))|(% style="width:87px" %)(((
301 -2
225 +2(optional)
302 302  )))
303 303  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
304 304  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
305 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
229 +)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
306 306  
307 -[[image:1665301636888-168.png]]
231 +[[image:1664501958445-288.png]]
308 308  
309 309  
310 310  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -313,11 +313,12 @@
313 313  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
314 314  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
315 315  
240 +
316 316  ==== (% style="color:blue" %)**FLAG:**(%%) ====
317 317  
318 318  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
319 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit
320 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
244 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits
245 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version 
321 321  
322 322  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
323 323  
... ... @@ -327,18 +327,23 @@
327 327  * Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
328 328  * Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
329 329  
255 +
256 +
330 330  (% style="color:red" %)**Important note:**
331 331  
332 332  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.
333 333  
334 -2.  In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
261 +2.  In firmware version v1.5, Roll & Pitch is disabled by default.
335 335  
263 +3.  When enable 9-axis motion sensor, the total payload will be 15 bytes, while US915/AU915 DR0 accept only 11 bytes payload. In this case, the payload on server will be ignore and shows as below:
336 336  
265 +
337 337  [[image:1664502116362-706.png]]
338 338  
339 339  
340 -3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
341 341  
270 +4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
271 +
342 342  [[image:1664502166010-515.png]]
343 343  
344 344  
... ... @@ -345,17 +345,18 @@
345 345  
346 346  ==== (% style="color:blue" %)**Alarm:**(%%) ====
347 347  
348 -**Example: ** 0x4B & 0x40 >> 6 = 0x01
278 +Example:  0x4B & 0x40 >> 6 = 0x01
349 349  
350 350  
351 351  ==== (% style="color:blue" %)**BAT:**(%%) ====
352 352  
353 -**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
283 +Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
354 354  
355 355  (((
356 -The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
286 +The battery info shows the current voltage, for (% style="color:blue" %)**TrackerD**(%%) version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \
357 357  )))
358 358  
289 +
359 359  * > 4.0v :  80% ~~ 100%
360 360  * 3.85v ~~3.99v:  60% ~~ 80%
361 361  * 3.70v ~~ 3.84v:  40% ~~ 60%
... ... @@ -362,37 +362,21 @@
362 362  * 3.40v ~~ 3.69v:  20% ~~ 40%
363 363  * < 3.39v:  0~~20%
364 364  
365 -==== (% style="color:blue" %)**MOD:**(%%) ====
366 366  
367 -**Example: ** (0x60>>6) & 0x3f =1
368 -
369 -**Set the format of GPS data uplink link：**
370 -
371 -(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
372 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
373 -
374 -
375 -**Set the format of BLE data uplink link：**
376 -
377 -(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon
378 -
379 -
380 380  ==== (% style="color:blue" %)**LON:**(%%) ====
381 381  
382 -**Example:** (0x60>>5) & 0x01=1.
383 -
299 +
384 384  Enable/Disable LED activity for uplink
385 385  
386 386  (((
387 -(% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
303 +0x00:  Disable LED indicator.
388 388  )))
389 389  
390 390  (((
391 -(% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
307 +0x01:  Enable LED indicator (Default Value)
392 392  )))
393 393  
394 394  
395 -
396 396  ==== (% style="color:blue" %)**Hum:**(%%) ====
397 397  
398 398  0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
... ... @@ -404,57 +404,15 @@
404 404  
405 405  
406 406  
407 -=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
322 +=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
408 408  
409 409  
410 -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)
411 411  
326 +=== 2.3.4 BLE positioning Payload(Fport2) ===
412 412  
413 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
414 -|=(% scope="row" style="width: 50px;" %)(((
415 -**Size(bytes)**
416 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
417 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
418 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
419 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
420 420  
421 -(% class="wikigeneratedid" %)
422 -[[image:1665301687277-443.png]]
329 +Different MODE has different payload:  (% style="color:blue" %)**MODE=2**
423 423  
424 -
425 -
426 -=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
427 -
428 -
429 -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.
430 -
431 -
432 -(% style="color:red" %)**Note for this mode:**
433 -
434 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
435 -* 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 -* 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
437 -
438 -The payload is 15 bytes, as below.
439 -
440 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
441 -|=(% scope="row" %)(((
442 -**Size(bytes)**
443 -)))|4|4|2|1|1|1|1|1
444 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
445 -
446 -[[image:image-20221009160309-2.png]]
447 -
448 -
449 -
450 -=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
451 -
452 -
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 -
458 458  (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
459 459  |=(% scope="row" style="width: 60px;" %)(((
460 460  **Size(bytes)**
... ... @@ -471,10 +471,11 @@
471 471  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
472 472  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
473 473  
347 +
474 474  [[image:1664502425687-834.png]]
475 475  
476 476  
477 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
351 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
478 478  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
479 479  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
480 480  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
... ... @@ -482,9 +482,11 @@
482 482  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
483 483  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
484 484  
485 -=== 2.4.6  Add Payload format in TTN V3 ===
486 486  
487 487  
361 +=== 2.3.5 Add Payload format in TTN V3 ===
362 +
363 +
488 488  In TTN V3, use can add a custom payload so it shows friendly.
489 489  
490 490  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
... ... @@ -493,9 +493,8 @@
493 493  [[image:1664502649601-895.png]]
494 494  
495 495  
496 -Add the decoder from this link: 
372 +Add the decoder from this link:
497 497  
498 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
499 499  
500 500  Save the change the uplink message will be parsed. As below:
501 501  
... ... @@ -503,49 +503,41 @@
503 503  
504 504  
505 505  
506 -== 2.5 Integrate with Datacake ==
381 +== 2.4 Integrate with Datacake ==
507 507  
508 508  
384 +(((
509 509  After TrackerD sends data to LoRaWAN server such as TTN, use can pass the data to Datacake and plot out, currently only support GPS plot.
386 +)))
510 510  
388 +(((
511 511  Instruction is here:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example~~-~~-AddTrackerDGPSTrackingInDataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Data%20Cake/#H7.Example--AddTrackerDGPSTrackingInDataCake]]
390 +)))
512 512  
392 +
513 513  [[image:1664502695771-538.png]]
514 514  
515 515  
516 516  
517 -== 2.6 Integrate with Tago ==
397 +== 2.5 Integrate with Tago ==
518 518  
519 519  
520 -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.
400 +(((
401 +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.
402 +)))
521 521  
404 +(((
522 522  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]]
406 +)))
523 523  
524 524  
525 -
526 526  [[image:1664502715371-321.png]]
527 527  
528 528  
529 529  
530 -== 2.7  Datalog Feature ==
413 +== 2.6 Alarm Mode ==
531 531  
532 532  
533 -total 273 entries,by default,
534 -
535 -User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
536 -
537 -Example use case.
538 -
539 -[[image:image-20221009234703-2.png||height="328" width="899"]]
540 -
541 -
542 -[[image:image-20221009234629-1.png||height="390" width="577"]]
543 -
544 -
545 -
546 -== 2.8 Alarm Mode ==
547 -
548 -
549 549  (((
550 550  User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
551 551  )))
... ... @@ -552,7 +552,7 @@
552 552  
553 553  
554 554  (((
555 -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.
422 +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.
556 556  )))
557 557  
558 558  
... ... @@ -560,9 +560,10 @@
560 560  Two ways to exit alarm mode:
561 561  )))
562 562  
563 -* Server sends a downlink command to exit.
430 +* Server send a downlink command to exit.
564 564  * User fast press the RED button 10 times.
565 565  
433 +
566 566  (((
567 567  When exit alarm mode, (% style="color:red" %)**RED LED**(%%) will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false.
568 568  )))
... ... @@ -569,16 +569,13 @@
569 569  
570 570  
571 571  
572 -== 2.9 Transport Mode ==
440 +== 2.7 Sports Mode ==
573 573  
574 574  
575 -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.
576 576  
444 +== 2.8 LED Status ==
577 577  
578 578  
579 -== 2.10 LED Status ==
580 -
581 -
582 582  (% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
583 583  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
584 584  |(% 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
... ... @@ -593,9 +593,11 @@
593 593  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
594 594  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
595 595  
596 -== 2.11 Button Function ==
597 597  
598 598  
463 +== 2.9 Button Function ==
464 +
465 +
599 599  (% style="color:blue" %)**RESET button:**
600 600  
601 601  [[image:1664502835802-546.png]]
... ... @@ -614,9 +614,11 @@
614 614  |(% 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
615 615  |(% 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.
616 616  
617 -== 2.12 USB Port Function ==
618 618  
619 619  
486 +== 2.10 USB Port Function ==
487 +
488 +
620 620  The USB interface of TrackerD has below functions:
621 621  
622 622  * Power on the device
... ... @@ -624,6 +624,9 @@
624 624  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
625 625  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
626 626  
496 +
497 +
498 +
627 627  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
628 628  
629 629  
... ... @@ -648,9 +648,11 @@
648 648  [[image:1664503022490-662.png]]
649 649  
650 650  
523 +
651 651  [[image:1664503035713-500.png]]
652 652  
653 653  
527 +
654 654  [[image:1664503047675-651.png]]
655 655  
656 656  
... ... @@ -694,16 +694,16 @@
694 694  
695 695  
696 696  
697 -=== 3.2.3 Set Transport Mode Packet transmission interval ===
571 +=== 3.2.3 Set Sports Mode Packet transmission interval ===
698 698  
699 699  
700 -Set Transport Mode packet transmit interval
574 +Set sports packet transmit interval
701 701  
702 702  * (% style="color:blue" %)**AT Command:**
703 703  
704 704  (% style="color:#037691" %)**AT+MTDC=xx. **
705 705  
706 -Example:  AT+MTDC=300000  **~-~->    ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000
580 +Example:  AT+MTDC=300000  **~-~->    ** Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000
707 707  
708 708  
709 709  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
... ... @@ -743,16 +743,16 @@
743 743  
744 744  
745 745  
746 -=== 3.2.6 Disable/Enable Transport Mode ===
620 +=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
747 747  
748 748  
749 -Users can use this feature to enable/disable Transport Mode.
623 +User can use this feature to check and set thread hole of movement detect
750 750  
751 751  * (% style="color:blue" %)**AT Command:**
752 752  
753 753  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
754 754  
755 -Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
629 +Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
756 756  
757 757  
758 758  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
... ... @@ -764,38 +764,35 @@
764 764  === 3.2.7 Set Positioning Mode ===
765 765  
766 766  
767 -SMOD define how TrackerD scan and uplink data:
641 +SMOD define the how TrackerD scan and uplink date.
768 768  
643 +GPS室外定位模式：  设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
769 769  
770 -* (% style="color:blue" %)**AT Command:**
645 +BLE室内定位模式：  设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
771 771  
772 -(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
647 +GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
773 773  
774 -(% style="color:#037691" %)** aa:**
649 +运动模式：  设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
775 775  
776 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
777 -* (% style="color:red" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
778 -* (% 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.
779 779  
780 -(% style="color:#037691" %)**bb:**
781 781  
782 -* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
783 -* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
653 +* (% style="color:blue" %)**AT Command:**
784 784  
785 -(% style="color:#037691" %)**cc:   **
655 +(% style="color:#037691" %)**AT+SMOD=xx. **
786 786  
787 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
788 788  
789 -(% style="color:blue" %)**Example:**
658 + **Example:**
790 790  
791 - AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
792 - AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
793 - AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
660 + AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
794 794  
662 + AT+ SMOD =1,1    **~-~->**  GPS +BAT State
795 795  
664 + AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
665 +
666 +
796 796  * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
797 797  
798 -(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
669 +(% style="color:#037691" %)**0xA5 01 00**    (%%) ~/~/  Same as AT+ SMOD =1,0
799 799  
800 800  
801 801  
... ... @@ -812,7 +812,7 @@
812 812  
813 813  (% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
814 814  
815 -**Example:**  AT+FTIME=150
686 +Example:  AT+FTIME=150
816 816  
817 817  
818 818  * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
... ... @@ -821,7 +821,7 @@
821 821  
822 822  
823 823  
824 -=== 3.2.9 Set PDOP value for GPS fix accuracy ===
695 +=== 3.3.9 Set PDOP value for GPS fix accuracy ===
825 825  
826 826  
827 827  PDOP(Position Dilution of Precision) filter, TrackerD will only accept GPS data with a lower PDOP value than pre-configure PDOP value. If device can't get a valid GPS packet within FTIME timeout, it will use the GPS data with lowest PDOP value to server.
... ... @@ -849,7 +849,7 @@
849 849  
850 850  * (% style="color:blue" %)**AT Command:**
851 851  
852 -(% style="color:#037691" %)**AT+CFM=xx**
723 +(% style="color:#037691" %)**AT+CFM=xx. **
853 853  
854 854  
855 855  **~ Example:**
... ... @@ -865,48 +865,6 @@
865 865  
866 866  
867 867  
868 -=== 3.2.10  Auto Send None-ACK messages ===
869 -
870 -
871 -TrackerD will wait for ACK for each uplink, If TrackerD doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. TrackerD keeps sending messages in normal periodically. Once TrackerD gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
872 -
873 -
874 -* (% style="color:blue" %)**AT Command: AT+PNACKMD**
875 -
876 -The default factory setting is 0.
877 -
878 -
879 -**Command Example Function Response:**
880 -
881 -(% style="color:#037691" %)**AT+PNACKMD=1**  (%%) ~/~/  Poll None-ACK message OK
882 -
883 -
884 -* (% style="color:blue" %)**Downlink Command: 0x34**
885 -
886 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
887 -
888 -
889 -
890 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
891 -
892 -
893 -BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. LBT1 will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
894 -
895 -(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
896 -
897 -(% style="color:blue" %)**AT Command:**
898 -
899 - (% style="color:#037691" %)**AT+BLEMASK=123456**   (%%) ~/~/ Set BLEMASK = 123456
900 -
901 - (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
902 -
903 -
904 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**
905 -
906 -Example: 0xA5010203040506    ~/~/ Set BLEMASK to 123456
907 -
908 -
909 -
910 910  = 4. Setting for Different Scenarios =
911 911  
912 912  
... ... @@ -947,10 +947,9 @@
947 947  [[image:1664503574618-659.png]]
948 948  
949 949  
950 -
951 951  (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
952 952  
953 -[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
781 +[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
954 954  
955 955  
956 956  Users need to use below files:
... ... @@ -987,24 +987,12 @@
987 987  [[image:1664503635019-941.png]]
988 988  
989 989  
990 -
991 991  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
992 992  
993 993  [[image:1664503715811-892.png]]
994 994  
995 995  
996 -(% 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.
997 997  
998 -[[image:image-20221024105643-1.png]]
999 -
1000 -**~ Figure1**
1001 -
1002 -
1003 -[[image:image-20221024105643-2.png]]
1004 -
1005 - **Figure2**
1006 -
1007 -
1008 1008  * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]**
1009 1009  
1010 1010  Put the Library in the TrackerD directory into the libraries file in the Arduino directory:
... ... @@ -1063,6 +1063,8 @@
1063 1063  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1064 1064  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1065 1065  
882 +
883 +
1066 1066  = 8.  Order Info =
1067 1067  
1068 1068  
... ... @@ -1078,19 +1078,25 @@
1078 1078  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1079 1079  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1080 1080  
899 +
900 +
901 +
1081 1081  = 9.  Packing Info =
1082 1082  
1083 1083  
1084 -(% style="color:#037691" %)**Package Includes**:
905 +**(% style="color:#037691" %)Package Includes**:
1085 1085  
1086 1086  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1087 1087  * USB recharge & program cable x 1
1088 1088  
1089 -(% style="color:#037691" %)**Dimensions and Weight**:
910 +**(% style="color:#037691" %)Dimensions and Weight**:
1090 1090  
1091 1091  * Device Size: 85 x 48 x 15 cm
1092 1092  * Weight: 50g
1093 1093  
915 +
916 +
917 +
1094 1094  = 10. Support =
1095 1095  
1096 1096  
... ... @@ -1097,6 +1097,9 @@
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.
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  
924 +
925 +
926 +
1100 1100  = 11.  Reference =
1101 1101  
1102 1102  
... ... @@ -1104,4 +1104,5 @@
1104 1104  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1105 1105  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1106 1106  
934 +
1107 1107  
1665301570342-765.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -31.6 KB
Content
1665301636888-168.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -36.6 KB
Content
1665301687277-443.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.6 KB
Content
1665301786397-168.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.6 KB
Content
image-20221006181316-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -17.7 KB
Content
image-20221006181357-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -88.0 KB
Content
image-20221009160220-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.4 KB
Content
image-20221009160309-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -57.2 KB
Content
image-20221009234629-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -222.9 KB
Content
image-20221009234703-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -136.4 KB
Content
image-20221024105643-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.3 KB
Content
image-20221024105643-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -64.5 KB
Content