Hydrodyn and moordyn error for help

Dear all:
First, my computer is 64-bit.
Then, based on test25 of FAST,I change the floating fundation structure, by using ServoData/DISCON_OC3Hywind_win32.dll of NRELOffshrBsline5MW_OC4DeepCwindSemi_ServoDyn.dat, but when running hydrodyn, it says:
'Generating incident wave kinematics and current time history.
Reading in WAMIT output with root name “.\5MW_Baseline/HydroData/marin_semi”.
Computing radiation impulse response functions and wave diffraction forces.

FAST_InitializeAll:HydroDyn_Init: Error allocating space for the distributed dynamic pressure

forces/moments array’

Then I choose ServoData/DISCON_OC3Hywind_x64.dll ,the hydrodyn is passed, but there is a error in moordyn, it says:

Running MoorDyn (v1.01.02F, 8-Apr-2016).
Creating mooring system. 3 fairleads, 3 anchors, 0 connects.
Catenary solver failed for one or more lines. Using linear node spacing.
Catenary solver failed for one or more lines. Using linear node spacing.
Catenary solver failed for one or more lines. Using linear node spacing.
Finalizing ICs using dynamic relaxation.
t=10 FairTen 1: 73522, 73908, 72804
Fairlead tensions converged to 1% after 10 seconds.

apping_ProjectToLine2:Node 1 does not project onto any line2 element.

FAST encountered an error during module initialization.
Simulation error level: FATAL ERROR

I fail to find the error by my own efforts, so I sincerely seek help.

Dear Yuanzhao,

Regarding 32-bit versus 64-bit, I’m assuming when you say that you chose “ServoData/DISCON_OC3Hywind_x64.dll” you mean that you also switched to using the 64-bit FAST executable, FAST_x64.exe? All of the models NREL has provided in the CertTest, including Test25, run with the 32-bit executable on a 64-bit machine, but if you added nodes to the HydroDyn model, you may need to upgrade to the 64-bit executable to handle the additional memory requirements.

I’m not familiar enough with the inner workings of MoorDyn to know if the warning messages you are receiving about the failure of the catenary solver are important; it seems that MoorDyn initial-condition (IC) solution converged regardless.

The error that is causing FAST to abort is relating to the mesh-mapping search for ED_L_2_AD_L_T, which is the mesh-mapping search between the ElastoDyn Line2 tower motion output mesh and the AeroDyn Line2 tower motion input mesh. I’m not sure why this error is triggered in your case, but my guess is that you’ve changed the tower definition or discretization in some way in either ElastoDyn or AeroDyn? FAST will trigger this error e.g. if the tower in AeroDyn starts lower than the tower in ElastoDyn or if the tower in AeroDyn ends higher than the tower in ElastoDyn.

I hope that helps.

Best regards,