IXXAT
started with ETHERNET Powerlink (EPL) version 2 in 2003 and in mid-2004 offered the
first complete EPL Protocol Stack according to the EPL V2 specification for Controlled
Nodes, Managing Nodes and combined Managing / Controlled Node implementations. The
software includes all mandatory functions of the EPL V2 specification and various optional
functions.
The IXXAT EPL protocol stack is available in a generic version which can easily be
ported to various target platforms and operating systems. The delivery content also
includes code which allows the stack to run directly on a reference system. This
enables a fast and easy start of development.
The EPL software stack has been developed in close cooperation with leading vendors of
ETHERNET Powerlink enabled devices like Bernecker & Rainer, Lenze and Hirschmann.
- Scope of functions based on the current Ethernet Powerlink (EPL) V2 specification
- High performance optimised modular software structure
- Enables quick and easy development of EPL devices
- Comprehensive configuration and scaling possibilities
- Clearly structured programming interface for connection of the application program
- "C" source code can be used with any target system
- Operation with or without operating system
- Adaptable to various Ethernet controller architectures and hardware architectures (e.g.
1-CPU, 2-CPU) via internal interfaces
- Dynamic modification of the Object Dictionary during operation
- Multi-channel capability

The EPL protocol software contains all the necessary functions for the
implementation of controlled nodes or managing nodes in accordance with the EPL V2
specification. It does not contain a TCP/IP stack, which is required for running the SDO
protocol via UDP, as this is usually provided by the operating system. Alternatively,
an external TCP/IP stack (commercial or open source) can be used. The integration of an
TCP/IP stack is simplified by the internal interfaces of the EPL stack.
The lower layers of the EPL software are specifically designed to guarantee fast response
times of real-time events on the EPL bus. Therefore, the access and the handling of the
Ethernet controller is encapsulated within a separate module, the lower layer driver
(LLD). For an adaptation of the EPL software to a specific CPU or hardware
platform, this module needs to be modified. This abstraction between
hardware-dependant routines and the higher layers of the EPL software makes it
possible to provide a high degree of scalability and adaptability. A configuration tool
delivered with the software allows optimum adaptation of the EPL functionality provided by
the protocol stack to the given application and thus enables effective use of available
resources which guarantees an extremely resource-efficient implementation.
The object dictionary is the interface between application and communication. Each object
dictionary entry can be directly allocated a reference to a variable with application
data. PDOs and SDOs access these application variables directly. Therefore, no
modifications to an existing CANopen application are necessary to integrate an EPL
protocol software.
User-specific call-back functions can be linked to every application object and
enable an event-controlled notification of the application in the event of accesses to
these objects. This mechanism allows a direct, application-specific reaction on
modifications to the application data caused on the bus side. In addition, saving and
recovery of configured data is also supported. The application is also able to build or
modify parts of the Object Dictionary during operation.
With PDOs, the EPL protocol software supports verification of the PDO version and of
the PDO size. Depending on the configuration used, PDO mapping can be configured
statically or dynamically, according to the required reaction speed or available
resources. Objects can be entered in several PDOs simultaneously.
With SDOs, the transfer types via UDP and via ASend (EPL frames) are supported. Both with
read and write accesses, the SDO-service can be confirmed by the application with a delay.
The application can thus check the data written by means of SDO for consistency before
overwriting the target variables and if necessary abort the SDO transfer. This mechanism
also enables data to first be acquired via another communication system (e.g. serial port)
before they are transmitted.
The EPL-protocol software enables the implementation of several independent EPL interfaces
in one device. Managing node or controlled node functionality can be configured
independently, also with independent object dictionaries in each case. In this way,
gateways can be developed that are connected to a higher order EPL network with one EPL
channel as a controlled node and control an EPL sub-network as a managing node with the
second EPL channel.
The EPL stack can be used with or without an operating system. The software has an
internal scheduler which ensures the optimal allocation of the available process
time resources to the various stack functions. When using an operating system, the
EPL stack is executed as one task. Only basic operating system functions like
semaphores and tasks are required. These functions are encapsulated by an abstraction
layer (GOE - Generic Operating Environment) and can, due to this, be easily adapted to
the operating system.
The "C" source code provided can be used on any target system. Besides the
generic version, the delivered software package includes implementation samples, which
work on Freescale Coldfire 523x based systems without the need of additional adaptation.
Evaluation boards with wiring diagrams (reference schematics) are also available. |
|