View Single Post
  #1   Spotlight this post!  
Unread 23-06-2011, 08:44
kenavt's Avatar
kenavt kenavt is offline
Registered User
AKA: Colin S
no team
Team Role: Alumni
 
Join Date: Feb 2010
Rookie Year: 2010
Location: Ann Arbor
Posts: 253
kenavt has a reputation beyond reputekenavt has a reputation beyond reputekenavt has a reputation beyond reputekenavt has a reputation beyond reputekenavt has a reputation beyond reputekenavt has a reputation beyond reputekenavt has a reputation beyond reputekenavt has a reputation beyond reputekenavt has a reputation beyond reputekenavt has a reputation beyond reputekenavt has a reputation beyond repute
Re: Jaguar communication issue

Quote:
Originally Posted by jhellr13 View Post
For a drivetrain code, whatever the drive code (arcade, tank. holonomic) is placed in the begin vi. On that block, the pwm cables are assigned for each jaguar controlling the CIM motors. In teleop, that is where you initiate the drive system and make it controllable by a joystick. As a heads up, if you are doing omni wheel or mecanum, remember that those drive systems have 3 axis. Forward, back, and strafe.
If you need some help because it seems like you might be confused, check out this link. It is the team website for Mark McLeod's team up above. They have a great resource for LabVIEW programming on any topic and it was a great help for me this year, and certainly help you out right now.
http://team358.org/files/programming...2009-/LabVIEW/
Frankly, I've never seen anyone place drive code in the Begin.vi - it was my understanding that was for initializing PWM channels, not putting drive code in Robot Main.vi at that point. You may be talking about the Open 4 Motor.vi, which frankly shouldn't be neccessary - I can open individual motors just as easily.

I may seem confused because I believe that I am initializing PWM channels correctly for each individual motor, but nothing seems to be allocated. That website is a great resource, though. I'll be sure to look through that.
__________________
University of Michigan Computer Engineering '17

FRC 2337 student alumni (2010-2013)