
Trouble taking snapshots of large systems
This application note describes how to adjust the snapshot timeout values. This may help when having trouble taking snapshots of large systems.
Problem
With large systems (greater than 15000 SIOTags) or heavily loaded system (near 100% CPU and RAM usage), MiMiC may take longer than expected to save a snapshot of the running system. Usually, while MiMiC is requesting a snapshot of the control system, it will timeout. In addition to that, a dialog may indicate that an internal messaging error has occurred. Below are the steps to increase the snapshot timeout values.
Procedure
-
Open the Windows Registry editor: Start -> Run and type regedit
-
Locate the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Mynah Technologies\MiMiC V3\OTM\DefaultTimeout
-
Double the current value. Please note that the default value is 10000 milliseconds.
-
Locate the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Mynah Technologies\MiMiC V3\OTM\CaptureTimeout
-
Double the current value. Please note that the default value is 60000 milliseconds.
-
Open the Windows Service control panel: Start -> Run and type services.msc
-
Restart the MiMiC Operator Training Engine service for the changes to take affect
Additional Detail
The DefaultTimeout key controls how long the MiMiC waits for feedback from the control system when a request, either "Take a snapshot" or "Restore a snapshot", is made. If the control system does not respond before the timeout period, then the request is dropped and an error is displayed in MiMiC.
The CaptureTimeout key controls how long the MiMiC waits for the file copy operation to complete. If the files are large, it could take longer than the timeout period to copy the files. If the timeout period is reached and the files are not copied then the operation is canceled and an error is displayed in MiMiC.


Subscribe to RSS feed