I am using ThingWorx Platform Release 8.4 and DatecodeF000
设备经常出现断连情况,kepware设备取数正常,但是twx提示设备未连接,里面数据全部没有获取。
Solved! Go to Solution.
Hi @SZ_8739263
Adding the following translations of your original question for the other Community users:
-----------------
Subject: The device is abnormally disconnected
Body:
I am using ThingWorx Platform Release 8.4 and DatecodeF000.
The device is often disconnected. Kepware can retrieve data from the device normally, but TWX prompts that the device is not connected and all the data in it cannot be retrieved.
-----------------
It seems like the connection between Kepware and ThingWorx is broken, thus the remote industrial thing is not connected.
Is it working at the beginning? I suggest firstly checking the connection settings for the ThingWorx Interface in Kepware to make sure every setting item is correctly set.
If all the settings are working and the remote industrial thing is connected, but sometimes it breaks, it may be related to intermittent connection issues. In that case, you will need to diagnose at the network level (e.g., utilizing other third-party tools like Wireshark to narrow down the root cause).
Hi @SZ_8739263
Adding the following translations of your original question for the other Community users:
-----------------
Subject: The device is abnormally disconnected
Body:
I am using ThingWorx Platform Release 8.4 and DatecodeF000.
The device is often disconnected. Kepware can retrieve data from the device normally, but TWX prompts that the device is not connected and all the data in it cannot be retrieved.
-----------------
It seems like the connection between Kepware and ThingWorx is broken, thus the remote industrial thing is not connected.
Is it working at the beginning? I suggest firstly checking the connection settings for the ThingWorx Interface in Kepware to make sure every setting item is correctly set.
If all the settings are working and the remote industrial thing is connected, but sometimes it breaks, it may be related to intermittent connection issues. In that case, you will need to diagnose at the network level (e.g., utilizing other third-party tools like Wireshark to narrow down the root cause).
Hi @SZ_8739263
I’ve provided some input on your topic. If you find it helpful, please consider marking it as the Accepted Solution so that other Community Members with similar questions can benefit from it.
In the event that this response did not answer your question, please post your current status so that we can continue to support.
Thanks for using the PTC Community!
Regards,
Charles