Glossary
ET 200M
254 Operating Instructions, 12/2008, EWA-4NEB780600602-08
Configuration
The process of assigning modules to mounting racks/slots and addresses. A distinction is
made between the actual configuration (= actually inserted modules) and the desired
configuration. The desired configuration is preset for
STEP 7
,
COM PROFIBUS
(or
COM ET 200 Windows
). This enables the operating system to detect any incorrect parts
during startup.
CPU
Central Processing Unit. It is part of the S7 automation system and contains control and
processing units, memory, operating system and the programming device interface.
Device names
Because a fixed IP address is assigned to the device name, an IO device must have a
device name in order to be addressed by an IO controller. With PROFINET, this procedure is
used because names are easier to handle than complex IP addresses.
The assignment of a device name for a specific IO device can be compared to setting the
PROFIBUS address of a DP slave.
When it ships, an IO device does not have a device name. The IO device can only be
addressed by an IO controller after the device has been assigned a device name, for the
transfer of configuration data (IP address and other data) in the startup phase or for the
exchange of user data in cyclic operation, for example.
The device name can alternatively be written directly in the programming device on the
SIMATIC Micro Memory Card (for the ET 200pro IO device).
Device replacement without removable media / programming device
IO devices having this function can be replaced easily:
● You do not require any removable media (e.g. Micro Memory Card) with saved device
names.
● The device name does not have to be assigned using the programming device.
Instead of being assigned a device name from the removable medium or programming
device, the IO device is now assigned a device name by the IO controller. The IO controller
uses the configured topology and the correlations derived from the IO devices. The
configured target topology must agree with the actual topology.
Diagnostic interrupt
Modules with diagnostics capabilities use diagnostic interrupts to report detected system
errors to the CPU.
In SIMATIC S7 / M7: If interrupts are enabled the module will trigger a diagnostic interrupt
when an error is detected or when an error disappears (e.g. wire breakage). The CPU then
interrupts the user program or any lower priority classes and starts processing the diagnostic
interrupt block (OB 82).
In SIMATIC S5: The diagnostic interrupt is simulated in the device-specific diagnostics.
Cyclic scanning of the relevant bits in the device-specific diagnostics will enable you to
detect errors such as wire breakage.
To Next Page
Loading...
Need help?
General
