Opened 11 years ago
Last modified 7 years ago
#2648 accepted defect
wrong simulation results for pulsed voltage source
| Reported by: | Volker Waurich | Owned by: | Willi Braun |
|---|---|---|---|
| Priority: | critical | Milestone: | Future |
| Component: | Run-time | Version: | trunk |
| Keywords: | events | Cc: | Christian Schubert, Willi Braun, Lennart Ochel |
Description
Hi,
the model Modelica.Electrical.Spice3.Sources.V_pulse which occurs for example in the Spice3.Inverter model is simulated wrongly.
I put a tiny model in testsuite\simulation\modelica\functions_eval\pulseSource.mos
Actually, there should be 3 voltage pulses during 1e-11 sec simulationtime but the omc outputs a constant voltage of 0.
compareSimulationResults says "Files Equal" which is not true(maybe due to the very short pulses which occure in the tolerance of the event comparison)
In fact, the events for the pulses are triggered correctly somehow because values for the time step back(!) at the points where the pulses should be. So there happens at least something but the time should not move backwards and the voltage should rise to 5V.
Attachments (1)
Change History (11)
by , 11 years ago
| Attachment: | PulseSource.mo added |
|---|
comment:1 by , 11 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → accepted |
comment:2 by , 11 years ago
Fixed (partially) in r19965.
- avoid step backwards, after a sample event.
- prevent infinite small step sizes.
- adjust tolerance of the relation hysteresis also by step-size.
Partially because there is still an issue with the hysteresis for zero-crossings. Which should changed to be more sophisticated, in that sense that the hysteresis should only applied if event occurred in the moment before.
comment:3 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:4 by , 10 years ago
| Milestone: | 1.9.2 → 1.9.3 |
|---|
Milestone changed to 1.9.3 since 1.9.2 was released.
comment:9 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:10 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.
For some reasons dassl misses the events, if you increase the tolerance(1e-10) the we get the events. But we do also strange steps backwards after some sample events, that's the reason why the results looks ugly.