BenH

I installed PowerChute Professional 10.0.5 for my APC SMT1500 connected to my ASUS TUF FA617NS laptop using USB (also have a NMC2 AP9630 installed). I have checked Power Managment in AIDA64 and it does display the information for the SmartUPS 1500. However, when adding LCD items, only the battery information for the ASUS laptop is available. HID UPS sensor support is enabled under preferences -> stability. LCD Items Available: System Battery level Battery Wear level Battery Estimated Battery Time Power State Voltage Battery Power Values Battery Charge Rate I had this working years ago on my desktop so I do not remember if I had to do anything special. I have also included the battery dump text file along with screenshots of the issue. Also, not sure if having PowerChute Professional installed on my laptop would effect the ASUS battery or AMD MUX for switching between the RX7600s and the Integrated graphics in the Ryzen. I have not noticed any issues yet... I did have PowerChute Serial shutdown installed, but it was super limited compared to PowerChute Business edition (found 10.0.5 from NEC Japan which is probably the last release). Serial Shutdown also would not permit leaving the NMC username/password as the default...maybe my dog will hack my SmartUPS. LOL battdump.txt

As I suspected, thank you Fiery.

Setting up a sensor panel for this laptop, that I just picked up, and the iGPU is the only one detected by AIDA64 for sensors. I went into preferences and enabled "Wake GPUs up at AIDA64 startup" and restarted AIDA64 with no luck. The AIDA64 GPGPU Benchmark detects it fine along with GPU-Z. I also tried starting up AIDA64 with GPU-Z PCIe render test active to see if that would resolve it which it did not. I am on an older version of AIDA64, 6.85.6300 which is the end of my Maintenance window for my registration and wanted to verify if this is functioning correctly in the newer version. This laptop does have Armoury Crate if that makes a difference. Laptop Specs: Ryzen 7 7735HS (iGPU) Radeon RX 7600S (dGPU)

It's funny how I posted how to fix this back in 2018. No response on my post and still has not been fixed...

With multiple network adapters and/or multiple IP addresses, AIDA64 may not show the proper IP Address. It all depends on the index that is assigned to the adapter when it is installed. Windows does have a Metric value at the TCP/IP layer for signifying priority. A possible fix for this is to get all IP available addresses with their Metrics and sort by the Metric value (smaller value has higher priority with Metric 1 being the highest). With this change, the user would then be able to specify which IP Address is primary (The one with the highest Metric). I noticed this issue by having my LAN NIC and a VirtualBox Host-Only NIC in my system. Windows reports the IP for the VirtualBox NIC as my Primary IP Address which is wrong. If I disable the VirtualBox NIC, then Primary IP Address displays correctly. I suspect AIDA64 is only getting the Primary IP Address using a single Windows API call. If this is the case, then this is lazy coding on Microsoft's part.