Showing results 1 to 4 of 4

Thread: Zenon Energy Edition IEC104 driver Redundancy According Edition 2 LANGROUPS

  1. #1
    Join Date
    19.01.2017
    Posts
    12

    Default Zenon Energy Edition IEC104 driver Redundancy According Edition 2 LANGROUPS

    Hi,



    I have a question related to redundancy
    according IEC60870-104 Edition 2.




    I'm at the moment converting a Sicam 230 program
    into a Zenon program.




    The existing configuration with Sicam 230 has
    following setup:




    - Two Redundant Sicam 230 SCADA Servers.

    - Two Redundant PLC's.

    - IEC104 connection between the Active Sicam
    Server and the Active PLC.  (so, 4 possible interfaces depending on which SCADA server is active and which PLC is active.  Only 1 connection is active at a time)




    This was configured in the AK driver using 1
    LANGROUP and 2 LANCONS.




    In the IEC104 driver in Zenon, I can find an
    option to activate redundancy according IEC60870-104 Edition 2 but I don't see
    any settings on how to configure a redundancy using LANGROUPS (as mentioned in
    IEC60870-104 Edition 2).




    Does anybody know how to setup redundancy with
    LANGROUPS in Zenon Energy Edition?

    Philippe

    PS: Hereafter the setup as made in the AK driver for information:

    /*
    // CONNECTION TO DATA COORDINATOR, CHANNEL 1

    [LANCON1]    
    TOPOLOGY_CONN_SYSTEM=2,2            //*** Topology of connected System (Component) ASDU adress Siemens
                                        //*** RegionComponentofHead
    TOPOLOGY_CONN_SUB_SYSTEM=NO         //*** Topology of connected Sub-Systems (Sub-Components)
                                        //*** RegionComponentofSub1*RegionComponentofSub2*...
    TOPOLOGY_CONN_SYSTEM_RED=NO         //*** Redundant Topology of connected System
                                        //*** Region Component or NO
    TOPOLOGY_CONN_SUB_SYSTEM_RED=NO     //*** Topology of connected Sub-Systems (Sub-Components)
                                        //*** RegionComponentofSub1*RegionComponentofSub2*...
                                        //*** NO...if not redundant, COMMON...if common sub

    Mode=CONTROLLING                    //*** CONTROLLING or CONTROLLED
    LAN_Nr=3                            //*** Lan number Linkaddress
    LAN_Nr_RED=4                        //*** Redundant Lan number Linkaddress // 23/11/2015 modified from NO to 4
    SYSTEM_TYPE=AX                      //*** AX/ACP/SK (default is AX)
    ADR_TYP=PTA                         //*** PTA processtechnical, STA systemtechnical
    TIMEMASTER=NO                       //*** Timemaster NO or Region, Component
    CON1=LAN*10.161.249.120:2404        //*** LAN*IP-address*PORT = IP address Data Coordinator
    CON2=LAN*10.161.249.121:2404        //*** LAN*IP-address*PORT 
    CON3=LAN*00.00.00.00:0000           //*** LAN*IP-address*PORT    
    CON4=LAN*00.00.00.00:0000           //*** LAN*IP-address*PORT

    IEC104_t0=30                        //*** Timeout of connection establishment [s],                    Default = 30 
    IEC104_t1=15                        //*** Timeout of send or test APDUs [s],                          Default = 15 
    IEC104_t2=10                        //*** Timeout for acknowledges in case of no data messages [s],   Default = 10 
    IEC104_t3=20                        //*** Timeout for sending test frames in case of idle state [s],  Default = 20 
    IEC104_k=12                         //*** Max. difference receive seq. number to send state variable, Default = 12 
    IEC104_w=8                          //*** Latest acknowledge after receiving w I-format APDUs,        Default = 8 
             

    // CONNECTION TO DATA COORDINATOR, CHANNEL 2

    [LANCON4]    
    TOPOLOGY_CONN_SYSTEM=2,2            //*** Topology of connected System (Component) ASDU adress Siemens
                                        //*** RegionComponentofHead
    TOPOLOGY_CONN_SUB_SYSTEM=NO         //*** Topology of connected Sub-Systems (Sub-Components)
                                        //*** RegionComponentofSub1*RegionComponentofSub2*...
    TOPOLOGY_CONN_SYSTEM_RED=NO         //*** Redundant Topology of connected System
                                        //*** Region Component or NO
    TOPOLOGY_CONN_SUB_SYSTEM_RED=NO     //*** Topology of connected Sub-Systems (Sub-Components)
                                        //*** RegionComponentofSub1*RegionComponentofSub2*...
                                        //*** NO...if not redundant, COMMON...if common sub

    Mode=CONTROLLING                    //*** CONTROLLING or CONTROLLED
    LAN_Nr=4                            //*** Lan number Linkaddress
    LAN_Nr_RED=3                        //*** Redundant Lan number Linkaddress // 23/11/2015 modified from NO to 4
    SYSTEM_TYPE=AX                      //*** AX/ACP/SK (default is AX)
    ADR_TYP=PTA                         //*** PTA processtechnical, STA systemtechnical
    TIMEMASTER=NO                       //*** Timemaster NO or Region, Component
    CON1=LAN*10.161.249.121:2405        //*** LAN*IP-address*PORT = IP address Data Coordinator
    CON2=LAN*10.161.249.120:2405        //*** LAN*IP-address*PORT 
    CON3=LAN*00.00.00.00:0000           //*** LAN*IP-address*PORT    
    CON4=LAN*00.00.00.00:0000           //*** LAN*IP-address*PORT

    IEC104_t0=30                        //*** Timeout of connection establishment [s],                    Default = 30 
    IEC104_t1=15                        //*** Timeout of send or test APDUs [s],                          Default = 15 
    IEC104_t2=10                        //*** Timeout for acknowledges in case of no data messages [s],   Default = 10 
    IEC104_t3=20                        //*** Timeout for sending test frames in case of idle state [s],  Default = 20 
    IEC104_k=12                         //*** Max. difference receive seq. number to send state variable, Default = 12 
    IEC104_w=8                          //*** Latest acknowledge after receiving w I-format APDUs,        Default = 8                    
                                        
    //************************************************** *********************************
    //*************************** definition of LAN-Groups ******************************
    //************************************************** *********************************
    [LANGRP1]                                    
    LANCON1
    LANCON4






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

    Default Re: Zenon Energy Edition IEC104 driver Redundancy According Edition 2 LANGROUPS

    What you are describing it is not the IEC60870-5-104 Edition 2.0 redundancy. The standard defines the redundancy of the Data Link layer: between single controlling station (master, e.g. zenon iec870 driver) and single controlled station (a slave, e.g. a PLC), while they are connected via two (or more) LAN interfaces.
    In praxis: between one PC with zenon and one device (PLC), each with two network adapters. 

    In the standard those alternative DL layer sessions are defined as "redundancy group connections" (BTW, not as "LAN group", this is probably some local - short so nice - naming in AK-driver). 
    The zenon iec870 driver supports 2 redundant connections, you can activate it in the driver configuration: device - settings: 'primary IP address', 'secondary IP address' and activate check-box 'redundancy according 60870-104 edition 2.0'.

    If you want that in zenon Network, the Server 1 and Server 2 are using different driver configurations, so the Server 1 communicates via another IP addresses of PLC as the Server 2, then you have to make sure the servers will not synchronize the driver configuration files. After you once configured and transferred via remote transport to the runtime PCs, you can - in project settings 'Remote Transport' - deactivate the check-box for transfer of files in \custom\drivers. BTW, the iec870 driver configuration files are text, the IP addresses are easy to find there.   

    Are you sure that those PLCs are supporting the DL layer redundancy strictly according the standard, e.g. general interrogation (GI) only on one DL, not after DL switch? I know from other customers moving projects from SICAM 230 to zenon, that they had to add manually trigger for additional GI after DL switch and had other issues because PLCs on disabled interface were  still responding the test procedure (so no way to automatically detect that zenon has to switch the DL) etc. 

      

  3. #3
    Join Date
    19.01.2017
    Posts
    12

    Default Re: Zenon Energy Edition IEC104 driver Redundancy According Edition 2 LANGROUPS

    Ok, thank you for your answer.

    I will try it as soon as I have both servers available.

    An additional question: do you know what the practical difference is between ticking or not ticking "Redundancy according to 60870-104 Edition 1"?  I can't find any explanation on it in the Help.

  4. #4
    Join Date
    01.07.2008
    Location
    Salzburg, AT
    Posts
    917

    Default Re: Zenon Energy Edition IEC104 driver Redundancy According Edition 2 LANGROUPS

    In zenon help you will not find copies of text of international standards.

    The IEC 60870-5-104 edition 2.0 redundancy, described very simplified, demands that on all N channels (e.g. via two Ethernet networks, N=2) the Data Link layer session is established (if physically possible) and the controlling station (master) chooses dynamically which one is the active channel; and the rest are passive channels, but are all the time open. Thus, the iec870 driver opens already at start two sessions - on both configured IP addresses. The stations are communicating the ASDU (data or command frames) only on active channel. By channel change there is no demand to re-send ASDUs which were acknowledged as received; so e.g. there is no re-send of the GI after switch to another DL channel if was once completed. The controlling station (master) informs controlled station (slave) which channel shall be the active one by sending DL frame STARTDT (and optionally STOPDT on passive DL channels). On all passive channels, as well controlling station as controlled are sending periodically the DL frames TESTFR - to check if passive DL is still healthy. This mode works only with controlled stations well supporting 104 redundancy.

    Without redundancy, the driver opens only one session (via one of configured IP addresses) and if this session fails (and only after also the re-connect tries fail) - then it opens on another IP. As sessions are independent, each open of the session results in new general interrogation procedure (GI). This mode works also with controlled stations (slaves) not supporting the 104 redundancy at all.

    IMHO, the concept of 104 redundancy was maybe nice in year 2003, but now, if I would had 2 Ethernet networks, I would rather use PRP protocol below "normal" 104 communication (to use fully "transparent", seamless redundant connection) as this much older concept introduced by IEC60870-5-104 making things more compilated, but not assuring seamless data and commands flow.

Similar Threads

  1. Load Management in zenon Energy Edition
    By Jose_Alejandro in forum zenon Energy Edition
    Replies: 1
    Last Post: 23rd April 2020, 07:40
  2. Zenon Energy Edition general and Cyber security query
    By jaimyg12 in forum zenon Supervisor
    Replies: 2
    Last Post: 9th December 2019, 13:33
  3. Zenon Energy Edition general and Cyber security query
    By jaimyg12 in forum zenon Energy Edition
    Replies: 0
    Last Post: 19th November 2019, 15:39
  4. Zenon energy edition 7.50 SP0 zendbsrv is not running
    By mehrdad6687 in forum Editor and Runtime Setup
    Replies: 2
    Last Post: 22nd December 2016, 14:45
  5. Zenon ENERGY Edition and Runtime
    By aladimurugan in forum zenon Energy Edition
    Replies: 3
    Last Post: 17th November 2015, 02:24

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
  •