Hello:

We're trying to communicate with an SLC 5/04 PLC from WinCC via Ethernet. The PLC lacks an Ethernet port natively so we have included a 1761-NET-ENI interface. We have added the Allen Bradley - Ethernet IP driver to the WinCC Explorer project tree and configured the connection to the PLC, indicating the IP address of the ENI interface. Also and we have set the "Communication Path" to "1,0" .

However, we are unable to establish a connection an read/write values from/to the PLC. We have also tested with the communication path "1,2", considering that the ENI is connected to the PLC through the DF1 port, but this was also unsuccesful. Leaving the communication path was of no help, too.

I am not sure if the Allen Bradley - Ethernet IP driver supports the 1761-NET-ENI module. This may be causing the problem. Also I'm not sure if we are specifying the communication path correctly.

Maybe someone has accomplished this task succesfully. We are able to communicate from WinCC to an SLC 5/05 CPU, which has a native Ethernet port. My PC runs Windows 7 Professional 64 bits and the WinCC version is WinCC V7.0 + SP3 + Upd1, K7.0.3.1.

Thanks in advance for your help.

Best regards.

Sand_man

Did anyone in the mean find out if this is possible or not?

 Hi

Same problem , Support not say why , i not need opc i need eth connection .. 

I'm not sure that SLC500/04 has a ethernet port!

SLC500/04 has a DH+, RS-232-C (ASCII or DF1) port! Check documentation!

SLC500/05 has a Ethernet Built-in Ports integrated!

I'm using an SLC500/05 PLC with a WINCC 7.3 HMI project with a lot of problems. Becouse the Ethernet port communicates with a 10MB rate, the PLC is going in fault once/twice per week or the Ethernet channel goes in fault once/twice per week.

I've read that there are newer SLC 500/05 plcs that can communicate with 100MB (newer Firmware 10-13). Mine is Frm. 04!

Hello RobstMX,

unfortunately I cannot test this setup myself as I am using a SLC5/05 with builtin Ethernet port. However I may be able to shed some light onto the communication path issue here.

The communication with CIP (Common Industrial Protocol) is routed throught the nodes along the path.

The first node in your scenario would be the NET-ENI Bridge. It is identified by either it's host name or it's IP address.

The second node in here is the backplane, which can be reached via the internal interface of the NET-ENI bridge named '1'.

The third part of the path is the slot of the backplane where the communication endpoint, the CPU is located. This is supossed to be '0'

therefore the correct communication path should look like '1,0'. This is the default and should work in your described scenario.

The communication path components are part of the reading/ writing request in order to be evaluated by the NET-ENI bridge. Wireshark traces show, that the EtherNet/IP driver of WinCC V7.3 is NOT appending the necessary routing path components to the request packet, therefore you will get an 'addressing error'.
This issue has been reported and addressed in a newer version of the EtherNet/IP driver.