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" 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.
Configuring the system
2.4 Service Commands
NCU operating system
40 Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1