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

FMIKit 3.1: FMU creation does not generate input and output signals if these are defined as BUSes. #469

Open
alexasap opened this issue Feb 8, 2024 · 2 comments

Comments

@alexasap
Copy link

alexasap commented Feb 8, 2024

When I change FMI version from 2.0 to 3.0, no more BUS signals are created. See pictures below.

This problem can be reproduced by executing the main.m script from MiniFMU.zip.

MiniFMU.zip

FMI version 2.0:
FMU2 0

FMI version 3.0:
FMU3 0

What am I doing wrong?

main.m script:
main m

@alexasap alexasap changed the title FMU 3.0 creation does not generate input and output signals if these are defined as BUSes. FMU 3.1 creation does not generate input and output signals if these are defined as BUSes. Feb 9, 2024
@alexasap alexasap changed the title FMU 3.1 creation does not generate input and output signals if these are defined as BUSes. FMUKit 3.1: FMU creation does not generate input and output signals if these are defined as BUSes. Feb 9, 2024
@alexasap alexasap changed the title FMUKit 3.1: FMU creation does not generate input and output signals if these are defined as BUSes. FMIKit 3.1: FMU creation does not generate input and output signals if these are defined as BUSes. Feb 9, 2024
@alexasap
Copy link
Author

Hello Support Team, have you been able to look at the problem and reproduce it?

@t-sommer
Copy link
Contributor

Buses are currently only supported for FMI 2.0 with grtfmi.tlc.

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