Applies To:
  • CitectSCADA 5.41, 5.41 Service Pack A, 5.41 Service Pack B, 5.42, 5.42 Service Pack A, 5.50, 5.50 Service Pack A, 5.50 Service Pack B, 5.50 Service Pack C, 6.00
  • CitectHMI 5.41, 5.41 Service Pack A, 5.41 Service Pack B, 5.42, 5.42 Service Pack A, 5.50, 5.50 Service Pack A, 5.50 Service Pack B, 5.50 Service Pack C, 6.00
Summary:
Why do I get Data Not Yet Valid errors in the kernel when the OPC parameter FailOnBadData=1, but not when FailOnBadData=0?
 

Solution:
The OPC parameter FailOnBadData does the following:

When FailOnBadData=1 (default)

If there is a bad tag, all tags within the optimised block will be displayed as #COM.


When FailOnBadData=0 (non-default)

If there is a bad tag, all tags within the optimised block will be displayed correctly except for the bad tag which will be displayed as 0.

Additionally, if a Citect tag is configured to refer to an address that does not exist in the OPC Server and FailOnBadData is set to 0, the error will be suppressed.

Citect recommends ensuring that your tag addressing is correct and in particular that the address specified as the address of the tag in Citect actually exists in the OPC Server.
 
Keywords:
OPC, FailOnBadData, hardware error, 25, data not yet valid 
 

Attachments