Jump to content
AIDA64 Discussion Forum
Fiery

Aquaero and Aquaduct sensor support

Recommended Posts

Hi

 

Great release guys. I love it.

 

There are just some small issues:

 

- The value for the current of the pump is different as the aquasuite values. See attached screenshot #1, #3.

Value for current in aquasuite: 0.63 A

Value in Aida64: 0.56 A

 

- All other values are matched.

 

- The value for flow rate is missing in Aida64, but I think it will come within a next release.

 

- I have an Aquaero pressure value in the sensor panel, but I dont have an Aquaero. See Screenshot  #3 - bottom value.

 

Good job so far guys :)

 

Best Regards

aquaerodump.txt

post-28536-0-37211900-1420812969_thumb.jpg

post-28536-0-07543600-1420812970_thumb.jpg

post-28536-0-25479800-1420813239_thumb.jpg

Share this post


Link to post
Share on other sites

Thank you for the feedback and the data. The pressure value shows the one measured by MPS, it's just a labelling issue that doesn't really affect anything fortunately :)

As for the current mismatch, we're still waiting Aqua Computer's instructions on what formula shall we use for certain values to get the proper results. We'll update AIDA64 once we get an answer from Aqua Computer.

As for the missing flow rate, we sadly have no idea how to measure that on AquaStreamXT, MPS and PowerAdjust currently, but we'll try to find out. If we fail to figure it out, hopefully Aqua Computer's friendly staff will help us out.

I'll post updates to this topic on the missing bits & pieces ;)

Share this post


Link to post
Share on other sites

No rush guys. You´re awesome. Good things need time.

 

God Job :)

Meanwhile, we've fine-tuned a few bits about your devices, so please try the latest AIDA64 Extreme beta available at:

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

Let me know if there're still items missing. If that's the case, then please submit a new Aquaero dump ;) Thank you.

(We're still waiting for Aqua Computer's response, so that's why things may still be missing or inaccurate)

Share this post


Link to post
Share on other sites

Here is my dump from Aida64 on the Aquaero.

 

------[ AIDA64 Extreme v5.00.3300 ]------

 
------[ Microsoft Windows 8.1 Professional 6.3.9600.17630 (64-bit) ]------
 
------[ Motherboard Info ]------
 
Motherboard ID      : 63-0100-000001-00101111-122211-Chipset$1APTC022_BIOS DATE: 08/13/13 18:22:21 VER: 21.04
Motherboard Model   : Asus P8Z77-V Pro
Motherboard Chipset : Intel Panther Point Z77, Intel Ivy Bridge
 
DMI MB Manufacturer : ASUSTeK COMPUTER INC.
DMI MB Product      : P8Z77-V PRO
DMI MB Version      : Rev 1.xx
DMI MB Serial       : 130308670300033
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    : 2104
 
 
------[ DevClass / Human Interface Devices ]------
 
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c229&mi_01&col01#9&1df34db6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C229&MI_01&COL01\9&1DF34DB6&0&0000</INSTANCE><BUSNUM>00000008</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c229&mi_01&col02#9&1df34db6&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C229&MI_01&COL02\9&1DF34DB6&0&0001</INSTANCE><BUSNUM>00000008</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_02#8&2258a26&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_02\8&2258A26&0&0000</INSTANCE><BUSNUM>00000002</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c228&mi_01&col01#9&2d2921f9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C228&MI_01&COL01\9&2D2921F9&0&0000</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000002</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c228&mi_01&col02#9&2d2921f9&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C228&MI_01&COL02\9&2D2921F9&0&0001</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000002</ADDR>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_00&col01#8&9ee2757&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_00&COL01\8&9EE2757&0&0000</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000001</ADDR>
<DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_046d&pid_c231#2&1652c37&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C231\2&1652C37&0&0000</INSTANCE><BUSNUM>0000000A</BUSNUM><ADDR></ADDR>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c228&mi_00#9&4be7430&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C228&MI_00\9&4BE7430&0&0000</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000001</ADDR>
<DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_00&col02#8&9ee2757&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_00&COL02\8&9EE2757&0&0001</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000001</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f003#7&37853827&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F003\7&37853827&0&0000</INSTANCE><BUSNUM>00000003</BUSNUM><ADDR>00000002</ADDR>
<DESC>Logitech HID-compliant G700 Gaming Mouse</DESC><DEVPATH>\\?\hid#vid_046d&pid_c06b&mi_00#8&37788258&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C06B&MI_00\8&37788258&0&0000</INSTANCE><BUSNUM>00000018</BUSNUM><ADDR>00000005</ADDR>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c06b&mi_01&col01#8&13a14496&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C06B&MI_01&COL01\8&13A14496&0&0000</INSTANCE><BUSNUM>00000019</BUSNUM><ADDR>00000006</ADDR>
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c06b&mi_01&col02#8&13a14496&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C06B&MI_01&COL02\8&13A14496&0&0001</INSTANCE><BUSNUM>00000019</BUSNUM><ADDR>00000006</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c06b&mi_01&col03#8&13a14496&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C06B&MI_01&COL03\8&13A14496&0&0002</INSTANCE><BUSNUM>00000019</BUSNUM><ADDR>00000006</ADDR>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c232#2&1928b87c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C232\2&1928B87C&0&0000</INSTANCE><BUSNUM>00000009</BUSNUM><ADDR></ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c06b&mi_01&col04#8&13a14496&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C06B&MI_01&COL04\8&13A14496&0&0003</INSTANCE><BUSNUM>00000019</BUSNUM><ADDR>00000006</ADDR>
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_01&col01#8&21b1b39c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_01&COL01\8&21B1B39C&0&0000</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>00000002</ADDR>
<DESC>HID-compliant system controller</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_01&col02#8&21b1b39c&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_01&COL02\8&21B1B39C&0&0001</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>00000002</ADDR>
 
------[ Aquaero/Aquaduct Device ]------
 
Manufacturer               = Aqua Computer GmbH & Co. KG
Product                    = aquaero Device
Serial Number              = 00093-35186
Device ID                  = 0C70-F001
Usage                      = 0001h
Usage Page                 = FF00h
Input Report Byte Length   = 1038
Output Report Byte Length  = 2114
Feature Report Byte Length = 2645
 
------[ AA5 Input Report ]------
 
Structure Version  = 1200
Firmware Version   = 2001
Bootloader Version = 102
Hardware Version   = 6000
Device Type        = 1  (Aquaero 5 Pro)
 
0000  0B 97 5B 2D  04 B0 00 5D  89 72 07 D1  00 66 17 70  ..[-...].r...f.p
0010  00 0C 35 3F  01 E9 D3 02  03 00 00 01  00 0B 00 00  ..5?............
0020  00 00 00 02  1E 8C ED FF  00 00 00 01  00 FF FF 00  ................
0030  0F A0 0F A0  01 F4 00 00  00 00 04 00  9F 42 FF C5  .............B..
0040  A8 A9 A6 B4  AA B3 FF C5  FF C8 FF C7  A4 5A 00 48  .............Z.H
0050  A4 4C 00 44  5C 81 15 72  59 B0 06 1D  65 9F 6D 7F  .L.D\..rY...e.m.
0060  6B 0F 5C 5E  0A 9C 7F FF  09 01 09 57  08 A5 7F FF  k.\^.......W....
0070  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  ................
0080  7F FF 7F FF  13 88 13 88  13 88 13 88  13 88 13 88  ................
0090  13 88 13 88  7F FF 7F FF  7F FF 7F FF  7F FF 0A D0  ................
00A0  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  ................
00B0  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  0B 58 0B 58  .............X.X
00C0  0C 9C 0C 9C  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  ................
00D0  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  ................
00E0  7F FF 7F FF  00 00 0F B8  00 00 0F B3  00 00 0C 95  ................
00F0  00 00 0F B0  00 00 00 00  00 00 00 00  7F FF 7F FF  ................
0100  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  00 00 7F FF  ................
0110  7F FF 7F FF  FF FF 7F FF  7F FF 00 00  00 00 7F FF  ................
0120  FF FF 7F FF  7F FF 00 00  00 00 7F FF  FF FF 7F FF  ................
0130  7F FF 00 00  00 00 7F FF  FF FF 7F FF  7F FF 00 00  ................
0140  00 00 7F FF  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  ................
0150  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  ................
0160  7F FF 7F FF  0D AC 02 E8  10 AB 04 AC  00 00 00 00  ................
0170  00 00 02 E9  10 AB 04 AC  00 00 00 00  00 00 03 A3  ................
0180  16 2E 02 A1  01 62 00 EE  00 F4 02 EB  15 82 02 8C  .....b..........
0190  00 7C 00 50  00 66 00 00  27 10 00 00  00 00 00 00  .|.P.f..'.......
01A0  00 00 00 00  27 10 00 00  00 00 00 00  00 00 00 00  ....'...........
01B0  27 10 00 00  00 00 00 00  00 00 00 00  27 10 00 00  '...........'...
01C0  00 00 00 00  00 00 00 00  27 10 00 00  00 00 00 00  ........'.......
01D0  00 00 00 00  27 10 00 00  00 00 00 00  00 00 00 00  ....'...........
01E0  27 10 00 00  00 00 00 00  00 00 00 00  27 10 00 00  '...........'...
01F0  00 00 00 00  00 00 02 FF  FF FF FF FF  FF FF 02 FF  ................
0200  FF FF FF FF  FF FF 00 FF  00 00 FF FF  FF FF 02 FF  ................
0210  00 00 FF FF  FF FF 02 FF  00 00 FF FF  FF FF 02 FF  ................
0220  00 00 FF FF  FF FF 00 FF  FF FF FF FF  FF FF 00 FF  ................
0230  FF FF FF FF  FF FF 00 00  00 3F 00 00  00 00 00 00  .........?......
0240  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0250  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0260  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0270  00 00 00 00  00 00 00 00  00 00 27 10  27 10 27 10  ..........'.'.'.
0280  27 10 27 10  27 10 27 10  27 10 00 00  00 00 00 00  '.'.'.'.'.......
0290  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
02A0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
02B0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
02C0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
02D0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 27 10  ..............'.
02E0  00 00 27 10  27 10 27 10  27 10 27 10  27 10 27 10  ..'.'.'.'.'.'.'.
02F0  27 10 27 10  27 10 27 10  27 10 27 10  27 10 00 00  '.'.'.'.'.'.'...
0300  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0310  00 00 00 00  00 00 00 00  00 00 00 00  00 00 0D 97  ................
0320  27 10 00 00  00 00 27 10  23 38 00 00  27 10 23 38  '.....'.#8..'.#8
0330  00 00 27 10  23 38 00 00  00 00 00 00  00 00 00 00  ..'.#8..........
0340  00 00 00 00  00 00 06 18  0D FC 0E F3  00 00 00 00  ................
0350  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0360  00 00 00 00  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
0370  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
0380  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
0390  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
03A0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
03B0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
03C0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
03D0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
03E0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
03F0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
0400  FF FF FF FF  FF FF FF FF  FF 09 53 CC  AB           ..........S..

 
Any help getting my flow sensor to show readings would be helpful.. 

Share this post


Link to post
Share on other sites

Here is my dump from Aida64 on the Aquaero.

[...] 

Any help getting my flow sensor to show readings would be helpful..

Thank you for the data. Please upgrade to the latest beta version of AIDA64 Extreme available at:

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

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

Let me know if it helps. If not, then please post a new Aquaero Dump made by the new beta.

Share this post


Link to post
Share on other sites

Hi,

 

I'm also using Aquaero and AIDA64 and for the most part it looks fine, it finds all the sensors except for the "mps Flow 100" (connected to Aquaero via Aquabus)). It shows as "Flow 11" in Aquasuite flow sensors, but I don't seem to get a sensor option for it in AIDA64. The mps Pressure for the liquid levels on the other hand shows up fine and also the temperature sensors for both mps devices.

 

Here is the dump (it is an Aquaero 6 XT btw, not a 5 XT as the dump says, the flow at the time I took the dump was somewhere between 97 and 99 L/h):

 

------[ AIDA64 Extreme v5.20.3400 ]------

------[ Microsoft Windows 8.1 Professional 6.3.9600.17736 (64-bit) ]------

------[ Motherboard Info ]------

Motherboard ID      : 63-0100-000001-00101111-080514-Chipset$A1103121_BIOS DATE: 12/17/14 20:18:22 VER: 04.06.05
Motherboard Model   : ASRock Z97 Extreme9
Motherboard Chipset : Intel Wildcat Point Z97, Intel Haswell

DMI MB Manufacturer : ASRock
DMI MB Product      : Z97 Extreme9
DMI MB Version      : 
DMI MB Serial       : E8P-44001400034
DMI SYS Manufacturer: To Be Filled By O.E.M.
DMI SYS Product     : To Be Filled By O.E.M.
DMI SYS Version     : To Be Filled By O.E.M.
DMI SYS Serial      : To Be Filled By O.E.M.
DMI BIOS Version    : P1.30


------[ DevClass / Human Interface Devices ]------

<DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_046d&pid_c714&col01#7&1b7abfeb&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C714&COL01\7&1B7ABFEB&0&0000</INSTANCE><BUSNUM>00000005</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_046d&pid_c714&col02#7&1b7abfeb&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C714&COL02\7&1B7ABFEB&0&0001</INSTANCE><BUSNUM>00000005</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c714&col03#7&1b7abfeb&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C714&COL03\7&1B7ABFEB&0&0002</INSTANCE><BUSNUM>00000005</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c713#7&d0202c2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C713\7&D0202C2&0&0000</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000002</ADDR>
<DESC>HID-compliant system controller</DESC><DEVPATH>\\?\hid#vid_046d&pid_c714&col04#7&1b7abfeb&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C714&COL04\7&1B7ABFEB&0&0003</INSTANCE><BUSNUM>00000005</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c714&col05#7&1b7abfeb&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C714&COL05\7&1B7ABFEB&0&0004</INSTANCE><BUSNUM>00000005</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c714&col06#7&1b7abfeb&0&0005#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C714&COL06\7&1B7ABFEB&0&0005</INSTANCE><BUSNUM>00000005</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c714&col07#7&1b7abfeb&0&0006#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C714&COL07\7&1B7ABFEB&0&0006</INSTANCE><BUSNUM>00000005</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_00&col01#7&297f640&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_00&COL01\7&297F640&0&0000</INSTANCE><BUSNUM>00000017</BUSNUM><ADDR>00000008</ADDR>
<DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_00&col02#7&297f640&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_00&COL02\7&297F640&0&0001</INSTANCE><BUSNUM>00000017</BUSNUM><ADDR>00000008</ADDR>
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_01&col01#7&15c8127e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_01&COL01\7&15C8127E&0&0000</INSTANCE><BUSNUM>00000018</BUSNUM><ADDR>00000009</ADDR>
<DESC>HID-compliant system controller</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_01&col02#7&15c8127e&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_01&COL02\7&15C8127E&0&0001</INSTANCE><BUSNUM>00000018</BUSNUM><ADDR>00000009</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_02#7&28f82ebc&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_02\7&28F82EBC&0&0000</INSTANCE><BUSNUM>00000019</BUSNUM><ADDR>0000000A</ADDR>
<DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_046d&pid_c52b&mi_01&col01#8&16e6c1e4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C52B&MI_01&COL01\8&16E6C1E4&0&0000</INSTANCE><BUSNUM>00000003</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c52b&mi_01&col02#8&16e6c1e4&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C52B&MI_01&COL02\8&16E6C1E4&0&0001</INSTANCE><BUSNUM>00000003</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant system controller</DESC><DEVPATH>\\?\hid#vid_046d&pid_c52b&mi_01&col03#8&16e6c1e4&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C52B&MI_01&COL03\8&16E6C1E4&0&0002</INSTANCE><BUSNUM>00000003</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c52b&mi_01&col04#8&16e6c1e4&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C52B&MI_01&COL04\8&16E6C1E4&0&0003</INSTANCE><BUSNUM>00000003</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c52b&mi_02&col01#8&3abdffa6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C52B&MI_02&COL01\8&3ABDFFA6&0&0000</INSTANCE><BUSNUM>00000004</BUSNUM><ADDR>00000004</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c52b&mi_02&col02#8&3abdffa6&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C52B&MI_02&COL02\8&3ABDFFA6&0&0001</INSTANCE><BUSNUM>00000004</BUSNUM><ADDR>00000004</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c52b&mi_02&col03#8&3abdffa6&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C52B&MI_02&COL03\8&3ABDFFA6&0&0002</INSTANCE><BUSNUM>00000004</BUSNUM><ADDR>00000004</ADDR>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c52b&mi_00#8&2eaa4e29&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C52B&MI_00\8&2EAA4E29&0&0000</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000002</ADDR>

------[ HID Device Info / HID-compliant consumer control device ]------

Manufacturer              : Aqua Computer GmbH & Co. KG
Product                   : aquaero System Control
Serial Number             : 09009-14142
Device ID                 : 0C70-F001
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              : Aqua Computer GmbH & Co. KG
Product                   : aquaero System Control
Serial Number             : 09009-14142
Device ID                 : 0C70-F001
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              : Aqua Computer GmbH & Co. KG
Product                   : aquaero Device
Serial Number             : 09009-14142
Device ID                 : 0C70-F001
Usage                     : 0001h
Usage Page                : FF00h
Input Report Byte Length  : 1038
Output Report Byte Length : 2114
Feature Report Byte Length: 2645

------[ Aquaero/Aquaduct Device ]------

Manufacturer               = Aqua Computer GmbH & Co. KG
Product                    = aquaero Device
Serial Number              = 09009-14142
Device ID                  = 0C70-F001
Usage                      = 0001h
Usage Page                 = FF00h
Input Report Byte Length   = 1038
Output Report Byte Length  = 2114
Feature Report Byte Length = 2645

------[ AA5 Input Report ]------

Structure Version  = 1200
Firmware Version   = 2003
Bootloader Version = 102
Hardware Version   = 6000
Device Type        = 2  (Aquaero 5 XT)

0000  0B E1 9A 5D  04 B0 23 31  37 3E 07 D3  00 66 17 70  ...]..#17>...f.p
0010  00 00 34 BF  00 00 38 3C  03 00 00 02  00 0F 00 00  ..4...8<........
0020  00 00 01 0B  E1 90 15 02  00 00 02 01  FF FF FF 00  ................
0030  0F A0 0F A0  01 F4 00 00  00 00 0C 01  94 85 FF D2  ................
0040  FF D2 FF D3  FF D2 FF CE  FF D2 FF CE  3C C8 02 B5  ............<...
0050  3C 33 01 8C  A6 47 00 70  A6 18 00 6E  6A 8A 62 BD  <3...G.p...nj.b.
0060  6B 7E 5C 64  0C 6F 7F FF  7F FF 7F FF  7F FF 7F FF  k~\d.o..........
0070  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  ................
0080  7F FF 7F FF  13 88 13 88  13 88 13 88  13 88 13 88  ................
0090  13 88 13 88  7F FF 7F FF  7F FF 7F FF  7F FF 0C E1  ................
00A0  7F FF 0A 52  7F FF 7F FF  7F FF 7F FF  0B 14 7F FF  ...R............
00B0  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  0C 1E 0C 1E  ................
00C0  0A DD 0A DD  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  ................
00D0  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  ................
00E0  7F FF 7F FF  00 00 16 C3  00 00 15 75  00 00 00 00  ...........u....
00F0  00 00 00 00  00 00 00 00  00 00 00 00  7F FF 7F FF  ................
0100  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  03 D1 7F FF  ................
0110  7F FF 7F FF  FF FF 7F FF  7F FF 00 00  00 00 7F FF  ................
0120  FF FF 7F FF  7F FF 00 00  00 00 7F FF  FF FF 7F FF  ................
0130  7F FF 00 00  00 00 7F FF  FF FF 7F FF  7F FF 00 00  ................
0140  00 00 7F FF  7F FF 24 AF  7F FF 7F FF  7F FF 7F FF  ......$.........
0150  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  ................
0160  7F FF 7F FF  0D AC 02 06  0E BB 01 BA  00 3F 00 1B  .............?..
0170  00 31 02 23  0E 58 01 B6  00 00 00 00  00 00 00 00  .1.#.X..........
0180  27 10 04 BA  00 00 00 00  00 00 00 00  27 10 04 B9  '...........'...
0190  00 00 00 00  00 00 00 00  27 10 00 00  00 00 00 00  ........'.......
01A0  00 00 00 00  27 10 00 00  00 00 00 00  00 00 00 00  ....'...........
01B0  27 10 00 00  00 00 00 00  00 00 00 00  27 10 00 00  '...........'...
01C0  00 00 00 00  00 00 00 00  27 10 00 00  00 00 00 00  ........'.......
01D0  00 00 00 00  27 10 00 00  00 00 00 00  00 00 00 00  ....'...........
01E0  27 10 00 00  00 00 00 00  00 00 00 00  27 10 00 00  '...........'...
01F0  00 00 00 00  00 00 01 00  12 FC 04 C4  02 53 02 FF  .............S..
0200  FF FF FF FF  FF FF 00 FF  00 00 FF FF  FF FF 00 FF  ................
0210  00 00 FF FF  FF FF 02 FF  00 00 FF FF  FF FF 02 FF  ................
0220  00 00 FF FF  FF FF 00 FF  FF FF FF FF  FF FF 00 FF  ................
0230  FF FF FF FF  FF FF 40 00  00 3F 00 00  00 00 00 00  ......@..?......
0240  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0250  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0260  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0270  00 00 00 00  00 00 00 00  00 00 27 10  27 10 27 10  ..........'.'.'.
0280  27 10 27 10  27 10 27 10  27 10 00 00  00 00 00 00  '.'.'.'.'.......
0290  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
02A0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
02B0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
02C0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
02D0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 71  ...............q
02E0  00 71 17 72  27 10 27 10  27 10 27 10  27 10 27 10  .q.r'.'.'.'.'.'.
02F0  27 10 27 10  27 10 27 10  27 10 27 10  27 10 00 00  '.'.'.'.'.'.'...
0300  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0310  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0320  27 10 11 41  27 10 00 00  10 2B 27 10  00 00 10 2B  '..A'....+'....+
0330  27 10 00 00  10 2B 00 00  00 00 00 00  00 00 00 00  '....+..........
0340  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0350  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0360  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0370  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0380  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0390  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
03A0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
03B0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
03C0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
03D0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
03E0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
03F0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0400  00 00 00 00  00 00 00 00  00 3A AF E9  08           .........:...

Share this post


Link to post
Share on other sites

I have now found out that in LCD items the flow sensors actually DO show up (Flow #1, Flow #2, Flow #11, just like in Aquasuite)!

So it seems rather that this has been forgotten for Sensor Icons than it being a bug. In the LCD (web server) the readings also show up fine.

Would be great if this was also available for the sensor icons in the tray bar.

 

I also managed to provide data TO aquasuite by enabling WMI, using it to control the internal fans via aquaero using the Motherboard temperature reading from AIDA64.

 

However I did encounter some other issue now:

Previously, when I had done the last post I did have 12 temperature sensors (Temparature #1 through Temperature #12), for some reason I do however only have 5 anymore. I tried restarting the aquacomputer service as well as AIDA 64 several times but the temperature sensors 6 to 12 for some reason will not show up anymore. Even changed the WMI setting back, but no go.

Sensors 1-5 which are still showing up are working fine btw and they are also coming from aquasuite/service as temp#1 is definitely the temperature from the first sensor connected to the aquero. But the reading from the aquastream pump, which previously showed up as temperature 10 (or 11 or 12, not sure)  is now gone. I did manage to create some "virtual sensor" in aquasuite which is calculating temperature differences and by doing 2 differences cancelling each other out I essentially made the "virtual sensor" show the temperature reading from the pump, and this one is "Temperature #3" in AIDA64, so this one is showing up now.

 

Here is another dump with temperature sensors 6 to 12 currently missing (when I had done the dump for the previous post they were still there).

Current dump:

------[ AIDA64 Extreme v5.20.3400 ]------

------[ Microsoft Windows 8.1 Professional 6.3.9600.17736 (64-bit) ]------

------[ Motherboard Info ]------

Motherboard ID      : 63-0100-000001-00101111-080514-Chipset$A1103121_BIOS DATE: 12/17/14 20:18:22 VER: 04.06.05
Motherboard Model   : ASRock Z97 Extreme9
Motherboard Chipset : Intel Wildcat Point Z97, Intel Haswell

DMI MB Manufacturer : ASRock
DMI MB Product      : Z97 Extreme9
DMI MB Version      : 
DMI MB Serial       : E8P-44001400034
DMI SYS Manufacturer: To Be Filled By O.E.M.
DMI SYS Product     : To Be Filled By O.E.M.
DMI SYS Version     : To Be Filled By O.E.M.
DMI SYS Serial      : To Be Filled By O.E.M.
DMI BIOS Version    : P1.30


------[ DevClass / Human Interface Devices ]------

<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c52b&mi_02&col03#8&3abdffa6&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C52B&MI_02&COL03\8&3ABDFFA6&0&0002</INSTANCE><BUSNUM>00000005</BUSNUM><ADDR>00000004</ADDR>
<DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_00&col02#7&297f640&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_00&COL02\7&297F640&0&0001</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000008</ADDR>
<DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_046d&pid_c714&col01#7&1b7abfeb&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C714&COL01\7&1B7ABFEB&0&0000</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c52b&mi_00#8&2eaa4e29&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C52B&MI_00\8&2EAA4E29&0&0000</INSTANCE><BUSNUM>00000003</BUSNUM><ADDR>00000002</ADDR>
<DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_046d&pid_c52b&mi_01&col01#8&16e6c1e4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C52B&MI_01&COL01\8&16E6C1E4&0&0000</INSTANCE><BUSNUM>00000004</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_046d&pid_c714&col02#7&1b7abfeb&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C714&COL02\7&1B7ABFEB&0&0001</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c52b&mi_01&col02#8&16e6c1e4&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C52B&MI_01&COL02\8&16E6C1E4&0&0001</INSTANCE><BUSNUM>00000004</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c714&col03#7&1b7abfeb&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C714&COL03\7&1B7ABFEB&0&0002</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c713#7&d0202c2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C713\7&D0202C2&0&0000</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000002</ADDR>
<DESC>HID-compliant system controller</DESC><DEVPATH>\\?\hid#vid_046d&pid_c52b&mi_01&col03#8&16e6c1e4&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C52B&MI_01&COL03\8&16E6C1E4&0&0002</INSTANCE><BUSNUM>00000004</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant system controller</DESC><DEVPATH>\\?\hid#vid_046d&pid_c714&col04#7&1b7abfeb&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C714&COL04\7&1B7ABFEB&0&0003</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c52b&mi_01&col04#8&16e6c1e4&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C52B&MI_01&COL04\8&16E6C1E4&0&0003</INSTANCE><BUSNUM>00000004</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c714&col05#7&1b7abfeb&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C714&COL05\7&1B7ABFEB&0&0004</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c714&col06#7&1b7abfeb&0&0005#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C714&COL06\7&1B7ABFEB&0&0005</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c714&col07#7&1b7abfeb&0&0006#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C714&COL07\7&1B7ABFEB&0&0006</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000003</ADDR>
<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_01&col01#7&15c8127e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_01&COL01\7&15C8127E&0&0000</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>00000009</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_02#7&28f82ebc&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_02\7&28F82EBC&0&0000</INSTANCE><BUSNUM>00000002</BUSNUM><ADDR>0000000A</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c52b&mi_02&col01#8&3abdffa6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C52B&MI_02&COL01\8&3ABDFFA6&0&0000</INSTANCE><BUSNUM>00000005</BUSNUM><ADDR>00000004</ADDR>
<DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_00&col01#7&297f640&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_00&COL01\7&297F640&0&0000</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000008</ADDR>
<DESC>HID-compliant system controller</DESC><DEVPATH>\\?\hid#vid_0c70&pid_f001&mi_01&col02#7&15c8127e&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_0C70&PID_F001&MI_01&COL02\7&15C8127E&0&0001</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>00000009</ADDR>
<DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c52b&mi_02&col02#8&3abdffa6&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C52B&MI_02&COL02\8&3ABDFFA6&0&0001</INSTANCE><BUSNUM>00000005</BUSNUM><ADDR>00000004</ADDR>

------[ HID Device Info / HID-compliant consumer control device ]------

Manufacturer              : Aqua Computer GmbH & Co. KG
Product                   : aquaero System Control
Serial Number             : 09009-14142
Device ID                 : 0C70-F001
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              : Aqua Computer GmbH & Co. KG
Product                   : aquaero Device
Serial Number             : 09009-14142
Device ID                 : 0C70-F001
Usage                     : 0001h
Usage Page                : FF00h
Input Report Byte Length  : 1038
Output Report Byte Length : 2114
Feature Report Byte Length: 2645

------[ HID Device Info / HID-compliant system controller ]------

Manufacturer              : Aqua Computer GmbH & Co. KG
Product                   : aquaero System Control
Serial Number             : 09009-14142
Device ID                 : 0C70-F001
Usage                     : 0080h
Usage Page                : 0001h
Input Report Byte Length  : 2
Output Report Byte Length : 0
Feature Report Byte Length: 0

------[ Aquaero/Aquaduct Device ]------

Manufacturer               = Aqua Computer GmbH & Co. KG
Product                    = aquaero Device
Serial Number              = 09009-14142
Device ID                  = 0C70-F001
Usage                      = 0001h
Usage Page                 = FF00h
Input Report Byte Length   = 1038
Output Report Byte Length  = 2114
Feature Report Byte Length = 2645

------[ AA5 Input Report ]------

Structure Version  = 1200
Firmware Version   = 2003
Bootloader Version = 102
Hardware Version   = 6000
Device Type        = 2  (Aquaero 5 XT)

0000  0B E4 04 B0  04 B0 23 31  37 3E 07 D3  00 66 17 70  ......#17>...f.p
0010  00 02 9E 8D  00 02 A2 0A  03 00 00 02  00 0F 00 00  ................
0020  00 00 01 0B  E2 AE 48 02  00 00 02 07  00 FF FF 00  ......H.........
0030  07 D5 0F A0  03 DA 00 00  00 00 0C 01  97 CD FF CD  ................
0040  FF D6 FF CD  FF CE FF CD  FF CB FF CD  3C 86 04 19  ............<...
0050  3C 03 00 FB  3E 07 03 E3  A6 2A 00 5A  67 C6 61 25  <...>....*.Zg.a%
0060  6B F2 5C 5E  0B DD 7F FF  7F FF 7F FF  7F FF 7F FF  k.\^............
0070  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  ................
0080  7F FF 7F FF  0D 48 7F FF  7F FF 7F FF  7F FF 7F FF  .....H..........
0090  7F FF 7F FF  0A 48 00 00  7F FF 7F FF  7F FF 0B E1  .....H..........
00A0  7F FF 09 4C  7F FF 7F FF  7F FF 7F FF  0A 48 7F FF  ...L.........H..
00B0  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  0B AD 0B AD  ................
00C0  0A 9D 0A 9D  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  ................
00D0  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  ................
00E0  7F FF 7F FF  00 00 17 19  00 00 15 AD  00 00 35 B8  ..............5.
00F0  00 00 00 00  00 00 00 00  00 00 00 00  7F FF 7F FF  ................
0100  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  01 A5 7F FF  ................
0110  7F FF 7F FF  FF FF 7F FF  7F FF 00 00  00 00 7F FF  ................
0120  FF FF 7F FF  7F FF 00 00  00 00 7F FF  FF FF 7F FF  ................
0130  7F FF 00 00  00 00 7F FF  FF FF 7F FF  7F FF 00 00  ................
0140  00 00 7F FF  7F FF 25 C1  7F FF 7F FF  7F FF 7F FF  ......%.........
0150  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  7F FF 7F FF  ................
0160  7F FF 7F FF  0D AC 01 FD  0E B3 01 B8  00 3A 00 19  .............:..
0170  00 2E 02 1A  0E 50 01 B4  00 00 00 00  00 00 00 D9  .....P..........
0180  0E 90 01 C3  00 3B 00 1A  00 72 00 00  27 10 04 B9  .....;...r..'...
0190  00 00 00 00  00 00 00 00  27 10 00 00  00 00 00 00  ........'.......
01A0  00 00 00 00  27 10 00 00  00 00 00 00  00 00 00 00  ....'...........
01B0  27 10 00 00  00 00 00 00  00 00 00 00  27 10 00 00  '...........'...
01C0  00 00 00 00  00 00 00 00  27 10 00 00  00 00 00 00  ........'.......
01D0  00 00 00 00  27 10 00 00  00 00 00 00  00 00 00 00  ....'...........
01E0  27 10 00 00  00 00 00 00  00 00 00 00  27 10 00 00  '...........'...
01F0  00 00 00 00  00 00 01 00  0B B8 04 C4  02 06 02 FF  ................
0200  FF FF FF FF  FF FF 00 FF  00 00 FF FF  FF FF 00 FF  ................
0210  00 00 FF FF  FF FF 02 FF  00 00 FF FF  FF FF 02 FF  ................
0220  00 00 FF FF  FF FF 00 FF  FF FF FF FF  FF FF 00 FF  ................
0230  FF FF FF FF  FF FF 40 00  00 3F 00 00  00 00 00 00  ......@..?......
0240  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0250  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0260  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0270  00 00 00 00  00 00 00 00  00 00 01 5F  27 10 27 10  ..........._'.'.
0280  27 10 27 10  27 10 27 10  27 10 00 00  00 00 00 00  '.'.'.'.'.......
0290  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
02A0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
02B0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
02C0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
02D0  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 83  ................
02E0  00 95 10 50  27 10 27 10  27 10 27 10  27 10 27 10  ...P'.'.'.'.'.'.
02F0  27 10 27 10  27 10 27 10  27 10 27 10  27 10 00 00  '.'.'.'.'.'.'...
0300  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0310  00 00 00 00  00 00 00 00  00 00 00 00  00 00 27 10  ..............'.
0320  1B 6F 00 00  27 10 00 00  15 43 27 10  00 00 15 43  .o..'....C'....C
0330  27 10 00 00  15 43 00 00  00 00 00 00  00 00 00 00  '....C..........
0340  00 00 00 00  00 00 00 64  01 5F 00 00  00 00 00 00  .......d._......
0350  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
0360  00 00 00 00  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
0370  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
0380  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
0390  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
03A0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
03B0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
03C0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
03D0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
03E0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
03F0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  ................
0400  FF FF FF FF  FF FF FF FF  FF CF 10 96  EF           .............
 

 

Another thing I noticed:

Fan #3 will only show up in Fan Speeds when it is running. This fan (cooling the external Airpley Gigant radiator) usually is at 0 RPM when the system is idle (triggered by water temperature in aquasuite/aquaero) and when it is at 0 RPM AIDA64 will neither show it in the sensor list nor in the tray bar. Only once the fan speed goes to some value greater than zero the fan will start showing up. At least the icon in the tray bar will automatically appear then. And gladly it will not go away after that anymore, unless I restart AIDA64 with the fan at 0 RPM, then it will be gone once again until the fan spins up.

 

So to sum it up, it would be nice if the following things could be added in future AIDA64 versions:

 

* Flow sensors also showing up in "Sensor Icons" for tray bar, not only in LCD items

* Show the fan sensor even if it is at 0 RPM

* Dunno if there is an issue on my side with temperature sensors 6 to 12 not showing up, but if this is some kind of bug it would be nice if it got fixed.

Share this post


Link to post
Share on other sites

Hi.
I use aquaero 4 and mps flow 200. Both are connected through USB to the motherboard.
When aquaero and mps are connected both, in aida64 sensors only these aquaero are displayed.
If to disconnect aquaero and to leave to mps connected to USB only, in aida64 these mps are displayed.
Thanks for high-quality work!

 

 

aquaerodump aquaero4.txt

aquaerodump mps.txt

aquaerodump aquaero4+mps.txt

Share this post


Link to post
Share on other sites

Hi.

I use aquaero 4 and mps flow 200. Both are connected through USB to the motherboard.

When aquaero and mps are connected both, in aida64 sensors only these aquaero are displayed.

If to disconnect aquaero and to leave to mps connected to USB only, in aida64 these mps are displayed.

Thanks for high-quality work!

 

Maybe it only detects it if connected via aquabus to the aquaero if an aquaero is present?

For me it detects the mps flow 100 which is connected via aquabus but not USB, however it will now show up in sensor icons, only in lcd items.

Share this post


Link to post
Share on other sites

Maybe it only detects it if connected via aquabus to the aquaero if an aquaero is present?

For me it detects the mps flow 100 which is connected via aquabus but not USB, however it will now show up in sensor icons, only in lcd items.

 

Aida64 detects both device (it is visible in aquaerodump aquaero4+mps.txt), but shows only these aquaero in "sensors".

Aquabus connection not supported for aquaero4 and mps flow 200 :(

Share this post


Link to post
Share on other sites

* Flow sensors also showing up in "Sensor Icons" for tray bar, not only in LCD items

That's normal. Flow sensors provide such values that are not possible to squeeze into the 2 and a half character space that is provided by sensor icons. You can put percentage values there or temperatures, so a scale of 0 to 199 is fine. But such values like 99.99 or 12.34 will not fit in the tiny (16x16 pixel) tray icons.

 

* Show the fan sensor even if it is at 0 RPM

That's also normal. AIDA64 will not display a stopped fan, since it treats the fan disconnected on that particular fan header in such cases. That is due to a hardware limitation: PC fan headers do not have connection sense logic, so the disconnected state and fan stopped state cannot be distinguished :(

 

* Dunno if there is an issue on my side with temperature sensors 6 to 12 not showing up, but if this is some kind of bug it would be nice if it got fixed.

We've checked the dumps, and it seems for some reason the temperature sensors called "stemp" (soft sensors) are missing from your second registers dump. So the Aquaero unit couldn't pick those temperatures up, hence it's not the fault of AIDA64.

BTW, Aquaero 5 and Aquaero 6 are identical on the firmware, API and software levels, they only differ in hardware properties. Even the firmware provides a device ID that is the same for Aquaero 5 XT and Aquaero 6 XT. That's why AIDA64 identified your device as Aquaero 5 ;)

Share this post


Link to post
Share on other sites

Hi.

I use aquaero 4 and mps flow 200. Both are connected through USB to the motherboard.

When aquaero and mps are connected both, in aida64 sensors only these aquaero are displayed.

If to disconnect aquaero and to leave to mps connected to USB only, in aida64 these mps are displayed.

Thanks for high-quality work!

Thank you for the dumps, the issue will be fixed in the next AIDA64 beta update due in a few days from now.

Share this post


Link to post
Share on other sites

That's normal. Flow sensors provide such values that are not possible to squeeze into the 2 and a half character space that is provided by sensor icons. You can put percentage values there or temperatures, so a scale of 0 to 199 is fine. But such values like 99.99 or 12.34 will not fit in the tiny (16x16 pixel) tray icons.

 

That's also normal. AIDA64 will not display a stopped fan, since it treats the fan disconnected on that particular fan header in such cases. That is due to a hardware limitation: PC fan headers do not have connection sense logic, so the disconnected state and fan stopped state cannot be distinguished :(

 

We've checked the dumps, and it seems for some reason the temperature sensors called "stemp" (soft sensors) are missing from your second registers dump. So the Aquaero unit couldn't pick those temperatures up, hence it's not the fault of AIDA64.

BTW, Aquaero 5 and Aquaero 6 are identical on the firmware, API and software levels, they only differ in hardware properties. Even the firmware provides a device ID that is the same for Aquaero 5 XT and Aquaero 6 XT. That's why AIDA64 identified your device as Aquaero 5 ;)

 

Thanks a lot for the feedback!

 

About the flow sensor icons and the 0 RPM fan:

 

* I don't get the argument about the flow, I have the water level, which in aquasuite is 97.4% and AIDA64 will happily show 97 as sensor icon, why shouldn't it be possible to show my 39.8l/h flow as as 39 or 40? ok people with 200+l/h might run into a display problem but who runs at 200+ l/h? That is completely pointless and even then you could just show a "+" or something as if the flow level if above 200l/h then you are very far from having an issue with too low flow and most likely can live with it if the real display only kicks in below 200l/h. In any case I think it's better than having no icon at all :)

 

* I get that it's probably no point in listing every potential 0 RPM fan if you can't determine whether the fan runs at 0 RPM or whether there is no fan connected at all. However once the fan had some RPM and it has been shown and I actually selected it for display in the tray bar then it would much rather be preferrable if it kept getting listed. I think it's pretty safe to assume that any fan that I actively select for display actually is connected and not a bogus 0 RPM reading. So then I could just spin up all fans for selection, select them, and from then on have them show up even if they are idle. Of course no big deal but better than to not list the fan. If the fan I had selected has an issue and runs with 0 RPM because of the issue I'd much rather see a 0.0 icon in my tray bar then seeing no icon at all.

 

* The issue with the temp sensors 6-12 not showing up.... dunno what's going on there, but as you say it's not in the dump I agree that this looks more likely to be an Aquacomputer issue, maybe with the service. btw after a reboot of the PC now 6 sensors show up with the 6th one being the pump temperature that had been missing before. 7-12 are still gone, but I don't need those anyway.

Share this post


Link to post
Share on other sites

About the flow sensor icons and the 0 RPM fan:

 

* I don't get the argument about the flow, I have the water level, which in aquasuite is 97.4% and AIDA64 will happily show 97 as sensor icon, why shouldn't it be possible to show my 39.8l/h flow as as 39 or 40? ok people with 200+l/h might run into a display problem but who runs at 200+ l/h? That is completely pointless and even then you could just show a "+" or something as if the flow level if above 200l/h then you are very far from having an issue with too low flow and most likely can live with it if the real display only kicks in below 200l/h. In any case I think it's better than having no icon at all :)

The problem is about displaying values beyond 199, for any type of readings, on the sensor icons. Water level is easy, since it's a percentage value, so it can never have a value above 100. But, in case you say it's quite uncommon to have a liquid flow beyond 199 LPH, then it could work as a sensor icon. So we'll add support for flow sensor sensor icons in the next AIDA64 beta update ;)

 

* I get that it's probably no point in listing every potential 0 RPM fan if you can't determine whether the fan runs at 0 RPM or whether there is no fan connected at all. However once the fan had some RPM and it has been shown and I actually selected it for display in the tray bar then it would much rather be preferrable if it kept getting listed. I think it's pretty safe to assume that any fan that I actively select for display actually is connected and not a bogus 0 RPM reading. So then I could just spin up all fans for selection, select them, and from then on have them show up even if they are idle. Of course no big deal but better than to not list the fan. If the fan I had selected has an issue and runs with 0 RPM because of the issue I'd much rather see a 0.0 icon in my tray bar then seeing no icon at all.

There are quite a few issues with displaying stopped fans or 0 RPM readings. AIDA64 by default has a set of sensor icons and OSD items enabled, including CPU fan. In case a user enables the sensor icons or OSD Panel feature, and doesn't touch the selected items, then displaying a 0RPM reading for a disconnected fan may cause confusion when for example the CPU fan is connected to another fan header, or the CPU fan cannot be measured. The current solution is the best we could come up, this is the solution that suits both inexperienced and skilled users. It may still not be perfect, but for power-users we usually recommend SensorPanel and LCD over sensor icons and OSD Panel anyway, since those modules offer way more flexibility to satisfy special needs ;)

Share this post


Link to post
Share on other sites

The problem is about displaying values beyond 199, for any type of readings, on the sensor icons. Water level is easy, since it's a percentage value, so it can never have a value above 100. But, in case you say it's quite uncommon to have a liquid flow beyond 199 LPH, then it could work as a sensor icon. So we'll add support for flow sensor sensor icons in the next AIDA64 beta update ;)

 

Thanks that's great!

There probably are some people that are running setups with 200+ l/h but even the hardcore high flow people say it's pretty pointless running over 200 l/h with temperature improvements barely being measurable above that. Most people try to have a minimum of 40 or 60 l/h which should be sufficient for most scenarios if you're not trying to break some cooling or overclocking world record. So a 199 l/h display limit should really be fine for the overwhelming majority of users.

 

There are quite a few issues with displaying stopped fans or 0 RPM readings. AIDA64 by default has a set of sensor icons and OSD items enabled, including CPU fan. In case a user enables the sensor icons or OSD Panel feature, and doesn't touch the selected items, then displaying a 0RPM reading for a disconnected fan may cause confusion when for example the CPU fan is connected to another fan header, or the CPU fan cannot be measured. The current solution is the best we could come up, this is the solution that suits both inexperienced and skilled users. It may still not be perfect, but for power-users we usually recommend SensorPanel and LCD over sensor icons and OSD Panel anyway, since those modules offer way more flexibility to satisfy special needs ;)

I get you don't want to show a CPU fan with 0 RPM if it really is not connected, but if I have selected this CPU fan for display in the tray bar wouldn't I want to keep showing the fan reading then? 

 

Example:

 

Fan 3 is at 0 RPM, the list (Hardware Monitoring/Sensor Icons) shows:

Fan1

Fan2

-> Fan3 not shown, because you don't want to list 100 fans that are probably not even connected, which I get and which is fine.

 

Now I spin up Fan3 to 500 RPM, and the list shows:

Fan1

Fan2

Fan3

-> Fan3 appearing in the list now

 

Now I select Fan3 for display in tray bar.

-> Fan3 shows up in tray bar with '0.5'

 

The I spin down the fan:

-> Fan3 shows up in tray bar with '0.0'

 

Now I restart AIDA64 (eg if I restart the PC due to a Windows update):

-> Now Fan3 is not showing up anymore in tray bar nor in the list unless I spin it up once again :(

 

-> I get you don't want to list all fans in step #1 and I agree with that but I think after I have selected the fan for display in step #2 it should keep showing up even after a restart of AIDA64 and even if the fan is at 0 RPM. Because if I have selected a fan for display I think it's safe to assume that I haven't selected a bogus fan.

Share this post


Link to post
Share on other sites

Look, I completely understand your issue, but I suppose you didn't understand the issue about default behavior of the sensor icons when AIDA64 sensor icons weren't configured before. Please read my previous post again, and I hope you will understand the problem behind this whole thing.

Share this post


Link to post
Share on other sites

Look, I completely understand your issue, but I suppose you didn't understand the issue about default behavior of the sensor icons when AIDA64 sensor icons weren't configured before. Please read my previous post again, and I hope you will understand the problem behind this whole thing.

 

Nope sorry I do not understand the argument. You want to enable less advanced users to be able to use the sensor icons without having to select sensor icons from the list if I understood that correctly. I guess that is also fine.

 

I do however not get how this relates in any way to what I was describing, which is actively selecting a specific fan for display (which the less advanced user isn't even doing if I understood your argument correctly) and then sticking to displaying it no matter what. I am not asking to automatically show 0 RPM fans in the tray bar nor even listing them in the list, but only to stick to listing and showing a fan if I have actively slected it in the past (which also means the very same fan MUST have been at > 0 RPM in the past, otherwise I couldn't have selected it).

 

I don't understand the issue a less advanced user could have with that if he doesn't even tick any fans for display and I am not sure how this could be an issue programmatically either, in pseudo code this can't be more than changing

 

if RPM > 0 then display = true

to

if RPM > 0 or HasBeenActivatedByUser = 1 then display = true

 

And you already must have data for both variables, RPM you obviously have, and the setting for "HasBeenAcivetedByUser" you also must have, as whenever I spin up the fan it reappears in the list, and it reappears being ticked if I had ticked it before, so AIDA64 must have this data stored already and know which sensor is which, otherwise it couldn't automatically be ticked already when it reappears in the list whenever I spin up the fan.

 

I'm sorry if my arguments are a bit annoying  :)

But why a tool (and generally it is a very great tool!) that has the main purpose of monitoring hardware would actively hide one of the most critical issues that could happen, which is when a fan that a previous point of time must have been working now isn't working anymore - that is one of THE most important things I would want a hardware minitor to show, and exactly this is being hidden.  :(

Share this post


Link to post
Share on other sites

That's actually a much more complicated issue than the 2 lines of "if ... then" sequence you've mentioned. AIDA64 always tries to handle things automatically, so that the user wouldn't have to worry about every single bits of configuration. When you start AIDA64 without previously altering the Preferences settings, it will automatically tick (enable) a pre-defined list of sensor icons. Since those are a pre-defined list, the items on the list may or may not be supported by the current system. For example, it will enable CPU Fan, System Fan, Chipset Fan, Chassis Fan, etc. And since it's not possible to know which items do exist on the current system, AIDA64 automatically will hide the ones that provide an invalid reading, like 0 RPM, negative RPM or excessively high (unrealistic) RPM like 60000 RPM. That logic assures that only the actually valid items from the pre-defined list would appear automatically on the System Tray as sensor icons.

And when I say "it will automatically tick" a certain list of sensor icons, it means it sets their SHOW property to 1 (enabled). It is the same property that you can alter by ticking the checkbox next to a sensor icon in the Preferences. So there's no separate property for "automatically ticked" and "ticked by the user". On a typical system the enabled list of sensor icons is much longer than the ones that actually get shown on the System Tray. You can open the AIDA64.INI file, and in there you can see that a lot of sensor icons (incl. many fan readouts) are enabled automatically, but they are not shown on your system simply because those fan headers do not exist or they provide a 0 RPM reading. Of course as soon as any of them start to provide a meaningful readout, the sensor icon will immediately appear on the System Tray -- and will not disappear until you restart AIDA64.

Another problem with the behavior about stopped fans and invalid readings is that some users prefer to have the sensor icon (or OSD Panel, LCD, etc) items hidden in such cases, while others would still want to watch them show the invalid reading. And in many cases it's not easy to decide what an invalid reading actually is :) The hardware monitoring module of AIDA64 is very sophisticated, but your example shows that no matter how much we try to improve it, it still cannot satisfy every single specific and unique needs ;) And when I say unique, I really mean that. The sensor icons module works the way it does now for many years, and noone complained about the 0 RPM fans issue before.

And quite frankly, I have to disagree with you on the "critical" issue of stopped fans. While it is a critical issue, I don't think a user would quickly and easily notice that a fan stopped by looking at tiny 16x16 pixel System Tray icons. Unless of course you only use just one sensor icon, and you constantly watch the System Tray area for icon text changes :) I don't think in practice anyone would rely on the tiny sensor icons for critical system readouts. Typically, you would configure the Alerting facilty of AIDA64 to warn you about fan issues or overheating situations.

Share this post


Link to post
Share on other sites

Maybe a new optional setting "always show all sensor readings" would make all parties happy?

I, too, have the same problem as Dschidi, btw, if you remember... :)

Share this post


Link to post
Share on other sites

Hi Guys,

 

Love what you've done with support for Aquaero and Corsair AXi PSU's!

 

Im just converting over from LCDhost to Arx with Aida. You've made it a lot simpler than it used to be to get all the sensor data! I had to make batch files and custom configurations and XML parsing to get the data into LCDHost. Well done making it this simple!

 

The interface and configurability of sensors for Arx is great, not as completely customisable and with the range of plugins for LCDHost, but it's still pretty powerful.   There is a couple additional things I'd like to add to the wish list!

 

The ability to set images, text or sounds to be triggered for events, such as over temp, under speed, under flow etc for critical events and alarms.

And support for Alarm events from the Aquaero.

 

Im about to put my PC away out of sight and (earshot) to create a quiet room and would like to have a completely wireless setup including, keyboard, mouse, and monitoring with Arx on tablet. (The PC screen will be in a multi-use room mounted to a wall behind a retractable projection screen with either a desk on wheels that I'll wheel from the side of the room infront when using the PC screen (55" 4K OLED) or the desk will slide/flip out from the wall when the projection screen is up.

 

 

I've attached below my draft progress moving over to Arx on a 8" tablet and the original LCDHost configuration so you can see where Im going with this.  With LCDHost I was able to set Aquaero alarms to trigger pop-up text and play sounds. Ive attached an example from a very old configuration. 

The mini icons on LCDHost also update based on thresholds for a quick view of any issues. If you could some how replicate this with the ability to trigger alerts from sensor readings and display text or images it would be wonderful! :)

LCDHost on G19

23856526309_4899895069_o.pngscreenshot-09 by Hilton, on Flickr

Draft layout of Arx on 8" tablet

24141765051_bd8197e942_o.pngaida64-arx-screenshot by Hilton, on Flickr

old Pop up Alarm example on G19 for GPU Pump 2 failure

23928789870_3007b6f63f_o.pngscreenshot-17 by Hilton, on Flickr

Here's how conditional formatting works in LCDHost. (Bottom right panel - click for full-size image)

23598906573_40fb14755b_c.jpgConditional Formatting - images by Hilton, on Flickr

In case you're wondering what on earth this is all for....

23857195139_5ff38b0db2_c.jpgIMG_4135 by Hilton, on Flickr

23857196609_a05c0eb013_c.jpgIMG_4129 by Hilton, on Flickr

24116970442_63a9ee40a7_c.jpgIMG_4115 by Hilton, on Flickr

23598213243_24273b4876_c.jpgIMG_4112 by Hilton, on Flickr

Share this post


Link to post
Share on other sites

Wow, what a beast you've got :D Very nice.

As for your ideas, we'll have to think about them. We do not want to over-complicate the existing hardware monitoring module of AIDA64. But maybe we can find a way to make it even more customizable than now, without making it look as freaking busy as an airplane dash :)

Share this post


Link to post
Share on other sites

Thanks!

You already have the alert module. Maybe you can leverage the existing alert configuration by providing an option in the LCD configuration page to link to an alert from the alerts that have been set to trigger an image, or text state change for an LCD item. Ill mock up an example.

PS. If you have a mega dollar investment in your PC (or whatever your PC is monitoring) you'd want to know if there was a problem too. ;) (hence the comprehensive dashboard)

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...

  • Similar Content

    • By Grestorn
      Aquacomputer updated their Aquasuite the other day. With that update, they also updated the firmware of many of their hardware components, including the D5 Next to version 1014.
      Since that update, AIDA64 doesn't see the D5 Next's values anymore. 
      HWInfo still sees them, though, so the export must work technically, there seems to be some misalignment between AIDA64 and the D5 Next. 
      Other values of Aquacomputer's components are still showing up fine, only the D5 Next is affected (on my system). 
       
      In that regard, I'd still very much appreciate if it would be possible, to restrict the polling of all Aquacomputer's components, as this keeps stalling all other values in AIDA64, too. Aquacomputer seems to limit the polling to once a second, and for some reason that has the effect that all other components monitored by AIDA64 are also restricted to once a second, as soon as there are AC components in the system. 
      And I also remember that there was a checkbox on the "Stability" tab where you could disable the AC's components polling, but that's missing now for some reason?
       
      /edit: Added the Sensor Dump File!
      aquacomputerdump.txt
    • By Buelldozer32
      Hello everyone, 
      After reading a lot of post I still didn't find a solution for my problem.
      I have An Aquaero 5 XT with a D5 pump and a MPS sensor connect with Aquabus. I cannot get the MPS pressure nor the pump speed when they are connected on the Aquabus. If I connect them with USB, it works well and I have both datas in Aida64.
      Does anyone have an idea to help me?
      Regards
      Florian
    • By Pak1979
      Is it possible to make the virtual flow sensor for the AquaComputer D5 Next readable with Aida64? All other sensors of the D5 Next are already readable. Only the Flow is not aviable.
    • By Dav'
      Hi,
      Since last update from Aquacomputer AIDA can read aquaero values but no more MPS values.
      As you can see on screenshot HWiNFO can read it.
      Regards.

    • By Fiery
      The latest AIDA64 update introduces wireless remote monitoring of sensor values on smartphones and tablets via RemoteSensor and Logitech Arx Control. It also provides detailed information on system certificates, and supports Aquaero and Aquaduct sensor devices.

      New features & improvements
      - RemoteSensor smartphone and tablet LCD integration
      - Logitech Arx Control smartphone and tablet LCD integration
      - System certificates information
      - Support for Gravitech, LCD Smartie Hardware, Leo Bodnar LCD devices
      - Microsoft Windows 10 Technical Preview Build 9888 support
      - Improved support for Intel "Skylake" CPU
      - Preliminary support for Intel "Braswell" SoC
      - Aquaero and Aquaduct sensor devices support
      - Improved support for Crucial SSDs

      What's new since AIDA64 v4.00
      - Microsoft Windows 10 Technical Preview and Windows Server 2015 Technical Preview support
      - Microsoft Windows 8.1 Update 1 and Windows Server 2012 R2 Update 1 support
      - OpenCL GPGPU Benchmark Suite
      - AMD Mantle graphics accelerator diagnostics
      - Multi-threaded memory stress test with SSE, SSE2, AVX, AVX2, FMA, BMI and BMI2 acceleration
      - Optimized 64-bit benchmarks for AMD “Kaveri”, “Bald Eagle”, “Mullins”, “Beema” APUs
      - Optimized 64-bit benchmarks for Intel Atom C2000 “Avoton” and “Rangeley” SoC
      - Optimized 64-bit benchmarks for Intel “Bay Trail” desktop, mobile and tablet SoC
      - Full support for the upcoming Intel “Haswell Refresh” platform with Intel “Wildcat Point” PCH
      - Support for 47 new LCD and VFD devices
      - Improved support for Intel “Broadwell” CPU
      - Preliminary support for AMD “Carrizo” and “Toronto” APUs
      - Preliminary support for Intel Quark X1000 “Clanton” SoC
      - Preliminary support for Intel “Skylake”, “Cherry Trail”, “Denverton” CPUs
      - Improved support for Intel “Haswell-E” CPU and DDR4 memory modules
      - Support for DDR4 XMP 2.0 memory profiles
      - Intel H97 and Z97 chipset based motherboards support
      - LGA2011-v3 motherboards support
      - Socket AM1 motherboards support
      - SMTP SSL support
      - Improved handling of XSL files
      - Revamped Direct3D Compute Shader devices enumeration
      - CUDA 6.5, OpenGL 4.5, OpenGL ES 3.1 support
      - Improved support for OpenCL 2.0
      - Support for VirtualBox v4.3 and VMware Workstation v10
      - AData SP610, AData SP910, A-Data SP920, Corsair Force LX, Corsair Neutron, Corsair Neutron GTX, Crucial M550, Intel 730, OCZ Arc 100, OCZ Vector 150, OCZ Vertex 460, Plextor M6M, Plextor M6S, Samsung 845DC Evo, Samsung 850 Pro, Samsung XP941, SanDisk Extreme Pro, SanDisk X300s, Seagate 600 SSD support
      - GPU details for AMD Radeon R5, R7, R9 Series
      - GPU details for nVIDIA GeForce 700, 800, 900 Series
      [ Press Release (English) ]
      [ Press Release (Deutsch) ]
      [ Press Release (italiano) ]
      [ Press Release (magyar) ]
      [ What's new in AIDA64 v5.00 ]
      [ Download ]
×
×
  • Create New...