Description Using FB390 "ALM_Control" you can control an ALM (Active Line Module) with DriveCLIQ of a SINAMICS 120S in combination with a SIMATIC CPU.
See below for the block (for STEP 7 V5) and instructions for commissioning the block:
Description Software Redundancy (SWR) is a software package for configuring fault-tolerant controllers with standard components. The controller part consists of standard CPUs of the S7-300 and S7-400 series. The redundancy link for synchronizing the redundant CPUs is achieved with standard communication mechanisms like CPs or via an MPI interface. Connection to I/O devices is via two redundant PROFIBUS DP segments to the ET-200M stations with redundant IM 153-2 interface modules. You can also implement Software Redundancy on WinAC RTX as from version 2008.
Note
More information is available in the function manual "Software Redundancy for SIMATIC S7" in Entry ID 1137637.
The following table lists modules that support software redundancy. The lowercase letter x is a wildcard character in the order numbers.
Note
The ET 200M stations must always be configured with active bus modules (6ES7195-7HB00-0XA0 or 6ES7195-7HC00-0XA0), even if the "Hot swapping of I/O modules" function is not possible with S7-300 CPUs.
Which organization blocks do you have to load into the CPU to ensure that the CPU does not go into the "STOP" status when a remote I/O fails?
Configuration Notes:
If the CPU recognizes an asynchronous or synchronous error during the cyclical run (e.g. diagnostics alarm of a DP slave or PROFINET I/O device, station failure, etc.), it calls an appropriate organization block (OB). Users thus have the option of responding to this event.
The following OBs have to be loaded in the CPU to ensure that they can be called by the CPU's operating system if an asynchronous or synchronous error occurs.
OB no.
Explanation
OB called
if
Error
category
Call upon
incoming event
Call upon
outgoing event
82
Diagnostics alarm
A diagnostics-compatible module, for which you have enabled the diagnostics alarm, detects an error and when the error is cleared
(e.g. a short circuit in the input module).
Asynchronous error
Yes
Yes
83
Remove/plug alarm1)
A module in the central or expansion devices is removed and plugged in (e.g. an input module is removed).
Asynchronous error
Yes
Yes
85
Program
cycle error
- A start event for an Alarm OB is present, but the OB cannot be executed because it has not been loaded into the CPU
- An error has occurred when accessing the instance DB of a system function block.
- An error has occurred when updating the process image (module missing or defective).
Asynchronous error
Configuration-specific
Configuration-specific
86
Module rack
failure
Failure of a DP slave in a PROFIBUS DP master system or of an IO device in the PROFINET IO system.
Asynchronous error
Yes
Yes
121
Programming
error
A programming error has occurred (e.g. called block is not loaded).
Synchronous error
Yes
No
122
IO access
error
An attempt is made to access a non-existent signal module.
Synchronous error
Yes
No
1) In the S7-300 CPU, there is no remove/plug alarm when removing/plugging in modules that are used on the PROFIBUS DP, like removing a DP slave module (exception: CPU 318-2). Depending on the DP slave used, the complete DP slave fails, which leads to OB86 "Subrack failure" being called, or standard diagnostics are performed, which leads to OB82 "Diagnostics alarm" being called.
In the S7-300 CPU, there is a remove/plug alarm only when removing/plugging in modules that are used on the PROFINET IO (e.g. removing an IO device).
If the above-mentioned organization blocks are not loaded in the CPU, the CPU switches to the "STOP" mode after attempting to call them.
Warning: If you use the error OBs, then error handling should be programmed for reliable and error-free plant operation or at least a message should be generated in case of an error. Please take into account that the CPU might no longer go into "STOP" and thus dangerous plant statuses might remain unnoticed.
Detailed information on programming the error OBs is available in the STEP 7 Online Help or in the manual "System Software for S7-300/400 System and Standard Functions" in Entry ID: 1214574.
Further information and notes: The diagnostics buffer of the CPU contains more information and notes about which organization block the CPU has called.
More detailed information on individual error OBs is also available in the STEP 7 Online Help under the following keywords:
"Diagnostics > Measures in the program for error handling"
"Calling reference data (LAD/FBD/STL, blocks ...) > Language description, block help, system attributes > Help on OBs"
"Error OBs"
"Settings for reporting system errors"
The following entry tells you which organization blocks do you need for error handling in the S7 program of the CPU: 11499205.
How do you find out further technical information about your module?
Description: In the following you will be shown how to access detailed technical data about the module you use. This is done using an S7-300 CPU315 as an example.
First of all, enter the name of the module you use (without its version designation, e.g.: CPU314, SM322, CP343, ET200S, ...) in the search line:
Fig. 01
While you are making your input, a product link window, which is shown in Fig. 2, appears to the left of the search line. The modules which match the keyword appear here. Now look for the module you use on the basis of the order number.
Fig. 02
Notes:
If the list in Fig. 2 does not include the module which you use, this indicates that this module has been phased out for a number of years. In this case, there will be no further technical information available.
Alternatively, you can also enter the start of an order number (e.g. 6es7315) instead of a module name.
Now left-click the module you use in the product link window. The corresponding product information then appears. It is shown in Fig. 3.
Fig. 03
You can find the following information, among others, in the Entries tab:
Downloads
FAQs
Certificates
Manuals and operating instructions
Applications
You can find further information about the module which you use in the Technical Data tab.
Why can't I see the values which are transmitted to an unlinked destination DB with SFC84, even though SFC84 is not indicating an error (RET_VAL = W#16#000?
Description:
Data blocks which are declared as unlinked are not monitored in
CPUs with MMC. Data in an unlinked DB isn't constantly updated in
the online view of the project, even though Monitor
(glasses) is enabled. This means that data transfer to the MMC by
means of SFC 84 (WRIT_DBL) cannot be monitored dynamically. One-off
updates occur if you close the relevant data block and then open it
again online. This data is represented by glasses crossed out in
the variables table.
Keywords: Sequence-relevant
Micro Memory Card
How does the CPU 31x/31xC/C7 react when an MMC fault occurs during the save procedure?
Description The service life of an MMC depends mainly on the number of delete and programming procedures.
The memory blocks of the MMC memory permit at least 100,000 write/delete operations. This refers to the operations with STEP 7 and data block backups upon power OFF and with SFC 84. In particular, therefore, SFC 84 should only be called at corresponding time intervals (e.g. hourly, daily ...).
If there is an MMC defect during saving, then the relevant application (e.g. load block, SFC) issues a negative acknowledgment or RET_VAL. This indicates that the routine has not been executed.
A resources or memory error is then recorded in the diagnostics buffer of the CPU.
The MMCs are also used with the C7 complete devices C7-613/635/636.
Note
More information on this topic is available in the device manual "CPU 31xC and CPU 31x, Technical Data", in the chapter entitled "Properties of the SIMATIC Micro Memory Card". The manual is available in Entry ID: 12996906 .
What is the effect of the STEP 7 function "Copy RAM to ROM"?
Description: This entry describes how the SIMATIC S7 function "Copy RAM to ROM..." works. We will be looking at how it works on data and code blocks in SIMATIC S7-300 CPUs and C7 devices (with reference to the controller part) taking into account various storage concepts. Since deleting the EPROM memory is also partially executed via the "Copy RAM to ROM..." function, this entry also includes an overview of how various storage media can be deleted. There is also a brief description of how to change a memory card (MC) using the "Copy RAM to ROM..." function.
A description of the various storage concepts is available in Entry ID 7302326 for S7-300 and in Entry ID 7302549 for S7-400.
On all CPUs you can only run the "Copy RAM to ROM..." function in the "STOP" operating mode. If the CPU is not yet in the "STOP" operating mode, you are ask whether the CPU should be switched to "STOP" via STEP 7.
The PDF file lists the S7-300 CPUs and C7 devices that support the "Copy RAM to ROM..." function.
SIMATIC S7-300 CPUs and SIMATIC C7 devices with built-in RAM and EPROM as load memory
In the case of CPU modules that have a built-in EPROM you can use the "Copy RAM to ROM..." function to copy the content of the internal RAM load memory to the built-in EPROM load memory so as not to lose data in the case of power failure without battery or overall reset. In the case of SIMATIC S7-300 CPUs or C7 devices with internal EPROM as load memory the code and data blocks are written from the RAM load memory to the EPROM load memory.
Warning: When you run the STEP 7 "Copy RAM to ROM..." function, the actual values of the runtime-relevant data blocks in the load memory are overwritten with the actual values from the main memory. If the runtime-relevant data blocks are then transferred again to the main memory (e.g. after overall reset), then the CPU takes the actual values from the load memory as initial values. These new initial values are displayed in SIMATIC STEP 7 in the "Actual value" column.
The following table describes the procedure in three figures.
No.
Procedure
1
In the case of data blocks the initial values and the actual values are transferred from STEP 7 to the CPU in the load memory (internal EPROM). However, the initial value is always then taken as the "First actual value" in the main memory if no actual value has been defined in STEP 7. If an actual value defined in STEP 7, it is transferred to the main memory.
Fig. 01
2
When you perform the "Copy RAM to ROM..." function, the actual values in the load memory are overwritten with the actual values from the main memory.
Fig. 02
3
If the load memory is transferred again to the main memory (e.g. after overall reset), then the actual values from the load memory are taken as the "First actual values" in the main memory.
Fig. 03
Delete EPROM The built-in EPROM is deleted by deleting the complete contents of the RAM and using the "Copy RAM to ROM..." function to copy the new RAM contents into the internal load memory EPROM. The procedure is described in the table below.
No.
Procedure
1
Connect the programming device (PG) with the CPU.
2
Open the SIMATIC Manager and go to "PLC/Display Accessible Nodes".
3
Open the view of the blocks "Accessible Nodes / MPI = .../Blocks" (click on "+").
4
Mark the blocks to be deleted (the system data too if you wish). If you want to delete the complete internal EPROM, mark all the blocks to be deleted and the system data.
You cannot delete system functions (SFC) and system function blocks (SFB).
5
Delete the marked blocks via "Edit/Delete" or via the "Del" key.
6
Perform "PLC / Copy RAM to ROM...".
This copies all the valid blocks from the RAM load memory to the internal EPROM memory. The blocks deleted in the internal RAM load memory are thus no longer written to the internal EPROM load memory and are thus also deleted in the EPROM.
SIMATIC S7-300 CPUs and SIMATIC C7 devices with built-in RAM and an external memory card (MC)
When you perform the "Copy RAM to ROM..." function, the runtime-relevant program and data blocks are copied from the internal RAM load memory to the memory card (MC).
Warning: When you run the STEP 7 "Copy RAM to ROM..." function, the actual values of the runtime-relevant data blocks in the load memory are overwritten with the actual values from the main memory. If the runtime-relevant data blocks are then transferred again to the main memory (e.g. after overall reset), then the CPU takes the actual values from the load memory as initial values. These new initial values are displayed in SIMATIC STEP 7 in the "Actual value" column.
The following table explains how to proceed in three figures. The procedure is identical for all 3 load memory types (internal EPROM, FLASH Memory Card, Micro Memory Card). The figures are repeated so that all the information on the load memory type is together.
No.
Procedure
1
In the case of data blocks the initial values and the actual values are transferred from STEP 7 to the CPU in the load memory (memory card). However, the initial value is always then taken as the "First actual value" in the main memory if no actual value has been defined in STEP 7. If an actual value defined in STEP 7, it is transferred to the main memory.
Fig. 01
2
When you perform the "Copy RAM to ROM..." function, the actual values in the load memory are overwritten with the actual values from the main memory.
Fig. 02
3
If the load memory is transferred again to the main memory (e.g. after overall reset), then the actual values from the load memory are taken as the "First actual values" in the main memory.
Fig. 03
Change the Memory Card (MC)
No.
Procedure
1
Set CPU in STOP mode.
2
Remove any slotted memory card.
3
Slot the "new" memory card.
4
Do an overall reset of the CPU.
5
If the memory card does not yet contain the matching user program, you must first load the user program into the CPU (internal RAM load memory) and then use "Copy RAM to ROM..." to transfer it to the memory card. Please note here that blocks already in the RAM load memory that are not overwritten by the new user program are also transferred to the memory card.
But here you can also use the "Load user program onto memory card" function directly.
Note: It is not permitted to remove and slot the memory card (MC) in the RUN operating mode.
When you remove/slot a memory card the CPU demands an overall reset and so the user program is lost in the RAM.
Delete individual blocks You cannot delete individual blocks from a memory card on the PG.
You can only delete individual blocks with a combination of the CPU and PG.
The requirement for this is that you slot the memory card in the CPU.
Then proceed as follows.
No.
Procedure
1
Connect the programming device (PG) with the CPU.
2
Open the SIMATIC Manager and go to "PLC/Display Accessible Nodes".
3
Open the view of the blocks "Accessible Nodes / MPI = .../Blocks" (click on "+").
4
Mark the blocks to be deleted (the system data too if you wish).
5
Delete the marked blocks via "Edit/Delete" or via the "Del" key.
6
Perform "PLC / Copy RAM to ROM...". This copies all the valid blocks to the memory card. The block deleted in the CPU is then no longer written to the memory card and is therefore deleted.
Completely delete the memory card (MC)
No.
Procedure
1
Slot the memory card into the programming device (PG).
2
In the SIMATIC Manager select "File/S7-MemoryCard/Delete".
3
Acknowledge with "yes" the security question asking whether you really want to delete.
If you are using a CPU with which you cannot write any memory cards or a PC with which you cannot write any memory cards, we recommend the prommer given below with its order number.
Order number
Description
6ES7792-0AA00-0XA0
SIMATIC PG, USB PROMMER 115/220V
SIMATIC S7-300 CPUs and SIMATIC C7 devices with micro memory card (MMC)
When you perform the "Copy RAM to ROM..." function, the runtime-relevant data blocks are copied from the main memory to the MMC. Here the actual values of the data blocks are overwritten on the MMC so that after an overall reset new initial values (the new actual values) are effective. These new initial values are displayed in SIMATIC STEP 7 in the "Actual value" column.
The following table explains how to proceed in three figures. The procedure is identical for all 3 load memory types (internal EPROM, FLASH Memory Card, Micro Memory Card). The figures are repeated so that all the information on the load memory type is together.
No.
Procedure
1
In the case of data blocks the initial values and the actual values are transferred from STEP 7 to the CPU in the load memory (MMC). However, the initial value is always then taken as the "First actual value" in the main memory if no actual value has been defined in STEP 7. If an actual value defined in STEP 7, it is transferred to the main memory. The actual values in the main memory are used when processing the program.
Fig. 01
2
When you perform the "Copy RAM to ROM..." function, the actual values in the load memory are overwritten with the actual values from the main memory.
Fig. 02
3
If the load memory is transferred again to the main memory (e.g. after overall reset), then the actual values from the load memory are taken as the "First actual values" in the main memory.
Fig. 03
In the case of CPU modules that work with a micro memory card (MMC) the load memory is on the MMC. When loaded, the program is stored on the MMC in such a way as to be immune to power failure and overall reset. The program is therefore always remanent in the load memory (on the MMC).
Delete individual blocks on a micro memory card (MMC)
With the PG
No.
Procedure
1
Slot the MMC into the programming device (PG).
2
In the SIMATIC Manager select "File/S7-MemoryCard/Open".
3
Mark the blocks to be deleted (the system data too if you wish).
4
Delete the marked blocks via "Edit/Delete" or via the "Del" key.
Via the CPU
The requirement for this is that you slot the micro memory card in the CPU.
No.
Procedure
1
Connect the programming device (PG) and your CPU.
2
Open the SIMATIC Manager and go to "PLC/Display Accessible Nodes".
3
Open the view of the blocks "Accessible Nodes / MPI = .../Blocks" (click on "+").
4
Mark the blocks to be deleted (the system data too if you wish).
5
Delete the marked blocks via "Edit/Delete" or via the "Del" key.
Completely delete the micro memory card (MMC)
No.
Procedure
1
Slot the MMC into the programming device (PG).
2
In the SIMATIC Manager select "File/S7-MemoryCard/Delete".
3
Acknowledge with "yes" the security question asking whether you really want to delete.
Note: In order to be able to read and write micro memory cards (MMC) on your PC too you need a prommer that can read and write the special format of the micro memory cards. A suitable prommer is available under order number 6ES7792-0AA00-0XA0.
You must never format the MMC in a standard slot or card reader with Windows, otherwise you will no longer be able to use the MMC for the SIMATIC-CPUs! (see Entry ID: 21830698)
SIMATIC S7-400 CPUs
The "Copy RAM to ROM..." function is not supported by S7-400 CPUs and the CPU S7-318 2DP. The options offered by the S7-400 are given in Entry ID 23670531.
Keywords:
Change
Why does the SFC 54 "RD_DPARM" not work with the new S7-300 CPU with MMC?
Description
In the new S7-300 CPUs with micro memory card, SFC 54 "RD_DPRARM" for reading out a data record of a chosen block of the system data configured with STEP 7 has been replaced by SFC 102 "RD_DPARA".
SFC 102 "RD_DPARA", in contrast to the old SFC 54 "RD_DPARM", is a system function that is executed asynchronously. This means that the processing is extended over various SFC calls.
Blocks containing SFC 54 "RD_DPARM" cannot be loaded to a new S7-300 CPU with MMC? Therefore, please replace the call of the SFC 54 "RD_DPARM" by the call of the SFC 102 "RD_DPARA" and change your programming logic to the asynchronous behavior of the SFC 102 "RD_DPARA".
Below is a comparison of the two system functions.
SFC 54 "RD_DPARM"
SFC 102 "RD_DPARA"
Comments
Inputs
---
REQ
Function will be executed only with REQ=1; new for SFC 102.
IOID
---
Parameter has been dropped for SFC 102; see LADDR.
LADDR
LADDR
SFC 54:
any block address, specification of the I or Q address range with IOID (B#16#54=IO input; B#16#55= IO output) SFC 102:
any block address, specification of the I or Q address range with bit 15 of LADDR (most significant bit). Bit 15=0 -> IO input; Bit 15=1 -> IO output.
RECNUM
RECNUM
Use identically.
Outputs
RET_VAL
RET_VAL
Use identically; however, there are additional error numbers available for SFC 102.
---
BUSY
BUSY=1; the job has not yet been finished, no results are available yet.
RECORD
RECORD
Use identically.
Table 1: Comparison of SFC 54 and SFC 102
How do you copy the user program from the load memory into the main memory without PG with a S7-300 CPU with MC slot?
Description When a memory card with user program is slotted into a CPU, the CPU copies the runtime-relevant program sections into the main memory.
Slot the memory card.
Do an overall reset.
CPU copies the runtime-relevant sections of the program from the load memory into the main memory. In particular this initializes the data blocks in the main memory (their initial values are reset).
A PG is not required for this procedure. This applies, for example, also when different user programs are stored on different memory cards and are to run at different times in the same CPU.
Notes
The memory card must remain slotted for as long as the CPU is in operation, especially in RUN.
The CPU transfers the program from the load memory into the main memory even after "Power off" without buffering (also even if the battery has undervoltage during "Power off").
Keywords Flash MC, MC
How can you backup your program from the load memory?
Instructions:
In the case of CPU modules that have a built-in EPROM, you can copy the contents of the load memory to the built-in EPROM so as not to lose data in the case of power failure without battery or overall reset.
Use the following procedure:
Set the CPU to operating mode STOP.
Use the menu command "View > Online" to open a window with an Online view of an opened project
or
call up the "Accessible Nodes" window by clicking on the "Accessible Nodes" button on the function toolbar or by selecting the menu command "PLC > Display accessible nodes".
Select the S7 or M7 program in the Online view of the project window or the node in the "Accessible nodes" window.
Select the menu command "PLC > Copy RAM to ROM".
The contents of the RAM memory are copied into the built-in EPROM.
Valid for:
CPU type
As from order no.
CPU 312 IFM
6ES7 312-5ACxx-0AB0
CPU 314 IFM
6ES7 314-5AExx-0AB0
C7-621
6ES7 621-1AD0x-0AE3
C7-621 ASI
6ES7 621-6BD0x-0AE3
C7-623/P
6ES7 623-1DE0x-0AE3
C7-624/P
6ES7 624-1DE0x-0AE3
C7-624
6ES7 624-1AE0x-0AE3
C7-626/P
6ES7 626-1DG0x-0AE3
C7-626/P DP
6ES7 626-2DG0x-0AE3
Table 1: CPU modules with built-in EPROM
In the case of CPU modules that have a memory card, you can copy the contents of the load memory to the memory card so as not to lose data in the case of power failure without battery or overall reset.
The procedure for copying the contents to the memory card is the same as the procedure for copying to a built-in EPROM.
Valid for:
CPU type
As from order no.
CPU 313
6ES7 313-1AD01-0AB0
CPU 314
6ES7 314-1AE02-0AB0
CPU 314 IFM
6ES7 314-5AE10-0AB0
CPU 315
6ES7 315-1AF01-0AB0
CPU 315-2DP
6ES7 315-2AF01-0AB0
CPU 316-2DP
6ES7 316-2AG00-0AB0
C7-633/P
6ES7 633-1DF0x-0AE3
C7-633 DP
6ES7 633-2BF0x-0AE3
C7-634/P
6ES7 634-1DF0x-0AE3
C7-634 DP
6ES7 634-2BF0x-0AE3
Table 2: CPU modules with memory card
In the case of CPU modules that work with a SIMATIC micro memory card (MMC), the load memory is on the MMC. It is precisely the same size as the MMC. When loaded, the program is stored on the MMC in such a way as to be immune to power failure and overall reset. The program is therefore always remanent in the load memory (on the MMC).
Description The table below gives you an overview of the communication services that are supported by the CPUs with integrated PROFINET interface and by the WinAC RTX (F) via Industrial Ethernet.
The following entries include the manuals for the above-mentioned CPUs, which provide more information on the Technical Data, Communication Services and Quantity Frameworks.
The following entries give you an overview of the communication services that are supported by the S7-300 and S7-400 Industrial Ethernet CPs: Entry IDs 16767769 and 15368142.
Keywords S7 communication, Open communication services, PROFINET IO, TCP, ISO-on-TCP, UDP, IO device, IO controller, PROFINET CBA
Implementation of SIMATIC modules of the product families S7-300, S7-400, ET 200M, ET 200S ET, 200iSP and TDC in environments with high concentrations of corrosive gas
are also approved for implementation in environments with high concentrations of corrosive gas in compliance with ISA–S71.04 severity level G1; G2; G3.
The relevant information is given in the manuals of the product families S7-300, S7-400, ET 200M, ET 200S, ET 200iSP and TDC.
Please refer to the relevant manuals for more information on climatic environmental conditions.
At which ambient temperature and at which air pressure can you operate a SIMATIC S7-300?
Description You can operate the S7-300 at the following ambient temperatures:
in a vertical position from 0°C to 40°C
in a horizontal position from 0°C to 60°C
Fig. 01
The aforementioned temperature values are based on an air pressure of 1080 hPa to 795 hPa, which corresponds to 2000 m above sea level. Under these conditions SIMATIC S7 controllers can be operated with natural convection.
At a lower air pressure (and thus lower air density), when operating at greater heights, the cooling performance of natural convection drops. If you use an S7-300 in an environment other than mentioned, please contact Technical Support for alternative configuration options at: http://www.siemens.com/automation/support-request
Note
More detailed information on setting up the S7-300 is available in the operating instructions "CPU 31xC and CPU 31x: Setting Up", in the "Configuration" chapter, in Entry ID: 13008499 .
What can you do when the power requirement of the modules in the subrack exceeds the power supply provided by the CPU on the backplane bus?
Description: If the overall power requirement of the S7-300 modules in subrack 0 exceeds the power supply provided by the CPU on the backplane bus, then you must implement interface modules.
The S7-300 CPUs provide 1.2 A for the backplane bus. If this is not sufficient, then you must implement interface modules IM 360 /IM 361. If you implement IM 360 (requires 350 mA itself), then there is only 800 ma left for the 8 possible I/O modules in subrack 0.
Interface modules IM 361 each provide 800 ma for the backplane bus in subracks 1 to 3.
Notes:
CPUs 312 and 312 C, with which you can only have a single-line setup, provide 800 ma
IM 365 cannot be used to cover increased power requirements in another subrack, because it can only distribute the power supply provided by the CPU in subrack 0 to subrack 1. IM 365 can distribute max. 800 ma of the power provided by the CPU in subrack 0 to subrack 1. IM 365 itself requires 100 ma from the backplane bus.
You can find more information on this in the manuals:
"Programmable Logic Controllers S7-300 Module Data" in Entry ID: 8859629
"S7-300, CPU 31xC and CPU 31x: Installation Operating Instructions" in Entry ID 13008499.
Where do you find certificates and approvals for SIMATIC S7 in the Internet?
Description: The SIMATIC S7 automation system complies with various different regulations and standards. You can read and if necessary, download the currently available certificates and approvals on the Service & Support pages in the Internet at:
In Product Support, you select the desired product group, e.g. S7-300/S7-300F.
There, you select the Entry list tab and in the Entry type drop-down list you select Certificates.
Using the filters you can narrow down the selection to specific certificates, e.g. UL.
Bild 01
Note: If you select a single product (Product View), you select the Entries tab; otherwise the procedure is identical.
Keywords:
Test certificate
Where can you find images, graphics, symbols and screenshots for SIMATIC industrial automation systems?
Configuration notes: Clock synchronicity is used to establish a direct connection between the equidistant DP cycle, the I/O modules and the user program.
The following SIMATIC components support clock-synchronicity functionality:
S7-300 CPUs
CPU 315 and CPU317 as DP masters from FW 2.5
CPU 319 as DP masters from FW2.4
S7-400 standard and S7-400F CPUs as DP masters from FW 3.1
ET 200M with selected modules
ET 200S with selected modules
Repeaters and diagnostics repeaters
Please note that only the internal DP interfaces on the CPUs can be used for clock-synchronicity communication.
STEP 7 V5.2 or higher is required for configuration purposes.
The drives which support the clock-synchronicity functionality are the entire product group comprising "SIMODRIVE 611U", "SINAMICS" and "MASTERDRIVE MC".
The following are required in order to configure the drives: Drive ES Basic V5.2 or higher, STEP 7 V5.2 or higher and one of the CPUs mentioned above.
You can find a list with the precise designations of the SIMATIC modules, which support clock-synchronicity functionality, in the manual SIMATIC Clock Synchronicity in subsection 2.2.1 of Entry ID 15218045
Keywords: Constant bus cycle time, Compatibility list
