This blog post describes a procedure to debug a crank-angle resolved engine model (CAREM) in Dymola. It helps narrow down to the cause of the problem in case the engine runs but does not produce the expected results. A CAREM is a multi-domain (mechanics, fluids, thermal, electrical) model so...
Tag Archive for: debugging
Dymola provides a means to measure where the CPU time is being spent in the model code execution. This feature is known as profiling. Profiling is described in Section 5.7.5 of the Dymola User Manual Volume 1. This blog article supplies further information. Profiling is implemented by inserting timers...
Models of physical systems with state logic and time based discontinuities can often produce events in Dymola. These events can have a significant impact on your simulation performance, so it is important that we understand where these events are coming from in the model. In this blog post I’m...
Looking for something?
- Making our lives easier: Default horizontal/x-axis time units 14th January 2019
- The “Capture Parameters” command: For tidying models 14th January 2019
- Future Powertrain Conference 2019 – 27 & 28 February, National Motorcycle Museum 8th January 2019
- Using inline integration and fixed step solvers to speed up offline simulations 7th January 2019
- TaaS Technology Feature Claytex – Modern vehicles, modern challenges 18th December 2018
- Automotive Testing Technology International Feature Claytex – No more prototypes 17th December 2018
- Build FMUs from Dymola model and run the FMUs in Dymola and Simulink 14th December 2018
- Race Tech Magazine Feature Claytex – Why our Heads are in the Cloud! 12th December 2018