Industrial Automation

The S7/S5 OPC Server V4.1x and the OPC Easy Connect Suite V2.x get licensed by the newest version of the license manager, the licence manager version 4. The license manager generates a PC-ID for the release. By entering your product key into the designated field and clicking onto the button “activate license”, your full version gets released. The license activation requires an internet-connection.

If your PC has no internet connection, the release has to be done from a PC with an internet connection. Therefore you have to do some steps in the license manager.

Procedure on the PC, on which the software shall be installed:

• In the box “Activate for this PC” there is a field “PC without internet connection”. In this field you have to click on the button “Export PC-IDs”
• Choose the BIOS line and save it to a file by marking “Save to file” and click “OK”
• Copy the generated file and transport it to the PC with internet connection

 
Procedure on the PC with internet connection:

• By clicking on the button “Import PC-ID from remote PC” in the box “Generate license file for remote PC” the generated file is imported to the license manager 4. The ID appears in the box now
• The Product-Key has to be set into the designated field
• By clicking on the button “Generate and export License file” a .lic file is generated

If the generation of the file is not possible, please check the settings of your proxy-server in the settings.

Last step on the PC without internet connection:

• Click on the button “Import license file” in the box “Activate for this PC”. In some cases you have to click on the button “Activate license”, to activate your license.

 You can release your software with an USB dongle, too. The procedure is similar to the licensing with software keys. The difference is that you don’t have a PC-ID for the authentication, but the serial number of the dongle (for further information see online help).

Softing OPC Servers are 32-bit applications that can be used on 64-bit systems in 32-bit mode without any limitations or performance reduction.

Background information from the German Wikipedia entry (translated excerpt):
The advantages of 64-bit CPUs include an easier calculation of large integer values. This offers benefits, for example, for encryption algorithms, graphical calculations (e.g. fixed point arithmetic for computer games), 64-bit file systems, or multimedia formats (MPEG2, MP3).

Another advantage over 32-bit architecture is that 64-bit systems can directly address more than four GB RAM. This is useful for applications with large memory requirements, such as video processing applications and database systems, provided they have been programmed for a 64-bit system. In most other applications – in particular, office applications – there is no subjectively noticeable speed advantage.

• Installation is not possible because of Microsoft XML DOM Parser.

• The attempt to establish a connection to an OPC-Server which is running as a service fails.

Note:
The hardlock driver blocks the access to the dongle when using Terminal Server or connecting through Remote Desktop! In these cases please use a software license key.

You can download the current Aladdin Hardlock driver from the website here:
www.esafe.com/support/hardlock/index.aspx

See application note: The License Manager fails to detect the hardware dongle (Aladdin Hardlock Key) license. Applications covered by the hardware key license indicate a demo version on startup of the computer.

The OPC Foundation provides the binaries needed to run DCOM OPC server and OPC client application as Windows Installer packages.
It is necessary to install the "OPC Core Components" on each machine where an OPC server or an OPC client is installed.
The latest version of the OPC Core Components Redistributables can be downloaded from the OPC Foundation web pages.

Yes this is possible. First, create the desired configuration file (.soc) with the OPC Demo Client. You can then access the OPC Demo Client with this configuration by specifying the  parameter load.

SOClient /load filename.soc

This parameter can be passed either in the command line or in the desktop from the context menu "Properties".

• The S7/S5 OPC Server can not read the S7 program files for newer version of Simatic S7 CPU types.

• Adding Customized web pages for visualization of values.

• How to use the integrated redundancy feature of the S7 OPC Server?
  

It depends on which version of the S7/S5 OPC Server you are using. The format of the configuration was changed between the versions 3.1x and 4.0x.
 
Version 3.1x:
In the previous version of the S7/S5 OPC Server, the configuration was stored partly in the registry and partly in different XML files.
The configuration for the NETLink PRO interface was stored in XML files located in the \NETLink folder of the S7/S5 OPC Server installation directory.
All other interface configurations were stored in the registry in the keys:
HKLM\Software\Deltalogic\AGLink
HKLM\Software\Softing\S7 OPC Server
 
Version 4.0x:
In the new version, the entire configuration is stored in XML files (*.XML) that reside in the OPC Server installation directory (C:\Program Files\Softing\S7S5OPCServer).

Where the alias files and Step7 projects are stored is user-specific.
When updating to version 4.0x, please note that the old configuration will be automatically converted to the new format.

Version 4.1x:The entire configuration is stored in XML files (*.XML). Standard file location:- Windows Vista, Windows 7, Windows Server 2008:   C:\ProgramData\Softing\S7S5OPCServer - Windows XP, Windows Server 2003:   C:\Document and Settings\All Users\Application Data\Softing\S7S5OPCServer

This error message in the trace file of the S7/S5 OPC Server indicates a possible communication overload between server and PLC. You can solve this problem by either increasing the update rate in the OPC client or reducing the number of polled items in a group.
 
You can get more details on this error by analyzing the Diagnostics web pages of the S7/S5 OPC Server (Cyclic Requests, Clients and PLC Connections). To access the Diagnostics pages, open the system tray application (right-click on the tray icon) and click “Show Web Pages”. Then log on as 'Administrator' (password 'ad').
 
Please note that you can only access the web pages when the OPC server is running.
The “Diagnostics | Cyclic Requests” page provides a list of all the cyclic read requests of the OPC clients.  If an OPC client creates items in the OPC server, an update rate is specified for the items of a group according the group's properties. This web page shows you the cyclic requests that are executed for all items of the OPC clients. The update rate should be at least the average value of the associated group on this page.
The update rate can only be set in the OPC client application you are using. When using the Softing OPC Demo Client, select the corresponding OPC group object in the tree on the left. Click the right mouse button, choose “Properties” from the context menu and set the update rate (a detailed description is provided in the Online Help under Softing OPC Demo Client -> DA Server access -> Displaying object properties).
If supported by your OPC client, you can also set an update rate of 0. This setting will cause the OPC server to retrieve the data from the PLC as fast as possible.

To read out data in KG format (Real) from an S5, you need to use the S7 syntax instead of the S5 syntax (e.g. DB8.DBD0 instead of DB8DD0).

I would like to measure electrical power and energy consumption at different points in my company. The measured data should be automatically displayed and processed in MS Excel. What simple setup could I use for this purpose?

The setup for measuring electrical power and energy values, and for visualizing them in MS Excel is described in the following PDF document:

Simple set-up for measuring of electrical power and energy including visualization in MS Excel (PDF)

PAC3200.xls

SoftingOpcClient_V1_30.xls

How can I activate the slave functionality of the Modbus/TCP OPC Server?

• How do I configure the Softing Modbus OPC Server to be able to access the data of a Modbus device?

The Item IDs of syntax items are structured in the following way:
[<Modbus/TCP Device Name[<:Modbus/TCP Port Number]>/][<Modbus Unit Identifier>.]<Modbus/TCP Address>[:<Data Type>][<Array Boundaries>]

Only the <Modbus/TCP Address> is mandatory. The other parts are optional.

<Modbus Unit Identifier>
The Modbus Unit Identifier in the Modbus/TCP device. In Modbus, the Unit Identifier is used to address multiple logic devices via one physical device. This functionality is mainly used for gateways (Modbus RTU -> Modbus TCP).
This part of the syntax is optional. The default value is "255"(0xFF).
Example with Modbus/TCP Device Name and Modbus/TCP Unit Identifier:
GatewayIP/1.300010

Devices that support the Modbus RTU protocol can only be addressed via a Modbus gateway. As the gateway combines multiple Modbus RTU devices into a single IP address, the devices must have different Modbus Unit IDs to allow the server to distinguish them. This means that the Modbus Unit Identifier always has to be specified for Modbus RTU devices. 

Devices that support the Modbus TCP protocol can be operated directly, without a gateway. In this case, the device description indicates whether the Modbus Unit Identifier is required, how it is set, and how it can be modified. Many Modbus TCP devices ignore the Unit Identifier, so that it does not have to be specified in these cases.

In the integrated Web interface, you can edit the trace settings of the OPC server and view the trace output.

• Detect devices: the configurator detects the slaves when you run the scanning process.
• Important: Delete the cyclic data container (CyclicData) of the slave whose address you want to change
• Then activate the configuration via the Toolbar (or context menu or F5). The PROFIBUS Master establishes a connection with the configured Slave.
• Change the desired station address. Highlight the slave whose address you want to change, open the context menu and select "Properties". A dialog box opens in which you can set the desired address. Click “Apply” to confirm your settings. After about 10 seconds the “Apply” button becomes grey which means the device address has changed. Click “OK” to close the dialog.  
• Deactivate the configuration
• Activate the configuration again.

The slave can now be accessed with its new address.

Please download and install the software patch from here LicenseManager_V306

There can generally only be one reason:
The PC's system time is changed.
This is done either by a program that changes the time due to incompatibility with the operating system (e.g. STEP5 V6.x under Win2000 - the product is not enabled for this combination) or by other programs that should actually synchronize the system time in the network, but lead to problems in that they change the system time for a minimal time (in most cases, users do not realize this because it easily goes unnoticed).

In any case, the time in the Logger has to be checked to see if the server really runs for 72h in demo mode or shorter.

After running for a while, the OPC server freezes. It then cannot be operated anymore and does not provide any data. All other programs on the PC and all other network functions continue to work as normal.

In all probability, a great many or all "Logger functions" have been activated in the OPC Server Logger. You might have verbose enabled. This may lead to the described effects on some PCs. If you disable Logger functions (default is "Show Errors"), the OPC server will run without freezing again.

In all probability, different TSAPs are used for the H1 connection. The CP535 HW3 (according to Siemens there is only one firmware version in HW3) has the effect that the TSAPs are swapped when the CP535 HW3 acknowledges the network connection. As a result, the PC closes the connection and no network connection is established.

How to solve the problem:
It is essential to enter identical TSAPs for communication with the CP535 HW3.

OPC/DDE communication with Siemens S7 controllers is normally done via default connections. This means that the connection parameter settings only have to be made on the OPC/DDE server side, not on the controller side (S7-CP):
In the OPC/DDE server, enable RFC1006 and select ISO-on-TCP (RFC1006). Here you need to enter the standard TSAPs in the HEX box:
Own TSAP: 01 00
Dest TSAP: 03 xy
(x = rack number multiplied by 2, where the first rack has rack number 0 / y = slot of the CPU)

An example is available for download as a PDF.

• Welche Einstellungen muss ich für den Zugriff über Standardverbindungen auf eine Siemens S7 vornehmen? 

In older versions, there was an error in the output of the STATUS for a correct connection. This has been corrected in the newer versions.
Now -1 (VT_I4) is output for a properly working connection.

This behavior may occur with Siemens CPs that have older firmware versions. For example, this problem occurs with a CP443-1 V2.0, whereas no errors occur with FW V2.6.

The Softing OPC Easy Connect Suite is a 32-bit application that can be used on 64-bit systems in 32-bit mode without restrictions or performance reduction.

Background information from the German Wikipedia entry (translated excerpt):
The advantages of 64-bit CPUs include an easier calculation of large integer values. This offers benefits, for example, for encryption algorithms, graphical calculations (e.g. fixed point arithmetic for computer games), 64-bit file systems, or multimedia formats (MPEG2, MP3).
Another advantage over 32-bit architecture is that 64-bit systems can directly address more than four GB RAM. This is useful for applications with large memory requirements, such as video processing applications and database systems, provided they have been programmed for a 64-bit system. In most other applications – in particular, office applications – there is no subjectively noticeable speed advantage.

• How to create and use a bidirectional OPC-Communication with OPC Tunnel?

• How to configure redundant server connections?

If EasyConnect OPC2Database is used on a 64Bit system it is essential, that the 32Bit version of the ODBC Database driver is installed. EasyConnect is not able to use 64Bit drivers.

It depends on which version of the OPC Easy Connect Suite you are using. Directory structure and configuration file names were changed between the versions 1.x and 2.x.
 
Version 1.x:

• file path: <installation directory> (C:\Program Files\Softing\OCT\)
• main configuration file: OCT.xml
• trace file: file name and directory are user defined (under Diagnostics).
• Storage: file name and path for storage items can be arbitrarily defined (default: <installation directory>Storage.txt)
• Task: Folder and file names for add-on DLLs can be arbitrarily defined (default: <installation directory>Mytask.txt)
• Subscription file: subscription configuration file name and path can be arbitrarily defined (default: <installation directory>MySubscription.txt)
• Filter file: Filter configuration file name and path can be arbitrarily defined (default: <installation directory>Filter.txt)

Version 2.x:

• file path: depends on the used operating system:

• main configuration file: OSF_Runtime.xml
• trace file: file name is user defined. Only the file name can be set (the path is the path of the instance)
• Storage: Storage renamed to Local Items, configuration file name and path are always relative to the main configuration file. (Path=".\LocalItems\LocalItems.txt")
• Task: folder and file names for add-on DLLs are fixed (Path=".\Tasks\Tasks.txt")
• Subscription file: subscription file name and path are always relative to the main configuration file (Path=".\Tasks\Subscriptions.txt")
• Filter file: filter file name and path are always relative to the main configuration file. (Path=".\Filters\Connection_2.txt"). The server connection name will be used as the name for the filter file.

Please use the menu items „Backup“ and „Restore“ in the Configurator (menu Configuration) for backup.

This error message is caused by missing or incorrectly installed OPC core components (OpcRcw is a class of the core components).
To solve the problem, please uninstall the OPC core components (if they are already installed) and then reinstall them.

The installer can be found in the /Retail/OPC folder on our installation CDs or as a download on the website of the OPC Foundation (www.opcfoundation.org) under → Downloads → Redistributables.

The server developed using the OPC Toolbox is launched more than once (e.g. by the Explorer and additionally by an OPC client).

This is a common DCOM problem. The OPC server is launched by different users (User / System). You can solve the problem by editing this server setting under Start / DCOM Settings. If the OPC Server is installed as a service, you can also edit the setting by selecting Control Panel → Services → Properties of the server → Launch the service as “This user.” In this case, the user has to be assigned a password.

OPC Toolbox Version 4.2x:
You either need a runtime license (or hardware key / dongle) or you need to enter the DesigntimeKey in the source code (“Activate” method). Please have a look at one of the provided samples that demonstrate how to invoke this method.

Softing ActiveX Controls:
You either need a runtime license (or hardware key / dongle) or you need to enter the DesigntimeKey in the source code (SoActivate method). Please also have a look at the help topic “Programmer’s Guide → Licensing and License Activation.”

If you want to debug into the OPC Toolbox, you will need the debug DLLs (xxxd.dll), which are not included with the Toolbox:

• Otbd.dll
• Tbcvs20xxd.dll (for c++)
• TBNxx.dll (for .NET, here without “d”)

Softing supplies only the release versions of the DLLs because the debug DLLs need to be created by the developers themselves. For this purpose, the Toolbox folder provides the appropriate projects, which you can open and compile in the desired version.
To debug, both DLLs used (API + core) need to be loaded into your project in the debug versions.

• ...\OPCToolbox\V42x\Windows\core\src\OTB\OTB_VS20xx.vcproj
  Results in the otbd.dll. This is the OPC Toolbox core.

• ...\OPCToolbox\V42x\Windows\C++\src\OPCToolboxC++_VS20xx.vcproj
  Results in the TBCVS20xxd.dll. This is the C++ API.

• ...\OPCToolbox\V42x\Windows\NET\src\OPCToolboxNET_VS20xx.vcproj
  Results in the TBNxx.dll. This is the .Net API.

Please also have a look at the help topic “Installation → Compiling the OPC Toolbox Core” and read the FAQ “What settings do I need for debugging the OPC Toolbox?”

• You need to compile the OPC Toolbox yourself (see help topic “Installation -> Compiling the OPC Toolbox Core”).
• For .NET:
  - Uncomment the “otbud.dll” in the “OTBFunctions.cs” file.
  - In the .NET project, check the “Enable unmanaged code debugging” check box.
  - TBN and OTB both have to be debug versions.
• For C++:
  - In the Project Linker -> input -> specify the debug dll (otbd.dll).
  - TBC and OTB have to have the same version (debug).
• Open the process explorer and check whether the correct DLLs are loaded.

You have developed an OPC server and installed it on a different computer. Now OPC clients cannot see this OPC server.

• The OPC core components have to be installed on the target computer, as well. Please open the task manager and check if the “OpcEnum.exe” process is running. If it isn't, you can download these components from www.opcfoundation.org and install them.
• The OPC server has to be registered on the target machine:
  MyServer.exe /regserver
• Check whether the DCOM settings have been correctly configured. Please ask for our DCOM brochure or use our EasyConnect software that helps you avoid DCOM problems.
• The OPC server has to be launched by the correct user.
  If the OPC server is registered as a service, the user under whose account the OPC server is started as a service still has to be configured. (Control Panel -> Administration Tools -> Services -> MyServer -> Properties -> Log On tab. Here, change the settings from “Local System account” to “This account”, select the user and assign a password.)

The “0x80004002 (E_NOINTERFACE)” error code is output if DaSession.write or DaSession.Read is called.

Read / Write operations on a session are only possible if the OPC server you are using supports the OPC Specification DA3. The above error code indicates that your server might only support DA2. In this case, please use only Subscription.read / Subscription.write  or Item.read / Item.write.

When a project is started on a 64-bit system, an error message like the following is displayed:
Failed to load TBN40.dll.

This problem is caused by a project setting in VisualStudio (Project settings -> Build -> Platform Target). If it is set to “AnyCPU” on a 64-bit system, the 64-bit version will be loaded. This will lead to an error because the Toolbox only supports 32 bits. Please change the setting to “x86” and recompile the project. In addition, open the API project (c:\Program files\Softing\OPCToolbox\V43x\Windows\NET\src\OPCToolboxNET_VS20xx.csproj), check the setting and, if required, compile all the versions of the API DLLs (Batch Build).

The project runs without problems on the development computer, but does not work when installed on a different computer.

The installation of an OPC project generally requires 2 DLLs from the Toolbox (TBx.dll and OTBx.dll), see online help under “Installation -> Installation of the created OPC-Application.”
If an installation is generated in VisualStudio, VisualStudio automatically detects the dependence on the TBx.dll, but unfortunately does not detect the dependence on the OTBx.dll, which depends on the TBx.dll.
Therefore, this DLL has to be manually added to the installation project.

The project runs without problems on the development computer, but fails to detect the license (shuts down automatically or runs only 90 minutes) when installed on a different computer.

Occurs after updates to the Toolbox (4.2x -> 4.3x). As the OTxx.dll is not detected automatically during generation, it has to be manually added to the installation. When the Toolbox is then updated, this DLL needs to be changed. Please check that all the DLLs of the installation use the correct versions of the two DLLs.

A project created with the Toolbox cannot connect to an OPC server, but the Demo Client can connect without any problems.

In the majority of cases, this problem is caused by the DCOM security settings. Preferably, they should be checked and corrected first.

The difference in behavior between the Demo Client and the OPC Toolbox lies in the configuration of the internal security settings. If you would like to use the same settings as the Demo Client, you can do this in the OTC.cpp file when invoking the “CoInitializeSecurity” method. After the change, you need to recompile the Toolbox (this is only possible if you have a source code license).

• Here, the Toolbox initializes RPC_C_IMP_LEVEL_IDENTIFY
• The Demo Client, however, uses RPC_C_IMP_LEVEL_IMPERSONATE

You have created an OPC Server using the Softing OPC-Toolbox. The developed OPC Server can be started by the OPC client but the Server does not exit when the Client closes the connection.

To terminate the OPC Server, you have to implement the method OpcServer::Shutdown in your code. The shutdown event is triggered by the toolbox when the last OPC client disconnects. Inside that method you have to implement the code, which closes your application.

• Installation of the OPC-Application on a target machine

install.bat might not work properly, if there are more than one network adapters present or if the adapter has an IPv6 address.
As workaround you should call the script with parameters:

install.bat <HostName> <UserDnsDomain> <IpAddress>

Please download and install the software patch s5vir122.exe from our download area.

Firmware version 1.03 or newer is installed in the S5-PCLink (check S5-LanManager).

Please download an update of the S5-LanManager from our web site. Replace the installed files (C:\Program Files\Softing\S5-PCLink\... ) with those from the S5LanManager_update.zip file.

On S5 PLCs of type S5U115-944 and -928B, the power sources needed by our S5-PCLink are often defective. This is indicated by a failure to connect to the PLC (green LED on S5-PCLink flashes once approx. every 4 seconds) or a broken connection at irregular intervals.

Pinging the S5-PCLink works.

Solution:
You will need a power source adapter that can be added between the PLC and the S5-PCLink, and provides the power sources.
Please contact our sales department if you need this adapter.

• Application Report – OPC Tunnel vs. DCOM Headache

Order our broschure "DCOM safety settings" free of charge

Although you can enter the same code again and thus re-activate the product, the activation is lost again when you exit and restart the program.
In all probability, an incorrect "licensekey.txt" path is given in the title bar of the program's license window.
Taking the OPC server (default) as an example, a correct path would be: C:\ProgramFiles\INAT\OPC Server Ethernet\license\licensekey.txt

How to solve the problem:
The following registry entry has to be deleted:
[HKEY_LOCAL_MACHINE\SOFTWARE\INAT\License]
"LicenseKey"="any path\\LICENSEKEY.TXT"
The "license_pfad_delete.reg" registry file attached as a ZIP file for download will do this automatically.
After a restart of the product, the correct "licensekey.txt" path is now given in the title bar of the license window. An activation code entered will be retained.