Hi
everyone , I am simulating the cases according to IEC61400-3 ( Design situation 2.1). I want to simulate the situation about N4 overspeed and Na overspeed, usually called sofrware overspeed and hardware overspeed. I know we can simulated in Bladed by choose security chain cycle, but in Fast, how we can simulated these work conditions ? By overwrite .dll or parameters?
Another problem is also about control is about Normal stop in IEC61400-3 ( Design situation 4.1). for example, if I want to stop the generator in normal, how can I transmit my order to .dll, is there any Interface for us to call for?
ANYONE WHO HAS ANY IDEA CAN CONTACT ME!
THANK YOU FOR YOUR ATTENTION.
I’m not familiar with the terms “N4 overspeed” or “Na overspeed”, so, I’m not sure how to answer your question. (Perhaps someone else on this forum can respond.) While there are few built-in control options in the ServoDyn module of FAST/OpenFAST, most control functionality is expected to be defined by the user using one of the available interfaces (subroutine, Bladed-style DLL, Simulink interface).
I want to know how to simulate fault work condition of our wind turbine.You know, there is no manual about ElastoDyn and ServoDyn in FASTv8/OpenFAST. I have read the manual of FASTv7, it certainly concludes some tips about simulating special events(such as Shutdown,Normal Pitch-to Feather) but not comprehensive. Is there any more tips or manual to simulate these events by using FAST/OpenFAST ?
However, if I can’t modified the parameters in ServoDyn module finally, I’ll modified the source files of FAST and compile it again. Now I am not familiar to the source codes, which module should focus on and modified it to communicate with my .dll file? Do you have any good idea about it?
There is no documentation other than what has already been provided. That said, the topic of simulating special events and faults has been discussed several times on this forum, so you can probably search for the answer here.
If your DLL follows standard Bladed DISCON DLL format, than there is no need to change the FAST/ServoDyn source code at all; instead, all you have to do is tell ServoDyn to accept controller commands from the DLL (by setting PCMode=5 to enable pitch control, etc.).
Dear Jonkman
Thank you for your reply!
These are certainly many simple fault work conditions what I can simulate by modified ServoDyn parameters. As for the fault work condition I have mentioned above, such as N4 overspeed，Na overspeed and normal stop(IEC 61400-3 Design situation 4.1), it can’t be simulated in this way.
In Bladed, I can simulate by using security chain cycle. Because it concludes signal code (or signal number) and can be transmitted from Bladed to Bladed DLL(Bladed DLL need the signal to decide the fault events). but for FAST, is there any such signal code defined in ServoDyn, that Bladed DLL can understand the fault work condition which I want to simulate? if not, how can I change the ServoDyn source code to tell the Bladed DLL, that I am simulating the fault work condition?
Yours sincerely
Zheng
2018/12/18
Again, I’m not familiar with the terms “N4 overspeed” or “Na overspeed” or the like and you haven’t provided details on what you need changed, so, I’m not sure I can comment on how you can change the ServoDyn source code to tell the Bladed DLL the “signal code”. Regardless, the ServoDyn interface to the Bladed-style DLL controller is written in the source file named, BladedInterface.f90. I suggest you start by reviewing that source code. If you know how you want ServoDyn to communicate with the DLL differently than it currently does not, hopefully it will be clear to you what in BladedInterface.f90 should be changed.
Thank you very much for your reply!
It’s very helpful for me！And I will read the source code as you have mentioned above. I believe I can get my way to solve the problem.