Generation Of The Comparison Topology Using External Software - Siemens SINUMERIK 840D sl Operating Manual

With the changeover from comparison topology to user-defined topology, the additional
properties DO activation, component activation and component number must also be specified.
On switchover to comparison topology, the data remain stored for when switch-back to user-
defined topology is performed. These data have no effect in the comparison topology.
For the deployment as user-defined topology, other necessary data is added internally and
output as binary user-defined topology file.
To deploy a user-defined topology, it is necessary to specify a CNC software version.
Figure 6-12
See also
Generation of the comparison topology using external software (Page 348)
6.6.8

Generation of the comparison topology using external software

The structure and the contents of the comparison topology for a package is an open and
documented interface, the Topo XML interface. The file format is XML.
You will find more information on this in Section Interface - Topo-XML (Page 400).
This means that it is also possible to generate the comparison topology using external software,
which is integrated in the PLM process of the machine manufacturer, e.g. ePlan, ELCAD or
similar. When required, the externally generated comparison topologies can also be read-in
in Topo as part of the production preparation for control purposes or adaptations, before they
are linked into the project when configuring with Expert or placed next to the package as
configuration file. A comparison configuration file, which is located in or next to the package,
can also be selected manually on the dialog of the "SINAMICS topology" during the runtime.
Normally, a special topology must be created for each machine version, whereas one package
can be sufficient for all machines.
SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo
Operating Manual, 11/2016, A5E36537479B-AD
Variants of the topology generation with CMC Topo
Create MyConfig - Topo
6.6 SINAMICS device configuration
389