Validation from PLC
Previous
You can configure a runtime platform to automatically notify a PLC (if using Quick Comm) when changes have been made to the project, and to receive validation requests from a PLC, using the PROJECT CHANGE VALIDATOR tab of the PROJECTS portal page. This can be useful to ensure that no changes made in the operator view affect inspection and go undetected. For example, if the user enters a new value in a TextBox element, the runtime platform's ValidationNeeded bit will be set to 1, notifying the PLC that a setting has been changed for that project, and it should be validated.
From the PROJECT CHANGE VALIDATOR tab, you must enable the Receive validation request from PLC option and specify the Project name of the deployed project for which the PLC will request validations. The Project Change Validator can only receive validation requests from a PLC for the specified project, even if there is more than one project running on your runtime platform.
Modifications that notify a PLC that changes have been made and how validation is actually performed is the same as when you manually request validation. For information about what changes in a project will automatically notify a PLC, see the Monitor for validation subsection of the Procedure for using the Project Change Validator section earlier in this chapter.
When the PLC requests a validation, the Project Change Validator will automatically copy your project and validation set to the validation server. For more information, see the Validation server subsection of the Procedure for using the Project Change Validator section earlier in this chapter.
Typically, you should not use a PLC to request validation if your runtime platform might run projects that communicate with the PLC but do not use Quick Comm. Communication with the PLC that is not managed by Quick Comm can sometimes be interpreted by the Project Change Validator as a request for validation.
Validation fields
(bits)
The fields used for validation are:
|
DataFromPLC |
|||||||||
|
Group |
Offset (Byte) |
Bit 7 |
Bit 6 |
Bit 5 |
Bit 4 |
Bit 3 |
Bit 2 |
Bit 1 |
Bit 0 |
|
Control |
0 |
(Reserved) |
PLCSoftEvent2 |
PLCSoftEvent1 |
(Reserved) |
(Reserved) |
PLCACK |
PLCReset |
PLCReady |
|
Validation |
1 |
(Reserved) |
(Reserved) |
(Reserved) |
(Reserved) |
(Reserved) |
(Reserved) |
(Reserved) |
PLCValidation |
|
DataToPLC |
|||||||||
|
Group |
Offset (Byte) |
Bit 7 |
Bit 6 |
Bit 5 |
Bit 4 |
Bit 3 |
Bit 2 |
Bit 1 |
Bit 0 |
|
Status |
0 |
(Reserved) |
SorfEvent2ACK |
SorfEvent1ACK |
(Reserved) |
OverallFail |
OverallPass |
Busy |
ProjectReady |
|
Validation |
1 |
(Reserved) |
(Reserved) |
(Reserved) |
(Reserved) |
ValidationNotAsExpected |
ValidationAsExpected |
ValidationNeeded |
ValidationRequested |
|
2 |
Validation Error |
||||||||
When a change is detected in your project (for example, if the user changes an operator view element that is being monitored for validation), the ValidationNeeded bit is set to 1. When the validation is requested, the ValidationRequested bit is set to 1, while the ValidationAsExpected, ValidationNotAsExpected and ValidationError bits are set to 0. When the validation is done, the ValidationRequested and ValidationNeeded bits are set to 0, while the ValidationAsExpected, ValidationNotAsExpected, and ValidationError bits are updated to reflect the validation result:
-
The ValidationAsExpected bit is set to 1 if the validation status was "As Expected".
-
The ValidationNotAsExpected bit is set to 1 if the validation status was "Not As Expected".
-
The ValidationError bit is set to a value other than 0 if the validation had an error.
If a change is detected in your project while validation is running, the ValidationNeeded bit will remain at 1 after validation has been completed.
The values in the ValidationError field can represent error codes. For more information about error codes and their corresponding messages, see the Validation error messages section later in this chapter. For information about viewing a report of a completed validation, see the Validation report section earlier in this chapter.