Opened 12 years ago
Last modified 7 years ago
#1940 reopened defect
Multibody USR and SSR joints have wrong simulation values
| Reported by: | Lennart Ochel | Owned by: | Willi Braun |
|---|---|---|---|
| Priority: | high | Milestone: | Future |
| Component: | Backend | Version: | trunk |
| Keywords: | Cc: | Bruno Scaglioni |
Description
ModelicaTest.MultiBody.FourbarVariants.JointUSR and
ModelicaTest.MultiBody.FourbarVariants.JointSSR models simulate with wrong results.
Change History (12)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
They results are different to dymola, but I won't say they are wrong, since the models are still initialized different to Dymola. You get also the same simulation results as dymola, if you use the dymola result file for initialization.
Maybe there is more than one possible solution.
comment:3 by , 12 years ago
| Resolution: | invalid |
|---|---|
| Status: | closed → reopened |
I have tested FourbarVariants.JointUSR once more and it seems to be initialized correctly (see #1929) but the simulation results are still not the same. If I use dymola results for the initialization, the simulation stops at time 0.004 with following message:
messages = "Simulation execution failed for model: ModelicaTest.MultiBody.FourbarVariants.JointUSR stdout | info | model terminate | non-linear system solver failed. | Simulation terminated at time 0.004"
So, how have you tested the simulation? And how have you got correct results?
comment:5 by , 10 years ago
| Milestone: | 1.9.1 → 1.9.2 |
|---|
This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).
comment:6 by , 10 years ago
| Milestone: | 1.9.2 → 1.9.3 |
|---|
Milestone changed to 1.9.3 since 1.9.2 was released.
comment:11 by , 8 years ago
| Milestone: | 1.11.0 → 1.12.0 |
|---|
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:12 by , 7 years ago
| Milestone: | 1.12.0 → Future |
|---|
The milestone of this ticket has been reassigned to "Future".
If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.
If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".
In both cases, a short informative comment would be welcome.
comes from #1929