• English
  • 中文
  • Français
  • Deutsch
  • Español
Contact Us
Home
Email
Follow Prosoft Technology on Twitter
Follow Prosoft Technology on Facebook
Follow Prosoft Technology on LinkedIn
Follow Prosoft Technology on YouTube
    • PROFINET Controller Module for ControlLogix®
    • EtherNet/IP™ to DH+ Gateway
    • Universal QuickServer Gateway
  • Solutions
    • Amusement
    • Automated Material Handling
    • 汽车解决方案
    • IIoT Solutions
    • Mining and Metals
    • Modernization
    • Oil and Gas Solutions
    • Secure Remote Connectivity
    • Water / Wastewater
  • 产品
    • 远程访问
    • 罗克韦尔自动化机架内产品
    • 网关
    • 工业无线设备
    • ProSoft 软件
  • 服务与支持
    • Knowledge Base
    • 区域技术支持
    • 下载
    • 培训
    • Return Material Instructions
    • 资料索取
  • 新闻与活动
    • ProSoft Insights (Blog)
    • Podcast
    • 成功案例
    • 新
      Knowledge Base / Gateways / PLX8x Gateways

      Why are MMS Reports not working?

      Search KB

      Categories

      • Gateways
        • ProLinx 4000/5000
        • PLX8x Gateways
        • QuickServer
        • PLX31/32 Gateways
        • PLX35 Gateways
        • AN-X / AN-X2
        • PLX51 Gateways
      • Rockwell In-chassis
      • Schneider In-chassis
      • Wireless
      • Accessories
      • Protocols
      • Software
      • Legacy Products
      • Certifications
      • Technical Support
      • Miscellaneous
      • 星期五, 2016年 十月 14日

      If MMS reports are not working with a ProSoft IEC 61850 client gateway please review the following points, as the most common reasons are listed below:

      1.Mismatch between the IEC 61850 client and server configuration: verify that the report configuration loaded in the Server and the configuration in the PLX81 are the same. In about 95+% of MMS report problems, the root-cause turns out to be that someone made changes to the report and downloaded the changes to the 61850 Server (Slave) without changing the Report configuration in the PLX8x- 61850 Client.

      2.Ensuring that a report is triggered correctly: In the 61850 Configuration file, if only one Report Trigger is configured for General Interrogation, then our gateway only performs this once on start-up. If it is desired to have it updated more than once, at boot-up, additional trigger options will need to be specified. Typically, customers use ‘intgPd’ (Integrity or periodic transmission), ‘dchg’ (send on Data Change or Report By Exception), or ‘qchg’ (send on Quality Change) as additional conditions to trigger the Server to send a MMS Report.

      Attachments

      Related Products