paper: LabVIEW Mecanum Programming

programming
mecanum
labview
#1

Thread created automatically to discuss a document in CD-Media.

LabVIEW Mecanum Programming
by: Jogo

This tutorial is a step-by-step implementation of mecanum drive in LabVIEW.

This tutorial is a step-by-step implementation of mecanum drive in LabVIEW. It is between beginner and intermediate LabVIEW, so it assumes some experience with LabVIEW and control loops.

Questions and comments are encouraged.

mecanum1.1.pdf (880 KB)

#2

**
Nice presentation. This should prove helpful to teams just getting started with LabVIEW and mecanum.

There’s a small error on Page 19 which may lead some astray:

Wouldn’t it be convienient to–on the push of a button–rotate to the direction you’re traveling?
:black_small_square:To calculate this angle, do Math.atan2(Joystick X, -Joystick Y)
:black_small_square:Implement a PID loop–the setpoint is the joystick angle, and the process variable is the gyro angle

The above won’t work very well. The joystick angle will be -180…+180, and the gyro angle will be 0…360+

You can’t just pass the joystick angle and gyro angle to the PID as-is. The PID will not like that at all.

For example, if the joystick angle is -1 degree and the gyro is reading +359 degrees, the PID will calculate (and act upon) an error of -1-359 = -360 degrees… even though the vehicle is already pointing in the desired direction.

To use the LabVIEW PID in this situation, you need to do something like this:

angle_error = joystick_angle - gyro_angle;
angle_error -= 360*floor(0.5+angle_error/360);
setpoint = gyro_angle + angle_error;
process_variable = gyro_angle;

Example LabVIEW code for the second line in the code block above can be found here.

**

#3

Thank you Ether. I added in a solution that I used but neglected to include in the first version. Now that I look at your solution closer, however, yours seems a great deal more elegant.

#4

I have a question on slide 9; what is the blue thing within the case structure? Sorry 1st time programming mechanum drive. Very helpful presentation

#5

I don’t know what it is you’re referring to. Can you describe the “blue thing” a little better? Blue typically means an integer value.

#6

Sorry about that; I mean in the true/false case structure, there is the"blue thing" that says"L1 rotate_mode." My question is where is that located in labview?

#7

rotate_mode is a global variable that was defined on the immediately preceding slides. L1 is an enumerated constant that was obviously created by right-clicking the input terminal of the variable and choosing Create Constant.

#8

Hello,

I did all the steps in page 8, but can not get my robot global data to read the “rotate mode” enum. Any help would be appreciated.

Thanx,

David

#9

I’m not sure what you mean. The robot global data doesn’t “read” or “write” the values. It just provides a place that contains them.

Are you trying to say you can’t get the global variable to appear on the Teleop block diagram?

#10

Yes sir. That is what I meant. I defined it’s values in the Robot Global Value.vi but they won’t show in teleoperated.

Thanks,

David

#11

It’s not exactly obvious how to place a reference to an existing global variable. Here’s how to do it:

Right-click on an empty spot in the block diagram to call up the function palette. Choose “Select a vi…” and navigate to the folder containing your robot project. Open “Robot Global Data.vi” and you’ll have a global variable attached to your cursor (it will likely be named “Enable Vision” – don’t worry about it). Click to place that variable on the block diagram. Now you can click on the middle of the variable to bring up a list of all the globals that are part of the Robot Global Data vi. Choose the one you want.

The default is to make a “write” reference. To change it to “read”, right-click on the variable and choose “Change To Read”.

#12

Okay. I got the global variable to show up, and I can connect the constant to it. But when I change the global variable to read, I can’t connect my constants anymore. Did I totally mess up somewhere? This is my third year programming, but I’ve never messed with the global robot data vi.

Thanks,

David

#13

If you want to put a constant in the global variable, you need to write to it. You would read it if you want to do something with the value it contains.

#14

Okay. On to page 14 :slight_smile: I’m getting tired of asking questions. But thanks to everyone for your help. The rotate mode runs into the case structure and then connects to the symbol I can’t seem to find. It’s blue with an arrow and a box with a circle under it.

Also, do need to create a global variable called “header”? If so, what properties does it need to have?

And… what is connect to the PID on page 15?

Thanks again,

David

#15

It’s called a Feedback Node. You will find it in the Programming>Structures function subpalette. Its output is the value that was connected to its input the previous time through the loop. It changes color based on what type of data it’s connected to; in this case it’s blue because the data is an (enumerated) integer type.

(The Feedback Node look has changed slightly between LabVIEW 8.6 and LabVIEW 2011. The “box with circle” is now a wider box with an asterisk.)

#16

Thanks for all your help. I’ve got a few more questions here, and then I think I’ll have it.

Do I need to create a global variable called “header”? If so, what properties does it need to have?

And… what is connected to the PID on page 15?

Thanks again,

David

#17

Hello David. You do need to add a global variable called “header” (numeric), which is used to store the gyro angle each time rotate_mode changes to “straight”.

For tuning the PID function, first right click on the “PID gains” terminal and add a control or a constant, and follow the instructions on page 16. There are plenty of good resources around the web for PID tuning specifics: http://zone.ni.com/devzone/cda/tut/p/id/3782.

If you have more implementation-specific questions, feel free to PM me.

#18

Ok My names Ernesto
I am still stuck on the global header and would like to ask if you could explain more on how to make it.

#19

I am also trying to figure out the global variable header. I wasnt sure where to create it or how. So i created a numeric and then create a local variable from the numeric and called it header and used that within my teleop code. Will this work or do i need to create a global somehow?

#20

The Robot Global Data.vi is where you create global variables (if you need them). It’s only a front panel, with no block diagram. Place (or paste) a control of the appropriate type on the front panel, then right-click it and make its label visible if it isn’t already. Change the label to whatever name you want the global variable to be.

To use a global variable, you can either copy one from elsewhere, or use the “Select a VI” item in the function palette to pick the Robot Global Data. You’ll end up with something on your block diagram with a popup menu that lets you choose among all the globals. You can use the right-click menu to make it a “read” or a “write”.