Leaderboard

Razer beat

There must be something wrong about the OpenCL software stack. Try to uninstall and reinstall ForceWare.

New Text Version, uses on Desktop > text_v2.sensorpanel Adapted to 5 Inch Dispaly with 800x480 Pixels > PiDisplay.sensorpanel PiDisplay.sensorpanel text_v2.sensorpanel

Hi, Aida64 now provides support for the Odospace Remote Panel app: Reuse your old android device to display sensor values of a Windows PC. A WiFi connection is not (!) required, Remote Panel works even when the device is connected to the PC via USB only. However, an SDK for Remote Panel is provided also. Sensor values are provided by the industry-leading system information tool Aida64 which must be purchased separately. Please note that Remote Panel is not affiliated with Aida64 or FinalWire in any way shape or form and no support can be provided by the Aida64 team for this app. Requirements - Aida64 version 5.20.3414 or heigher must be installed on the Windows PC. - Remote Panel (for Windows) version 1.16 must be installed and running, it can be downloaded with the following link http://apps.odospace.com/RemotePanelSetup.exe - Microsoft .Net framework 4.5 must be installed on the Windows PC. This will be done during the installation of Remote Panel (for Windows). - The android device vendor's drivers must be installed on the Windows PC. - USB debugging must be enabled on the android device. This is described in detail here. Enable Aiada64 plugIn - After installation of Remote Panel (for Windows) Aida64 must be restarted. - Within Aida64 open the preferences page, navigate to LCD and enable "Odospace". Add items within the LCD items page. Settings - A long press within the view opens the settings dialog. Troubleshooting - In general the settings dialog of Remote Panel (for Windows) can be opened from the popup menu of its tray icon. - Remote Panel (for Windows) uses port 38000 and 38001 for local communication, if you experience problems because another PC program is using one of this ports, change the port number within the Remote Panel (for Windows) settings dialog and within the Aida64 Odospace LCD plugin. - Remote Panel (for Windows) uses the Android Debug Bridge (adb.exe) for communication. If you experience problems with other Android synchronization programs, try to use another adb.exe file - it can be changed within the settings dialog of Remote Panel (for Windows). - On default, Remote Panel (for Windows) checks every 30 seconds for new devices, decrease this value within the settings for faster device recognition, increase this value for less CPU usage. Alternative usage - If an additional PC should send its sensor values to the android device, set the IP address within the Aida64 Odospace LCD plugin to the address of the PC where the android device is connected. For every PC specify a different panel position parameter. Remote Panel (for Windows) must be installed on every PC, however the Remote Panel (for Windows) executable must only be started on the PC where the Android device is connected. - Remote Panel can be used within a WiFi network also, in such case set the IP address within the Aida64 Odospace PlugIn to the device's address. The port must be set to 38000. The Remote Panel (for Windows) executable can be stopped in this case. Advanced topics - To automatically start Remote Panel you can use AutoStart. - To power off the device on PC shut down you can use AutomateIt Pro - use the USB disconnect trigger. - If the device battery discharge even connected via USB, try to set the CPU speed to a lower level. For example you can use Tickster MOD. - To power on the device on PC startup the device firmware must be modified (follow this AT YOUR OWN RISK, tested with Cyanogenmod 10.2 on LG P760/P880 and may not work with all devices): General 1. Download the device firmware - it can be the original or custom ROM. 2. Use Boot/Recovery Repacker to extract the boot.img file of the downloaded ROM. 3. Within the file init.rc, in the section beginning with "on charger" replace the string "class_start charger" with "trigger boot" or "trigger late-init". Ensure that your editor writes the file in UNIX format. 4. Use the repacker to compress the boot.img file. 5. Apply the new firmware. Nexus 7 (2012) 1. Boot in fastboot mode 2. Issue the following command within a command prompt: "fastboot oem off-mode-charge 0" Version 1.14 - Now sensor data of multiple PCs can be displayed on one android device - The android device can be connected to any PC (not only to the PC where Aida64 is running) - Requires Aida version 5.20.3414 or higher and Remote Panel (for Windows) version 1.14a Version 1.15 - Fullscreen mode (long press for settings) - RemotePanel (for windows) version 1.15: Verbose mode for better problem handling, fixes a rare ADB hang when multiple PCs are connected to one android device. Version 1.16 available - New option added: Keep screen on (long press for settings) Many thanks to the Aida64 team for the great support! Best regards odospace

If you have no RAID arrays defined, you can try disabling the two RAID related options in AIDA64 / main menu / File / Preferences / Stability. It accelerates AIDA64 startup and you can also avoid BSoD in certain circumstances.

On Asus AM4 systems it's safer with the Asus WMI sensor support enabled. Without it concurrent access by AIDA64 and the motherboard BIOS can cause collisions that may just end up in fan duty cycles messing up. Please note that even though the new Asus WMI ACPI interface was invented and designed to avoid those collisions that plagued the Asus AM4 platform since the very beginning, the interface is poorly implemented in multiple Asus motherboards. It is also not implemented all across the board. So while it's a great thing in theory, in practice it causes a lot of headaches. All you can do is put more pressure on Asus to fix this issue in a future BIOS update.

Thank you! It seems the HID protocol we use for Z10 cannot be used for Z10 RGB, since the protocol itself seems to have changed. We've contacted EVGA and asked them to provide us with he necessary technical information to implement support for the new Z10 RGB HID protocol and so let us put our own bitmaps on the LCD of Z10 RGB. I'll let you know once we could accomplish all of that.

Can you export and share this? This is sweet and I think it would looks sweet on my Snowblind display

What kind of tablet do you have? We've tested this with our Nexus 9 tablet, which reflects that a previous resolution of 1024 x 671 should be used in landscape mode. When we set it to that resolution, the LCD preview is in landscape mode (as it should be), and whatever we put on the LCD layout gets displayed properly on the screen. Almost the whole screen is filled, with only the top Android notification bar and the bottom Android virtual buttons bar make the usable area of the 9-inch screen a bit smaller.

This is a case of using SSD1322 & FT232H https://forums.aida64.com/topic/4479-sale-er-oledm032-ssd1322-32-oled-usb-interface/

Thank you for your feedback

Make sure to upgrade to the latest beta version of AIDA64 Engineer available at: https://www.aida64.com/downloads/latesta64eebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

Try to go to AIDA64 installation folder, and find the settings file called AIDA64.INI. If you have the file there, try to edit it using Notepad, and replace the following lines: LowLevelRAIDEnum=1 LowLevelRAIDSMART=1 ... with the followings: LowLevelRAIDEnum=0 LowLevelRAIDSMART=0 If you don't have the file there yet, create it, and enter the following lines into the new text file: [Generic] LowLevelRAIDEnum=0 LowLevelRAIDSMART=0

that looks really nice and clean. hope you share it soon

I was just asking because we've revamped the SMTP module to unlock support for Yandex and other mail services in AIDA64 v5.97. So you need that version or an even newer one to have proper SMTP support with SSL/STARTTLS.

State #0 should display the state where the range is zero, so it shows for example 0 RPM or 0 degrees Celsius. State #15 should display the state where the range is at its maximum. So it shows like 5000 RPM (if your cooler can spin up to 5000 RPM) or 100 degrees Celsius (if you deem your thermal readings will never exceed that value). All the other states should show an intermediate step. Since State #0 = 0%, and State #15 = 100%, for example State #5 should show the range as if it was 33%.

Thank you, we'll fix the issue in the next AIDA64 beta update. I'll post a message into this topic once the new build is available for download.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor 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. Thanks, Fiery

It is detected using various detection methods and built-in hardware databases. It's not possible to edit that string.

Thanks for the feedback. The new items should be available for the SensorPanel automatically -- but they're not added to the SensorPanel layout automatically. You need to right-click on your SensorPanel --> New, and pick the item you're looking for.

Yes, and already added support for it in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta You can activate the Rival 710 OLED module in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / SteelSeries. Let me know how it works.

Thank you. We've improved on Radeon VII support in the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta On the Display / GPU page the new update should measure GPU clock and memory clock properly now, and should display a whole bunch of sensor readings on the Computer / Sensor page as well. Please let us know how it works on your Radeon VII cards.

I am also having the same issue with AIDA 64 sensor panel not showing temps for the Radeon VII. I am on the current version stated above. From the debug it reads the temperatures and lines up with other programs but the option for the sensor does not appear in the sensor panel atigpureg.txt

Thank you for the info. We'll remove the VRM temperature reading in the next AIDA64 beta update.

First of all, make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. That should help about issue #1 and #2. If not, then please let me know where exactly are all your fans connected to (motherboard or water cooler/coolers), and whether the motherboard connected fans are "iffy" or the ones connected to your water cooler/coolers. As for #3, as you can see on the AIDA64 OSD Panel shots, there're quite a few thermal readings available for your CPU, namely "CPU", "CPU Package" and 4 core temperatures. iCUE could indicate any of those as CPU temperature, or it could simply show the liquid temperature of your water cooler as CPU temperature.

Along with the Logitech Arx integration, we've also come up with a new LCD module that basically acts as a web server. You can use your main computer to run AIDA64 on it and maintain its built-in web server, and you can use your other computers or mobile devices to monitor your main computer's status remotely, using nothing but a web browser. You can activate it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / RemoteSensor. Once you activated it, you can enter the IP address in virtually any web browsers to connect to the RemoteSensor. You can check the primary IP address of your computer on the Computer / Summary page in AIDA64. If it is e.g. 192.168.1.123, then enter the following in the address bar of your web browser: http://192.168.1.123 Or, in case you use a different TCP/IP port than the default http port of 80, then enter the address like this: http://192.168.1.123:8080 (if you use a TCP/IP port of 8080) Or, in case you try to use a web browser on the same computer where AIDA64 is running, you can simply use "localhost" instead of the IP address, like this: http://localhost Once you did that, you should see the AIDA64 splash screen in your web browser. 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 and other devices 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 way web browsers 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 1360 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. Known issues and limitations: 1) Graphs and gauges are not implemented yet. We're planning to add them in the next few weeks. 2) RemoteSensor uses HTML5 SSE (Server-Sent Events) to refresh the web page, without having to reload it all the time. SSE is supported by almost all major web browsers, including Android Browser, BlackBerry 10 Browser, Chrome, FireFox, Opera, and Safari. However, it is sadly not yet supported by Internet Explorer. AIDA64 implements a trick to get around that limitation, but it sometimes will result in a mixup of the browser. If you notice that after changing the LCD layout in the AIDA64 Preferences, a strange log replaces the LCD layout in your browser, just refresh the web page. Hopefully Microsoft will finally implement SSE support in Internet Explorer 12 3) In order to prevent your mobile device from going to sleep while having the web browser open, you may need to install special apps on your mobile device. RemoteSensor has absolutely no control over the power management behavior of your mobile device. In case this is a deal breaker for you, and you've got a Logitech Gaming hardware, consider using Logitech Arx instead of the RemoteSensor. You can try the RemoteSensor in the following new AIDA64 beta update: http://www.aida64.com/downloads/latesta64xebeta Please let us know how it works on your mobile devices Thanks, Fiery

That RGB fusion issue is fixed already, and the fix is inherited by the newer and newer beta updates, as well as the stable updates in the future.

Please note that it's not possible to diagnose such issues remotely. You may want to take your phone to a local specialist and have it checked out.

Special thanks to Novax as this entire Sensor Panel is a copy of his wonderful work. Thank you again for your creativity and generosity. HellKatDash02_08_2019.sensorpanel

Yes. Upgrading to a new beta is as simple as that. You can let it overwrite any existing files. It will retain your existing settings (it won't overwrite or remove AIDA64.INI file) as well as your existing license.

nuevo panel que estoy terminando este diseño no tiene nada que ver con los gauges les dejo unos gauges por si los quieren utilizar en el archivo rar. Gauge.7z

Final built in red orange 4 ORANGE Red.splcd.axlcd

Pls share

Thank you! We've fixed the voltage readings in the latest AIDA64 beta build available at: https://www.aida64.com/downloads/latesta64xebeta

I don't think your motherboard is capable of monitoring VRM temperature. We'll add the missing fan readings in the next AIDA64 beta update. I'll drop a message into this topic once the new AIDA64 beta is available for download.

We've fixed the issue in the latest beta version of AIDA64 Extreme available at: https://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 when your nVIDIA GPU is sleeping or went to sleep after a few minutes of inactivity.

I think it's due to a difference between character-sets (character encoding) used on your PC and on your iPad/iPhone. We'll do some test runs and try to solve it by switching to UTF-8 or Unicode. I'll let you know in this topic once we have a fix for this issue.

Decided to try and work on one of these doodads... Really schocked, got it done in like 5 hours. CHEERS I built it basically looking at the work from the samples shown on here by a couple of users.

CPU Package temperature is measured directly, without needing to hassle with TJMax. TJMax temperature is detected and shown on the Motherboard / CPUID page of AIDA64. Please note that CPU Package temperature and CPU core temperatures are measured using a different method. The measured values may or may not match, but all those values have relevance and should be accurate. If your goal is to keep your CPU working temperatures well below TJMax, then ignore the CPU Package temperature and just focus on the CPU core temperatures.

Ok cool I'll see what I can come up with for ya we can fine tune it later on ...

Thank you for your feedback

Bonjour à tous, Voici mon SensorPanel dont je suis fier d'avoir créé!

It's a shame that Sensor Panel is absurdly underused because the U.I to configure and customize it so unfriendly. Anyway, I find that having too much information on the panel just distract's me from what I really need to pay attention to when gaming, so here is my simple flat design panel inspired on the colors from material design (which also match the wallpaper behind it) flep_material-flat.sensorpanel

It's pretty simple, but it shows almost everything I want. If only I could include my Gryphon Z97's temperature probes! (image taken while folding with CPU and GPU)

Current:

Got a bit carried away with XCOM2 and hunting down a (possible) memory issue...

My MSI themed attempt SensorPanel

Here is mine, made to match some desktop gadgets I like to use. sensor.sensorpanel

Great :-) Can I get a set of these, please.

We've checked, and MQTT is quite a complicated protocol to implement from scratch. If there's a considerable demand for such a feature, then I believe it would be best if someone came up with a library that picks up AIDA64 External Applications readings from Shared Memory, Windows Registry or WMI, and send the stuff over MQTT using its own libraries and implementation.