Using UAMP in Abaqus 6.12
Using UAMP in Abaqus 6.12
(OP)
Hello everyone,
I'm experiencing a very annoying issue with Abaqus 6.12. I'm using the UAMP subroutine to impose the displacement of some nodes relatively to the position of a reference sensor.
Everything worked fine in version 6.11, but since my lab updated to 6.12, the job crashes as soon as the subroutine is called, with the error "illegal memory reference (signal 11)". I have the following error in the .msg file :
It crashes at the line
I copied/pasted the code template from the documentation and only added a couple of line, including that one.
My sensor is defined as an History Output named Sensor containing only U1 on the node set called SENSOR (containing 1 vertex). The output is active for the desired step. I repeat that everything worked perfectly in 6.11 and the only change was the Abaqus update. I don't use any customized environment.
Does anyone knows about some changes in the implementation of the GETSENSORVALUE function? I couldn't find anything in the 6.12 release note. Maybe I should change my definition of the sensor?
Thanks
I'm experiencing a very annoying issue with Abaqus 6.12. I'm using the UAMP subroutine to impose the displacement of some nodes relatively to the position of a reference sensor.
Everything worked fine in version 6.11, but since my lab updated to 6.12, the job crashes as soon as the subroutine is called, with the error "illegal memory reference (signal 11)". I have the following error in the .msg file :
CODE
***ERROR: Sensor SENSOR cannot be found but is accessed in UAMP. Please make sure that this sensor is defined for this step.
CODE
DISPLACEMENT = GETSENSORVALUE('SENSOR',jSensorLookUpTable,
* sensorValues) My sensor is defined as an History Output named Sensor containing only U1 on the node set called SENSOR (containing 1 vertex). The output is active for the desired step. I repeat that everything worked perfectly in 6.11 and the only change was the Abaqus update. I don't use any customized environment.
Does anyone knows about some changes in the implementation of the GETSENSORVALUE function? I couldn't find anything in the 6.12 release note. Maybe I should change my definition of the sensor?
Thanks





RE: Using UAMP in Abaqus 6.12
CODE --> ABAQUS_INP
The name must be Sensor; frequency does not have to be equal to 1.
http://www.eng-tips.com/faqs.cfm?fid=376
http://www.eng-tips.com/faqs.cfm?fid=1083
RE: Using UAMP in Abaqus 6.12
CODE --> ABAQUS_INP
http://www.eng-tips.com/faqs.cfm?fid=376
http://www.eng-tips.com/faqs.cfm?fid=1083
RE: Using UAMP in Abaqus 6.12
But good to know.
RE: Using UAMP in Abaqus 6.12
I noticed that when using version 6.11, the variables nSensor and sensorNames, passed with the UAMP subroutine were not empty and indeed contained the number of sensors and their names. In version 6.12 nSensor=0, just as if there weren't any sensors. This is why the subroutine crashes, but I really wonder why the sensor definition is not working at all in the latest version...
Maybe I'll keep working with the older version and contact the Abaqus support? I'm suspecting some kind of bug here!
RE: Using UAMP in Abaqus 6.12
Senor name changes befor is passed into the UAMP/VUAMP subroutine.
All white signs are removed, the letters are upper case and left justifice.
It means in the inputdeck you can write the name as you want in the subroutine it has to be capital letters.
Following thre names are avaiable inside the sub as 'SENSOR': 'Sensor', 's e n s o r', 'S e N s o R'.
It's not a bug it is a feature
In Abaqus 6.12-2 there is a new subroutine interface.
You can now pass information from the inputdeck inside the sub with props array.
So in list of dummies arguments you have two new variables nProp and props.
Of course there are also new variables definition.
You cannot take subroutine from 6.11 and run with 6.12, before that you have to updated subroutine's interface.
For details please check Abaqus 6.12-2 Releas notes.
Best,
Bartosz
RE: Using UAMP in Abaqus 6.12
I saw that there were some changes reported in the release notes, but I thought the problem came from the sensor definition.