Thread: I2C advice
View Single Post
  #5   Spotlight this post!  
Unread 01-11-2014, 09:05
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 Chadfrom308 View Post
I've only heard of a couple teams that have gotten I2C to work well (besides the accelerometer). What I would personally do is get an arduino and a CAN shield and read the sensors using I2C on arduino and then send the data over CAN. I am on a Formula SAE team and we are doing something similar to this and it works really well.

Also, Teensy 3.1 has CAN built in (minus a microchip for the i/o for CAN) and that has something like 22 analog ins, so if you are reading lots of sensors (like the Formula team I am on) you could use that to read sensors too.
Have you tried writing to non-Jaguar CAN devices on the cRIO? Or to arbitrary CAN devices on the roboRIO? WPILib does not currently have any user APIs for arbitrary CAN devices/traffic. This seems substantially harder than just getting I2C to work on the roboRIO itself.