95
1 ISOBUS in the ecomatmobile Controller CODESYS ® V2.3 English 7391086_02_UK 2017-06-14

ifm-Systemhandbuch ISOBUS im ifm-Controller

  • Upload
    others

  • View
    22

  • Download
    0

Embed Size (px)

Citation preview

Page 1: ifm-Systemhandbuch ISOBUS im ifm-Controller

1

ISOBUS in the ecomatmobile Controller

CODESYS® V2.3

English

7391

086

_02

_U

K 2

01

7-0

6-1

4

Page 2: ifm-Systemhandbuch ISOBUS im ifm-Controller

2

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Contents

Contents

1 About this manual 4

1.1 Copyright .............................................................................................................................. 4 1.2 Overview: documentation modules for CRnnnn .................................................................. 5 1.3 What devices are described in this manual? ....................................................................... 5 1.4 What do the symbols and formats mean? ........................................................................... 6 1.5 How is this documentation structured? ................................................................................ 7 1.6 History of the instructions (ISO) ......................................................................................... 7

2 Safety instructions 8

2.1 Please note .......................................................................................................................... 8 2.2 What previous knowledge is required? ................................................................................ 8

3 System requirements 9

3.1 Hardware .............................................................................................................................. 9 3.2 Software .............................................................................................................................10 3.3 Licensing ............................................................................................................................10

4 System description 11

4.1 Information about the device ..............................................................................................11 4.2 Hardware description .........................................................................................................12

4.2.1 Memory allocation for ISOBUS ................................................................................................... 12 4.3 Interface description ...........................................................................................................13

4.3.1 CAN: Interfaces and protocols .................................................................................................... 13 4.4 Software description ..........................................................................................................14

4.4.1 Software modules for ISOBUS ................................................................................................... 15

5 Configuration of the ISOBUS in the implement 19

5.1 Unpack files from ifm USB stick to the PC / laptop ............................................................19 5.1.1 Install the PerlScript interpreter .................................................................................................. 19 5.1.2 Unpack and install files ............................................................................................................... 19

5.2 Install ISOBUS stack in the controller ................................................................................20 5.2.1 Install ISOBUS stack in the controller via the ifm downloader .................................................... 21

5.3 ISOBUS mask editor ..........................................................................................................22 5.3.1 Recommendation ....................................................................................................................... 22 5.3.2 Notes .......................................................................................................................................... 22 5.3.3 Example: Mask generator........................................................................................................... 23 5.3.4 Complete the project .................................................................................................................. 32

5.4 ifm_ISOBUS-Wizard ..........................................................................................................33 5.4.1 Convert mask objects for the CODESYS program ..................................................................... 33

5.5 Create a CODESYS project ...............................................................................................36 5.5.1 Create a project from a template ................................................................................................ 36

5.6 Adjust and transmit a CODESYS project ...........................................................................44

6 Functional elements from ifm for ISOBUS 45

6.1 ifm library for ISOBUS ........................................................................................................45 6.1.1 ifm library ifm_ISOBUS_UTAux_Vxxyyzz.lib .............................................................................. 46

6.2 Functional elements from ifm: ISOBUS function blocks CODESYS interface...................47 6.2.1 ISOBUS function blocks: Initialisation of the signal table ........................................................... 47 6.2.2 ISOBUS function blocks: Initialisation of the object pool ............................................................ 49 6.2.3 ISOBUS function blocks: Basic functions ................................................................................... 53 6.2.4 ISOBUS function blocks: Data exchange regarding the universal terminal (VT) ........................ 57

Page 3: ifm-Systemhandbuch ISOBUS im ifm-Controller

3

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Contents

6.2.5 ISOBUS function blocks: Data exchange regarding the implement (WS)................................... 63

7 Glossary of Terms 86

8 Index 89

9 Notizen • Notes • Notes 91

10 ifm weltweit • ifm worldwide • ifm à l’échelle internationale 95

Page 4: ifm-Systemhandbuch ISOBUS im ifm-Controller

4

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

About this manual Copyright

1 About this manual

Copyright ............................................................................................................................................... 4 Overview: documentation modules for CRnnnn .................................................................................... 5 What devices are described in this manual? ......................................................................................... 5 What do the symbols and formats mean? ............................................................................................. 6 How is this documentation structured? ................................................................................................. 7 History of the instructions (ISO) .......................................................................................................... 7

202

>

1.1 Copyright 6088

© All rights reserved by ifm electronic gmbh. No part of this manual may be reproduced and used without the consent of ifm electronic gmbh.

All product names, pictures, companies or other brands used on our pages are the property of the respective rights owners: • AS-i is the property of the AS-International Association, (→ www.as-interface.net) • CAN is the property of the CiA (CAN in Automation e.V.), Germany (→ www.can-cia.org) • CODESYS™ is the property of the 3S – Smart Software Solutions GmbH, Germany (→ www.codesys.com) • DeviceNet™ is the property of the ODVA™ (Open DeviceNet Vendor Association), USA (→ www.odva.org) • EtherNet/IP® is the property of the →ODVA™ • EtherCAT® is a registered trade mark and patented technology, licensed by Beckhoff Automation GmbH, Germany • IO-Link® (→ www.io-link.com) is the property of the →PROFIBUS Nutzerorganisation e.V., Germany • ISOBUS is the property of the AEF – Agricultural Industry Electronics Foundation e.V., Deutschland (→ www.aef-online.org) • Microsoft® is the property of the Microsoft Corporation, USA (→ www.microsoft.com) • PROFIBUS® is the property of the PROFIBUS Nutzerorganisation e.V., Germany (→ www.profibus.com) • PROFINET® is the property of the →PROFIBUS Nutzerorganisation e.V., Germany • Windows® is the property of the →Microsoft Corporation, USA

Page 5: ifm-Systemhandbuch ISOBUS im ifm-Controller

5

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

About this manual Overview: documentation modules for CRnnnn

>

1.2 Overview: documentation modules for CRnnnn 23791 22853

The documentation for this devices consists of the following modules: (Downloads from ifm's website → ifm weltweit • ifm worldwide • ifm à l’échelle internationale (→ p. 95) )

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

System manual "The ISOBUS in the ifm controller"

Description of the configuration and the functions of the ISOBUS software in the device

>

1.3 What devices are described in this manual? 21052

Technology and methods can differ from device to device.

These instructions apply to the following devices (prepared for ISOBUS):

ISOBUS device Basic device CODESYS programming as

ClassicController CR0053 CR0033 CR0033

ClassicController CR0063 (prepared)

CR0033 CR0033

ExtendedController CR0153 = CR0053 + integrated I/O module

CR0133 = CR0033 + integrated I/O module

CR0033

ExtendedController CR0163 = CR0063 + integrated I/O module

(prepared)

CR0133 = CR0033 + integrated I/O module

CR0033

ExtendedController CR0253 CR0235 CR0235

ExtendedController CR0263 (prepared)

CR0235 CR0235

Page 6: ifm-Systemhandbuch ISOBUS im ifm-Controller

6

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

About this manual What do the symbols and formats mean?

>

1.4 What do the symbols and formats mean? 203

The following symbols or pictograms illustrate the notes in our instructions:

WARNING

Death or serious irreversible injuries may result.

CAUTION

Slight reversible injuries may result.

NOTICE

Property damage is to be expected or may result.

Important note Non-compliance can result in malfunction or interference

Information Supplementary note

► ... Request for action

> ... Reaction, result

→ ... "see"

abc Cross-reference

123 0x123 0b010

Decimal number Hexadecimal number Binary number

[...] Designation of pushbuttons, buttons or indications

Page 7: ifm-Systemhandbuch ISOBUS im ifm-Controller

7

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

About this manual How is this documentation structured?

>

1.5 How is this documentation structured? 204

1508

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 → ifm weltweit • ifm worldwide • ifm à l’échelle internationale (→ p. 95)

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: → ifm weltweit • ifm worldwide • ifm à l’échelle internationale (→ p. 95)

>

1.6 History of the instructions (ISO) 21053

What has been changed in this manual? An overview:

Date Theme Change

2017-02-16 new document --

2017-06-12 updated • easy installation • graphic software modules • Maintenance Tool

>

Page 8: ifm-Systemhandbuch ISOBUS im ifm-Controller

8

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Safety instructions Please note

2 Safety instructions

Please note ............................................................................................................................................ 8 What previous knowledge is required? ................................................................................................. 8

213 >

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!

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 → ifm weltweit • ifm worldwide • ifm à l’échelle internationale (→ p. 95)

>

2.2 What previous knowledge is required? 21055

The following applies in addition to the indications in the corresponding chapter of the basic device:

The following previous knowledge is required for the configuration and programming of the ISOBUS surface: • knowledge of the ISOBUS technology to ISO 11783 • good command of an ISOBUS mask generator software, e.g. ISO-Designer

>

Page 9: ifm-Systemhandbuch ISOBUS im ifm-Controller

9

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

System requirements Hardware

3 System requirements

Hardware ............................................................................................................................................... 9 Software .............................................................................................................................................. 10 Licensing ............................................................................................................................................. 10

16903 >

3.1 Hardware 21058

Device of the R360 controller product family with preinstalled ISOBUS:

ISOBUS device Hardware version as of ... ifm runtime system as of version ...

ClassicController CR0053 AA CR0033 V020002

ClassicController CR0063 = CR0053 + software "TaskController"

(in preparation) CR0033 V020002

ExtendedController CR0153 = CR0053 + integrated I/O module

AA CR0033 V020002

ExtendedController CR0163 = CR0063 + integrated I/O module

(in preparation) CR0033 V020002

ExtendedController CR0253 AA CR0235 V010001

ExtendedController CR0263 = CR0253 + software "TaskController"

(in preparation) CR0235 V010001

PC or laptop for CODESYS programming system (→ system requirements CODESYS Development System V2.3)

Ethernet connection between CODESYS PC/laptop and Ethernet interface of the controller (→ installation instructions)

Page 10: ifm-Systemhandbuch ISOBUS im ifm-Controller

10

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

System requirements Software

>

3.2 Software 21059

The following software is required for the ISOBUS surface:

Software Description

CP9200 R360/SysStart/VT Client

ifm System-Startup Virtual Terminal Client

Module for using the ifm ISOBUS stack and the wizard

Required once per ifm customer

Can be purchased separately fromifm

Contains e.g.: • ifm system manual • CODESYS library • CODESYS demo programs and templates • ifm ISOBUS stack • ifm ISOBUS wizard

CP9201 R360/SysStart/TC Client (in preparation)

ifm System-Startup TaskController Client (in preparation)

Module for using the ifm ISOBUS stack and the wizard

Required once per ifm customer Only if the following devices are used: CR0063, CR0163, CR0263

Can be purchased separately fromifm

ISOBUS mask generator for the operating masks on the virtual terminal (VT)

Editor program, e.g.: • ISO-Designer (Jetter) • Mask Generator (WTK Elektronik) • VT Designer (OSB AG)

Required once per editor workstation

Can be purchased separately or is available as freeware

ifm_ISOBUS-Stack To be installed as C library in the ifm controller → chapter Install ISOBUS stack in the controller (→ p. 20) Is also part of CP9200 and CP9201

The features and functions warranted in this manual can only be obtained by using the software components in the versions stated here.

On its website ifm electronic provides the software components for download: → ifm weltweit • ifm worldwide • ifm à l’échelle internationale (→ p. 95)

>

3.3 Licensing 21060

Software Licence

b-ISOBUS-Stack ISOBUS library integrated in the device

The license fee is covered by the purchase of a CR0n53 or CR0n63 ISOBUS controller.

CP9200 R360/SysStart/VT Client

System-Startup Virtual Terminal Client The licence has to be purchased once by each ifm customer.

CP9201 R360/SysStart/TC Client

System-Startup TaskController Client (in preparation)

The licence has to be purchased once by each ifm customer. Only if the following devices are used: CR0063, CR0163, CR0263

>

Page 11: ifm-Systemhandbuch ISOBUS im ifm-Controller

11

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

System description Information about the device

4 System description

Information about the device ............................................................................................................... 11 Hardware description........................................................................................................................... 12 Interface description ............................................................................................................................ 13 Software description ............................................................................................................................ 14

975 >

4.1 Information about the device 21062

ISOBUS device Hardware features (= basic device)

ISOBUS features

ClassicController CR0053 CR0033 • standard side: 16 inputs, 16 outputs

• Virtual Terminal Client (VT client) • Auxiliary Control (AUX-N)

ClassicController CR0063 (in preparation)

CR0033 • standard side: 16 inputs, 16 outputs

• Virtual Terminal Client (VT client) • Task Controller Client (TC client) • Auxiliary Control (AUX-N)

ExtendedController CR0153 = CR0053 + integrated I/O module

CR0133 = CR0033 + integrated I/O module • standard side: 16 inputs, 16 outputs • extended side: 16 inputs, 16 outputs

• Virtual Terminal Client (VT client) • Auxiliary Control (AUX-N)

ExtendedController CR0163 = CR0063 + integrated I/O module (in preparation)

CR0133 = CR0033 + integrated I/O module • standard side: 16 inputs, 16 outputs • extended side: 16 inputs, 16 outputs

• Virtual Terminal Client (VT client) • Task Controller Client (TC client) • Auxiliary Control (AUX-N)

ExtendedController CR0253 CR0235 • standard side: 16 inputs, 16 outputs • extended side: 24 inputs, 24 outputs

• Virtual Terminal Client (VT client) • Auxiliary Control (AUX-N)

ExtendedController CR0263 (in preparation)

CR0235 • standard side: 16 inputs, 16 outputs • extended side: 24 inputs, 24 outputs

• Virtual Terminal Client (VT client) • Task Controller Client (TC client) • Auxiliary Control (AUX-N)

Details to the hardware features of the basic device → Programming Manual of the basic device

Page 12: ifm-Systemhandbuch ISOBUS im ifm-Controller

12

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

System description Hardware description

>

4.2 Hardware description

Memory allocation for ISOBUS ........................................................................................................... 12 14081

>

4.2.1 Memory allocation for ISOBUS 21065

Standard memory allocation → programming manual of the basic device → chapter Available memory

>

FLASH memory 21066

FLASH memory (non-volatile, slow memory) overall existing in the device

2 176 kBytes

Thereof the following memory areas are reserved for ...

ISOBUS 128...512 kBytes

>

SRAM 21067

SRAM (volatile, fast memory) overall existing in the device SRAM indicates here all kinds of volatile and fast memories.

2 216 kBytes

Thereof the following memory areas are reserved for ...

ISOBUS 12 kBytes

Page 13: ifm-Systemhandbuch ISOBUS im ifm-Controller

13

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

System description Interface description

>

4.3 Interface description

CAN: Interfaces and protocols ............................................................................................................ 13 14098

>

4.3.1 CAN: Interfaces and protocols 21069

The following CAN interfaces and CAN protocols are available in this ecomatmobile device:

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 CAN Layer 2 CAN Layer 2

ISOBUS CANopen CANopen CANopen

SAEJ1939 SAEJ1939 SAEJ1939

Standard baud rate 125 Kbits/s 125 Kbits/s 125 Kbits/s 250 Kbit/s

CAN4 operates with a 29 bits ID.

Page 14: ifm-Systemhandbuch ISOBUS im ifm-Controller

14

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

System description Software description

>

4.4 Software description

Software modules for ISOBUS ............................................................................................................ 15 21097

Page 15: ifm-Systemhandbuch ISOBUS im ifm-Controller

15

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

System description Software description

>

4.4.1 Software modules for ISOBUS

ISOBUS concept ................................................................................................................................. 16 Overview .............................................................................................................................................. 17 Object pool mask generator ................................................................................................................ 17 ifm_ISOBUS-Wizard ............................................................................................................................ 17 Objekt-Pool / AutoCode ....................................................................................................................... 18 ifm ISOBUS stack ................................................................................................................................ 18

21101

Graphics: Software modules for ISOBUS

Page 16: ifm-Systemhandbuch ISOBUS im ifm-Controller

16

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

System description Software description

>

ISOBUS concept 21104

The ISOBUS concept is based on the following idea:

A universal terminal (VT) is installed in an agricultural machine (e.g. tractor).

From this universal terminal all main functions of the agricultural machine can be controlled and monitored via ISOBUS.

Different implements (WS) can be connected to the agricultural machine mechanically and electrically.

These implements have an independent controller that exchanges data and commands with the universal terminal on the agricultural machine via ISOBUS.

When the implement (WS) is connected to the universal terminal (VT), the following happens:

The VT automatically accesses the WS and saves the operating graphics and the data of the implement stored there in its own memory.

On demand, the VT indicates these graphics and this data.

Now the coupled implements can be controlled and monitored from the universal terminal.

Page 17: ifm-Systemhandbuch ISOBUS im ifm-Controller

17

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

System description Software description

>

Overview 21103

The ISOBUS concept provides for the following software modules:

Module Description Location

Object pool mask generator creates graphics and data that are to appear on the universal terminal (VT)

PC / laptop

ifm_ISOBUS-Wizard converts the files of the mask generator so that they can be loaded into the controller memory as a C code

PC / laptop

Objekt-Pool / AutoCode Graphics and data the universal terminal (VT) fetches from the ifm controller when the two are coupled and then displays

ifm controller: C code memory

ifm_ISOBUS-Stack Libraries with the following modules: • Virtual Terminal Client • Aux Control • Task Controller Client

ifm controller: C code memory

ISOBUS-CODESYS.lib Library links the ISOBUS stack to the application program ifm controller: memory for the application code

CODESYS application program Program for moving and monitoring the implement ifm controller: memory for the application code (created on the PC / laptop)

>

Object pool mask generator 21105

This program is used to create the graphics and the data that are to appear on the universal terminal.

The program operates on the programming station (PC / laptop).

The program is available in different versions / with different convenience levels / at different prices from various vendors.

Among others, the program creates the following files: *.iop

*.iop.h

These file types are according to the ISOBUS standard.

Configuration→ chapter ISOBUS mask generator (→ p. 22)

>

ifm_ISOBUS-Wizard 21106

The program is part of the ifm ISOBUS licence.

The program operates on the programming station (PC / laptop).

The program converts the .IOP files of the mask generator into a common .EXP file so that they

can be loaded into the controller memory as a C code.

Page 18: ifm-Systemhandbuch ISOBUS im ifm-Controller

18

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

System description Software description

>

Objekt-Pool / AutoCode 21108

The graphics and data created via the mask generator as stored in the C code memory of the ifm controller of the agricultural implement.

The universal terminal (Virtual Terminal, VT) on the agricultural machine (e.g. tractor) detects the following: • a new implement (working set, WS) has been connected OR: • there is a new version of the object pool of the coupled implement (WS)

The universal terminal automatically fetches the graphics and data from the object pool. If this version of the object pool has already been saved in the universal terminal, the graphics are not transferred.

The universal terminal indicates the graphics and the data of the implement on its display.

The implement can be controlled and monitored from the universal terminal.

>

ifm ISOBUS stack 21109

The ifmISOBUS stack is a collection of functions.

The ifmISOBUS stack is stored in the C code memory of the ifmISOBUS controller of the implement. → chapter Install ISOBUS stack in the controller (→ p. 20)

The functions in the ifm ISOBUS stack can be used in the following CODESYS library: • ifm_ISOBUS_UTAux_Vxxyyzz.lib

The ifm ISOBUS stack consists of the following modules: • Virtual Terminal Client • Aux Control • Task Controller Client (in preparation)

>

Page 19: ifm-Systemhandbuch ISOBUS im ifm-Controller

19

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement Unpack files from ifm USB stick to the PC / laptop

5 Configuration of the ISOBUS in the implement

Unpack files from ifm USB stick to the PC / laptop ............................................................................. 19 Install ISOBUS stack in the controller ................................................................................................. 20 ISOBUS mask editor ........................................................................................................................... 22 ifm_ISOBUS-Wizard ............................................................................................................................ 33 Create a CODESYS project ................................................................................................................ 36 Adjust and transmit a CODESYS project ............................................................................................ 44

21772

>

5.1 Unpack files from ifm USB stick to the PC / laptop 22971

ifm supplies the required ISOBUS files on a USB stick (CP9200, CP9201).

>

5.1.1 Install the PerlScript interpreter 22972

A PerlScript interpreter must be installed before the installation of the ISOBUS wizard.

e.g. ActivePerl: www.activestate.com/activeperl/downloads

► Install the current PerlScript interpreter. To do this, no administrator rights are required.

>

5.1.2 Unpack and install files 22973

► Double-click on the file ifm_ISOBUS_Vx.y.z.exe.

No administrator rights are required.

► Confirm or change suggested directories (as required).

> Program signals "All operations completed".

> The following files are installed:

Files Installation path (normal)

ISOBUS wizard %PROGRAMFILES(x86)%\ifm electronic\ISOBUS Wizard

ISOBUS stack CODESYS libraries

%PROGRAMFILES(x86)%\ifm electronic\CoDeSys V2.3\Targets\ifm\Library\ifm_ISOBUS

CODESYS templates %PROGRAMFILES(x86)%\ifm electronic\CoDeSys V2.3\Projects\TEMPLATE_ISOBUS

CODESYS demo programs %PROGRAMFILES(x86)%\ifm electronic\CoDeSys V2.3\Projects\DEMO_ISOBUS

Page 20: ifm-Systemhandbuch ISOBUS im ifm-Controller

20

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement Install ISOBUS stack in the controller

>

5.2 Install ISOBUS stack in the controller 22643

ifm delivers all controllers without runtime system.

► Use the ifm MaintenanceTool to install the files.

► Install the runtime system → programming manual of the controller

► Transmit the ISOBUS stack into the flash memory EXT2 of the device: Source = CP9200 USB stick > [Software] > [ifm_ISOBUS-Stack] File = ifm_ISOBUS_Stack_Vxxyyzz.h86

Each ISOBUS controller contains a permanently saved ISOBUS licence key. The ISOBUS stack cannot be used on the device without this key.

Page 21: ifm-Systemhandbuch ISOBUS im ifm-Controller

21

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement Install ISOBUS stack in the controller

>

5.2.1 Install ISOBUS stack in the controller via the ifm downloader 22952

A small batch file is ideal for use with the ifm downloader:

Create a batch file with a Windows Editor: Execute_Download_C_Code_Part.bat

Enter the following text in this file: Download_Directory\download.exe /debug /cfifm_ISOBUS_Stack_Vxxyyzz.txt The following applies:

Download_Directory = directory name, contains e.g. the following files:

the downloader program the batch configuration file ifm_ISOBUS_Stack_Vxxyyzz.txt

/cf = command copy file

ifm_ISOBUS_Stack_Vxxyyzz.txt = file containing the details for the batch file

This file has to be stored in the same directory as the downloader program! Vxxyyzz = version of the ISOBUS stack file

Create a text file with a Windows Editor in the directory Download_Directory:

ifm_ISOBUS_Stack_Vxxyyzz.txt

This is the batch configuration file.

Enter the following text in this file: rs232 com4

baudrate115200 nocrc

stop

lzsversion3 baseapplc=HA0100000

applcsize=H80000 f..\ifm_ISOBUS_Stack_Vxxyyzz.h86

download

run

The following applies: Line 1...6 define the parameters for the serial interface baseapplc = start address of the C file in the controller memory

applcsize = size of the C file in the controller memory

f..\ = location and file name of the C file (here: directory above the downloader program)

Page 22: ifm-Systemhandbuch ISOBUS im ifm-Controller

22

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement ISOBUS mask editor

>

5.3 ISOBUS mask editor

Recommendation ................................................................................................................................ 22 Notes ................................................................................................................................................... 22 Example: Mask generator ................................................................................................................... 23 Complete the project ........................................................................................................................... 32

22636

The ISOBUS mask editor has the following purpose:

Create graphics masks for display on the universal terminal (UT) on the tractor

Visualise signals of the implement (inputs/outputs, data) in the masks

Provide signals of the operating elements of the UT (softkeys) for the implement

Provide the labelling of the softkeys, data and messages • monolingual: in the basic IOP file • any further language: in further IOP files

The mask editor finishes by creating the file Projekt.IOP.

This basic IOP file contains the language defined as "Active Language" in the editor. If the mask has been created in several languages, the editor creates an individual IOP file for each additional language, e.g. Projekt_Sprache2.IOP, Projekt_Sprache3.IOP, etc.

Depending on the required user-friendliness there are different suppliers in the world market whose products have been accepted by the AEF (→ www.aef-online.org).

>

5.3.1 Recommendation 22629

ifm recommends to use the following basic settings in the mask editor:

project to ISO 11783-L3 (2004)

data mask size = 480 x 480 px

softkey size = 72 x 72 px

physical softkeys = max. 10

virtual softkeys (per mask) = max. 10

only use web-safe colours

Background: This corresponds to the possibilities of most common universal terminals on the market, you may call it their common denominator.

>

5.3.2 Notes 22637

The project should be named correctly from the beginning. In many cases, it is not possible to change the name at a later point.

Input / output numerical values are of the type DWORD (UNIT32); adapt other values by means of offset and scaling!

An entered variable replaces the effect of the object ID of the actual element.

Graphic element: encoding as RunLength minimises the data volume.

Page 23: ifm-Systemhandbuch ISOBUS im ifm-Controller

23

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement ISOBUS mask editor

>

5.3.3 Example: Mask generator

Create working area and project. ........................................................................................................ 23 Define display properties ..................................................................................................................... 23 Define project properties ..................................................................................................................... 24 Create masks and objects ................................................................................................................... 27

22711

The process may differ from program to program.

► Familiarise yourself with the selected mask generator before starting to work.

This example is based on Jetter's ISO-Designer.

>

Create working area and project. 22712

► Create working area "Workspace". Define name and memory location.

The working area contains all projects that have been created in it and all project files.

► Add a project to the working area. Set the following parameters: • platform (recommended: ISO 11 783-6 L3 (2004))

• display size (recommended: 480 x 480 px) • display name

• project name ( it might not be possible to change this name at a later point!) • memory location

► Then click [OK] to finish the process.

>

Define display properties 22713

Set the standard properties of the universal terminal (VT).

► Activate the tab [Hardware]. Alternatively: Menu bar [View] > [Hardware]

► Adapt the settings as needed in the window [Properties].

We recommend the following settings:

Parameter Setting

Number of visible keys max. 10

Softkey Width 72 px

Softkey Heigth 72 px

Display Width 640 px

Display Heigth 480 px

Datamask Width 480 px

Datamask Heigth 480 px

Default Background Color RGB (204,204,204)

Color depth 8 Bit / 256 Colors

Font Types ISO Latin 1

► Set the other parameters as needed.

> The program immediately reacts to every single setting.

► Finish the settings by clicking on the tab [Workspace].

Page 24: ifm-Systemhandbuch ISOBUS im ifm-Controller

24

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement ISOBUS mask editor

>

Define project properties 22714

► Open the context menu with right-click on project name in the window [Workspace].

► Open the properties dialogue via [Properties].

> 3 parameter groups appear in the new window: • General • Deployment • Object Templates

>

General project information 22715

The parameter group [General] shows general project information. Example:

[Location] shows the memory location of the project files. 22721

This memory location of the project files remains unchanged. It is not influenced by the indications in the parameter group [Deployment].

Page 25: ifm-Systemhandbuch ISOBUS im ifm-Controller

25

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement ISOBUS mask editor

>

Deployment options of the project 22716

The parameter group [Deployment] shows the deployment options of the project. Example:

The parameters have the following functions:

Parameter Function

Deploy Target Target platform for sending / saving the project files

Path Memory location for the exchange of the project files

Automatic Deployment Checkbox = active: The project is automatically sent to the operating panel after a build

Languages The languages to be transmitted in a deploy process can be selected via a dialogue. The dialogue is opened via the browse button.

22721

This memory location of the project files remains unchanged. It is not influenced by the indications in the parameter group [Deployment].

Page 26: ifm-Systemhandbuch ISOBUS im ifm-Controller

26

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement ISOBUS mask editor

>

Object templates 22717

The parameter group [Object Templates] shows the object templates available for the project. Example:

New masks or objects are created based on these templates. Each template consists of 3 parameters:

Parameter Description Note

Type Type or designation of the template cannot be changed

Start ID Each template type can assign up to 1000 IDs. There is only one WorkingSet in each project.

Example of type "SoftKeyMask": Start ID = 4000 possible IDs = 4000...4999

Name Format

Convention for the complete parameter name Structure: "Type" + "_" + "ID" The program saves each mask and each object under the resulting name

Example of type "SoftKeyMask": ID = 4001 Name Format = SoftKeyMask_4001 Datei = SoftKeyMask_4001.jvi

Page 27: ifm-Systemhandbuch ISOBUS im ifm-Controller

27

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement ISOBUS mask editor

>

Create masks and objects 22723

► Define the WorkingSet. This symbol image appears on the universal terminal (VT) on the tractor when the corresponding machine is not active.

► Create a start mask. This is the first image to appear on the universal terminal (VT) on the tractor when the corresponding machine is activated.

► Create required objects and place them on the mask.

► If required, create further masks.

► Set the conditions under which these masks are to appear.

► Create required objects for these masks and place them there.

ISOBUS offers 4 different masks:

Type 0 AlarmMask

An alarm mask (AlarmMask) serves to indicate an alarm.

An alarm mask cannot contain input fields. You can however assign a SoftKeyMask (keyboard) to an alarm mask which serves e.g. for the acknowledgement of an alarm.

Type 1 DataMask

The data mask can contain any objects except masks.

A data mask can also initiate events and corresponding macros. You can also assign a SoftKeyMask (keyboard) to a data mask.

Type 2 SoftKeyMask A SoftKeyMask is a mask for softkeys (keyboard) that is indicated at the edge of the terminal.

Type 3 WorkingSet

A WorkingSet object exists only once in a project.

Only certain objects can be created on the corresponding WorkingSet mask. Via the WorkingSet mask, the user can open the corresponding visualisation on the terminal.

>

WorkingSet-Maske 22724

A WorkingSet object exists only once in a project.

The WorkingSet object appears on the universal terminal (VT) as soon as the corresponding implement is linked to the tractor ISOBUS.

Via the WorkingSet mask, the user can open the corresponding visualisation on the universal terminal (VT).

The program automatically creates a WorkingSet mask when a new project is created.

Only certain objects can be created on the corresponding WorkingSet mask.

It makes sense to create an OutputString. The text should sufficiently describe the corresponding implement.

Page 28: ifm-Systemhandbuch ISOBUS im ifm-Controller

28

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement ISOBUS mask editor

>

Example: WorkingSet 22725

This symbol image is to appear on the universal terminal of the tractor as soon as the corresponding implement has been connected to the ISOBUS of the tractor.

WorkingSet: values in the properties window

OutputString in the WorkingSet: values in the properties window

WorkingSet: the summary in the working area

Page 29: ifm-Systemhandbuch ISOBUS im ifm-Controller

29

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement ISOBUS mask editor

>

Data mask 22730

The data mask appears on the universal terminal (VT) on the tractor (on request).

The data mask can contain any objects except masks.

A data mask can also initiate events and corresponding macros. You can also assign a SoftKeyMask (keyboard) to a data mask.

The data mask has the following functions:

give a graphic representation of the implement

display values and states

Further functions are possible by means of assigned SoftKeyMasks:

keys for changing the values or states

keys for changing to another data mask

>

Example: data mask 22731

As an example the data mask for a slurry tank car is shown.

Functions: • indicate the tank level • start / stop the pump via the pair of keys • only indicate the spray jet when the pump is running • individual setting of the spray quantity in [litres per minute].

The graphic on the mask represents a slurry tank car.

The graphic consists of the groups tank car and spray jet (framed by a dotted line).

A bar graph indicates the tank level on the tank car.

Below the input field to define the spray quantity.

Page 30: ifm-Systemhandbuch ISOBUS im ifm-Controller

30

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement ISOBUS mask editor

Bar graph for level indication: Properties

Input object for setting the spray quantity in [litres/minute]: Properties

Page 31: ifm-Systemhandbuch ISOBUS im ifm-Controller

31

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement ISOBUS mask editor

Macro for evaluation of the softkeys

Summary of the elements for the slurry tank car, view in the working area

Details on the procedure and parameter setting → Description of the used software

Page 32: ifm-Systemhandbuch ISOBUS im ifm-Controller

32

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement ISOBUS mask editor

>

5.3.4 Complete the project 22737

If all required elements have been created and configured, and / or if the current status is to be tested: complete the project.

To do so:

► In the menu [Build] > [Projekt 'Name']

> The program checks all elements of the project 'Name' integrated in the mask generator.

If the program finds all parameter settings to be correct:

> The program creates a number of files in the directory Projektname\Output. (iop = ISOBUS Output)

► Then select the IOP project file (here:MyProject1.iop) for further processing in the ifm_ISOBUS-

Wizard.

> The wizard searches all IOP files belonging to the project in the directory and converts them into an export file that can be processed by CODESYS.

Page 33: ifm-Systemhandbuch ISOBUS im ifm-Controller

33

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement ifm_ISOBUS-Wizard

>

5.4 ifm_ISOBUS-Wizard

Convert mask objects for the CODESYS program ............................................................................. 33 22639 21106

The program is part of the ifm ISOBUS licence.

The program operates on the programming station (PC / laptop).

The program converts the .IOP files of the mask generator into a common .EXP file so that they

can be loaded into the controller memory as a C code.

> >

5.4.1 Convert mask objects for the CODESYS program 22641

The ifm_ISOBUS-Wizard offers 2 possibilities to convert the mask objects. Goal:

the CODESYS program is to be able to evaluate signals and values of the mask objects

the CODESYS program is to be able to send signals and values to mask objects.

The following 2 possibilities exist:

Signal table → Method: wizard for signal table (→ p. 34) : As opposed to the →object pool the signal table contains only the objects the project planner has selected for the CODESYS project in the ifm_Wizard. Advantage: Access to all configured elements possible. Disadvantage: All elements are shown in the CODESYS program (→ confusing).

Object pool → Method: wizard for object pool (→ p. 35) : Compilation of all objects and data in the controller of the implement. The object pool is automatically transmitted into the universal terminal (on the tractor). Afterwards, the implement can be controlled and monitored from the universal terminal. Advantage: only the selected elements appear in the CODESYS program. Disadvantage: the required elements must be grouped together before compilation.

Prerequisite: The mask generator has successfully created the following files: • ProjektName.iop

• ProjektName_Language2.iop (for 2 or more configured display languages)

• ProjektName_Language3.iop (for 3 or more configured display languages)

etc.

Page 34: ifm-Systemhandbuch ISOBUS im ifm-Controller

34

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement ifm_ISOBUS-Wizard

>

Method: wizard for signal table 22749

Create the signal table:

► Select the file ProjektName.IOP created by

the mask generator (here:MyProject1.iop) by

clicking on [IOP-File] in the file manager window .

► Define the file name and the directory for the signal table to be created by clicking on [ST_EXP-File].

► Load the data from the project into the wizard via [Load].

> The feedback shown on the left appears.

► Mark all objects in the signal table (by clicking on them) that are to be evaluated or influenced in the CODESYS program. (Cancel selection: click on the element again)

► Optional: Define the file name and the memory location for the selection list to be created by clicking on [Selection-File]. The object selection will be immediately available for the next conversion.

► You can do the following via [Save & Build]:

save the project in the wizard directory

(optional: create and save the selection list)

export the signal table to adopt it in the CODESYS program

Page 35: ifm-Systemhandbuch ISOBUS im ifm-Controller

35

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement ifm_ISOBUS-Wizard

MyProject1.biwprj

Project file in the wizard

SelectionMyProject1.biwsel

File with object selection list in the wizard

SignalTable.exp Export file for adopting the signal table in the CODESYS program

> The files created by the wizard in the indicated target directory

>

Method: wizard for object pool 22750

Create the object pool:

► Select the file ProjektName.IOP created by

the mask generator by clicking on [IOP-File] in the file manager window (here: MyProject1.iop).

► Define the file name and the directory of the signal table to be created that is to be imported in CODESYS by clicking on [OP_EXP-File].

► [IOP-Language] = the language set as "active language" in the mask generator

► [Default-Language] = preset language in the CODESYS object pool

► Create the export file containing the object pool in the indicated target directory by clicking on [Start Convert].

ObjectPool.exp

File for importing the object pool into the CODESYS program

> The file created by the wizard in the indicated target directory

Page 36: ifm-Systemhandbuch ISOBUS im ifm-Controller

36

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement Create a CODESYS project

>

5.5 Create a CODESYS project

Create a project from a template ......................................................................................................... 36 22644

The graphic for the universal terminal has been finished by means of the mask generator (→ previous chapter). The next step is the PLC program on the implement.

we recommend the following procedure:

>

>

5.5.1 Create a project from a template

Method: CODESYS with signal table .................................................................................................. 37 Method: CODESYS with object pool ................................................................................................... 40

22634

Create the CODESYS project:

► Start the requested template file by double-click directory → chapter Unpack and install files (→ p. 19)

> CODESYS opens a new project from the selected template.

The further procedure depends on the selected method of the ISOBUS signal evaluation.

Page 37: ifm-Systemhandbuch ISOBUS im ifm-Controller

37

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement Create a CODESYS project

>

Method: CODESYS with signal table

View [Bausteine] .................................................................................................................................. 37 View [Datentypen] ............................................................................................................................... 37 View [Globale Variablen] ..................................................................................................................... 39

22754

Import the export file generated via the ifm_ISOBUS-Wizard into the CODESYS project:

► Integrate the .EXP file of the signal table into the CODESYS project in CODESYS via [Projekt] >

[Importieren...]. Source = e.g. C:\PROGRAM FILES (X86)\IFM ELECTRONIC\IFM_ISOBUS-WIZARD\PROJECTNAME\SIGNALTABLE.EXP

> CODESYS integrates the signal table into the CODESYS project.

► Check the CODESYS project for the folder [ifm_ISOBUS-Wizard].

>

View [Bausteine] 22797

► Activate the tab [Bausteine] in the CODESYS project:

> The following programs appear:

ifm_ISOBUS_Signaltable (calls the following programs:)

ifm_ISOBUS_Signaltable_Init

ifm_ISOBUS_Signaltable_ReInit

► In the program PRG_ISOBUS_MAIN call the program ifm_ISOBUS_Signaltable that has been prepared there.

► Delete or uncomment the prepared program parts for the "method with object pool" in the program PRG_ISOBUS_MAIN.

>

View [Datentypen] 22768

The user can access the signals via the global variable "Objects".

> Access the object structure of the signal table via the CODESYS tab [Datentypen].

Page 38: ifm-Systemhandbuch ISOBUS im ifm-Controller

38

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement Create a CODESYS project

>

Object structure from the wizard 22981

The variable "Objects" consists of the structure "t_Signalstructure". You can find the structure "t_Signalstructure" under [ifm-ISOBUS-Wizard] > [Signaltable] > [Objectstructure] in the tab [Datentypen] (→ figure below).

> Signal structure:

(* Structure generated from "ifm-ISOBUS-Wizard" *)

TYPE t_Signalstructure : STRUCT Container : t_Container; DataMask : t_DataMask; InputNumber : t_InputNumber; NumberVariable : t_NumberVariable; END_STRUCT END_TYPE

"t_Signalstructure" now contains all signals selected by the user beforehand. These signals are grouped into object types in the form of further structures, e.g. t_NumberVariable or t_Container. These object type structures contain the individual objects for which signals have been selected. These individual objects in turn are also organised as structures.

All these structures can be found under [ifm-ISOBUS-Wizard] > [Signaltable] > [Objectstructure] in the tab [Datentypen]:

>

Object structure for the example settings used above 22980

> Via the CODESYS tab [Datentypen] you can access the object structure of the signal table which has the following entries (according to the example created earlier):

Representation of the slurry jet when the pump is running: t_ContainerJauche_3001 :

STRUCT ObjectID_3001 : WORD := 3001; Hidden : BOOL := 1; END_STRUCT

t_DataMask :

STRUCT DataMask_1001 : t_DataMask_1001; END_STRUCT

Page 39: ifm-Systemhandbuch ISOBUS im ifm-Controller

39

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement Create a CODESYS project

t_DataMask_1001 :

STRUCT ObjectID_1001 : WORD := 1001; Soft_Key_Mask : WORD := 65535; END_STRUCT

Representation of the tank level t_NumberVariableBargraph_21000 :

STRUCT ObjectID_21000 : WORD := 21000; Value : DWORD := 0; END_STRUCT

Setting of the pump performance t_NumberVariableLiterMinute_21001 :

STRUCT ObjectID_21001 : WORD := 21001; Value : DWORD := 0; END_STRUCT

The filtered signal table only contains such elements as would be required for programming the project in CODESYS.

The user can write or read all signals via the global structure variable "objects". The user simply uses the structure variable like a global variable. Example: Objects.Container.ContainerJauche_3001.Hidden := FALSE

The user does not have to worry about when and how often the value on the ISOBUS is transmitted.

>

View [Globale Variablen] 22769

► Activate the tab [Resourcen] in the CODESYS project:

> The following global variables appear:

VAR_GLOBAL Dataarray : ARRAY[0..6] OF t_Datastructure; Objects : t_Signalstructure; Arraysize : DWORD := 7; END_VAR

The array "Dataarray" consists of the structure "t_Datastructure" which can be found under [ifm-ISOBUS-Wizard] > [Signaltable] > [Datastructure] in the tab [Datentypen]. The array "Dataarray" is of no interest to the user. The data array is only required for the internal administration of the functionality "signal table".

Do not access or change the data in the "Dataarray" array!

The array is used in the following 3 programs: • ifm_ISOBUS_Signaltable • ifm_ISOBUS_Signaltable_Init • ifm_ISOBUS_Signaltable_ReInit

Page 40: ifm-Systemhandbuch ISOBUS im ifm-Controller

40

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement Create a CODESYS project

>

Method: CODESYS with object pool

View [Bausteine] .................................................................................................................................. 40 View [Datentypen] ............................................................................................................................... 41 View [Globale Variablen] ..................................................................................................................... 43

22755

Import the export file generated via the ifm_ISOBUS-Wizard into the CODESYS project:

► Integrate the .EXP file of the object pool into the CODESYS project in CODESYS via [Projekt] >

[Importieren...]. Source = e.g. C:\PROGRAM FILES (X86)\IFM ELECTRONIC\IFM_ISOBUS-WIZARD\PROJECTNAME\OBJECTPOOL.EXP

> CODESYS integrates the object pool into the CODESYS project.

► Check the CODESYS project for the folder [ifm_ISOBUS-Wizard].

>

View [Bausteine] 22771

► Activate the tab [Bausteine] in the CODESYS project:

> The following functions appear:

ifm_ISOBUS_ObjectPool_Init (configures the following object pool elements:)

App_DataMask_array

App_None_Array

App_SoftkeyMask_Array

Page 41: ifm-Systemhandbuch ISOBUS im ifm-Controller

41

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement Create a CODESYS project

>

View [Datentypen] 22772

> Via the CODESYS tab [Datentypen] you can access the object structure of the signal table from the object pool which has the following entries (according to the example created earlier):

t_Datastructure :

STRUCT Timer : BYTE; DataSize : BYTE; Command : BYTE; AttributeID : BYTE; DataAddress : DWORD; OldValue : DWORD; ObjectID : DWORD; END_STRUCT

t_Container :

STRUCT Container_3000 : t_Container_3000; END_STRUCT

t_Container_3000 :

STRUCT ObjectID_3000 : WORD := 3000; Hidden : BOOL := 0; END_STRUCT

t_InputNumber :

STRUCT InputNumber_9000 : t_InputNumber_9000; InputNumber_9001 : t_InputNumber_9001;

END_STRUCT

t_InputNumber_9000 :

STRUCT ObjectID_9000 : WORD := 9000; Enabled : BOOL := 1; END_STRUCT

t_InputNumber_9001 :

STRUCT ObjectID_9001 : WORD := 9001; Enabled : BOOL := 1; END_STRUC

t_InputString :

STRUCT InputString_8000 : t_InputString_8000; END_STRUCT

t_InputString_8000 :

STRUCT ObjectID_8000 : WORD := 8000; Enable : BOOL := 1; END_STRUCT

Page 42: ifm-Systemhandbuch ISOBUS im ifm-Controller

42

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement Create a CODESYS project

t_NumberVariable :

STRUCT NumberVariable_ChkBox : t_NumberVariable_ChkBox; NumberVariable_InGanzzahlig : t_NumberVariable_InGanzzahlig; NumberVariable_OutGanzzahlig : t_NumberVariable_OutGanzzahlig; NumberVariable_InFloat : t_NumberVariable_InFloat; NumberVariable_OutFloat : t_NumberVariable_OutFloat; END_STRUCT

t_NumberVariable_21000 :

STRUCT ObjectID_21000 : WORD := 21000;

Value : DWORD := 0; END_STRUCT

t_NumberVariable_ChkBox :

STRUCT ObjectID_21000 : WORD := 21000; Value : DWORD := 1; END_STRUCT

t_NumberVariable_InFloat :

STRUCT ObjectID_21003 : WORD := 21003; Value : DWORD := 0; END_STRUCT

t_NumberVariable_InGanzzahlig :

STRUCT ObjectID_21001 : WORD := 21001; Value : DWORD := 0; END_STRUCT

t_NumberVariable_OutFloat :

STRUCT ObjectID_21004 : WORD := 21004; Value : DWORD := 0; END_STRUC

t_NumberVariable_OutGanzzahlig :

STRUCT

ObjectID_21002 : WORD := 21002; Value : DWORD := 0; END_STRUCT

t_Rectangle :

STRUCT Rectangle_14000 : t_Rectangle_14000; END_STRUCT

t_Rectangle_14000 :

STRUCT ObjectID_14000 : WORD := 14000; Fill_Attributes : WORD := 25002; Height : WORD := 100; END_STRUCT

t_Signalstructure :

STRUCT Container : t_Container; InputNumber : t_InputNumber; NumberVariable : t_NumberVariable; Rectangle : t_Rectangle; END_STRUCT

ALL elements of the project are described in the object pool, not only those elements that would be required for the programming in CODESYS.

Page 43: ifm-Systemhandbuch ISOBUS im ifm-Controller

43

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement Create a CODESYS project

>

View [Globale Variablen] 22773

► Activate the tab [Resourcen] in the CODESYS project:

> The following global variables appear in the form of a big data array:

Example:

App_DataMask_array : ARRAY[0..400] OF BYTE := DataMask_1001

ContainerTankwagen_3000 ContainerJauche_3001

InputNumber_9000 OutputString_11000

Line_13000

Rectangle_14000 Rectangle_14001

Ellipse_15000 Ellipse_15001

Ellipse_15002

Polygon_16000 LinearBargraph_18000

LineAttributes_24000 LineAttributes_24001

LineAttributes_24002 FillAttributes_25000

FillAttributes_25001

FillAttributes_25002

App_None_array : ARRAY[0..47] OF BYTE :=

Macro_1 Macro_2

NumberVariableBargraph_21000 NumberVariableLiterMinute_21001

FontAttributes_23001

App_SoftKeyMask_array : ARRAY[0..77] OF BYTE := WorkingSet_0

SoftKeyMask_4000 SoftKeySprayOn_5000

SoftKeySprayOff_5001 OutputString_11001

Generated_Pointer_To_Null

Page 44: ifm-Systemhandbuch ISOBUS im ifm-Controller

44

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Configuration of the ISOBUS in the implement Adjust and transmit a CODESYS project

>

5.6 Adjust and transmit a CODESYS project 22740

► Create the application program in the CODESYS project.

► Edit the required ISOBUS parameters and data in the program.

► Connect the programming station to the controller.

► Export the CODESYS project to the controller.

>

Page 45: ifm-Systemhandbuch ISOBUS im ifm-Controller

45

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS ifm library for ISOBUS

6 Functional elements from ifm for ISOBUS

ifm library for ISOBUS ......................................................................................................................... 45 Functional elements from ifm: ISOBUS function blocks CODESYS interface .................................... 47

21071

All CODESYS function elements (FBs, PRGs, FUNs) are stored in libraries. Below you will find all ifm ISOBUS libraries you can use together with this device.

Below you will find a thematic overview of the function elements.

>

6.1 ifm library for ISOBUS

ifm library ifm_ISOBUS_UTAux_Vxxyyzz.lib ...................................................................................... 46 21074

Page 46: ifm-Systemhandbuch ISOBUS im ifm-Controller

46

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS ifm library for ISOBUS

>

6.1.1 ifm library ifm_ISOBUS_UTAux_Vxxyyzz.lib 22809

This ifm library contains the following function blocks:

Function element Short description

Config_ObjectPool (→ p. 50) FUN initialises the ISOBUS on the intended CAN interface

Config_ObjectPool_LanguagePart (→ p. 51) FUN configures a language-dependent element in the object pool

Config_ObjectPool_Part (→ p. 52) FUN configures a language-independent element in the object pool

ifm_ISOBUS (→ p. 54) FB initialisiert den ISOBUS auf der dafür vorgesehenen CAN-Schnittstelle

ifm_ISOBUS_5msTask (→ p. 56) FB bildet die Zeitreferenz für der ISOBUS-Stack

ifm_ISOBUS_SigTableInterface (→ p. 48) FUN Reads the address and the size of the signal table created by means of the ifm wizard

VT_ExtendedInfo (→ p. 61) FB receives extended information from the connected universal terminal (VT)

VT_LocalizationInfo (→ p. 59) FB receives local information from the connected universal terminal (VT)

VT_NextVT (→ p. 58) FUN disconnects the implement from the current universal terminal (VT) and connects it to the next available universal terminal

WS_CmdChangeActiveMask (→ p. 64) FUN changes from the active mask of the implement to a data or alarm mask in the universal terminal

WS_CmdChangeAttribute (→ p. 65) FUN changes the attribute of an object by means of an attribute ID (AID)

WS_CmdChangeFillAttributes (→ p. 66) FUN changes the fill attributes in a graphic element in the universal terminal

WS_CmdChangeFontAttributes (→ p. 67) FUN changes the character attributes in a character object in the universal terminal

WS_CmdChangeLineAttributes (→ p. 69) FUN changes the line attributes in a line object in the universal terminal

WS_CmdChangeListItem (→ p. 70) FUN changes a list element in an input list object in the universal terminal

WS_CmdChangeNumericValue (→ p. 71) FUN changes the numerical value in an object in the universal terminal

WS_CmdChangeSize (→ p. 72) FUN changes the size of an object in the universal terminal

WS_CmdChangeSoftKeyMask (→ p. 73) FUN changes the mask of the programmed buttons belonging to the implement (WS) in the universal terminal

WS_CmdChangeStringValue (→ p. 74) FUN changes the text in an object in the universal terminal

WS_CmdControlAudioSignal (→ p. 75) FUN controls the audio signal output in the universal terminal

WS_CmdEnableDisableObject (→ p. 76) FUN controls the accessibility of an input field in the universal terminal

WS_CmdHideShowObject (→ p. 77) FUN hides or shows a container object in the universal terminal

WS_CmdMoveObject (→ p. 78) FUN changes the position of an object in relation to the current position in the universal terminal

WS_CmdSetAudioVolume (→ p. 79) FUN controls the volume of the audio signal output in the universal terminal

WS_CmdSetObjectPosition (→ p. 80) FUN changes the position of an object in the universal terminal

WS_EvtButtonActivation (→ p. 82) FB indicates the status of a key on the universal terminal

WS_EvtSoftKeyActivation (→ p. 83) FB indicates the status of a button programmed on the universal terminal

WS_EvtVTChangeNumericValue (→ p. 84) FB indicates the new value of a numerical value of an object changed on the universal terminal

WS_EvtVTChangeStringValue (→ p. 85) FB indicates the new value of a text character value of an object changed on the universal terminal

Legend:

GV ... FB ... FUN ... PRG ...

Global variable Function block Function Program

Page 47: ifm-Systemhandbuch ISOBUS im ifm-Controller

47

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

6.2 Functional elements from ifm: ISOBUS function blocks CODESYS interface

ISOBUS function blocks: Initialisation of the signal table .................................................................... 47 ISOBUS function blocks: Initialisation of the object pool..................................................................... 49 ISOBUS function blocks: Basic functions ............................................................................................ 53 ISOBUS function blocks: Data exchange regarding the universal terminal (VT) ................................ 57 ISOBUS function blocks: Data exchange regarding the implement (WS) .......................................... 63

21081

Below you will find the description of the ISOBUS function elements • for the CODESYS interface • sorted by subject

>

6.2.1 ISOBUS function blocks: Initialisation of the signal table

ifm_ISOBUS_SigTableInterface .......................................................................................................... 48 22815

Page 48: ifm-Systemhandbuch ISOBUS im ifm-Controller

48

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

ifm_ISOBUS_SigTableInterface 22812

= ifm ISOBUS Signal Table Interface

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 22830

This function is only used internally in the created (and imported) auto code in combination with the functionality "signal table". The function works internally for the administration of the functionality "signal table".

This function is not meant for the user.

The function is the interface between the library and the CODESYS application for the internal administrative data "Dataarray" and "Arraysize", which are global variables of the functionality "signal table". Due to logistic and programming-related reasons the data and the function must be located in the CODESYS application.

The call of the function is carried out cyclically in the program (PRG) ifm_ISOBUS_Signaltable, as follows: ifm_ISOBUS_SigTableInterface (ADR(Dataarray), Arraysize);

In the context of the cyclical call of the program ifm_ISOBUS_Signaltable this function is called cyclically as well; this means it is the central call for processing of the functionality "signal table" in the ISOBUS library and in the CODESYS application.

>

Parameters of the inputs 22831

Parameter Data type Description

AdrDataarray DWORD Start address of the signal table data matrix from the ifm ISOBUS wizard signal table

Determine the address by means of the operator ADR and assigne it to the POU!

ArraySize DWORD Size of the data matrix

>

22834

Parameter Data type Description

ifm_ISOBUS_SigTableInterface BOOL TRUE: Function has been finished The data is valid

Page 49: ifm-Systemhandbuch ISOBUS im ifm-Controller

49

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

6.2.2 ISOBUS function blocks: Initialisation of the object pool

Config_ObjectPool............................................................................................................................... 50 Config_ObjectPool_LanguagePart ...................................................................................................... 51 Config_ObjectPool_Part ...................................................................................................................... 52

.21095

An object pool can consist of various (max. 50) object pool elements.

► Each object pool element must be configured

► In a final step, the object pool needs to be configured.

Page 50: ifm-Systemhandbuch ISOBUS im ifm-Controller

50

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

Config_ObjectPool 21240

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21733

Configures the object pool, consisting of all previously configured object pool elements.

>

Parameters of the inputs 21734

Parameter Data type Description

Number_ObjectPoolParts DWORD Number of elements in the object pool permissible = 0...50

Size_DataMask_XY DWORD Intended size of the data range in [pixels]

Size_SoftKey_X DWORD Intended width of the softkey area in [pixels]

Size_SoftKey_Y DWORD Intended height of the softkey area in [pixels]

Address_VersionLabelString DWORD Address of the version designation (character string consisting of 7 characters): e.g. strVersionLabel : STRING(7) := 'App0107'

Address_LanguageString DWORD Address of the language character string (character string consisting of 2 characters): e.g. strLanguage : STRING(2) := 'en'

>

Parameters of the outputs 21735

Parameter Data type Description

Config_ObjectPool BOOL TRUE: Function has been finished The data is valid

Page 51: ifm-Systemhandbuch ISOBUS im ifm-Controller

51

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

Config_ObjectPool_LanguagePart 21237

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21728

Configures a language-dependent object pool element.

>

Parameters of the inputs 21729

Parameter Data type Description

Index_ObjectPoolPart DWORD Index of the object pool element to be initialised Number the index consecutively! permissible = 0...49

Address_ObjectPool_Data DWORD Address of the data range of the object pool element

Size_ObjectPool_Data DWORD Size of the data range of the object pool element

ScaleFactor DWORD Factor for scaling of the object pool element 0 = ScaleFactor_None 1 = ScaleFactor_DataMask 2 = ScaleFactor_SoftkeyMask

Address_LanguageString DWORD Address of the language character string (character string consisting of 2 characters): e.g. strLanguage : STRING(2) := 'en'

>

Parameters of the outputs 21730

Parameter Data type Description

Config_ObjectPool_LanguagePart BOOL TRUE: Function has been finished The data is valid

Page 52: ifm-Systemhandbuch ISOBUS im ifm-Controller

52

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

Config_ObjectPool_Part 21234

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21720

This function configures a language-independent element of the object pool.

>

Parameters of the inputs 21721

Parameter Data type Description

Index_ObjectPoolPart DWORD Index of the object pool element to be initialised Number the index consecutively! permissible = 0...49

Address_ObjectPool_Data DWORD Address of the data range of the object pool element

Size_ObjectPool_Data DWORD Size of the data range of the object pool element

ScaleFactor DWORD Factor for scaling of the object pool element 0 = ScaleFactor_None 1 = ScaleFactor_DataMask 2 = ScaleFactor_SoftkeyMask

>

Parameters of the outputs 21722

Parameter Data type Description

Config_ObjectPool_Part BOOL TRUE: Function has been finished The data is valid

Page 53: ifm-Systemhandbuch ISOBUS im ifm-Controller

53

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

6.2.3 ISOBUS function blocks: Basic functions

ifm_ISOBUS ........................................................................................................................................ 54 ifm_ISOBUS_5msTask ....................................................................................................................... 56

21085

Page 54: ifm-Systemhandbuch ISOBUS im ifm-Controller

54

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

ifm_ISOBUS 21117

Unit type = function block (FB)

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21331

This FB initialises the ISOBUS on the intended CAN interface.

► Call the FB in every PLC cycle!

The FB carries out the Init routine of the ISOBUS stack.

The FB initialises the CAN interface used.

>

Parameters of the inputs 21332

Parameter Data type Description

INIT BOOL TRUE (only for 1 cycle): Function block and interface are initialised

FALSE: during further processing of the program

ObjectPool_Development BOOL Transmit the object pool to the universal terminal (VT):

TRUE: upon each connection of the implement to the VT (terminal does not save the object pool) (during the development of the implement)

FALSE: only after the ObjectPool version has been changed (terminal saves the object pool)

Page 55: ifm-Systemhandbuch ISOBUS im ifm-Controller

55

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

Parameters of the outputs 21335

Parameter Data type Description

LicenceOK BOOL TRUE: ISOBUS licence on the controller is valid ISOBUS stack is being executed

FALSE: ISOBUS licence on the controller is missing / invalid ISOBUS stack is not being executed

My_SA BYTE Current source address (SA) of my implement (WS)

NrVTAvail BYTE Number of available VT bus participants

ConnectionStatus Byte Status of the connection with a VT:

0 = waiting for an available VT 1 = connected to VT (ObjectPool on VT not ready) 2 = waiting for the ObjectPool 3 = stores ObjectPool on the VT 4 = waiting for the ObjectPool to be stored on the VT 5 = manipulation by the operator Implement can work with/on VT 6 = disconnected from the VT

WorkingSet_Active BOOL TRUE: Implement is connected to the VT

FALSE: Implement is not connected to the VT

ActiveWorkingSet_SA BYTE Source address (SA) of the active implement (WS)

0 = implement is not connected to the VT

ConnectedVT_SA Byte Source address (SA) of the connected VT

0 = implement is not connected to the VT

ConnectedVT_ManufacturerCode Word Manufacturer code (according to ISO 11783) of the connected VT

0 = implement is not connected to the VT

Visible_DataAlarm_Mask DWORD If WorkingSet_Active = TRUE: Object ID of the visible data / alarm mask

If WorkingSet_Active = FALSE: Object ID of the previously active data / alarm mask

If there is no connection to a VT: Visible_DataAlarm_Mask = 0

Visible_Softkey_Mask DWORD If WorkingSet_Active = TRUE: Object ID of the visible softkey mask

If WorkingSet_Active = FALSE: Object ID of the previously active softkey mask

If there is no connection to a VT: Visible_Softkey_Mask = 0

Page 56: ifm-Systemhandbuch ISOBUS im ifm-Controller

56

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

ifm_ISOBUS_5msTask 21123

Unit type = function block (FB)

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21352

This FB serves as a time reference for the ISOBUS stack.

First: ifm_ISOBUS > INIT = TRUE Then: ifm_ISOBUS > INIT = FALSE Only then call the FB fm_ISOBUS_5msTask.

This function block has no output parameters. This function block has no input parameters.

Page 57: ifm-Systemhandbuch ISOBUS im ifm-Controller

57

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

6.2.4 ISOBUS function blocks: Data exchange regarding the universal terminal (VT)

VT_NextVT .......................................................................................................................................... 58 VT_LocalizationInfo ............................................................................................................................. 59 VT_ExtendedInfo ................................................................................................................................. 61

21087

Page 58: ifm-Systemhandbuch ISOBUS im ifm-Controller

58

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

VT_NextVT 21128

= Virtual Terminal_Next Virtual Terminal

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21355

This function disconnects the implement (WS) from the current universal terminal (VT) and connects it to the next available universal terminal.

Prerequisite: More than 1 VT is available on the ISOBUS: FB ifm_ISOBUS: Parameter NrVTAvail > 2

This function block has no input parameters.

>

Parameters of the outputs 21356

Parameter Data type Description

VT_NextVT BOOL TRUE: The function has been executed.

FALSE: The function has not been executed. Only 1 VT is available on the ISOBUS.

Page 59: ifm-Systemhandbuch ISOBUS im ifm-Controller

59

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

VT_LocalizationInfo 21131

= Virtual Terminal_Localization Info

Unit type = function block (FB)

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21361

This function block receives local information from the connected universal terminal (VT). This information is contained in the ISO 11683 LanguageCommand message. This FB filters individual information from the message and makes it accessible to the controller in the implement (WS).

The connected VT informs all controllers on the ISOBUS about the following parameters: • language code • data format • date and time format • units of the measured values

This information is given... • once, at the beginning, after the coupling • after the parameter setting of the universal terminal has been changed

This function block has no input parameters.

>

Parameters of the outputs 21362

Parameter Data type Description

VALID BOOL TRUE: WS is connected to the VT Data is valid

FALSE: Data is not valid There is no connection to the VT

LanguageCode STRING(2) Character string consisting of 2 characters for the country code to ISO 693-1, (only small letters) e.g.: de = German / en = English / es = Spanish fr = French / it = Italian / nl = Dutch

DecimalSymbol BYTE Symbol for the decimal point (binary, 2 digits): • 0b00 = use of a comma (e.g.: 100,5) • 0b01 = use of a full stop (e.g. 100.5) • 0b10 = reserved • 0b11 = no action (the 6 preceding binary digits are always "0")

Page 60: ifm-Systemhandbuch ISOBUS im ifm-Controller

60

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

Parameter Data type Description

DateFormat BYTE Date format (indication in decimal numbers) • 0 = ddmmyyyy (= day, month, year) • 1 = ddyyyymm (= day, year, month) • 2 = mmyyyydd (= month, year, day) • 3 = mmddyyyy (= month, day, year) • 4 = yyyymmdd (= year, month, day) • 5 = yyyyddmm (= year, day, month)

TimeFormat BYTE Time format (binary, two-digit): • 0b00 = 24 h time format (e.g.: 17:30) • 0b01 = 12 h time format (e.g. 05:30 pm) • 0b10 = reserved • 0b11 = no action (the 6 preceding binary digits are always "0")

UnitsSystem BYTE System of units (binary, two-digit): • 0b00 = metric units • 0b01 = British units • 0b10 = US units • 0b11 = no action (the 6 preceding binary digits are always "0")

DistanceUnits BYTE System of units used for distances (binary, two-digit): • 0b00 = metric (kilometre, metre...) • 0b01 = British/ US (miles, feet...) • 0b10 = reserved • 0b11 = no action (the 6 preceding binary digits are always "0")

ArealUnits BYTE System of units used for areas (binary, two-digit): • 0b00 = metric (ha, m²...) • 0b01 = British/ US (acre, square mile...) • 0b10 = reserved • 0b11 = no action (the 6 preceding binary digits are always "0")

VolumeUnits BYTE System of units used for volume (binary, two-digit): • 0b00 = metric (litre) • 0b01 = British (gallon) • 0b10 = US (US gallon) • 0b11 = no action (the 6 preceding binary digits are always "0")

MassUnits BYTE System of units used for weight (binary, two-digit): • 0b00 = metric (ton, kg, ...) • 0b01 = British (long tons, pounds, ...) • 0b10 = US (short tons, pounds, ...) • 0b11 = no action (the 6 preceding binary digits are always "0")

TemperatureUnits BYTE System of units used for temperatures (binary, two-digit): • 0b00 = metric (°C, Kelvin, ...) • 0b01 = British / US (°F, Kelvin, ...) • 0b10 = reserved • 0b11 = no action (the 6 preceding binary digits are always "0")

PressureUnits BYTE System of units used for pressure (binary, two-digit): • 0b00 = metric (kilopascal, bar, ...) • 0b01 = British/ US (pounds per square inch, ...) • 0b10 = reserved • 0b11 = no action (the 6 preceding binary digits are always "0")

ForceUnits BYTE System of units used for force (binary, two-digit): • 0b00 = metric (Newton, ...) • 0b01 = British/ US (long ton, pounds force, ...) • 0b10 = reserved • 0b11 = no action (the 6 preceding binary digits are always "0")

Page 61: ifm-Systemhandbuch ISOBUS im ifm-Controller

61

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

VT_ExtendedInfo 21134

= Virtual Terminal_Extended Info

Unit type = function block (FB)

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21386

This FB receives extended information from the connected universal terminal (VT).

This information comes from the following messages: • Get Memory Response message • Get Number of Soft Keys Response message • Get Text Fonts Data Response message • Get Hardware Response message

This function block has no input parameters.

>

Parameters of the outputs 21387

Parameter Data type Description

VALID BOOL TRUE: WS is connected to the VT Data is valid

FALSE: Data is not valid There is no connection to the VT

VT_Version BYTE Version of ISO 11783-6 the connected VT corresponds to

Softkey_X_Pixels BYTE Number of pixels on the X axis for a softkey labeler

Softkey_Y_Pixels BYTE Number of pixels on the Y axis for a softkey labeler

Softkey_Physical BYTE Number of physical softkeys

Softkey_Virtual BYTE Number of possible virtual softkeys in a softkey mask: • up to version 3: 6...64 • as of version 4: 64

Page 62: ifm-Systemhandbuch ISOBUS im ifm-Controller

62

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

Parameter Data type Description

Font_Size WORD Supported font sizes (if several font sizes are permissible, the values are linked with OR)

small font sizes: 0b0000 0000 0000 0001 = font size 6x8 px 0b0000 0000 0000 0010 = font size 8x8 px 0b0000 0000 0000 0100 = font size 8x12 px 0b0000 0000 0000 1000 = font size 12x16 px 0b0000 0000 0001 0000 = font size 16x16 px 0b0000 0000 0010 0000 = font size 16x24 px 0b0000 0000 0100 0000 = font size 24x32 px 0b0000 0000 1000 0000 = font size 32x32 px

large font sizes: 0b0000 0001 0000 0000 = font size 32x48 px 0b0000 0010 0000 0000 = font size 48x64 px 0b0000 0100 0000 0000 = font size 64x64 px 0b0000 1000 0000 0000 = font size 64x96 px 0b0001 0000 0000 0000 = font size 96x128 px 0b0010 0000 0000 0000 = font size 128x128 px 0b0100 0000 0000 0000 = font size 128x192 px 0b1000 0000 0000 0000 = not used

Font_Styles BYTE Supported font styles (if several font styles are permissible, the values are linked with OR)

0b0000 0000 = normal characters (preset) 0b0000 0001 = font bold 0b0000 0010 = font crossed out 0b0000 0100 = font underlined 0b0000 1000 = font italic 0b0001 0000 = font inverted 0b0010 0000 = inverted flashing of the font / style set 0...3 0b0100 0000 = font flashes / style set 0...3 including foreground and background 0b1000 0000 = font proportional (as of VT version 4)

HW_GraphicType BYTE Supported graphics modes:

00 = monochrome VT supports colour codes 0 and 1 and only monochrome graphic elements

01 = 16 colours VT supports colour codes 0 to 15 and graphic elements based on 16 colours

02 = 256 colours VT supports colour codes 0 to 255 and all formats for graphic elements

HW_Features BYTE Hardware features of the VT (if several features exist, the values are linked with OR):

0b0000 0001 = VT has a touch screen 0b0000 0010 = VT has a pointing device 0b0000 0100 = VT has a multi-frequency audio output 0b0000 1000 = VT has an audio output which allows adjustment of the volume 0b0001 0000 = VT supports simultaneous actuation of all combinations of the softkeys (as of VT version 4) 0b0010 0000 = VT supports simultaneous actuation of all combinations of the pushbuttons (as of VT version 4) 0b0100 0000 = VT signals drag operation via PointingEventMessage (as of VT version 4) 0b1000 0000 = VT supports intermediate coordinate values during a drag operation (if bit 6 is activated as well) (as of VT version 4)

HW_DataMask_X_Pixels DWORD Number of subdivisions (pixels) on the X axis of the data mask area

HW_DataMask_Y_Pixels DWORD Number of subdivisions (pixels) on the Y axis of the data mask area

Page 63: ifm-Systemhandbuch ISOBUS im ifm-Controller

63

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

6.2.5 ISOBUS function blocks: Data exchange regarding the implement (WS)

ISOBUS function blocks: Data exchange regarding the implement commands to the VT ................. 63 ISOBUS function blocks: Interface at the implement: Events from the VT ......................................... 81

21089

>

ISOBUS function blocks: Data exchange regarding the implement commands to the VT

WS_CmdChangeActiveMask .............................................................................................................. 64 WS_CmdChangeAttribute ................................................................................................................... 65 WS_CmdChangeFillAttributes ............................................................................................................. 66 WS_CmdChangeFontAttributes .......................................................................................................... 67 WS_CmdChangeLineAttributes .......................................................................................................... 69 WS_CmdChangeListItem .................................................................................................................... 70 WS_CmdChangeNumericValue .......................................................................................................... 71 WS_CmdChangeSize ......................................................................................................................... 72 WS_CmdChangeSoftKeyMask ........................................................................................................... 73 WS_CmdChangeStringValue .............................................................................................................. 74 WS_CmdControlAudioSignal .............................................................................................................. 75 WS_CmdEnableDisableObject ........................................................................................................... 76 WS_CmdHideShowObject .................................................................................................................. 77 WS_CmdMoveObject .......................................................................................................................... 78 WS_CmdSetAudioVolume .................................................................................................................. 79 WS_CmdSetObjectPosition ................................................................................................................ 80

21091

The coupled implement (WS) can send commands to the universal terminal (VT) in the agricultural machine by means of the following function blocks:

Page 64: ifm-Systemhandbuch ISOBUS im ifm-Controller

64

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_CmdChangeActiveMask 21140

= Working Set_Command Change Active Mask

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21425

This function changes from the active mask of the implement (WS) to a data or alarm mask in the universal terminal (VT). >

Parameters of the inputs 21425

Parameter Data type Description

ObjectID WORD Object ID of the new data or alarm mask

>

Parameters of the outputs 21426

Parameter Data type Description

WS_CmdChangeNumericValue BOOL TRUE: Function has been finished The data is valid

Page 65: ifm-Systemhandbuch ISOBUS im ifm-Controller

65

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_CmdChangeAttribute 21158

= Working Set_Command Change Attribute

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21451

This function changes the attribute of an object by means of an attribute ID (AID). Character Strings cannot be changed this way.

>

Parameters of the inputs 21453

Parameter Data type Description

ObjectID WORD Object ID of the object to be changed

AttributeID BYTE Attribute-ID (AID)

Attribute DWORD New value for the attribute

>

Parameters of the outputs 21454

Parameter Data type Description

WS_CmdChangeAttribute BOOL TRUE: Function has been finished The data is valid

Page 66: ifm-Systemhandbuch ISOBUS im ifm-Controller

66

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_CmdChangeFillAttributes 21182

= Working Set_Command Change Fill Attributes

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21680

This function changes the fill attribute of a fill attribute object.

If the attribute is to be changed from FillType = 0, 1 or 2 to FillType = 3:

► First change the fill pattern attribute (FillPattern_ObjectID) of the implement.

► Only then do change the fill type attribute (FillType=3).

> Otherwise the behaviour on the universal terminal cannot be predicted and depends on the device.

>

Parameters of the inputs 21681

Parameter Data type Description

ObjectID WORD Object ID of the object to be changed

FillType BYTE Type of the filling of the object 0 = 0x00 = no filling 1 = 0x01 = filled with the line colour 2 = 0x02 = filled with the colour set in → FillColor 3 = 0x03 = filled with the pattern set in → FillPattern_ObjectID

FillColor BYTE Colour of the filling of this object, only if FillType = 2 Fill colour according to ISO 11783-6 "VT standard colour palette"

FillPattern_ObjectID WORD Pattern of the filling of this object, only if FillType = 3 Object ID of a graphic object used as a fill pattern 65535 = 0xFFFF = NULL: Display the object without filling

>

Parameters of the outputs 21682

Parameter Data type Description

WS_CmdChangeFillAttributes BOOL TRUE: Function has been finished The data is valid

Page 67: ifm-Systemhandbuch ISOBUS im ifm-Controller

67

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_CmdChangeFontAttributes 21176

= Working Set_Command Change Font Attributes

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21606

This function changes the font attributes of the corresponding object on the universal terminal.

>

Parameters of the inputs 21607

Parameter Data type Description

ObjectID WORD Object ID of the object to be changed

FontColor BYTE Colour of the font of this object → standard colour palette for VT to ISO 11783-6

FontSize BYTE Size of the font of this object

0 = 0x00 = font size 6x8 px 1 = 0x01 = font size 8x8 px 2 = 0x02 = font size 8x12 px 3 = 0x03 = font size 12x16 px 4 = 0x04 = font size 16x16 px 5 = 0x05 = font size 16x24 px 6 = 0x06 = font size 24x32 px 7 = 0x07 = font size 32x32 px 8 = 0x08 = font size 32x48 px 9 = 0x09 = font size 48x64 px 10 = 0x0A = font size 64x64 px 11 = 0x0B = font size 64x96 px 12 = 0x0C = font size 96x128 px 13 = 0x0D = font size 128x128 px 14 = 0x0E = font size 128x192 px

FontType BYTE Font of this object 0 = 0x00 = ISO Latin 1 (to ISO8859-1) 1 = 0x01 = ISO Latin 9 (to ISO8859-15) 255 = 0xFF = proprietary

FontStyle BYTE Font style of the object (several font styles: values linked with OR):

0b0000 0000 = normal characters (preset) 0b0000 0001 = font bold 0b0000 0010 = font crossed out 0b0000 0100 = font underlined 0b0000 1000 = font italic 0b0001 0000 = font inverted 0b0010 0000 = inverted flashing of the font / style set 0...3 0b0100 0000 = font flashes / style set 0...4 including foreground and background (priority over 0b0100 0000)

Page 68: ifm-Systemhandbuch ISOBUS im ifm-Controller

68

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

Parameters of the outputs 21608

Parameter Data type Description

WS_CmdChangeFontAttributes BOOL TRUE: Function has been finished The data is valid

Page 69: ifm-Systemhandbuch ISOBUS im ifm-Controller

69

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_CmdChangeLineAttributes 21179

= Working Set_Command Change Line Attributes

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21626

This function changes the line attributes of the corresponding object on the universal terminal.

>

Parameters of the inputs 21627

Parameter Data type Description

ObjectID WORD Object ID of the object to be changed

LineColor BYTE Colour of the line object → standard colour palette for VT to ISO 11783-6

LineWidth BYTE Thickness of the line object in [pixels]

LineArt WORD Bit pattern of the line object Each bit corresponds to a point with the length and thickness of LineWidth Bit = 0: point of the line is displayed in the background colour Bit = 1: point of the line is displayed in the LineColor

Examples: 0x3333 = dashed line 0x5555 = dotted line 0xFFFF = continuous line

>

Parameters of the outputs 21628

Parameter Data type Description

WS_CmdChangeLineAttributes BOOL TRUE: Function has been finished The data is valid

Page 70: ifm-Systemhandbuch ISOBUS im ifm-Controller

70

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_CmdChangeListItem 21161

= Working Set_Command Change List Item

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21459

This function changes a list element in an input list object in the universal terminal (VT).

>

Parameters of the inputs 21460

Parameter Data type Description

ObjectID WORD Object ID of the object to be changed

ListIndex WORD List index (0..n)

NewObjectID WORD New object ID 0xFFFF = empty element

>

Parameters of the outputs 21461

Parameter Data type Description

WS_CmdChangeListItem BOOL TRUE: Function has been finished The data is valid

Page 71: ifm-Systemhandbuch ISOBUS im ifm-Controller

71

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_CmdChangeNumericValue 21137

= Working Set_Command Change Numeric Value

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21413

This function changes the numerical value in an object in the universal terminal (VT). The function is only valid for objects with the attribute "numerical value".

Do NOT change the size of the object via this command!

Only the object indicated in the command is changed. Variables the object refers to do NOT change.

Adapt the update frequency to the available band width of the ISOBUS! Only update the values if they have changed.

>

Parameters of the inputs 21414

Parameter Data type Description

ObjectID WORD Object ID of the object to be changed

Value DWORD New numerical value for the indicated object

>

Parameters of the outputs 21415

Parameter Data type Description

WS_CmdChangeNumericValue BOOL TRUE: Function has been finished The data is valid

Page 72: ifm-Systemhandbuch ISOBUS im ifm-Controller

72

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_CmdChangeSize 21173

= Working Set_Command Change Size

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21600

This function changes the size of an object.

The value "0" for width and/or height means that the object has the size 0 and is not displayed on the universal terminal. The object maintains its position.

>

Parameters of the inputs 21601

Parameter Data type Description

ObjectID WORD Object ID of the object to be changed

NewWidth WORD New width of the object in [pixels] 0x0000 = element not visible

NewHeight WORD New height of the object in [pixels] 0x0000 = element not visible

>

Parameters of the outputs 21602

Parameter Data type Description

WS_CmdChangeSize BOOL TRUE: Function has been finished The data is valid

Page 73: ifm-Systemhandbuch ISOBUS im ifm-Controller

73

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_CmdChangeSoftKeyMask 21144

= Working Set_Command Change Softkey Mask

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21431

This function changes the mask of the programmed buttons (softkeys) belonging to the active implement (WS) in the universal terminal (VT). >

Parameters of the inputs 21433

Parameter Data type Description

ObjectID WORD Object ID of the new softkey mask

>

Parameters of the outputs 21434

Parameter Data type Description

WS_CmdChangeSoftkeyMask BOOL TRUE: Function has been finished The data is valid

Page 74: ifm-Systemhandbuch ISOBUS im ifm-Controller

74

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_CmdChangeStringValue 21170

= Working Set_Command Change String Value

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21590

This function changes the character string value in an object. The size of the object is not changed. Variables the object refers to are not changed.

The transmitted character string can be shorter than the length attribute of the target object. In this case the universal terminal fills the character string with blanks.

The number of transmitted bytes for the character string may be smaller as or equal to the length attribute of the target object, i.e. the character string must not be longer.

>

Parameters of the inputs 21594

Parameter Data type Description

ObjectID WORD Object ID of the object to be changed

StringLength WORD Length of the character string (number of characters) e.g.: LEN(StringValue)

StringAddress WORD Address of the character string variable e.g.: ADR(StringValue)

>

Parameters of the outputs 21596

Parameter Data type Description

WS_CmdChangeStringValue BOOL TRUE: Function has been finished The data is valid

Page 75: ifm-Systemhandbuch ISOBUS im ifm-Controller

75

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_CmdControlAudioSignal 21185

= Working Set_Command Control Audio Signal

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21687

This function controls the audio signal on the universal terminal.

>

Parameters of the inputs 21688

Parameter Data type Description

Activations BYTE Number of the audio activation on the universal terminal 0 = stops all audio processes 1...255 = number of the audio activation

Frequency WORD Tone pitch in [Hz] If the tone pitch is too high for the terminal to emit, the terminal reduces the value to the permissible range.

ON_Time WORD Switch-on time of the audio signal on the universal terminal If the configured switch-on time for the terminal is too short, the terminal extends the value to the minimum permissible duration.

OFF_Time WORD Switch-off time of the audio signal on the universal terminal If the configured switch-off time for the terminal is too short, the terminal extends the value to the minimum permissible duration.

>

Parameters of the outputs 21689

Parameter Data type Description

WS_CmdControlAudioSignal BOOL TRUE: Function has been finished The data is valid

Page 76: ifm-Systemhandbuch ISOBUS im ifm-Controller

76

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_CmdEnableDisableObject 21155

= Working Set_Command Enable Disable Object

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21446

This function controls the accessibility of an input field object in the universal terminal (VT).

>

Parameters of the inputs 21447

Parameter Data type Description

ObjectID WORD Object ID of the object to be changed

DisableOrEnable BYTE 00 = lock input field object 01 = release input field object

>

Parameters of the outputs 21448

Parameter Data type Description

WS_CmdEnableDisableObject BOOL TRUE: Function has been finished The data is valid

Page 77: ifm-Systemhandbuch ISOBUS im ifm-Controller

77

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_CmdHideShowObject 21152

= Working Set_Command Hide Show Object

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21438

This functions hides or shows a container object in the universal terminal. >

Parameters of the inputs 21440

Parameter Data type Description

ObjectID WORD Object ID of the container object

HideOrShow BYTE 00 = hide object 01 = show object

>

Parameters of the outputs 21439

Parameter Data type Description

WS_CmdHideShowObject BOOL TRUE: Function has been finished The data is valid

Page 78: ifm-Systemhandbuch ISOBUS im ifm-Controller

78

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_CmdMoveObject 21162

= Working Set_Command Move Object

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21491

This function corresponds to the command "Change Child Location" of ISO 11783-6. The command "Change Child Location" changes the position of an object. The new position of the object is indicated in relation to the current position.

► The "Child Object" may be included in a great number of "Parent Objects". Therefore, do indicate the ID of the "Parent Object"!

If the "child object" is contained in a "Parent object" several times, all instances of the "Child object" are moved with this function.

If the object has been moved, the "Parent Object" has to be updated.

The position of the object changes as follows:

X > 0 Object moves to the right

X < 0 Object moves to the left

Y > 0 Object moves down

Y < 0 Object moves up

>

Parameters of the inputs 21492

Parameter Data type Description

Parent_ObjectID WORD ID of the "ParentObject"

ObjectID WORD Object ID of the object to be moved

X_Change INT Relative change of the position in X direction in [pixels] permissible = -127...+127

Y_Change INT Relative change of the position in Y direction in [pixels] permissible = -127...+127

>

Parameters of the outputs 21493

Parameter Data type Description

WS_CmdMoveObject BOOL TRUE: Function has been finished The data is valid

Page 79: ifm-Systemhandbuch ISOBUS im ifm-Controller

79

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_CmdSetAudioVolume 21188

= Working Set_Command Set Audio Volume

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21695

This function controls the volume of the audio signal on the universal terminal.

>

Parameters of the inputs 21696

Parameter Data type Description

VolumePercent BYTE Volume of the audio signal on the universal terminal in per cent of the maximum volume possible for the terminal permissible = 0...100

>

Parameters of the outputs 21697

Parameter Data type Description

WS_CmdSetAudioVolume BOOL TRUE: Function has been finished The data is valid

Page 80: ifm-Systemhandbuch ISOBUS im ifm-Controller

80

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_CmdSetObjectPosition 21167

= Working Set_Command Set Object Position

Unit type = function (FUN) of type BOOL

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21570

This function corresponds to the command "Change Child Location" of ISO 11783-6. The command "Change Child Location" changes the position of an object. The new position of the object is indicated in relation to the position of the "Parent Object".

► The "Child Object" may be included in a great number of "Parent Objects". Therefore, do indicate the ID of the "Parent Object"!

If the "Child Object" is contained in a "parent object" several times, all instances of the "child Object" are moved to the same new position with this function. If the instances are to be moved relatively, use the functionWS_CMDMOVEOBJECT (→ p. 78)!

The position of the object changes to the following value: • X(new) = X(upper left corner Parent Object) + X_POSITION (= to the right) • Y(new) = Y(upper left corner Parent Object) + Y_POSITION (= down)

>

Parameters of the inputs 21517

Parameter Data type Description

Parent_ObjectID WORD ID of the "ParentObject"

ObjectID WORD Object ID of the object to be moved

X_Position WORD New X position, in relation to the upper left corner of the "Parent Object" (= to the right) in [pixels]

Y_Position WORD New Y position, in relation to the upper left corner of the "Parent Object" (= down) in [pixels]

>

Parameters of the outputs 21572

Parameter Data type Description

WS_CmdSetObjectPosition BOOL TRUE: Function has been finished The data is valid

Page 81: ifm-Systemhandbuch ISOBUS im ifm-Controller

81

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

ISOBUS function blocks: Interface at the implement: Events from the VT

WS_EvtButtonActivation ..................................................................................................................... 82 WS_EvtSoftKeyActivation ................................................................................................................... 83 WS_EvtVTChangeNumericValue ........................................................................................................ 84 WS_EvtVTChangeStringValue ............................................................................................................ 85

21093

The coupled implement (WS) can receive commands or data from the universal terminal (VT) in the agricultural machine by means of the following function blocks:

In order not to miss any message of the universal terminal:

► Call function blocks in each PLC cycle!

Page 82: ifm-Systemhandbuch ISOBUS im ifm-Controller

82

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_EvtButtonActivation 21231

= Working Set_Event Button Activation

Unit type = function block (FB)

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21715

This message is sent by the universal terminal (VT) in the following cases: • a key is being actuated or locked (= status change); signal = 1 cycle • a key has been released or unlocked (= status change); signal = 1 cycle • a key is being pressed (keys with lock function do not send a repetition signal) • the actuation of a key has been stopped (as of VT version 4); signal = 1 cycle

> If a key is being pressed and the repetition rate exceeds 300 ms, the controller behaves as if the button had been released.

> If it is possible for the universal terminal to stop the actuation of a key, the terminal sends the KeyActivationCode=3 instead of KeyActivationCode=1.

This function block has no input parameters.

>

Parameters of the outputs 21716

Parameter Data type Description

EventOccured BOOL TRUE (only 1 cycle): Event signalled by the universal terminal: • Data entered • Key / softkey actuated

FALSE: during further processing of the program

KeyActivationCode BYTE Activation code of a key: 0 = key has been unlocked or released (= status change) 1 = key has been locked or actuated (= status change) 2 = key is being pressed 3 = actuation of the key stopped (= status change)

KeyNumber BYTE Code of the key (according to the implement)

ObjectID DWORD Object ID of the changed object

ParentObjectID DWORD Object ID of one of the following elements: • higher-level data mask • visible Windows mask object

Page 83: ifm-Systemhandbuch ISOBUS im ifm-Controller

83

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_EvtSoftKeyActivation 21126

= Working Set_Event Softkey Activation

Unit type = function block (FB)

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21710

This message is sent by the universal terminal (VT) in the following cases: • a button is being actuated (= status change); signal = 1 cycle • a button has been released (= status change); signal = 1 cycle • a button is being pressed • the actuation of a button has been stopped (as of VT version 4); signal = 1 cycle

> If a button is being pressed and the repetition rate exceeds 300 ms, the controller behaves as if the button had been released.

> If it is possible for the universal terminal to stop the actuation of a button, the terminal sends the KeyActivationCode=3 instead of KeyActivationCode=1.

This function block has no input parameters.

>

Parameters of the outputs 21711

Parameter Data type Description

EventOccured BOOL TRUE (only 1 cycle): Event signalled by the universal terminal: • Data entered • Key / softkey actuated

FALSE: during further processing of the program

KeyActivationCode BYTE Activation code of a button: 0 = button has been released (= status change) 1 = button has been actuated (= status change) 2 = button is being pressed 3 = actuation of the button stopped (= status change)

KeyNumber BYTE Code of the button 0 = Alarm ACK 1...255 = code of the button (according to the implement)

ObjectID DWORD Object ID of the changed object

ParentObjectID DWORD Object ID of one of the following elements: • visible data mask • visible alarm mask • visible button group object

Page 84: ifm-Systemhandbuch ISOBUS im ifm-Controller

84

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_EvtVTChangeNumericValue 21222

= Working Set_Event Virtual Terminal Change Numeric Value

Unit type = function block (FB)

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21702

The universal terminal (VT) sends this message as soon as the operator enters a numerical value... • for an input object, • for a variable irrespective of whether the value changes or not.

This message is not sent if the entering of values has been stopped.

If input objects refer to a numerical variable, the object ID of the object "numerical variable" is used in this message.

This function block has no input parameters.

>

Parameters of the outputs 21703

Parameter Data type Description

EventOccured BOOL TRUE (only 1 cycle): Event signalled by the universal terminal: • Data entered • Key / softkey actuated

FALSE: during further processing of the program

ObjectID DWORD Object ID of the changed object

Value DWORD New numerical value for the indicated object

Page 85: ifm-Systemhandbuch ISOBUS im ifm-Controller

85

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Functional elements from ifm for ISOBUS Functional elements from ifm: ISOBUS function blocks CODESYS interface

>

WS_EvtVTChangeStringValue 21225

= Working Set_Event Virtual Terminal Change String Value

Unit type = function block (FB)

Unit is contained in the library ifm_ISOBUS_UTAux_Vxxyyzz.lib

Symbol in CODESYS:

>

Description 21707

The universal terminal (VT) sends this message if a character string has been entered... • in a character string input object • in a referenced character string object

The universal terminal is not to delete leading blanks. The universal terminal can fill character strings with blanks up to the defined string length.

If character string input objects refer to a character string variable, the object ID of the object "character string variable" is used in this message instead of the object ID of the character string input object.

Max. permissible character string length = 255 characters (STRING(255)).

This function block has no input parameters. >

Parameters of the outputs 21708

Parameter Data type Description

EventOccured BOOL TRUE (only 1 cycle): Event signalled by the universal terminal: • Data entered • Key / softkey actuated

FALSE: during further processing of the program

StringValue STRING(255) New value for the indicated character string object

ObjectID DWORD Object ID of the changed object

StringLength DWORD Length of the character string (number of characters) e.g.: LEN(StringValue)

Page 86: ifm-Systemhandbuch ISOBUS im ifm-Controller

86

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Glossary of Terms

7 Glossary of Terms

A

Auto code

The auto code in the implement contains data and graphics for the universal terminal (VT) in the tractor. When both devices are connected via the ISOBUS and one of the following prerequisites is met: • the implement is connected to the universal terminal for the first time • the auto code in the implement has changed since the last coupling the implement transmits its auto code to the universal terminal.

>

Aux Control (AUX-N)

= Auxiliary Control a) Additional control element (e.g. joystick), enabling the operation of complex devices. b) Capability to control functions by means of an additional control element in the implement.

>

E

ECU

(1) Electronic Control Unit = control unit or microcontroller (2) Engine Control Unit = control device of a engine

Lance calls the controller in the tractor "job computer". AEF uses the term "Tractor ECU" (TECU) for the job computer.

Only the ECU of the tractor and the universal terminal can see all participants of the ISOBUS and influence them.

>

I

Implement

= machine, e.g. the intelligent tool coupled to the tractor.

>

ISO 11783

ISOBUS is the brand name or the application of a data bus for an agricultural or municipal application. It is compliant with the standard ISO 11783. Besides the physical properties of the network, such as connector and cables, the standard also defines the type of participants, data formats and interfaces. Essential elements of the J1939 and NMEA 2000 protocol have been adopted. An ISOBUS application almost never makes use all the possibilities defined in the standard, but always represents a limited amount of these possibilities. The ifm ISOBUS library meets the following parts of the standard: -3 Transport Protocol -5 Address Claim, Name Table -6 Annex J: VT v3 functions excluding Aux Control -6 Annex K: Extended Transport Protocol -12 ECU ID, SW ID, etc.

>

J

Job computer

Lance calls the controller in the tractor "job computer". → ECU

Page 87: ifm-Systemhandbuch ISOBUS im ifm-Controller

87

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Glossary of Terms

>

O

Object pool

Compilation of all objects and data in the controller of the implement. The object pool is automatically transmitted into the universal terminal (on the tractor). Afterwards, the implement can be controlled and monitored from the universal terminal. Advantage: only the selected elements appear in the CODESYS program. Disadvantage: the required elements must be grouped together before compilation. >

S

Signal table

As opposed to the →object pool the signal table contains only the objects the project planner has selected for the CODESYS project in the ifm_Wizard. Advantage: Access to all configured elements possible. Disadvantage: All elements are shown in the CODESYS program (→ confusing). >

Softkey

a) physical softkey = (mechanical) key of the universal terminal

b) virtual softkey = button programmed on the universal terminal max. number of softkeys representable (via scrolling) per data page

>

T

Task controller

(in preparation) Collects larger data amounts for transmission.

TC-BAS (basic) documents total values of e.g. the completed work. This way, orders are imported into the task controller or the finished documentation is exported after the work has been finished.

TC-GEO (geo-based) can be used additionally to collect location-based data or to plan location-based orders.

TC-SC (section control) makes it possible to set part widths for the spreading of material (seeds, fertilisers, crop science), depending on the GPS position and the required degree of overlap.

>

U

Universal terminal (UT)

Term used by the AEF for the master terminal on the tractor. One single ISOBUS terminal replaces the great number of implement-specific terminals on the tractor. With the universal terminal all ISOBUS implements can be controlled and displayed. → virtual terminal (VT)

>

V

Virtual terminal (VT)

Term for the master terminal on the tractor used in the standard (ISO 11783). → universal terminal

Page 88: ifm-Systemhandbuch ISOBUS im ifm-Controller

88

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Glossary of Terms

>

W

Wizard

Software that helps the user to carry out complex tasks. ifm_ISOBUS-Wizard: Software that converts the IOP files generated in the ISOBUS mask generator into one EXP file which can be imported in the CODESYS project.

>

Working set (WS)

→implement

Page 89: ifm-Systemhandbuch ISOBUS im ifm-Controller

89

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Index

8 Index

A

About this manual .................................................................................... 4

Adjust and transmit a CODESYS project .............................................. 44

Auto code ............................................................................................... 86

Aux Control (AUX-N) ............................................................................. 86

C

CAN

Interfaces and protocols ................................................................................ 13

Complete the project.............................................................................. 32

Config_ObjectPool ................................................................................. 50

Config_ObjectPool_LanguagePart ........................................................ 51

Config_ObjectPool_Part ........................................................................ 52

Configuration of the ISOBUS in the implement ..................................... 19

Convert mask objects for the CODESYS program ............................... 33

Copyright.................................................................................................. 4

Create a CODESYS project .................................................................. 36

Create a project from a template ........................................................... 36

Create masks and objects ..................................................................... 27

Create working area and project. .......................................................... 23

D

Data mask .............................................................................................. 29

Define display properties ....................................................................... 23

Define project properties ....................................................................... 24

Deployment options of the project ......................................................... 25

Description 48, 50, 51, 52, 54, 56, 58, 59, 61, 64, 65, 66, 67, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 82, 83, 84, 85

E

ECU ....................................................................................................... 86

Example

data mask ...................................................................................................... 29

Mask generator ............................................................................................. 23

WorkingSet .................................................................................................... 28

F

FLASH memory ..................................................................................... 12

Functional elements from ifm

ISOBUS function blocks CODESYS interface.............................................. 47

Functional elements from ifm for ISOBUS ............................................ 45

G

General project information ................................................................... 24

H

Hardware ................................................................................................. 9

Hardware description ............................................................................. 12

History of the instructions (ISO) ............................................................ 7

How is this documentation structured? ................................................... 7

I

ifm ISOBUS stack .................................................................................. 18

ifm library for ISOBUS ........................................................................... 45

ifm library ifm_ISOBUS_UTAux_Vxxyyzz.lib ........................................ 46

ifm weltweit • ifm worldwide • ifm à l’échelle internationale ................... 93

ifm_ISOBUS .......................................................................................... 54

ifm_ISOBUS_5msTask .......................................................................... 56

ifm_ISOBUS_SigTableInterface ............................................................ 48

ifm_ISOBUS-Wizard ........................................................................17, 33

Implement .............................................................................................. 86

Information about the device ................................................................. 11

Install ISOBUS stack in the controller ................................................... 20

Install ISOBUS stack in the controller via the ifm downloader .............. 21

Install the PerlScript interpreter ............................................................. 19

Interface description .............................................................................. 13

ISO 11783 .............................................................................................. 86

ISOBUS concept .................................................................................... 16

ISOBUS function blocks

Basic functions .............................................................................................. 53

Data exchange regarding the implement (WS) ............................................ 63

Data exchange regarding the implement commands to the VT ................... 63

Data exchange regarding the universal terminal (VT).................................. 57

Initialisation of the object pool ....................................................................... 49

Initialisation of the signal table ...................................................................... 47

Interface at the implement

Events from the VT .............................................................................. 81

ISOBUS mask editor.............................................................................. 22

J

Job computer ......................................................................................... 86

L

Licensing ................................................................................................ 10

M

Memory allocation for ISOBUS.............................................................. 12

Method

CODESYS with object pool ........................................................................... 40

CODESYS with signal table .......................................................................... 37

wizard for object pool .................................................................................... 35

wizard for signal table ................................................................................... 34

N

Notes ...................................................................................................... 22

Notizen • Notes • Notes ......................................................................... 91

O

Object pool ............................................................................................. 87

Object pool mask generator .................................................................. 17

Object structure for the example settings used above .......................... 38

Object structure from the wizard ........................................................... 38

Object templates .................................................................................... 26

Objekt-Pool / AutoCode ......................................................................... 18

Overview ................................................................................................ 17

documentation modules for CRnnnn .............................................................. 5

P

Parameters of the inputs ... 48, 50, 51, 52, 54, 64, 65, 66, 67, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80

Parameters of the outputs . 50, 51, 52, 55, 58, 59, 61, 64, 65, 66, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 82, 83, 84, 85

Pictograms ............................................................................................... 6

Please note .............................................................................................. 8

R

Recommendation ................................................................................... 22

Page 90: ifm-Systemhandbuch ISOBUS im ifm-Controller

90

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Index

S

Safety instructions ................................................................................... 8

Signal table ............................................................................................ 87

Softkey ................................................................................................... 87

Software ................................................................................................. 10

Software description .............................................................................. 14

Software modules for ISOBUS .............................................................. 15

SRAM ..................................................................................................... 12

System description ................................................................................ 11

System requirements ............................................................................... 9

T

Task controller ....................................................................................... 87

U

Universal terminal (UT) .......................................................................... 87

Unpack and install files .......................................................................... 19

Unpack files from ifm USB stick to the PC / laptop ............................... 19

V

View [Bausteine] ..............................................................................37, 40

View [Datentypen]............................................................................37, 41

View [Globale Variablen] .................................................................39, 43

Virtual terminal (VT) ............................................................................... 87

VT_ExtendedInfo ................................................................................... 61

VT_LocalizationInfo ............................................................................... 59

VT_NextVT ............................................................................................ 58

W

What devices are described in this manual? ........................................... 5

What do the symbols and formats mean? ............................................... 6

What previous knowledge is required? ................................................... 8

Wizard .................................................................................................... 88

Working set (WS) ................................................................................... 88

WorkingSet-Maske ................................................................................ 27

WS_CmdChangeActiveMask ................................................................ 64

WS_CmdChangeAttribute ..................................................................... 65

WS_CmdChangeFillAttributes ............................................................... 66

WS_CmdChangeFontAttributes ............................................................ 67

WS_CmdChangeLineAttributes ............................................................ 69

WS_CmdChangeListItem ...................................................................... 70

WS_CmdChangeNumericValue ............................................................ 71

WS_CmdChangeSize ............................................................................ 72

WS_CmdChangeSoftKeyMask ............................................................. 73

WS_CmdChangeStringValue ................................................................ 74

WS_CmdControlAudioSignal ................................................................ 75

WS_CmdEnableDisableObject.............................................................. 76

WS_CmdHideShowObject .................................................................... 77

WS_CmdMoveObject ............................................................................ 78

WS_CmdSetAudioVolume .................................................................... 79

WS_CmdSetObjectPosition................................................................... 80

WS_EvtButtonActivation ........................................................................ 82

WS_EvtSoftKeyActivation ..................................................................... 83

WS_EvtVTChangeNumericValue .......................................................... 84

WS_EvtVTChangeStringValue .............................................................. 85

Page 91: ifm-Systemhandbuch ISOBUS im ifm-Controller

91

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Notizen • Notes • Notes

9 Notizen • Notes • Notes

Page 92: ifm-Systemhandbuch ISOBUS im ifm-Controller

92

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Notizen • Notes • Notes

Page 93: ifm-Systemhandbuch ISOBUS im ifm-Controller

93

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Notizen • Notes • Notes

Page 94: ifm-Systemhandbuch ISOBUS im ifm-Controller

94

ifm System Manual ISOBUS in the ecomatmobile Controller (CRnn53, CRnn63) 2017-06-14

Notizen • Notes • Notes

Page 95: ifm-Systemhandbuch ISOBUS im ifm-Controller

95

10 ifm weltweit • ifm worldwide • ifm à l’échelle internationale

Version: 2016-11-29 8310

ifm electronic gmbh • Friedrichstraße 1 • 45128 Essen

www.ifm.com • Email: [email protected]

Service hotline: 0800 / 16 16 16 (only Germany, Mo-Fr 07.00...18.00 h)

ifm Niederlassungen • Sales offices • Agences

D Niederlassung Nord • 31135 Hildesheim • Tel. 0 51 21 / 76 67-0

Niederlassung West • 45128 Essen • Tel. 02 01 / 3 64 75 -0

Niederlassung Mitte-West • 58511 Lüdenscheid • Tel. 0 23 51 / 43 01-0

Niederlassung Süd-West • 64646 Heppenheim • Tel. 0 62 52 / 79 05-0

Niederlassung Baden-Württemberg • 73230 Kirchheim • Tel. 0 70 21 / 80 86-0

Niederlassung Bayern • 82178 Puchheim • Tel. 0 89 / 8 00 91-0

Niederlassung Ost • 07639 Tautenhain • Tel. 0 36 601 / 771-0

A, SL

AUS

B, L

BG

BR

CH

CL

CN

CND

CZ

DK

E

F

FIN

GB, IRL

GR

H

I

IL

IND

J

MAL

MEX

N

NA

NL

NZ

P

PL

RA, ROU

RO

ROK

RUS

S

SGP

SK

THA

TR

UA

USA

VN

ZA

ifm electronic gmbh • 1120 Wien • Tel. +43 16 17 45 00

ifm efector pty ltd. • Mulgrave Vic 3170 • Tel. +61 3 00 365 088

ifm electronic N.V. • 1731 Zellik • Tel. +32 2 / 4 81 02 20

ifm electronic eood • 1202 Sofia • Tel. +359 2 807 59 69

ifm electronic Ltda. • 03337-000, Sao Paulo SP • Tel. +55 11 / 2672-1730

ifm electronic ag • 4 624 Härkingen • Tel. +41 62 / 388 80 30

ifm electronic SpA • Oficina 5032 Comuna de Conchalí • Tel. +55 11 / 2672-1730

ifm electronic (Shanghai) Co. Ltd. • 201203 Shanghai • Tel. +86 21 / 3813 4800

ifm efector Canada inc. • Oakville, Ontario L6K 3V3 • Tel. +1 800-441-8246

ifm electronic spol. s.r.o. • 25243 Průhonice • Tel. +420 267 990 211

ifm electronic a/s • 2605 BROENDBY • Tel. +45 70 20 11 08

ifm electronic s.a. • 08820 El Prat de Llobregat • Tel. +34 93 479 30 80

ifm electronic s.a. • 93192 Noisy-le-Grand Cedex • Tél. +33 0820 22 30 01

ifm electronic oy • 00440 Helsinki • Tel . +358 75 329 5000

ifm electronic Ltd. • Hampton, Middlesex TW12 2HD • Tel. +44 208 / 213-0000

ifm electronic Monoprosopi E.P.E. • 15125 Amaroussio • Tel. +30 210 / 6180090

ifm electronic kft. • 9028 Györ • Tel. +36 96 / 518-397

ifm electronic s.a. • 20041 Agrate-Brianza (MI) • Tel. +39 039 / 68.99.982

Astragal Ltd. • Azur 58001 • Tel. +972 3 -559 1660

ifm electronic India Branch Office • Kolhapur, 416234 • Tel. +91 231-267 27 70

efector co., ltd. • Chiba-shi, Chiba 261-7118 • Tel. +81 043-299-2070

ifm electronic Pte. Ltd • 47100 Puchong Selangor • Tel. +603 8063 9522

ifm efector S. de R. L. de C. V. • Monterrey, N. L. 64630 • Tel. +52 81 8040-3535

Sivilingeniør J. F. Knudtzen A/S • 1396 Billingstad • Tel. +47 66 / 98 33 50

ifm elctronic (pty) Ltd • 25 Dr. W. Kulz Street Windhoek • Tel. +264 61 300984

ifm electronic b.v. • 3843 GA Harderwijk • Tel. +31 341 / 438 438

ifm efector pty ltd • 930 Great South Road Penrose, Auckland • Tel. +64 95 79 69 91

ifm electronic s.a. • 4410-136 São Félix da Marinha • Tel. +351 223 / 71 71 08

ifm electronic Sp. z o.o. • 40-106 Katowice • Tel. +48 32-608 74 54

ifm electronic s.r.l. • 1107 Buenos Aires • Tel. +54 11 / 5353 3436

ifm electronic s.r.l • Sibiu 557260 • Tel. +40 269 224550

ifm electronic Ltd. • 140-884 Seoul • Tel. +82 2 / 790 5610

ifm electronic • 105318 Moscow • Tel. +7 495 921-44-14

ifm electronic a b • 41250 Göteborg • Tel. +46 31 / 750 23 00

ifm electronic Pte. Ltd. • Singapore 609 916 • Tel. +65 6562 8661/2/3

ifm electronic s.r.o. • 835 54 Bratislava • Tel. +421 2 / 44 87 23 29

SCM Allianze Co., Ltd. • Bangkok 10 400 • Tel. +66 02 615 4888

ifm electronic Ltd. Sti. • 34381 Sisli/Istanbul • Tel. +90 212 / 210 50 80

TOV ifm electronic • 02660 Kiev • Tel. +380 44 501 8543

ifm efector inc. • Exton, PA 19341 • Tel. +1 610 / 5 24-2000

ifm electronic • Ho Chi Minh city 700000 • Tel. +84-8-35125177

ifm electronic (Pty) Ltd. • 0157 Pretoria • Tel. +27 12 345 44 49

Technische Änderungen behalten wir uns ohne vorherige Ankündigung vor. We reserve the right to make technical alterations without prior notice.

Nous nous réservons le droit de modifier les données techniques sans préavis.