我們的品牌

Impact-Company-Logo-English Black-01-177x54

歡迎造訪施耐德電機全球網站

歡迎訪問我們的網站
		
我们今天能为您提供什么帮助?
PME - VIPs with Modbus Slave Modules going stale

Issue

A VIP configured with Modbus Slave Modules repeatedly goes stale and stops responding to Modbus polls. Trying to restart the ION Virtual Processor Service for the VIP causes it to get stuck in the "Stopping" state. An error message shows in Management Console > System Log Events: "Subscription watchdog caught 'Real Time Data Proxy did not respond on time."

Subscription watchdog caught error

Product Line

Power Monitoring Expert 7.x

Power Monitoring Expert 8.x

Power Monitoring Expert 9.0

Power Monitoring Expert 2020

Power Monitoring Expert 2021

Power Monitoring Expert 2022

Environment

VIP Modbus Slave

Cause

A software component connection error occurs, requiring the VIP to be restarted.

Resolution

Upgrade Power Monitoring Expert (PME) to the latest version. The issue no longer occurs on version PME 2023 or later.

Until PME can be upgraded, the following workaround can be implemented to automatically force restart the VIP when it goes stale:

1. Select or create another VIP with no other modules (or at least no Modbus Slave Modules). This selected VIP will be used to automatically monitor and force restart the other VIP that is going stale. If needed, refer to this article for how to create a new VIP.

2. Open Services > right-click the ION Virtual Processor Service (for that selected VIP) > Properties > Log On > check the box for Local System account

Set to Local System

3. Create a .txt file using Notepad and save with the following text, replacing VIP.Modbus_Slave (2 instances) with the name of the VIP that is going stale.

taskkill /F /FI "SERVICES EQ PMLVIP_VIP.Modbus_Slave"
NET START PMLVIP_VIP.Modbus_Slave

4. Change the file type to .bat

Configure batch file

5. In Designer, open the selected VIP (not the VIP that is going stale).

6. Add a Data Monitor Module with its input linked to an output register of a module in the VIP that is going stale

Link to module in VIP going stale

7. Set the Data Monitor Module Duration to 60 seconds (or some other interval)

Set DMM duration

8. Add a Launching Module, link the Trigger output of the Data Monitor Module to the Launch input of the Launching Module

9. Set the Launching Module RunCommand to the path of the batch file

Set Launching Module path

6. Test the configuration by manually stopping the ION Virtual Processor Service for the VIP that is going stale. After the duration in the Data Monitor Module finishes, it should execute the batch file to restart the service automatically.

Confirm result of test using Windows Logs - Application

Note: When PME is upgraded to version 2023 or later, the configuration added using the above steps can be removed. However, an additional step will need to be followed to ensure continued VIP Modbus Slave functionality in the new version:

  • Right-click on each ION Virtual Processor Service (corresponding to a VIP with Modbus Slave Modules) > Properties > change the Startup Type to "Automatic (Delayed Start)"
  • This has the VIP start after the licensing service starts (which is the ION Application Modules Provider Engine Host) so it recognizes the Data Exchange Module and keeps its Modbus Slave Modules active

施耐德電機Taiwan

探索更多
系列:
探索更多
系列:

需要協助?

  • 產品選型工具

    快速輕鬆地為您的應用找到合適的產品和附件。

  • 取得報價

    立即線上提交您的銷售需求,專業團隊將主動聯繫您。

  • 購買地點

    輕鬆在您所在地區找到最近的施耐德電機經銷商。

  • 支援中心

    在同一位置找到滿足您所有需求的支援資源。

  • 產品文檔
  • 軟體下載
  • 產品選型工具
  • 產品替代和替換
  • 幫助和聯絡中心
  • 尋找我們的辦公室
  • 取得報價
  • 人才招募
  • 公司簡介
  • 舉報不當行為
  • 無障礙
  • 新聞中心
  • 投資者
  • 專業洞察
  • 台灣施耐德電機學院
  • 綠色影響力落差調查
  • Schneider Go Green 2025
  • 隱私政策
  • Cookie通告
  • 使用條款
  • Change your cookie settings