VEXpro 2016

[GeeTwo]

Originally Posted by cadandcookies

When I asked this a few years ago, here's the answer Aren gave me.

I'd assume the answer is somewhat similar here-- the arc motion is so short, and the cylinder and bar are very well defined, so it isn't necessary to connect the two.

Originally Posted by AllenGregoryIV

Nick has it right. If you have omni wheels floating, you can just leave them and they won't hurt your driving. If you float traction wheels you would probably need to add a spring to raise the module to keep it from scrubbing during turns.

I think that it is necessary to raise the omni wheel, because it is geared twice as fast as the fixed wheel; it would be spinning against the carpet whenever you were driving in traction generating heat and wearing down the wheel. In Aren's previous answer, he refers to a spring lifting the moving wheel up. I don't see one in the assembly directions, but it may be implicit in the way pieces fit.

[AllenGregoryIV]

Originally Posted by GeeTwo

I think that it is necessary to raise the omni wheel, because it is geared twice as fast as the fixed wheel; it would be spinning against the carpet whenever you were driving in traction generating heat and wearing down the wheel. In Aren's previous answer, he refers to a spring lifting the moving wheel up. I don't see one in the assembly directions, but it may be implicit in the way pieces fit.

It won't really wear the wheels since there is no down force on the wheel other then the weight of the module itself.

[s_forbes]

Regarding motors.vex.com:

The link for the locked rotor stall test data exists for all of the motors, but returns a 404 for the CIM and BAG motor. The data seems to exist for the other motors... Is this just an error in the site? (obligatory "fix plox")

[Grant Cox]

Originally Posted by s_forbes

Regarding motors.vex.com:

The link for the locked rotor stall test data exists for all of the motors, but returns a 404 for the CIM and BAG motor. The data seems to exist for the other motors... Is this just an error in the site? (obligatory "fix plox")

Whoops.. Thanks for pointing that out! This has been fixed.

For future reference, you can also let us know about website errors by emailing prosupport [at] vex [dot] com directly - you will likely receive a result quicker than by posting on Chief Delphi!