|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Team Update 17
We used CAN successfully last year, and are planning on using it this year. We will try the simulation procedure outlined in team update 17 and see how it goes. If it fails, we will switch to PWM. If it works, we will try it in a practice match before competition.
I have heard that there may be a CAN issue with using the CrIO imaging tool this year. |
|
#2
|
|||
|
|||
|
Re: Team Update 17
Hey cool they used 11 as the example for BOM naming!I think Team 11 is still using CAN, do those of you who had issues suggest switching out to PWM? /15minutesoffame |
|
#3
|
|||
|
|||
|
Re: Team Update 17
We have 8 Jaguars using CANbus this year, and much prefer the CANbus wiring to PWM cables. I know there were teams at GSR over the weekend having significant issues with CANbus, and one team even switched over to using PWM control of their Jags during Friday afternoon, but we did not see any problems. The field crew were keeping a very close eye on the diagnostics tab of our driver station (thank you!), especially during the later stages of eliminations. We've used CANbus every year since it became available and have been very happy with the results.
We have also not seen the same reliability issues with Jaguars - the worst thing that happened to us this year was a Jag on our practice bot randomly changing from id=3 to id=59 overnight. It took a few minutes to work out what the problem was but once we reset the id everything was fine. We number all of our Jags so we'll know if it ever happens again to the same one. If anything, I'd say that we have more experience of Victors failing than of Jaguars failing, but I'd be more inclined to put that down to our team getting better at not sprinkling robot electronics with metal shavings since we last used Victors than any intrinsic reliability difference. Noel |
|
#4
|
|||
|
|||
|
Re: Team Update 17
Quote:
|
|
#5
|
|||
|
|||
|
Re: Team Update 17
Quote:
Noel |
|
#6
|
||||
|
||||
|
Re: Team Update 17
"If a team is using a CAN network on the robot, they should check the messages in the “Diagnostic” tab of the Driver Station before a match starts to ensure that there aren’t any scrolling CAN timeouts."
Can someone please explain how messages get on the diagnostics tab? We're using Java and currently outputting text to the User Messages portion of the Operation tab using the DriverStationLCD object when we catch a CANTimeoutException. How are other people handling these exceptions? |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|