I am using Rate Transition blocks in a non-real-time Simulink model
for simulation purposes only (no Real-Time Code Generation). In the
Real-Time-Workshop documentation for this block it says that the maximum
latency added by a deterministic fast-to-slow transition is one sample
period of the slower task. This should be equivalent to a Zero-Order-Hold
operation which adds zero latency. Also it says the maximum latency added
by a deterministic slow-to-fast transition is two sample periods of the
slower task. This should be equivalent to a Unit Delay operation which
adds one sample period of the slower task. My question is: do these
"maximum" latency values only apply to real-time-generated code or do they
also apply in my non-real-time Simulink model? i.e. do rate transition
latency values in my Simulink model, which currently behave like strict
zero-order-hold and unit-delay blocks (and zero latency in NoOp operations)
have the potential to change, especially under unknown circumstances. If
so then I need to find a different way to model them.
The exact rate transfers I care about are these:
- Deterministic Fast-to-Slow Zero-Order-Hold transfers - should be
exactly zero sample time delay of slower task.
- Deterministic Slow-to-Fast Unit Delay transfers - should be exactly
1 sample time delay of slower task.
- NoOp Slow-to-Fast transfers - should be exactly zero sample time
delay of slower task.
These need to behave exactly like this in non-real-time Simulink models.
Best Answer