Presentation of technology in automation

Development of application software

the controller and the operator panel

Technical task

NUMBER OF PROJECT

2015

---

ANNOTATION
This document contains the program and test procedure application
software for DC boards in the series production of the “Customer”, installed in power plants.
Technical description defines the technical requirements, steps and stages of development, composition operational documentation, as well as procedures for monitoring and acceptance of the program software for DC boards.

CONTENT

1. INTRODUCTION

1.1. Name Development

1.2. Application area

2. REASONS FOR THE DEVELOPMENT

2.1. Company name of the Contractor and its details

2.2. Name of the company and the customer details

2.3. The documents, based on which creates a program software

3. PURPOSE OF THE DEVELOPMENT

4. Requirements for the program

4.1. General requirements for software

4.1.1. Requirements for the software tools of the information panel

4.1.2. Requirements for application software PLC

4.1.3. Requirements for application software to obtain data on Modbus RTU

4.2. Requirements for the functional characteristics of PPO

4.2.1. General requirements

4.2.2. Requirements for displaying information and signaling

4.2.3. Requirements for archiving information

4.2.4. Requirements for speed

4.2.5. Requirements for diagnostics functions

4.3. The requirements for the composition and parameters of technical means

4.4. Requirements to information and software compatibility

4.5. Requirements for networking

5. REQUIREMENTS FOR DOCUMENTATION

5.1. The requirements for compliance with standards and regulations

5.2. Requirements to the documentation

6. STAGES OF THE DEVELOPMENT STAGE AND OPS

7. PROCEDURE FOR ACCEPTANCE AND CONTROL

7.1. Conducting preliminary tests

7.2. The sequence of start-up activities for each of the systems

7.3. The equipment that will be necessary for Poland, but is not part of the system components

ANNEX 1

Table IO system

LIST OF ABBREVIATIONS

 

---

1. INTRODUCTION

1.1. Name Development

Full name of development – development of application software

Software for DC boards.

The abbreviated name of development – PPO

1.2. Application area

Scope – modernization of DC boards

Shields DC designed to provide a DC power

emergency power systems, the diesel generator, obscheblochnoy

system, control systems protection system, an open distributed device,

systems ensure the safety of the main equipment, control

Computing Systems.

2. REASONS FOR THE DEVELOPMENT
PPR is developed on the basis of contract No 01.02.2015.
2.1. Company name of the Contractor and its details “Contractor”
Location address:
2.2. Name of the company and the customer details “Customer”
Legal address:
2.3. The documents, based on which creates to develop as input data are used
the following documents:

– Terms of Reference for the PP.
– ANNEX 1 Table IO system
– ANNEX 2 List of events
– APPENDIX 3 Block diagram
Contractor shall be entitled to request from the Customer other IDs not listed in this
list, the need for which may arise in the course of development.
3. PURPOSE OF THE DEVELOPMENT
PPO is a part of the system, which serves as the display and archiving
part of the system information from the signal input-output and output of messages
the operator of the events with a time stamp.
The aim is to ensure the work performed:
– Registration of the events on the boards DC depth of no more than
500 messages in a circular buffer;

– The formation of a warning or alarm in case of violation (current, voltage, insulation resistance) routine or emergency borders;

– Processing the input digital signals representative of the work and protection switchgear panels DC;

– Diagnostic hardware controller communication diagnostics hardware network CanOpen.

4. Requirements for the program

4.1. General requirements for software

Software should be developed in the tool environment and Unity XL v6.0 package
Vijeo-Designer Lite company Schneider Electric V1.3.
The structure of the software should include:
– The basic system software, hardware compatibility
means;
– PPO, which should be developed to implement the functions of control and
control of technological equipment.
PPO must be subdivided into PPO PPO PLC and operator panel.
All software products supplied by the developer of middleware for
enable support should have open source code. Developer should be delivered corresponding software (firmware) keys, providing the ability to support the software controllers and panels.

4.1.1. Requirements for software tools panel

providing information

4.1.1.1. Tool software panel should represent

a package of Vijeo-DesignerLite company Schneider Electric V1.3

4.1.1.2. Interfaces PC software should be performed in Russian.

4.1.1.3. Software panel must be adapted and

optimized to run on a particular object in view of the technological process.

4.1.1.4. Software panel should be intuitive and

have the following functions:
– Operating system of real vremenizh
– Output with the possibility of paging archived events;

– Displays the current state of the input signals and output to video frames.

4.1.2. Requirements for application software PLC

4.1.2.1. Software PLC should be developed using

tool system UNITY PRO XL version 6.0 or later, the company Schneider Electric in the languages ​​of the International Electrotechnical Commission standard IEC 61131-3.

4.1.2.2. Software PLC must be adapted and optimized to run on a particular object in view of the technological process. Feature Requirements algorithms implemented in applications PLC must be defined by this TK.

4.1.2.3. Software PLC must ensure the implementation of the following

features:

– Exchange of information on communication channels;

– I / O digital and analog channels;

– Data collection and management of lighting board;

– Configuration of system software for a specific object;

– Diagnosing software and hardware;

4.1.3. Requirements for Application Software for Data Modbus RTU

The software should allow, by the operator, to receive a the controller information in the form of a “section” (buffer exchange) as a file to 500 XLS rows of posts.

4.2.Requrements functional characteristics of program software

4.2.1. General requirements

4.2.1.1. PPO must provide the following functions:

– Control of process parameters (current, voltage, resistance,

insulation), the state switching devices;

– Conversion of units of measurement in the physical dimension;

– Smoothing (filtering) of measurements;

– Formation and issuing commands to the external light indication;

– Display the status of switching devices and process values

parameters in the form of mimic diagrams (single-line diagrams);

– Check the events: change of state switching devices,

violation of technological parameters of warning and alarm values;

4.2.1.2. It shall be possible to change the authorized values warning and alarm. Access to change these parameters should be limited on the basis of organizational measures (limited access to the premises).

4.2.2. Requirements for displaying information and signaling

Showing information organized in the form of video frames and tables, sufficient for the transmission of current and historical information.

In the body of the video frame have to be given the location of the displayed items, single-line diagram with symbols of the equipment.

Sheet output messages should carry information about the exact time and date

an event, a text description in Russian.

4.2.3. Requirements for archiving information

4.2.3.1. It shall be capable of conducting the following files:

– Archive of registered events in chronological order on the project

management and control system, up to 500 recent messages. Storing

messages to be formed as a circular buffer.

The archive must be recorded the following events:

– Violations of the technological parameters of warning and alarm limits;

– Fault protection devices and switching devices;

– Faults and failures in software and hardware systems scheduling.

4.2.4. Requirements for speed

4.2.4.1. The period of updating information on the panel reporting

shall be not more than 1 second.

4.2.4.2. The frequency of the survey parameters must match the cycle of the survey

and a controller to be not more than 200 ms.

4.2.5. Requirements for diagnostics functions

4.2.5.1. PPO must perform the following diagnostic functions:

– Check for an open or short circuit of sensors for current channels 4 … 20 mA;

– Validation (going beyond the measuring range);

– Diagnostics of network connections on the bus CanOpen checking for open communication.

4.3.Trebovaniya to the composition and parameters of technical means

CPUs must be of type BMXP3420302. The composition of the IO moduls is listed in Annex 9 and 10 of this Terms of Reference.

4.4.Rrequrements to information and software compatibility of current board should be built in a modular fashion, which ensures autonomous creation of separate program modules (PM) on the basis of the standard
library of function blocks (FB) toolkit Unity Pro XL V.6.
Interaction of operational staff with the software must be on an external (user) level interface without support and maintenance programs.
4.5.Trebovaniya to networking
4.5.1.1. Interaction Network Level Ethernet TCP / IP
The system should provide the ability to retrieve the current state of signals
IO in a secure enterprise network. Addresses and addresses of network devices
variables specified during commissioning.

4.5.1.2. Interaction on the level of a Modbus RTU network

Customer will be sent an application that allows you to receive data from the ring buffer, and view messages in the format of MS OFFICE EXCEL. Customer will need to provide your computer with pre-installed Windows XP SP3.

5.1. The requirements for compliance with standards and regulations

Development and documentation PPO should be in accordance with the requirements of:

– ESPD standards;

Documentation should be designed for the following series of direct-current boards – 4EA, 4EB, 4EC and 4ED separately.

5.2. Requirements to the documentation

The software documentation should include the following program softwere documentation:

– Terms of Reference for the development of the TCO.

– Specification.

– Program description.

– Operator’s Manual.

– Programmer’s Guide.

– Program and methods of testing at the site of the Contractor.

– Program and methods of acceptance tests at the site of operation ().

6. STAGES OF THE DEVELOPMENT STAGE AND OPS

In developing the middleware must be carried out the following work:

-Development And the harmonization of technical requirements on development of middleware shields direct current.

-Correction of Software in accordance with the requirements of this specification.
-Development Of technical documentation in accordance with the Schedule (Table 6.1).
Carrying out of preliminary tests of PPO at the site of the Contractor to
using a software simulator of the lower level signals.
The planned schedule of work is given in Table 6.1.
Table 6.1 – The planned schedule of works

7.1. Conducting preliminary tests

The purpose of preliminary tests PPO is testing for compliance

the present terms of reference. Tests are carried out according to the procedure of acceptance tests.

Preliminary tests should be carried out by PPO agreed

Software + methodology and acceptance test (MIT) at the stand of the Contractor

If unsatisfactory results of preliminary tests

The Contractor shall carry out analysis of the causes of reported faults, take

the necessary measures to eliminate them. Repeated preliminary testing allowed

carry only those claims for which were obtained unsatisfactory

results.

By preliminary tests should be submitted to:

– PPO;

– Program and methods of testing.

Acceptance by the Commission, which includes representatives

Customer and the Contractor.

As a result of the acceptance act is signed by preliminary tests.

7.2. The sequence of start-up activities for each

Systems of

– Download new system software (firmware) to ensure

hardware compatibility;

– Checking and adjustment of the PPO in the field of reception of signals on the bus

CanOpen. Adjusting tire CanOpen;

– Download the PPO to the system controller;

– Download PPO panel visualization;

– Setting up and removal of the deficiencies identified.

7.3. The equipment that will be necessary for Poland, but that does not

a part of the components of the system

Personal portable computer with the operating system

Windows XP SP3, as well as the office package MS OFFICE 2007 (10).

ANNEX 1

Input-output tables for the 4EA System

 

 

 

 

ANNEX 5

HMI design 4EA

HMI screen #1 «The navigation bar»

HMI screen #2 «The list of violations»

HMI screen #3 «4EAN01_1»

HMI screen #4 «4EAN01_2»

HMI screen #5 «4EAN01_3»

HMI screen #6 «4EAN02»

HMI screen #7 «4EAN03»

HMI screen #8 «4EAN04»

HMI screen #9 «4EAN05_1»

HMI screen #10 «4EAN05_2»

HMI screen #11 «4EAN05_3»

HMI screen #12 «Setpoint V_ED_4EA»

HMI screen #13 «Setpoint IS_ED_4EA»

HMI screen #14 «Setpoint I_4EE01»

HMI screen #15 «Setpoint I_4EQ01»

HMI screen #16 «Setpoint V_ES_4ED»

HMI screen #17 «Time controller setpoints»

HMI screen #18 «Enter the value from the screen»

ANNEX 6

HMI design 4ED

HMI screen #1 «The navigation bar»

HMI screen #2 «The list of violations»

HMI screen #3 «4EDN01_1»

HMI screen #4 «4EDN01_2»

HMI screen #5 «4EDN01_3»

HMI screen #6 «4EDN02_1»

HMI screen #7 «4EDN02_2»

HMI screen #8 «4EDN02_3»

HMI screen #9 «4EDN03»

HMI screen #10 «4EDN04»

HMI screen #11 «4EDN05»

HMI screen #12 «4EDN06»

HMI screen #13 «4EDN07»

HMI screen #14 «4EDN08»

HMI screen #15 «4EDN09»

HMI screen #16 «4EDN10_1»

HMI screen #17 «4EDN10_2»

HMI screen #18 «4EDN10_3»

HMI screen #19 «4EDN11_1»

HMI screen #20 «4EDN11_2»

HMI screen #21 «4EDN11_3»

HMI screen #22 «Setpoints – V_ED1_4ED»

HMI screen #23 «Setpoints – IS_ED_4ED»

HMI screen #24 «Setpoints – I_4EE04»

HMI screen #25 «Setpoints – I_4EQ04»

HMI screen #26 «Setpoints – V_ES1_4ED»

HMI screen #27 «Setpoints – V_ED2_4ED»

HMI screen #28 «Setpoints – V_ES2_4ED»

HMI screen #29 «Changing the PLC»

HMI screen #30 «Enter the value from the screen»

ANNEX 7

The list of events for the 4EA

70	Авар откл˽	4ЕР01-А-˽˽
71	Неисправн˽	˽˽˽˽˽˽˽˽˽˽
72	Авар откл˽	4ЕР11-А-˽˽
73	Неисправн˽	˽˽˽˽˽˽˽˽˽˽
74	˽˽˽˽˽˽˽˽˽˽	Spare˽˽˽˽˽
75	˽˽˽˽˽˽˽˽˽˽	Spare˽˽˽˽˽
76	˽˽˽˽˽˽˽˽˽˽	Spare˽˽˽˽˽
77	˽˽˽˽˽˽˽˽˽˽	Spare˽˽˽˽˽
78	˽˽˽˽˽˽˽˽˽˽	Spare˽˽˽˽˽
79	Неисправн˽	конG10/G20

ПРИЛОЖЕНИЕ 10

Структурная схема 4ED

#Technical, #description, #defines,#steps,#stages,#development, #composition, #operational, #documentation,#boards

Russian version