Skip to main content
6-Contributor
February 19, 2025
Solved

Issue with Device Property Changes Not Being Applied in Kepserver

  • February 19, 2025
  • 2 replies
  • 1838 views

I am creating devices with the same IP and Slave ID and distributing the tags among them. When I create a device in the Kepserver application and modify its properties, the changes seem to be applied after saving. However, when I reopen the device, I see that the changes were not actually applied. However, if I copy a device with the desired properties and adjust it according to the device I tried to modify, everything works fine without any issues. Additionally, some devices like inv_02 and inv_05 constantly fall into "bad" status, losing their connection. How can we resolve this situation?

Best answer by rajskumar

Hello, 

Please take a look at the following article as it may help resolve your issue:

CS273673 - Unable to make configuration changes in Configuration Client or Datalogger Plugin in PTC Kepware Products

If you are prompted to log in to view the complete article, you can use your MyKepware login credentials.

 

For 2nd issue, 

  • After confirming connections settings are correct on Kepware side, tune the Request Timeout 
    1. Go to Device Properties >Timing > Request Timeout property
    2. Start with a high Timeout value of 5000
    3. Test whether the device still fails to respond within the Timeout
      • If this works fine and there are not demotions or device not responding messages, lower the timeout interval to half
        • Go to step 3
      • If it fails then raise the value by half
        • Go to step 3
      • Repeat this loop until you find the right interval for that device 

2 replies

rajskumar16-PearlAnswer
16-Pearl
February 19, 2025

Hello, 

Please take a look at the following article as it may help resolve your issue:

CS273673 - Unable to make configuration changes in Configuration Client or Datalogger Plugin in PTC Kepware Products

If you are prompted to log in to view the complete article, you can use your MyKepware login credentials.

 

For 2nd issue, 

  • After confirming connections settings are correct on Kepware side, tune the Request Timeout 
    1. Go to Device Properties >Timing > Request Timeout property
    2. Start with a high Timeout value of 5000
    3. Test whether the device still fails to respond within the Timeout
      • If this works fine and there are not demotions or device not responding messages, lower the timeout interval to half
        • Go to step 3
      • If it fails then raise the value by half
        • Go to step 3
      • Repeat this loop until you find the right interval for that device 
12-Amethyst
February 19, 2025

If this driver works like the database driver, you have to disable the channel first, then make the change, then reenable the channel. to make it stick.