Commissioning HMI Advanced (IM4) 08/2005
2 Functions/Parameterization
© Siemens AG, 2005. All rights reserved
IM4/2-120 SINUMERIK 840D sl/840D/840Di/810D Installation and Start-Up HMI (IAM) - 08/2005 Edition
Startup
The above files, if present, are read in when the simulation application starts up.
From the initialization data in the INITIAL.INI file, only the machine data are
interpreted by the simulation application during startup.
The files (CH(c)_xxx.INI, NC_xxx.INI and AX_SEA.INI) are read in according to the
order of their date stamp, starting with the oldest file.
DPCUSCYC.COM:
The file DPCUSCYC.COM (mapping of user cycle interfaces) is only read if in the
DPSIM.INI file in the [PRELOAD] section
CYCLES=0 or
CYCLEINTERFACE=1 is set.
The following cases are possible:
1. CYCLES=0
The corresponding cycles are not loaded into the simulation until they are
called by the simulation interpreter for the first time.
2. CYCLES=1
All cycles of the NCK and HMI Advanced are preloaded when the simulation
application is started (eliminating cycle reload times during simulation).
3. If a cycle of the same name exists on HMI Advanced and NCK, the NCK cycle
is loaded. If a cycle of the same name exists in \CUS.DIR, \CMA.DIR and
\CST.DIR, it is found and loaded first in \CUS.DIR, then in \CMA.DIR and
finally in \CST.DIR.
4. CYCLES=1 and CYCLEINTERFACE=0
The cycle interfaces are formed directly by simulation. This means that all
cycles (in \CUS.DIR, \CMA.DIR, and \CST.DIR of HMI Advanced and the NCK)
have to be loaded in advance (occupying program memory in the simulation
NC).
NC cycles
The NC cycles (CUS.DIR, CMA.DIR and CST.DIR) are copied as an image into the
corresponding directories in data management. The location is determined in the
DPSIM.INI file by the CYCLE entry (\DP.DIR\SIM.DIR) in the [MAIN] section.
Synchronization takes place when the HMI is started at every cycle
synchronization. This enables optimized access to the cycles and automatic
creation of images of the cycle interfaces.
Simulation with OEM transformations
For OEM-specific adjustments, e.g. for Compile cycles, the standard configuration,
which is normally located in <InstallationPath>\dp\dpsim.tea, can be overwritten.
To do this, you must create a dpsim.tea file containing the desired adjustments
(e.g. different values for TrafoType) in the <InstallationPath>\OEM directory. The
settings in this dpsim.tea are evaluated last and take priority over the default
settings in <InstallationPath>\dp\dpsim.tea.
To Next Page
Loading...
Need help?
General
