This CNCnetPDM device driver for Siemens Sinumerik 840D SL and 828D controllers with OPC Unified Architecture (UA) enables you to monitor and output machine-, process- and quality data from machines with these controllers. It also allows you to change or write parameters and variables on these devices.
This driver supports all controllers running Sinumerik Operate version 4.5 (>= SP3), 4.7 and 4.8.
Note: Please use our CNCnetPDM Standard OPC UA Device driver for machine monitoring and control as it additionally allows event driven data acquisition, comes with enhanced certificate handling and supports all OPC UA security modes and policies used by recent Siemens Sinumerik controllers!
You can dynamically define your own set of items (up to 30) that can be enabled and disabled on a per machine basis by an INI file that is automatically created with reasonable default values for each machine configured. This INI file also allows you to define your own names for every tag.
To read/write data from/to machines with Sinumerik 840D SL and 828D controllers connected to CNCnetPDM with your applications you can use our free Open Source Client (C-Sharp)
This device driver requires the most recent version of CNCnetPDM and also works with a free license. However, in this mode you only get output for the first item configured in your INI file. With a valid license you are able to output the result of up to 30 functions per reading cycle, see licensing for details. TOP
Download the Sinumerik OPC UA device driver, extract all content of sinumerikua_dll.zip into the folder where you have CNCnetPDM installed.
Edit CNCnetPDM.ini and add a new device as described in the quick start guide point 7. If you already have an entry in section [RS232] for a machine with a Sinumerik controller you can simply copy and paste this line and change its content.
Change the line as follows:
FIG. 2: Configure Sinumerik OPC UA device driver in CNCnetPDM.ini
For machines with Sinumerik 840D SL and 828D controllers you only have to change the last parameter (1) to sinumerikua.dll. Of course you also have to make sure that IP Address or DNS Hostname of your controller are correct. TOP
Start CNCnetPDM foreground program is sufficient (Start thread)
CNCnetPDM automatically copies the original sinumerikua.dll and appends the machine number as configured in the INI file, e.g. sinumerikua_1001.dll for machine 1001.
In addition an INI file with the same name is automatically created by the device driver, e.g. sinumerikua_1001.ini for machine with device number 1001.
Double click CNCnetControl, if your device number is 1001 and the device name is SINUMERIK #1 the output should be similar to the one below:
FIG 3: CNCnetControl (Sinumerik)
Here the machine (1) shows up as connected (2) which is good. On the right side (3) you see the acquired data:
The line starting with O contains items defined in the INI file of the device that should be output to section 1. If you didn’t change the INI file you get something like the following:
This device driver enables to dynamically add, group, enable or disable items and change their names. The INI file automatically created by the device driver for every machine contains sections that allow you to control its behavior.
Section [GENERAL] contains information about global parameters used by the driver on startup.
‘Commands’ defines the number of OPC commands you’d like to execute, maximum value = 30.
‘Alive command’ defines the OPC item number (section) that should be queried to detect if your controller replies to OPC commands. Please only change this to another number if your controller does NOT reply to command ‘/Bag/State/opMode’. Use our CNCnetPDM.OpcUA.SimpleClient (Sinumerik Operate 4.5) (Sinumerik Operate 4.7 and 4.8) program to check if you can read this OPC item.
‘Server port’ defines the TCP port number of the OPC Server at the controller, typically 4840.
‘Namespace’ sets the namespace to be queried, typically ‘SinumerikVarProvider’
‘Username’ and ‘Password’ are only needed for Sinumerik Operate 4.7 and 4.8 for Sinumerik Operate 4.5 you can leave these values blank.
‘No authentication’ has to be set to 1 for Sinumerik Operate 4.5 and 0 for Sinumerik Operate 4.7 and 4.8. Initially this is set to 1. For version 4.7 and 4.8 this has to be set to 0! TOP
OPC Items you query are organized in sections e.g. . Every section contains entries where you can define names and parameters for a specific OPC item. Unless otherwise instructed do NOT change sections ,  and .
Description of the numeric sections:
Section identifier, numbers starting with 0 are queried
If you set this to 0 the command is not executed
A short name (max 5 characters) to describe the item e.g. STATN for status number
A comment that describes the command (optional)
OPC command to be executed e.g. ‘/Channel/State/progStatus’ for NC program status. The command ‘cnc_oeestate’ executes several OPC commands and calculates output relevant for OEE, see section ‘Output item’ and chapter ‘Commands’ below.
For normal OPC commands like ‘/Channel/State/stopCond’ this is NOT needed. Only for command ‘cnc_oeestate’ you can enter the values described in chapter ‘Commands’ below.
You can output data to 3 sections that may contain up to 256 characters. 1 goes to section ‘O’, 2 to ‘A’ and 3 to ‘F’. If data in one section exceeds the maximum length you can send items to a different section. Make sure you have entries CollectOrders, CollectFeeder and CollectQuality enabled (=1) in CNCnetPDM.ini.
FIG 5: Description of a device INI file section
Note: To change commands, switch items on or off or alter its name while CNCnetPDM is running open the INI file with a text editor such as notepad, make the desired changes and save the file. To apply the changes immediately you can click on the machine in CNCnetControl on the left side followed by clicking buttons ‘Close’ and ‘Open’ above the section ‘Devices’. TOP
Here you can find information about commands and output items that can be used with this driver. In general you can use all commands supported by Sinumerik 840D SL and 828D controllers with OPC UA. See the ‘Parameter Manual’ of your controller for details or contact us if you need help. TOP
This special command is not a real OPC item like ‘/Channel/State/progStatus’ for NC program status. It executes several OPC commands and calculates output relevant for OEE. It also translates numeric output of specific OPC queries into text.
Numeric OEE state of the device (2 = producing, 3 = manual, 4 = interrupted, 5 = error)
State of the device as text (producing, manual, interrupted, error)
Numeric running mode of the controller (0 = JOG, 1 = MDA, 2 = AUTO
CNCnetPDM for Sinumerik 840D SL and 828D controllers also supports writing and changing of data on these devices from a remote PC. Although writing of ALL writable OPC items is supported it is highly recommended to start with simple commands like changing ‘R variables’. To do so proceed as follows:
With an unmodified INI file for a controller CNCnetPDM queries two ‘R variables’, section  = ‘R variable 1’, section  = ‘R variable 2’. To change the value of these 2 variables CNCnetPDM has to be running and you should see data for RVAR1 and RVAR2 via CNCnetControl, section ‘F’. TOP
To change the value of a parameter first click on the device in the left pane (1). Then click on button [Cmd] (2). In the drop down box below number (3) select or input 21. Enter a new numeric value into the text box below command text (4) here 1500. Click button [OK] (5). You can see the new value in the ‘Device Data’ area in the right pane (6).
FIG 7: Change R-Variable on Sinumerik 840D SL or 828D controller
All successful write actions and errors are written to the device’s log file in subfolder \log. TOP
To quickly test and build a working INI file for your controller you can use our tool devicedrivertester. If used with this driver the program creates INI file sinumerikda.ini. To use this file for CNCnetPDM you can simply append an underscore and the machine number e.g. sinumerikda_1001.ini for device number 1001.
All OPC items on Sinumerik Operate 4.5, 4.7 and 4.8 are case sensitive, for example NC program status has to be queried with /Channel/State/progStatus, if you use /Channel/State/PROGSTATUS you get an error!
If you want to add additional items (up to 30 in total) first adjust the number of commands in section [GENERAL]. Then, copy and paste the last numeric section and do not forget to adjust the section number and its content! TOP
The device driver writes a log file entry for any communication issue to the log file of the device. The file can be found in subdirectory \log of your CNCnetPDM program folder. The file format for the log file is log_ + device number + _ + date.txt. Please check this file first if you observe an issue.
If the machine shows a red icon, state disconnected and you get just output E = 0 the machine is not reachable at all. This has nothing to do with the device driver, the controller is switched off, it’s a network issue or DNS Hostname or IP Address is wrong.
If the machine shows a green icon, state connected but you just get output E = 1 the machine is reachable but the controller does not respond to commands, check your controller setup (Version 4.5) (Version 4.7 and 4.8) and the parameters used in section [RS232] of CNCnetPDM.ini. Please use the tool CNCnetPDM.OpcUA.SimpleClient (Sinumerik Operate 4.5) (Sinumerik Operate 4.7 and 4.8) to check if the machine replies to commands.
If you do get numeric device states but not any of the preconfigured items please make sure that entries CollectOrders, CollectQuality and CollectFeeder are set to 1 in section [General] of CNCnetPDM.ini.
If specific items are not acquired check first with CNCnetPDM.OpcUA.SimpleClient (Sinumerik Operate 4.5) (Sinumerik Operate 4.7 and 4.8) that you get output. Also make sure that the numeric section of the item in the device drivers INI file is activated and has an entry for ‘Name’, inactive or items with empty names are not acquired. Also check that you didn’t misspell entries for command and output item in your device driver INI file. TOP
If you already have a previous version of the driver installed and would like to upgrade to the most recent version proceed as follows:
Stop any CNCnetPDM background service or foreground program that uses the device driver
Extract all content of sinumerikua_dll.zip into the folder where you have CNCnetPDM installed, overwrite the existing files
Delete all sinumerikua_NNNN.dll and ClientAPIUA_NNNN.dll (NNNN = machine number) files. If you already have created adapted INI files for specific devices do NOT delete the sinumerikua_NNNN.ini files.
After restarting CNCnetPDM upgraded device driver versions for all machines are automatically created. TOP