In message <>, Steve at
fivetrees <> writes
>The temperature range you quote is the so-called "organic" range, and
>you may find it easier to use an RTD (aka PT100) sensor. These sensors
>*may* be a tad pricier than a type K t/c, but they are easier to read,
>either in 3-wire or 4-wire configurations, and you don't need a cold
>junction (but you do need a stable current source). Also the accuracy
>you're after may well be easier with an RTD.
We thought about Pt100 sensors but they're intrinsically more expensive
than "simple" thermocouples -- we may have to supply sets of different
sensors built for different physical layouts within the bath. Worst case
we roll our own sensors using regular twin-core K-series thermocouple
wire, insulate them and encapsulate them in thin-walled copper or
stainless tubing to prevent water ingress and corrosion. Other
possibilities include thermistors but they have their own problems like
individual calibration, drift, insensitivity etc. Nothing we can't fix
but it's more work again.
>
>Re cost: I've designed temperature controllers (albeit for high-volume
>production) with way tighter budgets than that
. Have you considered
>some of the 1/16th DIN controllers from e.g. CAL or West Instruments?
We're using a DIN PID module at the moment in the prototype, but unless
you know of anyone selling such modules under fifty bucks we're screwed.
Best price we've been quoted for small quantities is about a hundred
bucks each, and more typically they're about 150-200 bucks. They're also
over-complex for naive users to configure, with too many things that can
be programmed wrong for the job it's meant to do.
>Also, have you considered how you'll amortise the development costs? A
>PID algorithm is not rocket science, but there are a number of wrinkles
>(e.g. integral wind-up etc etc) that newcomers tend to have to learn the
>hard way...
Yah, one reason we prototyped using an off-the-shelf PID to start with.
There's a secondary R&D project running with the existing prototype
which we're also planning to make some money out of but we're looking to
sell units to end-users as well. For those end-users PID *is* rocket
science, just about. I've already had to reprogram the PID once after my
assistant managed to disable the PID autolearn function which we were
relying on to deal with variable masses of water in the bath. This was
after he managed to lose the programming instructions which were written
in Janglish anyway.
The idea is to roll a neutral set of characteristics for the bath
controller to preventing ringing, hunting and overshoot -- with no
active cooling system for the bath it takes a long time for the temp to
recover from an overshoot, one reason we're considering mineral oil or
something with a lot less thermal capacity than water. If it takes
longer to reach the target temperature but doesn't overshoot that
doesn't matter in user terms. Overshoot in operation is *the* major
worry as that will cause Bad Things to happen.
--
To reply, my gmail address is nojay1 Robert Sneddon