I just purchased one of these from Richard Ross. It seems to be an excellent developing timer and has certainly replaced a monstrous old Tandy computer I was using and will compensate for temperature fluctuations as well
Mark
Thanks for the tip Mark. I checked the RH site and I'm highly likely to buy one. I like the 30 sec agitation beep and the percentage N+ or N- capacity too. I'm just awaiting confirmation that open tray development is OK with a light source around, although apparently it turns off the lights after 30 seconds. The footswitch sounds a real bonus, too.
Thanks for the tip Mark. I checked the RH site and I'm highly likely to buy one. I like the 30 sec agitation beep and the percentage N+ or N- capacity too. I'm just awaiting confirmation that open tray development is OK with a light source around, although apparently it turns off the lights after 30 seconds. The footswitch sounds a real bonus, too.
I'm just awaiting confirmation that open tray development is OK with a light source around, although apparently it turns off the lights after 30 seconds.
Providing the display lights don't fall directly on the film you should be OK - see Les McLean's posting (there was a url link here which no longer exists)
The display switches off after 30 seconds in stand-by but not when counting, to save the battery; this function can be disabled.
The "final countdown" is indeed 10sec, not 15. I was overruled by the software man . If you have a large tank that takes more than 10sec to empty, I wouldn't worry about it as a few seconds are unlikely to make any difference to a development time of several minutes.
If so, is that compatible with the automatic temperature adjustment?
I ask because when I develop BTZS tubes, I put my Gralab timer in count up mode and then remove the tubes sequentially from the shortest to longest development times, and hold them all in stop bath until moving on. It would be a nice convenience if I could do the same thing but with temperature compensation.
Yes it does, optionally, and it is. If that mode is set, once the countdown has expired the timer will count up from zero until twice the original time has been reached. In conjunction with this the % display mode shows what percentage of the original time remains ( -ve display) or has elapsed since timeout (+ve display). You can swap between % and seconds at any time without affecting the count.
What it doesn't do is to optionally count upwards instead of downwards from the start, which if I understand correctly is what your Gralab is doing. I'm sure you could adapt your working method to the way the PM II works - maybe set countdown to the shortest dev time required, and then it will count up from the expiry of that period.