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

Community Tip - If community subscription notifications are filling up your inbox you can set up a daily digest and get all your notifications in a single email. X

Make it possible to configure tag-generation on a OPC-UA Client Device to be Read-only in Kepware

Make it possible to configure tag-generation on a OPC-UA Client Device to be Read-only in Kepware

When tags are generated using the OPC-UA Client driver in Kepware they are created with Client-Access "Read/Write" as default. There should be an Option on either the device or channel in Kepware to change this default behavior to Read only.

(The workaround currently is to utilize the export/import CSV function to change the the tag property to Read Only before importing the CSV file )

 

The reason is that in the normal ThingWorx monitoring scenario with Kepware, e.g. monitor a temperature value: It is dangerous to forget to change this configuration to "read-only" after importing tags.

 

This is quite easy to miss. Missing means that values in the PLC can be changed from the ThingWorx platform (depending on configuration). This can be extremely dangerous both from a process and/or safety perspective.

1 Comment
uyngvesson
7-Bedrock

I think there are a workaround for this by using the security policies in Kepware (separate install). Then you can set default access to all I/O Tags for the Thingworx Interface Users to Read Only. They are still R/W in Kepware, but they should be Read Only from Thingworx. Of course you can go in and unlock certain IO Devices or tags that you would need Write Access to. 

 Kepware Security Policy.png