My ethercad master do not go to OP-state because the device _9251_ethercad_Drive and device _9251_ethercad_brake do not can go to Safe-OP.
(this due to the option: Slave have to reach the master state. ) if this option is off then the master go to OP. but my slave device _9251_ethercad_Drive and device _9251_ethercad_brake still stand in PRE-OP.
At the diagnostics of the master i see the follow message:
As PDO: the follow content is assignt:
at the attachement the XML file from the supplier of the device.
Solved! Go to Solution.
As our engineering tool is using the data provided by the .XML file and we do not have any hardware to test, its quite hard to say what should be wrong here.
To be sure we are talking about "burster 9251 Fieldbus Controller" module right (external supplier page).
Did you ask the supplier if the data used is correct:
Could you give me the contact of the supplier so we can have a direct talk about that? Feel free to send me a private message.
Please also send us the IO project used and describe your application.
We will check this.
Could you please:
Thanks to your information we could figure out whats the matter:
Like the error says and also the device supplier says targets 0x1C12 and probably also 0x1C13 are written but read only.
There is a setting in the "Expert Process Data" in our ctrlX IO Engineering that tells the master to do so:
In fact these settings are predefined as active in the device description file provided by you. So it seems to be a predefinition fault in the ESI file. Could you please get in contact with you supplier to clarify this?
As workaround as long as there is no correct file:
With assignment and with configuration on, then download, and powercycle this is the result:
Without assignment and with configuration on, then download, and powercycle this is the result:
Without assignment and without configuration on, then download, and powercycle this is the result:
With assignment and without configuration on, then download, and powercycle this is the result:
Thanks again for the clarification I had another talk to our R&D and we see that ESI file seems not to fit to your device connected to the EtherCat master.
UPDATE: Supplier sent a new device descrption file that should be tested. @Henderickx waiting for your feedback.
The reaction of Burster: "The main problem is, that the Bosch PLC does not support the online reading of the device configuration and the Bosch PLC does not support to load a TwinCAT configuration file."
I recieved the new XML file from them but still without succes.
I sent then the follow screen shots from the errors depending on the state of : "Slave has to reach master state "