06-13-2011 03:14 PM
In the wait state when the iterations greater than or equal is true I reset the graph by sending a null cluster to the shift register. It never did that before.
06-21-2011 09:52 AM
Everything is working great but I am trying to add in a functionality of writing the current time and date to the file. I just would like the date and time to be written for the start of each cycle. I am not sure how to do this. I found a VI that prints out date and time but I am haveing trouble wiring that to the save file.
06-21-2011 10:14 AM
This is the easy way. It will give you seconds elapsed since 12:00 a.m., Friday, January 1, 1904, Universal Time. If that is not good enough then we can do something else.
07-05-2011 03:31 PM
Alright hopefully the final change. We were trying to communicate with a furnace that is holding our device to make the cycle start over each time a temperature is reached but without success so we are going to have the furnace take X amount of time to ramp up to the next temperature and therefore in the wait state of our program have it wait the same X amount of time (plus the time it takes for a cycle of our program) and start a new cycle.
So eliminating or maybe in addition to the start and stop buttins either way is it possible to have the cycle restart after a multiple of x seconds for example? and wait for the next "iteration" of X seconds to start again?
07-06-2011 07:24 AM
@Kenneth22 wrote:
Alright hopefully the final change. We were trying to communicate with a furnace that is holding our device to make the cycle start over each time a temperature is reached but without success so we are going to have the furnace take X amount of time to ramp up to the next temperature and therefore in the wait state of our program have it wait the same X amount of time (plus the time it takes for a cycle of our program) and start a new cycle.
So eliminating or maybe in addition to the start and stop buttins either way is it possible to have the cycle restart after a multiple of x seconds for example? and wait for the next "iteration" of X seconds to start again?
So are you just looking for an off and on again for X time verses the 25 steps that we orginally programmed?
The way I understand what you are asking for is:
Run the 25 iterations
Wait X seconds and restart 25 iterations?
Is this what you are looking for?
07-06-2011 09:45 AM
What Keithly are you using? I am going to try and get the vi that you are using to allow me to run the code.
07-06-2011 10:02 AM
Yes that is correct run 25 iterations wait x seconds then run 25 iterations wait x seconds etc. I am using three keithley 2100 multimeters
07-06-2011 01:06 PM
OK I changed a lot in the program. I believe that the way I changed the communication to the Keithly should work better. If you have problems with it let me know. I changed the layout of the front panel to make it easier for an operator to understand. You can also make the VI start when you open the vi so that the operator does not have to do that. I added that loop feature on the page after you press the done button.
If you have problems let me know and we can see what we need to do to fix them.
07-06-2011 01:09 PM
Sorry I forgot you need a lower version of LabVIEW.
07-06-2011 01:43 PM
Looks great I shouldve given you my newest version sorry. I added back in some of the functions that I had previously added and have it mostly working one poblem it is only displaying data for keithley 1 not 2 or 3 but it is recording the data in the file. Also in the process data state i had previously added the slope calculator to only work on steps 1-12 and stop calculating slope for the rest of the steps as it throws the fromula off for later. Do you have any ideas how to consistently reset the clock after it has reached the 12th step? I will add in my old newest version and the re-done one today so you cn hopefully see what I mean.