Showing results 1 to 3 of 3

Thread: Communication with IEC 61850 edition 1 and edition 2 simultaneously

  1. #1
    Join Date
    10.05.2017
    Posts
    68

    Frage Communication with IEC 61850 edition 1 and edition 2 simultaneously

    Hello team,
    While communicating with IED Devices of both IEC 61850 Edition 1 and edition 2 simultaneously, is there any prerequisites/necessary settings that needs to be taken care off?
    Can both the Edition devices communicate with the same IEC 61850 driver or shall I go with separate drivers. 
    Please suggest.

  2. #2
    Join Date
    01.07.2008
    Location
    Salzburg, AT
    Posts
    878
    Best Answer

    Default Re: Communication with IEC 61850 edition 1 and edition 2 simultaneously

    The iec850 driver works as well with Edition 1 and Edition 2 devices. The driver works always according online information from IED (850-Server), so if IED supports features introduced in Edition 2 - then the driver can use it. There is no extra setting to configure "edition" in general, you have to use settings "one-by-one" pro wished feature. Note that already in Edition 1 there are many differences in implementations of different manufactures, so it may happen that some feature (and driver setting) working with one device, does not work with another.

    For example, some Ed.1 devices are using fix Optional Fields (RCB.OptFlds), so even when the SCL-file expects they are dynamically changeable and you configure the driver to overwrite OptFlds, the IED will refuse to change. Then the driver will use the RCB like it is (with OptFlds the IED had). Be careful by overwriting OptFlds.EntryID of an unbuffered RCB - some IEDs are then sending malformed reports (but make sure to use EntryD in BRCBs).

    A typical mistake in IEDs running according Ed. 1 is missing Trigger Option 'general interrogation' (RCB.TrgOps.gi). So, if the IED is not delivering initial values for reported variables - try to configure the driver to overwrite the TrgOps - set 'data-change' & 'quality-change' & 'gi' (but do not try to use 'data-change' and 'data-update' in one RCB). And my experience shows that some Ed.1 devices are not supporting some TrgOps and/or not allowing to overwrite whatever the SCL-file defines...

    It also may turn out that you would have to activate check-box 'Do not send MMS-Abort' (available in latest builds/versions). This is because some IEDs are not supporting association's Abort according right guidelines; then the symptom - when you disconnected from IED (e.g. after you did in Editor online import or you exited the Runtime) - the IED hangs or has problem by reconnect etc.

    All relevant settings in driver are available pro connection, thus you can use few instances of drive or few connections in single driver, it's fully up to what you like.
    Last edited by ursulak : 6th August 2018 at 09:55 Reason: typo

  3. #3
    Join Date
    10.05.2017
    Posts
    68

    Daumen hoch Re: Communication with IEC 61850 edition 1 and edition 2 simultaneously

    Thank You Ursula.






    Joel.

Similar Threads

  1. Edition falsch
    By robs in forum Editor and Runtime Setup
    Replies: 1
    Last Post: 16th March 2017, 10:36
  2. IEC 61850 Edition 2
    By altera in forum zenon Energy Edition
    Replies: 4
    Last Post: 26th April 2016, 11:27
  3. IEC 61850 Edition 2
    By altera in forum Drivers
    Replies: 4
    Last Post: 26th April 2016, 11:27
  4. Standard Edition Commands
    By tihomir in forum zenon Energy Edition
    Replies: 3
    Last Post: 1st May 2013, 00:40

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
  •