In the Command Sequencer, sequences created in simulation mode cannot be read back. This is caused by errors in the "Recipe.unique" file. This file is used for both Batch Control and Command Sequencer. A hash in "Recipe.unique" ensures that the file is not corrupted. The hash values are calculated from the names of the sequences. Files that are detected as corrupted are usually recreated on the fly. This is not possible when reading back.

Possible error causes:

• 1: Client and server work with Service Engines with different bit versions. Thus the hash values differ.
• 2: The iteration for hash creation leads to a change in the order of the sequences during import.

This bug has been fixed. The checksum is now calculated over the data.

Behavior for versions with bug fix:

• For Batch Control and Command Sequencer in the production system, nothing changes on the server. The standby server recreates the "Recipe.unique" file after the first start of the project. Then this file remains until changes are made to the recipes that need to be written.
• Command SequencerImport: For reading back learned sequences, the server and the client need the bugfix. Because the client has created the "Recipe.unique" file for those sequences it holds. And the server must be able to read it.

To benefit from this fix:

• Update your zenon Software Platform to the latest build of zenon 11 or higher.