10-28-2019, 07:13 PM
Don't let the dosing container run low and problem solved lol, just kidding of course.
You brought this up at a good time, with the help from a customer we discovered a pretty big overlook on my behalf.
Remember when I first released v5.0 many had issues with I2C going down, the likely reason for all these issues was in the lighting code.
When a fade runs the controller was sending an update to the PCA9685 PWM chip about 1500 times per second or more which flooded the I2C bus with data, frankly it's amazing it works at all.
I completely over looked this as the fade code was the same as v4.2 but the difference was v5.0 runs so much faster than v4.2. v4.2 couldn't run fast enough to flood the bus.
I will have an update ready soon which has a lot of small issues fixed but will email the current sketches now.
You brought this up at a good time, with the help from a customer we discovered a pretty big overlook on my behalf.
Remember when I first released v5.0 many had issues with I2C going down, the likely reason for all these issues was in the lighting code.
When a fade runs the controller was sending an update to the PCA9685 PWM chip about 1500 times per second or more which flooded the I2C bus with data, frankly it's amazing it works at all.
I completely over looked this as the fade code was the same as v4.2 but the difference was v5.0 runs so much faster than v4.2. v4.2 couldn't run fast enough to flood the bus.
I will have an update ready soon which has a lot of small issues fixed but will email the current sketches now.
