Knowledge Base
Knowledge Base of the TcPlcHydraulics PLC library (from V3.0)
Here you will find a number of answers to recurring questions.
Topics
|
Name |
Description |
|---|---|
|
Pre-defined error codes, masks for bit queries, ADS codes etc. | |
|
Setup |
Commissioning information |
|
Program examples | |
|
Tips and tricks | |
|
The PlcMcManager |
Problems during library updates
Compilation problems may occur when the library is updated. The reason may be a change of name of one or several function blocks or data types. Such changes are not always avoidable and generally implemented for one of the following reasons:
- Adaptation to the rules of the PLC Open Motion Control definitions.
- Further development of the PLC Open Motion Control definitions.
- Further development the technology provided.
- Adaptation to the technology used, particularly support of further I/O devices.
- Avoidance of name collisions and other compatibility problems with other libraries.
From V3.0 build 22, the library uses TcEtherCAT.LIB for communication via the EtherCAT fieldbus. In older TwinCAT environments this library is not yet available. If the TcPlcHydraulics library is to be used in such an environment, the TcEtherCatDummy.LIB provided should be copied into the project directory and renamed to TcEtherCAT.LIB. This library should then be added to the project BEFORE TcPlcHydraulics.LIB.
 | This procedure must not be used in TwinCAT environments that support EtherCAT. The file provided must NOT be used to replace an existing operational TcEtherCAT.LIB. |
There are no functions that require EtherCAT technologies.
| The library version used in a project should be copied into the project directory and backed up together with the project. This avoids inadvertent version changes, which could otherwise occur if TwinCAT is updated in the meantime. To update the library, copy the new version directly into the project directory. |
| We strongly recommend carrying out a trial compilation of the whole project after a library update. In addition, the mapping should be updated with the System Manager. If the table shown below indicates a change in size in one of the structures, it is essential to check the address assignment. |
| If the library is updated to a version that differs not only in the third (build) number, but also in the major and minor version number, it can be assumed that the mappings created by the System Manager are no longer correct. In this case it is imperative to refresh the links. |
Old name | New name | Reason of for the change |
|---|---|---|
ST_TcMcAxInterface | Axis_Ref_BkPlcMc | Adaptation to PLC Open Motion Control definitions. |
ST_TcPlcMcCamId | MC_CAM_ID_BkPlcMc | Adaptation to PLC Open Motion Control definitions. |
ST_TcPlcMcCamRef | MC_CAM_REF_BkPlcMc | Adaptation to PLC Open Motion Control definitions. |
E_TcMCDirection | MC_Direction_BkPlcMc | Adaptation to PLC Open Motion Control definitions. |
E_TcMCStartMode | MC_StartMode_BkPlcMc | Adaptation to PLC Open Motion Control definitions. |
ST_TcPlcMcEncoderIn | --- | Omitted; task is handled by ST_TcPlcDeviceInput |
ST_TcPlcMcEncoderOut | --- | Omitted; task is handled by ST_TcPlcDeviceOutput |
ST_TcPlcMcDriveIn | --- | Omitted; task is handled by ST_TcPlcDeviceInput |
ST_TcPlcMcDriveOut | --- | Omitted; task is handled by ST_TcPlcDeviceOutput |
ST_TcPlcMcAx2000In | --- | Omitted; task is handled by ST_TcPlcDeviceInput |
ST_TcPlcMcAx2000Out | --- | Omitted; task is handled by ST_TcPlcDeviceOutput |
MC_AxUtiCancelMonitoring_BkPlcMc | --- | Omitted; redundant due to PLC Open definitions |
Size of the I/O structures in bytes
|
Name |
V 2.1.X |
from V3.0.0 |
from V3.1.0 (proposed) |
|---|---|---|---|
|
ST_TcPlcMcEncoderIn |
16 |
- |
- |
|
ST_TcPlcMcEncoderOut |
1 |
- |
- |
|
ST_TcPlcMcDriveIn |
23 |
- |
- |
|
ST_TcPlcMcDriveOut |
40 |
- |
- |
|
ST_TcPlcMcAx2000In |
37 |
- |
- |
|
ST_TcPlcMcAx2000Out |
26 |
- |
- |
|
- |
143 |
? | |
|
- |
103 |
? |