SIMATIC CFC介绍和安装文件下载网址
https://doc.eleok.com/843.html
此版本软件老旧，较新版本请参考以上网址
SIMATIC Update 4 for CFC V8.0 incl. Service Pack 4
Programming Software for SIMATIC S7 / M7
Notes on Installation and Usage
These notes should be considered more up-to-date than the information in other documents.
Please read the notes carefully; they contain important information on installing and using CFC.
You can find important information on Update 4 for CFC V8.0 SP4 in the section Notes on Usage / Chapter: 4 Notes on the Update
Contents
1 Contents of the Consignment
2 Hardware Requirements
3 Software Requirements
3.1 Operating Environment
3.2 Memory Requirements
4 Installation
4.1 Installing CFC
4.2 CFC License Key
4.3 Uninstalling CFC
4.4 Installing the Borland C Compiler (for M7)
Notes on Usage (Release Notes)
1 New Features and Modifications in the New Version
1.1 What’s New?
2 Notes on Configuring and Operating the Software
2.1 Data from Different Versions of CFC
2.2 General Information
2.3 CFC for S7
2.4 SFC Instances in the CFC
2.5 Inheritance of the Name of a Control Module Type by its Blocks
2.6 I/O Names in Step and Transition Programs after Import to PCS 7
2.7 Signal Processing During Data Exchange with COMOS IE
3 Notes on Documentation
4 Notes on the Update
Notes on Installation
The installation notes contain important information that you will require to install CFC. Read these notes before installing the software.
The CFC can be run 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: MS Windows XP Home and MS Windows 2000 operating systems are not supported.
1 Contents of the Consignment
You received one of the following products with this consignment:
SIMATIC CFC V8.0 SP4
Order number: 6ES7658-1EX08-2YA5
This product package includes:
• 1 CD TIA Engineering Toolset V8.0 SP4
• 1 license key memory stick
• 1 certificate of license
Contents of the TIA Engineering Toolset CD regarding CFC
• CFC V8.0 SP4
• Electronic manual "CFC - Getting Started" (for the sample project ZEn04_01_CFC)
• Electronic manual: "CFC - Manual for S7"
• Electronic manual: "CFC - Manual for M7"
2 Hardware Requirements
To work with the CFC, you require a programming device or PC with the following requirements:
• Minimum 600 MHz processor
• Minimum 512 MB RAM main memory
3 Software Requirements
3.1 Operating Environment
CFC is a 32-bit application which requires one of the operating systems listed above.
CFC is an optional software package. To be able to work with CFC, you require the following additional software packages on your programming device or PC:
• Basic software STEP 7 V5.4 SP5 or higher
----------------------------------------------------------------------------------------------------------------
Note:
The product SCL Compiler is no longer necessary as of CFC V6.1 incl. SP1.
The CFC setup itself installs the required SCL compiler functionality with the suitable version (it does not need an SCL license key).
If an SCL compiler previous to than V5.3 SP1 was installed on the computer and the
SCL is being uninstalled, the CFC has to be reinstalled. Otherwise you cannot
compile in the CFC because the SCL function cannot be found.
If you installed an SCL compiler with version V5.1.x on the PC, the SCL compiler
must be reinstalled after you have removed the CFC. Otherwise the SCL sources
will no longer be displayed in the SIMATIC Manager.
----------------------------------------------------------------------------------------------------------------
You need a PDF Reader compatible with PDF 1.x to read the supplied PDF files.
3.2 Memory Requirements
CFC V8.0.4 requires approximately 90 MB of space on your hard disk.
4 Installation
4.1 Installing CFC
When you install CFC V8.0.4, you can overwrite an existing installation of CFC.
CFC can only be installed after STEP 7 has been completely installed.
The Setup program automatically installs CFC on the drive containing the STEP 7 software.
Insert the CFC CD in the drive. To install CFC, double-click the SETUP program on the CFC CD from the Windows Explorer. The Setup program will guide you through the installation.
4.2 CFC License Key
Before you can start working with CFC, you must transfer the license key from the license key memory stick to the computer.
If the license key cannot be installed during setup, continue the Setup program without installing the license key. Perform a restart and install the license key via the Start menu entry Simatic > License Management > Automation License Manager.
The STEP 7 readme notices also apply to the license key.
4.3 Uninstalling CFC
----------------------------------------------------------------------------------------------------------------
Important Note:
Software products must be removed according to Microsoft Windows conventions.
Use the Microsoft Windows application "Add/Remove Programs" (for example, in Windows XP in the taskbar via the Start menu entry Settings > Control Panel > Add/Remove Programs) to remove your software package (for example, "SIMATIC CFC V8.0 SP3"). This is the only way to uninstall software in Microsoft Windows.
----------------------------------------------------------------------------------------------------------------
This applies to some files created dynamically by CFC. This is recognized by the uninstall tool and reported with the message "Some elements could not be removed. You should manually remove items related to the application." You can then decide whether or not you want to delete these files.
4.4 Installing the Borland C Compiler (for M7)
To allow correct M7 block import and problem-free operation of the M7 code generator, the Borland C compiler must be installed either completely or user-defined with the following minimum configuration:
• Select "user-defined" in the "Borland C++ Installation" window. The options offered do not need to be selected.
• "32-bit Windows" must be selected in the "Borland C++ Target Platforms" window.
• "Command Line Tools" must be selected in the "Borland C++ Tools" window.
• Subgroups "Visual Tools", "Borland Database Engine", "Examples" and "Help" can be deselected completely.
• "Runtime libraries" must be selected in the "Libraries" subgroup. At least the header files, static libraries and dynamic libraries are required.
----------------------------------------------------------------------------------------------------------------
Note:
Since 10/01/2003, the SIMATIC M7 automation computer and all the associated components have been discontinued. Although the M7 is still available as a PLC in the engineering system, it has been removed from the documentation and support is no longer provided. You can find additional information under http://support.automation.siemens.com/WW/view/en/14044569.
----------------------------------------------------------------------------------------------------------------
Notes on Usage (Release Notes)
These notes should be considered more up-to-date than the information in manuals and online helps.
1
Security information:
2
Siemens offers IT security mechanisms for its automation and drive product portfolio in order to support the safe operation of the plant/machine. Our products are also continuously developed further with regard to IT security. We therefore recommend that you keep yourself informed about updates and upgrades for our products and always use the latest version of each product. You can find information on this at: http://support.automation.siemens.com. You can register for a product-specific newsletter here.
For the safe operation of a plant/machine, however, it is also necessary to integrate the automation components into an overall IT security concept for the entire plant/machine, which corresponds to the state-of-the-art IT technology. You can find information on this at:
http://www.siemens.com/industrialsecurity. Products used from other manufacturers should also be taken into account here.
1 New Features and Modifications in the New Version
1.1 What’s New?
Version V8.0.4 contains the following expansions or changes as compared to the previous version V8.0.3:
• Technological editor
The technological editor now supports equipment modules and equipment module types with lower-level control modules.
• Data exchange with COMOS Integrated Engineering
Equipment modules and equipment module types are supported in data exchange.
• Commands and statuses
• At a control module type (not at an instance) or at a "Control module (basic requirement)". These commands and statuses are specific to these objects.
• Globally, i.e. created in the master data library with SIMATIC Manager. These global commands and statuses always relate to equipment phases and can be used in all equipment phases of a plant.
2 Notes on Configuring and Operating the Software
2.1 Data from Different Versions of CFC
Data created with older CFC versions can still be used as follows in CFC V8.0.4:
• The CFC V3.x to CFC V8.0 data can be read and displayed with CFC V8.0.4.
• If you edit this data, the contents of each chart folder are converted following the first write access (you will be asked to confirm conversion). This ensures compatibility.
Data created with CFC V1.0 or CFC V1.1 can still be used as follows in CFC V8.0.4:
• The CFC V1.x data can be read and displayed with CFC V8.0.4. Direct editing of CFC V1.x data is not possible here. If you want to edit V1.x data, proceed as follows:
• Open the project in the SIMATIC Manager and save it under a different name using the menu command File > Save As... and the option "Rearrange before saving (slow)" and select the file type "Project" in the dialog box which appears. The data is then automatically converted to V8 format.
General notes on compatibility:
• You cannot "reconvert" V8 data back to previous versions.
• Data created with newer CFC versions cannot be edited with previous CFC versions.
• After upgrading from older CFC versions, a series of function blocks are replaced in the program by new versions. The old blocks remain in the block container but can be removed with the menu command Options > Block Types > Clean Up.
2.2 General Information
Upper and Lower Case for CFC Objects
From STEP 7 V4.02 onwards, you can still use both upper and lower case when entering symbolic names. However, when the symbols are processed, this is no longer taken into account (in compliance with IEC 1131-3).
In other words, it is the name itself, and not the way it is written, which is important.
Example: The symbols "Motor" and "MOTOR" refer to the same variable.
CFC V8.0.4 still takes upper and lower case symbols into account for blocks in charts; in other words, you can create blocks with the same name which differ only in the case used. However, we recommend that you use different names to avoid problems in the future.
When using CFC in conjunction with WinCC you cannot use this option, because WinCC cannot distinguish between blocks with the same name.
The existing "CFC Library" block library is overwritten by the new version (which contains the corrected block R_TRIG) during the installation. If you want to retain the old library, it has to be copied before the installation.
Message "Key already exists" when migrating older projects to CFC version V8.0.4
This message appears when you have block types in your project that differ only in capitalization. You have to correct the previous version before migration is possible.
Differences in CPU protection
• In the CFC test mode, write access is also permitted with the key switch set to RUN.
• If password protection is activated, it is not possible to access the CPU without knowing the password regardless of the protection level.
Note of AS-wide interconnections
With version 7.1.1 we have made changes in the code of the IK_SEND system block. If you upgrade your project directly from version V7.1: You can accept this later version of the IK_SEND in your program by proceeding as follows:
o Open the CFC library in SIMATIC Manager and select the FC155 (IK_SEND) in the "IK" block folder of the S7 program.
o Execute the function "Options > Charts > Update block types", while you select all projects that use AS-wide interconnections in the following dialog.
Note of textual interconnections in F programs
When the "Make textual interconnections" function is used, open textual interconnections to F blocks may be made without prompting for the F password.
Note on using UDTs
As of PCS 7 V7.0, UDTs are used in the interface in different blocks of the block libraries. This means you can no longer use UDT1 to UDT50 in the user area of the program and in the templates of the master library.
Notes on control modules/control module types
If a project or a library is removed from the multiproject, the associated control modules or control module types cannot be edited further.
When a control module is created by copying a control module type, it may occur that the sampling time of the control module is changed. This happens when the default assignment of cyclic interrupt and sampling time has been changed in the library and/or in the target project (for example, when the organization block OB 35, instead of OB 36, has the sampling time 100 ms). In this version, the sampling time is not checked during copying, but rather the assignment to the organization block is maintained. In such cases, please check whether the copied control module has the right sampling time and correct it if necessary.
In this version, 100 ms is always given as the sampling time of a control unit type that has been created from a process tag type, regardless of the cyclic interrupt in which the blocks of the process tag type are installed. Please check whether the created control module type has the required sampling time and correct this if necessary.
Control module types containing no blocks cannot be used as copy templates in projects.
During configuration of control modules and control module types, avoid the use of nested control tags if you wish to exchange the data with COMOS and Advanced ES. Nested control tags are not supported in COMOS and Advanced ES and may lead to problems with these products.
Note on the use of memory cards when loading an S7 program
After loading an S7 program to a memory card (via SIMATIC Manager, menu “CPU > Save to memory card…), please note that the blocks cannot be monitored in test mode of the CFC. When the I/Os are registered, an error message appears informing you that the I/O cannot be monitored. To remedy this, load the program additionally via the CFC to a PLCSim or a test CPU. You will then be able to use test mode as normal.
2.3 CFC for S7
Creating CFC Block Types:
If you create blocks as FCs for subsequent use in CFC charts (for example, with STL/SCL), block outputs in these FCs must only be written (VAR_OUTPUT). If you read block outputs, you will be working with undefined values.
If you want old values to be retained beyond the cycle, you must use in/out parameters (VAR_INOUT) or write the block as an FB.
"CFC Library" block library is overwritten by the new version
The existing "CFC Library" block library is overwritten by the new version during the installation. If you want to retain the old library, it has to be copied before the installation.
2.4 SFC Instances in the CFC
After subsequent interconnection of the programmable associated values at the SFC instance (AUX_PR_04 ...10), a STOP-RUN transition of the CPU must be performed after a compilation of the changes and download of changes for the changes to take effect and for the associated values to be displayed again in WinCC. You can also perform a complete download.
2.5 Inheritance of the Name of a Control Module Type by its Blocks
For control module types, when an instance is created, the name of the control module type can be inherited by the names of the blocks in the instance. In the case of optional blocks, however, this inheritance of the type name is not possible.
2.6 I/O Names in Step and Transition Programs after Import to PCS 7
During data transfer of an equipment module type from COMOS IE to PCS 7, step and transition programs are automatically generated depending on the predefined commands and status queries of the control module types used.
It may occur that the generated I/O names in the step and transition programs are too long and therefore cannot be interpreted by the compiler.
In these cases, the I/O names of the relevant block contacts must be truncated in the corresponding SFC type.
2.7 Signal Processing During Data Exchange with COMOS IE
The signal processing concept has been expanded. In conjunction with COMOS IE, the control tags with the tag type "Signal" which represent a channel request should preferably be assigned to the corresponding block I/O of the technological processing block in the CFC technological editor, and not to the channel driver block.
This concept is only supported when the PCS 7 APL V8.0 library is used.
3 Notes on Documentation
Comprehensive documentation on CFC is available to you in the online help. This contains both general reference information and context-sensitive help on the current function or dialog.
CFC is also described in the manuals "CFC - Manual for S7", "CFC - Manual for M7".
You can find the manuals as electronic documents which you can read and print with Acrobat Reader (via the Start menu of Windows in the sub-menus SIMATIC and Documentation).
4 Notes on the Update
Update 4 contains the following expansions or corrections:
3 Optimized parameter transfer during download of changes.
4 When using indirect data transfer via XML between COMOS and SIMATIC PCS 7, please ensure that the transfer medium or transfer directory of the XML files is only accessible to authorized persons.
5 The interconnections remain set to external enable inputs from runtime groups when a CFC is overwritten.
This can be deactivated or activated in the SIMATIC Manager under the menu item Options > Charts > Settings for Copying/Moving…"
6 In connection with the overwriting of CFCs and multiple use of globally structured tags, it could happen that these variables can no longer be used. Overwriting CFCs no longer limits the use of these global tags.
7 The display of the "Charts" folder when the project is accessed via the network has been optimized.
8 Under certain circumstances, it was not possible to reset the "Enumeration" attribute at a setpoint to the value of the characteristic at the SFC type. The "Enumeration" attribute of a setpoint at the instance of an SFC type can now be converted again to the behavior of the type by entering "< like type >".
9 Programs that include system functions (SFC) 131 to 135 can now also be downloaded to CPU 300 PN, S7 410 and S7-mEC.
10 When saving or restoring a project with the “Save As With Reorganization” function, texts of SFC step acknowledgment information in connection with SIMATIC TDC, text of listings and equipment property types as well as equipment properties themselves could be lost. This is no longer the case.
11 Copying a sub CM from one control module type (CMT) to another resulted in an incorrect type reference in the copy. This is no longer the case.
12 When using an optional sub CM of a control module type (CMT), it could happen that the sampling time of the sub CM was not adapted to the sampling time of the instance. This is no longer the case.
13 You can now assign an equipment property in the PH to an equipment property type again.
14 Cross-chart interconnections at inputs that were broken by copying charts will only turn into textual references.
15 When using optional sub CM of a control module type (CMT) at the instance (CM), there could be interconnections in the instance that were not plausible in case of external interconnections from within the CMT. This is no longer the case.
Note: External interconnections from within a CMT are now ignored.
16 When saving or restoring a project with the “Save As With Reorganization” function, interconnections to other AS could be lost. This is no longer the case.
17 The correct assignment of control tags from lower-level CMs is now guaranteed.
18 The setting option “optional” can no longer be reached at Root CMs.
19 When a control module type is created by dragging a block to the technological editor, the name of the block is now automatically applied.
20 When block types are upgraded, texts configured at the instances are now retained.
21 Cross-AS interconnections can now also be configured if the CPUs of a H-system are connected to other CPUs via separate subnets
22 Previously, copying sub-control module types in the technological editor sometimes resulted in inconsistent project data. This is no longer the case.
23 Previously, creating a control module type from a process tag type failed under certain circumstances. This is no longer the case.
24 In the technological editor in CFC, signal names with a maximum length of up to 24 characters can now be used.
25 Opening of CFCs has been optimized.
26 The validity check of the global declarations has been improved.
27 After chart I/Os are deleted, the names that are no longer in use can be re-used again immediately.
28 Previously, under certain circumstances, it was not possible to rename blocks of a control module type in the technological editor. This is no longer the case.
29 Interconnections within a selected set of control modules are retained when this set is copied.
30 During loading of an S7-mEC, an existing license is now correctly detected.
31 Control module types with more than one block can now also be inserted in the technological editor of the type of a technological function using drag-and-drop.
32 Previously, when the function "Synchronize symbol table" was executed, system errors occurred under certain circumstances. This is no longer the case.
33 Output interconnections to runtime groups are now retained during copying.
34 Downloading changes is now possible for programs whose interfaces contain global DBs with interconnections to CFC blocks.
35 D7-SYS target system:
During cross-AS copying of a block with interconnections, the interconnections on the input side become textual references.
36 Previously, during an XML import of setpoints, the editor was closed under certain circumstances. This is no longer the case.
37 The synchronization of control module types has been improved.
38 When control module types are synchronized, instance-specific entries relating to TEXT0/TEXT1 are now retained.
39 The impermissible use of FB number 16 for a user-created block is now reported correctly during compilation.
40 During an XML transfer to COMOS, project data are now shown correctly in accordance with the set filters.
【必读】版权免责声明
1、本主题所有言论和内容纯属会员个人意见，与本论坛立场无关。2、本站对所发内容真实性、客观性、可用性不做任何保证也不负任何责任，网友之间仅出于学习目的进行交流。3、对提供的数字内容不拥有任何权利，其版权归原著者拥有。请勿将该数字内容进行商业交易、转载等行为，该内容只为学习所提供，使用后发生的一切问题与本站无关。 4、本网站不保证本站提供的下载资源的准确性、安全性和完整性;同时本网站也不承担用户因使用这些下载资源对自己和他人造成任何形式的损失或伤害。 5、本网站所有软件和资料均为网友推荐收集整理而来，仅供学习用途使用，请务必下载后两小时内删除，禁止商用。6、如有侵犯你版权的，请及时联系我们（电子邮箱1370723259@qq.com）指出，本站将立即改正。
|
|
