Temperature Control Program - Revision history

Warrenmj at 14:25, 16 June 2017

2017-06-16T14:25:48Z

Warrenmj at 14:25, 16 June 2017

2017-06-16T14:25:07Z

Warrenmj: Documenting new versions of the program

2017-06-16T14:09:26Z

Documenting new versions of the program

Asampino: /* Program logic */

2015-12-17T23:18:12Z

Program logic

Asampino: /* Program logic */

2015-12-17T23:16:49Z

Program logic

Asampino: /* Program logic */

2015-12-17T22:59:34Z

Program logic

Asampino: /* Program logic */

2015-12-17T22:58:27Z

Program logic

Asampino: /* Instructions for a Heating Run */

2015-12-17T22:51:54Z

Instructions for a Heating Run

Asampino: /* Instructions for a Heating Run */

2015-12-17T22:48:32Z

Instructions for a Heating Run

Asampino: /* Instructions for a Heating Run */

2015-12-17T22:44:02Z

Instructions for a Heating Run

@@ Line 37: / Line 37: @@
 =Versions=
 ==June 2017==
-Dr. Jones and I (Micah Warren) simplified the program somewhat. Previously, the program used a separate sub VI to turn the hot plate on and off. Dr. Jones replaced those VI's with a single VI called "HP Netbooter". I also had the program save the temperature data file to a folder on the desktop called "HotBoxDataSummer2017."
+Dr. Jones and I (Micah Warren) simplified the program somewhat. Previously, the program used a separate sub VI to turn the hot plate on and off. Dr. Jones replaced those VI's with a single VI called "HP Netbooter". I also had the program save the temperature data file to a folder on the desktop called "HotBoxDataSummer2017, instead of an old folder."
 ==Earlier==
 [See the section "Program Logic" above.]

@@ Line 37: / Line 37: @@
 =Versions=
 ==June 2017==
-Dr. Jones and I simplified the program somewhat. Previously, the program used a separate sub VI to turn the hot plate on and off. Dr. Jones replaced those VI's with a single VI called "HP Netbooter". I also had the program save the temperature data file to a folder on the desktop called "HotBoxDataSummer2017."
+Dr. Jones and I (Micah Warren) simplified the program somewhat. Previously, the program used a separate sub VI to turn the hot plate on and off. Dr. Jones replaced those VI's with a single VI called "HP Netbooter". I also had the program save the temperature data file to a folder on the desktop called "HotBoxDataSummer2017."
 ==Earlier==
 [See the section "Program Logic" above.]

← Older revision		Revision as of 14:09, 16 June 2017
Line 34:		Line 34:
	The temperature regulation section serves to keep the box at a prescribed temperature. Here the code is centered around a user defined VI named GoUnlessTooHot2, which reads the user indicated target temperature and turns the hotplate on if the highest measured temperature is more than one degree fahrenheit below that value and turns it off if the highest measured temperature is more than one degree higher than that value. GoUnlessTooHot2 also has failsafes that check if there are zero and NaN values reported from the variable Highest temperature and if the box temperature exceeds 190 degrees Fahrenheit. If either of these conditions are met the VI will shut the hotplate off with the use of the VI HP 1 Outlet 1 OFF. GoUnlessTooHot2 is contained in the true state of a case structure that is controlled by a connected timer, which returns true once every ten seconds; the result is that GoUnlessTooHot2 only reads values from the variable Highest Temperature every ten seconds. Therefore, the hotplate state can only change at a maximum frequency of once every ten seconds. Having both a time constraint and a temperature range is redundant so the time dependence of the case structure should be removed, but the case structure itself should be left in tact as it has another function related to stop conditions. [[File:Timer.jpg\|200px\|thumb\|right\|upright\|Timed stop case structure.]]		The temperature regulation section serves to keep the box at a prescribed temperature. Here the code is centered around a user defined VI named GoUnlessTooHot2, which reads the user indicated target temperature and turns the hotplate on if the highest measured temperature is more than one degree fahrenheit below that value and turns it off if the highest measured temperature is more than one degree higher than that value. GoUnlessTooHot2 also has failsafes that check if there are zero and NaN values reported from the variable Highest temperature and if the box temperature exceeds 190 degrees Fahrenheit. If either of these conditions are met the VI will shut the hotplate off with the use of the VI HP 1 Outlet 1 OFF. GoUnlessTooHot2 is contained in the true state of a case structure that is controlled by a connected timer, which returns true once every ten seconds; the result is that GoUnlessTooHot2 only reads values from the variable Highest Temperature every ten seconds. Therefore, the hotplate state can only change at a maximum frequency of once every ten seconds. Having both a time constraint and a temperature range is redundant so the time dependence of the case structure should be removed, but the case structure itself should be left in tact as it has another function related to stop conditions. [[File:Timer.jpg\|200px\|thumb\|right\|upright\|Timed stop case structure.]]
	<br/>The stop condition section is not as localized as the the other sections because the three ways to manually stop the hotplate are independent of each other. The first method of stopping the hot plate is the STOP button, which is the stop condition for the overarching while loop in the first frame; this terminates the while loop and ends the first frame of the sequence structure. The second frame of the sequence structure will then begin and shut off the hotplate and the program will end. The second method is in the manual controls. These controls determine the state of a case structure in the VI GoUnlessTooHot2, which can automatically regulate the temperature, turn the hotplate on, or turn the hotplate off all without ending the program. The final method is a timed stop. The timer is an "elapsed time" block in the true state of a case structure, which is controlled by a boolean button. When the button is pressed the case structure is set to a true state and the timer runs until a user indicated amount of time passes. At this point the VI HP 1 Outlet 1 OFF is run and the temperature regulation section subverted to turn off the hotplate for the rest of the run.		<br/>The stop condition section is not as localized as the the other sections because the three ways to manually stop the hotplate are independent of each other. The first method of stopping the hot plate is the STOP button, which is the stop condition for the overarching while loop in the first frame; this terminates the while loop and ends the first frame of the sequence structure. The second frame of the sequence structure will then begin and shut off the hotplate and the program will end. The second method is in the manual controls. These controls determine the state of a case structure in the VI GoUnlessTooHot2, which can automatically regulate the temperature, turn the hotplate on, or turn the hotplate off all without ending the program. The final method is a timed stop. The timer is an "elapsed time" block in the true state of a case structure, which is controlled by a boolean button. When the button is pressed the case structure is set to a true state and the timer runs until a user indicated amount of time passes. At this point the VI HP 1 Outlet 1 OFF is run and the temperature regulation section subverted to turn off the hotplate for the rest of the run.
		+
		+	=Versions=
		+	==June 2017==
		+	Dr. Jones and I simplified the program somewhat. Previously, the program used a separate sub VI to turn the hot plate on and off. Dr. Jones replaced those VI's with a single VI called "HP Netbooter". I also had the program save the temperature data file to a folder on the desktop called "HotBoxDataSummer2017."
		+	==Earlier==
		+	[See the section "Program Logic" above.]

@@ Line 31: / Line 31: @@
 <br/><br/>
-File:GoUnlessTooHot2.jpg|200px|thumb|right|upright|GoUnlessTooHot2 VI, with the automatic option of manual controls showing.
+[[File:GoUnlessTooHot2.jpg|200px|thumb|right|upright|GoUnlessTooHot2 VI, with the automatic option of manual controls showing.]]
 The temperature regulation section serves to keep the box at a prescribed temperature. Here the code is centered around a user defined VI named GoUnlessTooHot2, which reads the user indicated target temperature and turns the hotplate on if the highest measured temperature is more than one degree fahrenheit below that value and turns it off if the highest measured temperature is more than one degree higher than that value. GoUnlessTooHot2 also has failsafes that check if there are zero and NaN values reported from the variable Highest temperature and if the box temperature exceeds 190 degrees Fahrenheit. If either of these conditions are met the VI will shut the hotplate off with the use of the VI HP 1 Outlet 1 OFF. GoUnlessTooHot2 is contained in the true state of a case structure that is controlled by a connected timer, which returns true once every ten seconds; the result is that GoUnlessTooHot2 only reads values from the variable Highest Temperature every ten seconds. Therefore, the hotplate state can only change at a maximum frequency of once every ten seconds. Having both a time constraint and a temperature range is redundant so the time dependence of the case structure should be removed, but the case structure itself should be left in tact as it has another function related to stop conditions. [[File:Timer.jpg|200px|thumb|right|upright|Timed stop case structure.]]
 <br/>The stop condition section is not as localized as the the other sections because the three ways to manually stop the hotplate are independent of each other. The first method of stopping the hot plate is the STOP button, which is the stop condition for the overarching while loop in the first frame; this terminates the while loop and ends the first frame of the sequence structure. The second frame of the sequence structure will then begin and shut off the hotplate and the program will end. The second method is in the manual controls. These controls determine the state of a case structure in the VI GoUnlessTooHot2, which can automatically regulate the temperature, turn the hotplate on, or turn the hotplate off all without ending the program.  The final method is a timed stop. The timer is an "elapsed time" block in the true state of a case structure, which is controlled by a boolean button. When the button is pressed the case structure is set to a true state and the timer runs until a user indicated amount of time passes. At this point the VI HP 1 Outlet 1 OFF is run and the temperature regulation section subverted to turn off the hotplate for the rest of the run.

@@ Line 31: / Line 31: @@
 <br/><br/>
-[[File:GoUnlessTooHot2.jpg|200px|thumb|right|upright|GoUnlessTooHot2 VI, with the automatic option of manual controls showing.]]
+File:GoUnlessTooHot2.jpg|200px|thumb|right|upright|GoUnlessTooHot2 VI, with the automatic option of manual controls showing.
 The temperature regulation section serves to keep the box at a prescribed temperature. Here the code is centered around a user defined VI named GoUnlessTooHot2, which reads the user indicated target temperature and turns the hotplate on if the highest measured temperature is more than one degree fahrenheit below that value and turns it off if the highest measured temperature is more than one degree higher than that value. GoUnlessTooHot2 also has failsafes that check if there are zero and NaN values reported from the variable Highest temperature and if the box temperature exceeds 190 degrees Fahrenheit. If either of these conditions are met the VI will shut the hotplate off with the use of the VI HP 1 Outlet 1 OFF. GoUnlessTooHot2 is contained in the true state of a case structure that is controlled by a connected timer, which returns true once every ten seconds; the result is that GoUnlessTooHot2 only reads values from the variable Highest Temperature every ten seconds. Therefore, the hotplate state can only change at a maximum frequency of once every ten seconds. Having both a time constraint and a temperature range is redundant so the time dependence of the case structure should be removed, but the case structure itself should be left in tact as it has another function related to stop conditions. [[File:Timer.jpg|200px|thumb|right|upright|Timed stop case structure.]]
 <br/>The stop condition section is not as localized as the the other sections because the three ways to manually stop the hotplate are independent of each other. The first method of stopping the hot plate is the STOP button, which is the stop condition for the overarching while loop in the first frame; this terminates the while loop and ends the first frame of the sequence structure. The second frame of the sequence structure will then begin and shut off the hotplate and the program will end. The second method is in the manual controls. These controls determine the state of a case structure in the VI GoUnlessTooHot2, which can automatically regulate the temperature, turn the hotplate on, or turn the hotplate off all without ending the program.  The final method is a timed stop. The timer is an "elapsed time" block in the true state of a case structure, which is controlled by a boolean button. When the button is pressed the case structure is set to a true state and the timer runs until a user indicated amount of time passes. At this point the VI HP 1 Outlet 1 OFF is run and the temperature regulation section subverted to turn off the hotplate for the rest of the run.

@@ Line 28: / Line 28: @@
 [[File:TempReg.jpg|200px|thumb|right|upright|Temperature Regulation Section centered on the GoUnlessTooHot2 VI.]]
-The initialization of the DAQ section leads directly into the temperature conversion and storage section. Here the voltage readings are converted to temperature in Fahrenheit with an equation block. The temperature values are then all merged into one wire connected to a waveform chart, which displays the temperatures separately on a line graph on the front panel. The combined signals are also sent to a user defined VI named TemperatureSpread, which stores the highest temperature out of all the signals in a variable called Highest Temperature. Each individual temperature value in fahrenheit is converted to celsius and displayed (in both fahrenheit and celsius) on the front panel. Additionally, each temperature in Fahrenheit is stored as a variable named after the location of its respective thermistor. These variables are combined and stored as one variable called WriteToFile (this section of the code is above the Initialization of the DAQ section at the time of this documentation). WriteToFile connects to a "save to measurement file" block, which itself is in a case structure that skips saving the data if there are zero or not a number (NaN) values coming from the DAQ.
+The initialization of the DAQ section leads directly into the temperature conversion and storage section. Here the voltage readings are converted to temperature in Fahrenheit with an equation block. The temperature values are then all merged into one wire connected to a waveform chart, which displays the temperatures separately on a line graph on the front panel. The combined signals are also sent to a user defined VI named TemperatureSpread, which stores the highest temperature out of all the signals in a variable called Highest Temperature. Each individual temperature value in fahrenheit is converted to celsius and displayed (in both fahrenheit and celsius) on the front panel. Additionally, each temperature in Fahrenheit is stored as a variable named after the location of its respective thermistor. These variables are combined and stored as one variable called WriteToFile (this section of the code is above the Initialization of the DAQ section at the time of this documentation). WriteToFile connects to a "save to measurement file" block, which is in a case structure that skips saving the data if there are zero or not a number (NaN) values coming from the DAQ.
 <br/><br/>

@@ Line 18: / Line 18: @@
 *Start Timer: On to start timer when the program starts, off otherwise. *Can turn this on at any point during run.<br/>
 Once all of these are set appropriately the run can begin. Pressing the LabView Run button on the tool bar will initiate all relevant processes and the hotplate will turn on within the first twenty seconds assuming the interior box temperature is less than the target temperature. When the netbooter is on and supplying voltage to the hotplate an indicator light on the front of the netbooter under "Power Outlet Status 1" will be on. If the program needs to be stopped in the middle of a run, the "STOP" button must be pressed; as a general rule do not end the program with the Abort Execution Labview button in the tool bar while the netbooter indicator light for outlet one is still on. If this does happen by accident, the program can be started again and the "STOP" button pressed while it is running.
 ==Program logic==

@@ Line 11: / Line 11: @@
 *Rate: 1 is sufficient here, increase for more data points.<br/>
 *Sample Mode: FiniteSamples<br/>
-*Save your file?: Pressed if you want to save the run, unpressed if you don't.<br/>
+*Save your file?: Pressed to save the run, unpressed otherwise.<br/>
 *STOP: Must be unpressed at program start.<br/>
 *Control Manually: Automatic<br/>

@@ Line 5: / Line 5: @@
 ==Instructions for a Heating Run==
-In order to calibrate the communication between the DAQ and the computer, the program InstaCal must be used. Open up instacal and right click on the DAQ, then click configure and there will be a drop down menu called number of channels in which 8 single ended mode should be selected and not 4 differential. This doesn't need to be done before every run, but it should be checked every time the DAQ is unplugged from the computer. Next, the physical setup must be appropriately configured. To set the hotplate temperature, plug it into a regular wall outlet and turn the knob until the temperature display reads 140 degrees Celsius, then unplug it. Plug the hotplate into outlet one on the correct netbooter (usually the top one) as the state of this outlet will be controlled by the program. Finally, plug all fans in and look to see that they are actually spinning.<br/><br/>
+In order to calibrate the communication between the DAQ and the computer, the program InstaCal must be used. Open up instacal and right click on the DAQ, then click configure and there will be a drop down menu called number of channels in which 8 single ended mode should be selected and not 4 differential. This doesn't need to be done before every run, but it should be checked if the program reports that the DAQ isn't responding. Next, the physical setup must be appropriately configured. To set the hotplate temperature, plug it into a regular wall outlet and turn the knob until the temperature display reads 140 degrees Celsius, then unplug it. Plug the hotplate into outlet one on the correct netbooter (usually the top one) as the state of this outlet will be controlled by the program. Finally, plug all fans in and look to see that they are actually spinning.<br/><br/>
 In order to perform a heating run there are a number of parameters, which can be found on the front panel, that must be set properly. The conditions for a normal run are listed below: