What influence do the TA identification settings (TA number, TA version) as well as the firmware version of the i950 have on the detection of the EtherCAT slave during startup of the EtherCAT Master?
Within the boot-up of the EtherCAT master (e.g. C5x0 or i950) it is checked whether the identification of the slaves matches the EtherCAT configuration in the controller.
If differences are detected, this can lead to warnings or the bus state 'Operational' cannot be reached.
This differentiation of the reaction during monitoring is possible because the identification is multi-part. It consists of the manufacturer identification, the product code and the revision number.
- If a changed revision number is detected, a warning is entered in the logbook: Configuration mismatch. Check Revision failed. The bus state 'operational' can be reached.
- Differences in the manufacturer identification and/or the product code prevent the EtherCAT from being set 'operational'.
For the i950 the product code (0x1018:2) is composed of the i950 type (Basic or Extended Safety) and the TA number.
The revision number (0x1018:3) is influenced by the version of the basic device firmware and the TA version.
The TA number, the TA version and the firmware version can be influenced by the user.
For different use cases 'Update / Change of the Application Software of the i950 EtherCAT Slave' it can be determined in advance, whether the EtherCAT may start or not after a changed PLD project has been started; here it must be differentiated during project creation.
- Only minor adjustments of the PLC project are made (clean-ups, renaming, ...) or the changes are made in the course of an initial creation of the project.
-> Neither TA number nor TA version are changed.
-> No differences are detected during EtherCAT slave recognition.
- Despite the changes, the axis behaves in the overall context of the EtherCAT network and the motion and logic functionality is compatible with the previous version.
The EtherCAT master should recognize this device as changed, but should allow the automatic transition to the 'operational' state at startup.
-> In this case the TA version must be changed in the tab TA Identification in PLC Designer.
-> This changes the revision number
-> The reaction is warning 'Configuration mismatch
-> The bus status 'operational' is reached.
- Dhe EtherCAT mapping was changed. OR
User parameters were deleted, newly created or changed. OR
Changes in the motion and/or logic functionality of the axis change the behaviour of this axis in the overall context of the EtherCAT network incompatible with the previous version.
-> In this case the TA number must be changed in the TA Identification tab in PLC Designer.
-> This changes the product code
-> The bus status 'operational' must not be reached
Use case device replacement or firmware update - The i950 replacement device has a newer firmware version than configured in the EtherCAT master.
-> This changes the revision number
-> The reaction is warning 'Configuration mismatch
-> The bus status 'operational' is reached
