Skip to Content
Last modified by Xiaoling on 2025/04/27 16:48
From version 84.13
edited by Xiaoling
on 2022/10/26 08:59
Change comment: There is no comment for this version
To version 103.1
edited by Bei Jinggeng
on 2022/11/04 09:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -189,9 +189,9 @@
189 189  
190 190  Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported.
191 191  
192 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
193 -* (% style="color:#037691" %)**BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
194 -* (% style="color:#037691" %)**GPS/BLE Hybrid:   **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
192 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
193 +* (% style="color:#037691" %)**BLE or WiFi ONLY:            **(%%)** **Only obtain iBeacon info via BLE and uplink  or obtain wifi ssid info via WiFi and uplink. Design for Indoor tracking.
194 +* (% style="color:#037691" %)**GPS/BLE Hybrid:                        **(%%)Combination for Indoor and Outdoor tracking. Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning.
195 195  
196 196  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
197 197  
... ... @@ -279,7 +279,9 @@
279 279  
280 280  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
281 281  
282 +(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
282 282  
284 +
283 283  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
284 284  
285 285  (% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
... ... @@ -294,8 +294,12 @@
294 294  
295 295  (% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %)
296 296  |=(% scope="row" style="width: 60px;" %)(((
297 -**Size(bytes)**)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
298 -2)))|(% style="width:30px" %)(((2)))
299 +**Size(bytes)**
300 +)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)(((
301 +2
302 +)))|(% style="width:30px" %)(((
303 +2
304 +)))
299 299  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
300 300  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
301 301  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]]
... ... @@ -388,7 +388,6 @@
388 388  )))
389 389  
390 390  
391 -
392 392  ==== (% style="color:blue" %)**Hum:**(%%) ====
393 393  
394 394  0202 = //if (0x0202 & 0x8000 = 0 ):  value =// 0x0202 / 100 = +514 ⇒ 51.4 degree
... ... @@ -406,10 +406,10 @@
406 406  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)
407 407  
408 408  
409 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %)
410 -|=(% scope="row" style="width: 50px;" %)(((
414 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %)
415 +|=(% scope="row" style="width: 60px;" %)(((
411 411  **Size(bytes)**
412 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1
417 +)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1
413 413  |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)(((
414 414  [[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
415 415  )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]
... ... @@ -428,12 +428,12 @@
428 428  (% style="color:red" %)**Note for this mode:**
429 429  
430 430  * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
431 -* 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 +* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages.
432 432  * 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
433 433  
434 434  The payload is 15 bytes, as below.
435 435  
436 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
441 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %)
437 437  |=(% scope="row" %)(((
438 438  **Size(bytes)**
439 439  )))|4|4|2|1|1|1|1|1
... ... @@ -478,11 +478,33 @@
478 478  * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon.
479 479  * (% style="color:#037691" %)**RSSI:  ** (%%) The RSSI from the strongest iBeacon.
480 480  
481 -=== 2.4.6  Add Payload format in TTN V3 ===
486 +=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID ===
482 482  
483 483  
484 -In TTN V3, use can add a custom payload so it shows friendly.
489 +TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
485 485  
491 +
492 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
493 +|=(% scope="row" style="width: 60px;" %)(((
494 +**Size(bytes)**
495 +)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
496 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
497 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
498 +)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
499 +
500 +(% class="wikigeneratedid" %)
501 +[[image:1667288597595-714.png||height="212" width="1151"]]
502 +
503 +
504 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
505 +* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
506 +* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
507 +
508 +=== 2.4.7  Add Payload format in TTN V3 ===
509 +
510 +
511 +In TTN V3, user can add a custom payload so it shows friendly.
512 +
486 486  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
487 487  
488 488  
... ... @@ -604,8 +604,8 @@
604 604  [[image:1664502854406-763.png]]
605 605  
606 606  
607 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %)
608 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description**
634 +(% border="1" style="background-color:#ffffcc; color:green; width:510px" %)
635 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description**
609 609  |(% style="width:135px" %)Send Alarm|(% style="width:220px" %)Keep Pressing (% style="color:red" %)**RED**(%%) button for more than 5 seconds|(% style="width:265px" %)Enter Alarm Mode.  See [[Alarm Mode>>||anchor="H2.6AlarmMode"]]
610 610  |(% 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
611 611  |(% 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.
... ... @@ -769,9 +769,9 @@
769 769  
770 770  (% style="color:#037691" %)** aa:**
771 771  
772 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
773 -* (% style="color:red" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
774 -* (% 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.
799 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
800 +* (% style="color:red" %)**2: BLE or WiFi ONLY:                     **(%%)Only obtain iBeacon info via BLE and uplink  or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking.
801 +* (% 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.
775 775  
776 776  (% style="color:#037691" %)**bb:**
777 777  
... ... @@ -781,6 +781,7 @@
781 781  (% style="color:#037691" %)**cc:   **
782 782  
783 783  * (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
811 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
784 784  
785 785  (% style="color:blue" %)**Example:**
786 786  
... ... @@ -787,6 +787,7 @@
787 787   AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
788 788   AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
789 789   AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
818 + AT+ SMOD =2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
790 790  
791 791  
792 792  * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
... ... @@ -857,7 +857,7 @@
857 857  
858 858  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
859 859  
860 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
889 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ CFM =1
861 861  
862 862  
863 863  
... ... @@ -886,7 +886,7 @@
886 886  === 3.2.11  Set BLEMASK to filter BLE iBeacon ===
887 887  
888 888  
889 -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.
918 +BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID.
890 890  
891 891  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
892 892  
... ... @@ -896,13 +896,40 @@
896 896  
897 897   (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
898 898  
928 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
899 899  
900 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**
930 +Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
901 901  
902 -Example: 0xA5010203040506    ~/~/ Set BLEMASK to 123456
932 +=== 3.2.12  Set WiFIMASK to filter WiFi SSID ===
903 903  
904 904  
935 +WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
905 905  
937 +(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
938 +
939 +(% style="color:blue" %)**AT Command:**
940 +
941 + (% style="color:#037691" %)**AT+ WiFiMASK =123456**    (%%) ~/~/ Set WiFiMASK = 123456
942 +
943 + (% style="color:#037691" %)**AT+ WiFiMASK =0**       (%%) ~/~/ disable WiFiMASK
944 +
945 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
946 +
947 +Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
948 +
949 +=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
950 +
951 +
952 +Users can use this feature to enable/disable Information printing.
953 +
954 +(% style="color:blue" %)**AT Command:**
955 +
956 +
957 +(% style="color:#037691" %)**AT+ SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
958 +
959 +Example: AT+ SHOWID =1 ~-~-> Enable Information printing.
960 +
961 +
906 906  = 4. Setting for Different Scenarios =
907 907  
908 908  
... ... @@ -1059,6 +1059,54 @@
1059 1059  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1060 1060  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1061 1061  
1118 +== 7.3 Notes on using different serial port tools for TrackerD ==
1119 +
1120 +
1121 +=== **Serial port utility** ===
1122 +
1123 +
1124 +Serial port utility requires you to automatically add data streams.
1125 +
1126 +Need to adjust the data stream to RTS/CTS on physical restart.
1127 +
1128 +
1129 +(% class="wikigeneratedid" %)
1130 +[[image:image-20221102140621-1.png]]
1131 +
1132 +
1133 +When using AT commands, the data flow needs to be adjusted to XON/XOFF
1134 +
1135 +
1136 +[[image:image-20221102140638-2.png]]
1137 +
1138 +
1139 +
1140 +=== **SecureCRT** ===
1141 +
1142 +
1143 +The default command window of SecureCRT is not displayed. Entering a command requires a complete input of the entire command. You can open the command window in the view.
1144 +
1145 +
1146 +[[image:image-20221102140704-3.png]]
1147 +
1148 +
1149 +[[image:image-20221102140712-4.png]]
1150 +
1151 +
1152 +
1153 +=== **PUTTY** ===
1154 +
1155 +
1156 +[[image:image-20221102140748-5.png]]
1157 +
1158 +
1159 +Since putty does not have a command window, you need to fill in the complete command externally, and then copy it to putty.The information copied outside can be pasted by right-clicking the mouse in putty.
1160 +
1161 +
1162 +[[image:image-20221102140801-6.png]]
1163 +
1164 +
1165 +
1062 1062  = 8.  Order Info =
1063 1063  
1064 1064  
... ... @@ -1084,7 +1084,7 @@
1084 1084  
1085 1085  (% style="color:#037691" %)**Dimensions and Weight**:
1086 1086  
1087 -* Device Size: 85 x 48 x 15 cm
1191 +* Device Size: 85 x 48 x 15 mm
1088 1088  * Weight: 50g
1089 1089  
1090 1090  = 10. Support =
... ... @@ -1099,5 +1099,3 @@
1099 1099  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1100 1100  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1101 1101  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1102 -
1103 -
1667288597595-714.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +27.9 KB
Content
image-20221102140621-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +46.1 KB
Content
image-20221102140638-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +40.8 KB
Content
image-20221102140704-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +15.5 KB
Content
image-20221102140712-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +73.2 KB
Content
image-20221102140748-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +56.0 KB
Content
image-20221102140801-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +21.0 KB
Content