cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - When posting, your subject should be specific and summarize your question. Here are some additional tips on asking a great question. X

Experience with Industrial Connectivity Kepware OPC-UA and the AutoID Companion Specification

RagnarRoestad
7-Bedrock

Experience with Industrial Connectivity Kepware OPC-UA and the AutoID Companion Specification

I'm looking into communicating with a Turk RFID Module for OPC-UA 

https://www.turckbanner.my/en/product/6814126

 

Does anyone have experience with use of Industrial Connectivity Kepware OPC-UA and the AutoID Companion Specification?

 

Any experience or general thoughts?

Any known pitfalls with either Kepware OPC-UA or working with the AutoID specification?

1 ACCEPTED SOLUTION

Accepted Solutions

Hi and thanks for your interest. 

 

We have been exploiting the Turck RFID system for a parts tracking scenario. AutoID have no key part in this scenario, it was a case of the OPC-Module only supporting communication based on this companion specification.

 

Based on this we will utilize the Multiprotocol module TBEN-L5-4RFID-8DXP-CDS. 

This device can be used as an EtherNet/IP device, Modbus TCP slave or PROFINET RT device. The device can also be used as master in a Modbus TCP fieldbus system. It can also be an OPC UA Server, but this device is not following the AutoID Companion Specification and it has to be used with CODESYS.

 

If combined with KepserverEx CODESYS driver one should be able to communicate on OPC-UA, but that would have to be verified by testing.

We have decided on using Modbus Ethernet in our project/customer offer as this is part of the Manufacturing Suite.

 

BR

/Ragnar

View solution in original post

3 REPLIES 3
egriffin
5-Regular Member
(To:RagnarRoestad)

Good morning - Expanded support of OPC-UA Companion Specifications is something we are actively researching as part of our forward-looking roadmap at Kepware.  Currently, we don't have a definitive timeline for when this would be available, as there are several pre-requisites involved.  However, we would be happy to engage with you in a discussion around use-case and business impact to understand your requirements.

 

Many thanks - 

Kepware Product Management

Hi and thanks for your interest. 

 

We have been exploiting the Turck RFID system for a parts tracking scenario. AutoID have no key part in this scenario, it was a case of the OPC-Module only supporting communication based on this companion specification.

 

Based on this we will utilize the Multiprotocol module TBEN-L5-4RFID-8DXP-CDS. 

This device can be used as an EtherNet/IP device, Modbus TCP slave or PROFINET RT device. The device can also be used as master in a Modbus TCP fieldbus system. It can also be an OPC UA Server, but this device is not following the AutoID Companion Specification and it has to be used with CODESYS.

 

If combined with KepserverEx CODESYS driver one should be able to communicate on OPC-UA, but that would have to be verified by testing.

We have decided on using Modbus Ethernet in our project/customer offer as this is part of the Manufacturing Suite.

 

BR

/Ragnar

Hi @RagnarRoestad.

 

If your last post has proven to be a viable solution, please mark it as the Accepted Solution for the benefit of others on the community.

 

Regards.

 

--Sharon

Top Tags