Thread: I2C advice
View Single Post
  #14   Spotlight this post!  
Unread 04-11-2014, 15:40
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 Joe Ross View Post
There were a few problems with I2C on the cRIO that caused people problems.
  • The cRIO software expected an 8 bit address, whereas most people were used to a 7 bit address. The roboRIO now uses a 7 bit address.
  • The cRIO's clock skewing behavior caused problems for some devices. It always supported a "compatibility" mode to solve those issues, and was enabled by default in 2014. This is no longer necessary on the roboRIO.
  • If the device stopped communicating in the middle of a transaction, the cRIO software would be stuck in an infinite loop waiting for data. http://firstforge.wpi.edu/sf/go/artf1726 This is not present on the roboRIO.



I think many people have complained about the CAN implementation on the cRIO.
Ooh sounds like I2C is going to be a good way of communicating this year! I am excited! I love how easy I2C is to set up on an arduino, but I have never gotten it to work on a cRIO. Hopefully that will be a lot easier this year!

And I meant that I haven't heard of CAN crashing the whole robot.