Configuring Lifebeat Monitoring for an OS Client

Configuring Lifebeat monitoring for an OS client is not difficult. There are several
steps that need to be taken. Here is an outline of those steps.
When in doubt, the online help for WinCC Manager is the best resource. Note
that specific PDF files can be access from the help system with regards to
DCOM, OPC and Lifebeat Monitoring.
The general sequence of steps to be taken are:
1. Create an OPC connection channel for the client to be monitored;
2. Add the client to the Lifebeat monitoring list in the Server OS in WinCC;
3. Verify the settings for DCOM on the client.

Creating the OPC Connection Channel

1. Open the server OS in WinCC Explorer.
2. Right Click on Tag Management and select “Add New Driver”
Choose OPC.chn to add an OPC Channel driver.

The action will create an OPC group where you create the OPC Channel
for connecting to the Client.
3. Right Click on the newly created OPC group and create a new connection
Name the connection something unique. It is best if you use the same
name as the client computer.

Select OK to create the connection channel.

4. Right click on the newly created connection and select Properties. In the
Connection Properties Window, click on the Properties button to set the
information for the connection.

5. Enter OPCServer.WinCC in the OPC Server Name text box.

6. Enter the name of the client computer you wish to monitor in the text box
“Run the server on another computer:”
7. If the OS Client is running, you may click the Test Server button to see if
the connection can be made between the machines. A successful
connection does not guarantee success.
8. Click OK on all the windows back to the WinCC Manager. You will see
the newly created connection (the connection name preceded by the @)
Creating the Lifebeat Monitor Connection
1. Open Lifebeat Monitoring on the server OS in WinCC Explorer.

2. Select the Add button to add another device to the lifebeat monitor list.
3. On the newly added row, double click on the Device Name column to
“ungray” the box. Enter in a new, unique name for the device. The same
name as the OPC channel is best – here OS_SRV1.
4. Double click on the Device Type column and select the device type.
OS/Client is chosen here.
5. Double Click on the Connection column. Available connections will
appear on the drop down list. Select the OPC channel you just created.
6. Select the Update button to regenerate the lifebeat monitor screen.

Upon completion of the update screen generation, lifebeat monitoring for

the client has been established. Both the Server OS and the client OS
must be recompiled and downloaded to their respective computers.
Verifying DCOM on the Client Computer
1. Verifying DCOM is not always necessary, however the author has seen
instances where the default client installation was not compatible with
Lifebeat Monitoring.
2. On the client computer, from the start bar, open Control Panel –
Administrative Tools – Component Services.
Expand out the component services tree to display the DCOM services
installed on the client computer.
If any windows pop up asking if you want to register DCOM components
to Windows, select Yes.
3. Navigate the DCOM component tree to OPCServer.WinCC.
4. Right click on OPCServer.WinCC and select Properties.

5. The most important detail is Authentication Level. If set to None, Lifebeat

monitoring will not work for that client.

Set the value to “Connect” from the drop down box.

6. Select the Security Tab to set access permissions.

By Default, only Everyone will be listed as permitted DCOM access users.

The online documentation recommends adding the users
ADMINISTRATORS, INTERACTIVE, NETWORK and SYSTEM.

This would be for avoiding any Windows user authentication issues or

privilege levels.
7. Do the same for Launch Permission.

8. Lifebeat monitoring should work.