How are you going to operate you're robot?

That is awesome. Is’nt freedom and choice great.

I would like to see this… done with a joystick.

My question is why do you need any buttons on the O/I? You still have 6 more buttons available to you on the Xbox-controller. You could impliment the same logic using those.

Ours is a very complex system of sensors on the skin of the driver, a biomechanical suit and several large anteaters.

Two joysticks and I have no clue on how to control the arm, maybe a big button to slam with your head?

Chris

you have anteaters too???

kiddin’. just two joysticks and a button.
simple, easy, and it works ,too! [we hope :)]

two joystics for driver, and we are going to have to find some buttons for manipulator contoll, as well as a big red “Don’t press”. And we’ll call it the football.

It’s intended as a safety measure. Some people are concerned about accidentally deploying the ramp in the middle of the match, so we decided to put the ramp control far away from anything that might accidental get pressed.

Drivetrain: Joystick and a turntable…
Arm: ???

For the main driver, we’re using one joystick drive, with a kill switch to disable motors, a manual override to kill sensor assitance, a ramp deploy switch, and an extra switch either for raising ramps or for using the camera in manual mode.

For the arm guy, we’re using a joystick for arm angle adjustment, the hat switch for claw angle adjustment, 5 automatic arm position buttons, 1 switch to switch which side of our robot the automatic buttons work for, an abort button to cancel auto arm movements, a switch to turn the compressor on/off, a button for our elevator, and then 2 buttons on the joystick for claw and extension control.

Plus we’ve got 4 indicator LEDs.

All in all we’re using 4 analog inputs, 13 digital inputs, and 4 LEDs.

why control it when you can be fully autonomous…:wink:

2 CH flight sticks for the drive and a 2k7 version of this:http://www.chiefdelphi.com/pics/bin/111068167879.jpg

:cool:

My team is using a xbox 360 controller. The analog sticks control respectfully the left and right side full speed. The top left and right bumpers are half speed. Then for the arm and gripper positioning were mounting plugs onto an elevated peice of plexy-glass so you can see the wiring beneath it. it will have 4 positons for the arm one on know ground, 1st spider, second spider, and 3rd spider and the gripper will have open and close. Thats really all we need. I think…

We are going to use:
1 steering wheel
1 f16 joystick
and we might add 1 special switch box for the ramp.

Our robot’s base chassis is an omnidrive, complete with forklift, a gyro and a big claw. There are going to be 2 operators, one to drive and one to manipulate the tubes (unless they changed the design again…). Our gyro is to keep the robot on course, so if it’s bumped, it will try to counter the bumping. our loose battery has been giving us quite a bit of strife… it mucks up the gyro and causes spurious movements.

We’re using an X-Box 360 controller both to drive and manipulate. Our driver tried it this morning (he was originally totally against using it) and found he loved driving with it.

Two logitech playstation controller spinoffs, and a big red button. Anyone wanna guess what the red button does?

Our control panel has changed from my previous post. Me and TdorTheBnator built one with four joysticks. Two for the driver and two for the operator.

Says “Ah, that was easy…”???

2 Xbox 360 controllers - found that using thumbs is much faster than using whole arms w/ joysticks (less movement).

No actually, allot of teams have Staples buttons, ours just eliminates all the other bots on the field with laser technology. Or it shuts off the suction cup and motors and drops the lift, either or.

2-axis CH joystick with stiff springs for the driver.

Logitech USB joystick with 3-axes and 8 buttons for the arm operator.

Driver has option of 2 joy or 1 joy mode, along with change of view (reverse what is front, what is back). The arm is controlled by 4 buttons and a switch… the code takes care of pretty much everything.

We’re still having issues with some P and PID loops, so hopefully we’ll get those fixed at the competition.

There’s no finer engineering than pit engineering.