You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am attempting to reverse engineer an existing spa controller, and would like to target a specific I2C address that correlates to the topside panel. I need to passively monitor the bus so the spa can continue to work as intended, but the main controller is constantly spamming out a bunch of different addresses. All of these addresses (other than the topside panel) don't appear to be present and just result in hundreds of NACKs and repeated read/writes each cycle. I've been using a cheap Chinese logic analyzer and PulseView, but the process is pretty inefficient and slow to analyze.
From what I see in the wiki, the 'sniff' command is what I should focus on - but I don't see a way to have it only sniff a specific address or data pattern. My oscilloscope has this feature, but maxes out at seven messages per capture.
Would this be a feature that could be implemented in your project?
It would also be great if the user could specify an sample period and number of samples in each period to log in an attempt to decrease the number of duplicate messages being ingested.
I'd be happy to answer any questions or clarifications you might have!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
First off, this is an amazingly cool project!
I am attempting to reverse engineer an existing spa controller, and would like to target a specific I2C address that correlates to the topside panel. I need to passively monitor the bus so the spa can continue to work as intended, but the main controller is constantly spamming out a bunch of different addresses. All of these addresses (other than the topside panel) don't appear to be present and just result in hundreds of NACKs and repeated read/writes each cycle. I've been using a cheap Chinese logic analyzer and PulseView, but the process is pretty inefficient and slow to analyze.
From what I see in the wiki, the 'sniff' command is what I should focus on - but I don't see a way to have it only sniff a specific address or data pattern. My oscilloscope has this feature, but maxes out at seven messages per capture.
Would this be a feature that could be implemented in your project?
It would also be great if the user could specify an sample period and number of samples in each period to log in an attempt to decrease the number of duplicate messages being ingested.
I'd be happy to answer any questions or clarifications you might have!
Thank you!
All reactions