Community Tip - When posting, your subject should be specific and summarize your question. Here are some additional tips on asking a great question. X
Hi,
Can Kepware connected tags in thingworx be scanned at one rate and be logged(in Value Streams) at different rates. For example, let say a tag OilTemp is set with scan rate of 3 secs and the logging option is checked. Not the data is displayed on a mashup and changes every 3 secs and gets logged simultaneously.
But instead of logging every 3sec, I want the data to be logged at every 1 min. ie. I want the displayed value to be changed every 3secs and wants that data to be logged with 1mins interval in valuestreams.
Can it be achieved?
Regards
Solved! Go to Solution.
That will cause some weird interference, because the scan rate is not actually set at the ThingWorx side but Kepware side, so the two bindings will interfere and I'm not sure which one would win or if it would just break.
You could use Advanced tags to duplicate tag values or the OPC aggregator and in that way achieve duplicate tags that could work with different scan rates.
Not sure what approach would be more efficient for you, the one I suggested or trying to go duplicate tags, which also means double the number of properties.
You would have to do that with a regular stream and a subscription.
Subscription either to a timer or based on a timestamp and vtq of property that is updating.
Hi PaiChung,
What if I bind a single kepware tag to two different thingworx properties. One with a scan rate of 3sec(Not logged) and the other with scan rate of 1min(logged), and use one for displaying and the other for logging data.
Will this be a good setup work, or does it hamper the performance is some way?
Thanks
SriH
That will cause some weird interference, because the scan rate is not actually set at the ThingWorx side but Kepware side, so the two bindings will interfere and I'm not sure which one would win or if it would just break.
You could use Advanced tags to duplicate tag values or the OPC aggregator and in that way achieve duplicate tags that could work with different scan rates.
Not sure what approach would be more efficient for you, the one I suggested or trying to go duplicate tags, which also means double the number of properties.