Simatic S Tcpu
Simatic S Tcpu
Simatic S Tcpu
Subset of the
Technical Specification
PLCopen - Technical Committee 2 – Task Force
Version 2.0
Appendix B
DISCLAIMER OF WARANTIES
THIS DOCUMENT IS PROVIDED ON AN “AS IS” BASIS AND MAY BE SUBJECT TO FUTURE ADDITIONS,
MODIFICATIONS, OR CORRECTIONS. PLCOPEN HEREBY DISCLAIMS ALL WARRANTIES OR
CONDITIONS OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY
WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR
A PARTICULAR PURPOSE, FOR THIS DOCUMENT. IN NO EVENT WILL PLCOPEN BE RESPONSIBLE FOR
ANY LOSS OR DAMAGE ARISING OUT OR RESULTING FROM ANY DEFECT, ERROR OR OMISSION IN
THIS DOCUMENT OR FROM ANYONE’S USE OF OR RELIANCE ON THIS DOCUMENT.
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 1/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
By submitting these tables to PLCopen, and after approval by PLCopen, the list will be published on the PLCopen web-
site, www.plcopen.org as well as a shortform overview, as specified in Appendix B 2 Supported Data types and Ap-
pendix B 3 Overview of the Function Blocks as below.
In addition to this approval, the supplier is granted access and usage rights of the PLCopen Motion Control logo, as
described in Appendix B 4:
Data types
The data type REAL listed in the Function Blocks and parameters (e.g. for velocity, acceleration, distance, etc.) may be
exchanged to SINT, INT, DINT or LREAL without to be seen as incompliant to this standard, as long as they are con-
sistent for the whole set of Function Blocks and parameters.
Implementation allows the extension of data types as long as the basic data type is kept. For example: WORD may be
changed to DWORD, but not to REAL.
- Basic input/output variables are mandatory Marked in the tables with the letter “B”
- Extended input /output variables are optional Marked in the tables with the letter “E”
- Vendor Specific additions Marked in the vendor’s compliance documentation with “V”
All the vendor specific items will not be listed in the comparison table on the PLCopen website, but in the detailed ven-
dor specific list, which also is published.
All vendor specific in- and outputs of all FBs must be listed in the certification list of the supplier. With this, the certifi-
cation listing from a supplier describes all the I/Os of the relevant FBs, including vendor-specific extensions, and thus
showing the complete FBs as used by the supplier.
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 2/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
I hereby state that the following tables as filled out and submitted do match our product as well as the accompanying
user manual, as stated above.
Signature:
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 3/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Defined datatypes with MC library: Supported If not supported, which datatype used
BOOL YES
INT YES Additional DINT
WORD YES Additional DWORD
REAL YES Additional LREAL
ENUM No INT is used
UINT YES
Table 1: Supported datatypes
Within the specification the following derived datatypes are defined. Define which of these structures are used in this
system:
Derived datatypes: Where used Supported Which structure
AXIS_REF Nearly all FBs YES TO_Axis
MC_DIRECTION MC_MoveAbsolute YES INT
(extended) MC_MoveVelocity
MC_TorqueControl
MC_MoveContinuousAbsolute
MC_TP_REF MC_PositionProfile No
MC_TV_REF MC_VelocityProfile No
MC_TA_REF MC_AccelerationProfile No
MC_CAM_REF MC_CamTableSelect No
MC_CAM_ID MC_CamTableSelect YES TO_Cam
(extended) MC_CamIn
MC_START_MODE MC_CamIn No
(extended) MC_CamTableSelect
MC_BUFFER_MODE Buffered FBs No
MC_EXECUTION_MODE MC_SetPosition No
MC_WriteParameter
MC_WriteBoolParameter
MC_WriteDigitalOutput
MC_CamTableSelect
MC_SOURCE MC_ReadMotionState No
MC_CamIn
MC_GearIn
MC_GearInPos
MC_CombineAxes
MC_DigitalCamSwitch
MC_SYNC_MODE MC_GearInPos No
MC_COMBINE_MODE MC_CombineAxes No
MC_TRIGGER_REF MC_TouchProbe YES TO_MeasuringInput
MC_AbortTrigger
MC_INPUT_REF MC_ReadDigitalInput No
MC_OUTPUT_REF MC_DigitalCamSwitch YES TO_OutputCam
MC_ReadDigitalOutput TO_CamTrack
MC_WriteDigitalOutput
MC_CAMSWITCH_REF MC_DigitalCamSwitch No Configured in TO_CamTrack or
TO_OutputCam
MC_TRACK_REF MC_DigitalCamSwitch No Configured in TO_CamTrack
Table 2: Supported derived datatypes
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 4/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 5/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 6/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 7/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 8/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 9/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 10/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 11/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 12/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 13/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 14/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 15/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 16/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 17/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 18/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 19/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 20/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 21/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 22/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 23/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 24/ 25
Compliance Procedure and Compliance List
PLCopen
for efficiency in automation
In order to use this logo free-of-charge, the relevant company has to fulfill all the following requirements:
1. the company has to be a voting member of PLCopen;
2. the company has to comply with the existing specification, as specified by the PLCopen Task Force Motion
Control, and as published by PLCopen, and of which this statement is a part;
3. this compliance application is provided in written form by the company to PLCopen, clearly stating the appli-
cable software package and the supporting elements of all the specified tables, as specified in the document it-
self;
4. in case of non-fulfillment, which has to be decided by PLCopen, the company will receive a written statement
concerning this from PLCopen. The company will have a one month period to either adopt their software pack-
age in such a way that it complies, represented by the issuing of a new compliance statement, or remove all ref-
erence to the specification, including the use of the logo, from all their specification, be it technical or promo-
tional material;
5. the logo has to be used as is - meaning the full logo. It may be altered in size providing the original scale and
color setting is kept.
6. the logo has to be used in the context of Motion Control.
Unrestricted TC2 Task Force Motion ControlMarch 17, 2011 © 1999 - 2011 copyright by PLCopen
Function Blocks for Motion Control Version 2.0, Appendix B page 25/ 25
Compliance Procedure and Compliance List