About AutomateSHANE

@Filip_K to connect using EoE is not very difficult., it just requires several steps. From within IO Engineering, double-click the EtherCAT master, then select the EoE tab. Here, you must enabled the Virtual Ethernet port, and assign an IP address. You can do the same as I have set here: Notice that on the right the master will automatically assign an address to all slaves which have EoE enabled using the range .1 to .253 Below, it will show all of the slaves which are enabled, and their information. For example, my SAFEX control is listed first:   In order for this, you must enabled EoE for the SAFEX. Double-click your SAFEX control in IO Engineering, then click the check box for 'Expert settings'. Now you will see an EoE tab for the SAFEX. From that tab, you can enable the Virtual Ethernet port for SAFEX. Make sure it is selected 'IP-Port'. Here you will see the IP address of the SAFEX. In ctrlX SAFETY Engineering, navigate to 'Connection Settings' and select 'Ethernet'. Here you will enter the IP address that was displayed for the SAFEX. Now, you need to enable forwarding on the CORE. Log in to your ctrlX CORE via the web interface. Select Settings and then Network Interfaces. For both XF10 (or XF51 if you are connected this way) and 'eoe0' select 'Enable IP forwarding' The last step is set up routing on your PC. The IP address for the SAFEX is only on the EtherCAT bus. To connect using this, the Ethernet connection must be routed through the CORE. You must set up the routing table on your PC so that it knows the hop. In my case, my PC is connected to the XF10 port of my CORE, which is set to 192.168.1.1. Thus, I have set up a route through this address. Open a Windows command prompt with administrator priviledges. Type: route -p add 172.31.254.0 MASK 255.255.0.0 192.168.1.1 (or whichever IP addresses match your configuration. This adds a persistent route which will not change. If the address of your CORE will change in the future, or you only want to make the connection temporarily, do not include the '-p' in the command. Now you should be able to connect to SAFEX control from SAFETY Engineering using EoE!     ... View more

@Maax That is very interesting that this was a solution for you. I am also not using FastChannel, but my setting is already 'None' and I still have this problem. ... View more

@AllAutomation I had wondered if online edits or downloads via PLC Engineering were interfering with the bus communications. I am commissioning and debugging a machine, so this happens often. However, I stopped for a while and did nothing but monitor the bus status in IO Engineering. After some time between 5 and 10 minutes, the error occured again. Yes, a connection to the CORE from my PC was active with PLC Engineering and IO Engineering online, but nothing else was happening. ... View more

@AllAutomation I have used both USB and EoE. It does not make a difference in regards to this error. ... View more

@AllAutomation  The Log Book of the SAFEX is not very helpful. The entries are given based on operating time which must be rectified manually from the current time in seconds to days, hours, minutes, and seconds. It also does not sort in chronological order. I assume this is because it is a ring buffer. Anyways, there are not entires which correspond to the times that the 0x001B diagnostic appears. The only two alarms which appear are concerning two outputs, and I have verified that there is nothing wrong with them. Aside from that, the most frequent entry is Info Number 10260: - ctrlX SAFETYlink: EC_ZB_TIMEOUT_INIT. This also does not make sense because I am not using the SAFETYlink connection.   You see that the latest entry is 4d 2h, yet today I am already in excess of 4d 6h and there are no new entries. ... View more