Skip to content
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

Structured declaration of coupled clutches #4

Open
KarlWernersson opened this issue Nov 4, 2024 · 2 comments
Open

Structured declaration of coupled clutches #4

KarlWernersson opened this issue Nov 4, 2024 · 2 comments

Comments

@KarlWernersson
Copy link

KarlWernersson commented Nov 4, 2024

Hi The coupled clutches FMI 3 FMU has the following variables

<Float64 name = "J1.phi" valueReference = "1" description = "J1.phi" initial = "exact" start = "0.00000000000000000e+00"/> <Float64 name = "J1.phi.der" valueReference = "2" description = "J1.phi.der" initial = "exact" start = "1.00000000000000000e+01"/>

I would say that having both variables J1.phi & J1.phi.der isn't legal structured declaration, according to fmi standard as we state its the same as modelica and this is illegal modelica.

Anyhow this currently causes translation error when importing into Dymola with structured import.
Using flat import works fine.
I have updated future Dymola version to diagnose the error and give a recommendation to do a flat import.

Best Regards
Karl Wernersson

@Maplesoft-fmigroup
Copy link
Owner

@KarlWernersson Thanks for pointing this out. I have added a bug report for our next release.

@Maplesoft-fmigroup
Copy link
Owner

@KarlWernersson Hi Karl, could you please try an updated FMU CoupledClutches3.fmu to see if it now passes the structured variable name check on your end?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants