The basic principles of the MK VI control Subject:

Control Page
Logics 5.1

Blz.
Sequencing 5.3
Blockware 5.4
Libraries 5.5
 The basic principles of the MK VI control Subject:
Control Page
Logics 5.2

Intentionally left blank

 Sequencing Subject:
Control Page
Logics 5.3

The mark VI primary features are:

•
•User friendly Windows-based common tools across product offerings
•EGD support to pass data to Cimplicity HMI over ethernet
•Sequencing, math calculations, and regulators
•Floating point math calculations
•On-line software changes
•Automatic diagnostic message generation
•Forcing of I/O and internal signals
•Controlled order of execution
•Nonvolatile Flash memory for product software

Mark VI Configuration:

Control functions are implemented in the form of blockware

Some function blocks are:

Boolean Engine, Math Engine, Clamp, Compare, Filter, Linear Interpolator, Select,
Pulse, Timer, and Latch.

The function blocks are the fundamental elements of which process control is built

Blockware is configured via GE Control Systems ToolBox.

Macros and modules are supported by the configuration.

Configuration is built & compiled then downloaded to the UCVx

 Blockware Subject:
Control Page
Logics 5.4

Control Blockware

The Mark VI software is made up of units of information known as blocks

The Mark VI control blockware is organized hierarchically into layers
Functions are made up of modules.
Module are made up of tasks.
Tasks are made up of blocks and macros.
Macros are made up of blocks.
Blocks are the smallest programming element. They can perform math, solve a
Boolean equation, perform a filter, and such. (These blocks can be compared to
C-language functions.)

Blockware Structure

For the purpose of scheduling

Modules (period, skew)
Tasks (period mult., skew offset)

For the purpose of logical structuring

Blocks
Macros
Tasks
Modules
Functions

Macros

The macro allows the user to create a higher functionality block out of blocks and other macros
A macro is a mechanism by which control code is structured for reuse
Each macro may be instanced (reused) multiple times within a module

Tasks
Tasks contain multiple strings of blocks that may be scheduled to execute periodically
All of the external inputs required by a task are automatically collected just prior to its execution
These inputs are frozen for the duration of the sweep
All of the external outputs are automatically driven at the end of the sweep
The automatic collection and dispersion of I/O may be overridden for testing and/or simulation.

Modules

Modules contain multiple tasks and are the blockware elements that compose the fundamental
unit for application code configuration
Modules can be added, deleted, or modified on-line
Modules provide a place to specify the base scheduler period, offset and order of execution for a
group of tasks

Functions

Functions exist at the highest level

They contain modules and have no runtime effects

See for
additional info Geh-6402 chapter 3 Blockware concepts
 Subject:
Libraries
Control Page
Logics 5.5

There are 3 types of Libraries.

1) Hardware Modules Libraries

This contains all software needed to configure the I/O cards

2) Block Libraries.

SBLIB De standard mark VI platform blocks

TURBLIB De standard Turbine group library

3) Macro en Module Libraries

Here are all the usable macro’s en modules for the application