Support : Knowledge base

Knowledge Base

Welcome to OPAL-RT’s Knowledge Base

OPAL-RT offers a repository of support information for optimal use of its technology.

Loading…

Please note that OPAL-RT knowledge base is not fully optimized for mobile platforms.

For optimal experience, use a desktop computer.

Reference Number: AA-01473// Views: AA-01473// Created: 2018-04-19 18:32:34// Last Updated: 2021-10-20 15:07:47
General Article
HYPERSIM : Troubleshooting using SIMOUT (exhaustive logs - simulation logging)

HYPERSIM : Troubleshooting using SIMOUT (exhaustive logs - enable simulation logging)

In HYPERSIM, you might run into errors that will need advanced troubleshooting especially when it's related to IOs, communication protocols and target communications. The log provided in the HYPERSIM Console might not be enough.

To help you troubleshoot the problem, HYPERSIM (6.1 and later) has a feature called the simout. This tool is available as a tab right next to the console tab.

Here is how you will access it,


As you can see in the above figure in the red boxes, there is a .simout tab. In this case, there are three models open and each one of them has a simout. To access the simout, simply click on the tab.

By default, the simout has basic information. 

Enable exhaustive logs (Enable simulation logging)

To enable exhaustive logs, use the Enable simulation Logging option before starting the simulation (Note that Real-Time performances are reduced when using the exhaustive logs):


For example, we will look at how the simout can be used to identify the problem with the C37.118 example model. 


In this case above, in the code compilation console, there was not much information why the simulation didn't start, but in the simout, we can clearly see the error is coming from an issue related to the license.

A great way to help the OPAL-RT Techincal Support is by providing a copy of the simout when your simulation fails. You can do that by right-clicking on the simout page and save as to a .txt file