Hello
Can the EthernetIP driver in WinCCOA connect to the new PLC Schneider eg:
- BME H584040 central unit
- NOC communication module (e.g. BME NOC0301).
Currently, in configuring this driver it is possible to select from the list only PLC Allen Bradley.
The WinCC OA documentation also mentions only PLC Allen Bradley.
Is there any method to connect to PLC Schneider with this driver?
Maybe there are some tips or someone has succeeded to connect to the new PLC Schneider using EthernetIP (EIP) driver.
Unfortunately, I was unable to connect to the Schneider PLC. I tested on
BME H584040 central unit or BME NOC0301 communication module using the EthernetIP driver in WinCCOA.
Will Siemens plan to develop this driver (EthernetIP) by adding native support for Schneider controllers.
This would make it easier to cooperate with the new PLC Schneider in comparison to the MODBUS driver.
Regards
Karol Burnecki
EthernetIP ( EIP ) driver WinCCOA not connect to Schneider PLC
- burneckik
- Posts:1
- Joined: Tue Feb 13, 2018 2:59 pm
EthernetIP ( EIP ) driver WinCCOA not connect to Schneider PLC
- pwbarrett
- Posts:9
- Joined: Mon Jan 31, 2011 10:18 am
Re: EthernetIP ( EIP ) driver WinCCOA not connect to Schneider PLC
Karol,
Unfortunately, the EIP specification is very loose, with some features optional, and also allowing vendor-specific features & functions.
We previously made a custom version to support another vendor's PLC and it was not a simple task.
I would guess that Schneider did not implement things the same way as Allen Bradley.
I assume that you have tried connecting it as if it were a ControlLogix? If so it would be interesting to turn on full debug in the driver (-dbg ALL) and try to connect, then see if a specific error code is reported.
There is no plan at this moment to add support for Schneider PLCs, but maybe someone could be convinced to do so.
In the meantime, I wonder if Kepware will talk to it?
-- Paul Barrett
Siemens Industry
Unfortunately, the EIP specification is very loose, with some features optional, and also allowing vendor-specific features & functions.
We previously made a custom version to support another vendor's PLC and it was not a simple task.
I would guess that Schneider did not implement things the same way as Allen Bradley.
I assume that you have tried connecting it as if it were a ControlLogix? If so it would be interesting to turn on full debug in the driver (-dbg ALL) and try to connect, then see if a specific error code is reported.
There is no plan at this moment to add support for Schneider PLCs, but maybe someone could be convinced to do so.
In the meantime, I wonder if Kepware will talk to it?
-- Paul Barrett
Siemens Industry