Leaderboard

ROG Edition I uploaded the font i used as well pirulen rg.ttf 2019-10-08-Final.sensorpanel

Razer beat

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.

Current:

LCD exporting takes all LCD pages and writes them to the export file. If you open the .RSLCD files using Notepad for example, you can see that each page content is between similar tags like this: <LCDPAGE1> ... page content ... </LCDPAGE1> If you have multiple RemoteSensor layouts created, and you always used Page 1 in those layouts, and exported them to separate .RSLCD files, you should have LCDPAGE1 tags (and only those, not LCDPAGE2, LCDPAGE3, etc) in all those files. Problem is: when you import a layout, it will wipe your current layout, all pages of it, and import the page (or pages) from the .RSLCD file you select. Currently it's not possible to import a .RSLCD file into a page of your choice, so even if you alter the files to have different LCDPAGEx tags, you will only be able to import a file into a specific page but the rest of the pages will still be blank. What you can do to overcome this limitation is to combine the .RSLCD files into a single .RSLCD file where you use multiple page tags and put the relevant content between them. For example: <LCDVER>200</LCDVER><SWVER>6.20.5321 Beta</SWVER> <LCDBGCOLOR>16777215</LCDBGCOLOR> <LCDPAGE1> ... page content coming from one of your .RSLCD files ... </LCDPAGE1> <LCDPAGE2> ... page content coming from another one of your .RSLCD files ... </LCDPAGE2> <LCDPAGE3> ... page content coming from the 3rd .RSLCD file ... </LCDPAGE3> That way you can combine your .RSLCD layouts to exactly the page assignment of your choice.

For clarity, there is a screenshot of my situation at the bottom. I. e. 2 monitors are connected to the computer, absolutely identical-but except for the serial number and release date, and when uploading the report to the database-I can't process this information so that I understand that in the report there are 2 monitors, if they differ in name, then it would still be possible to group them, but not in this case. And this is where it would help a lot to have an additional field Sequel by which I would be able to group, and understand that there are 2 or more pieces. Similar situations are suitable for many other types of information where there are many similar devices

Thank you, we'll check it out.

Hi! Last year, I was looking for a display to show different information on my home theather computer. I wanted a display to fit in a 5" 1/4 bay and no LCD technology as I don't want backlight that lights all my room when I watch a movie (high contrast required). Then I discovered the 3.2" monochrome OLED display ER-OLEDM032 based on SSD1322 chip. Support in Aida64 was implemented by Fiery. It looks great! Infinite contrast of OLED technology is perfect. 4 different models exist for 4 different colours. Blue: Green: White (what I chose): And yellow: Dimensions: 4 protocols are available. Protocol to be used is set using bridges on the display PCB. 6800 8-bit parallel 8080 8-bit parallel 3 wires SPI 4 wires SPI 6800 and 8080 are obsolete as we don't use anymore parallel port. I chose 4 wires SPI rather than 3 wires SPI because communication speed is a bit higher. To convert USB to 4 wires SPI, I used a FTDI UM232H-B-WE breakout module based on chip FT232H. Here is the schematic of connections between USB breakout module and OLED display:

That was quite harsh. This forum is dedicated to providing support for our software (AIDA64), and not as a generic technical help/support forum for various hardware or software related issues. Even so, I've replied you and started a conversation. Anyway, I'm glad you've managed to solve your issue. This topic is locked.

We'll remove the bogus CPU thermal reading in the next AIDA64 beta update.

Please 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. Let me know how it works.

Done a sensor panel with lot's of room for more gauges.I use them for PC gaming. Dragon Nights Gauges.7z Dragon Nights.sensorpanel

Did some re-arranging: Would it be possible to add a feature where we could highlight certain sensors (gauges) and have them change color? For example; I want to keep an eye on CPU voltage and water temperatures. I would be able to select those gauges and the gauge background would turn red with yellow numbers and blue 'ticks'?

HI, just got Aida64 Extreme for my new PC coz my 3900X was running hot and the Wraith cooler was spinning up & down frequently at idle with no load so I wanted to stress test and monitor the system stats. I found the SensorPanel very useful but the customisation is not very intuitive so I took one from this Reddit post, and downloaded the sonsorpanel file from the poster's link but mine doesn't look like his SensorPanel, looks like scaling/sizing issue. I did a clean Windows install and installed Aida64 Extreme again and imported from the link again but same issue, the gauges & bars have shrunk and I couldn't find any settings to resize them. 2019-08-09 fixed.sensorpanel

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.

Hello, Sorry for the delay been real busy ... so in the end result I ended up making the background transparent so they would be universal plus the blades spin ....and I took the branding off cause I don't support Thermaltake anymore..(Cause they won't support me).BTW anyone looking to buy 120mm TT riing plus fan kit ??? 5 x fans (3 are about 1 year old and 2 are new with only 100 hours use) bran new riing trio controller and all the wiring... $100 ....I can't get the software to work properly anymore due to another program I'm running (DAW) and I need the other program... BTW Nik, If you have any questions about sensor panels I have a bunch of stuff I made and modded over the past few years so I may have something you are looking for and I would be glad to lend a hand....Also those pics you "quoted" are from like 2 years ago ... lol transparent black fan - gauge 70 x 70.zip

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

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.

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.

Thank to Novax for sharing gauges 3 BLUE Red.splcd.axlcd

I have reworked everything a bit. The left side i am happy with at this moment. Right side i have to go another time. With top i am not sure what i will make, the gauges can still be in place but i don`t know what i do with fraps and processes. Icons for components are all interaktiv. Many thanx to @xtcislove who shared his panel, (which is also really great) and .psd files. I have used some of them and changed the orange to green, so it will fit better my needs! What do you think? is it to overload, i have missed something important? So i hope you like it, if its ready in my opinion i will share it to the forum in any way! Greetz Stealth

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

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

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

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

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

Greetings to all First of all this is not my work at all, it belong's to @Stupe9968 there is great works here but i think this is the best i ever saw it. when Stupe9968 post it here i send him a PM to share hi's great work but only after 2 years he reply me back and shared to me So i will share hi's work to you guys aswell hi's worked images file is to big for upload https://drive.google.com/file/d/0Bx2ic5sIfLxCQm1mV3B2TWNRcjg/view?usp=sharing

1) Do you have 2 or 4 processor sockets populated? 2) Do all processors have DDR3-1333 memory installed? So every processors use the same memory configuration? In case you have 4 processor sockets populated, and every processors use the same DDR3-1333 memory configuration, that would mean you've got 16 memory channels total, each running at DDR3-1333 speed, which would mean a total memory bandwidth of 166.6 GBytes/sec. Hence the results could well be accurate The confusion may come from the fact that AIDA64 (the main application itself) only supports up to 32 processor threads, so it cannot show you all processors on the Cache & Memory Benchmark Panel. However, the multi-threaded memory benchmarks support up to 64 processor threads, so it can utilize all 48 processing threads you've got in your system (if you have all 4 processor sockets populated, each with a 12-core Magny-Cours CPU). Regards, Fiery

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.