Simulink Real Time Workshop - how to measure code execution time?

I have a Simulink model from which I generate code using Real Time Workshop for a Quanser Q8 data acquisition board. How do I measure the actual execution time of my model?

[Paulo Silva]

That's a good question, I'm going to work with Quanser hardware and maybe something like that will be needed, +1 vote, good luck.

Answer 1

[Hervé Lacheray]

If you are using Quanser's QUARC software to access the Q8, there is also a Computation Time block that is available. This block measures and outputs the computation time of the attached Function Call Subsystem (or model), using a high-resolution independent time source. In Windows, this time has nanosecond resolution.

[H S]

I tried this and got good results.

Answer 2

[Kaustubha Govind]

I don't know if this answers your question completely, but if you're using ert.tlc or one of its descendants, rt_OneStep is the function that is to be called at every time step - so adding instrumentation around a call to rt_OneStep should give you a measure of execution time per step.

Answer 3

[MarkB]

There is an additional feature called "RTW profiling hooks" that might help with this. It is somewhat advanced and requires you to write some TLC code, but it essentially lets you add user-defined code at the beginning and end of generated functions, which is an ideal location for adding "tic"/"toc" commands.