How do you wire a Kick motor in labview?

[Omar]

Originally Posted by K Lenox

Ok heres whats happening.
We are using a motor to pullback a bar, using a dogleg, once it clears the gap, it lets go of the tension and kicks back. Kindof like when you use your foot and bend your knee ato kick something.

But you still have not fully explaned how you plan on controlling the motor.
Do you turn it on and leave it on? How will you know when it has "let go"
When will you stop your motor?

Originally Posted by K Lenox

Now, the team want me to devise 3 Autonomous modes. 1 code for each starting position. We can determine which one we want to use by flipping one of three switches on a box to on.

Use the Get Alliance.VI and forget about flipping switches on a box.
Set the Alliance and field position on the driver station.

[K Lenox]

Now we have a limit switch that gets activated once the dogleg's gap passes by. The dog leg winds the kicker back, then it hits the limit switch and lets go.

Now I understand that you are encouraging me to get the Get Alliance Vi. But the box is already on the robot and we have the digitial I/O programed into the Robot Main Vi.

Now What is the Get Alliance Vi. and where would I get it justs incase the box doesnt work.

By the way thanks for all the help youve given me.

Kyle Lenox

[Alan Anderson]

Originally Posted by Omar

Have you looked at the Get Alliance VI?
The Alliance and field position is set on the driver station and can then be read by you code.

This won't do what you want. The "field position" actually tells which of the three spots behind the glass your driver station is set up on. It has nothing to do with where your robot is placed on the field.

[Omar]

Originally Posted by Alan Anderson

The "field position" actually tells which of the three spots behind the glass your driver station is set up on. It has nothing to do with where your robot is placed on the field.

Alan I am very sorry to hear that. We have already built our auto code around that. I misunderstood the term "field position" to mean the position on the field and not the driver station position.

We have even tested it out. We are able to set the field position on the driver station and the robot code reads it correctly. Does this mean that durning commetition they will over write what we set it to?

Are you sure about the mean of "field position"?

[Omar]

Originally Posted by Alan Anderson

The "field position" actually tells which of the three spots behind the glass your driver station is set up on. It has nothing to do with where your robot is placed on the field.

I have tried to research this more and feel that when they say field position they mean one of the 3 positions the robot will start from on the field.

In the manual they use the terms "Alliance Stations" and "PLAYER STATIONS" when referring to the area behind the glass and they use the term "field" when referring to the green area that the robots are in.

We can set the field position value on the driver station and then read it from the robot. I feel we can set it to mean what we want it to mean. What ever we want the values 1, 2 or 3 to mean to our robot code.

[Omar]

Originally Posted by K Lenox

Now What is the Get Alliance Vi. and where would I get it justs incase the box doesnt work.
Kyle Lenox

It is located on the DriverStaion sub palette.

[Mark McLeod]

I'm behind Alan.
Get Alliance only specifies your Driver Station location, not your robot's actual location on the actual field.

We get assigned Driver Station positions for the benefit of the Field Management System (FMS). That's the only reason that information is available.

Robot starting position is unrelated to Driver Station position and is negotiated ahead of the match between the three alliance partners rather than the starting positions being randomly assigned by FMS.

FMS has no way to tell where you have negotiated with your two alliance partners and agreed to place your robots, and it doesn't really care.

[K Lenox]

Okay so let me get this straight.

My team wants me to make 3 Autonomous Codes. One code relating to the 3 places where your robot starts out on the field.(near, middle, far)

We currently have a white box with three switches in it. all switches are a on/off flipper type switch. Somehow in labVIEW, I should be able to take the Digital Outputs ( I/O 6, I/O 7, I/O8) and program it so when one is set to on(true) and the others are set to off(false) it should bring up its corresponding Autonomous Code and deploy it.

Now we were talking and if we can select which code to use in the driver station, that would be even better.(take off the box, save some weight)

But from reading your messages, The Get Alliance vi. wont let us do that?
I thought it would, but now it seems like that vi wont work like that......

Am I right? Am I misunderstanding? I have only been using Labview for the month of Febuary. Any clarifacation would be nice.

Thanks, any help is appriciated
Kyle Lenox

[Mark McLeod]

You can easily make your Autonomous choice from the driver station before the match begins and you're required to step back from the controls.

In your code you'd use the Driver Station Get Dig In.vi to test any switches you attached to the Diriver Station via the Cypress IO board.

Or without the Cypress IO board you can select your Autonomous from the I/O tab.