Re: Mecanum - use of gyro
 

Greg,

I'm curious....why does the PID.vi itself use a regular while loop, rather than a timed loop?

Re: Mecanum - use of gyro
 

In this case, the While loop is actually not used to loop the PID function (if it were, the PID function would never get new inputs). It is instead simply for its shift registers. Note that the loop is set to end on the first iteration, and none of the shift registers are initialized (meaning they retain their values between calls).
It is also a reentrant VI, storing the shift register data separately for each instance.

The other way to accomplish this is to use feedback nodes (found in the structures palette). However, shift registers often create cleaner and more readable code, and so are more commonly used.

Re: Mecanum - use of gyro
 

Since the PID VI is a subVI, it is intended to be placed after the sensor and before the actuator. Placing this into a user's loop, timed loop, or callback lets the user control the timing and priority. If these are placed into a timed loop set at a higher priority, the PID and other VIs will inherit the higher priority.

If this were flipped and the PID were an object that owned the loop, you could do this by registering the sensor, actuator, timing, priority, and other elements with it. I believe this is how it was done with Java and C++.

I'm assuming this was useful because the PID may need to spin up a new thread and this handles it for the user. Meanwhile in LV, it is easy to draw a parallel loop if that is what you want.

Different strokes.
Greg McKaskle

Re: Mecanum - use of gyro
 

bump.

@mwsmith78: haven't heard from you in almost 2 weeks. could you give us an update on where you're at with this? did you resolve it successfully, or did you move on to other issues?

Re: Mecanum - use of gyro
 

In the video above, I notice the person pushing the robot and it responds to return back to a specific pointing direction. Is this based on vision camera, gyro, wheel encoders? Thanks!