General

Faults are first displayed in Viper.NET via the “GEFASOFT” button at the bottom left.

After clicking on the button, the status of the components can be checked for faults (red) or warnings (yellow). This can be, for example, a communication fault with the controller or a faulty loaded type.

Most errors can be fixed via a Reset.

If the fault persists or occurs more frequently, further analysis is required.

In case of communication failures with a connected controller, the tab Stations in the sidebar can be used to check the state of the signals. The tab HW Explorer offers even deeper analysis possibilities.

Error messages are also logged in various logs and are both saved to files and displayed in the user interface.

In the Info Dialog the loaded .NET assemblies and the plugin selection can be checked.

Collect information for support

If a problem cannot be solved, please contact the GEFASOFT support. Ideally, you should send us a backup of your project via SaveVersion. If required, we will gladly provide online storage space for this purpose.

HALCON: licence errors despite a valid licence

If HALCON tools report errors such as #2381 (License is for wrong edition), #2033 (License file does not support a version this new) or license missing after a HALCON update or with several HALCON installations, the HALCON .NET interface delivered with Viper often does not match the native HALCON library that is actually loaded (halcon.dll).

Viper checks this on the first call of a HALCON tool and, if they differ, writes one ERROR to the log, starting with HALCON version mismatch. The entry names both versions, both paths and HALCONROOT.

Remedy: set HALCONROOT and PATH of the Viper process to the matching HALCON installation and start Viper from a new session (e.g. log on again after installing HALCON).