Kuhnke Electronics

Operating Manual
Ventura Skaleo 100 RS232
Ventura Skaleo 100 RS485

E 783 GB 01.03.13/ 10144408

This operating manual is primarily directed to system designers, project engineers and
device developers. It does not provide any information as to product availability. All speci-
fications are only of descriptive nature and are not to be understood as warranted proper-
ties in a legal sense. Any claims for compensation against us – independent from the le-
gal reason – are excluded, provided there is no intention or gross negligence on our side.
We accept no responsibility for changes, omissions and errors.
Complete or partial reproduction of this manual requires the prior written consent of the
publishers.
 Table of contents

Table of contents
1 Introduction ......................................................................................................................................................5
1.1 EtherCAT – Ethernet Control Automation Technology.............................................................................5
1.2 Ventura – the automation platform ...........................................................................................................5
1.3 Ventura Skaleo – the mini IPC in FIO design ...........................................................................................5
1.4 Product range ...........................................................................................................................................6
1.5 Models ......................................................................................................................................................6
2 Reliability and safety........................................................................................................................................7
2.1 Application range ......................................................................................................................................7
2.2 Target group .............................................................................................................................................7
2.3 Reliability...................................................................................................................................................7
2.4 Notes.........................................................................................................................................................7
2.4.1 Danger................................................................................................................................................8
2.4.2 Attention .............................................................................................................................................8
2.4.3 Note....................................................................................................................................................8
2.4.4 Under development............................................................................................................................8
2.4.5 Operating instruction ..........................................................................................................................8
2.5 Safety ........................................................................................................................................................8
2.5.1 During project design and installation ................................................................................................9
2.5.2 During repair and maintenance..........................................................................................................9
2.6 Electromagnetic compatibility .................................................................................................................10
2.6.1 Definition ..........................................................................................................................................10
2.6.2 Electromagnetic interferences..........................................................................................................10
2.6.3 General installation notes.................................................................................................................10
2.6.4 Protection against external electric influences.................................................................................11
2.6.5 Wiring ...............................................................................................................................................11
2.6.6 Place of installation ..........................................................................................................................11
2.6.7 Special interference sources............................................................................................................12
3 Ventura Skaleo 100 .......................................................................................................................................13
3.1 Description of system with FIO modules ................................................................................................13
3.2 Mechanical design ..................................................................................................................................13
3.2.1 Mounting...........................................................................................................................................14
3.3 System power supply..............................................................................................................................15
3.3 System power supply..............................................................................................................................16
3.3.1 General notes...................................................................................................................................16
3.3.2 24 V DC power supply ....................................................................................................................16
3.3.3 Grounding.........................................................................................................................................17
3.4 Interfaces ................................................................................................................................................18
3.4.1 Interrupt input ...................................................................................................................................18
3.4.2 LAN interface....................................................................................................................................19
3.4.3 COM interface ..................................................................................................................................19
3.4.4 SD-card slot......................................................................................................................................21
3.5 Control and display elements .................................................................................................................22
3.5.1 Stop/reset key ..................................................................................................................................22
3.5.2 Status indicators...............................................................................................................................22
3.6 System memory ......................................................................................................................................24
3.6.1 Data ranges......................................................................................................................................24
3.6.2 Retain variables................................................................................................................................24
3.7 Web server..............................................................................................................................................25
3.8 Web visualization ....................................................................................................................................26

E 783 GB 3
01.03.13/10144408
Table of contents

3.9 Watchdog................................................................................................................................................28
4. Installation ....................................................................................................................................................29
4.1 CoDeSys installation on the programming PC .......................................................................................29
4.2 Target installation in CoDeSys ...............................................................................................................29
4.3 Settings of the IP address of the Skaleo IPC .........................................................................................30
4.4 Settings of the CoDeSys programming PC ............................................................................................30
4.4.1 Ethernet interface settings on the programming PC ........................................................................30
4.4.2 Setting the communication parameters within CoDeSys .................................................................31
4.5 Create a CoDeSys project with EtherCAT..............................................................................................32
4.5.1 Loading a CoDeSys boot project onto the SD-card .........................................................................33
4.5.2 Loading a CoDeSys boot project from the SD-card.........................................................................33
4.5.2.1 Loading a boot project without version information.......................................................................33
4.5.2.2 Loading a boot project with version information............................................................................34
4.6 Operation of EtherCAT slaves ................................................................................................................34
4.6.1 System requirements .......................................................................................................................35
4.6.2 Install EasiCat configurator ..............................................................................................................35
4.6.3 Select EtherCAT participant.............................................................................................................38
4.6.4 Importing configuration data into CoDeSys .....................................................................................43
4.6.5 Changing of the control configuration with EasiCat .........................................................................44
4.6.6 Renaming a CoDeSys project..........................................................................................................45
4.6.7 Including an EtherCAT master into CoDeSys ..................................................................................46
4.7 SPS function libraries..............................................................................................................................48
4.7.1 Skaleo100.lib....................................................................................................................................48
4.7.2 SkaleoRS485.lib...............................................................................................................................49
4.7.3 KuhnkeECatLibSkaleo.lib.................................................................................................................50
4.7.4 KubesPrtLib.lib .................................................................................................................................50
5 Special functions of the Skaleo 100 ..............................................................................................................51
5.1 Time synchronization with an NTP server ..............................................................................................51
5.2 Update of the runtime system with an SD card ......................................................................................52
5.2.1 Update without version information..................................................................................................52
5.2.2 Update with version information.......................................................................................................53
5.3 Hardware stamp......................................................................................................................................53
5.4 Deactivation of slaves of a control system configuration........................................................................54
5.5 Customer specific error HTML pages for the web server .......................................................................54
5.6 Sending a ping ........................................................................................................................................55
5.7 Reading of the Skaleo100.lib version .....................................................................................................56
5.8 Reading of SD-card specific information ................................................................................................56
5.9 Writing data on drive A............................................................................................................................56
6 Error treatment after a system crash.............................................................................................................57
7 Appendix........................................................................................................................................................58
7.1 Technical specifications ..........................................................................................................................58
7.2 Ordering information ...............................................................................................................................58
7.3 Further reading .......................................................................................................................................59
8 Sales & Service .............................................................................................................................................60
8.1 Malente headquarter...............................................................................................................................60
8.2 Customer service / customer care ..........................................................................................................60
9 Index ..............................................................................................................................................................61

4 E 783 GB
01.03.13/10144408
 Introduction

1 Introduction

1.1 EtherCAT – Ethernet Control Automation Technology

EtherCAT is presently the most powerful Ethernet-based field bus system.

EtherCAT not only sets new standards as to communication speed. Thanks
to its flexible topology and easy configuration, it is also excellently suited to
control extremely fast processes. EtherCAT is able to process 1000 I/Os
within 30 µs.
Due to its high performance, easy wiring and openness for other protocols,
EtherCAT is frequently used in industry PCs and smaller controllers as a fast
drive control and I/O bus. Where other field bus systems reach their limits,
EtherCAT sets new standards. EtherCAT is able to connect the controller
with both I/O modules and drives as fast as a back pane bus. For this rea-
son, EtherCAT control systems perform almost as central control systems.
There is no need to take the transmission delay of the bus into considera-
tion, as it is the case with conventional field bus systems.

1.2 Ventura – the automation platform

The automation platform Ventura was especially developed for machine con-
trol applications. Ventura offers flexible automation solutions with hard and
soft PLCs on the basis of industry PCs, remote I/Os, remote PLCs and dis-
tributed drives. For networking, Ventura supports EtherCAT, PROFIBUS-DP,
CANopen and AS-Interface.
Ventura industry PCs as EtherCAT master offer defined real time perform-
ance and are equipped a CoDeSys SPS.

1.3 Ventura Skaleo – the mini IPC in FIO design

The Mini PC Ventura Skaleo 100 was designed for automation processes
with medium complexity. Thanks to numerous interfaces it can be used for
distributed structures and can easily be integrated into existing control con-
cepts.
An integrated digital input with interrupt capability allows fast reactions to
process events. The built-in serial interface (RS232 or RS485) allows data
exchange with other devices, as well as the connection of cost-effective ter-
minals for visualization. In addition, a built-in web server supports web-
based visualization. An SD-card slot allows the local storage of process
data and the exchange of control software. In addition, the Mini IPC offers a
built-in real time clock, as well as numerous status LEDs for easy error
analysis.
Using Ventura FIO I/O modules as EtherCAT slaves, the Mini IPC Ventura
Skaleo 100 IPC provides easy expansion to match customer-specific re-
quirements.
Programming is achieved via CoDeSys, the comfortable standard IEC
61131-3 programming and commissioning tool with the programming lan-
guages AWL, KOP, FUP, ST, SFC and CFC.
The multitasking system of the Ventura Skaleo 100 IPC allows time or
event controlled processing of program segments.

E 783 GB 5
01.03.13/10144408
Introduction

1.4 Product range

This operating manual describes the characteristics of the following standard

models available for CoDeSys programming:

Ventura Skaleo 100 RS232

with RS232 interface… 694.300.00
Ventura Skaleo 100 RS485
with RS485 interface… 694.300.01

The I/O system Ventura FIO is described in the operating manual E 747.

1.5 Models

The Mini IPC Ventura Skaleo is available in two models with different serial
interfaces.
Ventura Skaleo 100 RS232
with RS232 interface
Ventura Skaleo 100 RS485
with RS485 interface

Terminology
The following terms are used in this operating manual:
Skaleo
Abbreviation of the Ventura Skaleo 100 IPC
Ventura Skaleo 100
Information referring to all models of the IPC
Ventura Skaleo 100 RS232
Information referring to the model with RS232 interface
Ventura Skaleo 100 RS485
Information referring to the model with RS485 interface

6 E 783 GB
01.03.13/10144408
 Reliability and safety

2 Reliability and safety

2.1 Application range

Kuhnke products are designed to be used as technical resources for indus-

trial applications.
Using them for any other purposes requires consulting the manufacturer.
The manufacturer does not accept any liability if the products are used for
purposes they were not intended for, as well as any damages resulting from
such use. In such cases, the risk exclusively rests on the user.
Using these products as intended also includes observing this operating
manual.

2.2 Target group

This operating manual contains all information required to use the product
described therein for the purpose it is intended for (control unit, operating
terminal, software etc.). It is directed to skilled personnel in fields such as
product design, project development, service and implementation. Compre-
hensive knowledge in the field of automation technology is required to fully
comprehend and apply the technical descriptions contained in this manual,
as well as to understand the respective warnings and dangers associated
with the use of the product.

2.3 Reliability

Design and production of Kuhnke products include comprehensive and

costly means to achieve a maximum of reliability. This includes

• Selection of high-quality components

• Specific quality agreements with suppliers
• Measures to prevent static discharges when handling MOS circuits
• Worst-case dimensioning of all circuits
• Visual controls at various steps of the production process
• Computer-aided control of all components and their interaction within the
system
• Statistic evaluation of manufacturing quality and returned products to
immediately start corrective measures

2.4 Notes

Despite all preventive measures described in chapter 2.3, it is not possible to

fully exclude any technical malfunctions of electronic control devices, al-
though these are rather unlikely.
We ask you to carefully observe the additional warnings marked by respec-
tive symbols in this manual. Some of this warnings refer to dangers, while
others are more of informative nature for the reader.
E 783 GB 7
01.03.13/10144408
Reliability and safety

The following paragraphs describe the meaning of the individual symbols in

the order of their importance.

2.4.1 Danger
This symbol refers to dangers which might lead to personal injuries or death,
if the preventive measures described are not observed.

2.4.2 Attention
This symbol points out to information that needs to be observed by all
means, in order to prevent malfunctions, the destruction of materials or even
dangerous situations.

2.4.3 Note
This symbol refers to additional information referring to the application of the
product described. This might also be a reference to information contained in
external sources (such as other operating manuals).

2.4.4 Under development

This symbol points out to the fact that the function described is not or not
fully implemented into the product at the time of printing this manual.

2.4.5 Operating instruction

Whenever this symbol appears next to a column, the respective text includes
specific operating instructions referring to the computer or other hardware.
This symbols is primarily used for better orientation in descriptions which
contain both background information and instructions.

2.5 Safety

Our products are usually integrated into larger systems or become part of a
machine. The following instructions are helpful to integrate the product into
an infrastructure without any danger for humans or the machine/system.

In order to gain the highest level of safety when developing and installing
and electronic control device, it is vital to carefully follow the instructions pro-
vided in this operating manual. Incorrect handling may prevent features de-
signed to exclude fatal errors from functioning correctly or may lead to addi-
tional safety hazards.

8 E 783 GB
01.03.13/10144408
 Reliability and safety

2.5.1 During project design and installation

• 24 V DC supply: Use an electrically isolated low voltage source. Suitable

sources are transformers with separate windings, designed according to
EN 60742 (corresponding to VDE 0551).
• In the case of voltage failures or voltage dips: The software must be
designed in a way to result in a defined state after a restart of the system,
which excludes any dangerous situations.
• Any provisions to switch the system off in case of an emergency need to
be realized according to EN 60204/IEC 204 (VDE 0113) and active at any
time.
• All safety regulations and arrangements to prevent accidents applying to
a specific application need to be observed.
• Please note the cautions and warning symbols of this manual pointing out
to possible error causes.
• All applicable standards and VDE regulations need to observed by all
means.
• Control elements must be installed in a way to prevent any unintended
activation.
• Cables need to be located in a way to avoid inductive or capacitive
interferences which might influence the function of the control unit.

2.5.2 During repair and maintenance

• During measuring and testing while the control unit is activated, all
related accident prevention regulations according to VGB 4.0 need to be
observed. This refers especially to § 5 (accepted deviations when
working with system components).
• Repairs must be performed by Kuhnke specialists exclusively (which
normally takes place at the Malente headquarters). Any other repairs will
void the guarantee.
• Spare parts: Only use spare parts authorized by Kuhnke. Only original
Kuhnke modules may be inserted into modular control units.
• With modular systems: Insert or remove modules only while the power is
switched off. Not observing this rule might destroy a module or result in
limited functionality (which might not be obvious immediately)
• Dispose of batteries and rechargeable batteries according to local
regulations.

E 783 GB 9
01.03.13/10144408
Reliability and safety

2.6 Electromagnetic compatibility

2.6.1 Definition

Electromagnetic compatibility refers to the ability of a device to work reliably

within electromagnetic environments without causing electromagnetic inter-
ferences which might not be acceptable to other devices present in the same
environment.
Depending on the environment a device operates in, only a part of all known
electromagnetic interferences will appear. Such interferences are defined in
the respective product standards.
Design and interference immunity of logic controllers are regulated by the in-
ternational standard IEC 61131-2, which confirms to the European standard
EN 61131-2.

General installation rules, which need to be observed in order to limit the

coupling factors and resulting noise voltage to a compatible level are in-
cluded in IEC 61131-4 (user guidelines).

2.6.2 Electromagnetic interferences

Emissions of electromagnetic high frequency fields according to EN 61000-

6-4, emissions in industrial environments.

If the control unit will be operated within residential areas, its electromagnet
emissions must conform to threshold class B according to EN 55011 or EN
61000-6-3.
This can be achieved for example be integrating the control unit into
grounded metal cabinets or by integrating filters into all input and output
lines.

2.6.3 General installation notes

Depending on their application, electric control systems installed as part of

machines, installations and systems need to conform to applicable rules and
regulations.
General requirements concerning the electric equipment of machines with
reference to the safety of such machines are included in the European stan-
dard EN 60204, part 1 (which confirms to VDE 0113).

For the safe installation of our control system, the following instructions need
to be observed (→ 2.6.4)

10 E 783 GB
01.03.13/10144408
 Reliability and safety

2.6.4 Protection against external electric influences

In order to dissipate electric interferences, make sure to connect the control

system to the ground wiring, if such is provided. Run the associated wiring in
a suitable way.

2.6.5 Wiring

Separate wiring: Preferably, wires transporting control signals should be run

separately from power supply lines.

• Direct current 60 V … 400 V

• Alternating current 25 V … 400 V

Parallel wiring: Power supply lines and data signal lines can be run together,
if the following precautions are observed:

• Shielded data signal lines

• Shielded analog signal lines
• Shielded digital I/O lines
• Direct current <60 V unshielded
• Alternating current <25 V, unshielded

2.6.6 Place of installation

Select a place of location which does not lead to any interferences by envi-
ronmental influences, such as temperature, contaminations, shocks, vibra-
tions or electromagnetic interferences.

2.6.6.1 Temperature
Take the presence of heat sources into consideration, such as radiators,
sunlight, as well as the accumulation of heat inside rooms and control cabi-
nets.

2.6.6.2 Contamination
Use suitable cabinets to avoid possible negative influences caused by hu-
midity, corrosive gases, fluids and conductive dust.

2.6.6.3 Shocks and vibrations

Take possible interferences into consideration, which might be caused by
motors, compressors, transfer lines, metal presses, rams and vehicles

E 783 GB 11
01.03.13/10144408
Reliability and safety

2.6.6.4 Electromagnetic influences

Take electromagnetic interferences from various sources into considera-
tion, which might be present at the place of installation: motors, switching
devices, switching thyristors, remote controlled devices, welding devices,
arcs, switching power supplies, inverters and power converters.

2.6.7 Special interference sources

2.6.7.1 Inductive actors

Switching off inductive devices (such as relay coils, solenoid valves or sole-
noid switches) results in voltage peaks. It is necessary to reduce such noise
voltage to a permitted level. This can be achieved by using suitable dampen-
ing elements, such as diodes, Z diodes, varistors and RC-chains. Determin-
ing the suitable dimension of these elements requires to observe the techni-
cal information of the manufacturer or supplier of such actors.

12 E 783 GB
01.03.13/10144408
 Ventura Skaleo 100

3 Ventura Skaleo 100

3.1 Description of system with FIO modules

The Ventura Skaleo 100 IPC serves as a controller module. It provides the
supply voltage for all connected Ventura FIO I/O modules and drives the in-
ternal bus (E bus). Just as an EtherCAT master it sends EtherCAT tele-
grams to write output data and read input data. Doing so, the EtherCAT pro-
tocol is maintained all the way until the last I/Omodule. The extender module
can be used to connect additional EtherCAT slaves to the Skaleo IPC.
The system consists of various individual components which can be com-
bined according to individual requirements.
Additional I/O modules of the Ventura FIO range are available to expand the
Ventura Skaleo 100 Mini IPC.

Skaleo

FIO 1 FIO 2 FIO 3 FIO 4

3.2 Mechanical design

Figure 1 shows the principal mechanical setup of the Ventura Skaleo 100
IPC:

TStatus-LEDs (EtherCAT, Run/Stop, Error)

h Identification clip
Status-LEDs
e (LAN Link + LAN Active)
Stop/reset-key
m
o SD-card-clot Grip
d
Status-LEDs (24V + DI) LAN interface
u
Shieldl connector at COM- interface
the case
e carrier
Interrupt input & supply
c voltage
a
r slots
Venting Module lock & E-
r Bus
i DIN rail connector and
e functional grounding
r
Figure 1: Mechanical setup

The module carrier consists of an aluminium profile with an integrated snap-

in device for connecting the module to a standard 35 mm DIN rail. The case
itself with the optical light guides for the status indicators, as well as the side
and front covers of the module are made of plastic and are designed to

E 783 GB 13
01.03.13/10144408
Ventura Skaleo 100

completely enclose the module. The light guides of the status LEDs are lo-
cated next to the the module lock and are slightly elevated. This allows
monitoring the status of the device at one glance.

Expansion:
The Ventura Skaleo 100 IPC allows the connection of up to 15 I/O modules
of the Ventura FIO product range. Each expansion module has a length of
112 mm.

Connecting multiple FIO I/O modules requires separate EMI measure-

ments.

3.2.1 Mounting

The Ventura Skaleo IPC is designed to be

mounted on a standard 35x7.5 mm rail 2
according to DIN EN 50022.

3.2.1.1 Attaching individual modules

1. Observing the illustration, insert the Skaleo
IPC from the bottom into the rail until the
metal spring is positioned between the rail
and the mounting surface.
2. Press the upper part of the Skaleo IPC
against the mounting surface until it clicks
onto the rail. 1

Figure 2: Mounting of the Skaleo IPC

3.2.1.2 Connecting of the Skaleo IPC to an FIO module

After attaching the Skaleo IPC onto a DIN rail, attach the first FIO module
onto the same rail, maintaining a distance of appx. 1 cm from the first
module on the rail.

Push the FIO module towards the Skaleo IPC until the it interlocks with
the IPC

3.2.1.3 Disconnecting the Skaleo IPC from an FIO module

Press the lock release of the module (see illustration) towards the left of
the Skaleo IPC which you want to disconnect.

Push both modules aside until there is a space of appx. 1 cm.

14 E 783 GB
01.03.13/10144408
 Ventura Skaleo 100

3.2.1.4 Disconnecting the Skaleo IPC

1. Push the Skaleo IPC upwards against the metal spring at the bottom of
the connector.
2. Tilt the Skaleo IPC from the rail, as shown in the illustration.
3. Pull the Skaleo IPC downwards from the rail.

2 3

Figure 3: Disconnecting the Skaleo

1

E 783 GB 15
01.03.13/10144408
Ventura Skaleo 100

3.3 System power supply

3.3.1 General notes

Power supply of the system and attached I/O modules:

The device is powered from an external 24 V DC power supply. A built-in
converter converts this power to the internal system voltage of 5 V DC to
supply CPU, system bus and field bus interface with the required power.

Please note while connecting the device: Always connect the 0 V lead first
and disconnect it last. Otherwise it is possible that compensating currants
flow via the interface, if a device is connected to the RS232 interface. This
will trigger the electronic fuse and the device will only be ready for opera-
tion after a delay of appx. 1 minute (cooling phase).

3.3.2 24 V DC power supply

A built-in undervoltage monitor allows the early detection of voltage dips. In

the case of undervoltage dips > 10ms, the system will be shut down in a
controlled way.
The device must be exclusively connected to a 24 V DC power supply con-
firming to the requirements of a safe low voltage supply (SELV).
Use the supplied connector to connect the supply voltage. This 3pin connec-
tor serves to connect the supply voltage of the Skaleo IPC as well as the in-
terrupt input. Since the Skaleo IPC supplies both E bus and the logics of the
I/O modules, the required current depends on the number of connected I/O
modules.
2
The acceptable size of the 24 V DC connection cable is between 0.2 mm
2
and 1.5 mm .

Terminal 3-pin plug, 3,5 mm grid

Pin Function
DI Interrupt input
L+ Supply voltage +24 VDC
L- GND

16 E 783 GB
01.03.13/10144408
 Ventura Skaleo 100

3.3.3 Grounding

The Skaleo 100 IPC needs to be grounded. For this purpose, the metal case
needs to be connected to a ground connection.
The ground connection serves to dissipate HF currants and is of vital impor-
tance for the resistance of the module against interferences.
HF interferences are transferred from the electronic board to the metal case
of the device. This is why the case needs to be attached to a ground con-
nection.
In general it is important to make sure that
 the case of the module has a well conductive connection to the DIN rail
 the DIN rail has a well conductive connection to the switching cabinet
 the switching cabinet is grounded sufficiently
In special situations, the grounding can also be connected directly to the
module.

Connect cable shield here

Connect with
M3x5 bolts

Connect DIN rail to

ground

Figure 4: Aluminium profile

Grounding lines should be as short as possible and have a large surface

(copper mesh). For additional information, please visit
http://wikipedia.org/wiki/grounding_(electronics)

It is recommended to ground the Vebntura Skaleo IPC and all associated

Ventura FIO I/O modules via one and the same ground connection (DIN rail).

E 783 GB 17
01.03.13/10144408
Ventura Skaleo 100

3.4 Interfaces

3.4.1 Interrupt input

The Ventura Skaleo IPC offers an interrupt capable digital input. For connec-
tions to this input, use the connector included in the package. The status
LED D1 informs about the status of this input.

Address %IB0

Voltage 24 V DC -20%+25%

Interrupt delay >1 ms

Signal detection on rising flange only

Connection 1-pin

Connection: 3-pin connector with 3.5 mm spacing

Pin Function
DI Interrupt input
L+ Supply voltage +24 VDC
L- GND

The interrupt input needs to be initialized as follows:

The library „SysLibIecTasks.lib“ has to be added to the project and thethe

POU “IrqEingang” has to be created. Changing of the condition from FALSE
to TRUE then leads to the start of the interrupt service routine.

Initialization may only take place once at program start.

18 E 783 GB
01.03.13/10144408
 Ventura Skaleo 100

3.4.2 LAN interface

A RJ-45 plug is needed to use the LAN interface of the Ventura IPC. The
LAN interface can be used as a CoDeSys programming interface or for the
data exchange with dialog terminals, bar code readers and other devices.
For this purpose, the library SysLibSockets.lib needs to be used. The
status LEDs LAN (link) and LAN (active) indicate a successful network con-
nection.

• Standard protocol CoDeSys

• Baud rate 10/100 Mbit/s

• IP address software controlled

Connection: RJ-45 connector

Pin Function
1 TX+
2 TX-
3 RX+
4 -
5 -
6 RX-
7 -
8 -

To achieve good EMI characteristics, the LAN cable needs to be grounded

with a short ground wire.

If the Skaleo IPC does not communicate via a switch or a local network, but
is connected directly to a programming PC, a cross-over cable needs to be
used to connect the PC.

3.4.3 COM interface

The Ventura Skaleo 100 features a COM interface. With the Ventura Skaleo
100 RS232 it is designed as a RS232 interface, while the Ventura Skaleo
100 RS 485 features a RS485 interface.

The COM interface is not available for programming. It can be programmed

freely by means of the library SysLibCom.lib. With the library KubesPrtLib.lib,
the KUBES protocol can be realized. This allows the connection of terminals
using the KUBES protocol.

For good EMI characteristics, a connector with plastic housing should be

preferred.

E 783 GB 19
01.03.13/10144408
Ventura Skaleo 100

3.4.3.1 RS232
For connecting devices to the Skaleo IPC via the RS232 terminal, a 9pin D-
Sub connector (male) is used. It matches the terminal of the device (female).
The RS232 interface can be used for data communication with dialog termi-
nals, bar code readers and other devices.

• Standard protocol CoDeSys

• Baud rate up to 115.2 kbit/s
• Potential separation no

Connection: 9pin D-SUB connector

Pin Function
1 -
2 TxD
3 RxD
9
5 4 -
4
8
3
5 GND
7
6
2
6 -
1
7 CTS
8 RTS
9 -
case ground (cable shielding)

3.4.3.2 RS485
For connecting devices to the Skaleo IPC via the RS485 terminal, a 9pin D-
Sub connector (male) is used. It matches the terminal of the device (female).
The RS485 interface can be used for data communication with dialog termi-
nals, bar code readers and other devices.

• Standard protocol CoDeSys

• Baud rate up to 115.2 kbit/s
• Potential separation no

Connection: 9pin D-SUB connector

Pin Function
1 shield
2 -
3 data B (RxD/TxD-P)
6
1 4 -
2
7 5 GND-
3
8
9
4 6 VP
5
7 -
8 data A (RxD/TxD-N)
9 -
case ground (cable shielding)

20 E 783 GB
01.03.13/10144408
 Ventura Skaleo 100

3.4.4 SD-card slot

The SD-card slot is compatible with SD-cards with a storage capacity of up
to 2 GB. It can be used for storing data or CoDeSys projects and is available
to download projects and consecutive generation of a boot project, as well
as firmware updates of the runtime system.

The SD-card contains a DOS file system. During operation of the IPC, the
SD-card may only be removed while no program accesses the card and wile
no file is opened.

For Skaleos of the revision 2 or younger inserting the SD-Card during opera-
tion can lead to communication errors depending on the type of card which is
used.
The following SD-Cards have been tested without communication errors:
Producer: Type:
Swissbit 1GB SFSD1024L4BN2SA-I-D1-131-STD
Swissbit 2GB SFSD2048L3BN2SA-I-D1-121-STD

While booting the system, the SD-card is initialized via the autoexec.bat file
and is available as drive B: From the CoDeSys application as well, the card
can be accessed via the drive letter B:

Sample project:

After having called this program the root-directory of the drive B: (SD-card)
contains a data file with the name Myname.txt and the stated content.

A SD-Card is not included in the scope of delivery and has to be ordered

separately. Using a industrial SD-card is recommended.

E 783 GB 21
01.03.13/10144408
Ventura Skaleo 100

3.5 Control and display elements

3.5.1 Stop/reset key

The stop/reset key is located at the front of the module below the status indi-
cators.
In order to prevent unintentional activation, the stop/reset key can only be
activated with a pointed devices (such as ball point pen, screw driver).
Pressing it once for less than 5 seconds causes the Skaleo IPC to go into
stop mode. Pressing it again with a duration of less than 5 seconds re-
activates the start mode of the Skaleo IPC.

Pressing the key for more than 5 seconds activates a reset of the Skaleo
IPC. After doing so, an SD-card can be inserted or a new project can be
loaded into the control unit.

While the unit is in reset mode, no communication with the Ventura Skaleo
100 is possible. All CoDeSys connections are terminated, resulting in a
“communication terminated” error message.

A hardware reset means total deactivation of the SPS processor. This ef-
fects the SPS program as well as all interfaces. After the reset is completed,
the unit will restart again. All variables with the exception of the RETAIN
variables will be reset into their initialization state (default value “0”).

3.5.2 Status indicators

3.5.2.1 EtherCAT LED

The EtherCAT LED indicates the condition of the EtherCAT ASIC.

Condition LED, signal Meaning

Init Red, continuous Initializing, no data exchange
Pre-Op Red/green, 1:1 Pre-operational state, no data exchange
Safe-Op Red/green, 3:1 Safe operational state, inputs are accessible
Op Green, continuous Operational state, full data exchange

3.5.2.2 Run/Stop LED

The run/stop LED indicates the condition of the CoDeSys project.

Condition LED Meaning

Run Green CoDeSys project running
Stop Red CoDeSys project stopped
Reset Yellow CoDeSys project resetted

22 E 783 GB
01.03.13/10144408
 Ventura Skaleo 100

3.5.2.3 Error LED

The error LED indicates an error condition of Skaleo IPC.

LED, signal Meaning

Red, 1x Short circuit
Red, 2x Undervoltage
Red, 3x Watchdog
Red, 4x Bus error EtherCAT
Red, 8x No CoDeSys project loaded

3.5.2.4 LAN (linked) and LAN (active) LED

The LEDs LAN (linked) and LAN (active) indicate the physical condition of
the Ethernet port.

Condition LED Meaning

Linked Green Connected
Active Yellow Active data exchange

3.5.2.5 DI LED
The DI LED indicates the condition of the digital interrupt input.

Condition LED Meaning

Active Green Input active

3.5.2.6 24 V LED
The 24 V LED indicates the condition of the power supply.

Condition LED Meaning

On Green 24 V DC available

E 783 GB 23
01.03.13/10144408
Ventura Skaleo 100

3.6 System memory

The Ventura Skaleo 100 IPC is equipped with the following memory chips:

• Flash EPROM 8 Mbyte

Used for SPS program appx. 6 Mbyte
Used for programs, fixed data and file system
• RAM 8 Mbyte
Used for SPS program appx. 256 kByte
Used for variable data and operands
• Remanent data 1 kByte
Used for retain and extra remanent data
• SD-card max. 2 Gbyte
Used for program and runtime system transfer, fixed data

Presently, the runtime system uses the memory as follows:

3.6.1 Data ranges

Initially, the memory range for data is smaller than 64 kByte. Using the func-
tion SkaleoGetMemoryPtr(), additional memory ranges can be allocated. A
total of 192 kBytes is available. However, it is not possible to allocate indi-
vidual data ranges of more than 64 kByte. Access to all allocated data
ranges is achieved by means of pointers.

3.6.2 Retain variables

Presently, the memory range for retain variables has a size of 1024 bytes.
During power down, this range is saved to the internal flash memory and will
be restored from there during the next boot procedure. This range is secured
by means of a check sum.

24 E 783 GB
01.03.13/10144408
 Ventura Skaleo 100

3.7 Web server

The system features a web server which presently consists of the following
pages:

Start page

“Skaleo settings”

The start page can be accessed via: http://[IP address of the Skaleo
100]/kuhnke.htm

The illustration above shows the start page with the IP address 172.25.1.195
of the Skaleo 100 IPC. See chapter 4.3 to determine the IP address.

The settings page can be accessed by clicking onto the button “Settings”.
This page allows the configuration of settings, such as IP address, subnet
mask, date and time.

E 783 GB 25
01.03.13/10144408
Ventura Skaleo 100

3.8 Web visualization

In order to use the the web visualization of the Skaleo IPC, the setting “web
visualization” needs to be selected in the settings of the target system.

When selecting the settings of a visualization it needs to be observed that

the start page into the visualization carries the name “PLC_VISU”.

CoDeSys generates the required files for the target system and automati-
cally loads them to the system as soon as an online connection is estab-
lished.

To select the visualization, the browser needs to be directed to the address

http://[IP address of the Skaleo 100]/webvisu.htm

26 E 783 GB
01.03.13/10144408
 Ventura Skaleo 100

For further information to determine the IP address, please consult chapter

4.3.

It is necessary to activate the Java applets of the browser. This will auto-
matically start the respective Java engine for using the visualizations.

The name of a visualization as well as the name of any bitmaps must not
exceed a length of 8 characters!

Web server and Web Visu can be used at the same time.

Take the following steps in order do enable dynamic web visualization:

• Open the directory with the explorer

• Go to C:\programs\3S Software\CoDeSys V2.3\Visu
• Open the file webvisu.htm with an editor
• insert the following text into the forth line (section printed bold only):

<param name="USEFIXSOCKETCONNECTION" value="FALSE">

<param name="USEURLCONNECTION" value ="TRUE">
</APPLET>
</BODY>
</HTML>

• Save the file

E 783 GB 27
01.03.13/10144408
Ventura Skaleo 100

3.9 Watchdog

With the Skaleo 100 IPC, activating the watchdog requires slightly more ef-
forts than with other CoDeSys-based systems.
For a watchdog to become active at all, the task configuration needs to be
set accordingly:

This will result in monitoring the respective task. Whenever the selected time
is exceeded, the task will be suspended automatically. However, this operat-
ing condition is not indicated by the Skaleo 100 IPC in any way.
For this reason, the following code needs to be integrated into the applica-
tion program to cause the error LED to flash.

This initialization may only take place once at the start of the application.

28 E 783 GB
01.03.13/10144408
 Installation

4. Installation

4.1 CoDeSys installation on the programming PC

Install the CoDeSys software on your programming PC.

• Locate the file CoDeSys....exe via the Windows Explorer or select

“execute” in the start menu to type the file name.
• Execute the application.
• The installation dialog of CoDeSys will start and the software will be
installed with your settings on the target system.

You can download the latest installation version of the CoDeSys program-
ming system from www.3s-software.com.

4.2 Target installation in CoDeSys

In order to create a CoDeSys project for the Ventura Skaleo 100 IPC, the
Target Support Package (TSP) “Target_Skaleo100_VXX_XX” needs to be
installed before starting the programming system.

You can download the latest TSP free of charge from www.kuhnke.com.

The target needs to be installed by means of the batch file install.bat (which
needs to be extracted from the ZIP file prior to starting it). It must not be in-
stalled by means of the program InstallTarget.exe from 3S.

Presently, the batch file will not be installed into the standard directory
C:\programs\common files\CAA-Targets,
but into the directory
C:\programs\3S Software\CoDeSys V2.3\Targets\Kuhnke

Before installing a new version of the target, the old target needs to be dein-
stalled with the program InstallTarget.exe from 3S. After that, the directory

C:\programs\\3S Software\CoDeSys 2.3\Targets\Kuhnke\VenturaSkaleo100

needs to be deleted, before the target can be installed as described above.

A TSP contains all configuration and extension files (target system, target)
required to operate a specific control system by means of an application.
The configuration data include: code generator, memory layout, functional
scope of the control system and I/O modules
In addition, libraries, as well as error and ini files for the PLC browser will be
integrated. After successful installation the Skaleo IPC can be accessed via
the programming system.

E 783 GB 29
01.03.13/10144408
Installation

4.3 Settings of the IP address of the Skaleo IPC

• After the Ventura Skaleo 100 IPC is connected to a power source, it

needs to be connected via an Ethernet cable to a local network or via a
cross-over cable directly to the programming PC.
• Use the tool @CHIPTOOL from Beck to locate the device in the
network.

It will show you the IP address and the subnet mask of the Skaleo IPC.

• Note the IP address and subnet mask for later use.

4.4 Settings of the CoDeSys programming PC

4.4.1 Ethernet interface settings on the programming PC

Connection via a network

On the programming PC, no special settings should be necessary to pro-
gram the Skaleo IPC via a local network.

Windows 98 – Direct connection

• From the start menu, select Start – Settings – System Control: Network
– TCP/IP – Properties.
• Select the tab “IP address” and then “Setting IP address”. Enter an IP
address which must be identical to the one you noted according to the
instructions in Chapter 4.3, except for the last three digits. Type the
subnet mask noted according to chapter 4.3.
Example: 172.25.1.100 (instead of 137), subnet mask 255.255.0.0

30 E 783 GB
01.03.13/10144408
 Installation

Windows XP – Direct connection

• From the start menu, select Start – Settings – Network Connections: LAN
Connection – Properties
• Select the tab “General” and select “Internet protocol (TCP/IP)” from the
list. Select “Properties”.
• Select the tab “General”. Under “Use the following IP address”, enter an
IP address which must be identical to the one you noted according to the
instructions in Chapter 4.3, except for the last three digits. Type the
subnet mask noted according to chapter 4.3.
Example: 172.25.1.100 (instead of 137), subnet mask 255.255.0.0

If you connect the programming PC directly to the Skaleo IPC, “File and
Printer Sharing” needs to be activated. Any active firewall needs to be deac-
tivated at least for this connection.

4.4.2 Setting the communication parameters within CoDeSys

The communication channel can be selected and configured in the “Com-

munications Parameters” window of the “Online” menu.

• Open the “Communication Parameters” window of the “Online” menu.

Click onto “New” button. You will see the dialog “Comunication parameters:
new channel”

The “name” field will automatically show the name of the channel which was
entered last. You may edit the name of the channel. The channel number is
for information purposes only. Unambiguity is not mandatory, but recom-
mended.
The table in the “devices” field lists all device drivers available on the gate-
way computer. Your options depends on the drivers installed on your com-
puter.

• For an Ethernet connection, select the entry “TCP/IP” (Level 2 Route).

• In the field “Address” enter the IP address of the Skaleo 100 IPC, which
you determined according to the procedure described in chapter 4.3
• In the field “Motorola Byte order” select “No”.

E 783 GB 31
01.03.13/10144408
Installation

Sample of the communications parameters settings for an Ethernet connec-

tion.

4.5 Create a CoDeSys project with EtherCAT

• Set up a new CoDeSys project on the programming PC

• Select the target VenturaSkaleo 100
• A window will open. Select the “General” tab and select “no address
checking” and when using EasiCat_1_7_1 or newer also select “Byte-
addressing”

• Close the window by clicking onto “OK”.

• Set up the module PLC_PRG as a “program” and select “ST” as
language.
• Close the window by clicking onto “OK”.
• Insert a semicolon (;) into the program to prevent the generation of an
error message during translation.
• Set the communications parameters as described in chapter 4.4.2.
• Save the project.

32 E 783 GB
01.03.13/10144408
 Installation

4.5.1 Loading a CoDeSys boot project onto the SD-card

This function is offered by all Skaleo IPCs from version 1.60 onward:

• Generate a CoDeSys boot project on a Skaleo IPC.

• In the root directory of a SD-card generate a directory with the name
“PGUPDATE”.
• Insert the SD-card into the Skaleo IPC.
• Turn off the Skaleo IPC and restart it.
• Wait until the boot project has started. The project will then be stored in
the above mentioned directory.
• Remove the CD-card.

4.5.2 Loading a CoDeSys boot project from the SD-card

4.5.2.1 Loading a boot project without version information

This function is offered by all Skaleo IPCs from version 1.60 onward:

• Insert a SD-card with a CoDeSys boot project in the PGUPDATE

directory into the Skaleo IPC.
• Restart the Skaleo IPC. This will automatically install the boot project
onto the Skaleo IPC.
• Remove the SD-card

The boot project will only be transferred to the Skaleo IPC if ether no boot
project is available on the Skaleo IPC or if the project on the SD-card has a
later date than the one on the Skaleo IPC.

E 783 GB 33
01.03.13/10144408
Installation

4.5.2.2 Loading a boot project with version information

This function is offered by all Skaleo IPCs from version 2.12.3 onward:

• Insert a SD-card with a CoDeSys boot project in the PGUPDATE

directory into the Skaleo IPC.
• Restart the Skaleo IPC. This will automatically install the boot project
onto the Skaleo IPC.
• Remove the SD-card

The boot project will only be transferred to the Skaleo IPC if no version file is
available on drive A:\ of the Skaleo or if the version file on the SD-card is not
identical with the one on the IPC. When comparing the files ct the beginning
the first 31 characters of the name, then the size of the file and finally the
date of the file are taken into consideration. The version file is the last file
which is copied. Accordingly an incorrect copying process will be detected at
the next boot-up.

4.6 Operation of EtherCAT slaves

The EthterCAT master function is realized by means of the library

“KuhnkeEcatLibSkaleo.lib” With this library, it is possible to access Ether-
CAT devices and exchange data. The installation and configuration of an
EtherCAT bus system is described in the manual E 773 D “Ventura EasiCat”
for Kuhnke Masters with Ethernet interface.

The library KuhnkeEcatLibSkaleo.Lib has already been installed together

with the target!

Presently, the runtime of EtherCAT is app. 2 ms.

Presently, the FIO thermo modules are not released for use with the Ventura
Skaleo IPC.

34 E 783 GB
01.03.13/10144408
 Installation

4.6.1 System requirements

The firmware of the Ventura Skaleo IPC needs to be version 1.62 or higher.

To determine the firmware version of the Skaleo IPC, use the command
“ver” in the PLC browser of CoDeSys. The last line contains a reference to
the version number.
Example: OEM Impl.Version: Skaleo100 V01.62 Build 1 001 2701

4.6.2 Install EasiCat configurator

Install the EtherCAT configurator by starting the program

setup_EasiCat_x_y_z.exe.

• Start the setup program

• Click onto “Next”

• Determine the directory you want to use for the installation of EasiCat

E 783 GB 35
01.03.13/10144408
Installation

Next, setup will ask for the program group to install the link for starting the
program.

In the next step, the following message will appear:

• Click onto „Install“.

Afterwards the EasiCat is started and the following window appears:

• Click onto “OK”.

36 E 783 GB
01.03.13/10144408
 Installation

• Select in the menu “Optionen/ Sprache”

• Select “English” and click onto “OK”

• Select in the menu “Options/XML Path”

• Enter the path to the device driver file “KuhnkeEtherCATModules.xml”
• Confirm by clicking onto “OK”.

In this example, the path C:\programs\EtherCAT Configurator\EtherCAT was

selected. This is the directory containing the device description files of the
Beckhoff configurator used for the Ventura IPC.

E 783 GB 37
01.03.13/10144408
Installation

• Copy the file Skaleo.XML and the device description files (XML files) for
all devices to be included into the directory you selected.

EasiCat will present itself in the following way on the screen:

• Close the configurator.

4.6.3 Select EtherCAT participant

• Save the CoDeSys project. The project needs to be saved once before
the configurator can be activated! Please also note the descriptions in
chapter 4.6.6 “Renaming a CoDeSys project”.
• Go9 to the control configuration and click onto “Ventu-
raSkaleo100[SLOT] while you keep the right mouse button pressed, in
order to select “Attach EtherCAT UDP Master”.

38 E 783 GB
01.03.13/10144408
 Installation

• Click onto “EtherCAT UDP Master[VAR]” and then click in the right hand
window onto “Configurator”.

• Right click on the symbol of the target system and select “add module”.

• A window will open. Select “Skaleo” under “Kuhnke Automation GmbH

& Co. KG”. Then click onto “Add”.

E 783 GB 39
01.03.13/10144408
Installation

• Click onto the entry “Skaleo” at the upper left side and select the I/O
modules connected to the Skaleo IPC. Please observe the correct or-
der. In case several identical modules are connected next to each other,
you can select the number in the field at the bottom of the window.

40 E 783 GB
01.03.13/10144408
 Installation

• After concluding the module selection, click onto “Close” to return to the
main window.
• Click onto the “Modules” tab in order to get an overview of all selected
participants.

• Make sure that all modules are set to “Active”.

• Now click onto the “CoDeSys Export” tab.

• Make sure that all positions are marked as shown in the figure above.
• Select the “File” menu and click onto “Exit” to save the configuration.

E 783 GB 41
01.03.13/10144408
Installation

EasiCat will now save the data under the project name in the directory con-
taining the CoDeSys project you created.
After the process is concluded, the configurator will close and CoDeSys will
appear in the foreground again.

42 E 783 GB
01.03.13/10144408
 Installation

4.6.4 Importing configuration data into CoDeSys

In course of the configuration process described in the previous step, Easi-

Cat has created three files in the project directory:

<project name>.eco, <project name>.exp and <project name>.kec.

• In the “Project” menu of CoDeSys select the option “Import”.

• Select the project directory.

• Select the file <project name>.exp and click onto “Open”.

This will include the configuration of the EtherCAT participant into the pro-
ject. The configuration data will be stored in the subdirectory “Global vari-
able” of a new directory KUECAT .

The new variables – meaning the input and output data of the configured
Ethernet slaves – are not stored in the directory containing the control con-
figuration, but are stored unter global variables.

E 783 GB 43
01.03.13/10144408
Installation

4.6.5 Changing of the control configuration with EasiCat

If you want to change the control configuration after the configuration file
was already imported into CoDeSys, the following procedure needs to be
observed:

• First delete the directories KUECAT from the list of global variables,
from the visualizations and from the components!

This step can be omitted, if the configuration file was not imported yet. In this
case, proceed as described in the following steps:

• Start the configurator as described in chapter 4.6.3 and change the

module selection.
• Save the new configuration under the same name, by clicking onto “File”
and “Save”.
• Close the configurator in order to return back to CoDeSys.
• Import the configuration file <project name>.exp into CoDeSys, as de-
scribed in chapter 4.6.4.

44 E 783 GB
01.03.13/10144408
 Installation

4.6.6 Renaming a CoDeSys project

If you want to change the project name after the configuration file was al-
ready imported into CoDeSys, the following procedure needs to be ob-
served:

• Change the name of the input variable “sFilename” of the component

Ecat into <project name>.kec.
Replace <project name> by the new name of the CoDeSys project.

This step can be omitted, if the configuration file was not imported yet. In this
case, proceed as described in the following steps:

• Start the configurator as described in chapter 4.6.3 and change the

module selection.
• Save the new configuration under the new name, by clicking onto “File”
and “Save”.
• Close the configurator in order to return back to CoDeSys.
• Import the configuration file <project name>.exp into CoDeSys, as
described in chapter 4.6.4.

If no configuration file was created with the configurator, the name of CoDe-
Sys project can be changed without limitations. However, generating a valid
project always requires importing a configuration file with the same name as
the respective CoDeSys project.

E 783 GB 45
01.03.13/10144408
Installation

4.6.7 Including an EtherCAT master into CoDeSys

In order to get a consistant process representation, it is recommended to ac-

tivate the EtherCAT program module within PLC-PRG!

Thus the number of deactivated slaves is set to 0 (see also chapter 5.4), the
EtherCAT program is called up and the program code will be started, as
soon as the EtherCAT bus runs without errors. There is no need to activate
the module InitKuhnkeECat.

Alternatively, it is also possible to include the master as a task as follows:

• Go to the task configuration.

• Right click onto the symbol “tTask Configuration” and include a new
cyclical task.

• Name this task – for example “EC” – and enter the time interval for
cyclic sending of telegrams. The time cycle should be > 10 ms (by
entering t#10ms).

46 E 783 GB
01.03.13/10144408
 Installation

• Right click in the center window onto the clock symbol next to the task
“EC” and select “Attach program execution”.

• In the input field “Program execution” select the module “Ecat(PRG)”.

• Confirm by clicking onto “OK”.

This concludes the creation of a ready-to-turn EtherCAT master.

In the browser view, some odd characters will appear. This is a result of the
high number of parameters of the module and is not of importance. You can
avoid the display of these odd characters by directly entering the program
name “ECat” into the field “Program execution” without stating any additional
parameters.

E 783 GB 47
01.03.13/10144408
Installation

4.7 SPS function libraries

With the target installation (see page 29) CoDeSys also will receive a num-
ber of function libraries for the target system Ventura Skaleo 100.
Skaleo100.lib contains functions to access resources on the Skaleo 100
IPC.
SkaleoRS485.lib contains functions for using the RS485 interface.
KuhnkeECatLibSkaleo.lib contains functions to use the EtherCAT master
functions with the Skaleo IPC. This library allows the access of EtherCAT
devices and the exchange of process data with such devices.
Kubes PrtLib.lib contains functions to use the Kubes protocol on CoDeSys-
SPS controls.

4.7.1 Skaleo100.lib
Skaleo100.lib contains the following functions:

Name Purpose

SkaleoComCheckInput Counts the number of bits to be read from the port

SkaleoGetDate Returns the actual date

SkaleoGetDigIn Counts the interrupts at the interrupt input

SkaleoGetDiskSpace Calculates the total or free disk space of a drive

SkaleoGetMemoryPtr Returns a pointer to a data section with a length of “memsize”

SkaleoGetPersistenceData Read up to 64 persistent data bytes (see 5.3 “Hardware stamp”)

SkaleoGetSerialNumber Reads the serial number

SkaleoGetTime Returns the actual time

SkaleoIOGetPinState Reads an I/O port

SkaleoIOSetPinState Positions an I/O pin

SkaleoIsSDCardPresent Checking the presence of a SD-card

SkaleoIsSDCardReadOnly Checks whether the SC-card is in read-only mode

SkaleoIsVoltageOK Checks for undervoltage. TRUE, if voltage is OK, otherwise FALSE

SkaleoNTPInstallService Starts the NTP service

SkaleoNTPIsService-Finished Checks whether the service was concluded?

SkaleoNTPStartService Stats the one-time execution of the service

SkaleoResetSystem Initiates a reset of the complete system

SkaleoSetInputIrqHandler Installs a callback function for the input interrupt

SkaleoSetPersistenceData Positions up to 64 persistant data bytes (see 5.3 “Hardware stamp”)

SkaleoSetU24VIrqHandler Installs a callback function for the undervoltage event

SkaleoSynchClockFromRTC Synchronizes the RTC with the DOS clock

SkaleoWatchdog Installs the watchdog

SET_WATCHDOG Installs the watchdog

48 E 783 GB
01.03.13/10144408
 Installation

From version 1.64 onward, Skaleo100.lib contains the following additional

functions:
Name Purpose

SkaleoGetLZSVersionInfo Returns the version string of the runtime system

SkaleoGetSDCardInfo Reads the internal registers CSD and CID of the SD-card
SkaleoIsPingDone Checks whether ping was successful

SkaleoSendPing Function to send a ping

SkaleoSetTimeDate Function to set date and time

4.7.2 SkaleoRS485.lib

SkaleoRS485.lib contains the following functions:

Name Purpose

Rs485ComClose Closes an open RS485 interface

Rs485ComOpen Opens a RS485 interface

Rs485FlushOutput Spontaneous output of the characters in the buffer of the interface

Rs485GetStatus Status of the interface – the returned value contains the following bits:
Bit 7: %
Bit 6: output buffer is empty
Bit 5: output buffer is not full
Bit 4: Cable interruption detected
Bit 3: Framing error detected
Bit 2: Parity error detected
Bit 1: Receiver-side overflow detected
Bit 0: Data in input buffer detected

Rs485IsByteAvailable Is at least one Byte in the input buffer?

Rs485PurgeInput Clearing of the input buffer

Rs485PurgeOutput Clearing of the output buffer

Rs485ReceiveBlock Reception of a block of multiple bytes

Rs485ReceiveByte Reception of one single byte

Rs485SendBlock Sending of a block of multiple bytes

Rs485SendBreak Sending of a break to terminate the transmission

Rs485SendByte Sending of one single byte

Rs485SetDirection Determining data direction

Rs485SetFlowcontrol Setting the flow control parameters

Rs485SetMode Setting the modes, such as high or low active

The function library SkaleoRS485 is available at the target, but will not be
loaded automatically with the start of a new project.

E 783 GB 49
01.03.13/10144408
Installation

4.7.3 KuhnkeECatLibSkaleo.lib

KuhnkeECatLibSkaleo.lib exclusively contains programs, functions and

components for internal purposes. These functions may not be used in any
application program and are therefore not explaind in detail.

4.7.4 KubesPrtLib.lib

KubesPrtLib.lib contains the following functions:

Name Purpose

kbs_M Interface component to the KUBES protocol

To be able to use the KubesPrtLib.lib, the SyslibCOm.lib needs to be inte-

grated.
The function library KubeaPrtLib.lib is available in the target, but will not be
loaded automatically when establishing a new project.

50 E 783 GB
01.03.13/10144408
 Special functions

5 Special functions of the Skaleo 100

5.1 Time synchronization with an NTP server

The Skaleo IPC is able to synchronize the realtime clock with an NTP time
server at defined intervals. This function is implemented as follows.

The function SkaleoNTPInstallService(...) initiates a connection to the NTP

server.

E 783 GB 51
01.03.13/10144408
Special functions

The function SkaleoNTPStartService() obtains the time once and transfers it

to the RTC of the Skalo as well as the software clock of the CoDeSys run-
time system. The function SkaleoNTPIsServiceFinished() determines
whether the service is concluded. From version 1.64 onward, this function
will return error no. 2 if the clocks were not set.

This function is available with Skaleo IPCs with firmware version 1.60 and
later.

5.2 Update of the runtime system with an SD card

The Skaleo IPC is able to synchronize the system files of the runtime system
via a SD-card.

5.2.1 Update without version information

• Insert a SD-card containing system files in the directory RTUPDATE into

the Skaleo IPC.
• Restart the Skaleo IPC. This will automatically transfer the system files
to the Skaleo IPC.
• Remove the SD-card

The system files will only be transferred to the Skaleo IPC if no system file is
available on drive A:\ of the Skaleo or if the system file on the SD-card is a
newer version than that on the IPC.

This function is available with Skaleo IPCs with firmware version 1.60 and
later.

These are the system files:

"AUTOEXEC.BAT", "BECK.GIF", "BILD1.JPG", "BILD2.JPG", "BOOT.SDB",
"CHIP.GIF", "CHIP.INI", "ETH1.EXE", "EXTSD.EXE", "FUPDATE.EXE",
"KUHNKE.HTM", "MYCGI.EXE", "NOTOK.HTM", "OK.HTM",
"PAGE2.HTM", "RT.EXE", "SETCLOCK.EXE"
From firmware version 1.63 onward, the file BOOT.SDB is not catego-
rized as a system file anymore.

52 E 783 GB
01.03.13/10144408
 Special functions

5.2.2 Update with version information

• Insert a SD-card containing system files in the directory RTUPDATE into

the Skaleo IPC.
• Restart the Skaleo IPC. This will automatically transfer the system files
to the Skaleo IPC.
• Remove the SD-card

The system files will only be transferred to the Skaleo IPC if no version file is
available on drive A:\ of the Skaleo or if the version file on the SD-card is not
identical with the one on the IPC. When comparing the files only the first 31
characters of the Name are taken into consideration. The version file is the
last file which is copied. Accordingly an incorrect copying process will be
detected at the next boot-up.

This function is available with Skaleo IPCs with firmware version 2.12.3 and
later.

These are the system files:

"AUTOEXEC.BAT", "BECK.GIF", "BILD1.JPG", "BILD2.JPG", "BOOT.SDB",
"CHIP.GIF", "CHIP.INI", "ETH1.EXE", "EXTSD.EXE", "FUPDATE.EXE",
"KUHNKE.HTM", "MYCGI.EXE", "NOTOK.HTM", "OK.HTM",
"PAGE2.HTM", "RT.EXE", "SETCLOCK.EXE"
From firmware version 1.63 onward, the file BOOT.SDB is not catego-
rized as a system file anymore.

5.3 Hardware stamp

From version 1.63, the Skaleo IC is delivered with a hardware stamp. This
provides increased know-how protection and offers the following function:

The hardware stemp prevents that the runtime system on the chip of a
Skaleo IPC can be copied to another chip.

By means of the component “SkaleoSetPersistenceData” of the

Skaleo100.lib library, an identification with a size of up to 64 Bytes can be
stored together with a project. This identification can be read with the com-
ponent “SkaleoGetPersistenceData”. Reading this identification can be inte-
grated into a project. In this way, copying the boot project by a third party not
owning the source code of the project is only permitted if a respecitive identi-
fication is available.

E 783 GB 53
01.03.13/10144408
Special functions

5.4 Deactivation of slaves of a control system configuration

From version 1.62 onward, the Skaleo IPC is able to de-activate a defined
number of salves of a control configuration.

• This function is achieved by setting the integer variable

nNumberDisableSlaves in the PLC-PRG
prior to the Ecat component.

This variable is part of the global variable (VAR_GLOBAL PERSISTENT>

RETAIN) of the library KuhnkeECatLibSkaleo.lib!

“nNumberDisable Slaves” determines the number of the last slaves of the

control configuration which are to be deactivated.
For example, nNumberDisable Slaves :=5 means that the last 5 slaves of the
control configuration of the present CoDeSys project will be deactivated.

It is only possible to deactivate the last slaves of a configuration. It is not

possible to deactivate specific slaves which are not located at the end.

5.5 Customer specific error HTML pages for the web server

In addition to the parameter settings described in chapter 3.7, from version

1.64 onward, the standard pages to respond to errors no. 401, 404, 500 and
503 can be replaced by customer-specific pages.
These pages can be stored on drive A:\ with the file names, such as
HTLM401.HTM, HTML404.HTM, HTML500.HTM and
HTML503.HTM and will be displayed when the respective er-
rors occur.

54 E 783 GB
01.03.13/10144408
 Special functions

5.6 Sending a ping

With the library functions “SkaleoSendPing” and “SkaleolsPingDone” in the

file Skaleo100.lib, from version 1.64 onward a ping can be sent to an exter-
nal Ethernet participant.

Sample program:

E 783 GB 55
01.03.13/10144408
Special functions

5.7 Reading of the Skaleo100.lib version

From version 1.64 onward, the library Skaleo100.lib defines two global vari-
ables which can be used by the application program:

5.8 Reading of SD-card specific information

From version 1.64 onward, the internal registers CSD and CID of the SC-
card can be read with the function “SkaleoGetSDCardInfo”.

To gather this information, the operating system needs some time. After in-
serting the card it can take up to 500 ms until the correct information is dis-
played in the field.

For additional information on the registers, please visit:

http://www.sdcard.org/developers/tech/sdcard/pls/Simplified_Physical_Layer
_Spec.pdf

5.9 Writing data on drive A

When writing data on driva A the following limitations have to taken into con-
sideration:

Writing data on drive A is only save, if it can be ensured that all files are clo-
sed accordingly before the Skaleo will be shut down!
If it can not be ensured that all files will be closed accordingly, the files have
to be stored on drive B (SD-card)!

56 E 783 GB
01.03.13/10144408
 Error treatment

6 Error treatment after a system crash

In case the SPS program (with boot project) should repeatedly crash shortly
after program start and initiate a restart of the system, it is not possible to
use the RESET key to stabilize the system again.

In order to end such a fatal endless loop, a SD-card needs to be inserted.

This card needs to have an empty directory named PGRESET. At a reboot
of the system, the boot project files DEFAULT.PRG, DETAULT.CHK and
BOOT.SDB will be renamed into DEFAULT.PRX, DEFAULT.CHX and
BOOT.SDX. From now on, the system will not start automatically with the
SPS program anymore and can be accessed via CoDeSys as well as an
FTP client.

Alternatively, it is also possible to copy a fault-free boot project via the SD-
card. Further details are described in chapter 4.5.2.

E 783 GB 57
01.03.13/10144408
Appendix

7 Appendix

7.1 Technical specifications

7.1.1 Ventura Skaleo 100

Field bus EtherCat 100MBit/s 100 Base TX according

to IEEE802.3
Dimensions 25mm x 120 mm x 90 mm (W/H/D)
Case carrier Aluminum
Shielded connector directly at the module case
Mounting 35 mm DIN rail
I/O terminal 3-pin spring loaded connector with
mechanical release
Signal indicators LED: EtherCAT status, module status, input
status, short circuit / undervoltage /watchdog
/CoDeSys project
Number of terminals 1x LAN, 1x COM, 1x SD-card, 1x digital
interrupt input
Controller Beck IPC@Chip®
Supply voltage 24 V DC -20% / +25%
Extension Connector for the first Ventura FIO I/O module
integrated into the side of the module
Number I/O modules Up to 15 FIO modules with 1 Skaleo IPC
Storage temperature -25°C … + 85°C
Relative humidity 5% … 95% non condensing
Protection rating IP20
Interference resistance Zone B according to EN 61131-2
if mounted on grounded DIN rail in grounded
switching cabinet

7.2 Ordering information

IO/Power
Name Order no.. Ident no.
plug
Ventura Skaleo 100 RS232 694.300.00 157.090 3-pin

Ventura Skaleo 100 RS485 694.300.01 162.849 3-pin

58 E 783 GB
01.03.13/10144408
 Appendix

7.3 Further reading

Title/subject Number Source

Manual Ventura EasiCat E 773 D http://www.kuhnke.de
Technical Info Ventura FIO E 740 D http://www.kuhnke.de
EtherCAT, Technology, FAQs, Downloads http://www.ethercat.org
CoDeSys manuals
(available as PDF in the CoDeSys direc- http:// www.3s-software.com
tory on the programming PC)

E 783 GB 59
01.03.13/10144408
Sales & Service

8 Sales & Service

Please visit our website to find further information on our sales and service
network and the respective addresses. Feel free to also contact us at our
headquarter in Malente/Germany:

8.1 Malente headquarter

Kuhnke Automation GmbH & Co. KG

Lütjenburger Straße 101
23714 Malente/Germany
Phone +49 45 23 402 0
Fax +49 45 23 402 247
Email [email protected]
www.kuhnke.de

8.2 Customer service / customer care

Kuhnke Automation GmbH & Co. KG

Lütjenburger Straße 101
23714 Malente/Germany
Phone +49 45 23 402 200
Email [email protected]
www.kuhnke.de

60 E 783 GB
01.03.13/10144408
 Index

9 Index

Attention 8 LAN (active) 23

CoDeSys LAN (linked) 23
Communication parameters 32 Run/Stop 22
CoDeSys Maintenance 9
Boot project from SD-card 34 Mechanical design 13
Boot project onto SD-card 34 Memory
Create a project 33 Allocating of data ranges 24
CoDeSys installation 29 Retain variables 24
COM interface 19 Memory 24
RS232 20 Models
RS485 20 Terminology 6
Contamination 11 Mounting 14
Danger 8 Note 8
Deactivation of slaves 54 Operating instruction 8
Demounting 15 Ordering information 58
Description of system 13 Place of Installation 11
EasiCat configurator 35 Power supply 16
Electromagnetic compatibility 10 Project design 9
Electromagnetic influences 12 Reading SD-card specific information 56
Electromagnetic interferences 10 Reliability 7
Error treatment after a system crash 57 Repair 9
EtherCAT slaves 34 Safety 8
Function libraries 48 Sales & Service 60
KubesPrtLib.lib 50 SD-card slot 21
KuhnkeECatLibSkaleo.lib 50 Sending a ping 55
Skaleo 100.lib 48 Shock and vibrations 11
SkaleoRS485.lib 49 Status indicators 22
Function library Stop/reset key 22
Skaleo100.lib 56 Target group 7
Grounding 17 Target installation 29
Inductive actors 12 Technical specifications
Installation 9 Overview 58
Installation notes 10 Temperature 11
Instructions 8 Time synchronization 51
Interrupt input 18 Under development 8
IP address 31 Update runtime system 52
Know-how protection 52 Watchdog 28
LAN interface 19 Web server 54
LED Web server 25
24V 23 Web visualization 26
DI 23 Wiring 11
Error 23 Writing data on drive A 56
EtherCAT 22

E 783 GB 61
01.03.13/10144408
Sales & Service

62 E 783 GB
01.03.13/10144408