Page History

LINK LINK TO MEASURING VI

LINK TO RESPONDING VI

...

***When you initialize the valve position, it is important that the valve be completely closed, and that zero is set as the initial position. If this is not done successfully then there is a risk of the valve overturning and breaking. Likewise, the constant velocity should not be too fast in order to prevent the valve from slipping while the program is running.***

init.vi

init.vi, short for initialize.vi, initializes

initializes the motor

...

by writing that motor to the VISA.

microstep_revolution.vi

writes a constant "number" to the VISA.
"number" is the _________.

setvelocity.vi

getposition.vi

Image Removed Image Removed

to_turns.vi

writes the constant "Velocity" to the VISA.
"Velocity" is the speed at which the motor spins.

getposition.vi

Image Added Image Added

using the VISA indicated, this VI tells the user if the VISA is able to be used or not by indicating if "Is Null?" is true or false.
- True: the bool is activated and the VISA is null, and therefore not able to be used.
- False: the bool remains inactive and the VISA is not null, and therefore can be used.
The VISA can be null if one of two scenarios are true:
- if the number of bytes available at the VISA's port is equal to zero AND/OR
- if the valve position returned is not readable to the VI.
If both of these cases are false, then the VISA is not null and the valve position is returned.

to_turns.vi

Image Added

uses predefined global variables to convert from the number of steps, which is how LabVIEW reads the change in height of the valve, to the number of turns, which is how the motor knows how much to open.
basically this VI uses a conversion to create a number that is readable to the motor.

Image Removed

to_steps.vi

this VI uses the same idea as to_turns, but it converts the other way around, therefore converting the valve's change in position into a number readable to LabVIEW.