• 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

      Issue importing ICD device template file into the 61850 Configuration manager

      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日

      When using a .ICD file to configure devices on an IEC 61850 network there are potential issues in importing the file into the 61850 Configuration Manager software.  There are a couple of things to look at. 

      1)       The configuration tool accepts only configured IED files such as .CID and .SCD files.  The only reason that the configuration tool allows the importing of an .ICD file is that some major equipment vendors actually export a .ICD file, but with configuration settings such as a .CID file (with IP Address defined).  The .ICD file is normally a template file, and does not contain an IP address for the device, so this is certainly not standard, but to support this vendor we allow a configured .ICD file to be imported in the software. 

      2)      The configuration tool does not allow the same IED Name to be used.  So even though you have the following file names (RELAY1.ICD and RELAY2.ICD) if the IEDName field inside the configuration file says TEMPLATE for both, then you will not be able to import both of the configuration files.  Each IED Name must be unique (this is defined around lines 7 and 37 of the .ICD file)

      When using .ICD files in the configuration software, make sure that the file is configured (contains an IP address) and not just a template file.  Additionally if importing multiple .ICD files, make sure that the IED Name is unique for each. 

       

      Attachments

      Related Products