Skip to main content
S
SN_101104673-Newcomer
3-Newcomer
February 17, 2022
Solved

Kepware Complex Tag TimeStamp Issues

  • February 17, 2022
  • 2 replies
  • 1846 views

Hii PTC Team,

 

We are using Kepware and the Advanced Tag plug-in with the above-mentioned details and creating complex tags, which are being updated using a Trigger Tag.

 

The Issue which we have observed is in terms of Complex Tags configuration, normally Complex Tags should triggered when our Trigger Tags are triggered, but we have observed that whenever we are launching Kepware Quick Client. In that particular timestamp also our Complex Tag is being generated.

 

We are using this complex tag’s XML data over the ThingWorx Platform and in the ThingWorx Platform valuestream, we observed that whenever we launch the Quick Client of Kepware, then the trigger tag is logged with the launch timestamp. We have set Complex Tag logging to be on only when a value is changed in ThingWorx Platform.

 

We know this shouldn't be happening because Quick Client is just for monitoring data quality and value, but it is happening.

 

Best answer by slangley

Hi @SN_10110467

 

In a review of the case, it was determined that the behavior you described is expected. The Quick Client is treated as a just another OPC client and when it connects it is telling TKS to get an initial read from the complex tag which is causing it to update.

An option to prevent this is to disable the Quick Client from automatically building a client project when it is opened through the toolbar in the server window. You could then build a Quick Client project that does not contain any tags that you don't want to trigger an update on. This can be done by opening Quick Client and selecting Tools -> Options -> Unchecking "Automatically build a client project when launched by the server."

You can also open the Quick Client without auto building a project by opening it through the system tray by right clicking the ex icon and selecting Quick Client. This will open an empty Quick Client regardless of you unchecking the option above. 

 

If you feel this information helped you to find a solution, please mark this post as the Accepted Solution for the benefit of others with the same question.

 

Regards.

 

--Sharon

2 replies

S
slangleyCommunity Manager
Community Manager
March 3, 2022

Hi @SN_10110467.

 

It appears a case was opened for this issue.  Once the case is resolved, I will post the solution here.

 

Regards.

 

--Sharon

S
slangleyCommunity ManagerAnswer
Community Manager
May 2, 2022

Hi @SN_10110467

 

In a review of the case, it was determined that the behavior you described is expected. The Quick Client is treated as a just another OPC client and when it connects it is telling TKS to get an initial read from the complex tag which is causing it to update.

An option to prevent this is to disable the Quick Client from automatically building a client project when it is opened through the toolbar in the server window. You could then build a Quick Client project that does not contain any tags that you don't want to trigger an update on. This can be done by opening Quick Client and selecting Tools -> Options -> Unchecking "Automatically build a client project when launched by the server."

You can also open the Quick Client without auto building a project by opening it through the system tray by right clicking the ex icon and selecting Quick Client. This will open an empty Quick Client regardless of you unchecking the option above. 

 

If you feel this information helped you to find a solution, please mark this post as the Accepted Solution for the benefit of others with the same question.

 

Regards.

 

--Sharon

Terms & ConditionsCookie settingsAccessibility statement