![]() To keep things simple there's a global variable that is a list of HD temps to monitor, which you can remove from or add to as needed. He changed the sub's for getting HDD temps to utilize hddtemp. He helped me with the bits of perl that needed changing since this area's not my forte. It utilizes the hddtemp & lm-sensors programs instead, and I'm also including the systemd service file so you can autorun it.įirst off, the scripter I worked with was gperales on Fiverr. In the event any other Ubuntu Server folks stumble on this script and want to utilize it, I worked with someone who knows Perl far better than I to update a couple portions for Ubuntu Server 16.04. Intel Xenon E3-1231v3 | Supermicro X10SL7-F | 4X8GB Crucial 1600Mhz ECC CT2KIT102472BD160BĢX16GB Cruzer Fit Mirrored (Internally mounted 2 Port USB Motherboard Header Adapter USBMBADAPT2)įractal Define R4 | Seasonic G-450 | 2X Noctua NF-A14 Industrial PPC-3000 PWM, 2X Cougar Vortex PWM CF-V12HP Many thanks to all who have contributed to the development of this script.Ĭonfiguration at the time of this report: Attached is a plot of various factors observed over a 24 hour period. ![]() I will continue to monitor over the next few days before making this change permanent. It appears to me that no additional PID tuning is required. Implementing this script certainly provides much narrower temperature control and generally runs much quieter than the previous version. The only change made to the script was the the max_fan_speed variable according to my specific hardware. The script is currently running at debug level 1 and has logged about 5 days worth of data. Just this past week I've started evaluating this latest script. ![]() Until recently, I was using the version of the hybrid_fan_ script for rudimentary HDD temperature control. It is unlikely to work on X9 boards or earlier. Update - This script was written and tested on Supermicro X10 motherboards. Update - the latest versions of the script is available on Github. pl uploads), and make it executable, with "chmod +x PID_fan_". Thanks for for his script, and to for doing the research and creating his PID control shell script. Be sure to test it carefully before trusting it. I'll take the blame for anything I've screwed up. The bulk of the script is unchanged from his version, and he deserves full credit for those parts. I left the CPU fan control portion alone. I've updated hybrid fan controller script to replace his HD fan control logic (which uses three discrete fan duty cycles as a function of warmest HD temperature) with a PID control loop, which controls duty cycle in 1% increments as a function of the average HD temperature. I have changed the USB slots of the motherboard (ASUS ROG Strix Z790E) as well as the USB-C connector of the cables to see if it is an USB issue.I can't post in Useful Scripts, so Hardware will have to do. So when I turn on the computer the MX2 Waterblock, R2 Monitor and 4x Toughram DDR5 start using the color profile that I defined while the toughfans and the Distroplate go on in RGB waves as they do when I turn on the computer. I also do have the problem that the RGB Controller that runs 3 Toughfan 12 RGB and a DP100-D5 Distroplate looses connection to the RGB Plus Software. If it's a USB thing how hard could that be to get it to recognize? I've heard something about newer controllers or other controllers that were given to people as replacements - THAT DIDN'T WORK EITHER. It's worked in the past so no I'm not doing that. I refuse to take apart my computers to pull the USB header off and then back on to "See if it will work." That's not the problem. I'm running the latest version of Windows 11 with Asrock TRX40 Taichi and ASUS Pro-WS-WRX80E-SAGE-SE-WIFI. If you think you know a stable version that works, let me know. Time to take the entire thing back to base code and work it. You all know about it and haven't done anything that actually works. The controller issue not able to be detected has been this way for YEARS. If I uninstall it and then reinstall, sometimes that fixes the problem but for the most part it goes back to not working properly. ![]() I have 2 AIO Units for Ryzen Threadripper and TR Pro CPUs, the software DID work initially but then stopped. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |