Skip to Content
Last modified by Xiaoling on 2025/04/27 16:48
From version 84.2
edited by Xiaoling
on 2022/10/24 10:58
Change comment: There is no comment for this version
To version 51.28
edited by Xiaoling
on 2022/09/30 15:46
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
... ... @@ -105,7 +105,7 @@
105 105  * LoRaWAN 1.0.3 Class A
106 106  * ESP32 PICO D4
107 107  * SX1276/78 Wireless Chip
108 -* Arduino IDE Compatible
112 +** Arduino IDE Compatible
109 109  * Open source hardware / software
110 110  * Regular/ Real-time GPS,BLE,WIFI tracking
111 111  * Built-in3 axis accelerometer (LIS3DH)
... ... @@ -189,130 +189,42 @@
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  
196 +(% style="color:blue" %)**Positioning Mode(SMOD):**
192 192  
193 -== 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.
194 194  
202 +User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
195 195  
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.
201 201  
202 -Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
206 +== 2.3 Uplink Payload ==
203 203  
204 204  
209 +=== 2.3.1 Uplink FPORT~=5, Device Status ===
205 205  
206 -== 2.4  Uplink Payload ==
207 207  
208 208  
209 -=== 2.4.1 Uplink FPORT~=5, Device Status ===
213 +=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning ===
210 210  
211 211  
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.
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. )
213 213  
214 -Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
215 215  
216 -
217 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
218 -|=(% 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
219 -|=(% 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
220 -
221 -[[image:1665301570342-765.png]]
222 -
223 -
224 -(% style="color:#037691" %)**Example of Device Status:**(%%) 13014001FF0FA24002
225 -
226 -(% style="color:#037691" %)**Sensor Model:** (%%) For TrackerD,this value is 0x13
227 -
228 -(% style="color:#037691" %)**Firmware Version: **(%%) 0x0140,Means:v1.4.0 version
229 -
230 -(% style="color:#037691" %)**Frequency Band**:
231 -
232 -*0x01: EU868
233 -
234 -*0x02: US915
235 -
236 -*0x03: IN865
237 -
238 -*0x04: AU915
239 -
240 -*0x05: KZ865
241 -
242 -*0x06: RU864
243 -
244 -*0x07: AS923
245 -
246 -*0x08: AS923-1
247 -
248 -*0x09: AS923-2
249 -
250 -*0x0a: AS923-3
251 -
252 -Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
253 -
254 -(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
255 -
256 -
257 -(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
258 -
259 -Use can also get the Device Status uplink through the downlink command:
260 -
261 -
262 -(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
263 -
264 -(% border="1.5" style="background-color:#ffffcc; color:green; width:420px" %)
265 -|(% style="width:75px" %)**Size(bit)**|(% style="width:64px" %)2bits|(% style="width:137px" %)2bit|(% style="width:142px" %)4bit
266 -|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:137px" %)GPS_Settings|(% style="width:142px" %)BLE_Settings
267 -
268 -(% style="color:blue" %)** SMOD：**
269 -
270 -(% style="color:red" %)** 1 :** (%%) GPS ONLY
271 -
272 -(% style="color:red" %)** 2 :** (%%) BLE ONLY
273 -
274 -(% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
275 -
276 -
277 -(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
278 -
279 -(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
280 -
281 -(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values
282 -
283 -
284 -(% style="color:blue" %)** BLE_Settings:**
285 -
286 -(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
287 -
288 -
289 -(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
290 -
291 -(% border="1.5" style="background-color:#ffffcc; color:green; width:417px" %)
292 -|(% 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
293 -|(% 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"]]
294 -
295 -
296 -
297 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
298 -
299 -
300 -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,
301 -
302 -
303 303  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
304 304  |=(% scope="row" style="width: 50px;" %)(((
305 305  **Size(bytes)**
306 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
307 -2
222 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)(((
223 +2(optional)
308 308  )))|(% style="width:87px" %)(((
309 -2
225 +2(optional)
310 310  )))
311 311  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
312 312  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
313 -)))|(% 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:"]]
314 314  
315 -[[image:1665301636888-168.png]]
231 +[[image:1664501958445-288.png]]
316 316  
317 317  
318 318  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -321,11 +321,12 @@
321 321  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
322 322  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
323 323  
240 +
324 324  ==== (% style="color:blue" %)**FLAG:**(%%) ====
325 325  
326 326  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
327 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit
328 -|=(% 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="H2.3.4BLEpositioningPayload28Fport229"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]|(% style="width:140px" %)Firmware version 
329 329  
330 330  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
331 331  
... ... @@ -335,18 +335,23 @@
335 335  * Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
336 336  * Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
337 337  
255 +
256 +
338 338  (% style="color:red" %)**Important note:**
339 339  
340 340  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.
341 341  
342 -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.
343 343  
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:
344 344  
265 +
345 345  [[image:1664502116362-706.png]]
346 346  
347 347  
348 -3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
349 349  
270 +4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
271 +
350 350  [[image:1664502166010-515.png]]
351 351  
352 352  
... ... @@ -353,17 +353,18 @@
353 353  
354 354  ==== (% style="color:blue" %)**Alarm:**(%%) ====
355 355  
356 -**Example: ** 0x4B & 0x40 >> 6 = 0x01
278 +Example:  0x4B & 0x40 >> 6 = 0x01
357 357  
358 358  
359 359  ==== (% style="color:blue" %)**BAT:**(%%) ====
360 360  
361 -**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
283 +Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
362 362  
363 363  (((
364 -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: \
365 365  )))
366 366  
289 +
367 367  * > 4.0v :  80% ~~ 100%
368 368  * 3.85v ~~3.99v:  60% ~~ 80%
369 369  * 3.70v ~~ 3.84v:  40% ~~ 60%
... ... @@ -371,38 +371,20 @@
371 371  * < 3.39v:  0~~20%
372 372  
373 373  
374 -
375 -==== (% style="color:blue" %)**MOD:**(%%) ====
376 -
377 -**Example: ** (0x60>>6) & 0x3f =1
378 -
379 -**Set the format of GPS data uplink link：**
380 -
381 -(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
382 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
383 -
384 -
385 -**Set the format of BLE data uplink link：**
386 -
387 -(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon
388 -
389 -
390 390  ==== (% style="color:blue" %)**LON:**(%%) ====
391 391  
392 -**Example:** (0x60>>5) & 0x01=1.
393 -
299 +
394 394  Enable/Disable LED activity for uplink
395 395  
396 396  (((
397 -(% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
303 +0x00:  Disable LED indicator.
398 398  )))
399 399  
400 400  (((
401 -(% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
307 +0x01:  Enable LED indicator (Default Value)
402 402  )))
403 403  
404 404  
405 -
406 406  ==== (% style="color:blue" %)**Hum:**(%%) ====
407 407  
408 408  0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
... ... @@ -414,57 +414,15 @@
414 414  
415 415  
416 416  
417 -=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
322 +=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
418 418  
419 419  
420 -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)
421 421  
326 +=== 2.3.4 BLE positioning Payload(Fport2) ===
422 422  
423 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
424 -|=(% scope="row" style="width: 50px;" %)(((
425 -**Size(bytes)**
426 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
427 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
428 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
429 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
430 430  
431 -(% class="wikigeneratedid" %)
432 -[[image:1665301687277-443.png]]
329 +Different MODE has different payload:  (% style="color:blue" %)**MODE=2**
433 433  
434 -
435 -
436 -=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
437 -
438 -
439 -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.
440 -
441 -
442 -(% style="color:red" %)**Note for this mode:**
443 -
444 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
445 -* 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.
446 -* 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 -
448 -The payload is 15 bytes, as below.
449 -
450 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
451 -|=(% scope="row" %)(((
452 -**Size(bytes)**
453 -)))|4|4|2|1|1|1|1|1
454 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
455 -
456 -[[image:image-20221009160309-2.png]]
457 -
458 -
459 -
460 -=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
461 -
462 -
463 -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.
464 -
465 -User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings.
466 -
467 -
468 468  (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
469 469  |=(% scope="row" style="width: 60px;" %)(((
470 470  **Size(bytes)**
... ... @@ -481,10 +481,11 @@
481 481  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
482 482  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
483 483  
347 +
484 484  [[image:1664502425687-834.png]]
485 485  
486 486  
487 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
351 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV).
488 488  * (% style="color:#037691" %)**MODE:   **(%%)Define the payload format.
489 489  * (% style="color:#037691" %)**UUID:     **(%%)The uuid from the strongest iBeacon.
490 490  * (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon.
... ... @@ -494,7 +494,7 @@
494 494  
495 495  
496 496  
497 -=== 2.4.6  Add Payload format in TTN V3 ===
361 +=== 2.3.5 Add Payload format in TTN V3 ===
498 498  
499 499  
500 500  In TTN V3, use can add a custom payload so it shows friendly.
... ... @@ -505,9 +505,8 @@
505 505  [[image:1664502649601-895.png]]
506 506  
507 507  
508 -Add the decoder from this link: 
372 +Add the decoder from this link:
509 509  
510 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]]
511 511  
512 512  Save the change the uplink message will be parsed. As below:
513 513  
... ... @@ -515,49 +515,41 @@
515 515  
516 516  
517 517  
518 -== 2.5 Integrate with Datacake ==
381 +== 2.4 Integrate with Datacake ==
519 519  
383 +
384 +(((
520 520  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 +)))
521 521  
388 +(((
522 522  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 +)))
523 523  
392 +
524 524  [[image:1664502695771-538.png]]
525 525  
526 526  
527 527  
528 -== 2.6 Integrate with Tago ==
397 +== 2.5 Integrate with Tago ==
529 529  
530 530  
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 +)))
531 531  
532 -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.
533 -
404 +(((
534 534  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 +)))
535 535  
536 536  
537 -
538 538  [[image:1664502715371-321.png]]
539 539  
540 540  
541 541  
542 -== 2.7  Datalog Feature ==
413 +== 2.6 Alarm Mode ==
543 543  
544 544  
545 -total 273 entries,by default,
546 -
547 -User can set [[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]], to enable Datalog feature.
548 -
549 -Example use case.
550 -
551 -[[image:image-20221009234703-2.png||height="328" width="899"]]
552 -
553 -
554 -[[image:image-20221009234629-1.png||height="390" width="577"]]
555 -
556 -
557 -
558 -== 2.8 Alarm Mode ==
559 -
560 -
561 561  (((
562 562  User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
563 563  )))
... ... @@ -564,7 +564,7 @@
564 564  
565 565  
566 566  (((
567 -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.
568 568  )))
569 569  
570 570  
... ... @@ -572,9 +572,10 @@
572 572  Two ways to exit alarm mode:
573 573  )))
574 574  
575 -* Server sends a downlink command to exit.
430 +* Server send a downlink command to exit.
576 576  * User fast press the RED button 10 times.
577 577  
433 +
578 578  (((
579 579  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.
580 580  )))
... ... @@ -581,16 +581,13 @@
581 581  
582 582  
583 583  
584 -== 2.9 Transport Mode ==
440 +== 2.7 Sports Mode ==
585 585  
586 586  
587 -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.
588 588  
444 +== 2.8 LED Status ==
589 589  
590 590  
591 -== 2.10 LED Status ==
592 -
593 -
594 594  (% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
595 595  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
596 596  |(% 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
... ... @@ -607,7 +607,7 @@
607 607  
608 608  
609 609  
610 -== 2.11 Button Function ==
463 +== 2.9 Button Function ==
611 611  
612 612  
613 613  (% style="color:blue" %)**RESET button:**
... ... @@ -630,7 +630,7 @@
630 630  
631 631  
632 632  
633 -== 2.12 USB Port Function ==
486 +== 2.10 USB Port Function ==
634 634  
635 635  
636 636  The USB interface of TrackerD has below functions:
... ... @@ -642,6 +642,7 @@
642 642  
643 643  
644 644  
498 +
645 645  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
646 646  
647 647  
... ... @@ -666,9 +666,11 @@
666 666  [[image:1664503022490-662.png]]
667 667  
668 668  
523 +
669 669  [[image:1664503035713-500.png]]
670 670  
671 671  
527 +
672 672  [[image:1664503047675-651.png]]
673 673  
674 674  
... ... @@ -712,16 +712,16 @@
712 712  
713 713  
714 714  
715 -=== 3.2.3 Set Transport Mode Packet transmission interval ===
571 +=== 3.2.3 Set Sports Mode Packet transmission interval ===
716 716  
717 717  
718 -Set Transport Mode packet transmit interval
574 +Set sports packet transmit interval
719 719  
720 720  * (% style="color:blue" %)**AT Command:**
721 721  
722 722  (% style="color:#037691" %)**AT+MTDC=xx. **
723 723  
724 -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
725 725  
726 726  
727 727  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
... ... @@ -761,16 +761,16 @@
761 761  
762 762  
763 763  
764 -=== 3.2.6 Disable/Enable Transport Mode ===
620 +=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
765 765  
766 766  
767 -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
768 768  
769 769  * (% style="color:blue" %)**AT Command:**
770 770  
771 771  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
772 772  
773 -Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
629 +Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
774 774  
775 775  
776 776  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
... ... @@ -782,38 +782,35 @@
782 782  === 3.2.7 Set Positioning Mode ===
783 783  
784 784  
785 -SMOD define how TrackerD scan and uplink data:
641 +SMOD define the how TrackerD scan and uplink date.
786 786  
643 +GPS室外定位模式：  设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
787 787  
788 -* (% style="color:blue" %)**AT Command:**
645 +BLE室内定位模式：  设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
789 789  
790 -(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
647 +GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
791 791  
792 -(% style="color:#037691" %)** aa:**
649 +运动模式：  设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
793 793  
794 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
795 -* (% style="color:red" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
796 -* (% 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.
797 797  
798 -(% style="color:#037691" %)**bb:**
799 799  
800 -* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
801 -* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
653 +* (% style="color:blue" %)**AT Command:**
802 802  
803 -(% style="color:#037691" %)**cc:   **
655 +(% style="color:#037691" %)**AT+SMOD=xx. **
804 804  
805 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
806 806  
807 -(% style="color:blue" %)**Example:**
658 + **Example:**
808 808  
809 - AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
810 - AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
811 - AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
660 + AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
812 812  
662 + AT+ SMOD =1,1    **~-~->**  GPS +BAT State
813 813  
664 + AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
665 +
666 +
814 814  * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
815 815  
816 -(% 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
817 817  
818 818  
819 819  
... ... @@ -830,7 +830,7 @@
830 830  
831 831  (% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
832 832  
833 -**Example:**  AT+FTIME=150
686 +Example:  AT+FTIME=150
834 834  
835 835  
836 836  * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
... ... @@ -839,7 +839,7 @@
839 839  
840 840  
841 841  
842 -=== 3.2.9 Set PDOP value for GPS fix accuracy ===
695 +=== 3.3.9 Set PDOP value for GPS fix accuracy ===
843 843  
844 844  
845 845  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.
... ... @@ -867,7 +867,7 @@
867 867  
868 868  * (% style="color:blue" %)**AT Command:**
869 869  
870 -(% style="color:#037691" %)**AT+CFM=xx**
723 +(% style="color:#037691" %)**AT+CFM=xx. **
871 871  
872 872  
873 873  **~ Example:**
... ... @@ -883,46 +883,6 @@
883 883  
884 884  
885 885  
886 -=== 3.2.10  Auto Send None-ACK messages ===
887 -
888 -
889 -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.
890 -
891 -
892 -* (% style="color:blue" %)**AT Command: AT+PNACKMD**
893 -
894 -The default factory setting is 0.
895 -
896 -
897 -**Command Example Function Response:**
898 -
899 -(% style="color:#037691" %)**AT+PNACKMD=1**  (%%) ~/~/  Poll None-ACK message OK
900 -
901 -
902 -* (% style="color:blue" %)**Downlink Command: 0x34**
903 -
904 -Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
905 -
906 -
907 -
908 -=== 3.2.11  Set BLEMASK to filter BLE iBeacon ===
909 -
910 -
911 -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.
912 -
913 -Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.
914 -
915 -(% style="color:blue" %)**AT Command:**(%%)
916 - AT+BLEMASK=123456     ~/~/ Set BLEMASK = 123456
917 - AT+BLEMASK=0  ~/~/ disable BLEMASK
918 -
919 -
920 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**(%%)
921 -Example:
922 -0xA5010203040506    ~/~/ Set BLEMASK to 123456
923 -
924 -
925 -
926 926  = 4. Setting for Different Scenarios =
927 927  
928 928  
... ... @@ -963,21 +963,9 @@
963 963  [[image:1664503574618-659.png]]
964 964  
965 965  
966 -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.
967 -
968 -[[image:image-20221024105643-1.png]]
969 -
970 - Figure1
971 -
972 -
973 -[[image:image-20221024105643-2.png]]
974 -
975 - Figure2
976 -
977 -
978 978  (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
979 979  
980 -[[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]]
981 981  
982 982  
983 983  Users need to use below files:
... ... @@ -1014,7 +1014,6 @@
1014 1014  [[image:1664503635019-941.png]]
1015 1015  
1016 1016  
1017 -
1018 1018  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
1019 1019  
1020 1020  [[image:1664503715811-892.png]]
... ... @@ -1079,6 +1079,8 @@
1079 1079  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1080 1080  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1081 1081  
882 +
883 +
1082 1082  = 8.  Order Info =
1083 1083  
1084 1084  
... ... @@ -1096,15 +1096,16 @@
1096 1096  
1097 1097  
1098 1098  
901 +
1099 1099  = 9.  Packing Info =
1100 1100  
1101 1101  
1102 -(% style="color:#037691" %)**Package Includes**:
905 +**(% style="color:#037691" %)Package Includes**:
1103 1103  
1104 1104  * TrackerD LoRaWAN GPS/BLE Tracker x 1
1105 1105  * USB recharge & program cable x 1
1106 1106  
1107 -(% style="color:#037691" %)**Dimensions and Weight**:
910 +**(% style="color:#037691" %)Dimensions and Weight**:
1108 1108  
1109 1109  * Device Size: 85 x 48 x 15 cm
1110 1110  * Weight: 50g
... ... @@ -1111,6 +1111,7 @@
1111 1111  
1112 1112  
1113 1113  
917 +
1114 1114  = 10. Support =
1115 1115  
1116 1116  
... ... @@ -1119,6 +1119,7 @@
1119 1119  
1120 1120  
1121 1121  
926 +
1122 1122  = 11.  Reference =
1123 1123  
1124 1124  
... ... @@ -1126,4 +1126,5 @@
1126 1126  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1127 1127  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1128 1128  
934 +
1129 1129  
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