Y_YA_EC_Diagnostics
This block provides information
about the configured and actual topology of the devices on the EtherCAT network. Comparisons and status determinations will aid in EtherCAT network diagnostics.
Data is read on rising edge of the Execute input, but it may take multiple scans to complete the acquisition of the data.
Parameters
| * | Parameter | Data Type | Description | Default |
|---|---|---|---|---|
| VAR_IN_OUT | ||||
| V | ECData | Yt_YA_ECStatusStruct | Stores status and config data related to EC network. | |
| VAR_INPUT | ||||
| B | Execute | BOOL |
Upon the rising edge of the Execute input, all inputs are read, and the function will begin reading EtherCAT network information. If an input needs to be modified, the value will have to be changed, and then the Execute has to be triggered again.
|
False |
| VAR_OUTPUT | ||||
| B | Done | BOOL | The Done output is set to Indicates that the function completed operation normally. This output resets when Execute becomes FALSE. |
FALSE |
| B | Busy | BOOL | The Busy output is set to TRUE upon the rising edge of the Execute input, and is set to FALSE when Done or Error become TRUE. Indicates that the function is still performing a task. | FALSE |
| B | Error | BOOL | The Error output is set to TRUE if an error has occurred during the execution of the function block. This output is cleared when Execute becomes FALSE. | FALSE |
| B | ErrorID | UINT |
The ErrorID output provides the identifier of the error when there is an active error in the function block execution. Output is cleared when Execute becomes false. |
UINT#0 |
Notes
- Y_YA_EC_Diagnostics relies on accuracy of data reported by the EtherCAT network. When EC_Topology_OK == FALSE, some data may not be possibly to collect.
Error Description
See the Function Block ErrorID List.
Example
Only ECData and Execute inputs are required. A rising edge or a TRUE input into Execute starts the process of populating data about the EtherCAT network connected.
This FB takes multiple scans to complete. So, the faster the task, the faster the completion of the read to ECData.
The structure of ECData is based around Master/High Level info being immediately accessible, while per device details are under ConfiguredDevices. Items inConfiguredDevices are ordered by the order they appear in the Plant within iCube Engineer.
The DeviceComparisonList sub-struct allows for the comparison of the individual devices seen by the Controller on the EtherCAT network. Configured Devices are populated based on their order in the Plant, while Connected Devices are ordered by their physical connected order (based on autoincrement EtherCAT addressing). If Hot Connect is enabled, there is less value in this comparison list, at least for devices that support Hot Connect, as connected order is not strictly matched against the order in the Plant.
