IO-Link

[jwbaker3]

Can I use the Stride IO-Link master with the BRX PLC? I see on AD has a lot of info on the Productivity PLC but nothing on BRX.

Thanks,
JW

[MAEdwards]

Whereas I want to try and be clear with regards to the capabilities of the Stride IO-Link Master, I also fear that the explanation is also going to make things appear more complicated. I am including the following information for both clarification of the device behavior, and for searchability within this forum for later.
 
The Stride IO-Link Master (SIOL-EI8B) uses the following Assembly Instances for EtherNet/IP IO (Implicit) Messaging:
?   Input Data: Assembly Instance 101
?   Output Data: Assembly Instance 111
?   Configuration Data: Assembly Instance 170

These Assemblies also support Explicit Messaging, but with one caveat:
?   Configuration Assembly 170 supports both data READ access and data WRITE access.
?   Input Assembly 101 supports data READ access, but not data WRITE access.
?   Output Assembly 111 supports data READ access, but not data WRITE access... sort of.  This is the caveat.
 
The Output Assembly actually DOES allow WRITE access AND will hold the value that is written to the data attribute, BUT the hardware WILL NOT react or respond the value. For example, you could WRITE a value to the Output Assembly that instructs the IO-Link Master to turn on an output. The message will successfully be sent and received, and the data attribute of the Output Assembly will contain the value that was written, but the hardware will NOT engage the output. This is common behavior with EtherNet/IP adapter devices. The ProtosX PX-EIP1 exhibits the same behavior.
 
So... why is this important to know?
 
To assume that the target device, in this case the Stride IO-Link Master, only supports Implicit Messaging for the Assembly Instances would be both inaccurate and misleading to the user. There are SOME scenarios where the user could use the Stride IO-Link Master with only an Explicit Messaging Client and still get what they need.

Here is an example scenario where Explicit Messaging WILL work for the user:
?   The Wenglor OPT2153 photoelectric sensor has 3 bytes of Input Data and no Output Data. The user could both configure the IO-Link Master AND get the Input Data
supplied by the Wenglor sensor using Explicit Messaging. 

Here is an example scenario where Explicit Messaging will only PARTIALLY work for the user:
?   The Captron Caneo Series 10 capacitive pushbuttons has 10 bytes of Input Data and 8 bytes of Output Data. The user could read the status information from the Captron device, but would not have the ability to control the LEDs with the Output Data.

Here is an example scenario where Explicit Messaging will NOT work for the user:
?   The Werma eSign Beacon and Siren devices have no Input Data and 3 bytes of Output Data. Explicit Messaging will not be an option for the user in this situation.
 
I hope this explanation doesn't make things more complicated. If you have a Stride IO-Link Master, feel free to test out these scenarios.

[jwbaker3]

No I understand what you are saying. I will have to use a product that is made for explicit messaging, I was hoping the Stride would work with this PLC but I will stick with the BRX and look for a IO Link master that can talk to it. I am looking at a Keyence IO Link master, they say it will work with explicit messaging. I am waiting for some information and a test unit to try. This is for a customer so it has to be rock solid when we leave.
Thanks for the information!

JW

[RBPLC]

I'll chime in here as I haven't posted in a while. BRX has to support implicit EIP as a master. I know you guys are working on it but there are too many products out there that are designed to be controlled with implicit EIP (even though it's a monster to wrangle).

[BobO]

I'll chime in here as I haven't posted in a while. BRX has to support implicit EIP as a master. I know you guys are working on it but there are too many products out there that are designed to be controlled with implicit EIP (even though it's a monster to wrangle).

It is the current development priority, meaning, we're working on it right now. It will be in the next release, later this year.