Corrected from:
L-force 3200C controller V3.14
L-force p500 controller V3.14
L-force c300 controller V3.14
L-force p300 controller V3.14
Response of the new version:
If the GetRecipeNames method of the RecipeManCommands function block is called with the name of a recipe definition that does not exist, the method returns the value 16#4004 (ERR_RECIPE_DEFINITION_NOT_FOUND). No exception occurs.
What happens?
PLC processing stops with the exception "AccessViolation".
When does this behaviour occur?
If the GetRecipeNames method of the RecipeManCommands function block is called with the name of a recipe definition that does not exist, the PLC stops with the exception "AccessViolation".
Which products are affected?
L-force 3200C controller from V3.0
L-force p500 controller from V3.3
L-force c300 controller from V3.8
L-force p300 controller from V3.8
Short-term measures/recommendations:
Call the GetRecipeNames method with the name of an existing recipe definition.
Evaluation:
The RecipeManCommands function block will be available if the Recipe Manager has been included in the PLC Designer project. If a method of this function block is called with a non-existing name of a recipe definition, PLC processing stops with an exception. Usually, recipe data is handled by the visualisation. If VisiWinNET is used as visualisation, recipe management will be performed by VisiWinNET. In this case, the RecipeManCommands FB will not be used and the function restriction will not occur.
