Last modified by Xiaoling on 2025/04/27 16:48

From version 84.11
edited by Xiaoling
on 2022/10/26 08:50
Change comment: There is no comment for this version
To version 55.1
edited by Edwin Chen
on 2022/10/06 18:45
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
... ... @@ -1,3 +1,5 @@
1 +== ==
2 +
1 1  (% style="text-align:center" %)
2 2  [[image:1664505654417-133.png]]
3 3  
... ... @@ -183,10 +183,8 @@
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  
188 +== 2.3 Positioning Mode(SMOD) ==
186 186  
187 -== 2.3  Positioning Mode(SMOD) ==
188 -
189 -
190 190  Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
191 191  
192 192  * (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
... ... @@ -196,33 +196,26 @@
196 196  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
197 197  
198 198  
199 +== 2.3 Uplink Payload ==
199 199  
200 -== 2.4  Uplink Payload ==
201 201  
202 +=== 2.3.1 Uplink FPORT~=5, Device Status ===
202 202  
203 -=== 2.4.1 Uplink FPORT~=5, Device Status ===
204 +Uplink the device configures with FPORT=5. Once LHT52 Joined the network, it will uplink this message to the server. After first uplink, LHT52 will uplink Device Status every 12 hours.
204 204  
206 +|=**Size (bytes)**|=**1**|=**2**|=**1**|=**1**|=**2**
207 +|**Value**|Sensor Model|Firmware Version|Frequency Band|Sub-band|BAT
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.
209 +[[image:image-20221006181357-2.png]]
207 207  
208 -Use can also get the Device Status uplink through the downlink command: **Downlink:  0x2301**
211 +Example Payload (FPort=5):  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT52%20-%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20User%20Manual/WebHome/image-20220621105116-11.png?rev=1.1||alt="image-20220621105116-11.png"]]
209 209  
213 +**Sensor Model**: For TrackerD, this value is 0x13.
210 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
215 +**Firmware Version**: 0x0100, Means: v1.0.0 version.
214 214  
215 -[[image:1665301570342-765.png]]
217 +**Frequency Band**:
216 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 226  *0x01: EU868
227 227  
228 228  *0x02: US915
... ... @@ -243,68 +243,34 @@
243 243  
244 244  *0x0a: AS923-3
245 245  
246 -Sub- Band:value 0x00~~0x08(only forAU915,US915,Others are 0xFF)
239 +**Sub-Band**: value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
247 247  
248 -(% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD.
241 +**BAT**: shows the battery voltage for TrackerD.
249 249  
243 +Ex1: 0x0B3A = 2874mV
250 250  
251 -(% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV
252 -
253 253  Use can also get the Device Status uplink through the downlink command:
254 254  
255 255  
256 -(% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40
248 +=== 2.3.2 Uplink FPORT~=2, Realtime GNSS Positioning ===
257 257  
258 -(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %)
259 -|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit
260 -|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings
261 261  
262 -(% style="color:blue" %)** SMOD:**
251 +The default uplink payload includes totally 11 bytes. (User can use AT+SMOD=1,0 to enable uploading on-board Temperature and humidity value, and total payload will be 15 bytes, please note 15 bytes won't work on DR0 on US915/AU915 frequency band. )
263 263  
264 -(% style="color:red" %)** 1 :** (%%) GPS ONLY
265 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:260px" %)
286 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit
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
257 +)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:50px" %)1|(% style="width:88px" %)(((
258 +2(optional)
300 300  )))|(% style="width:87px" %)(((
301 -2
260 +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:"]]
264 +)))|(% 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]]
266 +[[image:1664501958445-288.png]]
308 308  
309 309  
310 310  ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ====
... ... @@ -316,8 +316,8 @@
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:"]]
278 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit|(% style="width:100px" %)5 bits
279 +|=(% 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  
... ... @@ -331,14 +331,15 @@
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:
293 +2.  When enable 9-axis motion sensor, 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:
335 335  
336 336  
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  
300 +4.  While GPS can't get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00:
301 +
342 342  [[image:1664502166010-515.png]]
343 343  
344 344  
... ... @@ -345,15 +345,15 @@
345 345  
346 346  ==== (% style="color:blue" %)**Alarm:**(%%) ====
347 347  
348 -**Example: ** 0x4B & 0x40 >> 6 = 0x01
308 +Example:  0x4B & 0x40 >> 6 = 0x01
349 349  
350 350  
351 351  ==== (% style="color:blue" %)**BAT:**(%%) ====
352 352  
353 -**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV).
313 +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: \
316 +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  
359 359  * > 4.0v :  80% ~~ 100%
... ... @@ -362,37 +362,20 @@
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 -
384 384  Enable/Disable LED activity for uplink
385 385  
386 386  (((
387 -(% style="color:#037691" %)**0x00:**  (%%) Disable LED indicator.
331 +0x00:  Disable LED indicator.
388 388  )))
389 389  
390 390  (((
391 -(% style="color:#037691" %)**0x01:**  (%%) Enable LED indicator (Default Value)
335 +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) ===
350 +=== 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  
354 +=== 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]]
357 +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)**
... ... @@ -474,7 +474,7 @@
474 474  [[image:1664502425687-834.png]]
475 475  
476 476  
477 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
378 +* (% 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,7 +482,7 @@
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. Add Payload format in TTN V3 ===
386 +=== 2.3.5 Add Payload format in TTN V3 ===
486 486  
487 487  
488 488  In TTN V3, use can add a custom payload so it shows friendly.
... ... @@ -493,9 +493,8 @@
493 493  [[image:1664502649601-895.png]]
494 494  
495 495  
496 -Add the decoder from this link: 
397 +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 ==
406 +== 2.4 Integrate with Datacake ==
507 507  
508 508  
409 +(((
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.
411 +)))
510 510  
413 +(((
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]]
415 +)))
512 512  
417 +
513 513  [[image:1664502695771-538.png]]
514 514  
515 515  
516 516  
517 -== 2.6 Integrate with Tago ==
422 +== 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.
425 +(((
426 +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.
427 +)))
521 521  
429 +(((
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]]
431 +)))
523 523  
524 524  
525 -
526 526  [[image:1664502715371-321.png]]
527 527  
528 528  
529 529  
530 -== 2. Datalog Feature ==
438 +== 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.
447 +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,7 +560,7 @@
560 560  Two ways to exit alarm mode:
561 561  )))
562 562  
563 -* Server sends a downlink command to exit.
455 +* Server send a downlink command to exit.
564 564  * User fast press the RED button 10 times.
565 565  
566 566  (((
... ... @@ -569,16 +569,15 @@
569 569  
570 570  
571 571  
572 -== 2.9 Transport Mode ==
464 +== 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.
467 +In Sports 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  
577 577  
470 +== 2.8 LED Status ==
578 578  
579 -== 2.10 LED Status ==
580 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,7 +593,7 @@
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 ==
487 +== 2.9 Button Function ==
597 597  
598 598  
599 599  (% style="color:blue" %)**RESET button:**
... ... @@ -614,7 +614,7 @@
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 ==
508 +== 2.10 USB Port Function ==
618 618  
619 619  
620 620  The USB interface of TrackerD has below functions:
... ... @@ -648,9 +648,11 @@
648 648  [[image:1664503022490-662.png]]
649 649  
650 650  
542 +
651 651  [[image:1664503035713-500.png]]
652 652  
653 653  
546 +
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 ===
590 +=== 3.2.3 Set Sports Mode Packet transmission interval ===
698 698  
699 699  
700 -Set Transport Mode packet transmit interval
593 +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
599 +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 ===
639 +=== 3.2.6 Disable/Enable movement detect (Debug Only) ===
747 747  
748 748  
749 -Users can use this feature to enable/disable Transport Mode.
642 +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.
648 +Example:  AT+ INTWK =1  **~-~->   ** Enable detect movement.
756 756  
757 757  
758 758  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
... ... @@ -764,38 +764,26 @@
764 764  === 3.2.7 Set Positioning Mode ===
765 765  
766 766  
767 -SMOD define how TrackerD scan and uplink data:
660 +SMOD define the how TrackerD scan and uplink data:
768 768  
769 769  
770 770  * (% style="color:blue" %)**AT Command:**
771 771  
772 -(% style="color:#037691" %)**AT+SMOD=aa,bb,cc**
665 +(% style="color:#037691" %)**AT+SMOD=xx. **
773 773  
774 -(% style="color:#037691" %)** aa:**
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.
668 + **Example:**
779 779  
780 -(% style="color:#037691" %)**bb:**
670 + AT+ SMOD =1,0  **~-~-> ** GPS+ BAT+ State+Tem&Hum
781 781  
782 -* (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
783 -* (% style="color:red" %)**1 :**(%%)  GPS +BAT State
672 + AT+ SMOD =1,1    **~-~->**  GPS +BAT State
784 784  
785 -(% style="color:#037691" %)**cc:   **
674 + AT+ SMOD =2,3    **~-~->**  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。
786 786  
787 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
788 788  
789 -(% style="color:blue" %)**Example:**
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
794 -
795 -
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
679 +(% 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
696 +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 ===
705 +=== 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**
733 +(% 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]]
791 +[[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,7 @@
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  
892 +
1066 1066  = 8.  Order Info =
1067 1067  
1068 1068  
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-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