BRESIMAR(asaTek)-Beckhoff-Livro Formação Técnica TwinCAT 2
BECKHOFF - TwinCAT 2 Livro de Formação Técnica v1.2/2009 BRESIMAR AUTOMAÇÃO / asaTek Autoria : Jorge Andril
BECKHOFF - TwinCAT 2
Livro de Formação Técnica v1.2/2009
BRESIMAR AUTOMAÇÃO / asaTek
Autoria : Jorge Andril
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
TWINCAT PLC – Lista de erros<br />
BECKHOFF New Automation Technology<br />
not defined<br />
supported in current<br />
code generator!<br />
3700 POU with name<br />
‘' is already in<br />
library ''<br />
3701 Name used in interface<br />
is not identical with<br />
POU Name<br />
for a subrange or array type.<br />
not support bit access on variables.<br />
A POU name is used in the project, which is already used for<br />
a library POU. Rename the POU.<br />
Use command ‘Project’ ‘Rename object’ to rename the POU<br />
in the object organizer, or change the name of the POU in<br />
the declaration window. There the POU name has to be<br />
placed next to one of the keywords PROGRAM, FUNCTION<br />
or FUNCTIONBLOCK.<br />
3702 Overflow of identifier list Maximum 100 identifiers can be entered in one variable<br />
3703 Duplicate definition of<br />
identifier ''<br />
3905 data recursion:<br />
-> -<br />
> .. -> <br />
3720 Address expected after<br />
'AT'<br />
3721 Only 'VAR' and<br />
'VAR_GLOBAL' can be<br />
located to addresses<br />
3722 Only 'BOOL' variables<br />
allowed on bit<br />
addresses<br />
3729 Invalid type '' at<br />
address: ''<br />
declaration.<br />
Take care that there is only one identifier with the given<br />
name in the declaration part of the POU.<br />
A FB instance was used, which needs itself.<br />
Add a valid address after the keyword AT or modify the<br />
keyword.<br />
Put the declaration to a VAR or VAR_GLOBAL declaration<br />
area.<br />
Modify the address or modify the type of the variable to<br />
which the address is assigned.<br />
The type of this variable cannot be placed on the given<br />
address. Example: For a target system working with<br />
‘alignment 2’ the following declaration is not valid: var1 AT %<br />
IB1:WORD;<br />
3740 Invalid type: '' An invalid data type is used in a variable declaration.<br />
3741 Expecting type<br />
specification<br />
3742 Enumeration value<br />
expected<br />
3743 Integer number<br />
expected<br />
3744 Enum constant<br />
'' already<br />
defined.<br />
A keyword or an operator is used instead of a valid type<br />
identifier.<br />
In the definition of the enumeration type an identifier is<br />
missing after the opening bracket or after a comma between<br />
the brackets.<br />
Enumerations can only be initialized with numbers of type<br />
INT.<br />
Check if you have followed the following rules for the<br />
definition of enumeration values:<br />
- Within one enum definition all values have to be unique.<br />
- Within all global enum definitions all values have to be<br />
unique.<br />
- Within all local enum definitions all values have to be<br />
unique<br />
3745 Subranges are only<br />
allowed on Integers!<br />
Subrange types can only be defined resting on integer data<br />
types.<br />
3746 Subrange '' is<br />
not compatible with<br />
One of the limits set for the range of the subrange type is out<br />
of the range which is valid for the base type.<br />
Type ''<br />
3747 unknown string length:<br />
''<br />
There is a not valid constant used for the definition of the<br />
string length.<br />
3748 More than three<br />
dimensions are not<br />
allowed for arrays<br />
More than the allowed three dimensions are given in the<br />
definition of an array. If applicable use an ARRAY OF<br />
ARRAY.<br />
3749 lower bound ''<br />
not defined<br />
There is a not defined constant used to define the lower limit<br />
for a subrange or array type.<br />
3903 Invalid duration<br />
constant<br />
The notation of the constant does not comply with the<br />
IEC61131-3 format.<br />
3904 Overflow in duration<br />
constant.<br />
The value used for the time constant cannot be represented<br />
in the internal format. The maximum value which is<br />
representable is t#49d17h2m47s295ms<br />
3905 Invalid date constant The notation of the constant dies not comply with the<br />
IEC61131-3 format.<br />
3906 Invalid time of day<br />
constant<br />
The notation of the constant dies not comply with the<br />
IEC61131-3 format.<br />
3907 Invalid date and time<br />
constant<br />
The notation of the constant dies not comply with the<br />
IEC61131-3 format.<br />
<strong>BRESIMAR</strong> Anexo B – 9 de 18