What you need to do is wire draw the C1p33_DigOut onto another/bus leg and call it whatever you want, I would recommend putting a RETYPE function in-between the C1p33_DigOut and whatever you new name is in case you intend to change the new name again this will make it easier.

You can then reference your new name anywhere in the program, and that will be connected to the C1p33_DigOut.

I have an MC050-010 with a simple speed sensor and I'm trying to get speed and distance.  The speed (frequency) is accurate but when I get over 25hz the pulse count is not keeping up.  What am I doing wrong?

Hi all,

I am attempting to write a simple program that replaces the old PAM cards in one of our test stands with a Plus 1 controller. A couple of the throttle valves (Vickers CVU16 EFP1 B29 1931 with an analog control card EEA-PAM-571-A-32) use LVDT feedback on the PAM card.

Is there a good valve control block that could be dropped in for this application? All of the blocks appear to be very valve specific and I am unsure if it matters which one I choose.

Thanks!

Hello,

If you use the regular Scale component it's important to understand that the values you enter are not end points, the line keeps going in both directions (see image ScaleLine.png).
In the user manual for the Scale component you can read that the values (A2 - A5) do not limit the resulting output value (see image ScaleComponent.png). The risk of an overflow is imminent if you don't know what kind of signal you have.

And as BRIan pointed out, a capped component will solve this. On the capped component the output value is clamped to Max or Min value in case of an overflow (see image ScaleCappedComponent.png)

All the images and examples can be found in the component user manual.
To find the Online User Manual for the component, mark the component in the component tree and press F1 on the keyboard, or Query the component in the drawing area and click the question mark in the top right corner.


Have a nice day.

Hello.

I ran into an interesting issue today.

While using the scale function in Guide, if the input is out of the minimum value, or the max value, the output becomes undefined.
Took me a while to figure out what was going on. This is not mentioned in the documentation as far as I can see.

For a solution to this problem I did the following (see attached screenshot)