Post Go back to editing

Discovery Delay

Thread Summary

The user is experiencing issues with the AD2433W A2B sub-device discovery in Sigma Studio 2.3, receiving junk data from the custom node ID (0xA003000D) during the first discovery attempt. The final answer suggests using the peripheral configuration window in the analyzer to parse the XML file after discovery, allowing for proper initialization of the sub-device. The user should consider adding a delay after setting A2B bias high to ensure the sub-device has enough time to wake up before discovery.
AI Generated Content
Category: Software
Product Number: AD2433W
Software Version: sigma studio+ 2.3

Hello,

I am using an AD2433W as a main and another as a sub. I am configuring all my settings in Sigma studio+ 2.3. I am having a little trouble in the discovery phase. My sub device is woken up when A2B bias is high (Phantom power). I am discovering using a custom node identifier. The main device brings the sub out of sleep mode with A2B bias and then performs a discovery. I noticed that when my main device attempts discovery, I get junk from the custom node ID (0xA003000D), but if I attempt a discovery again rapidly, my sub node gets discovered properly. This leads me to believe that my sub device is not given enough time to wake up before a discovery is performed. Is there a way to add a delay after I set a2b bias high and just before discovery to give my sub node time to initialize?

Here are the logs from a failed discovery:

Here are the logs from a successful discovery:

Edit Notes

Captured logs using A2B bus analyzer
[edited by: SudoObey at 6:07 PM (GMT -4) on 22 Sep 2025]