6-Contributor

Solved

Kepware bad quality data not being sent to ThingWorx

Forum|Forum|2 years ago
July 26, 2023
4 replies
4559 views

Hi,

ThingWorx cannot read the bad quality data from Kepware?

Thanks

Hema

Connectivity

Best answer by pshashipreetham

Hi @MSK

Just adding some extra info from @NERaj,

In KepServerEx, the Tag address becomes a bad quality in the following scenarios:

When the connection with PLC or end client is disconnected
When there is a connectivity issue in terms of the IP of the Device or the KepServerEX

When there is bad quality, no data will be received by KepServerEx. Therefore, it will not be sending any data to Thingworx. The quality of the signals in the Thingworx will also be in the Bad Quality. If you have bonded to the Remote thing, you can write a logic to check which Signal is down.

Thanks,

P

PaiChung

22-Sapphire I

How did you determine this? Any data that is actually read and triggers a transmission in kepware should arrive in ThingWorx with said quality.

M

MSK

Author

6-Contributor

Hi,

In kepware we used to see data with good/bad quality. For good we are receiving the data from Kepware to ThingWorx but for bad quality we are not receiving, is this an expected behavior. some the tag values are not changing rather timestamp is changing, Is that possible to take timestamp values?

Thanks

Hem

P

PaiChung

22-Sapphire I

Not 100% sure what you are asking.

However if you set datachange to 'always' you would always trigger a datachange event when a value is updated even if the value stays the same (but only the timestamp changes)

I was under the impression that all value changes (good bad unknown) should be transmitted though.

You may need to file a support ticket.

S

slangley

Community Manager

Hi @MSK.

If you are still having issues and have not already opened a ticket, please let us know and we can open a ticket on your behalf.

Regards.

--Sharon

M

MSK

Author

6-Contributor

Thanks for the information.

S

slangley

Community Manager

Hi @MSK.

Were you able to resolve your issue? If so, please share your solution with the community.

Regards.

--Sharon

P

pshashipreetham

Answer

18-Opal

Hi @MSK

Just adding some extra info from @NERaj,

In KepServerEx, the Tag address becomes a bad quality in the following scenarios:

When the connection with PLC or end client is disconnected
When there is a connectivity issue in terms of the IP of the Device or the KepServerEX

When there is bad quality, no data will be received by KepServerEx. Therefore, it will not be sending any data to Thingworx. The quality of the signals in the Thingworx will also be in the Bad Quality. If you have bonded to the Remote thing, you can write a logic to check which Signal is down.

Thanks,

D

DH_9170547