04-26-2007 11:32 AM
04-27-2007 08:59 AM
What do you mean "it dropped during transition." If you are maintaining temperature at some level, then the transition should have no affect on the temperature unless you reinitialize or have wired a default number to the temperature you are trying to control. I tried loading your program. I don't have the instrument controls for the instrument you are using -- not a problem -- but it is hard to follow what you are doing. It looks like you have many different setpoints all coming from the ni435x read.vi in a 2d array. You should check that the values you expect out of that array are correct for each of the points that you use it.
Tom
04-27-2007 09:11 AM
I read your question again... Sorry the first response is not what you were looking for. I looked at the code where you switch cases after the temperature is in range. The only thing you do there is switch which indicator the elapsed time goes to. You need to reset the time if you want the denature indicator to start from zero seconds.
Tom
04-27-2007 09:14 AM
04-27-2007 09:15 AM
You could do this by subtracting the init heat time from the elapsed time in the False case and wire that to init denature. But you would also need to wire that result out of your case to the Greater than or equal compare used to tell when denature time is up. I won't be critical with you but there are many ways you could improve your code!
Tom
04-27-2007 09:18 AM
04-27-2007 09:19 AM
04-27-2007 09:23 AM
As for the drop in temperature, depending how quickly it drops it may just be the transition taking a long time because there are so many things to set up in each case. BTW, you are not running the program with execution highlighting, correct? If you did that would cause a large delay in state transition.
Tom
04-27-2007 09:25 AM