PVIS Systemdescription

PVIS
User software
System Description – Item No. 21 697-03

All rights to this documentation are reserved by Pilz GmbH & Co. KG. Copies may be made
for internal purposes.
Suggestions and comments for improving this documentation will be gratefully received.
The names of products, goods and technologies used in this documentation are registered
trademarks of the respective companies. Automation Workbench®, Pilz®, PIT®, PMI®,
PNOZ®, Primo®, PSS®, SafetyBUS p® are registered trademarks of Pilz GmbH & Co. KG.
Contents
Contents
Contents Page
Chapter 1 Introduction
1.1 Validity of documentation 1-1
1.2 Overview of documentation 1-2
Chapter 2 Diagnostics and visualisation with PVIS

2.1 Aim of diagnostics and visualisation 2-1
2.2 Overview of the procedure 2-2
2.3 Supported hardware and software 2-4
Chapter 3 PVIS diagnostic configuration

3.1 Introduction 3-1
3.2 Event messages and remedy 3-3
3.2.1 Priorities 3-5
3.2.2 Scopes 3-6
3.2.3 Responsibilities 3-7
3.2.4 Event list 3-8
3.3 Device's diagnostic configuration 3-9
3.4 Diagnostic configuration for safety devices 3-10
3.4.1 Copies 3-10
3.4.2 PSS only: Instances 3-11
3.5 Diagnostic configuration of operands 3-13
3.5.1 Bit diagnostic type 3-13
3.5.2 PSS only: "Word" diagnostic type 3-13
Chapter 4 PVIS OPC Server

4.1 Function of the PVIS OPC Server 4-1
4.2 Install PVIS OPC Server 4-2
4.2.1 System requirements 4-2
4.2.2 Licencing 4-2
4.2.3 Installation on a PC 4-3
4.2.4 Installation on a PMIvisu/PMIopen 4-5
4.3 Install PVIS OPC Configurator 4-8
4.4 Communication and security settings 4-9
4.4.1 DCOM configuration under Windows 2000 4-10
4.4.1.1 DCOM configuration on all PCs 4-10
4.4.1.2 DCOM configuration on the PC with the 4-13
PVIS OPC Server
4.4.2 DCOM configuration under Windows XP 4-23
4.4.2.1 DCOM configuration on all PCs 4-23
4.4.2.2 DCOM configuration on the PC with the 4-30
PVIS OPC Server
4.4.3 Enabling access rights under Windows 4-38
Vista
Pilz GmbH & Co. KG, Felix-Wankel-Straße 2, 73760 Ostfildern, Germany

1
Telephone: +49 711 3409-0, Telefax: +49 711 3409-133, E-Mail: pilz.gmbh@pilz.de
Contents
4.4.4 Firewalls and security settings 4-39

4.5 PVIS OPC project 4-40
4.5.1 Structure of a PVIS OPC project 4-40
4.5.2 Language management 4-41
4.6 Event view 4-43
4.7 Commissioning the PVIS OPC Server 4-44
Chapter 5 PVIS ActiveX Control

5.1 Function of the PVIS ActiveX Control 5-1
5.2 Install PVIS ActiveX Control 5-2
5.2.1 Installation on a PC 5-2
5.2.2 Installation on a PMIvisu/PMIopen 5-2
5.3 Configure PVIS ActiveX Control 5-4
5.4 Operate PVIS ActiveX Control 5-7
5.4.1 Split window 5-7
5.4.2 Single window 5-9
5.4.3 Event log 5-11
5.4.4 Information window 5-12
5.4.5 Icons 5-12
5.4.6 Filtering 5-13
5.5 Start PVIS ActiveX Control in the browser 5-15
Chapter 6 Namespace
6.1 Basics 6-1
6.1.1 Definition of symbols 6-1
6.2 Structure of the namespace 6-2
6.2.1 OPCProjectName 6-2
6.2.2 SummaryInformation 6-3
6.2.3 OverviewInformation 6-5
6.2.4 CentralDevices 6-6
6.2.5 PSS: SafetyBUSp 6-7
6.2.6 PSS: Interfaces 6-8
6.2.7 PSS: IOGroups 6-9
6.2.8 PSS: Subscribers 6-10
6.2.9 SafetyDevices 6-11
6.2.10 Operands 6-12
6.2.11 DetailInformation 6-13
6.2.12 EventList 6-14
6.2.13 Actions 6-16
6.2.14 SystemInfo 6-17
6.2.15 PNOZ: PNOZmultiProject 6-18
6.2.16 PNOZ: DiagnosticConfig 6-19
6.2.17 PSS: DiagnosticConfig 6-20
6.2.18 PSS: FSProgram 6-22
6.2.19 Generic process data access 6-23

2
Contents
6.2.20 PNOZ: Generic 6-24

6.2.21 PSS: Generic/FS and Generic/ST 6-25
6.2.22 PSS: Generic/FS 6-26
6.2.23 PSS: Symbolic process data access 6-28
6.2.24 EventLog 6-29
6.2.25 Licence and versions 6-31
Chapter 7 Applications
7.1 PSS diagnostics on a PMImicro diag 7-1
7.1.1 Create diagnostic configuration 7-1
7.1.2 Download the diagnostic configuration to 7-2
the PSS
the PMImicro diag
7.2 PNOZmulti diagnostics on a PMImicro 7-3
diag
7.2.1 Create diagnostic configuration 7-3
the PNOZmulti
the PMImicro diag

3
Contents

4
1 Introduction
1.1 Validity of documentation
1000 of documentation
1.1
Introduction
Validity
1100
1-
This operating manual describes expanded PVIS diagnostics for all

PVIS-compatible control systems from PILZ.
This operating manual is valid for:

` PVIS OPC Server from Version 1.4.0
` PVIS ActiveX Control from Version 1.4.0
` PVIS OPC Configurator from Version 1.4.0
It is valid until new documentation is published.
This documentation is intended for instruction and should be retained

for future reference.

1-1
1 Introduction
1.2 Overview of documentation
1.2
Overview
1200
1- of documentation
1 Introduction
The introduction is designed to familiarise you with the contents and

structure of this system description.
2 Diagnostics and visualisation with PVIS
This chapter explains the objective of expanded PVIS diagnostics and

the mode of operation.
3 PVIS diagnostic configuration
This chapter describes the components of the PVIS diagnostic configu-

ration.
4 PVIS OPC Server
This chapter describes the function and application of the PVIS OPC
Server.
5 PVIS ActiveX Control
This chapter describes how to run diagnostics with a PVIS ActiveX Con-
trol.
6 Namespace
This chapter illustrates the structure and contents of the namespace in

which the diagnostic data and visualisation data are stored.
7 Examples
This chapter contains check lists for how to create a diagnostic config-
uration and download it to the diagnostic unit.

1-2
2.1 Aim of diagnostics and visualisation
2000of diagnostics
Diagnostics
2.1
Aim
2100
2- and visualisation
and visualisation
with PVIS
PVIS is a concept for expanded diagnostics. What does PVIS expanded

diagnostics intend to achieve?
` PVIS minimises machine downtimes by rectifying errors quickly and
efficiently.
How is this achieved?

` Detailed plain text messages are available for each event.
` Location information as plain text or as an Equip ID (equipment iden-
tifier) shows where a problem lies.
` Priorities highlight the events which require an immediate reaction.
` Responsibilities tell you who can rectify the problem.
` The remedy provides a step-by-step solution.
` Only current messages are displayed.
` PVIS distinguishes between a first fault and subsequent faults. Only
first faults are displayed.
` Users can modify and adapt default messages.
` The PVIS OPC Server provides a standardised interface to visualisa-
tion systems.

2-1
2.2 Overview of the procedure
2.2
Overview
2200
2- of the procedure
Diagnostic configurations can be created for all PVIS-compatible control

systems. This is done using the specific system software for the control
system, e.g. using PSS WIN-PRO or the PNOZmulti Configurator.
The diagnostic configuration contains event messages, which can be

displayed when there are faults in or on the control system, when the op-
erating status of the control system changes or when safety devices
have a defined status, for example.
The diagnostic configuration can be processed directly by a PVIS-com-

patible display unit such as the PMI m107 diag. To do this, the diagnos-
tic configuration is downloaded to the control system and display unit,
and the display unit is then connected to the control system (see illus-
tration: Diagnostics without PVIS OPC Server).
PVIS-compatible
Control system display unit
Diagnostic configuration Diagnostic configuration
Fig. 2-1: Diagnostics without PVIS OPC Server
The PVIS OPC Server is used to display event messages on a visualisa-

tion device. The PVIS OPC Server is installed on a PC, PMIvisu or PMI-
open. The PVIS OPC Configurator is used to create an OPC project; this
contains the diagnostic configurations and the OPC data for the sepa-
rate control systems.
The PVIS OPC Server establishes a connection to the control systems,

reads in the data and makes it available within the namespace. Not only
can the event messages be called up within the namespace but also sta-
tus information and process data from the control systems (see illustra-
tion: Diagnostics with PVIS OPC Server).
PVIS ActiveX Control can be used to call up a control system's event

messages from the PVIS OPC Server and display them in a graphics
software package.

2-2
2.2 Overview of the procedure
Graphics software/
Control system PMI-PRO/PMI-PROopen
Diagnostic configuration With/without

PVIS ActiveX Control
Graphics software/
Control system PVIS OPC Server PMI-PRO/PMI-PROopen
Diagnostic configuration Namespace With/without

(Diagnostic configuration, PVIS ActiveX Control
process data)
Graphics software/
Control system PMI-PRO/PMI-PROopen
Diagnostic configuration
With/without
Fig. 2-2: Diagnostics with PVIS OPC Server and several Clients for
visualisation

2-3
2.3 Supported hardware and software
2.3
Supported
2300
2- hardware and software
The functions of the PVIS expanded diagnostics are supported by the

control systems, system software and display or visualisation devices as
follows:
Diagnostics on the PSS using PMImicro diag:

` PSS from operating system version 47
` PSS WIN-PRO from Version 1.4.0
` PMI m107 diag from Version 1.0
Diagnostics on the PNOZmulti using PMImicro diag:

` PNOZmulti base units from the following versions:
– PNOZ m0p from Version 2.0
` PNOZmulti Configurator from Version 5.0.0
Diagnostics on the PNOZmulti using the PVIS OPC Server:

` PNOZmulti base units from the following versions:
` PVIS OPC Server from Version 1.4.0
` PVIS ActiveX Control from Version 1.4.0
` PVIS OPC Configurator from Version 1.4.0
Diagnostics on the PSS using the PVIS OPC Server:

` When only the event list is to be displayed:
– PSS from operating system version 53
– PSS WIN-PRO from Version 1.4.0
– PVIS OPC Server from Version 1.3.0
– PVIS ActiveX Control from Version 1.3.0
– PVIS OPC Configurator from Version 1.3.0
` When the event list is to be displayed, summary information and de-
tailed information is to be available to call up and access to generic
and symbolic process data is to be available:
– PSS from operating system version 53
– PVIS OPC Server from Version 1.4.0
– PVIS ActiveX Control from Version 1.4.0
– PVIS OPC Configurator from Version 1.4.0

2-4
Diagnostic configurations that have been created for the PMImicro diag
can also be used for the PVIS OPC Server.

2-5

2-6
3.1 Introduction
3000 diagnostic configuration

PVIS
3100
Introduction
3.1
3-
The diagnostic configuration contains all the information required for ex-
panded diagnostics. The diagnostic configuration enables event mes-
sages to be displayed in the case of:
` Errors in or on the control system
` Changes in the operating status of the control system
` Defined status conditions of safety devices
– PSS: MBS blocks
– PNOZmulti: Elements
` PSS: Defined status conditions of inputs, outputs and flags
` PSS: Errors in or on the SafetyBUS p bus subscribers
` PSS: Changes in the operating status of the I/O-Groups on SafetyBUS
p
` PNOZmulti: Defined status conditions of diagnostic points (inputs,
outputs and connection points)
The control system's event messages can also be supplemented

through additional information, which is helpful during diagnostics.
With expanded diagnostics, a diagnostic unit (e.g. the PMImicro diag or

PVIS OPC Server) is connected to the control system. If an event occurs
in or on the control system, an event telegram is sent to the diagnostic
unit. The event telegram is evaluated within the diagnostic unit, i.e. a de-
cision is made as to whether the corresponding event message should
be displayed and entered in the event list. The event message contains
a description of the event. A remedy can be displayed for each event
message. The remedy describes how to react to the event. The remedy
contains a maximum of 8 steps, the so-called "Actions".
The diagnostic configuration consists of three independent parts:

` Device's diagnostic configuration
Contains the event messages which are output if an error occurs in or
on the control system or if there is a change in the operating status of
the control system
` Diagnostic configuration for safety devices
Contains the event messages that are triggered when safety devices
have a defined status
` Operand's diagnostic configuration
– PSS: Contains the event messages that are output when inputs, out-
puts and flags have a defined status
– PNOZmulti: Contains the event messages that are output when in-
puts, outputs and connection points have a defined status
The diagnostic configuration is project-related, i.e. a separate diagnostic

configuration is created for each PNOZmulti or PSS project.

3-1
3.1 Introduction
The diagnostic configuration is downloaded to the control system and

to the diagnostic unit. The whole diagnostic configuration is not down-
loaded, just the data that the control system and diagnostic unit require
from the diagnostic configuration. The device's diagnostic configuration
is not downloaded to the control system at all, because it is part of the
controller's operating system.
Diagnostic configuration
Device Control system

diagnostic
configuration
Diagnostic
configuration
for safety
devices
Operands Diagnostic unit

diagnostic
configuration
Fig. 3-3: Download diagnostic configuration

3-2
3.2 Event messages and remedy
3.2 messages and remedy

Event
3200
3-
If an event occurs in or on the diagnosed control system, the corre-

sponding event message is displayed. The event message contains a
description of the event. A remedy can be displayed for each event mes-
sage. The remedy describes how to react to the event. The remedy con-
tains a maximum of 8 steps, the so-called "Actions".
Event message components

` Priority
Importance of the event message
` Scope
Approximate classification of the event message
` Description of event
Description of what happened
` Location information
Information on where the event occurred.
The location information may consist of the following details:
– Device
Name of device/module, details of the faulty object (e.g. PSS config-
uration), type of safety device (e.g. safety gate) or information on the
operand (e.g. reset input)
– Equip ID
Equipment identifier of the device/module or symbolic name of the
safety device or operand
– Address
More precise information on where the error occurred on a device,
e.g. information on the terminals
– Location description
Text description of the location, e.g. specification of the control cab-
inet in which the device is located.
Action components
` Scope
Approximate classification of the action
` Responsibility
Information on who should undertake the action.
` Description of action
Description of what has to be done.
` Location information
Information on where the action is to be undertaken.
The location information may consist of the following details:
– Device
Name of device/module, information on a program section (e.g. PSS

3-3
configuration), type of safety device (e.g. safety gate) or information

on an operand (e.g. reset input)
– Equip ID
Equipment identifier of the device/module or symbolic name of the
safety device or operand
– Address
More precise information on where the action is required on a de-
vice, e.g. information on the terminals
Text description of the location, e.g. specification of the control cab-
inet in which the device is located.
– Image 1 and image 2
Images of the device, safety device or operand, for the event and the
remedy respectively
If two images are stored, these two images alternate on the display
approximately every 1.5 s.
The images are only used if the Pilz PVIS ActiveX Control is used for
diagnostics or if the images are accessed in the namespace of the
PVIS OPC Server.

3-4
3.2.1 Priorities
3-
Priorities
Each event message is assigned a priority, which describes the impor-

tance of an event message. 15 priorities can be defined. Of these, prior-
ity 3 “Error”, priority 8 “Warning” and priority 13 “Status information” are
pre-defined by Pilz.
You can change the name of the pre-defined priorities but you cannot
delete them.
Priority 1 is the highest priority and priority 15 the lowest.
The 15 priorities are divided into three priority classes:

` Error
This priority class contains event messages to which the user must re-
act immediately. These event messages provide information on the
status of a technical device on which functions have failed or are com-
promised.
The "Error" priority class includes the pre-defined priority, "Error".
` Warning
This priority class contains event messages which demand the user's
attention. These event messages warn the user about a potential or
imminent critical machine status.
The "Warning" priority class includes the pre-defined priority, "Warn-
ing".
` Status information
This priority class contains event messages which describe the cur-
rent status of the process and/or machine. These event messages are
provided for information; the production cycle is neither impeded nor
compromised.
The "Status information" priority class includes the pre-defined priori-
ty, "Status information".

3-5
Priority class Priority Name of the priority

Error 1
2
3 Error
4
5
Warning 6
7
8 Warning
9
10
Status information 11
12
13 Status information
14
15
3.2.2 Scopes
3-
Scopes
Each event message and each action can be assigned a scope. The
scope roughly describes the type of event/action.
15 scopes can be defined. Pilz has predefined three scopes, but these
can be changed.
Pre-defined scopes:
` Plant/device
Affects the mechanics, electrics, electronics or software.
Examples: Defective device, periphery error (e.g. wiring, actuator/sen-
sor or supply voltage is faulty), project configuration error (e.g. PNOZ-
multi configuration, PSS configuration or user program is faulty), bus
error (e.g. error on SafetyBUS p or on the standard fieldbus)
` Process
Affects sequence or operation.
Examples: Sequence error (cylinder fails to reach an end position),
safety device was triggered (e.g. E-STOP operated)
` Communication
Data transfer between the control system and diagnostic device is dis-
rupted.
` ---
No details of the scope are possible or necessary.

3-6
3.2.3 Responsibilities
3-
Responsibilities
An area of responsibility can be assigned to each action. The responsi-

bility stands for the person or group who is supposed to perform an ac-
tion.
Some responsibilities are pre-defined by Pilz and a maximum of 15 re-

sponsibilities can be defined by the user. The user can change the name
of the pre-defined responsibilities, but cannot delete them.
Pre-defined responsibilities:
` Safety device
This action involves the release, actuation or operation of a safety de-
vice.
Responsible person: Plant operator, for example
` Periphery
This action refers to the mechanics/electrics/ electronics outside the
Pilz devices, e.g. rectify short circuit, check supply voltage, check
switch contacts.
Responsible person: Maintenance engineer, for example
` Device malfunction
This action refers directly to an error within the device, e.g. check de-
vice, swap device.
Responsible person: Maintenance engineer, for example
` Project configuration
This action can only be performed using the programming device
(PSS) or PNOZmulti Configurator (PNOZmulti), or requires some pro-
gramming knowledge, e.g. check or adapt configuration, check or
adapt programming.
Responsible person: Maintenance engineer, programmer, project en-
gineer, for example
` Bus
This action can be performed where there is technical understanding
of SafetyBUS p/the fieldbus, e.g. check bus load, check cable runs.
Responsible person: Maintenance engineer, bus specialist, for exam-
ple
` Sequence
The process sequence was wrong and must be corrected.
Responsible person: Operator, maintenance engineer, programmer,
project engineer, for example
` ---
No details of responsibility are possible or necessary.

3-7
3.2.4 Event list

Event list
3-
The event list is shown on the diagnostic unit. The diagnostic unit re-
ceives the event telegrams from the diagnosed control system. Each
event telegram is checked to see whether the corresponding event mes-
sage needs to be displayed and entered in the event list. For example, if
it relates to an event occurring as the result of a previous event, the
event telegram will be ignored.
A check is also made to see whether the user requires further informa-
tion on an event. For example, if the PSS registers that an I/O-Group on
SafetyBUS p has stopped, the diagnostic unit calls up the error stack of
the device that triggered the stop, displays the relevant event messages
and enters them in the event list.
Event messages are deleted from the event list as soon as the cause of
the fault has been rectified.
The event list is substantially different from the error stack on the PNOZ-
multi and PSS. The error stack simply lists all events in the order in which
they occurred.

3-8
3.3 Device's diagnostic configuration
3.3
Device's
3300
3- diagnostic configuration
The device's diagnostic configuration contains the event messages

which are output if an error occurs in or on the diagnosed control system
or if there is a change in the operating status of the diagnosed control
system.
The device's diagnostic configuration is supplied by Pilz in full and can-

not be modified by the user.

3-9
3.4 Diagnostic configuration for safety devices
3.4
Diagnostic
3400
3- configuration for safety devices
The diagnostic configuration for safety devices contains the event mes-
sages that are triggered when safety devices have a defined status.
Safety devices are:

` PSS:
– MBS blocks
– Input devices that are monitored by MBS blocks
` PNOZmulti:
– Elements
– Input devices that are monitored by function elements
Pilz has a pre-defined "Safety Device" diagnostic type for each standard
safety device. The diagnostic type contains an event message, including
remedy, for every potential safety device status, i.e. for each event. Us-
ers cannot modify the Pilz pre-defined diagnostic types for safety devic-
es. However, copies may be created for individual adaptation. On the
PSS it is also possible to create instances. Copies or instances may be
edited to a limited extent.
3.4.1 Copies
3-
Copies
Copies of a "Safety device" diagnostic type enable the event message

and remedies to be adapted, should an MBS block or function element
be used for an alternative purpose, e.g.:
` PSS: The MBS block SB060 "E-STOP" is not to be used to monitor an
E-STOP pushbutton but to monitor an end switch.
` PNOZmulti: The function element "E-STOP" is not to be used to mon-
itor an E-STOP pushbutton but to monitor an end switch.
A copy is valid for the same MBS block or the same function element as
the original.
Copies may be made of each Pilz pre-defined "Safety device" diagnos-

tic type. Copies may also be made of copies. A copy is given a default
name, which may be changed.
Events may not be deleted from the copy, but they may be edited. The
priority and the event's scope and description may be changed.
The remedy can be changed as required: existing actions may be edited,

actions may be deleted and new actions may be added.

3-10
3.4.2 PSS only: Instances

PSS only: Instances
3-
Instances of diagnostic types enable diagnostics to be adapted dynam-

ically while the PSS is in operation. This is only required on special ap-
plications, e.g. if different event messages to those shown previously are
to be displayed after a plant section has shut down.
INFORMATION
Instances may be created for Pilz pre-defined "Safety device"
diagnostic types and for copies of Pilz pre-defined diagnostic
types, but not for "Bit" or "Word" diagnostic types.
Counting of instances starts at "0". The number of the instance is shown

inside square brackets, e.g. "[2]".
Instances >= [1] can be edited by the user. Events cannot be deleted
from the instance, but the event message can be edited. The remedy
may be changed as required, existing actions may be edited or deleted
and new actions may be added.
Instance [0] of a Pilz pre-defined diagnostic type corresponds to the

original and may not be modified by the user. Instance [0] of a copied
diagnostic type may be edited, in the same way as instances >= [1].
The SSNR of the MBS block used within the user program is entered in
the diagnostic table. The SSNR is assigned the required diagnostic type.
An existing message is not deleted if the diagnostics for the correspond-

ing SSNR is subsequently deactivated. The message is not deleted until
the corresponding diagnostic word is modified.
If instances have been created for this diagnostic type, it is possible to

switch from one instance to another. This occurs in DB018 of the ST
project section. The diagnostics for a block can also be completely shut
down within DB018. DB018 must be created by the user.

3-11
Assignment of DB018:
Data word Contents

0 Free
1 DR: Instance number of SSNR 1, which is to be active.
DL: If DL = 1, diagnostics will not be run for the block with SSNR 1.
2 DR: Instance number of SSNR 2, which is to be active.
DL: If DL = 1, diagnostics will not be run for the block with SSNR 2.
... ...
x DR: Instance number of the highest SSNR used within the user program (max. SSNR 600) and
which is to be active.
DL: If DL = 1, diagnostics will not be run for this block.
INFORMATION
Before you can create instances you will need to activate this
function.
Details of how to switch on this function are provided in PSS WIN-PRO's

online help.

3-12
3.5 Diagnostic configuration of operands
3.5
Diagnostic
3500
3- configuration of operands
Operand's diagnostic configuration

` PSS: Contains the event messages that are output when inputs, out-
puts and flags have a defined status.
` PNOZmulti: Contains the event messages that are output when inputs,
outputs and connection points have a defined status.
You can configure a "Bit" diagnostic type for any bit, and a "Word" di-
agnostic type for any word (PSS only).
3.5.1 Bit diagnostic type

Bit diagnostic type
3-
Bit operands are:

` PSS
– Input and output bits
– Flag bits
` PNOZmulti
– Inputs and outputs
– Inputs and outputs of elements in the PNOZmulti Configurator
The "Bit" diagnostic type can be configured for bit operands. A new "Bit"
diagnostic type is given a default name, which you can change.
The “Bit” diagnostic type contains a single event message, including

remedies. The event message is displayed during diagnostics when the
operand assumes a "1" status. On a PNOZmulti it is also possible to
evaluate by a rising or falling edge.
3.5.2 PSS only: "Word" diagnostic type

PSS only: "Word" diagnostic type
3-
The "Word" diagnostic type can be configured for word operands (input,
output and flag words). A new "Word" diagnostic type is given a default
name, which you can change.
In the "Word" diagnostic type, an event message including remedy can

be defined for each individual bit of the word. The event message is dis-
played during diagnostics when the corresponding bit of the word oper-
and assumes a "1" status. Specific event messages cannot be defined
for events in which several bits of the word operand can assume a "1"
status simultaneously. In this case, all event messages for the affected
bits are displayed during diagnostics.

3-13
3.5 Diagnostic configuration of operands

3-14
4 PVIS OPC Server
4.1 Function of the PVIS OPC Server
4000 OPCofServer
PVIS
4.1
Function
4100
4- the PVIS OPC Server
OPC stands for openness, productivity, collaboration. OPC is a stand-

ardised software interface, which enables applications from a wide vari-
ety of manufacturers to exchange data. The OPC Foundation is
responsible for maintaining and propagating the standard. Around one
hundred companies are currently members, including Pilz.
The PVIS OPC Server is a software package that serves as a diagnostic

unit and runs on a PMIvisu/PMIopen or PC. The PVIS OPC Server reads
the data from the connected control systems and displays them in the
namespace. From there they are called up by PVIS ActiveX Control or by
another OPC Client. All the settings for the PVIS OPC Server are made
by the PVIS OPC Configurator and are downloaded to the PVIS OPC
Server as an OPC project.
Expanded PVIS diagnostics may also be run without the PVIS OPC
Server, e.g. using a PMI m107 diag. With the PVIS OPC Server it is pos-
sible to download diagnostic data, the process data display and addi-
tional information to any graphics software or to other applications.
The key features of the PVIS OPC Server are:

` OPC specification with
– Data Access 1.0a (when installed on a PC)
– Data Access 2.05
– Data Access 3.0
` OPC interfaces with
– All "Mandatory Interfaces" in accordance with the data access spec-
ification
– Generic access to process data in the namespace with pre-defined
syntax
– Symbolic access to process data in the namespace (PSS only)
` OPC data types are:
– VARIANT UI1, I1, UI2, I2, UI4, I4, R4, R8, BOOL
– Fields from these data types
– BSTR

4-1
4 PVIS OPC Server
4.2 Install PVIS OPC Server
4.2.1 System requirements

4.2
Install
4200
4- PVIS OPC Server
System requirements
4-
The PVIS OPC Server can be installed on the following diagnostic units:
` PC with operating system:
– Windows 2000
– Windows 2003 Server
– Windows XP
– Windows Vista
or
` PMIvisu or PMIopen Generation 3 (PMI v3xx/PMI o3xx) or higher
If installing on a PC you will need “.NET Framework”, from Version 2.0.

“.NET Framework” is available on Microsoft's website. If installing under
Windows Vista, specific settings regarding user rights will be required
(see also section 4.4.3).
OPC-compatible graphics software is also required in order to display

and visualise the data. PMIvisu already contains such graphics soft-
ware, PMI-PRO, so no other software is required.
4.2.2 Licencing
4-
Licencing
After installation the PVIS OPC Server runs in demo mode. In demo
mode the PVIS OPC Server will send data for four hours, after which
time it will stop sending new messages to the OPC Clients (e.g. PMI
m309 diag, PVIS Active X,...). Demo mode is displayed in PVIS ActiveX.
You will need to license the OPC Server in order to obtain the required
licence mode. You can do this via the Licence Manager on the PVIS
OPC Configurator.
After licensing you will need to restart the PVIS OPC Server for the
changes to take effect.
There are two different licences for the PVIS OPC Server on a PC:
` Point-to-point licence
One OPC Client (display unit) and one diagnosed control system.
` Full licence
Any number of OPC Clients (display units) and diagnosed control sys-
tems.
There are two different licences for the PVIS OPC Server on a PMI:
` Point-to-point licence
One OPC Client (display unit) and one diagnosed control system.

4-2
4 PVIS OPC Server
` Full licence
The total of diagnosed control systems and OPC Clients (display units)
is a maximum of 8, e.g. one PMI and seven control systems.
The following applies in the case of a licence with a limited number of

connections: The units are operated in the order in which they log on to
the PVIS OPC Server. Once the permitted number of connections is
reached, all other units are rejected. If the number of units configured is
greater than the number permitted, the PVIS OPC Server will start up in
demo mode.
4.2.3 Installation on a PC
Installation on a PC
4-
If the PVIS OPC Server is being operated on a PC, the following struc-
ture will result, for example:
PC PC PC
Diagnostic unit
Display unit PVIS OPC Server

PVIS OPC Configurator
PVIS ActiveX Control (Display unit Diagnostic configurations
Graphics software
Graphics software)
ETH COM/ETH
PMI PSS PSS
COM
Control system Control system
Display unit
Graphics software PSS PNOZmulti
Control system COM

Control system
Fig. 4-4: Example: PVIS OPC Server on a PC in the network
In the diagram, the PVIS OPC Server and PVIS OPC Configurator are in-
stalled on different PCs, connected via a network (Ethernet) or serial in-
terface (COM). The PVIS OPC Server and PVIS OPC Configurator may
be installed on the same PC. Several control systems can be diagnosed
via a network or via the serial interface.
Install the following programs and components from the "PVIS OPC
Tools" CD:
` PVIS OPC Server

4-3
4 PVIS OPC Server
` PVIS OPC Configurator
The PVIS OPC Server is installed on the PC that serves as the diagnostic
unit. The diagnostic unit may be used simultaneously as a display unit
(shown in brackets in the diagram).
The OPC Core Components are installed automatically together with the
PVIS OPC Server and the PVIS OPC Configurator. The OPC Core Com-
ponents are various auxiliary programs and software components for
the OPC Server.
Procedure when installing the PVIS OPC Server on a PC for the first
time:
` Start the PC on which the PVIS OPC Server is to be installed.
` Insert the "PVIS OPC Tools" CD into your CD-ROM drive.
` Select "Install PVIS OPC Server on PC".
` Follow the on-screen instructions to complete the installation.
During installation the "PilzPVISTransfer.exe" file will automatically be

copied to the PC's Autostart menu. This file must be run to enable the
PVIS OPC Configurator to download files to the PVIS OPC Server.
Procedure when updating the PVIS OPC Server or reinstalling on the

same PC:
` Start the PC on which the PVIS OPC Server is to be installed.
` Separate all the OPC Clients from the PVIS OPC Server.
` Stop the PVIS OPC Server by clicking on the program icon in the task
bar and exiting the program through the menu.
` Select "Install PVIS OPC Server on PC".
` In the "InstallShield Wizard", select the "Repair" option to reinstall all
parts of the program.
` Enter the licence key in the PVIS OPC Configurator.
` Restart the computer if prompted to do so by the installation program.

4-4
4 PVIS OPC Server
4.2.4 Installation on a PMIvisu/PMIopen

Installation on a PMIvisu/PMIopen
4-
If the PVIS OPC Server is being operated on a PMIvisu/PMIopen, the fol-

lowing structure will result, for example:
PC PMI PC
Diagnostic unit
Display unit PVIS OPC Server

PVIS OPC Configurator
PVIS ActiveX Control (Display unit Diagnostic configurations
Graphics software
Graphics software)
ETH USB
PMI PSS PSS
COM
Control system Control system
Display unit

Graphics software PSS PNOZmulti
Control system COM

Control system
Fig. 4-5: Example: PVIS OPC Server on a PMIvisu/PMIopen in the

network
The PVIS OPC Server is installed on the PMIvisu/PMIopen that serves

as the diagnostic unit. The diagnostic unit may be used simultaneously
as a display unit (shown in brackets in the diagram). Several control sys-
tems can be diagnosed via a network or via the serial interface.
Install the following programs and components from the "PVIS OPC
Tools" CD:
` PVIS OPC Server
is installed on a PMIvisu/PMIopen.
` PVIS OPC Configurator
is installed on a PC.
Installation requirement with ActiveSync/ Windows Mobile Device Man-

ager:
` The PC containing the "PVIS OPC Tools" CD must be connected to
the PMIvisu/PMIopen via USB cable.
` ActiveSync must be installed and there must be a connection to the
PMIvisu/PMIopen (on Windows Vista, Version 6.1 or higher of the Win-
dows Mobile Device Manager must be installed).
– ActiveSync can be found on the "PVIS OPC Tools" CD.

4-5
4 PVIS OPC Server
Procedure:
` Start your PC.
` Insert the "PVIS OPC Tools" CD into your CD-ROM drive. The CD
starts automatically.
` Switch on your PMIvisu/PMIopen.
` From the CD-ROM, start up the file
"PVIS OPC Server.PMI3xx.exe" on the PC.
The directory \IPSM\PVISOPCServer is created on the PMIvisu/PMIo-
pen as a result of the installation.
` Confirm the suggested data directory or select a different data direc-
tory for the PVIS OPC Server on the PMI. Please note that on a PMI,
all directories created by the user outside the \IPSM directory are de-
leted at each restart.
Alternatively, a transfer via FTP/Ethernet connection or CF card is also

possible. Procedure:
` Start your PC.
` The "PVIS OPC Tools" CD contains the following CAB file:
"PVIS OPC Server.PMI3xx.CAB"
Copy this CAB file from the PC's CD-ROM drive to the \IPSM directory
on the PMIvisu/PMIopen.
` Open Windows Explorer on the PMIvisu/PMIopen. Go to the
\IPSM\PVISOPCServer directory.
` Start the CAB file. The installation process will start. The CAB file in the
\IPSM directory of the PMIvisu/PMIopen will be deleted as a result of
the installation.

4-6
4 PVIS OPC Server
The available disk space you will require is approximately:

` 3.5 MB for the PVIS OPC Server and associated components
` 1 MB for PVIS ActiveX Control
` Space requirement for the OPC project (depends on the scope):
– From 2 MB per device project
If you change the installation directory you will need to enter the details
later in the PVIS OPC Configurator under OPC Project Properties.
During installation the file OPCEnum.exe will be created in the

\IPSM\PVISOPCServer directory. This program must be started for ac-
cess to the PVIS OPC Server via a different PMIvisu/PMIopen or PC. The
OPCEnum.exe program can be copied to the PMIvisu/PMIopen's start
file so that it is started automatically.
If a PMI-PRO project is copied to another PMIvisu/PMIopen, the PVIS

OPC Server must also be installed and licensed on the other PMIvisu/
PMIopen.

4-7
4 PVIS OPC Server
4.3 Install PVIS OPC Configurator
4.3
Install
4300
4- PVIS OPC Configurator
The OPC Configurator is installed on a PC. The following operating sys-

tems are supported:
` Windows 2000
` Windows 2003 Server
` Windows XP
` Windows Vista
An HTML 3.2-compatible browser is required to view the online help,

e.g. Internet Explorer from Version 5.0. If installing under Windows Vista,
specific settings regarding user rights will be required (see also section
4.4.3).
Installation procedure for the PVIS OPC Configurator:

` Start the PC on which the PVIS OPC Configurator is to be installed.
` Select "Install PVIS OPC Configurator".

4-8
4 PVIS OPC Server
4.4 Communication and security settings
4.4
Communication
4400
4- and security settings
The following DCOM configurations are only required if:

` The PVIS OPC Server is being operated on a PC and
` The PVIS OPC Server is to be accessed via a network.
In this case, all the PCs involved will require specific DCOM configura-
tions to enable network access to the PVIS OPC Server. The PCs should
be logged on to the same domain.
Certain additional DCOM configurations are required on the PC with the

PVIS OPC Server. The following section describes the DCOM configu-
ration for the Windows 2000 and Windows XP operating systems. The
dialogue boxes may vary depending on your Windows version. Further
guidelines are available under the Windows Help.
These DCOM configurations grant access rights to the PVIS OPC Server
to other network users. If installing under Windows Vista, specific set-
tings regarding user rights will be required (see also section 4.4.3).
An incorrect configuration can compromise the safety and stability of

the operating system. A network administrator can optimise these con-
figurations to protect the server from unauthorised access.

4-9
4 PVIS OPC Server
4.4.1 DCOM configuration under Windows 2000

DCOM configuration under Windows 2000
4-
4.4.1.1 DCOM configuration on all PCs

DCOM configuration on all PCs
4-
The following DCOM configurations must be made on the PC with the

PVIS OPC Server and on all connected PCs that are to communicate
with the PVIS OPC Server.
Fig. 4-6: Call up dcomcnfg.exe

` Select Run... in the Windows Start menu
` Enter "dcomcnfg".
` Click OK.
The "DCOM Configuration Properties" window opens.

4-10
4 PVIS OPC Server
Fig. 4-7: "Default Properties" tab

` Select the "Default properties" tab
` Enable DCOM.
` Select "None" under "Default Authentication Level".
` Select "Identify" under "Default Impersonation Level".

4-11
4 PVIS OPC Server
Fig. 4-8: "Default Protocols" tab

` Select the "Default Protocols" tab.
` If it's not already available: Add the "Connection-oriented TCP/IP"
protocol.
` Move the "Connection-oriented TCP/IP" protocol to the top of the list
(using the "Move Up" button).
The DCOM properties are now set correctly.

` Click OK to close the window and save all the settings.
With this you will exit dcomcnfg.exe. The next time the PC is restarted
the changes will be active.

4-12
4 PVIS OPC Server
4.4.1.2 DCOM configuration on the PC with the PVIS OPC Server

DCOM configuration on the PC with the PVIS OPC Server
4-
The following DCOM configurations must be run exclusively on the PC

on which the PVIS OPC Server is installed.
Fig. 4-9: "Applications" tab

` Enter "dcomcnfg".
` Click OK.
The "DCOM Configuration Properties" window opens.

` Select the "Applications" tab.
` Select the application "Pilz PVIS OPC Server DA".
` Click Properties...
The "Pilz PVIS OPC Server DA Properties" window opens.

4-13
4 PVIS OPC Server
Fig. 4-10: "General" tab

` Select the "General" tab.
` Select "None" under "Authentication Level".

4-14
4 PVIS OPC Server
Fig. 4-11: "Location" tab

` Select the "Location" tab.
` Enable "Run application on this Computer".

4-15
4 PVIS OPC Server
Fig. 4-12: "Security" tab

` Select the "Security" tab.
` Enable all the custom permissions.

4-16
4 PVIS OPC Server
Fig. 4-13: Custom access permission

` Click "Edit..." under "Custom access permission".
` Add the following users
– INTERACTIVE
– Everyone
– NETWORK
– SYSTEM
` Select "Allow Access" throughout.

4-17
4 PVIS OPC Server
Fig. 4-14: Custom launch permission

` Click "Edit..." under "Custom launch permission".
` Add the following users
– INTERACTIVE
– Everyone
– NETWORK
– SYSTEM
` Select "Allow Launch" throughout.

4-18
4 PVIS OPC Server
Fig. 4-15: Custom configuration permissions

` Click "Edit..." under "Custom configuration permissions".
– Select "Unlimited Access"/"Full Control" throughout.

4-19
4 PVIS OPC Server
Fig. 4-16: "Identity" tab

` Select the "Identity" tab.
` Enable "Interactive User".

4-20
4 PVIS OPC Server
Fig. 4-17: "Endpoints" tab

` Select the "Endpoints" tab.
` If it's not available: Add "Default System Protocols...".
` Click OK.
The properties of the "Pilz PVIS OPC Server DA" are now set correctly.
The next step is to set the same configurations for "OPCEnum".

` Select the application "OPCEnum".
The "OPCEnum Properties" window opens.

` Go through the same steps as described for the "Pilz PVIS OPC Server
DA".
` Only difference: Select "System Account (services only)" under the
"Identity" tab

4-21
4 PVIS OPC Server


4-22
4 PVIS OPC Server
4.4.2 DCOM configuration under Windows XP

DCOM configuration under Windows XP
4-
4.4.2.1 DCOM configuration on all PCs

DCOM configuration on all PCs
4-
The following DCOM configurations must be made on the PC with the

PVIS OPC Server and on all connected PCs that are to communicate
with the PVIS OPC Server.
Fig. 4-18: Call up dcomcnfg.exe

` Enter "dcomcnfg".
` Click OK.
The "Component Services" window opens.

4-23
4 PVIS OPC Server
Fig. 4-19: "Component Services" window

` In the toolbar, select Configure My Computer by right-clicking on the
My Computer icon.
The "My Computer" window opens.

4-24
4 PVIS OPC Server
Fig. 4-20: "Default Properties" tab

` Select the "Default Properties" tab.
` Enable DCOM.
` Select "None" under "Default Authentication Level".
` Select "Identify" under "Default Impersonation Level".

4-25
4 PVIS OPC Server
Fig. 4-21: "Default Protocols" tab

` Select the "Default Protocols" tab.
` If it's not already available: Add the "Connection-oriented TCP/IP"
protocol.
` Move the "Connection-oriented TCP/IP" protocol to the top of the list
(using the "Move Up" button).

4-26
4 PVIS OPC Server
Fig. 4-22: "COM Security" tab

` Select the "COM Security" tab.
` Click "Edit Limits" under "Access Permissions".

4-27
4 PVIS OPC Server
Fig. 4-23: “Access Permission” tab

` Add the following users (Add... – Advanced– Search now)::
– ANONYMOUS LOGON
– INTERACTIVE
– Everyone
– NETWORK
– SYSTEM
` Enable local access and remote access for all users.
` Click OK.
` Click "Edit Limits" under "Launch and Activation Permissions".

4-28
4 PVIS OPC Server
Fig. 4-24: “Launch Permission” tab

` Enable all the launch permissions.
` Click OK.

That completes the component services. The next time the PC is restart-
ed the changes will be active.

4-29
4 PVIS OPC Server
4.4.2.2 DCOM configuration on the PC with the PVIS OPC Server

DCOM configuration on the PC with the PVIS OPC Server
4-
The following DCOM configurations must be run exclusively on the PC

on which the PVIS OPC Server is installed.
Fig. 4-25: "DCOM Config"

` Enter "dcomcnfg".
` Click OK.
` In the "Component Services" window, open the "DCOM Config" di-
rectory.
` Right-click on the "Pilz PVIS OPC Server DA" application.
` Click "Properties...".
The "Pilz PVIS OPC Server DA Properties" window opens.

4-30
4 PVIS OPC Server
Fig. 4-26: "General" tab

` Select the "General" tab.
` Select "None" under "Authentication Level".

4-31
4 PVIS OPC Server
Fig. 4-27: "Location" tab

` Select the "Location" tab.
` Enable "Run application on this Computer".

4-32
4 PVIS OPC Server
Fig. 4-28: "Security" tab

` Select the "Security" tab.
– Select "Customize" throughout.
` Click "Apply".

4-33
4 PVIS OPC Server
Fig. 4-29: Custom access permission

` Click "Edit..." under "Access Permissions".
` Add the following users:
– INTERACTIVE
– Everyone
– NETWORK
– SYSTEM
` Enable "Local Access" and "Remote Access" throughout.
` Click "Edit..." under "Configuration Permissions".
– Add the same groups entered under access permissions and acti-
vate "Allow Read-only" and "Full Access".
` Click "Edit..." under "Launch and Activation Permissions".
– Add the same groups entered under access permissions and acti-
vate "Allow Launch".

4-34
4 PVIS OPC Server
Fig. 4-30: "Identity" tab

` Select the "Identity" tab.
` Enable "The Interactive User".

4-35
4 PVIS OPC Server
Fig. 4-31: "Endpoints" tab

` Select the "Endpoints" tab.
` If it's not available: Add "Default System Protocols...".
The properties of the "Pilz PVIS OPC Server DA" are now set correctly.
The next step is to set the same configurations for "OPCEnum".

` Select the application "OPCEnum".
The "OPCEnum Properties" window opens.

` Go through the same steps as described for the "Pilz PVIS OPC Server
DA".
` Only difference: Select "System Account (services only)" under the
"Identity" tab

4-36
4 PVIS OPC Server


4-37
4 PVIS OPC Server
4.4.3 Enabling access rights under Windows Vista

Enabling access rights under Windows Vista
4-
Under Windows Vista you will need to make the same DCOM settings
as under Windows XP. In addition to the Windows XP settings you will
also need to configure the user rights for Windows Vista.
Procedure:
` Log in with administrator rights and, in Windows Explorer, open the di-
rectory in which the PVIS OPC Server is installed.
` Right-click on the directory and select Security -> Groups or User
Name -> Edit.
The Permissions for PVIS OPC Server window will open.
` Select User under Groups and User Name.
` Select Full Access under Permissions.
` If the PVIS OPC Server uses additional directories to store data, the
same permissions will also need to be granted in these directories.
To install the PVIS OPC Server on a PMI, Version 6.1 or higher of the
"Windows Mobile Device Center" must be installed.
During installation the Pilz Transfer Tool can store directories and files
exclusively as a "User". To ensure that both users (Administrator and
User) have access to the same OPC project, the following settings must
be made after the PVIS OPC Server is installed.
` Start Windows Explorer.
` Open the folder in which the PVIS OPC Server is installed.
` Right-click on the directory and select Properties.
` On the Security tab, click on Edit under Groups or User Name.
` Select User from Groups or User Name.
` Select full access under User Permissions.
From Version 1.4.0 of the PVIS OPC Server, this setting must also be
made for the data folder that was stated during installation. This setting
must be made each time the data directory is changed.
The PVIS OPC Server and OPC Client must have the same rights on the
PC. For this reason the programs must be assigned administrator rights
after installation.
Procedure:
` Start Windows Explorer.
` Open the folder in which the program is installed.
` Right-click on the directory and select Properties.
` Click on the Compatibility tab.
` Select Run Program as Administrator under Permissions Level.

4-38
4 PVIS OPC Server
4.4.4 Firewalls and security settings

Firewalls and security settings
4-
A firewall or any other security mechanisms on the PC and network may

prevent the PVIS OPC Server from communicating correctly with the
connected device. If this is the case it will be necessary to adjust the se-
curity settings and firewall settings. Current documentation on the re-
quired security settings is available on the website for the OPC
Foundation, under "Downloads" and "White Papers":
www.opcfoundation.org
Firewalls allow access to explicitly registered programs. The following
programs must have access:
` All OPC Clients
` Microsoft Management Console
` OPCenum.exe
A port must also be enabled for data exchange:

` Name: DCOM
` Port number 135
` Protocol: TCP
These enables grant access rights to the PC to other network users or

users on the Internet. A network administrator can optimise these Fire-
wall settings to protect the server from unauthorised access.

4-39
4 PVIS OPC Server
4.5 PVIS OPC project
4.5.1 Structure of a PVIS OPC project

4.5 OPC project
PVIS
4500
4-
Structure of a PVIS OPC project

4-
An OPC project is required in order to operate a PVIS OPC Server. The

OPC project contains all the information that the PVIS OPC Server re-
quires in order to make the necessary data for the PVIS ActiveX Control
or any other graphics device available within the namespace.
OPC Project
OPC Project Properties
Device Project 1 ... Device Project n
Device Project Properties Device Project Properties
Diagnostic Configuration Diagnostic Configuration
OPC Data OPC Data
Fig. 4-32: PVIS OPC project
An OPC project consists of the following components:

` OPC Project Properties
Details of the OPC project, for example, the name of the OPC project,
plus information on the connection between the PC on which the PVIS
OPC Configurator is installed and the PVIS OPC Server.
` Device projects
A device such as a PSS has a device project. The device project is cre-
ated using the device's system software, e.g. a PSS project is created
using the PSS WIN-PRO system software. The device's diagnostic
configuration and OPC data are stored within the device project.
– Diagnostic configuration
The diagnostic configuration contains the event messages and rem-
edies that are to be displayed when the device has a defined status.

4-40
4 PVIS OPC Server
– OPC data
Data that the PVIS OPC Server needs in order to make all the device
information available within the namespace. For example, if a device
project does not contain any OPC data, "Overview Information" can-
not be provided.
For each device connected to the PVIS OPC Server, the corresponding
device project is incorporated into the OPC project. In other words, a
link to the device project is stored in the OPC project. The number of
OPC projects that can be added to a device project will depend on the
licence.
Inside the OPC project, the "Device Project Properties" are added to
each device project. These include information such as the name of the
device project, details of the connection between the device and the
PVIS OPC Server plus the default language.
4.5.2 Language management

Language management
4-
In the OPC Configurator the user can define the languages that are to be
downloaded to the PVIS OPC Server. These languages must be availa-
ble in each device project in the OPC project. The user defines the lan-
guages for the device projects when he creates the diagnostic
configuration in the system software's diagnostic configurator (PSS
WIN-PRO or PNOZmulti Configurator). A device project's diagnostic
configuration is made up of one part that is pre-defined by Pilz and one
part that is created by the user.
The user defines the language required for both parts:

` Pilz diagnostic language/alternative language
Language for the device's diagnostic configuration and the Pilz pre-
defined diagnostic types for safety devices
` Project language
This is the language in which the user creates the texts for the diag-
nostic configuration, e.g. device names, equipment identifiers and us-
er's diagnostic types
The user also defines the default language. The default language is used
as follows: If PVIS ActiveX Control or another visualisation system re-
quests event messages in a language that's unavailable, the PVIS OPC
Server will display the event messages in the default language.

4-41
4 PVIS OPC Server
Example: Certain languages have been selected for an OPC project. The
PVIS ActiveX Control calls up information from the PVIS OPC Server in
one of these languages. If this language is not available within a device
project, the PVIS ActiveX Control will receive the information in the de-
fault language.

4-42
4 PVIS OPC Server
4.6 Event view
4.6 view
Event
4600
4-
The PVIS OPC Server stores all the event messages in the event log. The
event log is a ring memory, in other words, the most recent event mes-
sages are stored. The number of events in the ring memory is configura-
ble.
The PVIS OPC Server should be synchronised with all the connected
control systems to ensure that the events are stored in the event view
with the correct time stamp.

4-43
4 PVIS OPC Server
4.7 Commissioning the PVIS OPC Server
4.7
Commissioning
4700
4- the PVIS OPC Server
You can use the PVIS OPC Configurator to download diagnostic config-
urations to a PVIS OPC Server.
Prerequisite:
` The PVIS OPC Configurator is installed.
` The diagnostic configurations is available. The PVIS OPC Configurator
has access to the diagnostic configurations.
` The PVIS OPC Server is installed.
If the PVIS OPC Server is run on a PMIvisu/PMIopen, there must be a
connection between the PC with the PVIS OPC Configurator and the
PMIvisu/PMIopen:
– Type 1:
ActiveSync must be installed (on Windows Vista, Version 6.1 or high-
er of the Windows Mobile Device Manager must be installed). Ac-
tiveSync can be found on the "PVIS OPC Tools" CD.
– Type 2:
It is possible to connect via Ethernet without ActiveSync.
` The PSS and PNOZmulti are connected to the PC or PMIvisu/PMIo-
pen that is running the PVIS OPC Server. This is described in the op-
erating manuals for the PMIvisu/PMIopen, PSS and PNOZmulti.
Start the PVIS OPC Configurator:

` In the Windows Start menu select Programs -> Pilz -> PVIS OPC
Configurator.
Procedure for downloading the diagnostic configurations:

` Create an OPC project.
` Start to download.
The various steps are described in the online help for the PVIS OPC
Configurator.
If the PVIS OPC Configurator cannot establish contact with a PVIS OPC
Server on a PC, it's possible that the "PilzPVISTransfer.exe" file is not
running on the PC with the PVIS OPC Server. You can check this in the
Windows Task Manager (see section entitled "Install PVIS OPC Server").

4-44
4 PVIS OPC Server
There is no need to start the PVIS OPC Server manually; it starts auto-
matically via the PVIS ActiveX Control on the graphics software or via
another OPC Client. The PVIS OPC Server loads the OPC project at
each restart. To restart the PVIS OPC Server when there is a new OPC
project, you can:
` Exit all the graphics tasks that are currently running with PVIS ActiveX
Control and restart.
` Exit the PVIS OPC Server manually. Depending on the configuration of
the OPC Client:
– The OPC Client restarts the PVIS OPC Server automatically.
– Restart the OPC Client. The OPC Client then restarts the PVIS OPC
Server.

4-45
4 PVIS OPC Server

4-46
5.1 Function of the PVIS ActiveX Control
5000 ActiveX
PVIS
5.1
Function
5100
5- of the
Control
ActiveX is a software component model from Microsoft for active con-

tent such as macros or applets; it is based on the Component Object
Model (COM). ActiveX elements can be used in various environments,
e.g. in browsers, in graphics software or in common programming envi-
ronments (e.g. Microsoft Visual Studio).
PVIS ActiveX Control is an OPC Client and is used to display the diag-
nostic data from a PVIS OPC Server's namespace on the graphics soft-
ware. The PVIS ActiveX Control must be configured for this purpose.
Details of how to incorporate PVIS ActiveX Control into your graphics
software and how to call up the configuration can be found in the de-
scription or in the graphics software's online help.
For the PMI-PRO (open) graphics software, a detailed description can

be found in the manual: "PMI-PRO (open) – ActiveX Elements".

5-1
5.2 Install PVIS ActiveX Control
5.2.1 Installation on a PC
5.2
Install
5200
5- PVIS ActiveX Control
Installation on a PC
5-
Procedure:
` Start your PC.
` Select "Install PVIS ActiveX Control on PC". If installing under Win-
dows Vista, specific settings regarding user rights will be required (see
also section 4.4.3).
5.2.2 Installation on a PMIvisu/PMIopen

Installation on a PMIvisu/PMIopen
5-
Installation requirement with ActiveSync/ Windows Mobile Device Man-

ager:
` The PC containing the "PVIS OPC Tools" CD must be connected to
the PMIvisu/PMIopen via USB cable or Ethernet.
` ActiveSync must be installed and there must be a connection to the
PMIvisu/PMIopen (on Windows Vista, Version 6.1 or higher of the Win-
dows Mobile Device Manager must be installed).
– ActiveSync can be found on the "PVIS OPC Tools" CD.
Procedure:
` Start your PC.
` From the CD-ROM, start up the file
"PVIS ActiveX Control.PMI3xx.exe" on the PC.

5-2
5.2 Install PVIS ActiveX Control
Alternatively, a transfer via FTP/Ethernet connection or CF card is also

possible. Procedure:
` Start your PC.
` Open Windows Explorer on the PMIvisu/PMIopen.
` Copy the file "PVIS ActiveX Control.PMI3xx.CAB" from the PC's CD-
ROM drive to the \IPSM directory of the PMIvisu/PMIopen.
` Start the CAB file. The installation process will start. The CAB file in the
\IPSM directory of the PMIvisu/PMIopen will be deleted as a result of
the installation.
If a PMI-PRO project is copied to another PMIvisu, the PVIS ActiveX

Control must also be installed on the other PMIvisu.

5-3
5.3 Configure PVIS ActiveX Control
5.3
Configure
5300
The following settings can be made in the PVIS ActiveX Control's con-
figuration menu:
Fig. 5-33: PVIS ActiveX Control configuration menu

5-4
On the General tab you can make the following settings:

` OPC server address
Enter the IP address or the logical name of the PVIS OPC Server.
Default: "localhost"
"localhost" is the valid logical name when the PVIS OPC Server and
the graphics software are on the same computer.
` OPC project
Enter the name of the OPC project, as defined using the OPC Config-
urator.
` Device project
Enter the name of the device project belonging to the relevant device.
` Language
Select the language in which the diagnostic texts and the interface of
the PVIS ActiveX Control are to be displayed. You will have defined
the languages available for the diagnostic texts when you created the
diagnostic configuration. If the language you select as the diagnostic
language is not available for the interface, the interface will appear in
English. The interface can be displayed in the following languages:
– German
– English
– French
– Spanish
– Italian
– Dutch
– Chinese
– Japanese
` Display
Select:
– "Single window"
Event messages and remedies appear in separate windows.
– "Split window"
Event messages and remedies appear in a split window, one above
the other.
– "Event log"
Instead of the current event messages and remedies, the entries
from the event log appear, showing past events.
` Optimize for QVGA
Select this option to optimise the screen output for QVGA format.
QVGA is a standard for small screens with 320 x 240 pixels ("Quarter
VGA"), e.g. the PMI v315.
` Use keyboard
Select this option to enable keyboard operation.
` Font type
Select the font type
` Font size
Select the font size.
` Allow filtration

5-5
Select whether or not a configurable criterion can be used to filter

messages.
On the Split Window 1 tab you can make the settings relating to the
configuration and size of the window areas. These settings will apply if
you selected Split Window under Display:
` Pane configuration
Select between two window configurations.
– Horizontal split
– Horizontal and vertical split
` Pane height
Adjust the height of the window areas as a percentage of the overall
window height.
` Pane width
Adjust the width of the window areas as a percentage of the overall
window width.
` Line height
Adjust the height of the table row in multiples of the text height.
On the Split Window 2 tab you can make settings relating to the dis-
played fields. These settings will apply if you selected Split Window un-
der Display:
` Columns in event list
Select the fields that will be displayed in the event messages window,
plus their position and width within the table.
` Columns in remedy list
Select the fields that will be displayed in the remedies window, plus
their position and width within the table.
You can check the the settings used to design the windows using the
preview function. The preview will be filled with dummy data.
On the Event Log tab you can make settings relating to how the event
log is displayed:
` The fields' window width in pixels, for displaying the event log
` The maximum number of event messages that can be displayed within
a window.
The following properties can be modified during runtime:

` OPC server address, OPC project and Device project
If these properties are modified, the PVIS ActiveX Control will be re-
initialised.
` Language
The current language of the diagnostic texts is displayed in code ("de",
"en",...) on a button on the PVIS ActiveX Control. The button can be
used to open a window in which you can switch between the available
languages.

5-6
5.4 Operate PVIS ActiveX Control
5.4.1 Split window

5.4
Operate
5400
Split window
5-
While diagnostics are being run, you can see the event list in the top half
of the window. If you highlight an event, that row will turn blue and the
bottom half of the window will show the remedy for this event. If you
highlight a remedy, the row showing the event will turn grey and the row
showing the remedy will turn blue.
Fig. 5-34: Window wit horizontal and vertical split

5-7
Fig. 5-35: Window with horizontal split
Keyboard assignment
Focus is on a line...
...of the event list ...of the remedy list ...of the event log
Cursor up To previous event To previous remedy To previous event
Cursor down To next event To next remedy To next event
Enter Show remedy and image for Show image for remedy No function
selected event
ESC Remedy and image for Focus on event list, remedy Switch to information win-
event are deleted and image for event are de- dow
leted
F1 No function Refresh event log
F2 Switch to information window Save event log as log file
F3 Previous 10 events No function Previous 10 events
F4 Next 10 events Next 10 events
INFORMATION
The "Split window" setting is unsuitable for the PMI 309 and
PMI 315 units due to the screen resolution.

5-8
5.4.2 Single window

Single window
5-
If you have selected "Single window" under "Display" in the basic con-
figuration, the event list and remedies will be displayed in separate win-
dows.
Fig. 5-36: Separate window with event list in VGA resolution

5-9
Fig. 5-37: Separate window with event list in QVGA resolution
While the diagnostics are running, call up the remedy for an event by
clicking "Remedy".
While the diagnostics are running, call up an image relating to this action
by clicking "Image".
You can switch from this view to "Event log" and back again during op-
eration.
Keyboard assignment
Focus is...
...on an event ...on a remedy ...on the event view
Cursor up To previous event To previous remedy To previous event
Cursor down To next event To next remedy To next event
Enter Show remedy for selected No function No function
event
ESC No function Switch to event view Switch to information win-
dow
F1 Display image for event (1) Image for remedy is dis- Refresh event log
played (1)
F2 Switch to information win- No function Save event log as log file
dow
F3 Previous 10 events Previous 10 events
F4 Next 10 events Next 10 events
(1)
The image can be closed using ESC.

5-10
5.4.3 Event log

Event log
5-
The events in the event view are displayed in list format. The length of
the list is specified under Event Log during the configuration. The most
recent events are displayed.
If the "Optimize for QVGA" option is selected, only one event will be dis-
played at a time.
Fig. 5-38: Event log
The current event log is saved via the "Save" button. The event log is
saved in full, irrespective of the number of events that have been defined
under "Event log display size". The event log is saved on the PVIS OPC
Server in the the OPC project's data root directory, using the ".log" ex-
tension. Any existing event log file in this directory will be overwritten in
the process.
Keyboard assignment
Cursor up To previous event

Cursor down To next event
Enter Select language
F1 Refresh event log
F2 Save event log as log file
F3 Previous 10 events
F4 Next 10 events

5-11
5.4.4 Information window

Information window
5-
Various program statistics are displayed in the information window, in-

cluding:
` FS program's project name, integrity, check sum and time stamp
` ST program's project name, integrity and time stamp
` Diagnostic configuration's project name, integrity and time stamp
` Version and licence of the PVIS OPC Server
` Version of the PVIS ActiveX Control
Keyboard assignment
Cursor up Scroll forwards through tab (1)

Cursor down Scroll backwards through tab (1)
ESC Back to event list
F1 No function
F2 Open next tab
F3 Select language
F4 Open event log
(1)
With QVGA, the display switches to the next/previous data record.
5.4.5 Icons
5-
Icons
The icons in the window's top left-hand corner indicate the event type:
Icons in the "Diagnostics" window
Icon Key
Status information
Warning
Error

5-12
5.4.6 Filtering
5-
Filtering
With filtering, the value of the address is compared with the filter criteri-
on. Allow Filtration must be selected in the PVIS ActiveX configuration
to enable filtering. This configuration setting can be modified during
runtime, provided this is permitted by the container in which the ActiveX
is embedded. For filtering, therefore, the FilterCriterion property can be
assigned the required filter criterion, while the filter process can be ena-
bled by setting the FiltrationActive property to "1". The filter icon
in the status bar shows whether filtering has been enabled.
Application example for Microsoft Visual C++-Container:

` ActiveX instance: m_AX
` Set filter criterion:
m_AX.SetFilterCriterion(_T("MW 010.16"))
` Start filtration:
m_AX.SetFiltrationActive(1)
` End filtration:
m_AX.SetFiltrationActive(0)
The following criteria are available on a PSS:

` Filter to individual SSNR:
– For example: SSNR 23
– Range: SSNR 1 – SSNR 600
– State the number without leading zeros, leaving a space between
the number and "SSNR".
` Filter to an individual user-defined message:
– For example: MW 070.00
– State the number with leading zeros, leaving a space between the
number and "MW".
` Filter to a SafetyBUS subscriber:
– For example: 35
– Range: 32-95 and 132-195
– State the number with no leading zeros and no additional informa-
tion.
` Filter to a central device:
– For example: 1 (slot 1)
– Range: 0 – 31
– State the number with no leading zeros and no additional informa-
tion.

5-13
The following criteria are available on a PNOZmulti:

` Filter to an individual diagnostic point (DPID):
– For example: DPID 1
the number and "DPID".
` Filter to an individual safety block (SBID):
– For example: SBID 3
the number and "SBID".
` Filter to modules:
– For example: Module 1
– Range: -4 – 8
the number and "Module".
Procedure to enable filtering in PMI-PRO.

` Open the user interface configuration.
` Create the variables under Tools -> Variable Table...
` Define a string variable for the filter criterion. Any name can be used,
e.g.: "Criterion"
` Define a bit variable to start filtering. Any name can be used, e.g.: "Fil-
terMode".
` Create a "Linked Text" type PMI-PRO element for the filter criterion
and link it to the string variable.
` Create a "Switch" type PMI-PRO element to start filtering and link it to
the bit variable.
` Register these variables in PVIS ActiveX by selecting Properties.. in
the ActiveX context menu.
` Click Variable. Keep to the following order when selecting variables:
Select the variable for the filter criterion first, and then the variable to
start filtering.
Procedure for setting the runtime filter criterion:

` Double-click on the Linked Text element.
` Enter the filter criterion in the text field within the dialogue box.
A message window is displayed while the filter process is running. This

window disappears automatically once the filter process is complete,
and the filtered events are displayed.
If no event is found that matches the specified filter criterion, the follow-
ing message is displayed:
` "No events found that match the specified filter criterion."

5-14
5.5 Start PVIS ActiveX Control in the browser
5.5 PVIS ActiveX Control in the browser

Start
5500
5-
The PVIS ActiveX Control can be started on a PMIopen directly within a

browser with an HTML file. The browser must have Active-X capability,
e.g. Microsoft Internet Explorer. Graphics software is not required. An
example of such an HTML file is available in the download area of the
Pilz homepage. You can also create your own HTML file using the fol-
lowing examples.
Simplified example for HTML code:
<html>
<head>
</head>
<body scroll=no>
<OBJECT ID="PilzDiag" WIDTH=320 HEIGHT=240
style="vertical-align:left; margin-left:-10px; margin-top:-15px;"
CLASSID="CLSID:75678BBA-5CB8-4C20-9976-E9D23688C164">
<PARAM NAME="OPCServer" VALUE="localhost">
<PARAM NAME="OPCNodeEntry" VALUE="Centr_PSS">
<PARAM NAME="OPCRoot" VALUE="Centr_PSS_OPC">
<PARAM NAME="ViewLanguage" VALUE=8>
<PARAM NAME="ViewSettings" VALUE=0>
<PARAM NAME="OptQVGA" VALUE=0>
<PARAM NAME="UseKeyboard" VALUE=1>
<PARAM NAME="FontSize" VALUE=14>
<PARAM NAME="SelectedFont" VALUE="Arial">
</OBJECT>
</body>
</html>
Advanced example for HTML code, including all properties:
<html>
<head>
</head>
<body scroll=no>
<OBJECT ID="PilzDiag" WIDTH=640 HEIGHT=480
style="vertical-align:left; margin-left:-10px; margin-top:-15px;"
CLASSID="CLSID:75678BBA-5CB8-4C20-9976-E9D23688C164">
<PARAM NAME="OPCServer" VALUE="localhost">
<PARAM NAME="OPCNodeEntry" VALUE="Zentr_PSS">
<PARAM NAME="OPCRoot" VALUE="Zentr_PSS_OPC">
<PARAM NAME="ViewLanguage" VALUE=8>
<PARAM NAME="ViewSettings" VALUE=1>
<PARAM NAME="OptQVGA" VALUE=0>

5-15
<PARAM NAME="UseKeyboard" VALUE=1>

<PARAM NAME="SelectedFont" VALUE="Arial">
<PARAM NAME="FontSize" VALUE="14">
<PARAM NAME="AllowFiltration" VALUE=0>
<PARAM NAME="FiltrationActive" VALUE=0>
<PARAM NAME="FilterCriterion" VALUE="">
<PARAM NAME="ReportDisplay" VALUE=20>
<PARAM NAME="Layout" VALUE=0>
<PARAM NAME="HeightPane1" VALUE=35>
<PARAM NAME="WidthPane1" VALUE=50>
<PARAM NAME="WidthPane2" VALUE=50>
<PARAM NAME="LineHeightFactor" VALUE="2">
<PARAM NAME="EvtCol1" VALUE=0>
<PARAM NAME="EvtColWidth1" VALUE=120>
<PARAM NAME="RmdCol1" VALUE=0>
<PARAM NAME="RmdColWidth1" VALUE=120>
<PARAM NAME="ReportColWidth1" VALUE=20>

5-16

</OBJECT>
</body>
</html>
This HTML file can be configured as follows:

` <body scroll=no>
Switches off Internet Explorer's vertical scroll bar.
` WIDTH=a; HEIGHT=b
Size of the window in which the PVIS ActiveX Control is displayed, in
pixels.
` style="vertical-align:left; margin-left:-10px; margin-top:-15px;"
Aligned left, -10 pixels from left margin and -15 pixels from top margin
for better presentation
` CLASSID="CLSID:75678BBA-5CB8-4C20-9976-E9D23688C164"
Class-ID of PVIS Active X
General properties of PVIS ActiveX:

` "OPCServer"
The IP address or logical name of the PVIS OPC Server. "localhost" is
the valid logical name when the PVIS OPC Server and the PVIS Ac-
tiveX Control are on the same computer.
` "OPCNodeEntry"
Name of the OPC project, as defined via the OPC Configurator.
` "OPCRoot"
Name of the device project
` "ViewSettings"
Window format
– 0 = "single window"
– 1 = "split window"
– 2 = "event view"
` "OptQVGA"
Screen output optimised for QVGA format
– 0 = not activated
– 1 = activated

5-17
` "ViewLanguage"
Language of the diagnostic texts
– 0 = Afrikaans
– 1 = Albanian
– 2 = Danish
– 3 = Dutch
– 4 = English
– 5 = Estonian
– 6 = Finnish
– 7 = French
– 8 = German
– 9 = Icelandic
– 10 = Italian
– 11 = Norwegian
– 12 = Portuguese
– 13 = Spanish
– 14 = Swedish
– 15 = Chinese
– 16 = Japanese
` "UseKeyboard"
Keyboard operation
– 1 = activated
` "FontSize"
Font size in points
` "SelectedFont
Name of font as it appears on the PC
(not the font's file name)
` FilterCriterion
Filter criterion (see section on "Filtering" for details of syntax)
` FiltrationActive
Filter activated
– 1 = activated
` AllowFiltration
Filtering permitted
– 0 = not permitted
– 1 = permitted
Properties for split window display:

` Layout
– 0 = corresponds to layout 1 (horizontal split)
– 1 = corresponds to layout 2 (horizontal and vertical split)

5-18
` HeightPane1
– Layout 1: Height of event window as a percentage
– Layout 2: Height of event and event image window as a percentage
` HeightPane2
– Layout 1: Height of remedy window as a percentage
– Layout 2: Height of remedy and remedy image window as a percent-
age
` HeightPane3
– Layout 1: Height of event image and remedy image window as a per-
centage
– Layout 2: Has no effect, but must be 0
` WidthPane1
– Layout 1: Width of event image window as a percentage
– Layout 2: Width of event and remedy window as a percentage
` WidthPane2
– Layout 1: Width of remedy image window as a percentage
– Layout 2: Width of event image and remedy image window as a per-
centage
` LineHeightFactor
– e.g. "3" (in inverted commas)
With the "Layout" property, please note the following:

` The properties "HeightPane1", "HeightPane2" and "HeightPane3"
must be stated.
` With layout 2, "HeightPane3" must = 0.
` The sum of the values of "HeightPane1", "HeightPane2" and
"HeightPane3" must be 100.
` "WidthPane1" and "WidthPane2" are optional, but:
– Either both parameters are stated, or none at all.
– The sum of the values of "WidthPane1" and "WidthPane2" must be
100.
Properties for split window 2 display:

` EvtColN (N columns from 1 to 9: EvtCol1, EvtCol2 to EvtCol9)
– 0 = Timestamp
– 1 = Priority icon
– 2 = Priority text
– 3 = Scope
– 4 = Event
– 5 = Device
– 6 = Equipment ID
– 7 = Address
– 8 = Location description
– -1 = Invisible column

5-19
` EvtColWidthN (N columns from 1 to 9: EvtColWidth1, EvtColWidth2 to

EvtColWidth9)
Column width in pixels
` RmdColN (N columns from 1 to 6: RmdCol1, RmdCol2 to RmdCol6)
– 0 = Responsibility
– 1 = Remedy for selected event
– 2 = Device
– 3 = Equipment ID
– 4 = Address
– 5 = Location description
– -1 = Invisible column
` RmdColWidthN (N columns from 1 to 6: RmdColWidth1,
RmdColWidth2 to RmdColWidth6)
Column width in pixels
With the properties for the events, please note the following:
` The "EvtColN" properties are optional.
– However: Either none of these properties are stated, or all of them
are.
– If the "EvtColN" properties are stated, then all the "EvtColWidthN"
properties must also be stated.
` The "RmdColN" properties are optional.
– However: Either none of these properties are stated, or all of them
are.
– If the "RmdColN" properties are stated, then all the "RmdCol-
WidthN" properties must also be stated.
` The respective values 0 to 8 and 0 to 5 must be unique.
` The value -1 must always be assigned to the highest column number.
Example: Last three columns are to be invisible.
` Correct configuration:
– RmdCol1=3
– RmdCol2=2
– RmdCol3=1
– RmdCol4=-1
– RmdCol5=-1
– RmdCol6=-1
` Incorrect configuration:
– RmdCol1=3
– RmdCol2=2
– RmdCol3=1
– RmdCol4=-1
– RmdCol5=4
– RmdCol6=5

5-20
The "ReportColWidthN" properties are used to define the width of the

columns in the event log table in the "Event Log" view. The values are
stated in pixels. The order of the columns cannot be modified.
` ReportColWidth1
– Contents: "In/out" icon
` ReportColWidth2
– Contents: Timestamp
` ReportColWidth3
– Contents: Priority icon
` ReportColWidth4
– Contents: Priority
` ReportColWidth5
– Contents: Scope
` ReportColWidth6
– Contents: Event
` ReportColWidth7
– Contents: Device
` ReportColWidth8
– Contents: Equipment ID
` ReportColWidth9
– Address
` ReportColWidth10
The HTML file can be started automatically once the PMI has booted.
The following additional lines are required in the "PMIStart.cmd" file in
order to do this:
copy \IPSM\PVIS_ActiveX_DE_Resources.dll \windows

copy \IPSM\PVIS_ActiveX_EN_Resources.dll \windows
start \windows\iexplore.exe \IPSM\<Name of HTML file>
If you are using additional languages, you will need to incorporate the re-
source files for these languages at this point (with "FR", "IT", "NL" etc.
in the file name instead of "DE").
Replace the <Name of HTML file> marker with the name of the HTML file
on your PMI.
To start Internet Explorer in full screen mode you will need to create the
following entry in the Windows registry:
` Enter "regedit" and click OK to open the registry.
` Go to "HKEY_CURRENT_USER\Software\Microsoft\Internet Explor-
er\Main"

5-21
` Right-click on Main, then select New and Key.

` Create the key "StartUpInFullScreen" and assign the key the value "1".
` Save and then close the Windows registry.

5-22
6 Namespace
6.1 Basics
6.1.1 Definition of symbols

6000
6100
Basics
6.1
6-
Namespace
Definition of symbols
6-
The following symbols are used in the diagrams and tables:

` Names in angle brackets (<...>) are markers and are replaced by the
respective name. <OPCProjectName>, for example, becomes My-
Project.
` Small numbers below a box signify the possible number of nodes. "1
.. 2" means that up to two nodes are available. The infinity symbol (∞)
means that the number of nodes is open, in other words, you can have
as many nodes as you like. The actual number of nodes depends on
the configuration of the OPC project.
` "PSS" printed above a box means that these nodes and everything
below them are only valid for the PSS. "PNOZ" printed above a box
means that these nodes and everything below them are only valid for
the PNOZmulti.
The namespace is a memory area in which the PVIS OPC Server stores
all the diagnostic data and process data from the connected control sys-
tems. For the most part the namespace can be viewed using the brows-
er of an OPC Client.
Further information on versions can be found under "Supported hard-

ware and software" in the chapter entitled "Diagnostics and visualisation
with PVIS".
The PVIS ActiveX Control automatically reads the diagnostic data from
the namespace and displays it for the user. Users themselves must pro-
gram access to the process data.
Within the namespace there is read/write access to the variables of the

PSS ST section. Access to all other variables is exclusively read-only.
In the following section the namespace is represented in a tree structure.

The display format may vary depending on the browser. However, the
structure remains the same. The higher-level nodes are used for data
structuring. The data is exclusively found on the lowest level.

6-1
6 Namespace
6.2 Structure of the namespace
6.2.1 OPCProjectName
6.2
Structure
6200
6- of the namespace
6-
OPCProjectName
SummaryInformation
OverviewInformation
DetailInformation
Generic
<OPCProjectName> <DeviceProjectName>
PSS
1 ..
8
Symbolic
EventLog
Licence
Versions
Fig. 6-39: <OPCProjectName>
Node name Contents

<OPCProjectName> Name of the OPC project
Example: "MyProject"
<DeviceProjectName> Name of the device project
Example: "MyDevice"

6-2
6 Namespace
6.2.2 SummaryInformation
6-
SummaryInformation
Event Collective
Process
Error
Device
Communication
Collective
SummaryInformation
Process
Warning
Device
Communication
Collective
Process
Status
Device
Communication
Fig. 6-40: <OPCProjectName>/<DeviceProjectName>/SummaryIn-

formation

6-3
6 Namespace
Node name Contents

SummaryInformation Information on whether there are any entries in the event list,
what priority class they are and which area is affected.
Event Indicates whether an event has occurred.
FALSE = No event occurred
TRUE = Event occurred
Error Information on event messages with "Error" priority class
Collective Indicates whether there is an event message of the "Error" pri-
ority class.
FALSE = No error
TRUE = Error
Process Indicates whether there is an event message of the "Error" pri-
ority class within the "Process" scope.
Device Indicates whether there is an event message of the "Error" pri-
ority class within the "Plant/device" scope.
Communication Indicates whether there is an event message of the "Error" pri-
ority class within the "Communication" scope.
Warning Information on event messages with "Warning" priority class
Collective Indicates whether there is an event message of the "Warning"
priority class.
FALSE = No warning
TRUE = Warning
Process Indicates whether there is an event message of the "Warning"
priority class within the "Process" scope.
Device Indicates whether there is an event message of the "Warning"
priority class within the "Plant/device" scope.
Communication Indicates whether there is an event message of the "Warning"
priority class within the "Communication" scope.
Status Information on event messages of the "Status information" pri-
ority class
Collective Indicates whether there is an event message of the "Status in-
formation" priority class.
FALSE = No status information
TRUE = Status information
Process Indicates whether there is an event message of the "Status in-
formation" priority class within the "Process" scope.
Device Indicates whether there is an event message of the "Status in-
formation" priority class within the "Plant/device" scope.
Communication Indicates whether there is an event message of the "Status in-
formation" priority class within the "Communication" scope.

6-4
6 Namespace
6.2.3 OverviewInformation
6-
OverviewInformation
CentralDevices
PSS
SafetyBUSp
OverviewInformation
SafetyDevices
Operands
Fig. 6-41: <OPCProjectName>/<DeviceProjectName>/OverviewIn-

formation
Node name Contents

OverviewInformation Information on the central devices (PSS), modules (PNOZ), SafetyBUS p (PSS),
safety devices and operands

6-5
6 Namespace
6.2.4 CentralDevices
6-
CentralDevices
CentralDevices <Slot> Status

PSS: 1 ..
8
PNOZ: -6 .. 8
PSS
SafetyBUSp
OverviewInformation
SafetyDevices
Operands

formation/CentralDevices
Node name Contents

CentralDevices Information on central devices (PSS) or modules (PNOZ)
<Slot> Slot number of the central device (PSS) or module (PNOZ)
Example: "3"
Status Bit 0: Indicates whether an event occurred for this device or module and was en-
tered in the event list.
FALSE = No event

6-6
6 Namespace
6.2.5 PSS: SafetyBUSp

PSS: SafetyBUSp
6-
CentralDevices Interfaces
PSS
SafetyBUSp IOGroups
OverviewInformation
SafetyDevices Subscribers
Operands

formation/SafetyBUSp
Node name Contents

SafetyBUSp Information on SafetyBUS p

6-7
6 Namespace
6.2.6 PSS: Interfaces

PSS: Interfaces
6-
Interfaces <InterfaceNumber> Status

1 .. 2
PSS
SafetyBUSp IOGroups
Subscribers

formation/SafetyBUSp/Interfaces
Node name Contents

Interfaces Information on SafetyBUS p interfaces
(SafetyBUS p 0 / SafetyBUS p 1)
<InterfaceNumber> Number of the SafetyBUS p interface
Example: "0" or "1"
Status Bit 0: Indicates whether an event occurred for this SafetyBUS p interface and was
entered in the event list.
FALSE = No event

6-8
6 Namespace
6.2.7 PSS: IOGroups

PSS: IOGroups
6-
Interfaces
PSS
SafetyBUSp IOGroups <IOGroupNumber> Status

0 .. 31
100 .. 131
Subscribers

formation/SafetyBUSp/IOGroups
Node name Contents

IOGroups Information on I/O-Groups
<IOGroupNumber> Number of I/O-Group
Example: "12"
Status Bit 0: Indicates whether an event occurred for this I/O-Group and was entered in
the event list.
FALSE = No event

6-9
6 Namespace
6.2.8 PSS: Subscribers

PSS: Subscribers
6-
Interfaces
PSS
SafetyBUSp IOGroups
Status
Subscribers <DeviceAddress>
1 ..
8
Active

formation/SafetyBUSp/Subscribers
Node name Contents

Subscribers Information on bus subscribers
<DeviceAddress> Bus subscriber's device address
Example: "95"
Status Bit 0: Indicates whether an event occurred for this bus subscriber and was entered
in the event list.
FALSE = No event
Active Bit 0: Indicates whether the bus subscriber is actively involved in bus traffic.
FALSE = Inactive
TRUE = Active

6-10
6 Namespace
6.2.9 SafetyDevices
6-
SafetyDevices
CentralDevices
PSS
SafetyBUSp
OverviewInformation
SafetyDevices <NR> Status

1 ..
8
Operands

formation/SafetyDevices
Node name Contents

SafetyDevices Information on safety devices
<NR> PSS: Safety subroutine number, SSNR
PNOZ: Connection point, safety block's element ID
Example: "1"
Status Bit 0: Safety device inactive
FALSE = Active
TRUE = Inactive
Bit 1: Safety device triggered
FALSE = Not triggered
TRUE = Triggered
Bit 2: Safety device ready for reset
FALSE = Not ready for reset
TRUE = Ready for reset
Bit 3: Function test
FALSE = Not required
TRUE = Required
Bit 4: User error
FALSE = None present
TRUE = Present
Bit 5: Feasibility error
TRUE = Present
Bit 6 – Bit 14: Reserved
Bit 15: Device error
TRUE = Present

6-11
6 Namespace
6.2.10 Operands
6-
Operands
CentralDevices
SafetyBUSp
OverviewInformation
SafetyDevices
Operands <AbsoluteAddress> Status

1 ..
8
formation/Operands
Node name Contents

Operands Information on the operands for which operand diagnostics are configured.
<AbsoluteAddress> PSS: Operand address
PNOZ: Operand ID
Example: "MW 064.16"
Status Bit 0: Indicates whether an event has been entered for this operand in the event
list.
FALSE = No event

6-12
6 Namespace
6.2.11 DetailInformation
6-
DetailInformation
SummaryInformation
OverviewInformation EventList
PSS
DetailInformation SystemInfo
PNOZ
Generic SystemInfo
PSS
Symbolic
EventLog
Fig. 6-49: <OPCProjectName>/<DeviceProjectName>/DetailInfor-

mation
Node name Contents

DetailInformation Event list: Version information for the diagnostic configuration and device projects

6-13
6 Namespace
6.2.12 EventList
6-
EventList
Timestamp
Priority
Scope
Description
Event
DeviceName
EventList Event<Number>
10 EquipmentID
Actions LocationDescription
Parameter
Image1
Image2

mation/EventList

6-14
6 Namespace
Node name Contents

EventList Event list containing the 10 most current events
Event<Number> Event number
Example: "Event 8"
Event Details of the event
Timestamp Time stamp
Priority Priority
Scope Scope
Description Description
DeviceName Device name
EquipmentID Equipment identifier (Equip ID)
LocationDescription Location description
Parameters Precise information on where an event occurred, e.g. information on the input ter-
minal ("E3.0")
Image1 Information on the path in which the first image belonging to an event is stored.
Example: "OPCProject/visu/links/Pic123a.jpg"
Image2 Information on the path in which the second image belonging to an event is stored.

6-15
6 Namespace
6.2.13 Actions
6-
Actions
Scope
Responsability
Event Description
Event<Number> DeviceName
10
Actions Action<Number> EquipmentID

8
LocationDescription
Parameter
Image1
Image2

mation/EventList/Event<Number>/Actions

6-16
6 Namespace
Node name Contents

Actions Actions for an event
<ActionNumber> Action number
Example: "Action 5"
(8 nodes)
Scope Scope
Responsibility Responsibility
LocationDescription Location description
Parameter Precise information on where an action is to be performed, e.g. information on the
input terminal ("E3.0")
Image1 Information on the path in which the first picture belonging to an action is stored.
Image2 Information on the path in which the second picture belonging to an action is
stored.
6.2.14 SystemInfo
6-
SystemInfo
EventList
DiagnosticConfig_1
DetailInformation PSS
SystemInfo
FSProgram
PNOZ
SystemInfo

mation/SystemInfo
Node name Contents

SystemInfo (PSS) Version information for the PSS project and diagnostic configuration
SystemInfo (PNOZ) Version information for the PNOZmulti project and diagnostic configuration

6-17
6 Namespace
6.2.15 PNOZ: PNOZmultiProject

PNOZ: PNOZmultiProject
6-
PSS
DiagnosticConfig
SystemInfo ProjectName
PNOZ
DiagnosticConfig
CRC

mation/SystemInfo/DiagnosticConfig
Node name Contents

DiagnosticConfig Node for data via the PNOZmulti program
ProjectName Name of the project to which the program belongs
CRC Program's CRC check sum

6-18
6 Namespace
6.2.16 PNOZ: DiagnosticConfig

PNOZ: DiagnosticConfig
6-
Name
DiagnosticConfigPNOZmulti VersionInfo
Status
PNOZ
DiagnosticConfig Integrity
Name
DiagnosticConfigDisplayUnit VersionInfo
Status

Node name Contents

DiagnosticConfig Node for all "Integrity" type nodes (see below)
Integrity Node for all PNOZmulti program sections
DiagnosticConfigPNOZmulti Node for all the diagnostic configuration data belonging to the PNOZmulti
Name Name of the project to which the program belongs
VersionInfo Time stamp on the download
Status Integrity information for the diagnostic configuration:
0 = The diagnostic configuration is in order.
1 = The diagnostic configuration belongs to another project.
2 = There is no information on the current diagnostic configuration.
4 = The diagnostic configuration is obsolete.
DiagnosticConfigDisplayUnit Node for all the diagnostic configuration data belonging to the visualisation device
Name See DiagnosticConfigPNOZmulti-Name/VersionInfo/Status
VersionInfo
Status

6-19
6 Namespace
6.2.17 PSS: DiagnosticConfig

PSS: DiagnosticConfig
6-
Name
FSProgram VersionInfo
Status
Name
STProgram VersionInfo
Status
PSS
DiagnosticConfig Integrity
Name
DiagnosticConfigPSS VersionInfo
Status
Name
DiagnosticConfigDisplayUnit VersionInfo
Status


6-20
6 Namespace
Node name Contents

DiagnosticConfig Version information for the diagnostic configuration
Integrity Information on the integrity test
FSProgram Information on the FS program
Name Name of the project to which the FS program belongs
VersionInfo Time stamp at the time the FS program was downloaded to the
PSS
Status Integrity information for the PSS FS program:
0 = The FS program is in order.
1 = The FS program belongs to another project.
2 = There is no information on the FS program.
4 = The FS program is obsolete.
STProgram Information on the ST program
Name Name of the project to which the ST program belongs
VersionInfo Time stamp at the time the ST program was downloaded to the
PSS
Status Integrity information for the PSS ST program:
0 = The ST program is in order.
1 = The ST program belongs to another project.
2 = There is no information on the ST program.
4 = The ST program is obsolete.
DiagnosticConfigPSS Information about the diagnostic configuration on the PSS
Name Name of the project to which the diagnostic configuration be-
longs
VersionInfo Time stamp at the time the diagnostic configuration was
downloaded to the PSS
0 = The diagnostic configuration is in order.
1 = The diagnostic configuration belongs to another project.
2 = There is no information on the current diagnostic configu-
ration.
4 = The diagnostic configuration is obsolete.
DiagnosticConfigDisplayUnit Information about the diagnostic configuration on the PVIS
OPC Server
Name Name of the project to which the diagnostic configuration be-
longs
VersionInfo Time stamp at the time the diagnostic configuration was
downloaded to the PVIS OPC Server
0 = The configuration is in order.
1 = The configuration belongs to another project.
2 = There is no information on the current configuration.
4 = The configuration is obsolete.

6-21
6 Namespace
6.2.18 PSS: FSProgram

PSS: FSProgram
6-
Name
DetailInformation
FSProgram LinkTime
PSS
SystemInfo
DiagnosticConfig CRC
PNOZ
SystemInfo

mation/SystemInfo/FSProgram
Node name Contents

FSProgram Version information for the FS program
Name Name of the project to which the FS program belongs
LinkTime Time stamp at the time the FS program was linked.
CRC FS program's CRC sum

6-22
6 Namespace
6.2.19 Generic process data access

Generic process data access
6-
SummaryInformation
OverviewInformation
DetailInformation
Generic
PSS
1 ..
8
Symbolic
EventLog
Licence
Versions
Fig. 6-57: <OPCProjectName>/<DeviceProjectName>/Generic
Node name Contents

Generic Access to the process data via absolute addresses
From "Generic", it is impossible to navigate the namespace using a

browser. Navigation is only possible by entering a path, if one is con-
figured.
Example of full path information:

"Namespace1/Project1/Generic/FS/E/3.01"

6-23
6 Namespace
6.2.20 PNOZ: Generic

PNOZ: Generic
6-
I <BitAddress>
O <BitAddress>
IW <WordAddress>
Generic
OW <WordAddress>
Ivirtual <BitAddress>
Ovirtual <BitAddress>
Fig. 6-58: <OPCProjectName>/<DeviceProjectName>/Generic
Node name Contents

I/<BitAddress> Input bits
Example: "I/3.1"
O/<BitAddress> Output bits
Example: "O/-4.1"
IW/<WordAddress> Input words and channel number (0 or 1)
Example: "IW/3.0"
OW/<WordAddress> Output words and channel number (0 or 1)
Example: "OW/1.1"
Ivirtual/<BitAddress> Input bits
Example: "Ivirtual/0.1"
Ovirtual/<BitAddress> Output bits
Example: "Ovirtual/0.5"

6-24
6 Namespace
6.2.21 PSS: Generic/FS and Generic/ST

PSS: Generic/FS and Generic/ST
6-
FS
PSS
Generic
ST
Fig. 6-59: <OPCProjectName>/<DeviceProjectName>/Generic/FS
Node name Contents

FS FS section data
ST ST section data. The data structure is identical to that of the FS section.

6-25
6 Namespace
6.2.22 PSS: Generic/FS

PSS: Generic/FS
6-
E <BitAddress>
EB <ByteAddress>
EW <WordAddress>
A <BitAddress>
AB <ByteAddress>
AW <WordAddress>
FS M <BitAddress>
MB <ByteAddress>
MW <WordAddress>
DB <DBnr> DW <DataWordNumber>
T <TimerNumber>
Z <CounterNumber>
ZW <CounterNumber>
Fig. 6-60: <OPCProjectName>/<DeviceProjectName>/Generic/FS

6-26
6 Namespace
Node name Contents

E/<BitAddress> Input bits
Example: "E/3.01"
EB/<ByteAddress> Input bytes
Example: "EB/3.08"
EW/<WordAddress> Input words
Example: "EW/3.00"
A/<BitAddress> Output bits
Example: "A/4.01"
AB/<ByteAddress> Output bytes
Example: "AB/4.08"
AW/<WordAddress> Output words
Example: "AW/4.16"
M/<BitAddress> Flag bits
Example: "M/64.06"
MB/<ByteAddress> Flag bytes
Example: "MB/64.08"
MW/<WordAddress> Flag words
Example: "MW/64.16"
DB/<DBno>/DW/ Data words
<DataWordNumber> Example: "DB/10/DW/45"
T/<TimerNumber> Timer status
Example: "T/64"
Z/<CounterNumber> Counter status
Example: "Z/65"
ZW/<CounterNumber> Counter word
Example: "ZW/65"

6-27
6 Namespace
6.2.23 PSS: Symbolic process data access

PSS: Symbolic process data access
6-
FS <Tag> Value
1 ..
8
PSS
Symbolic
ST
Fig. 6-61: <OPCProjectName>/<DeviceProjectName>/Symbolic
Node name Contents

Symbolic Access to the PSS process data via symbolic names
FS FS section data.
ST ST section data. The data structure is identical to that of the FS section.
<Tag> Tag that was defined for the operand in the allocation table.
Example: "Switch_1"
Value Content of operand

6-28
6 Namespace
6.2.24 EventLog
6-
EventLog
Event <Number>
0 .. n
Number
EventLog
Reset
Save
Fig. 6-62: <OPCProjectName>/<DeviceProjectName>/EventLog

6-29
6 Namespace
Node name Contents

EventLog Access to the event log
Event<Number> Access to the individual events on the event log
Example: "Event 499"
The entries for the events are character strings. The individual pieces of informa-
tion are separated by a <tab>:
The maximum number of events is configurable.
IO <<+>>: New event message
<<->>: Event message cleared
Timestamp Time stamp
Priority Priority
PriorityText Description of priority
Scope Scope
EquipmentDescription Location description
Parameter Precise information on where an event occurred.
Example:
<<+>><tab>2007-03-19 14:45<tab>12<tab>Warning<tab>Scope1<tab>Event 2
has occurred<tab>Device 23<tab>Equip-ID 7<tab>Location<tab>Terminal E3.0
Number Number of events in the event log
Reset Deleting the event log:
0 = Do not delete event log.
1 = Delete the event log.
The bit is set by the OPC Client and downloaded to the PVIS OPC Server.
Save Saving the event view in an export file:
<Name of export file > = Event view is saved.
The file name of the export file is set by the OPC Client and downloaded to the
PVIS OPC Server. If a file of the same name already exists, it will be overwritten
The export file is saved in the root directory of the data belonging to the OPC
project. Alternatively, an absolute or relative path to the file's storage location can
also be entered under <Name of export file>.
From "EventLog", it is impossible to navigate the namespace using a

browser. Navigation is only possible by entering a path. If the event log
in the PVIS OPC Configurator is switched off, it cannot be accessed
within the namespace. Example of full path information:
"Namespace1/Project1/EventLog/Event 499"

6-30
6 Namespace
6.2.25 Licence and versions

Licence and versions
6-
1 .. Licence Info
8
Versions PilzOPCServerDA
Fig. 6-63: <OPCProjectName>/<DeviceProjectName>/Licence und

<OPCProjectName>/<DeviceProjectName>/Versions
Node name Contents

Licence Information about the licensing of the PVIS OPC Server
Info Licence
Versions Information about the version number of the PVIS OPC Server
PilzOPCServerDA Version

6-31
6 Namespace

6-32
7 Applications
7.1 PSS diagnostics on a PMImicro diag
7.1.1 Create diagnostic configuration

7000diagnostics on a PMImicro diag
7.1
Applications
PSS
7100
7-
Create diagnostic configuration

7-
The diagnostic configuration is project-related, i.e. you will need to cre-

ate a separate diagnostic configuration for each PSS project.
The diagnostic configuration is valid for both the ST and FS section and
can be created when PSS WIN-PRO is in either FS or ST mode.
Steps:
` Select diagnostic language
` Define priorities
You will only need to perform this step if you wish to change the prior-
ities pre-defined by Pilz or if you wish to define your own priorities.
` Define scopes
You will only need to perform this step if you wish to change the
scopes pre-defined by Pilz or if you wish to define your own scopes.
` Define responsibilities
You will only need to perform this step if you wish to change the re-
sponsibilities pre-defined by Pilz or if you wish to define your own re-
sponsibilities.
` Configure diagnostic types
You will only need to perform this step if you are creating an operand's
diagnostic configuration or if you wish to create your own "Safety de-
vice" diagnostic types.
` Edit diagnostic table
diagnostic configuration or a diagnostic configuration for safety devic-
es.
` Define device name and Equip ID
You will only need to perform this step if your own device names are
to be displayed during device diagnostics rather than the device
names pre-defined by Pilz, or if the devices' Equip IDs are also to be
displayed.
` Enter location information
It is not absolutely essential to enter location information. If you do not
enter your own information, some default entries will be used or the
corresponding errors will remain blank when the event messages and
remedies are displayed.
` Link diagnostic configuration
The diagnostic configuration must be linked before it is downloaded to
the PSS.
The diagnostic configuration can now be downloaded to the PSS and

display unit.

7-1
7 Applications
7.1 PSS diagnostics on a PMImicro diag
7.1.2 Download the diagnostic configuration to the PSS

Download the diagnostic configuration to the PSS
7-
The diagnostic configuration must be downloaded to the PSS and to the

diagnostic unit. Exception: If you are only running device diagnostics,
you only have to download the diagnostic configuration to the diagnos-
tic unit. The diagnostic configuration can be downloaded in FS mode or
ST mode. Once the diagnostic configuration is downloaded to the PSS,
diagnostics are run on the PSS automatically. In other words, all availa-
ble components in the diagnostic configuration are switched on. If the
diagnostic configuration does not contain a diagnostic configuration for
safety devices, for example, diagnostics for the safety devices are auto-
matically switched off. Device diagnostics are always switched on, as
they are part of the PSS operating system and as such are always avail-
able. The running of the individual diagnostic components (device diag-
nostics, diagnostics for safety devices and operand diagnostics) can be
switched off separately.
The diagnostic data is stored in non-retentive memory.
INFORMATION
If you are only using device diagnostics and are not download-
ing the diagnostic configuration to the PSS, you will need to
switch on the device diagnostics manually. This is described in
PSS WIN-PRO's online help.
7.1.3 Download the diagnostic configuration to the PMImicro diag

Download the diagnostic configuration to the PMImicro diag
7-
The diagnostic configuration is downloaded to the PMI m107 diag dis-

play unit using the PMImicro Configurator.
The steps you need to take to connect the PMImicro diag to a PSS and
to commission the device are described in the operating manual for the
PMI m107 diag.
Please also refer to the PSS operating manual.
The PSS is connected to the PMImicro diag using RS 232 or RS 485

download cable. This download cable is available as a PSS accessory.

7-2
7 Applications
7.2 PNOZmulti diagnostics on a PMImicro diag
7.2.1 Create diagnostic configuration

7.2
PNOZmulti
7200
7- diagnostics on a PMImicro diag
Create diagnostic configuration

7-
The diagnostic configuration is project-related, i.e. you will need to cre-

ate a separate diagnostic configuration for each PNOZmulti project.
Steps:
` Select diagnostic language
` Define priorities
You will only need to perform this step if you wish to change the prior-
ities pre-defined by Pilz or if you wish to define your own priorities.
` Define scopes
You will only need to perform this step if you wish to change the
scopes pre-defined by Pilz or if you wish to define your own scopes.
` Define responsibilities
You will only need to perform this step if you wish to change the re-
sponsibilities pre-defined by Pilz or if you wish to define your own re-
sponsibilities.
` Activate expanded diagnostics
You need to activate the PVIS expanded diagnostics first if you wish
to use the PVIS expanded diagnostics or if you want to create your
own diagnostic types during the configuration of elements. The diag-
nostic types can be activated independently.
` Configure diagnostic types
diagnostic configuration or if you wish to create your own "Safety de-
vice" diagnostic types. There are two different ways to configure the
diagnostic types. Both methods are equally valid. The diagnostic
types "Safety Device" and "Bit" can be modified or created in the di-
agnostic configurator or during the element configuration. A separate
element is available for the "Bit" diagnostic type: the "Diagnostic
Point". To ensure that PVIS expanded diagnostics are performed for
an element used in the configuration, the diagnostic type must be as-
signed to the element.
` Define device name and Equip ID
You will only need to perform this step if your own device names are
to be displayed during device diagnostics rather than the device
names pre-defined by Pilz, or if the devices' Equip IDs are also to be
displayed.
Finally, the diagnostic configuration must be downloaded to the PNOZ-

multi and to the display unit.

7-3
7 Applications
7.2 PNOZmulti diagnostics on a PMImicro diag
7.2.2 Download the diagnostic configuration to the PNOZmulti

Download the diagnostic configuration to the PNOZmulti
7-
Once the diagnostic configuration has been created it will need to be

downloaded to the PNOZmulti and diagnostic unit. Exception: If you
only wish to run device diagnostics, you only have to download the di-
agnostic configuration to the diagnostic unit. The diagnostic configura-
tion is downloaded to the PNOZmulti with the project.
Special configurators are used to download the diagnostic configuration

to the diagnostic unit. Please consult the operating manual for your dis-
play unit for information on which configurator to use. For example, the
PMImicro Configurator is used for the PMI m107 diag display unit. The
PVIS OPC Server uses the PVIS OPC Configurator.
Once the diagnostic configuration has been downloaded to the PNOZ-

multi, diagnostics on the PNOZmulti are run automatically.
The diagnostic configuration of another project can be imported into an

open project.
7.2.3 Download the diagnostic configuration to the PMImicro diag

Download the diagnostic configuration to the PMImicro diag
7-
The diagnostic configuration is downloaded to the PMI m107 diag dis-

play unit using the PMImicro Configurator.
The steps you need to take to connect the PMImicro diag to a PSS and
to commission the device are described in the operating manual for the
PMI m107 diag.
Please also refer to the PNOZmulti operating manual.
The PNOZmulti is connected to the PMImicro diag using an RS 232 0-

modem cable.

7-4
21 697-03, 2008-06 Printed in Germany
© Pilz GmbH & Co. KG, 2008
•… • www
In many countries we are www.pilz.com
represented by sales partners.
Please refer to our homepage • Technical support

for further details or contact our +49 711 3409-444
headquarters.
Pilz GmbH & Co. KG

Sichere Automation
Felix-Wankel-Straße 2
73760 Ostﬁldern, Germany
Telephone: +49 711 3409-0
Telefax: +49 711 3409-133
E-Mail: pilz.gmbh@pilz.de

PVIS Systemdescription

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PVIS Systemdescription

Uploaded by

Copyright:

Available Formats

PVIS

System Description – Item No. 21 697-03

Chapter 2 Diagnostics and visualisation with PVIS

Chapter 3 PVIS diagnostic configuration

Chapter 4 PVIS OPC Server

Pilz GmbH & Co. KG, Felix-Wankel-Straße 2, 73760 Ostfildern, Germany

4.4.4 Firewalls and security settings 4-39

Chapter 5 PVIS ActiveX Control

Pilz GmbH & Co. KG, Felix-Wankel-Straße 2, 73760 Ostfildern, Germany

6.2.20 PNOZ: Generic 6-24

Pilz GmbH & Co. KG, Felix-Wankel-Straße 2, 73760 Ostfildern, Germany

Pilz GmbH & Co. KG, Felix-Wankel-Straße 2, 73760 Ostfildern, Germany

1.1 Validity of documentation

This operating manual describes expanded PVIS diagnostics for all

This operating manual is valid for:

It is valid until new documentation is published.

This documentation is intended for instruction and should be retained

Pilz GmbH & Co. KG, Felix-Wankel-Straße 2, 73760 Ostfildern, Germany

1.2 Overview of documentation

The introduction is designed to familiarise you with the contents and

2 Diagnostics and visualisation with PVIS

This chapter explains the objective of expanded PVIS diagnostics and

3 PVIS diagnostic configuration

This chapter describes the components of the PVIS diagnostic configu-

4 PVIS OPC Server

5 PVIS ActiveX Control

This chapter illustrates the structure and contents of the namespace in

Pilz GmbH & Co. KG, Felix-Wankel-Straße 2, 73760 Ostfildern, Germany

2.1 Aim of diagnostics and visualisation

PVIS is a concept for expanded diagnostics. What does PVIS expanded

How is this achieved?

Pilz GmbH & Co. KG, Felix-Wankel-Straße 2, 73760 Ostfildern, Germany

2.2 Overview of the procedure

Diagnostic configurations can be created for all PVIS-compatible control

The diagnostic configuration contains event messages, which can be

The diagnostic configuration can be processed directly by a PVIS-com-

Diagnostic configuration Diagnostic configuration

Fig. 2-1: Diagnostics without PVIS OPC Server

The PVIS OPC Server is used to display event messages on a visualisa-

The PVIS OPC Server establishes a connection to the control systems,

PVIS ActiveX Control can be used to call up a control system's event

Pilz GmbH & Co. KG, Felix-Wankel-Straße 2, 73760 Ostfildern, Germany

2.2 Overview of the procedure

Diagnostic configuration With/without

Diagnostic configuration Namespace With/without

Pilz GmbH & Co. KG, Felix-Wankel-Straße 2, 73760 Ostfildern, Germany

2.3 Supported hardware and software

The functions of the PVIS expanded diagnostics are supported by the

Diagnostics on the PSS using PMImicro diag:

Diagnostics on the PNOZmulti using PMImicro diag:

Diagnostics on the PNOZmulti using the PVIS OPC Server:

Diagnostics on the PSS using the PVIS OPC Server:

Pilz GmbH & Co. KG, Felix-Wankel-Straße 2, 73760 Ostfildern, Germany

2.3 Supported hardware and software

Pilz GmbH & Co. KG, Felix-Wankel-Straße 2, 73760 Ostfildern, Germany

2.3 Supported hardware and software

Pilz GmbH & Co. KG, Felix-Wankel-Straße 2, 73760 Ostfildern, Germany

3000 diagnostic configuration

The control system's event messages can also be supplemented

With expanded diagnostics, a diagnostic unit (e.g. the PMImicro diag or

The diagnostic configuration consists of three independent parts:

The diagnostic configuration is project-related, i.e. a separate diagnostic

Pilz GmbH & Co. KG, Felix-Wankel-Straße 2, 73760 Ostfildern, Germany

Operands Diagnostic unit