Part Number: ISOW7841
Currently we are facing an issue when using 2 isolator parts in parallel and trying to control 2 ADS129* parts in Daisy Chain Mode.
We are finding some issues as follows:
1, When we power up the board, we supply 3v3 to VCC1 of the ISOW part, and can read 3v3 on VCC2. As soon as we try write data to the ISO and ISOW parts, the voltage on VCC2 drops to 2V and never recovers, until we powercycle the board
2, When we try and write commands across either ISO part (ISO and ISOW) we do not read any data on the output of the isolator devices. We only get data across when we remove the parts and manually bridge the gaps with wire
3, I don't know if this is relevant to the Isolation forum, but our ADS129* are not working, as we do not get any activity on the DRDY pin when we remove the isolators.
Thanks for reaching out to us. I remember us discussing a related topic in the past, I am copying below the other related E2E post you had posted earlier. I believe you had mentioned that there was something wrong with the schematic and you will be working to fix the same, were you able to fix the schematic and make the isolators communicate normal?
VISO voltage can get disturbed for the following reasons,
Please do let us know if your application violates any of the above points listed. Thanks.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Koteshwar Rao:
Thanks for your reply, to answer your points:
Do you have any other suggestions on why it would not be working?
In reply to James Hatswell:
Hi James,While Koteshwar responds, below are some common debug E2E posts you can reference regarding the ADS129x silence on /DRDY pin. The PADC team informed me this resembles a startup issue:Respectfully,Manuel Chavez
In reply to Manuel Chavez:
thanks for the reading material! If I had a question about our setup, would it be best asking it on this thread or shall I start a new one? ( I don't know if there is a link between our problems hence why I included the ADS129*)
We have managed to fix the problem, it turns out that our /RESET was being pulled low so the device was not able to communicate at all.
Thanks for all your help guys!
Hi James,You're welcome! We're glad to have helped and wish you success on your projects.Thank you for posting to E2E,Manuel Chavez
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.