找回密码
 注册

QQ登录

只需一步,快速开始

搜索

[PLC编程] SIMATIC CFC V8.1

[复制链接]
山海致远 发表于 2019-3-7 23:04:32 | 显示全部楼层 |阅读模式
SIMATIC CFC介绍和安装文件下载网址
https://doc.eleok.com/843.html
此版本较老,较新版本请参考以上网址
SIMATIC Process Control System PCS 7  CFC Readme V8.1
Readme
1        Notes on Installation and Usage
2        Notes on Installation
2.1        Scope of Delivery
2.2        Hardware Requirements
2.3        Software Requirements
2.4        Installation
3        Notes on Usage
4        New features and changes as compared to previous versions
5        Information on Configuration and Operation
5.1        Migrating to Other CFC Versions
5.2        General Information on CFC
5.3        CFC for S7
5.4        SFC instances in the CFC
5.5        Inheritance of the name of the control module type by its blocks
6        Notes on the Documentation



1        Notes on Installation and Usage
CFC V8.1 - programming software for SIMATIC S7
This information has priority over statements made in other documentation.
Please read these notes carefully, as they contain important information about the installation and use of CFC.

Security information:
Siemens provides automation and drive products with industrial security functions that support the secure operation of plants or machines. They are an important component in a holistic industrial security concept. With this in mind, our products undergo continuous development. We therefore recommend that you keep yourself informed with respect to our product updates. Please find further information and newsletters on this subject at: http://support.automation.siemens.com
To ensure the secure operation of a plant or machine it is also necessary to take suitable preventive action (e.g. cell protection concept) and to integrate the automation and drive components into a state-of-the-art holistic industrial security concept for the entire plant or machine. Products used from other manufacturers should also be taken into account here. Please find further information at: http://www.siemens.com/industrialsecurity
2        Notes on Installation
The installation notes include important information that you need for installing the SIMATIC Version Trail software. Please read these notes prior to installation.
This version runs on the following operating systems:
The installation notes include important information that you need to install the CFC software. Please read these notes prior to installation.
CFC runs on the following operating systems:
●        MS Windows XP Professional SP3
●        MS Windows Server 2003 SP2 Standard
●        MS Windows Server 2003 R2 SP2
●        MS Windows 7 Ultimate SP1 32 Bit
●        MS Windows 7 Ultimate SP1 64 Bit
●        MS Windows Server 2008 SP2 32 Bit
●        MS Windows Server 2008 R2 SP1 64 Bit
●        MS Windows 7 Professional SP1 32 Bit
●        MS Windows 7 Professional SP1 64 Bit
●        MS Windows Vista 32 Bit SP2 Ultimate
●        MS Windows Vista 32 Bit SP2 Business

Note
Non-supported operating systems
The MS Windows XP Home and MS Windows 2000 operating systems are not supported.


2.1        Scope of Delivery
You have received one of the following products with this delivery:
SIMATIC CFC V8.1
Order number: 6ES7658-1EX08-2YA5
The contents of this package include the following:
●        1 TIA Engineering Toolset V8.1 CD
●        1 license key memory stick
●        1 Certificate of License
Contents of the TIA Engineering Toolset CD for CFC
●        CFC V8.1
●        Electronic manual "CFC - Getting Started" (for the sample project ZEn04_01_CFC)
●        Electronic manual "CFC - Manual for S7"
2.2        Hardware Requirements
To be able to work with CFC, you require a programming device or a PC which meets the following requirements:
●        Processor with at least 600 MHz
●        At least 512 MB RAM main memory
2.3        Software Requirements
Runtime environment
CFC is a 32-bit application that requires one of the operating systems listed above.
CFC is add-on software. In order to operate CFC, you also need the following software on your programming device or PC:
●        Basic software STEP 7 V5.4 SP5 or later

Note
The SCL Compiler product is no longer needed as of CFC V6.1 including SP1.
The setup for CFC installs the required SCL Compiler functionality in the appropriate version (no SCL license key is required for this).
If a version of SCL Compiler earlier than V5.3 including SP1 was installed on the PC and SCL has been removed, CFC must be reinstalled. Otherwise, you cannot compile in CFC, because the SCL function cannot be found.
If you have installed an SCL Compiler with version V5.1.x on the PC, you must install the SCL Compiler again after removing CFC, because otherwise the SCL sources will no longer be displayed in the SIMATIC Manager.

To read the provided PDF files, you need a PDF reader that is compatible with PDF 1.x.
Space requirements
CFC V8.1 requires approximately 90 MB of space on your hard disk.
2.4        Installation
Installation of CFC
You can install CFC V8.1 over an existing installation of CFC.
CFC can be installed only after the complete installation by STEP 7. The setup program automatically installs CFC on the drive containing the STEP 7 software.
Insert the CFC CD into the drive. CFC is installed with a user-guided setup that you launch with the MS Windows Explorer by double-clicking on the SETUP program on the CFC CD.
CFC license key
Before you can work with CFC, you need to transfer the license key (usage right) from the license key memory stick to the computer.
If the license key cannot be installed during setup, continue setup without installing the license key. Afterwards, restart the
computer and install the license key using the Start menu command "Simatic > License Management > Automation License Manager".
The notes from the STEP 7 readme also apply to the license key.
Uninstalling CFC

Note
Note on uninstalling
You have to remove software products in accordance with the MS Windows guidelines.
In Windows XP, for example, you remove your software package (e.g. "SIMATIC CFC V8.1") using the MS Windows application "Add or remove programs" (in the MS Windows task bar via the start menu command Settings > Control Panel > Add or Remove Programs). This is the only way to uninstall the software under MS Windows.

Dynamically created files could remain when you uninstall CFC. This is detected by the uninstall tool, and the message "Some elements could not be removed. You should manually remove items related to the application." is displayed. You can, but do not have to, delete these dynamically created files.
3        Notes on Usage
These notes take precedence over statements made in the manuals and online help.
4        New features and changes as compared to previous versions
What's new in CFC?
Version V8.1 includes the following enhancements or changes compared with the previous version V8.0.4:
●        "Selective download" function
The new "Selective download" function can be used to download individual or multiple modified CFCs or SFCs to a target system. You can use selective downloading as a user to specifically select which configured changes should be transferred to the target system, enabled and tested.
You can find additional information in the section "Selective download of individual charts" of the "CFC for SIMATIC S7" manual or online help.
●        Type update in RUN mode
CPU 410-5H PA supports type update in RUN mode. This makes it possible to update the instances and download them to the target system in RUN mode after changing an interface at the block types. This is only possible in STOP mode in other automation systems.
You can find additional information in the section "Type update of a CPU 410-5H PA" of the "CFC for SIMATIC S7" manual or online help.
●        Block icons for process pictures in APL-based style
The templates for the block icons can be available in different variants. Variants "1" and "2" are already present as standard.
・        Variant "1" contains icons in the PCS 7 standard.
・        Variant "2" contains icons in an APL-based style.
You can find additional information on this:
・        In the "Operator control and monitoring" section in the "CFC for SIMATIC S7" manual or online help.
・        In the "Configuring SFC block icons" section of the "SFC Visualization" manual or online help.
5        Information on Configuration and Operation
5.1        Migrating to Other CFC Versions
Migrating to Other CFC Versions
Data created with older versions of CFC can be further processed with CFC V8.1 as follows:
●        CFC V3.x to CFC V8.1 data can be read and displayed with CFC V8.1.
●        Processing the data results in the conversion of this data at first write access (following a system prompt) for each chart folder in order to ensure compatibility.
You can still continue working with the data created with CFC V1.0 or CFC V1.1 as follows in CFC V8.1:
●        CFC V1.x data can be read and displayed with CFC V8.1. Direct editing of CFC V1.x data is not possible here. If you want to continue working with V1.x data, follow these steps:
●        In the SIMATIC Manager, open the project and save it under another name with "File > Save As..." and the "With reorganization (slow)" option in the following dialog box with "Project" file type. This results in an automatic conversion to the V8 file format.
General notes on compatibility:
●        You cannot "reconvert" V8 data to older versions.
●        Data that was created with newer CFC versions cannot be processed with older CFC versions.
●        After upgrading from an older CFC version, various function blocks are replaced by newer versions in the program. The old blocks remain in the block folder and can be removed using the command Options > Block Types > Clean Up.
5.2        General Information on CFC
Maintaining the capability for type updating in RUN
Supplement to the topic "Type update with a CPU 410-5H PA" in the "CFC for SIMATIC S7" documentation:
Type updating in RUN is no longer possible if one of the following changes has been made at a block:
●        The name of an input with configured message was changed ("Message Event ID").
●        The default value of an I/O has been changed.
After these changes, loading can only take place in STOP mode.

Handling of upper/lower case text for CFC objects
Upper and lower cases are still permitted in symbols as of STEP 7 V4.02. However, the case is no longer considered when processing the symbols (according to IEC 1131-3).
This means that the name and not the notation of a symbol is important.
Example: The "Motor" and "MOTOR" symbols refer to the same variable.
CFC V8.1 is still case-sensitive when dealing with blocks within the charts, i.e. a block can be created with a name that differs from another name only in its case. However, we recommend that you refrain from using this option in order to make it easier to change at a later date. To cooperate with WinCC, you should keep names case-sensitive; otherwise, WinCC will not be able to distinguish between the blocks with the same names.

"Key already exists" message during conversion of older projects to CFC version V8.1.
If this message appears, your project contains block types with names that differ only in their case. You must correct this in the previous version. You can perform the conversion only after you have done this.

Differences in CPU protection
●        In CFC test mode, write access is also allowed with the key in RUN position.
●        When password protection is enabled, those who do not know the password cannot access the CPU, regardless of the protection level.

Notes on AS-wide interconnections
●        Changes were made to the code of the IK_SEND system block in version 7.1.1. If you upgrade your project directly from version V7.1: You can accept this newer version of IK_SEND in your program by doing the following:
・        Open the CFC library in the SIMATIC Manager and select "IK" in the S7 program in the block folder of FC155 (IK_SEND).
・        Run the "Options > Charts > Update Block Types" function, selecting all projects using AS-wide interconnections in the following dialog.

Note on textual interconnections in F-programs
When the "Make textual interconnections" function is executed, any open textual interconnections to F-blocks are closed without querying the F-password.

Note on use of UDTs
Since PCS 7 V7.0, UDTs are used in the interface in various blocks of the block libraries. Therefore, UDT1 to UDT50 can no longer be used in the user area of the program or the templates in the master data library.

Notes on control modules/control module types
If a project or a library is removed from the multiproject, the associated control modules and control module types cannot be processed further.
When a control module is created by copying a control module type, it is possible that the sampling time of the control module will be changed. This always happens when the default assignment of cyclic interrupt and sampling time has been changed in the library and/or the target project (e.g. when organization block OB36 instead of OB35 has the sampling time of 100 ms). In this version, the assignment to the organization block is set instead of the sampling time during copying. If this happens, check whether the copied control module has the desired sampling time and correct it if necessary.
The sampling time of a control module type that was generated from a process tag type is always 100 ms in this version, regardless of the cyclic interrupt in which the blocks of the process tag type are installed. Please check whether the generated control module type has the desired sampling time and correct it if necessary.
Control module types that do not contain blocks cannot be used as templates in projects.
When configuring control modules and control module types, avoid using nested control tags if you want to exchange data with COMOS and Advanced ES. Nested control tags are not supported in COMOS and Advanced ES and can lead to problems in these products.

System behavior when synchronizing type and instances of control modules
Blocks, interconnections and messages can be added or removed from existing and already instantiated control modules. These changes can be passed on to the existing, corresponding instances of the control modules by executing a synchronization.
The behavior during synchronization depends on:
●        The type of change (parameter value, interconnection)
●        The location of the change (type or instance)
●        The attributes of the modified parameters
You can find detailed information on system behavior during synchronization between type and instance of control modules at http://support.automation.siemens.com under the entry ID 99861834.

Note on the use of memory cards when loading an S7 program
Note that after loading an S7 program to a memory card (via SIMATIC Manager, "CPU > Save to Memory Card ..." menu), the blocks cannot be monitored in the test mode of the CFC. When the connections log on, an error message appears stating that the connection cannot be monitored. To remedy this, download the program via the CFC to an S7-PLCSIM or to a test CPU in addition. You can then use test mode as usual.
5.3        CFC for S7
Creating Block Types
If blocks are created for later use as FCs in CFCs (for example, with STL/SCL), you can only write to block outputs (VAR_OUTPUT) in these FCs. If block outputs are read, this will lead to working with undefined values.
If old values should be retained beyond the cycle, the in/out parameter (VAR_INOUT) must be used or written to the block as an FB.
Block library "CFC Library" is overwritten by the new version
The existing "CFC Library" block library is overwritten by the new version during installation. If you want to retain the old library, it must be copied prior to the installation.
5.4        SFC instances in the CFC
For subsequent interconnection of freely programmable associated message values to the SFC instance (AUX_PR_04 to 10), a Stop/Run transition of the CPU must be executed after a delta compile and delta download for the change to take effect, and the associated message values to be displayed in WinCC. Alternatively, a complete download can be performed.
5.5        Inheritance of the name of the control module type by its blocks
When creating an instance for control module types, the name of the control module type can be inherited by the name of the blocks in the instance.
For optional blocks in the control module type, however, it is not possible to inherit the type name.
6        Notes on the Documentation
The entire documentation on CFC is available to you via the online help. This documentation contains both "basic knowledge" on cross-function contents as well as information on the direct operating and functional context.
CFC is described in the "CFC - Manual for S7" manual.
The manuals are available as electronic documents which you can read and print with Acrobat Reader (in Windows Start menu, submenu "Siemens Automation > SIMATIC > Documentation").
您需要登录后才可以回帖 登录 | 注册

本版积分规则

QQ|手机版|小黑屋|ELEOK |网站地图

GMT+8, 2024-11-19 02:44

Powered by Discuz! X3.5

© 2001-2024 Discuz! Team.

快速回复 返回顶部 返回列表