Thread: I2C advice
View Single Post
  #10   Spotlight this post!  
Unread 03-11-2014, 16:57
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 jhersh View Post
That sounds like a pretty complex solution to a simple problem. There would have to be some extenuating circumstances to warrant such a design.
Well I've always heard of hangs and program crashes because of bad i2c code., never CAN. And it is easier to get all of your sensor data from 1 source (CAN) and you can pre process the data. That's the way I would do it. It also allows you to develop code faster (you only have to compile arduino code, not the whole robot code).

It seems like i2c isn't really fully developed on the cRIO or the roboRIO. Bit that's just what I have heard