v0.9.0 vs. v1.0.1 in I2C communication
Posted: Thu Jan 31, 2013 1:28 pm
Hey all,
I was trying to make some updates to my auxillary monitor (original RA connected to the I2C), but ran into some problems. When I uploaded the ino to the second monitor the main RA+ kind of goes nuts with relays turning on and off quickly. This doesn't happen when all I load into the RA is an internal memory ino. But any basic RA ino causes this effect. I was at my wits end trying to figure it out when I remembered that the code on it now was loaded with the v0.9.0 libraries. I switched out the libraries and everything went back to normal with the I2C sending data from the RA+ to the RA. I have no idea what changed that would cause this problem, but if folks want to upgrade to the RA+ and still get some use out of the original RA, as a second monitor like I did or as an expansion module for pH, temp, IO, etc they may run into this same issue.
Jon
I was trying to make some updates to my auxillary monitor (original RA connected to the I2C), but ran into some problems. When I uploaded the ino to the second monitor the main RA+ kind of goes nuts with relays turning on and off quickly. This doesn't happen when all I load into the RA is an internal memory ino. But any basic RA ino causes this effect. I was at my wits end trying to figure it out when I remembered that the code on it now was loaded with the v0.9.0 libraries. I switched out the libraries and everything went back to normal with the I2C sending data from the RA+ to the RA. I have no idea what changed that would cause this problem, but if folks want to upgrade to the RA+ and still get some use out of the original RA, as a second monitor like I did or as an expansion module for pH, temp, IO, etc they may run into this same issue.
Jon