Fiery

In the past few weeks we've been working closely with Logitech developers to make this happen. Super nice guys, great professionals working there BTW. So, here's the first AIDA64 beta to implement Logitech Arx smartphone and tablet LCD integration: http://www.aida64.com/downloads/latesta64xebeta You can activate it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / Logitech Arx. Once you activated it, the AIDA64 applet will appear in the Arx app's bottom row of icons. Tap on the AIDA64 icon, and the AIDA64 splash screen should be displayed on your mobile device. It will provide you with information on the resolution that you need to use to get the most out of the LCD layout designer. On iOS devices the default setting should be close to the actual value to use, while on Android it may not match at all, so you need to change both the width and height. Please note that the Preview Resolution usually will not match the native screen resolution of your device. It's not a problem at all, and that discrepancy is due to the Arx app using an embedded web view. Hence, AIDA64 and other Arx-ready software will need to render a HTML page, and the Arx framework will display that on your mobile device. And the embedded web view has its own ideas on how to manage the pixels of your screen, so don't be surprised that e.g. an iPhone 5 would report a Preview Resolution of 980 x 1140 pixels After the Preview Resolution is updated on the AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD page, you can use the same LCD layout designer that you would use for other LCD devices or the SensorPanel. On phone devices you can use a wider and/or taller LCD Preview Resolution than what your phone supports. So effectively you can have a much larger space to drop sensor readings on, and use scrolling to move around the big virtual "desktop" on your phone. Known issues and limitations: 1) Graphs and gauges are not implemented yet. We're planning to add them in the next few weeks. 2) The current Android Arx app (Version 172) may not display the AIDA64 applet properly, but instead throw an error message that is almost impossible to read, due to an unfortunate choice of colour scheme by the Arx app. If that happens, just kill the Android app, and start it again. Logitech is already working on a fix. 3) The current Android Arx app (Version 172) will not update the AIDA64 applet when the LCD layout is changed in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / LCD Items. After applying a change on the layout, you need to switch to another Arx applet and then switch back to the AIDA64 applet. Logitech is already working on a fix. 4) Both the iOS and Android Arx app supports screen orientation change only on tablet devices, and page scrolling only on phone devices. We've notified Logitech about this pecularity, but we're not sure in which way would they remedy this. BTW, if you've got no Logitech Gaming hardware and so you cannot use Arx, check out the new RemoteSensor feature: http://forums.aida64.com/topic/2636-aida64-web-server-lcd-for-smartphones-and-tablets/ Please let us know how it works on your mobile devices Thanks, Fiery

Thank you for the bug report. Both issues will be fixed in the next AIDA64 beta update due in a few days from now. I'll drop a message into this topic once the new beta is available for download. Regards, Fiery

ISA in this case refers to the ISA Sensor Dump of AIDA64.

Thank you for the dump. I'm afraid the missing values are only available via EC indexed register access. And performing such register access is quite dangerous, it could easily collide with Asus AI Suite or the BIOS, and would cause a BSoD or system lockup. So it's best not to risk that. If it's possible, try connecting the Extension Fans to other fan headers.

I'm not sure how big are you looking for. LCDInfo makes gorgeous 4.3-inch colour TFT with very fast update rate: http://www.lcdinfo.com/products/usbd480-wq43.html The only problem is, that's an OEM device, so it has no frame or stand. You can integrate it into your case side or front though, and it would make a terrific addition to your existing chassis. If you're looking for even bigger external displays, then your only option is either going for a DisplayLink USB connected LCD monitor, e.g. Mimo 720S ... http://www.mimomonitors.com/products/mimo-720-s ... or Samsung SPF digital photo frames: http://forums.aida64.com/topic/2424-new-lcd-device-support-samsung-spf-digital-photo-frames/ DisplayLink monitors have a huge advantage that they can be used as a classic secondary display under Windows, so you can display any windows, and use any software on them. Samsung SPF DPFs on the other hand can be picked up at reasonable prices at eBay for example. If you go for Samsung SPF, then make sure to use our own drivers for it. Regards, Fiery

Few years ago PNG completely replaced GIF as a still image format, and AIDA64 already supports PNG as well as JPEG. As for animated images/clips, they cannot be put on the SensorPanel or LCD anyway, so it's not a matter of the media format. Regards, Fiery

That's normal for modern AMD processors. Their core diode only provides a meaningful readout when the processor is under load. Regards, Fiery

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic. Thanks, Fiery

The only thing that may cause such issues is when HDD/SSD drives report an incorrect (or unstable) temperature readout. When a certain temperature readout crosses the predefined limits, like they report 1000 Celsius, AIDA64 will remove the readout from the OSD Panel. What sort of SATA controller do you have your drives connected to? Do you use a RAID array? What kind of Windows do you have installed? Regards, Fiery

It should be the CPU VRM voltage. But it's only available on Haswell CPUs. Regards, Fiery

Fan RPM speeds disappear from the Sensor page when they fall to zero, that's normal. It is done because many sensor chips feature 5 or more fan speed tachometers, but most motherboards will not use all of them, and users will usually just use 1 or 2 out of those actually. And it wouldn't make much sense to show a lot of stopped fans when actually just a few of those are actually connected. Sadly, sensor chips are not capable of telling monitoring software which fan tachometer input actually has a connected fan. There's no contact or pressure sensor built into fan headers to indicate that the fan header is currently utilized/connected While on the other hand, when you build your SensorPanel, you will not drop such fan speed readings on your panel that are not connected, so it's vital to see not spinning fans there, and not hide them. I know that sometimes the logic AIDA64 uses about hardware monitoring may sound twisted or not logical at all, but usually it's just designed that way to ensure a great user experience.

1) Turbo Boost may not be able to shoot up to the highest multiplier because of the activities AIDA64 does when measuring sensor values, incl. CPU multiplier and BCLK. Intel's own utility (XTU) may use special tricks to indicate such Turbo spikes, simply because it makes their product work at a higher speed. 2) On modern processors BCLK (FSB) measurement can only be as accurate as APIC timer measurement allows it. In case APIC timer reflects an unstable or too low value, clock speeds measured by AIDA64 and similar monitoring software will suffer. We cannot really do much about that issue, it's simply out of our control Regards, Fiery

The problem with putting GPU Bus Type to a graph or just display it as a single value is that it is simply not possible Since GPU Bus Type holds up to 5 information bits in a single string: bus type (e.g. PCI Express), supported PCIe generation (speed), supported PCIe link width, current PCIe generation, current PCIe link width.

It sounds doable, we'll work on it

PSU information is only available for Gigabyte Odin PSUs. For the rest, yes, AIDA64 provides detailed information on all of those components. Regards, Fiery

Do you mean you would prefer to purchase AIDA64 on a physical media? Or that you want to copy AIDA64 to your media and use it from there as a portable software?

No, they're all unsupported. Out of those picture frames that you can pick up from a store, only Samsung SPF is supported. It is a limitation of the DPF devices, they aren't designed to handle such tasks... BTW, if you're US based, check out eBay. From time to time you can find a Samsung SPF device there for a great price.

Only Samsung SPF and AX206-based hacked firmware DPF devices can be used with AIDA64. Most DPFs do not support sending images on-the-fly (without copying them to the DPF's flash memory) over the USB connection.

Please let us know what exactly the problem is about the serial number detection. What is the expected serial number, and what does AIDA64 show? And if possible, please use English. Regards, Fiery

We haven't yet found a way to have a window like SensorPanel shown in Aero Peek

Unfortunately controlling fans, especially if you wanna do it "right", would take a lot of efforts and resources on our part. And if you fail to configure it properly, quite dangerous things could happen that might just destroy some of your hardware It's not something we'd like to deal with in the near future. We do however allocate even more resources on improving the monitoring capabilities of AIDA64 next year.

It is possible. What you have to do is set proper values for Min, Limit 1, Limit 2 and Limit 3, and set a too low value for Max. The only trick is that Max has to be higher than Min. So for example, for a CPU fan you can set the following values to have a full bar that changes colour depending on the value limits: Min = 0 Limit 1 = 1000 Limit 2 = 3000 Limit 3 = 5000 Max = 1

We've tested it with RTSS, and GPU Bus Type appeared on the OSD properly. Can you have other values displayed properly, or no AIDA64 values appear on the Rivatuner OSD?

You can already use the Aquaero sensor module in the latest AIDA64 Extreme beta update: http://www.aida64.com/downloads/latesta64xebeta

That's fine of course, but the problem in your case is that your fan registers seem to report a zero current even when they're spinning. At least that's what I can see on the Alarm Level related screen shot of yours. Most of the items are already on the SensorPanel. The ones missing are the Pressure, Water Quality, UpTime and Total UpTime. As for the zero fan speed, it will of course be indicated as a zero value on the graphs, as expected.