Kuhnke Electronics Instruction Manual

Kuhnke Electronics
Instruction Manual
Ventura Remote PLC DP
Ventura Remote PLC Can
E 700 GB 31.05.07 / 105.238

This instruction manual is primarily intended for use by design, project and
development engineers. It does not contain any availability information.
Data is only given to describe the product and must not be regarded as
guaranteed properties in the legal sense. Any claims for damages - on
whatever legal grounds - are excluded except for instances of deliberate
intent or gross negligence on our part.
We reserve the rights for errors, omissions and modifications.
Reproduction even of extracts only with the editor's express and written
prior consent.

Table of Contents
Introduction
1 Introduction ................................................................................................9
1.1 Area of Application .......................................................................10
1.2 Variants ........................................................................................11
1.3 From Stand-alone Controllers to Distributed Networks................12
1.4 Ventura Remote PLC as a Field Bus Unit....................................14
1.5 Network Examples .......................................................................15
1.5.1 PROFIBUS-DP ...........................................................................15
1.5.2 CANopen ....................................................................................16
2 Reliability, Safety .....................................................................................17
2.1 Intended Use ................................................................................17
2.2 Target Group ................................................................................17
2.3 Reliability ......................................................................................17
2.4 Symbols........................................................................................18
2.4.1 Danger........................................................................................18
2.4.2 Attention .....................................................................................18
2.4.3 Note ............................................................................................19
2.4.4 Under Construction.....................................................................19
2.4.5 Instruction ...................................................................................19
2.5 Safety ...........................................................................................20
2.5.1 Project Planning and Installation ................................................21
2.5.2 Maintenance and Servicing ........................................................22
2.6 Electromagnetic Compatibility......................................................23
2.6.1 Definition.....................................................................................23
2.6.2 Interference Emission.................................................................23
2.6.3 General Notes on Installation .....................................................23
2.6.4 Electrical Immission Safeguard ..................................................24
2.6.5 Cable Routing and Wiring ..........................................................24
2.6.6 Location of Installation................................................................24
2.6.7 Particular Sources of Interference..............................................25
3 Hardware .................................................................................................27
3.1 System Description ......................................................................27
3.2 Mechanical Design .......................................................................28
3

Introduction
3.2.1 Dimensions.................................................................................28
3.2.2 Installation ..................................................................................30
3.3 Power Supply ...............................................................................31
3.3.1 Earth ...........................................................................................31
3.3.2 Wiring .........................................................................................32
3.3.3 Power Supply .............................................................................33
3.4 Inputs and Outputs .......................................................................35
3.4.1 Digital I/Os, Basic Module ..........................................................35
3.4.2 Digital Combi I/Os.......................................................................37
3.4.3 Analogue Inputs..........................................................................39
3.4.4 Analogue Outputs.......................................................................40
3.5 A, B, Ref Counter .........................................................................41
3.6 Communication Ports ...................................................................42
3.6.1 V.24 / com ..................................................................................42
3.6.2 PROFIBUS .................................................................................43
3.6.3 CAN ............................................................................................44
3.7 Expansion Modules ......................................................................45
3.8 Modes of Operation......................................................................46
3.8.1 External Non-volatile Memory Card (MMC) ...............................46
3.8.2 Mode Selector ............................................................................47
3.8.3 Modes Overview.........................................................................48
3.9 Status and Failure Indication........................................................51
3.10 Memory.........................................................................................52
3.11 Multimedia Card (MMC) ...............................................................52
4 PLC Functions of Ventura Remote PLC..................................................53
4.1 CoDeSys Target Installation.........................................................53
4.2 Writing CoDeSys Programs Online..............................................55
4.2.1 Serial (RS232) Online-V.24........................................................55
4.2.2 CAN: Online CAN.......................................................................57
4.3 Method of PLC Operation.............................................................58
4.3.1 Operating System.......................................................................59
4.3.2 The CoDeSys Runtime System..................................................59
4.3.3 Task Configuration .....................................................................61
4 E 700 GB

Introduction
4.3.4 PLC Configuration ......................................................................65
4.3.5 The User Program ......................................................................68
4.3.6 The Flash File System................................................................69
4.4 Function Library P690.lib/C690.lib ...............................................70
4.4.1 Installing a Thread......................................................................71
4.4.2 Installing / Uninstalling a Timer Task..........................................75
4.4.3 Enabling / Disabling the Outputs ................................................79
4.4.4 Direct Read of Local Inputs ........................................................80
4.4.5 Direct Write of Local Outputs .....................................................81
4.4.6 Installing an Error Module ..........................................................82
4.4.7 Installing an Input IRQ Module ...................................................84
4.4.8 Installing a REF IRQ Module......................................................87
4.4.9 Installing a Reference Value IRQ Module ..................................88
4.4.10 Setting up the Watchdog ..........................................................89
4.5 Library MMC.LIB ..........................................................................91
4.5.1 Procedure ...................................................................................92
4.5.2 Registering with the File System ................................................93
4.5.3 Closing a File..............................................................................94
4.5.4 Copying Files..............................................................................95
4.5.5 Deleting a File.............................................................................96
4.5.6 Determining the Free MMC Space.............................................97
4.5.7 Creating a Subdirectory..............................................................98
4.5.8 Moving a File ..............................................................................99
4.5.9 Opening a File ..........................................................................101
4.5.10 Reading from a File ................................................................103
4.5.11 Renaming a File .....................................................................104
4.5.12 Setting the Edit Bookmark of a File........................................105
4.5.13 Writing to a File.......................................................................106
4.5.14 Initialising the File System......................................................107
4.5.15 Opening, Reading, Closing a File...........................................108
4.5.16 Opening, Writing, Closing a File.............................................110
4.6 PLC States .................................................................................112
4.6.1 RUN..........................................................................................112
5

Introduction
4.6.2 STOP........................................................................................112
4.6.3 Online Reset.............................................................................112
4.6.4 Online Reset (cold)...................................................................113
4.6.5 Reset (original) .........................................................................113
4.7 Programming Using CoDeSys ...................................................114
4.7.1 Variables/Addresses.................................................................114
4.7.2 Variables with Set Addresses...................................................115
4.8 Extraremanent Data ...................................................................117
4.8.1 Remanence Compliant to IEC 11631-3....................................117
4.8.2 Extraremanent Data Range......................................................118
5 Software.................................................................................................125
5.1 The User Program Memory........................................................125
5.2 Programming Using CoDeSys ...................................................126
5.2.1 Overview of I/O Variable Addresses ........................................126
5.3 Special Functions of Internal I/Os ..............................................130
5.3.1 Internal Digital Inputs/Outputs ..................................................130
5.3.2 Functions of Internal Inputs SI_0...SI_3 ...................................132
5.3.3 Functions of Internal Outputs (0.1 A) SO_0...SO_3.................133
5.3.4 Short-circuited Output...............................................................137
5.3.5 Internal Analogue Input Functions............................................139
5.3.6 Internal Analogue Output Functions.........................................141
5.3.7 Functions of Internal Counters .................................................143
5.4 Functions of the Basic Module's Inputs and Outputs .................149
5.4.1 Functions of Inputs SDE_0...SDE_1 (SDE_3) .........................149
5.4.2 Functions of Outputs SDO_0... SD0_1 (SD0_3)......................149
5.5 Start after Configuration Error ....................................................150
5.6 Functions of Expansion Modules 0...3 .......................................150
5.7 Status Messages of Expansion Modules 0...3 ...........................151
6 PROFIBUS-DP ......................................................................................153
6.1 Basic Information........................................................................153
6.1.1 What is PROFIBUS? ................................................................153
6.1.2 Bus Protocol .............................................................................153
6.1.3 Topology...................................................................................153
6 E 700 GB

Introduction
6.1.4 Station Address ........................................................................154
6.1.5 Network Configuration..............................................................154
6.2 Master-Slave Communication ....................................................155
6.2.1 Device Master File KUHN690B.GSD .......................................155
6.2.2 Receive Parameter Data (Prm_Data) .....................................157
6.2.3 Send Diagnostic Data (Diag_Data) ..........................................160
6.2.4 Master-Slave Data Communication..........................................165
7 CANopen ...............................................................................................169
7.1 CANopen for Beginners .............................................................169
7.1.1 CANopen Example...................................................................171
7.1.2 CAN Network Status.................................................................173
8 PLC Error Handling................................................................................177
8.1 "Failure" LED..............................................................................177
8.2 Status Variable "SYSTEMINFO"................................................177
8.3 Faults and Failures Overview.....................................................180
8.3.1 Short-circuited Output (Error #1) ..............................................181
8.3.2 Low Voltage (Power Supply, Error #2).....................................182
8.3.3 Watchdog (Program Runtime Exceeded, Error #3) .................184
9 Appendix................................................................................................185
9.1 Technical Data ...........................................................................185
9.1.1 Basic Data ................................................................................185
9.1.2 Integrated Inputs and Outputs..................................................186
9.1.3 Communication Ports ...............................................................189
9.1.4 Hardware ..................................................................................189
9.1.5 Project Setup ............................................................................190
9.1.6 Permits .....................................................................................190
9.2 Order Specifications ...................................................................191
9.2.1 Controllers Ventura Remote PLC.............................................191
9.2.2 Accessories ..............................................................................191
9.3 Ventura Remote I/O Expansion Modules...................................193
9.4 References .................................................................................194
9.5 Sales & Service ..........................................................................195
9.5.1 Main Factory in Malente ...........................................................195
7

Introduction
9.5.2 Sales Germany.........................................................................195
9.5.3 Customer Service.....................................................................195
9.6 Index...........................................................................................197
8 E 700 GB

1 Introduction
Introduction
Ventura Remote PLC, Kuhnke's compact control system,
has been designed for automation tasks of an average
degree of complexity. As part of a PROFIBUS or
CANopen network it lets you implement decentralised
structures.
Its integrated analogue and digital inputs and outputs with
special functions allow you to process all signals
immediately in the control unit without having to install any
additional devices or modules. The A/B/Ref counter input
provides solutions for drive, positioning and fast counting
tasks.
Ventura Remote PLC can be extended by the modules of
the Ventura Remote I/O system which provide a
convenient means of adapting the unit to your very needs.
CoDeSys, the convenient IEC 61131-3-standard
programming and startup environment, is used for writing
and editing programs in the IL, LD, FD, SFC, CFC and
Structured Text languages.
The PLC's multi-tasking system lets timers or events take
control of parts of the program. A powerful processor very
much speeds up program execution.
Benefits
� Integrated analogue/digital inputs and outputs
� Extendable by modules of system
Ventura Remote I/O
� Event handling by interrupt routines
� User program back-ups on MultiMediaCard
� Extended data memory by MultiMediaCard
� Integrated PROFIBUS DP or CANopen field bus
interface
� DIN top hat rail bracket for easy installation
� CoDeSys version 02.03.05.00 or higher for easy
configuration and programming
� Extensive diagnosis options
9

Introduction
1.1 Area of Application
This instruction manual describes the properties of the
following standard device variants programmable using
CoDeSys:
Ventura Remote PLC DP 16DI/16DO
plus PROFIBUS DP field bus interface ..........................693.9x3.22.00
Ventura Remote PLC CAN 16DI/16DO
plus CANopen field bus interface ....................................693.9x1.22.00
Ventura Remote PLC DP 32DI/32DO
plus PROFIBUS DP field bus interface ..........................693.9x3.44.00
Ventura Remote PLC CAN 32DI/32DO
plus CANopen field bus interface ....................................693.9x1.44.00
x=1: Spring-type locking
x=2: Screw-type locking
The following standard variants are programmed using
KUBES and are thus described in instruction manual E
633:
ProfiControl 690PLC+ 16DI/16DO
plus PROFIBUS DP field bus interface ...........................690.723.22.01
CanControl 690PLC+ 16DI/16DO
plus CANopen field bus interface ....................................690.721.22.01
ProfiControl 690PLC+ 32DI/32DO
plus PROFIBUS DP field bus interface ...........................690.723.44.00
CanControl 690PLC+ 32DI/32DO
plus CANopen field bus interface ....................................690.721.44.00
The following release1 variants are programmed using
KUBES and are thus described in instruction manual E
559:
ProfiControl 690PLC+ 16DI/16DO
plus PROFIBUS DP field bus interface ...........................690.723.22.00
CanControl 690PLC+ 16DI/16DO
plus CANopen field bus interface ....................................690.721.22.00
10 E 700 GB

1.2 Variants
Introduction
Compact controller Ventura Remote PLC has two model
variants which are distinguished by the target field bus:
� Ventura Remote PLC CAN
Field bus: CANopen
� Ventura Remote PLC DP
Field bus: PROFIBUS-DP (as DP slave)
The information below describes the sets of inputs and
outputs of every variant.
Example:
� Ventura Remote PLC CAN 16DI/16DO
Field bus: CANopen
digital inputs: 16
digital outputs: 16
Terminology
This instruction manual specifies the variants as follows:
� Ventura Remote PLC
information referring to all variants,
� Ventura Remote PLC CAN
information referring to variants equipped with a
CANopen interface only,
� Ventura Remote PLC DP
information referring to variants equipped with a
PROFIBUS-DP interface only.
11

Introduction
1.3 From Stand-alone Controllers to
Distributed Networks
For mainly three reasons, programmable logic controllers
and PCs play a key role in industrial automation:
� they are universally applicable,
� programming them is both simple and clear,
� extensive utilities for testing and commissioning are
available.
Standard programming utilities compliant to EN 61131-3
further reduces the effort to be put into programming. The
latest generation of Kuhnke PLCs therefore deploys
CoDeSys for programming.
The PLC has become a universal automation tool in a
wide range of application requirements.
Networkable control systems have emerged in response
to the ever increasing requirements of the complexity and
flexibility of machines and process control systems. The
"old" allround PLC for all aspects is being replaced with a
notion of task separation. Every part system just does
what it can do best.
For example, PCs are the perfect tool for computing and
managing large volumes of data at the control level or for
visualisation and operation.
PLCs are responsible for real-time control tasks and, if a
suitable field bus is available, for the process interfacing
level.
The process signals go through remote I/O units located
somewhere near the sensors and actuators.
The field bus focusses on the speed and reliability of data
transfer and the design as an open system. PROFIBUS-
DP and CANopen currently have the greatest market
awareness.
12 E 700 GB

Advantages of Decentralisation
Introduction
� no more multicore cables,
- material (cables, connectors...)
- space (ducts, terminal boxes, switching cabinets)
- installation (time, possible mistakes)
� improved functionality
� clearer arrangements
� reduced setup and commissioning times
� failure response and availability (if one part fails,
other parts continue to work)
� pre-testing of individual stations
� vendor-independence
To be able to fully benefit from these plus points,
standardised solutions for all sub-systems should be
available focussing on the speed and reliability of data
transfer and the design as an open system.
The networkability of Ventura Remote PLC and Ventura
Remote I/O turn the Ventura range into a system that fully
meets the above requirements.
13

Introduction
1.4 Ventura Remote PLC as a Field Bus Unit
The purpose of PLCs is to control machines, facilities etc.
To fulfil its task, it needs to exchange data with the
process controlled which it normally does via inputs and
outputs.
Ventura Remote PLC is a standalone controller
programmed using CoDeSys and equipped with local
digital and analogue I/Os and an incremental encoder
input. Install any of the modules from the Ventura Remote
I/O system to expand its possibilities.
Ventura Remote PLC has the added capability of
exchanging data via PROFIBUS-DP and CANopen which
makes it an intelligent I/O unit for use in PROFIBUS or
CANopen networks.
� Time-critical processes can be controlled without
delays caused by field bus communication.
� Distributed intelligence relieves the master controller
and improves the performance and flexibility of the
machine.
14 E 700 GB

1.5 Network Examples
1.5.1 PROFIBUS-DP
Introduction
PC Control 645-12M-PCI-CoDeSys, the PROFIBUS PLC
in the PC, configured as DP master in a network with DP
slaves.
PC Control 645-12M-PCI
PROFIBUS DP
Ventura DriveControl Ventura other
Remote PLC DP 684DP Remote I/O slaves
Fig.: 1 PC Control 645-12M-PCI-CoDeSys as the DP master
15

Introduction
1.5.2 CANopen
ProfiControl 680V-C as the CANopen configuration
master (top) in a network with Remote Control CAN.
Ventura DriveControl 684 CanControl 691 I/O
Remote PLC CAN
CANopen
ProfiControl 680V-C
Fig.: 2 Ventura Remote PLC CAN in a CANopen network
16 E 700 GB

2 Reliability, Safety
2.1 Intended Use
2.2 Target Group
2.3 Reliability
Reliability, Safety
Kuhnke products are designed as resources for use in
industrial environments.
All other applications need to be discussed with the
factory first. The manufacturer shall neither be liable for
any other than the intended use of our products nor for
any ensuing damages. The risk shall be borne by the
operator alone. The use as intended includes that you
read and apply all information and instructions contained
in this manual.
This instruction manual contains all information necessary
for the use of the described product (control device,
control terminal, software, etc.) according to instructions.
It is written for design, project planning, servicing and
commissioning experts. For proper understanding and
error-free application of technical descriptions, instructions
for use and particularly of notes of danger and warning,
extensive knowledge of automation technology is
compulsory.
Reliability of Kuhnke controllers is brought to the highest
possible standards by extensive and cost-effective means
in their design and manufacture.
These include:
� selecting high-quality components,
� quality agreements with our suppliers,
� actions to avoid static charges when handling MOS
circuits,
� worst case planning and design of all circuits,
17

Reliability, Safety
2.4 Symbols
2.4.1 Danger
2.4.2 Attention
� visual inspections at various stages of fabrication,
� computer-aided tests of all assemblies and their
interaction in the circuit,
� statistical assessment of the quality of fabrication and
of all returned goods for the immediate taking of
appropriate corrective actions.
Despite the measures described in chapter 2.3 the
occurrence of faults or errors in electronic control units -
even if most highly improbable - must be taken into
consideration.
Please pay particular attention to the additional notices
which we have marked by symbols throughout this
instruction manual. While some of these notices make you
aware of possible dangers, others are intended as a
means of orientation. They are described further down
below in descending order of importance.
This symbol warns you of dangers which may cause
death or grievous bodily harm if operators fail to
implement the precautions described.
This symbol draws your attention to information you must
take a look at to avoid malfunctions, possible material
damage or dangerous states.
18 E 700 GB

2.4.3 Note
Reliability, Safety
This symbol draws your attention to additional information
concerning the use of the described product. This may
include cross references to information found elsewhere
(e.g. in other manuals).
2.4.4 Under Construction
2.4.5 Instruction
This symbol tells you that the function described was not
or not fully available at the time this document went to
press.
Wherever you see these symbols in the left margin, you
will find a list of steps instructing you to take the
appropriate computer or hardware actions.
They are intended as a means of orientation wherever
working steps and background information alternate (e.g.
in tutorials).
19

Reliability, Safety
2.5 Safety
Our products normally become part of larger systems or
installations. The information below is intended to help
you integrate the product into its environment without
dangers to humans or material/equipment.
To achieve a high degree of conceptual safety in
planning and installing an electronic controller, it is
essential to exactly follow the instructions given in the
manual because wrong handling could lead to rendering
measures against dangers ineffective or to creating
additional dangers.
20 E 700 GB

2.5.1 Project Planning and Installation
Reliability, Safety
� 24 VDC power supply: generate as electrically safely
separated low voltage. Suitable devices are, for
example, split transformers constructed in
compliance with European Standard EN 60742
(corresponds to VDE 0551).
� Power breakdowns or power fades: the program
structure is to ensure that a defined state at restart
excludes all dangerous states.
� Emergency switch-off installations must comply with
EN 60204/IEC 204 (VDE 0113). They must be
effective at any time.
� Safety and precautions regulations for qualified
applications have to be complied with.
� Please pay particular attention to the notices of
warning which, at relevant places, will make you
aware of possible sources of dangerous mistakes or
faults.
� Relevant standards and VDE regulations are to be
complied with in every case.
� Control elements are to be installed in such a way as
to exclude unintended operation.
� Control cables are to be laid in such a way as to
exclude interference (inductive or capacitive) which
could influence controller operation or its functionality.
21

Reliability, Safety
2.5.2 Maintenance and Servicing
� Precautions regulation VBG 4.0 must be observed
when measuring or checking a controller in a powerup
condition. This applies to section 8 (Admissible
deviations when working on parts) in particular.
� Repairs must be carried out by specially trained
Kuhnke staff only (usually in the main factory in
Malente). Warranty expires in every other case.
� Only use parts approved of by Kuhnke. Only genuine
Kuhnke modules must be used in modular
controllers.
� Modular systems: always plug or unplug modules in a
power-down state. You might otherwise damage the
modules or (possibly not immediately recognisably!)
inhibit their functionality.
� Always dispose of any batteries and accumulators as
hazardous waste.
22 E 700 GB

2.6 Electromagnetic Compatibility
2.6.1 Definition
Reliability, Safety
Electromagnetic compatibility is the ability of a device to
function satisfactorily in its electromagnetic environment
without itself causing any electromagnetic interference
that would be intolerable to other devices in this
environment.
Of all known phenomena of electromagnetic noise, only a
certain range occurs at the location of a given device. It is
defined in the relevant product standards.
The design and immunity to interference of programmable
logic controllers are internationally governed by standard
IEC 61131-2 which, in Europe, has been the basis for
European Standard
EN 61131-2.
2.6.2 Interference Emission
Interfering emission of electromagnetic fields, HF
compliant to EN 55011, limiting value class A, Group 1
(industrial use)
If the controller is designed for use in residential areas,
high-frequency emissions must comply with limiting value
class B as described in EN 55011.
Fitting the controller into earthed metal cabinets and installing
filters in the supply lines may produce a shielding
compliant to the above standard.
2.6.3 General Notes on Installation
As component parts of machines, facilities and systems,
electronic control systems must comply with valid rules
and regulations, depending on their field of application.
General requirements concerning the electrical equipment
of machines and aiming at the safety of these machines
23

Reliability, Safety
are contained in Part 1 of European Standard EN 60204
(corresponds to VDE 0113).
For safe installation of our control system please observe
the information contained in the next chapters (� 2.6.4
ff).
2.6.4 Electrical Immission Safeguard
Connect the control system to the protective earth
conductor to eliminate electromagnetic interference.
Practice best cable routing.
2.6.5 Cable Routing and Wiring
Keep power circuits separate from control circuits:
� DC voltages 60 V ... 400 V
� AC voltages 25 V ... 400 V
Joint laying of control circuits is allowed for:
� shielded data signals
� shielded analogue signals
� unshielded digital I/O lines
� unshielded DC voltages < 60 V
� unshielded AC voltages < 25 V
2.6.6 Location of Installation
2.6.6.1 Temperature
Ensure that temperatures, contaminations, impact,
vibration or electromagnetic interference are no
impediment to the installation.
Consider heat sources such as general heating of rooms,
sunlight, heat accumulation in assembly rooms or control
cabinets.
24 E 700 GB

2.6.6.2 Contamination
Reliability, Safety
Use suitable casings to avoid possible negative influences
due to humidity, corrosive gas, liquid or conducting dust.
2.6.6.3 Impact and Vibration
Consider possible influences caused by motors,
compressors, transfer lines, presses, ramming machines
and vehicles.
2.6.6.4 Electromagnetic Interference
Consider electromagnetic interference from various local
sources: motors, switching devices, switching thyristors,
radio-controlled devices, welding equipment, arcing,
switched-mode power supplies, converters / inverters.
2.6.7 Particular Sources of Interference
2.6.7.1 Inductive Actuators
Switching off inductances (such as from relays,
contactors, solenoids or switching magnets) produces
surge voltages. It is mandatory to throttle these noise
voltages to an admissible dimension.
Throttling elements could be diodes, Z diodes, varistors or
RC elements. To find the best adapted elements, we
recommend that you contact the manufacturer or supplier
of the corresponding actuators for the relevant
information.
25

Reliability, Safety
26 E 700 GB

3 Hardware
3.1 System Description
Hardware
Ventura Remote PLC DP is a decentralised input/output
unit (I/O) featuring a 12 Mbps PROFIBUS-DP slave port.
Ventura Remote PLC DP is a decentralised input/output
unit (I/O) featuring a 1 Mbps CANopen port.
The system is made up of various components which you
can combine as necessary.
Adding I/O modules of the Ventura Remote I/O system
expands the capabilities of the basic unit.
See page 193: Ventura Remote I/O Expansion Modules
The following are the maximum configurations:
Basic 16di/16do module
basic modulemodule0 module1 module2 module3
Basic 32di/32do module
basic module module0 module1 module2 module3
27

Hardware
3.2 Mechanical Design
H
W
The housing mainly consists of a backbone of profiled
aluminium with an integrated snap-on device for
installation on a mounting rail. The sides of galvanised
steel sheet are riveted to that backbone.
Fig.: 3 16di/16do variant
3.2.1 Dimensions
Variant 16di/16do 32di/32do
Length "L" [mm] 213 329
Width "W" [mm] 90 90
Height "H" [mm] 75 75
28 E 700 GB
L

Hardware
Extensions
Ventura Remote PLC can be extended by up to four I/O
expansion modules of the Ventura Remote I/O range of
system products. Every expansion module is 112 mm
long.
See page 193: Ventura Remote I/O Expansion Modules
29

Hardware
3.2.2 Installation
Both the Ventura Remote PLC controller and its I/O addons
install on mounting rails (to DIN EN 50022, 35 x 7.5
mm).
Procedure
1.
Push up the device against
the mounting rail from
below, allowing the metal
spring to snap in between
mounting rail and
mounting area. Do as
shown in the illustration.
2.
metal spring
Push the device against
the mounting wall until is
snaps in.
Every expansion module installs to the right of the control
unit as described above. Look down the left side of your
expansion module to discover a short ribbon cable and
plug. The connector plugs into the counterplug located
under the lid of the preceding device. There is a recess in
the side wall that the ribbon cable threads through.
30 E 700 GB

3.3 Power Supply
3.3.1 Earth
left side wall
Hardware
The metal housing has to be connected to earth. Use the
earth conductor located on the left side wall.
� Earth conductor
Cross section: min. 2.5 mm²
Length: as short as possible
� Interfacing
Flat plug 6.3 x 0.8 mm
� Function
The earth conductor serves as operative earth
(special case: relay module � E 409 GB).
The +24 VDC and 0 V power supply connectors have
an internal (by spring-actuated contacts on the PCB)
capacitive connection to the housing which also
attaches them to earth. Line-conducted HF
interference is bled off into the ground.
The PROFIBUS plug connector housing directly
connects to operative earth which is where the cable
shield is attached also.
This earth conductor is no protection against high contact
voltage. To provide sufficient protection, supply the
devices with properly separated low voltage.
31

Hardware
3.3.2 Wiring
All plug-type terminals accept flexible wires whose
conductor has a diameter of 2.5 mm 2 .
Screwdriver
To fit the wires you need a standard flat-blade screwdriver
with a blade max. 4 mm wide.
To unplug
The connectors fit very tightly to avoid them coming off if
exposed to vibration. In case they won't come off by hand
you can use a lever, e.g. a flat object such as a
screwdriver with a wide blade.
Do not pull the lead to unplug. They might otherwise slip
out of the terminals or rip off.
32 E 700 GB

3.3.3 Power Supply
Hardware
Voltages are fed into the unit through screw-type locking
connectors.
Voltage: 24 VDC +25 % /-20 %
System I/Os and special I/Os receive their power through
connector L1. Plug L2 is used to separately attach the
digital I/Os to the voltage supply.
Provide a separate power source for all expansion
modules.
digital I/Os
system I/Os and special I/Os
Keeping the power supply separate allows you to turn off
the outputs without turning off the PLC at the same time.
The advantage is that the system is still supplied with
energy, inputs are kept being read, and communication
(bus, terminal...) is not interrupted.
33

Hardware
3.3.3.1 Power Supply Information
Power to system I/Os and special I/Os
An external source supplies the unit with 24 VDC which a
built-in power supply unit takes to generate the internal
system voltage (5 V) and fed it to the CPU, the device bus
and the fieldbus interfaces.
Please note: always connect the 0V line first and
disconnect it last. You may otherwise experience
equalisation currents go through a V.24 (RS 232)
interface that may be connected. This in turn will cause
the electronic fuse to trip. It will afterwards take about one
minute until the unit has cooled down and is ready to
operate again.
Power to digital I/Os
Power supply to auxiliary push-buttons or other switching
devices that are connected in parallel with the outputs
must also be switched off together with the outputs.
Avoid any reverse feeding of outputs while the power
supply to the outputs is turned off!
This applies if the system is still supplied with power.
Outputs enabled by the user program may be supplied
power via the protective diode of a reversely fed output,
thus overriding the switch-off function of these outputs.
Moreover, the protective diode of the feeding outputs may
yield under high loads and be destroyed.
34 E 700 GB

3.4 Inputs and Outputs
3.4.1 Digital I/Os, Basic Module
3.4.1.1 Terminals
3.4.1.2 Electrical Insulation
Hardware
Ventura Remote PLC has a basic module equipped with
16 or 32 digital inputs and 16 or 32 digital outputs.
Digital inputs, 24 VDC
� "0"..."7" inputs 0...7 (16...23) 1
� ".0"...".7" inputs 8...15 (24...31) 1
Digital outputs, 24 VDC, 0.5A
� "0"..."7" outputs 0...7 (16...23) 1
� ".0"...".7" outputs 8...15 (24...31) 1
Inputs and output are not electrically insulated from the
system voltage "L1".
At the time of installation, please take heed of the
information about how to connect the supply voltage (�
3.3.3.1).
1 Variants featuring 32 digital inputs and 32 digital outputs
35

Hardware
3.4.1.3 Inputs
3.4.1.4 Outputs
Inputs are actuated by +24 VDC signals. The 0 V potential
connects to terminal L2-. Whenever an input signal is sent
to the terminal the LED assigned to that terminal will light
up green.
Power (24 VDC) to the outputs is supplied via terminals
"L2+" and "L2-". Whenever an output signal is sent to the
terminal the LED assigned to that terminal will light up red.
Output current
The current of every output is rated at 0.5 A. Outputs are
put into groups of 4 (0...3 and 4...7) which are actuated by
the same driver module. Every driver module can sustain
a total load of up to 1.9 A (� Technical Data, Outputs).
Overload (short circuit) on an output or an output driver
will switch the output off. The outputs of the basic module
are not monitored for short circuits. A fault occurring in the
outputs of the expansion modules cause Ventura Remote
PLC to set the relevant status flag (�section 5.3.4.4).
Parallel connection of outputs
Since the controller uses a data byte to address the
outputs of the same driver module, it is fairly
unproblematic to connect them in parallel.
The total load of every group of 16 outputs must be no
greater than 8 A. This is the limiting current that supply
terminal L2 is rated at.
36 E 700 GB

3.4.2 Digital Combi I/Os
Hardware
Ventura Remote PLC features 4 digital combi I/Os (di/do0
– di/do3) which can be configured to act either as inputs
or as outputs. To make the configuration settings, you
either use the Module Configurator - a utility provided by
the KUBES programming software - or the user program.
Signal pin wiring
3
2
1
0
di/do
The screw-type locking terminals are
safe for use with conductors of a
diameter between 0.25 mm 2 and 1.5
mm 2 .
LEDs down the status indicator bar
show the signal state of the combi
I/Os.
Digital combi I/O configured as input
The signal state of digital combi I/Os acting as inputs is
shown by the appropriate LEDs. When a 24 V signal is
supplied, the LEDs light up green.
The inputs have a rising delay of 0.2 ms. The user
program can read them just like normal inputs. To be able
to immediately react to events, they are capable of
requesting processor interrupts.
37

Hardware
Digital combi I/O configured as output
The signal state of digital combi I/Os acting as outputs is
shown by the appropriate LEDs. When a 24 V signal is
supplied, the LEDs light up red. If the clock pulse output
function is enabled they can output frequencies between
200 Hz and 10kHz. Whenever a clock pulse output is
active, the LEDs light up orange (between yellow and red,
depending on the frequency).
The maximum nominal current of every combi I/O output
is 0.1 A.
38 E 700 GB

3.4.3 Analogue Inputs
Hardware
Ventura Remote PLC has 4 analogue inputs labelled ai0,
ai1, ai2 and ai3. They are set by the configuration. The
resolution is 10 bit. They attach to the screw-type locking
terminal. Immediately next to the analogue input, there is
a terminal for the analogue reference potential. All
analogue reference potential terminals are
interconnected.
Signal pin wiring
1
0
ai
The screw-type locking terminals are
safe for use with conductors of a
diameter between 0.25 mm 2 and 1.5
mm 2 .
To avoid noise on the operative
signal, you are advised to use
shielded cables. Attach the shield to
the earth conductor terminals on the
left side wall.
39

Hardware
3.4.4 Analogue Outputs
Ventura Remote PLC has 2 analogue outputs labelled
ao0, and ao1. They are set by the configuration. Their
resolution can be set to either 8 bit (10V/256, i.e. approx.
39mV) or 10 bit (10V/1024, i.e. approx. 96mV). They
attach to the screw-type locking terminal. Immediately
next to the analogue input, there is a terminal for the
analogue reference potential. All analogue reference
potential terminals are interconnected.
ao
1
0
Signal pin wiring
The screw-type locking terminals
are safe for use with conductors of
a diameter between 0.25 mm 2 and
1.5 mm 2 .
To avoid noise on the operative
signal, you are advised to use
shielded cables. Attach the shield
to the earth conductor terminals on
the left side wall.
40 E 700 GB

3.5 A, B, Ref Counter
Hardware
Ventura Remote PLC features a connector for a 24 V
incremental encoder which can be used either as A, B,
Ref counter or as an event counter. Its actual function is
set at the configuration stage. To connect, attach a 9-pin
male Sub-D connector to the female Sub-D Encoder port
on the unit.
Signal pin wiring
encoder
9
8
7
6
5
4
3
2
1
Pin 1 Gnd
Pin 2 reference input
Pin 3 counter input B
Pin 4 counter input A
Pin 5 +24V
Housing frame ground (cable
shield)
41

Hardware
3.6 Communication Ports
3.6.1 V.24 / com
Ventura Remote PLC features a serial COM port which is
used as a CoDeSys programming interface or for
connecting dialog terminals to. To connect, attach a 9-pin
male Sub-D connector to the female com port on the unit.
Make sure that the cable matches the purpose you wish
to use it for.
Signal pin wiring
com
9
8
7
6
5
4
3
2
1
Pin 2 TxD
Pin 3 RxD
Pin 5 GND
Pin 7 CTS
Pin 8 RTS
Housing frame ground (cable
shield)
42 E 700 GB

3.6.2 PROFIBUS
Hardware
Ventura Remote PLC DP is a PROFIBUS-DP slave. To
connect to PROFIBUS, attach a 9-pin male Sub-D
connector to the female Sub-D PROFIBUS port on the
unit. Its address is set at the configuration stage.
PROFIBUS
9
8
7
6
Signal pin wiring
Pin 3 RxD/TxD (Data+)
Pin 5 DGND
5
4
3
2
1
Pin 6 VP (5V)
Pin 8 RxD/TxD (Data-)
Housing frame ground (cable shield)
Please note that the PROFIBUS must be properly
terminated at both ends of the bus cable. The PROFIBUS
jack of Ventura Remote PLC supplies the required voltage.
For details on how to install the bus cable, on shielding,
connectors, bus nodes and bus termination refer to
instruction manual E 611 GB "PROFIBUS-DP“.
43

Hardware
3.6.3 CAN
Ventura Remote PLC CAN features a CANopen port. To
connect to a CAN bus, attach a 9-pin female Sub-D
connector to the male Sub-D CAN port on the unit. Its
address is set at the configuration stage.
Signal pin wiring
Pin 2 CAN-L
Pin 3 CAN-GND
Pin 7 CAN-H
CAN
Housing frame ground (cable shield)
Please note that the CAN BUS must be properly
terminated at both ends of the bus cable.
For details on how to install the bus cable, on shielding,
connectors, bus nodes and bus termination refer to
instruction manual E 615 GB "CANopen“.
44 E 700 GB
9
8
7
6
5
4
3
2
1

3.7 Expansion Modules
Ventura Remote
PLC16di/16do
Hardware
An I/O expansion is a separate unit with an I/O module
and connectors for an upstream and a downstream
module. I/O expansions are available with different
input/output configurations. See section 9.3 for an
overview.
A serial bus is the means of communication between I/O
modules and the CPU.
Up to 4 I/O expansions can be attached to a basic control
unit. Every extension module has a short ribbon cable
with a plug on its left side that connects it with the unit.
The connector plugs into the counterplug located under
the lid of the preceding device. There is an opening in the
side of the module that the ribbon cable threads through.
Ventura Remote
PLC32di/32do
module0 module1 module2 module3
module0 module1 module2 module3
For further information about modules refer to instruction
manual E 698 GB "Ventura Remote I/O".
45

Modes of Operation
3.8 Modes of Operation
Ventura Remote PLC supports various modes of
operation which are activated by turning the mode
selector and resetting the unit by restarting it.
Apart from Run mode for normal PLC operation, there are
also modes available for program transfer.
Options are to store the user program (Program 1 or
Program 2) on non-volatile Memory Card (MC) memory
or, vice versa, get the program from the MC and load it
into a PLC.
3.8.1 External Non-volatile Memory Card (MMC)
� Capacity: up to 128 Mbyte
� Function: program interchange memory, data
memory
Check the lid of the housing where you will find a slot for
the multimedia memory card on the left side. When you
slot in a card it will snap on to the connector underneath
to firmly attach to the system.
Do not pull out the multimedia card while the system is
accessing it. You may otherwise lose valuable data!
46 E 700 GB

3.8.2 Mode Selector
mode selector
Hardware
The mode selector is located on the left at the front of the
unit.
Fig.: 4 Location of mode selector
The mode selector can be set to 10 different positions (�
table on next page). Use a flat screwdriver (2.3 mm blade)
to change the setting.
The mode selector setting is only checked once when the
power is turned on. The controller will ignore all changes
made during operation.
47

Modes of Operation
3.8.3 Modes Overview
Switch Setting
0 "run" ■
PLC ready
yes no
1 stop ■
2 export 1 ■
3 import 1 ■
4 boot com1 ■
5 -- ■ No function
6 boot mc ■ No function
7 export 2 ■
8 import 2 ■
9 clear ■
Explanation
Normal op. mode:
This is the only setting that enables the
PLC functions.
Safety mode:
All PLC functions stopped, all outputs off,
no interface communication, no access
via the programming device
Save user program 1 and store on
memory card
Load user program 1 from the memory
card into the controller (flash memory)
Load monitor program via com into the
controller (flash memory)
Save user program 2 and store on
memory card
Load user program 2 from the memory
card into the controller (flash memory)
Delete user program and remanent data.
Code: 9, Off/On,1-5-9
(to enter � 3.8.3.6)
48 E 700 GB

3.8.3.1 RUN
3.8.3.2 Stop
3.8.3.3 Export
3.8.3.4 Import
3.8.3.5 Boot
All PLC functions are available.
Hardware
Safety mode. No function is executed although power is
supplied.
Write program onto MC. Two programs can be stored
(export1, 2).
� During data transfer:
LED run=green, stop=red
� Data transfer successfully completed:
LED run green
Never pull the memory card out of the slot while data is
being transferred.
Load program from the MC into the internal flash memory.
Two programs can be stored (export1, 2).
� During data transfer:
LED run=green, stop=red
� Data transfer successfully completed:
LED run green
Never pull the memory card out of the slot while data is
being transferred.
Use this mode to load firmware from the PC to the unit,
going via the com port.
49

Modes of Operation
3.8.3.6 Clear (Code-protected)
Action
1. Set selector to "9"
For safety reasons, some modes require that you enter a
code first. This is to avoid dangerous states, prevent the
program or data from being erased, etc.
How to enter the code for "clear" mode:
Code: 9, Off/On,1-5-9
This is what you do:
LED
run stop
2. Turn unit off and back on red
3. Selector to 1 for ≥ 1 second red
4. Selector to 5 for ≥ 1 second red
5. Selector to 9 for ≥ 1 second green
50 E 700 GB

3.9 Status and Failure Indication
"run" LED
"stop" LED
"failure" LED
"bus" LED
There are three light-emitting diodes that indicate the
status of the controller.
Fig.: 5 Location of status and failure LEDs
� LED "run" is green:
program running,
special function completed
� LED "stop" is red:
user program stopped
� red LED "failure":
failure somewhere in the system
� yellow LED "bus":
bus status / failure
Read the appendix (� section 8) to know what the
separate and combined signals stand for.
Hardware
51

Modes of Operation
3.10 Memory
Ventura Remote PLC has large memory capacities:
� Flash-EPROM, 1 Mbyte 1
Use for: runtime system, program and remanent data
� RAM, 1 Mbyte 1
Use for: variable data
(user program memory � section 5.1)
3.11 Multimedia Card (MMC)
The unit accepts standard multimedia cards of up to 128
Mb capacity (theoretically up to 2 Gb) which have been
previously formatted using a commercially available card
reader connected to the PC.
Data can be arranged in a directory tree. The card reader
and Windows Explorer together let you view and
manipulate the data structure.
Multimedia cards are used for the following purposes:
� storing of up to two user programs.
(� section 3.8 )
� logging / reading data generated by the running user
program.
(� section 4.5 )
1 Some of the memory is reserved for the monitor program.
52 E 700 GB

Installation
4 PLC Functions of Ventura Remote PLC
Read this section to know how to make use of the PLC
functions provided by Ventura Remote PLC.
Prerequisites
� CoDeSys version 2.334 or higher
� Target Ventura Remote PLC version 02030207 or
higher
4.1 CoDeSys Target Installation
To create a CoDeSys project for target system "Ventura
Remote PLC DP" / "Ventura Remote PLC CAN", you
must install the Target Support Package (TSP)
"VRPLC_Vxxxxxxxx"
prior to running the program by running the CoDeSys
installer called InstallTarget.
A TSP contains all configuration and extension files
required to use an application for operating a certain
controller (target system).
A configuration includes the code generator, the memory
layout, the set of functions provided by the controller and
the I/O modules.
The libraries, error and ini files for the PLC browser etc.
are also installed.
Browse site www.kuhnke.com for page Ventura Remote
PLC to get a free download of the up-to-date TSP
package.
53

Installation
� Run the target installer delivered with your CoDeSys
package.
� Open the folder containing TSP "TargetSlotPLC..."
and choose either P690.tnf for the PROFIBUS-DP
variants or C690.tnf for the CANopen variants.
� Select "KUHNKE", and then click on "Install".
54 E 700 GB

4.2 Writing CoDeSys Programs Online
Function Libraries
To log into the Ventura SlotPLC, CoDeSys can use one of
the following communication channels:
� Serial (RS232)
� CANopen
First choose a communication channel, and then log on.
4.2.1 Serial (RS232) Online-V.24
4.2.1.1 CoDeSys Settings
equivalent to KUBES' "Online V.24" command
Plug one end of the programming cable into the correct
outlet of the Ventura Remote PLC. The other end plugs
into the PC's COM port defined in the CoDeSys
environment.
Suitable programming cables are either the KUBES
programming cable (part number 657.151.03) or simple 9pin
1:1 cables (691.151.09).
� Choose Online�Communication Parameters
� New: Serial (RS232)
� Specify a name, e.g. "Online V.24"
� Select the PC's COM port that you will attach the
programming cable to.
� Select 19200,No,1. (Other baud rates are not
supported.)
To modify:
- Double-click on a value
- Press ↑ / ↓ or PgUp / PgDn
55

Function Libraries
4.2.1.2 Go Online
Since the settings are project-specific, a project must be
open before you can adapt them.
� Choose Online�Login
"Online" appears on CoDeSys' status line.
Have you got communication problems, i.e. in case of
"Create boot project" ?
CoDeSys uses 2 adjustable timeouts for watching the
communication.
� Increase the timeout-value (in ms) in the
CoDeSys.ini-file.
C:\Programs\3S Software\CoDeSys V2.3\CoDeSys.INI
[CoDeSys]
DefaultWaitTime=2200
; DownloadWaitTime=2200
DownloadWaitTime=5000
56 E 700 GB

4.2.2 CAN: Online CAN
Function Libraries
This section applies to Ventura Remote PLC CAN only.
Programming directly via the CAN bus is the most
practical approach whenever you wish to commission
your system with a RS 232 terminal connected. You need
a CAN converter for the PC used for programming (e.g. a
CAN dongle provided by Peak) and you must adapt the
CoDeSys programming system.
Online CAN upon request only!
Programming via CAN is subject to a couple of
constraints.
57

Function Libraries
4.3 Method of PLC Operation
The microprocessor for the user program retrieves its
instructions from three programs, i.e.:
1. the operating system,
2. the CoDeSys runtime system
3. the user program.
Version info
Information about the version of the operating system and
the CoDeSys runtime system implemented in your PLC
can be found online running the CoDeSys PLC Browser.
Go to tab "Resources"
Select the PLC Browser
Run the "metrics" command.
In response you will be shown a summary of PLC
settings.
To find the software version entry, locate item
KUHNKE CoDeSys SP:
V02.03.02.09 reads as follows:
� 02.03: runs in conjunction with CoDeSys version 2.3.
� 02.09: release 2.9
58 E 700 GB

4.3.1 Operating System
Function Libraries
The operating system defines all of the controller's
properties. It is part of the Ventura Remote PLC delivery
package and is stored in the internal flash EPROM.
The best part of the operating system is made up of its
real-time kernel, ARTOS.
ARTOS provides options for optimising the control
processes with regard to the installation of interrupt
routines or parallel programs, for example.
To be able to make best use of these options, you should
have some understanding of how the operating system
actually works.
ARTOS provides Ventura Remote PLC with pre-emptive
multitasking.
Pre-emptive multitasking means that several processes
(tasks) can be run and that the processor's computing
time is cut up into slices of a defined size.
A Scheduler (dispatcher) allocates time slices to the
processes during which program actions can be
performed.
When a process's time slice comes to an end the process
is interrupted and another process is allocated a time
slice.
A process could be anything like the CoDeSys runtime
system (see section 4.3.2) or PROFIBUS communication
routines. Running a function would set up another process
which is capable of interrupting the CoDeSys runtime
system.
Programs that the CoDeSys Task Configurator utility
assigned to specified events will not interrupt the
CoDeSys runtime system, though, because they are
processed only when they are "out of the way", e.g. when
the main program, PLC_PRG, has been completed.
(See pages 59 and 70)
4.3.2 The CoDeSys Runtime System
The CoDeSys runtime system is a process embedded in
the multitasking system of Ventura Remote PLC.
59

Function Libraries
The main program, PLC_PRG, is a free-wheeling task
equivalent to the organisation module of KUBES
programs. PLC_PRG runs exactly once in every control
cycle. PLC_PRG is the plug board for other actions such
as refreshing the process chart or communicating with the
CoDeSys programming system.
Event-controlled tasks configured using the Task
Configurator (see page 61) are picked from a task list
whenever the specified event occurs. They act as
interrupt handlers. Their processing starts when the
current task has stopped running.
Example: a cyclic task to be run at an interval t#10ms will
not be processed after every timer interrupt if the main
program runs for longer than 10ms.
Use function calls to set up event-controlled tasks to run
as interrupt service routines. They can interrupt the
processing of the current task.
To know how to use functions for setting up special tasks,
refer to section: 4.4 P690.lib
60 E 700 GB

4.3.3 Task Configuration
4.3.3.1 PLC_PRG
Function Libraries
Project handling can be controlled by so-called tasks
and/or the dedicated PLC_PRG utility program.
A task defines as a runtime unit of an IEC program. It is
specified by its name, a priority and a type defining the
condition that triggers it. A condition can be either timebased
(cyclic interval, free-wheeling) or defined by an
internal or external event that triggers the task whenever it
occurs. Examples would be the rising edge of a global
project variable or one of the controller's interrupt events.
Every task can be assigned a sequence of programs to be
run as the task is being executed.
The combination of priority and condition defines the order
in time in which the tasks are processed.
Every task can have a watchdog (timer-controlled
monitor) to it.
When running a task in online mode, its actual processing
can be viewed by means of a dynamic chart display.
There is also the option of directly linking system events
(Start, Stop, Reset etc) to running a project module.
The CoDeSys runtime system of Ventura Remote PLC
has extensive task management features which you
should use to optimise the control processes. Run the
Task Configurator utility to define the properties of the
tasks.
Furthermore, function calls can be used to set up special
event-controlled tasks/threads as processes of the
ARTOS runtime kernel (see page 70 )
PLC_PRG is automatically created as a program-type
module every first time you choose 'Project' 'Add Object'
to add a module to a new project. PLC_PRG runs exactly
once in every control cycle.
Generally speaking, PLC_PRG is the main program of a
single-task program.
If it has no task configuration to it, the project must contain
module PLC_PRG. Vice versa, if it does have a task
61

Function Libraries
configuration to it, the project must not contain module
PLC_PRG. (If it is a part of the project it will not be run if a
task configuration is defined.)
PLC_PRG is a module free-wheeling through 800µs time
slices.
At the end of the time slice, processing of PLC_PRG is
interrupted to give way to the handling of other registered
processes.
When the task manager reactivates PLC_PRG it will pick
up the thread at the point where it was interrupted.
Once the last PLC_PRG command has been executed
the actions linked to PLC_PRG, i.e. refreshing the
process chart, CANopen ∗ , communication etc., will be
taken only to start the task afresh afterwards.
A long PLC_PRG runtime is an extra burden to
communication:
- To program non-time-critical sections, use a thread
instead (see page 71)
∗ Controllers featuring a CANopen interface only
62 E 700 GB

4.3.3.2 The Task Configurator
4.3.3.3 Task Properties
4.3.3.3.1 Name
4.3.3.3.2 Priority (0-31)
Function Libraries
The Task Configurator is one of the objects on the
Resources tab of the Object Organizer. The Task Editor
window has two panes.
The pane on the left displays a tree view of the tasks. The
first line has 'Task Configuration' in it which is followed by
a 'System Events' entry and the separate task items
represented by their task name. The relevant program run
commands are appended underneath every task item.
The right-hand pane consists of a Properties dialog
showing the parameters of the item selected on the lefthand
pane. Use the dialog to define the tasks, program
run commands or system events as appropriate. The
configuration options available in the Properties dialogs
depend on the target system; they are set by a XML-type
description file referenced by the Target file. In case the
default definitions contained in the description file have
been expanded by tailored definitions, the latter are
available for configuration purposes via an extra
'Parameters' tab sheet on the right-hand dialog side.
This is the name under which the task appears in the
configuration browser where it can be changed by clicking
on it or by pressing the spacebar to open a text box.
The priority is a numeral between 0 and 31, 0 the highest
priority, 31 the lowest.
63

Function Libraries
4.3.3.3.3 Type
4.3.3.3.4 Properties
� Cyclic ( ) :
The task is run at cyclic intervals as specified next to
'Interval'.
� Free-wheeling ( ) :
The task starts running together with the program and
restarts every time it comes to its end. There is no cyclic
interval timer.
� Triggered by event ():
The task is run when it meets the rising edge of the
variable entered as the 'Event'.
� External event ():
The task is run when it encounters the system event
entered as the 'Event'. The items of the drop-down list of
events depend on the target system (currently not
supported).
Event-controlled tasks configured using the Task
Configurator are picked from a task list whenever the
specified event occurs. Their processing starts when the
current task has stopped running.
� Interval (for the 'Cyclic' or 'Free-wheeling' types):
An interval sets the time after which the task will be
restarted. If you enter a numeral click on the control box
next to it to set milliseconds [ms] or microseconds [µs] as
the unit of measurement. Milliseconds will be turned into
the TIME format (e.g. "t#200ms") after the next shift of
focus. Microseconds will continue to the shown as a bare
figure (e.g. "300").
� Event (for the "Triggered by event" type):
An event is a global variable whose rising edge is set to
running the task. Click on the control or press to
display a list of global variables for you to choose from.
64 E 700 GB

4.3.4 PLC Configuration
Function Libraries
Programmers need to know the addresses of inputs and
outputs of both the controller's local I/Os and the I/Os of
any expansion module connected.
It is a must to properly configure and set the parameters
of the network of units to achieve the required excellence
of data interchange between Ventura Remote PLC and
the other units, no matter whether Ventura is the
PROFIBUS-DP slave interacting with its DP master or a
CANopen device interacting with other CAN slaves.
The tool to use for setting addresses and parameters and
for configuring the network is the PLC Configuration
Editor.
4.3.4.1 The CoDeSys PLC Configuration Editor
PLC Configuration is one of the objects on the Resources
tab of the Object Organizer.
Run the configuration editor to describe the target
hardware that the open project will run on. CoDeSys takes
this description to verify whether the hardware actually
has the IEC addresses declared in the program.
The basis for working with the configuration editor are the
configuration files, *.cfg, and device files (e.g. *.gsd, *.eds)
stored in set hard disk directories and read when a project
is opened.
You can add files to these directories at any time.
The configuration file (*.cfg) describes a default
configuration whose settings are automatically shown
when the editor is run. It also characterises the set of
parameters available and in what way they can be
changed.
The device files (*.gsd) describe the configuration and
properties of PROFIBUS-DP slaves.
The device files (*.eds) describe the configuration and
properties of CANopen slaves.
When the user has finalised the configuration details in
the editor a binary compilation of the project structure
65

Function Libraries
information is downloaded into the controller together with
all other project data.
In the editor, the configuration is shown as a tree structure
which can be adapted using the editor's menus and
dialogs. There are elements which act either as inputs or
outputs or as administration elements which can have
sets of sub-elements to them (e.g. a PROFIBUS or the
internal I/Os with made up of various groups of inputs and
outputs.
4.3.4.2 PLC Configuration Example
Example:
A Ventura Remote PLC DP 32DI/32DO is to be expanded
by 2 Ventura Remote I/O 16DI/16DO modules.
Open a project and set "KUHNKE Ventura Remote PLC
DP" as the target system.
� Choose "PLC Configuration" from the "Resources"
tab.
� To display the list of I/O elements, either right-click to
display the action menu and choose or double-click
on "KUHNKE Ventura Remote PLC DP" and then on
"Internal I/O PLC DP" and "External I/O PLC DP".
� Click on "Bus module 16DI/16DO" and choose
"Extras, Replace element, Bus module 32DI/32DO".
� Click to select the first "External I/O PLC DP, empty
slot" and choose "Extras, Replace element,
66 E 700 GB

Function Libraries
DI16/DO16". Repeat this step for the second "empty
slot".
� You can edit the parameters of the expansion
modules. Select a property or enter the value into the
list on tab "Module parameters".
� Select "Kuhnke Ventura Remote PLC DP". Go to tab
"Module parameters" and specify the property for
"module configuration error" as appropriate.
On the editor screen, the inputs and outputs are shown
together with their IEC address by which they can be
accessed.
67

Function Libraries
To label the elements, every input and output can be
assigned a symbolic name which is prefixed to the IEC
address. (There are other methods which may be more
practical, depending on the situation.)
4.3.5 The User Program
The user program contains variable declarations and the
instructions required to control the machine or facility.
The way the user program actually runs in the controller is
defined by the runtime system and the PLC configuration
and task configuration settings.
Run CoDeSys to create the user program, then log on to
the PLC, transfer the program and store it in the
controller's RAM.
Only boot projects are permanently stored in the flash
EPROM.
68 E 700 GB

4.3.6 The Flash File System
Function Libraries
One of the options provided by the flash memory of
Ventura Remote PLC is to store any set of files, e.g.
project files, to have them available at the controller
(machine).
The data storage capacity is 192 Kbytes.
CoDeSys menu items:
� "Online, Write file to PLC"
� "Online, Read file from PLC"
The file system installed does not support the display and
selection of file names stored.
To be able to reload files from the controller's flash
memory into the RAM, you should therefore try to
remember the exact names of files.
69

Function Libraries
4.4 Function Library P690.lib/C690.lib
Together with the Target installation data (see page 53)
CoDeSys is sent libraries of functions provided by the
target system, Ventura Remote PLC.
� P690.lib hosts functions affecting the operating
system of Ventura Remote PLC DP. They can be
used to adapt program execution to specific
conditions.
� C690.lib covers the same set of functions, except that
it applies to Ventura Remote PLC CAN.
The table below summarises and explains the functions
contained in P690.lib / C690.lib:
Name Purpose
CREATE_THREAD installs a thread
CREATE_TIMERTASK installs a timer task
DELETE_TIMERTASK uninstalls a timer task
ENADIS_OUTPUTS enables / disables the outputs
FLUSH_INPUTS direct reading of inputs
FLUSH_OUTPUTS direct writing to outputs
INSTALL_ERROR_IRQ installs an error IRQ module
INSTALL_INPUT_IRQ installs an Input IRQ Module
REGIT_REFIRQ installs a REF IRQ Module
REGIT_T3IRQ installs a reference value IRQ module
SET_WATCHDOG sets up the watchdog
Pay attention that the library modules for installing and creating of
the special program units do not run permanently. Use the return
value for locking. Otherwise unforeseeable program flows could
arise.
70 E 700 GB

4.4.1 Installing a Thread
Function Libraries
A thread is the executive part of a process with several
threads being allowed to run at a time (parallel program).
Thread properties:
The operating system assigns a time slice of a defined
size (in µs) to the program identified by its index and runs
that program as a process. When the time slice comes to
its end, the thread is terminated and the next process is
run. It is the first thread's turn again when all other
registered processes have been completed. The RUNS
parameter allows you to restrict the number thread runs.
When the count of runs is complete, the thread is killed
and needs to be set up again if and when required.
Parameter Type Value Explanation
NPOU_Idparam WORD module index
TSLICE WORD
100..
6500
RUNS WORD 1..
65553
else 800µs
size of time slice, in µs
0 always
number of runs
Only one thread can run at exactly the same time. Your
program should provide for just 1 program module being
set up as a thread.
Modules defined to be threads must not also be started
directly by other parts of the program. You otherwise run
the risk of producing incalculable program runs.
71

Function Libraries
To set up a thread:
To install a program module as a thread you must run the
following code to identify the module:
Index := INDEXOF (module name);
Afterwards, the following function just needs to be run
once in order to set up the thread:
CREATE_THREAD (index);
FUNCTION CREATE_THREAD : BOOL
VAR_INPUT
NPOU_IDparam: WORD;
TSLICE: WORD;
RUNS: WORD;
END_VAR
VAR
END_VAR
The value returned by the function tells you something
about the thread status.
Value returned Explanation
0 not installed, no thread available
1 installed as thread #1
72 E 700 GB

Thread usage
Function Libraries
A thread's program covers a number of tasks which are
more or less detached from others. Consequently, it also
allows you to separately program and run these tasks.
Try wrapping non-time-critical parts of the program into a
thread. This will shorten the runtime of PLC_PRG and,
thus, the intervals at which the process image and online
communication are refreshed.
Example:
You wish to turn a program module called "Thread1" into
a thread and have IN_00 run it. Add the following code
lines to the PLC_PRG module.
VAR
IN00_00 AT %IX0.0: BOOL;
Index1: WORD;
Tslice1: WORD;
Runs1: WORD;
Flag1: UINT:=255;
Start_Thread1: R_TRIG;
Activate_Thread1: BOOL;
END_VAR
Start_Thread1
( CLK:=IN_00,Q=>Activate_Thread1 );
IF Activate_Thread1 = TRUE THEN
Flag1:=0;
END_IF
IF Flag1 = 0 THEN
Index1:= INDEXOF ( Thread1 );
Flag1:= CREATE_THREAD
(Index1,Tslice1,Runs1);
END_IF
73

Function Libraries
Thread and PLC_PRG ∗ :
The way the thread is processed compared with the freewheeling
control cycle not only depends on the thread's
parameters but also on the execution time of both the
thread and PLC_PRG.
TSLICE< thread execution time
start
PLC_PRG
time slice
PLC_PRG
TSLICE TSLICE
...
thread
...
PLC_PRG
time slice
PLC_PRG
...
thread
End of
PLC_PRG
process image
communication
time slice
PLC_PRG
In this case, PLC_PRG runs through a time slice of a size
of 800µs, i.e. at the end of this time processing it is
interrupted.
This is when the thread starts running for a time 'TSLICE'.
Task management then returns control to PLC_PRG etc.,
etc.
Once the last PLC_PRG command has been executed
the actions linked to PLC_PRG, i.e. refreshing the
process chart and communication, will be taken only to
resume the cycle with the first command again.
In our example, the threaded program is not completed
within a single TSLICE. If the program is shorter or
TSLICE is longer, the thread could also run more than
once within one TSLICE.
In any case, thread processing is stopped when it has run
the specified number of times.
∗ We are cutting out the influences that other processes may have.
TSLICE
74 E 700 GB
thread
time

4.4.2 Installing / Uninstalling a Timer Task
Function Libraries
A timer task is an executable unit within a program run
with several other processes being allowed to run at the
same time but without a time slice being allocated to the
timer task. In other words, this kind of timer task is run
exactly when it is requested to by a timer interrupt.
Timer task properties:
The program identified by its index is marked as a
separate process by the operating system and runs at
defined intervals, interrupting the process that is currently
running. The timer task is run once, then terminated and
the interrupted process is resumed.
Parameter Type Value Explanation
NPOU_IDparam WORD module index
TTIME WORD
Timer task usage:
1..
65535
time interval, in 1ms
(1ms..65,535s)
0 not allowed!
A timer task is beneficial wherever everything depends on
a high accuracy of repetition in time. Timer tasks work just
like timer modules in KUBES controllers.
The watchdog can be enabled.
The programmer must make sure that the timer task's
runtime never exceeds the time set as "TTIME".
75

Function Libraries
To install a timer task:
To install a program module as a timer task you must run
the following code to identify the module:
Index := INDEXOF (module name);
Afterwards, the following function just needs to be run
once in order to set up the timer task:
CREATE_TIMERTASK ( Index, TTIME );
FUNCTION CREATE_TIMERTASK : UINT
VAR_INPUT
NPOU_IDparam: WORD;
TTIME: WORD;
END_VAR
VAR
END_VAR
The value returned by the function tells you something
about the thread status.
Value returned Explanation
0 not installed, no timer task available
1 installed as timer task #1
Ventura Remote PLC only supports a single timer task at
a time.
To modify "TTIME" you must first uninstall the timer task,
set it to another value, and reinstall it.
76 E 700 GB

To uninstall a timer task:
Function Libraries
To no longer use a program module as a timer task, run
the following code:
Index := INDEXOF (module name);
Afterwards, run the following module in order to uninstall
the timer task:
DELETE_TIMERTASK ( Index );
FUNCTION DECREATE_TIMERTASK : BOOL
VAR_INPUT
NPOU_IDparam: WORD;
END_VAR
VAR
END_VAR
77

Function Libraries
start
PLC_PRG
Example:
You wish to turn a program module called
"TimerTask1ms" into a timer task. Add the following code
lines to the PLC_PRG module.
VAR
Index: WORD;
TTime: WORD:=1;
Flag: UINT;
END_VAR
IF Flag = 0 THEN
Index := INDEXOF ( Timertask1ms );
Flag := Create_Timertask(Index,TTime);
END_IF
Timer task and PLC_PRG:
"TimerTask1ms" interrupts the cyclic program, PRG_PLC,
every 1ms. The number of times the timer task is run and
the time it takes to actually run it adds to the execution
time of PRG_PLC.
timer task
next
PLC_PRG
timer task
1
1
ms
ms
runtime of PLC_PRG
1 ms
* PLC_PRG can be interrupted by other processes (see
section 4.4.1)
78 E 700 GB
next
PLC_PRG
timer task
PLC_PRG
end
time

4.4.3 Enabling / Disabling the Outputs
Function Libraries
The local outputs can be entirely switched off and on
electrically.
The function is equivalent to commands O_ON and
O_OFF in KUBES controllers.
ENADIS_OUTPUTS( Mode );
Parameter Type Value Explanation
mode WORD
0 disable
1 enable
FUNCTION ENADIS_OUTPUTS : BOOL
VAR_INPUT
Mode:WORD;
END_VAR
VAR
END_VAR
Example:
If input IN_00 is ON, all local outputs are to be OFF.
IF IN_00 THEN
ENADIS_OUTPUTS(0);
ELSE
ENADIS_OUTPUTS(1);
END_IF
79

Function Libraries
4.4.4 Direct Read of Local Inputs
You can read the current state of local inputs without
reference to the process image which is refreshed
automatically in a cyclic process.
To manually refresh the process image of inputs, run
function Flush_Inputs.
The effect of this function is similar to that of KUBES
module RD_IN found in KUBES controllers.
Prerequisite: Target and LZS version 02030207
Flush_Inputs:
Direct read of inputs (RD_IN)
Example:
FLUSH_INPUTS();
IF %IX0.0 THEN
....;
END_IF
80 E 700 GB

4.4.5 Direct Write of Local Outputs
Function Libraries
You can overwrite the current state of local outputs
without reference to the process image which is refreshed
automatically in a cyclic process.
Running function Flush_Outputs adapts the states of all
outputs to the states currently found in the process image.
The effect of this function is similar to that of KUBES
module WR_OUT
Prerequisite: Target and LZS version 02030207
Flush_Outputs:
Direct write of outputs (WR_OUT)
Example:
%QX0.0:=TRUE;
FLUSH_OUTPUTS();
81

Function Libraries
4.4.6 Installing an Error Module
An error module is run after an error event has occurred.
Error module properties:
Error modules are equivalent to the error interrupt
modules of KUBES controllers. If an error occurs, the
current process is interrupted and the error module is run.
The error module is run once, then terminated and the
interrupted process is resumed.
To install an error module:
To install a program as an error module you must run the
following code to identify the module:
Index := INDEXOF (module name);
Afterwards, run the following function in order to set up
the error module:
INSTALL_ERROR_IRQ ( Index, Channel );
After successful completion, the function returns TRUE.
Parameter Type Value Explanation
Index WORD module number
channel
(failure
mode)
WORD
0 low voltage (24 V)
1 short circuit
82 E 700 GB
2
internal low voltage (8V,
15V)
3 low voltage MMC

FUNCTION INSTALL_ERROR_IRQ : BOOL
VAR_INPUT
POU_ID: WORD;
Channel: WORD;
END_VAR
VAR
END_VAR
Example:
Function Libraries
Write a program module called "ErrorIRQmodule_0"
containing the reaction to the voltage being too low.
To install the module as an error interrupt module,
proceed as follows:
PROGRAM Init_Error_IRQ
VAR
Index0: WORD;
Init_Ready: BOOL;
END_VAR
IF NOT Init_Ready THEN
Index0:=INDEXOF(ErrorIRQmodule_0);
Init_Ready:=INSTALL_ERROR_IRQ (Index0,0);
END_IF
83

Function Libraries
4.4.7 Installing an Input IRQ Module
Changing states of inputs di0 to di3 of Ventura Remote
PLC generate interrupt requests (IRQs) which can
interrupt the processing of the current program and run an
IRQ module instead.
Input IRQ module properties:
Immediately after an interrupt request is received as
specified by the MODE instruction the program identified
by the "index" is run once. Then the interrupted program
is resumed.
Parameter Type Value Explanation
Index WORD module number
channel
WORD
mode WORD
0 input 0
1 input 1
2 input 2
3 input 3
0 no IRQ handling
1 rising edge
2 falling edge
3 both edges
To install a program module as an input IRQ module you
must run the following code to identify the module:
Index := INDEXOF (module name);
Afterwards, run the following function in order to set up
the input IRQ module:
84 E 700 GB

Function Libraries
INSTALL_INPUT_IRQ(index, channel, mode);
FUNCTION INSTALL_INPUT_IRQ : BOOL
VAR_INPUT
POU_ID: WORD;
Channel: WORD;
Mode : WORD;
END_VAR
VAR
END_VAR
Example:
I0 (SI_0) and I1 (SI_1) are interrupt inputs of Ventura
Remote PLC.
IN_00 and IN_01 are normal inputs of Ventura Remote
PLC.
� Write a program module called "Interrupt_I0" which is
to run when the I0 signal status changes from 0 to 1.
IN_00 is to stop the module from being run.
� Write a program module called "Interrupt_I1" which is
to run when the I1 signal status changes from 0 to 1
or from 1 to 0. IN_01 is to stop the module from being
run.
� Write a program module called "Init_Interrupt_IO" and
have the main program, PLC_PRG, run it.
85

Function Libraries
PROGRAM Init_Interrupt_IO
VAR
Index0: WORD;
Index1: WORD;
flag0:BOOL;
flag1:BOOL;
END_VAR
Index0:=INDEXOF(Interrupt_I0);
Index1:=INDEXOF(Interrupt_I1);
IF IN_00 AND NOT flag0 THEN
flag0:=INSTALL_INPUT_IRQ(Index0,0,1);
ELSE
flag0:=INSTALL_INPUT_IRQ(Index0,0,0);
END_IF
IF IN_01 AND NOT flag1 THEN
flag1:=INSTALL_INPUT_IRQ(Index1,1,3);
ELSE
flag1:=INSTALL_INPUT_IRQ(Index1,1,0);
END_IF
86 E 700 GB

4.4.8 Installing a REF IRQ Module
Function Libraries
A Ref impulse from Ventura Remote PLC's counter
interface generates an interrupt request (IRQ) which can
interrupt the processing of the current program and run an
IRQ module instead.
This requires that running an interrupt module (IRQmod)
following reference interrupt is admitted by the project
parameter settings made using the PLC Configuration
Editor.
To install a program module as a REF-IRQ module you
must run the following code to identify the module:
Index := INDEXOF (module name);
Afterwards, run the following function in order to set up
the error module:
REGIT_REFIRQ ( Index );
After successful completion, the function returns TRUE.
FUNCTION REGIT_REFIRQ: BOOL
VAR_INPUT
POU_ID: WORD;
END_VAR
VAR
END_VAR
87

Function Libraries
4.4.9 Installing a Reference Value IRQ Module
The count of Ventura Remote PLC's counter reaching the
reference value generates an interrupt request (IRQ)
which can interrupt the processing of the current program
and run an IRQ module instead.
This requires that running an interrupt module (IRQmod)
following reference value interrupt is admitted by the
project parameter settings made using the PLC
Configuration Editor.
To install a program module as a reference value IRQ
module you must run the following code to identify the
module:
Index := INDEXOF (module name);
Afterwards, run the following function in order to set up
the error module:
REGIT_T3IRQ ( Index );
After successful completion, the function returns TRUE.
FUNCTION REGIT_T3IRQ: BOOL
VAR_INPUT
POU_ID: WORD;
END_VAR
VAR
END_VAR
88 E 700 GB

4.4.10 Setting up the Watchdog
Function Libraries
Every task can have a watchdog (timer-controlled
monitor) to it.
Function "SET_WATCHDOG" can be used for both
setting the watchdog timeout and enabling/disabling
watchdog execution.
SET_WATCHDOG ( Mode, WDT_Time );
Parameter Type Value Explanation
mode WORD
WDT_Time WORD
0 disable
1 enable
0..49
50...
65535
FUNCTION SET_WATCHDOG: WORD
VAR_INPUT
Mode : WORD;
WDT_Time: WORD;
END_VAR
VAR
END_VAR
minimum monitoring time
50 ms
monitoring time in ms
50ms.. 65535ms
(t#1m5s535ms)
89

Function Libraries
Example:
Set the watchdog to 2.5 s
VAR
Mode : WORD:=1;
WDT_Time: WORD:=2500;
FirstCycle: BOOL:=TRUE;
END_VAR
IF FirstCycle THEN
SET_WATCHDOG ( Mode, WDT_Time );
FirstCycle:=FALSE;
END_IF
;
90 E 700 GB

4.5 Library MMC.LIB
Function Libraries
Together with the Target installation data (see page 53)
CoDeSys is sent libraries provided by the target system,
Ventura Remote PLC.
� MMC.lib provides the functions and function modules
Ventura Remote PLC needs to use the multimedia
card as a data memory.
MMC.lib contains the following:
Name Purpose
MMC_Attach registers with the file system
MMC_FileClose closes a file
MMC_FileCopy copies files
MMC_FileDelete deletes a file
MMC_FileFreeSpace finds out how much space is left on the MMC
MMC_FileMkDir creates a subdirectory
MMC_FileMove moves a file
MMC_FileOpen opens a file
MMC_FileRead reads from a file
MMC_FileRename renames a file
MMC_FileSeek sets the edit bookmark in a file
MMC_FileWrite writes to a file
MMC_InitMMC initialises the file system
MMC_ORC opens, reads, closes a file
MMC_OWC opens, writes, closes a file
Internal functions Purpose
MMC_PostCommand sends a command to the file system
MMC_WaitCmd waits for a job to complete
Do not use the internal functions or the internal variables
defined in the function modules for the user program!
91

Function Libraries
4.5.1 Procedure
Start with the obvious first steps:
� Register with the file system
� Initialise the file system
The next steps depend on what you wish to do, e.g. to
exchange data between the PLC and the MMC:
� Open a file
� Write/read data
� Close the file
The Target installation for Ventura Remote PLC includes
a sample program called "TST_PLC+_MMC" which is
stored in folder "C:\Programs\Shared\CAA-
Targets\Kuhnke\Samples".
To check the card functions, first plug a MMC into
Ventura Remote PLC.
Remember to close all files before you turn off the PLC or
remove the card from the slot.
92 E 700 GB

4.5.2 Registering with the File System
Function Libraries
Function "MMC_Attach" enables the user program to
register with the file system. The transfer parameter is a
pointer to "systeminfo", a global variable of data type
"MMC_SYSINFO" which is defined in library MMC.LIB.
In "systeminfo", the runtime system stores a link to the file
system. The file system can be used only if this link is
found.
Parameter Typ
e
MMC_Attach INT
Value Explanation
1 successfully registered
0 error
FUNCTION MMC_Attach : INT
VAR_INPUT
pSysInfo:POINTER TO MMC_SYSINFO;
END_VAR
Example:
PROGRAM Call_MMC
VAR
INIT_MMC : BOOL := TRUE ;
OK : INT;
END_VAR
IF INIT_MMC THEN
OK := MMC_Attach(ADR(systeminfo)) ;
INIT_MMC := FALSE;
END_IF
93

Function Libraries
4.5.3 Closing a File
"MMC_FileClose" allows you to close an open file by
transferring the file handle of the open file.
This is an asynchronous Function Block. It transfers the
job to the file system and checks if it has been completed.
It needs to be run until the job has been handled
successfully.
Parameter Type Value Explanation
handle INT file handle
result INT
0 running
< 0 error
> 0 job done
FUNCTION_BLOCK MMC_FileClose
VAR_INPUT
handle:INT;
END_VAR
VAR_OUTPUT
result:INT;
END_VAR
94 E 700 GB

4.5.4 Copying Files
Function Libraries
"MMC_FileCopy" allows you to copy a file by copying file
'adrname1' to file 'adrname2'.
This is an asynchronous Function Block. It transfers the
job to the file system and checks if it has been completed.
It needs to be run until the job has been handled
successfully.
Parameter Type Value Explanation
adrname ADR(source file)
POINTER
TO STRING
adrname2
Value
ADR(destination file)
result INT
0 running
< 0 error
> 0 job done
FUNCTION_BLOCK MMC_FileCopy
VAR_INPUT
adrname1 : POINTER TO STRING;
adrname2 : POINTER TO STRING;
END_VAR
VAR_OUTPUT
result:INT;
END_VAR
95

Function Libraries
4.5.5 Deleting a File
"MMC_FileDelete" allows you to delete a file.
This is an asynchronous Function Block. It transfers the
job to the file system and checks if it has been completed.
It needs to be run until the job has been handled
successfully.
Parameter Type Value Explanation
adrname
result INT
POINTER
TO STRING
ADR(file name)
0 running
< 0 error
> 0 job done
FUNCTION_BLOCK MMC_FileDelete
VAR_INPUT
adrname : POINTER TO STRING;
END_VAR
VAR_OUTPUT
result:INT;
END_VAR
96 E 700 GB

4.5.6 Determining the Free MMC Space
Function Libraries
"MMC_FileFreeSpace" allows you to find out how much
space is left on the MMCard.
This is an asynchronous Function Block. It transfers the
job to the file system and checks if it has been completed.
It needs to be run until the job has been handled
successfully.
Parameter Type Value Explanation
device
POINTER
TO STRING
ADR(CardName)
space DINT free space in byte
result INT
0 running
< 0 error
> 0 job done
FUNCTION_BLOCK MMC_FileFreeSpace
VAR_INPUT
device : POINTER TO STRING;
END_VAR
VAR_OUTPUT
space:DINT;
result:INT;
END_VAR
97

Function Libraries
4.5.7 Creating a Subdirectory
"MMC_MKDIR" allows you to create a subdirectory.
This is an asynchronous Function Block. It transfers the
job to the file system and checks if it has been completed.
It needs to be run until the job has been handled
successfully.
Parameter Type Value Explanation
device
result INT
POINTER
TO STRING
ADR(path)
0 running
< 0 error
> 0 job done
Paths must obey the following convention:
� The drive letter is always prefixed (leave out the " \ " )
� Subdirectories are separated by " \ ".
Sample path: A:DIR1\DIR2
FUNCTION_BLOCK MMC_FileMkDir
VAR_INPUT
device : POINTER TO STRING;
END_VAR
VAR_OUTPUT
result:INT;
END_VAR
98 E 700 GB

4.5.8 Moving a File
Function Libraries
"MMC_FileMove" allows you to move a file.
The file will be moved from 'adrname' to 'adrname2'. You
can specify different subdirectories.
This is an asynchronous Function Block. It transfers the
job to the file system and checks if it has been completed.
It needs to be run until the job has been handled
successfully.
Parameter Type Value Explanation
adrname
POINTER
ADR(source file)
adrname2
TO STRING
ADR(destination file)
result INT
0 running
< 0 error
> 0 job done
Files are moved compliant to the following convention:
� The drive letter is prefixed to the source file only.
� Specify the path to the destination file.
� Always suffix the file extension (separated by a dot).
Source file example: A:DIR1\Text1.txt
Destination file example: DIR1\Text2.txt
99

Function Libraries
FUNCTION_BLOCK MMC_FileMove
VAR_INPUT
adrname : POINTER TO STRING;
adrname2 : POINTER TO STRING;
END_VAR
VAR_OUTPUT
result:INT;
END_VAR
100 E 700 GB

4.5.9 Opening a File
Function Libraries
"MMC_FileOpen" allows you to open a file.
This is an asynchronous Function Block. It transfers the
job to the file system and checks if it has been completed.
It needs to be run until the job has been handled
successfully.
Parameter Type Value Explanation
adrname
mode UINT
POINTER
TO STRING
ADR(file name)
0 create and open file
1 open file to read
2 open file to read/write
handle INT file handle
result INT
0 running
< 0 error
> 0 job done
'mode' constant defined Type Value
MMC_OPENMODE_CREATE 0
MMC_OPENMODE_READ UINT 1
MMC_OPENMODE_READ_WRITE
MMC_OPENMODE_CREATE will delete a file of the
same name.
The file handle is returned as 'handle' which is required for
any subsequent operations such as read, write, or close.
2
101

Function Libraries
FUNCTION_BLOCK MMC_FileOpen
VAR_INPUT
adrname : POINTER TO STRING;
mode:UINT;
END_VAR
VAR_OUTPUT
handle:INT;
result:INT;
END_VAR
102 E 700 GB

4.5.10 Reading from a File
Function Libraries
"MMC_FileRead" lets you read data from a file. The
parameters required are the file handle of the open file, a
pointer to a buffer plus the number of bytes to be read.
This is an asynchronous Function Block. It transfers the
job to the file system and checks if it has been completed.
It needs to be run until the job has been handled
successfully.
Parameter Type Value Explanation
handle INT file handle
buff DWORD pointer to read buffer
count INT
result INT
number of bytes to be
read
0 running
< 0 error
> 0 job done
FUNCTION_BLOCK MMC_FileRead
VAR_INPUT
handle:INT;
buff:DWORD;
count:INT;
END_VAR
VAR_OUTPUT
result:INT;
END_VAR
103

Function Libraries
4.5.11 Renaming a File
"MMC_FileDelete" allows you to rename a file by
changing the name of 'adrname' to 'adrname2'.
This is an asynchronous Function Block. It transfers the
job to the file system and checks if it has been completed.
It needs to be run until the job has been handled
successfully.
Parameter Type Value Explanation
adrname POINTER ADR(old name)
adrname2 TO STRING ADR(new name)
result INT
0 running
< 0 error
> 0 job done
Files are renamed compliant to the following convention:
� The drive letter is prefixed to the source file only.
� Specify the path to the destination file.
� Always suffix the file extension (separated by a dot).
FUNCTION_BLOCK MMC_FileRename
VAR_INPUT
adrname : POINTER TO STRING;
adrname2 : POINTER TO STRING;
END_VAR
VAR_OUTPUT
result:INT;
END_VAR
104 E 700 GB

4.5.12 Setting the Edit Bookmark of a File
Function Libraries
Use "MMC_FileSeek" to add an edit bookmark to an open
file which allows you to access the contents of the file at
any point by transferring the file handle of the open file.
Note that the edit bookmark cannot be moved to
somewhere after the end of the file.
This is an asynchronous Function Block. It transfers the
job to the file system and checks if it has been completed.
It needs to be run until the job has been handled
successfully.
Parameter Type Value Explanation
handle INT file handle
offset UDINT offset from the start of file
result INT
0 running
< 0 error
> 0 job done
FUNCTION_BLOCK MMC_FileSeek
VAR_INPUT
handle:INT;
offset:UDINT;
END_VAR
VAR_OUTPUT
result:INT;
END_VAR
105

Function Libraries
4.5.13 Writing to a File
"MMC_FileRead" lets you write data to a file. The
parameters required are the file handle of the open file, a
pointer to a buffer plus the number of bytes to be written.
This is an asynchronous Function Block. It transfers the
job to the file system and checks if it has been completed.
It needs to be run until the job has been handled
successfully.
Parameter Type Value Explanation
handle INT file handle
buff DWORD pointer to write buffer
count INT
result INT
number of bytes to be
written
0 running
< 0 error
> 0 job done
FUNCTION_BLOCK MMC_FileWrite
VAR_INPUT
handle:INT;
buff:DWORD;
count:INT;
END_VAR
VAR_OUTPUT
result:INT;
END_VAR
106 E 700 GB

4.5.14 Initialising the File System
Function Libraries
Use "MMC_InitMMC" to re-initialise the file system after
changing the medium. You are advised to run this function
every time you change cards because the file system will
otherwise perform uncontrolled data access.
This is an asynchronous Function Block. It transfers the
job to the file system and checks if it has been completed.
It needs to be run until the job has been handled
successfully.
Parameter Type Value Explanation
result INT
FUNCTION_BLOCK MMC_InitMMC
VAR_INPUT
END_VAR
VAR_OUTPUT
result:INT;
END_VAR
0 running
< 0 error
> 0 job done
107

Function Libraries
4.5.15 Opening, Reading, Closing a File
"MMC_ORC" lets you read data from a file. The function
will open the file, read the set number of data bytes, and
close the file again afterwards. Users therefore need not
worry about the file handle.
Parameter Type Value Explanation
name DWORD ADR(file name)
buff DWORD pointer to read buffer
count INT
pSysInfo POINTER
TO STRING
error INT
finished BOOL
start BOOL
number of bytes to be
read
ADR(systeminfo)
0 no error
? error code
TRUE function performed
FALSE executing function
TRUE start function
FALSE stop function
� Use 'start' to repeatedly run the function.
� 'Finished' is TRUE when the defined process is
complete.
� There is no error if 'error' = 0 at that point; otherwise
you can get the error code.
108 E 700 GB

Function Libraries
FUNCTION_BLOCK MMC_ORC
VAR_INPUT
name:DWORD;
buff: DWORD;
count: INT;
pSysInfo:POINTER TO MMC_SYSINFO;
END_VAR
VAR_OUTPUT
error: INT:=0;
finished:BOOL:=FALSE;
END_VAR
VAR_IN_OUT
Start:BOOL;
END_VAR
109

Function Libraries
4.5.16 Opening, Writing, Closing a File
"MMC_OWC" lets you write data to a file. The function will
open the file, write the set number of data bytes, and
close the file again afterwards. Users therefore need not
worry about the file handle.
Parameter Type Value Explanation
name DWORD ADR(file name)
mode UINT
0 create and open file
1 read access to file
2 read/write access to file
buff DWORD pointer to write buffer
count INT
pSysInfo POINTER
TO STRING
error INT
finished BOOL
start BOOL
number of bytes to be
read
ADR(systeminfo)
0 no error
? error code
TRUE function performed
FALSE executing function
TRUE start function
FALSE stop function
'mode' constant defined Type Value
MMC_OPENMODE_CREATE 0
MMC_OPENMODE_READ UINT 1
MMC_OPENMODE_READ_WRITE
MMC_OPENMODE_CREATE will delete a file of the
same name.
110 E 700 GB
2

� Use 'start' to repeatedly run the function.
Function Libraries
� 'Finished' is TRUE when the defined process is
complete.
� There is no error if 'error' = 0 at that point; otherwise
you can get the error code.
FUNCTION_BLOCK MMC_OWC
VAR_INPUT
name:DWORD;
mode:UINT;
buff: DWORD;
count: INT;
pSysInfo:POINTER TO MMC_SYSINFO;
END_VAR
VAR_OUTPUT
error: INT:=0;
finished:BOOL:=FALSE;
END_VAR
VAR_IN_OUT
Start:BOOL;
END_VAR
111

PLC States
4.6 PLC States
4.6.1 RUN
4.6.2 STOP
4.6.3 Online Reset
Events and commands cause the PLC to adopt different
states.
� The user program is running.
� The PROFIBUS state is either "Operate" or it remains
"Offline". Data is transferred via the external process
image which is not synchronised with the user
program cycle.
� The user program stops running between two cycles.
� PROFIBUS retains its state, i.e. "Operate".
� The user program no longer runs.
� The state of PROFIBUS changes to "Clear". Zeros
are sent to the DP slave outputs. The reaction of the
remote data depends on the peripheral (DP slave).
� Except for the Retain variables (VAR RETAIN), all
variables are reset to the value that they were
originally initialised to (also applies to the variables
declared as VAR PERSISTENT!!). Variables not
explicitly assigned an initialisation value are set to
their default initial values (e.g. integers are set to 0).
Prior to overwriting the variables, CoDeSys displays a
security prompt.
A Reset is the same switching off the controller and
turning it back on (warm boot) while the program is
running.
112 E 700 GB

4.6.4 Online Reset (cold)
4.6.5 Reset (original)
� The user program no longer runs.
� All variables are reset.
PLC States
This command is very similar to the Reset command,
except that all variables - including the Retain variables -
are reset to their initialisation values.
Online Reset (cold) is the same as launching a program
when it has first been loaded into the controller (cold
boot).
� The user program is cleared. The controller is
returned to its original unmodified state.
� All variables, including the remanent ones (VAR
RETAIN and VAR PERSISTENT) are reset to their
initialisation values.
The CoDeSys runtime system does not support the
"PERSISTENT" property of variables.
113

4.7 Programming Using CoDeSys
114
Programming
The sections below explain some basic details you need
to know to use CoDeSys for writing your user programs.
4.7.1 Variables/Addresses
All memory cells that can be addressed by the user
program for signal processing or data storage are referred
to as variables. There are two basic types of variables:
� Variables with a set address:
These variables are inputs, outputs or internal
memory cells of the control unit which can be directly
accessed by the user program.
� External PROFIBUS operands:
These variables are either declared locally in a
module's declaration section, or globally in the list of
global variables. CoDeSys defines the address in the
controller when the variables are "interpreted".

4.7.2 Variables with Set Addresses
4.7.2.1 Local Inputs and Outputs
Group Input Function Type Qty
I
Q
%IX0.0 inputs 16/32 %IX0.0
Input Range
from to
%IX0.15
(%IX1.15)
PROFIBUS-DP
Comment
standard IN
%IX12.0 inputs 4 %IX12.0 %IX12.3 interrupt IN
%QX0.0 outputs 16/32 %QX0.0 %QX0.15
BOOL
(%QX1.15)
standard OUT
%QX10.0 outputs
4 %QX0.0 %QX10.3
special/clock
OUT
I %IW2 inputs 4 %IW2 %IW5 analogue IN
Q %QW2 outputs
WORD
2 %QW2 %QW3 analogue OUT
Q %QW8 parameter
2 %QW8 %QW9
clock output
frequency
I %ID3 parameter 3 %ID3 %ID5 counter
Q %QD2 parameter DWORD
2 %QD2 %QD3 counter
4.7.2.2 Internal Markers
Group Input Function Type Qty
Input Range
from to
MX %MX0.0 BOOL 2048 %MX0.0 %MX2047.15
MB %MB0 BYTE 4096 %MB0 %MB4095
Marker
MW %MW0 WORD 2048 %MW0 %MW2047
MD %MD0
DWORD 1024 %MD0 %MD1023
Comment
There is a marker range exactly 4096 byte in size.
MX, MB, MW and MD are just different ways of accessing
the same marker range.
The first byte in a word is byte #0.
Bits are stored by word. The first bit in a word is bit #0.
115

Programming
Examples:
� Address %MD48 points to bytes no. 192, 193, 194
and 195 (48 * 4 = 192).
� %MX5.0 accesses the first bit of word #6.
%MX999.15 accesses the sixteenth bit in word
#1000.
Addresses %MB0...MB19 hold the diagnostic information
of the expansion modules.
These addresses are not available for general use.
For further information on programming, use of
commands, and example programs please refer to the
CoDeSys online help engine.
116 E 700 GB

4.8 Extraremanent Data
4.8.1 Remanence Compliant to IEC 11631-3
117
Remanent Data
Retain variables are re-initialised when a program has
been transferred (i.e. they are set =0 unless another initial
value has been defined).
(Since all data references in the newly loaded program
may have changed, it would be the safest approach to
simply clear all Retain data.)
IEC 11631-3 rules that persistent data are re-initialised
following a reset.
If Retain and Persistent data are combined, a reset (cold)
or (origin) re-initialises the data.
This approach allows important operative data or recipes
to be safely stored at the commissioning and startup
stage.
The CoDeSys runtime system of PCControl 645-12M-PCI
and the Ventura SlotPLC does not support variable
property "PERSISTENT".
Property of variables "Retain" is not available for
variables with fixed addresses (%IB, %QB, %MB …)

Remanent Data
4.8.2 Extraremanent Data Range
Prerequisite: Ventura Remote PLC DP:
Target and LZS version 02030207
Ventura Remote PLC CAN:
Target and LZS version 02030106
To avoid the transfer of a program provoking the loss of
important data or data it took a lot of effort to enter, a
NVRAM area of 8 or 12 Kbytes was provided for safekeeping
data that the system will not delete at any time.
To keep things simple, these data are referred to as
"extraremanent data".
Controller Address Range
Ventura SlotPLC 8 Kbytes
PCControl 645-12M-
PCI-CoDeSys
Ventura Remote
PLC
8 Kbytes
from 16#404000
to 16#405FFF
from 16#1F4000
to 16#1F5FFF
12 from 16#204000
Kbytes to 16#206FFF
Data management of these data is entirely subject to the
user's responsibility.
� The extraremanent memory range is appended as a
subelement to the PLC configuration.
� This range is addressed by global variable "xrdata".
� The data type of "xrdata" is "XREMDATA". This data
type is specified by its name only. Its contents is to be
defined by the programmer with regard to the
application (see example below).
118 E 700 GB

Remanent Data
If an extraremanent memory range has been appended,
data type "XREMDATA" must needs be defined.
Otherwise, you will run into interpreter error
3740: unknown data type "XREMDATA"
Keep an eye on the size of "xrdata".
There will be no automatic monitoring with regard to
memory overflow.
Example:
Store extraremanent data of an operating hour counter
and a recipe.
• Step1: Enable the extraremanent memory range.
� Go to tab "Resources" and choose "PLC
Configuration".
� Select "Add, Append Subelement, xRemanente
Daten".
119

Remanent Data
• Step2: Define extraremanent data structure
� Go to tab "Data Types" and define the structure of
extraremanent data to be stored.
� Attach "Magic Numbers" to the beginning and end of
every block. Magic numbers are written once in a
defined manner and should be checked every time
the controller is switched on. They can be used to
verify whether the extraremanent data memory works
properly (e.g. battery charge status).
� Operating hour counter data block:
This structure is an example of some system data
such as a counter for system starts or an operating
hour counter.
(* What magic_numbers are good for:
The extraremanent data of this structure are regarded as valid only
if the magic_numbers return the correct value, in this case:
16#47110815. If not you can go to CheckXREMDATA and remove the
structure.*)
TYPE SystemData:
STRUCT
END_STRUCT
END_TYPE
magic_number:DWORD; (* key for the validity of
the extraremanent data *)
noof_SystemStarts:UDINT; (* count of system starts *)
secs:INT; (* second count *)
mins:INT; (* minute count *)
hors:INT; (* hour count *)
days:INT; (* day count *)
dummy:INT;
dummy2:INT;
magic_number2:DWORD; (* key for the validity of
the extraremanent data *)
120 E 700 GB

TYPE Extrarema_02:
STRUCT
END_STRUCT
END_TYPE
� Recipe data block:
This could be a structure for storing a recipe.
magic_number:DWORD;
Recipe_01:ARRAY [0..255] OF INT; (* 256 elements *)
magic_number2:DWORD;
TYPE XREMDATA :
STRUCT
END_STRUCT
END_TYPE
Remanent Data
� Combine data blocks in XREMDATA:
XREMDATA is stored in variable XRDATA and is
automatically extraremanent.
SysVars:SystemData;
Extrarema02:Extrarema_02;
• Step3: Program
FUNCTION CheckXREMDATA : BOOL
� Check if memory capacity is exceeded:
The extraremanent memory has a capacity of 12 kb.
This function should be used while the memory
concept is still being changed.
IF SIZEOF(xrdata) > 16#3000 THEN
ELSE
END_IF
CheckXREMDATA := FALSE;
CheckXREMDATA := TRUE ;
121

Remanent Data
PROGRAM operating time
� Operating hour counter:
This program compiles a count of the operating time
using elements from SystemData.
xrdata.SysVars.secs := xrdata.SysVars.secs +1 ;
IF xrdata.SysVars.secs >= 60 THEN
END_IF
xrdata.SysVars.secs := 0;
xrdata.SysVars.mins := xrdata.SysVars.mins +1 ;
IF xrdata.SysVars.mins >= 60 THEN
END_IF
xrdata.SysVars.mins := 0;
xrdata.SysVars.hors := xrdata.SysVars.hors + 1 ;
IF xrdata.SysVars.hors >= 24 THEN
END_IF
PROGRAM PLC_PRG
VAR
END_VAR
VAR RETAIN
END_VAR
xrdata.SysVars.hors := 0;
xrdata.SysVars.days := xrdata.SysVars.days + 1 ;
PLC_PRG
Checks if the extraremanent data are OK. Run "Clear" to
remove the data if they are not OK.
noof_SystemStarts counts the number of system starts.
Rema1 is a Retain variable. Use it to check the difference
to the extraremanent data.
flag: BOOL := TRUE ;
running: UDINT;
Start_OK: BOOL;
Clear: BOOL;
Rema1: UDINT;
122 E 700 GB

Start_OK := CheckXREMDATA(Clear);
IF flag AND Start_OK THEN
END_IF
xrdata.SysVars.noof_SystemStarts :=
Rema1:=Rema1+1;
flag := FALSE;
IF Start_OK THEN
(* The actual main program goes here. *)
END_IF
running:=running +1;
FUNCTION CheckXREMDATA : BOOL
VAR_INPUT
END_VAR
VAR
END_VAR
flag1:BOOL;
Remanent Data
xrdata.SysVars.noof_SystemStarts+1;
CheckXREMDATA:
Use the "magic words" to check if the remanent data are
OK. If the contents of the "magic words" changed they are
overwritten with the defined bit pattern. Depending on the
value of the "clear" input variable, the extraremanent
structures can be removed.
pSysVars: POINTER TO DWORD;
pExtrarema02: POINTER TO DWORD;
Size_SysVars: UINT;
Size_Extrarema02: UINT;
i: INT;
pByte: POINTER TO ARRAY[0..4095] OF BYTE;
123

Remanent Data
(*Check address and set pointer*)
pSysVars:=ADR(xrdata.SysVars.magic_number);
pExtrarema02:=ADR(xrdata.Extrarema02.magic_number);
(*Check size of extraremanent structures and set pointer*)
Size_SysVars:=SIZEOF (xrdata.Sysvars);
Size_Extrarema02:=SIZEOF (xrdata.Extrarema02);
(* Check structure1 of type SystemData an clear as necessary:
"SysVars" *)
IF ( xrdata.SysVars.magic_number 16#47110815 )
THEN
END_IF
OR ( xrdata.SysVars.magic_number2 16#47110815 )
IF clear THEN pByte := pSysVars;
END_IF
FOR i:=0 TO Size_SysVars DO
END_IF;
pByte^[i]:=0;
xrdata.SysVars.magic_number := 16#47110815;
xrdata.SysVars.magic_number2 := 16#47110815;
(* Check structure2 of type Extrarema_02 and clear as necessary:
"Extrarema02" *)
IF ( xrdata.Extrarema02.magic_number 16#47110815 )
THEN
END_IF
OR ( xrdata.Extrarema02.magic_number2 16#47110815 )
IF clear THEN pByte := pExtrarema02;
END_IF
FOR i:=0 TO Size_Extrarema02 DO
END_IF;
pByte^[i]:=0;
xrdata.Extrarema02.magic_number := 16#47110815;
xrdata.Extrarema02.magic_number2 := 16#47110815;
124 E 700 GB

5 Software
Software
Read this section to know how to write Ventura Remote
PLC programs.
� What you should know about the user program
memory.
� How to program the functions of counters and digital
and analogue inputs and outputs.
� Which commands and operands are available and
which addressing options you have.
5.1 The User Program Memory
The following memory is available to users:
Allocation Type Capacity
program code
(boot project)
flash 192 Kbytes
program code RAM 192 Kbytes
global variables RAM 48 Kbytes
M markers RAM 4 Kbytes
inputs RAM 0.5 Kbytes
outputs RAM 0.5 Kbytes
retain variables NV-RAM 16 Kbytes
Data stored in the flash EPROM cannot be modified when
the PLC is running.
Whereas RAM data can be modified at runtime, it will also
be lost when power is turned off.
NV-RAM data can be modified at runtime and is retained
when power is turned off.
125

Software
5.2 Programming Using CoDeSys
5.2.1 Overview of I/O Variable Addresses
5.2.1.1 Digital Inputs and Outputs
Module I/Os %IXy.z and %QXy.z
� I/Os of the basic module
� I/Os of the expansion modules which are attached to
the core Ventura Remote PLC unit by a ribbon cable.
Further configuration options are with the user who
integrates the appropriate expansion modules as
required. Module I/Os are mapped onto the process
image and refreshed between program cycles. Whereas
the basic module is accessed directly, the expansion
modules are accessed via a serial bus. To directly get the
signal states of the basic module, run function
FLUSH_INPUTS or FLUSH_OUTPUTS.
To view the addresses of module I/Os run the CoDeSys
PLC Configuration Editor.
I/Os are automatically addresses with respect to the
configuration.
Ventura Remote PLC 16DI/16DO plus 16DI/16DO
expansion module configuration example:
Basic module (693.723.22.01):
Digital inputs: %IB0-%IB1
Digital outputs: %QB0-%QB1
Expansion module (693.622.22)
Digital inputs: %IB28-%IB29
Digital outputs: %QB24-%QB25
126 E 700 GB

Internal combi I/Os %IX0.0-%IX0.3 and
%QX0.0-%QX0.3
Software
The basic unit hosts a set of some I/Os which can be
assigned both normal and special functions.
� Inputs "read" the signals of switches, push-buttons,
initiators, etc. The generate interrupts and run the
input IRQ modules. The signal state is entered into
the process image.
Run function FLUSH_INPUTS to directly get the
signal states of internal inputs and of the inputs of the
basic module.
� Outputs deliver control signals to relays, contactors,
solenoids, etc. in order to turn them on or off. The
CPU enters the signals into the process image
depending on user program instructions. The output
data in the process image are sent to the outputs
between every two PLC cycles. Run function
FLUSH_OUTPUTS to directly get the signal states of
internal outputs and of the outputs of the basic
module.
If set up accordingly, the internal outputs can also be
used as clock pulse outputs for actuating stepper
motors compliant to a frequency table stored in the
PLC memory. The PLC program selects the correct
values from the table, maintaining a pulse-to-pause
ratio of 1:1 at all times. Whereas outputs do0 and do1
as well as do2 and do3 are actuated by the same
clock pulse, they can still be enabled and disabled
separately.
127

Software
5.2.1.2 Analogue inputs and outputs
Module I/Os %IWx and %QWy
These analogue I/Os attach as expansion modules to the
core Ventura Remote PLC unit by a ribbon cable. Further
configuration options are with the user who integrates the
appropriate expansion modules as required. I/Os are
mapped onto the process image and refreshed between
program cycles.
To view the operands of the module I/Os, run the
configuration utility and display the appropriate module
tab.
Example of 8AI Thermo used as Module0:
Inputs: %IW14-%IW21
Outputs: none
� Inputs "read" the analogue values of temperatures,
fill levels, speeds, etc. The A/D converter on the
module takes care of the analogue-to-digital
conversion. The digital value is sent to the CPU via
the process image and the expansion bus to be
further processed by the user program.
� Outputs send analogue control signals to drives etc.
in order to control and actuate them. The CPU
outputs the signals to a process image which puts
them onto the expansion bus according to user
program instructions. Digital-to-analogue conversion
is performed by the module. In the end, the analogue
signal is available at the appropriate terminal points.
128 E 700 GB

Internal I/Os AI_x and AO_x
I/O Variable Address
ai0 AI_0 %IW2
ai1 AI_1 %IW3
ai2 AI_2 %IW4
ai3 AI_3 %IW5
ao0 AO_0 %QW2
ao1 AO_1 %QW2
Software
Analogue I/Os are mapped onto the process image and
refreshed between program cycles.
� Inputs "read" the analogue values of temperatures,
fill levels, speeds, etc. The PLC processor takes care
of analogue-to-digital conversion. Digitized values
can be further processed by the user program.
� Outputs send analogue control signals to drives etc.
in order to control and actuate them. The analogue
output signal is generated as a PWM signal. Its
output frequency is set according to the chosen
resolution. The output voltage is determined by the
pulse-to-pause ratio. In the end, the smoothed
analogue signal is available at the appropriate
terminal points.
129

Software
5.3 Special Functions of Internal I/Os
For a description of the hardware and the location of
connectors refer back to section 3.4 (� p35 and
following).
Some of the internal I/Os can be used for special
functions which are described below.
The special functions are performed by means of software
modules which are component parts of the monitor
program.
5.3.1 Internal Digital Inputs/Outputs
5.3.1.1 Function Select
The di/do terminals start both input and output circuits.
They can thus be used either as
� interrupt inputs
� or normal outputs
� or clock pulse outputs
The inputs are operative at all times.
Before using a terminal as an output you must first decide
whether to set it up as a normal output or as a clock pulse
output. To make the selection, run the CoDeSys PLC
Configuration Editor.
� Choose "Resources, PLC Configuration, Kuhnke
Ventura Remote IO CAN (or DP), Internal IO, DO 4 /
Stepper 2"
� Set the module parameters of every channel.
Clock pulse output_x Address
Off normal output
On clock pulse
output(Taktausgang)
130 E 700 GB

Software
If an "Input IRQ module" has been set up for an input and
the same connector has been configured as a "clock
pulse output", the system will automatically block the
output as a "clock pulse output".
131

Software
5.3.2 Functions of Internal Inputs SI_0...SI_3
A change of input signals generates interrupts in the PLC.
You can set every input to have its rising edge, falling
edge or both edges to generate interrupts.
Select input/output function: (� 5.3.1.1).
To allocate program code to the interrupt request run
function INSTALL_INPUT_IRQ (� 4.4.7)
Sample program: (� 4.4.7 ff.)
132 E 700 GB

5.3.3 Functions of Internal Outputs (0.1 A)
SO_0...SO_3
The following functions are supported
� normal output
5.3.3.1 Normal Outputs
� clock pulse output
5.3.3.2 Clock Pulse Outputs
'Normal' output means that the output is enabled or
disabled as a continuous signal.
Software
'Clock pulse' output means that a clock pulse is enabled
or disabled as the output signal.
Clock pulse outputs are designed for the actuation or
stepper motor output stages, for example.
- The pulse-to-pause ratio of the clock pulse is always
1:1.
To start or stop a motor, the speed needs to go up or
down with reference to the time, which is realised by the
PLC program selecting the appropriate frequency.
� The value entered and the frequency are linked by an
allocation table which is stored in the PLC's monitor
program.
� The frequency is adjustable by selecting any of the
395 different frequencies on the list.
� Note that selecting '0' sets a frequency of 200 Hz
already.
� Whereas do0 and do1 as well as do2 and do3 are
actuated by the same clock pulse, they can still be
enabled and disabled separately.
Select input/output function (� 5.3.1.1)
The frequency is set by variables.
� To be shown information about these variables,
choose "Resources, PLC Configuration, Kuhnke
133

Software
Ventura Remote IO CAN (or DP), Internal IO, DO 4 /
Stepper 2".
Clock pulse output: frequency selection
Variable Address Value Comment
FREQ_0_1 %QW8 0..394 frequency for DO0 and DO1;
range: 200 Hz ...10000 Hz
FREQ_2_3 %QW9 0..394 frequency for DO2and DO13
range: 200 Hz ...10000 Hz
Example of clock pulse output to do2 and do3 at
200 Hz
FREQ_2_3:=0; (* 200Hz *)
SO_2:=TRUE; (* output to do2 *)
SO_3:=TRUE; (* output to do3*)
5.3.3.3 Clock Pulse Frequency Allocation Table
The value entered in FREQ_0_1 or FREQ_2_3 and the
clock pulse frequency are linked as follows:
Value Frequency Value Frequency Value Frequency Value Frequency
0 200.0 100 541.0 200 1463.2 300 3957.7
1 202.0 101 546.4 201 1477.8 301 3997.3
2 204.0 102 551.8 202 1492.6 302 4037.2
3 206.1 103 557.4 203 1507.5 303 4077.6
4 208.1 104 562.9 204 1522.6 304 4118.4
5 210.2 105 568.6 205 1537.8 305 4159.6
6 212.3 106 574.2 206 1553.2 306 4201.2
7 214.4 107 580.0 207 1568.8 307 4243.2
8 216.6 108 585.8 208 1584.4 308 4285.6
9 218.7 109 591.6 209 1600.3 309 4328.5
10 220.9 110 597.6 210 1616.3 310 4371.8
11 223.1 111 603.5 211 1632.4 311 4415.5
12 225.4 112 609.6 212 1648.8 312 4459.6
13 227.6 113 615.7 213 1665.3 313 4504.2
14 229.9 114 621.8 214 1681.9 314 4549.3
15 232.2 115 628.0 215 1698.7 315 4594.8
16 234.5 116 634.3 216 1715.7 316 4640.7
17 236.9 117 640.7 217 1732.9 317 4687.1
18 239.2 118 647.1 218 1750.2 318 4734.0
19 241.6 119 653.5 219 1767.7 319 4781.3
20 244.0 120 660.1 220 1785.4 320 4829.1
134 E 700 GB

Software
Value Frequency Value Frequency Value Frequency Value Frequency
21 246.5 121 666.7 221 1803.2 321 4877.4
22 248.9 122 673.3 222 1821.3 322 4926.2
23 251.4 123 680.1 223 1839.5 323 4975.5
24 253.9 124 686.9 224 1857.9 324 5025.2
25 256.5 125 693.7 225 1876.5 325 5075.5
26 259.1 126 700.7 226 1895.2 326 5126.2
27 261.6 127 707.7 227 1914.2 327 5177.5
28 264.3 128 714.8 228 1933.3 328 5229.3
29 266.9 129 721.9 229 1952.7 329 5281.6
30 269.6 130 729.1 230 1972.2 330 5334.4
31 272.3 131 736.4 231 1991.9 331 5387.7
32 275.0 132 743.8 232 2011.8 332 5441.6
33 277.7 133 751.2 233 2031.9 333 5496.0
34 280.5 134 758.7 234 2052.3 334 5551.0
35 283.3 135 766.3 235 2072.8 335 5606.5
36 286.2 136 774.0 236 2093.5 336 5662.5
37 289.0 137 781.7 237 2114.4 337 5719.2
38 291.9 138 789.5 238 2135.6 338 5776.4
39 294.8 139 797.4 239 2156.9 339 5834.1
40 297.8 140 805.4 240 2178.5 340 5892.5
41 300.8 141 813.5 241 2200.3 341 5951.4
42 303.8 142 821.6 242 2222.3 342 6010.9
43 306.8 143 829.8 243 2244.5 343 6071.0
44 309.9 144 838.1 244 2267.0 344 6131.7
45 313.0 145 846.5 245 2289.6 345 6193.0
46 316.1 146 855.0 246 2312.5 346 6255.0
47 319.3 147 863.5 247 2335.7 347 6317.5
48 322.4 148 872.2 248 2359.0 348 6380.7
49 325.7 149 880.9 249 2382.6 349 6444.5
50 328.9 150 889.7 250 2406.4 350 6508.9
51 332.2 151 898.6 251 2430.5 351 6574.0
52 335.5 152 907.6 252 2454.8 352 6639.8
53 338.9 153 916.6 253 2479.3 353 6706.2
54 342.3 154 925.8 254 2504.1 354 6773.2
55 345.7 155 935.1 255 2529.2 355 6841.0
56 349.2 156 944.4 256 2554.5 356 6909.4
57 352.7 157 953.9 257 2580.0 357 6978.5
58 356.2 158 963.4 258 2605.8 358 7048.3
59 359.7 159 973.0 259 2631.9 359 7118.7
60 363.3 160 982.8 260 2658.2 360 7189.9
61 367.0 161 992.6 261 2684.8 361 7261.8
62 370.6 162 1002.5 262 2711.6 362 7334.4
63 374.3 163 1012.5 263 2738.7 363 7407.8
64 378.1 164 1022.7 264 2766.1 364 7481.9
65 381.9 165 1032.9 265 2793.8 365 7556.7
66 385.7 166 1043.2 266 2821.7 366 7632.3
67 389.5 167 1053.7 267 2849.9 367 7708.6
68 393.4 168 1064.2 268 2878.4 368 7785.7
69 397.4 169 1074.8 269 2907.2 369 7863.5
70 401.4 170 1085.6 270 2936.3 370 7942.2
71 405.4 171 1096.4 271 2965.7 371 8021.6
72 409.4 172 1107.4 272 2995.3 372 8101.8
73 413.5 173 1118.5 273 3025.3 373 8182.8
74 417.6 174 1129.7 274 3055.5 374 8264.6
75 421.8 175 1141.0 275 3086.1 375 8347.3
135

Software
Value Frequency Value Frequency Value Frequency Value Frequency
76 426.0 176 1152.4 276 3116.9 376 8430.8
77 430.3 177 1163.9 277 3148.1 377 8515.1
78 434.6 178 1175.5 278 3179.6 378 8600.2
79 439.0 179 1187.3 279 3211.4 379 8686.2
80 443.3 180 1199.2 280 3243.5 380 8773.1
81 447.8 181 1211.2 281 3275.9 381 8860.8
82 452.3 182 1223.3 282 3308.7 382 8949.4
83 456.8 183 1235.5 283 3341.8 383 9038.9
84 461.3 184 1247.9 284 3375.2 384 9129.3
85 466.0 185 1260.3 285 3409.0 385 9220.6
86 470.6 186 1272.9 286 3443.0 386 9312.8
87 475.3 187 1285.7 287 3477.5 387 9405.9
88 480.1 188 1298.5 288 3512.3 388 9500.0
89 484.9 189 1311.5 289 3547.4 389 9595.0
90 489.7 190 1324.6 290 3582.8 390 9690.9
91 494.6 191 1337.9 291 3618.7 391 9787.8
92 499.6 192 1351.2 292 3654.9 392 9885.7
93 504.6 193 1364.8 293 3691.4 393 9984.6
94 509.6 194 1378.4 294 3728.3 394 10084.4
95 514.7 195 1392.2 295 3765.6
96 519.9 196 1406.1 296 3803.3
97 525.1 197 1420.2 297 3841.3
98 530.3 198 1434.4 298 3879.7
99 535.6 199 1448.7 299 3918.5
136 E 700 GB

5.3.4 Short-circuited Output
Software
Overload fuses out the outputs thermally. This section
describes an extra, software-controlled short circuit
monitoring which is available for normal outputs but not
for clock pulse outputs, though.
5.3.4.1 Combi Outputs di0...do3 (SO_0...SO_3)
A short-circuited output is turned off by the PLC. To undo
the switch-off you must first restart the PLC or choose
Online-CoDeSys-Reset. The short circuit error indicated
by the error LED will be reset only when you restart the
controller.
Getting the input states back from the inputs allows you to
check the PLC program for the output that was actually
short-circuited.
Getting the input states back from the inputs allows you
to check the PLC program for the output that was actually
short-circuited.
5.3.4.2 Digital Outputs of the Basic Module
A short-circuited output is turned off by a thermal fuse.
5.3.4.3 Interrupt Following Short Circuit
A short circuit to do0 ... do3 will generate an interrupt
request to the PLC. To allocate program code to the
interrupt request run function INSTALL_ERROR_IRQ
(� 4.4.6)
The module should contain the code to respond to the
request, e.g. to turn off some major or all outputs using
function ENADIS_OUTPUTS (� 4.4.3)
137

Software
5.3.4.4 Digital Outputs of Modules 0 to 3
A short-circuited output is turned off by a thermal fuse. To
notify the PLC of the short circuit, the module will set its
diagnostic byte to 1.
(Diagnostic addresses � section 5.6)
The output will be turned back on when the fuse has
cooled down. It is up to the programmer to decide about
switching off the outputs following a short circuit and
about how to respond to the event.
138 E 700 GB

5.3.5 Internal Analogue Input Functions
Ventura Remote PLC has:
- 4 analogue inputs ai0, ai1, ai2 and ai3
Software
� To set up the resolution of every analogue input and
to retrieve information about analogue input
variables, choose "Resources, PLC Configuration,
Kuhnke Ventura Remote IO CAN (or DP), Internal IO,
AI 4".
� Set the measuring range of every analogue input.
� Enable or disable the filter (for all analogue inputs).
� Analogue inputs read the analogue values of
temperatures, fill levels, speeds, etc. The processor
takes care of analogue-to-digital conversion. Digitized
values can be further processed by the user program.
Representation of analogue values:
The resolution is 10 bit. Values are shown as two's
complements in an integer-type variable.
139

Software
Measuring
range
Number of
digital values
Range of
values
0..+5 V 1024 0..16#7FE0
0..+10 V 1024 0..16#7FE0
Sample program:
The measuring range of channel 3 is set to 10V.
ai3 measures +10.0V.
140 E 700 GB

5.3.6 Internal Analogue Output Functions
Ventura Remote PLC has:
� 2 analogue outputs ao0 and ao1
Software
� Analogue outputs send analogue control signals to
drives etc. in order to control and actuate them.
Analogue outputs are designed as PWM outputs.
The voltage is set by the pulse-to-pause ratio plus
subsequent smoothing.
The resolution is used to set the output frequency
and, with it, the range of output voltages:
Resolution
(Aufloesung)
Number of
output values
Frequency
[kHz]
Ripple
8 bit 256 62.5 ±5mV
10 bit 1024 15.625 ±10mV
� To set up the resolution of every analogue output and
to retrieve information about analogue output
variables, choose "Resources, PLC Configuration,
Kuhnke Ventura Remote IO CAN (or DP), Internal IO,
AO 2".
Analogue output: resolution
� Disable unused analogue outputs via the PLC
Configuration Editor.
141

Software
Analogue output: output voltage
Program the output value as two's complement in an
integer-type variable.
Variable Address Value Comment
AO_0 %QW2 0..16#7FFF 0...+10V at do0
AO_1 %QW3 0..16#7FFF 0...+10V at do1
Depending on your setup, the value is implemented as an
8-bit or 10-bit value.
Sample program:
PROGRAM PLC_PRG
VAR
Value0: INT:= 16#7FFF;
Value1: INT:= 16#2000;
END_VAR
AO_0:=Value0; (*initial value +10V*)
AO_1:=Value1; (*initial value +2.5V*)
142 E 700 GB

5.3.7 Functions of Internal Counters
5.3.7.1 Event counter
Software
Ventura Remote PLC has A, B and Ref terminals for a
counter.
The counter can be used either as A, B, Ref counter or as
an event counter of pin A.
Run the PLC Configuration Editor to choose a counting
function. A, B, Ref is the default.
� Choose "Resources, PLC Configuration, Kuhnke
Ventura Remote IO CAN (or DP), Internal IO,
Counter1 A-BRef".
� Then choose "Extras, Replace element".
The event counter is a 16-bit ring counter which counts
the changes of pin A signals in the Sub-D plug.
5.3.7.1.1 Event Counter Setup
Run the PLC Configuration Editor to set up the event
counter.
� Choose "Resources, PLC Configuration, Kuhnke
Ventura Remote IO CAN (or DP), Internal IO,
Counter1 Event".
� Set the options as appropriate.
143

Software
run_IRQmod_after_timer_overflow
(Aufruf_Ubst_bei_Timerueberlauf)
Sets the module to running the reference value IRQ
module in the PLC program in response to the counter
reading going from 0 to -1 or from -1 to 0.
The IRQ module contains your code on how to react to
the interrupt request (IRQ module � section 4.4.9 )
up_down_count
(Zaehlrichtung)
Specifies whether the encoder value starts counting up
from 0 or down from 65535.
encoder_resolution
(Drehgeberaufloesung)
This parameter specifies the resolution of the rotary
encoder: single or double.
counter_enable
(Zaehlerfreigabe)
Globally enables or disables the event counter.
144 E 700 GB

5.3.7.1.2 Event Counter Variables
Variable Address Value Comment
CNTR_AV %IW6 WORD actual counter reading
CNTR_PV %QW4 WORD preset counter reading
Software
ACK_PV %IW7 WORD counter preset, acknowledge.
CNTR_CLR %QX5.0 BOOL clear count
ACK_CLR %IX8.0 BOOL clear count: acknowledge.
The counter preset is changed every time CNTR_PV is
modified. To check the new setting is returned to
ACK_PV.
The count is cleared every time CNTR_CLR is modified.
To check the new setting is returned to ACK_CLR.
145

Software
5.3.7.2 A, B, Ref Up/Down Counter
The A, B, Ref counter is a 32-bit counter that counts the
alternations of pin A and pin B signals. It can discriminate
phases to enable up/down count detection. The counter is
controlled either by the Ref impulse of an encoder or by a
sensor attached to the Ref input.
5.3.7.2.1 A, B, Ref Counter Setup
Run the PLC Configuration Editor to set up the A, B, Ref
counter.
� Choose "Resources, PLC Configuration, Kuhnke
Ventura Remote IO CAN (or DP), Internal IO,
Counter1 A-BRef".
� Set the options as appropriate.
Run_IRQmod_after_reference_value
(Aufruf_Ubst_bei_ Vergleichswert)
Setting to say whether or not a reference value IRQ
module is to be run when the count equals a reference
value.
The reference value can be 0 or set to any other value in
the user program.
The IRQ module contains your code on how to react to
the interrupt request (IRQ module � section 4.4.9)
Encoder resolution (single / 4_fold)
(Drehgeberauflösung (1_fach / 4_fach)
146 E 700 GB

Resolution of the rotary encoder: single or four-fold.
Reference interrupt
(Referenzinterrupt)
Software
Specifies whether an impulse received by the Ref input
will generate an interrupt request.
The next two parameters, i.e.
- run_IRQmod_after_reference_interrupt
- clear_counter_after_reference_interrupt
allow you to specify which of the two available functions
will be run.
Run_IRQmod_after_reference_interrupt
(Aufruf_Ubst_bei_Referenzinterrupt)
(only if reference interrupt = On).
Setting to say whether or not a ref IRQ module is to be
run when a ref impulse is received.
The IRQ module contains your code on how to react to
the interrupt request (IRQ module � section 4.4.8 )
You can use this function to prevent the user program
from running the interrupt module.
Clear_counter_after_reference_interrupt
(Zaehler_loeschen_bei_Referenzinterrupt)
(only if reference interrupt = On).
Specifies whether the current encoder value is to be
cleared when a ref impulse is received.
You can use this function to prevent the counter reading
from being cleared, e.g. if you just with the REF IRQ
Module to be run.
Clear_counter_after_reference_value
(Zaehler_loeschen_bei_Vergleichswert erreicht)
Specifies whether the counter reading is cleared or just a
reference value interrupt request is generated when the
count equals a previously set reference value.
A reference value IRQ will occur whenever a count equals
a reference value, no matter whether
clear_counter_after_reference_value is set or not.
147

Software
To suppress this function, set the reference value to 0!
Counter_enable
(Zaehlerfreigabe)
Globally enables or disables the A, B, Ref counter.
5.3.7.2.2 A, B, Ref Counter Variables
Variable Address Value Comment
INK_AV %ID3 WORD actual counter reading
INK_PV %QD2 WORD preset counter reading
ACK_PV %ID4 WORD counter preset, acknowledge.
INK_RV %QD3 BOOL reference value
ACK_RV %ID5 BOOL reference value, acknowledge.
Proceed as follows to set a preset value / reference value
for the incremental encoder in A, B, Ref mode:
First of all, the user program enters the preset value or
reference value into the output variables. The PLC
acknowledges the value by returning the same value to
the corresponding input variable. This enables the PLC
program to check whether a value has been accepted and
which value it is currently set to. A new preset value /
reference value is entered whenever there is a difference
between the output variable and the input variable.
148 E 700 GB

Software
5.4 Functions of the Basic Module's Inputs and
Outputs
5.4.1 Functions of Inputs SDE_0...SDE_1 (SDE_3)
The 16 (or 32) inputs of the basic module are normal
inputs without any special function.
5.4.2 Functions of Outputs SDO_0... SD0_1 (SD0_3)
The 16 (or 32) outputs of the basic module are normal
outputs without any special function.
A short-circuited output is not turned off by the PLC.
Overload simply fuses out the outputs thermally. You are
advised to provide means of preventing the output from
turning back on after cooling down.
The short-circuited output generates an interrupt request.
To allocate program code to the interrupt request run
function INSTALL_ERROR_IRQ
(� 4.4.6)
The module should contain the code to respond to the
request, e.g. to turn off some major or all outputs using
function ENADIS_OUTPUTS (� 4.4.3)
149

Software
5.5 Start after Configuration Error
When the system is started it checks the actual module
configuration and compares it with the module
configuration set in the project. You can say how the PLC
is to react at startup:
- start if set configuration actual configuration
- do not start if set configuration actual configuration
(� section 4.3.4.2 )
5.6 Functions of Expansion Modules 0...3
Modules 0..3 are the expansion modules of Ventura
Remote PLC.
Run the CoDeSys PLC Configuration Editor to allocate
the modules in the slots to modules 0..3 of Ventura
Remote PLC (external I/O PLC, empty slot)
(� section 4.3.4.2 )
The Configuration Editor will afterwards show the I/O
addresses assigned to the module.
Module parameter setup:
There are 24 parameter bytes available for every module.
These parameters let you set the specific properties of the
I/O modules.
(� section 4.3.4.2 )
For detailed information about the adjustable properties of
the expansion modules please refer to the module
descriptions in E698GB (instruction manual Ventura
Remote I/O).
150 E 700 GB

5.7 Status Messages of Expansion Modules
0...3
Software
At startup, Ventura Remote PLC checks if modules 0...3
are properly configured and whether the set configuration
matches the actual configuration. During operation, the
correct functioning of the modules is monitored.
Any diagnostic information sent by an expansion module
is made available as module diagnostics by Ventura
Remote PLC.
Ventura Remote PLC DP also logs all diagnostic module
information and sends it to the PROFIBUS master as
extended diagnostic information.
(� section 6.2.3.2 )
Ventura Remote PLC module diagnostics:
There are 5 diagnostic bytes available for every module.
Addresses %MB0...MB19 hold the diagnostic information
of the expansion modules.
Module0 Module1 Module2 Module3 Diagnosis
%MB0 %MB5 %MB10 %MB15 byte0
%MB1 %MB6 %MB11 %MB16 byte1
%MB2 %MB7 %MB12 %MB17 byte2
%MB3 %MB8 %MB13 %MB18 byte3
%MB4 %MB9 %MB14 %MB19 byte4
Please read the module descriptions in E698GB
(instruction manual Ventura Remote I/O) to know which
byte contains exactly which states/events.
151

Software
Example: 16DI/16DO module:
Address Bit Value Allocation
%MB0 0 not used
0 1 short-circuited output
%MB1
1 1 low voltage supplied to
module
2..7 0 not used
%MB2 0 not used
%MB3 0 not used
%MB4 0..255 software version
Addresses %MB0...MB19 hold the diagnostic information
of the expansion modules.
These addresses are not available for general use.
(Internal marker range � section 4.7.2.2 )
152 E 700 GB

6 PROFIBUS-DP
6.1 Basic Information
PROFIBUS
At this point, we will only very briefly touch upon the key
properties of PROFIBUS-DP.
For more detailed information, please refer to instruction
manual E 611 GB, PROFIBUS-DP.
6.1.1 What is PROFIBUS?
6.1.2 Bus Protocol
6.1.3 Topology
PROFIBUS is a field bus. Its name is an acronym for
"Process Field Bus". PROFIBUS has been developed to
network multiple control units while maintaining a link to
the field level, i.e. to the sensors and actuators, via
remote I/Os.
At the same time, it interfaces with the control level where
one or several process computers may be installed to
control the overall process.
Ventura Remote PLC DP is a PROFIBUS-DP slave.
Open communication
The principle of open communication is to ensure that
devices of various manufacturers can exchange data.
European standard EN 50170 sets the standard for this
field bus.
PROFIBUS is constructed as a line. Using repeaters, you
can also create a tree structure. The number of stations
on any one segment is limited to 32. Where that is not
enough, you can establish a second segment which is
connected to the first segment by a repeater (bidirectional
line amplifier).
153

PROFIBUS
6.1.4 Station Address
Repeaters also count as physical stations so that the
number of "real" stations on the line is reduced to 31 (or to
30 if 2 repeaters are used.
Up to 3 repeaters are supported, boosting the total
number of bus stations to 122.
Every logical PROFIBUS station is assigned its own
station address that other stations use to access this
station. Station addresses can be anything between 0 and
126.
The PROFIBUS station address of Ventura Remote PLC
DP is set by the software in the DP master project.
6.1.5 Network Configuration
To define a Kuhnke controller as the master, run the
VEBES configuration tool to build the PROFIBUS
network.
To define a Kuhnke CoDeSys controller as the master,
run the CoDeSys configuration tool to build the
PROFIBUS network. Within this network, Ventura Remote
PLC DP is configured and set up as a slave.
154 E 700 GB

6.2 Master-Slave Communication
PROFIBUS
Read this section to obtain basic information about how to
integrate Ventura Remote PLC in a network system.
6.2.1 Device Master File KUHN690B.GSD
File "KUHN690B.GSD" contains the master data of DP
slave unit Ventura Remote PLC. You need the file
whenever you wish to add the device to a DP network
using a PROFIBUS configuration utility.
Graphics-ready configuration tools can also show a
picture of the DP slaves. The graphics file showing
Ventura Remote PLC is "KU_6902n.DIB". (In case your
configuration utility accepts ".BMP" files only, pass the
".DIB" file through a graphics application that is able to
convert the file).
Sources:
� Internet
http://kuhnke.de
including CoDeSys targets for Kuhnke's CoDeSys DP
master controllers
� Internet
http://kuhnke.de
Download page or product page
155

PROFIBUS
Step
0 1
1
2
3
4
Initialising
After starting the master it will first of all initialise the
slaves:
Sent by Frame
Recipient
Station SAP
Station SAP
master 62 set parameters slave 61
slave - single code acknowl. master -
master 62 get diagnostic data slave 60
slave 60 diagnostic data master 62
master 62 set parameters slave 61
slave - single code acknowl. master -
master 62 check configuration slave 62
slave - single code acknowl. master -
master 62 get diagnostic data slave 60
slave 60 diagnostic data master 62
If the DP slave has no device-specific problem it returns 6
bytes of standard diagnostic data, i.e. initialisation was
successful and data communication can commence. If
there was a problem it will append the device-specific
diagnostic data. In this case, no connection will be
established and initialisation will be repeated starting with
Step 1.
1 Step 0 is taken by the following masters only:
Profi Control 680I, DP master module of system 680 (500 kbps), PC Control 645-500
156 E 700 GB

6.2.2 Receive Parameter Data (Prm_Data)
PROFIBUS
The parameters of passive stations (slaves) are set during
DP system startup. The master transmits all parameter
data to the DP slave (here: Ventura Remote PLC DP).
The master is also allowed to send/change parameter
settings during operation.
The first 7 bytes (octets 1...7) contain the general bus
parameters. They are obligatory for all DP slaves and
generally supported by the usual configuration tools.
Starting with byte 8, you can transmit device-specific
parameters. These parameters deserve special attention
because they affect the functions of the unit concerned.
6.2.2.1 General Bus Parameters
Octet 1: Station_status
See EN 50170, "Parameter Data Transmission" for details
Octet 2: WD_Fact_1
Range: 1...255
Octet 3: WD_Fact_2
Range: 1...255
Octets 2 and 3 use the following equation to define the
response monitoring timeout (watchdog time, TWD):
TWD [s] = 10 ms * WD_FACT_1 * WD_FACT_2
This allows you to set times between 10 ms and 650 s
that are entirely independent of the baud rate. When the
watchdog control reacts the unit reports the event as error
no. 3 (� section 8.3.3).
157

PROFIBUS
Output reaction to bus error
Bit 3 (WD_ON) of Octet 1 enables (=1) or disables (=0)
the watchdog control of the DP slave.
Octet 4: Min. Station Delay Responder (min
TSDR)
Default: 11
Sets the minimum time that the DP slave must delay its
returning its response frames to the DP master. Writing
"0" retains the set value.
Octets 5...6: Ident_Number (unsigned16)
Ventura Remote PLC: 6902 (hex)
ID number of DP slave.
Octet 7: Group_Ident
See EN 50170, "Parameter Data Transmission" for details
158 E 700 GB

6.2.2.2 Device-specific Bus Parameters
Octets 8...12: User_Prm_Data
PROFIBUS
Apart from the general bus parameters, the DP master
can also send device-specific parameters (octets
8...max.244) to every DP slave Six bytes (octets) are
available to Ventura Remote PLC DP.
Device-specific parameters are currently not used.
159

PROFIBUS
6.2.3 Send Diagnostic Data (Diag_Data)
The set of diagnostic data informs the master of the status
of the DP slave.
DP slave message
Usually the slave responds by sending a low-priority
telegram to the master. However, if the DP slave finds an
error, it sends the master a high-priority telegram. As long
as the master does not respond accurately but continues
data communication as before, the DP slave continues to
send a high-priority telegram.
Response from the master
The master's appropriate response to a high-priority frame
is to request the diagnostic data:
Sent by Frame
Recipient
Unit SAP
master request diagnostic data slave 60
slave send diagnostic data master -
After successful diagnosis, the master continues data
communication unless other actions are started by the
user program.
All diagnostic data are sent to the master where they are
mapped onto specific byte operands.
In the case of Kuhnke masters
� 645-500, 680I, PROFIBUS modules of system 680
and 657P, the VEBES configuration utility is used to
define this operand range.
� 645-12M and 680V, KUBES module DP_CTRL is
used to request and download the diagnostic data.
� Ventura Slot PLC and PC Control 645-PCI-CoDeSys,
function PbGetDiagnostics is run to download the
diagnostic data.
Six bytes (Octets 1...6) contain the standard diagnostic
information of Ventura Remote I/O. Bytes 7...13 contain
the device-specific diagnostic information. The text below
160 E 700 GB

PROFIBUS
replaces the term "byte" with the term "octet" which is also
the word used by the standard.
A set bit (=1) signifies that the described event has
occurred.
6.2.3.1 Standard Diagnostic Data
Bit set by Explanation
Octet 1: station_status_1
0 master Diag.Station_Non_Existent (not supported by Kuhnke masters)
DP slave cannot be accessed via the bus
1 slave Diag.Station_Not_Ready
DP slave not ready for data exchange
2 slave Diag.Cfg_Fault
The last set of configuration data received from the master is
not the same that the DP slave found
3 slave Diag.Ext_Diag
There is a device-specific diagnostic result (octet 7...)
4 slave Diag.Not_Supported
The requested information cannot be supplied by the DP slave
5 master Diag.Invalid_Slave_Response
The slave response is not plausible
6 slave Diag.Param_Fault
Bad telegram of parameter data sent
7 master Diag.Master_Lock
The DP slave parameters were set by another master
161

PROFIBUS
Bit set by Explanation
0 slave Diag.Prm_Req
Octet 2: station_status_2
DP slave parameters need to be set again
1 slave Diag.Stat_Diag (static diagnosis)
DP master to get diagnostic data
2 slave Always set (=1)
3 slave Diag.WD_On
Watchdog (response timeout) enabled
4 slave Diag.Freeze_Mode
DP slave received a Freeze command
5 slave Diag.Sync_Mode
6 slave Reserved
7
master
DP slave received a Sync command
Diag.Deactivated
The set of DP slave parameters marks the DP slave as
inactive so that it is no longer included in the master's cyclic
procedures
Bit set by Explanation
0
1
2
3
4
5
6
7 slave
Octet 3: station_status_3
Reserved
Diag.Ext_Diag_Overflow
There is more diagnostic data than specified in the devicespecific
diagnosis
162 E 700 GB

Octet 4: Diag.Master_Add
PROFIBUS
Address of the DP master that set the parameters of the
DP slave.
Octets 5...6: Ident_Number
Manufacturer code for DP slave identification
Ventura Remote PLC: 6902 (hex)
163

PROFIBUS
6.2.3.2 Device-specific Diagnostic Data "Ext_Diag_Data"
Octets 7...12 are provided for device-specific diagnostic
data. Only the DP slave has write access to this range.
Extended diagnostic information
Octet Bit Explanation
7
8
9
0...5 Header byte Length of block = 6 bytes
6...7
0... 6 Device
status
Permanently set to "0"
1 Short circuit
2 Low voltage
7 (Expansion) module error
124 Run
125 Stop
126 Reset
7 Diagnostic module data available
0 Diagnosis, I/O Error found
1 module 0 Error modification
2 Diagnosis, I/O Error found
3 module 1 Error modification
4 Diagnosis Error found
5
I/O module 2 Error modification
6 Diagnosis Error found
7
I/O module 3 Error modification
10 0... 7 Variable
DPSLAVE.
UserError
11 0... 7 Internal
PROFIBUS
error byte
12
Changes to user program of
Ventura Remote PLC provoke
diagnostics.
0 no error
128 Wrong length User
Param.
0... 3 Software Digit after separator
4..7 version Digit before separator
164 E 700 GB

6.2.4 Master-Slave Data Communication
PROFIBUS
Following successful initialisation, the master starts
exchanging data always repeating the same routine:
Sent by Frame Recipient
master sends output data slave
slave sends input data master
The volume of data transferred is specified when
configuring the master project.
The maximum transfer volume is 100 words (200 byte)
which can be made up of several data modules.
Available modules
In
Length
Out
Module Name Consistency
1 word 1 word Data in:1w / out: 1 w Total length
4 words 4 words Data in:4w / out: 4 w Total length
8 words 8 words Data in:8w / out: 8 w Total length
16 words 16 words Data in:16w / out: 16 w Total length
32 words 32 words Data in:32w / out: 32 w Word
64 words 64 words Data in:64w / out: 64 w Word
Ventura Remote PLC DP uses global variable DPSLAVE
to store the data (inputs and outputs) plus the information
about the configuration and the PROFIBUS status. The
data type of DPSLAVE is SPC3_P690 which is defined in
library P690.LIB.
� Run the CoDeSys PLC Configuration Editor and
display the Library Manager screen.
� Choose P690.LIB and open folder "Data types".
165

PROFIBUS
SPC3_P690 is made up of the following elements:
Element Data type Explanation
Address BYTE To be set by the PLC program.
Status BYTE Status: 16#A1 = OK,
16#05 = connection lost
SystemError BYTE Internal error message
Operating mode BYTE Internal message
UserError BYTE Internal error message
InputLen BYTE Input length (set by master)
OutputLen BYTE Output length (set by master)
dummy BYTE Internal variable
UserParameter BYTE Internal message
InputData ARRAY[0..255]
OF BYTE
OutputData ARRAY[0..255]
OF BYTE
Input data as sent by the master
Output data as received by the
master.
To program the variables type DPSLAVE followed by a
dot. The editor will display a box where you can select
the structural element.
166 E 700 GB

Example:
VAR
bIn_0: BYTE;
bOut_0: BYTE;
END_VAR
(*Set to PROFIBUS address 2*)
IF DPSLAVE.address 2 THEN
DPSLAVE.address:=2;
END_IF
(*Check PROFIBUS status*)
IF DPSLAVE.Status=16#A1THEN
PROFIBUS_OK:=TRUE;
ELSE
PROFIBUS_OK:=FALSE;
END_IF
(*Copy PROFIBUS InputByte 0 to bIn_0*)
bIn_0:=DPSLAVE.InputData[0];
(*Enter bOut0 into PROFIBUS OutputByte 0*)
DPSLAVE.OutputData[0]:=bOut_0;
PROFIBUS
167

PROFIBUS
168 E 700 GB

7 CANopen
CANopen
At this point, we will only very briefly touch upon the key
properties of CANopen.
For further reading please study instruction manual E 615
GB, CANopen - Basics and KUBES Controller
Applications or
CANopen for 3S Runtime System.pdf by 3S
Useful details can also be found at http://www.canopen.org
7.1 CANopen for Beginners
Standard:
CANopen is defined in European Standard (EN 50325-4
2002 Part 4: CANopen).
EDS file:
The functionality and properties of a CANopen device are
described in a standardised "electronic data sheet" (EDS).
To integrate a CANopen unit, CoDeSys requires the
relevant EDS file.
Object dictionary:
Every CANopen unit compiles its internal data (process
data, parameters) into an object dictionary which it makes
available to the bus via a defined interface.
The items of the object dictionary are accessed by means
of a 16 bit index plus an 8 bit subindex.
Addresses:
CANopen networks support the management of up to 127
logical devices which are identified and addressed by their
node address.
169

CANopen
Master & Slave:
One unit in the network must provide the CANopen
master functionality.
CANopen masters can monitor CANopen slaves and
manipulate their status.
With regard to data exchange, master and slaves have
equal rights.
Ventura Remote PLC can act as a CANopen master.
Bus communication:
As opposed to "station-based" data transfer, which
defines as the exchange of messages between two
specified stations, the transfer of CAN messages is based
upon the so-called "producer/consumer principle", i.e. a
message sent by one of the stations (producer) can be
received and read by all of the other stations (consumers).
To sustain this approach, messages are not labelled with
a target address but with a unique "message identifier".
CANopen distinguishes between two types of basic
communication objects.
SDO
Service data objects (SDO) are used for configuring and
setting the parameters of CANopen slaves, for example.
SDOs are exchanged as acknowledged data transfer
operations with two CAN objects being sent through a
point-to-point connection between two network nodes
every time. The appropriate object dictionary item is
addressed by its index and subindex.
PDO
Process data objects (PDO) speed up the exchange of
process data.
PDOs are configured with reference to object dictionary
items.
There are various ways of transferring process data
objects, i.e. in response to an event, cyclically or after
request as broadcast objects without extra protocol
overhead. Every PDO can carry a maximum of 8 byte
user data.
170 E 700 GB

7.1.1 CANopen Example
CANopen
A Ventura Remote PLC CAN 32DI/32DO is to act as the
CAN master that exchanges data with Ventura Remote
I/O CAN 32DI/32DO.
• Step1: Add CAN library.
� Open a project for target system "KUHNKE Remote
PLC CAN".
� Go to tab "Resources" and choose "Library
Manager". Select "Insert, Additional Library". Choose
library 3S_CANopenMaster.lib located in library folder
C:\Programs\Common Files\CAA-Targets\Kuhnke
\Libs_C690.
This will also load 3S_Can_Drv.lib and
3S_CANopenManager.lib into the project.
• Step2: Configure CAN master.
� Go to tab "Resources" and choose "PLC
Configuration".
� Select Ventura Remote PLC CAN and choose "Add,
Append Subelement, CanMaster".
171

CANopen
� Set the baud rate as appropriate as well as the
address (node ID).
� Select "CanMaster" and choose
"Add, Append Subelement,
Ventura Remote IO CAN (EDS)".
� Set the node ID of Ventura Remote IO CAN. Enter
exactly the same address as the node ID into tab
"CAN Parameters".
� Go to tab "Receive PDO Mapping".
Ventura Remote IO CAN returns 4 PDOs containing
8 bytes each = set volume of 32 bytes of incoming
data.
� Go to tab "Send PDO Mapping". Ventura Remote IO
CAN returns 4 PDOs containing 8 bytes each = set
volume of 32 bytes of outgoing data.
� To make the CAN IOs easier to address, enter
names for the output and input variables.
The configuration of Ventura Remote IO CAN
chosen for this example only uses the first 4 bytes of
outgoing data and the first 4 bytes of incoming data of
the set CAN configuration.
172 E 700 GB

• Step3: Write and test CoDeSys program.
7.1.2 CAN Network Status
CANopen
Adding the 3S CANopen libraries to the CoDeSys project
opens the door to a special group of global variables, the
"CANopen implicit Variables"
These variables represent the status of the CAN network
and can thus be used for network monitoring tasks.
To check these variables, go to tab "Resources" and
select "Global Variables".
173

CANopen
pCANopenMaster[0] returns details about the settings and
status of the master.
0 means that this is the first master in the CANopen
network (Ventura Remote PLC does not support any more
than that).
pCanOpenNode[n] returns details about the settings and
status of the slave with serial number n.
Whereas n is the index of the node, it is not identical with
the Node ID!
Parameter Value Explanation
pCANopenMaster[0].
3 Error: slave not found
nStatus 5 OK, normal operation
pCANopenNode[n].
3 Error
nStatus 5 OK, normal operation
174 E 700 GB

PROGRAM PLC_PRG
VAR
CANMaster_Ok: BOOL;
CANSlave0_OK: BOOL;
CANSlave1_OK: BOOL;
END_VAR
CANopen
We recommend to include the following lines of code as a
means of basic CAN network monitoring. They do not pay
respect to optional settings such as node guarding, etc.
IF pCANopenMaster[0].nStatus=5 THEN (*check master*)
ELSE
CANMaster_Ok:=TRUE;
IF pCanOpenNode[0].nStatus=5 THEN (*check slave0*)
ELSE
CANSlave0_OK:=TRUE;
CANSlave0_OK:=FALSE;
END_IF
IF pCanOpenNode[1].nStatus=5 THEN (*check slave1*)
ELSE
CANSlave1_OK:=TRUE;
CANSlave1_OK:=FALSE;
END_IF
CANMaster_Ok:=FALSE;
END_IF
175

CANopen
176 E 700 GB

8 PLC Error Handling
8.1 "Failure" LED
177
Error Handling
Ventura Remote PLC monitors itself. It is notified of or
detects any errors and reacts in response to the error's
danger potential.
Errors are numbered consecutively from 1 to max. 255
and can be indicated in various ways:
Whenever a fault occurs, the red "failure" LED starts
flashing to indicate the error number:
No. Flash code
1
2
3
4
etc.
The flashes pulse quickly (250/250 ms). Then there is a
break of 1 s and the flash code is repeated.
8.2 Status Variable "SYSTEMINFO"
The status of the controller is shown in global variable
"SYSTEMINFO".
"SYSTEMINFO" is a data structure of type "SYSINFO".
Click on:
� the "Resources" tab of the CoDeSys Object
Organizer
� P690.LIB or C690.LIB, tab Data Types

Error Handling
The relevant information is found at:
SYSTEMINFO Value Explanation
Error
Byte
Operating mode
(Betriebsart)
Bit 0 Short circuit
Bit 1 Supply voltage low
Bit 2 not used
Bit 3 not used
Bit 4 not used
Bit 5 Watchdog
Bit
6..7
0 Run
not used
1 Stop
Byte 19 Reset
ExtError
WORD
noofT3Error
WORD
Bit 0 TimerTaskTimer overflow
Bit 1 TimerTask does not exist
Bit2..7 not used
TimerTasks error counter
178 E 700 GB

Example
VAR
C690_Error: BYTE;
END_VAR
C690_Error:=SYSTEMINFO.Error;
Error Handling
The following sections describe the types of faults and
suggest handling and corrective actions.
179

Error Handling
8.3 Faults and Failures Overview
Fault Indication
No. Type
Failure LED
flashes
n times*
SYSINFO.
ERROR
Error_IRQ
(see page 82)
1 Short circuit 1 yes
2 Low voltage 2
(see page
177)
yes
3 Watchdog 3
-
For a discussion of PROFIBUS communication errors:
see section 6.2.3
180 E 700 GB

8.3.1 Short-circuited Output (Error #1)
Cause
� Short circuit
� Overload
Indication
� Red "failure" LED flashes
� "SYSINFO. ERROR" bit 0 is set
Reaction
Error Handling
� The output concerned is switched off thermically
� Internal outputs generate an interrupt request.
Function "Install_ERR_IRQ" (see p82) installs an
error module which is run once. In this module, the
user can specify how the controller is to react:
Function "ENADIS_OUTPUTS" allows you to switch
off all outputs, for example (see page 79)
ENADIS_OUTPUTS(0);
The program continues to run but the outputs are
switched off towards the outside (internally, they retain
their state).
Corrective action
� Remove the short circuit, then turn the power off and
back on again.
181

Error Handling
8.3.2 Low Voltage (Power Supply, Error #2)
Supply voltage: 24 VDC -20%/+20%
The integrated voltage monitor has a two-stage reaction
to voltages dropping below set limits:
1st stage
Cause supply voltage drops to approx. < 17.5 V
Reaction
� ERROR_IRQ_module is run (see page 82)
� The program keeps running for the time being
Variables may be reset unintentionally if the user program
continues to run at this stage. This would be caused by
remote inputs already detecting a 0 signal due to the low
voltage.
Indication
� "failure" LED flashes (2x)
� Bit 1 in "SYSTEMINFO.ERROR" is set
2nd stage
First alternative
Cause
The voltage goes back up to 24 VDC ± 20%
Reaction
� "failure" LED stops flashing
� Bit 1 in "SYSTEMINFO.ERROR" is reset
� The program keeps running without interruption
Second alternative
Cause
The supply voltage keeps dropping further to < 7 V
Reaction
The 5 V system voltage is interrupted
182 E 700 GB

=> - STOP: The program is stopped
Error Handling
- RESET: all outputs and non-RETAIN variables
are reset
- All LEDs extinguish
Corrective action
� Preliminary user program action to protect the
buffered operands:
Running the user program should be suspended until
the cause is at its second stage or until a practically
feasible time has elapsed.
Error IRQ module, example:
VAR
Wait: TP; (*max. LOW time*)
LOW_ongoing: BOOL; (*max. LOW time exceeded*)
ON: BOOL;
Active:
END_VAR
BOOL;
PROGRAM low voltage
On:=TRUE;
WHILE On OR Active = TRUE DO
Wait (IN:=On, PT:=T#1000ms, Q=>Active, ET=> );
On := FALSE;
END_WHILE
IF SYSTEMINFO.Error.1 =TRUE THEN
LOW_ongoing :=TRUE;
ELSE
LOW_ongoing :=FALSE;
END_IF
183

Error Handling
8.3.3 Watchdog (Program Runtime Exceeded, Error
#3)
Cause
� Total program runtime has exceeded the set
watchdog time
Indication
� "failure" LED flashes
� CoDeSys reports communication error
Reaction
� STOP: The program is stopped
� RESET: local outputs and non-buffered markers,
timers and counters are reset
� external outputs (PROFIBUS) off
Corrective action
� Modify the program to shorten the runtime
� Restart the controller:
- Hardware: turn power off and back on,
or
- Software: in CoDeSys, choose,
Reset, then Start
184 E 700 GB

9 Appendix
9.1 Technical Data
9.1.1 Basic Data
Appendix
Function .........................................................compact, expandable PLC
with a bus interface unit
Type .............................................................small housing for mounting
on rail DIN EN 50022, 35 x 7.5
Protection..................................................IP 20
Dimensions L x B x H [mm] ......................213/329 x 89.6 x 73.9
Weight.......................................................735/1092 g
Power supply
Operating voltage .....................................24 V DC -20%/+25%
Power consumption ..................................at U=24 V
idling = 200 mA
Admissible ambient conditions
Operating temperature..............................0 °C to +55 °C
Transport/storage temperature.................-40 °C to +70 °C
Working altitude ........................................max. 3000 m above sea level
Relative humidity ......................................5% - 95 %, non-condensing
Line interfacing
Power .......................................................2-pin screw-type locking
terminal
Signals ......................................................screw-type locking terminal
Interface(s) RS232....................................D-Sub, socket
9-pin,
Interface(s) RS485....................................CANopen:
D-Sub plug, 9-pin,
PROFIBUS:
D-Sub, 9-pin, female
185

Appendix
Local status indication / LEDs 1
LED run.....................................................LED green / run
LED stop ...................................................LED red / stop
LED failure ................................................LED red / status
LED bus ....................................................LED yellow / bus
communication
9.1.2 Integrated Inputs and Outputs
Digital inputs ................................................16, 32, no electrical
insulation
Rising delay type1 1 ...................................n+2.5 ±2.5ms, adjustable
Rising delay type2, type3 .........................5ms
Indicators ..................................................green LEDs
Tapping point.......................................in input circuit
Signal state..........................................1: LED on, 0: LED off
Input voltage .............................................24 VDC +25%
Signal detection ...................................≤ 5 VDC
≥ 15 VDC
Surge immunity.........................................≤ 60 VDC (≤ 30 min.)
Power consumption per input ...................max. 10 mA
Digital outputs..............................................16, 32, no electrical
insulation
Type..........................................................semiconductor
Indicators ..................................................red LEDs
Tapping point.......................................in load circuit
Switching state ....................................1: LED on, 0: LED off
Output voltage ..........................................24 VDC –20%/+25%
Current......................................................0.5 A, short-circuit-proof,
auto resetting
1 Built-in LEDs: class 1 light emitting diodes (to EN 60825-1)
1 See page 191 for list of types
186 E 700 GB

Appendix
Max. current .............................................1.9 A per driver module
(1 driver module = 4 outputs)
Digital combi I/O .........................................4, no electrical insulation
Digital input
rising delay...........................................0.2 ms (interrupt-ready)
Indicators .............................................LEDs, green light
1: LED on, 0: LED off
Input voltage ........................................24 VDC +25%
Signal detection ...................................≤ 5 VDC
≥ 15 VDC
Digital output
Output voltage .....................................24 VDC –20%/+25%
Indicators .............................................LEDs, red light
Switching state ....................................1: LED on, 0: LED off
Current.................................................0.1 A, short-circuit-proof
auto resetting
Analogue inputs...........................................4, 0 - 10 V
Internal resistance ....................................≥ 200 kΩ
Admissible overload..................................60 V
Resolution.................................................10 bit
Scanning repetition...................................1 ms
Input filter ..................................................first order
Analogue outputs ........................................2, 0 - 10 V
Resolution.................................................8 bit / 10 bit switchover
Max. load ..................................................10 mA, short-circuit-proof
max. capacitive load 470 pF
Max. admissible reverse feed...................15V
Output ripple .............................................±5 mV (8 bit) / ±10 mV (10 bit)
Rate of change .........................................40 ms
187

Appendix
A/B/Ref, counters.........................................1
Maximum frequency .................................10 kHz
Indicators ..................................................LEDs: A,B yellow, Ref green
Signal state..........................................1: LED on, 0: LED off
Input voltage .............................................24 VDC +25%
Signal detection ...................................≤ 5 VDC
≥ 15 VDC
Power consumption per input ...................max. 10 mA
188 E 700 GB

9.1.3 Communication Ports
V.24 ports (RS 232) .....................................1
Transfer rate .............................................19.2 kbps
Field bus ports .............................................1
PROFIBUS
Function...............................................DP slave
Available protocols ..............................PROFIBUS-DP
Transfer rate ........................................9.6 kbps to 12 Mbps
(adjustable by software)
Own station address............................0 - 125 (adjustable)
CANopen
Function...............................................NMT master, slave
Protocol................................................DSP
Transfer rate ........................................50 - 1000 kbps
(adjustable by software)
Own station address............................0 - 125 (adjustable)
9.1.4 Hardware
Processor
For user program ......................................80C167
Program memory, internal
RAM..........................................................240 Kbytes
Flash .........................................................256 Kbytes
NV-RAM....................................................32 Kbytes
Program memory, external
Multimedia card ........................................min. 8 Mb
Appendix
189

Appendix
9.1.5 Project Setup
Programming device.................................IBM-PC (or compatible)
Operating systems....................................Windows 98, NT, 2000, XP
Programming software..............................KUBES (user program)
VEBES (PROFIBUS
configuration)
Programming language ............................IL, C
Documentation..........................................IL, FD, LD, SymT, CRL
9.1.6 Permits
CE .............................................................yes
UL .............................................................upon request
PNO certificate (PROFIBUS)....................upon request
190 E 700 GB

9.2 Order Specifications
9.2.1 Controllers Ventura Remote PLC
9.2.1.1 Order Key
9.2.1.2 PROFIBUS-DP
693.x1x=spring return
693.x2x=clamp-screw
693.xx1=CAN
693.xx3=PROFIBUS 12Mbd
693.xxx.22=16DI / 16DO
693.xxx.44=32DI / 32DO
Appendix
VRPLC DP 16DI/16DO SS ...................................................693.923.22.00
VRPLC DP 16DI/16DO FD ...................................................693.913.22.00
VRPLC DP 32DI/32DO SS ...................................................693.923.44.00
VRPLC DP 32DI/32DO FD ...................................................693.913.44.00
9.2.1.3 CANopen
VRPLC CAN 16DI/16DO SS ................................................693.921.22.00
VRPLC CAN 16DI/16DO FD ................................................693.911.22.00
VRPLC CAN 32DI/32DO SS ................................................693.921.44.00
VRPLC CAN 32DI/32DO FD ................................................693.911.44.00
9.2.2 Accessories
External program memory and data memory
Memory card, 8 Mb Flash................................................680.180.18
PROFIBUS plug (D-Sub, 9-pin)
Bus node (T-piece) with screw connectors, line A, bus termination
on/off, with vertical wire outlet .........................................645.180.00
191

Appendix
PROFIBUS bus terminations (D-Sub, 9-pin)
Active, line B, power 230 VAC.........................................680.180.10
Active, line B, power 24 VDC ..........................................680.180.15
Active, line A, power 230 VAC.........................................680.180.12
Active, line A, power 24 VDC ..........................................680.180.14
CAN plug (D-Sub, 9-pin)
Bus node (T-piece) with screw connectors, bus termination on/off
CAN SUB-D-Connector axial................................................693.182.01
CAN SUB-D-Stecker angled.................................................693.182.00
Simulator
Digital input simulator box (1 x 8-pin) ..............................667.155.50
192 E 700 GB

Appendix
9.3 Ventura Remote I/O Expansion Modules
Digital
16 DI, 1-wire, screw-type terminal*..................................693.622.20
32 DI, 1-wire, screw-type terminal*..................................693.622.40
8 DO relay, 1-wire, screw-type terminal*.........................693.122.08
16 DO, 1-wire, screw-type terminal*................................693.622.02
32 DO, 1-wire, screw-type terminal*................................693.622.04
16 DI / 16 DO, 1-wire, screw-type terminal* ....................693.622.22
8 DI / 8 DO electrically insulated, 1-wire,
screw-type terminal*...................................................693.522.11
Counters
2 CNT, 1 MHz, 2AO, 8DI, 4DO, 1-wire,
screw-type terminal* ...................................................693.322.42
Analogue
6 DI / 2 AO, 1-wire, screw-type terminal* ........................693.222.32
4 AI, 1-wire, screw-type terminal*....................................693.222.40
4 thermal inputs, 1-wire, screw-type terminal* ................693.222.70
8 thermal inputs, 1-wire, screw-type terminal* ................693.222.80
* 693.x1x=spring return
693.x2x=clamp-screw
Expansion module optionally available with spring terminal upon
request.
193

Appendix
9.4 References
Title / Subject Number Source
Programming manual
Programming of Kuhnke's PLC systems
KUBES
Programming software for Kuhnke's PLC
systems
VEBES
PROFIBUS network configuration editor
PROFIBUS-DP
Operating Instructions
Ventura Remote I/O
Operating Instructions
Profi/CanControl 690E+
Operating Instructions
First Steps into CoDeSys
First Steps into CoDeSys V.pdf
PLC programming manual
CoDeSys_V_GB.pdf
CoDeSys Visualisation, PLC programming manual
supplement
CoDeSys_Visu_V_GB.pdf
CANopen for 3S Runtime System
CANopen for 3S Runtime System.pdf
E 417 GB Kuhnke GmbH
E 327 GB Kuhnke GmbH
E 315 GB Kuhnke GmbH
E 611 GB Kuhnke GmbH
E 409 GB Kuhnke GmbH
E 559 GB Kuhnke GmbH
194 E 700 GB
3S
3S
3S
3S

9.5 Sales & Service
Appendix
Please visit us on the Internet to find a comprehensive
overview of our sales and service network including all the
relevant addresses. You are, of course, always welcome
to contact our staff at the main factory in Malente or at
sales headquarters in Neuhausen:
9.5.1 Main Factory in Malente
9.5.2 Sales Germany
9.5.3 Customer Service
Kuhnke Automation GmbH & Co. KG
Lütjenburger Str. 101
D-23714 Malente
Phone +49-45 23-4 02-0
Fax +49-45 23-40 22 47
Email sales@kuhnke.de
Internet www.kuhnke.de
Kuhnke Automation GmbH & Co. KG
Niederlassung Stuttgart
Strohgäustr. 3
D-73765 Neuhausen
Phone +49-71 58-90 74-0
Fax +49-71 58-90 74 80
Email sales@kuhnke.de
Internet www.kuhnke.de
Kuhnke Automation GmbH & Co. KG
Lütjenburger Str. 101
D-23714 Malente
Telefon +49 (0)4523 402 200
Telefax +49 (0)4523 402 201
E-mail service@kuhnke.de
Internet www.kuhnke.com
195

Appendix
196 E 700 GB

9.6 Index
A, B, Ref counter 146
connection 41
functions 143
accessories 191
analogue inputs
connection 39
functions 139
operands 128
analogue outputs
connection 40
functions 141
operands 128
attention 18
boot 49
bus protocols 153
cable routing and wiring 24
CAN
port 44
CANopen 169
basics 169
example 171
clear 50
code-protection 50
com
port 42
contamination 25
danger 18
decentralisation benefits 13
device master file 155
Index
device-specific bus parameters
159
device-specific diagnostic data
"Ext_Diag_Data" 164
diagnostic data (Diag_Data) 160
digital combi I/Os
connection 37
digital inputs
connection 35
functions 130
functions of internal inputs
132, 149
operands 126
digital inputs and outputs 115
digital outputs
connection 35
functions 130
functions of internal outputs
133
operands 126
dimensions 28
earth 31
earth conductor 31
electromagnetic compatibility 23
electromagnetic interference 25
error module 82
event counter 143
expansion modules 45
order specifications 193
export 49
failure indication 51
197

Index
failure LED 177
faults and errors 177
faults and failures overview 180
fieldbus 14
flash file system 69
Flush_Inputs 80
Flush_Outputs 81
function libraries 70
general bus parameters 157
GSD file 155
impact and vibration 25
import 49
inductive actuators 25
initialisation 156
input IRQ module 84
inputs
direct read 80
installation 21, 30
installation instructions 23
instruction 19
interfacing 31
interference emission 23
internal I/Os 127, 129
interrupt inputs 132
interrupt module
32 144, 146, 147
KUHN6902.GSD 155
LED 51
limiting value class 23
location of installation 24
low voltage (power supply, error
#2) 182
maintenance 22
master-slave communication
155
master-slave data
communication 165
memory 52
memory card 46
method of PLC operation 58
modes of operation 48
module configuration
at startup 150
module I/Os 126, 128
functions of module 1-3 150
multimedia card
functions 52
hardware 46
MMC.LIB 91
network configuration 154
network examples 15
note 19
online
RS 232 55, 57
operands 114
operating system 59
operative earth 31
order specifications 191
outputs
direct write 81
enable/disable 79
PC/ProfiControl 645-12M
PLC range 81
PLC error handling 177
PLC functions 53
PLC states 112
power supply 33
198 E 700 GB

PROFIBUS
port 43
PROFIBUS-DP 153
diagnosis 164
example 66
network example 15
parameter settings 157, 160
user data 165
programming 114, 126
project planning 21
PWM outputs 133
reliability 17
RUN 49, 112
runtime system 59
safety 20
sales & service 195
servicing 22
short circuit 137
special functions
of internal I/Os 130
standard diagnostic data 161
station address 154
status indication 51
status messages of modules 151
stop 49
STOP 112
STOP and Reset 112, 113
symbols 18
system description 27
target group 17
temperature 24
thread 71, 111
timer task 75
topology 153
under construction 19
up/down counter 146
user memory 125
user program 68
variants
order specifications 191
standard, release1 10
terminology 11
version info 58
watchdog (program runtime
exceeded, error #3) 184
watchdog set-up 89
working steps 19
Index
199