QuoteWhat is the role of this computer? Is it Ethercat controller or device? Ethercat bridge is used when connecting two Ethercat networks that already have controller ("master"). bridge acts as device ("slave") to both of them (it serves two masters). If your computer is acting as device, this will not work. On each network there must be master-slave relationship where one master can have one or more slaves.
I forgot to mention that I will connect an EK1100 to the computer and run my PLC program on the computer. I will connect some IO terminals to the EK1100 and then go into some pneumatic vents. The computer will be an EtherCat master with TwinCAT 3. So it will be Computer <-> EK1100 <-> EL6695 Slave ...
Quotestop thinking about your own needs. robot has needs too. and robot needs safety interface. what is the safety interface that your robot was shipped with? Where did the PLC come from - it does not show up in your connections:
"KRC4 <-> EK1100 <-> EL6695 Master <-> EL6695 Slave <-> Computer"
With PLC I meant my computer which will work as a PLC. I am not very familiar with the KRC4. Actually I am working on reading all the documentation. The KRC4 was used before my project from other colleagues. Right now it is in a working condition, so there are external emergency buttons connected to X11. I pushed the buttons and they are working, I can see it in the user interface. In WorkVisual I can see "CIB SR Safety Module (SION-CIB-SR)".
Quotetwo...? what two?
you need to read the documentation and talk to KUKA sales guy. when you buy robot, you should order it with mxAutomation. mxAutomation is available with interface/library for different PLC brands (AB, Siemens, Beckhoff). that library need to be installed into PLC programming software. then you get access to mxAutomation instructions (function blocks).
I spoke with my team and they told me, that there was already a KRC4 with KSS 8.3. So the KRC4 was upgraded to 8.6 and we got the new hardware and software from KUKA. The robot was not replaced and is still from earlier. Therefore it wasnt ordered with mxAutomation. With two I mean buying mxAutomation from KUKA and mxAutomation Library from Beckhoff (TF5120) for TwinCAT.
Quotemost robots do not use mxAutomation. KSS is quite capable or controlling robot on its own - without mxAutomation. mxAutomation is just an option that allows writing programs in PLC instead of on robot HMI. it is meant for people familiar with PLC but with little or no experience with robots
As far as I understand now one way would be to map PLC IOs with the EL6695 to the KUKA IOs. Can I use these IOs then to trigger commands inside my robot program? For example when I would write a program inside my KUKA like (only conceptual description):
If IO1 = TRUE then execute MOVEMENT1