Information for the Changeover to the Technology CPU
9.3 Interrupt events from distributed I/Os while the CPU status is in STOP
9.3 9.3 Interrupt events from distributed I/Os while the CPU status is in STOP
Interrupt events from distributed I/Os while the CPU status is in STOP
With the new DPV1 functionality (IEC 61158/ EN 50170, volume 2, PROFIBUS), the
handling of incoming interrupt events from the distributed I/Os while the CPU status is in
STOP has also changed.
Previous response by the CPU in the STOP state:
With CPUs 312 IFM to 318-2 DP, an interrupt event was initially noted while the CPU was in
STOP mode. When the CPU status subsequently returned to RUN, the interrupt was then
fetched by an appropriate OB (e.g. OB 82).
New response by the CPU:
With the Technology CPU, an interrupt event (process or diagnostic interrupt, new DPV1
interrupts) is acknowledged by the distributed I/O while the CPU is still in STOP status, and
is entered in the diagnostic buffer if necessary (diagnostic interrupts only). When the CPU
status subsequently returns to RUN, the interrupt is no longer fetched by the OB. Possible
slave faults can be read using suitable SSL queries (e.g. read SSL 0x692 via SFC51).
9.4 9.4 Runtimes that change while the program is running
Runtimes that change while the program is running
If you have created a user program that has been fine-tuned in relation to certain processing
times, please note the following points if you are using a
Technology CPU:
• The program will run much faster on the
Technology CPU.
• Functions that require MMC access (e.g. system start-up time, program download in
RUN, return of DP station, etc), may sometimes run slower on the
Technology CPU.
9.5 9.5 Converting the diagnostic addresses of DP slaves
Converting the diagnostic addresses of DP slaves
If you are using a Technology CPU as the master, please note that you may have to
reassign the diagnostic addresses for the slaves since the changes to the DPV1 standard
sometimes require two diagnostic addresses per slave.
• The virtual slot 0 has its own address (diagnostic address of the station proxy). The
module status data for this slot (read SSL 0xD91 with SFC 51 "RDSYSST") contains IDs
that relate to the entire slave/station, e.g. the "station error ID". Failure and restoration of
the station are also signaled in OB 86 on the master via the diagnostic address of the
virtual slot 0.
S7-300 CPU Data: CPU 315T-2 DP
9-4 Manual, 12/2005, A5E00427933-02
To Next Page
Loading...
Need help?
General
