That may be an inaccurate count. The chambers that I have worked with will use both systems (heating and cooling) while performing ramp operations. Take the heating cycle: While going from a low temperature to a high temperature, the heaters will come on, but as the temperature approaches the endpoint of the ramp, the cooling system will come on so the temperature does not overshoot by too much. It's either that or ramp the temperature over a LONG time. If it is a long ramp, then I think your latch system would be a good way of doing it.
As for the recording - he may need data to show that the test was performed correctly. Admittedly, every 5 minutes over this amount of time will be a HUGE amount of data. As long as he is taking readings, a simple VI can
be created to "test" the data and increment a counter on screen for each cycle.
Borrowing your latch concept - a while loop with a case structure in it would work. The counter increment would by in a case that looks for the temperature to reach a certain value (for example the high temperature) and call another case that looks for the temperature to reach a different value (for example the low temperature) then call the first case. This would get rid of any extra counts from the temperature oscillating around one dwell or the other.
I just re-read his question and he says that he's "taking" data every 5 minutes, not necessarily recording the data every 5 minutes. Recording a subset of this would be a good idea.
Rob