I ended up having to backtrack to Netburner SKD 2.3. That and your advice of reading 2 bytes is what seemed to work for now.
Reading 2 bytes helped. I stopped getting any errors after that (and going back to 2.3, from 2.5.2... 2.5.2 wouldn't work regardless of what I tried)
Thanks for all your ...
Search found 3 matches
- Wed May 11, 2011 4:48 pm
- Forum: NetBurner Software
- Topic: MOD5270, I2C and latest software problem
- Replies: 4
- Views: 6006
- Tue May 10, 2011 11:18 am
- Forum: NetBurner Software
- Topic: MOD5270, I2C and latest software problem
- Replies: 4
- Views: 6006
Re: MOD5270, I2C and latest software problem
Thanks for the reply. I will open a support ticket.
I tried a Restart, and while I did not get errors, I never got valid voltages from the chip. The ReadBuf seems to always return I2C_NEXT_READ_OK for the first two power-cycle reads, then I2C_TIMEOUT after that.
The chip is the "Maxim Max127 ...
I tried a Restart, and while I did not get errors, I never got valid voltages from the chip. The ReadBuf seems to always return I2C_NEXT_READ_OK for the first two power-cycle reads, then I2C_TIMEOUT after that.
The chip is the "Maxim Max127 ...
- Tue May 10, 2011 5:19 am
- Forum: NetBurner Software
- Topic: MOD5270, I2C and latest software problem
- Replies: 4
- Views: 6006
MOD5270, I2C and latest software problem
We have the MOD5270. Our old NetBurner software is from around2009ish... I've formatted my computer since then, so I do not have it. We bought the latest software, and I ported the source code into a new project. The OLD .s19 program reads the I2C values correctly. The exact same source code ...