Thread: CAN Design Kit
View Single Post
  #19   Spotlight this post!  
Unread 09-12-2009, 22:31
Mike Copioli's Avatar
Mike Copioli Mike Copioli is offline
You make it pretty We make it dance
no team (Retired(3539, 217))
Team Role: Engineer
 
Join Date: Jan 2006
Rookie Year: 2001
Location: Romeo
Posts: 453
Mike Copioli has a reputation beyond reputeMike Copioli has a reputation beyond reputeMike Copioli has a reputation beyond reputeMike Copioli has a reputation beyond reputeMike Copioli has a reputation beyond reputeMike Copioli has a reputation beyond reputeMike Copioli has a reputation beyond reputeMike Copioli has a reputation beyond reputeMike Copioli has a reputation beyond reputeMike Copioli has a reputation beyond reputeMike Copioli has a reputation beyond repute
Re: CAN Design Kit

Quote:
Originally Posted by AdamHeard View Post
Ah, I was thinking more along the lines of full functionality.

Could a gyro be hooked up the to analog input on a jaguar and have the operation of the two be unrelated? The Jaguar's analog input just being used to pass the value to the processor.
The 2CAN is only one component of what would be a modular control system. It would be the core communications module. Other modules would be needed such as CAN to GPIO(general purpose input/output), CAN gyro, CAN to analog. CAN speed controllers such as the Jaguar, CAN accelerometers, CAN encoders. These devices could be developed by teams or purchased form a third party vendor. The advantage to using a device like the 2CAN is that a developer could use ANY processor using ANY platform to rapidly develop a fully functional robot. You could use a laptop, an arm processor, a PIC, a basic stamp. Any language c,c++, c#, basic, Java so long as the processor module supports either CAN or Ethernet or Both. Furthermore this device opens a door that will allow teams to develope their own CAN modules.

For years the primary focus of a FIRST team during design and the robot development cycle was mechanical and programming with some allowances for custom circuitry, leaving a very important field of engineering behind, Electrical. We mentor students on forces like inertia, and momentum, power to weight ratios with little or no focus on things like Ohm's Law, Thevenin's Theorem and Kirchhoff's laws. We do not have rules that require you to use a specific size axle shaft or sheet metal thickness because we want this to be part of the "Problem" that needs to be solved. But we have rules that require teams to use a certain gauge wire and specific breaker size. We disallow the use of power management devices in fear of fire. I argue a wheel flying off of the robot or an end of arm tooling that was under engineered is just as if not more dangerous than a rouge electronic component releasing the magic smoke in an arena with enough fire suppression capabilities to put out the earths core. Allowing teams to build their own speed controllers is as important as allowing them to build a transmission. Teaching them to use PCB layout and design software such as EAGLE or PADS or Altium is just as important as teaching them how to use Solidworks or Autodesk.

I hope the 2CAN is the gateway to these changes.
__________________
Mike Copioli
CTRE Hardware Engineer
http://www.ctr-electronics.com

Team 3539 The Byting Bull Dogs
2013 Michigan State Champions
Team 217 The Thunder Chickens
2006 World Champions
2008 World Champions
2009 Michigan State Champions
Reply With Quote