Many amateur darkroom enthusiasts (until recently, me included) are wary about developing colour film with the C-41 process, on the assumption that it is difficult, confusing, expensive, or all three.

It is true that colour process has to be more accurately temperature-controlled, and that the development should be done at 38°C. Immediately, this conjures up images of having to buy an expensive electronic water bath, such as the Jobo CPE-2. These machines do help, and they do cost hundreds of pounds. However, they’re not necessary. The development usually takes only 3-4 minutes and the later stages do not have to be quite so accurately controlled. This means it’s possible to use a plain warm water bath.

It’s not too expensive or confusing, either. There are beginner’s kits such as the Rollei Digibase C-41 LT20 which include all of the chemicals you need, with instructions. I paid £25 for a kit that can do about 20 films. There are bigger kits which are better value too, and it’s possible to restock on the individual chemicals in future. I’m no expert on the C-41 process, so you should probably read up on C-41 chemistry yourself.

I bought a wallpaper pasting trough for £2 and made a cardboard lid with holes for my bottles and tank to stand in the water. I filled the trough with water at 50°C and stood the bottles and tank in the water to reach the right temperature. The temperature of the water bath fell rapidly at first, and then slowed down. After about 5 minutes the water bath was at about 40°C so I waited until the temperature fell to 38°C, checked the temperature of the developer as well as the water bath, and set the development process going. The thermometer still read 38°C after the development was up.

By the end of the entire process of developing, stopping, bleaching, fixing and stabilising, the temperature of the water bath had fallen to 35°C, but this is still within tolerances.

My message to photographers who are wary of processing colour film at home: don’t be. You have to be careful, but you don’t need any special equipment other than what you’ve already got for your black & white work.

Have fun!

From these graphs, it seems that the higher the outdoor temperature, the more free memory the system has available. I’m sure this is just a coincidence, though…

Outdoor temperature

Free memory

Well, now it’s too cold. The UK has had a bit of a cold snap lately. Outdoor temperatures in Bristol last night got as low as -3 °C, and in turn the temperature in my loft went down to 2.5 °C.

Ambient temperature in my loft

Thing is, that’s probably a bit too cold for my server now. The CPU is happily sitting there at 24 °C but the disks are all around 15 °C.

According to Wikipedia:

A common misconception is that a colder hard drive will last longer than a hotter hard drive. The Google study seems to imply the reverse – “lower temperatures are associated with higher failure rates”. Hard drives with S.M.A.R.T.-reported average temperatures below 27 °C had failure rates worse than hard drives with the highest reported average temperature of 50 °C, failure rates at least twice as high as the optimum S.M.A.R.T.-reported temperature range of 36 °C to 47 °C.

So my disks appear to be at risk of failing sooner. Worse yet, they’re not consistently at 15 °C but fluctuate wildly on a daily and seasonal basis. Looks like all I can do is keep my data on a redundant array and swap out any disks when (not if) they fail.

However I found that with a large area of roof exposed to the sun (even the weak Autumn sun), and practically no ventilation the ambient temperature fluctuates enormously.

In October when it was a little warmer and a little sunnier, the temperature would drop almost as low at 10°C and almost as high as 30°C. An ambient temperature of over 25°C seems to drive my disk temperatures up to over 50°C. This constantly changing temperature with high and low extremes is a sure-fire way to break hard disks.

After Week 42, I opened the loft trapdoor, which went a long way to keeping the temperature more constant. Unfortunately it also makes the flat rather cold.

Now it’s much colder outdoors, I’ve closed the trapdoor again and the loft temperature seems pleasantly cool and reasonably constant. Today the temperature up there is a steady 13°C, although the sun hardly shone. That’s cooler than your average air-conditioned data centre – and all free thanks to the crappy British weather

Oh, and the 6 disks are now all between 25°C and 30°C.

• I’m measuring and graphing this using a TEMPer USB thermometer, using Nagios monitoring software with my own plugin and PNP4Nagios to draw the graphs.
• The “outage” between weeks 43 and 44 was caused by the shift from BST to GMT, apparently. I didn’t notice for a while, but restarting Nagios fixed it

Here’s a quick summary:

• check_temper for monitoring the temperature with a TEMPer USB thermometer
• check_kernel for checking that the currently running kernel on an RPM-based system is the most recent installed kernel (not necessarily the latest available kernel in the repository)
• check_aql_balance for monitoring the number of SMS text message credits on your AQL account^[1]
• check_k8temp for monitoring the temperature of an AMD K8 (e.g. Athlon or Sempron) CPU

I’m not familiar with C so I only made minor tweaks to Tollef Fog Heen’s code, which returns a temperature as a number. I wrote a wrapper in Perl that crudely interfaces this program to Nagios. In reality, I should wise up on my C a little and write the whole thing in C. When I do this, I’ll submit it to Monitoring Exchange.

For the time being, I’ll publish my Nagios plugin on this blog, in the hope that it might be useful to someone, despite being incredibly hacky.

First you’ll need the code for the program that reads the temperature from the TEMPer. Compile it like this:

g++ -o get_temper TEMPer2.c

Note that the path to the TEMPer device is hard-coded in the C If yours isn’t at /dev/ttyUSB0 then you’ll need to change the source before compiling.

Then download my Nagios plugin (check_temper), and put both the plugin and the program get_temper in your Nagios plugin directory. This is likely to be /usr/local/nagios/libexec if you built from source, and /usr/lib/nagios/plugins if you installed from RPM in the Fedora repository.

Now all you have to do is the usual Nagios magic for adding any other plugin. Simple!

Update

Forget all that you’ve read above! I’ve now rewritten the entire plugin in C, so there is no need for the perl wrapper. You can download it from MonitoringExchange.

I eventually found the blog of Tollef Fog Heen, who had managed to get his TEMPer to work. Unfortunately his solution involved patching and compiling a kernel.

However since then, it seems his patch has been integrated into the stock Fedora kernel and it is now possible to read the temperature from it.

The TEMPer device appears to be a USB-serial adapter, with a serial I2C device at the end of it. It’s not straightforward to extract the temperature from it, but Tollef Fog Heen has written a simple C program to return the temperature.

His program polls the TEMPer every second and prints the temperature to the command line. It doesn’t stop until you kill the program. I made a couple of tweaks to the code so it prints the temperature once, formatted as a raw number with no extra text, and then quits. You can find my modified source here.

Disclaimer: I don’t know C. I haven’t changed any of the logic of the code, only the way it prints the output. If the code is buggy, it wasn’t me!

Now I have an executable that returns the temperature from the TEMPer, I can think about building some application that could use this. How about a Nagios plugin?