error id 760
Altair Employeein solver ,it is showing error id 760
any solution please....?
Altair EmployeeHi
The corrected file is shared here.
Thank you very much PranavHari.
Altair EmployeeHi,
I am trying to model the contact between a sphere and a plate, but when I run I get the same error message: 'ERROR TRAPPED : REPORT TO LISTING FILE
ERROR ID : 760'. I tried but I didn't manage to fixe it.
Please could somebody help me?
Thank you,
Guerric
Hi Guerric,
there are some modeling errors, listed from the starter .out file:
ERROR ID : 60
** ERROR IN PROPERTY/ELEMENT DEFINITION (TYPE)
DESCRIPTION :
INVALID PROPERTY TYPE ,
FOR BRICK ELEMENT
shell property is defined for brick elements, which is incompatible.
ERROR ID : 1125
** ERROR IN PART/ELEMENT DEFINITION
DESCRIPTION :
INVALID PART ,
FOR SHELL ELEMENT
all components containing FE entities should have card image set to Part.
There were also some shell elements which were used for solid mesh creation but should be deleted before the simulation.
Always check the .out file for warnings and errors and use Tools>Model Checker>RadiossBlock for debugging purposes.
Hi yugang
You can click delete button from the tool bar, select elements by config.
Then select the shell elements and click, delete
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
Altair EmployeeHi Ivan,
Thanks a lot for your answer.
I tried to run it, but I got another problem related to the cinematic conditions:
WARNING ID : 312
** INCOMPATIBLE KINEMATIC CONDITIONS IN MODEL
DESCRIPTION :
9 INCOMPATIBLE KINEMATIC CONDITIONS IN MODEL
I know it comes from the creation of the velocity with BCmanagers, would you have any idea how I can fixe it by any chance?
Also, I am using the version 2017.2, which is perhaps an older version than yours...
Thanks a lot again,
Guerric
RADIOSS Starter does not check if the kinematic conditions are truly incompatible. You have constrained the independent node of the rigid in all but Y traslational DOF and also imposed velocity in this direction so those kinematic conditions are compatible. But there are examples where they are not incompatible (see attached documentation from Help)
I also revised the boundary conditions (the referred node for liberty and velocity was not the same) and contact definition (slave component was not specified, also I activated some flags) and moved the plate closer to ball by 27 units so the contact happens earlier.
You can click delete button from the tool bar, select elements by config.
Then select the shell elements and click, delete
while this procedure does the job it will delete all shells, including shell elements that might be desired in the analysis.
Altair EmployeeHi Ivan,
Thank you a lot for you several answers and modifications, that works now much better! We're trying now to understand all what you did 
Guerric
Altair EmployeeHi,
Please I have a probleme with the model that Guerric talk, about in fact it calculate but there is no results.
their is another probleme which is the Arrow that is up,while the ball should go down.
please help us.
thanks a lot.
the model you shared failed to run for no good reason. Sometimes it helps to save the model with a different name.
I do not see any problem with the model, other than it could benefit from mass and/or time scaling so I defined advanced mass scaling (AMS & AMS/DT keywords).
Altair Employeehello!
Please I have a problem with the same project, in fact when i had made the plat a rigid body the radioss not work, and it write the folowing warning:
WARNING ID : 1190
** CONNECTION THROUGH RBODY OVER AMS AND NON AMS DOMAINS
.. DOMAIN DECOMPOSITION
.. ELEMENT GROUPS
.. INTERFACES
.. INTERFACE BUFFER INITIALIZATION
.. RIGID BODIES
.. ELEMENT BUFFER INITIALIZATION
WARNING ID : 312
** INCOMPATIBLE KINEMATIC CONDITIONS IN MODEL
please help us to make this project with boot the ball and the plat rigids.
thanks a lot
Hi,
Radioss will finish the run after 1 cycle if everything is covered by rigid element, i.e. there are no deformable elements.
** CONNECTION THROUGH RBODY OVER AMS AND NON AMS DOMAINS
If rigid body overlaps the AMS and non AMS domains, the AMS will expand overall the rigid body if Iexpams is set to 1. You can do that manually (HM does not support this keyword) or use HyperCrash to edit the rigids. If the Iexpams is set to 0 (by default) then AMS will not be effective on components which have rigids connected to them.
Altair Employeehi !
thanks a lot
when i made oly the plat rigid there are no result , i Don't know why
thanks for your support
This kind of problem is unphysical: you are forcing nodes (imposing velocity) to penetrate into the rigid plate which is non-deformable.
To simulate impact the ball should have an initial velocity so the nodes are free to deform according to the laws of physics after impact.
Also, boundary conditions should only be applied to the master node of the rigid body.
Hi RaghuDobbala
The error was due to 2 reasons
1. The Master nodes were not defined for self contact type 7
2. Card image for the Rigids is NONE, but it was assigned as PART
Once the run is completed i will share the file here.
Hello, also in solverit is showing error id 760
Hi RaghuDobbala
The error was due to 2 reasons
1. The Master nodes were not defined for self contact type 7
2. Card image for the Rigids is NONE, but it was assigned as PART
Once the run is completed i will share the file here.