Heating Unit Controls - Revision history

Hrampanis: /* Oscilloscope LabVIEW Program */

2012-05-05T04:31:41Z

Oscilloscope LabVIEW Program

Hrampanis: /* Oscilloscope LabVIEW Program */

2012-05-05T04:24:33Z

Oscilloscope LabVIEW Program

Hrampanis: /* Oscilloscope LabVIEW Program */

2012-05-05T04:23:57Z

Oscilloscope LabVIEW Program

Hrampanis: /* Oscilloscope LabVIEW Program */

2012-05-05T04:22:28Z

Oscilloscope LabVIEW Program

Hrampanis: /* Oscilloscope LabVIEW Program */

2012-05-05T04:14:41Z

Oscilloscope LabVIEW Program

Hrampanis: /* Oscilloscope LabVIEW Program */

2012-05-05T04:09:54Z

Oscilloscope LabVIEW Program

Hrampanis: /* Oscilloscope LabVIEW Program */

2012-05-05T04:06:19Z

Oscilloscope LabVIEW Program

Hrampanis: /* Oscilloscope LabVIEW Program */

2012-05-05T04:03:53Z

Oscilloscope LabVIEW Program

Hrampanis: /* Oscilloscope LabVIEW Program */

2012-05-05T03:59:33Z

Oscilloscope LabVIEW Program

Hrampanis: /* Oscilloscope LabVIEW Program */

2012-05-05T03:41:12Z

Oscilloscope LabVIEW Program

@@ Line 179: / Line 179: @@
 There are a couple other things in the program that are shown but do not quite pertain to the actual data acquisition. The scales of “X” and “Y” of the graph are depicted in the LabVIEW program. And, a trigger rate is shown; the trigger rate gives a value in hertz which shows how quickly the program is executing. For the most part, the more parts of the program enabled, the faster it runs. The controls enabler and the graph display take up the most processing power.
 [[File:Front Panel Graph.png|200px|thumb|Graph]]
 [[File:Front Panel variables.png|200px|thumb|Variables]]

@@ Line 37: / Line 37: @@
 •	Library Function “sdSetFilt” – sets channel and filter trigger
-[[File:Frame 2.png|200px|thumb|right|Frame 2]]
+[[File:Frame 2.png|100px|thumb|right|Frame 2]]
 '''Frame 3:'''
@@ Line 57: / Line 57: @@
 •	Library Function “sdSetVoltageAndCoupling” – sets voltage and coupling of both channels of the oscilloscope
-[[File:Frame 3.png|200px|thumb|right|Frame 3]]
+[[File:Frame 3.png|100px|thumb|right|Frame 3]]
 '''Frame 4:'''
@@ Line 70: / Line 70: @@
 •	Library Function “sdGetLevel”
-[[File:Frame 4.png|200px|thumb|right|Frame 4]]
+[[File:Frame 4.png|100px|thumb|right|Frame 4]]
 '''Frame 5:'''
@@ Line 87: / Line 87: @@
 •	Library Function “sdSetOffset” – adjusts the position of the channel
-[[File:Frame 5.png|200px|thumb|right|Frame 5]]
+[[File:Frame 5.png|100px|thumb|right|Frame 5]]
 '''Frame 6:'''
@@ Line 99: / Line 99: @@
 •	Library Function “sdCaptureStart” – starts to capture data from the oscilloscope
-[[File:Frame 6.png|200px|thumb|right|Frame 6]]
+[[File:Frame 6.png|100px|thumb|right|Frame 6]]
 '''Frame 7:'''
@@ Line 111: / Line 111: @@
 •	Library Function “sdTriggerEnabled” – sets the trigger
-[[File:Frame 7.png|200px|thumb|right|Frame 7]]
+[[File:Frame 7.png|100px|thumb|right|Frame 7]]
 '''Frame 8:'''

@@ Line 21: / Line 21: @@
 *(Note: The library functions are .DLL files and it requires decoders, usually in C++. Therefore, it is not quite possible to see exactly what the function is doing, but if the parameters fit the success criteria the output is either a 1 for success or 0 for failure. The inputs of the library functions are also preserved.)
-[[File:Frame 1.png|200px|thumb|right|Frame 1]]
+[[File:Frame 1.png|100px|thumb|right|Frame 1]]
 '''Frame 2:'''

← Older revision		Revision as of 04:22, 5 May 2012
Line 179:		Line 179:

	There are a couple other things in the program that are shown but do not quite pertain to the actual data acquisition. The scales of “X” and “Y” of the graph are depicted in the LabVIEW program. And, a trigger rate is shown; the trigger rate gives a value in hertz which shows how quickly the program is executing. For the most part, the more parts of the program enabled, the faster it runs. The controls enabler and the graph display take up the most processing power.		There are a couple other things in the program that are shown but do not quite pertain to the actual data acquisition. The scales of “X” and “Y” of the graph are depicted in the LabVIEW program. And, a trigger rate is shown; the trigger rate gives a value in hertz which shows how quickly the program is executing. For the most part, the more parts of the program enabled, the faster it runs. The controls enabler and the graph display take up the most processing power.
		+
		+	[[File:Front Panel Graph.png\|200px\|thumb\|Graph]]
		+	[[File:Front Panel variables.png\|200px\|thumb\|Variables]]

@@ Line 1: / Line 1: @@
 === Oscilloscope LabVIEW Program ===
 '''Frame 1:'''
@@ Line 22: / Line 21: @@
 *(Note: The library functions are .DLL files and it requires decoders, usually in C++. Therefore, it is not quite possible to see exactly what the function is doing, but if the parameters fit the success criteria the output is either a 1 for success or 0 for failure. The inputs of the library functions are also preserved.)
-[[File:Frame 1.png|Frame 1]]
+[[File:Frame 1.png|200px|thumb|right|Frame 1]]
 '''Frame 2:'''
@@ Line 38: / Line 37: @@
 •	Library Function “sdSetFilt” – sets channel and filter trigger
-[[File:Frame 2.png|Frame 2]]
+[[File:Frame 2.png|200px|thumb|right|Frame 2]]
 '''Frame 3:'''
@@ Line 58: / Line 57: @@
 •	Library Function “sdSetVoltageAndCoupling” – sets voltage and coupling of both channels of the oscilloscope
-[[File:Frame 3.png|Frame 3]]
+[[File:Frame 3.png|200px|thumb|right|Frame 3]]
 '''Frame 4:'''
@@ Line 71: / Line 70: @@
 •	Library Function “sdGetLevel”
-[[File:Frame 4.png|Frame 4]]
+[[File:Frame 4.png|200px|thumb|right|Frame 4]]
 '''Frame 5:'''
@@ Line 88: / Line 87: @@
 •	Library Function “sdSetOffset” – adjusts the position of the channel
-[[File:Frame 5.png|Frame 5]]
+[[File:Frame 5.png|200px|thumb|right|Frame 5]]
 '''Frame 6:'''
@@ Line 100: / Line 99: @@
 •	Library Function “sdCaptureStart” – starts to capture data from the oscilloscope
-[[File:Frame 6.png|Frame 6]]
+[[File:Frame 6.png|200px|thumb|right|Frame 6]]
 '''Frame 7:'''
@@ Line 112: / Line 111: @@
 •	Library Function “sdTriggerEnabled” – sets the trigger
-[[File:Frame 7.png|Frame 7]]
+[[File:Frame 7.png|200px|thumb|right|Frame 7]]
 '''Frame 8:'''
@@ Line 166: / Line 165: @@
 •	Library Function “sdSetVoltageAndCoupling”
-[[File:Frame 8.png|Frame 8]]
+[[File:Frame 8.png|200px|thumb|right|Frame 8]]
 ''Function of the Program:''

@@ Line 11: / Line 11: @@
 •	Control_Data1
 •	PulseTrigger
 ''Functions-''
@@ Line 23: / Line 21: @@
 *(Note: The library functions are .DLL files and it requires decoders, usually in C++. Therefore, it is not quite possible to see exactly what the function is doing, but if the parameters fit the success criteria the output is either a 1 for success or 0 for failure. The inputs of the library functions are also preserved.)
 '''Frame 2:'''

@@ Line 15: / Line 15: @@
 •	Unbundle – takes the values in a cluster and returns separate elements within the cluster as 1-dimensional values
 •	Bundle - takes multiple 1-dimensional values and combines them into a cluster
 •	Library Function* “sdSetTriggerAndSampleRate” – sets up a trigger to initialize other functions in the program as well as the time interval of data acquisition.
@@ Line 31: / Line 33: @@
 •	Unbundle
 •	Library Function “sdSetFilt” – sets channel and filter trigger
@@ Line 48: / Line 51: @@
 •	Library Function “sdGetLevel” – reads waveform position adjust data from the oscilloscope
 •	Library Function “sdSetVoltageAndCoupling” – sets voltage and coupling of both channels of the oscilloscope
@@ Line 127: / Line 131: @@
 •	Bundle
 •	Unbundle
 •	Build Array – creates a multidimensional array from building multiple 1-dimensional arrays.
 •	Subset Array – creates an array of the length of all the input indices
 •	Write to Binary File – writes the data of the program to a file
 •	Waveform graph – creates a graph with plots from an input array.
 •	Library Function “sdGetData” – reads data from the oscilloscope
 •	Library Function “sdSetFilt”
 •	Library Function “sdSetTriggerAndSampleRate”
 •	Library Function “sdSetOffset”
 •	Library Function “sdSetVoltageAndCoupling”
-Function of the Program:
+''Function of the Program:''
 	Frames 1-7 of the LabVIEW program for the oscilloscope are part a flat sequence structure. It was most likely set up like this for organization and to ensure all of the functions and subVIs fire in the correct order. The first 7 frames are for initializing the data acquisition and the 8th fame has the bulk of the program functionality.
@@ Line 146: / Line 160: @@
 The majority of Frame 8 is immersed in a “while” loop, which continues unless stopped. The first half of the “while” loop is inside of a case structure which is enabled or disabled by the push of a Boolean push-button; by disabling this case-structure, it makes the program run faster because there is no need to process data that need not be inputted. A case structure is wired to the CH1_Voltage variable; the case structure has a numeric value inside which changes to whatever the CH1_Voltage is equal to. Another case structure is set up in the same manner but the variable is for channel 2 (CH2_Voltage). CH1_Voltage and CH2_Voltage are compared to CH1_Att and CH2_Att respectively; if the channels’ voltages are not equal to each other, a Boolean value of true is produced and sent to an “or” comparator. The “or” comparator sends a value of true or false to another case structure which when “true,” sets voltages and couplings via the function “sdSetVoltageAndCoupling,” otherwise when false, funnels the CH1_Voltage and CH2_Voltage straight through. Concurrently, Ch1Lever, Ch2Lever, Ch1TrigLever, and Ch2TrigLever are bundled with the “Lever” cluster to create a larger cluster. This cluster with the CH1_Voltage, CH2_Voltage, DeviceIndex, Trigger Source, and Level are put into the Library Function “sdSetOffset.” From this, Trig_Source and TIMEBASE are bundled with Control_Data1 into a cluster.
 Most of the data is then wired into another flat sequence structure for two frames; Pulse_Trigger is unbundled into 1-dimensional arrays and wired to the function “sdSetTriggerAndSampleRate” along with DeviceIndex, TriggerSlope, ETS, and the bundled TIMEBASE and Trig_Source. The data is then moved to the second frame in this sequence where the DeviceIndex and FiltAndTrigger are put into the function “sdSetFilt.”
 The last part of “initialization” is the funneling of all of the variables listed including data_tab_ch1 and data_tab_ch2, and a constant 0 into the “sdGetData” function, which sends the appropriate data to show on the waveform graph. This last half of the “while” loop has a sequence of case structures that may be disabled via use of push-buttons. If the return value of the “sdGetData” function has a successful value of 1 it then enables the next case-structure. The data from channel 1 of the oscilloscope then wired to two separate case-structures, one which is sent to a “write to file” function and the other to a graphing function. The case-structure which contains the “write to file” function can be enabled or disabled by a switch; the data is wired to an “array subset” function with the “length” as the length of the subset array and the “X Minimum” is the index. The last portion of the work of the program deals with the case-structure which contains the graphing function. The data from channels 1 and 2 are into a build array function and put into a “waveform graph” function, which can also be enabled or disabled via button. The data of the program is then put into a shift-register, which preserves the data and reuses it as starting values at the beginning of the register.
 There are a couple other things in the program that are shown but do not quite pertain to the actual data acquisition. The scales of “X” and “Y” of the graph are depicted in the LabVIEW program. And, a trigger rate is shown; the trigger rate gives a value in hertz which shows how quickly the program is executing. For the most part, the more parts of the program enabled, the faster it runs. The controls enabler and the graph display take up the most processing power.