next topic »

[on:]

Anyone interested in trying a new I2C master library for the Arduino?  I got tired of trying to modify the TWI library to get the repeated start feature to work so I went ahead and wrote a new library that combines the Wire and TWI libraries into one.  It has more functionality, higher throughput and reduced code size.  It's available for download here http://www.dsscircuits.com/images/code/I2C.zip and there's a full write up about it here http://www.dsscircuits.com/articles/arduino-i2c-master-library.html

I've tested it on several devices and so far it works well. 

Let me know what you think.

[Reply #1 on:]

Very nice. Although the current Arduino I2C library works for me (single reads to a register), I thought it was kind of "klunky" the request operation.

[Reply #2 on:]

Hi wayneft. Just to let you know i am now using your i2c library on my lighting controller.  Not too worried about the speed, using bitbanged Pic as slaves so max clock frequency they can handle is about 20kHz but was having problems with bus hanging.  Your timeout routine seems to work well. 
Also looking at using the write routine return codes to initiate retry if required
Will let you know how it goes
Wil

[Reply #3 on:]

Great. Let me know if you have any problems.

[Reply #4 on:]

Some more examples would be nice. I'm trying to read blocks of registers from the MPR121 capacitive touch sensor controller (which needs repeated starts) and would have appreciated examples demonstrating more of the api. I'll let you know how it goes, I'm about to wake up I2C and see if it can get some data...

[Reply #5 on:]

I can report that I was able to use I2c to read all, or chunks of registers from the mpr121 - thank you. A suggestion would be to alter the header file such that the arguments are named instead of just typed however. While coding I was reading the api docs on your site, and copying and pasting relevant lines into my own code. The compilation failed however, due to data type differences between my arguments, and those specified by the I2c api. So I looked into the header file to see what I needed to alter - and because the arguments weren't named (just typed) I found it difficult to figure out which function matched the api docs, thus I had to look at the source code which took additional time. Another suggestion would be to include the html page with the api docs inside the library folder for easy reference.

Thanks for the effort, you saved me a lot of time. I'd already burned about 12 hours finding out that the wire library wasn't going to work and yours was the third library I tried. The third pass was the charm. Thanks.

[Reply #6 on:]

Glad to hear it worked out for you.

and because the arguments weren't named (just typed)

I'm not sure what you mean by this.  I must tell you that I'm more of a hardware guy than software but I am trying to increase my coding skills.  So any pointers you have please feel free to pass them on.  Anything I can do to improve the library I'm happy to do.

[Reply #7 on:]

The function prototype in the header file can contain the variable names used in the function definition. This was a change introduced with ANSI C. It sounds like you're using the older K&R C standard. Here's an example:

Code:

void MyFunction(int x, int y, char* message)
{
    ...
}

In K&R C you would prototype the function like this:

Code:

extern void MyFunction(int, int, char*);

In ANSI C you would prototype the function like this:

Code:

extern void MyFunction(int x, int y, char* message);

The ANSI C style has the advantage that you can use copy and paste to create the declarations from your function definition AND anyone viewing your headers can tell that the first parameter is x and the second y, rather than having to find the function definition.