For the Ansible thing I'm seeing:
- I2C stays healthy with the Ansible; it still responds to read requests.
- Set values are persisted and returned when reading.
- More often it is the CV LEDs and output values that get locked; rarely it will be the trigger outputs (same symptom - LEDs frozen and no trigger voltages on the jacks).
It feels to me like the Ansible's i2c is healthy and that some other process on the unit is loused up, which is causing it to stop updating the LEDs and CV voltages. I haven't dug around in the code - so I really don't know what I'm talking about here. So, sorry if I'm wasting ASCII characters.
On a side note, I want to thank EVERYONE who has helped with this troubleshooting. I've spent the last year building out these two expanders (TXo and TXi) and was starting to sweat heavily about the integration. With the work that you have done and supported with your tests and thoughts in the last week, the expanders are now totally solid with the Teletype. I'm a month or two from being able to ship out a bunch of them to folks and, when that happens, each and every user will be indebted to you for helping ready the platform for their arrival.
Here is a video I posted over in the Teletype Expanders thread with 24 Triggers, 24 CV Values, and 16 reads (8 knobs and 8 CV values) running at 100ms: