Skip to main content
K
KA_101640621-Visitor
1-Visitor
January 13, 2022
Solved

Kepserverex Device is not responding in EventLog

  • January 13, 2022
  • 1 reply
  • 10737 views

My Kepserverex Modbus Ethernet  installed in Windows Server 2012 connected to around 15 plc using tcp communication. All the my plc giving device is not responding for every few minutes in eventlog. In OPC client the tag quality will change from good to bad once awhile(not all the tag in the device only few of it)

Best answer by KCorrigan

Hi KA,

 

I would check the following 2 things next, though with either of these I would expect no communication at all:

 

1. Explicit Congestion Notification

  • When Explicit Congestion Notification (ECN) is enabled, some older devices will drop or reject the packets because of the manipulated header
    Disable ECN on the machine by:
    Launching a DOS command prompt by right-clicking and selecting Run as Administrator
    Type the following and then press Enter:
    ​netsh int tcp set global ecncapability=disabled
    Restart the computer

2. IF you saved and imported the project file from the another machine, you will want to check that the Network Adapters configured in the Channels/Devices in the KEPServerEX project are set to 'default' or one on this new machine instead of being bound to the NIC of the old machine still.

 

Another thought:

Since you are getting good comms occasionally, please make sure each of the 15 devices are on their own individual channel in KEPServerEX.

 

If none of these is the issue, please open a technical support case so we can get more details and files from you.

 

Thanks,

KC

1 reply

V
24-Ruby III
VladimirN24-Ruby III
24-Ruby III
January 13, 2022

 Hi,

 

Read this article - "Error "Device is not responding" in event log in PTC Kepware Products": https://www.ptc.com/en/support/article/CS276466 

K
KA_101640621-VisitorAuthor
1-Visitor
January 14, 2022

I already try this. I didnt face this connection issue when i test it in windows 10 using demo version kepserverex during development stage. This issue only come when i run the kepserverex in my window server 2012. 

K
KCorrigan14-AlexandriteAnswer
14-Alexandrite
January 20, 2022

Hi KA,

 

I would check the following 2 things next, though with either of these I would expect no communication at all:

 

1. Explicit Congestion Notification

  • When Explicit Congestion Notification (ECN) is enabled, some older devices will drop or reject the packets because of the manipulated header
    Disable ECN on the machine by:
    Launching a DOS command prompt by right-clicking and selecting Run as Administrator
    Type the following and then press Enter:
    ​netsh int tcp set global ecncapability=disabled
    Restart the computer

2. IF you saved and imported the project file from the another machine, you will want to check that the Network Adapters configured in the Channels/Devices in the KEPServerEX project are set to 'default' or one on this new machine instead of being bound to the NIC of the old machine still.

 

Another thought:

Since you are getting good comms occasionally, please make sure each of the 15 devices are on their own individual channel in KEPServerEX.

 

If none of these is the issue, please open a technical support case so we can get more details and files from you.

 

Thanks,

KC

    Terms & ConditionsCookie settingsAccessibility statement