Changes for page TrackerD -- LoRaWAN Tracker User Manual
Last modified by Xiaoling on 2025/04/27 16:48
From version 82.1
edited by Edwin Chen
on 2022/10/22 00:26
on 2022/10/22 00:26
Change comment:
There is no comment for this version
To version 107.1
edited by Bei Jinggeng
on 2022/11/07 09:24
on 2022/11/07 09:24
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 9 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.Bei - Content
-
... ... @@ -121,7 +121,7 @@ 121 121 * Logistics and Supply Chain Management 122 122 * Human tracking 123 123 124 -= 2. 1124 += 2. Use TrackerD = 125 125 126 126 127 127 == 2.1 How it works? == ... ... @@ -189,9 +189,9 @@ 189 189 190 190 Users can set TrackerD to different Positioning Mode for different applications. Below mod are supported. 191 191 192 -* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%) only get and uplink GPS location info.193 -* (% style="color:#037691" %)**BLE ONLY: 194 -* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 192 +* (% style="color:#037691" %)**GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 193 +* (% style="color:#037691" %)**BLE or WiFi ONLY: **(%%)** **Only obtain iBeacon info via BLE and uplink or obtain wifi ssid info via WiFi and uplink. Design for Indoor tracking. 194 +* (% style="color:#037691" %)**GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking. Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 195 195 196 196 Users can switch modes by [[changing SMOD>>||anchor="H3.2.7SetPositioningMode"]]. 197 197 ... ... @@ -208,8 +208,8 @@ 208 208 Use can also get the Device Status uplink through the downlink command: **Downlink: 0x2301** 209 209 210 210 211 -(% border="1.5" style="background-color:#ffffcc; color:green; width: 520px" %)212 -|=(% s cope="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;" %)1211 +(% border="1.5" style="background-color:#ffffcc; color:green; width:440px" %) 212 +|=(% style="width: 60px;" %)**Size(bytes)**|=(% style="width: 70px;" %)**1**|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)**1**|=(% style="width: 30px;" %)2|=(% style="width: 40px;" %)**2**|=(% style="width: 40px;" %)1 213 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 214 215 215 [[image:1665301570342-765.png]] ... ... @@ -253,12 +253,11 @@ 253 253 Use can also get the Device Status uplink through the downlink command: 254 254 255 255 256 - 257 257 (% style="color:#037691" %)**SMOD Field (total 1 byte)**(%%):0x40 258 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" %)4bit261 -|(% style="width:75px" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:1 37px" %)GPS_Settings|(% style="width:142px" %)BLE_Settings258 +(% border="1.5" style="background-color:#ffffcc; color:green; width:270px" %) 259 +|=(% scope="row" style="width: 60px;" %)**Size(bit)**|(% style="width:50px" %)2bits|(% style="width:80px" %)2bit|(% style="width:80px" %)4bit 260 +|=(% style="width: 75px;" %)**Value**|(% style="width:64px" %)SMOD|(% style="width:104px" %)GPS_Settings|(% style="width:103px" %)BLE_Settings 262 262 263 263 (% style="color:blue" %)** SMOD:** 264 264 ... ... @@ -280,13 +280,14 @@ 280 280 281 281 (% style="color:red" %)** 1: ** (%%) BLE Positioning with Strongest iBeacon 282 282 282 +(% style="color:red" %)** 2:** (%%)WiFi Positioning with Strongest WiFi SSID(% style="color:blue" %)(V1.4.1 Version support this function later)(%%) 283 283 284 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: 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 Bit289 -|(% 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"]] 287 +(% border="1.5" style="background-color:#ffffcc; color:green; width:260px" %) 288 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:50px" %)5 Bits|(% style="width:60px" %)1 Bit|(% style="width:20px" %)1 Bit|(% style="width:80px" %)1 Bit 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 290 291 291 === 2.4.2 Uplink FPORT~=2, Realtime GNSS Positioning + Temperature & Humidity === 292 292 ... ... @@ -294,12 +294,12 @@ 294 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 295 296 296 297 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width: 480px" %)298 -|=(% scope="row" style="width: 50px;" %)(((297 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:320px" %) 298 +|=(% scope="row" style="width: 60px;" %)((( 299 299 **Size(bytes)** 300 -)))|(% style="width: 60px" %)4|(% style="width:70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1|(% style="width:40px" %)(((300 +)))|(% style="width:50px" %)4|(% style="width:50px" %)4|(% style="width:70px" %)2|(% style="width:30px" %)1|(% style="width:30px" %)((( 301 301 2 302 -)))|(% style="width: 87px" %)(((302 +)))|(% style="width:30px" %)((( 303 303 2 304 304 ))) 305 305 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( ... ... @@ -317,8 +317,8 @@ 317 317 318 318 ==== (% style="color:blue" %)**FLAG:**(%%) ==== 319 319 320 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:2 50px" %)321 -|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width: 50px" %)2bits|(% style="width:50px" %)1bit320 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:120px" %) 321 +|=(% scope="row" style="width: 50px;" %)**Size(bit)**|(% style="width:30px" %)2bits|(% style="width:30px" %)1bit 322 322 |=(% style="width: 79px;" %)**Value**|(% style="width:55px" %)[[MOD>>||anchor="H3.2.7SetPositioningMode"]]|(% style="width:47px" %)[[LON>>||anchor="HLON:"]] 323 323 324 324 **Example:** Payload: 0x02863D68 FAC29BAF 4B45 60 0202 011A ... ... @@ -394,7 +394,6 @@ 394 394 ))) 395 395 396 396 397 - 398 398 ==== (% style="color:blue" %)**Hum:**(%%) ==== 399 399 400 400 0202 = //if (0x0202 & 0x8000 = 0 ): value =// 0x0202 / 100 = +514 ⇒ 51.4 degree ... ... @@ -412,10 +412,10 @@ 412 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 414 414 415 -(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width: 480px" %)416 -|=(% scope="row" style="width: 50px;" %)(((414 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:300px" %) 415 +|=(% scope="row" style="width: 60px;" %)((( 417 417 **Size(bytes)** 418 -)))|(% style="width:60px" %)4|(% style="width: 70px" %)4|(% style="width:80px" %)2|(% style="width:73px" %)1417 +)))|(% style="width:60px" %)4|(% style="width:60px" %)4|(% style="width:60px" %)2|(% style="width:50px" %)1 419 419 |=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)[[Latitude>>||anchor="HLocationinfo:"]]|(% style="width:87px" %)[[Longitude>>||anchor="HLocationinfo:"]]|(% style="width:76px" %)((( 420 420 [[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 421 421 )))|(% style="width:73px" %)[[FLAG>>||anchor="HFLAG:"]] ... ... @@ -434,12 +434,12 @@ 434 434 (% style="color:red" %)**Note for this mode:** 435 435 436 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.436 +* b) TrackerD will send data in CONFIRMED Mode when PNACKMD=1 and CFM=1, but TrackerD won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink, if TrackerD gets an ACK, TrackerD will consider there is a network connection and resend all NONE-ACK Messages. 438 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 439 440 440 The payload is 15 bytes, as below. 441 441 442 -(% border="1.5" style="background-color:#ffffcc; color:green; width:5 20px" %)441 +(% border="1.5" style="background-color:#ffffcc; color:green; width:500px" %) 443 443 |=(% scope="row" %)((( 444 444 **Size(bytes)** 445 445 )))|4|4|2|1|1|1|1|1 ... ... @@ -451,6 +451,7 @@ 451 451 452 452 === 2.4.5 Uplink FPORT~=6, BLE Positioning with Strongest iBeacon === 453 453 453 + 454 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 455 456 456 User can set **[[BLEMASK>>||anchor="H3.2.11A0SetBLEMASKtofilterBLEiBeacon"]]** so TrackerD will only search the iBeacons which have UUID that match the BLEMASK settings. ... ... @@ -483,12 +483,33 @@ 483 483 * (% style="color:#037691" %)**Measured Power: ** (%%) The Measured Power from the strongest iBeacon. 484 484 * (% style="color:#037691" %)**RSSI: ** (%%) The RSSI from the strongest iBeacon. 485 485 486 +=== 2.4.6 Uplink FPORT~=8, WiFi Positioning with Strongest WiFi SSID(Since firmware 1.4.1) === 486 486 487 -=== 2.4.6 Add Payload format in TTN V3 === 488 488 489 +TrackerD supports WiFi scans for indoor positioning. User can set [[**SMOD**>>||anchor="H3.2.7SetPositioningMode"]] to **BLE pure** or **GPS/BLE hybrid** so TrackerD will scan WiFi and find the strongest WiFi info and uplink. 489 489 490 -In TTN V3, use can add a custom payload so it shows friendly. 491 491 492 +(% border="1.2" cellspacing="3" style="background-color:#ffffcc; color:green; width:371.222px" %) 493 +|=(% scope="row" style="width: 60px;" %)((( 494 +**Size(bytes)** 495 +)))|(% style="width:60px" %)6|(% style="width:60px" %)4|(% style="width:79px" %)2|(% style="width:66px" %)1 496 +|=(% style="width: 69px;" %)**Value**|(% style="width:76px" %)SSID|(% style="width:87px" %)RSSI|(% style="width:79px" %)((( 497 +[[Alarm & BAT>>||anchor="HAlarm26BAT:"]] 498 +)))|(% style="width:66px" %)[[FLAG>>||anchor="HFLAG:"]] 499 + 500 +(% class="wikigeneratedid" %) 501 +[[image:1667288597595-714.png||height="212" width="1151"]] 502 + 503 + 504 +* (% style="color:#037691" %)**BAT: ** (%%) Ex1:0x4B45 & 0x3FFF ⇒ 3901 (mV). 505 +* (% style="color:#037691" %)**SSID: **(%%)WiFi name. 506 +* (% style="color:#037691" %)**RSSI: **(%%)The RSSI from the strongest WiFi. 507 + 508 +=== 2.4.7 Add Payload format in TTN V3 === 509 + 510 + 511 +In TTN V3, user can add a custom payload so it shows friendly. 512 + 492 492 In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder** 493 493 494 494 ... ... @@ -507,6 +507,7 @@ 507 507 508 508 == 2.5 Integrate with Datacake == 509 509 531 + 510 510 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. 511 511 512 512 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]] ... ... @@ -518,7 +518,6 @@ 518 518 == 2.6 Integrate with Tago == 519 519 520 520 521 - 522 522 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. 523 523 524 524 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]] ... ... @@ -610,8 +610,8 @@ 610 610 [[image:1664502854406-763.png]] 611 611 612 612 613 -(% border="1 .5" style="background-color:#ffffcc; color:green; width:520px" %)614 -|=(% style="width: 100px;" %)**Function**|=(% style="width: 2 10px;" %)**Action**|=(% style="width: 210px;" %)**Description**634 +(% border="1" style="background-color:#ffffcc; color:green; width:510px" %) 635 +|=(% style="width: 100px;" %)**Function**|=(% style="width: 205px;" %)**Action**|=(% style="width: 205px;" %)**Description** 615 615 |(% 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"]] 616 616 |(% 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 617 617 |(% 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. ... ... @@ -754,7 +754,7 @@ 754 754 755 755 (% style="color:#037691" %)**AT+INTWK=xx. (Disable (0), Enable (1), default:0)** 756 756 757 -Example: AT+ 778 +Example: AT+INTWK =1 **~-~-> ** Enable Transport Mode. 758 758 759 759 760 760 * (% style="color:blue" %)**Downlink Payload (prefix 0xAF):** ... ... @@ -775,9 +775,9 @@ 775 775 776 776 (% style="color:#037691" %)** aa:** 777 777 778 -* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%) only get and uplink GPS location info.779 -* (% style="color:red" %)**2: BLE ONLY: **(%%)Only obtain iBeacon info via BLE and uplink. Design for Indoor tracking. 780 -* (% style="color:red" %)**3: GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 799 +* (% style="color:red" %)**1: GPS ONLY(Factory Settings): **(%%)Only get and uplink GPS location info. 800 +* (% style="color:red" %)**2: BLE or WiFi ONLY: **(%%)Only obtain iBeacon info via BLE and uplink or obtain WiFi ssid info via WiFi and uplink. Design for Indoor tracking. 801 +* (% style="color:red" %)**3: GPS/BLE Hybrid: **(%%)Combination for Indoor and Outdoor tracking.Devices will try to search BLE iBeacon first. If device can't find the iBeacon, it will use GPS for positioning. 781 781 782 782 (% style="color:#037691" %)**bb:** 783 783 ... ... @@ -787,12 +787,14 @@ 787 787 (% style="color:#037691" %)**cc: ** 788 788 789 789 * (% style="color:red" %)**1 : **(%%) (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 811 +* (% style="color:red" %)**2 : **(%%) (WiFi)SSID+Rssi+BAT+State ((% style="color:#037691" %)V1.4.1 Version support this function later(%%)) 790 790 791 791 (% style="color:blue" %)**Example:** 792 792 793 - AT+ SMOD =1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 794 - AT+ SMOD =1,1,0 ~-~-> GPS +BAT State 795 - AT+ SMOD =2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 815 + AT+SMOD =1,0,0 ~-~-> GPS+ BAT+ State+Tem&Hum 816 + AT+SMOD =1,1,0 ~-~-> GPS +BAT State 817 + AT+SMOD =2,0,1 ~-~-> (iBeacon)UUID+ Major + Minor+Power+Rssi+BAT+State 818 + AT+SMOD =2,0,2 ~-~-> (WiFi)SSID+Rssi+BAT+State 796 796 797 797 798 798 * (% style="color:blue" %)**Downlink Payload (prefix 0xA5):** ... ... @@ -856,14 +856,14 @@ 856 856 857 857 **~ Example:** 858 858 859 - AT+ 882 + AT+CFM=0 **~-~-> ** Disable confirmation 860 860 861 - AT+ 884 + AT+CFM=1 **~-~-> ** Enable confirmation 862 862 863 863 864 864 * (% style="color:blue" %)**Downlink Payload (prefix 0x05):** 865 865 866 -(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+ SMOD=1889 +(% style="color:#037691" %)**0x05 01 **(%%) ~/~/ Same as AT+CFM =1 867 867 868 868 869 869 ... ... @@ -888,23 +888,71 @@ 888 888 Example: 0x3401 ~/~/ Same as AT+PNACKMD=1 889 889 890 890 914 + 891 891 === 3.2.11 Set BLEMASK to filter BLE iBeacon === 892 892 893 -BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. LBT1 will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID. 894 894 895 - Note:BLEMASK range is6~~10bytes.IfAT+BLEMASK<6bytes,BLEMASKwillbedisabled.918 +BLEMASK is to filter the unwanted BLE iBeacons during scan. For example, if BLEMASK is 123456. TrackerD will only uplink UUID info which includes 123456. It will ignore all other iBeacons which doesn’t contact 123456 in the UUID. 896 896 897 -(% style="color:blue" %)**AT Command:**(%%) 898 - AT+BLEMASK=123456 ~/~/ Set BLEMASK = 123456 899 - AT+BLEMASK=0 ~/~/ disable BLEMASK 920 +(% style="color:red" %)**Note: BLEMASK range is 6 ~~ 10 bytes. If AT+BLEMASK < 6 bytes, BLEMASK will be disabled.** 900 900 922 +(% style="color:blue" %)**AT Command:** 901 901 902 -(% style="color:blue" %)**Downlink Payload: (Prefix : 0xA5)**(%%) 903 -Example: 904 -0xA5010203040506 ~/~/ Set BLEMASK to 123456 924 + (% style="color:#037691" %)**AT+BLEMASK=123456** (%%) ~/~/ Set BLEMASK = 123456 905 905 926 + (% style="color:#037691" %)**AT+BLEMASK=0** (%%) ~/~/ disable BLEMASK 906 906 928 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB2)(Since firmware 1.4.1)** 907 907 930 +Example: 0xB2010203040506 ~/~/ Set BLEMASK to 123456 931 + 932 + 933 + 934 +=== 3.2.12 Set WiFIMASK to filter WiFi SSID(Since firmware 1.4.1) === 935 + 936 + 937 +WiFiMASK is to filter the unwanted WiFi SSID during scan. For example, if WiFiMASK is 123456. TrackerD will only uplink SSID info which includes 123456. It will ignore all other WiFi which doesn’t contact 123456 in the SSID. 938 + 939 +(% style="color:red" %)**Note: WiFiMASK range is 6 ~~ 10 bytes. If AT+ WiFiMASK < 6 bytes, WiFiMASK will be disabled.** 940 + 941 +(% style="color:blue" %)**AT Command:** 942 + 943 + (% style="color:#037691" %)**AT+WiFiMASK =123456** (%%) ~/~/ Set WiFiMASK = 123456 944 + 945 + (% style="color:#037691" %)**AT+WiFiMASK =0** (%%) ~/~/ disable WiFiMASK 946 + 947 +(% style="color:blue" %)**Downlink Payload: (Prefix : 0xB3)(Since firmware 1.4.1)** 948 + 949 +Example: 0xB3010203040506 ~/~/ Set WiFiMASK to 123456 950 + 951 + 952 + 953 +=== 3.2.13 Disable/Enable Information printing(Since firmware 1.4.1) === 954 + 955 + 956 +Users can use this feature to enable/disable Information printing. 957 + 958 +(% style="color:blue" %)**AT Command:** 959 + 960 +(% style="color:#037691" %)**AT+SHOWID=XX **(%%) ~/~/(Disable (0), Enable (1), default:0) 961 +\\Example: AT+SHOWID =1 ~-~-> Enable Information printing. 962 + 963 + 964 + 965 +=== 3.2.14 Get or Set Eight Channels Mode, only for us915, AU915(Since firmware 1.4.1) === 966 + 967 + 968 +The Channels Mode in the LORAWAN LMIC library is from 0 ~~ 7. When CHE = 8, 72 channels will be accessible to the network. 969 + 970 +(% style="color:blue" %)**AT Command:** 971 + 972 +(% style="color:#037691" %)**AT+CHE=1**(%%) ~/~/ set one channels mode, 973 + 974 +(% style="color:blue" %)**Downlink Payload:0X24**(%%) 975 +Example: 0x24 01 ~/~/ Same as AT+CHE= = 1 976 + 977 + 978 + 908 908 = 4. Setting for Different Scenarios = 909 909 910 910 ... ... @@ -945,6 +945,7 @@ 945 945 [[image:1664503574618-659.png]] 946 946 947 947 1019 + 948 948 (% style="color:blue" %)**Step5:** (%%) Select the firmware file (.bin format), com port and proper SPI configure. Clink Start. Bin file location: 949 949 950 950 [[https:~~/~~/github.com/dragino/TrackerD/releases>>https://github.com/dragino/TrackerD/releases]] ... ... @@ -990,7 +990,18 @@ 990 990 [[image:1664503715811-892.png]] 991 991 992 992 1065 +(% id="cke_bm_4554S" style="display:none" %) (%%)Find the path of SP32 installation, find the file as shown in Figure 1, and change the SPI pin to the shown in Figure 2. 993 993 1067 +[[image:image-20221024105643-1.png]] 1068 + 1069 +**~ Figure1** 1070 + 1071 + 1072 +[[image:image-20221024105643-2.png]] 1073 + 1074 + **Figure2** 1075 + 1076 + 994 994 * **Download the latest TrackerD from the dragino github: [[https:~~/~~/github.com/dragino/TrackerD>>url:https://github.com/dragino/TrackerD]]** 995 995 996 996 Put the Library in the TrackerD directory into the libraries file in the Arduino directory: ... ... @@ -1049,6 +1049,60 @@ 1049 1049 |(% style="width:118px" %)A8|(% style="width:67px" %)Yellow|(% style="width:123px" %)MTMS/GPIO14 1050 1050 |(% style="width:118px" %)B8|(% style="width:67px" %)Grey|(% style="width:123px" %)MTDO/GPIO15 1051 1051 1135 +== 7.3 Notes on using different serial port tools for TrackerD == 1136 + 1137 + 1138 +=== **Serial port utility** === 1139 + 1140 + 1141 +Serial port utility requires you to automatically add data streams. 1142 + 1143 +Need to adjust the data stream to RTS/CTS on physical restart. 1144 + 1145 + 1146 +(% class="wikigeneratedid" %) 1147 +[[image:image-20221102140621-1.png]] 1148 + 1149 + 1150 +When using AT commands, the data flow needs to be adjusted to XON/XOFF 1151 + 1152 + 1153 +[[image:image-20221102140638-2.png]] 1154 + 1155 + 1156 + 1157 +=== **SecureCRT** === 1158 + 1159 + 1160 +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. 1161 + 1162 + 1163 +[[image:image-20221102140704-3.png]] 1164 + 1165 + 1166 +[[image:image-20221102140712-4.png]] 1167 + 1168 + 1169 + 1170 +=== **PUTTY** === 1171 + 1172 + 1173 +[[image:image-20221102140748-5.png]] 1174 + 1175 + 1176 +Since putty does not have a command window, you need to fill in the complete command externally, and then copy it to putty.The information copied outside can be pasted by right-clicking the mouse in putty. 1177 + 1178 + 1179 +[[image:image-20221102140801-6.png]] 1180 + 1181 + 1182 +== 7.4 TrackerD trouble shooting == 1183 + 1184 + 1185 +V1.4.0: When the motion mode is turned on, the TDC needs to be greater than MTDC, otherwise TDC time will be confused 1186 + 1187 + 1188 + 1052 1052 = 8. Order Info = 1053 1053 1054 1054 ... ... @@ -1074,7 +1074,7 @@ 1074 1074 1075 1075 (% style="color:#037691" %)**Dimensions and Weight**: 1076 1076 1077 -* Device Size: 85 x 48 x 15 cm1214 +* Device Size: 85 x 48 x 15 mm 1078 1078 * Weight: 50g 1079 1079 1080 1080 = 10. Support =
- 1667288597595-714.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +27.9 KB - Content
- image-20221024105643-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +11.3 KB - Content
- image-20221024105643-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +64.5 KB - Content
- image-20221102140621-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +46.1 KB - Content
- image-20221102140638-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +40.8 KB - Content
- image-20221102140704-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +15.5 KB - Content
- image-20221102140712-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +73.2 KB - Content
- image-20221102140748-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +56.0 KB - Content
- image-20221102140801-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +21.0 KB - Content