Computer Aided Engineering Journal & Forums

Full Version: Subroutine SIGINI doesn't work...
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello !

I would like to use subroutine SIGINI in Abaqus Standard. I create a simple model without load, only SIGINI prestress.
So, I add in .inp file :


** INITIAL CONDITIONS
**
** Name: BC-3 Type: Stress, user



just before STEP and after Boundary Conditions.
The subroutine used is very simple, just sigma(1)=500.
I attach subroutine file containing SIGINI to the job :

abaqus job=carre_precontr user=precontr.f



My job runs neither warning nor error : "job completed successfully".

BUT, when I open .odb file in visualisation, the result is the same withor without SIGINI (stress=0 , displacements=0 , ...).
Do you know why ?
I want my subroutine to become activ, how I do that ?

Regards

Laura
Why are you putting '**' in front of everything? This usually denotes comments in the input file, no wonder nothing happened Smile

The correct syntax is:

*INITIAL CONDITIONS,TYPE=STRESS, USER
Thank you.
But it's a typo ! Sorry...

Even they are only one star "*" :

** Name: BC-3 Type: Stress, user
*Initial Conditions, Type=Stress, User

I have the same result (stress=0, displacements=0, ...)


NB : When I import the input file, I have this warning :

The model "carre_precontr" has been created.
The part "PART-CARRE" has been imported from the input file.

WARNING: The following keywords/parameters are not yet supported by the input file reader:
---------------------------------------------------------------------------------
*INITIALCONDITIONS, TYPE=STRESS
The model "carre_precontr" has been imported from an input file.
Please scroll up to check for error and warning messages.


So the initial conditions can't to be read. I don't know why. Do you have any idea ?

Regards
This could be another typo but the warning message seems to suggest that the keyword is being read in as *InitialCondition....there should be a space between the two.

A good way to check if the UMAT is being entered at all is to get it to write to the message file when it is exexcuted. I can't remember off the top of my head what unit it is but have a look at the User Subroutine manual. A simple

print(unit,a) 'Test'

Or something like that will do the job.
Reference URL's