NCU operating system (IM7) System settings 1

___________________

___________________
Configuring the system 2

___________________
Service and diagnostics 3
SINUMERIK
___________________
Appendix A
SINUMERIK 840D sl
NCU operating system (IM7)

Commissioning Manual

Valid for:

CNC software for 840D sl/ 840DE sl Version 2.6

03/2010
6FC5397-1DP10-5BA0
Legal information
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.

DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.

WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.

CAUTION
with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.

CAUTION
without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.

NOTICE
indicates that an unintended result or situation can occur if the corresponding information is not taken into
account.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation for the specific task, in particular its warning notices and
safety instructions. Qualified personnel are those who, based on their training and experience, are capable of
identifying risks and avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:

WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be adhered to. The information in the relevant documentation must be observed.

Trademarks
All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this
publication may be trademarks whose use by third parties for their own purposes could violate the rights of the
owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.

Siemens AG Ordernumber: 6FC5397-1DP10-5BA0 Copyright © Siemens AG 2010.

Industry Sector Ⓟ 02/2010 Technical data subject to change
Postfach 48 48
90026 NÜRNBERG
GERMANY
Table of contents

1 System settings ......................................................................................................................................... 5

1.1 Delivery condition of the system ....................................................................................................5
1.2 Meaning of switch positions ...........................................................................................................7
1.3 System booting ..............................................................................................................................8
1.4 Displays during system booting .....................................................................................................9
2 Configuring the system ............................................................................................................................ 13
2.1 Ethernet interfaces of the NCU ....................................................................................................13
2.2 How to determine the IP address of the NCU..............................................................................14
2.3 Configuration file "basesys.ini".....................................................................................................15
2.3.1 Section [ExternalInterface]...........................................................................................................15
2.3.2 Section [InternalInterface] ............................................................................................................18
2.3.3 Section [IBNInterface] ..................................................................................................................20
2.3.4 Section [SNMP]............................................................................................................................21
2.3.5 Section [DCP]...............................................................................................................................22
2.3.6 Section [LLDP] .............................................................................................................................23
2.3.7 Section [LinuxBase] .....................................................................................................................24
2.3.8 Example: Configuration file 'basesys.ini'......................................................................................27
2.4 Service Commands......................................................................................................................31
2.4.1 Using service commands.............................................................................................................31
2.4.2 Syntax for the Actions ..................................................................................................................32
2.4.3 Generic elements.........................................................................................................................33
2.5 Description of the actions.............................................................................................................35
2.5.1 Help..............................................................................................................................................35
2.5.2 Check-cf .......................................................................................................................................36
2.5.3 Clear.............................................................................................................................................36
2.5.4 Closeport......................................................................................................................................37
2.5.5 Connect........................................................................................................................................37
2.5.6 Disable .........................................................................................................................................39
2.5.7 Disconnect ...................................................................................................................................40
2.5.8 Distribute ......................................................................................................................................40
2.5.9 Enable ..........................................................................................................................................41
2.5.10 Openport ......................................................................................................................................42
2.5.11 Restart..........................................................................................................................................43
2.5.12 Restore.........................................................................................................................................44
2.5.13 Save .............................................................................................................................................45
2.5.14 Show ............................................................................................................................................46
2.5.15 Start, Stop ....................................................................................................................................50
3 Service and diagnostics........................................................................................................................... 53
3.1 Creating a service system............................................................................................................53
3.1.1 How do you create a service system for the NCU? .....................................................................53
3.1.2 This is how you operate the service system ................................................................................56
3.1.3 Diagnostics functions ...................................................................................................................57
3.1.4 This is how you connect to a network drive .................................................................................59

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 3
Table of contents

3.2 Backup license ............................................................................................................................ 60

3.2.1 This is how you backup the license key...................................................................................... 61
3.3 Backup data via the service menu .............................................................................................. 63
3.3.1 This is how you backup user data............................................................................................... 63
3.3.2 This is how you restore user data ............................................................................................... 65
3.3.3 This is how you create a complete backup of the CompactFlash Card...................................... 66
3.3.4 This is how you install a complete system backup ..................................................................... 68
3.4 Backing up data via the service shell.......................................................................................... 70
3.4.1 This is how you save data on a service system.......................................................................... 70
3.4.2 This is how you restore data from the service system................................................................ 71
3.4.3 This is how you save data on a network drive ............................................................................ 71
3.4.4 This is how you restore data from the network drive .................................................................. 73
3.5 Updating the software ................................................................................................................. 75
3.5.1 This is how you update the firmware .......................................................................................... 75
3.5.2 This is how you update the software........................................................................................... 77
3.6 System diagnostics ..................................................................................................................... 79
3.6.1 Performing system diagnostics ................................................................................................... 79
3.6.2 This is how you change the system settings............................................................................... 81
3.6.3 This is how you check the CompactFlash Card.......................................................................... 82
3.6.4 Calling the VNC Viewer............................................................................................................... 84
3.6.5 WinSCP and PuTTY ................................................................................................................... 86
A Appendix.................................................................................................................................................. 87
A.1 Abbreviations .............................................................................................................................. 87
A.2 Licenses for WinSCP and PuTTY............................................................................................... 89
A.2.1 GNU License............................................................................................................................... 89
A.2.2 PuTTY Licence............................................................................................................................ 94
Glossary .................................................................................................................................................. 97
Index........................................................................................................................................................ 99

NCU operating system (IM7)

4 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
System settings 1
1.1 Delivery condition of the system

Scope of validity
This document is valid for all systems that are supplied with Linux as operating system on
the CompactFlash Card, such as all NCUs of the type NCU 7x0.

Structure and contents of the CompactFlash Card

A Linux partition as well as a FAT partition are available on the CompactFlash Card. The
memory space of the CompactFlash Card is occupied mainly by the Linux-EXT3 partition
containing the system software and the user data. A 2MB large FAT partition still exists but
only for internal administration purposes.
When the system is in operation, the following directories (this is a selection and not a
complete list) are available in the EXT3 partition on the CompactFlash Card:

Directory Use
/siemens Reserved for Siemens system software
/addon Reserved for Siemens add-on software
/oem Additional software and configurations of the machine manufacturer
/user  Storage of user data
 Configuring the HMI application
 Data that are created using the HMI application when commissioning
the system.
/system Linux operating system
/user/system/etc File basesys.ini (modifications possible)
/user/common/tcu TCU configuration files
/var/log/messages System log file (same as event.log under Windows)

Files in the directory under /user always have priority over files with the same name in the
directory /oem → /addon → /siemens.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 5
System settings
1.1 Delivery condition of the system

NOTICE
Suitable editors for Linux
In most Linux system files, lines may only be ended with LF, and not with CRLF as in
Windows. Please take note of this when selecting an editor. The HMI application editor
under "Commissioning” is suitable.
In the Linux operating system, the UNIX editor vi is available.
Please take note that the Linux operating system is case-sensitive.

Preset users
The following users have already been set up:

Users Access level Target group

Operator Key switch position 0 Operators, users
Operator1 Key switch position 1 Operators, users
Operator2 Key switch position 2 Operators, users
Operator3 Key switch position 3 Operators, users
user Password: CUSTOMER Operators, users
service Password: EVENING Service personnel
manufact Password: SUNRISE Machine manufacturer

NCU operating system (IM7)

6 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 System settings
1.2 Meaning of switch positions

1.2 Meaning of switch positions

Overview
The NCU has two twist buttons in the lower section of the front panel.
● NCK start-up switch with label SIM/NCK
● PLC mode selector switch with label PLC
The switch positions are marked with even numbers or letters; the uneven numbers are
represented by dots due to space limitations.

6,01&. 3/&
Figure 1-1 Startup and mode selector switch

SIM/NCK twist button

The switch positions of the SIM/NCK switch have the following meaning:

Switch position Operating mode of the NCK

0 Normal boot-up NCK
1 NCK boot-up with default values (= memory reset)
2 The NCK (and PLC) starts up with the data that was saved at the last
shutdown.
7 Debug mode (NCK is not started.)
8 IP address of the NCU is displayed on the seven-segment display.
All others Not relevant

PLC twist button

The switch positions of the PLC switch have the same meaning as in a SIMATIC S7-CPU:

Switch position Operating mode of the PLC

0 RUN
1 RUN (protected mode)
2 STOP
3 Memory reset (MRES)
All others Not relevant

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 7
System settings
1.3 System booting

1.3 System booting

Sequence
To ensure unproblematic booting of the NCU, the CompactFlash Card must be inserted.
When the NCU is booting up, visual information on the current operating system is provided
using the following displays:
● The RDY-LED flashes slowly yellow when the CF card is accessed.
● During booting, the 7-segment display outputs different codes that indicate, for example,
when the BIOS is started, when the CompactFlash Card is accessed, etc.

When the booting has been completed successfully, the following is displayed:
● The PLC LED lights up green.
● The 7-segment display shows "6." with a flashing dot.
● The RDY-LED lights up green. All other LEDs are not illuminated.

Performing a reset operation

The reset button is located behind the blanking plate of the NCU.
A reset operation resets the entire system and requires a system restart. This is comparable
to a "Power On reset" except that the 24 V power supply does not have to be switched off.

Booting for servicing purposes

For service or diagnosis purposes, the NCU can be booted from a service system, the
Emergency Boot System.

See also
How do you create a service system for the NCU? (Page 53)

NCU operating system (IM7)

8 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 System settings
1.4 Displays during system booting

1.4 Displays during system booting

Behavior of the LEDs when booting

Of the LEDs on the front panel of the NCU, only the RDY LED and its status is important
when booting up the NCU.

LED: LED designations: State/phase 7-segment display

RDY RUN STOP SU/PF
SF DP1 DP2 OPT
Orange Orange BIOS boot Post codes, see table: Load
BIOS
Slowly flashing Set by PLC/option module Booting up the kernel 1
orange (0.5 Hz) Phase 2: Initialization of the
driver
Slowly flashing Set by PLC/option module Booting the basic system See table: Load operating
orange/green Phase 3: Initialization of the system
(0.5 Hz) basic system
OFF Set by PLC/option module NRK/NCK outputs See table: NRK/NCK outputs
green/red flashing Set by PLC/option module Basic system shutdown OFF
(0.5 Hz)
red Set by PLC/option module Kernel shutdown OFF
red (5 Hz) Set by PLC/option module SINAMICS fault ---
SINAMICS faults and alarms, also see: SINAMICS S120/S150 List Manual (LH1)

Load BIOS

7-segment Meaning
display
00 Before loading the Master Boot Record (MBR) from the CompactFlash Card
01 Before starting the Master Boot Record (MBR) codes
02 Master Boot Record (MBR) code started
03 Second stage of the boot loader started, before reading the configuration file
04 Before loading the kernel
05 Before starting the kernel

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 9
System settings
1.4 Displays during system booting

Booting the basic system

7-segment display Meaning

1 (begin) Basis initializations
2 (prepfs) Cleaning up and preparing the file system
3 (hostname, loopback) The name is set and the loopback interface configured.
4 (syslog) Starting the system logging
Starting the CFS class 1, provide the network interfaces.
5 (network) Initializing the network interfaces and the firewall
6 (NCU:rtai, TCU:tcuconfig) Starting the time server (ntpd)
7 (lsh) Starting the SSH server (if required, generate a host key if still not
available).
8 (NCU:ftpd, TCU:mtouch) Starting the FTP server
9 (NCU:tcuservices, Starting the TCU services (TFTP, VNC)
TCU:usbexport)

NRK/NCK outputs

7-segment Meaning
display
1 Not applicable.
2 Not applicable.
3 Debugger was initialized.
4 NRK operating system was successfully activated.
5 NRK operating system has booted, init task is being processed (→ the application
boots).
6 Initialization was successfully performed; the control is in cyclic operation.
with flashing point: The control is in cyclic operation and the cycles are active.
6.
F Internal error: Can only be read via additional diagnostics.
1 or 2 CompactFlash Card and SRAM data do not match. To resolve this problem, a
general reset is required by booting with switch position 1 or 2.
Lxx=yyy Internal error when starting NCK, "xx" is the line number in the mcsystem.ini, "yyy"
is a unique error code for the code position.

NCU operating system (IM7)

10 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 System settings
1.4 Displays during system booting

System error

LED: LED designations: Meaning 7-segment

RDY RUN STOP SU/PF display
SF DP1 DP2 OPT
Rapidly flashing Set by PLC/option module Permanent error:
red (2Hz) The system is stopped. see the following
Rapidly flashing Set by PLC/option module Temporary error: table
red/orange (2 Hz) The system may continue to run with
restricted functions.

7-segment Meaning
display
Permanent error:
C "crash": The operating system crashes (this approximately corresponds to a Blue
Screen for Windows); details can be found in the system log file.
P "partition": Error when repartitioning
Temporary error:
E "error": A read or write error has occurred on the CompactFlash Card (an additional
point is displayed for a write error). It is possible that the CompactFlash Card is
defective and should be replaced.
F "full": The CompactFlash Card is too full, so it is probable that not all of the services
will be able to be successfully started.
When booting, this error is displayed for 1 minute; the system then continues to
boot, however, it can be assumed that problems will occur.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 11
System settings
1.4 Displays during system booting

NCU operating system (IM7)

12 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
Configuring the system 2
2.1 Ethernet interfaces of the NCU

Supplementary conditions
For the operation of an NCU:
● No more than one NCU may be operated as a DHCP server on the system network.
● An additional external keyboard is required for uppercase/lowercase letters and a mouse
is needed when using the System Network Center.

Configuration of the interfaces

The following connections can be established via the Ethernet interfaces:

Interface Labeling Interna Terminal settings

l name
Ethernet IE1/OP X120 (Eth 2) Connection to the system network with preset IP address
192.168.214.1 with subnet screen form 255.255.255.0
and active DHCP server for SINUMERIK
Ethernet IE2/NET X130 (Eth 1) Connection to company network as standard DHCP
client
Ethernet X127 (Ibn 0) Service terminal with fixed IP address 192.168.215.1 and
fixed subnet screen form 255.255.255.224 with active
DHCP server

Network interface
The network interface is an interface that enables network communication. These are the
Ethernet interfaces on the NCU.

VNC (Virtual Network Computing)

Virtual Network Computing is a software that displays the screen contents of a remote
computer, with a running VNC server, on a local computer, with a running VNC viewer, and
in return sends keyboard and mouse movements of the local computer to the remote
computer.

Reference
Operator Components and Networking Manual

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 13
Configuring the system
2.2 How to determine the IP address of the NCU

2.2 How to determine the IP address of the NCU

Determining the IP address of the NCU on the company network (X130)

On X130, the NCU is set to the address reference via DHCP. If the company network has a
DHCP server no further settings are required.
There are several possibilities for determining the address that the NCU obtained on the
company network, and these possibilities are listed below:
● If the NCU boots in switch position 8, it shows the IP address on X130 on the 7-segment
display.
● Once the NCU has booted successfully, open a service shell on the TCU and execute the
following command to obtain the desired information:
SC SHOW IP

Changing the IP address

If the company network has no available DHCP server or if this cannot be used, you are
given the option to set a fixed address for the NCU on X130 (in accordance with the
addresses already used on the company network).
Example:
The following command results in an IP address 157.163.245.105 with a subnet mask
255.255.255.0.
SC SET IP 157.163.245.105 255.255.255.0 -X130

NCU in the system network (X120)

On X120, the NCU is pre-selected as required: No settings are necessary.

See also
Generic elements (Page 33)

NCU operating system (IM7)

14 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.3 Configuration file "basesys.ini"

2.3 Configuration file "basesys.ini"

Storage path
For a Linux basic system, the original file can be found on the CompactFlash Card at
/system/usr/etc; OEM versions are stored under /oem/system/etc as well as
/oem_i/system/etc and user versions under /user/system/etc.

Use
Settings are made in the basesys.ini file that specify the behavior of the system in the
network.
To edit the basesys.ini file:
● Comments are introduced by ';' or '#' at the beginning of the line, and span the width of
the line. Empty lines are also handled as comments.
● The sections that start with a "[NAME]" line are ignored by the basic system itself, but are
sometimes used by the HMI.
● Variable definitions are written in the form "NAME=VALUE". Blanks are permitted around
the '=' character. The value may also be enclosed in double quotation marks, but this is
optional.

NOTICE
Only the basesys.ini file parameters described in this chapter can be changed.
The "System Network Center" can also be used for this purpose. Use the "sc start snc"
command to call this program. To operate it, you will need a mouse.

2.3.1 Section [ExternalInterface]

Description
In this section, the parameters and settings for the external Ethernet interface are defined.
For an NCU7x0, this is X130 (Eth1). If the external interface is in DHCP mode, i.e. the value
of ExternalIP is empty or not defined, then all parameters listed here, with the exception of
"DHCPClientID", are accepted by the DHCP server as long as the server provides a value
for the parameter.

ExternalIP
If ExternalIP is not empty, the fixed IP address specified there is used on the company
network interface. The ExternalNetMask then also needs to be set, as well as the gateway,
name servers, host name, and domain if required.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 15
Configuring the system
2.3 Configuration file "basesys.ini"

If ExternalIP is not set or is empty, a DHCP client is started on the interface.

Value: IP address
Default: Empty

ExternalNetMask
ExternalNetMask must be set together with ExternalIP, in order to define the size of the
network.

Value: Subnet mask

Default: Empty

Gateway
If the value of gateway is not empty, the host specified there is used as the default gateway,
which means that all IP packages that cannot be directly assigned are sent here for routing.
If no gateway is specified, only the networks that are directly connected are accessible.

Value: IP address
Default: Empty

Nameservers
If DNS name servers are specified here, then these must be used to resolve symbolic host
names, i.e. at most of the points where an IP address is expected, a computer name can
also be used instead.
The name server setting is also sent to your DHCP client (TCU, PG) via the DHCP server of
the NCU, so that this can also work with symbolic names.

Value: List of IP addresses (separated by a blank)

Default: Empty

Timeservers
Here you can specify a list of NTP servers (UDP/123) that can be used by the NTPD on the
NCU for time synchronization.

Value: List of IP addresses (separated by a blank)

Default: Empty

Hostname
Here you can define a name for the local host. This manually assigned name takes priority
over all other names.

NCU operating system (IM7)

16 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.3 Configuration file "basesys.ini"

The host name is determined in the following order:

● Host name from the basesys.ini file, if set
● A name received from the DHCP server (if DHCP client mode and a name have been
supplied), the result of a reverse DNS lookup, i.e. which name belongs to the IP received
(if nameservers are defined)
● A default name ("NONAME_...")
Because the host name is also used as DNS name it must satisfy the corresponding
requirements of the RFC:
● ASCII letters (a-z, A-Z), numbers (0-9) and '-'
● max. 63 characters

Value: Name
Default: Empty

Domain
These variables can be used to configure the DNS domain. The effect is that names in this
domain can be resolved without qualification (e.g. if the domain is "test.local", you can also
specify the name "computer1.test.local" as "computer1").

Value: Name
Default: Empty

DHCPClientID
With these variables, you can influence which ClientID the DHCP client presents to its
server. This ID can be used by the server to assign certain parameters to the client, for
example a static IP address.
Usually, the MAC address of the Ethernet interface is used for this purpose. This is also the
default setting. Alternatively, you can also use the host name ("@NAME"), which must then
be defined in the basesys.ini, in order to be recognized before the DHCP request. It is also
possible to use an arbitrary string for ClientID.

Value: @MAC, @CFID, @NAME or any string

Default: @MAC

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 17
Configuring the system
2.3 Configuration file "basesys.ini"

2.3.2 Section [InternalInterface]

Description
In the section [InternalInterface] the data is specified for synchronization of the DHCP server
in the system network.

Note
This section of the basesys.ini file is on Linux systems (e.g. NCU, PCU 321) and, from PCU
base software V8.1, also on Windows systems (e.g. PCU 50.3).

InternalIP
Use this variable to set the fixed IP address in the system network. InternalIP should always
be used together with InternalNetMask.

Value: IP address
Default: 192.168.214.1

InternalNetMask
Specifies the subnet mask for InternallP and should always be used together with it.

Value: Subnet mask

Default: 255.255.255.0

InternalIP_Alias
Use this variable to define an additional alias IP address for the interface of the system
network (X120); this is practical in certain application cases.

Value: IP address
Default: Empty
InternalIP_Alias should always be used together with InternalNetMask_Alias.

InternalNetMask_Alias
This variable specifies the subnet mask for InternallP_Alias and should always be used
together with it.

Value: Subnet mask

Default: Empty

NCU operating system (IM7)

18 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.3 Configuration file "basesys.ini"

SyncModeDHCPD_SysNet
If this variable is not set on "OFF" then the DHCP servers synchronize themselves in the
system network (X120) so that only one of them actively assigns addresses. This makes it
possible to operate multiple NCUs or PCUs 50.3concurrently without having to adjust the
network settings.

Value: ON_MASTER, ON_HIGH (= ON), ON_LOW, or OFF

Default: ON_HIGH
The DHCP servers that are not active go into "standby" mode; in this mode they regularly get
the current address data and TCU data from the active server so that if the active server fails
a standby server can take over the active role without data loss.
● With the ON_MASTER setting instead of ON_HIGH you can influence the
synchronization in such a manner that the server with the "Master" setting is always the
active server (for this it must be active on the network). This means that in the normal
situation deterministically the same controller is always the DHCP server and you can find
the actual address data (/var/etc/udhcp-eth0.leases) and the TCU data
/user/common/tcu/etc.) there. ON_MASTER should only be set for a single DHCP server
in the system network; there should not be multiple masters.
● The ON_LOW setting assigns the DHCP server a lower priority than normal. It then
becomes the active server if no server with ON_HIGH or ON_MASTER is found in the
network.

Note
Compatibility with earlier versions
The priority level "ON_LOW" is used automatically if the DHCP server was previously
switched off with the no longer available variable DisableDHCPDeth0=1. Such an NCU
then indeed does have a (standby) DHCP server and keeps a backup of the lease data,
however normally it does not become an active server.

InternalDynRangeStart
With the two variables InternalDynRangeStart and InternalDynRangeEnd, you can explicitly
specify the range of IP address assigned by the DHCP server. The number band of the
presetting should normally suffice.

Value: IP address
Default: First address in the system network + 10 or +2 (if ≤ 16 addresses)

InternalDynRangeEnd

Value: IP address
Default: Last address in the system network - 15 or -1 (if ≤ 16 addresses)

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 19
Configuring the system
2.3 Configuration file "basesys.ini"

DHCPDNoMasterWait
If a synchronizing DHCP server has once seen a master server in the past, then it waits for
synchronization until the time specified here elapses before it becomes the active server.
This additional pause makes it possible for the intended DHCP master to become the active
DHCP server without displacement even if it is shortly switched on thereafter, or takes longer
to boot than other controllers.

Value: Time in seconds

Default: 120

InternalDNSDomain
This is used to specify the Top Level Domain (TLD) name that is used in the system
network. The DNS server of the NCU assigns names to the devices in the system network in
this zone. Name requests for all other zones are forwarded to an external name server in the
company network.
As presetting the "local" recommended by the RFC1035 is used for local networks, to avoid
conflicts with globally defined domain names. Recommendation: The preset should be
maintained.

Value: Domain name (letters, numbers, '-', '_', max. 63 characters)

Default: local

2.3.3 Section [IBNInterface]

Description
The settings in this section affect interface X127.

EnableDHCP_IBNNet
If this variable is set to 0 then this prevents the start of the DHCP server on the
commissioning interface (X127).

Value: Empty, 0 or 1
Default: Empty

EnableSysNetToIBNForwarding
If this variable is set to 1, it is possible to transmit packages from the system network (X120)
to X127. A firewall usually prevents this.

NCU operating system (IM7)

20 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.3 Configuration file "basesys.ini"

It is important to remember that there is no NAT involved, and the sender is responsible for
ensuring (with a suitable routing entry, for example) that packages sent to the PG or service
PC on X127 with the address 192.168.215.x only reach the NCU to which the device is
connected.

Value: Empty, 0 or 1
Default: Empty

DisableIBNForwarding
If this variable is set to 1, the NAT transfer of packages from the service connection X127 to
the system network (X120) is deactivated.

Value: Empty, 0 or 1
Default: Empty

2.3.4 Section [SNMP]

Description
Character strings delivered via SNMP (Simple Network Management Protocol) are entered
here. This is a way of giving out information.

SNMPLocation
This string is used for the standard OID SNMPv2-MIB::sysLocation. It is possible to specify a
location here, which can be subsequently called with an SNMP client.

Value: Any character string

Default: Empty

SNMPContact
This string is used for the standard OID SNMPv2-MIB::sysContact. It is possible to specify a
contact address here, which can be subsequently called with an SNMP client.

Value: Any character string

Default: Empty

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 21
Configuring the system
2.3 Configuration file "basesys.ini"

SNMPAutLocation
This string is used for the Siemens-specific OID
automationSystemIdent.automationLocationTag. It is possible to specify an additional
location here, which can be subsequently called with an SNMP client. This is similar to
SNMPLocation in terms of the MIB description, although it is intended for entries relating to
automation.

Value: Any character string

Default: Empty

SNMPFunction
This string is used for the Siemens-specific OID
automationSystemIdent.automationFunctionTag. It is possible to specify a function
designation here, which can be subsequently called with an SNMP client.

Value: Any character string

Default: Empty

See also
Example: Configuration file 'basesys.ini' (Page 27)

2.3.5 Section [DCP]

Description
The parameters in this section define the properties of the DCP protocol (Discovery and
Basic Configuration Protocol) e.g. that are used in the menu item "Accessible participants" of
STEP 7 is used.

InternalDcpEnabled
This can be used to switch-on and switch-off the DCP in the system network (X120); for the
NCU, the value is also used for X127.

Value: 0 or 1
Default: 1

NCU operating system (IM7)

22 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.3 Configuration file "basesys.ini"

ExternalDcpEnabled
This can be used to switch-on and switch-off the DCP in the company network (X130).

Value: 0 or 1
Default: 0

2.3.6 Section [LLDP]

Description
The parameters in this section define the properties of the LLDP protocol (Link Layer
Discovery Protocol), which is used by several applications for network diagnostics.

InternalLldpEnabled
This can be used to switch-on and switch-off LLDP in the system network (X120); for the
NCU, the value is also used for X127.

Value: 0 or 1
Default: 1

ExternalLldpEnabled
This can be used to switch-on and switch-off LLDP in the company network (X130).

Value: 0 or 1
Default: 0

InternalLldpTLVsTxEnabled
Using this parameter, additional information in the LLDP packages are enabled at
X120/X127, which are normally not included.

Value: Numerical value from 0 ... 15

Default: 0

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 23
Configuring the system
2.3 Configuration file "basesys.ini"

The value is a bit field, i.e. the total value is obtained as a sum (total) of the specified
numbers, if the corresponding information is to be sent:

1: port description
2: system name
4: system description
8: capabilities

ExternalLldpTLVsTxEnabled
Using this parameter, additional information in the LLDP packages is enabled at X130, which
are normally not included.

Value: Numerical value from 0 ... 15

Default: 0

The value corresponds to parameter InternalLldpTLVsTxEnabled.

2.3.7 Section [LinuxBase]

Description
Additional setting possibilities of the Linux system are combined in this section.

Synchronizing the time

There are two different cases:
● If there is an external NTP server to act as a time server (entered in the basesys.ini file or
via DHCP), then the PLC clock is synchronized via the Linux clock.
● If there is no external time server, the PLC clock will be the master for the Linux clock:

NOTICE
Power on the PLC in switch setting 3: "MRES"
With "memory reset" the time of the PLC clock remains intact and is not reset.
If the PLC is switched on in switch position 3 "MRES" then the time will be reset. In this
case the valid time is taken over from the Linux system and does not need to be reset.

NCU operating system (IM7)

24 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.3 Configuration file "basesys.ini"

Timezone
The time zone set here is used by the system to convert UTC time into local time. The time
zone is also sent to all applications via the environment variable TZ, and is taken into
account by the libc function localtime().
The time zone influences all time entries in the basic system, particularly for the command
"date", for "ls -l", and in the system log file (on the CompactFlash Card under
/var/log/messages).

Value: Time zone description

Default: UTC
Some selected time zone descriptions are listed in the comments of the supplied example
file "basesys.ini":

LogFileLimit
The size of the system logfile /var/log/messages can be restricted with the help of this
variable. By entering "Zero", the logfile has no size limitations.
The specified limit is no hard limit for reasons of efficiency but rather a sort of limit value. If
the logfile reaches a limit value times factor 1.5, then it is reduced to around 75% of the limit
value. A check is carried out every two minutes maximum to see if the file has become too
large.

Value: Size in KB
Default: 100 KB

FirewallOpenPorts
Here you can specify a list of the ports which is to be enabled in the firewall of the external
network interface. Always enabled are TCP/22 (ssh) and TCP/102 (S7 communications).
Logfile is "TCP" or "UDP", the port is the (numerical) port number of the service to be
enabled.

Value: List of logfile/port pairs

Default: Empty

Several entries are separated by a blank.

For example, you can additionally enable the VNC server:
FirewallOpenPorts=TCP/5900 TCP/5904 TCP/5905

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 25
Configuring the system
2.3 Configuration file "basesys.ini"

DisableSubsystems
Using this variable, you can suppress mounting and starting of certain subsystems (CFS
systems). Several subsystem names, too, can be specified - separated by blanks.

Value: List of CFS names (separated by a blank)

Default: Empty

The names can either be simple CFS basic names (e.g. "nck") - ignoring all CFS systems
with this name - or you specify an absolute path (e.g. /siemens/sinumerik/nck) referring
specifically to this CFS system.
It is also possible to set "DisableSubsystems=all" whereby not a single CFS system can be
mounted or started any more.

DisablePLCTimeSync
If this variable is set to 1, synchronization of the system time with the PLC time (in both
directions) will not be executed.

Value: 0 or 1
Default: 0

EnableCoreDumps
If this variable is set as equal to 1, a logfile for processes is created and stored under
/var/tmp. The protocol file contains a memory print of the process that has crashed or that
has terminated.

Value: Empty, 0 or 1
Default: 0

NCU operating system (IM7)

26 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.3 Configuration file "basesys.ini"

2.3.8 Example: Configuration file 'basesys.ini'

Configuration file basesys.ini

The following defaults are applied to the template_basesys.ini file which is supplied in the
directory /siemens/system/etc.:
; ------------------------------------------------------------------
; Default Linux basesystem configuration
; ------------------------------------------------------------------
;
; section ID is for Windows compatibility and is ignored
[ExternalInterface]

; If ExternalIP is set, you can force the external Ethernet

; interface to use a fixed IP addr. etc instead of using DHCP
; if a Hostname is set, it even overrides one received by DHCP
;ExternalIP=210.210.210.210
;ExternalNetMask=255.255.255.0
;Gateway=210.210.210.1
;Nameservers=210.210.210.1 210.210.210.2
;Timeservers=210.210.210.3
;Hostname=somename
;Domain=example.com

; if ExternalIP is empty (default), DHCP is used with the following

; ClientID. The default is "@MAC" to use the MAC address,
; alternatives are "@NAME" to use the hostname (Hostname above)
; or any other arbitrary string.
;DHCPClientID=@MAC

[InternalInterface]
; With InternalIP and InternalNetMask (both must be set together),
; you can change the address on the internal/TCU/automation net.
; This should not be needed normally.
;InternalIP=192.168.214.1
;InternalNetMask=255.255.255.0

; These two can define an alias IP for X120.

;InternalIP_Alias=192.168.216.1
;InternalNetMask_Alias=255.255.255.0

; This defines a "name of station" for PROFINET (ERTEC interface),

; e.g. for DCP. If not defined or empty, the usual hostname is also
; the PN name.
;PN_StationName="PN_IO"

; Setting EnableDHCPD_SysNet to 0 suppresses that a DHCP server

; is started on that interface
;EnableDHCPD_SysNet=0

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 27
Configuring the system
2.3 Configuration file "basesys.ini"

; Set synchronization of all DHCP servers in the system/TCU network

; (X120). Possible values are:
; OFF, ON_LOW (low priority),
; ON or ON_HIGH (normal priority), or ON_MASTER (highest priority).
; ON_MASTER is used to make this machine deterministically
; the DHCP master server, but should be used only for one server
; in the network.
;SyncModeDHCPD_SysNet=ON

; This is the range of dynamic IPs given out by the DHCP server
; Defaults should be sensible
InternalDynRangeStart=192.168.214.10
InternalDynRangeEnd=192.168.214.239

; If once a DHCP master was seen, the DHCP server waits this many
; seconds for the master to show up before trying to become the
; active server.
;DHCPDNoMasterWait=120

; DNS domain name used for names in system/TCU network

; (default is "local" to conform with RFC)
InternalDNSDomain=local

; FixedDomain and FixedNameservers can be used to define a DNS

; domain and nameservers, if the DHCP/DNS server on system network
; is disabled.
;FixedDomain=local
;FixedNameservers=192.168.214.1

; If DisableNATRouting is set to 1, the NCU won't forward from TCU

; or IBN net (X120 and X127, resp.) to external net (X130).
; If set to "X120" or "X127", forwarding will only be disabled
; from that interface.
;DisableNATRouting=1

[IBNInterface]
; Setting EnableDHCPD_IBNNet to 0 suppresses that a DHCP server
; is started on that interface.
;EnableDHCPD_IBNNet=0

; If DisableIBNForwarding is set to 1, the NCU won't do NAT routing

; from IBN network (X127) to system network (X120).
;DisableIBNForwarding=1

; If EnableSysNetToIBNForwarding is set to 1, the NCU forwards packets

; from X120 to X127. (Please note that the sending host must be able
; to route the packets to the NCU by its own means, the NCU just
; accepts and forwards packets to 192.168.215.x with this setting.)
;EnableSysNetToIBNForwarding=1

NCU operating system (IM7)

28 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.3 Configuration file "basesys.ini"

[SNMP]
; The following variables define strings which are delivered
; on certain SNMP requests.
; SNMPLocation and SNMPContact are reported for the standard OIDs
; SNMPv2-MIB::sysLocation and SNMPv2-MIB::sysContact, resp.
; SNMPAutLocation and SNMPFunction are used in the Siemens specific
; AUTOMATION-SYSTEM-MIB as automationSystemIdent.automationLocationTag
; and automationSystemIdent.automationFunctionTag, resp.
SNMPLocation="not specified"
SNMPContact="not specified"
SNMPAutLocation="not specified"
SNMPLocation="not specified"

[DCP]
; These variables en/disable the DCP protocol on X120/X127
and X130, resp.
;InternalDcpEnabled=0
;ExternalDcpEnabled=1

[LLDP]
; These variables en/disable the LLDP protocol on X120/X127
and X130, resp.
;InternalLldpEnabled=0
;ExternalLldpEnabled=1

[LinuxBase]
; Keep size of /var/log/messages around this value (not followed
; exactly for performance reasons)
LogfileLimit=102400

; Protocol/Port pairs to open in the firewall

; (e.g., TCP/5900, UDP/514, ...)
;FirewallOpenPorts=TCP/5900 TCP

; If there is only one Ethernet interface, it's used by default as

; an external(company) network. Alternatively, usage as automation
; net (TCU boot support etc.) is possible by setting NetworkModel
; to "automation". (Only NCU, Service and PCU20A variants!)
;NetworkModel=automation

; DisableSubsystems can be used to skip certain CFSes (= subsystems)

; a list of multiple names (separated by spaces) is possible
; a simple name means all CFSes with this name, an absolute path
; (e.g., /siemens/sinumerik/nck) exactly this one CFS
; with the special value "ALL", all subsystems can be disabled
;DisableSubsystems=nck

; Directory for OEM netboot files (served by tftp to diskless clients)

NetbootDirectory=/oem/common/netboot

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 29
Configuring the system
2.3 Configuration file "basesys.ini"

; Properties of local time zone: names, offset, start and end day
; Some examples:
; Europe: WET0WEST,M3.5.0,M10.5.0
; CET-1CEST,M3.5.0,M10.5.0
; EET-2EEST,M3.5.0,M10.5.0
; USA: EST5EDT,M4.1.0,M10.5.0
; CST6CDT,M4.1.0,M10.5.0
; MST7MDT,M4.1.0,M10.5.0
; PST8PDT,M4.1.0,M10.5.0
; China: CST-8
; Japan: JST-9
Timezone=UTC

; If DisablePLCTimeSync is set, no time synchronization

; with PLC will happen.
;DisablePLCTimeSync=1

; Set to 1 to enable coredumps in /var/tmp

EnableCoreDumps=0

NCU operating system (IM7)

30 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.4 Service Commands

2.4 Service Commands

2.4.1 Using service commands

Overview
The service command 'sc' is a tool used for performing a range of service tasks on a
SINUMERIK NCU. The required action is written in the command line after the 'sc', e.g.: sc
help
This action produces a list of all actions with a short description. After the action, further
parameters or options can follow.
'sc' is available in both the NCU basic system and the service system (mostly in the form of a
USB memory.) However, some actions are only useful in one of the two systems
(NCU/Service). This is noted for each action.

See also
The most important terms and abbreviations are explained in the glossary.

Privilege levels
The 'sc' command can execute its actions using more privileges than are normally granted to
the calling user. For example, starting or stopping subsystems requires root privileges, but
'sc' allows every user who belongs to the ‘service’ group to do this.
Each action of 'sc' is assigned a “privilege level”. This is a user group to which the user must
belong in order to execute the action. As the groups are hierarchically nested, members of
“higher” groups can also use the action in question. For example, the group 'manufact' is
above 'service', which means that members of the group 'manufact' can call all actions that
require the privilege level 'service'.
The privilege level that the caller requires is noted for each individual action. The possible
levels are (in ascending order):
● none
● operator
● user
● service
● manufact
Example:
An action with the privilege level 'user' can also always be executed by members of the
groups 'service' and 'manufact'. Actions with privilege level ‘none’ can be called by all users.
If a user does not have the required privileges, the following error message is output:
Action 'ACTION' needs at least GROUP privilege level.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 31
Configuring the system
2.4 Service Commands

2.4.2 Syntax for the Actions

Description
'sc' in the command line is essentially not case-sensitive.
The following entries are therefore interpreted as identical:
sc help show
SC help SHOW
sc HeLp sHoW
In some cases, however, upper/lower case can make a difference, for example in file or user
names. This is avoided wherever possible.
The conventions used are as follows:
● Names completely in upper case represent objects to be used depending on the
situation.
Example: sc help ACTION

In this case, ACTION is to be replaced by the action for which you want a description. If
written in lower case, however, the entry should be entered as specified.
● Square brackets indicate optional entries.
Example: sc help [ACTION]

In this case the specification of an action is optional, which means that you can enter an
action, but do not have to. Square brackets may also be nested:
... [USERNAME[/DOMAIN]] ...
In this case, USERNAME and DOMAIN are both optional, but you can only enter a
DOMAIN if you have also entered the USERNAME.
● Alternatives are separated with '|'.
Example: sc start all|system|SUBSYSTEM

This means that any of the following commands applies:

sc start all
sc start system
sc start SUBSYSTEM
In the latter case, SUBSYSTEM in upper case can be replaced by a concrete subsystem
name.
● As a shortened form, alternatives can also be written in square brackets:
sc save [-full|-user] ...
Here you can use the option "-full" or "-user", or none at all.
● Options that begin with '-' can always be entered in any order.
For example, the notation could be interpreted to mean that "-force" must come after "-
full" or "-user", but this is not necessarily the case:
sc save [-full|-user] [-force] FILENAME

NCU operating system (IM7)

32 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.4 Service Commands

2.4.3 Generic elements

Overview
This sections describes the syntax elements that are used by several actions.

Permitted interface designations

The names of network interfaces are used by "sc show ip", "sc set ip" and "sc enable
DHCPSvr", for example.
As the input of an interface is optional, it is always introduced by a '−' character. The '−' is
followed by the actual name. In most cases, multiple names are possible for the same
interface.
Accepted names are:

System network port: "X120", "eth2", "tcu", "internal"

Company network port: "X130", "eth1", "factory", "extern
IBN port: "X127", "ibn0", "pg"

Permitted subsystem designations

Subsystem names are entered when using "sc enable" and "sc start", for example. In most
cases, the name of the subsystem is simply the name of the corresponding CFS, without the
path and without the extension ".cfs". For example, for the CFS /siemens/sinumerik/nck.cfs,
the relevant subsystem name is simply "nck".
It is also possible to use absolute paths (beginning with /) in a subsystem name. In the
example above, you could also use "/siemens/sinumerik/nck" as a subsystem name. The
difference between names with and without a specified path is that without the path, all CFS
with this name are included, but if the path is specified, only this exact CFS is meant.

Subsystem
A subsystem is a CFS that not only contains a collection of files, but also executes a
program, for example, at runtime. To do this, the CFS contains a script that is used to control
the starting and stopping of this program.
For this reason, only administrators are permitted to set up NFS file systems, and NFS is
usually only implemented in uniformly administrated environments. Exported file systems on
the server are addressed directly on the server via their path.

CFS (Compressed File System)

A CFS (file extension ".cfs") is a compressed file system, similar to a zip file. It contains files
and subdirectories that look like normal files on the controller at runtime. Files and directories
contained in a CFS cannot be changed. They are decompressed at runtime as required.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 33
Configuring the system
2.4 Service Commands

NFS (Network File System)

NFS is the most common protocol for remote file systems in the world of Unix, and is also
available for Windows. NFS is closely based on the Unix privilege model – each time a file is
accessed, a UID and GID are supplied which the server then uses to decide whether the
operation is permitted. The server relies on the client to provide the correct IDs.

Remote File System

A file system that is contacted over the network. The files are physically located on another
computer in the network (the "server"), but appear locally the same as all other files.
Operations performed on these files are sent via the network to the server, instead of being
executed directly on a local storage medium (such as a hard drive or CompactFlash Card).
As a server usually exports more than one file system, a name for the required file system
must also be entered in addition to the name of the server.

SMB (Server Message Block)

SMB is the underlying protocol of MS Windows file systems (also known as drives, releases,
shares, etc.). SMB connections are always active in the context of a specific user, who must
be known to the server. Exported file systems have a name (release name), by which they
can be addressed. The client does not need to know the concrete path on the server.

NCU operating system (IM7)

34 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.5 Description of the actions

2.5 Description of the actions

2.5.1 Help

Description

Syntax: sc help [Action]

Alternative names: -h, --help
Privilege level: none
The call of "sc help" without any additional action outputs a list of possible actions with a
short description. If you enter an additional action, you receive a more detailed description
for this action.
Examples:
sc help
All actions:
help [ACTION]
Print help about a specific or list all actions
restart
Reboot the machine
enable hmi|nck|SUBSYSTEM...
enable DHCPSvr -INTERFACE
Enable HMI, NCK, or any other subsystem
[...]

sc help enable
enable hmi|nck|SUBSYSTEM...
DHCPSvr -INTERFACE

Enable subsystem(s), like 'hmi', 'nck', and so on. A subsystem name

is the name of the CFS containing it, without the '.cfs' extension.
This enables all CFSs with that name, but you can also use a full
path (e.g. /siemens/sinumerik/nck) to enable just a specific CFS.
Another form is to enable the DHCP server on a network interface,
for example 'enable DHCPSvr -X120'.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 35
Configuring the system
2.5 Description of the actions

2.5.2 Check-cf

Description

Syntax: sc check-df
Alternative names: checkcf
Privilege level: user
With this action, the CF card is checked reading to see whether it contains defective sectors.
If errors occur, this is noted in the file /var/log/messages.

2.5.3 Clear

Description
Various actions can be performed with the "clear" command; only the "clear dhcp" command
is relevant here.

clear dhcp

Syntax: sc clear dhcp [-INTERFACE]

Alternative names: ---
Privilege level: service
This command clears any state of the DHCP server at the specified interface (default setting
is the system network) and resets it to its initial state. This means that the Lease data is
deleted: all IP addresses are re-assigned in the network and the server forgets having ever
seen a master server.
This action is only appropriate on a machine on which the active DHCP server runs.

Note
The clearing of the Lease data does not delete the entire file, but only the data contained
therein. This action also increments the version number, so that available standby DHCP
servers can also perform the deletion.

NCU operating system (IM7)

36 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.5 Description of the actions

2.5.4 Closeport

Description

Syntax: sc closeport ID
Alternative names: ---
Privilege level: service

Mode of operation
This command closes a port in the firewall opened previously with the "sc openport"
command. This is only necessary when the port is to be closed manually before the time set
with "sc openport" expires. Otherwise the port is closed automatically when the port service
life expires.
ON parameter is the ID number of the firewall rule output by "sc openport".

2.5.5 Connect

Description

Syntax: sc connect [-ro] SERVER:/PATH [MOUNTPOINT]

sc connect [-ro] [-public] //[USERNAME[/DOMAIN]
[%PASSWORD]@]SERVER/SHARE [MOUNTPOINT]
Alternative names: mount
Privilege level: none
This action makes a remote file system on a server available on the controller. This is
enabled by linking the remote file system to a local directory, known as the "MOUNTPOINT".
The files offered by the server are then visible under this directory.

NOTICE
Note that when entering this command, the password appears on the screen in plain text
according to the specified syntax.
For path names, use the slash “/” and not the backslash “\”.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 37
Configuring the system
2.5 Description of the actions

Supported file systems

Two types of remote file system are supported: Windows SMB and Unix NFS. These two
systems have completely different characteristics, particularly in terms of user administration:
● In Windows SMB, you connect to the server as a particular user that the server must
recognize. Via this connection, you then access the files as this user, independently of
which local user triggers the action.
This feature means that in SMB systems, you already have to enter a user name, if
necessary its domain, and a password at the time of connection.
● In NFS servers, the connection itself does not require a particular user to be entered.
Instead, for each file operation, the user who wants to carry out the operation must log on
to the server. The server then decides whether or not to permit this. Users are entered
using a user ID and group ID, not with names. The server must therefore recognize the
corresponding IDs (or permit access for all users.)
Another type of remote file system that is supported are USB memory devices exported
from TCUs (USB Flash Drive). Since these are integrated using NFS, the entries for
server and path are similar to those for NFS. However, the TCU names are administrated
differently, and the USB memory devices have specific paths that do not physically exist.

Notation of the remote file system

For SMB and NFS/TCU, the file system is entered using different notations:

SMB: //[USERNAME[/DOMAIN][%PASSWORD]@]SERVER/SHARE
The fixed share is: //SERVER/SHARE
The server name can of course also be a numeric IP address. SHARE is the name of the
release on the server. Note that the character '$', which often occurs in this type of name,
must be preceded by a backslash ('\') in the command line. Otherwise, the system tries to
expand a variable.
A user name can also be entered in front of the server name, separated with a '@' character.
If necessary, the user name can also be extended by adding '/' followed by the Windows
domain to which it belongs. The password belonging to this user is normally queried
interactively, so that it is not visible on the screen. ´
For some applications, however, it may be necessary to write the password on the command
line. (For example, programs started from WinSCP cannot read from the keyboard.) In this
case, you can append an additional '%' character, followed by the password. If this contains
any special characters that are interpreted by the shell (<, >, &, ;, ", ', $, (, ), |), you should
shield these by preceding them with a backslash. Commas in SMB passwords cannot be
interpreted.

NFS: SERVER:/PATH
In NFS, entering the user is not required, which just leaves the two components SERVER
and PATH. As before, SERVER is the name of the file server. In contrast to SMB, PATH is a
path name that exists on the server, and not an arbitrarily assigned name.
The command "sc show drives SERVER" shows the file systems offered by a particular
server in the correct notation. For SMB, if required, the user name etc. still need to be added.

NCU operating system (IM7)

38 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.5 Description of the actions

After the entry of the remote file system, you can also specify the required directory
('MOUNTPOINT') in which the remote files will become visible locally. This should be an
empty directory to which you have write access. If MOUNTPOINT is omitted, 'sc' itself
generates a suitable directory. The name is /tmp/drvNN (numbered consecutively), and is
displayed when the connection is successful.
The option "-ro" connects the remote file system in read-only mode, which means that you
can only read and do not have write access. This can be useful if you want to exclude
changes that originate from the controller, or if the server only allows read-only connections.
As explained above, an SMB file system is connected as the specified user. To prevent a
third user from executing file operations on the controller in the name of the connected user,
the local directory can normally only be accessed by the latter (and all members of the same
group).
However, if you do want to make the remote directory available to further local users, you
can use the option "-public" to make the MOUNTPOINT belong to the "operator" group, and
this access is therefore guaranteed.

2.5.6 Disable

Description

Syntax: sc disable hmi|nck|SUBSYSTEM ...

sc disable DHCPSvr -INTERFACE
sc disable DHCPSync [-X120]
sc disable IPAlias [-X120]
Alternative names: ---
Privilege level: service
The "sc disable" command switches the specified subsystems off. These subsystems are
then not loaded again at the next restart. You can also switch several subsystems off with a
single "disable" command.
"hmi", "nck" or any other subsystem names can be used for the subsystems.
"sc disable IPAlias" deactivates the second alias IP address for the X120 network interface.

See also:
Parameters "InternalIP_Alias" and "InternalNetMask_Alias" in the "basesys.ini" file.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 39
Configuring the system
2.5 Description of the actions

Specific subsystems
The name "DHCPSvr" is a special case. This does not switch a normal subsystem on or off,
but specifies whether or not a DHCP server should be started on a network interface. The
interface is entered in the standard form.
The synchronization of the DHCP server is switched on and off with "DHCPSync". The
synchronization is only possible in the system network.
The commands "sc enable" and "sc disable" function by changing certain variables in the file
/user/system/etc/basesys.ini. In subsystems, this variable is "DisableSubsystems", in
DHCPSvr "DisableDHCPD<INTERFACE>".

2.5.7 Disconnect

Description

Syntax: sc disconnect MOUNTPOINT

sc disconnect all
Alternative names: umount, unmount
Privilege level: user
The action "disconnect" terminates the connection to a remote file system previously
connected using "connect“. If the MOUNTPOINT has been automatically created by 'sc', the
corresponding directory is also deleted again.
The variant "sc disconnect -all" can be used to remove all existing SMB and NFS file
systems.

2.5.8 Distribute

Description

Syntax: sc distribute [parameter]

Alternative names: dist
Privilege level: service
This command distributes TCU data to other machines in the system network. Only the
parameter "tcudata" is relevant here.

distribute tcudata

Syntax: sc distribute tcudata

Alternative names: ---
Privilege level: service

NCU operating system (IM7)

40 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.5 Description of the actions

This command informs the active DHCP server that TCU data in /user/common/tcu has been
manually changed. The server can then distribute this data to the standby servers.
It is recommended that the version file in /user/common/tcu be changed manually as this is
only read in once by the DHCP server at the start. An incrementing of the version would then
only take effect at a restart.

Note
This command can be performed on any machine in the system network, not only on the
active server. A message is always sent to the active server.

2.5.9 Enable

Description

Syntax: sc enable hmi|nck|SUBSYSTEM ...

sc enable DHCPSvr -INTERFACE
sc enable DHCPSync [-X120] [-PRIORITY]
sc enable IPAlias [-X120] IPADDR[/NETMASK]
Alternative names: ---
Privilege level: service

The "sc enable" command switches on the specified subsystems such that these are also
activated when a subsystem is started. You can also switch several subsystems on with a
single "enable" command.
"hmi", "nck" or any other subsystem names can be used for the subsystems.
"sc enable IPAlias" defines a second alias IP address for a network interface. This is only
supported for X120. The IP address itself has the usual notation with four numbers
separated by decimal points. If not specified, the subnet screen form can be determined from
the class (A/B/C) of the IP or determined explicitly. The CIDR notation (number of bits of the
network section) is also possible.

See also:
Parameters "InternalIP_Alias" and "InternalNetMask_Alias" in the "basesys.ini" file.

Specific subsystems
The name "DHCPSvr" is a special case. This does not switch a normal subsystem on or off,
but specifies whether or not a DHCP server should be started on a network interface. The
interface is entered in the standard form.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 41
Configuring the system
2.5 Description of the actions

The commands "sc enable" and "sc disable" function by changing certain variables in the file
/user/system/etc/basesys.ini. In subsystems, this variable is "DisableSubsystems", in
DHCPSvr "DisableDHCPD<INTERFACE>".

DHCP synchronization
The synchronization of the DHCP server is switched on and off with "DHCPSync". The
synchronization is only possible in the system network (X120). A priority can also be
specified. -LOW, -HIGH or -MASTER.
The priorities have the following effect for the synchronization of the DHCP server:
● MASTER:The computer node will become an active DHCP server. If several servers
have been configured in the system network, this computer has the highest priority.
● HIGH:The computer node belongs to the server candidates with high priority, i.e. if no
server with "MASTER" priority becomes active, then a computer with "HIGH" priority can
be the active server.
● LOW:The computer node belongs to the server candidates with low priority, i.e. if no
server with "MASTER" priority or "HIGH" priority becomes active, then a computer with
"LOW" priority can be the active server.

Note
Recommended settings are:
 DHCP operation and DHCP synchronization are switched on in the system network.
 Exactly one NCU is set as DHCP server.
 Maximum of two computers are candidates with "HIGH" priority.
 All other components are set as DHCP clients or candidates with "LOW" priority.

See also:
Parameter "SyncModeDHCPD_SysNet" in the "basesys.ini" file.

2.5.10 Openport

Description

Syntax: sc openport [-MINUTES] PROTO/PORT SOURCE ...

Alternative names: ---
Privilege level: service

NCU operating system (IM7)

42 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.5 Description of the actions

Mode of operation
This command opens a port in the firewall to the company network (X130) for a certain time.
The default time is 15 minutes, but this can be changed with the -MINUTES option. The
maximum possible time is 60 minutes.
The port to be opened is specified in the form "PROTO/PORTNR". The protocol can be
either "tcp" or "udp". This is followed by the specification of the hosts from which the port
should be accessible. Several forms are possible here:
● A single IP address: "128.128.12.12"
● A host name (if this can be resolved via DNS), e.g. "server"
● An IP area with network screen form specification, e.g. "128.128.12.0/255.255.255.0"
● An IP area with specification of the valid bits, e.g. "128.128.12.0/24"
If the specification of the source host is completely missing, this is normally acknowledged
with an error message. However, an exception is when the "sc openport" command is
entered in a shell opened via SSH. The permitted host is taken from the environment
variable $SSH_CLIENT that contains the IP of the SSH client.
If the opening was successful, an ID number is output in a status message:
sc: Port tcp/25 is open, rule ID is 6620
This ID can be used with "sc closeport" to manually close the port earlier.

See also:
Parameter "FirewallOpenPorts" in the "basesys.ini" file.

2.5.11 Restart

Description

Syntax: sc restart
Alternative names: reboot
Privilege level: service
The action "sc restart" triggers a controlled shut down of the machine (stops all subsystems
and the basic system), and then initiates a restart. The effect is the same as the "reboot"
command in the basic system, which can only be executed by "root".

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 43
Configuring the system
2.5 Description of the actions

2.5.12 Restore

Description

Syntax: sc restore [-full|-addon|-addon+|-oem|-oem+|-user]

[-force] [-nodelete] [-update] [-restart] FILENAME
Alternative names: ---
Privilege level: user
A backup created using "sc save" can be restored to the controller using "sc restore".

Mode of operation
As for "sc save", a restore is only possible from the service system or if subsystems are
stopped. If “sc restore" reports an error, for example that the restore will cause running
subsystems to crash, you can use the option "-force" to force the operation – just as for “sc
save”.
Normally, "sc restore" deletes the whole destination area before the backup is restored
(complete CF card for full backup, /user in user data backups). This means that no files are
subsequently available that were not included in the backup.

Options
If no further options are specified, the archive should represent a full backup and this should
be restored in full. The status of all files is therefore the same after the "restore" as it was at
the time of the backup.
● The -full option additionally forces the partition and the file system to be recreated on the
CF card. This is only possible from a service system however. -full is necessary if the
partition table and/or file system is missing or damaged.
● However, if you want to restore the backup files without losing any files that have been
created in the meantime, you can use the option "-nodelete" to prevent these from being
deleted. "-nodelete" is not executed together with "-full", as when the file system is
recreated, all files are essentially deleted.
● The options -addon, -oem, -user, -addon+ and -oem+ also allow you to unpack only parts
of an archive.
● The -update option is used for loading software updates supplied by Siemens. The -
restart option can also be useful with -update. If user-defined system files are changed
when loading an archive, a restart or reinitialization is necessary. In such cases, "sc
restore" outputs a message to that effect at the end of the operation. The -restart option
causes the required action to be performed automatically.

NCU operating system (IM7)

44 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.5 Description of the actions

2.5.13 Save

Description

Syntax: sc save [-full|-addon|-addon+|-oem|-oem+|-user]

[-force] [-update] FILENAME
Alternative names: backup
Privilege level: user
The call of "sc help" without any additional action outputs a list of possible actions with a
short description. If you enter an additional action, you receive a more detailed description
for this action.
The action "Save" or “Backup” creates a backup of the CF card in FILENAME. If the action is
used from a service system, the backup receives the files of the underlying controller, not of
the service system itself.

Options
The following options are used for selecting which directories of the file system are to be
written to the archive:

-full: complete backup (default): all files of the controller, incl. Boot Loader
-addon: only /addon directory
-oem: only /oem directory
-user: only /user directory (user data)
-addon+: /addon, /oem and /user
-oem+: /oem and /user

If "sc save" is used directly on the controller and the subsystems are running, this may lead
to inconsistencies between saved files, because they can still change during the backup
process. Therefore, in this case “sc save" normally ends in an error message to inform you
that subsystems are still running.
● If you want to create a backup anyway, you can use the -force option. "sc save" still
issues a warning, but the process continues. If "sc save" is started from the service
system, no subsystems of the controller are running and "-force" is not necessary.
● The -update option writes an Img-D control file to the archive. This makes it possible to
use the archive at a later date via "sc restore -update".
Example:
sc save -user /tmp/drv01/backup.tgz

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 45
Configuring the system
2.5 Description of the actions

2.5.14 Show

Description

Syntax: sc show ip [-INTERFACE]

Alternative names: ----
Privilege level: none

In the "sc show" command, various displays are grouped together showing the status of the
system.

show ip

Syntax: sc show ip [-INTERFACE]

Privilege level: none

This command displays the IP address data of network interfaces. You have the option to
enter a specific interface. If no particular interface is specified, the data for all existing
interfaces is displayed, as well as the Default Gateway.
Example:
sc show ip
X120 (system network, eth0):
configured: (default)
current : IP=192.168.214.1 Netmask=255.255.255.0
MAC=08:00:06:73:55:fd
DNS Name : ncu1.local
Nameserver: 127.0.0.1
DNS Suffix: local
DHCP : synced server, prio=high, active
Statistics: RX=0.0MB (0.00% errors), TX=0.2MB (0.00% errors)
X130 (company network, eth1):
configured: DHCP
current : IP=111.222.333.64 Netmask=255.255.248.0
MAC=08:00:06:73:55:fe
DNS Name : name.test.siemens.de
Nameserver: 111.222.333.12 111.222.333.13 111.222.333.14
DNS suffix: test.siemens.de
DHCP : client (server: 111.222.333.221)
Statistics: RX=1.2MB (0.00% errors), TX=0.0MB (0.00% errors)
X127 (engineering network, ibn0):
current : IP=192.168.215.1 Netmask=255.255.255.224
MAC=08:00:06:73:55:ff
DNS Name : ncu-ibn
DHCP : server
Statistics: RX=0.0MB (0.00% errors), TX=0.0MB (0.00% errors)
Default gateway: 111.222.333.1 (via eth1)
Used nameserver: 127.0.0.1
Used DNS suffix: test.siemens.de local

NCU operating system (IM7)

46 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.5 Description of the actions

The following data is displayed for each interface:

● Name: the name of the connection socket (X1_ _), together with the name used by the
operating system in brackets (ethN or ibnN).
● "configured": the IP address configured in the basesys.ini (variables
ExternalIP/ExternalNetMask for X130, InternalIP/Internal-NetMask for X120), or
"(default)" if nothing is configured in the basesys.ini, or "DHCP" if the address was
sourced via DHCP.
● "current": the currently set IP address together with the network screen form and MAC
address of the interface.
● "DNS Name": Result of a DNS reverse lookup on the current IP address.
● "Nameserver": Here the list of DNS servers is output which are related to this interface
(receive e.g. DHCP via this interface).
● "DNS Suffix": DNS search suffix related to this interface.
● "DHCP": Indication is given here if a DHCP client or server is running for this interface. In
the case of a client, the server where the IP address comes from is displayed, too. A
DHCP server on X120 can additionally be synchronized on the system network. Then the
information is displayed if this is the active server or if it is in standby mode.
● "Statistics": Total amount of data received or sent via this interface, and the percentage of
faulty packages.
When all interfaces are displayed, the default gateway is also output, i.e. the address of a
router to which all packages are sent that cannot reach their destination directly via a local
interface.
The default gateway is therefore a piece of data that applies to all interfaces and of which
there is only one instance. However, there is one interface via which it must be possible to
address the default gateway. This is displayed in brackets after the address.

show drives

Syntax: sc show drives SERVER

Privilege level: none

"sc show drives" shows the available remote file systems for a particular server. The server
name SERVER can be an NFS server, an SMB server or "TCU", which represents any USB
media that are connected to a TCU. For details of possible server names and entering a user
name (often required for SMB), see the description of the "sc connect" command.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 47
Configuring the system
2.5 Description of the actions

Examples
Notation:
sc show drives someuser/somedomain@somepc # Windows-Server
Password: *******
//somepc/C$
//somepc/D$
//somepc/images
sc show drives someserver # NFS-Server
someserver:/export/home1
someserver:/export/home2
sc show drives TCU # TCU USB-Medien
TCU1:/dev0-0
TCU2:/dev0-0

All the available remote file systems of the relevant server are listed in the notation that is
expected by "sc connect".
● SMB shared drives on Windows servers always begin with "//", followed by the server
name and the name of the shared drive. In NFS file systems, the server name is always
first, followed by a colon and then the export path.
Connection to SMB servers usually requires the entry of a user name (with domain, if
applicable) and a password.
● A USB memory on a TCU is a special form of NFS, and therefore also has the same
notation as an NFS file system. The specified path exists - but not physically - on the
TCU, but is converted there to USB by the NFS server.

show net

Syntax: sc show net [-xml] [-hw|-tco|-sw|-swfull|-loc|-panel|

-dhcp|-switch|-all] [HOSTS...]
Privilege level: none

The "sc show net" command displays the devices in the system network and gives additional
information on these devices.
As both these functions rely on SNMP (Simple Network Management Protocol), only those
devices able to use SNMP will be found. SNMP as from version 2.6 is available for Linux-
based devices, for all other devices (e.g. MCP) this depends on the respective software
version. If a simple call is made, without any additional options, a list of the devices found will
appear showing the relevant IP address, DNS name (if known), and a short description
(module name).

NCU operating system (IM7)

48 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.5 Description of the actions

Options
The various switches, which can also be combined, allow additional information to be output
on the devices found:
● Unless additional options are involved, the output format for "sc show net" is designed to
be displayed on the screen. The alternative XML format is preferable, however, if further
machine-based processing is required. This can be selected via the -xml option (this
option must be the first one!).
● If the command line contains nothing after the switches, "sc show net" will search the
entire system network by broadcast for devices able to use SNMP. This search takes
time, however, and in the case of larger systems, the volume of information output may
be considerable. In view of this, a list of IP addresses or (DNS) names can be specified to
ensure a better overview. This will limit the search process and only the named devices
will be included.

-hw Information on hardware, such as the MLFB, serial number, hardware ID,
hardware version, SRM version, manufacturer, and the serial number of
the CF card. Some devices have two of these hardware blocks (the
second one being intended for an integrated device).
The PLC in the NCU and the TACO in the OP on an TCU are two such
examples.
-tco Operating state data: switching counter, operating hours counter, quantity
of data written to the CF card, number of times maximum temperature
exceeded
-loc Location data: location, function, and contact details for the device (if
configured there)
-sw Displays brief details of the software installed, just the version of the
overall status (or of the basic system, if this is all that is installed)
-swfull Displays all the installed software components. These are represented
hierarchically in the form of a tree. The following is provided for each
component: information on the version, internal version (if different), target
version (if different), version details, and the installation path.
-panel: Displays panel-specific data: size and color depth of the display,
MCP/TCU/DCK/EKS index, and the VNC server currently represented
-dhcp Data on a synchronizing DHCP server: operating state (off/standby/active),
priority, versions of the .leases file and TCU data, and the range for
dynamically assigned IP addresses
-switch Displays the settings of rotary switches on the device, e.g. the NC and
PLC switches of an NCU or the DIPFIX of an HT 8
-all Equivalent to all the switches above

Note
EUNA (End User Notification Administration)
The data and information read out here is written to the EUNA file and saved on the
respective device.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 49
Configuring the system
2.5 Description of the actions

2.5.15 Start, Stop

Description

Syntax: sc start all|system|SUBSYSTEM

sc start all|system|SUBSYSTEM
Alternative names: ---
Privilege level: service

These two actions start or stop individual or all subsystems. Since these actions have a
direct influence on the runtime behavior, they are only available directly on the PLC, but not
in the service system (with the exception of "sc stop system"). The subsystems of the
underlying PLC do not run here, and can therefore not be controlled.

Note
Only "all" and "system" function, but not arbitrary subsystems.
Both of these actions have only been implemented to a restricted extent.

Subsystem names
"hmi", "nck", or any other names, can be used for the subsystems. Multiple subsystems can
also be specified in a row, which are then started and stopped in this order.
"all" and "system" are special values for the subsystem:
● "all" starts or stops all available subsystems.
● "sc stop system" similarly stops all subsystems, but also the basic system with the PLC.
● "start system" is identical to "start all" and exists mainly for reasons of symmetry.

start snc

Syntax: sc start snc

Alternative names: ---
Privilege level: service

This command starts the "System Network Center". To operate it, you will need a mouse.
The "System Network Center" you can end with "Exit". If you do not wish to end the "System
Network Center", then switch to the HMI with the following key combination:
<Recall> + <MENU SELECT> (Area switchover key) or
<F9> + <F10> on an external keyboard

NCU operating system (IM7)

50 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Configuring the system
2.5 Description of the actions

Reference
A description of the settings in the "System Network Center" is provided in the Operating
Components and Networking Manual.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 51
Configuring the system
2.5 Description of the actions

NCU operating system (IM7)

52 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
Service and diagnostics 3
3.1 Creating a service system

Overview
To backup user data or the complete CompactFlash Card, proceed as follows:
● Creating a service system.
● Backing up the license
● Backup: Data backup on USB storage medium or on a network drive.
● System diagnostics
– Output network settings
– Changing the network settings
– Starting the VNC Viewer
To restore the user data or the complete CompactFlash Card, proceed as follows:
● Restore/Recover: Restore the data from USB storage medium or from network drive.
● Carry out software update.
● Carry out firmware update.

Capacity

Note
CompactFlash Card > 1 GB
A CompactFlash Card with a capacity of > 1 GB is not partitioned, but behaves just like a
1 GB CompactFlash Card.

3.1.1 How do you create a service system for the NCU?

Purpose
In case service is needed, create a portable "Emergency Boot System" (EBS) on a USB
memory. Thus you can start the booting of the NCU from the service system in order to carry
out various service tasks, such as data backup or updates, in a service shell.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 53
Service and diagnostics
3.1 Creating a service system

Two partitions are created on the service system:

● A Linux partition that is invisible under Windows.
● An FAT partition for DOS or Windows applications.
The FAT partition can be read and written to under Linux as well as from a Windows
system. The FAT partition can be addressed under the path/data in a command shell
under Linux.

Scope of delivery
To create a service system on a USB storage medium, the following files are included on
CD:
● an executable file installdisk.exe
● an image file linuxbase-512M.img for USB-FlashDrive with 512 MB
● an image file linuxbase-resize.img for USB-FlashDrive > 512 MB
● a file with the newest information siemensd.txt

Recommendation:
It is better to use SIMATIC PC USB-FlashDrive.

Note
To create the service system, you need administrator rights.
All data already on the USB storage medium will be deleted.
The transfer is optimized for USB 2.0; therefore, the transmission to the USB storage
medium takes longer when using USB 1.1 than USB 2.0

Proceed as follows
To create a service system on a 512 MB USB storage medium:
1. Copy the service system onto a local hard disk of your programming device (PG) or PC.
2. Connect the USB storage medium to the USB interface of the PG/PC.
3. Determine in Windows Explorer which drive letter the USB storage medium was
assigned, e.g. H:
4. Open a DOS shell and change to the directory in which the files for the service system
are stored.
5. In the DOS shell, enter the following command:
installdisk ––verbose ––blocksize 1m linuxbase-512M.img h:
Result:
The image is transferred to the USB storage medium; a partition for Linux and a FAT
partition for Windows systems are created.

NCU operating system (IM7)

54 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Service and diagnostics
3.1 Creating a service system

1. Disconnect the USB storage medium and connect it again.

Result:
After this has been completed successfully, you will have a bootable service system on
the USB storage medium.

NOTICE
USB storage medium > 512 MB:
If you use a USB storage medium with a storage capacity > 512 MB as service system,
there is a further variant, "linuxbase-resize.img", so that the storage capacity of the USB
storage medium is retained.

To create a service system on a USB storage medium > 512 MB:

1. Copy the service system onto a local hard disk of your PG/PC.
2. Connect the USB storage medium to the USB interface of the PG/PC.
3. Determine in Windows Explorer which drive letter the USB storage medium was
assigned, e.g. H:
4. Open a DOS shell and change to the directory in which the files for the service system
are stored.
5. In the DOS shell, enter the following command:
installdisk ––verbose ––blocksize 1m linuxbase-resize.img h:
Result: The image is transferred to the USB storage medium.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 55
Service and diagnostics
3.1 Creating a service system

3.1.2 This is how you operate the service system

Connecting-up the service system

Procedure:
1. Connect the USB storage medium to the USB interface X125 or X135 of the NCU.
2. Switch-off the system and then switch on again.
OR
3. Press the "Reset" button.
The service system is unzipped from the USB storage medium when the NCU boots for
the first time: Only then can the USB storage medium be used as service system and the
entire storage capacity is available.

Operating the service system

Keys and softkeys to navigate in the service system:

Softkey Key on OP External Description

keyboard
HSK1 <F1> Moves the cursor down a row

HSK2 <F2> Moves the cursor up a row

Page HSK3 <F3> Moves the cursor down a page

Page HSK4 <F4> Moves the cursor up a page

Char HSK5 <F5> Inserts text or digits

Char HSK6 <F6> Inserts text or digits

VSK7 ← Cancel / Return

Cancel

VSK8 → OK / Confirm
Ok

--- Pos1 Moves the cursor to the top row

--- End Moves the cursor to the bottom row

NCU operating system (IM7)

56 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Service and diagnostics
3.1 Creating a service system

3.1.3 Diagnostics functions

Functions of the service menu

The following functions for service and diagnostics are available on the service system:

Figure 3-1 Service menu

Overview of the main menu:

Main menu Description Reference to chapter/manual

Firmware Update BIOS update or perform a PLC BIOS This is how you update the firmware
update. (Page 75)
VNC Viewer Start a VNC Viewer Calling the VNC Viewer (Page 84)
Diagnosis Starting a diagnostic function to display Performing system diagnostics
network-connection data and data on the (Page 79)
system CompactFlash Card.
Backup NCU Software and Data Backup system and user data on the USB Backup data via the service menu
FlashDrive or network drive. (Page 63)
Update NCU Software and Data Upgrade the system from the USB This is how you update the software
FlashDrive or network drive. (Page 77)
Restore NCU Software and Data Restore system and user data from the Backup data via the service menu
USB storage medium or network drive. (Page 63)

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 57
Service and diagnostics
3.1 Creating a service system

Main menu Description Reference to chapter/manual

Modify NCU Settings  Change network settings This is how you change the system
 Activate/deactivate HMI settings (Page 81)
 Restore delivery condition of the
following components:
– HMI
– NCK
– PLC
– Drive
Service Shell A Service Shell is opened in order to input Backing up data via the service shell
service commands. (Page 70)
Service Commands (Page 31)

NCU operating system (IM7)

58 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Service and diagnostics
3.1 Creating a service system

3.1.4 This is how you connect to a network drive

Connecting network drives

1. Select "Connect to network drive".
2. Enter the complete path name of the network drive.
3. Register yourself with a user name with access authorization to this drive.
Note the syntax of the examples specified:

Figure 3-2 Connecting network drives

4. Confirm with "Ok". You are then prompted to enter a password.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 59
Service and diagnostics
3.2 Backup license

3.2 Backup license

Validity of the license key

The license key corresponds to the serial number of the CompactFlash Card. If the
CompactFlash Card is replaced for a SINUMERIK 840D sl, the license key loses its validity
and the system is no longer ready for operation.
This situation can occur for a defective hardware of the system CompactFlash Card.

Application
For the following cases, backup the license key of the CompactFlash Card on a USB storage
medium or on a network drive:
● Software update without license key
● System software error without defective hardware

NOTICE
Replacement CompactFlash Card
The following data are required in order to obtain a valid license key after replacing the
system CompactFlash Card: The serial number of the defective and the new
CompactFlash Card.

NCU operating system (IM7)

60 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Service and diagnostics
3.2 Backup license

3.2.1 This is how you backup the license key

Backing up the license key on a USB storage medium

Procedure:
1. In the main menu, select the menu item "Backup NCU Software and Data".
The following menu is displayed:

Figure 3-3 Backing up licenses

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 61
Service and diagnostics
3.2 Backup license

2. Select the menu item "Backup license key to USB memory stick".
The following menu is displayed:

Figure 3-4 Save license key

The license key is backed up in the specified directory together with the serial number of the
CompactFlash Card.

See also
The procedure is essentially the same as for "Backup license key to network drive". In
addition, you connect to a network drive:
This is how you connect to a network drive (Page 59)

NCU operating system (IM7)

62 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Service and diagnostics
3.3 Backup data via the service menu

3.3 Backup data via the service menu

3.3.1 This is how you backup user data

Backing up and restoring user data

Procedure:
1. In the main menu, select the menu item "Backup NCU Software and Data".
2. Select "Backup user data to USB memory stick" and confirm with "Ok".
3. Enter a complete file name - as shown in the example:

Figure 3-5 Entering a file name

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 63
Service and diagnostics
3.3 Backup data via the service menu

4. Confirm with "Ok". The following message is output after the operation has been
successfully completed:

Figure 3-6 Operation complete

See also
The procedure for "Backup user data to network drive" is essentially the same. In addition,
you connect to a network drive:
This is how you connect to a network drive (Page 59)

NCU operating system (IM7)

64 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Service and diagnostics
3.3 Backup data via the service menu

3.3.2 This is how you restore user data

Restoring user data

Procedure:
1. In the main menu, select the menu item "Restore NCU Software and Data".
The following menu is displayed:

Figure 3-7 Restoring user data

2. Select "Restore user data from USB memory stick" and confirm with "Ok".
The list of the tgz files available on the USB storage medium are displayed.
3. Select the appropriate tgz file and confirm with "Ok".
A message is output after the operation has been successfully completed.

See also
The procedure for "Restore user data from network drive" is essentially the same. In
addition, you connect to a network drive:
This is how you connect to a network drive (Page 59)

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 65
Service and diagnostics
3.3 Backup data via the service menu

3.3.3 This is how you create a complete backup of the CompactFlash Card

Creating a complete backup

Procedure:
1. In the main menu, select the menu item "Backup NCU Software and Data".
The following menu is displayed:

Figure 3-8 Backup up

2. Select "Backup complete CF card to USB memory stick" and confirm with "OK".

NCU operating system (IM7)

66 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Service and diagnostics
3.3 Backup data via the service menu

3. Enter a complete file name - as specified in the example.

4. Confirm with "OK". This can take several minutes.
The operation is displayed:

Figure 3-9 Backing up ...

A message is output after the operation has been successfully completed.

See also
The procedure for "Backup complete CF card to network drive" is essentially the same. In
addition, you connect to a network drive:
This is how you connect to a network drive (Page 59)

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 67
Service and diagnostics
3.3 Backup data via the service menu

3.3.4 This is how you install a complete system backup

Installing the complete backup

With this menu item, a complete backup of the data from the service system or from a
network drive is installed on the CompactFlash Card, i.e. this backup includes both the
system software as well as also the user data.

NOTICE
Formatting
This procedure corresponds to formatting the CompactFlash Card and all of the existing
data are overwritten.

Installing the complete backup

Procedure:
1. In the main menu, select the menu item "Update NCU Software and Data".
The following menu is displayed:

Figure 3-10 Recover system

NCU operating system (IM7)

68 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Service and diagnostics
3.3 Backup data via the service menu

2. Select the menu item "Recover system from USB memory stick (reformat CF card)" and
confirm with "Ok".
The list of the tgz files available on the USB storage medium is displayed.
3. Select the appropriate tgz file and confirm with "Ok".
A message is output after the operation has been successfully completed.

Completion
The system must be restarted in order that the new data become effective.

See also
The procedure for "Recover system from network drive (reformat CF card)" is essentially the
same. In addition, you connect to a network drive:
This is how you connect to a network drive (Page 59)

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 69
Service and diagnostics
3.4 Backing up data via the service shell

3.4 Backing up data via the service shell

Backing up and restoring using a service shell

To call a service shell, depending on the configuration, the following possibilities are
available:

(I)
Configuration of NCU with TCU: the service shell is called under Linux.
(II)
Configuring the NCU with PCU 50 or programming device (PG).
A service shell can be called under:
 on the NCU under Linux
 on the PCU/PG using the VNC Viewer (system network or company network)
 on the PCU/PG using WinSCP (system network or company network)

3.4.1 This is how you save data on a service system

Proceed as follows
To back up the complete system:
1. Connect the service system to a USB interface (X125 or X135) of the NCU and press the
reset button.
Alternatively, you can switch the NCU off, connect the service system, and switch the
NCU on again.
Result: The NCU boots from the service system.
2. In the main menu, select the menu item "Service Shell".
3. Log on as a service technician using the user name "manufact" and password
"SUNRISE".
4. Using the command "sc backup" you can create the backup file "backup01.tgz".
The directory /data on the service system is provided for backup files. The complete path
should be specified.
5. Choose –full, to backup all data on the CompactFlash Card, or –user, if you only want to
backup user data.
Example: sc backup –full /data/backup01.tgz

Result:
A backup file of the complete CompactFlash Card is created under /data on the service
system on the USB storage medium.

NCU operating system (IM7)

70 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Service and diagnostics
3.4 Backing up data via the service shell

3.4.2 This is how you restore data from the service system

Proceed as follows
To restore the complete system:
1. Connect the service system to a USB interface (X125 or X135) of the NCU and press the
reset button.
Alternatively, you can switch the NCU off, connect the service system, and switch the
NCU on again.
Result: The NCU boots from the service system and the main menu is displayed.
2. In the main menu, select the menu item "Service Shell".
3. Log on as a service technician using the user name "manufact" and password
"SUNRISE".
4. With the command "sc restore" you can write the backup file "backup01" from the service
system back to the CompactFlash Card in the NCU. The complete path should be
specified.
Example: sc restore /data/backup01.tgz

Result:
The system state stored in the file "backup01" is restored on the NCU.

Note
If access to the system data on the CompactFlash Card is not possible because the
CompactFlash Card is defective or empty, you can only log in as user "admin" with the
password "SUNRISE" and no longer as the user "manufact".

3.4.3 This is how you save data on a network drive

Sequence
Proceed as follows:
● Connect the service system.
● "Service Shell" open.
● Establish a connection to a network drive.
● Create a backup file.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 71
Service and diagnostics
3.4 Backing up data via the service shell

Scenario I: Start Command Shell under Linux

Procedure:
1. Connect the service system to the USB interface X125 or X135 of the NCU.
2. In the main menu, select the menu item "Service Shell".
3. Log on as a service technician using the user name "manufact" and password
"SUNRISE".
4. Use the command "sc connect" to connect the network drive:
sc connect //username%password@server/share /tmp/backup
Please enter here the user name and the password for the network drive that is to be
connected to.
5. Using the command "sc save", create the backup file "backup01".
Choose –full, to backup all data on the CompactFlash Card, or –user, if you only want to
backup user data in the directory /user.
Example: sc save –full /tmp/backup/backup01

Result:
A backup file of the complete CompactFlash Card is created under the specified path on
the network drive.

Scenario II: Start the command shell with WinSCP on the programming device:
Procedure:
1. Start WinSCP and enter the following data in the log-on window:
– IP address of the NCU (or, if required, host name)
– User name "manufact" with password "SUNRISE".
2. Select in the menu "Commands" → "Open Terminal".
3. Execute the data backup using the commands described in steps 4 to 6 from scenario I.

Scenario II: Start the command shell using the VNC Viewer on the programming device
Procedure:
1. Start the VNC Viewer and connect to the NCU using the IP address (or where relevant,
using the host name)
2. Log on under the "manufact" user name with the password "SUNRISE".
3. To restore the data, enter the corresponding commands as described under steps 3 to 5
in scenario I.

NCU operating system (IM7)

72 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Service and diagnostics
3.4 Backing up data via the service shell

3.4.4 This is how you restore data from the network drive

Sequence
Proceed as follows:
● Connect the service system.
● "Service Shell" open.
● Establish a connection to a network drive.
● Restore the data.

Scenario I: Start command shell under Linux

1. Connect the service system to the USB interface X125 or X135 of the NCU.
2. In the main menu, select the menu item "Service Shell".
3. Log on as a service technician using the user name "manufact" and password
"SUNRISE".
4. Use the command "sc connect" to connect the network drive:
sc connect //username%password@server/share /tmp/backup
1. Please enter here the user name and the password for the network drive that is to be
connected to.
To completely restore the system (system data and user data), enter the following: sc
restore –full backup01
Result: The whole system is overwritten by the backup data.
2. To restore user data only, enter the following command:
sc restore –user backup01
Result: The user data are written back again.
All subsystems are then restarted: sc start all

Result:
The system state stored in the file "backup01.tgz" is restored on the NCU.

Scenario II: Start the command shell with WinSCP on the programming device:
Procedure:
1. Start WinSCP and enter the following data in the log-on window:
– IP address of the NCU (or, if required, host name)
– User name "manufact" with password "SUNRISE".
2. Select in the menu "Commands" → "Open Terminal".
3. To restore the data, enter the corresponding commands as described under steps 3 to 5
in scenario I.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 73
Service and diagnostics
3.4 Backing up data via the service shell

Scenario II: Start the command shell using the VNC Viewer on the programming device
Procedure:
1. Start the VNC Viewer and connect to the NCU using the IP address (or where relevant,
using the host name)
2. Log on under the "manufact" user name with the password "SUNRISE".
3. To restore the data, enter the corresponding commands as described under steps 3 to 5
in scenario I.

NCU operating system (IM7)

74 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Service and diagnostics
3.5 Updating the software

3.5 Updating the software

3.5.1 This is how you update the firmware

Firmware Update
When service is required, it may be necessary for a service technician to install a BIOS
update. Siemens provides the corresponding update file. Possible formats include: *.img or
*.rom or *.bin. Or, the update file is already supplied on the service system, then step 1 is
eliminated.
Procedure:
1. Copy the update file to the service system.
2. Connect the service system to interface X125 or X135 of the NCU.
3. Switch on the system.
4. In the main menu, select the menu item "Firmware Update".
The following menu is displayed:

Figure 3-11 Firmware update

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 75
Service and diagnostics
3.5 Updating the software

5. Select "BIOS Update" and confirm with "Ok".

The BIOS version installed on the NCU and the update files available in the service
system are output:

Figure 3-12 Select the updates

6. Select the update file and confirm with "OK".

A "Restart" is then required.
The procedure to update the PLC-BIOS is essentially the same as the procedure described
here.

Note
Fall back strategy
Before the BIOS update is installed, a backup of the installed BIOS version is saved on the
service system.
For safety reasons, only files can be selected that are suitable and are appropriate for this
NCU.

NCU operating system (IM7)

76 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Service and diagnostics
3.5 Updating the software

3.5.2 This is how you update the software

Update / Recover
The following options are available:
● Update the software from the service system or from the network drive.
● Completely restore the CompactFlash Card with the system software from the service
system or from the network drive (Recover system ...).

Updating the software

Procedure:
1. In the main menu, select the menu item "Update NCU Software and Data".
The following menu is displayed:

Figure 3-13 Software update

2. Select the menu item "Update system software from USB memory stick".
The list of the tgz files available on the USB storage medium are displayed.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 77
Service and diagnostics
3.5 Updating the software

3. In order to check which software version contains the tgz file, first select the tgz file, then
press "Show version".
The following information is output:

Figure 3-14 Version information

4. Select the appropriate tgz file and confirm with "Ok".

A message is output after the update has been successfully completed.

Completion
The system must be restarted in order that the new data become effective.

See also
The procedure for "Update system software from network drive" is essentially the same. In
addition, you connect to a network drive: This is how you connect to a network drive
(Page 59)
For a complete backup of the system: This is how you install a complete system backup
(Page 68)

NCU operating system (IM7)

78 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Service and diagnostics
3.6 System diagnostics

3.6 System diagnostics

3.6.1 Performing system diagnostics

Overview of diagnostic functions

The following diagnostic functions to display network settings are included in this menu:

Figure 3-15 Diagnostics functions

System diagnosis Description

Show all network settings Connection data of all Ethernet interfaces is displayed.
Show network settings X120 The connection data of interface X120 is displayed.
(system network)
Show network settings X127 The connection data of interface X127 is displayed.
(engineering network)
Show network settings X130 The connection data of interface X130 is displayed.
(factory network)

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 79
Service and diagnostics
3.6 System diagnostics

System diagnosis Description

Show card identification The following data of the system CompactFlash Card is
output:
 Serial number
 System software version
 Hardware version (NCU)
Check card integrity Checking the CompactFlash Card system

Example: Connection data of all Ethernet interfaces of the NCU:

Figure 3-16 NCU: Interfaces

See also
This is how you check the CompactFlash Card (Page 82)

NCU operating system (IM7)

80 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Service and diagnostics
3.6 System diagnostics

3.6.2 This is how you change the system settings

Modify NCU Settings

You can change the following system settings in this menu:

Figure 3-17 Changing system settings

Menu item Description

Change network settings Changing network settings of the NCU.
Disable internal HMI (currently enabled) Activating/deactivating an HMI task
Reset HMI data to factory defaults Restoring the delivery condition of HMI data.
Reset NC data to factory defaults Restoring the delivery condition of NC data.
Reset PLC data to factory defaults Restoring the delivery condition of PLC data.
Reset DRIVE data to factory defaults Restoring the delivery condition of drive data.

NOTICE
Reset ... data to factory defaults
If this data is restored to the delivery condition, then all specific commissioning settings that
were performed up until now are overwritten.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 81
Service and diagnostics
3.6 System diagnostics

3.6.3 This is how you check the CompactFlash Card

Displaying identification data

Procedure:
1. In the main menu, select the menu item "Diagnosis".
The following menu is displayed:

Figure 3-18 System diagnostics

NCU operating system (IM7)

82 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Service and diagnostics
3.6 System diagnostics

2. Select the menu item "Show card identification".

The following data for identification are output:

Figure 3-19 Identification

3. Select the menu item "Check card integritiy".

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 83
Service and diagnostics
3.6 System diagnostics

The CompactFlash Card is checked for errors:

Figure 3-20 Check

Note
This procedure can take several minutes.

3.6.4 Calling the VNC Viewer

Purpose
The VNC Viewer is used to connect directly with a VNC Server and, for example, to operate
an HMI application.
Furthermore, it enables you to call up a list of all the network devices, thereby obtaining an
overview of the system network.

NCU operating system (IM7)

84 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Service and diagnostics
3.6 System diagnostics

Starting the VNC Viewer

Procedure:
1. In the main menu, select the menu item "VNC Viewer".
The following menu is displayed:

Figure 3-21 VNC Viewer

2. To start the VNC Viewer, enter the following connection data:

– Server name, e.g. IP address or DNS.
– The password is optional and can also be left empty.
– The following assignment applies to the "Session number":

Number Meaning
Session 0 HMI-Applikation
Session 4 Command Shell
Session 5 System logfile
Session 6 System Network Center (SNC)

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 85
Service and diagnostics
3.6 System diagnostics

3.6.5 WinSCP and PuTTY

Use
The programs WinSCP and PuTTY are freely-available open source programs for Windows.
WinSCP is intended especially for transferring files from and to Linux systems, PuTTY for
the remote operation of a command shell.
● WinSCP can be downloaded via the following link: http://winscp.net/eng/download.php
(http://winscp.net/eng/download.php) (Installation Package).
WinSCP also offers a "command shell" that is limited so that commands can be issued,
but no callbacks can be answered.
● PuTTY, by contrast, offers a complete command shell.
PuTTY web page: http://www.chiark.greenend.org.uk/~sgtatham/putty
(http://www.chiark.greenend.org.uk/~sgtatham/putty)
With both programs, a service technician can log onto the NCU and carry out service tasks.
The username ‘manufact’ with the password ‘SUNRISE’ is available for the Siemens service
technician.

Starting WinSCP
WinSCP is started from Windows after the service technician has logged onto the NCU with
which he is connected using the corresponding authorization (e.g. as user "manufact" with
password "SUNRISE").
From the "Commands“ menu, select ”Open terminal” to open a command shell. There you
can carry out the service commands in the usual way.

NCU operating system (IM7)

86 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
Appendix A
A.1 Abbreviations

CF CompactFlash card: Memory card

CFS Cluster File System
DCK Direct Control Keys Direct control keys
DCP Discovery and Basic Configuration Protocol
DHCP Dynamic Host Configuration Protocol: Dynamic assignment of an IP address and other configuration
parameters on a computer in a network
DNS Domain Name System: Conversion of domain names into IP addresses
EBS Emergency Boot System
EKS Electronic Key System: System to check the identity of a user (authentication system)
EUNA End User Notification Administration
HMI Human Machine Interface: Operator interface
IRT Isochronous Realtime (Ethernet)
LLDP Link Layer Discovery Protocol: multi-vendor Layer 2 Protocol defined in accordance with the IEEE-
802.1AB standard, allows information to be exchanged between devices.
MAC Media Access Control: The MAC address is a 48-bit Ethernet ID.
MCP Machine Control Panel Machine control panel
MPI Multi-Point Interface Multiple interface
MUI Multilanguage User Interface
NCK Numerical Control Kernel: NC kernel with block preparation, travel range, etc.
NCU Numerical Control Unit: NCK hardware unit
NRT Non-Realtime (Ethernet)
NTFS New Technology File System
NTP Network Time Protocol: Standard for synchronizing clocks in the entire network
NTPD NTP Daemon:
Utility that runs in the background and does not have to be started by the user.
PCU PC Unit: Computer unit
PDEV Physical device
PG Programming device
PLC Programmable Logic Control: PLC
RAM Random Access Memory: Program memory which can be read and written into
RDY Ready The system is ready to operate.
SNMP Simple Network Management Protocol (network protocol for monitoring and controlling network elements
such as routers, servers, switches, and printers from a central station)
TCU Thin Client Unit
TFTP Trivial File Transfer Protocol: Very simple data transmission protocol
UDP User Datagram Protocol: NTP is mostly processed via UDP.
USB Universal Serial Bus

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 87
Appendix
A.1 Abbreviations

UPS Uninterruptible power supply

UTC Universal Time, Coordinated Coordinated universal time
VNC Virtual Network Computing

NCU operating system (IM7)

88 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Appendix
A.2 Licenses for WinSCP and PuTTY

A.2 Licenses for WinSCP and PuTTY

Copyright of license texts

WinSCP: Copyright © 2000-2005 Martin Přikryl.

The application is protected by GNU General Public Licence.
Part of the code of this software comes from program PuTTY 0.58 © 1997-
2005 Simon Tatham. License agreements for using PuTTY are part of
WinSCP license agreement.
PuTTYgen and Pageant applications distributed with WinSCP installation package are
© 1997-2005 Simon Tatham.
PuTTYgen and Pageant applications distributed with WinSCP installation
package are © 1997-2005 Simon Tatham.

A.2.1 GNU License

GNU General Public License

GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but
changing it is not allowed.

Preamble
The licenses for most software are designed to take away your freedom to share and change
it. By contrast, the GNU General Public License is intended to guarantee your freedom to
share and change free software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software Foundation's software and to
any other program whose authors commit to using it. (Some other Free Software Foundation
software is covered by the GNU Lesser General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public
Licenses are designed to make sure that you have the freedom to distribute copies of free
software (and charge for this service if you wish), that you receive source code or can get it if
you want it, that you can change the software or use pieces of it in new free programs; and
that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these
rights or to ask you to surrender the rights. These restrictions translate to certain
responsibilities for you if you distribute copies of the software, or if you modify it.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 89
Appendix
A.2 Licenses for WinSCP and PuTTY

For example, if you distribute copies of such a program, whether free of charge or for a fee,
you must give the recipients all the rights that you have. You must make sure that they, too,
receive or can get the source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you this
license which gives you legal permission to copy, distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain that everyone
understands that there is no warranty for this free software. If the software is modified by
someone else and passed on, we want its recipients to know that what they have is not the
original, so that any problems introduced by others will not reflect on the original authors'
reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the
danger that redistributors of a free program will individually obtain patent licenses, in effect
making the program proprietary. To prevent this, we have made it clear that any patent must
be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and modification follow:

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed by the
copyright holder saying it may be distributed under the terms of this General Public License.
The "Program", below, refers to any such program or work, and a "work based on the
Program" means either the Program or any derivative work under copyright law: that is to
say, a work containing the Program or a portion of it, either verbatim or with modifications
and/or translated into another language. (Hereinafter, translation is included without
limitation in the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not covered by this License;
they are outside its scope. The act of running the Program is not restricted, and the output
from the Program is covered only if its contents constitute a work based on the Program
(independent of having been made by running the Program). Whether that is true depends
on what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as you receive
it, in any medium, provided that you conspicuously and appropriately publish on each copy
an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that
refer to this License and to the absence of any warranty; and give any other recipients of the
Program a copy of this License along with the Program. You may charge a fee for the
physical act of transferring a copy, and you may at your option offer warranty protection in
exchange for a fee.

2. You may modify your copy or copies of the program or any portion of it, thus forming a
work based on the program, and copy and distribute such modifications or work under the
terms of Section 1 above, provided that you also meet all of these conditions:
You must cause the modified files to carry prominent notices stating that you changed the
files and the date of any change.

NCU operating system (IM7)

90 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Appendix
A.2 Licenses for WinSCP and PuTTY

You must cause any work that you distribute or publish, that in whole or in part contains or is
derived from the Program or any part thereof, to be licensed as a whole at no charge to all
third parties under the terms of this License.
If the modified program normally reads commands interactively when run, you must cause it,
when started running for such interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a notice that there is no
warranty (or else, saying that you provide a warranty) and that users may redistribute the
program under these conditions, and telling the user how to view a copy of this License.
(Exception: if the Program itself is interactive but does not normally print such an
announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that
work are not derived from the Program, and can be reasonably considered independent and
separate works in themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you distribute the same
sections as part of a whole which is a work based on the Program, the distribution of the
whole must be on the terms of this License, whose permissions for other licensees extend to
the entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written
entirely by you; rather, the intent is to exercise the right to control the distribution of
derivative or collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program
(or with a work based on the Program) on a volume of a storage or distribution medium does
not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in
object code or executable form under the terms of Sections 1 and 2 above provided that you
also do one of the following:
Accompany it with the complete corresponding machine-readable source code, which must
be distributed under the terms of Sections 1 and 2 above on a medium customarily used for
software interchange; or,
Accompany it with a written offer, valid for at least three years, to give any third party, for a
charge no more than your cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be distributed under the terms
of Sections 1 and 2 above on a medium customarily used for software interchange; or,
Accompany it with the information you received as to the offer to distribute corresponding
source code. (This alternative is allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such an offer, in accord with
Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to
it. For an executable work, complete source code means all the source code for all modules
it contains, plus any associated interface definition files, plus the scripts used to control
compilation and installation of the executable. However, as a special exception, the source
code distributed need not include anything that is normally distributed (in either source or
binary form) with the major components (compiler, kernel, and so on) of the operating
system on which the executable runs, unless that component itself accompanies the
executable.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 91
Appendix
A.2 Licenses for WinSCP and PuTTY

If distribution of executable or object code is made by offering access to copy from a

designated place, then offering equivalent access to copy the source code from the same
place counts as distribution of the source code, even though third parties are not compelled
to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as expressly
provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute
the Program is void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under this License will not
have their licenses terminated so long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it. However,
nothing else grants you permission to modify or distribute the Program or its derivative
works. These actions are prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the Program), you indicate your
acceptance of this License to do so, and all its terms and conditions for copying, distributing
or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient
automatically receives a license from the original licensor to copy, distribute or modify the
Program subject to these terms and conditions. You may not impose any further restrictions
on the recipients' exercise of the rights granted herein. You are not responsible for enforcing
compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any

other reason (not limited to patent issues), conditions are imposed on you (whether by court
order, agreement or otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot distribute so as to satisfy
simultaneously your obligations under this License and any other pertinent obligations, then
as a consequence you may not distribute the Program at all. For example, if a patent license
would not permit royalty-free redistribution of the Program by all those who receive copies
directly or indirectly through you, then the only way you could satisfy both it and this License
would be to refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under any particular
circumstance, the balance of the section is intended to apply and the section as a whole is
intended to apply in other circumstances. It is not the purpose of this section to induce you to
infringe any patents or other property right claims or to contest validity of any such claims;
this section has the sole purpose of protecting the integrity of the free software distribution
system, which is implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed through that system in
reliance on consistent application of that system; it is up to the author/donor to decide if he or
she is willing to distribute software through any other system and a licensee cannot impose
that choice. This section is intended to make thoroughly clear what is believed to be a
consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by
patents or by copyrighted interfaces, the original copyright holder who places the Program
under this License may add an explicit geographical distribution limitation excluding those
countries, so that distribution is permitted only in or among countries not thus excluded. In
such case, this License incorporates the limitation as if written in the body of this License.

NCU operating system (IM7)

92 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Appendix
A.2 Licenses for WinSCP and PuTTY

9. The Free Software Foundation may publish revised and/or new versions of the General
Public License from time to time. Such new versions will be similar in spirit to the present
version, but may differ in detail to address new problems or concerns. Each version is given
a distinguishing version number. If the Program specifies a version number of this License
which applies to it and "any later version", you have the option of following the terms and
conditions either of that version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of this License, you may
choose any version ever published by the Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programs whose
distribution conditions are different, write to the author to ask for permission. For software
which is copyrighted by the Free Software Foundation, write to the Free Software
Foundation; we sometimes make exceptions for this. Our decision will be guided by the two
goals of preserving the free status of all derivatives of our free software and of promoting the
sharing and reuse of software generally.

NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS
AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF
ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN

WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the
public, the best way to achieve this is to make it free software which everyone can
redistribute and change under these terms. To do so, attach the following notices to the
program. It is safest to attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the "copyright" line and a
pointer to where the full notice is found. one line to give the program's name and an idea of
what it does.
Copyright (C) yyyy name of author

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 93
Appendix
A.2 Licenses for WinSCP and PuTTY

This program is free software; you can redistribute it and/or modify it under the terms of the
GNU General Public License as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this
program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
Boston, MA 02110-1301, USA.
Also add information on how to contact you by electronic and paper mail. If the program is
interactive, make it output a short notice like this when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with
ABSOLUTELY NO WARRANTY; for details type 'show w'. This is free software, and you are
welcome to redistribute it under certain conditions; type 'show c' for details.
The hypothetical commands `show w' and 'show c' should show the appropriate parts of the
General Public License. Of course, the commands you use may be called something other
than 'show w' and 'show c'; they could even be mouse-clicks or menu items -- whatever suits
your program.
You should also get your employer (if you work as a programmer) or your school, if any, to
sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the
names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program 'Gnomovision'(which
makes passes at compilers) written by James Hacker.

signature of Ty Coon, 1 April 1989

Ty Coon, President of Vice

This General Public License does not permit incorporating your program into proprietary
programs. If your program is a subroutine library, you may consider it more useful to permit
linking proprietary applications with the library. If this is what you want to do, use the GNU
Lesser General Public License instead of this License.
Updated: $Date: 2005/06/07 16:30:55 $ $Author: novalis $

A.2.2 PuTTY Licence

PuTTY Licence
The PuTTY executables and source code are distributed under the MIT licence, which is
similar in effect to the BSD licence. (This licence is Open Source certified and complies with
the Debian Free Software Guidelines.)

NCU operating system (IM7)

94 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
 Appendix
A.2 Licenses for WinSCP and PuTTY

The precise licence text, as given in the file LICENCE in the source distribution, is as follows:
PuTTY is copyright 1997-2005 Simon Tatham.
Portions copyright Robert de Bath, Joris van Rantwijk, Delian Delchev, Andreas Schultz,
Jeroen Massar, Wez Furlong, Nicolas Barry, Justin Bradford, Ben Harris, Malcolm Smith,
Ahmad Khalifa, Markus Kuhn, and CORE SDI S.A.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software
and associated documentation files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or
substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL SIMON TATHAM BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
In particular, anybody (even companies) can use PuTTY without restriction (even for
commercial purposes) and owe nothing to me or anybody else. Also, apart from having to
maintain the copyright notice and the licence text in derivative products, anybody (even
companies) can adapt the PuTTY source code into their own programs and products (even
commercial products) and owe nothing to me or anybody else. And, of course, there is no
warranty and if PuTTY causes you damage you're on your own, so don't use it if you're
unhappy with that.
In particular, note that the MIT licence is compatible with the GNU GPL. So if you want to
incorporate PuTTY or pieces of PuTTY into a GPL program, there's no problem with that.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 95
Appendix
A.2 Licenses for WinSCP and PuTTY

NCU operating system (IM7)

96 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
Glossary

CFS (Compressed File System)

A CFS (file extension ".cfs") is a compressed file system, similar to a zip file. It contains files
and subdirectories that look like normal files on the controller at runtime. Files and directories
contained in a CFS cannot be changed. They are decompressed at runtime as required.

Network interface
The network interface is an interface that enables network communication. These are the
Ethernet interfaces on the NCU.

NFS (Network File System)

NFS is the most common protocol for remote file systems in the world of Unix, and is also
available for Windows. NFS is closely based on the Unix privilege model – each time a file is
accessed, a UID and GID are supplied which the server then uses to decide whether the
operation is permitted. The server relies on the client to provide the correct IDs.

Remote File System

A file system that is contacted over the network. The files are physically located on another
computer in the network (the "server"), but appear locally the same as all other files.
Operations performed on these files are sent via the network to the server, instead of being
executed directly on a local storage medium (such as a hard drive or CompactFlash Card).
As a server usually exports more than one file system, a name for the required file system
must also be entered in addition to the name of the server.

SMB (Server Message Block)

SMB is the underlying protocol of MS Windows file systems (also known as drives, releases,
shares, etc.). SMB connections are always active in the context of a specific user, who must
be known to the server. Exported file systems have a name (release name), by which they
can be addressed. The client does not need to know the concrete path on the server.

Subsystem
A subsystem is a CFS that not only contains a collection of files, but also executes a
program, for example, at runtime. To do this, the CFS contains a script that is used to control
the starting and stopping of this program.
For this reason, only administrators are permitted to set up NFS file systems, and NFS is
usually only implemented in uniformly administrated environments. Exported file systems on
the server are addressed directly on the server via their path.

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 97
Glossary

VNC (Virtual Network Computing)

Virtual Network Computing is a software that displays the screen contents of a remote
computer, with a running VNC server, on a local computer, with a running VNC viewer, and
in return sends keyboard and mouse movements of the local computer to the remote
computer.

NCU operating system (IM7)

98 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0
Index

Timezone, 25

7
C
7-segment display, 9
CFS (Compressed File System), 33
Coding switches, 7
A Command
Backup, (See Save)
Applications, 53
Check-cf, 36
Closeport, 37
Connect, 37
B
Disable, 39
basesys.ini, 15 Disconnect, 40
DHCPClientID, 17 Enable, 41
DHCPDNoMasterWait, 20 Help, 35
DisableIBNForwarding, 21 Openport, 42
DisablePLCTimeSync, 26 Reboot, (Siehe Restart)
DisableSubsystems, 26 Restart, 43
Domain, 17 Restore, 44
EnableCoreDumps, 26 Save, 45
EnableDHCP_IBNNet, 20 Show, 46
EnableSysNetToIBNForwarding, 20 Start, 50
ExternalDcpEnabled, 23 Stop, 50
ExternalIP, 15 CompactFlash Card, 5, 71
ExternalLldpEnabled, 23
ExternalLldpTLVsTxEnabled, 24
ExternalNetMask, 16 D
FirewallOpenPort, 25
data
Gateway, 16
Restoring, 73
Host name, 16
DHCP synchronization, 42
InternalDcpEnabled, 22
Directory structure, 5
InternalDNSDomain, 20
InternalDynRangeEnd, 19
InternalDynRangeStart, 19
E
InternalIP, 18
InternalIP_Alias, 18 Emergency Boot System, 53
InternalLldpEnabled, 23 Ethernet interfaces, 13
InternalLldpTLVsTxEnabled, 23
InternalNetMask, 18
InternalNetMask_Alias, 18 I
LogFileLimit, 25
Interfaces
Nameservers, 16
Ethernet, 33
SNMPAutLocation, 22
NCU, 13
SNMPContact, 21
IP address
SNMPFunction, 22
Setting, 14
SNMPLocation, 21
SyncModeDHCPD_SysNet, 19
Timeservers, 16

NCU operating system (IM7)

Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0 99
Index

L System
Diagnostics, 9
Load operating system, 9
Log file, 5, 26
System error, 11
N
NCK start-up switch, 7 T
NCU booting, 8
Time zone, 25
Network drive, 59
Network interface, 13
NFS (Network File System), 34
U
Update
P BIOS, 75
Firmware, 75
PLC mode selector switch, 7
User group, 31
Privilege, 31
Users (default setting), 6

R V
Remote File System, 34
VNC (Virtual Network Computing), 13
Replacement part, 60
Reset
Button, 8
W
Execute, 8
WinSCP, 86

S
Section
[DCP], 22
[ExternalInterface], 15
[IBNInterface], 20
[InternalInterface], 18
[LinuxBase], 24
[LLDP], 23
[SNMP], 21
Service command
Application, 31
Rights, 31
Syntax, 32
Service menu, 57
Service system
Backing up data, 70
Creating for the NCU, 54
Restoring data, 71
Service Tool WinSCP, 86
SMB (Server Message Block), 34
Subnet mask, 14
Subsystem, 33
Designation, 33
Synchronization
DHCP, 42

NCU operating system (IM7)

100 Commissioning Manual, 03/2010, 6FC5397-1DP10-5BA0