|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools |
Rating:
|
Display Modes |
|
#16
|
||||
|
||||
|
Re: Minibot Standardization (FRC 2011: Logomotion)
Not at all. Why would teams design for a suspension bar when they could design for the very standard, has to be there hanging bar instead? Making a different "suspension bar" size was stupid.
|
|
#17
|
||||
|
||||
|
Re: Minibot Standardization (FRC 2011: Logomotion)
Quote:
Quote:
I believe that minibots should be designed such that they are deployment-mechanism-agnostic, be it by pushing, swinging, or something else, because teams will end up having to make different deployment mechanisms based on how the rest of their robot is designed Last edited by ChristopherBuck : 01-08-2011 at 11:46 PM. |
|
#18
|
||||
|
||||
|
Re: Minibot Standardization (FRC 2011: Logomotion)
I propose the name of: MIND: MINibot Deployment
It is a ramp that is essentially drawbridge, that deploys at 30 inches (at the line) and emulates deploying at base level. Other than that, there must be 12*12*12 space inside the robot to store minibots. Last edited by Grim Tuesday : 01-09-2011 at 12:24 AM. |
|
#19
|
|||||
|
|||||
|
Re: Minibot Standardization (FRC 2011: Logomotion)
I think there are 2 things to be standardized.
1) Minibot activation. 2) Minibot-pole transition device. #2 is the simplest. The drawbridge or a platform device is simple: move ramp/robot to either the base or the pole and let it do its thing. Telling it when to go could be as simple as a bar across the end that when released turns the minibot on or lets it go. #1 is harder. NXT device, pure mechanical, non-NXT... Ideally, the start trigger is contained on the minibot and is "running" when the minibot is loaded onto the hostbot. The 30" height might be tricky--it depends on whether the minibot is allowed to be above the line. But substitute your favorite height in there as you need to. |
|
#20
|
|||
|
|||
|
Re: Minibot Standardization (FRC 2011: Logomotion)
Quote:
An internal limit switch that detects the pole would probably be enough, and would work with almost any design (triggers nxt program to start, closes circuit to a motor, etc) |
|
#21
|
|||
|
|||
|
Re: Minibot Standardization (FRC 2011: Logomotion)
Quick question, one to (perhaps) get people thinking:
Are you allowed to use an IR Receiver with a minibot? (does this qualify? http://unlimited.syraweb.org/NewFTCkits.htm) How easy is it to distribute a software module, an IR Led and some wire, and perhaps a button to teams at your regional? Will that be too much weight on their robot? How difficult will that be to install on a generic robot? That's probably the best way I can think of to get it going. Let me know what you think. |
|
#22
|
||||
|
||||
|
Re: Minibot Standardization (FRC 2011: Logomotion)
Quote:
Quote:
|
|
#23
|
|||||
|
|||||
|
Re: Minibot Standardization (FRC 2011: Logomotion)
We're trying to pick a system that will work with a variety of minibots to get them to the pole here. If teams put a 12"+ cube on their robots, with some form of platform that gets a minibot to the pole, it seems that that has the largest potential to accept any random minibot. That leaves activation up to the minibot users, but standardizing activation methods would be nice too.
If you standardize minibot activation on the minibot, teams have to design for that. If you standardize a deployment that can accept any minibot, and have activation be automatic on the minibot, that's easier to do. |
|
#24
|
|||
|
|||
|
Re: Minibot Standardization (FRC 2011: Logomotion)
Perhaps a Bayonet - type of mounting where your robot has a delivery system,
eg a 1" square tube with a right angle end that actuates out, you can then provide a female connector to a partner team to mount on their mini-bot and make it compatible. Bad thing is probably the need for re-inspection of the mini-bot in this case if it's done on-the-fly. Ideally your mini-bot could be launched electrically using a Digital input or closed switch arrangement or have its own internal detection of pole contact. Nothing says you have to make arrangements for the bot deployment at the competition, you could agree with some partner teams locally to create a regional standard. Teams can build their bots to intentionally be traded off at the regional for the additional points any time it scores. That's co-oper-tastic. |
|
#25
|
||||
|
||||
|
Re: Minibot Standardization (FRC 2011: Logomotion)
What if all the standard was would be a 12x12x12, and each minibot had to include its own deployment mechanism?
|
|
#26
|
||||
|
||||
|
Re: Minibot Standardization (FRC 2011: Logomotion)
This may seem stupid but how will they stop the program from running on the mini bot? I mean a simple limit switch type device would work to activate the programming for the mini bot. I had an idea of it being on the inside of the bot and once it hits the pole it just takes off. Then once we get a confirmation about if the robot can come back down just plan around that also.
|
|
#27
|
|||||
|
|||||
|
Re: Minibot Standardization (FRC 2011: Logomotion)
Quote:
It's when the deployment mechanism goes outside, or when the robot's docking area isn't where the deployment mechanism needs to be to deploy right that there's a problem. W/R/T stopping the minibot from running, I was thinking a switch at the pole as well. Activate it, and the minibot turns on. Biggest problem is the hostbots that expect the minibot to move out on its own onto the base--but another switch with a "standardish" mounting area set and a servo on the robot to activate it would probably work. |
|
#28
|
|||
|
|||
|
Re: Minibot Standardization (FRC 2011: Logomotion)
My idea was to use a drawer type bearing to shove the mininbot out to the pole. For the minibot, I hat the thought of haveing three wheels, arranged in a triangle, with the "tip" of the triangle on the robot side of the minibot (away from the pole). As the bot was deployed, the one wheel would be pushed back and it would mechanicly grip the pole. Once all three wheels were on the pole, the unpowered wheel would somehow trigger a switch that would tigger the other two wheels to turn on. They would stay on for 10 seconds, stop for 10 seconds, then reverse at half speed for 15 seconds.
I'm sorry in advance if it makes no sense, but I'm just throwing an idea out there... |
|
#29
|
|||
|
|||
|
Re: Minibot Standardization (FRC 2011: Logomotion)
I feel there has been some discussion on standardizing the minibots. Some people, donrotolo and darist, have expressed a desire for somebody to take the initiative in coming up with an open standard minibot. We want everyone to have freedom within the one foot cube, but we want to be able to expect some common way to mount the minibot to the host bot in a way it can be delivered on a pole.
Building on the comments by caffel I believe these could be the four criteria we need to keep in mind 1) Box/envelope/open top 2) Delivery platform (minibot doesn’t fall out of host bot) 3) Delivery (because currently it appears that our robot and minibot will be in contact with the pole the max hight of deployment is 18in) 4) Attach/ launch We at 1712 would like to propose the acronym for the standardization, CLIMBS (Committee Leading the Initiative for MiniBot Standardization). Post fast we only have 10 seconds to the top |
|
#30
|
||||
|
||||
|
Re: Minibot Standardization (FRC 2011: Logomotion)
I'm working on something right now, I'll post in a bit with what I get.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|