Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 51.29
edited by Xiaoling
on 2022/09/30 15:58
Change comment: There is no comment for this version
To version 77.1
edited by Edwin Chen
on 2022/10/13 23:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -61,13 +61,11 @@
61 61  * EEPROM: 520 KB
62 62  * Clock Speed: 32Mhz
63 63  
64 -
65 65  (% style="color:blue" %)**Common DC Characteristics:**
66 66  
67 67  * Supply Voltage: 5V via USB port or Internal li-on battery
68 68  * Operating Temperature: -40 ~~ 60°C
69 69  
70 -
71 71  (% style="color:blue" %)**LoRa Spec:**
72 72  
73 73  * Frequency Range,
... ... @@ -89,12 +89,10 @@
89 89  * Packet engine up to 256 bytes with CRC.
90 90  * LoRaWAN 1.0.3 Specification
91 91  
92 -
93 93  (% style="color:blue" %)**Battery:**
94 94  
95 95  * 1000mA Li-on Battery power (for model TrackerD)
96 96  
97 -
98 98  (% style="color:blue" %)**Power Consumption**
99 99  
100 100  * Sleeping Mode: 200uA
... ... @@ -101,8 +101,6 @@
101 101  * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm
102 102  * Tracking: max: 38mA
103 103  
104 -
105 -
106 106  == 1.3  Features ==
107 107  
108 108  
... ... @@ -109,7 +109,7 @@
109 109  * LoRaWAN 1.0.3 Class A
110 110  * ESP32 PICO D4
111 111  * SX1276/78 Wireless Chip
112 -** Arduino IDE Compatible
106 +* Arduino IDE Compatible
113 113  * Open source hardware / software
114 114  * Regular/ Real-time GPS,BLE,WIFI tracking
115 115  * Built-in3 axis accelerometer (LIS3DH)
... ... @@ -121,8 +121,6 @@
121 121  * Tri-color LED, Alarm button
122 122  * Datalog
123 123  
124 -
125 -
126 126  == 1.4  Applications ==
127 127  
128 128  
... ... @@ -129,8 +129,6 @@
129 129  * Logistics and Supply Chain Management
130 130  * Human tracking
131 131  
132 -
133 -
134 134  = 2.1 Use TrackerD =
135 135  
136 136  
... ... @@ -193,42 +193,134 @@
193 193  (% 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.
194 194  
195 195  
196 -(% style="color:blue" %)**Positioning Mode(SMOD):**
197 197  
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.
187 +== 2.3  Positioning Mode(SMOD) ==
201 201  
202 -User can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
203 203  
190 +Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
204 204  
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.
205 205  
206 -== 2.3 Uplink Payload ==
196 +Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
207 207  
208 208  
209 -=== 2.3.1 Uplink FPORT~=5, Device Status ===
210 210  
200 +== 2.4  Uplink Payload ==
211 211  
212 212  
213 -=== 2.3.2 Uplink FPORT~= , Realtime GNSS Positioning ===
203 +=== 2.4.1 Uplink FPORT~=5, Device Status ===
214 214  
215 215  
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. )
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.
217 217  
208 +Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
218 218  
210 +
211 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
212 +|=(% scope="row" style="width: 108px;" %)**Size(bytes)**|=(% style="width: 82px;" %)**1**|=(% style="width: 83px;" %)**2**|=(% style="width: 94px;" %)**1**|=(% style="width: 84px;" %)**1**|=(% style="width: 44px;" %)2|=(% style="width: 63px;" %)**2**|=(% style="width: 60px;" %)1
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 +
257 +(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%)：0x40
258 +
259 +(% border="1.5" style="background-color:#ffffcc; color:green; width:420px" %)
260 +|(% style="width:75px" %)**Size(bit)**|(% style="width:64px" %)2bits|(% style="width:137px" %)2bit|(% style="width:142px" %)4bit
261 +|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:137px" %)GPS_Settings|(% style="width:142px" %)BLE_Settings
262 +
263 +(% style="color:blue" %)** SMOD：**
264 +
265 +(% style="color:red" %)** 1 :** (%%) GPS ONLY
266 +
267 +(% style="color:red" %)** 2 :** (%%) BLE ONLY
268 +
269 +(% style="color:red" %)** 3 :**  (%%) GPS/BLE Hybrid
270 +
271 +
272 +(% style="color:blue" %)** GPS_MOD: Define how to send GPS payload**
273 +
274 +(% style="color:red" %)** 0 : ** (%%) Enable uploading on-board Temperature and humidity values
275 +
276 +(% style="color:red" %)** 1 :** (%%) Disable uploading on-board Temperature and humidity values
277 +
278 +
279 +(% style="color:blue" %)** BLE_Settings:**
280 +
281 +(% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
282 +
283 +
284 +
285 +(% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
286 +
287 +(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
288 +|(% style="width:77px" %)**Size(bit)**|(% style="width:82px" %)5 Bits|(% style="width:106px" %)1 Bit|(% style="width:67px" %)1 Bit|(% style="width:121px" %)1 Bit
289 +|(% style="width:77px" %)**Value**|(% style="width:82px" %)Reserve|(% style="width:106px" %)PNACKMD|(% style="width:67px" %)LON|(% style="width:121px" %)Transport** **Mode
290 +
291 +
292 +
293 +=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity ===
294 +
295 +
296 +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,
297 +
298 +(% style="color:red" %)Please note that 15 bytes won't work on DR0 on US915/AU915 frequency band. IoT server will see NULL payload in this case.(%%)
299 +
300 +
219 219  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
220 220  |=(% scope="row" style="width: 50px;" %)(((
221 221  **Size(bytes)**
222 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)(((
223 -2(optional)
304 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((
305 +2
224 224  )))|(% style="width:87px" %)(((
225 -2(optional)
307 +2
226 226  )))
227 227  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
228 228  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
229 -)))|(% style="width:52px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:88px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
311 +)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
230 230  
231 -[[image:1664501958445-288.png]]
313 +[[image:1665301636888-168.png]]
232 232  
233 233  
234 234  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -237,12 +237,11 @@
237 237  |=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits
238 238  |=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 
239 239  
240 -
241 241  ==== (% style="color:blue" %)**FLAG:**(%%) ====
242 242  
243 243  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %)
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 
325 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit
326 +|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]]
246 246  
247 247  **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 
248 248  
... ... @@ -252,23 +252,18 @@
252 252  * Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
253 253  * Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
254 254  
255 -
256 -
257 257  (% style="color:red" %)**Important note:**
258 258  
259 259  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.
260 260  
261 -2.  In firmware version v1.5, Roll & Pitch is disabled by default.
340 +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:
262 262  
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:
264 264  
265 -
266 266  [[image:1664502116362-706.png]]
267 267  
268 268  
346 +3.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
269 269  
270 -4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
271 -
272 272  [[image:1664502166010-515.png]]
273 273  
274 274  
... ... @@ -275,18 +275,17 @@
275 275  
276 276  ==== (% style="color:blue" %)**Alarm:**(%%) ====
277 277  
278 -Example:  0x4B & 0x40 >> 6 = 0x01
354 +**Example: ** 0x4B & 0x40 >> 6 = 0x01
279 279  
280 280  
281 281  ==== (% style="color:blue" %)**BAT:**(%%) ====
282 282  
283 -Example:  0x0CDD & 0x3FFF ⇒ 3293 (mV).
359 +**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
284 284  
285 285  (((
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: \
362 +The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \
287 287  )))
288 288  
289 -
290 290  * > 4.0v :  80% ~~ 100%
291 291  * 3.85v ~~3.99v:  60% ~~ 80%
292 292  * 3.70v ~~ 3.84v:  40% ~~ 60%
... ... @@ -293,21 +293,37 @@
293 293  * 3.40v ~~ 3.69v:  20% ~~ 40%
294 294  * < 3.39v:  0~~20%
295 295  
371 +==== (% style="color:blue" %)**MOD:**(%%) ====
296 296  
373 +**Example: ** (0x60>>6)& 0x3f =1.
374 +
375 +**Set the format of GPS data uplink link：**
376 +
377 +(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values
378 +(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values
379 +
380 +
381 +**Set the format of BLE data uplink link：**
382 +
383 +(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon
384 +
385 +
297 297  ==== (% style="color:blue" %)**LON:**(%%) ====
298 298  
299 -
388 +**Example:** (0x60>>5) & 0x01=1.
389 +
300 300  Enable/Disable LED activity for uplink
301 301  
302 302  (((
303 -0x00:  Disable LED indicator.
393 +(% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
304 304  )))
305 305  
306 306  (((
307 -0x01:  Enable LED indicator (Default Value)
397 +(% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
308 308  )))
309 309  
310 310  
401 +
311 311  ==== (% style="color:blue" %)**Hum:**(%%) ====
312 312  
313 313  0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
... ... @@ -319,15 +319,51 @@
319 319  
320 320  
321 321  
322 -=== 2.3.3 Uplink FPORT~= , History GNSS Positioning ===
413 +=== 2.4.3  Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) ===
323 323  
324 324  
416 +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)
325 325  
326 -=== 2.3.4 BLE positioning Payload(Fport2) ===
327 327  
419 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
420 +|=(% scope="row" style="width: 50px;" %)(((
421 +**Size(bytes)**
422 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
423 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
424 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
425 +)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
328 328  
329 -Different MODE has different payload:  (% style="color:blue" %)**MODE=2**
427 +(% class="wikigeneratedid" %)
428 +[[image:1665301687277-443.png]]
330 330  
430 +
431 +
432 +=== 2.4.4  Uplink FPORT~=4, History GNSS Positioning ===
433 +
434 +
435 +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 +
437 +
438 +(% style="color:red" %)**Note for this mode:**
439 +
440 +* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
441 +* 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 +
443 +The payload is 15 bytes, as below.
444 +
445 +(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
446 +|=(% scope="row" %)(((
447 +**Size(bytes)**
448 +)))|4|4|2|1|1|1|1|1
449 +|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen
450 +
451 +[[image:image-20221009160309-2.png]]
452 +
453 +
454 +
455 +=== 2.4.5  Uplink FPORT~=6, BLE Positioning with Strongest iBeacon ===
456 +
457 +
331 331  (% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %)
332 332  |=(% scope="row" style="width: 60px;" %)(((
333 333  **Size(bytes)**
... ... @@ -344,7 +344,6 @@
344 344  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
345 345  )))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]]
346 346  
347 -
348 348  [[image:1664502425687-834.png]]
349 349  
350 350  
... ... @@ -356,11 +356,9 @@
356 356  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
357 357  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
358 358  
485 +=== 2.4.6  Add Payload format in TTN V3 ===
359 359  
360 360  
361 -=== 2.3.5 Add Payload format in TTN V3 ===
362 -
363 -
364 364  In TTN V3, use can add a custom payload so it shows friendly.
365 365  
366 366  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
... ... @@ -378,7 +378,7 @@
378 378  
379 379  
380 380  
381 -== 2.4 Integrate with Datacake ==
505 +== 2.5 Integrate with Datacake ==
382 382  
383 383  
384 384  (((
... ... @@ -394,7 +394,7 @@
394 394  
395 395  
396 396  
397 -== 2.5 Integrate with Tago ==
521 +== 2.6 Integrate with Tago ==
398 398  
399 399  
400 400  (((
... ... @@ -410,9 +410,24 @@
410 410  
411 411  
412 412  
413 -== 2.6 Alarm Mode ==
537 +== 2.7  Datalog Feature ==
414 414  
415 415  
540 +total 273 entries,by default disable
541 +
542 +
543 +Example use case.
544 +
545 +[[image:image-20221009234703-2.png||height="328" width="899"]]
546 +
547 +
548 +[[image:image-20221009234629-1.png||height="390" width="577"]]
549 +
550 +
551 +
552 +== 2.8 Alarm Mode ==
553 +
554 +
416 416  (((
417 417  User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode.
418 418  )))
... ... @@ -430,7 +430,6 @@
430 430  * Server send a downlink command to exit.
431 431  * User fast press the RED button 10 times.
432 432  
433 -
434 434  (((
435 435  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.
436 436  )))
... ... @@ -437,13 +437,16 @@
437 437  
438 438  
439 439  
440 -== 2.7 Sports Mode ==
578 +== 2.9 Transport Mode ==
441 441  
442 442  
581 +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.
443 443  
444 -== 2.8 LED Status ==
445 445  
446 446  
585 +== 2.10 LED Status ==
586 +
587 +
447 447  (% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
448 448  |=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off**
449 449  |(% 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
... ... @@ -458,11 +458,9 @@
458 458  |(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes
459 459  |(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A
460 460  
602 +== 2.11 Button Function ==
461 461  
462 462  
463 -== 2.9 Button Function ==
464 -
465 -
466 466  (% style="color:blue" %)**RESET button:**
467 467  
468 468  [[image:1664502835802-546.png]]
... ... @@ -481,11 +481,9 @@
481 481  |(% 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
482 482  |(% 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.
483 483  
623 +== 2.12 USB Port Function ==
484 484  
485 485  
486 -== 2.10 USB Port Function ==
487 -
488 -
489 489  The USB interface of TrackerD has below functions:
490 490  
491 491  * Power on the device
... ... @@ -493,9 +493,6 @@
493 493  * [[Configure Device>>||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]
494 494  * [[Upgrade Firmware>>||anchor="H5.UploadFirmware"]]
495 495  
496 -
497 -
498 -
499 499  = 3. Configure TrackerD via AT command or LoRaWAN downlink =
500 500  
501 501  
... ... @@ -568,16 +568,16 @@
568 568  
569 569  
570 570  
571 -=== 3.2.3 Set Sports Mode Packet transmission interval ===
705 +=== 3.2.3 Set Transport Mode Packet transmission interval ===
572 572  
573 573  
574 -Set sports packet transmit interval
708 +Set Transport Mode packet transmit interval
575 575  
576 576  * (% style="color:blue" %)**AT Command:**
577 577  
578 578  (% style="color:#037691" %)**AT+MTDC=xx. **
579 579  
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
714 +Example:  AT+MTDC=300000  **~-~->    ** Set Transport Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Transport mode, Default Value: 300000
581 581  
582 582  
583 583  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
... ... @@ -617,16 +617,16 @@
617 617  
618 618  
619 619  
620 -=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
754 +=== 3.2.6 Disable/Enable Transport Mode ===
621 621  
622 622  
623 -User can use this feature to check and set thread hole of movement detect
757 +Users can use this feature to enable/disable Transport Mode.
624 624  
625 625  * (% style="color:blue" %)**AT Command:**
626 626  
627 627  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
628 628  
629 -Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
763 +Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
630 630  
631 631  
632 632  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
... ... @@ -638,35 +638,38 @@
638 638  === 3.2.7 Set Positioning Mode ===
639 639  
640 640  
641 -SMOD define the how TrackerD scan and uplink date.
775 +SMOD define the how TrackerD scan and uplink data:
642 642  
643 -GPS室外定位模式：  设备默认模式，设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是3分钟定位，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。GPS还有一种logdata模式，在断网的情况下将数据存储下来，等到有网的时候，一次将数据以每10秒上报。
644 644  
645 -BLE室内定位模式：  设备入网后会发送device当前模式下的信息，随后立即定位发送数据包（默认是5秒，超过将发送无效数据），如果出现意外情况下，快速按键3下，将会发出报警消息（默认每3分钟发送一次）。
778 +* (% style="color:blue" %)**AT Command:**
646 646  
647 -GPS和BLE混动模式：设备入网后会发送device当前模式下的信息，随后立即判断是否在室内，如果是就进行BLE定位，不是就GPS定位。如果出现意外情况下，快速按键3下，将会发出报警消息（默认每分钟发送一次）。
780 +(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
648 648  
649 -运动模式：  设备入网后会发送device当前模式下的信息，随后发送GPS定位数据，设备判断是否在运动，没有运动传感器没有检测到动作，立即进入静止状态（默认20分钟），如果产生运动，将每5分钟发送一次数据，再第五分钟后检测设备有误运动，无将切换到静止状态，有立即发送数据。
782 +(% style="color:#037691" %)** aa:**
650 650  
784 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
785 +* (% style="color:red" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
786 +* (% 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.
651 651  
788 +(% style="color:#037691" %)**bb:**
652 652  
653 -* (% style="color:blue" %)**AT Command:**
790 +* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
791 +* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
654 654  
655 -(% style="color:#037691" %)**AT+SMOD=xx. **
793 +(% style="color:#037691" %)**cc:   **
656 656  
795 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
657 657  
658 - **Example:**
797 +(% style="color:blue" %)**Example:**
659 659  
660 - AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
799 + AT+ SMOD =1,0 ,0 ~-~->  GPS+ BAT+ State+Tem&Hum
800 + AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
801 + AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
661 661  
662 - AT+ SMOD =1,1    **~-~->**  GPS +BAT State
663 663  
664 - AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
665 -
666 -
667 667  * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
668 668  
669 -(% style="color:#037691" %)**0xA5 01 00**    (%%) ~/~/  Same as AT+ SMOD =1,0
806 +(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
670 670  
671 671  
672 672  
... ... @@ -683,7 +683,7 @@
683 683  
684 684  (% style="color:#037691" %)**AT+FTIME=xx**  (%%) **~-~-> ** Set to use xx as max fix time.
685 685  
686 -Example:  AT+FTIME=150
823 +**Example:**  AT+FTIME=150
687 687  
688 688  
689 689  * (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**
... ... @@ -692,7 +692,7 @@
692 692  
693 693  
694 694  
695 -=== 3.3.9 Set PDOP value for GPS fix accuracy ===
832 +=== 3.2.9 Set PDOP value for GPS fix accuracy ===
696 696  
697 697  
698 698  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.
... ... @@ -720,7 +720,7 @@
720 720  
721 721  * (% style="color:blue" %)**AT Command:**
722 722  
723 -(% style="color:#037691" %)**AT+CFM=xx. **
860 +(% style="color:#037691" %)**AT+CFM=xx**
724 724  
725 725  
726 726  **~ Example:**
... ... @@ -736,6 +736,27 @@
736 736  
737 737  
738 738  
876 +=== 3.2.10  Auto Send None-ACK messages ===
877 +
878 +
879 +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.
880 +
881 +
882 +* (% style="color:blue" %)**AT Command: AT+PNACKMD**
883 +
884 +The default factory setting is 0.
885 +
886 +
887 +**Command Example Function Response:**
888 +
889 +(% style="color:#037691" %)**AT+PNACKMD=1**  (%%) ~/~/  Poll None-ACK message OK
890 +
891 +
892 +* (% style="color:blue" %)**Downlink Command: 0x34**
893 +
894 +Example: 0x3401  ~/~/  Same as AT+PNACKMD=1
895 +
896 +
739 739  = 4. Setting for Different Scenarios =
740 740  
741 741  
... ... @@ -778,7 +778,7 @@
778 778  
779 779  (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location:
780 780  
781 -[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
939 +[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]]
782 782  
783 783  
784 784  Users need to use below files:
... ... @@ -815,6 +815,7 @@
815 815  [[image:1664503635019-941.png]]
816 816  
817 817  
976 +
818 818  * (% style="color:#037691" %)**Go to tools ~-~-> Boards ~-~-> Boards Manager**,(%%) **find the esp32 information and install it.**
819 819  
820 820  [[image:1664503715811-892.png]]
... ... @@ -879,8 +879,6 @@
879 879  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
880 880  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
881 881  
882 -
883 -
884 884  = 8.  Order Info =
885 885  
886 886  
... ... @@ -896,25 +896,19 @@
896 896  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
897 897  * (% style="color:red" %)**US915**(%%): Default frequency band US915
898 898  
899 -
900 -
901 -
902 902  = 9.  Packing Info =
903 903  
904 904  
905 -**(% style="color:#037691" %)Package Includes**:
1059 +(% style="color:#037691" %)**Package Includes**:
906 906  
907 907  * TrackerD LoRaWAN GPS/BLE Tracker x 1
908 908  * USB recharge & program cable x 1
909 909  
910 -**(% style="color:#037691" %)Dimensions and Weight**:
1064 +(% style="color:#037691" %)**Dimensions and Weight**:
911 911  
912 912  * Device Size: 85 x 48 x 15 cm
913 913  * Weight: 50g
914 914  
915 -
916 -
917 -
918 918  = 10. Support =
919 919  
920 920  
... ... @@ -921,9 +921,6 @@
921 921  * 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.
922 922  * 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]].
923 923  
924 -
925 -
926 -
927 927  = 11.  Reference =
928 928  
929 929  
... ... @@ -931,5 +931,4 @@
931 931  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
932 932  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
933 933  
934 -
935 935  
1665301570342-765.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.6 KB
Content
1665301636888-168.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +36.6 KB
Content
1665301687277-443.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.6 KB
Content
1665301786397-168.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.6 KB
Content
image-20221006181316-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +17.7 KB
Content
image-20221006181357-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +88.0 KB
Content
image-20221009160220-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +46.4 KB
Content
image-20221009160309-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +57.2 KB
Content
image-20221009234629-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +222.9 KB
Content
image-20221009234703-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +136.4 KB
Content