For anyone that’s interested, the ADAMS documentation lists the following for FORTRAN compiler options:
/c /architecture:pn4 /MD /Ob2 /automatic /Z7
(Z7 is used for debug mode, and can be removed)
I’ve also run into the same error as Juan:
! ERROR: GFOSUB(11010, 1, 1, 0, 11010) has been illegally defined. A new functional dependency on the measure
! TDISP(11010,1,1) has been encountered during execution.
‘Error calling INFARY for blade element coordinates.’
It should be noted that using INFARY instead of SYSARY is not only causing errors to crop up in different versions of ADAMS (I use MD ADAMS x64), but it will also cause poor convergence rates for the ADAMS solver. Using SYSARY requires declaring a dependency so that ADAMS knows to perturb those markers in the Jacobian. Using INFARY does not. This is really bad news since the forces between blade nodes should definitely depend on the displacement of the markers on either node. I’m actually surprised that the ADAMS simulations converge at all, considering most of the system consists of the blade nodes & connecting force elements. If you have access to the ADAMS user forums, I found info on the topic here, and it’s from an extremely reliable source:
forums.mscsoftware.com/adams/sho … #Post53469
I have a feeling the A2AD simulations would run much faster and crash a lot less if those INFARY calls were replaced with their proper SYSARY counterparts.
Justin