Hi,
Abaqus converts all names to upper case and removes all white signs.
In your case you need use:
if (cmname .eq. 'MATERIAL-1') then
Bartosz
VIM filetype plugin for Abaqus
https://github.com/gradzikb/vim-abaqus
Hi,
FORTRAN layout is spilt into declaration and executable section.
Declaration section is first and executable second, you must not mix these two sections.
The executable section starts after first executable line and after it you must not put any declaration lines.
Here is executable...
Hi
You defined AREA variable as parameter it means the variable never change value and always will be 0.0.
PARAMETER(RADIUS=0.15D0,AREA=0.D0)
but next you try to change AREA value
AREA=AREA+AREA1
Bartosz
VIM filetype plugin for Abaqus
https://github.com/gradzikb/vim-abaqus
Hi
You can define name and description for each state variable.
**
*DEPVAR
** number of variables
3
** variables list
1, outputKey1, outputDescription1
2, outputKey2, outputDescription2
3, outputKey3, outputDescription3
**
Bartosz
VIM filetype plugin for Abaqus...
Hi,
It you prefer to work directly with abaqus inputdecks in text editor the plugin make work easier.
However it is for VIM text editor so you have to know it.
Regards,
Bartosz
VIM filetype plugin for Abaqus
https://github.com/gradzikb/vim-abaqus
Hi,
Your example is incorrect and interpolation can not be done in this case.
From Abaqus documentation (21.1.2 Material data definition, Interpolation of material data)
For three field variables with values in range from 0 to 2 we must define lines:
**
**
50 0 0 0
30 1 0 0
20 2 0 0
**
50 0...
Hi,
You must not use more than one USDFLD subroutine.
You can test your material name with CMNAME variable to do different operation for each material in your model.
See following thread for more info:
http://www.eng-tips.com/viewthread.cfm?qid=314887
Regards,
Bartosz
VIM filetype plugin...
Hi,
I ran your model and I noticed FV1 vary between value of 145.0 and 375.0.
With your material definition it make sense only when FV1 vary from 1.0 to 2.0.
Abaqus use constant extrapolation outside field variable range so any value above 2.0 will use E=2e+09.
Please check your equation...
Hi,
Could you share your inputdeck and subroutine, please?
I will take a look for it.
Regards,
Bartosz
VIM filetype plugin for Abaqus
https://github.com/gradzikb/vim-abaqus
Hi,
It looks like your UMAT is wrong, to be more precise FORTRAN does not like line 14 "4 JSTEP(4)".
If you compare your UMAT arguments with documentation you will find a mistake. One before the last argumnent is JSTEP not KSTEP.
SUBROUTINE UMAT(STRESS,STATEV,DDSDDE,SSE,SPD,SCD,
1...
Hi Jungao
>>> Is it correct that we need to declare 'save' in the beginning, then they are saved as global variables
By default all variables used in subroutine are not controlled after call.
It means part of memory where your variable is stored can be overwrite by any other program or Abagus...
Hi Jungao,
I have never used URDFIL subroutine so I know nothing about it.
But as long you are ok with displacement and velocity of integration points you can evaluate them in DLOAD.
! keep values in memory
save rPrevCOORDx
save rPrevCOORDy
save rPrevCOORDz
save rPrevTIME
! disp =...
Hi Jungao
It is good to hear that it is starting to work as you expecting.
One advice from my side. You really should not depend on "187 offset" between user and internal ids.
It's probably true only for this one model, or maybe not. It is high likely with different Abaqus version/number of...
Hi Jungao,
>>> I have also attached the .dat file for your information
There is no attachment.
>>> I suppose when ABAQUS call the subroutine DLOAD, it's actually looping in main function ABAQUS to define F for each element integration point
Yes.
>>> the size of the loop is (element...
Hi Jungao,
To be honest I am still confuse about your load. I understand that each beam element will get different load.
The load is calculate outside DLOAD subroutine and next stored (by initialization and/or reading from external file) in FY array.
The FY array structures is:
FY(1) : load for...
