Hi ocluke. It sounds like you are doing everything right, everything that you describe is correct. Note that the setpoint that you enter in the Current State Properties table, 65 in your case, is immediately overwritten by the new ramp setpoint when in ramp mode. Things to try:
- Temperature probe association. Make sure that you are ramping the setpoint that is associated with your output! Make sure Alt Pid is disabled if you are not using it for this state as it could switch the association.
- Latest firmware revision? v3.3 had a bug on the upper temperature probes (462 only) http://www.embeddedcc.com/wiki/index.ph ... and_Errata
- The output needs to be set in either Hysteresis or PID control, these are the only two control modes that use a temperature association.
- This might be a case of output contention. By that I mean multiple processes trying to control the same output. Make sure that no other processes controlling this output are enabled, including manual mode.
I would recommend using the datalog feature. You can plot the temperature setpoint along with the temperature. You should see (when you enable the process) the temperature setpoint immediately goes to the start temp (which you noted that you observed), and it then slowly ramps down to the End Temp over the ramp time. Obviously this is going to be pretty slow over a 24 hour period, you may want to shorten the ramp time just to see how it works and get a feel for it.
This doesn't sound like your situation, but I'll list it here anyway.. Remember, we are ramping the temperature setpoint, not the temperature. If everything is setup correctly, the temperature should follow the setpoint when it is adjusted. But if the cooler can't keep up for whatever reason, the temperature may not be able to follow the setpoint due to system design.