Variables of the Math32 driver are not considered in the network rating

• Related Articles

• FAQ: Initialization of Internal variables (Network) in Dominant redundancy mode.

  When (re-)starting the dominant Server 1, regardless of their 'Remanence' configuration, internal variables with calculation in 'Network' are initialized first in the dominant Server 1 and only after synchronized with the running Server 2. Modules ...

• Rated redundancy does not correctly consider internal variables set to calculation "Network" in the rating matrix

  Summary When internal driver variables with calculation "Network" are used in the rated redundancy matrix with the option to validate the value / status, the rating does not consider these values invalid after a redundancy switch. DescriptionWhen ...

• Checklist: Driver(s) cannot establish a reliable communication

  Time estimate: 60 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• 3S_V3 Driver : The length of WSTRING variables is not considered during variable Import.

  Summary The length of a WSTRING variable is available in the Symbol file. During variable Online or Offline Import, the length is not considered and the WSTRING variable acquires the Default length "5" in zenon. The length of STRING variables is set ...

• local Recipegroup Manager system driver variables are incorrectly updated on all systems in the network for the action write graphic recipe variables

  Summary When executing a Recipegroup Manager function with the option to write the graphic recipe variables, the local system driver variables that indicate for which recipegroup, recipe, recipe version etc. the action has been called, are updated on ...