Showing results 1 to 3 of 3

Thread: IEC 61850 .cid file import

  1. #1
    Join Date
    01.02.2017
    Posts
    6

    Default IEC 61850 .cid file import

    Hi to all.
    I have dilemma about how some files are imported with .cid file.
    Example:
    When I open xyz.cid file in notepad++ a get 6 values of mag.f[MX] type, but when I do import and when I filter those same tags with same name,
    there are more tags with extensions like [EX],[DC],[CF]...

    My question is, does Zenon during importing .cid file create those file?

    Please, look for picture in attachment.

    Regards,
    Damir
    Attached Thumbnails Attached Thumbnails cid_file.png  

  2. #2
    Join Date
    01.07.2008
    Location
    Salzburg, AT
    Posts
    809

    Default Re: IEC 61850 .cid file import

    >does Zenon during importing .cid file create those file?

    During variable import the iec850 driver is not creating, nor making updates, in CID-file. The driver reads the data model from the file and gives you possibility to create variables representing Data Attributes present in this data model. To create or update a CID-file you have to use an XML or SCL-editor. 

    On your screenshot i can see that this CID-file defines that the data model of the IED contains two identical Data Object (of type "MV_simple_i_e_#LIB1") with almost identical names - VoltsAB and VoltsAb (difference is upper and lower case char B), both in the same IED+Logical Device (XB1212A01F1LD0) and same Logical Node (FLTMSTA1). That's why then imported variables look double. But these are different variables, according the IEC61850 Standard the ObjectReferences are case sensitive
    BTW, this double definition looks like result of playing around with some SCL Editor, not like a reasonable file of a real device.
     
    And the line visible on your screenshot with "<FCDA ... fc="MX" />" does not define the data model of the IED. The keyword FCDA can be present only as member of a data set. A data set has nothing to do with variable list, this is additional info that Data Attributes from Object VoltsAB which have Functional Constraint MX can be delivered by reporting. The FCDA has no influence on the importing.
    And obviously - as driver has imported - the type "MV_simple_i_e_#LIB1" contains not only MX Data Attributes, but also some with FC=DC, EX and CF. And the screenshot does not show the definition of this type.

  3. #3
    Join Date
    01.02.2017
    Posts
    6

    Default Re: IEC 61850 .cid file import

    Tnx for Your reply. I appreciate YOur help.

    Regards,
    Damir

Similar Threads

  1. IEC 61850 disturbance file extraction
    By ansab.tp in forum zenon Energy Edition
    Replies: 8
    Last Post: 11th December 2017, 14:52
  2. 61850 SCL or ICD import
    By mehrdad66 in forum zenon Energy Edition
    Replies: 2
    Last Post: 26th April 2016, 09:53
  3. 61850 SCL or ICD import
    By mehrdad66 in forum Drivers
    Replies: 2
    Last Post: 26th April 2016, 09:53
  4. IEC 61850 disturbance file extraction
    By ansab.tp in forum Drivers
    Replies: 6
    Last Post: 16th April 2013, 07:28
  5. Help! I can not import my variables .dbf file
    By markclemens in forum zenon Supervisor
    Replies: 0
    Last Post: 20th August 2007, 15:36

Tags for this Thread

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •