This document is the original instructions�
All trademarks and company names used are subject to the copyright of the respective companies�
3
Page 4
ioControl
1 Preliminary note
This document applies to devices of the type "ioControl" (art� no�: CR2050,
CR2051 and CR2052)�
It is part of the device�
The document contains information about the correct handling of the device�
Adhere to the safety instructions�
Technical data, approvals, accessories and further information at:
www�ifm�com�
1.1 Explanation of symbols
►Instructions
>Reaction, result
[…]Designation of keys, buttons or indications
→Cross-reference
Important note
Non-compliance may result in malfunction or interference�
Information
Supplementary note
WARNING
Warning of serious personal injury�
Death or serious irreversible injuries may result�
CAUTION
Warning of personal injury�
Slight reversible injuries may result�
NOTE
Warning of damage to property�
2 Safety instructions
2.1 General safety instructions
●Read this document before setting up the device and keep it during the entire
service life�
●Ensure that the product is suitable for your application and operating conditions
without any restrictions�
4
Page 5
ioControl
●Improper or non-intended use may lead to malfunctions of the unit, to
unwanted effects in the application or to a loss of the warranty claims�The
manufacturer assumes no liability for any consequences caused by tampering
with the device or incorrect use by the operator�
●Installation, electrical connection, set-up, operation and maintenance of the
unit must be carried out by qualified personnel authorised and trained by the
machine operator�
●After installation, maintenance or repair of the system perform a complete
function check�
●The system installer is responsible for the safety of the system into which the
device is integrated�
2.2 Target group
These instructions are intended for authorised persons according to the EMC
and low-voltage directives� The device must be installed, connected and put into
operation by a qualified electrician�
UK
2.3 Electrical connection
WARNING
Disconnect the device externally before handling it�
Supply via a mobile on-board system 12/24V battery voltage or safety extra-low
voltage (SELV) according to the technical data� The supply is directly transferred to
the connected sensors/actuators�
Accessible surfaces of the housing are insulated from the circuits with basic
insulation to IEC 61010-1, secondary circuit with max� 32 V DC, supplied from
main circuit up to 300 V of overvoltage category II�
The external wiring has to be carried out in a way that ensures the required
separation from other circuits�
The cable cross section is to be adapted to the fuse used, taking into account the
applicable regulations for the application�
The wiring has to be suitable for the max� temperature reached in the application�
If the supplied SELV voltage is externally grounded (SELV becomes PELV), the
responsibility lies with the user and the respective national installation regulations
must be complied with�
The connections may only be supplied with the signals indicated in the technical
data and/or on the device label and only the approved accessories of ifm
electronic gmbh may be connected�
5
Page 6
ioControl
2.4 Tampering with the unit
WARNING
In case of malfunctions or uncertainties please contact the manufacturer� Any
tampering with the device can seriously affect the safety of operators and
machinery�
3 Functions and features
The freely programmable controllers of the "ioControl" series are rated for use
under difficult conditions (e�g� extended temperature range, strong vibration,
intensive EMC interference)� They are suitable for direct installation in mobile
machines, even in wet environments�
By means of the application software the user can configure the inputs and outputs
to adapt to the respective application� The controllers can be used as CANopen
slave, CANopen master or intelligent I/O module (→ 9 Technical data)�
Application-specific extensions and adaptations are possible in conjunction with
additional products of the modular ioControl and ecomatmobile Basic design�
WARNING
The "ioControl" series is not approved for safety tasks in the field of safety of
persons�
NOTE
The "ioControl" controllers are intended for installation in vehicle bodies, not in
engines�
NOTE
The device must only be used within the limits indicated in the technical data
(→ 9 Technical data)� If the device is used in a way that is not intended by the
manufacturer, the protection supported by the device may be impaired�
6
Page 7
ioControl
4 Function
●The user can easily create the application software by means of the IEC 61131-
3 compliant programming system CODESYS 2�3� On delivery the devices are
pre-configured as CANopen slaves�
●2 CAN interfaces
●Configurable inputs/outputs
●Status LEDs, I/O Leds and 4-digit 10-segment display
●Operating keys
More information and accessories at www�ifm�com�
5 Installation
5.1 Mounting surface
NOTE
The housing must not be exposed to any torsional forces or mechanical stress�
► Mount the device on a flat surface�► Use compensating elements if there is no flat mounting surface available�
UK
Mounting surface
5.2 Fixing
► Insert the enclosed tubular rivets from the back of the module in the 3 fixing
Cylinder screws with hexagon socket (M5 x L)DIN EN ISO 4762
Cylinder screws with hexagon socket and low head (M5 x L)DIN 7984
5.3 Cable seal
NOTE
Protection rating IP 65 / IP 67 is only guaranteed if all ports are sealed by means
of connectors or dummy plugs�
8
Page 9
ioControl
Original Scale Drawing (MTD)
1
3
5
6
7
2
4
878
9
10
11
6 Electrical connection
6.1 General electrical connection
The supply cables and the CAN2 interface are connected via the X1 connector
on the bottom of the device� The inputs/outputs, the CAN1 interface and the CAN
supply are connected via the Deutsch connectors on the front side of the housing�
CAN1 OUTCAN1 interface (e�g� for looping through)6
X1Supply voltage and CAN2 interface6
NOTE
Wrong connection may cause damage to the device�
► Observe the safety instructions (→ 2.3 Electrical connection)�
9
Page 10
ioControl
► Basically all supply and signal cables must be laid separately�► Lay supply and signal cables away from the device using the shortest possible
route�
► All connected cables must be provided with a strain relief max� 400 mm behind
the cable entry�
► Cover unused terminals with dummy plugs / seals�
6.2 Connection accessories
Information about the available accessories at www�ifm�com
6.3 Frequency inputs
CR2050 / CR2052:
► Operate frequency inputs with screened cables so that useful signals are not
affected by external interference�
6.4 Reverse polarity protection
Reverse polarity protection of the operating voltage is only ensured in case of
operation on an on-board system in connection with a fuse� In case of operation
via a power supply, there is no reverse polarity protection of the operating voltage�
CR2051: There is no reverse polarity protection of the CAN supply voltage, as this
voltage is not used within the device�
6.5 Supply of the signal generators at the inputs
CR2050 / CR2052:
► Use sensor voltage VBBS of the corresponding connector as supply voltage for
the signal generators at the inputs (e�g� switches or sensors)�
► If the input (switch or sensor) is supplied via an external voltage, protect this
voltage with max� 3 A�
6.6 Fuses
► The individual electric circuits must be protected in order to protect the whole
system�
DesignationPotentialConnector: PinFuse
VBBSSupply sensors/module8���32 V DCAMP connector:
Pin 4
VBB1Supply outputs
CR2050: not available
CR2051: OUT00, 02, 04, 06, 08, 10, 12, 14
CR2052: not available
VBB2Supply outputs
CR2050: not available
CR2051: OUT01, 03, 05, 07, 09, 11, 13, 15
CR2052: OUT00���07
10
8���32 V DCAMP connector:
Pin 4
8���32 V DCAMP connector:
Pin 6
CR2050: 3 A
CR2052: 3 A
CR2050: CR2051: ≤ 25 A
CR2052: -
CR2050: -
CR2051: ≤ 25 A
CR2052: ≤ 25 A
Page 11
DesignationPotentialConnector: PinFuse
Supply
3 A
Supply
ioControl
V
CAN
Optional supply CAN1 interface
CR2050: connected to VBBS
CR2051: no connection to VBBS
CR2052: connected to VBB
S
8���32 V DCCAN IN: Pins 3+4
CR2050: CR2051: 3 A
CR2052: -
► Connect the ground pins belonging to the supply voltages (GND1, GND2, if
appl� GND
) to the common ground�
CAN
6.7 Examples for connection types
6.7.1 CR2050
Example 1
CAN loop,
supply via
CAN IN
03/04V
01/06GND
02/05
CAN
CAN
CAN1
CAN INCAN OUT
*
S
VBB
GND1n.c.
CR2050
01
04
06
03n.c.
02/05 CAN2
CAN
V
CAN
GND
CAN1
* Load-Dump
Protection
UK
03/04
01/06
02/05
Example 2
Supply via
connectorX1
n.c.n.c.
03/04V
01/06GND
02/05
CAN
CAN
CAN1
CAN INCAN OUT
*
S
VBB
GND1n.c.
GND
CAN1
CR2050
01
04
3 A
06
n.c.
03n.c.
02/05 CAN2
CAN
CAN
03/04V
01/06
02/05
* Load-Dump
Protection
11
Page 12
ioControl
Supply
3 A
Supply
Supply
Supply
6.7.2 CR2051
Example 1
CAN loop, low
load, supply
via CAN IN
Example 2
medium load,
common fuse
**additional
protection
required if
common fuse
> 3 A
3 A**
GND
03/04V
01/06GND
02/05
CAN
CAN
GND
CAN1
CAN INCAN OUT
/
*
S
1
VBB
VBB
GND1VBB2GND
2
CAN2
CR2051
06
03/04V
CAN
01/06GND
CAN
04
01
03
02/05
GND
02/05CAN1
CAN INCAN OUT
/
*
S
1
VBB
VBB
GND1VBB2GND
2
CAN2
CR2051
06
04
GND
01
GND
03
02/05
CAN
CAN1
CAN
03/04V
01/06
02/05
* Load-Dump
Protection
CAN
CAN1
CAN
03/04V
01/06
02/05
* Load-Dump
Protection
max. 25 A
Supply
Example 3
max. load
3 A
03/04V
01/06GND
02/05
CR2051
CAN
CAN
CAN1
CAN INCAN OUT
/
*
S
1
VBB
VBB
GND1VBB2GND
2
CAN2
CAN
CAN
GND
CAN1
* Load-Dump
03/04V
01/06
02/05
Protection
04
01
03
02/05
06
GNDGND
15...25 A
max. 25 A
Protection against overvoltage from the vehicle's on-board system is only ensured
if the connection VBBS/VBB1 is protected with at least 15 A (example 3) or if all
voltages are protected by means of a common fuse (examples 1 and 2)�
12
Page 13
6.7.3 CR2052
Supply
3 A
Supply
Supply
ioControl
Example 1
CAN loop, low
load, supply
via CAN IN
Example 2
low load,
common fuse
03/04V
01/06GND
02/05
CAN
CAN
GND
CAN1
CAN INCAN OUT
S
VBB
1
GND
*
2
VBB
2
CR2052
01
04
03/04V
01/06GND
02/05
CAN
CAN
CAN1
CAN INCAN OUT
S
VBB
1
GND
06
*
2
VBB
03GND
2
02/05 CAN2
GND
CR2052
01
04
06
03GND
02/05 CAN2
CAN
V
CAN1
CAN
03/04
01/06
02/05
* Load-Dump
Protection
CAN
V
CAN1
CAN
03/04
01/06
02/05
* Load-Dump
Protection
UK
Example 3
max. load
GNDGND
3 A
Supply
03/04V
01/06GND
02/05
CAN
CAN
GND
CAN1
CAN INCAN OUT
S
VBB
1
GND
*
2
VBB
2
CR2052
01
04
GND
3 A
06
03GND
GND
15...25 A
02/05 CAN2
CAN
V
CAN1
CAN
03/04
01/06
02/05
* Load-Dump
Protection
Protection against overvoltage from the vehicle's on-board system is only ensured
if the connection VBB2 is protected with at least 15 A (example 3) or if all voltages
are protected by means of a common fuse (examples 1 and 2)�
13
Page 14
ioControl
Original Scale Drawing (MTD)
Original Scale Drawing (MTD)
7 Operating and display elements
1
8
7
6
5
4
3
1 2
Indicators
10-segment display (→ 9 Technical data)
1
2
3
1: I/O LEDs (yellow)
2: Power LED (green)
3: Mode LED (green)
4: Application LEDs LED A���LED D (green)
5: Lock LED (green)
6: Diagnostics LED (red)
7: 4-digit 10-segment display
1: UP button
2: DOWN button
3: ENTER button
Operating elements
Pushbutton functions (→ 8.1 I/O module)�
14
Page 15
7.1 Menu structure
The following description of the menu structure refers to the factory
setting as I/O module� When the device is configured as a controller, the
corresponding menu structure has to be defined (see system manual
ioControl)�
1
ioControl
Node ID
Baud rate
Error code 1
Error code 2
Error code 3
Error code 4
+
>10 s
nodE
BAUD
>10 s
uLoc
+
-123
-123
-123
20
50
100
125
250
500
2
UK
1...125
1: Display mode (→ 8.1.1)
2: Editing mode (→ 8.1.2)
List of parameters: (→ 8.1.3)
800
1000
1
Loc
15
Page 16
ioControl
7.2 Status indication of the inputs/outputs (I/O LEDs, yellow)
I/O configuration
(see attached object directory)
0 (not used)Off
1 (digital input BL)OffInput signal FALSE
2 (digital output BH)OffOutput signal FALSE
3 (voltage input 10 V)Off
4 (PWM output)OffPWM = 0
5 (current-controlled output)OffCurrent value ≤ 20 mA
6 (voltage input 32 V, ratiometric)Off
7 (current input 20 mA)Off
LED statusDescription
OnInput signal TRUE
OnOutput signal TRUE
OnPWM > 0
OnCurrent value ≤ 20 mA
2 HzFault at the input
9 (voltage input 32 V)Off
10 (digital input BL)OffInput signal FALSE
OnInput signal TRUE
11 (digital input BL, mit Diagnose)OffInput signal FALSE
OnInput signal TRUE
2 HzFault at the input
12 (digital input BH)OffInput signal FALSE
OnInput signal TRUE
14 (frequency input)Off
2 HzFault at the input
15 (digital output BH, with diagnostics)OffOutput signal FALSE
OnOutput signal TRUE
2 HzFault at the output
16 (digital output BH, with diagnostics,
short-circuit proof and overload protected)
OffOutput signal FALSE
OnOutput signal TRUE
2 HzFault at the output
18 (resistor input)Off
20 (interval measurement)Off
16
2 HzFault at the input
2 HzFault at the input
Page 17
ioControl
8 Set-up
8.1 I/O module
On delivery the device is configured as I/O module�
After power on the 10-segment display indicates the article number of the device,
followed by the set node ID�
8.1.1 Display mode
If the green Lock LED is on, the device is in display mode� The device can only
indicate the set node ID and baud rate and, if appl�, error messages; parameters
cannot be edited�
► Press the DOWN button�
>The device displays the set baud rate�
► Press the DOWN button�
>The device displays error code 1, if applicable�
► Press the DOWN button again�
>Every time the DOWN button is pressed, the device displays another error
code, if applicable�
► Use the UP button to go back�
Max� 4 different error codes can occur and be displayed:
Error codeDescription
SHShort circuit to GND
UK
OPWire break
oLExcessive current
CommCommunication error
If no button is activated for 10 s, the device displays the set node ID�
8.1.2 Parameter setting
► Press UP and DOWN simultaneously for at least 10 s to change to the editing
mode�
>Green Lock LED goes out�
>Parameters can be edited�
>"uLoc" is displayed for 5 s
>"nodE" is displayed
► Press the ENTER button�
>The device displays the set node ID�
17
Page 18
ioControl
>The 1st digit to be edited flashes�
► Use the UP and DOWN buttons to set the requested value�
► Use the ENTER button to go to the next digit�
>The 2nd digit to be edited flashes�
► Use the UP and DOWN buttons to set the requested value�
► Use the ENTER button to go to the next digit�
>The 3rd digit to be edited flashes�
► Use the UP and DOWN buttons to set the requested value�
► Press the ENTER button�
>The set node ID is confirmed�
>"nodE" is displayed
► Press the DOWN button�
>"BAUD" is displayed
► Press the ENTER button�
>The device displays the set baud rate�
► Use the UP and DOWN buttons to set the requested value�
► Press the ENTER button�
>The set baud rate is confirmed�
Changes of the parameters are only applied after a reset of the device�
Exit the editing mode:
► Press UP and DOWN simultaneously for at least 10 s�
>Green Lock LED on�
>Parameters cannot be edited�
>"Loc" is displayed for 5 s, then the set node ID is displayed
If no button is activated for 30 s, the device automatically finishes the editing
mode�
The device can be configured as a controller� The existing menu structure and the
properties as I/O module will be lost�
8.2.1 Programming
The user can easily create the application software by means of the IEC 61131-3
compliant programming system CODESYS 2�3�
WARNING
The user is responsible for the safe function of the application programs which
he created himself� If necessary, he must additionally carry out an approval
by corresponding supervisory and test organisations according to the national
regulations�
UK
For notes on the setting of the CAN ID and the baud rate when used as
CANopen slave, refer to the system manual�
8.3 Required documentation
In addition to the CODESYS programming system, the following documents are
required for programming and set-up of the device:
●Programming manual CODESYS V2�3
(alternatively as online help)
●System manual ioControl
(alternatively as online help)
The manuals can be downloaded from the internet:
www�ifm�com
8.4 Required hardware
If used as mobile controller a CAN interface for connection to a PC or notebook is
required to load the application program to the device�
Example:
●CAN/RS232 USB interface CANfox
●Adapter cable for CANfox
You can find more information about the available accessories at:
www�ifm�com
● Voltage inputs
Input voltage0���10 V or 0���32 V
Resolution12 bits
Accuracy± 1% FS
Input resistance65.6 kΩ (0...10 V), 50.7 kΩ (0...32 V)
Input frequency≤ 500 Hz
● Current inputs, with diagnostic capability
Input current0 … 20 mA
Resolution12 bits
Accuracy± 1% FS
Input resistance400 Ω
Input frequency≤ 500 Hz
At a current of > 23 mA the input is switched to the voltage input!
● Voltage inputs, 0���32 V, ratiometric
Function(U
÷ UB) x 1000 ‰
IN
Value range0���1000 ‰
Input resistance50.7 kΩ
● Binary voltage inputs for positive sensor signals
Switch-on level
Switch-off level< 0�3 U
We reserve the right to make technical alterations without prior notice!20 April 2018CR2050 / page 4
23
Page 24
ioControl
Control systems
CR2050Technical data
Test standards and regulations
CE markEN 61000-6-2Electromagnetic compatibility (EMC)
EN 61000-6-4Electromagnetic compatibility (EMC)
E1 marking*
Climatic testsEN 60068-2-30Damp heat, cyclic
Mechanical testsISO 16750-3Test VII; Vibration, random
Chemical resistanceISO 16750-5:2010AA, AB, BA, BD, CC, DB, DC, DD
UN/ECE-R10Radiation of interference
ISO 7637-2Pulse 1, severity level: IV; function state C
EN 60068-2-78Damp heat, constant
EN 60068-2-52Salt spray test
EN 60068-2-6Vibration, sinusoidal
ISO 16750-3Bump
Noise immunity
Radiation of interference
Immunity with 100 V/m
Pulse 2a, severity level: IV; function state A
Pulse 2b, severity level: IV; function state C
Pulse 3a, severity level: IV; function state A
Pulse 3b, severity level: IV; function state A
Pulse 4, severity level: IV; function state B
Pulse 5, severity level: III; function state C
(data valid for the 24 V system)
Pulse 4, severity level: III; function state C
(data valid for the 12 V system)
upper temperature 55°C, number of cycles: 6
Test temperature 40°C / 93% RH,
Test duration: 21 days
Severity level 3 (vehicle)
Mounting location vehicle body
10���500 Hz; 0�72 mm/10 g; 10 cycles/axis
30 g/6 ms; 24,000 shocks
NoteThe EC declaration of conformity and approvals can be found at:
We reserve the right to make technical alterations without prior notice!20 April 2018CR2050 / page 5
Page 25
CR2050Technical data
Control systems
Original Scale Drawing (MTD)
P_MZ_e100_0092
Wiring
03/04 VBB
02
05
Con. 7
01/06 GND
S
IN14
IN06
1
VBB
IN15
IN07
GND
ioControl
S
03/04
02
05
01/06
Con. 8
1
LED assignment
1: LED IN15
2: LED IN07
3: LED IN13
4: LED IN05
5: LED IN11
6: LED IN03
7: LED IN09
8: LED IN01
9: LED IN08
10: LED IN00
11: LED IN10
12: LED IN02
13: LED IN12
14: LED IN04
15: LED IN14
16: LED IN06
● Semiconductor outputs, positive switching (high side), short-circuit proof and
overload protected�
Diagnosis via current feedback (wire break / overload)
Diagnosis via voltage feedback, pullup resistance can be deactivated (wire
break / short circuit)
Switching voltage8���32 V
Switching current≤ 4
Load resistance≥ 3 Ω (at 12 V DC)
Current measuring range0,02���6 A
● PWM outputs
Output frequency20���250 Hz
Pulse/pause ratio1���1000 ‰
Switching current≤ 4 A
Current measuring range0,02���6 A
● Current-controlled output
Output frequency20���250 Hz
Control range0,02���4 A
Setting resolution1 mA
Max� inrush current≤ 24 A
● Semiconductor outputs, positive switching (high side), short-circuit proof and
overload protected�
Diagnosis via current feedback (wire break / overload)
Diagnosis via voltage feedback, pullup resistance can be deactivated (wire
break / short circuit)
Switching voltage8���32 V
Switching current≤ 2.5
Load resistance≥ 4.8 Ω (at 12 V DC)
Current measuring range0,02���4 A
● PWM outputs
Output frequency20���250 Hz
Pulse/pause ratio1���1000 ‰
Switching current≤ 2.5 A
Current measuring range0,02���4 A
● Current-controlled output
Output frequency20���250 Hz
Control range0�02���2�5 A
Setting resolution1 mA
Max� inrush current≤ 24 A
We reserve the right to make technical alterations without prior notice!
15 Aug 2017
CR2051 / page 5
Control systems
CR2051Technical data
Test standards and regulations
CE markEN 61000-6-2Electromagnetic compatibility (EMC)
EN 61000-6-4Electromagnetic compatibility (EMC)
E1 marking*
UN/ECE-R10Radiation of interference
ISO 7637-2Pulse 1, severity level: IV; function state C
Climatic testsEN 60068-2-30Damp heat, cyclic
EN 60068-2-78Damp heat, constant
EN 60068-2-52Salt spray test
Mechanical testsISO 16750-3Test VII; Vibration, random
EN 60068-2-6Vibration, sinusoidal
ISO 16750-3Bump
Chemical resistanceISO 16750-5:2010AA, AB, BA, BD, CC, DB, DC, DD
Noise immunity
Radiation of interference
Immunity with 100 V/m
Pulse 2a, severity level: IV; function state A
Pulse 2b, severity level: IV; function state C
Pulse 3a, severity level: IV; function state A
Pulse 3b, severity level: IV; function state A
Pulse 4, severity level: IV; function state B
Pulse 5, severity level: III; function state C
(data valid for the 24 V system)
Pulse 4, severity level: III; function state C
(data valid for the 12 V system)
upper temperature 55°C, number of cycles: 6
Test temperature 40°C / 93% RH,
Test duration: 21 days
Severity level 3 (vehicle)
Mounting location vehicle body
10���500 Hz; 0�72 mm/10 g; 10 cycles/axis
30 g/6 ms; 24,000 shocks
NoteThe EC declaration of conformity and approvals can be found at:
We reserve the right to make technical alterations without prior notice!
15 Aug 2017
CR2051 / page 6
CR2051Technical data
Control systems
Con. 7
Con. 8
Con. 5
Con. 6
Con. 3
Con. 4
Con. 1
Con. 2
CAN IN
CAN OUT
X1
Original Scale Drawing (MTD)
P_MZ_e100_0092
Wiring
03/04 n.c.
OUT14
02
OUT06
05
01/06 GND
1
n.c.
OUT15
OUT07
GND
ioControl
03/04
02
05
2
01/06
LED assignment
1: LED OUT15
2: LED OUT07
3: LED OUT13
4: LED OUT05
5: LED OUT11
6: LED OUT03
7: LED OUT09
8: LED OUT01
9: LED OUT08
10: LED OUT00
11: LED OUT10
12: LED OUT02
13: LED OUT12
14: LED OUT04
15: LED OUT14
16: LED OUT06
5 HzApplication stopped due to undervoltage
Permanently onSystem error (fatal error)
● Voltage inputs
Input voltage0���10 V or 0���32 V
Resolution12 bits
Accuracy± 1% FS
Input resistance65.6 kΩ (0...10 V), 50.7 kΩ (0...32 V)
Input frequency≤ 500 Hz
● Current inputs, with diagnostic capability
Input current0 … 20 mA
Resolution12 bits
Accuracy± 1% FS
Input resistance400 Ω
Input frequency≤ 500 Hz
At a current of > 23 mA the input is switched to the voltage input!
● Voltage inputs, 0���32 V, ratiometric
Function(U
÷ UB) x 1000 ‰
IN
Value range0���1000 ‰
Input resistance50.7 kΩ
● Binary voltage inputs for positive sensor signals
Switch-on level
Switch-off level< 0�3 U
● Semiconductor outputs, positive switching (high side), short-circuit proof and
overload protected�
Diagnosis via current feedback (wire break / overload)
Diagnosis via voltage feedback, pullup resistance can be deactivated (wire
break / short circuit)
Switching voltage8���32 V
Switching current≤ 4
A
Load resistance≥ 3 Ω (at 12 V DC)
≥ 6 Ω (at 24 V DC)
Current measuring range0,02���6 A
● PWM outputs
Output frequency20���250 Hz
Pulse/pause ratio1���1000 ‰
Switching current≤ 4 A
Current measuring range0,02���6 A
● Current-controlled output
Output frequency20���250 Hz
Control range0,02���4 A
Setting resolution1 mA
Max� inrush current≤ 24 A
● Semiconductor outputs, positive switching (high side), short-circuit proof and
overload protected�
Diagnosis via current feedback (wire break / overload)
Diagnosis via voltage feedback, pullup resistance can be deactivated (wire
break / short circuit)
Switching voltage8���32 V
Switching current≤ 2.5
A
Load resistance≥ 4.8 Ω (at 12 V DC)
≥ 9.6 Ω (at 24 V DC)
Current measuring range0,02���4 A
● PWM outputs
Output frequency20���250 Hz
Pulse/pause ratio1���1000 ‰
Switching current≤ 2.5 A
Current measuring range0,02���4 A
● Current-controlled output
Output frequency20���250 Hz
Control range0�02���2�5 A
Setting resolution1 mA
Max� inrush current≤ 24 A
Free wheel diodesFree wheel diodes for the deactivation of inductive loads are integrated
Overload protection
≤ 5 minutes (at 100% overload)
(valid for all outputs)
Short-circuit protection
≤ 5 minutes
(valid for all inputs and outputs)
Max� total current of the CAN supply +
sensor supplies V
We reserve the right to make technical alterations without prior notice!
CR2052 / page 5
15 Aug 2017
Page 37
CR2052Technical data
Control systems
Test standards and regulations
CE markEN 61000-6-2Electromagnetic compatibility (EMC)
EN 61000-6-4Electromagnetic compatibility (EMC)
E1 marking*
Climatic testsEN 60068-2-30Damp heat, cyclic
Mechanical testsISO 16750-3Test VII; Vibration, random
Chemical resistanceISO 16750-5:2010AA, AB, BA, BD, CC, DB, DC, DD
UN/ECE-R10Radiation of interference
ISO 7637-2Pulse 1, severity level: IV; function state C
EN 60068-2-78Damp heat, constant
EN 60068-2-52Salt spray test
EN 60068-2-6Vibration, sinusoidal
ISO 16750-3Bump
Noise immunity
Radiation of interference
Immunity with 100 V/m
Pulse 2a, severity level: IV; function state A
Pulse 2b, severity level: IV; function state C
Pulse 3a, severity level: IV; function state A
Pulse 3b, severity level: IV; function state A
Pulse 4, severity level: IV; function state B
Pulse 5, severity level: III; function state C
(data valid for the 24 V system)
Pulse 4, severity level: III; function state C
(data valid for the 12 V system)
upper temperature 55°C, number of cycles: 6
Test temperature 40°C / 93% RH,
Test duration: 21 days
Severity level 3 (vehicle)
Mounting location vehicle body
10���500 Hz; 0�72 mm/10 g; 10 cycles/axis
30 g/6 ms; 24,000 shocks
ioControl
UK
NoteThe EC declaration of conformity and approvals can be found at:
We reserve the right to make technical alterations without prior notice!
CR2052 / page 6
15 Aug 2017
37
Page 38
ioControl
Control systems
Original Scale Drawing (MTD)
P_MZ_e100_0092
CR2052Technical data
Wiring
03/04 VBB
02
05
Con. 7
01/06 GND
S
IN07
IN03
1
n.c.
OUT07
OUT03
GND
03/04
02
05
01/06
Con. 8
2
LED assignment
Con. 5
Con. 3
Con. 1
CAN IN
1: LED OUT07
2: LED OUT03
3: LED OUT06
4: LED OUT02
5: LED OUT05
6: LED OUT01
7: LED OUT04
8: LED OUT00
9: LED IN04
10: LED IN00
11: LED IN05
12: LED IN01
13: LED IN06
14: LED IN02
15: LED IN07
16: LED IN03
We reserve the right to make technical alterations without prior notice!
38
R
FRQ
B
H
B
L
PWM
PWM
VBBS
VBB
V
CAN
Analogue
Resistor input
Frequency / pulse input
Binary high side
Binary low side
Pulse width modulation
Pulse width modulation, current-controlled
I
Supply sensors/module
Supply OUT01���OUT07
2
Supply CAN connector
CR2052 / page 7
15 Aug 2017
Page 39
ioControl
10 Maintenance, repair and disposal
10.1 Maintenance
The device does not contain any components that need to be maintained by the
user�
10.2 Cleaning the housing surface
► Disconnect the device�► Clean the device from dirt using a soft, chemically untreated and dry cloth�► In case of heavy dirt, use a damp cloth�
The following agents are not suited for cleaning the device:
Chemicals dissolving plastics such as isopropanol, methylated spirit,
benzine, thinner, alcohol, acetone or ammonia�
Micro-fibre cloths without chemical additives are recommended�
UK
10.3 Repair
► The device must only be repaired by the manufacturer�
Observe the safety instructions (→ 2.4 Tampering with the unit)
10.4 Disposal
► Dispose of the device in accordance with the national environmental
regulations�
11 Approvals/standards
Test standards and regulations (→ 9 Technical data)
The EC declaration of conformity and approvals can be found at:
www�ifm�com
39
Page 40
ioControl
12 Appendix
12.1 EMCY Object
The following error codes according to DSP-401 or DSP-301 are supported:
EMCY codeError regAdditional codeDescription
0x61000x110x00Internal Software
Overflow of an Rx queue e�g� frequency of the Rx
PDOs is too high�
Reset only externally via entry in the index 0x1003
SubIdx 00�
0x61010x110x00Internal Software
Overflow of a Tx queue e�g� device does not
communicate with the bus�
Reset only externally via entry in the index 0x1003
SubIdx 00�
0x81000x110x00Monitoring (Guarding Error)
No guard object is received for „guard time“ x „life time
factor“�
Reset with the next communication�
0x82000x110x00Monitoring (Synch Error)
For "communication cycle" no synch object is received
Only in OPEATIONAL�
Reset with the next synch OBJ or PREOP�
CANopen does not provide for two identical EMCY objects to be sent
consecutively�
12.2 Object directory CR205x
Obligatory objects (index 0x1000…0x1FFF):
IndexS-idxDesignationData typeDefaultDetails
0x1001Device typeroUDINT0x000F0191Device type
0x1001Error registerroUSINT0Error register bitcoded to profile
301
Permissible values:
0b0000 0000 = no error
0b0000 0001 = generic error
0b0001 0000 = communication
error
0b1000 0000 = manufacturer
specific
40
Page 41
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x10180x00Device
identification
Number of
entries
0x01Vendor-IDroUDINT0x0069666DVendor ID oft he device according
0x02Product coderoSTRING0Product code of the device
0x03Revision
number
0x04Serial
number
0x10030x00Predefined
error field
Number of
entries
0x01Error historyroUDINT0Error occured, coded according to
roUSINT0x04Device identification
to CiA specifikation
roUDINT0Revision number of the device
UK
roUDINT0Serial number of the device
rwUDINT0An error list with 4 entries is
supported
EMCY list
The last error is indicated in the
sub-index 1
0x02Error historyroUDINT0Error occured, coded according to
0x03Error historyroUDINT0Error occured, coded according to
0x04Error historyroUDINT0Error occured, coded according to
0x05Error historyroUDINT0Error occured, coded according to
0x1005COB-ID
synch
message
0x1006Communi-
cation cycle
period
EMCY list
EMCY list
EMCY list
EMCY list
rwUDINT0x0000 0080Identifier of the synch message
Bit 30 = 0 → device generates no
synch message
Bit 30 = 1 → device generates a
synch message
Bit 29 = 0 → 11 bit ID
Bit 29 = 1 → ID = 0x80 + node ID
rwUDINT0Max� time between 2 synch objects
in [µs]
Control resolution = 1 ms
0x1008Manufacturer
device name
0x1009Manufacturer
hardware
version
roSTRINGCR205xDevice designation (CR2050 or
CR2051 or CR2052)
roSTRINGV00�00�00Hardware version
41
Page 42
ioControl
IndexS-idxDesignationData typeDefaultDetails
0x100AManufacturer
roSTRINGV00�00�00Software version
software
version
0x100CGuard timerwUINT0Within this time in [ms] the device
expects a „node guarding“ of the
master oft he system�
0 = this function is not supported�
The monitoring oft he node
with „node guarding“ or „heartbeat“ is only possible as an
alternative!
0x100DLifetime
factor
rwUSINT0If for „guard time“ • “lifetime” no
"node guarding" was received, the
device switches off the outputs�
The device changes the CANopen
status to PREOP�
Default: "guard time" • "lifetime" =
0���65535
0x10100x00Store para-
roUSINT0x01Number of “save options”
meters
Largest
sub-index
supported
0x01Save all
parameters
0x10110x00Restore
default
parameters
Largest
sub-index
supported
0x01Restore
all default
parameters
0x1014COBId
Emergency
rwUDINT2Automatic saving of all parameters
changed
0 = AutoSave OFF
2 = AutoSave ON
roUSINT0x01Number of "restore options"
rwUDINT0x01If the String "load" is entered here,
the default parameters set at the
factory are restored and become
valid after the next reset�
rwUDINT0x80 + node IDBit 31 = 0 → EMCY is valid
Bit 31 = 1 → EMCY is not valid
Bit 29 = 0 → 11-bit ID
Bit 29 = 1 → ID = 0x80 + node ID
CAN identifier can be changed by
the user�
42
Page 43
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x10160x00Consumer
heartbeat
times
Nums
consumer
heartbeat
time
0x01Consumer
heartbeat
time
0x1017Producer
heartbeat
time
roUSINT0x01Heartbeat monitoring time for the
node
Number of devices monitored = 1
rwUDINT0Heartbeat monitoring time for the
node
Format: 0x0nntttt
tttt = monitoring time [ms]
nn = node number
if nn=0 or tttt=0 → no monitoring
The monitoring of the node
with „node guarding“ or „heartbeat“ is only possible as an
alternative!
rwUINT0Time intervall [ms] during which
the device generates a producer
heartbeat
UK
43
Page 44
ioControl
12.2.1 Device-specic CR2050
Transmit PDO communication parameters (index 0x1800…0x18FF):
IndexS-idxDesignationData typeDefaultDetails
0x18000x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 1
number of entries = 5
rwUDINT0x180 +
Node ID
rwUSINT0xFF0x00 = synch acyclic
CAN ID of the transmit PDO 1
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
44
Page 45
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x18010x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 2
number of entries = 5
rwUDINT0x280 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 2
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
UK
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
45
Page 46
ioControl
IndexS-idxDesignationData typeDefaultDetails
0x18020x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 3
number of entries = 5
rwUDINT0x380 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 3
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
46
Page 47
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x18030x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 4
number of entries = 5
rwUDINT0x480 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 4
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
UK
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
47
Page 48
ioControl
IndexS-idxDesignationData typeDefaultDetails
0x18040x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 5
number of entries = 5
rwUDINT0x181 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 5
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
48
Page 49
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x18050x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 6
number of entries = 5
rwUDINT0x281 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 6
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
UK
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
49
Page 50
ioControl
IndexS-idxDesignationData typeDefaultDetails
0x18060x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 7
number of entries = 5
rwUDINT0x381 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 7
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
50
Page 51
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x18070x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 8
number of entries = 5
rwUDINT0x481 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 8
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
UK
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
51
Page 52
ioControl
IndexS-idxDesignationData typeDefaultDetails
0x18080x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 9
number of entries = 5
rwUDINT0x182 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 9
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
52
Page 53
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x18090x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 10
number of entries = 5
rwUDINT0x282 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 10
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
UK
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
53
Page 54
ioControl
Transmit PDO mapping (index 0x1A00…0x1AFF):
IndexS-idxDesignationData typeDefaultDetails
0x1A000x00Transmit
PDO mapping
Number of
mapped
objects in
PDO
0x01PDO map-
ping
0x02PDO map-
ping
0x03PDO map-
ping
0x04PDO map-
ping
0x05PDO map-
ping
rwUSINT0x07mapping transmit PDO 1
number of integrated application
objects = 7
rwUDINT0x6000 0108Index 0x6000, SubIndex 0x01
binary inputs 00���07: actual values
(bit coded)
rwUDINT0x6000 0208Index 0x6000, SubIndex 0x02
binary inputs 08…15: actual values
(bit coded)
rwUDINT0x2020 0108Index 0x2020, SubIndex 0x01
binary inputs 00���07: flag "short
circuit" (bit coded)
rwUDINT0x2020 0208Index 0x2020, SubIndex 0x02
binary inputs 08…15: flag "short
circuit" (bit coded)
rwUDINT0x2021 0108Index 0x2021, SubIndex 0x01
outputs 00���07: flag " wire break " (bit
coded)
0x06PDO map-
ping
0x07PDO map-
ping
rwUDINT0x2021 0208Index 0x2021, SubIndex 0x02
outputs 08…15: flag " wire break "
(bit coded)
rwUDINT0x2025 0108Index 0x2025, SubIndex 0x01
inputs 00���03: flag " overload " (bit
coded)
54
Page 55
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x1A010x00Transmit
PDO mapping
Number of
mapped
objects in
PDO
0x01PDO map-
ping
0x02PDO map-
ping
0x03PDO map-
ping
0x04PDO map-
ping
rwUSINT0x04mapping transmit PDO 2 (analogue
inputs)
number of integrated application
objects = 4
rwUDINT0x6404 0110Index 0x6404, SubIndex 0x01
analogue input 00: actual value
(depending on the configuration
0x2000)
rwUDINT0x6404 0210Index 0x6404, SubIndex 0x02
analogue input 01: actual value
(depending on the configuration
0x2000))
rwUDINT0x6404 0310Index 0x6404, SubIndex 0x03
analogue input 02: actual value
(depending on the configuration
0x2000)
rwUDINT0x6404 0410Index 0x6404, SubIndex 0x04
analogue input 03: actual value
(depending on the configuration
0x2000)
UK
0x1A020x00Transmit
PDO mapping
Number of
mapped
objects in
PDO
0x01PDO map-
ping
0x02PDO map-
ping
0x03PDO map-
ping
0x04PDO map-
ping
rwUSINT0x04mapping transmit PDO 3 (analogue
inputs)
number of integrated application
objects = 4
rwUDINT0x6404 0510Index 0x6404, SubIndex 0x05
analogue input 04: actual value
(depending on the configuration
0x2000)
rwUDINT0x6404 0610Index 0x6404, SubIndex 0x06
analogue input 05: actual value
(depending on the configuration
0x2000))
rwUDINT0x6404 0710Index 0x6404, SubIndex 0x07
analogue input 06: actual value
(depending on the configuration
0x2000)
rwUDINT0x6404 0810Index 0x6404, SubIndex 0x08
analogue input 07: actual value
(depending on the configuration
0x2000)
55
Page 56
ioControl
IndexS-idxDesignationData typeDefaultDetails
0x1A030x00Transmit
PDO mapping
Number of
mapped
objects in
PDO
0x01PDO map-
ping
0x02PDO map-
ping
0x03PDO map-
ping
0x04PDO map-
ping
0x1A040x00Transmit
PDO mapping
Number of
mapped
objects in
PDO
rwUSINT0x04mapping transmit PDO 4
number of integrated application
objects = 4
rwUDINT0x2030 0110Index 0x2030, SubIndex 0x01
input 08: actual resistor value
rwUDINT0x2030 0210Index 0x2030, SubIndex 0x02
input 10: actual resistor value
rwUDINT0x2030 0310Index 0x2030, SubIndex 0x03
input 12: actual resistor value
rwUDINT0x2030 0410Index 0x2030, SubIndex 0x04
input 14: actual resistor value
rwUSINT0x02mapping transmit PDO 5 (periode
time IN09, IN11)
number of integrated application
objects = 2
0x01PDO map-
ping
0x02PDO map-
ping
0x1A050x00Transmit
PDO mapping
Number of
mapped
objects in
PDO
0x01PDO map-
ping
0x02PDO map-
ping
rwUDINT0x2012 0120Index 0x2012, SubIndex 0x01
frequency input IN09: periode time of
the signal
rwUDINT0x2012 0220Index 0x2012, SubIndex 0x02
frequency input IN11: periode time of
the signal
rwUSINT0x02mapping transmit PDO 6 (periode
time IN13, IN15)
number of integrated application
objects = 2
rwUDINT0x2012 0320Index 0x2012, SubIndex 0x03
frequency input IN13: periode time of
the signal
rwUDINT0x2012 0420Index 0x2012, SubIndex 0x04
frequency input IN15: periode time of
the signal
56
Page 57
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x1A060x00Transmit
PDO mapping
Number of
mapped
objects in
PDO
0x01PDO map-
ping
0x02PDO map-
ping
0x03PDO map-
ping
0x04PDO map-
ping
0x1A070x00Transmit
PDO mapping
Number of
mapped
objects in
PDO
rwUSINT0x04mapping transmit PDO 7 (duty cycle
of the signal on the frequency input
IN09, IN11, IN13, IN15)
number of integrated application
objects = 4
rwUDINT0x2014 0110Index 0x2014, SubIndex 0x01
frequency input IN09: duty cycle of
the signal in ‰
rwUDINT0x2014 0210Index 0x2014, SubIndex 0x02
frequency input IN11: duty cycle of
the signal in ‰
rwUDINT0x2014 0310Index 0x2014, SubIndex 0x03
frequency input IN13: duty cycle of
the signal in ‰
rwUDINT0x2014 0410Index 0x2014, SubIndex 0x04
frequency input IN15: duty cycle of
the signal in ‰
rwUSINT0x02mapping transmit PDO 8 (frequency
on IN09, IN11)
number of integrated application
objects = 2
UK
0x01PDO map-
ping
0x02PDO map-
ping
0x1A080x00Transmit
PDO mapping
Number of
mapped
objects in
PDO
0x01PDO map-
ping
0x02PDO map-
ping
rwUDINT0x2015 0120Index 0x2015, SubIndex 0x01
frequency input IN09: frequency
value of the signal in Hz
rwUDINT0x2015 0220Index 0x2015, SubIndex 0x02
frequency input IN11: frequency value
of the signal in Hz
rwUSINT0x02mapping transmit PDO 9 (frequency
on IN13, IN15)
number of integrated application
objects = 2
rwUDINT0x2015 0320Index 0x2015, SubIndex 0x03
frequency input IN13: frequency
value of the signal in Hz
rwUDINT0x2015 0420Index 0x2015, SubIndex 0x04
frequency input IN15: frequency
value of the signal in Hz
57
Page 58
ioControl
IndexS-idxDesignationData typeDefaultDetails
0x1A090x00Transmit
PDO mapping
Number of
mapped
objects in
PDO
0x01PDO map-
ping
0x02PDO map-
ping
rwUSINT0x02mapping transmit PDO 10 (system
flag)
number of integrated application
objects = 2
PWM outputs OUT00…OUT03
number of integrated application
objects = 4
rwUDINT0x6414 0110PWM/current output OUT00
Index 0x6414, SubIndex 0x01
contains the preset value of the
PWM output OUT00, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
rwUDINT0x6414 0210PWM/ current output OUT01
Index 0x6414, SubIndex 0x02
contains the preset value of the
PWM output OUT01, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
rwUDINT0x6414 0310PWM/ current output OUT02
Index 0x6414, SubIndex 0x03
contains the preset value of the
PWM output OUT02, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
0x04PDO map-
ping
rwUDINT0x6414 0410PWM/ current output OUT03
Index 0x6414, SubIndex 0x04
contains the preset value of the
PWM output OUT03, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
68
Page 69
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x16020x00"Receive
PDO mapping
Number of
mapped
objects in
PDO"
0x01PDO map-
ping
0x02PDO map-
ping
0x03PDO map-
ping
rwUSINT0x04Mapping read PDO 3:
PWM outputs OUT04…OUT07
number of integrated application
objects = 4
rwUDINT0x6414 0510PWM/ current output OUT04
Index 0x6414, SubIndex 0x05
contains the preset value of the
PWM output OUT04, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
rwUDINT0x6414 0610PWM/ current output OUT05
Index 0x6414, SubIndex 0x06
contains the preset value of the
PWM output OUT05, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
rwUDINT0x6414 0710PWM/ current output OUT06
Index 0x6414, SubIndex 0x07
contains the preset value of the
PWM output OUT06, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
UK
0x04PDO map-
ping
rwUDINT0x6414 0810PWM/ current output OUT07
Index 0x6414, SubIndex 0x08
contains the preset value of the
PWM output OUT07, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
69
Page 70
ioControl
IndexS-idxDesignationData typeDefaultDetails
0x16030x00Receive PDO
mapping
Number of
mapped
objects in
PDO
0x01PDO map-
ping
0x02PDO map-
ping
0x03PDO map-
ping
rwUSINT0x04Mapping read PDO 4:
PWM outputs OUT08…OUT11
number of integrated application
objects = 4
rwUDINT0x6414 0910PWM/ current output OUT08
Index 0x6414, SubIndex 0x09
contains the preset value of the
PWM output OUT08, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
rwUDINT0x6414 0A10PWM/ current output OUT09
Index 0x6414, SubIndex 0x0A
contains the preset value of the
PWM output OUT09, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
rwUDINT0x6414 0B10PWM/ current output OUT10
Index 0x6414, SubIndex 0x0B
contains the preset value of the
PWM output OUT10, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
0x04PDO map-
ping
rwUDINT0x6414 0C10PWM/ current output OUT11
Index 0x6414, SubIndex 0x0C
contains the preset value of the
PWM output OUT11, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
70
Page 71
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x16040x00Receive PDO
mapping
Number of
mapped
objects in
PDO
0x01PDO map-
ping
0x02PDO map-
ping
0x03PDO map-
ping
rwUSINT0x04Mapping read PDO 5:
PWM outputs OUT12…OUT15
number of integrated application
objects = 4
rwUDINT0x6414 0D10PWM/ current output OUT12
Index 0x6414, SubIndex 0x0D
contains the preset value of the
PWM output OUT12, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
rwUDINT0x6414 0E10PWM/ current output OUT13
Index 0x6414, SubIndex 0x0E
contains the preset value of the
PWM output OUT13, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
rwUDINT0x6414 0F10PWM/ current output OUT14
Index 0x6414, SubIndex 0x0F
contains the preset value of the
PWM output OUT14, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
UK
0x04PDO map-
ping
rwUDINT0x6414 1010PWM/ current output OUT15
Index 0x6414, SubIndex 0x10
contains the preset value of the
PWM output OUT15, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
71
Page 72
ioControl
Transmit PDO communication parameters (index 0x1800…0x18FF):
IndexS-idxDesignationData typeDefaultDetails
0x18000x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 1
number of entries = 5
rwUDINT0x180 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 1
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
72
Page 73
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x18010x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 2
number of entries = 5
rwUDINT0x280 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 2
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
UK
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
73
Page 74
ioControl
IndexS-idxDesignationData typeDefaultDetails
0x18020x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 3
number of entries = 5
rwUDINT0x380 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 3
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
74
Page 75
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x18030x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 4
number of entries = 5
rwUDINT0x480 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 4
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
UK
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
75
Page 76
ioControl
Transmit PDO mapping (index 0x1A00…0x1AFF):
IndexS-idxDesignationData typeDefaultDetails
0x1A000x00Transmit
PDO mapping
Number of
mapped
objects in
PDO
0x01PDO map-
ping
0x02PDO map-
ping
0x03PDO map-
ping
0x04PDO map-
ping
0x1A010x00Transmit
PDO mapping
Number of
mapped
objects in
PDO
rwUSINT0x04mapping transmit PDO 01 (output
current OUT00���OUT03)
number of integrated application
objects = 4
rwUDINT0x2002 0110Index 0x2002, SubIndex 0x01
current on output OUT00
rwUDINT0x2002 0210Index 0x2002, SubIndex 0x02
current on output OUT01
rwUDINT0x2002 0310Index 0x2002, SubIndex 0x03
current on output OUT02
rwUDINT0x2002 0410Index 0x2002, SubIndex 0x04
current on output OUT03
rwUSINT0x04mapping transmit PDO 02 (output
current OUT04���OUT07)
number of integrated application
objects = 4
0x01PDO map-
ping
0x02PDO map-
ping
0x03PDO map-
ping
0x04PDO map-
ping
rwUDINT0x2002 0510Index 0x2002, SubIndex 0x05
current on output OUT04
rwUDINT0x2002 0610Index 0x2002, SubIndex 0x06
current on output OUT05
rwUDINT0x2002 0710Index 0x2002, SubIndex 0x07
current on output OUT06
rwUDINT0x2002 0810Index 0x2002, SubIndex 0x08
current on output OUT07
76
Page 77
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x1A020x00Transmit
PDO mapping
Number of
mapped
objects in
PDO
0x01PDO map-
ping
0x02PDO map-
ping
0x03PDO map-
ping
0x04PDO map-
ping
0x05PDO map-
ping
rwUSINT0x05mapping transmit PDO 3
number of integrated application
objects = 5
rwUDINT0x2022 0108Index 0x2022, SubIndex 0x01
outputs 00���07: flag " short circuit "
(bit coded)
rwUDINT0x2022 0208Index 0x2022, SubIndex 0x02
outputs 08…15: flag " short circuit "
(bit coded)
rwUDINT0x2023 0108Index 0x2023, SubIndex 0x01
outputs 00���07: flag " wire break " (bit
coded)
rwUDINT0x2023 0208Index 0x2023, SubIndex 0x02
outputs 08���015: flag " wire break "
(bit coded)
rwUDINT0x2024 0108Index 0x2024, SubIndex 0x01
outputs 00���07: flag " overload " (bit
coded)
UK
0x1A030x00Transmit
PDO mapping
Number of
mapped
objects in
PDO
0x01PDO map-
ping
0x02PDO map-
ping
0x03PDO map-
ping
0x04PDO map-
ping
rwUSINT0x04mapping transmit PDO 4 (system
flag)
number of integrated application
objects = 4
PWM outputs OUT00…OUT03
number of integrated application
objects = 4
rwUDINT0x6414 0110PWM/current output OUT00
Index 0x6414, SubIndex 0x01
contains the preset value of the
PWM output OUT00, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
rwUDINT0x6414 0210PWM/ current output OUT01
Index 0x6414, SubIndex 0x02
contains the preset value of the
PWM output OUT01, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
rwUDINT0x6414 0310PWM/ current output OUT02
Index 0x6414, SubIndex 0x03
contains the preset value of the
PWM output OUT02, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
UK
0x04PDO map-
ping
rwUDINT0x6414 0410PWM/ current output OUT03
Index 0x6414, SubIndex 0x04
contains the preset value of the
PWM output OUT03, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
91
Page 92
ioControl
IndexS-idxDesignationData typeDefaultDetails
0x16020x00Receive PDO
mapping
Number of
mapped
objects in
PDO
0x01PDO map-
ping
0x02PDO map-
ping
0x03PDO map-
ping
rwUSINT0x04Mapping read PDO 3:
PWM outputs OUT04…OUT07
number of integrated application
objects = 4
rwUDINT0x6414 0510PWM/ current output OUT04
Index 0x6414, SubIndex 0x05
contains the preset value of the
PWM output OUT04, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
rwUDINT0x6414 0610PWM/ current output OUT05
Index 0x6414, SubIndex 0x06
contains the preset value of the
PWM output OUT05, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
rwUDINT0x6414 0710PWM/ current output OUT06
Index 0x6414, SubIndex 0x07
contains the preset value of the
PWM output OUT06, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
0x04PDO map-
ping
rwUDINT0x6414 0810PWM/ current output OUT07
Index 0x6414, SubIndex 0x08
contains the preset value of the
PWM output OUT07, the value is
interpreted as duty cycle in ‰ or as
target current value (depending on
the configuration index 0x2000)
92
Page 93
Transmit PDO communication parameters (index 0x1800…0x18FF):
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x18000x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 1
number of entries = 5
rwUDINT0x180 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 1
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
UK
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
93
Page 94
ioControl
IndexS-idxDesignationData typeDefaultDetails
0x18010x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 2
number of entries = 5
rwUDINT0x280 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 2
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
94
Page 95
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x18020x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 3
number of entries = 5
rwUDINT0x380 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 3
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
UK
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
95
Page 96
ioControl
IndexS-idxDesignationData typeDefaultDetails
0x18030x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 4
number of entries = 5
rwUDINT0x480 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 4
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
96
Page 97
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x18040x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 5
number of entries = 5
rwUDINT0x181 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 5
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
UK
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
97
Page 98
ioControl
IndexS-idxDesignationData typeDefaultDetails
0x18050x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 6
number of entries = 5
rwUDINT0x281 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 6
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
98
Page 99
IndexS-idxDesignationData typeDefaultDetails
ioControl
0x18060x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 7
number of entries = 5
rwUDINT0x381 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 7
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
UK
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
99
Page 100
ioControl
IndexS-idxDesignationData typeDefaultDetails
0x18070x00Transmit
PDO Communication
Parameter
Number of
entries
0x01COBID used
by PDO
0x02transmission
type
0x03inhibit timerwUINT0delay time in the transmission
roUSINT0x05Configuration transmit PDO 8
number of entries = 5
rwUDINT0x481 +
Node ID
rwUSINT0x010x00 = synch acyclic
CAN ID of the transmit PDO 8
Bit 31 = 0 → PDO is valid
Bit 31 = 1 → PDO is not valid
0x01���0xF0 = synch cyclic; values
are only transmitted after „n" synch
objects
n = 1…240 = 0x01���0xF0
0xFC/0xFD not implemented
0xFE = asynch man� spec� event;
values are immediately transferred
0xFF = asynch device profile event;
values are immediately transferred
type "asynch" before the PDO is
transmitted again at the earliest�
(0���65535 • 100 µs)
0x04reservedrwUSINT0reserve
0x05event timerwUINT0max� transfer break in the transmissi-
on type „asynch" (0���65535 ms)
When this time has elapsed, the PDO
is transferred even if the appl� event
has not accured�
100
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.