Skip to Content
Last modified by Xiaoling on 2023/12/27 09:15
From version 113.2
edited by Xiaoling
on 2022/11/09 15:43
Change comment: There is no comment for this version
To version 84.19
edited by Xiaoling
on 2022/10/26 09:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -127,7 +127,7 @@
127 127  
128 128  
129 129  
130 -= 2.  Use TrackerD =
130 += 2.1 Use TrackerD =
131 131  
132 132  
133 133  == 2.1 How it works? ==
... ... @@ -195,9 +195,9 @@
195 195  
196 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 or WiFi ONLY:            **(%%)** **Only obtain iBeacon info via BLE and uplink  or obtain wifi ssid info via WiFi 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.
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 202  Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]].
203 203  
... ... @@ -285,9 +285,7 @@
285 285  
286 286  (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon
287 287  
288 -(% style="color:red" %)** 2：**  (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%)  
289 289  
290 -
291 291  (% style="color:#037691" %)**Status Field (total 1 byte)**(%%):  0x02
292 292  
293 293  (% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %)
... ... @@ -339,6 +339,8 @@
339 339  * Latitude: 02863D68  ⇒  //if (0x//02863D68//& 0x80000000 = 0 )~://  //value = 02863D68 /1000000 = 42.351976//
340 340  * Longitude: FAC29BAF  ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~://  //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57//
341 341  
340 +
341 +
342 342  (% style="color:red" %)**Important note:**
343 343  
344 344  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.
... ... @@ -445,7 +445,7 @@
445 445  (% style="color:red" %)**Note for this mode:**
446 446  
447 447  * a) TrackerD will do an ACK check for data records sending to make sure every data arrive server.
448 -* 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.
448 +* 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.
449 449  * 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
450 450  
451 451  The payload is 15 bytes, as below.
... ... @@ -497,35 +497,11 @@
497 497  
498 498  
499 499  
500 -=== 2.4.6  Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID（Since firmware 1.4.1） ===
500 +=== 2.4.6  Add Payload format in TTN V3 ===
501 501  
502 502  
503 -TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **WiFi** so TrackerD will scan WiFi and find the strongest WiFi info and uplink.
503 +In TTN V3, use can add a custom payload so it shows friendly.
504 504  
505 -
506 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %)
507 -|=(% scope="row" style="width: 60px;" %)(((
508 -**Size(bytes)**
509 -)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1
510 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)(((
511 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]]
512 -)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]]
513 -
514 -(% class="wikigeneratedid" %)
515 -[[image:1667288597595-714.png||height="212" width="1151"]]
516 -
517 -
518 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).
519 -* (% style="color:#037691" %)**SSID:      **(%%)WiFi name.
520 -* (% style="color:#037691" %)**RSSI:      **(%%)The RSSI from the strongest WiFi.
521 -
522 -
523 -
524 -=== 2.4.7  Add Payload format in TTN V3 ===
525 -
526 -
527 -In TTN V3, user can add a custom payload so it shows friendly.
528 -
529 529  In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**
530 530  
531 531  
... ... @@ -753,7 +753,7 @@
753 753  
754 754  * (% style="color:blue" %)**Downlink Payload (prefix 0x03):**
755 755  
756 -(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+MTDC=3000000
732 +(% style="color:#037691" %)**0x03 00 01 2C**  (%%) ~/~/  Same as AT+ MTDC=3000000
757 757  
758 758  
759 759  
... ... @@ -797,12 +797,12 @@
797 797  
798 798  (% style="color:#037691" %)**AT+INTWK=xx.  (Disable (0), Enable (1), default:0)**
799 799  
800 -Example:  AT+INTWK=1  **~-~->   ** Enable Transport Mode.
776 +Example:  AT+ INTWK =1  **~-~->   ** Enable Transport Mode.
801 801  
802 802  
803 803  * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**
804 804  
805 -(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+INTWK=1
781 +(% style="color:#037691" %)**0xAF 01 ** (%%) ~/~/  Same as AT+ INTWK =1
806 806  
807 807  
808 808  
... ... @@ -818,36 +818,29 @@
818 818  
819 819  (% style="color:#037691" %)** aa:**
820 820  
821 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)Only get and uplink GPS location info.
822 -* (% 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.
823 -* (% 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 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings):    **(%%)only get and uplink GPS location info.
798 +* (% style="color:red" %)**2: BLE ONLY:              **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking.
799 +* (% 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.
824 824  
825 825  (% style="color:#037691" %)**bb:**
826 826  
827 827  * (% style="color:red" %)**0 :  **(%%)GPS+ BAT+ State+Tem&Hum
828 -
829 829  * (% style="color:red" %)**1 :**(%%)  GPS +BAT State
830 830  
831 831  (% style="color:#037691" %)**cc:   **
832 832  
833 -* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
834 -
835 -* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%))  
808 +* (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State  
836 836  
837 837  (% style="color:blue" %)**Example:**
838 838  
839 - AT+SMOD=1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
812 + AT+ SMOD =1,0,0 ~-~->  GPS+ BAT+ State+Tem&Hum
813 + AT+ SMOD =1,1,0 ~-~->  GPS +BAT State
814 + AT+ SMOD =2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
840 840  
841 - AT+SMOD=1,1,0 ~-~->  GPS +BAT State
842 842  
843 - AT+SMOD=2,0,1 ~-~->  (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State
844 -
845 - AT+SMOD=2,0,2 ~-~->  (WiFi)SSID+Rssi+BAT+State
846 -
847 -
848 848  * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):**
849 849  
850 -(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+SMOD=1,0,0
819 +(% style="color:#037691" %)**0xA5 01 00 00**    (%%) ~/~/  Same as AT+ SMOD =1,0,0
851 851  
852 852  
853 853  
... ... @@ -906,14 +906,14 @@
906 906  
907 907  **~ Example:**
908 908  
909 - AT+CFM=0    **~-~->   ** Disable confirmation
878 + AT+ CFM=0    **~-~->   ** Disable confirmation
910 910  
911 - AT+CFM=1    **~-~->  ** Enable confirmation
880 + AT+ CFM=1    **~-~->  ** Enable confirmation
912 912  
913 913  
914 914  * (% style="color:blue" %)**Downlink Payload (prefix 0x05):**
915 915  
916 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+CFM=1
885 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/  Same as AT+ SMOD =1
917 917  
918 918  
919 919  
... ... @@ -942,7 +942,7 @@
942 942  === 3.2.11  Set BLEMASK to filter BLE iBeacon ===
943 943  
944 944  
945 -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.
914 +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.
946 946  
947 947  (% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.**
948 948  
... ... @@ -952,59 +952,13 @@
952 952  
953 953   (% style="color:#037691" %)**AT+BLEMASK=0**  (%%) ~/~/ disable BLEMASK
954 954  
955 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1）**
956 956  
957 -Example: 0xB2010203040506    ~/~/ Set BLEMASK to 123456
925 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**
958 958  
927 +Example: 0xA5010203040506    ~/~/ Set BLEMASK to 123456
959 959  
960 960  
961 -=== 3.2.12  Set WiFIMASK to filter WiFi SSID（Since firmware 1.4.1） ===
962 962  
963 -
964 -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 as prefix. It will ignore all other WiFi which doesn’t contact 123456 in the SSID.
965 -
966 -(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.**
967 -
968 -(% style="color:blue" %)**AT Command:**
969 -
970 - (% style="color:#037691" %)**AT+WiFiMASK=123456**    (%%) ~/~/ Set WiFiMASK = 123456
971 -
972 - (% style="color:#037691" %)**AT+WiFiMASK=0**       (%%) ~/~/ disable WiFiMASK
973 -
974 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1）**
975 -
976 -Example: 0xB3010203040506    ~/~/ Set WiFiMASK to 123456
977 -
978 -
979 -
980 -=== 3.2.13 Disable/Enable Information printing（Since firmware 1.4.1） ===
981 -
982 -
983 -Users can use this feature to enable/disable Information printing.
984 -
985 -(% style="color:blue" %)**AT Command:**
986 -
987 -(% style="color:#037691" %)**AT+SHOWID=XX         **(%%) ~/~/(Disable (0), Enable (1), default:0)
988 -\\Example: AT+SHOWID=1 ~-~-> Enable Information printing.
989 -
990 -
991 -
992 -=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915（Since firmware 1.4.1） ===
993 -
994 -
995 -The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network.
996 -
997 -(% style="color:blue" %)**AT Command:**
998 -
999 -(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode
1000 -
1001 -
1002 -(% style="color:blue" %)**Downlink Payload:0X24**(%%)
1003 -
1004 -Example: 0x24 01 ~/~/ Same as AT+CHE=1
1005 -
1006 -
1007 -
1008 1008  = 4. Setting for Different Scenarios =
1009 1009  
1010 1010  
... ... @@ -1161,75 +1161,11 @@
1161 1161  |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14
1162 1162  |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15
1163 1163  
1164 -== 7.3 Notes on using different serial port tools for TrackerD ==
1165 1165  
1166 1166  
1167 -=== **Serial port utility** ===
1089 += 8.  Order Info =
1168 1168  
1169 1169  
1170 -Serial port utility requires you to automatically add data streams.
1171 -
1172 -Need to adjust the data stream to RTS/CTS on physical restart.
1173 -
1174 -
1175 -(% class="wikigeneratedid" %)
1176 -[[image:image-20221102140621-1.png]]
1177 -
1178 -
1179 -When using AT commands, the data flow needs to be adjusted to XON/XOFF
1180 -
1181 -
1182 -[[image:image-20221102140638-2.png]]
1183 -
1184 -
1185 -
1186 -=== **SecureCRT** ===
1187 -
1188 -
1189 -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.
1190 -
1191 -
1192 -[[image:image-20221102140704-3.png]]
1193 -
1194 -
1195 -[[image:image-20221102140712-4.png]]
1196 -
1197 -
1198 -
1199 -=== **PUTTY** ===
1200 -
1201 -
1202 -[[image:image-20221102140748-5.png]]
1203 -
1204 -
1205 -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.
1206 -
1207 -
1208 -[[image:image-20221102140801-6.png]]
1209 -
1210 -
1211 -= 8  Trouble Shooting =
1212 -
1213 -== 8.1 TDC is changed to 4294947296 and cause no uplink. ==
1214 -
1215 -Before firmware v1.4.0: When the Transport Mode is enabled (**AT+INTWK=1**), the **TDC** needs to be greater than **MTDC**, otherwise, TDC setting will because 4294947296 after wakre up from motion. This bug is fixed in firmware v1.4.1
1216 -
1217 -
1218 -== 8.2 Device not able get AT Command or show output after wake up from deep sleep mode ==
1219 -
1220 -ESP32 is not able to accept the Interrupt from UART after wake up from deep sleep mode. User need to press the button (one click) and trackerD will be able to accept UART command, it there is no action in UART for 15 seconds. it will go to deep sleep mode.
1221 -
1222 -
1223 -== 8.3 The reason why it has been restarted after upgrading（V.1.4.1） ==
1224 -
1225 -If it is V1.4.0 and the previous version, new partitions need to be loaded when upgrading. The new version of the software is stored in the partition package. The upgrade method is shown in the figure
1226 -
1227 -[[image:image-20221107145243-1.png||height="695" width="443"]]
1228 -
1229 -
1230 -= 9.  Order Info =
1231 -
1232 -
1233 1233  Part Number: (% style="color:blue" %)**TrackerD-XXX**
1234 1234  
1235 1235  (% style="color:blue" %)**XXX**(%%): The default frequency band
... ... @@ -1242,9 +1242,11 @@
1242 1242  * (% style="color:red" %)**AU915**(%%): Default frequency band AU915
1243 1243  * (% style="color:red" %)**US915**(%%): Default frequency band US915
1244 1244  
1245 -= 10.  Packing Info =
1246 1246  
1247 1247  
1106 += 9.  Packing Info =
1107 +
1108 +
1248 1248  (% style="color:#037691" %)**Package Includes**:
1249 1249  
1250 1250  * TrackerD LoRaWAN GPS/BLE Tracker x 1
... ... @@ -1252,18 +1252,22 @@
1252 1252  
1253 1253  (% style="color:#037691" %)**Dimensions and Weight**:
1254 1254  
1255 -* Device Size: 85 x 48 x 15 mm
1116 +* Device Size: 85 x 48 x 15 cm
1256 1256  * Weight: 50g
1257 1257  
1258 -= 11. Support =
1259 1259  
1260 1260  
1121 += 10. Support =
1122 +
1123 +
1261 1261  * 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.
1262 1262  * 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]].
1263 1263  
1264 -= 12.  Reference =
1265 1265  
1266 1266  
1129 += 11.  Reference =
1130 +
1131 +
1267 1267  * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]]
1268 1268  * **[[Source Code>>https://github.com/dragino/TrackerD]] **
1269 1269  * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]]
1667288597595-714.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -27.9 KB
Content
image-20221102140621-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -46.1 KB
Content
image-20221102140638-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -40.8 KB
Content
image-20221102140704-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -15.5 KB
Content
image-20221102140712-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -73.2 KB
Content
image-20221102140748-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -56.0 KB
Content
image-20221102140801-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -21.0 KB
Content
image-20221107145243-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -107.3 KB
Content