|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#16
|
|||
|
|||
|
Re: paper: LabVIEW Mecanum Programming
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
|
|||
|
|||
|
Re: paper: LabVIEW Mecanum Programming
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
|
|||
|
|||
|
Re: paper: LabVIEW Mecanum Programming
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
|
||||
|
||||
|
Re: paper: LabVIEW Mecanum Programming
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
|
|||||
|
|||||
|
Re: paper: LabVIEW Mecanum Programming
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". |
|
#21
|
|||
|
|||
|
Re: paper: LabVIEW Mecanum Programming
Last edited by xule : 15-05-2012 at 19:25. |
|
#22
|
|||||
|
|||||
|
Re: paper: LabVIEW Mecanum Programming
If you double-click on the error, it should take you to the Case structure having the missing cases.
There are only two Case structures, right? The inner Case structure (inside the outer Straight case) should contain the True case you showed, along with an empty False case. The outer Case structure should contain a case for every possible value of the Rotation_mode enumeration. You're only showing us the Straight and L1 cases. Are any of the others missing? |
|
#23
|
|||
|
|||
|
Re: paper: LabVIEW Mecanum Programming
|
|
#24
|
|||||
|
|||||
|
Re: paper: LabVIEW Mecanum Programming
Is there a blank in the enumeration list?
Sorry, I can't see your posted images. They get blocked where I am. Last edited by Mark McLeod : 16-05-2012 at 08:01. |
|
#25
|
|||
|
|||
|
Re: paper: LabVIEW Mecanum Programming
Thanks, that was it. A blank space in the enumerated list.
|
|
#26
|
|||||
|
|||||
|
Re: paper: LabVIEW Mecanum Programming
You mean the outer Case structure, the one having Rotation_mode as its selection input, right?
Double-check the list of possible values of Rotation_mode. Make sure there are only the five you expect. You might accidentally have inserted an unnamed value at the end. |
|
#27
|
|||
|
|||
|
Re: paper: LabVIEW Mecanum Programming
Thanks, that was it. Program runs.
|
|
#28
|
|||
|
|||
|
Re: paper: LabVIEW Mecanum Programming
Quote:
Last edited by Priyesh69 : 22-11-2012 at 16:22. |
|
#29
|
|||||
|
|||||
|
Re: paper: LabVIEW Mecanum Programming
There is no Block Diagram for Global Data, so ignore that.
Last edited by Mark McLeod : 22-11-2012 at 18:39. |
|
#30
|
||||
|
||||
|
Re: paper: LabVIEW Mecanum Programming
We purchased a Mecanum kit as an off-season project and played with the code last night. I believe there are some errors in the code, that I thought I would post here in case others also did not get the results expected.
First, let me thank you for taking the time to develop this, it was a huge asset with trying to get students to get the code working. Now to the issues. On page 14, I believe the feedback node needs to be outside of the case structure for "Straight"... What we saw is that the only way you can get into the "Straight" structure is for the rotate_mode to be equal to "Straight" and therefore the feedback node can only be equal to "Straight" and since they never not equal each other, you never update the "Header" value. When you add the PID on page 15, the PID now will unwind whatever rotation you do, because the Header is not updated, and stuck at the default, which we set to 0. So spin the bot 3 times CCW, and the let go of the sticks, the PID runs the 3 times CW and stops. The simple fix for this is to move the feedback node out, and the header updates correctly. On slide 17, when you add the case structure to make sure the rotate momentum is less than 10, this also breaks Header updating. As written the Header can only update the first loop after you took your finger off the sticks, so if you are spinning faster than the 10, the Header will not update, and if spinning slower than 10, you really didn't need this case anyways.... I have not fixed this one yet. It seems we almost need another enumeration state.. Say the joysticks put you in a "WaitingForStraight" and the case structure for WaitingForStriaght would check that rate less than 10 while sending 0 to the rotation, once the rate is less than ten we would write Straight to the "Rotate_Mode" I'll post back in a couple weeks on this fix, and debugging of page 21. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|