Robonauts Everybot program.

[lmedina]

We have updated the blog with our XML code.

In this XML file, that we used on Everybot, we are able to create controls on the fly without having to hard code those controls in.

For example, when we needed to put on an extra motor and assign it to a joystick control, we do not have to go into the source code. Instead, we go into the XML file and created the control by simply following the established XML syntax.

The XML file allows for the code to be modular and much more efficient.

Hope this Helps.

[AllenGregoryIV]

Luis, this is an awesome program, I wonder who gave you the idea? Just messing with you.

This is turning out even better than I expected when we first talked about it. I would suggest adding more specifications for each of your prototypes like which motors & gearboxes you are using. It helps teams that don't have any idea of where to start to see suggestions.

I hope this robot turns out very well, maybe it can even compete in the fall with a pre-rookie driving it.

[NWChen]

Do you guys have more images/media of Everybot besides what's on your website and the Recoil video?

[bEdhEd]

I think this is just as helpful, if not more helpful than robot in 3 days.

[ahartnet]

Originally Posted by AllenGregoryIV

Luis, this is an awesome program, I wonder who gave you the idea? Just messing with you.

This is turning out even better than I expected when we first talked about it. I would suggest adding more specifications for each of your prototypes like which motors & gearboxes you are using. It helps teams that don't have any idea of where to start to see suggestions.

I hope this robot turns out very well, maybe it can even compete in the fall with a pre-rookie driving it.

Looks like fall was not optimistic enough...

Glad y'all did this.

[Monochron]

Trying to put myself in the place of someone coming into FIRST with no prior experience, I don't think this would give me too much of a jump on how to build an effective robot. For example, the cam actuated choo-choo is a somewhat complicated mechanism and it would have been much more beneficial if you documented how it was build with pictures and/or videos. If someone is at the point where they are unable to come up with any kind of mechanism on their own, they will likely need a lot of guidance to build a working choo-choo.

In the "Brainstorming" section it might be helpful to actually post some of your brainstorming notes. Even something like random sketches would be helpful just to see what level of detail is needed for good brainstorming.

I think this was a really great idea. Detailing a simple yet reliable build process from a very experienced team can be a huge help to young teams, as long as you include enough detail to follow along to.