If it helps for debugging, you can write information to specified Fortran file unit numbers from the user subroutine to get information in the output file. That would at least allow you to confirm the user subroutine is working in 64-bit so that you can focus on any issues connecting it to Abaqus. You mentioned several combinations you have tried in testing, and do you also have a main program to run the user subroutine outside of Abaqus? That approach has been useful for me to confirm that I can call the user subroutine many times from a "main" program (not Abaqus) with a range of data and get expected return values. This may help to be certain that the 64-bit build is getting used by Abaqus to avoid mixing 32 and 64 files, as Steve mentioned. (Make changes for your installed versions). Start -> Intel Parallel Studio XE 2017- > Compiler 17.0 for Intel 64 Visual Studio 2015 environment I open the Intel Fortran console from the Start menu as: That way all the Intel Fortran variables are initialized in that console window for Abaqus to use. How do you run the Abaqus job with the user subroutine? Not sure if this will help, but I have had success running Abaqus with user subroutines by opening the Intel Fortran console first, and then run the Abaqus job from there. f file, and it is not in the Abaqus model (even though it is somehow influenced by it). In summary, it is a problem related to the interface between Abaqus and Intel Composer, but it happens only sometimes. I tried to uninstall Intel Composer and reinstall it but it did not fix the issue. I also tried in three different machines, but I get the same error. This same model with the same user subroutine works with Abaqus 6.11-3, Intel Composer 2011, Visual Studio 2008. However as soon as I change any parameter or geometry the simulations gives me the same error again. Then I uncommented these lines one by one and after few attempts the model ran (the same model that did not run the first time I tried!). user defined amplitude cards, sensor outputs) and the model suddenly worked.
What is even stranger is that trying to debug the problem I started commenting out the parts of the model in the Abaqus input file that interface with the user subroutine (e.g. However I did not make any change to the VUAMP.f file. When I try running the model without the user subroutine it runs fine, so it's not a problem with the geometry. Now I am changing few things in the geometries of the model and I got this error. I have been running this same model for a while and I had no problems. I am using Abaqus 6.14-2, Intel Parallel Studio XE 2013 SP1 and Visual Studio 2012. I am running an Abaqus 6.14 simulation using the user subroutine VUAMP.f and I get the "Unexpected LoadLibraryA error 193".
0 kommentar(er)
