Thread: I2C advice
View Single Post
  #12   Spotlight this post!  
Unread 03-11-2014, 22:10
Chadfrom308's Avatar
Chadfrom308 Chadfrom308 is offline
Slave to the bot
AKA: Chad Krause
FRC #0308 (The Monsters)
Team Role: Driver
 
Join Date: Jan 2013
Rookie Year: 2011
Location: Novi
Posts: 272
Chadfrom308 is a splendid one to beholdChadfrom308 is a splendid one to beholdChadfrom308 is a splendid one to beholdChadfrom308 is a splendid one to beholdChadfrom308 is a splendid one to beholdChadfrom308 is a splendid one to beholdChadfrom308 is a splendid one to behold
Re: I2C advice

Quote:
Originally Posted by RufflesRidge View Post
Speculation and FUD seems unhelpful. Perhaps we should stick to actual data and not hearsay? Especially when it comes to a system that's still in Beta, in the hands of 90 teams, and which has no current bugs filed against the I2C software from a quick glance at the Beta tracker.
I understand that, but if I2C freezes the whole robot, then that is a big problem. CAN won't freeze your whole robot, and a lot of things already run off CAN. If the arduino freezes, it probably won't freeze your robot. I am just trying to stay on the safe side, and that is what we will be doing next year if we use I2C for something.