Learning Forum

[ludvig]

Have followed the Ansys recommendation to use IPC2581-B, USERDEF with all boxes ticked except "Export Cross Section Data Only".
When importing into SIwave:


Logfile says:

Looking into the xml-file, it does include stackup information. It can also be opened in free IPC2581 viewers with stackup data present.

[Aymen Mzoughi]

Try using the SIwave PinToPin utility found in the "Tools" tab in SIwave for the import

[ludvig]

 

 

 

 

Thanks for your suggestion. Using PinToPin gives the same error.
I compared the generated XML-file to a reference file from IPC, and found that Cadence had written the level in the file while the reference file had not:

Cadence file: 

   

IPC reference file:   

   

If I removed the level=”1″, Ansys finally accepted the file and imported!

I thought I had sorted it out, but today when trying to import another project, the import fails again. It does not help to remove the level=”1″ this time.

Looking at the log file from the failed import it doesn’t tell anything. It seams to fail before the log file is completely written.

Translation Log file
AnsTranslator Path: C:\Program Files\ANSYS Inc\v251\AnsysEM\anstranslator.exe
Input: C:/Temp/dcdc layout.xml
Output: C:/Users/xxxxxx/AppData/Local/Temp/dcdc layout.aedb
Translation Start: Thu May 29 20:54:55 2025

I’m running 2025R2.

Please help, I cannot use the program if I cannot import anything to it…

 

 

 

 

[ludvig]

I found the isse. The variable value

[imdog394]

What is "The variable value"? I encounter this issue too.

 

[ludvig]

Check the XML-file for the variable "Person name". This variable gets the name of your Windows account used when you generated the IPC2581 in OrCAD. In my case, my account name includes a scandinavian character. It seems that Ansys IPC2581 import can't handle those non-standard characters. Just remove the non-standard character or remove the whole line in the XML-file, it's not used for anything in Ansys. After doing this, Ansys smoothly imports everything I have thrown at it. I have reported the bug to their support.