TAGGED: aedt
-
-
April 4, 2023 at 7:17 am
Eglantine PERRON
SubscriberI'm simulating a circuit in AEDT with IBIS AMI models of a component. However, these models use a version 6.0 or 6.1 which seems not to be supported by ANSYS. I get the following error message on the console "Unexpected engine termination" and "ERROR - AMI_Version 6.0 is not valid" on the Linux console. Have you ever had this problem and it is possible to solve it ?
-
April 4, 2023 at 1:13 pm
Dan Dv
Ansys EmployeeAEDT Circuit does support IBIS 6.x AMI models. So I'm not sure the exact reason for that error. Can you go to the full log file (right mouse click on the AMI definition in the project manager and select "browse log file") and paste the full error message in question from that log here?
-
April 4, 2023 at 2:13 pm
Eglantine PERRON
SubscriberThanks for your response. I don't have error message in the full log file but only this :
(info): Procesing circuit for new analysis
omp(status): Requested number of threads in UI setting is 16
-
April 4, 2023 at 2:21 pm
Dan Dv
Ansys EmployeeThat seems odd. Any simulation warning or error that appears in the message manager should also be in that log file. You may need to try re-simulating. Worst case, if you can copy the full message out of the message manager that may give me a little bit more to go on.
-
April 5, 2023 at 7:46 am
Eglantine PERRON
SubscriberI re-simulated several times there is still nothing. On the Linux terminal I have the following messages :
WARNING - Filename 'PolarFire_IBIS_AMT_SR_Model.ibs' should be lowercase
ERROR (line 5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'P'.
ERROR (line 5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'F'.
ERROR (line 5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'I'.
ERROR (line 5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'B'.
ERROR (line 5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'I'.
ERROR (line 5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'S'.
ERROR (line 5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'A'.
ERROR (line 5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'M'.
ERROR (line 5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'T'.
ERROR (line 5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'S'.
ERROR (line 5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'R'.
ERROR (line 5) - File_name 'PolarFire_IBIS_AMT_SR_Model.ibs' contains an upper case character 'M'.... Reading PolarFire_IBIS_AMT_SR_Model_100.ami
WARNING - Filename 'PolarFire_IBIS_AMT_SR_Model_100.ami' should be lowercase... Checking PolarFire_IBIS_AMT_SR_Model_100.ami for Implicit AMI Version 5.0 Compatibility...
ERROR - AMI_Version "6.1" is not valid
... Done Checking PolarFire_IBIS_AMT_SR_Model_100.ami
... Done Reading PolarFire_IBIS_AMT_SR_Model_100.ami
... Reading PolarFire_IBIS_AMT_SR_Model_150.ami
WARNING - Filename 'PolarFire_IBIS_AMT_SR_Model_150.ami' should be lowercase... Checking PolarFire_IBIS_AMT_SR_Model_150.ami for Implicit AMI Version 5.0 Compatibility...
ERROR - AMI_Version "6.1" is not valid
... Done Checking PolarFire_IBIS_AMT_SR_Model_150.ami
... Done Reading PolarFire_IBIS_AMT_SR_Model_150.ami
... Reading PolarFire_IBIS_AMT_SR_Model_float.ami
WARNING - Filename 'PolarFire_IBIS_AMT_SR_Model_float.ami' should be lowercase... Checking PolarFire_IBIS_AMT_SR_Model_float.ami for Implicit AMI Version 5.0 Compatibility...
ERROR - AMI_Version "6.1" is not valid
... Done Checking PolarFire_IBIS_AMT_SR_Model_float.ami
... Done Reading PolarFire_IBIS_AMT_SR_Model_float.amiIt wouldbe better to send you the project with the IBIS models that I took directly from the microchip's website.
-
April 5, 2023 at 2:35 pm
Dan Dv
Ansys EmployeeThose appear to be comittee parser messages. That implies as hard failure with respect to the IBIS file rules. I'll look into that further. I probably should have asked earlier. What version of AEDT are you running?
-
April 5, 2023 at 2:41 pm
Eglantine PERRON
SubscriberI use AEDT 2021/R2.2
-
April 5, 2023 at 2:48 pm
Dan Dv
Ansys EmployeeOK. Those really look like IBIS comittee parser errors. You can download the stand alone version of that here:
IBISCHK
If you run the stand alone checker on these files and get these errors then it is something that the model writer needs to addres. -
April 6, 2023 at 2:41 pm
Eglantine PERRON
SubscriberI tried. Indeed I have errors on one of the models. The first errors are due to the presence of capital letters in the .ibs filename. The second errors are the presence of two identical numbers.
For the second IBIS AMI model I have no errors with IBISCHK but during the simulation I have two error codes that appear in AEDT which are the following :
- Expression cannot be evaluated "CTE"
- Expression cannot be evaluated "agc"
-
April 6, 2023 at 6:08 pm
Dan Dv
Ansys EmployeeCan you also try running the parser on the .ami files? The syntax should be:
ibischk7_64 -ami
I'm not sure what might be going on with those other errors in AEDT about he "CTE" and "agc" parameters. What model set do those come from?
-
April 7, 2023 at 7:55 am
Eglantine PERRON
SubscriberThere are no errors with the .ami files. The models come from Microsemi directly : https://www.microsemi.com/products/fpga-soc/design-resources/ibis-models/ibis-models-polarfire
-
April 12, 2023 at 3:30 pm
Dan Dv
Ansys EmployeeI did download those models and they seem to run for me without errors in 2022R1 and 2023R1. I was running on Windows, and I think you mentioned that you were using Linux. I've asked a colleague to check this on Linux for me. I'll let you know if that shows anything different.
Just to check, are you able to try this on our latest 2023R1 release? -
April 13, 2023 at 1:08 pm
Dan Dv
Ansys EmployeeI did confer with development. The version of the committee parser used in release 2022R1 was not updated to support 6.1. Would you be able to try in a newer version of the tool and let me know if that works better?
-
- You must be logged in to reply to this topic.

Boost Ansys Fluent Simulations with AWS
Computational Fluid Dynamics (CFD) helps engineers design products in which the flow of fluid components is a significant challenge. These different use cases often require large complex models to solve on a traditional workstation. Click here to join this event to learn how to leverage Ansys Fluids on the cloud, thanks to Ansys Gateway powered by AWS.

Earth Rescue – An Ansys Online Series
The climate crisis is here. But so is the human ingenuity to fight it. Earth Rescue reveals what visionary companies are doing today to engineer radical new ideas in the fight against climate change. Click here to watch the first episode.

Ansys Blog
Subscribe to the Ansys Blog to get great new content about the power of simulation delivered right to your email on a weekly basis. With content from Ansys experts, partners and customers you will learn about product development advances, thought leadership and trends and tips to better use Ansys tools. Sign up here.
- simulation completed with execution error on server
- Maxwell, HFSS or Q3D?
- How to export Ansys Maxwell simulation results for post-processing in matlab or in .csv file
- Unable to assign correctly the excitations in a coil
- Running ANSYS HFSS on the HPC (it runs on Linux only)
- Running ANSYS HFSS on multiple nodes on SLURM based cluster
- Intersect errors with model with complex structure
- Error
- Process ‘3dtds’ terminated abnormally
- HFSS: reset marker legend dimensions.
-
5386
-
3375
-
2471
-
1310
-
1022
© 2023 Copyright ANSYS, Inc. All rights reserved.