View Single Post
  #9   Spotlight this post!  
Unread 01-11-2012, 04:03 AM
jhersh jhersh is offline
National Instruments
AKA: Joe Hershberger
FRC #2468 (Appreciate)
Team Role: Mentor
 
Join Date: May 2008
Rookie Year: 1997
Location: Austin, TX
Posts: 1,006
jhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond repute
Re: New to 2CAN and Jaguar

Quote:
Originally Posted by mikets View Post
Wiring should be fine. I have tested it with the bdc-comm-100.exe tool and was able to see and run all motors. So it means the CAN bus is good. I am also able to see the 2CAN and all the Jags on the network (i.e. can access the 2CAN dashboard on 10.4.92.10 and see the status of all the jags). So it means the ethernet connection to the 2CAN is good. What other wiring could be wrong?
Probably nothing. Are you checking for errors or messages on the console being printed by the 2CAN plugin? Have you tried a BlackJag bridge?

Quote:
Originally Posted by mikets View Post
Yeah, I decided to redo the program with standard template and thinking I don't care about the encoders yet so I skipped the encoder related initialization. So you are saying they are still required?
They are required for closed loop mode... without some process variable, the controller does nothing. You may want to try simple PercentVbus mode first. Start simple and all. Verify you can talk to the Jags at all. Make sure your device numbers in the constructors match what you configured.
Reply With Quote