04-23-2007 06:48 PM
04-24-2007 04:27 AM
Hi Alison,
Can you repost the VI saved for LV 7.1 ?
I think I can provide you a solution once I see the code. ![]()
04-24-2007 05:24 AM
04-24-2007 07:53 AM
GerdW,
thanks a lot for your help. I appreciate the improvements! Anyway, I'm still sort of confused. how would you suggest fixing the adding and subtracting problem? If I am testing teh wrong values how would i fix that? Thanks again,
alison
04-24-2007 08:17 AM
04-24-2007 08:21 AM
Partha,
thanks for your help. Here is the code in labview 7.1. I hope you can help me out!! Is there some sort of switch that will toggle between two values whenever it recieves a true value or something. The case structure I'm using has an assigned true and false, but I don't want each case to have an assigned true or false value because as soon as they go false, I want to switch to the other curve.
THANKS!!
Alison
04-24-2007 08:28 AM
GerdW,
Doesn't the offset into the simulate signal VI make the VI change its value as it grows and shrinks? When i run the curve the offset varies between 0 and 9.8, so i think the second comparison is necessary to protect the DAQ. Or is there something else that I'm missing? I'm a total novice, so I'm making things up as I go along.
Thanks,
Alison
04-24-2007 08:33 AM
04-24-2007 08:37 AM
GerdW,
So, how would I make adiagram constant that would has some sort of offset? But more importantly, is there some sort of way in which I can toggle between what would be my two cases of the case structure each time the shift register power value is greater than the newer power value? So essentially a switch that turns on whenever a false reading comes on? Thanks again and again,
Alison
04-24-2007 08:51 AM
Hello Ambrownster,
i have looked at your vi, which seem interresting. however i have several remarks, some of them already pointed in this thread:
1)i understand you try to make some kind of PID regulation on your output board as a function of input (PID stands for proportional, integrator, derivative feedback). you could then try to make a little more elaborate response to your output dependant not only on the direction of change but also its violence (rate of change), and correct for offset.
2) try not to use express vis and dynamic data conversion. also, try to minimise nb of operations (*, ^2, /...) when possible.
3) i strongly suggest avoiding feedback nodes in case you are not totally sure what value it will have, expecially at the first iteration of the loop.
4) your card is going to send 10V out no matter what higher input you give (if you put 15V, your card cannot deliver such value). i would simply propose to use a "in range and coerce" function if you want to keep track of the value.
all the best