
A2B network fails to discover sub-node on EVAL-AD2428WD1BZ + Molex accelerometer — "Main Running Interrupt Not Detected", 0 nodes found
KCC's Quizzes AQQ304 - A pure logic
1. Quote of the month: "I am not lazy, I'm just in energy-saving mode" - unknown
2. Quiz AQQ304 about finding a pure logic puzzle
Mike is looking at Anne, but Anne is looking at Paul.
Mike is married, but Paul is not.
Question:
Is a married
View All
September Monthly Blog Quiz! Read the blog, take the quiz, and you could win a gift card
Quiz: How Well Do You Know Adaptive Power Switching?
Is your I/O module overheating? The AD74416H's Adaptive Power Switching (APS) can cut heat dissipation by up to 40% — but how well do you really understand how it works?
Read the blog first: Cooling
View All

A2B network fails to discover sub-node on EVAL-AD2428WD1BZ + Molex accelerometer — "Main Running Interrupt Not Detected", 0 nodes found
Trying to get a single-node A2B setup working: EVAL-AD2428WD1BZ as Main, connected via ~1m cable to a Molex A2B accelerometer (part 2047490013-SD) as the only sub-node. Every Link + Download in SigmaStudio gives:
Main Running Interrupt Not Detected Number of sub Nodes discovered: 0
Things I've already checked, all fine:
New thing I found: I can Read/Write the Main's registers fine once connected, but the sub-node's registers (e.g. trying to set I2SGCFG/I2SCFG per Molex's app note) are completely greyed out, even with checkboxes ticked. Guessing that's because sub-node access has to relay over A2B, which needs discovery to succeed first — so it's really just one root problem.
Anyone seen this before or got ideas what else to check? Trying to avoid buying a Bus Analyzer if there's a simpler explanation I'm missing.
Thanks
> Main Running Interrupt Not Detected
Means USBi is not fully talking to your main node. Since you can read main node I2C it's almost certainly a bad frame sync (has to be 48 kHz). Check at the AD2428 pin.