I'm not sure why it has changed, but is there really a problem with calculating the address first? Sounds to me like you have solved the problem.
I'm not sure why it has changed, but is there really a problem with calculating the address first? Sounds to me like you have solved the problem.
"I think fish is nice, but then I think that rain is wet, so who am I to judge?" - Douglas Adams
Not at all. It's just a curiosity, and a slight concern for the units already deployed. Lesson learned.
I had a similar problem with the write command. DT said it had something to do with adding LONGs in 2.6. You can see his response here
Maybe something similar happened with the I2CREAD command
David
I try to avoid doing Math in any I2CREAD or I2CWRITE statement. Do it first and keep the statements as clean as possible. Always do what the book says. It says use a particular kind of variable, then use a particular kind of variable. It doesn't say Math is allowed, and doesn't show you examples with Math - so don't do it.
You DON'T need PAUSEs for READING - you can do that at top speed. You DO need them for writing - the EEPROM Datasheet will tell you how much is required.
Thanks Luckyborg. Think DT answered the question, and will keep an eye on patches to 2.60.
Bookmarks