Calibos
-
Posts
14 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Calibos
-
-
On 10/25/2021 at 1:41 PM, Fiery said:
As far as I can understand, that display connects to the PC as a regular monitor. In which case you can use the SensorPanel facility of AIDA64 and no special support or change necessary to be applied to AIDA64.
I've tried finding an alternative screen for my front of media server case mounted sensor panel but none of the BeadaPanels are actually suitable (I will actually be buying one of the new 6.8" Long thin Beada Panels for a different PC build though)
I keep falling back on the Eviciv 7" IPS panel....which is HDMI. I have contacted Ecivic because the documentation does mention Video over Type C but that might just be HDMII or Displayport over Type C rather than the True USB video I need to be able to run a second Sensor panel from 1 instance of Aida64 on the media server using Aida64's 'LCD' functionality.
So I ask again, would it be possible to add support for the other USB Monitor in true USB mode as opposed to Display-Link mode so that I can use it with Aida64's LCD function mode rather than its multi-monitor Sensor panel mode?
-
Just wondering if there is any advantage or indeed caveats to connecting a 7" HDMI Sensor Panel to my Motherboards HDMI output and running it off the CPU's iGPU.
Potentially moving from an AMD CPU without iGPU back to an Alderlake Intel with an iGPU and have an RTX3090 Discrete GPU, so its not like I am lacking outputs on my dGPU. However I do a lot of High Res/High refresh rate VR gaming and Simming and just bought MSFS2020 and will be flying in VR. Every extra frame and the frame timing etc is very important for a smooth experience with MSFS2020 in VR.
Thus I am wondering that given this use-case and even with the mighty RTX3090 it might be advantageous not to distract it so to speak with it having to run a Sensor Panel as well as the 3440x1440 @ 60hz Ultrawide Monitor and a 90hz VR Headset.
So my question is if its even possible to run a HDMI Sensor panel off of the iGPU or if there are any downsides in doing so?
-
A question for the Beada fans here.
I am buying this particular Beada 6.8" Screen for the front of my Media Server case but will also be buying the Phone screen sized 5" model for a HTPC Formfactor PC build for my brother. This 6.8" inch one is an IPS Panel whereas the 5" one comes in both IPS and TFT screen types. Is it worth paying the extra $20 for the IPS version for a screen this size used as a Sensor panel or should I save that $20 which effectively pays for most of the shipping cost. (I know I can't buy a TFT version of the 6.8" screen as it only comes in an IPS version)
-
17 hours ago, criskoe said:
My Logitech G19 was starting to finally die so I needed a simple Aida lcd screen solution for my desk that looked good. I really wanted something clean looking with a simple usb connection. No hdmi second screen tweaking. After searching, there doesn't seem to be a completely finished option available at all surprisingly. Just janky 3d printed stuff. Shame really.
Anyways, I ended up going with the 7 inch Beada panel cause it comes with a front bezel at least and figured I could make it work some how. After lots of brainstorming on what would be the easiest way that would look good. I came up with this. I Used a 1/6 thin sheet of ABS plastic that I cut and bent to wrap around the sides of the screen and sandwich between the bezel lip and back acrylic plate that comes with the screen. I also attached a cheap iPad stand to the back acrylic plate with some small nuts and bolts so the screen can tilt at multiple angles and stand up solid and sturdy. Lots of adjustment with Zero wobble. And lastly gave all the parts a nice thin coat of flat enamel spray paint. I think It turned out pretty nice. I mean its not perfect but I'm very please with it. Could actually almost pass as a finished product. Over all it wasn't too hard to make. The side cover part was a bit of a pain to get the bends perfect so they were flush with the bezel and back plate. Took me 3 or 4 try's to get the piece perfect. The rest was super simple stuff. It would be nice if Beada could included a simple Side trim ring like I made for their screens. Really cleans it up.
Im also so happy I went with a display that only needs a USB cable for both power and display. I hated the idea of using HDMI and second screen issues and weirdness. USB only is the only way to go IMO...
Now I'm just trying to figure out why Aida64 has missing and incorrect values for some of my sensors. I have the most recent version and I cant seem to get it right.
I'm sorry that this place is as quiet as a graveyard most of the time. You'd think with Sensor panels getting so popular these days that this place would be a hive of activity but unfortunately its not...but I'm here tonight....and I am taking the time to tell you that that is an epic mod you should be proud of and you would never know it was DIY. Amazing work!!
-
On 10/25/2021 at 1:41 PM, Fiery said:
As far as I can understand, that display connects to the PC as a regular monitor. In which case you can use the SensorPanel facility of AIDA64 and no special support or change necessary to be applied to AIDA64.
I'm the guy that PM'd you the other day. I want to use a 7" rPi HDMI Display as a conventional Sensor panel mounted to the front of my case Displaying everything except my HDD info and harvest the LCD layer of the AOC USB 3.0 Donor Monitor for a 'Snowblind Mod' (Transparent Screen on the case side window) that Displays HDD Data Widgets in front of each physical HDD Hotswap Bay. Imagine a Live Virtual Label for Each Bay.
You told me in that thread that in order to run two Sensor Panels in the same PC with different layouts on each screen, that I would need to use a USB Monitor and use Aida64's LCD screen functionality.
[EDIT 1] If it is not actually possible to add support for this AOC USB monitor rather than you simply not seeing the need because you didn't remember my particular use-case from the other day, can you comment on the following idea then.
I decide to put the 7" rPi HDMI screen in my Main Gaming rig that I original bought it for before changing my mind and wanting to use it in the Media Server. In that rig its back to being a conventional Sensor Panel secondary Monitor.
For the Media Server with the AOC USB Monitor used for the 'SnowBlind Mod', I do as you say and use this AOC USB 'Snowblind' Monitor as a conventional Sensor Panel secondary monitor but remember, I do still want a front of case mounted 6-7" Sensor panel displaying a different layout and information. As you told me in the other thread I need to use a USB Display and the LCD functionality of Aida64 to be able to have two sensor panels in the same PC running off the same instance of Aida64 displaying different layouts and info.
So can someone point me to a list of AIDA64 supported 6-7" USB Displays??
[EDIT 2] Its OK. Found the Beada Panels. Look Great!
-
Hi,
I'm wondering can support be added for the following Monitor to be used as a USB LCD Sensor panel:
AOC E1659Fwu USB 3.0 Monitor (15.6" 1366x768)
Quote------[ Versions ]------
Program Version : AIDA64 Extreme v6.50.5800
BenchDLL Version: 4.5.859.8-x64
Windows Version : Microsoft Windows 10 Home 10.0.19041.1288 (64-bit)
GetProductInfo : 0x00000065------[ Motherboard Info ]------
Motherboard ID : 63-0100-000001-00101111-051315-Chipset$0AAAA000_BIOS DATE: 11/29/16 20:32:52 VER: 05.0000C
Motherboard Model : Asus Z170-A
Motherboard Chipset : Intel Sunrise Point Z170, Intel Skylake-SDMI MB Manufacturer : ASUSTeK COMPUTER INC.
DMI MB Product : Z170-A
DMI MB Version : Rev 1.xx
DMI MB Serial : 160367247103191
DMI SYS Manufacturer: System manufacturer
DMI SYS Product : System Product Name
DMI SYS Version : System Version
DMI SYS Serial : System Serial Number
DMI BIOS Version : 3007------[ USB Devices ]------
Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
- [Port 1] < No Device Connected >
- [Port 2] < No Device Connected >
- [Port 3] < No Device Connected >
- [Port 4] < No Device Connected >
- [Port 5] Generic USB Hub (Gaming USB2.0 Smart Port)
- - [Port 1] USB Composite Device (Corsair Gaming MM800 RGB POLARIS)
- - - USB Input Device
- - - - HID-compliant vendor-defined device
- - - USB Input Device
- - - - HID Keyboard Device
- - [Port 2] USB Composite Device (Corsair Gaming M65 Pro RGB Mouse)
- - - USB Input Device
- - - - HID-compliant vendor-defined device
- - - - HID-compliant vendor-defined device
- - - - HID-compliant mouse
- - - USB Input Device
- - - - HID-compliant vendor-defined device
- [Port 6] USB Composite Device (Corsair STRAFE RGB Gaming Keyboard)
- - USB Input Device
- - - HID-compliant consumer control device
- - - HID-compliant vendor-defined device
- - - HID-compliant vendor-defined device
- - - HID Keyboard Device
- - USB Input Device
- - - HID-compliant vendor-defined device
- [Port 7] < No Device Connected >
- [Port 8] < No Device Connected >
- [Port 9] < No Device Connected >
- [Port 10] USB Input Device (CORSAIR iCUE LS100 Smart Lighting Strip Starter Kit)
- - HID-compliant vendor-defined device
- [Port 11] USB Input Device (Integrated USB Bridge)
- - HID-compliant vendor-defined device
- [Port 12] < No Device Connected >
- [Port 13] USB Composite Device (flirc)
- - USB Input Device
- - - HID-compliant vendor-defined device
- - USB Input Device
- - - HID-compliant consumer control device
- - - HID-compliant consumer control device
- - - HID-compliant system controller
- - - HID Keyboard Device
- - USB Input Device
- - - HID-compliant vendor-defined device
- [Port 14] < No Device Connected >
- [Port 15] < No Device Connected >
- [Port 16] < No Device Connected >
- [Port 17] < No Device Connected >
- [Port 18] USB Mass Storage Device (USB Reader)
- - Generic STORAGE DEVICE USB Device
- - Generic STORAGE DEVICE USB Device
- - Generic STORAGE DEVICE USB Device
- - Generic STORAGE DEVICE USB Device
- [Port 19] < No Device Connected >
- [Port 20] < No Device Connected >
- [Port 21] < No Device Connected >
- [Port 22] < No Device Connected >
- [Port 23] < No Device Connected >
- [Port 24] < No Device Connected >
- [Port 25] < No Device Connected >
- [Port 26] < No Device Connected >
NVIDIA USB 3.10 eXtensible Host Controller - 1.10 (Microsoft)
- [Port 1] < No Device Connected >
- [Port 2] < No Device Connected >
- [Port 3] < No Device Connected >
- [Port 4] < No Device Connected >
- [Port 5] < No Device Connected >
- [Port 6] < No Device Connected >
ASMedia USB3.1 eXtensible Host Controller
- [Port 1] Generic SuperSpeed USB Hub (USB3.0 Hub)
- - [Port 1] USB Composite Device (E1659Fwu)
- - - E1659Fwu
- - - E1659Fwu
- - - - Generic PnP Monitor
- - [Port 2] < No Device Connected >
- - [Port 3] < No Device Connected >
- - [Port 4] < No Device Connected >
- [Port 2] Generic SuperSpeed USB Hub (Corsair ST100 USB 3.1 Hub)
- - [Port 1] < No Device Connected >
- - [Port 2] < No Device Connected >
- - [Port 3] < No Device Connected >
- - [Port 4] < No Device Connected >
- [Port 3] Generic USB Hub (USB2.0 Hub)
- - [Port 1] < No Device Connected >
- - [Port 2] < No Device Connected >
- - [Port 3] < No Device Connected >
- - [Port 4] < No Device Connected >
- [Port 4] Generic USB Hub (Corsair ST100 USB 2.0 Hub)
- - [Port 1] USB Composite Device (Corsair ST100 Headset Output)
- - - USB Input Device
- - - - HID-compliant consumer control device
- - - CORSAIR ST100 Headset Output
- - - - Headphones (CORSAIR ST100 Headset Output)
- - - - Microphone (CORSAIR ST100 Headset Output)
- - [Port 2] USB Input Device (Corsair ST100 LED Driver)
- - - HID-compliant vendor-defined device
- - [Port 3] USB Input Device (Corsair VOID RGB Wireless Gaming Headset)
- - - HID-compliant vendor-defined device
- - - HID-compliant vendor-defined device
- - [Port 4] USB Composite Device (Corsair VOID Wireless Gaming Dongle)
- - - USB Input Device
- - - - HID-compliant consumer control device
- - - - HID-compliant vendor-defined device
- - - - HID-compliant vendor-defined device
- - - CORSAIR VOID RGB Wireless Gaming Headset
- - - - Headset Earphone (2- CORSAIR VOID RGB Wireless Gaming Headset)
- - - - Headset Microphone (2- CORSAIR VOID RGB Wireless Gaming Headset)
Standard OpenHCD USB Host Controller
- [Port 1] < No Device Connected >
Standard Enhanced PCI to USB Host Controller
- [Port 1] < No Device Connected >
Standard OpenHCD USB Host Controller
- [Port 1] < No Device Connected >
Standard Enhanced PCI to USB Host Controller
- [Port 1] < No Device Connected >
Standard OpenHCD USB Host Controller
- [Port 1] < No Device Connected >
Standard Enhanced PCI to USB Host Controller
- [Port 1] < No Device Connected >
Standard OpenHCD USB Host Controller
- [Port 1] < No Device Connected >
Standard Enhanced PCI to USB Host Controller
- [Port 1] < No Device Connected >
Renesas USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
- [Port 1] < No Device Connected >
- [Port 2] Unknown Device
- [Port 3] < No Device Connected >
Renesas USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
- [Port 1] < No Device Connected >
- [Port 2] Unknown Device
- [Port 3] < No Device Connected >
Renesas USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
- [Port 1] < No Device Connected >
- [Port 2] Unknown Device
- [Port 3] < No Device Connected >
Renesas USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
- [Port 1] < No Device Connected >
- [Port 2] Unknown Device
- [Port 3] < No Device Connected >------[ Generic USB Hub]------
Device Description : Generic USB Hub
Device ID : 1B1C-1B2C
Device Class : 09 / 00 (Hi-Speed Hub with multiple TTs)
Device Protocol : 02
Revision : 3298h
Manufacturer : Corsair Components, Inc.
Product : Gaming USB2.0 Smart Port
Supported USB Version: 2.00
Current Speed : High (USB 2.0)------[ USB Composite Device]------
Device Description : USB Composite Device
Device ID : 1B1C-1B3B
Device Class : 03 / 00 (Human Interface Device)
Device Protocol : 00
Revision : 0102h
Manufacturer : Corsair Components, Inc.
Product : Corsair Gaming MM800 RGB POLARIS
Serial Number : 43B0020C621C75AFDC45D25E071C00F5
Supported USB Version: 2.00
Current Speed : Full (USB 1.1)------[ USB Composite Device]------
Device Description : USB Composite Device
Device ID : 1B1C-1B2E
Device Class : 03 / 01 (Human Interface Device)
Device Protocol : 02
Revision : 0306h
Manufacturer : Corsair
Product : Corsair Gaming M65 Pro RGB Mouse
Serial Number : 17019008AEB890E555ACE715F5001944
Supported USB Version: 2.00
Current Speed : Full (USB 1.1)------[ USB Composite Device]------
Device Description : USB Composite Device
Device ID : 1B1C-1B20
Device Class : 03 / 01 (Human Interface Device)
Device Protocol : 01
Revision : 0308h
Manufacturer : Corsair
Product : Corsair STRAFE RGB Gaming Keyboard
Serial Number : 1203401BAEB8180655A5C965F5001947
Supported USB Version: 2.00
Current Speed : Full (USB 1.1)------[ USB Input Device]------
Device Description : USB Input Device
Device ID : 1B1C-0C1E
Device Class : 03 / 00 (Human Interface Device)
Device Protocol : 00
Revision : 0009h
Manufacturer : Corsair
Product : CORSAIR iCUE LS100 Smart Lighting Strip Starter Kit
Serial Number : 2400030AC8207AAF0226475F011C00F5
Supported USB Version: 2.00
Current Speed : Full (USB 1.1)------[ USB Input Device]------
Device Description : USB Input Device
Device ID : 1B1C-0C04
Device Class : 03 / 00 (Human Interface Device)
Device Protocol : 00
Revision : 0200h
Manufacturer : Corsair Memory, Inc.
Product : Integrated USB Bridge
Supported USB Version: 2.00
Current Speed : Full (USB 1.1)------[ USB Composite Device]------
Device Description : USB Composite Device
Device ID : 20A0-0006
Device Class : 03 / 00 (Human Interface Device)
Device Protocol : 01
Revision : 0200h
Manufacturer : flirc.tv
Product : flirc
Supported USB Version: 2.00
Current Speed : Full (USB 1.1)------[ USB Mass Storage Device]------
Device Description : USB Mass Storage Device
Device ID : 05E3-0732
Device Class : 08 / 06 (Mass Storage)
Device Protocol : 50
Revision : 0551h
Manufacturer : Genesys
Product : USB Reader
Serial Number : 000000000654
Supported USB Version: 3.00
Current Speed : Super (USB 3.0)------[ Generic SuperSpeed USB Hub]------
Device Description : Generic SuperSpeed USB Hub
Device ID : 2109-0813
Device Class : 09 / 00 (Hub)
Device Protocol : 03
Revision : 9011h
Manufacturer : VIA Labs, Inc.
Product : USB3.0 Hub
Supported USB Version: 3.00
Current Speed : Super (USB 3.0)------[ USB Composite Device]------
Device Description : USB Composite Device
Device ID : 17E9-FF0C
Device Class : EF / 02 (Interface Association Descriptor)
Device Protocol : 01
Revision : 3114h
Manufacturer : DisplayLink
Product : E1659Fwu
Serial Number : LMYM1HA000328
Supported USB Version: 3.20
Current Speed : Super (USB 3.0)------[ Generic SuperSpeed USB Hub]------
Device Description : Generic SuperSpeed USB Hub
Device ID : 1B1C-0A33
Device Class : 09 / 00 (Hub)
Device Protocol : 03
Revision : 9302h
Manufacturer : Corsair Components
Product : Corsair ST100 USB 3.1 Hub
Serial Number : v5.0
Supported USB Version: 3.10
Current Speed : Super (USB 3.0)------[ Generic USB Hub]------
Device Description : Generic USB Hub
Device ID : 2109-2813
Device Class : 09 / 00 (Hi-Speed Hub with single TT)
Device Protocol : 01
Revision : 9011h
Manufacturer : VIA Labs, Inc.
Product : USB2.0 Hub
Supported USB Version: 2.10
Current Speed : High (USB 2.0)------[ Generic USB Hub]------
Device Description : Generic USB Hub
Device ID : 1B1C-0A36
Device Class : 09 / 00 (Hi-Speed Hub with multiple TTs)
Device Protocol : 02
Revision : 9302h
Manufacturer : Corsair Components
Product : Corsair ST100 USB 2.0 Hub
Serial Number : v5.0
Supported USB Version: 2.10
Current Speed : High (USB 2.0)------[ USB Composite Device]------
Device Description : USB Composite Device
Device ID : 1B1C-0A32
Device Class : 01 / 01 (Audio Control)
Device Protocol : 00
Revision : 0100h
Manufacturer : Corsair Components Inc.
Product : Corsair ST100 Headset Output
Serial Number : v0.6
Supported USB Version: 1.10
Current Speed : Full (USB 1.1)------[ USB Input Device]------
Device Description : USB Input Device
Device ID : 1B1C-0A34
Device Class : 03 / 00 (Human Interface Device)
Device Protocol : 00
Revision : 0004h
Manufacturer : Corsair
Product : Corsair ST100 LED Driver
Serial Number : 21200307A8047BAF86B5635F041C00F5
Supported USB Version: 2.01
Current Speed : Full (USB 1.1)------[ USB Input Device]------
Device Description : USB Input Device
Device ID : 1B1C-0A2C
Device Class : 03 / 00 (Human Interface Device)
Device Protocol : 00
Revision : 0000h
Manufacturer : Corsair
Product : Corsair VOID RGB Wireless Gaming Headset
Supported USB Version: 1.10
Current Speed : Full (USB 1.1)------[ USB Composite Device]------
Device Description : USB Composite Device
Device ID : 1B1C-0A2B
Device Class : 01 / 01 (Audio Control)
Device Protocol : 00
Revision : 0000h
Manufacturer : Corsair
Product : Corsair VOID Wireless Gaming Dongle
Supported USB Version: 1.10
Current Speed : Full (USB 1.1)------[ Unknown Device]------
Device Description : Unknown Device
Device ID : 0000-0000
Device Class : 00 / 00
Device Protocol : 00
Revision : 0000h
Supported USB Version: 0.00
Current Speed : Low (USB 1.1)------[ Unknown Device]------
Device Description : Unknown Device
Device ID : 0000-0000
Device Class : 00 / 00
Device Protocol : 00
Revision : 0000h
Supported USB Version: 0.00
Current Speed : Low (USB 1.1)------[ Unknown Device]------
Device Description : Unknown Device
Device ID : 0000-0000
Device Class : 00 / 00
Device Protocol : 00
Revision : 0000h
Supported USB Version: 0.00
Current Speed : Low (USB 1.1)------[ Unknown Device]------
Device Description : Unknown Device
Device ID : 0000-0000
Device Class : 00 / 00
Device Protocol : 00
Revision : 0000h
Supported USB Version: 0.00
Current Speed : Low (USB 1.1)------[ DevClass / USB Hubs ]------
<DESC>Generic USB Hub</DESC><DEVPATH>\\?\usb#vid_1b1c&pid_1b2c#5&521a615&0&5#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>16</DEVINST><INSTANCE>USB\VID_1B1C&PID_1B2C\5&521A615&0&5</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000005</ADDR><REV>3298</REV>
<DESC>Generic USB Hub</DESC><DEVPATH>\\?\usb#vid_1b1c&pid_0a36&asmediausbd_hub#6&21b51711&1&4#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>17</DEVINST><INSTANCE>USB\VID_1B1C&PID_0A36&ASMEDIAUSBD_HUB\6&21B51711&1&4</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000008</ADDR><REV>9302</REV>
<DESC>ASMedia USB Root Hub</DESC><DEVPATH>\\?\usb#asmediaroot_hub#5&1b46e37c&1&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>18</DEVINST><INSTANCE>USB\ASMEDIAROOT_HUB\5&1B46E37C&1&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>USB Root Hub (USB 3.0)</DESC><DEVPATH>\\?\usb#root_hub30#7&1cd2c02c&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>19</DEVINST><INSTANCE>USB\ROOT_HUB30\7&1CD2C02C&0&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>USB Root Hub</DESC><DEVPATH>\\?\usb#root_hub20#5&32332fe1&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>20</DEVINST><INSTANCE>USB\ROOT_HUB20\5&32332FE1&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>USB Root Hub (USB 3.0)</DESC><DEVPATH>\\?\usb#root_hub30#7&1fdd67c6&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>21</DEVINST><INSTANCE>USB\ROOT_HUB30\7&1FDD67C6&0&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>USB Root Hub (USB 3.0)</DESC><DEVPATH>\\?\usb#root_hub30#5&299832dd&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>22</DEVINST><INSTANCE>USB\ROOT_HUB30\5&299832DD&0&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>USB Root Hub</DESC><DEVPATH>\\?\usb#root_hub#5&339599b4&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>23</DEVINST><INSTANCE>USB\ROOT_HUB\5&339599B4&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>Generic SuperSpeed USB Hub</DESC><DEVPATH>\\?\usb#vid_1b1c&pid_0a33&asmediausbd_hubss#v5.0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>24</DEVINST><INSTANCE>USB\VID_1B1C&PID_0A33&ASMEDIAUSBD_HUBSS\V5.0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000007</ADDR><REV>9302</REV>
<DESC>USB Root Hub (USB 3.0)</DESC><DEVPATH>\\?\usb#root_hub30#7&308aeeb4&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>25</DEVINST><INSTANCE>USB\ROOT_HUB30\7&308AEEB4&0&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>USB Root Hub</DESC><DEVPATH>\\?\usb#root_hub#5&273ea06c&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>26</DEVINST><INSTANCE>USB\ROOT_HUB\5&273EA06C&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>USB Root Hub</DESC><DEVPATH>\\?\usb#root_hub#5&292d1f01&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>27</DEVINST><INSTANCE>USB\ROOT_HUB\5&292D1F01&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>USB Root Hub (USB 3.0)</DESC><DEVPATH>\\?\usb#root_hub30#4&1148bc98&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>28</DEVINST><INSTANCE>USB\ROOT_HUB30\4&1148BC98&0&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>USB Root Hub</DESC><DEVPATH>\\?\usb#root_hub20#5&62b7ca4&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>29</DEVINST><INSTANCE>USB\ROOT_HUB20\5&62B7CA4&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>USB Root Hub</DESC><DEVPATH>\\?\usb#root_hub#5&1cd625b9&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>30</DEVINST><INSTANCE>USB\ROOT_HUB\5&1CD625B9&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>USB Root Hub</DESC><DEVPATH>\\?\usb#root_hub20#5&43cfe0f&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>31</DEVINST><INSTANCE>USB\ROOT_HUB20\5&43CFE0F&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>USB Root Hub (USB 3.0)</DESC><DEVPATH>\\?\usb#root_hub30#7&8b996c7&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>32</DEVINST><INSTANCE>USB\ROOT_HUB30\7&8B996C7&0&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>USB Root Hub</DESC><DEVPATH>\\?\usb#root_hub20#5&1093f757&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>33</DEVINST><INSTANCE>USB\ROOT_HUB20\5&1093F757&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>Generic SuperSpeed USB Hub</DESC><DEVPATH>\\?\usb#vid_2109&pid_0813&asmediausbd_hubss#00000810#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>34</DEVINST><INSTANCE>USB\VID_2109&PID_0813&ASMEDIAUSBD_HUBSS\00000810</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000010</ADDR><REV>9011</REV>
<DESC>Generic USB Hub</DESC><DEVPATH>\\?\usb#vid_2109&pid_2813&asmediausbd_hub#00000830#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><DEVINST>35</DEVINST><INSTANCE>USB\VID_2109&PID_2813&ASMEDIAUSBD_HUB\00000830</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000011</ADDR><REV>9011</REV>------[ DevClass / USB Devices ]------
<DESC>Generic SuperSpeed USB Hub</DESC><DEVPATH>\\?\usb#vid_1b1c&pid_0a33&asmediausbd_hubss#v5.0#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><DEVINST>24</DEVINST><INSTANCE>USB\VID_1B1C&PID_0A33&ASMEDIAUSBD_HUBSS\V5.0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000007</ADDR><REV>9302</REV>
<DESC>USB Composite Device</DESC><DEVPATH>\\?\usb#vid_1b1c&pid_0a2b#40000040#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><DEVINST>36</DEVINST><INSTANCE>USB\VID_1B1C&PID_0A2B\40000040</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>0000000C</ADDR><REV>0000</REV>
<DESC>USB Composite Device</DESC><DEVPATH>\\?\usb#vid_1b1c&pid_1b3b#43b0020c621c75afdc45d25e071c00f5#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><DEVINST>37</DEVINST><INSTANCE>USB\VID_1B1C&PID_1B3B\43B0020C621C75AFDC45D25E071C00F5</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000001</ADDR><REV>0102</REV>
<DESC>USB Composite Device</DESC><DEVPATH>\\?\usb#vid_1b1c&pid_0a32#v0.6#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><DEVINST>38</DEVINST><INSTANCE>USB\VID_1B1C&PID_0A32\V0.6</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000009</ADDR><REV>0100</REV>
<DESC>USB Composite Device</DESC><DEVPATH>\\?\usb#vid_20a0&pid_0006#5&521a615&0&13#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><DEVINST>39</DEVINST><INSTANCE>USB\VID_20A0&PID_0006\5&521A615&0&13</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>0000000D</ADDR><REV>0200</REV>
<DESC>USB Mass Storage Device</DESC><DEVPATH>\\?\usb#vid_05e3&pid_0732#000000000654#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><DEVINST>40</DEVINST><INSTANCE>USB\VID_05E3&PID_0732\000000000654</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000012</ADDR><REV>0551</REV>
<DESC>USB Composite Device</DESC><DEVPATH>\\?\usb#vid_1b1c&pid_1b2e#17019008aeb890e555ace715f5001944#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><DEVINST>41</DEVINST><INSTANCE>USB\VID_1B1C&PID_1B2E\17019008AEB890E555ACE715F5001944</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000002</ADDR><REV>0306</REV>
<DESC>USB Input Device</DESC><DEVPATH>\\?\usb#vid_1b1c&pid_0a34#21200307a8047baf86b5635f041c00f5#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><DEVINST>42</DEVINST><INSTANCE>USB\VID_1B1C&PID_0A34\21200307A8047BAF86B5635F041C00F5</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>0000000A</ADDR><REV>0004</REV>
<DESC>USB Composite Device</DESC><DEVPATH>\\?\usb#vid_1b1c&pid_1b20#1203401baeb8180655a5c965f5001947#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><DEVINST>43</DEVINST><INSTANCE>USB\VID_1B1C&PID_1B20\1203401BAEB8180655A5C965F5001947</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000006</ADDR><REV>0308</REV>
<DESC>USB Input Device</DESC><DEVPATH>\\?\usb#vid_1b1c&pid_0a2c#30000040#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><DEVINST>44</DEVINST><INSTANCE>USB\VID_1B1C&PID_0A2C\30000040</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>0000000B</ADDR><REV>0000</REV>
<DESC>Generic USB Hub</DESC><DEVPATH>\\?\usb#vid_1b1c&pid_0a36&asmediausbd_hub#6&21b51711&1&4#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><DEVINST>17</DEVINST><INSTANCE>USB\VID_1B1C&PID_0A36&ASMEDIAUSBD_HUB\6&21B51711&1&4</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000008</ADDR><REV>9302</REV>
<DESC>USB Input Device</DESC><DEVPATH>\\?\usb#vid_1b1c&pid_0c04#5&521a615&0&11#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><DEVINST>45</DEVINST><INSTANCE>USB\VID_1B1C&PID_0C04\5&521A615&0&11</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>0000000B</ADDR><REV>0200</REV>
<DESC>USB Input Device</DESC><DEVPATH>\\?\usb#vid_1b1c&pid_0c1e#2400030ac8207aaf0226475f011c00f5#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><DEVINST>46</DEVINST><INSTANCE>USB\VID_1B1C&PID_0C1E\2400030AC8207AAF0226475F011C00F5</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>0000000A</ADDR><REV>0009</REV>
<DESC>Generic SuperSpeed USB Hub</DESC><DEVPATH>\\?\usb#vid_2109&pid_0813&asmediausbd_hubss#00000810#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><DEVINST>34</DEVINST><INSTANCE>USB\VID_2109&PID_0813&ASMEDIAUSBD_HUBSS\00000810</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000010</ADDR><REV>9011</REV>
<DESC>Generic USB Hub</DESC><DEVPATH>\\?\usb#vid_2109&pid_2813&asmediausbd_hub#00000830#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><DEVINST>35</DEVINST><INSTANCE>USB\VID_2109&PID_2813&ASMEDIAUSBD_HUB\00000830</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000011</ADDR><REV>9011</REV>
<DESC>USB Composite Device</DESC><DEVPATH>\\?\usb#vid_17e9&pid_ff0c#lmym1ha000328#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><DEVINST>47</DEVINST><INSTANCE>USB\VID_17E9&PID_FF0C\LMYM1HA000328</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000013</ADDR><REV>3114</REV>------[ DevClass / Human Interface Devices ]------
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_20a0&pid_0006&mi_00#7&1c8766f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>48</DEVINST><INSTANCE>HID\VID_20A0&PID_0006&MI_00\7&1C8766F&0&0000</INSTANCE><BUSNUM>00000005</BUSNUM><ADDR>00000001</ADDR><REV>0200</REV>
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b20&mi_00&col02#7&a5de6ae&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>49</DEVINST><INSTANCE>HID\VID_1B1C&PID_1B20&MI_00&COL02\7&A5DE6AE&0&0001</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>00000002</ADDR><REV>0308</REV>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b20&mi_01#7&19795714&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>50</DEVINST><INSTANCE>HID\VID_1B1C&PID_1B20&MI_01\7&19795714&0&0000</INSTANCE><BUSNUM>00000002</BUSNUM><ADDR>00000001</ADDR><REV>0308</REV>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#virtualdevice&10&col03#2&240820d2&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd</DEVPATH><DEVINST>51</DEVINST><INSTANCE>HID\VIRTUALDEVICE&10&COL03\2&240820D2&0&0002</INSTANCE><BUSNUM>00000010</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_20a0&pid_0006&mi_01&col02#7&5186c6b&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>52</DEVINST><INSTANCE>HID\VID_20A0&PID_0006&MI_01&COL02\7&5186C6B&0&0001</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000002</ADDR><REV>0200</REV>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b3b&mi_01#8&65f2a6f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd</DEVPATH><DEVINST>53</DEVINST><INSTANCE>HID\VID_1B1C&PID_1B3B&MI_01\8&65F2A6F&0&0000</INSTANCE><BUSNUM>00000009</BUSNUM><ADDR>00000001</ADDR><REV>0102</REV>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b20&mi_00&col03#7&a5de6ae&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>54</DEVINST><INSTANCE>HID\VID_1B1C&PID_1B20&MI_00&COL03\7&A5DE6AE&0&0002</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>00000003</ADDR><REV>0308</REV>
<DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b2e&mi_00&col01#7&485f2ac&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>55</DEVINST><INSTANCE>HID\VID_1B1C&PID_1B2E&MI_00&COL01\7&485F2AC&0&0000</INSTANCE><BUSNUM>0000000A</BUSNUM><ADDR>00000001</ADDR><REV>0306</REV>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_0a34#8&1d44a2a4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>56</DEVINST><INSTANCE>HID\VID_1B1C&PID_0A34\8&1D44A2A4&0&0000</INSTANCE><BUSNUM>00000012</BUSNUM><ADDR>00000001</ADDR><REV>0004</REV>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_0c1e#6&74e0344&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>57</DEVINST><INSTANCE>HID\VID_1B1C&PID_0C1E\6&74E0344&0&0000</INSTANCE><BUSNUM>00000003</BUSNUM><ADDR>00000001</ADDR><REV>0009</REV>
<DESC>HID-compliant system controller</DESC><DEVPATH>\\?\hid#vid_20a0&pid_0006&mi_01&col03#7&5186c6b&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>58</DEVINST><INSTANCE>HID\VID_20A0&PID_0006&MI_01&COL03\7&5186C6B&0&0002</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000003</ADDR><REV>0200</REV>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b20&mi_00&col04#7&a5de6ae&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>59</DEVINST><INSTANCE>HID\VID_1B1C&PID_1B20&MI_00&COL04\7&A5DE6AE&0&0003</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>00000004</ADDR><REV>0308</REV>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b2e&mi_00&col02#7&485f2ac&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>60</DEVINST><INSTANCE>HID\VID_1B1C&PID_1B2E&MI_00&COL02\7&485F2AC&0&0001</INSTANCE><BUSNUM>0000000A</BUSNUM><ADDR>00000002</ADDR><REV>0306</REV>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_20a0&pid_0006&mi_02#7&92c757d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>61</DEVINST><INSTANCE>HID\VID_20A0&PID_0006&MI_02\7&92C757D&0&0000</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000001</ADDR><REV>0200</REV>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_0c04#6&35e9b2e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>62</DEVINST><INSTANCE>HID\VID_1B1C&PID_0C04\6&35E9B2E&0&0000</INSTANCE><BUSNUM>00000004</BUSNUM><ADDR>00000001</ADDR><REV>0200</REV>
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_20a0&pid_0006&mi_01&col04#7&5186c6b&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>63</DEVINST><INSTANCE>HID\VID_20A0&PID_0006&MI_01&COL04\7&5186C6B&0&0003</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000004</ADDR><REV>0200</REV>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b3b&mi_00#8&cd0f1cf&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>64</DEVINST><INSTANCE>HID\VID_1B1C&PID_1B3B&MI_00\8&CD0F1CF&0&0000</INSTANCE><BUSNUM>00000008</BUSNUM><ADDR>00000001</ADDR><REV>0102</REV>
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_0a2b&mi_03&col01#9&35e989d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>65</DEVINST><INSTANCE>HID\VID_1B1C&PID_0A2B&MI_03&COL01\9&35E989D&0&0000</INSTANCE><BUSNUM>00000014</BUSNUM><ADDR>00000001</ADDR><REV>0000</REV>
<DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#virtualdevice&10&col01#2&240820d2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>66</DEVINST><INSTANCE>HID\VIRTUALDEVICE&10&COL01\2&240820D2&0&0000</INSTANCE><BUSNUM>00000010</BUSNUM><ADDR>00000001</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b2e&mi_00&col03#7&485f2ac&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>67</DEVINST><INSTANCE>HID\VID_1B1C&PID_1B2E&MI_00&COL03\7&485F2AC&0&0002</INSTANCE><BUSNUM>0000000A</BUSNUM><ADDR>00000003</ADDR><REV>0306</REV>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b20&mi_00&col01#7&a5de6ae&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd</DEVPATH><DEVINST>68</DEVINST><INSTANCE>HID\VID_1B1C&PID_1B20&MI_00&COL01\7&A5DE6AE&0&0000</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>00000001</ADDR><REV>0308</REV>
<DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#virtualdevice&10&col04#2&240820d2&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>69</DEVINST><INSTANCE>HID\VIRTUALDEVICE&10&COL04\2&240820D2&0&0003</INSTANCE><BUSNUM>00000010</BUSNUM><ADDR>00000004</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_0a2b&mi_03&col02#9&35e989d&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>70</DEVINST><INSTANCE>HID\VID_1B1C&PID_0A2B&MI_03&COL02\9&35E989D&0&0001</INSTANCE><BUSNUM>00000014</BUSNUM><ADDR>00000002</ADDR><REV>0000</REV>
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#virtualdevice&10&col05#2&240820d2&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>71</DEVINST><INSTANCE>HID\VIRTUALDEVICE&10&COL05\2&240820D2&0&0004</INSTANCE><BUSNUM>00000010</BUSNUM><ADDR>00000005</ADDR>
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_0a32&mi_03#9&339b5882&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>72</DEVINST><INSTANCE>HID\VID_1B1C&PID_0A32&MI_03\9&339B5882&0&0000</INSTANCE><BUSNUM>00000011</BUSNUM><ADDR>00000001</ADDR><REV>0100</REV>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b2e&mi_01#7&285d306e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>73</DEVINST><INSTANCE>HID\VID_1B1C&PID_1B2E&MI_01\7&285D306E&0&0000</INSTANCE><BUSNUM>0000000B</BUSNUM><ADDR>00000001</ADDR><REV>0306</REV>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_20a0&pid_0006&mi_01&col01#7&5186c6b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd</DEVPATH><DEVINST>74</DEVINST><INSTANCE>HID\VID_20A0&PID_0006&MI_01&COL01\7&5186C6B&0&0000</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000001</ADDR><REV>0200</REV>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#virtualdevice&10&col02#2&240820d2&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd</DEVPATH><DEVINST>75</DEVINST><INSTANCE>HID\VIRTUALDEVICE&10&COL02\2&240820D2&0&0001</INSTANCE><BUSNUM>00000010</BUSNUM><ADDR>00000002</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_0a2c&col01#8&13ffc47e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>76</DEVINST><INSTANCE>HID\VID_1B1C&PID_0A2C&COL01\8&13FFC47E&0&0000</INSTANCE><BUSNUM>00000013</BUSNUM><ADDR>00000001</ADDR><REV>0000</REV>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_0a2b&mi_03&col03#9&35e989d&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>77</DEVINST><INSTANCE>HID\VID_1B1C&PID_0A2B&MI_03&COL03\9&35E989D&0&0002</INSTANCE><BUSNUM>00000014</BUSNUM><ADDR>00000003</ADDR><REV>0000</REV>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_0a2c&col02#8&13ffc47e&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><DEVINST>78</DEVINST><INSTANCE>HID\VID_1B1C&PID_0A2C&COL02\8&13FFC47E&0&0001</INSTANCE><BUSNUM>00000013</BUSNUM><ADDR>00000002</ADDR><REV>0000</REV>------[ HID Device Info / HID-compliant vendor-defined device ]------
Manufacturer : flirc.tv
Product : flirc
Device ID : 20A0-0006
Revision : 0200h
Device Instance : HID\VID_20A0&PID_0006&MI_00\7&1C8766F&0&0000
Usage : 0001h
Usage Page : FF00h
Input Report Byte Length : 65
Output Report Byte Length : 65
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant consumer control device ]------
Manufacturer : Corsair
Product : Corsair STRAFE RGB Gaming Keyboard
Serial Number : 1203401BAEB8180655A5C965F5001947
Device ID : 1B1C-1B20
Revision : 0308h
Device Instance : HID\VID_1B1C&PID_1B20&MI_00&COL02\7&A5DE6AE&0&0001
Usage : 0001h
Usage Page : 000Ch
Input Report Byte Length : 5
Output Report Byte Length : 0
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant vendor-defined device ]------
Manufacturer : Corsair
Product : Corsair STRAFE RGB Gaming Keyboard
Serial Number : 1203401BAEB8180655A5C965F5001947
Device ID : 1B1C-1B20
Revision : 0308h
Device Instance : HID\VID_1B1C&PID_1B20&MI_01\7&19795714&0&0000
Usage : 0004h
Usage Page : FFC2h
Input Report Byte Length : 65
Output Report Byte Length : 65
Feature Report Byte Length: 65------[ HID Device Info / HID-compliant consumer control device ]------
Manufacturer : flirc.tv
Product : flirc
Device ID : 20A0-0006
Revision : 0200h
Device Instance : HID\VID_20A0&PID_0006&MI_01&COL02\7&5186C6B&0&0001
Usage : 0001h
Usage Page : 000Ch
Input Report Byte Length : 2
Output Report Byte Length : 0
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant vendor-defined device ]------
Manufacturer : Corsair
Product : Corsair STRAFE RGB Gaming Keyboard
Serial Number : 1203401BAEB8180655A5C965F5001947
Device ID : 1B1C-1B20
Revision : 0308h
Device Instance : HID\VID_1B1C&PID_1B20&MI_00&COL03\7&A5DE6AE&0&0002
Usage : 0002h
Usage Page : FFC0h
Input Report Byte Length : 64
Output Report Byte Length : 0
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant vendor-defined device ]------
Manufacturer : Corsair
Product : Corsair ST100 LED Driver
Serial Number : 21200307A8047BAF86B5635F041C00F5
Device ID : 1B1C-0A34
Revision : 0004h
Device Instance : HID\VID_1B1C&PID_0A34\8&1D44A2A4&0&0000
Usage : 0001h
Usage Page : FFC2h
Input Report Byte Length : 65
Output Report Byte Length : 65
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant vendor-defined device ]------
Manufacturer : Corsair
Product : CORSAIR iCUE LS100 Smart Lighting Strip Starter Kit
Serial Number : 2400030AC8207AAF0226475F011C00F5
Device ID : 1B1C-0C1E
Revision : 0009h
Device Instance : HID\VID_1B1C&PID_0C1E\6&74E0344&0&0000
Usage : 0001h
Usage Page : FFC0h
Input Report Byte Length : 17
Output Report Byte Length : 65
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant system controller ]------
Manufacturer : flirc.tv
Product : flirc
Device ID : 20A0-0006
Revision : 0200h
Device Instance : HID\VID_20A0&PID_0006&MI_01&COL03\7&5186C6B&0&0002
Usage : 0080h
Usage Page : 0001h
Input Report Byte Length : 2
Output Report Byte Length : 0
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant vendor-defined device ]------
Manufacturer : Corsair
Product : Corsair STRAFE RGB Gaming Keyboard
Serial Number : 1203401BAEB8180655A5C965F5001947
Device ID : 1B1C-1B20
Revision : 0308h
Device Instance : HID\VID_1B1C&PID_1B20&MI_00&COL04\7&A5DE6AE&0&0003
Usage : 0003h
Usage Page : FFC2h
Input Report Byte Length : 64
Output Report Byte Length : 0
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant vendor-defined device ]------
Manufacturer : Corsair
Product : Corsair Gaming M65 Pro RGB Mouse
Serial Number : 17019008AEB890E555ACE715F5001944
Device ID : 1B1C-1B2E
Revision : 0306h
Device Instance : HID\VID_1B1C&PID_1B2E&MI_00&COL02\7&485F2AC&0&0001
Usage : 0002h
Usage Page : FFC1h
Input Report Byte Length : 64
Output Report Byte Length : 0
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant vendor-defined device ]------
Manufacturer : flirc.tv
Product : flirc
Device ID : 20A0-0006
Revision : 0200h
Device Instance : HID\VID_20A0&PID_0006&MI_02\7&92C757D&0&0000
Usage : 0001h
Usage Page : FF00h
Input Report Byte Length : 65
Output Report Byte Length : 65
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant vendor-defined device ]------
Manufacturer : Corsair Memory, Inc.
Product : Integrated USB Bridge
Device ID : 1B1C-0C04
Revision : 0200h
Device Instance : HID\VID_1B1C&PID_0C04\6&35E9B2E&0&0000
Usage : 0001h
Usage Page : FF00h
Input Report Byte Length : 65
Output Report Byte Length : 65
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant consumer control device ]------
Manufacturer : flirc.tv
Product : flirc
Device ID : 20A0-0006
Revision : 0200h
Device Instance : HID\VID_20A0&PID_0006&MI_01&COL04\7&5186C6B&0&0003
Usage : 0001h
Usage Page : 000Ch
Input Report Byte Length : 2
Output Report Byte Length : 0
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant vendor-defined device ]------
Manufacturer : Corsair Components, Inc.
Product : Corsair Gaming MM800 RGB POLARIS
Serial Number : 43B0020C621C75AFDC45D25E071C00F5
Device ID : 1B1C-1B3B
Revision : 0102h
Device Instance : HID\VID_1B1C&PID_1B3B&MI_00\8&CD0F1CF&0&0000
Usage : 0001h
Usage Page : FFC2h
Input Report Byte Length : 65
Output Report Byte Length : 65
Feature Report Byte Length: 65------[ HID Device Info / HID-compliant consumer control device ]------
Manufacturer : Corsair
Product : Hid Interface
Device ID : 1B1C-0A2B
Revision : 0000h
Device Instance : HID\VID_1B1C&PID_0A2B&MI_03&COL01\9&35E989D&0&0000
Usage : 0001h
Usage Page : 000Ch
Input Report Byte Length : 3
Output Report Byte Length : 0
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant vendor-defined device ]------
Manufacturer : Corsair
Product : Corsair Gaming M65 Pro RGB Mouse
Serial Number : 17019008AEB890E555ACE715F5001944
Device ID : 1B1C-1B2E
Revision : 0306h
Device Instance : HID\VID_1B1C&PID_1B2E&MI_00&COL03\7&485F2AC&0&0002
Usage : 0003h
Usage Page : FFC2h
Input Report Byte Length : 64
Output Report Byte Length : 0
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant vendor-defined device ]------
Manufacturer : Corsair
Product : Hid Interface
Device ID : 1B1C-0A2B
Revision : 0000h
Device Instance : HID\VID_1B1C&PID_0A2B&MI_03&COL02\9&35E989D&0&0001
Usage : 0001h
Usage Page : FFC5h
Input Report Byte Length : 5
Output Report Byte Length : 20
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant consumer control device ]------
Device ID : 1B1C-1BF0
Revision : 0001h
Device Instance : HID\VIRTUALDEVICE&10&COL05\2&240820D2&0&0004
Usage : 0001h
Usage Page : 000Ch
Input Report Byte Length : 3
Output Report Byte Length : 0
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant consumer control device ]------
Manufacturer : Corsair Components Inc.
Product : Corsair ST100 Headset Output
Serial Number : v0.6
Device ID : 1B1C-0A32
Revision : 0100h
Device Instance : HID\VID_1B1C&PID_0A32&MI_03\9&339B5882&0&0000
Usage : 0001h
Usage Page : 000Ch
Input Report Byte Length : 5
Output Report Byte Length : 5
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant vendor-defined device ]------
Manufacturer : Corsair
Product : Corsair Gaming M65 Pro RGB Mouse
Serial Number : 17019008AEB890E555ACE715F5001944
Device ID : 1B1C-1B2E
Revision : 0306h
Device Instance : HID\VID_1B1C&PID_1B2E&MI_01\7&285D306E&0&0000
Usage : 0004h
Usage Page : FFC2h
Input Report Byte Length : 65
Output Report Byte Length : 65
Feature Report Byte Length: 65------[ HID Device Info / HID-compliant vendor-defined device ]------
Manufacturer : Corsair
Product : Corsair VOID RGB Wireless Gaming Headset
Device ID : 1B1C-0A2C
Revision : 0000h
Device Instance : HID\VID_1B1C&PID_0A2C&COL01\8&13FFC47E&0&0000
Usage : 0001h
Usage Page : FFC5h
Input Report Byte Length : 5
Output Report Byte Length : 2
Feature Report Byte Length: 0------[ HID Device Info / HID-compliant vendor-defined device ]------
Manufacturer : Corsair
Product : Hid Interface
Device ID : 1B1C-0A2B
Revision : 0000h
Device Instance : HID\VID_1B1C&PID_0A2B&MI_03&COL03\9&35E989D&0&0002
Usage : 0001h
Usage Page : FF00h
Input Report Byte Length : 64
Output Report Byte Length : 64
Feature Report Byte Length: 64------[ HID Device Info / HID-compliant vendor-defined device ]------
Manufacturer : Corsair
Product : Corsair VOID RGB Wireless Gaming Headset
Device ID : 1B1C-0A2C
Revision : 0000h
Device Instance : HID\VID_1B1C&PID_0A2C&COL02\8&13FFC47E&0&0001
Usage : 0001h
Usage Page : FF00h
Input Report Byte Length : 64
Output Report Byte Length : 0
Feature Report Byte Length: 64------[ DevClass / COM Ports ]------
<DESC>Communications Port (COM1)</DESC><DEVPATH>\\?\acpi#pnp0501#0#{86e0d1e0-8089-11d0-9ce4-08003e301f73}</DEVPATH><DEVINST>79</DEVINST><INSTANCE>ACPI\PNP0501\0</INSTANCE><BUSNUM>00000000</BUSNUM>
------[ DevClass / LPT Ports ]------
< No LPT Port Found >
------[ DevClass / Modems ]------
< No Modem Found >
------[ DevClass / SideShow Devices ]------
< No SideShow Device Found >
------[ DevClass / GX3 Devices ]------
< No GX3 Device Found >
------[ DevClass / USBXpress Devices ]------
< No USBXpress Device Found >
------[ DevClass / WinUSB Devices ]------
< No WinUSB Device Found >
------[ LibUsb0 Devices ]------
< No LibUsb0 Device Found >
------[ CH341 Devices ]------
< No CH341 Device Found >
------[ FTD2xx Devices ]------
< No FTD2xx Device Found >
------[ LibMPSSE Devices ]------
< No LibMPSSE Device Found >
------[ SiUSBXp Devices ]------
SiUSBXp.dll Path = C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\SiUSBXp.dll
DLL Version = 3.5.0.0
Driver Version =< No SiUSBXp Device Found >
------[ T-Balancer Devices ]------
< No T-Balancer Device Found >
------[ Koolance TMS-200 Devices ]------
< No T-Koolance TMS-200 Device Found >
------[ GRID+ V3 Devices ]------
< No GRID+ V3 Device Found >
------[ Smart Dev V2 Devices ]------
< No Smart Dev V2 Device Found >
------[ Kraken X-2/X-3 Devices ]------
< No Kraken X-2/X-3 Device Found >
-
Hopefully this is the correct sub-forum to ask this question.
I assume I need to buy the Extreme Edition of Aida64 for Personal use on at least 2 of my PC's for Sensor Panels. Am I correct in assuming that you need to buy Aida64 for this use-case or is there a free version you use for Sensor Panels and only need the paid version for Benchmarking???
Anyway, I noted that the Extreme (Personal Use) version allows you to use Aida64 on 3 PC's. I was already planning to use it on two of mine already but I realised, why not use the third licence on my HTPC. The available space on the front panel of the PC case is 8cm/3.14" wide by 11cm/4.33" tall.
Can anyone recommend an Aida64 compatible screen, HDMI or USB will do, at or close to but not above those dimensions?
[EDIT] Its OK. I found the Beada Panels and in the sizes I wanted. Full Steam ahead now! Utilising the 3 PC licences of the Extreme AIDA64 tier. 1 Panel in my main VR Gaming Rig, 2 Panels in my 12 Bay Media Server and 1 small panel in my Brothers HTPC formfactor rig.
-
1 can be a HDMI screen but any more have to be supported USB screens and added via the 'LCD' functionality of AIDA64
-
2 hours ago, Fiery said:
As far as I can understand, both those displays would appear as a monitor in Windows. In that case you can only use one of them with AIDA64 since SensorPanel only supports a single instance. If you can find a display that connects as an external (e.g. USB) screen and uses a LCD protocol that AIDA64 supports, you can scale the whole config up a lot better than with small monitors.
Forget about the Snowblind Mod screen on the side panel for a moment.
So I can run my conventional Desktop Monitor connected to my motherboard with Display Port and I can also run the rPI HDMI 7" display as a Sensor Panel on the front of my case. Thats the setup most people have/use.
You are saying that if I want another sensor panel as well as the small HDMI 7" one, that I need to use a USB Monitor as the second Sensor Panel and utilise AIDA64's LCD display support.
I'm not sure if you missed this information but' I said at the beginning that the monitor I am going to use for the second sensor panel display on the Side Window of the Media Server for my Snowblind Mod is this - AOC 1366x768 e1659Fwu 16 Inch Portable LED Glossy Black USB 3.0 Monitor. ie. This is not a HDMI or Display Port Monitor. It connects via USB 3.0.
So with that in mind does this mean that YES I can run both the 7" HDMI rPI screen and the USB 3.0 AOC 'SnowBlind' screens with a different Sensor Panel layout on each all run from one instance of AIDA64??
Or did you already note that the AOC display is a USB 3.0 screen but it is simply just not one of the currently supported USB screens in AIDA64? Would it help if I installed AIDA64 on my current PC and connect that USB Monitor to it and get AIDA64 to spit out all the hardware/driver specs of this Monitor and post here so that maybe support for this monitor could be added to AIDA64 USB LCD Panel support?
-
28 minutes ago, Fiery said:
My previous idea/suggestion is still valid since you can still use only a single instance of the SensorPanel.
To be clear. Are you saying that YES? I could run 1 instance of AIDA64/Sensor Panel and using the 'LCD Facility' of AIDA64, I could create two different layouts, one layout that displays only CPU/RAM/LOGO's etc info on the front of case 7" rPI LCD Touchscreen Display and then a different layout that displays only HDD related info on the Side Window Snowblind Mod USB3.0 LCD Display?
I need clarification before I start cutting and modding the chassis and plastic of my case, because once I do that I can't undo it, and thus I need to be 100% sure that my idea is possible to achieve with AIDA64.
Nagyon szépen köszönöm !
-
Apologies Mods for double posting, I realised my other thread might be in the wrong sub-forum. If you need to delete one, please delete the other one in the 'General' sub-forum.
I have long planned a 'Snowblind Mod' for the Windowed side panel of my soon to be built 12 bay Media Server.
https://youtu.be/uq8GTglYJNw?t=711
The USB Monitor I am using as the donor screen for the Snowblind Mod is the AOC 1366x768 e1659Fwu 16 Inch Portable LED Glossy Black USB 3.0 Monitor.
However, I also want to mount a 7" HDMI Display as a Sensor Panel in the front 5.25" Bays of the case. That 7" Monitor I'd be using for the Sensor Panel is the Raspberry Pi Monitor, EVICIV 7 Inch Touchscreen Monitor, 1024x600 HD Display. I would also have a 1080p AOC Desktop monitor attached to the PC (No Sensor panel needed for that).
Below is an Old Render of an early iteration of my idea. Hadn't heard of SnowBlind Mods back then, I'm not installing so many hotswap bays anymore, but I am actually going back to the idea of having a front mounted sensor panel screen like in this old render and like I said above. So picture that left side case window with 12 Hotswap bays in the bottom half. I'd cover the whole acrylic window with black Vinyl. In the bottom half of the Vinyl would be a large laser cutout rectangle. (Laser Cut Logo Decals in the top half of the vinyl backlit with the Backlight panel of the Donor screen. Yay, no e-waste!!).
The LCD layer of the Donor screen is affixed on the inside lined up with this rectangular cutout in the Vinyl. You'd still be able to see the Hotswap bays. On that transparent screen I would create a sensor panel such that the HDD widgets/icons I would create are aligned over the physical HDD Bay they correspond to. 'Virtual' & 'Live' Labels so to speak.
So the big question is this. Can I run 2 sensor panels from one instance of AIDA64. The front mounted 7" HDMI Sensor Panel displaying only CPU, RAM info etc and the 'SnowBlind' USB Sensor panel displaying only Hard Drive related information where I would create a layout with 'Virtual' & 'Live' labels for each HDD with the Virtual label aligned over the actual physical Hotswap Bay it corresponds to.
I found this quote from Fiery from last year where he says this to a similar question but I am not sure if his suggestion is what I am effectively doing with 2 discrete Displays for my sensor panels.
QuoteI know it's not the best advice, and also it would cost you money, but picking one (or even more than one) external LCD screen would enable you to use the LCD facility of AIDA64 and effectively double or triple the amount of "SensorPanels" you can use at any given time. For example, if you picked up a BeadaPanel, you could place your secondary readings on it using the same layout editor that you use for SensorPanel.
-
Saw the BPS Customs Youtube video a few weeks ago and bought the 7" RPi Touchscreen he recommended in the Video. The Eviciv MDS7802 1024x600 IPS Touchscreen. I'll be using it in my new Black Lian Li O11 Dynamic XL build just like he did installed in the Rear Exhaust Port location just like he did. No need for Touchscreen functionality for this particular use-case.
However, I am also building a 12 Bay Media Server which while connected to the main monitor will run 'Headless' most of the time for all intents and purposes. The thing is, that this media server will be on my IKEA-Hack Desk along with the main rig and I also want it to look good and thus will have all manner of Corsair iCUE RGB fans and strips on it too. I was going to do a 'SnowBlind Mod on the clear side panel of the case I am using for the Media Server but decied against it in the end. Instead I decided to integrate a Sensor panel like the one I bought for my main gaming rig into the front of the Media Server case Chassis so I can monitor the Servers perfomance, drive health, stats etc without having to switch the main monitor on or change monitor inputs etc Ideally though I would like to be able to add an active Touch button to the sensor Panel to enable/disable Corsair iCUE to turn on and off the RGB lights at night as the Media Server is in my bedroom.
Is this possible to have an active Touch button integrated into an Aida64 Sensor Panel Skin does anybody know?
Ironically the sensor panel on the front of the media server mod is me actually going back to the plan I had and made some sketchup models and renders of back in 2015 but never got around to building.
TIA
Importing Sensor Panels
in General Discussion
Posted
Can someone point me to a fool proof guide on how to import sensor panels.
I found one I liked and DM'd the creator and he emailed it to me a while back. Only getting around to building the PC the sensor panel is going into now. The panel I want to use is a Beadapanel 1280x480. Though I can't remember if the imported panel layout is 1280x480 or if I picked it because I want to mount the screen vertical and thus the res and layout would be 480x1280. At any rate, when I set either res in sensorpanal preferances and import, the import changes the sensor panel to a much smaller res and 16:9 ratio and the formatting is all screwed up. I have done the DPI 100% in aida64.exe, properties/compatibility already. Note I haven't connected the actual beadpanel to the PC as I am just testing things out on a different PC before I start the actual PC build and buy a $50 Aida64 licence. When I set 480x1280 for example with an empty template, it does seem to display a black background sensor panel of that res on my 1920x1080 monitor. Its when I import the user created sensor panel that the sensor panel changes to a much smaller 16:9 window and formating of text and graphs etc is screwed up.
Tbh I don't hold out much hope of either getting a reply here or a solution as googling the issue seems to bring up nothing but unanswered threads here or threads where only the DPI fix is suggested and then weeks/months later the OP or other members posting a reply pleading, "Has anyone fixed this yet??"
Honestly it amazes me that the Sensorpanel functionality is so hard to do or buggy when the software is so expensive for what most people are buying it for. Lets be honest. Most sales in the last few years are probably not people buying it for the hardware monitoring/diagnostic/benchmarking aspects that can be done by other programs for free, but most are probably buying it for the sensor panel functionality...yet that is the aspect of the software that gets the least user support???
I'll happily spend $55+ for a 3 PC licence if I can get it to do what its supposed to do. However, if its this hard to configure with little to no help from either the Dev's or other users, then I am not going to waste my money.