I'm trying to track down the cause of a line fault during discovery, I figured my first step would be to see what bits were flying around on the I2C bus to hopefully see why the software is failing (I've shown separately there is no actual fault).
The capture window in SS+ is awful for pretty much anything (hint hint, SS+ needs some improvement) I exported that to the sequence window, then exported that to xml, and then edited the xml so Excel won't barf importing it, and then opened up the xml in Excel to filter out the crud...
What got saved is very incomplete. Only traffic for sub nodes up to 5 got captured, and the error I'm chasing is out at node 15. [I can redo things to a smaller example and then maybe the capture window becomes useful but I shouldn't have to fight with the tools!]
Here's the end of the capture window contents (since sub-node names are arbitrary and can't be edited to reflect actual location 3 is the 5th one.)
(SS+ is 2.2.0 upd 2)
Not sure if this is SS+ bug or an A2B plug in bug but figured I would start here and ask.
*
[edited by: Brewster at 8:50 PM (GMT -4) on 25 Sep 2024]
