0

What is the best way to understand a complex LabView VI that controls a motor?

My goal is to control the motor from a joystick.

The wiring diagram shown below allows a LabView user to control the motor from the LabView GUI: move a slider up and down either increasing or decreasing the desired velocity. As the slider's value changes, it is fed into a bunch of math controls and eventually gets converted into a command string for the motor to interpret. This command string, if I understand correctly, is bunch of bytes that get written to the serial port.

Instead of using the LabView GUI to control the motor, I would like to use the joystick.

What is the best way to approach this?

The joystick has pitch,yaw,roll,and throttle. Which one relates best to the velocity of a motor?

enter image description here

user1068636
  • 1,871
  • 7
  • 33
  • 57
  • 2
    What is your question? The title does not relate to the final question. The code you have lacks documentation, I would start by creating subVIs that encapsulate the mathematical functions, so you get a defined set of inputs and outputs. Then I would print the diagram on an A3 sheet and handwrite comments to the code and the wires. One thing to mention is that your code runs inside a timed loop so the code has a dedicated speed. To understand this VI, you should start using probes. – Ton Plomp Mar 27 '13 at 08:34

3 Answers3

2

The answer to your title "What is the most efficient way to quickly understand how a complex LabView VI works?" is probably to do some combination of the following:

  • Look at the VI's inputs and outputs to try and understand what they are there for. The label and caption of controls and indicators may be helpful, also right-click to check the description and tip.
  • As well as controls and indicators, look for other I/O: queues, notifiers, global variables, file read/writes, instrument communications, and for any data storage that persists between calls such as an uninitialised shift register.
  • Look at the overall structure of the VI to see how it executes, e.g. is it a one-off operation, does it execute different cases depending on some input, does it loop until a certain condition happens, does it use a state machine structure, etc
  • Break down the VI's structure into smaller pieces that you can understand. You could print the diagram out and annotate it by hand, or add frame decorations and text comments to the diagram to record what you deduce. If the diagram is cluttered or poorly laid out, rearrange it as you go along (use Ctrl-click and drag on the diagram background to add blank space where you need it).
  • Set probes on key wires and watch them while the VI runs to see what happens
  • If possible, manually set the VI's controls to example values and run it to see what happens (this may not work if the VI depends on other parts of a program running at the same time)
  • Write a test wrapper VI that calls the complex VI and supplies it with example data or inputs to see what happens.

To address your specific question about the VI diagram you've posted, I can see various controls for quantities such as Velocity, Position, Amplitude, Max A (amplitude?), Frequency and so on. You need to decide which of these quantities should be controlled by which axis or output of your joystick. Then you need to add code that reads those values from your joystick, and modify the existing code so that the parameters you want to control are supplied by the joystick values instead of the front panel controls. You could probably just put the joystick reading code inside the existing loop, wire the joystick outputs to join up with the wires from the front panel controls you want to replace, and then change the relevant front panel controls to indicators from the right-click menu so that they will show the values you are getting from the joystick.

nekomatic
  • 5,988
  • 1
  • 20
  • 27
1

The best way is to write one from scratch. But you could analyse the code by clicking the Highlight Execution button to display an animation of the block diagram execution when you run the VI, and use probes to check intermediate values. And you probably should also do an on-line course, e.g. LabVIEW Training: Learn LabVIEW in Three or Six Hours

Jakub Czaplicki
  • 1,787
  • 2
  • 28
  • 50
1

My answer to your third question is "throttle.".

jcarmody
  • 205
  • 1
  • 4