(measured) Pitch Angle differs to demanded pitch angle

This forum if for discussing controls. Questions about how to implement controls in FAST are more appropriate to the CAE Tools forum.

Moderator: Bonnie.Jonkman

Marvin.Goetzke
Posts: 4
Joined: Fri Apr 26, 2019 7:37 am
Organization: TÜV NORD
Location: Germany

(measured) Pitch Angle differs to demanded pitch angle

Postby Marvin.Goetzke » Mon Jul 08, 2019 7:07 am

Hi,

I have some trouble with the pitch behavior in openFASTv1. As far as I understand the (measured/actual) pitch angle should be the same as the demanded pitch angle. In my case the actual pitch angle oscillates around the demanded pitch angle.
As background knowledge to my problem might be said, the the main controller-DLL (from third party) has a pitch communication interval that differs to the controller step size. To change this I have created a wrapper-DLL which gives one output per controller step. (problem also occurs without wrapper-DLL)
The demanded pitch angle has the correct (favored) behavior. Nevertheless the actual pitch angle shows unfavored oscilations.

Has anyone experienced similar behavior and can suggest a solution?

Best Regards,
Marvin

Jason.Jonkman
Posts: 4223
Joined: Thu Nov 03, 2005 4:38 pm
Location: Boulder, CO
Contact:

Re: (measured) Pitch Angle differs to demanded pitch angle

Postby Jason.Jonkman » Sun Jul 14, 2019 9:56 pm

Dear Marvin,

You are correct that there is no blade-pitch actuator model currently in OpenFAST, so, the commanded / demanded blade pitch should be the actual blade pitch. But because of the solution approach implemented in the OpenFAST glue code, the ElastoDyn module effectively uses extrapolated values of the blade-pitch command as its actual blade-pitch input (the extrapolation is linear with InterpOrder=1 or quadratic with InterpOrder=2). This extrapolation tends to work without problems if the input is smooth / continuous, but can cause problems e.g. overshoots if the input is not smooth e.g. if the blade-pitch command contains steps. I suspect this is what is happening in your case because you said that the controller operates at different time steps. You can reduce or eliminate the error between the command and actual blade pitch angle using a few approaches:
    1) Add a correction step to the solver (NumCrctn>0) in the OpenFAST primary input file.
    2) Use linear (InterpOrder=1) instead of quadratic extrapolation in the OpenFAST primary input file.
    3) Ensure the blade-pitch command output from ServoDyn is smooth (linear) by setting DLL_Ramp=True.
    4) Low-pass filter the blade-pitch command output from ServoDyn by setting BPCutoff to a small value (typically 1 Hz or less).
I hope that helps.

Best regards,
Jason Jonkman, Ph.D.
Senior Engineer | National Wind Technology Center (NWTC)

National Renewable Energy Laboratory (NREL)
15013 Denver West Parkway | Golden, CO 80401
+1 (303) 384 – 7026 | Fax: +1 (303) 384 – 6901
nwtc.nrel.gov

Marvin.Goetzke
Posts: 4
Joined: Fri Apr 26, 2019 7:37 am
Organization: TÜV NORD
Location: Germany

Re: (measured) Pitch Angle differs to demanded pitch angle

Postby Marvin.Goetzke » Wed Jul 17, 2019 5:02 am

Hi Jason,

Thanks for the information. The first approach works perfectly for me. Now the commanded and the actual pitch angle is identical.

Best Regards,
Marvin


Return to “Controls”

Who is online

Users browsing this forum: No registered users and 1 guest