Lenze DDS v2.3 - Manual (Page 321)

Drive PLC Developer Studio
Appendix
15-11
l
DDS EN 2.3
No. Possible remedy Cause
1901 Access variables and configuration variables are not saved
in a library! Access variables and variable configurations are not saved in the library.
1902 : Library not suitable for the current machine type! The .obj file of the library was generated for a different machine type.
1903 : Incorrect library The file does not correspond to the file format required by the automation system.
2900 A system organization unit was used in a scale function. It
is possible that no process image will be generated for this
system organization unit.
Chapter on Scale functions ( ^ 8-18).
Ensure with the help of the process image monitor that a process image is generated for the
applied system organization unit.
^ 8-20
2901 A system organization unit was used in a system POU. It is
possible that no process image will be generated for this
system organization unit.
Chapter System POUs in the automation system
documentation (
^ 2-7)
Ensure with the help of the process image monitor that a process image is generated for the
applied system organization unit.
Caution!
Even if a process image is generated, some system POUs may cause problems if the data do
not exist yet at the time of processing.
2902 Invalid target path for the GDC device description.
An error occurred during generation of the GDC device
description. For the error cause refer to the transmitted
error code:
100: No valid name for the device description
200: Basic device description could not be opened
300: Error in basic device description
100:
Use
Project W Options category Device description to specify a different path.
200, 300:
Deinstall the DDS and correctly reinstall it.
If the error still occurs, please contact your Lenze representative.
2903 A user code is using an unknown unit. Define the applied unit in the Instance Parameter Manager. ^ 8-11
2904 The code reference to an organization unit could not be
resolved. The organization unit was deleted.
2905 The binary file project name.bin (*.bin) could not be
created. The *.bin file may be write-protected. Remove the write protection.
15.5.2 Compile errors
No. Cause Possible remedy
3100 Program too large.
Maximum size: byte (K) Maximum program size exceeded.
Reduce program size.
3101 Data area too large.
Maximum size: byte (K) The data memory is full.
Reduce your applications data requirement.
3110 Error in library file . The .hex file does not correspond to the INTEL hex format.
3111 Library is too big. Maximum size: 64K The .hex file exceeds the maximum possible size.
3112 Irrelocatable instruction in library. The .hex file contains an irrelocatable instruction.
The library code can not be linked.
3113 Library code overwriting function tables. The code and information table sections overlap.
3114 Library uses more than one segment. The tables and code in the .hex file use more than one segment.
3115 Constant cannot be assigned to VAR_IN_OUT. Incompatible
data types. The internal pointer format for string constants cannot be converted into the internal pointer
format of VAR_IN_OUT as the data are defined as near and the string constants as huge or
far.
Change these automation system settings if possible
3120 Current code segment in excess of 64K. The system code just generated is in excess of 64K.
The system possibly requires too much initialization code.
3121 Organization unit too big. An organization unit must not exceed 64K.
3122 Initialization too large. Maximum size: 64K The initialization code for a function block or a structure must not exceed 64K.
3130 Application stack too small:
DWORD required
DWORD available. The organization unit calls are nested too deeply. Enlarge the stack size in the automation
system settings, or compile the program without the project compile option Debug.
3131 User stack too small:
WORD required, WORD available. Contact the control manufacturer.
3132 System stack too small:
WORD required, WORD available. Contact the control manufacturer.
3150 Parameter %d of function :
The result of an IEC function cannot be transferred to a C
function as string parameter. Use an intermediate variable.
Transfer the result of an IEC function to the variable.
3160 Cannot open library file . The file required for a library cannot be found.
3161 Library contains no code segment An .obj file of a library must contain at least one C function.
Insert a dummy function into the .obj file, that is not defined in the .lib file.
3162 Cannot resolve reference in library (Icon
, Class , Type ) The .obj file contains an irresolvable reference to another icon.
Check the C compiler settings.
Show/Hide Bookmarks