Scope and current bias online RT-Box

Hi,

Can you help with suggestions to fix the current bias when I move the simulation (offline) to the RT-Box implementation (online)?
Thanks in advance!

There isn’t enough information here to assist you. For a well implemented real-time model, the root cause is likely something in your model that differs between offline and real-time.

For example:

  • Your model already includes a slow error build-up that is only visible for extended simulation runs.
  • Introducing noise or DC offset into a control algorithm leads to different results.
  • A sensor or signal is incorrectly mapped between the real control hardware and RT Box while it works fine in a model.
  • Some events are perfectly synchronous in an offline simulation but differ when executed in real-time due to different clocks (i.e. RT Box and controller do not share a common clock).

Thanks, Bryan for the reply!

I read you’ve an idea of what I am working on from our previous interactions. While I consider the points you highlighted here, see a more merged plot for more info if that clarifies stuffs a little more.

Extended simulation time: