WinCC OA tutorial. Part 1. Creating a project and the para module

I decided to tell a little about the visualization system from Siemens called WinCC OA. This SCADA is much less widespread on the Russian market than the classic versions of WinCC (and tia-portal ones too), there is little knowledge about it in the public domain, knowledge is shared reluctantly. In some respects, WinCC OA is radically different from conventional SCADA systems, so first you need to learn the basics.

Before assimilating this basis, I recommend that you familiarize yourself in general with the WinCC OA build architecture. The best way to do this is to find recordings of webinars and speeches by Andrey Kondrashkin, WinCC OA expert, on the Internet. Andrey Gennadievich is a very powerful specialist and an excellent speaker. This cycle of notes, in fact, is based on his two-day introductory training. I recommend this post .

You can go deeper into the study of the issue and further, for example - get acquainted with the SmartSCADA or Preactor add-ons, but this goes very far beyond the basic understanding of the system. The most important thing to take away from this video is an understanding of the WinCC OA architecture. For example, the fact that the system consists of separate complete functional units, which are called "managers". The manager performs his strictly assigned role. At the heart of the entire system is the event manager (EV). There is a visualization manager, User Interface or ui. There are drivers, for example - s7. There is a script manager, control. All managers communicate with each other via the central EV using the standard TCP / IP protocol, regardless of whether they are located on one physical PC, or spaced across several.

The second important distinguishing feature that needs to be understood. OA is an event-driven system. It has almost no constant polling of data. The readings on the operator's screen will change only if the value of the corresponding variable in the controller changes.

Third. All or almost everything is implemented by scripts ("What cannot be programmed in Assembler, you can solder" (c)) and text files. Need to light a mimic light? Script. Moreover, a script that is tied to a change in a variable and performs certain actions only on this change automatically.

, . . , , . , , 1 . . , , 3, 4 TIA Portal, . , , , , — . , . - . S7plus , -.

tips & tricks . , «». — , . , winccoa, . , — TCP, «» WinCC OA, . .

. — . . — 30 (ui) . WinCC OA ( «para» «gedi» ) , «». — 30 . 30 . 10 , ui , 30 , 20. , , , .

, . . , — . , - , — « ». WinCC OA , . , , WinCC OA C:\Siemens\Automation\WinCC_OA\3.16\config\config

, WinCC OA.

:

[general]
pvss_path ="C:\Siemens\Automation\WinCC_OA\3.16\"
proj_path ="C:\Siemens\Automation\WinCC_OA\3.16\"
proj_version = "3.16"
langs = "en_US.utf8"
langs = "de_AT.utf8"
langs = "ru_RU.utf8"
lang = "auto"

lang = «auto» lang = «ru_RU.utf8», .

[general]
pvss_path ="C:\Siemens\Automation\WinCC_OA\3.16\"
proj_path ="C:\Siemens\Automation\WinCC_OA\3.16\"
proj_version = "3.16"
langs = "en_US.utf8"
langs = "de_AT.utf8"
langs = "ru_RU.utf8"
#lang = "auto"
lang = "ru_RU.utf8"

# ( — ) lang, lang, :

— « »

. WinCC OA Project Administrator.

- , hardware code , shield-file. «Get hardware code».

. «New project». 3.17, Legacy Standart Project.

New project in series 3.16
3.16

.

. Runnable () . 3.17 "Use NextGenArchiver", , " ", , " ". . , . WinCC OA . .

(root). , , , .

.

, - . ( ) «Change project properties», «Edit config file» .

Editing a project
Selecting the project config file
-
Editing the project config

. . - . - . . .

. , . root' . , . gedi, WinCC OA Console

. : , , , . , .

Process Monitor. ( Event Manager). pmon WinCC OA, , , , , .

Database Manager . Archive Manager (6 ) WinCC OA . , . , , -num .

Control Manager. — , . , , ( ).

— ui gedi, .

. .

, ui, 0 () ( , ). 1 — , 2 — , 3 — . , , , , .

gedi ( — gedi ) para

In the gedi editor, press the button highlighted in the screenshot
gedi ,
Para data editing module
para

Para . , data point type — , (data point) . , WinCC OA. — , .

, , (, ..), ( , , ). ? , , /, ( /) ..

Create data point type
Declare data point type name

DPT (data point type) — Flap. Add node .

Specify data point type structure

Type detailing

. (inputs) — (Position) (Flow), (Commands) — (Open) (Close), — (Torque). , ( ) . Position Flow , Open, Close Torque — . :

Assigning variable types to structure "leaves"
""
Final View of Flap Data Point Type
Flap

Position Flow — int, — bool. Flap ( , DP, DPT).

Data point type created

Flap , , «Create datapoint»

Create data point of type Flap
Flap
Specify data point name

. DP: Flap1, Flap2 Flap3.

Three DPs created
DP

DP Flap1

Expanded view of DP Flap1 in para module
DP Flap1 para

, , . : _original, _common _lock. WinCC OA . - . DPE (datapoint element) .

Original config for data point item
original

original — DPE. DPE . 0, 01.01.1970. unix time, 1970 . Flap1.Inputs.Position.original para

Setting a value for DPE
DPE

, , , . (variable bits). 5 6 ( , ), .

, Original Value ( DPE — , ), Online Value — . . Original — , , , « », Online — . ? , . , 12, , — 10, Online = 10 .

DPE Position (Flap1) , , .

Adding config to DPE
DPE

Archive settings .

Alert settings — .

Periphery address — OPC- . DPE . , — DPE, « ».

Command conversion Message conversion — «» ( , — , ..) .

Default value Value Range — , .

Smoothing — . . , (polling) . , (, s7 100 10 ), EV. ( ) ? , . , , . , «/».

Authorization —

Datapoint function — . . Datapoint function DPE Flap3.Inputs.Position

_dp_fct, Configure

Click "Configure"
"Configure"
Call the data point selection window for the first parameter
Select Flap1.Inputs.Position as the first parameter
Flap1.Inputs.Position
Add parameter to list
The parameter p1 is now set
p1

. ( Flap1 Flap2 «p..=») .

«Function» "p1 + p2"

.. . _original DPE Flap3.Inputs.Position

, , Flap1 10 ( ), Flap2 10, 0 + 10 = 10.

, , DPE , DPT ( ). — ? , , ? — . . — Master Datapoint. , . , , . — , DP Excel .




All Articles