2011 Logomotion Mini Bots

[Bethie42]

From an FTC website: http://sites.google.com/site/ftciowacoaches/software

'The LEGO NXT bricks can run on one of three software programs: NXT-G, LabView or RobotC. However, to compete in an FTC competition, teams must use LabView or RobotC.'

I understand RobotC is text-based; NXT-G is a simple visual LabVIEW-type language but not allowed in FTC. Good Q for Wednesday: does the FTC programming rule apply, or can we program in NXT-G?


The Oregon FTC/FLL website ORTOP also has info. http://www.ortop.org/ftc/

[cooldude8181]

Is there any real advantage to having code on the minibot?

Because everyone knows that code just ads excessive weight.

Would a bot that would just start when it knows the pole is there work better than something that the drivers would have to control?

[TJ Cawley]

software, or code, has no weight. for any robot to move, it needs code. otherwise, to get it running would be direct control between motor wires and battery, which is illegal

[nighterfighter]

Originally Posted by TJ Cawley

for any robot to move, it needs code. otherwise, to get it running would be direct control between motor wires and battery, which is illegal

Are you sure? Why couldn't one simply leave it running forward, until it hits a switch, then drive in reverse? (Assuming they don't have to stay at the top)

[TJ Cawley]

Originally Posted by nighterfighter

Are you sure? Why couldn't one simply leave it running forward, until it hits a switch, then drive in reverse? (Assuming they don't have to stay at the top)

that would take code. we do not have self programmed parts available to this competition. no code, no movement.

plus, that means your minibot would be running the entire autonomous and teleop match, leaving no battery life left

[DonRotolo]

Originally Posted by TJ Cawley

software, or code, has no weight. for any robot to move, it needs code. otherwise, to get it running would be direct control between motor wires and battery, which is illegal

Can you cite the specific rule that forbids this please?

[TJ Cawley]

Originally Posted by DonRotolo

Can you cite the specific rule that forbids this please?

I could not find a specific rule on this, so it MAY be legal, but if your minibot runs the entire match, you have no power when you need it to climb the last 10 seconds

[pfosx]

the game manuel seems to be alittle on the vague side towards these minibots. how do we control them!

The FTC mini-kit from FIRST Choice, does that include 'everything' to make a minibot? If we use an NXT with this 'mini-kit', is it a functioning minibot?

[byteit101]

Originally Posted by TJ Cawley

that would take code. we do not have self programmed parts available to this competition. no code, no movement.

plus, that means your minibot would be running the entire autonomous and teleop match, leaving no battery life left

not necessarily, you could have a three way switch that connects the battery directly to the motor forward, backwards, and off, and the main robot could turn it on, deploy it, it would hit the top, flipping the switch, sending it in reverse. No wasted battery, no code

[nighterfighter]

Originally Posted by byteit101

not necessarily, you could have a three way switch that connects the battery directly to the motor forward, backwards, and off, and the main robot could turn it on, deploy it, it would hit the top, flipping the switch, sending it in reverse. No wasted battery, no code

Exactly. The minibot rule section states you can use some common household light switches. Seems trivial to set up your deployment system to flip it on as it goes up.

Even if you left it always on, I don't think ~4 mins will kill the battery. Then again, I don't know the life of these batteries.

[SuperS_5]

The NXT may be programmed in LabVIEW. There are libraries available, and it is easier to program then the cRIO. FRCmastery.com is the sister to FTCmastery.com. There are videos and help on both sites.

[Egg 3141592654]

I was thinking about this same issue. Wouldn't sapping power from the main robot to power the minibot eliminate the need to place batteries on the minibot? The rule people on our team are still looking this up, but still would be a good idea if legal (minimum code if at all, and super light).

[PSHRobotics]

Originally Posted by Egg 3141592654

I was thinking about this same issue. Wouldn't sapping power from the main robot to power the minibot eliminate the need to place batteries on the minibot? The rule people on our team are still looking this up, but still would be a good idea if legal (minimum code if at all, and super light).

How would you manage to have the minibot continue up the pole once it is disconnected from the main robot?

Also, LabView is pretty popular for FTC. The FTC section on CD has several teams that use it, including mine.
Now what I'm worried about is access to the libraries for FTC and FRC at the same time. My team has tried to install (last season, not this season) FRC's LabView directly over the version for FTC. The install always failed over three labtops. We had to completely remove everything related to FTC's LabView before installing FRC's LabView. Hopefully this will not be too big of a problem because an "FTC Toolkit" is released to use with LabView which should contain all the libraries for FTC. You can get the Toolkit off of USFirst.org's FTC Programming section in the "LabView Resources" link." Tomorrow, I will try installing the ToolKit over this FRC's LabView and then try to compile our most recent FTC code. I will post any problems or successes here.

[kamocat]

Originally Posted by PSHRobotics

How would you manage to have the minibot continue up the pole once it is disconnected from the main robot?

Also, LabView is pretty popular for FTC. The FTC section on CD has several teams that use it, including mine.
Now what I'm worried about is access to the libraries for FTC and FRC at the same time. My team has tried to install (last season, not this season) FRC's LabView directly over the version for FTC. The install always failed over three labtops. We had to completely remove everything related to FTC's LabView before installing FRC's LabView. Hopefully this will not be too big of a problem because an "FTC Toolkit" is released to use with LabView which should contain all the libraries for FTC. You can get the Toolkit off of USFirst.org's FTC Programming section in the "LabView Resources" link." Tomorrow, I will try installing the ToolKit over this FRC's LabView and then try to compile our most recent FTC code. I will post any problems or successes here.

Interesting you should have this problem.
I know this was an issue for FRC 2009 and FTC 2008/09, but since then FTC and FRC have used different versions of LabVIEW.
I just yesterday installed FRC LabVIEW on laptops with the FTC LabVIEW.
Could you PM me with more details of your issue?

[Egg 3141592654]

To answer all those who questioned how i would keep power to the robot, our team would use a really long wire and tether it to the robot. I thought I could make it like those old rc car power systems (except with no manual control). Just a thought.