Bypass Disable Switch

[jakep]

We are making a robot over the summer using the 2004 RC. However, this is a fully automous robot, and doesn't need to be hooked up via radio (but it can be). We want to be able to let the robot run, with full control of the motors without any OI turned on or anything. However, if you do decide to turn on the OI, the robot should still accept input from it.

My question: Is there anyway to let the RC output to the motors even without an OI plugged in?

Thanks!

[Matt Krass]

If you set the team number to 0, I believe the RC runs entirely autonomous, I don't have access to confirm this. However I also believe that prevents you from establishing a successful radio link, so this might not help you at all.

[bear24rw]

Originally Posted by Matt Krass

If you set the team number to 0, I believe the RC runs entirely autonomous, I don't have access to confirm this. However I also believe that prevents you from establishing a successful radio link, so this might not help you at all.

I thought it was the last bit down on the dip switch

[Matt Krass]

Originally Posted by bear24rw

I thought it was the last bit down on the dip switch

If by last bit down you mean the left most, that's the MSB (Most Significant Bit) and that was used to unlock extra radio channels on pre-2005 controllers I think.

EDIT: The above statement needs to be amended, I left it there for clarity. Pre-2005 controllers needed a dongle to switch radio channels, as well as the team number change, newer ones only need the team number change. I forgot about the dongle but I remember something about newer controllers was less complicated.

[Andrew Blair]

I wasn't sure there was a way to enable this type of operation, short of an IFI code change. I thought I read somewhere that the code required an OI be communicating with the RC for any robot operation to take place, so that you can't easily be killed right as you turn on the robot. Kind of like an out of range disable with RC.

Or maybe not...

[KenWittlief]

there is no auton mode switch on the robot controller. You must have the OI on for the RC to operate

think about this for a minute: if the OI is not on then how in the world would the RC know what the switches on the OI are set to?!

[CmptrGk]

if you happen to have an extra vex controller and the ablility to make cable converters, the vex controller can function without its OI. it even has a #define line in its code to enable only auton mode. i also belive that the edubot controller can function without and OI (this wouldnt need a cable conversion).

[Pat Fairbank]

The robot controller CAN function without the operator interface. To enable this, the team number dipswitch on the OI must be set to 0, then the OI must be tethered to the RC to download the team number setting to it. Once the tether is disconnected and the RC is reset, the autonomous loop will execute forever and the RC will ignore any radio signals, until the team number is changed back to a non-zero value using the tether method.

However, it would be impossible to switch back and forth between OI and non-OI mode on the fly - the team number must be changed each time with the tether cable.

Originally Posted by Matt Krass

If by last bit down you mean the left most, that's the MSB (Most Significant Bit) and that was used to unlock extra radio channels on pre-2005 controllers I think.

Just to clarify, setting the MSB enables the extra radio channels on the 2005 and later controllers, while the pre-2005 controllers required you to ground a specific pin on the Competition port in order to do so.

[Matt Krass]

Originally Posted by Pat Fairbank

Just to clarify, setting the MSB enables the extra radio channels on the 2005 and later controllers, while the pre-2005 controllers required you to ground a specific pin on the Competition port in order to do so.

You're right, I already edited my previous post, but thanks for catching my slip anyway.

[Andy A.]

PBasic type educontrollers can also be run autonomously, by setting the team number to 0 and cycling power. If there is a user defined auto mode program, it will execute until power is turned off.

Another option might be to keep the OI on the robot, connected by a tether and enable automode with a dongle switch. Add a short pause at the start of the program to allow you to flip the switch and extract you're hand before it takes off. This would save you from having to set the team number back and forth, and also allow you a quick and easy way to put the robot under manual control. Just connect a joystick and disable automode and away you go. No radio, external power supply and the only range limit is the length of the joystick cable.

I would be a little leery about a large scale robot running in autonomous mode with out any remote way of turning it off though. But I am not the computer trusting sort...

[KenWittlief]

Originally Posted by Andy A.

I would be a little leery about a large scale robot running in autonomous mode with out any remote way of turning it off though. But I am not the computer trusting sort...

I agree - even if the auton code is simple and the bot moves around slowly - thats how it operates when all on-board systems are operating within normal parameters.

what happens if a wire on a sensor breaks, or a connection to one motor fails - or a feedback sensor goes open loop?

On every piece of commercial robotic equipment, that is used in proximity with humans, there is a big red mushroom shaped KILL button where you can get to it without having to go near the robot.

[Rob2713g]

Note: I'm pretty new to programming and haven't tried this yet. While working on a different project I was told to use interrupts. So you could run autonomous until joystick pressed then jump to regular joystick code. Anyone know if this is possible?

[RoboMadi]

Lets not make it much complicated
Our team build a robot that completely runs on autonomous and uses sensors to interface with the environment around it.
heres a simple easy solution

If you set the operator interface to team 0, then tether it to the robot, it forces the robot into permanent autonomous mode. In this mode it does not look for the operator interface.

[KenWittlief]

Originally Posted by RoboMadi

Lets not make it much complicated...

Complicaitons: what your team will experience if you dont have a kill switch! :^)

[Matt Krass]

Originally Posted by KenWittlief

Complicaitons: what your team will experience if you dont have a kill switch! :^)

Ken actually I think the word is Lacerations

Setting it to 0 would work, but be sure to build in some way to disable it on the fly if necessary. Locally tethering the OI is still an option as you can make a competition port dongle that wires up to a toggle switch between tele-op and auton, with a big red disable button right on top of the robot.