Command Sequencer - old Sequences corrupt Recipe.unique file in Simulation mode
Summary
An error occurs in the Command Sequencer when reading back sequences created in simulation mode. This has been fixed.
Description
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.
Item ID: 267408
Version: 12.00 Build: 162090
Version: 11.00 Build: 161931
Related Articles
FAQ: What are the different zenon drivers modes?
All Service Engine process-driven drivers can run in four different modes, mainly allowing you to switch between active hardware connection and values simulation. While "Hardware" allows establishing a connection to the target device(s) and its the ...
FAQ: It seems that sometimes not all variables are correctly written to the PLC by the RGM module, although the system driver variable states that the recipe was written successfully and the option "write synchronously" is active. How can this be?
When reading a RGM recipe immediately after writing a RGM recipe, with a driver that has the option "keep update list in memory" active, and recipe variables that have been read previously, it can happen that a read cycle is currently in progress, ...
When using a Driver in mode "Simulation - static" and in the zenon runtime the Driver command "Switch to Hardware mode" is executed, variables of the corresponding Driver get INVALID (correct) but when then executing the Driver command "Switch to Simulation mode" the variable stays INVALID but gets also SPONT.
Summary When performing the Driver command "Switch to Hardware mode" in the zenon runtime variables of a Driver which is running in mode "Simulation - static" get INVALID (correct). When then performing the Driver command "Switch to Simulation mode" ...
missing license for command sequencer is called "Batch Control"
Summary if a project has no license for command sequencer, or has 'batch preferred', and at Runtime an operation "new switching sequence" is tried, the error message box tells "no license for module batch control". Description if a project has no ...
When using the Opc2Cli32 Driver in the zenon runtime and using first the Driver command "switch to Simulation mode" (with Opc2Cli32 Driver set to "Hardware" mode in the Editor) and then using the Driver command "switch to Hardware mode" the variables will become invalid and have the Status "switched off" instead of SPONT.
Summary When using the Opc2Cli32 Driver in the zenon runtime and using first the Driver command "switch to Simulation mode" (with Opc2Cli32 Driver set to "Hardware" mode in the Editor) and then using the Driver command "switch to Hardware mode" the ...