Insights on DC Offset Issue in Hypersim 2026.2.3

Hi Team,

I am currently observing a DC offset in a plant model running on Hypersim 2026.2.3.

I recall from one of the previous conferences that, during the RT24, a similar DC offset issue was encountered and successfully resolved. I would like to understand the approach that was taken and any modifications or parameter adjustments that helped eliminate or reduce the offset.

As part of the investigation, I have already:

Checked the I/O board configuration.
Reviewed the Sensor Summary.
Discussed the issue with the India Support Team.

Despite these efforts, we have not yet been able to identify the root cause of the problem.

Could you please share any insights from your previous experience, including areas to investigate or specific settings that were modified to resolve the DC offset? Any guidance would be greatly appreciated.

Thank you in advance for your support.!

Before:

After

Thank you for the detailed description and for sharing the screenshots, they clearly illustrate the issue.

DC offset in HIL plant models is typically caused by one of two things, and the first step is determining which applies to your case:

  1. Is the offset in the model or in the hardware output?

While the simulation is running, check ScopeView:

If the signal looks correct in ScopeView but the physical analog output shows the offset → hardware signal chain calibration

If the offset is also visible in ScopeView → model initialization or configuration.

  1. General areas to investigate

  1. On-the-fly tuning (HYPERSIM 2026.2+)

Your version supports real-time gain/offset adjustment in the I/O Interface configuration — you can experimentally zero out the offset without stopping or recompiling. This is a good way to confirm whether calibration resolves the issue.

Next steps

Since you’ve already reviewed the I/O board configuration and Sensor Summary without identifying the root cause, and given that this involves your specific plant model, hardware target, and I/O configuration, we recommend opening a support ticket for further investigation.

The support team can:

Review your specific .ecf model and .io configuration

Analyze ScopeView captures vs. physical output measurements

Verify calibration values for your specific I/O modules and target hardware

Provide step-by-step guidance tailored to your setup

You can open a ticket here: Support Center | Access Technical Help and System Resources | OPAL-RT

Please include:

Your model file (.ecf)

I/O configuration file (.io)

ScopeView screenshot showing whether the offset is present in the simulation output

Physical measurement screenshot (as you’ve already shared)

Target hardware model and firmware version

This will help the team provide a targeted resolution quickly.