Thread: I2C advice
View Single Post
  #11   Spotlight this post!  
Unread 03-11-2014, 21:17
RufflesRidge RufflesRidge is offline
Registered User
no team
 
Join Date: Jan 2012
Location: USA
Posts: 990
RufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant future
Re: I2C advice

Quote:
Originally Posted by 2B || !2B View Post
The FIRST I2C class kept hanging up the robot because it would start another transaction when another was already active.
Quote:
Originally Posted by jhersh View Post
I'm surprised that the Java class allowed more than one write at a time to the I2C bus. I haven't looked to see if that is a bug or a misunderstanding.
The transaction method in the cRIO Java code is synchronized, you cannot execute two transactions at once.

Quote:
Originally Posted by Chadfrom308 View Post
It seems like i2c isn't really fully developed on the cRIO or the roboRIO. Bit that's just what I have heard
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.