About this manual Overview: documentation modules for CR0452
>
Document
Contents / Description
Data sheet
Technical data in a table
Installation instructions
(are supplied with the
device)
Instructions for installation, electrical installation, and commissioning
Technical data
Programming manual
Functions of the setup menu of the device
Creation of a CODESYS project with this device
Target settings with CODESYS
Programming of the device-internal PLC with CODESYS
Description of the device-specific CODESYS function libraries
System manual
"Know-How ecomatmobile"
Know-how about the following topics (examples):
Overview Templates and demo programs
CAN, CANopen
Control outputs
Visualisations
Overview of the files and libraries
1.2 Overview: documentation modules for CR0452
The documentation for this devices consists of the following modules:
(Downloads from ifm's website →www.ifm.com )
About this manual How is this documentation structured?
>
Date
Theme
Change
2014-03-24
Visualisation limits
Information concerning the permissible drawing area
2014-04-29
FB CAN_REMOTE_RESPONSE
More precise description of the function block
ENABLE
2014-05-12
Limitations CAN
Limitations added for CAN, CANopen and CAN J1939
2014-06-30
Name of the documentation
"System manual" renamed as "Programming manual"
2015-01-13
Structure of documentation for error codes, system
flags
• error flags:
now only in the appendix, chapter System flags
• CAN / CANopen errors and error handling:
now only in the system manual "Know-How"
• error codes, EMCY codes:
now in the appendix, chapter Error tables
2015-03-10
Available memory
Description improved
2017-01-13
Software manual for CODESYS 2.3
hint to download from the ifm homepage removed
2018-07-09
List of the ifm branch offices
removed
1.4 How is this documentation structured?
This documentation is a combination of different types of manuals. It is for beginners and also a
reference for advanced users. This document is addressed to the programmers of the applications.
How to use this manual:
Refer to the table of contents to select a specific subject.
Using the index you can also quickly find a term you are looking for.
At the beginning of a chapter we will give you a brief overview of its contents.
Abbreviations and technical terms → Appendix.
In case of malfunctions or uncertainties please contact the manufacturer at:
Contact →www.ifm.com
We want to become even better! Each separate section has an identification number in the top right
corner. If you want to inform us about any inconsistencies, indicate this number with the title and the
language of this documentation. Thank you very much for your support!
We reserve the right to make alterations which can result in a change of contents of the
documentation. You can find the current version on ifm's website:
→www.ifm.com
>
204
1508
1.5 History of the instructions (CR0452)
What has been changed in this manual? An overview:
What previous knowledge is required? .................................................................................................... 8
Start-up behaviour of the controller .......................................................................................................... 9
Notes: serial number ................................................................................................................................ 9
WARNING
Non-observance of these instructions can lead to property damage or personal injury.
ifm electronic gmbh does not assume any liability in this regard.
► The acting person must have read and understood the safety instructions and the corresponding
chapters in this manual before working on and with this device.
► The acting person must be authorised to work on the machine/equipment.
► The acting person must have the qualifications and training required to perform this work.
► Adhere to the technical data of the devices!
You can find the current data sheet on the ifm website.
► Note the installation and wiring information as well as the functions and features of the devices!
→ supplied installation instructions or on the ifm website.
Homepage →www.ifm.com
>
2.1 Please note
6091
11779
No characteristics are warranted with the information, notes and examples provided in this manual.
With the drawings, representations and examples given no responsibility for the system is assumed
and no application-specific particularities are taken into account.
► The manufacturer of the machine/equipment is responsible for ensuring the safety of the
machine/equipment.
► Follow the national and international regulations of the country in which the machine/installation is
to be placed on the market!
213
>
2.2 What previous knowledge is required?
This document is intended for people with knowledge of control technology and PLC programming
with IEC 61131-3.
To program the PLC, the people should also be familiar with the CODESYS software.
The document is intended for specialists. These specialists are people who are qualified by their
training and their experience to see risks and to avoid possible hazards that may be caused during
operation or maintenance of a product. The document contains information about the correct handling
of the product.
Read this document before use to familiarise yourself with operating conditions, installation and
operation. Keep the document during the entire duration of use of the device.
Safety instructions Start-up behaviour of the controller
>
WARNING
Danger due to unintentional and dangerous start of machine or plant sections!
► When creating the program, the programmer must ensure that no unintentional and dangerous
start of machines or plant sections after a fault (e.g. e-stop) and the following fault elimination can
occur!
Realise restart inhibit.
► In case of an error, set the outputs concerned to FALSE in the program!
2.3 Start-up behaviour of the controller
6827
15233
11575
A restart can, for example, be caused by:
• Voltage restoration after power failure
• Reset after the watchdog responded because the cycle time was too long
• Error elimination after an E-stop
To ensure safe controller behaviour:
► monitor the voltage supply in the application program.
► In case of an error switch off all relevant outputs in the application program.
► Additionally monitor actuators which can cause hazardous movements in the application program
(feedback).
► Monitor relay contacts which can cause hazardous movements in the application program
(feedback).
► If necessary, ensure that welded relay contacts in the application project cannot trigger or continue
hazardous movements.
>
2.4 Notes: serial number
20780
► In the user's production facility, draw a diagram of the controller network in the machine. Enter the
serial number of each controller installed into the network diagram.
► Before downloading a software component, read out this serial number and check the network
diagram to make sure that you are accessing the right controller.
Cable for power supply and CAN between the display and the BasicController when the
cover EC0402 is used
EC0454
5 m cable for power supply and CAN between the display and the BasicController
---
"Maintenance Tool" software for updating firmware, runtime system and application
program
Download →www.ifm.com
>
3.1 Information about the device
This manual describes of the ecomatmobile family for mobile machines of ifm electronic gmbh:
BasicDisplayXL: CR0452
The display is part of the family of the BasicController: CR040n, CR041n, CR043n.
>
3.1.1 Accessories
A wide range of accessories is available for the BasicDisplay. Examples:
975
15407
15406
You can find accessories for the article on ifm's website:
→www.ifm.com > Select your country > [Data sheet search] > article no. > [Accessories]
CAN interfaces .......................................................................................................................................15
CAN: interfaces and protocols ................................................................................................................15
CAN interface
CAN 1
CAN 2
CAN 3
CAN 4
Default download ID
ID 127
ID 126
ID 125
ID 124
CAN protocols
CAN Layer 2
Interface does not
exist
Interface does not
exist
Interface does not
exist
CANopen
SAE J1939
3.3 Interface description
3.3.1 CAN interfaces
Connections and data → data sheet
>
CAN: interfaces and protocols
The device is equipped with only one CAN interface.
The interface can be used with the following functions:
• RAW-CAN (Layer 2): CAN on level 2 (→ chapter Function elements: RAW-CAN (Layer 2) (→ p. 52))
• CANopen master / CANopen slave (→ chapter Function elements: CANopen (→ p. 80))
Software modules for the device ............................................................................................................16
Programming notes for CODESYS projects ...........................................................................................19
Operating states .....................................................................................................................................22
Performance limits of the device ............................................................................................................25
Runtime system ......................................................................................................................................17
Application program ................................................................................................................................17
The software in this device communicates with the hardware as below:
14107
14110
*) The runtime system version number must correspond to the target version number in the CODESYS target system setting.
→ chapter Set up the target (→ p. 36)
The user is responsible for the reliable function of the application programs he designed. If necessary,
he must additionally carry out an approval test by corresponding supervisory and test organisations
according to the national regulations.
Bootloader
14111
On delivery ecomatmobile controllers only contain the boot loader.
The boot loader is a start program that allows to reload the runtime system and the application
program on the device.
The boot loader contains basic routines...
• for communication between hardware modules,
• for reloading the operating system.
The boot loader is the first software module to be saved on the device.
>
Runtime system
14112
Basic program in the device, establishes the connection between the hardware of the device and the
application program.
→ chapter Software modules for the device (→ p. 16)
On delivery, there is normally no runtime system loaded in the controller (LED flashes green at 5 Hz).
Only the bootloader is active in this operating mode. It provides the minimum functions for loading the
runtime system, among others support of the interfaces (e.g. CAN).
Normally it is necessary to download the runtime system only once. Then, the application program can
be loaded into the controller (also repeatedly) without affecting the runtime system.
The runtime system is provided with this documentation on a separate data carrier. In addition, the
current version can be downloaded from the website of ifm electronic gmbh:
→www.ifm.com
>
Application program
15274
14118
Software specific to the application, implemented by the machine manufacturer, generally containing
logic sequences, limits and expressions that control the appropriate inputs, outputs, calculations and
decisions.
The visualisation pages and embedded graphics are part of the CODESYS application program.
FB, FUN, PRG in CODESYS .................................................................................................................19
Note the cycle time! ................................................................................................................................20
Important note to program the device ....................................................................................................20
Creating application program .................................................................................................................21
Using ifm maintenance tool ....................................................................................................................22
Distribution of the application program ...................................................................................................22
NOTE
Function blocks must NOT be called in functions!
Otherwise: During execution the application program will crash.
All function elements must NOT be called recursively, nor indirectly!
An IEC application may contain maximum 8000 function elements; in this device maximum 512
function elements!
3.4.2 Programming notes for CODESYS projects
Here you receive tips how to program the device.
► See the notes in the CODESYS programming manual.
>
FB, FUN, PRG in CODESYS
In CODESYS we differentiate between the following types of function elements:
FB = function block
• An FB can have several inputs and several outputs.
• An FB may be called several times in a project.
• An instance must be declared for each call.
• Permitted: Call FB and FUN in FB.FUN = function
• A function can have several inputs but only one output.
• The output is of the same data type as the function itself.PRG = program
• A PRG can have several inputs and several outputs.
• A PRG may only be called once in a project.
• Permitted: Call PRG, FB and FUN in PRG.
7426
15410
Background:
All variables of functions...
• are initialised when called and
• become invalid after return to the caller.
Function blocks have 2 calls:
• an initialisation call and
• the actual call to do something.
Consequently that means for the function block call in a function:
• every time there is an additional initialisation call and
Risk that the device acts too slowly!
Cycle time must not become too long!
► When designing the application program the above-mentioned recommendations must be
complied with and tested.
► If necessary, the cycle time must be optimised by restructuring the software and the system
set-up.
Note the cycle time!
For the programmable devices from the controller family ecomatmobile numerous functions are
available which enable use of the devices in a wide range of applications.
As these units use more or fewer system resources depending on their complexity it is not always
possible to use all units at the same time and several times.
>
Important note to program the device
Applies to the following devices:
• BasicController relay CR0431► For the time of programming interconnect the connections B:1 (VBB15) and B:8 (VBBs).
Otherwise programming is not possible.
Background:
The controller resets all outputs when programming begins, also SUPPLY_SWITCH.
Without VBB15 the controller would be separated from the voltage supply and is switched off.
When the controller is switched on again, the device is in bootloader mode.
The programmer has to load the Basic System to the device again.
Then reload the application program to the device.
The application program is generated by the CODESYS 2.3 programming system and loaded in the
controller several times during the program development for testing:
In CODESYS: [Online] > [Login] > load the new program.
For each such download via CODESYS 2.3 the source code is translated again. The result is that
each time a new checksum is formed in the controller memory. This process is also permissible for
safety controllers until the release of the software.
8007
Graphics: Creation and distribution of the software
The ifm Maintenance Tool serves for easy transfer of the program code from the programming station
to the controller. As a matter of principle each application software can be copied to the controllers
using the ifm Maintenance Tool. Advantage: A programming system with CODESYS licence is not
required.
Here you will find the current ifm Maintenance Tool:
Homepage →www.ifm.com
>
Distribution of the application program
8493
We recommend the following sequence, if the application software is to be copied to the series
machine and used:
Saving the software
After completion of program development the latest version of the application program loaded in
the controller using the ifm Maintenance Tool has to be read from the controller and saved on a
data carrier using the name project_file.RESX. Only this process ensures that the application
software and its checksums are stored.
Download of the software.
To equip all machines of a series production with an identical software only this file may be loaded
in the controllers using the ifm Maintenance Tool.
An error in the data of this file is automatically recognised by the integrated checksum when
loaded again using the ifm Maintenance Tool.
>
3.4.3 Operating states
After power on the ecomatmobile device can be in one of five possible operating states:
• BOOTLOADER
• INIT
• STOP
• RUN
• SYSTEM STOP
>
INIT state (Reset)
Premise: a valid runtime system is installed.
This state is passed through after every power on reset:
> The runtime system is initialised.
> Various checks are carried out, e.g. waiting for correctly power supply voltage.
> This temporary state is replaced by the RUN or STOP state.
> The LED lights orange.
Change out of this state possible into one of the following states:
A transition into this state is possible in the following cases:
• if the supply voltage is too low.
In the ERROR state:
> The outputs of the device are switched off.
> Processing of the application program is stopped.
> System parameters are saved.
> The LED flashed red with 5 Hz.
A transition from this state into one of the following states is possible:
• INIT (after power-on-reset)
• RUN
• STOP
• FATAL ERROR
>
FATAL ERROR state
A transition into this state is possible in the following cases:
• memory error (RAM / Flash)
• exception error
• runtime system error
In the FATAL ERROR state:
> The outputs of the device are switched off.
> The application program is terminated.
> The runtime system is terminated.
> The LED lights red.
A transition from this state into one of the following states is possible:
In this device, a watchdog monitors the program runtime of the CODESYS application.
If the maximum watchdog time (application program: 100 ms; visualisation: 1 200 ms) is exceeded:
> the device changes to the "Timeout Error" state
> all processes are stopped (reset)
> all outputs are switched off
> the screen goes black
> the status LED flashes red at 10 Hz
Eliminate the fault:
Delete application program!
PowerOn Reset
Reload the application program into the device
If the watchdog in question fails:
> a second watchdog leads the device to the state "Fatal Error"
> the status LED lights red
Eliminate the fault:
PowerOn Reset
If unsuccessful:
Goto Bootloader
PowerOn Reset
Reload the runtime system into the device
Reload the application program into the device
If unsuccessful:
Hardware error: return device to ifm!
8 bit = 28 colours = 256 colours can be represented
Required memory space
< 76 Kbytes, depending on the image content for RLE compression
Visualisation limits
Embedded displays, used e.g. in ecomatmobile devices, cannot provide the full colour scope of
bitmap graphics because the available power reserves are restricted. Nevertheless, the following
preparations enable bitmap images in the device:
Correct selection of the motifs,
clever shifting of colours or
clever compilation of a colour palette and
the correct scaling of the bitmaps before using them in the device.
Performance limits of the device (→ p. 25)
Table: specifications for the start image
The graphics used in the project may be larger than the specified image size. In this case, however,
only a (selectable) section of the image will be visible.
Colours:
The device supports 28 (= 256) colour nuances.
► Create bitmap (BMP) with 256 colours:
8337
8465
8464
>
Resample / scale image
If an image is loaded in the device which does not meet the requirements for size or colour, it is
resized before it is displayed and the colours used are "checked".
Each time the image is opened, it must be resampled. This often leads to much longer times to
change from one image to the other. Corrective measures:
► First carry out all transformations of the bitmap or the image in an image processing program on
your computer.
Only for BasicDisplay: The colour palette is adapted when the image is integrated into the project
by CODESYS. On the device itself no adaptations will be made (size, scaling, colour).
► Only save the suitably transformed images in the visualisation of the device.
A polyline is to consist of maximum 5 anchor points; not scalable
A polyline is not to enclose any area.
Curve
--
Not supported
Rectangle
+
No problems known
Rounded rectangle
--
Not supported
Circle, ellipse
+
No problems known
Polygon
o
A polygon is to consist of maximum 10 anchor points; not scalable
Pie chart
--
Not supported
Visualisation
--
Not supported
Button
--
Not supported
Table
--
Not supported
Scroll bar
--
Not supported
Trend curve
--
Not supported
Alarm table
--
Not supported
Scales
+
Create scale as BMP file
Pointer instrument
+
Represent pointer instrument as BMP file with a superposed CoDeSys
polygon
Bar graph
+
Create scale as BMP file
Represent value as a superposed CoDeSys rectangle
Histogram
+
Create scale as BMP file
Represent value as a superposed CoDeSys rectangle
Graphic file
+
Up to 256 per project possible
• BMP ¹)
• BMP RLE compressed
• TIFF ¹)
• JPEG ¹)
Graphics scaling mode
o
Supported for circle, ellipse, rectangle, line, polyline, polygon
ActiveX element
--
Not supported
Pointer diagram
--
Not supported
Edit tools
--
Not supported
+
o
--
can be used without problem
can be used with restrictions
cannot be used
CODESYS visualisation elements
Bitmap graphics (BMP) chapter Visualisation limits (→ p. 26)
Not all CODESYS functions can be executed successfully on this device:
453
¹) During the integration into the project the file is converted into an RLE compressed bitmap.
From the CODESYS version 2.3.9.24 an additional dialogue opens when an image is integrated.
Using this dialogue the file is adapted to the Colour palette used for the device. During the colour
conversion you can select between 'most similar colour' (deactivate [Dithering]) and 'Dithering'.
Drawing area:
The left upper corner marks the home position (0,0) of the virtual and physical drawing area.
Virtual drawing area = 2,560 x 1,536 pixels
(enlarges the physical drawing area)
Elements in the virtual drawing area are not calculated.
The left upper corner marks the home position (0,0) of the virtual and physical drawing area.
Virtual drawing area (X/Y coordinates) = -32768...+32767
(enlarges the physical drawing area)
All objects including their outer dimensions must be within the borders of the virtual drawing area
even after scaling or shifting!
Otherwise the visualisation will not be correct any more.
Elements in the virtual drawing area are not calculated.
>
Texts
The smallest font size which is clearly visible on the device is 11 point.
Permissible fonts:
- Arial (standard)
- Lucida Console
Permissible font size [Pixel] and font weight:
- Arial: 11 (standard), 16, 24, 32 (all only normal)
- Lucida Console: 16, 24, 48*) (all only normal)
*) Lucida Console in the font size 48 only has the following characters:
Rotate the element around a defined pivot point
Indicate the angle of rotation
angle of rotation in [degree]
positive value = rotation clockwise
negative value = rotation anticlockwise
Shift
Shifting of the element:
horizontal
vertical
only within the drawing area
max. until leaving the drawing area
Relative shifting of
• rectangle
• ellipse / circle
Each edge of the element can be shifted by a specified number of pixels via an
INT type variable:
basic position of the 4 edges = zero
new value shifts this edge by the specified value
Shift direction for value > 0:
horizontal edge down
vertical edge to the right
Shift direction for value < 0:
horizontal edge up
vertical edge to the left
Device
BasicController: CR040n, CR041n,
CR043n
BasicDisplay: CR045n
ioControl: CR205n
SmartController: CR253n
PDM360 NG: CR108n, CR120n
Criterion
max. FiFo transmit
- with FB CAN_TX...
- with FB CAN_TX_ENH...
4 messages
16 messages
4 messages
16 messages
max. FiFo receive
- with FB CAN_RX_..._FIFO
32 messages
32 messages
Movement of elements
Image and text elements can be moved on the display in a defined manner.
7392
>
Limitations for CAN in this device
17975
FIFO (First In, First Out) = Operating principle of the stack memory: The data packet that was
written into the stack memory first, will also be read first. Each identifier has such a buffer (queue).
Some Raw-CAN function elements enable transmitting and receiving of several messages in one PLC
cycle as the messages are temporarily stored in a FiFo:
- CAN_TX..., → Function elements: transmit RAW-CAN data
- CAN_RX_ENH_FIFO (→ p. 62)
- CAN_RX_RANGE_FIFO (→ p. 66)
The number of FIFo messages is limited. The following limitations of the devices are valid:
30
Loading...
+ 179 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.