Troubleshooting Custom Sequences

If you encounter any problems while testing custom acquisition sequences, you can check the following information. It describes some error causes and might help you solve the problem.

Violating the schema definition in a sequence file

The sequence files are validated against a defined schema when parsing them at startup of MERLIC.

Violating the schema definition, for example, by missing a required parameter, causes the sequence not to be loaded and creates an error in the log file of MERLIC.

Defining an unusable sequence

This may happen by defining dead-locking barrier actions or using an image name in multiple "AcquireImage" actions.

These errors are displayed in the MERLIC RTE Setup by marking the sequence with an error symbol. When hovering this symbol, a tool tip provides additional information on the specific error.