Machines that have Sinumerik controllers which are based on NT 4.0 OS are NOT able to permanently store information about the trusted DDE share NCU840D$, the data does not survive a reboot of the machine. This share is mandatorily needed for data acquisition as it grants access to the controllers internal data structures from a remote location.
Examples for the required .reg and .bat files taken from various controllers can be downloaded here.
The information about the trusted share is stored in the following location of the registry at the controller:
As the above information does not survive a reboot of the controller it has to be automatically added to the registry on startup of the machine. Steps:
Create a .reg file that contains the required information.
The .reg file can be created by exporting the whole sub key that contains the NCU840D$ key. This is done by calling regedit followed by connecting to the registry of the controller (File -> Connect Network Registry) and manually input of the controller’s IP address.
The required data can be found at the following location
wherein CRYPTIC_USERID is a string like S-1-5-21-1455767761-1966283977-1617787245-500. On these specific controllers only one of these UserID’s can be selected.
By right clicking the sub key under “DDE Trusted Shares” the required information can be exported (Note: Only the selected branch must be exported, file format must be Win9x/NT4 Registration Files) and saved in a file (e.g. 1349.reg).
After exporting the registry key one line of the file has to be changed. The line containing
has to be changed into
[HKEY_CURRENT_USER… the full line has to look similar to
To restore the share a directory at the controller (e.g. f:\scripts\) is needed that contains the .reg file created in the above steps as well as a batch file (e.g. 1349.bat). The batch file just has to contain one single line:
@regedit /s f:\scripts\1349.reg
wherein regedit /s means insert the content of f:\scripts\1349.reg into registry silently. The batch file has to be stored in the same folder as the .reg file.
To automatically run the batch file when the controller starts up another entry in the registry of the controller is needed. Navigate, via regedit, File -> Connect Network Registry and manually input of the controller’s IP address, to the following registry branch of the controller:
Create a string value with a descriptive name (e.g. ddetrust) that, as string value, points to the batch file created in step 1, e.g. f:\scripts\1349.bat
Now, every time the controller is powered on it automatically executes the above batch file which results in addition of the registry entry that is needed to access the controller for correct machine data acquisition.