-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
32 bit DLL ROSCO with Bladed #193
Comments
Abhi-postdoc
changed the title
Interface of BLADED 32. bit DLL of 5 MW NREL-ROSCO
Interfaing of 32. bit DLL of 5 MW NREL_ROSCO in BLADED 4.10
Dec 7, 2022
Abhi-postdoc
changed the title
Interfaing of 32. bit DLL of 5 MW NREL_ROSCO in BLADED 4.10
Interface of 32. bit DLL of 5 MW NREL_ROSCO in BLADED 4.10
Dec 7, 2022
Abhi-postdoc
changed the title
Interface of 32. bit DLL of 5 MW NREL_ROSCO in BLADED 4.10
Interfacing of 32. bit DLL of 5 MW NREL_ROSCO in BLADED 4.10
Dec 7, 2022
There are 32-bit dlls you should be able to use here: https://github.com/NREL/ROSCO/releases/tag/v2.6.0 |
Not working Sir. Same "ERROR: Unknown SEH (Structured Exception Handling) error encountered". |
Sorry, I'm out of ideas. Have you asked the Bladed team about this? |
dzalkind
changed the title
Interfacing of 32. bit DLL of 5 MW NREL_ROSCO in BLADED 4.10
32 bit DLL ROSCO with Bladed
Dec 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Everyone,
I have generated 32-bit.dll for BLADED 4.10 and followed all the steps as mentioned in "https://rosco.readthedocs.io/en/latest/source/ROSCO_instructions_for_Bladed.html". However, I got this error msg in the BLADED interface. Please help me to sort this out. If possible can you kindly provide any working model of .DLL, and DISCON.IN, .prj file of 5 MW turbine for BLADED to verify where I am doing mistakes. Thanks in advance,
*** Note: Using legacy controller, 'DISCON' in controller C:\Users\PC00\ROSCO\Test_Cases\NREL-5MW\libdiscon.dll
*** ERROR: Unknown SEH (Structured Exception Handling) error encountered. This could be due to using the wrong calling convention being used when calling a dll, or a C++ exception being thrown from within an extern "C" function, or a missing dll dependency encountered in external controller.
Originally posted by @Abhi-postdoc in #12 (comment)
The text was updated successfully, but these errors were encountered: