Fiery

I don't know how those devices can interact with each other. As long as you can have a device that provides the readings via a meaningful way to AIDA64, it will display the measurements. AIDA64 does support Corsair Commander Pro, just keep in mind that iCUE (Corsair's monitoring software) and 3rd party monitoring applications don't play well together due to Corsair's decision on not supporting the industry standard synchronization mutexes that would prevent collisions.

No idea, sorry

I don't think so, since motherboard fan headers are designed to measure the RPM of fans and not the temperature of a fan or something else. Unless of course the thermal diode is designed in a way to let you connect it to a fan header and it provides thermal readings as e.g. 2345 RPM = 23.45 Celsius or so.

Quite frankly, I don't know any IoT users personally, so I cannot gauge the generic approach or requirements of IoT users. And because of that I cannot really allocate developer resources on a complicated project where we haven't yet seen a big demand for MQTT support. You can however come up with your own library, publish it on GitHub or your own website, we can implement support for it in AIDA64 (as well as linking to your website), and it could drive more exposure to your page/website as well as satisfy those IoT users who're hungry for a MQTT sensor solution.

We try to avoid writing dynamic data periodically into files, since many computers these days are equipped with a SSD drive. Wearing it down by writing a file constantly (like once or twice a second) is a bad idea. You can however use any of the existing 3 methods that AIDA64 offers to export the sensor readings for post-processing by a library or another software. Just check AIDA64 / main menu / File / Preferences / Hardware Monitoring / External Applications. Out of the 3 options there we recommend going for Shared Memory, since it's the most efficient way.

AIDA64 uses the standard Asus WMI ACPI interface that has a known issue in a few BIOS versions on AM4 motherboards. You need to wait for Asus to fix this bug in the BIOS of your motherboard.

I'm afraid we have no information on the register index of the flow rate reading on D5 Next. In other words, we don't know how to measure that value right now. If you can help us a bit about that, we _may_ be able to figure it out though, so it's not a lost cause Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Aquaero 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. Also, check what Aquasuite reports as flow rate for your D5 Next device. The value should fluctuate a bit, in which case please let us know a few examples of readings. We'll do our best to try and find the reading among the D5 Next registers that are shown in the Aquaero Dump. Thanks, Fiery

AMD processors have no per-core thermal diodes, so it's normal.

I really don't know... Because we have done everything we could: talked to both the management and the right technical professionals at Corsair who understands the issue in depth. And when I say "we", it's not only us here at FinalWire, but also the other folks behind CPU-Z, HWiNFO, HWMonitor and SIV. I think the only way that may work is when multiple (10+, maybe 100+) inquiries to be submitted to Corsair customer support. That should trigger someone from middle management to dig deeper and think about the issue thoroughly.

Are you using the latest version of AIDA64, v6.10? Can you please copy the OS Version line of the Operating System / Operating System page of AIDA64 to the Clipboard and paste it here? So we can check the full version+build of your OS installation.

Since the difference is about eight-fold (8x), maybe you're mixing up MB/s (MegaBytes/sec) and Mbps (Megabits/sec) ? A network that can push 100 Megabits/sec can actually transfer 1/8 of that in MegaBytes/sec, so 12 MegaBytes/sec. BTW, you can enter a unit for the NIC download/upload rate items as "Mbps" to have Megabits/sec as the result.

Thank you for the info. We will fix the issue in the next AIDA64 beta update. Meanwhile, I've sent you a download link (in private message) for a special beta build that you can try now.

We don't have a list of compatible devices with the RGB LED features, mostly because it's so diverse and complicated that it's not really possible to compile a list. It's because e.g. with Corsair and Razer there's a SDK that potentially supports a wide range of devices and even future devices. With other modules it's still not in a final stage and the manufacturer doesn't guarantee that it would work for a wide range of RGB devices. So it's best if we go by a case by case basis. As for your system, ASRock motherboards in general are not supported by the RGB LED module, because only Asus motherboards are supported via the Aura LED SDK. Razer is easy, since the Razer Chroma SDK supports virtually any Razer device out there, and certainly all Razer keyboards and mice. Only Asus video cards are supported via the Aura LED SDK. RGB fans and controlling the RGB LED portion of liquid coolers are not supported right now. Since our RGB LED features are designed to reflect the state of a hardware component or a sensor reading, we do not push for implementing support for such devices that are not easily visible for most users. We believe peripherals are the best candidates to reflect e.g. high system temperature by changing their LED colour, so that's why -- in general -- the AIDA64 RGB LED module supports keyboards, mice, mousepads and headset stands.

It seems high, but in case your computer is stable, you have nothing to worry about.

We'll do our best. Does it work with 90 degrees and 180 degrees rotation?

The mentioned new AIDA64 update is now out, as the v6.10 stable update: https://forums.aida64.com/topic/5213-aida64-v610-is-out/

The mentioned new AIDA64 update is now out, as the v6.10 stable update:

The new AIDA64 release implements AVX optimized benchmarks for Zhaoxin processors, adds PCIe 4.0 and NVMe 1.4 devices support, monitoring of sensor values on Matrix Orbital EVE3 displays, and supports the latest AMD and Intel CPU platforms as well as the new graphics and GPGPU computing technologies by both AMD and nVIDIA. New features & improvements - AVX accelerated 64-bit benchmarks for Zhaoxin ZX-C+ and Zhaoxin KaiXian KX-5000 processors - Full support for Hygon C86 “Mukti/Dhyana” CPU - Enhanced RGB LED monitoring module - Matrix Orbital EVE3 LCD display support - Improved support for Intel “Comet Lake” and “Ice Lake” CPUs - Support for PCI Express 4.0 controllers and devices - Preliminary support for Zhaoxin KaiXian KX-6000 CPU - Advanced support for LSI RAID controllers - NVMe 1.4 support - Improvements for AMD X570 chipset based motherboards - GPU details for AMD Radeon RX 5700 Series - GPU details for nVIDIA GeForce RTX 2000 Super Series What's new since AIDA64 v6.00 - SHA3-512 cryptographic hash benchmark utilizing AVX, AVX2 and AVX-512 - AVX2 and FMA accelerated 64-bit benchmarks for AMD Zen 2 “Matisse” processors - Microsoft Windows 10 May 2019 Update support - BeadaPanel LCD and SteelSeries Rival 710 OLED display support - Corsair H100i Platinum and H115i Platinum liquid cooler sensor support - Cooler Master MP750 RGB LED mousepad support - Corsair Obsidian 1000D, EVGA iCX2, Farbwerk 360, NZXT GRID+ V3 sensor support - Preliminary support for Intel “Comet Lake” CPU - GPU details for AMD Radeon VII - GPU details for nVIDIA GeForce GTX 1600 and GeForce RTX 2060 Series - Preliminary support for AMD “Navi” GPUs - Retired SHA1 and VP8 benchmarks [ Press Release (English) ] [ Press Release (Deutsch) ] [ Press Release (magyar) ] [ What's new in AIDA64 v6.10 ] [ Download ]

Thanks, we'll add that monitor too. The next AIDA64 update should be out tomorrow

It's not few minutes. At least not if you do it properly.

We'll add the requested new option to the Preferences / Stability page in the next AIDA64 update due in a few days from now.

Please give us a few days to implement that.

The first one lacks the necessary information to detect it properly, but we'll add the second one in the next AIDA64 update due in a day or two.

This is a collision between AIDA64 and iCUE. Please report this issue to Corsair. We've been in contact with them for over a decade now, but this is the only issue where we cannot convince them to fix their software. AIDA64 -- as well as many other 3rd party monitoring applications including CoreTemp, CPU-Z, GPU-Z, HWiNFO, HWMonitor, MSI Afterburner, Rivatuner, SIV, SpeedFan, etc -- use industry standard synchronization mutexes in order to prevent such collisions when multiple monitoring software is trying to interact with the same hardware. This works great as long as you use two or more of the mentioned software concurrently. We've got to the point of convincing Corsair to implement a synchronization mechanism in their previous generation software (Corsair Link Software), but then at a certain point they simply removed the mutex and never implemented in iCUE. It means iCUE cannot be used concurrently with 3rd party monitoring applications which is simply unacceptable IMHO. No matter how much pressure us and the developers of the previously mentioned 3rd party monitoring software put on Corsair, they stick to their stance on this matter. Only you, the customers of Corsair and owners of Corsair hardware have a chance to convince Corsair to change their mind.

I've sent you a private message about this issue.