Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Bei Jinggeng on 2025/07/23 11:03
From version 81.1
edited by Edwin Chen
on 2022/10/22 00:24
on 2022/10/22 00:24
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 42 removed)
- 1664501652064-326.png
- 1664501677253-891.png
- 1664501711466-918.png
- 1664501721248-725.png
- 1664501734705-405.png
- 1664501784668-703.png
- 1664501958445-288.png
- 1664502116362-706.png
- 1664502166010-515.png
- 1664502425687-834.png
- 1664502649601-895.png
- 1664502676891-606.png
- 1664502695771-538.png
- 1664502715371-321.png
- 1664502835802-546.png
- 1664502854406-763.png
- 1664502999401-486.png
- 1664503022490-662.png
- 1664503035713-500.png
- 1664503047675-651.png
- 1664503563660-578.png
- 1664503574618-659.png
- 1664503593459-435.png
- 1664503611848-385.png
- 1664503635019-941.png
- 1664503715811-892.png
- 1664503752288-974.png
- 1664503794261-827.png
- 1664503808294-336.png
- 1664503824081-592.png
- 1664503831430-500.png
- 1664505654417-133.png
- 1665301570342-765.png
- 1665301636888-168.png
- 1665301687277-443.png
- 1665301786397-168.png
- image-20221006181316-1.png
- image-20221006181357-2.png
- image-20221009160220-1.png
- image-20221009160309-2.png
- image-20221009234629-1.png
- image-20221009234703-2.png
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.Xiaoling - Content
-
... ... @@ -1,13 +7,6 @@ 1 -(% style="text-align:center" %) 2 -[[image:1664505654417-133.png]] 3 - 4 - 5 - 6 - 7 7 (% class="wikigeneratedid" %) 8 8 **Table of Contents:** 9 9 10 -{{toc/}} 11 11 12 12 13 13 ... ... @@ -14,10 +14,9 @@ 14 14 15 15 = 1. Introduction = 16 16 10 +== 1.1 OverView == 17 17 18 -== 1.1 What is TrackerD == 19 19 20 - 21 21 ((( 22 22 TrackerD is an (% style="color:blue" %)**Open Source LoRaWAN Tracker**(%%) based on (% style="color:blue" %)**ESP32 MCU**(%%) and (% style="color:blue" %)**Semtech LoRa Wireless Chip**. 23 23 ))) ... ... @@ -25,14 +25,10 @@ 25 25 ((( 26 26 In TrackerD, there are various sensors such as GPS, WiFi, BLE, Temperature, Humidity, Motion Detection, and Buzzer. User can use TrackerD for different tracking scenario. 27 27 28 -((( 29 29 TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution. 30 -))) 31 31 32 -((( 33 33 The LoRa wireless technology used in TrackerD allows the user to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional tracking services. 34 34 ))) 35 -))) 36 36 37 37 ((( 38 38 TrackerD is equipped with a (% style="color:blue" %)**1000mAh Li-on rechargeable battery**(%%). Each TrackerD has a worldwide unique OTAA keys to join the LoRaWAN network. ... ... @@ -46,7 +46,6 @@ 46 46 (% style="color:red" %)**Note: LoRaWAN server can be a general LoRaWAN server other than TTN.** 47 47 48 48 49 - 50 50 == 1.2 Specifications == 51 51 52 52 ... ... @@ -61,11 +61,13 @@ 61 61 * EEPROM: 520 KB 62 62 * Clock Speed: 32Mhz 63 63 51 + 64 64 (% style="color:blue" %)**Common DC Characteristics:** 65 65 66 66 * Supply Voltage: 5V via USB port or Internal li-on battery 67 67 * Operating Temperature: -40 ~~ 60°C 68 68 57 + 69 69 (% style="color:blue" %)**LoRa Spec:** 70 70 71 71 * Frequency Range, ... ... @@ -87,10 +87,12 @@ 87 87 * Packet engine up to 256 bytes with CRC. 88 88 * LoRaWAN 1.0.3 Specification 89 89 79 + 90 90 (% style="color:blue" %)**Battery:** 91 91 92 92 * 1000mA Li-on Battery power (for model TrackerD) 93 93 84 + 94 94 (% style="color:blue" %)**Power Consumption** 95 95 96 96 * Sleeping Mode: 200uA ... ... @@ -97,6 +97,9 @@ 97 97 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm 98 98 * Tracking: max: 38mA 99 99 91 + 92 + 93 + 100 100 == 1.3 Features == 101 101 102 102 ... ... @@ -103,7 +103,7 @@ 103 103 * LoRaWAN 1.0.3 Class A 104 104 * ESP32 PICO D4 105 105 * SX1276/78 Wireless Chip 106 -* Arduino IDE Compatible 100 +* Arduino IDE Compatible 107 107 * Open source hardware / software 108 108 * Regular/ Real-time GPS,BLE,WIFI tracking 109 109 * Built-in3 axis accelerometer (LIS3DH) ... ... @@ -115,6 +115,8 @@ 115 115 * Tri-color LED, Alarm button 116 116 * Datalog 117 117 112 + 113 + 118 118 == 1.4 Applications == 119 119 120 120 ... ... @@ -121,688 +121,536 @@ 121 121 * Logistics and Supply Chain Management 122 122 * Human tracking 123 123 124 -= 2.1 Use TrackerD = 125 125 126 126 127 -== 2.1 How it works? == 128 128 123 +1. Use TrackerD 124 +11. How it works? 129 129 126 + 130 130 TrackerD is configured as LoRaWAN OTAA Class A GPS tracker by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, user need to input the OTAA keys in the LoRaWAN IoT server and push reset button of TrackerD (next to USB port). TrackerD will wake up and auto join the network via OTAA. 131 131 132 132 130 +1. 131 +11. Quick guide to connect to LoRaWAN server 133 133 134 - ==2.2Quickguideto connect to LoRaWAN server==133 +Here is an example for how to join the [[TTNv3 LoRaWAN Network>>url:https://eu1.cloud.thethings.network]]. Below is the network structure, we use LPS8N as LoRaWAN gateway in this example. 135 135 136 136 137 - Hereisanexamplefor how to join the[[TTNv3RaWAN Network>>url:https://eu1.cloud.thethings.network]]. Belowis the network structure, we use LPS8Nas LoRaWANgateway in this example.136 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]] 138 138 139 139 140 -[[image:1664501652064-326.png]] 141 - 142 - 143 - 144 144 The LPS8N is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. What the rest need to is register this device in TTN V3: 145 145 141 +**Step 1**: Create a device in TTN V3 with the OTAA keys from TrackerD. 146 146 147 -(% style="color:blue" %)**Step 1**:(%%) Create a device in TTN V3 with the OTAA keys from TrackerD. 148 - 149 149 Each TrackerD is shipped with a sticker with the default device EUI as below: 150 150 145 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]] 151 151 152 -[[image:1664501677253-891.png]] 153 153 154 154 149 + 155 155 Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot: 156 156 157 157 158 - **__Add APP EUI in the application:__**153 +Add APP EUI in the application 159 159 155 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]] 160 160 161 -[[image: 1664501711466-918.png]]157 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]] 162 162 163 163 160 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image005.png]] 164 164 165 -[[image:1664501721248-725.png]] 166 166 167 167 168 - [[image:1664501734705-405.png]]164 +Add APP KEY and DEV EUI 169 169 166 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image006.png]] 170 170 171 171 172 -**__Add APP KEY and DEV EUI:__** 173 173 174 174 175 - [[image:1664501784668-703.png]]171 +**Step 2**: Power on TrackerD by using the on board switch. 176 176 177 177 174 +**Step 3:** TrackerD will auto join to the LoRaWAN network. After join success, TrackerD will start to upload message to IoT server. 178 178 179 179 180 - (% style="color:blue" %)**Step 2**:(%%)PoweronTrackerD by usingtheon boardswitch.177 +**Positioning Mode(SMOD):** 181 181 179 +* **GPS ONLY(Factory Settings): **only get GPS location info. 180 +* **BLE ONLY: **Only obtain iBeacon info via BLE. Design for Indoor tracking. 181 +* **GPS/BLE Hybrid: **Combination for Indoor and Outdoor tracking. 182 182 183 - (%style="color:blue"%)**Step 3:**(%%) TrackerDwill autojointothe LoRaWANnetwork. After joinsuccess, TrackerDwill starttoupload messagetoIoT server.183 +User can switch modes by [[changing SMOD>>path:#Positioning_Mode]]. 184 184 185 185 186 +1. 187 +11. Uplink Payload ~-~-~-~-~-~-~-~-~-~-~-~-~-~- 186 186 187 -== 2.3 Positioning Mode(SMOD) == 188 188 190 +1. 191 +11. 192 +111. Uplink FPORT=5, Device Status 189 189 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. 195 195 196 -Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 196 +1. 197 +11. 198 +111. Uplink FPORT= , Realtime GNSS Positioning 197 197 200 +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. ) 198 198 199 199 200 -== 2.4 Uplink Payload == 203 +|((( 204 +**Size** 201 201 206 +**(bytes)** 207 +)))|4|4|2|1|((( 208 +2 202 202 203 -=== 2.4.1 Uplink FPORT~=5, Device Status === 204 - 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. 207 - 208 -Use can also get the Device Status uplink through the downlink command: **Downlink: 0x2301** 209 - 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:417px" %) 288 -|(% style="width:77px" %)**Size(bit)**|(% style="width:70px" %)5 Bits|(% style="width:92px" %)1 Bit|(% style="width:48px" %)1 Bit|(% style="width:126px" %)1 Bit 289 -|(% 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"]] 290 - 291 -=== 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 292 - 293 - 294 -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, 295 - 296 - 297 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) 298 -|=(% scope="row" style="width: 50px;" %)((( 299 -**Size(bytes)** 300 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)((( 210 +(optional ) 211 +)))|((( 301 301 2 302 - )))|(% style="width:87px" %)(((303 - 2213 + 214 +(optional) 304 304 ))) 305 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 306 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 307 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 216 +|**Value**|[[Latitude>>path:#Location]]|[[Longitude>>path:#Location]]|((( 217 +[[Alarm &>>path:#Alarm]] 308 308 309 -[[image:1665301636888-168.png]] 219 +[[BAT>>path:#Alarm]] 220 +)))|[[FLAG>>path:#Flag]]|Hum|[[Tem>>path:#Pitch]] 310 310 311 311 312 - ==== (%style="color:blue" %)**Alarm& BAT:**(%%) ====223 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image007.png]] 313 313 314 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 315 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)1bit|(% style="width:50px" %)14bits 316 -|=(% style="width: 72px;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:118px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]] 317 317 318 - ==== (% style="color:blue"%)**FLAG:**(%%) ====226 +**Alarm & BAT:** 319 319 320 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:250px" %) 321 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:50px" %)1bit 322 -|=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] 228 +|**Size(bit)**|1 bit|1bit|14 bits 229 +|**Value**|reserve|Alarm Indicate|[[BAT>>path:#BAT]] 323 323 324 -** Example:**Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A231 +**FLAG:** 325 325 233 +|**Size(bit)**|2 bits|1bit|5 bits 234 +|**Value**|[[MOD>>path:#MD]]|[[LON>>path:#LON]]|Firmware version 326 326 327 -==== (% style="color:blue" %)**Location info:**(%%) ==== 328 328 329 -* Latitude: 02863D68 ⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// //value = 02863D68 /1000000 = 42.351976// 330 -* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// //value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 331 331 332 - (% style="color:red" %)**Importantnote:**238 +**Example: Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A ** 333 333 334 -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. 335 335 336 - 2. In this mode, the total payload will be 15 bytes, while US915/AU915 DR0 accepts only 11 bytes payload. Inthis case, the payload onserver will be ignore and shows as below:241 +**Location info:** 337 337 243 +* Latitude: 02863D68⇒ //if (0x//02863D68//& 0x80000000 = 0 )~:// 338 338 339 - [[image:1664502116362-706.png]]245 +//value = 02863D68 /1000000 = 42.351976// 340 340 247 +* Longitude: FAC29BAF ⇒ //if (0x//FAC29BAF// & 0x80000000 = 1 )~:// 341 341 342 - 3. While GPS can't getlocation info aftertimeout(FTIMEParameter),the latitude and longitude will be filled with all0x00:249 +//value = (0x//FAC29BAF// – 0x 100000000)/1000000 =//-87.9094//57// 343 343 344 -[[image:1664502166010-515.png]] 345 345 252 +Important note: 346 346 254 +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. 255 +1. In firmware version v1.5, Roll & Pitch is disabled by default. 256 +1. 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: 347 347 348 - ==== (%style="color:blue" %)**Alarm:**(%%) ====258 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png]] 349 349 350 -**Example: ** 0x4B & 0x40 >> 6 = 0x01 351 351 261 +1. While GPS can’t get location info after timeout(FTIME Parameter), the latitude and longitude will be filled with all 0x00: 352 352 353 - ==== (%style="color:blue" %)**BAT:**(%%) ====263 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.png]] 354 354 355 -**Example: ** 0x4B45 & 0x3FFF ⇒ 2885 (mV). 265 +* **Alarm**: Example: 0x4B & 0x40 >> 6 = 0x01 266 +* **BAT**: Example: 0x0CDD & 0x3FFF ⇒ 3293 (mV). 356 356 357 -((( 358 -The battery info shows the battery voltage, User can use the below mapping to indicate the battery in percentage: \ 359 -))) 268 +The battery info shows the current voltage, for **TrackerD** version which powered by li-on battery. User can use below mapping to indicate the battery in percentage: \ 360 360 361 -* > 4.0v : 80% ~~ 100% 362 -* 3.85v ~~3.99v: 60% ~~ 80% 363 -* 3.70v ~~ 3.84v: 40% ~~ 60% 364 -* 3.40v ~~ 3.69v: 20% ~~ 40% 365 -* < 3.39v: 0~~20% 366 366 367 -==== (% style="color:blue" %)**MOD:**(%%) ==== 271 +* > 4.0v : 80% ~~ 100% 272 +* 3.85v ~~3.99v: 60% ~~ 80% 273 +* 3.70v ~~ 3.84v: 40% ~~ 60% 274 +* 3.40v ~~ 3.69v: 20% ~~ 40% 275 +* < 3.39v: 0~~20% 368 368 369 -**Example: ** (0x60>>6) & 0x3f =1 370 370 371 -** SettheformatofGPS datauplinklink:**278 +* **LON: **Enable/Disable LED activity for uplink 372 372 373 -(% style="color:#037691" %)**0x00:** (%%) Enable uploading on-board Temperature and humidity values 374 -(% style="color:#037691" %)**0x01: ** (%%) Disable uploading on-board Temperature and humidity values 280 +0x00: Disable LED indicator. 375 375 282 +0x01: Enable LED indicator (Default Value) 376 376 377 -**Set the format of BLE data uplink link:** 378 378 379 -(% style="color:#037691" %)**0x01: ** (%%) BLE Positioning with Strongest iBeacon 285 +* **Hum**: 0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree 286 +* **//Tem//**//: 011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree 380 380 381 381 382 -==== (% style="color:blue" %)**LON:**(%%) ==== 383 383 384 -**Example:** (0x60>>5) & 0x01=1. 290 +1. 291 +11. 292 +111. Uplink FPORT= , History GNSS Positioning 385 385 386 -Enable/Disable LED activity for uplink 387 387 388 -((( 389 -(% style="color:#037691" %)**0x00:** (%%) Disable LED indicator. 390 -))) 391 391 392 - (((393 - (% style="color:#037691" %)**0x01:**(%%) Enable LED indicator (Default Value)394 -) ))296 +1. 297 +11. 298 +111. BLE positioning Payload(Fport=2) 395 395 300 +Different MODE has different payload: 396 396 302 +**MODE=2** 397 397 398 -==== (% style="color:blue" %)**Hum:**(%%) ==== 304 +|((( 305 +**Size** 399 399 400 -0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree 307 +**(bytes)** 308 +)))|16|4|4|2|4|2|1 309 +|**Value**|[[UUID>>path:#Location]]|((( 310 +iBeacon 401 401 312 +MAJOR 313 +)))|((( 314 +iBeacon 402 402 403 -==== (% style="color:blue" %)**Tem:**(%%) ==== 316 +MINOR 317 +)))|((( 318 +iBeacon Measured 404 404 405 -011A =if (0x011A & 0x8000 = 1 ): value =( 0x011A - 0x10000)/10(dec) ⇒ -//28.2 degree// 320 +Power 321 +)))|((( 322 +iBeacon 406 406 324 +RSSI 325 +)))|((( 326 +[[Alarm &>>path:#Alarm]] 407 407 328 +[[BAT>>path:#Alarm]] 329 +)))|[[FLAG>>path:#Flag]] 408 408 409 -=== 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) === 410 410 332 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]] 411 411 412 -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) 413 413 335 +* **BAT**: Ex1: 0x4B45 & 0x3FFF ⇒ 3901 (mV). 336 +* **MODE: **Define the payload format. 337 +* **UUID: **The uuid from the strongest iBeacon. 338 +* **MAJOR**: The MAJOR from the strongest iBeacon. 339 +* **MINOR**: The MAJOR from the strongest iBeacon. 340 +* **Measured** **Power**: The Measured Power from the strongest iBeacon. 341 +* **RSSI**: The RSSI from the strongest iBeacon. 414 414 415 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:480px" %) 416 -|=(% scope="row" style="width: 50px;" %)((( 417 -**Size(bytes)** 418 -)))|(% style="width:60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1 419 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 420 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 421 -)))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 422 422 423 -(% class="wikigeneratedid" %) 424 -[[image:1665301687277-443.png]] 344 +1. 345 +11. 346 +111. Add Payload format in TTN V3 425 425 426 - 427 - 428 -=== 2.4.4 Uplink FPORT~=4, History GNSS Positioning === 429 - 430 - 431 -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. 432 - 433 - 434 -(% style="color:red" %)**Note for this mode:** 435 - 436 -* a) TrackerD will do an ACK check for data records sending to make sure every data arrive server. 437 -* 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. 438 -* 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 439 - 440 -The payload is 15 bytes, as below. 441 - 442 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %) 443 -|=(% scope="row" %)((( 444 -**Size(bytes)** 445 -)))|4|4|2|1|1|1|1|1 446 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 447 - 448 -[[image:image-20221009160309-2.png]] 449 - 450 - 451 - 452 -=== 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 453 - 454 -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. 455 - 456 -User can set [[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]] so TrackerD will only search the iBeacons which have UUID match the BLEMASK. 457 - 458 - 459 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 460 -|=(% scope="row" style="width: 60px;" %)((( 461 -**Size(bytes)** 462 -)))|(% style="width:30px" %)16|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:120px" %)2|(% style="width:50px" %)4|(% style="width:50px" %)2|(% style="width:30px" %)1 463 -|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)((( 464 -iBeacon MAJOR 465 -)))|(% style="width:63px" %)((( 466 -iBeacon MINOR 467 -)))|(% style="width:71px" %)((( 468 -iBeacon Measured Power 469 -)))|(% style="width:50px" %)((( 470 -iBeacon RSSI 471 -)))|(% style="width:47px" %)((( 472 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 473 -)))|(% style="width:15px" %)[[FLAG>>||anchor="HFLAG:"]] 474 - 475 -[[image:1664502425687-834.png]] 476 - 477 - 478 -* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 479 -* (% style="color:#037691" %)**MODE: **(%%)Define the payload format. 480 -* (% style="color:#037691" %)**UUID: **(%%)The uuid from the strongest iBeacon. 481 -* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. 482 -* (% style="color:#037691" %)**MINOR:** (%%)The MAJOR from the strongest iBeacon. 483 -* (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 484 -* (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 485 - 486 -=== 2.4.6 Add Payload format in TTN V3 === 487 - 488 - 489 489 In TTN V3, use can add a custom payload so it shows friendly. 490 490 491 -In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**350 +In the page Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder 492 492 352 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]] 493 493 494 - [[image:1664502649601-895.png]]354 +Add the decoder from this link: 495 495 496 496 497 -Add the decoder from this link: 498 - 499 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] 500 - 501 501 Save the change the uplink message will be parsed. As below: 502 502 503 -[[image: 1664502676891-606.png]]359 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]] 504 504 505 505 506 506 507 -== 2.5 Integrate with Datacake == 508 508 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. 510 510 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]] 365 +1. 366 +11. Integrate with Datacake 512 512 513 -[[image:1664502695771-538.png]] 514 514 369 +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. 515 515 371 +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]] 516 516 517 - == 2.6 IntegratewithTago ==373 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]] 518 518 519 519 376 +1. 377 +11. Integrate with Tago 520 520 521 -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. 522 522 380 +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. 381 + 523 523 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]] 524 524 384 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]] 525 525 526 526 527 -[[image:1664502715371-321.png]] 528 528 529 529 389 +1. 390 +11. Alarm Mode 530 530 531 -== 2.7 Datalog Feature == 532 532 393 +User can push the **RED button** by more than 5 seconds to enter Alarm Mode. 533 533 534 -total 273 entries,by default, 535 535 536 - Usercanset[[PNACKMD=1>>||anchor="H3.2.10A0A0AutoSendNone-ACKmessages"]],toenableDatalogfeature.396 +Once enter Alarm mode, the **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. 537 537 538 -Example use case. 539 539 540 -[[image:image-20221009234703-2.png||height="328" width="899"]] 541 - 542 - 543 -[[image:image-20221009234629-1.png||height="390" width="577"]] 544 - 545 - 546 - 547 -== 2.8 Alarm Mode == 548 - 549 - 550 -((( 551 -User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 552 -))) 553 - 554 - 555 -((( 556 -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. 557 -))) 558 - 559 - 560 -((( 561 561 Two ways to exit alarm mode: 562 -))) 563 563 564 -* Server send sa downlink command to exit.401 +* Server send a downlink command to exit. 565 565 * User fast press the RED button 10 times. 566 566 567 -((( 568 -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. 569 -))) 404 +When exit alarm mode, **RED LED** will light up for 5 seconds, indicating that the alarm mode is exited. And the alert flag will be set to false. 570 570 571 571 407 +1. 408 +11. Sports Mode ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-- 572 572 573 -== 2.9 Transport Mode == 574 574 575 575 576 -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. 412 +1. 413 +11. LED Status 577 577 578 578 416 +|**Event**|**Action**|**AT+LON to control on/off** 417 +|**Power On**|**BLUE, RED , Green** flash once|N/A 418 +|**Join request**|**Green** led fast blink once (200ms)|Yes 419 +|**Join Success**|**Green** led on 5 second|N/A 420 +|**Fixing Location**|**BLUE **blinks 200ms per second|Yes 421 +|**Fixed and uplink**|**GREEN **blinks twice (200ms per blink)|Yes 422 +|**Fail Fix and uplink**|**RED **blinks twice (200ms per blink)|Yes 423 +|**Enter Alarm mode**|**RED **on for 3 seconds|Yes 424 +|**Uplink under Alarm**|**RED **on for 1 second|Yes 425 +|**Exit Alarm**|**BLUE **led on 5 second|Yes 426 +|**Get Downlink**|**GREEN** led on 1 second|Yes 427 +|**Movement Detect**|**RED **on 500ms|N/A 579 579 580 -== 2.10 LED Status == 581 581 582 582 583 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 584 -|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 585 -|(% 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 586 -|(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes 587 -|(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A 588 -|(% style="width:157px" %)**Fixing Location**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)blinks 200ms per second|(% style="width:202px" %)Yes 589 -|(% style="width:157px" %)**Fixed and uplink**|(% style="width:271px" %)(% style="color:green" %)**GREEN ***(%%)***blinks twice (200ms per blink)**|(% style="width:202px" %)Yes 590 -|(% style="width:157px" %)**Fail Fix and uplink**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)blinks twice (200ms per blink)|(% style="width:202px" %)Yes 591 -|(% style="width:157px" %)**Enter Alarm mode**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 3 seconds|(% style="width:202px" %)Yes 592 -|(% style="width:157px" %)**Uplink under Alarm**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)on for 1 second|(% style="width:202px" %)Yes 593 -|(% style="width:157px" %)**Exit Alarm**|(% style="width:271px" %)(% style="color:blue" %)**BLUE **(%%)led on 5 second|(% style="width:202px" %)Yes 594 -|(% style="width:157px" %)**Get Downlink**|(% style="width:271px" %)(% style="color:green" %)**GREEN**(%%) led on 1 second|(% style="width:202px" %)Yes 595 -|(% style="width:157px" %)**Movement Detect**|(% style="width:271px" %)(% style="color:red" %)**RED **(%%)led on 500ms|(% style="width:202px" %)N/A 596 596 597 -== 2.11 Button Function == 598 598 433 +1. 434 +11. Button Function 599 599 600 - (% style="color:blue" %)**RESET button:**436 +**RESET button:** 601 601 602 -[[image: 1664502835802-546.png]]438 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]] 603 603 604 604 Push this button will reboot the device. Device will exit alarm mode and re-join to LoRaWAN server. 605 605 606 606 607 - (% style="color:red" %)**RED button:**443 +**RED button:** 608 608 609 -[[image: 1664502854406-763.png]]445 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]] 610 610 447 +|**Function**|**Action**|**Description** 448 +|Send Alarm|Keep Pressing **RED** button for more than 5 seconds|Enter Alarm Mode. See [[Alarm Mode>>path:#Alarm_Mode]] 449 +|Exit Alarm Mode|Fast press the **RED** button 10 times|Exit Alarm Mode 450 +|Enter Deep Sleep Mode|Press and hold the button for 10 seconds, then quickly press the device 3 times to enter deep sleep|This is the mode ship out from factory. CPU will be complete in sleep mode and no LoRa activity, only use before deploy. 611 611 612 -(% border="1.5" style="background-color:#ffffcc; color:green; width:520px" %) 613 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 210px;" %)**Action**|=(% style="width: 210px;" %)**Description** 614 -|(% 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"]] 615 -|(% 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 616 -|(% 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. 617 617 618 -== 2.12 USB Port Function == 619 619 620 620 455 +1. 456 +11. USB Port Function 457 + 621 621 The USB interface of TrackerD has below functions: 622 622 623 623 * Power on the device 624 624 * Recharge the battery 625 -* [[Configure Device>> ||anchor="H3.ConfigureTrackerDviaATcommandorLoRaWANdownlink"]]626 -* [[Upgrade Firmware>> ||anchor="H5.UploadFirmware"]]462 +* [[Configure Device>>path:#AT_Command]] 463 +* [[Upgrade Firmware>>path:#upgrade_image]] 627 627 628 -= 3. Configure TrackerD via AT command or LoRaWAN downlink = 629 629 630 630 631 -User can configure TrackerD via AT Command or LoRaWAN Downlink. 632 632 633 -LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] 634 634 469 +1. Configure TrackerD via AT command or LoRaWAN downlink 635 635 636 636 637 - ==3.1AccessAT Command==472 +User can configure TrackerD via AT Command or LoRaWAN Downlink. 638 638 474 +LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]] 639 639 640 -TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below. 641 641 477 +1. 478 +11. Access AT Command 642 642 643 - [[image:1664502999401-486.png]]480 +TrackerD supports the AT command set in stock firmware. User can connect to TrackerD with TYPE-C cable to use AT commands as shown below. ... 644 644 482 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]] 645 645 646 -In PC, User needs to set serial tool baud rate to (% style="color:green" %)**115200**(%%) to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands: 647 647 485 +In PC, User needs to set serial tool baud rate to **115200** to access serial console for TrackerD. TrackerD will output system info once power on and user will be able to send AT commands: 648 648 649 -[[image:1664503022490-662.png]] 650 650 488 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]] 651 651 652 -[[image:1664503035713-500.png]] 653 653 654 654 655 -[[image: 1664503047675-651.png]]492 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]] 656 656 494 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]] 657 657 658 658 659 -== 3.2 Command Set == 497 +1. 498 +11. Command Set 660 660 661 661 662 -=== 3.2.1 Set Transmit Interval === 501 +1. 502 +11. 503 +111. Set Transmit Interval 663 663 664 - 665 665 Set device uplink interval. 666 666 667 -* (% style="color:blue" %)**AT Command:**507 +* AT Command: 668 668 669 - (% style="color:#037691" %)**AT+TDC=xxx**509 +AT+TDC=xxx 670 670 671 -Example: 511 +Example: AT+TDC=300000. Means set interval to 5 minutes(300 seconds) 672 672 673 673 674 -* (% style="color:blue" %)**Downlink Payload (prefix 0x01):**514 +* Downlink Payload (prefix 0x01): 675 675 676 - (% style="color:#037691" %)**0x01 00 01 2C**(%%)~/~/516 +0x01 00 01 2C ~/~/ Same as AT+TDC=300000 677 677 678 678 519 +1. 520 +11. 521 +111. Set Alarm Packet transmission interval 679 679 680 -=== 3.2.2 Set Alarm Packet transmission interval === 681 - 682 - 683 683 Set alarm packet transmit interval 684 684 685 -* (% style="color:blue" %)**AT Command:**525 +* AT Command: 686 686 687 - (% style="color:#037691" %)**AT+ATDC=xx.**527 +AT+ATDC=xx. 688 688 689 -Example: **~-~-> **Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000529 +Example: AT+ATDC=60000 à Set Alarm Packet Interval to 60 seconds. TrackerD will send every 60 seconds in Alarm mode, Default Value: 60000 690 690 691 691 692 -* (% style="color:blue" %)**Downlink Payload (prefix 0xB1):**532 +* Downlink Payload (prefix 0xB1): 693 693 694 - (% style="color:#037691" %)**0xB1 00 00 3C** (%%)~/~/534 +0xB1 00 00 3C ~/~/Same as AT+ATDC=60000 695 695 696 696 537 +1. 538 +11. 539 +111. Set Sports Mode Packet transmission interval 697 697 698 - === 3.2.3SetTransportMode Packet transmissioninterval===541 +Set sports packet transmit interval 699 699 543 +* AT Command: 700 700 701 - SetTransportModepacket transmit interval545 +AT+MTDC=xx. 702 702 703 - *(%style="color:blue"%)**ATCommand:**547 + Example: AT+MTDC=300000 à Set Sports Mode Packet Interval to 300 seconds. TrackerD will send every 300 seconds in Sports mode, Default Value: 300000 704 704 705 -(% style="color:#037691" %)**AT+MTDC=xx. ** 706 706 707 - Example: AT+MTDC=300000**~-~->** Set Transport Mode Packet Intervalto 300 seconds. TrackerDwill send every300 secondsin Transport mode, DefaultValue: 300000550 +* Downlink Payload (prefix 0x03): 708 708 552 +0x03 00 01 2C ~/~/Same as AT+ MTDC=3000000 709 709 710 -* (% style="color:blue" %)**Downlink Payload (prefix 0x03):** 711 711 712 -(% style="color:#037691" %)**0x03 00 01 2C** (%%) ~/~/ Same as AT+ MTDC=3000000 713 713 556 +1. 557 +11. 558 +111. Exit Alarm 714 714 715 - 716 -=== 3.2.4 Exit Alarm === 717 - 718 - 719 719 Server send downlink command to exit Alarm mode 720 720 721 -* (% style="color:blue" %)**AT Command:No AT Command**562 +* AT Command: 722 722 723 - * (% style="color:blue"%)**DownlinkPayload(prefix 0x02):**564 +No AT Command 724 724 725 -(% style="color:#037691" %)**0x02 01** (%%) ~/~/ Exit Alarm Mode 726 726 567 +* Downlink Payload (prefix 0x02): 727 727 569 +0x02 01 ~/~/ Exit Alarm Mode 728 728 729 -=== 3.2.5 Disable/Enable LED flash === 730 730 572 +1. 573 +11. 574 +111. Disable/Enable LED flash 731 731 732 732 Disable/Enable LED for position, downlink and uplink 733 733 734 -* (% style="color:blue" %)**AT Command:**578 +* AT Command: 735 735 736 - (% style="color:#037691" %)**AT+LON=xx. (Disable (0), Enable (1), default:1)**580 +AT+LON=xx. (Disable (0), Enable (1), default:1) 737 737 738 -Example: AT+LON=0 **~-~-> **Disable LED for position, downlink and uplink.582 + Example: AT+LON=0 à Disable LED for position, downlink and uplink. 739 739 740 740 741 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAE):**585 +* Downlink Payload (prefix 0xAE): 742 742 743 - (% style="color:#037691" %)**0xAE 00** (%%)~/~/587 +0xAE 00 ~/~/Same as AT+LON=0 744 744 745 745 746 746 747 -=== 3.2.6 Disable/Enable Transport Mode === 748 748 592 +1. 593 +11. 594 +111. Disable/Enable movement detect (Debug Only) 749 749 750 -User scan use this feature to enable/disableTransportMode.596 +User can use this feature to check and set thread hole of movement detect 751 751 752 -* (% style="color:blue" %)**AT Command:**598 +* AT Command: 753 753 754 - (% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)**600 +AT+INTWK=xx. (Disable (0), Enable (1), default:0) 755 755 756 -Example: **~-~-> **EnableTransportMode.602 + Example: AT+ INTWK =1 à Enable detect movement. 757 757 758 758 759 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAF):**605 +* Downlink Payload (prefix 0xAF): 760 760 761 - (% style="color:#037691" %)**0xAF 01** (%%)~/~/607 +0xAF 01 ~/~/Same as AT+ INTWK =1 762 762 763 763 764 764 765 -=== 3.2.7 Set Positioning Mode === 611 +1. 612 +11. 613 +111. Set Positioning Mode 766 766 615 +SMOD define the how TrackerD scan and uplink date. 767 767 768 -S MODdefine how TrackerD scan and uplinkdata:617 +GPS室外定位模式:设备默认模式,设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是3分钟定位,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。GPS还有一种logdata模式,在断网的情况下将数据存储下来,等到有网的时候,一次将数据以每10秒上报。 769 769 619 + BLE室内定位模式:设备入网后会发送device当前模式下的信息,随后立即定位发送数据包(默认是5秒,超过将发送无效数据),如果出现意外情况下,快速按键3下,将会发出报警消息(默认每3分钟发送一次)。 770 770 771 - *(%style="color:blue"%)**ATCommand:**621 + GPS和BLE混动模式:设备入网后会发送device当前模式下的信息,随后立即判断是否在室内,如果是就进行BLE定位,不是就GPS定位。如果出现意外情况下,快速按键3下,将会发出报警消息(默认每分钟发送一次)。 772 772 773 - (% style="color:#037691" %)**AT+SMOD=aa,bb,cc**623 +运动模式:设备入网后会发送device当前模式下的信息,随后发送GPS定位数据,设备判断是否在运动,没有运动传感器没有检测到动作,立即进入静止状态(默认20分钟),如果产生运动,将每5分钟发送一次数据,再第五分钟后检测设备有误运动,无将切换到静止状态,有立即发送数据。 774 774 775 -(% style="color:#037691" %)** aa:** 776 776 777 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)only get and uplink GPS location info. 778 -* (% style="color:red" %)**2: BLE ONLY: **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking. 779 -* (% 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. 780 780 781 -(% style="color:#037691" %)**bb:** 782 782 783 -* (% style="color:red" %)**0 : **(%%)GPS+ BAT+ State+Tem&Hum 784 -* (% style="color:red" %)**1 :**(%%) GPS +BAT State 628 +* AT Command: 785 785 786 - (% style="color:#037691"%)**cc: **630 +AT+SMOD=xx. 787 787 788 - *(% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State632 + Example: 789 789 790 - (%style="color:blue"%)**Example:**634 + AT+ SMOD =1,0 à GPS+ BAT+ State+Tem&Hum 791 791 792 - AT+ SMOD =1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 793 - AT+ SMOD =1,1,0 ~-~-> GPS +BAT State 794 - AT+ SMOD =2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 636 + AT+ SMOD =1,1 à GPS +BAT State 795 795 638 + AT+ SMOD =2,3 à (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State。 796 796 797 -* (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** 798 798 799 - (%style="color:#037691"%)**0xA501 00 00** (%%)~/~/ Same as AT+ SMOD =1,0,0641 +* Downlink Payload (prefix 0xA5): 800 800 643 +0xA5 01 00 ~/~/ Same as AT+ SMOD =1,0 801 801 802 802 803 -=== 3.2.8 Set MAX GPS position time === 646 +1. 647 +11. 648 +111. Set MAX GPS position time 804 804 805 - 806 806 Set max positioning time, default is 150 seconds. TrackerD will try to get location info within this period. If fail to get position data within this time, TrackerD will use 000000 for latitude and longitude. 807 807 808 808 ... ... @@ -809,146 +809,105 @@ 809 809 If AT+FTIME=0. The GPS module will be always powered and positioning. This will highly increase the power consumption (up to 50mA). When AT+FTIME=0, it will improve fix accuracy and shorten the acquire time for next uplink. 810 810 811 811 812 -* (% style="color:blue" %)**AT Command:**656 +* AT Command: 813 813 814 - (% style="color:#037691" %)**AT+FTIME=xx**(%%)**~-~-> **Set to use xx as max fix time.658 +AT+FTIME=xx à Set to use xx as max fix time. 815 815 816 - **Example:**AT+FTIME=150660 +Example: AT+FTIME=150 817 817 818 818 819 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAA):**663 +* Downlink Payload (prefix 0xAA): 820 820 821 - (% style="color:#037691" %)**0xAA 00 96** (%%)~/~/665 +0xAA 00 96 ~/~/Set AT+FTIME=150 822 822 823 823 824 824 825 -=== 3.2.9 Set PDOP value for GPS fix accuracy === 826 826 670 +1. 671 +11. 672 +111. Set PDOP value for GPS fix accuracy 827 827 828 -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.674 +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. 829 829 830 830 831 831 A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0 832 832 833 833 834 -* (% style="color:blue" %)**AT Command:**680 +* AT Command: 835 835 836 - (% style="color:#037691" %)**AT+PDOP=2.5** (%%) **~-~->**Set PDOP to 2.5682 +AT+PDOP=2.5 à Set PDOP to 2.5 837 837 838 838 839 -* (% style="color:blue" %)**Downlink Payload (prefix 0xAD):**685 +* Downlink Payload (prefix 0xAD): 840 840 841 - (% style="color:#037691" %)**0xAD 00 0A**(%%)~/~/687 +0xAD 00 0A ~/~/Set AT+PDOP=1 (0x0A / 10 =1) 842 842 843 - (% style="color:#037691" %)**0xAD 00 19**(%%)~/~/689 +0xAD 00 19 ~/~/Set AT+PDOP=2.5 (0x19 / 10 =2.5) 844 844 845 - (% style="color:#037691" %)**0xAD 00 46**(%%)691 +0xAD 00 46 ~/~/Set AT+PDOP=7 (0x46 / 10 =7) 846 846 847 - 848 - 849 849 Disable/Enable the confirmation mode 850 850 851 -* (% style="color:blue" %)**AT Command:**695 +* AT Command: 852 852 853 - (% style="color:#037691" %)**AT+CFM=xx**697 +AT+CFM=xx. 854 854 699 + Example: 855 855 856 - **~Example:**701 + AT+ CFM=0 à Disable confirmation 857 857 858 - AT+ CFM= 0**~-~->** Disable confirmation703 + AT+ CFM=1 à Enable confirmation 859 859 860 - AT+ CFM=1 **~-~-> ** Enable confirmation 861 861 706 +* Downlink Payload (prefix 0x05): 862 862 863 - *(%style="color:blue"%)**Downlink Payload(prefix0x05):**708 +0x05 01 ~/~/ Same as AT+ SMOD =1 864 864 865 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+ SMOD =1 866 866 867 867 868 868 869 -=== 3.2.10 Auto Send None-ACK messages === 870 870 871 871 872 - TrackerDwill wait for ACK foreach uplink, If TrackerD doesn'tgetACK from the IoT server,it will consider the messagedoesn't arriveserver and store it. TrackerDkeeps sending messages in normal periodically. Once TrackerD getsACK from a server, it willconsider thenetworkisok andstart to send the not-arrive message.715 +1. Setting for Different Scenarios 873 873 874 874 875 -* (% style="color:blue" %)**AT Command: AT+PNACKMD** 876 876 877 -The default factory setting is 0. 719 +1. Upload Firmware 720 +11. Firmware Change Log 878 878 879 - 880 -**Command Example Function Response:** 881 - 882 -(% style="color:#037691" %)**AT+PNACKMD=1** (%%) ~/~/ Poll None-ACK message OK 883 - 884 - 885 -* (% style="color:blue" %)**Downlink Command: 0x34** 886 - 887 -Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 888 - 889 - 890 -=== 3.2.11 Set BLEMASK to filter BLE iBeacon === 891 - 892 -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. 893 - 894 -Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled. 895 - 896 -(% style="color:blue" %)**AT Command:**(%%) 897 - AT+BLEMASK=123456 ~/~/ Set BLEMASK = 123456 898 - AT+BLEMASK=0 ~/~/ disable BLEMASK 899 - 900 - 901 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**(%%) 902 -Example: 903 -0xA5010203040506 ~/~/ Set BLEMASK to 123456 904 - 905 - 906 - 907 -= 4. Setting for Different Scenarios = 908 - 909 - 910 - 911 -= 5. Upload Firmware = 912 - 913 - 914 -== 5.1 Firmware Change Log == 915 - 916 - 917 917 **[[See this link>>url:https://github.com/dragino/TrackerD]]** 918 918 919 919 725 +1. 726 +11. How to upgrade firmware 920 920 921 - ==5.2How to upgrade firmware==728 +User can use the TrackerD ’s USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below: 922 922 923 923 924 - UsercanuseheTrackerD'sUSB port to upgradefirmwareintoit. The hardwareconnection for upgradefirmwareisas below:731 +**Step1: **Connect TrackerD and PC via USB cable shipped with TrackerD. 925 925 733 +**Step2:** Install CH9102 driver in the PC. 926 926 927 -(% style="color:blue" %)**Step1: **(%%)Connect TrackerD and PC via USB cable shipped with TrackerD. 928 - 929 - 930 -(% style="color:blue" %)**Step2:** (%%) Install CH9102 driver in the PC. 931 - 932 932 After installation of the driver and plug in TrackerD, user should be able to see com port in PC's device manager. 933 933 934 934 935 - (% style="color:blue" %)**Step3:**(%%)Download and Install Flash Tool:[[https:~~/~~/www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools]]738 +**Step3:** Download and Install Flash Tool: 936 936 740 +[[https:~~/~~/www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools>>url:https://www.espressif.com.cn/en/support/download/other-tools?keys=Flash%2BDownload%2BTools]] 937 937 938 - (% style="color:blue" %)**Step4:**(%%)Run Flash Download Tool and configure chip type to ESP32742 +**Step4:** Run Flash Download Tool and configure chip type to ESP32 939 939 940 940 941 -[[image: 1664503563660-578.png]]745 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png||alt="image-20220712083115-1.png"]] 942 942 747 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png||alt="image-20220712083115-2.png"]] 943 943 944 -[[image:1664503574618-659.png]] 945 945 750 +**Step5:** Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 946 946 947 - (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format),comportnder SPI configure.Clink Start.Bin file location:752 +[[https:~~/~~/www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0>>url:https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 948 948 949 -[[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]] 950 950 951 - 952 952 Users need to use below files: 953 953 954 954 boot_app0.bin @0e000 ... ... @@ -955,78 +955,75 @@ 955 955 956 956 ESP_LORA-eeprom-class.bin @ 0x10000 957 957 761 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png||alt="image-20220712083115-3.png"]] 958 958 959 -[[image:1664503593459-435.png]] 960 - 961 - 962 - 963 963 After upgrade finish, it will show finish as below: 964 964 965 -[[image: 1664503611848-385.png]]765 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png||alt="image-20220712083115-4.png"]] 966 966 967 967 968 968 969 -= 6. Developer Guide = 970 970 971 971 972 - == 6.1CompileSourceCode==771 +1. Developer Guide 973 973 974 974 975 -=== 6.1.1 Set up ARDUINO compile environment === 774 +* 775 +*1. Compile Source Code 776 +*11. Set up ARDUINO compile environment 777 +* Download the latest Arduino software (IDE) from the Arduino official website 976 976 779 +[[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]] 977 977 978 - ***DownloadthelatestArduinosoftware(IDE)fromtheArduino officialebsite:[[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]]**781 +Install IDE on PC, open and click File ~-~-> Preference, add the following URL [[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fdl.espressif.com%2Fdl%2Fpackage_esp32_index.json]] 979 979 980 - Install IDE on PC, open and click (% style="color:#037691" %)**File~-~-> Preference**,(%%) add the following URL:[[https:~~/~~/dl.espressif.com/dl/package_esp32_index.json>>url:https://links.jianshu.com/go?to=https%3A%2F%2Fdl.espressif.com%2Fdl%2Fpackage_esp32_index.json]]783 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]] 981 981 785 +* Go to tools ~-~-> Boards ~-~-> Boards Manager, find the esp32 information and install it. 982 982 983 -[[image: 1664503635019-941.png]]787 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]] 984 984 985 985 790 +* Download the latest TrackerD from the dragino github 986 986 987 - * (% style="color:#037691" %)**Goto tools-~-> Boards~-~-> Boards Manager**,(%%) **find the esp32informationnd install it.**792 +[[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]] 988 988 989 -[[image:1664503715811-892.png]] 990 990 795 +Put the Library in the TrackerD directory into the libraries file in the Arduino directory 991 991 797 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]] 992 992 993 -* **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]** 994 994 995 -Put the Library in the TrackerD directory into the libraries file in the Arduino directory: 996 996 997 997 998 -[[image:1664503752288-974.png]] 802 +* 803 +*1. Source Code 804 +* Open the example in the TrackerD file, please select the correct port in the IDE, as shown below: 999 999 806 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]] 1000 1000 808 +* Click to upload 1001 1001 1002 - ==6.2 SourceCode==810 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]] 1003 1003 812 +* Check the result, if the upload is successful, as shown below, open the serial port to view the data 1004 1004 1005 -* (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:** 1006 1006 1007 -[[image: 1664503794261-827.png]]815 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]] 1008 1008 1009 1009 1010 1010 1011 -* (% style="color:blue" %)**Click to upload** 1012 1012 1013 -[[image:1664503808294-336.png]] 1014 1014 1015 1015 1016 - 1017 -* (% style="color:blue" %)**Check the result, if the upload is successful, as shown below, open the serial port to view the data** 1018 - 1019 -[[image:1664503824081-592.png]] [[image:1664503831430-500.png]] 1020 - 1021 - 1022 - 1023 1023 = 7. FAQ = 1024 1024 1025 1025 825 + 1026 1026 == 7.1 How to change the LoRa Frequency Bands/Region? == 1027 1027 1028 1028 1029 -User can follow the introduction for [[how to upgrade image>> ||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download.829 +User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download. 1030 1030 1031 1031 1032 1032 ... ... @@ -1037,8 +1037,8 @@ 1037 1037 1038 1038 1039 1039 1040 -(% border=" 1.5"cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %)1041 -| =(% style="width:;" %)**Pin**|=(% style="width:;" %)**Color**|=(% style="width:;" %)**USB Pin**840 +(% border="2" style="background-color:#ffffcc; color:green; width:314px" %) 841 +|(% style="width:118px" %)**Pin**|(% style="width:67px" %)**Color**|(% style="width:123px" %)**USB Pin** 1042 1042 |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC 1043 1043 |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A) 1044 1044 |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A) ... ... @@ -1056,6 +1056,7 @@ 1056 1056 (% style="color:blue" %)**XXX**(%%): The default frequency band 1057 1057 1058 1058 * (% style="color:red" %)**EU433**(%%): Default frequency band EU433 859 +* (% style="color:red" %)**CN470**(%%): Default frequency band CN470 1059 1059 * (% style="color:red" %)**EU868**(%%): Default frequency band EU868 1060 1060 * (% style="color:red" %)**IN865**(%%): Default frequency band IN865 1061 1061 * (% style="color:red" %)**KR920**(%%): Default frequency band KR920 ... ... @@ -1063,25 +1063,33 @@ 1063 1063 * (% style="color:red" %)**AU915**(%%): Default frequency band AU915 1064 1064 * (% style="color:red" %)**US915**(%%): Default frequency band US915 1065 1065 867 + 1066 1066 = 9. Packing Info = 1067 1067 1068 1068 1069 - (% style="color:#037691" %)**Package Includes**:871 +**Package Includes**: 1070 1070 1071 -* TrackerD LoRaWAN GPS/BLE Tracker x 1 1072 -* USB recharge & program cable x 1 873 +* TrackerD x 1 874 +* Rechargeable cable x 1 875 +* Program Cable x 1 1073 1073 1074 - (% style="color:#037691" %)**Dimensions and Weight**:877 +**Dimensions and Weight**: 1075 1075 1076 -* Device Size: 85 x 48 x 15 cm1077 -* Weight: 5 0g879 +* Device Size: 85 x 48 x 15 mm/pcs 880 +* Weight: 55g/pcs 1078 1078 1079 -= 10. Support = 1080 1080 1081 1081 884 += 10. Support = 885 + 1082 1082 * 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. 1083 -* 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]].887 +* 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 1084 1084 889 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]] 890 + 891 + 892 + 893 + 1085 1085 = 11. Reference = 1086 1086 1087 1087 ... ... @@ -1088,5 +1088,3 @@ 1088 1088 * [[**Firmware in Bin format**>>https://www.dropbox.com/sh/733s8xlwahhqg1d/AABxDz80lBVX_to8zNuUQWFja?dl=0]] 1089 1089 * **[[Source Code>>https://github.com/dragino/TrackerD]] ** 1090 1090 * [[**Hardware Source**>>https://www.dropbox.com/sh/orwoy6cecb89m4e/AAD37sRuUrvKsHgAJxuVTkB5a?dl=0]] 1091 - 1092 -
- 1664501652064-326.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -143.9 KB - Content
- 1664501677253-891.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -202.7 KB - Content
- 1664501711466-918.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -62.0 KB - Content
- 1664501721248-725.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -55.6 KB - Content
- 1664501734705-405.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -64.1 KB - Content
- 1664501784668-703.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -62.0 KB - Content
- 1664501958445-288.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -74.1 KB - Content
- 1664502116362-706.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -56.0 KB - Content
- 1664502166010-515.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -41.3 KB - Content
- 1664502425687-834.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -38.2 KB - Content
- 1664502649601-895.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -59.2 KB - Content
- 1664502676891-606.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -64.3 KB - Content
- 1664502695771-538.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -54.7 KB - Content
- 1664502715371-321.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -79.9 KB - Content
- 1664502835802-546.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -37.8 KB - Content
- 1664502854406-763.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -14.3 KB - Content
- 1664502999401-486.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -916.7 KB - Content
- 1664503022490-662.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -133.6 KB - Content
- 1664503035713-500.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -354.0 KB - Content
- 1664503047675-651.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -199.1 KB - Content
- 1664503563660-578.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -38.1 KB - Content
- 1664503574618-659.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -139.8 KB - Content
- 1664503593459-435.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -183.3 KB - Content
- 1664503611848-385.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -175.9 KB - Content
- 1664503635019-941.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -161.8 KB - Content
- 1664503715811-892.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -36.6 KB - Content
- 1664503752288-974.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -112.6 KB - Content
- 1664503794261-827.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -119.5 KB - Content
- 1664503808294-336.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -161.6 KB - Content
- 1664503824081-592.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -77.4 KB - Content
- 1664503831430-500.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -147.8 KB - Content
- 1664505654417-133.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -27.5 KB - Content
- 1665301570342-765.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.6 KB - Content
- 1665301636888-168.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -36.6 KB - Content
- 1665301687277-443.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -22.6 KB - Content
- 1665301786397-168.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -22.6 KB - Content
- image-20221006181316-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -17.7 KB - Content
- image-20221006181357-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -88.0 KB - Content
- image-20221009160220-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -46.4 KB - Content
- image-20221009160309-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -57.2 KB - Content
- image-20221009234629-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -222.9 KB - Content
- image-20221009234703-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -136.4 KB - Content