JB2020 (Customer) asked a question.

I/O Link Durability

I am designing a control system for a conveyor distribution system. I am thinking of using I/O link for all the inputs (mechanical limit switches, photoeyes, etc.). As for outputs, it would mainly be pneumatic solenoid valves and warning lights.

 

Is I/O link reliable enough or maybe the better question is, what is the longevity of it? This is the first time I'm using it so I would like to here some opinion (negative and positive) from some of you seasoned designers/integrators.

 

I looked for I/O Link pneumatic valves but all I could find were the Ethernet CMV controlled valve blocks. These will work but was curious how reliable it all is?

 

Also found the PAL valve blocks... These are ethernet but not I/O link. Maybe they don't make a I/O link air valve...

 

EDIT ...

I understand I/O Link is a communication protocol, and maybe asking about the "durability" of it wasn't the right question. I understand that it can cut down on wiring and PLC cards.

My real concern would be, I am familiar with running hard wires to/from inputs/outputs. Switching to a communication method and knowing how connection issues have plagued me in the past, I was a little wary of doing that.

Some suggestions or help would be appreciated...

 

EDIT 2 ...

I've been playing around with it and I like what I'm seeing so far. The latency concerns me a bit. Is this really only for slower inputs? I was hoping to use a photoeye to watch sprocket teeth for a "zero speed input" like to sense whether a chain stops or not. It may work but it doesn't seem to catch every input that I give it. I am not talking about a high speed input here...I can use a mechanical limit switch on my test panel and trigger it as fast as I can with my hand and it doesn't catch every input. Any thoughts?

 

 


  • Durallymax (Customer)

    It sounds like all you want is field discrete I/O, not necessarily IO-Link. IO-Link is great when you have sensors you need more data out of or you want to send config data to. For a bunch of limit switches, solenoids and photoeyes, there are simple remote IO options in the same form factor without the IO-Link layer. I like IO-Link, but it adds a layer of complexity as you have the IO-Link data going over another protocol into your PLC. First you need to sort out the comm protocol and then the IO-Link data.

     

    There is no shortage of IO-Link capable pneumatic valves, and also just valves with plain I/O built in. I don't know if AD sells them, but the big names in pneumatics do. These may meet your needs.

     

    Also, unsure of your conveyor sizes, but current IO-Link standards have a limit of 20m.

    Expand Post
    Selected as Best
  • Durallymax (Customer)

    It sounds like all you want is field discrete I/O, not necessarily IO-Link. IO-Link is great when you have sensors you need more data out of or you want to send config data to. For a bunch of limit switches, solenoids and photoeyes, there are simple remote IO options in the same form factor without the IO-Link layer. I like IO-Link, but it adds a layer of complexity as you have the IO-Link data going over another protocol into your PLC. First you need to sort out the comm protocol and then the IO-Link data.

     

    There is no shortage of IO-Link capable pneumatic valves, and also just valves with plain I/O built in. I don't know if AD sells them, but the big names in pneumatics do. These may meet your needs.

     

    Also, unsure of your conveyor sizes, but current IO-Link standards have a limit of 20m.

    Expand Post
    Selected as Best
    • JB2020 (Customer)

      That may be better to do remote IO. Is the 20m for the IO Link cables only or is that for the Ethernet cable going to/from PLC and IO Master too?

       

      • z28z34man (Customer)

        The 20M cable limit is IO Link sensors to the IO Link master. I do not believe Digital IO to the IO link master has a limit but i am not sure. for Ethernet i would think the standard 100M limit of an ethernet cable.