My NUC needed an SSD brain transplant, which presented a good opportunity to clean the dust out of the fan exhaust vents. It was almost completely clogged:
I vacuumed it out, which didn’t work too well, since the dust was a little greasy, so I hauled out the carpentry tools (my compressor and blower attachment),
and gave it a good blast. Check out the after picture for the vents:
Here it is, reassembled
Ready to be my little workhorse once again. I also blew the dust out of my older non-skull canyon NUC, which I had abandoned (switching to a backup) when it started emitting a strong burnt electronics smell. That unit is now fully functional again too, and doesn’t smell like burnt electronics anymore!
These NUCs are nice little machines, but are really susceptible to dust clogs, as the vent spacing is really tight. Once those gets clogged, there’s basically no airflow possible.
My “nuc1” has been inoperable for months, with a dead fan. The replacement was delayed by the panic-demic significantly, but finally arrived today. Here’s the NUC all opened up, with my replacement fan ready to be installed:
I had some trouble taking it out, and it turns out that it’s taped down, as well as screwed, so it just took some brute force. However, check out the dust on the vents:
I’m wondering if the original fan was actually okay, and this beastie just needed a cleaning. There wasn’t much surface area that would allow any air flow (just that tiny little corner), and I suspect that even that tiny little corner that wasn’t blocked was obscured before I pried up the old fan.
After cleaning the vents, and installing the new fan (I’d purchased it, so thought I may as well install it, even if the blocked ducts were the problem.), I can now run a parallel build without a constant barrage of temperature events. I do get some:
but things return to normal and the lm_sensor package (sensors program) reports core temperatures within range, despite the parallel make:
This beastie runs hot, but I already knew that. I see the temperatures spike during make, and get near the high threshold, but not all the way there.
I’m monitoring with both dmesg -w and sensors:
sudo yum install lm_sensors
while [ 0 ] ; do clear ; sensors ; sleep 5 ; done
For reasons not completely known to myself, I bought a raspberry pi recently. Here’s a first circuit, a collaboration between myself and Lance. Lance added a switch between the GPIO output port and the LED, so that the port has to be enabled by both software, and by the physical switch
pi and the circuit
I tried two different ways of controlling the GPIO, the first using a command line tool:
gpio mode 0 out
gpio write 0 1
gpio write 0 0
and the second with a bit of python code:
import RPi.GPIO as GPIO
GPIO.output( 17, 1 ) ;
time.sleep( 5 ) ;
GPIO.output( 17, 0 ) ;