10-12-2016 09:52 AM
Hi there,
I am slowly getting a bit more familiar with LabView and feel confident enough to code for an ISCO Pump (model 100dx).
My pump has two syringes, and I'd like to display the ammount of fluid contained in those pumps - continuously.
So far I've tried what's on my snippet (tank A & B)
I beleive there is a more elegant way to send a command at every loop. Thank you for your help 🙂
Flo
Solved! Go to Solution.
10-12-2016 10:32 AM
Tank A's terminal belongs inside the loop rather than using a local variable. (The read local variable write to terminal outside the loop only happens once, and it otherwise pointless. That's like say Let x=x in a text based language.
Beyond that, I don't understand your question.
What I do see is that you have an event structure there. That loop only iterates whenever an event happens, which means reading the tank A and B values onlyi happens when an event happens. You might want to wire in a timeout value to the event structure so that it will execute the timeout case (even if you do nothing in it) and it will iterate the loop again to read the tank A and B values.
10-12-2016 10:48 AM
I must have been more specific: my syringes see their contain varying all the time throughout my experiment (their are receiving and giving fluids). So I would like to see those changes over my tank indicator.
The only problem is that I have to send a command to get that information, and as you said, the while loop will loop if an action is done by the user.
Let me know if you need further explaination
Flo
10-12-2016 10:56 AM
So do what I said and wire up a value to the timeout terminal of the event structure.
10-12-2016 10:58 AM
10-13-2016 04:28 AM
I tired to add a timeout event, but everytime I trigger an action (run the pump, or whatever action), it fails....
Flo
10-13-2016 04:34 AM
10-13-2016 05:30 AM
I did yes, and besides clcking on a run button I don't generate that much event.
Basically what's happening is that every other case event which contain a WRITE/READ function fails to send that command. the error message is -107something (sorry I am not in the lab this morning).
Flo
10-13-2016 08:22 AM
You will need to attach your latest VI. Somehow I don't think you implemented things the way we said.
10-13-2016 08:36 AM
Here you go 🙂