LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

propotional flow control valves

Thanks

 

It seems the file’s mad in 2013 version. Could anyone please save it as 2011 or 2012 file.

 

Thanks 

 

Rajab 

0 Kudos
Message 11 of 21
(1,317 Views)

Here is a LV 2010 snippet.

0 Kudos
Message 12 of 21
(1,312 Views)

Sorry  

 

it's still showing me that the file is in 2013 version 

 

Thanks 

 

Rajab 

0 Kudos
Message 13 of 21
(1,304 Views)

Sorry about that.  I thought when I set the snippet to LV 10  (I'm actually using the Code Capture Tool), it saved it backwards.  I was mistaken.

 

Here it is as a .vi.

0 Kudos
Message 14 of 21
(1,298 Views)

2011 attached

 

Again this is only one example of how I used som EPVs.  your system will have its own requirements.


"Should be" isn't "Is" -Jay
0 Kudos
Message 15 of 21
(1,297 Views)

Hi 

 

Thanks for your help.

 

 Is this code designed to fully open the valves or for proportional control??  How to control the case structure (commands)  was it mad as type def control??  The file’s not attached with the main vi.

 

Could you please explain to me in more details the purpose of the vi?

 

Best Regards 

Rajab 

0 Kudos
Message 16 of 21
(1,286 Views)

Jeff,

 

Double check your VI.  It looks like you are trying to do a conversion to 4-20 mA.  But your scaling factor should be .016 rather than .00016 in that case. before adding to .004

0 Kudos
Message 17 of 21
(1,277 Views)

Thanks for the review Bill but the Data Out Scaled is in % open (0-100) it scales fine to 4-20 e-3 or the default -25%= (0mA):smileywink:


"Should be" isn't "Is" -Jay
0 Kudos
Message 18 of 21
(1,271 Views)

Okay.  I didn't realize you had it scaled to 0-100.  I thought you may have already divided by 100 earlier.  Like you were working with a value that was already a fraction of the range.  I only was looking at MixB case and didn't know the divide by 100 was included in the scale factor with the constant for the 16mA.

0 Kudos
Message 19 of 21
(1,262 Views)
I'm not really clear on the goal here. If you want to use a sophisticated proportional control setup, you need valves that can be set to a precise open level, and you need analog outputs. Both of these are likely to increase the cost and complexity of your setup substantially. Since it sounds like you will just face small changes in flow, and since the changes are likely to be continuous, and since the response time will likely be limited by the speed of the valves, and since you want to use digital outputs, you really should just use a open/off/close type valve and change it's state using digital outputs based on whether your flow is under/equal/over your target flow.

In this case, the only reason to use PID is if you are worried about the duty cycle on the valves and you want to use a timer setup, where you, for example, check the flow status every two minutes and then run the valve forward or backward for X% of the next two minutes based on how far away it is from the setpoint. However, I doubt that's a big concern for this type of motor, and anyway you could more easily achieve the same goal (and preserve your ability to respond to sudden large changes) by just increasing the allowable error on the setpoint or reducing the loop speed.
0 Kudos
Message 20 of 21
(1,246 Views)