LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

I received a new VI, but I'm not sure how to build or organize it.

I received a new VI, but I'm not sure how to build or organize it.

I’m planning to build a system using this VI to control the motor and perform measurements. I’ll also refer to the example VI below — could you help me structure it in a similar way?

Download All
0 Kudos
Message 1 of 4
(250 Views)

A "new Vi" is typically an empty VI.

 

You received a zip file with a set of drivers and an absolutely horrible VI full of race conditions, deeply stacked sequences, disconnected terminals, tons of local variables, and event cases with extensive inner code. Do you know who wrote it? Maybe ask them.

 

What are the requirements for the program you are trying to write? You probably should start from scratch, maybe based on the example included with the drivers.

 

0 Kudos
Message 2 of 4
(204 Views)

I received the zip file to use a rotation motor.
I would like to create a program that rotates the motor using the VIs from the zip file, detects signals with a photodetector, and records the data through a DAQ device.

However, the existing VIs are quite difficult to understand and seem overly complicated.
Could you help me simplify or rewrite the program so that even a beginner like me can understand and use it more easily?

0 Kudos
Message 3 of 4
(156 Views)

@altenbach wrote:

You received a zip file with a set of drivers and an absolutely horrible VI full of race conditions, deeply stacked sequences, disconnected terminals, tons of local variables, and event cases with extensive inner code. Do you know who wrote it? Maybe ask them.

A classic case of Localitis and Sequentitis. The original developer is clearly a text based programmer.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 4 of 4
(129 Views)