Jump to content
AIDA64 Discussion Forum
Alerax

Sabertooth Z170, cannot get all sensors

Recommended Posts

Hi,

 

I'm looking to buy the Aida64 software, and I was reading the other thread on the Sabertooth Z170, but couldn't find the answer anywhere. I have the Z170 Sabertooth board as well, but for some reason the Aida64 only reads the follow in the Cooling Fans sensors:

 

CPU

CPU OP

Chassis #2

Chassis #3

 

Things that I'm looking to get reading from are:

 

1) Chassis #5 fan speed (connect to CPU_FAN_5)

2) W_Pump speed (NZXT Kraken x61, pump control connected to W_Pump header)

3) Power supply fan (Corsair AX860i, connected using Corsair Link hardware, no software installed)

4) GPU fan speed (980 Strix)

 

Please let me know if Aida64 can support these hardwares and/or what I could do to make the sensors show up.

 

Thanks in advance.

 

Share this post


Link to post
Share on other sites

1) Unfortunately Sabertooth Z170 Series use a special EC muxing method that is very difficult and dangerous to handle by 3rd party software like AIDA64. Asus still refuses to implement the necessary industry standard mutexes to avoid collisions with other monitoring software. And when a collision occurs due to the EC mux, system could lock up. So we cannot risk implementing the EC mux in AIDA64. And without using the EC mux, it's not possible to access several fan header readings :(

2) Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first.

3) Corsair Link is not supported by AIDA64, and we do not plan to support it. Corsair HXi and RMi Series PSUs are supported, but only when they are directly connected to a USB header of the motherboard.

4) Are you sure the fan is spinning? AIDA64 will only pick up the GPU fan and show it on the Computer / Sensor page when it is spinning. It will not show 0 RPM there, but instead hide the relevant line about the GPU fan.

Share this post


Link to post
Share on other sites

Hey Fiery,

 

Thanks for the quick reply. Below is the USB Dump you requested (looks like it's Port 11, Asetek USB Device).

 

1) Copy that. I'll move the connection around.

2) See below.

3) That's unfortunate. (Just checking... this still wont work even if the AXi is connected to the mobo's usb?)

4) My bad, when the GPU on, it shows the fan speed. Bravo.

 

 

 

 

 

------[ AIDA64 Extreme v5.60.3703 Beta ]------
 
------[ Microsoft Windows 10 Home 10.0.10240.16384 (64-bit) ]------
 
------[ Motherboard Info ]------
 
Motherboard ID      : 63-0100-000001-00101111-012115-Chipset$0AAAA000_BIOS DATE: 11/09/15 16:57:43 VER: 05.0000B
Motherboard Model   : Asus Sabertooth Z170 Mark 1
Motherboard Chipset : Intel Sunrise Point Z170, Intel Skylake-S
 
DMI MB Manufacturer : ASUSTeK COMPUTER INC.
DMI MB Product      : SABERTOOTH Z170 MARK 1
DMI MB Version      : Rev 1.xx
DMI MB Serial       : 151056108200199
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    : 1302
 
------[ USB Devices ]------
 
ASMedia USB 3.1 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 >
Intel® 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] < No Device Connected >
- [Port 6] < No Device Connected >
- [Port 7] < No Device Connected >
- [Port 8] Generic USB Hub (ROCCAT Ryos MK Pro Hub)
- - [Port 1] Generic USB Hub
- - - [Port 1] < No Device Connected >
- - - [Port 2] < No Device Connected >
- - - [Port 3] < No Device Connected >
- - - [Port 4] < No Device Connected >
- - [Port 2] < No Device Connected >
- - [Port 3] USB Composite Device (ROCCAT Ryos MK Pro)
- - - USB Input Device
- - - - HID Keyboard Device
- - - USB Input Device
- - - - HID-compliant consumer control device
- - - - HID-compliant device
- - - - HID-compliant device
- - - - HID-compliant system controller
- - - - HID-compliant mouse
- [Port 9] < No Device Connected >
- [Port 10] USB Composite Device (ROCCAT Tyon White)
- - USB Input Device
- - - HID-compliant consumer control device
- - - HID-compliant device
- - - HID-compliant mouse
- - USB Input Device
- - - HID Keyboard Device
- - USB Input Device
- - - HID-compliant game controller
- - USB Input Device
- - - HID-compliant device
- [Port 11] Asetek USB Device (690LC)
- [Port 12] < No Device Connected >
- [Port 13] Unknown Device
- [Port 14] < No Device Connected >
- [Port 15] < No Device Connected >
- [Port 16] < No Device Connected >
- [Port 17] < No Device Connected >
- [Port 18] < No Device Connected >
- [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 >
 
------[ Generic USB Hub]------
 
Device Description   : Generic USB Hub
Device ID            : 1E7D-2EE1
Device Class         : 09 / 00 (Hi-Speed Hub with multiple TTs)
Device Protocol      : 02
Manufacturer         : ROCCAT GmbH
Product              : ROCCAT Ryos MK Pro Hub
Serial Number        : 001000000001
Supported USB Version: 2.00
Current Speed        : High  (USB 2.0)
 
------[ Generic USB Hub]------
 
Device Description   : Generic USB Hub
Device ID            : 1A40-0101
Device Class         : 09 / 00 (Hi-Speed Hub with single TT)
Device Protocol      : 01
Supported USB Version: 2.00
Current Speed        : High  (USB 2.0)
 
------[ USB Composite Device]------
 
Device Description   : USB Composite Device
Device ID            : 1E7D-3232
Device Class         : 03 / 01 (Human Interface Device)
Device Protocol      : 01
Manufacturer         : ROCCAT
Product              : ROCCAT Ryos MK Pro
Supported USB Version: 2.00
Current Speed        : Full  (USB 1.1)
 
------[ USB Composite Device]------
 
Device Description   : USB Composite Device
Device ID            : 1E7D-2E4B
Device Class         : 03 / 01 (Human Interface Device)
Device Protocol      : 02
Manufacturer         : ROCCAT
Product              : ROCCAT Tyon White
Serial Number        : ROC-11-851
Supported USB Version: 2.00
Current Speed        : Full  (USB 1.1)
 
------[ Asetek USB Device]------
 
Device Description   : Asetek USB Device
Device ID            : 2433-B200
Device Class         : FF / 00
Device Protocol      : 00
Manufacturer         : ASETEK
Product              : 690LC
Serial Number        : CCVI_1.0
Supported USB Version: 1.10
Current Speed        : Full  (USB 1.1)
 
------[ Unknown Device]------
 
Device Description   : Unknown Device
Device ID            : 1B1C-1C00
Device Class         : FF / 00
Device Protocol      : 00
Supported USB Version: 1.10
Current Speed        : Full  (USB 1.1)
 
------[ DevClass / USB Hubs ]------
 
<DESC>Generic USB Hub</DESC><DEVPATH>\\?\usb#vid_1e7d&pid_2ee1#msft20001000000001#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\VID_1E7D&PID_2EE1\MSFT20001000000001</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000008</ADDR>
<DESC>USB Root Hub (xHCI)</DESC><DEVPATH>\\?\usb#root_hub30#5&fa529e7&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\ROOT_HUB30\5&FA529E7&0&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
<DESC>Generic USB Hub</DESC><DEVPATH>\\?\usb#vid_1a40&pid_0101#6&274b308e&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\VID_1A40&PID_0101\6&274B308E&0&1</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000001</ADDR>
<DESC>USB Root Hub (xHCI)</DESC><DEVPATH>\\?\usb#root_hub30#4&1148bc98&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}</DEVPATH><INSTANCE>USB\ROOT_HUB30\4&1148BC98&0&0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000000</ADDR>
 
------[ DevClass / USB Devices ]------
 
<DESC>Asetek USB Device</DESC><DEVPATH>\\?\usb#vid_2433&pid_b200#ccvi_1.0#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><INSTANCE>USB\VID_2433&PID_B200\CCVI_1.0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>0000000B</ADDR>
<DESC>USB Composite Device</DESC><DEVPATH>\\?\usb#vid_1e7d&pid_3232#6&274b308e&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><INSTANCE>USB\VID_1E7D&PID_3232\6&274B308E&0&3</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000003</ADDR>
<DESC>USB Composite Device</DESC><DEVPATH>\\?\usb#vid_1e7d&pid_2e4b#roc-11-851#{a5dcbf10-6530-11d2-901f-00c04fb951ed}</DEVPATH><INSTANCE>USB\VID_1E7D&PID_2E4B\ROC-11-851</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>0000000A</ADDR>
 
------[ DevClass / Human Interface Devices ]------
 
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_3232&mi_01&col02#8&26a810af&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_3232&MI_01&COL02\8&26A810AF&0&0001</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000004</ADDR>
<DESC>HID-compliant system controller</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_3232&mi_01&col03#8&26a810af&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_3232&MI_01&COL03\8&26A810AF&0&0002</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000004</ADDR>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_3232&mi_00#8&2d0d2ed&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_3232&MI_00\8&2D0D2ED&0&0000</INSTANCE><BUSNUM>00000005</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant device</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_3232&mi_01&col04#8&26a810af&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_3232&MI_01&COL04\8&26A810AF&0&0003</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000004</ADDR>
<DESC>HID-compliant device</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_3232&mi_01&col05#8&26a810af&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_3232&MI_01&COL05\8&26A810AF&0&0004</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000004</ADDR>
<DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_2e4b&mi_00&col01#7&4319e4c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_2E4B&MI_00&COL01\7&4319E4C&0&0000</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>0000000A</ADDR>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c232#2&33191fed&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C232\2&33191FED&0&0000</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR></ADDR>
<DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_046d&pid_c231#2&1dd8bfaf&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C231\2&1DD8BFAF&0&0000</INSTANCE><BUSNUM>00000008</BUSNUM><ADDR></ADDR>
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_2e4b&mi_00&col02#7&4319e4c&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_2E4B&MI_00&COL02\7&4319E4C&0&0001</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>0000000A</ADDR>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_2e4b&mi_01#7&1bf52a91&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_2E4B&MI_01\7&1BF52A91&0&0000</INSTANCE><BUSNUM>00000002</BUSNUM><ADDR>0000000B</ADDR>
<DESC>HID-compliant device</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_2e4b&mi_00&col03#7&4319e4c&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_2E4B&MI_00&COL03\7&4319E4C&0&0002</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>0000000A</ADDR>
<DESC>HID-compliant game controller</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_2e4b&mi_02#7&33b8b6d6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_2E4B&MI_02\7&33B8B6D6&0&0000</INSTANCE><BUSNUM>00000003</BUSNUM><ADDR>0000000C</ADDR>
<DESC>Virtual XInput Device</DESC><DEVPATH>\\?\hid#myvirtualhiddevice#1&2d595ca7&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\MYVIRTUALHIDDEVICE\1&2D595CA7&1&0000</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR></ADDR>
<DESC>HID-compliant device</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_2e4b&mi_03#7&fe17914&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_2E4B&MI_03\7&FE17914&0&0000</INSTANCE><BUSNUM>00000004</BUSNUM><ADDR>0000000D</ADDR>
<DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_1e7d&pid_3232&mi_01&col01#8&26a810af&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1E7D&PID_3232&MI_01&COL01\8&26A810AF&0&0000</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000004</ADDR>
 
------[ HID Device Info / HID-compliant consumer control device ]------
 
Manufacturer              : ROCCAT
Product                   : ROCCAT Ryos MK Pro
Device ID                 : 1E7D-3232
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 system controller ]------
 
Manufacturer              : ROCCAT
Product                   : ROCCAT Ryos MK Pro
Device ID                 : 1E7D-3232
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 device ]------
 
Manufacturer              : ROCCAT
Product                   : ROCCAT Ryos MK Pro
Device ID                 : 1E7D-3232
Usage                     : 0000h
Usage Page                : 000Ah
Input Report Byte Length  : 5
Output Report Byte Length : 0
Feature Report Byte Length: 0
 
------[ HID Device Info / HID-compliant device ]------
 
Manufacturer              : ROCCAT
Product                   : ROCCAT Ryos MK Pro
Device ID                 : 1E7D-3232
Usage                     : 0000h
Usage Page                : 000Bh
Input Report Byte Length  : 0
Output Report Byte Length : 0
Feature Report Byte Length: 2002
 
------[ HID Device Info / HID-compliant consumer control device ]------
 
Manufacturer              : ROCCAT
Product                   : ROCCAT Tyon White
Serial Number             : ROC-11-851
Device ID                 : 1E7D-2E4B
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 device ]------
 
Manufacturer              : ROCCAT
Product                   : ROCCAT Tyon White
Serial Number             : ROC-11-851
Device ID                 : 1E7D-2E4B
Usage                     : 0000h
Usage Page                : 000Bh
Input Report Byte Length  : 0
Output Report Byte Length : 0
Feature Report Byte Length: 1028
 
------[ HID Device Info / HID-compliant game controller ]------
 
Manufacturer              : ROCCAT
Product                   : ROCCAT Tyon White
Serial Number             : ROC-11-851
Device ID                 : 1E7D-2E4B
Usage                     : 0004h
Usage Page                : 0001h
Input Report Byte Length  : 9
Output Report Byte Length : 8
Feature Report Byte Length: 0
 
------[ HID Device Info / Virtual XInput Device ]------
 
Device ID                 : BEEF-FEED
Usage                     : 0005h
Usage Page                : 0001h
Input Report Byte Length  : 15
Output Report Byte Length : 33
Feature Report Byte Length: 0
 
------[ HID Device Info / HID-compliant device ]------
 
Manufacturer              : ROCCAT
Product                   : ROCCAT Tyon White
Serial Number             : ROC-11-851
Device ID                 : 1E7D-2E4B
Usage                     : 0000h
Usage Page                : 000Ah
Input Report Byte Length  : 5
Output Report Byte Length : 0
Feature Report Byte Length: 0
 
------[ DevClass / COM Ports ]------
 
< No COM Port Found >
 
------[ 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 >
 
------[ LibUsb0 Devices ]------
 
< No LibUsb0 Device Found >
 
------[ CH341 Devices ]------
 
< No CH341 Device Found >
 
------[ FTD2xx Devices ]------
 
< No FTD2xx Device Found >
 
------[ SiUSBXp Devices ]------
 
SiUSBXp.dll Path = 
 
< No SiUSBXp Device Found >

Share this post


Link to post
Share on other sites

2) Thank you for the data. Try to find the file called SiUSBXp.dll on your system, and let me know which path do you have it stored at. AIDA64 tries to load that file to activate Kraken sensor support from multiple paths, but maybe on your system it's at a non-standard location. Then, as a temporary solution, you can try copying the DLL into the installation folder of AIDA64. I suppose it will work that way too, please let me know how it goes.

3) No, AXi is not supported via USB connection either. It uses a special USB protocol that is tough to handle. HXi and RMi are way better about the USB protocol.

Share this post


Link to post
Share on other sites

Awesome. I copied the DLL to the installation folder and it worked. FYI, the folder path is somehow in the C:\RecycleBin.

That's quite odd :) Maybe an anti-virus software moved it there? Please note that it could cause issues with other software like NZXT CAM as well. You may want to copy the file into CAM's installation folder as well, just in case ;)

Share this post


Link to post
Share on other sites

We've implemented support for Corsair Link sensor devices (including Link Commander, Commander Mini, H80, H80i, H100, H100i, H100i GT, H110i, H110i GT, and various Corsair Link capable PSU models) in the latest AIDA64 Extreme beta update available at:

http://www.aida64.com/downloads/latesta64xebeta

After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

Please note that since Corsair's own Corsair Link software is not synchronized with any other monitoring software, it is very important to make sure it is closed, and also that its background service is not running. It's best if you completely uninstall the Corsair Link software. Due to the special precautions required to use the new Corsair Link feature of AIDA64, it is disabled by default. You have to go to AIDA64 / main menu / File / Preferences / Stability, and enable (check) Corsair Link sensor support to activate the new feature.

Let us know how it works on your system. If you find any issues, please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Corsair Link Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...