SIMATIC CFC介绍和安装文件下载网址
https://doc.eleok.com/843.html
SIMATIC Hotfix 12 for CFC V6.1 incl. Service Pack 1
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 V6.1 incl. Service Pack 1 (SP1).
Section 4 in Part II Notes on the Hotfix contains important information on the bugfix version CFC V6.1.1 Hotfix 12.
If you print the file, make sure that the left and right margins are set to a width of 25 millimeters (approximately 1 inch) for A4 portrait.
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 V6.1 incl. SP1
4.2 CFC V6.1 License Key
4.3 Uninstalling CFC V6.1 incl. SP1
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 is New in Version 6.1 ?
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
3 Notes on Documentation
4 Notes on the Hotfix
Notes on Installation
The installation notes contain important information that you will require to install CFC V6.1 incl. SP1. Read these notes before installing the software.
1 Contents of the Consignment
You received one of the following products with this consignment:
CFC V6.1 incl. SP1
Order number: 6ES7658-1EX16-2YA5
This package contains the following:
• 1 CD
• License Key Disk UPGRADE
• 1 Certificate of License
CFC V6.1 incl. SP1 Upgrade
Order number: 6ES7 658-1EX16-2YE5
This package contains the following:
• 1 CD
• License Key Disk UPGRADE
• 1 Certificate of License
Contents of the CFC CD
• CFC V6.1 incl. SP1
• Electronic manual "CFC - Getting Started" (for the sample project ZEn04_01_CFC)
• Electronic manual: "CFC - Manual for S7"
• Electronic manual: "CFC - Manual for M7"
• File "CFC-Whatsnew.wri"
The CFC can be run on the following operation systems:
• MS Windows 2000 Professional and SP3 or higher (subsequently called MS Windows 2000)
• MS Windows XP Professional with SP1 or SP1a or SP2 (subsequently called MS Windows XP)
• MS Windows Server 2003
Notice: MS Windows XP Home operating system is not supported.
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 V6.1 incl. SP1 is a 32-bit application that requires MS Windows 2000 or MS Windows XP or MS Windows Server 2003 as the operating system.
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.3 or higher
• If using CFC for M7:
• M7-SYS V2.1, M7-SYS-RT V4.0 or M7-SYS-RT V5.0
• MS Windows XP or MS Windows Server 2003 is not supported by M7-SYS, the operating system MS Windows 2000 must be selected.
• Borland C compiler V5.01 (can be supplied by Siemens; Order Number: 6ES7812-1BC01-0AA0)
----------------------------------------------------------------------------------------------------------------
Note:
The product SCL Compiler is no longer necessary as of CFC V6.1 incl. SP1.
The CFC setup automatically installs the necessary SCL Compiler functionality
(no SCL License Key is necessary).
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.
----------------------------------------------------------------------------------------------------------------
3.2 Memory Requirements
CFC V6.1 incl. SP1 requires approximately. 60 Mbytes of space on your hard disk.
4 Installation
4.1 Installing CFC V6.1 incl. SP1
When you install CFC V6.1 incl. SP1, 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 V6.1 License Key
Before you can start working with CFC, you must transfer the license key from the License Key Disk to the computer. There are two ways of doing this:
• While you are installing CFC, the Setup program displays a message if there is no suitable license key installed on your computer. You can then decide whether you want the license key to be installed by the Setup program or whether you want to install the license at a later time using the to-be-installed Automation License Manager program.
• 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 item Simatic\License Management\Automation License Manager.
The STEP 7 readme notices also apply to the license key.
4.3 Uninstalling CFC V6.1 incl. SP1
----------------------------------------------------------------------------------------------------------------
Important Note:
Software products must be removed according to Microsoft Windows conventions.
Use the Microsoft Windows application "Add/Remove Programs" (in the taskbar under Start > Settings > Control Panel > Add/Remove Programs) to remove your software package (for example, "SIMATIC CFC V6.1 + SP1"). This is the only way to uninstall software in Microsoft Windows.
----------------------------------------------------------------------------------------------------------------
This also 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.
Notes on Usage (Release Notes)
These notes should be considered more up-to-date than the information in manuals and online helps.
1 New Features and Modifications in the New Version
1.1 What is New in Version 6.1 ?
For more information, read the topic "What's New?" in the online help. You can call this topic from the contents page of the Help on CFC (menu command Help > Contents; Introduction to CFC ).
You will also find this information on the installation CD in the file "CFC-whatsnew" and following installation with START > Simatic > Product Notes.
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 V6.1:
• The CFC V3.x to CFC V6.0 data can be read and displayed with CFC V6.1.
• 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 V6.1:
• The CFC V1.x data can be read and displayed with CFC V6.1. 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 V6.x format.
General notes on compatibility:
• You cannot "reconvert" V6.1 data back to previous versions.
• Data created with newer CFC versions cannot be edited with previous CFC versions.
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 V6.1 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 V6.1
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 keyswitch 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.
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 (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.
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".
The manuals are available as electronic documentation and can be displayed and printed with the Acrobat Reader which is supplied with the software (Start > Simatic > Documentation).
4 Notes on the Hotfix
Hotfix 12 contains the following enhancements or bugfixes:
• When a chart is compiled as a block type which contains blocks with message functions, then the newly created block also has these message functions.
• When using custom blocks, the parameters can now also have names such as "MAX", "MIN", "LIMIT", "SEL" without the SCL compiler recognizing these as keywords and outputting an error during compilation.
• When updating blocks, renamed blocks and blocks capable of operator control and monitoring will also be updated.
• It was not possible to compile sucessfully if an SFC instance was interconnected with a block of the type TIMER_P (FB5) and the characteristic "Times" and the SFC type were used at the same time. This has been corrected.
• After the migration of project from version 6.0, compiling errors no longer occur even with highly complex configurations of characteristics at SFC types.
• When handling CFC and SFC objects in the Simatic Manager, the sporadic incorrect error message ("Hardware error") is no longer displayed.
• Blocks imported into CFC and later renamed in the symbol table are now recognized by CFC without explicit update (F5) or compilation.
• If only the interconnections of the outputs were changed in a hierarchy chart, these changes did not go into effect when the program was compiled. This error has been corrected.
• After stopping test mode and closing the SFC editor, the SFC Editor is correctly started as soon as a SFC is opened again.
• An existing SFC license is correctly detected even with a D7-SYS installation.
• Any number of chart folders can now be created during a session.
• The delta download of SFCs, which require a sequencer to be edited in the "Ready" operating mode, is now executed correctly in every case. This especially applies for interface changes of SFC types, since the associated SFC instances are now correctly canceled with a prompt by the user. A complete compile and download must be performed for this change to go into effect.
• The use of the data type Block_DB, Block_FB, Block_FC, Block_SDB is now correctly supported. Until now, a parameter change at such an input for a delta download was not applied in the online program.
• When the "Manage Multilingual Texts > Export..." function is executed in the SIMATIC Manager, the "Invalid identifier" message is no longer generated if global addresses with very long identifiers are used.
• When units and enumerations of setpoints in an SFC type are changed, these are now correctly entered in the SFC instances with "Compile OS" if no changes have been made to the units and enumerations in the SFC instance itself.
This correction requires the installation of AS-OS Engineering V6.1 SP1 Hotfix 2 or later.
For this correction to take effect, a complete compilation and download of the OS must be performed. Then you can compile and download changes for the OS once again.
• The demand on PTP resources were calculated with 0 during complete compiling of a program. This error has been corrected.
• When changing a UDT that is used more than 100 times in a block type, no more errors occur when the block type is imported into the CFC. Now, up to 1000 occurences of the same UDT can be used in a block type.
• The format for displaying addresses in the object properties of steps, transitions and sequences of SFC instances in the SFC visualization has been enhanced. Now, not only the address and its interconnection partner is displayed (e.g. "PH/CFC/Block.Elem"), the connection of the SFC instance is displayed as well (e.g."setpoint" ("PH/CFC/Block.Elem")).
• After changing SFC type characteristics it was necessary to compile the program a second time. This error has been corrected.
• While printing CFC charts, the printouts may be illegible due to a too wide font. The error only effected the following character sets: Greek, Turkish, Vietnamese, Hebrew, Baltic, Russian and Eastern European. This error has been corrected.
• When loading via the CFCs/SFCs all programs are checked. If not, loading with errors is canceled. When applying the CFC outside of PCS 7 (Application STEP 7) the following system blocks are now taken out of the check and loading is executed on AS 300 and AS 400: SFC 131...136. Only on AS 300: SFC 75 and 76, SFB 8, 9, 12...15.
• Real data type memory bits can now also be created as the first element in an SFC type via the memory bit editor.
• New functions can be selected for the shared declarations in the multiproject.
Update in Multiproject: Using the menu command "Shared declarations > Update in Multiproject" you can call up the dialog box, by selectively merging all shared declarations of all projects of a multiproject or you can export them in other projects. If errors occurred while synchronizing, reading the full log (menu command "Shared declarations > Display full log synchronization") you can find out in which projects the error occurred. Using the menu command "Shared declarations > Display log synchronization" you can open the log for a project in which the actions and errors have been listed.
Check plausibility: With the menu command "Shared declarations > Check plausibility" you check the distinct existing enumerations, which means that you are checking that the enumeration values are not being used twice. When you have executed the check of a single project, the log is automatically opened at the end of the check. When you have executed a check for a multiproject you will receive a message asking you to open the local project logs to identify possible errors. The log is opened with the menu command "Shared declarations > Display log plausibility check".
• If you used "S7 F Systems" and programmed several runtime groups there in a partial shutdown group, F module drivers were positioned at the wrong location when "Generate Module Drivers" was performed, which then required an additional compilation. This resulted in an unnecessary prompt from the security password. This scenario has been corrected.
• If you create a new interconnection at a structured input of a nested chart, it is now assigned an initialization value typical for its type (similar to all other data types), i.e. any previously assigned parameters are discarded. This is especially important when using F blocks, as they otherwise are given a wrong collective signature during the compilation of the changes.
• The "Save as... With Reorganization" can now also be performed when a multiproject contains more than 60 chart folders and shared declarations.
• When moving the mouse pointer in test mode, an "Internal error (3)" error message appeared sporadically. This has been corrected.
• When the data type of a characteristic is changed in an SFC type, the points of use in the sequencers, steps and transitions are now adapted accordingly. If these modifications cannot be made distinctively, the addresses in text references may be converted in some instances. The affected points of use are displayed during the conversion.
• When a value for an I/O with the data type BYTE, WORD or DWORD is entered in test mode, the value is uniformly displayed and processed standardized (e.g. input '10' for the WORD data type is standardized to '0x000A').
• Parameters that have set the UDA "S7_param" to "False" are no longer read back when "All parameters" are selected in the readback dialog. This corresponds once again to the reaction in CFC V6.0.
• Compilation of a program was frozen in the initialization phase if symbolic names of instantiated blocks were deleted from the symbol table or if different notations in terms of uppercase and lowercase letters were being used in the name of block types of which several instances existed. This error has been corrected.
• An active chain was possibly no longer processed if interconnections were changed at the inputs of an SFC instance. This error has been corrected.
• When blocks with inverted inputs were copied, the inversion identifier was frozen in the representation of the copied block, irrespective of the removal of the input interconnection. This representation error has been corrected.
• Copying of CFC templates from the "SIMATIC BATCH AS based" library to a program is now supported.
• As these are now transferred correctly to WinCC, it is again possible to use the free associated values with SFCs by interconnecting inputs AUX_PR04 to AUX_PR10. In order to correctly transfer newly interconnected associated values to WinCC, a compilation of the changes, a download of the changes and, for newly interconnected associated values, the automation system must be restarted. For this reason, the associated values should only be changed if this procedure can be subsequently performed as described. If no associated values are added, the restart of the automation system is not necessary.
• If there were interconnections of a structured data type between inputs or outputs of CFC instances and shared data blocks in the program and the structured data type of the CFC instance was changed to the "ANY" data type, sometimes the interconnection could no longer be deleted because a structured data type and, therefore, a global variable could not be deleted. As a result, neither the involved CFC instance nor the chart could be deleted. This error has been corrected.
• Error correction for SFC:
Depending on the configuration of an SFC chart or SFC type (for example, a sequencer with the start condition "IDLE=TRUE), sometimes the changed configuration could not be loaded into the automation system with a download of changes (for example, when the SFC in the automation system was in the IDLE state at the time of download).
• To ensure that changed SFCs can be loaded with a download of changes, SIMATIC SFC 6.1 SP1 Hotfix 1 must be installed in addition to the current hotfix and the procedure described in the corresponding readme must be performed. Subsequently, a complete compilation and a download of the changes must be carried out for each chart folder with SFCs. Configuration changes cannot be simultaneously made during this procedure because they may prevent the download of the changes.
• Error correction for SFC Visualization:
Depending on the configuration of a SFC chart or SFC type, sometimes a process value was displayed incorrectly in a transition.
The following should be done to ensure that this error no longer occurs:
In addition to this hotfix, Hotfix 5 for SIMATIC SFC Visualization 6.1 SP1 or a later hotfix for this version should be installed and the procedure described in the corresponding readme file should be performed. The OS must then be compiled ("SFC Visualization" option activated, "Changes" option for the scope is sufficient) and an OS download performed ("Changes" option for the scope is sufficient).
• Error correction for SFC:
After changes in the sequencer topology, the concerned and running SFCs must be aborted before user acknowledgment. If sequencers are concermed by changes, which should have been canceled during processing SFCs, these were no longer processed due to an incorrectly set startup lock.
• Even very large (multi) projects with multiple AS stations can now be completely compiled with the function "Compile and Download Objects".
• In very rare cases the message "Check the consistency of the ES data management!" was output when compiling the OS from programs with SFC types. This error has been corrected.
• Error correction for SFC:
Sporadically, the message "Execution time exceeded" was output by the WinCC message system during a transition of the AS operating mode from STOP to RUN, although no triggering event ocurred. This error has been corrected.
Each chart folder with SFC instances has to be completely recompiled and the changes have to be downloaded for this correction to take effect.
• Referenced SFB instances that are missing are now listed correctly in the compilation protocol.
• The starting value of a enumeration in WinCC that is used in a block I/O and can be altered and monitored, will remain intact even after the block interface has been changed. This correction is effective only for the AS-OS-Engineering V6.1.1 with Hotfix 2 or higher.
• When copying SFC types to a user program, the message "Invalid identifier" may show up if this program already contains a lot of SFC types. This error has been corrected.
• The SCL component is now installed in version V5.3.2. This solves an internal SCL problem which may have resulted in an unexpected termination of the CFC compilation under certain circumstances.
• During read back, real values of less than 1e-37 are entered as 0.
• Changes of Global-DBs are now saved when compiling, even if option "Generate Module Drivers" has not been selected.
• The invalid use of elements of a structure of an IN_OUT I/O type in a step or transition of an SFC type is now recognized as a error, when compiling the program.
【必读】版权免责声明
1、本主题所有言论和内容纯属会员个人意见，与本论坛立场无关。2、本站对所发内容真实性、客观性、可用性不做任何保证也不负任何责任，网友之间仅出于学习目的进行交流。3、对提供的数字内容不拥有任何权利，其版权归原著者拥有。请勿将该数字内容进行商业交易、转载等行为，该内容只为学习所提供，使用后发生的一切问题与本站无关。 4、本网站不保证本站提供的下载资源的准确性、安全性和完整性;同时本网站也不承担用户因使用这些下载资源对自己和他人造成任何形式的损失或伤害。 5、本网站所有软件和资料均为网友推荐收集整理而来，仅供学习用途使用，请务必下载后两小时内删除，禁止商用。6、如有侵犯你版权的，请及时联系我们（电子邮箱1370723259@qq.com）指出，本站将立即改正。
|
|
