Thread: i2c output
View Single Post
  #12   Spotlight this post!  
Unread 15-01-2009, 13:32
Jared Russell's Avatar
Jared Russell Jared Russell is offline
Taking a year (mostly) off
FRC #0254 (The Cheesy Poofs), FRC #0341 (Miss Daisy)
Team Role: Engineer
 
Join Date: Nov 2002
Rookie Year: 2001
Location: San Francisco, CA
Posts: 3,077
Jared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond reputeJared Russell has a reputation beyond repute
Re: i2c output

Quote:
Originally Posted by timmmoore View Post
Unfortuntely its in the offical Q/A http://forums.usfirst.org/showthread.php?t=11227
The Q&A still is not supposed to be the medium over which rules changes are made. If any rules changes have been made (I haven't read the relevant manual sections, so I'm not sure whether they were or if only clarifications were offered), they might appear in a team update.

As far as why - who knows. Leveling the field? Maybe the back end software isn't there yet? Keeping things simple for inspectors?

Regardless, you should be able to mimic the I2C (or serial, for that matter) interface using digital I/O and some low-level code. It would be a lot of work, but it can be done.

EDIT: You can also look out for specialized hardware to convert between I2C and an easier-to-implement protocol like RS-232. You can then connect your sensor to that custom circuit and write some simple serial port code for your digital inputs. I believe that this would still be legal.

Last edited by Jared Russell : 15-01-2009 at 13:37.