Frame checksum validation in openPDC is applied at the point of ingress into openPDC. Therefore, it is independent of the destination for the data, whether it’s the database, the local historian, another IEEE C37.118 stream, or some collection of multiple destinations. That is to say, if checksum validation is disabled in the input device’s configuration, it will pass data into openPDC’s routing engine to be consumed by the AdoOutputAdapter and written to the database regardless of the CRC.
Checksum validation can be controlled for each frame type independently by adding the
checkSumValidationFrameTypes parameter to the connection string for the input device. The value of this setting is a comma separated list of frame types for which validation should be enabled. Valid frame types come from the following list.
For example, to disable checksum validation specifically on data frames, add the following setting to your input device’s connection string:
checkSumValidationFrameTypes=ConfigurationFrame, HeaderFrame, CommandFrame. To ignore all checksums, add the following setting to your input device’s connection string:
By default, validation is enabled for all frame types, which means data would not be passed along to the AdoOutputAdapter and would not be written to the database in the case of an invalid CRC.