Article - CS276466
"Device is not responding" warning message in event log of PTC Kepware Products
Modified: 16-Jan-2026
Applies To
- Kepware Server (formerly KEPServerEX) 5.20.396.0 to 7.0
- ThingWorx Kepware Server (legacy) 8.0 to 6.18
Description
- Warn message in Kepware Event Log
-
Channel.Device | Device is not responding. | ID = 'xxx.xxx.xxx.xxx'.
-
- Will above warn message cause any performance issue?
- Failed connection to PLC device
- Ping PLC device IPAddress/Port successfully , but received Bad quality data in Quick Client
- Receiving "unknown" value and "bad" quality for tags on a particular device
- Resolution steps for the "Device is not responding" in PTC Kepware Products
- Communication Diagnostics log shows good read requests (TX), but no responses (RX)
- User mentioned that various Vaisala devices are live and measuring gas values (verified via individual web portals), but Kepware is not receiving telemetry data and shows "Device is not responding" errors
- Tuning the Request Timeout property
- User reported that there is no communication with BACNet Driver and seeing “Device is not responding” errors
- PLC not communicating with error
Device is not responding
- Event log message
-
<channel.device> has been automatically demoted
-
This is a printer-friendly version of Article 276466 and may be out of date. For the latest version click CS276466