This document describes setup and test of alarm & event monitoring from Sinumerik 840D controllers that use the OPC Classic A&E Interface which is most likely the case if your controller has a Microsoft Windows OS and does NOT run Sinumerik Operate >= Version 4.5.
If you have the firewall enabled at the controller proceed as follows: The most simple way to avoid communication problems is to turn off the firewall. Click on Start->Settings->Control Panel->Windows Firewall. Click on Off (not recommended) followed by OK. You’re done.
If you want to keep the firewall switched on you have to adjust some settings.
Add Port 135 to exceptions
Check ‘File and Printer Sharing’
Add program ‘OPCSinumerikAlarm.exe’ (..\mmc2\opc\alarmevent\OPCSinumerikAlarm.exe)*
* Depending on the setup of your controller these files may be stored at a different location.
FIG 2: Firewall settings on Sinumerik 840D
Restart the controller in normal mode to enable HMI again. TOP
Either click on Start->Programs->Administrative Tools->Component Services or Start->Run and type in dcomcnfg and click OK
Expand Component Services->Computers->My Computer
Right click My Computer select Properties
Open tab Default Properties
Make sure that Enable Distributed COM on this computer is checked TOP
Important: In case your PC runs an Operating System > XP, e.g. Windows 7 AND the controller PC runs Operating System Windows NT 4.0 you mandatorily have to set 'Default Authentication Level' in tab 'Default Properties' to 'None' otherwise you just get an 'Access denied' output from the test programs and the device driver! You also have to reboot your PC for these changes to take effect.
NETWORK ACCESS TO CONTROLLER
For successful communication between PC and controller it is necessary that the querying computer is able to access the controller and its Operating System via the network with proper credentials!
Typically the account you’re using on your PC does NOT have the rights to access the controller. To resolve this you need to setup an additional account:
Right click ‘This PC’ on your desktop and select Manage
Expand Local Users and Groups
Right click on ‘Users’ and select ‘New User’
In ‘User name’ enter ‘auduser’ (without quotes)
In ‘Password’ enter the password for user ‘auduser’ used at the controller, (typically ‘SUNRISE’)
Confirm the password, uncheck ‘User must change password at next logon’, click button Create followed by Close
Right click on username ‘auduser’, select Properties
In tab ‘Member Of’ click button Add and type in Administrators, click button Check Names followed by OK
If you have installed CNCnetPDM on your PC with a license other than a ‘free license’ and run this program from the folder where CNCnetPDM is installed you can monitor ALL alarms & events output by your controller, otherwise only the first one. Please see licensing for details or contact us if you have any questions.
Note: If you like to run this program from a different location on your PC you can simply copy your CNCnetPDM.ini file to this directory. TOP
SOFTWARE SETUP & USAGE (PC)
Download AEClient.zip and extract all files to a folder on your PC.
In case you use a firewall at your PC or your company network please make sure that there is an exception for TCP Port 135. As the ports for OPC communication are dynamically assigned you also have to add an exception for program AEClient.exe. You can use our tool Device Port Scanner to check if your controller is reachable via port 135.
Note: The program requires .NET Framework 2 components to be installed on your PC.
Note: If your PC does NOT have any OPC programs installed you need to install the x86 version of the OPC core components:
If you see a popup window with ‘CoCreateInstanceEx: The RPC server is unavailable’ check that the controller is running, you typed in the correct IP Address and you configured your firewall correctly.
If the program outputs an error that contains: 'Interface not registered' make sure that you have the OPC core components installed.
If you shut down AEClient.exe via Task Manager or it crashes the process OPCSinumerikAlarm.exe at the controller keeps running and refuses any new connections. In this case you can either, if possible, terminate OPCSinumerikAlarm.exe directly at the controller or restart the controller.