Hi

We have a S7-1513 R/H PLC connected to a ABB XT2 circuit breaker via profinet. 

The circuit breaker uses a EKIP Hi-Touch LSI unit with EKIP COM Profinet module. 

In TIA portal V17 we use the GSMDL profinet driver: 1SDH002031A1101-C .zip file

After a full hardware and software download we get det following error message:

"Error: IO device connection failure - Too many IO controllers accessing device EkipCOMProfinet"

As seen in the attachement the GSMDL device must be connected to both CPU's since it is a R/H system. 

Any advice on what is wrong or what to check further? 

TN123

Hi

We have a S7-1513 R/H PLC connected to a ABB XT2 circuit breaker via profinet. 

The circuit breaker uses a EKIP Hi-Touch LSI unit with EKIP COM Profinet module. 

In TIA portal V17 we use the GSMDL profinet driver: 1SDH002031A1101-C .zip file

After a full hardware and software download we get det following error message:

"Error: IO device connection failure - Too many IO controllers accessing device EkipCOMProfinet"

As seen in the attachement the GSMDL device must be connected to both CPU's since it is a R/H system. 

Any advice on what is wrong or what to check further? 

 I interpret the message: 
"Error: IO device connection failure - Too many IO controllers accessing device EkipCOMProfinet"

as telling us that he EKIP Profinet module does not support S2 redundancy, so it can only maintain a relationship with one PN controller at a time.  This does not necessarily mean that it cannot be part of a redundant system, but it does mean that its switchover performance will not be as "bumpless" as a device that supports S2 redundancy.  For details on connecting S1 redundant devices to a S7-1500R/H system, see Redundancy: Switched S1 device

Thanks for the answer. 

To exclude the possibility of S1/S2 redundancy issues I connected the circuit breaker to a regular et200 1510P CPU with no other profinet devices on the network. See attached topology.

However, the same error message appares. 

Possibilities I can think of:

• The device is remembering a previous PN controller connection, so won't let the current PN controller take it over.  Normally, there is a timeout period set for a device.  If the time elapses without a message from the PN controller, the device releases its relationship with the controller and will talk to any controller that attempts to connect it and knows its correct PN name.  It is possible that this timeout is disabled or set to a very long period, so it is still waiting for the first controller that ever connected to it.
• The device may have a "number of controllers" setting somewhere that got set to 0.
• The PN name of the device in the TIA Portal project may not exactly match the PN name that the device has.  This could cause communication connection problems.  I would normally expect the error message to be more exact in this case, but it is possible that there is just 1 catch-all error message.

Thanks for the answer.

- During operation I have done a power cycle on the IO device. Would think this would break the AR connection with the IO controller? But it might be something there. 

- The GSD file says "number of allowed connections = 1". And there is no configuration allowed in TIA portal for that. 

- In TIA portal I have sucessfully set the profinet name of the device (at leaset it says the prosess was sucessfull)

The thing is that I really cannot log on and see the approperiate settings on the EKIP COM module. The onboard display only displays "enable", MAC adderss and serial number. No IP address or profinet name. I'm waithing for a EKIP programming device ordered from ABB to see if there is more settings avaliable. 

Anyway, thanks for all the help!

Hi

Did you manage to setup the ACB without the programming device? Is that device needed?

Thanks in advance for your help