Changes for page TrackerD - LoRaWAN Tracker User Manual(Remove WiFi)
Last modified by Xiaoling on 2023/12/27 09:15
From version 201.1
edited by Bei Jinggeng
on 2023/03/08 11:57
on 2023/03/08 11:57
Change comment:
Uploaded new attachment "image-20230308115701-3.png", version {1}
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 2 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -TrackerD -LoRaWAN Tracker User Manual 1 +TrackerD - LoRaWAN Tracker User Manual - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Bei1 +XWiki.Xiaoling - Content
-
... ... @@ -23,7 +23,7 @@ 23 23 ))) 24 24 25 25 ((( 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.26 +In TrackerD, there are various sensors such as GPS,BLE, Temperature, Humidity, Motion Detection, and Buzzer. User can use TrackerD for different tracking scenario. 27 27 28 28 ((( 29 29 TrackerD is program friendly. Developers can use Arduino IDE to customize the software of TrackerD to fit their IoT solution. ... ... @@ -51,7 +51,6 @@ 51 51 * Espressif ESP32 PICO D4 52 52 * MCU: ESP32 PICO D4 53 53 * Bluetooth: Bluetooth V4.2 BR/EDR and Bluetooth LE 54 -* WiFi : 802.11 b/g/n (802.11n up to 150 Mbps) 55 55 * Integrated SPI flash : 4 MB 56 56 * RAM: 448 KB 57 57 * EEPROM: 520 KB ... ... @@ -93,8 +93,10 @@ 93 93 * LoRa Transmit Mode: 125mA @ 20dBm 44mA @ 14dBm 94 94 * Tracking: max: 38mA 95 95 95 +(% style="display:none" %) 96 96 97 97 98 + 98 98 == 1.3 Features == 99 99 100 100 ... ... @@ -103,7 +103,7 @@ 103 103 * SX1276/78 Wireless Chip 104 104 * Arduino IDE Compatible 105 105 * Open source hardware / software 106 -* Regular/ Real-time GPS,BLE ,WIFI tracking107 +* Regular/ Real-time GPS,BLE 107 107 * Built-in3 axis accelerometer (LIS3DH) 108 108 * Humidity / temperature sensor : GXCAS Technology GXHT3X 109 109 * Motion sensing capability ... ... @@ -113,8 +113,10 @@ 113 113 * Tri-color LED, Alarm button 114 114 * Datalog 115 115 117 +(% style="display:none" %) 116 116 117 117 120 + 118 118 == 1.4 Applications == 119 119 120 120 ... ... @@ -121,8 +121,10 @@ 121 121 * Logistics and Supply Chain Management 122 122 * Human tracking 123 123 127 +(% style="display:none" %) 124 124 125 125 130 + 126 126 = 2. Use TrackerD = 127 127 128 128 == 2.1 How it works? == ... ... @@ -140,7 +140,6 @@ 140 140 [[image:image-20230213110214-2.png||height="388" width="847"]] 141 141 142 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 146 146 ... ... @@ -149,7 +149,7 @@ 149 149 Each TrackerD is shipped with a sticker with the default device EUI as below: 150 150 151 151 152 -[[image: 1664501677253-891.png||_mstalt="296569"]]156 +[[image:image-20230426085815-1.png||height="259" width="558"]] 153 153 154 154 155 155 Input these keys to their LoRaWAN Server portal. Below is TTN V3 screen shot: ... ... @@ -157,11 +157,9 @@ 157 157 158 158 **__Add APP EUI in the application:__** 159 159 160 - 161 161 [[image:1664501711466-918.png||_mstalt="295828"]] 162 162 163 163 164 - 165 165 [[image:1664501721248-725.png||_mstalt="294450"]] 166 166 167 167 ... ... @@ -168,7 +168,6 @@ 168 168 [[image:1664501734705-405.png||_mstalt="293306"]] 169 169 170 170 171 - 172 172 **__Add APP KEY and DEV EUI:__** 173 173 174 174 ... ... @@ -175,7 +175,6 @@ 175 175 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/1654671889112-678.png?rev=1.1||_mstalt="298233" alt="1654671889112-678.png"]] 176 176 177 177 178 - 179 179 (% style="color:blue" %)**Step 2**:(%%) Push this button will activate this device. 180 180 181 181 (% id="cke_bm_7709S" style="display:none" %) [[image:1664502835802-546.png||_mstalt="295061"]] ... ... @@ -192,7 +192,7 @@ 192 192 Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 193 193 194 194 * (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 195 -* (% style="color:#037691" %)**BLE or WiFi ONLY: **(%%)** **Only obtain iBeacon info via BLE and uplinkor obtain wifi ssid info via WiFi anduplink. Design for Indoor tracking.195 +* (% style="color:#037691" %)**BLE: **(%%)** **Only obtain iBeacon info via BLE and uplink uplink. Design for Indoor tracking. 196 196 * (% 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. 197 197 198 198 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. ... ... @@ -203,15 +203,14 @@ 203 203 === 2.4.1 Uplink FPORT~=5, Device Status === 204 204 205 205 206 -Uplink the device configures with FPORT=5. Once TrackerD Joined the network, it will uplink this message to the server. After the first uplink, TrackerD will uplink Device Status every 12 hours. 206 +Uplink the device configures with (% style="color:blue" %)**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 207 208 -Use can also get the Device Status uplink through the downlink command: **Downlink: 0x2301** 208 +Use can also get the Device Status uplink through the downlink command: (% style="color:#037691" %)**Downlink: 0x2301** 209 209 210 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:440px" %) 211 +|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**Size(bytes)**|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)1|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 30px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 40px;background-color:#D9E2F3;color:#0070C0" %)1|=(% style="width: 40px;background-color:#D9E2F3;color:#0070C0" %)1 212 +|(% 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 210 210 211 -(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %) 212 -|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)1|=(% style="width: 40px;" %)1 213 -|=(% style="width: 108px;" %)**Value**|(% style="width:82px" %)Sensor Model|(% style="width:83px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:84px" %)Sub-band|(% style="width:44px" %)BAT|(% style="width:63px" %)SMOD|(% style="width:60px" %)Status 214 - 215 215 [[image:1665301570342-765.png||_mstalt="294580"]] 216 216 217 217 ... ... @@ -223,31 +223,30 @@ 223 223 224 224 (% style="color:#037691" %)**Frequency Band**: 225 225 226 - *0x01: EU868225 +0x01: EU868 227 227 228 - *0x02: US915227 +0x02: US915 229 229 230 - *0x03: IN865229 +0x03: IN865 231 231 232 - *0x04: AU915231 +0x04: AU915 233 233 234 - *0x05: KZ865233 +0x05: KZ865 235 235 236 - *0x06: RU864235 +0x06: RU864 237 237 238 - *0x07: AS923237 +0x07: AS923 239 239 240 - *0x08: AS923-1239 +0x08: AS923-1 241 241 242 - *0x09: AS923-2241 +0x09: AS923-2 243 243 244 - *0x0a: AS923-3243 +0x0a: AS923-3 245 245 246 -Sub- 245 +(% style="color:#037691" %)**Sub-Band:**(%%) value 0x00~~0x08(only forAU915,US915,Others are 0xFF) 247 247 248 248 (% style="color:#037691" %)**BAT:**(%%) shows the battery voltage for TrackerD. 249 249 250 - 251 251 (% style="color:#037691" %)**Ex1:**(%%) 0x0FA2 = 4002mV 252 252 253 253 Use can also get the Device Status uplink through the downlink command: ... ... @@ -255,56 +255,48 @@ 255 255 256 256 (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40 257 257 258 -(% border="1 .5" style="background-color:#ffffcc;color:green;width:270px" %)259 -| =(% scope="row" style="width:;" %)**Size(bit)**|(% style="width:50px" %)1bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit260 -| =(% style="width:;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings256 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:270px" %) 257 +|(% style="width:60px" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:80px" %)2 bits|(% style="width:80px" %)4 bits 258 +|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings 261 261 262 -(% style="color:blue" %)** 260 +(% style="color:blue" %)**SMOD:** 263 263 264 -(% style="color:red" %)** 262 +(% style="color:red" %)**1 :** (%%) GPS ONLY 265 265 266 -(% style="color:red" %)** 264 +(% style="color:red" %)**2 :** (%%) BLE ONLY 267 267 268 -(% style="color:red" %)** 266 +(% style="color:red" %)**3 :** (%%) GPS/BLE Hybrid 269 269 270 270 271 -(% style="color:blue" %)** 269 +(% style="color:blue" %)**GPS_MOD: Define how to send GPS payload** 272 272 273 -(% style="color:red" %)** 271 +(% style="color:red" %)**0 : ** (%%) Enable uploading on-board Temperature and humidity values 274 274 275 -(% style="color:red" %)** 273 +(% style="color:red" %)**1 :** (%%) Disable uploading on-board Temperature and humidity values 276 276 277 277 278 -(% style="color:blue" %)** 276 +(% style="color:blue" %)**BLE_Settings:** 279 279 280 -(% style="color:red" %)** 278 +(% style="color:red" %)**1: ** (%%) BLE Positioning with Strongest iBeacon 281 281 282 -(% _mstmutation="1" style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(% _mstmutation="1" style="color:blue" %)(V1.4.1 Version support this function later)(%%) 283 283 284 - 285 285 (% style="color:#037691" %)**Status Field (total 1 byte)**(%%): 0x02 286 286 287 -(% border="1 .5" style="background-color:#ffffcc;color:green;width:412.222px" %)288 -| =(% scope="row" style="width:5px;" %)**Size(bit)**|(% style="width:68px" %)5 Bits|(% style="width:87px" %)1 Bit|(% style="width:49px" %)1 Bit|(% style="width:126px" %)1 Bit289 -| =(% style="width:;" %)**Value**|(% style="width:68px" %)Reserve|(% style="width:87px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:49px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]]283 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:413px" %) 284 +|(% style="width:77px" %)**Size(bit)**|(% style="width:70px" %)5 Bits|(% style="width:88px" %)1 Bit|(% style="width:50px" %)1 Bit|(% style="width:128px" %)1 Bit 285 +|(% style="width:75px" %)**Value**|(% style="width:68px" %)Reserve|(% style="width:87px" %)[[PNACKMD>>||anchor="H2.4.4A0UplinkFPORT3D42CHistoryGNSSPositioning"]]|(% style="width:49px" %)[[LON>>||anchor="H3.2.5Disable2FEnableLEDflash"]]|(% style="width:126px" %)[[Transport Mode>>||anchor="H2.9TransportMode"]] 290 290 287 +(% style="display:none" %) 291 291 292 292 293 293 === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 294 294 295 295 296 -Users can use **AT+SMOD=1,0,0** to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes, 293 +Users can use (% style="color:blue" %)**AT+SMOD=1,0,0**(%%) to enable uploading on-board Temperature and humidity values, and the total payload will be 15 bytes, 297 297 298 - 299 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %) 300 -|=(% scope="row" style="width: 60px;" %)((( 301 -**Size(bytes)** 302 -)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)((( 303 -2 304 -)))|(% style="width:30px" %)((( 305 -2 306 -))) 307 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 295 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:320px" %) 296 +|(% style="width:60px" %)**Size(bytes)**|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)2|(% style="width:30px" %)2 297 +|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 308 308 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 309 309 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]]|(% style="width:40px" %)[[Hum>>||anchor="HHum:"]]|(% style="width:87px" %)[[Tem>>||anchor="HTem:"]] 310 310 ... ... @@ -313,15 +313,18 @@ 313 313 314 314 ==== (% style="color:blue" %)**Alarm & BAT:**(%%) ==== 315 315 316 -(% border="1 .2" cellspacing="3" style="background-color:#ffffcc;color:green;width:279.222px" %)317 -| =(% scope="row" style="width:50px;" %)**Size(bit)**|(% style="width:50px" %)1 bit|(% style="width:69px" %)1 bit|(% style="width:63px" %)14 bits318 -| =(% style="width:;" %)**Value**|(% style="width:67px" %)reserve|(% style="width:69px" %)Alarm Indicate|(% style="width:63px" %)[[BAT>>||anchor="HBAT:"]]306 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:321px" %) 307 +|(% style="width:60px" %)**Size(bit)**|(% style="width:60px" %)1 bit|(% style="width:134px" %)1 bit|(% style="width:67px" %)14 bits 308 +|(% style="width:72px" %)**Value**|(% style="width:67px" %)reserve|(% style="width:114px" %)Alarm Indicate|(% style="width:62px" %)[[BAT>>||anchor="HBAT:"]] 319 319 310 +(% style="display:none" %) 311 + 312 + 320 320 ==== (% style="color:blue" %)**FLAG:**(%%) ==== 321 321 322 -(% border="1 .2" cellspacing="3" style="background-color:#ffffcc;color:green;width:183.222px" %)323 -| =(% scope="row" style="width:50px;" %)**Size(bit)**|(% style="width:30px" %)2 bits|(% style="width:52px" %)1 bit324 -| =(% style="width:;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:52px" %)[[LON>>||anchor="HLON:"]]315 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:184px" %) 316 +|(% style="width:68px" %)**Size(bit)**|(% style="width:61px" %)2 bits|(% style="width:55px" %)1 bit 317 +|(% style="width:79px" %)**Value**|(% style="width:56px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:50px" %)[[LON>>||anchor="HLON:"]] 325 325 326 326 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A 327 327 ... ... @@ -346,7 +346,6 @@ 346 346 [[image:1664502166010-515.png||_mstalt="291395"]] 347 347 348 348 349 - 350 350 ==== (% style="color:blue" %)**Alarm:**(%%) ==== 351 351 352 352 **Example: ** 0x4B & 0x40 >> 6 = 0x01 ... ... @@ -368,7 +368,6 @@ 368 368 369 369 (% style="display:none" %) (%%) 370 370 371 - 372 372 ==== (% style="color:blue" %)**MOD:**(%%) ==== 373 373 374 374 **Example: ** (0x60>>6) & 0x3f =1 ... ... @@ -412,14 +412,12 @@ 412 412 === 2.4.3 Uplink FPORT~=3, Realtime GNSS Positioning (Default Mode) === 413 413 414 414 415 -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) 406 +The default uplink payload includes total 11 bytes ((% style="color:blue" %)**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) 416 416 417 417 418 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %) 419 -|=(% scope="row" style="width: 60px;" %)((( 420 -**Size(bytes)** 421 -)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1 422 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 409 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:300px" %) 410 +|(% style="width:60px" %)**Size(bytes)**|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:70px" %)2|(% style="width:50px" %)1 411 +|(% style="width:69px" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 423 423 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 424 424 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] 425 425 ... ... @@ -441,11 +441,9 @@ 441 441 442 442 The payload is 15 bytes, as below. 443 443 444 -(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 445 -|=(% scope="row" %)((( 446 -**Size(bytes)** 447 -)))|4|4|2|1|1|1|1|1 448 -|=**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 433 +(% border="1" style="background-color:#f2f2f2; width:500px" %) 434 +|**Size(bytes)**|4|4|2|1|1|1|1|1 435 +|**Value**|Latitude|Longitude|Year|Month|Day|Hous|Min|Sen 449 449 450 450 [[image:image-20221009160309-2.png||_mstalt="429312"]] 451 451 ... ... @@ -458,11 +458,9 @@ 458 458 User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings. 459 459 460 460 461 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:450px" %) 462 -|=(% scope="row" style="width: 60px;" %)((( 463 -**Size(bytes)** 464 -)))|(% 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 465 -|=(% style="width: 50px;" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)((( 448 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %) 449 +|(% style="width:60px" %)**Size(bytes)**|(% 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 450 +|(% style="width:50px" %)**Value**|(% style="width:44px" %)[[UUID>>||anchor="HLocationinfo:"]]|(% style="width:61px" %)((( 466 466 iBeacon MAJOR 467 467 )))|(% style="width:63px" %)((( 468 468 iBeacon MINOR ... ... @@ -487,52 +487,50 @@ 487 487 488 488 (% style="display:none" %) (%%) 489 489 490 - 491 491 === 2.4.6 Uplink FPORT~=7, Alarm information status(Since firmware 1.4.4) === 492 492 493 493 494 494 The upward link device is configured to FPORT = 7. Once Trackerd alarm, it will upload the news to the server. 495 495 496 -(% border="1 .5" cellspacing="3" style="background-color:#ffffcc;color:green;width:450px" %)497 -|**Size(bytes)**|2|1 498 -|**Value**|[[Alarm & BAT>>path:#HAlarm26BAT:]]|Mod+lon 480 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:284.818px" %) 481 +|(% style="width:97px" %)**Size(bytes)**|(% style="width:103px" %)2|(% style="width:81px" %)1 482 +|(% style="width:97px" %)**Value**|(% style="width:103px" %)[[Alarm & BAT>>path:#HAlarm26BAT:]]|(% style="width:81px" %)Mod+lon 499 499 500 500 [[image:image-20230302145315-1.png]] 501 501 502 -alarm=(bytes[0] & 0x40) ~/~/ Alarm status 486 +**alarm**=(bytes[0] & 0x40) ~/~/ Alarm status 503 503 504 -batV=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000; ~/~/ Battery,units:V 488 +**batV**=~(~(~(bytes[0] & 0x3f) <<8) | bytes[1])/1000; ~/~/ Battery,units:V 505 505 506 -mod = bytes[2] & 0xC0; 490 +**mod** = bytes[2] & 0xC0; 507 507 508 -Lon=(bytes[2] & 0x20) 492 +**Lon**=(bytes[2] & 0x20) 509 509 510 510 511 -=== 2.4.7 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 512 512 496 +=== 2.4.7 Uplink FPORT~=9, BLE Positioning with Multiple iBeacon(Since firmware 1.4.7) === 513 513 514 -TrackerD supports WiFiscansfor indoor positioning. User can set[[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]]to**WiFi**so TrackerD will scanWiFiandfindthestrongestWiFi infoand uplink.498 +TrackerD supports BLE scanning for indoor positioning. Users can set SMOD to BLE pure or GPS/BLE Hybrid, so TrackerD will scan up to 40 BLE iBeacons and send uplinks. 515 515 500 +User can set [[(% class="wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink wikiinternallink" %)**BLEMASK**>>path:#H3.2.11A0SetBLEMASKtofilterBLEiBeacon]](%%) so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings. 516 516 517 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %) 518 -|=(% scope="row" style="width: 60px;" %)((( 519 -**Size(bytes)** 520 -)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1 521 -|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)((( 522 -[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 523 -)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 502 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:348px" %) 503 +|**Size(bytes)**|2|2|1|…..|2|2|1|2|1 504 +|**Value**|iBeacon MAJOR|iBeacon MINOR|iBeacon RSSI|…..|iBeacon MAJOR|iBeacon MINOR|iBeacon RSSI|[[Alarm & BAT>>path:#HAlarm26BAT:]]|[[FLAG>>path:#HFLAG:]] 524 524 525 -(% class="wikigeneratedid" %) 526 -[[image:1 667288597595-714.png||_mstalt="299598"height="212" width="1151"]]506 +(% class="wikigeneratedid" id="H" %) 507 +[[image:image-20231023103116-1.png||height="448" width="901"]] 527 527 509 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 510 +* (% style="color:#037691" %)**MAJOR:** (%%) The MAJOR from the strongest iBeacon. 511 +* (% style="color:#037691" %)**MINOR:** (%%)The MINOR from the strongest iBeacon. 512 +* (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 528 528 529 - *(%style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV).530 -* (%style="color:#037691"%)**SSID:**(%%)WiFiname.531 - * (% style="color:#037691"%)**RSSI: **(%%)TheRSSIfromthestrongest WiFi.514 +(% class="wikigeneratedid" %) 515 +**Note: This mode does not have a fixed decoder. Its decoder depends on the number of beacons and can be parsed according to the order of the payload.** 516 +payload format: (Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...+BAT+State 532 532 533 -(% style="display:none" %) (%%) 534 534 535 - 536 536 === 2.4.8 Add Payload format in TTN V3 === 537 537 538 538 ... ... @@ -540,15 +540,11 @@ 540 540 541 541 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 542 542 543 - 544 544 [[image:1664502649601-895.png||_mstalt="296985"]] 545 545 546 546 529 +Add the decoder from this link: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] 547 547 548 -Add the decoder from this link: 549 - 550 -[[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD>>https://github.com/dragino/dragino-end-node-decoder/tree/main/TrackerD]] 551 - 552 552 Save the change the uplink message will be parsed. As below: 553 553 554 554 [[image:1664502676891-606.png||_mstalt="296673"]] ... ... @@ -561,7 +561,6 @@ 561 561 562 562 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]] 563 563 564 - 565 565 [[image:1664502695771-538.png||_mstalt="297349"]] 566 566 567 567 ... ... @@ -572,7 +572,6 @@ 572 572 573 573 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]] 574 574 575 - 576 576 [[image:1664502715371-321.png||_mstalt="292162"]] 577 577 578 578 ... ... @@ -581,13 +581,15 @@ 581 581 582 582 ~1. Install node-red, please refer to the installation method in the link: 583 583 584 - [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]] 561 +[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H1.A0Installation]] 562 + 563 + 585 585 2. Import the created flow template, please refer to the import method in the link: 586 586 587 - 588 - The address of the flow template:566 +[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0Importsampleflow]] 567 + 589 589 590 - [[dragino-end-node-decoder/TrackerD.json at main · dragino/dragino-end-node-decoder · GitHub>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/TrackerD.json]] 569 +The address of the flow template: [[dragino-end-node-decoder/TrackerD.json at main · dragino/dragino-end-node-decoder · GitHub>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/TrackerD.json]] 591 591 592 592 (% style="color:red" %)**Note: If you are using NODE-RED for the first time, please search and install the two plug-ins in the figure below in node-red to fully use the flow template.** 593 593 ... ... @@ -597,6 +597,24 @@ 597 597 [[image:image-20230307135932-2.png||height="527" width="1044"]] 598 598 599 599 579 +3. Display the map 580 + Enter the link to the map: 581 + 582 + Change its suffix to ditu:http:~/~/119.91.62.30:1880/**ditu/** 583 + 584 +**~ **[[image:image-20230308115430-1.png||height="548" width="1041"]] 585 + 586 + 587 + Hit all input in input stream 588 + 589 + [[image:image-20230308115616-2.png||height="563" width="1070"]] 590 + 591 + 592 + View map again 593 + 594 +[[image:image-20230308115701-3.png||height="571" width="1085"]] 595 + 596 + 600 600 == 2.8 Datalog Feature == 601 601 602 602 ... ... @@ -616,10 +616,9 @@ 616 616 617 617 618 618 ((( 619 -User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. 616 +User can push the (% style="color:red" %)**RED button**(%%) by more than 5 seconds to enter Alarm Mode. Alarm Mode is used to send SOS info to IoT platform. 620 620 ))) 621 621 622 - 623 623 ((( 624 624 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. 625 625 ))) ... ... @@ -640,8 +640,10 @@ 640 640 == 2.10 Transport Mode == 641 641 642 642 643 -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. 639 +In Transport Mode, TrackerD will check if there is motion (threldhold defined by **[[PT)>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** . If there is no motion, device will send uplinks every 20 minutes (Defined by **[[TDC)>>||anchor="H3.2.1SetTransmitInterval"]]** . If there is motion, device will send uplink every 5 minutes(defined by **[[MTDC)>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]**. 644 644 641 +When device is set in Transport Mode, it will uplink more frequenctly during moving. 642 + 645 645 * **[[MTDC>>||anchor="H3.2.3SetTransportModePackettransmissioninterval"]]** defines the Uplink Interval during transportation. 646 646 * **[[TDC>>||anchor="H3.2.1SetTransmitInterval"]]** defines the uplink interval when TrackerD is stactic. 647 647 * **[[PT>>||anchor="H3.2.16GetorSetThresholdformotiondetectFF08Sincefirmware1.4.3FF09"]]** defines the threldhold to detect a motion. ... ... @@ -648,12 +648,11 @@ 648 648 649 649 (% style="display:none" %) (%%) 650 650 651 - 652 652 == 2.11 LED Status == 653 653 654 654 655 -(% border="1 .5" style="background-color:#ffffcc; width:500px" %)656 -|=(% style="width: 150px;" %)**Event**|=(% style="width: 200px;" %)**Action**|=(% style="width: 150px;" %)**AT+LON to control on/off** 652 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:500px" %) 653 +|=(% style="width: 150px;background-color:#D9E2F3;color:#0070C0" %)**Event**|=(% style="width: 200px;background-color:#D9E2F3;color:#0070C0" %)**Action**|=(% style="width: 150px;background-color:#D9E2F3;color:#0070C0" %)**AT+LON to control on/off** 657 657 |(% 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 658 658 |(% style="width:157px" %)**Join request**|(% style="width:271px" %)(% style="color:green" %)**Green** (%%)led fast blink once (200ms)|(% style="width:202px" %)Yes 659 659 |(% style="width:157px" %)**Join Success**|(% style="width:271px" %)(% style="color:green" %)**Green**(%%) led on 5 second|(% style="width:202px" %)N/A ... ... @@ -668,7 +668,6 @@ 668 668 669 669 (% style="display:none" %) (%%) 670 670 671 - 672 672 == 2.12 Button Function == 673 673 674 674 ... ... @@ -685,8 +685,8 @@ 685 685 686 686 (% style="display:none" %) (%%) 687 687 688 -(% border="1" style="background-color:#fff fcc; width:510px" %)689 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description** 684 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %) 685 +|=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 205px;background-color:#D9E2F3;color:#0070C0" %)**Action**|=(% style="width: 205px;background-color:#D9E2F3;color:#0070C0" %)**Description** 690 690 |(% 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.8AlarmMode"]] 691 691 |(% 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 692 692 |(% 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. ... ... @@ -693,7 +693,6 @@ 693 693 694 694 (% style="display:none" %) (%%) 695 695 696 - 697 697 == 2.13 USB Port Function == 698 698 699 699 ... ... @@ -706,7 +706,16 @@ 706 706 707 707 (% style="display:none" %) (%%) 708 708 704 +== 2.14 Sleep Mode == 709 709 706 + 707 +(% style="color:blue" %)**Sleep Mode:**(%%) To prevent accidental touch of the red button during transportation or assembly, so the peripherals of the device are turned off and enter deep sleep. 708 + 709 +In SLEEP mode, you need to reset by (% style="color:#037691" %)**reset button**. 710 + 711 +Use the** (% style="color:#4472c4" %)AT+SLEEP(%%)** command to put the device into sleep. 712 + 713 + 710 710 = 3. Configure TrackerD via AT command or LoRaWAN downlink = 711 711 712 712 ... ... @@ -720,7 +720,6 @@ 720 720 721 721 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. 722 722 723 - 724 724 [[image:1664502999401-486.png||_mstalt="296985"]] 725 725 726 726 ... ... @@ -841,7 +841,6 @@ 841 841 842 842 SMOD define how TrackerD scan and uplink data: 843 843 844 - 845 845 * (% style="color:blue" %)**AT Command:** 846 846 847 847 (% style="color:#037691" %)**AT+SMOD=aa,bb,cc** ... ... @@ -850,7 +850,7 @@ 850 850 851 851 * (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 852 852 853 -* (% style="color:red" %)**2: BLE or WiFi ONLY: **(%%)Only obtain iBeacon info via BLE and uplinkor obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking.855 +* (% style="color:red" %)**2: BLE : **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking. 854 854 855 855 * (% 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. 856 856 ... ... @@ -863,8 +863,7 @@ 863 863 (% style="color:#037691" %)**cc: ** 864 864 865 865 * (% _mstmutation="1" style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 866 - 867 -* (% _mstmutation="1" style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% _mstmutation="1" style="color:#037691" %)V1.4.1 Version support this function later(%%)) 868 + 868 868 869 869 (% style="color:blue" %)**Example:** 870 870 ... ... @@ -874,9 +874,8 @@ 874 874 875 875 AT+SMOD=2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 876 876 877 - AT+SMOD=2,0, 2WiFi)SSID+Rssi+BAT+State878 + AT+SMOD=2,0,3 ~-~-> (iBeacon) (Major + Minor+Rssi)+(Major + Minor+Rssi)+...(Maximum forty group)...+BAT+State 878 878 879 - 880 880 * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** 881 881 882 882 (% style="color:#037691" %)**0xA5 01 00 00** (%%) ~/~/ Same as AT+SMOD=1,0,0 ... ... @@ -887,10 +887,8 @@ 887 887 888 888 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. 889 889 890 - 891 891 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. 892 892 893 - 894 894 * (% style="color:blue" %)**AT Command:** 895 895 896 896 (% style="color:#037691" %)**AT+FTIME=xx** (%%) **~-~-> ** Set to use xx as max fix time. ... ... @@ -908,10 +908,8 @@ 908 908 909 909 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. 910 910 911 - 912 912 A GPS packet with lower PDOP has higher accuracy. PDOP default value is 2.0 913 913 914 - 915 915 * (% style="color:blue" %)**AT Command:** 916 916 917 917 (% style="color:#037691" %)**AT+PDOP=2.5 ** (%%) **~-~-> ** Set PDOP to 2.5 ... ... @@ -934,11 +934,11 @@ 934 934 (% style="color:#037691" %)**AT+CFM=xx** 935 935 936 936 937 -** ~Example:**933 +**Example:** 938 938 939 - 935 +AT+CFM=0 **~-~-> ** Disable confirmation 940 940 941 - 937 +AT+CFM=1 **~-~-> ** Enable confirmation 942 942 943 943 944 944 * (% style="color:blue" %)**Downlink Payload (prefix 0x05):** ... ... @@ -976,92 +976,167 @@ 976 976 977 977 (% style="color:blue" %)**AT Command:** 978 978 979 - 975 +(% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 980 980 981 - 977 +(% _mstmutation="1" style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 982 982 983 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1 )**979 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 984 984 985 985 Example: 0xB2 01 02 03 04 05 06 ~/~/ Set BLEMASK to 123456 986 986 987 987 988 -=== 3.2.13 SetWiFIMASKtofilter WiFiSSID(Since firmware 1.4.1)===984 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 989 989 990 990 991 - WiFiMASK isto filterthe unwantedWiFi SSID duringscan. Forexample,if WiFiMASK is123456. TrackerDwillonlyuplink SSID info which includes123456as prefix.It will ignoreall other WiFi which doesn’tcontact 123456inthe SSID.987 +Users can use this feature to enable/disable Information printing. 992 992 993 -(% style="color: red" %)**Note: WiFiMASKrange is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will bedisabled.**989 +(% style="color:blue" %)**AT Command:** 994 994 991 +(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/ (Disable (0), Enable (1), default:0) 992 +\\Example: AT+SHOWID=1 ~-~-> Enable Information printing. 993 + 994 + 995 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 996 + 997 + 998 +The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. 999 + 995 995 (% style="color:blue" %)**AT Command:** 996 996 997 - _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=123456**(%%) ~/~/SetWiFiMASK=1234561002 +(% style="color:#037691" %)**AT+CHE=1 **(%%) ~/~/ set one channels mode 998 998 999 - (% _mstmutation="1" style="color:#037691" %)**AT+WiFiMASK=0** (%%) ~/~/ disable WiFiMASK 1000 1000 1001 -(% style="color:blue" %)**Downlink Payload: (Prefix :0xB3)(Since firmware 1.4.1)**1005 +(% style="color:blue" %)**Downlink Payload:0X24** 1002 1002 1003 -Example: B3 01 0203 04 05 06tWiFiMASKto1234561007 +Example: 0x24 01 ~/~/ Same as AT+CHE=1 1004 1004 1005 1005 1006 -=== 3.2.1 4Disable/EnableInformationprinting(Since firmware 1.4.1)===1010 +=== 3.2.15 Get or Set Threshold for motion detect(Since firmware 1.4.3) === 1007 1007 1008 1008 1009 -User scanuse thisfeature to enable/disableInformationprinting.1013 +User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event. 1010 1010 1011 1011 (% style="color:blue" %)**AT Command:** 1012 1012 1013 -(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/ (Disable (0), Enable (1), default:0) 1014 -\\Example: AT+SHOWID=1 ~-~-> Enable Information printing. 1017 +(% style="color:#037691" %)**AT+PT=xx** 1015 1015 1019 +Example: 1016 1016 1017 -= == 3.2.15GetorSetEightChannels Mode, only for us915, AU915(Sincefirmware1.4.1) ===1021 +AT+PT=14 ~-~-> Set to detect car motion. 1018 1018 1023 +AT+PT=41 ~-~-> set to detect walk motion. 1019 1019 1020 -The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. 1021 1021 1026 +(% style="color:blue" %)**Downlink Payload:0xB4** 1027 + 1028 +0xB4 14 ~/~/ Same as AT+PT=14 1029 + 1030 + 1031 +=== 3.2.16 Set AT command window time(Since firmware 1.4.5) === 1032 + 1033 + 1034 +AT command window time setting, customers can set the required time according to their own operation mode.The unit is second. 1035 + 1022 1022 (% style="color:blue" %)**AT Command:** 1023 1023 1024 -(% style="color:#037691" %)**AT+ CHE=1**(%%) ~/~/ set one channels mode1038 +(% style="color:#037691" %)**AT+ATST=XX** 1025 1025 1040 +Example: 1026 1026 1027 - (%style="color:blue"%)**DownlinkPayload:0X24**1042 +AT+ATST=15 ~-~-> Set the time to 15 seconds 1028 1028 1029 - Example:0x2401 ~/~/ Sameas AT+CHE=11044 +(% style="color:blue" %)**Downlink Payload:0XB5** 1030 1030 1046 +0xB5 0F ~/~/ Same as AT+ATST=15 1031 1031 1032 -=== 3.2.16 Get or Set Threshold for motion detect(Since firmware 1.4.3) === 1033 1033 1049 +=== 3.2.17 Set the stepmeter mode(Since firmware 1.4.5) === 1034 1034 1035 -User can set the motion detect thredhold for transportation mode. The smaller the value, the more sensitivity to trigger a motion event. 1036 1036 1052 +After setting the step counting mode, it cannot be interrupted by motion. This mode is very power consuming. Used on some special occasions. 1053 + 1037 1037 (% style="color:blue" %)**AT Command:** 1038 1038 1039 -(% style="color:#037691" %)**AT+P T=xx**1056 +(% style="color:#037691" %)**AT+PM=xx** 1040 1040 1041 - 1058 +Example: 1042 1042 1043 - T=14~-~->Set todetectcar motion.1060 +AT+PM=1 ~-~-> Turn on step counting mode 1044 1044 1045 - T=41etto detectwalk motion.1062 +AT+PM=0 ~-~-> Turn OFF step counting mode 1046 1046 1064 +(% style="color:blue" %)**Downlink Payload:0XB6** 1047 1047 1048 -(% style="color:blue" %)**Downlink Payload:0xB4**(%%) 1049 -0xB4 14 ~/~/ Same as AT+PT=14 1066 +0xB6 01 ~/~/ Same as AT+PM=1 1050 1050 1051 1051 1052 -= 4.tingforDifferent Scenarios=1069 +=== 3.2.18 Set down the decline detection mode(Since firmware 1.4.5) === 1053 1053 1054 1054 1072 +This mode is used in conjunction with AT+PT(The recommended threshold is between 50 and 70, you need to set it according to the environment yourself). This function is used in hospitals, nursing homes, nursing homes and other places to prevent the elderly and patients from falling. No one knows. 1055 1055 1056 - =5. Upload Firmware=1074 +(% style="color:blue" %)**AT Command:** 1057 1057 1058 - ==5.1 FirmwareChange Log==1076 +(% style="color:#037691" %)**AT+FD=xx** 1059 1059 1078 +**Example:** 1060 1060 1080 +AT+FD=1 ~-~-> Turn on the Fall detection 1081 + 1082 +AT+FD=0 ~-~-> Turn OFF the Fall detection 1083 + 1084 +(% style="color:blue" %)**Downlink Payload:0XB7** 1085 + 1086 +0xB7 01 ~/~/ Same as AT+FD=1 1087 + 1088 + 1089 +=== 3.2.19 Disable/Enable buzzer(Since firmware 1.4.6) === 1090 + 1091 + 1092 +Disable/Enable buzzer for Alarm, downlink and uplink 1093 + 1094 +(% style="color:blue" %)**AT Command:** 1095 + 1096 +(% style="color:#037691" %)**AT+BEEP=XX** 1097 + 1098 +Example: 1099 + 1100 +AT+BEEP=1 ~-~-> Turn on the buzzer 1101 + 1102 +AT+BEEP=0 ~-~-> Turn OFF the buzzer 1103 + 1104 +(% style="color:blue" %)**Downlink Payload:0XB9** 1105 + 1106 +0xB9 01 ~/~/ Same as AT+BEEP=1 1107 + 1108 + 1109 +=== 3.2.20 Set long press time(Since firmware 1.4.6) === 1110 + 1111 + 1112 +When using the red button Changan to alarm, press and hold the time to set 0~~10 seconds, which is convenient for use scenarios. 1113 + 1114 +(% style="color:blue" %)**AT Command:** 1115 + 1116 +(% style="color:#037691" %)**AT+EAT=XX** 1117 + 1118 +Example: 1119 + 1120 +AT+EAT=2 ~-~-> Set the long press time to 2s 1121 + 1122 +(% style="color:blue" %)**Downlink Payload:0XBA** 1123 + 1124 +0xBA 02 ~/~/ Same as AT+EAT=2 1125 + 1126 + 1127 += 4. Upload Firmware = 1128 + 1129 +== 4.1 Firmware Change Log == 1130 + 1131 + 1061 1061 **[[See this link>>url:https://github.com/dragino/TrackerD]]** 1062 1062 1063 1063 1064 -== 5.2 How to upgrade firmware ==1135 +== 4.2 How to upgrade firmware == 1065 1065 1066 1066 1067 1067 User can use the TrackerD's USB port to upgrade firmware into it. The hardware connection for upgrade firmware is as below: ... ... @@ -1109,11 +1109,11 @@ 1109 1109 [[image:image-20221207133911-7.png]] 1110 1110 1111 1111 1112 -= 6. Developer Guide =1183 += 5. Developer Guide = 1113 1113 1114 -== 6.1 Compile Source Code ==1185 +== 5.1 Compile Source Code == 1115 1115 1116 -=== 6.1.1 Set up ARDUINO compile environment ===1187 +=== 5.1.1 Set up ARDUINO compile environment === 1117 1117 1118 1118 1119 1119 * **Download the latest Arduino software (IDE) from the Arduino official website: [[https:~~/~~/www.arduino.cc/en/Main/Software>>url:https://www.arduino.cc/en/Main/Software]]** ... ... @@ -1130,7 +1130,7 @@ 1130 1130 [[image:1664503715811-892.png||_mstalt="295698"]] 1131 1131 1132 1132 1133 -=== 6.1.2 Build the development environment ===1204 +=== 5.1.2 Build the development environment === 1134 1134 1135 1135 1136 1136 **~1. Download and install arduino IDE** ... ... @@ -1207,7 +1207,7 @@ 1207 1207 [[image:1664503752288-974.png||_mstalt="298194"]] 1208 1208 1209 1209 1210 -== 6.2 Source Code ==1281 +== 5.2 Source Code == 1211 1211 1212 1212 1213 1213 * (% style="color:blue" %)**Open the example in the TrackerD file, please select the correct port in the IDE, as shown below:** ... ... @@ -1227,23 +1227,22 @@ 1227 1227 [[image:1664503824081-592.png||_mstalt="294918"]] [[image:1664503831430-500.png||_mstalt="290784"]] 1228 1228 1229 1229 1230 -= 7. FAQ =1301 += 6. FAQ = 1231 1231 1232 -== 7.1 How to change the LoRa Frequency Bands/Region? ==1303 +== 6.1 How to change the LoRa Frequency Bands/Region? == 1233 1233 1234 1234 1235 1235 User can follow the introduction for [[how to upgrade image>>||anchor="H5.UploadFirmware"]]. When download the images, choose the required image file for download. 1236 1236 1237 1237 1238 -== 7.2 What is the pin mapping for the USB program cable? ==1309 +== 6.2 What is the pin mapping for the USB program cable? == 1239 1239 1240 1240 1241 1241 [[image:1664499635206-262.png||_mstalt="295360"]] 1242 1242 1243 1243 1244 - 1245 -(% border="1.5" cellspacing="3" style="background-color:#ffffcc; color:green; width:314px" %) 1246 -|=(% style="width: 118px;" %)**Pin**|=(% style="width: 67px;" %)**Color**|=(% style="width: 123px;" %)**USB Pin** 1315 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:314px" %) 1316 +|=(% style="width: 120px;background-color:#D9E2F3;color:#0070C0" %)**Pin**|=(% style="width: 69px;background-color:#D9E2F3;color:#0070C0" %)**Color**|=(% style="width: 125px;background-color:#D9E2F3;color:#0070C0" %)**USB Pin** 1247 1247 |(% style="width:118px" %)A4,B4,A9,B9|(% style="width:67px" %)Red|(% style="width:123px" %)VCC 1248 1248 |(% style="width:118px" %)A7,B7|(% style="width:67px" %)White|(% style="width:123px" %)D- (N/A) 1249 1249 |(% style="width:118px" %)A6,B6|(% style="width:67px" %)Green|(% style="width:123px" %)D+(N/A) ... ... @@ -1256,9 +1256,9 @@ 1256 1256 (% style="display:none" %) (%%) 1257 1257 1258 1258 1259 -== 7.3 Notes on using different serial port tools for TrackerD ==1329 +== 6.3 Notes on using different serial port tools for TrackerD == 1260 1260 1261 -=== 7.3.1 Serial port utility ===1331 +=== 6.3.1 Serial port utility === 1262 1262 1263 1263 1264 1264 Serial port utility requires you to automatically add data streams. ... ... @@ -1269,13 +1269,12 @@ 1269 1269 [[image:image-20221102140621-1.png||_mstalt="425672"]] 1270 1270 1271 1271 1272 - 1273 1273 When using AT commands, the data flow needs to be adjusted to XON/XOFF 1274 1274 1275 1275 [[image:image-20221102140638-2.png||_mstalt="428727"]] 1276 1276 1277 1277 1278 -=== 7.3.2 SecureCRT ===1347 +=== 6.3.2 SecureCRT === 1279 1279 1280 1280 1281 1281 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. ... ... @@ -1287,7 +1287,7 @@ 1287 1287 [[image:image-20221102140712-4.png||_mstalt="427089"]] 1288 1288 1289 1289 1290 -=== 7.3.3 PUTTY ===1359 +=== 6.3.3 PUTTY === 1291 1291 1292 1292 1293 1293 [[image:image-20221102140748-5.png||_mstalt="430456"]] ... ... @@ -1299,7 +1299,7 @@ 1299 1299 [[image:image-20221102140801-6.png||_mstalt="427466"]] 1300 1300 1301 1301 1302 -== 7.4 How to modify source code to compile different frequency band bin file? ==1371 +== 6.4 How to modify source code to compile different frequency band bin file? == 1303 1303 1304 1304 1305 1305 (% class="box infomessage" %) ... ... @@ -1338,23 +1338,29 @@ 1338 1338 [[image:image-20221116111844-5.png||_mstalt="430144" height="551" width="708"]] 1339 1339 1340 1340 1341 -== 7.5 Are there example python example for BLE Indoor Positioning? ==1410 +== 6.5 Are there example python example for BLE Indoor Positioning? == 1342 1342 1343 1343 1344 -[[Operating instructions for BLE indoor positioning>>doc:.Example of BLE indoor positioning python.WebHome]] 1413 +[[Operating instructions for BLE indoor positioning>>doc:Main.User Manual for LoRaWAN End Nodes.TrackerD.Example of BLE indoor positioning python.WebHome]] 1345 1345 1346 1346 1347 -= 8TroubleShooting =1416 +== 6.6 Can alert mode and transport mode be used together? == 1348 1348 1349 -== 8.1 TDC is changed to 4294947296 and cause no uplink. == 1350 1350 1419 +Yes, you can also press the panic button to sound the alarm if set to transport mode 1351 1351 1421 + 1422 += 7 Trouble Shooting = 1423 + 1424 +== 7.1 TDC is changed to 4294947296 and cause no uplink. == 1425 + 1426 + 1352 1352 ((( 1353 1353 Before firmware v1.4.0: When the Transport Mode is enabled ((% style="color:blue" %)**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 1354 1354 ))) 1355 1355 1356 1356 1357 -== 8.2 Device not able get AT Command or show output after wake up from deep sleep mode ==1432 +== 7.2 Device not able get AT Command or show output after wake up from deep sleep mode == 1358 1358 1359 1359 1360 1360 ((( ... ... @@ -1362,9 +1362,9 @@ 1362 1362 ))) 1363 1363 1364 1364 1365 -== 8.3 Problem after Upgrading Firmware ==1440 +== 7.3 Problem after Upgrading Firmware == 1366 1366 1367 -=== 8.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading ===1442 +=== 7.3.1 "rst: (0x3 SW_RESET)" and Continue Restart after upgrading === 1368 1368 1369 1369 1370 1370 **Error Output** ... ... @@ -1380,18 +1380,17 @@ 1380 1380 ))) 1381 1381 1382 1382 1383 -=== 8.3.2 TrackerD's led light is always GREEN on after upgrading ===1458 +=== 7.3.2 TrackerD's led light is always GREEN on after upgrading === 1384 1384 1385 1385 1386 1386 It is because the partitions are different when upgrading versions above 1.4.1, and a new partition file needs to be added. Please refer to the operation steps in chapter 8.3.1 1387 1387 1388 1388 1389 -=== 8.3.3 "flash read err" after upgrade firmware ===1464 +=== 7.3.3 "flash read err" after upgrade firmware === 1390 1390 1391 1391 1392 1392 Error shows below, user might erase the entire flash include u-boot partition which cause this issue. 1393 1393 1394 - 1395 1395 [[image:image-20221122100004-1.png||_mstalt="423514" height="497" width="534"]] 1396 1396 1397 1397 ... ... @@ -1402,12 +1402,12 @@ 1402 1402 **Figure 2** 1403 1403 1404 1404 1405 -=== 8.3.4 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware ===1479 +=== 7.3.4 "Device Key become ff ff ff ff ff ff ff ff " after upgrade firmware === 1406 1406 1407 1407 1408 1408 User might erase the entire flash include keys and default settings which cause this issue. 1409 1409 1410 -After the upgrade is completed, enter **AT+CFG** as shown in the figure below. 1484 +After the upgrade is completed, enter (% style="color:blue" %)**AT+CFG**(%%) as shown in the figure below. 1411 1411 1412 1412 1413 1413 [[image:image-20221122100004-3.png||_mstalt="424242"]] ... ... @@ -1440,13 +1440,13 @@ 1440 1440 AT+APPSKEY=dacce2299ecd97a73ee3f80b5a46a559 ( no need for OTAA) 1441 1441 1442 1442 1443 -== 8.4 When positioning, it will restart or the PDOP setting is unsuccessful ==1517 +== 7.4 When positioning, it will restart or the PDOP setting is unsuccessful == 1444 1444 1445 1445 1446 1446 Please download version 1.4.2 again 1447 1447 1448 1448 1449 -== 8.5 How to deal with unsuccessful GPS positioning? ==1523 +== 7.5 How to deal with unsuccessful GPS positioning? == 1450 1450 1451 1451 1452 1452 1) Make Sure the device is in Open Area where can see the sky. ... ... @@ -1462,7 +1462,7 @@ 1462 1462 Please refer to this [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/TrackerD/#H3.2.9SetPDOPvalueforGPSfixaccuracy]] on how to set up PDOP 1463 1463 1464 1464 1465 -== 8.6 When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets ==1539 +== 7.6 When upgrading the firmware, the data is not completely erased, and the information does not return to normal after multiple resets == 1466 1466 1467 1467 1468 1468 When upgrading, use the erase button to upgrade ... ... @@ -1485,7 +1485,7 @@ 1485 1485 [[image:image-20221128111443-4.png||height="432" width="546"]] 1486 1486 1487 1487 1488 -Use **AT+FDR** command to reset and then use **AT+CFG** to check whether the configuration is back to normal 1562 +Use (% style="color:blue" %)**AT+FDR**(%%) command to reset and then use (% style="color:blue" %)**AT+CFG**(%%) to check whether the configuration is back to normal 1489 1489 1490 1490 [[image:image-20221128111850-5.png]] 1491 1491 ... ... @@ -1500,7 +1500,7 @@ 1500 1500 [[image:image-20221128112035-7.png]] 1501 1501 1502 1502 1503 -== 8.7 If you encounter the following problems, please upgrade to the latest version ==1577 +== 7.7 If you encounter the following problems, please upgrade to the latest version == 1504 1504 1505 1505 1506 1506 ~1. Press and hold the red button (more than 5 seconds), and the device and server do not respond. ... ... @@ -1508,9 +1508,16 @@ 1508 1508 2. Send some commands through the serial port to prompt an error (Example:AT+SMOD=1,0,1) 1509 1509 1510 1510 1511 -= 9.OrderInfo =1585 +== 7.8 Why when using some serial consoles, only inputting the first string port console will return "error"? == 1512 1512 1513 1513 1588 +Need to enter the entire command at once, not a single character. 1589 +User can open a command window or copy the entire command to the serial console. 1590 + 1591 + 1592 += 8. Order Info = 1593 + 1594 + 1514 1514 Part Number: (% style="color:blue" %)**TrackerD-XXX** 1515 1515 1516 1516 (% style="color:blue" %)**XXX**(%%): The default frequency band ... ... @@ -1532,7 +1532,7 @@ 1532 1532 (% style="display:none" %) (%%) 1533 1533 1534 1534 1535 -= 10. Packing Info =1616 += 9. Packing Info = 1536 1536 1537 1537 1538 1538 (% style="color:#037691" %)**Package Includes**: ... ... @@ -1557,9 +1557,10 @@ 1557 1557 1558 1558 * 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]]. 1559 1559 1560 -(% style="display:none" %) (%%)1641 +(% style="display:none" %) 1561 1561 1562 1562 1644 + 1563 1563 = 12. Reference = 1564 1564 1565 1565
- image-20230426085815-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +190.0 KB - Content
- image-20231023103116-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +48.2 KB - Content