Skip to content

Conversation

@juguma
Copy link
Contributor

@juguma juguma commented Mar 18, 2025

I modified the tests such that they also work for the SimulationX 4.6.2 FMUs (all those who are there, e.g. no FMI3ME). However, there are two remaining issues:

  • SpringTimeFrictionPendulum as SX-ME2FMU simulates differently. Cause of the problem so far unclear, hence I added a special treatment in the test (sim_ME.jl)
  • simulateCS of SpringPendulumExtForce has a wrong calling sequence, hence SX-CS 2 and 3 FMU end in error status(sim_CS.jl). That's a bug in FMI.jl, hence not excluded from the test (cf. #269) - causes 4 Errors in total (due to combination of fmu/instance + 2/3).

Julia Gundermann added 4 commits March 5, 2025 15:25
…d function to get permutation order of FMU states, used this in any check for u. 2. Modified tests in sim_ME.jl for values at end of simulation (now test that it has settled in stuck mode and force is c*(1-s))
…ass.s)"), hence modify getPermutationOfStates
…rors for SX4.6.2 3.0 ME).

sim_ME.jl: (1) compare final results of SpringTimeFrictionPendulum with Dymola 2024X Refresh1, (2) exclude SX-ME-4.6.2-FMU since it clearly is not treated correctly.
… sim_CS.jl and sim_zero_state.jl (test only if FMU exists)

Now exactly one test fails 4 times due to always the same issue (CS FMU 2+3 as fmu+instance with input, caused by wrong calling sequence (FMI.jl#269).
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

Successfully merging this pull request may close these issues.

1 participant