This software component implements a client for the DHCP protocol according to RFC-2131 and RFC-2132.

The DHCP client runs in the background as an application task. After start it requests a configuration from a DHCP server. It monitors the time for which an offered configuration is valid and applies for an extension of the cycle time. The application can communicate with the client by using an Eventflag object. This object can retrieve the status of the client. Likewise, the client can be shut down by using an Eventflag.

The EUROS FTP server implements an FTP server for embedded systems.

It supports the following commands from RFC 959: USER, PASS, CWD, CDUP, QUIT, PORT, TYPE, STRU, MODE, RETR, STOR, APPE, DELE, RMD, MKD, PWD, LIST, NLST, SYST, HELP, NOOP, REIN, PASV

In addition, the following non-standard commands are supported: XPWD, XMKD, XRMD, SIZE, MDTM.

The server can only handle one connection at a time. Only one client can be operated simultaneously. Both, an authentication with password and anonymous FTP connection without a password are supported. However, there a rights managing when accessing files does not take place???.

The server only supports the transmission mode "stream" and the file structure 'File'. It supports display types "ASCII" and "image" (binary). Both types are not distinguished.

Software requirements:

The FTP server requires the operating system EUROS, the EUROS - TCP / IP stack and the EUROS - file system.

The SNMP agent implements Simple Network Management Protocol version 1 as described in RFC 1157. It loads MIB-II (RFC 1213) and provides necessary support for MIB-II functionality.

The SNMP agent is implemented in EUROS as a separate task. It requires TCP/IP functionality and system services of the Microkernel, I/O System and Process Manager. Your hardware should be equipped with Ethernet or at least with a serial port. The examples in the respective document are configured for the Ethernet usage.

The user is responsible for creating a separate SNMP task, assigning its priority and reserving stack space for it. The values in the provided examples can be used for initial settings. The memory usage can be computed from the linker map.

The PPP is implemented as a Resource Manager under EUROS and represents a hardware-independent high-level driver.  The PPP Resource Manager can be used to transfer data frames over a serial interface. The Resource Manager does not depend on specific interface hardware. It must be attached to a Serial Port Driver that performs the actual transmission and reception using specific hardware. The resource manager can operate either as a server (passive connection) or as a client (active link). The resource manager works with all port drivers of type “serial”. A full duplex connection with 8 data bits is required. It can communicate either via a modem or directly using a null modem cable. The IP addresses can be specified using the system service netctl or it can be automatically determined during the connection time. An embedded unit operates either as a client (active link) or as a server (waiting for connection establishment to the remote party). The PPP Resource Manager can be used only on top of the network component.

The Ethernet/IP implements the Ethernet Industrial Protocol as described by the respective ODVA technical specification. By using this component one can quickly define and implement application-specific CIP services as well as support multiple sessions and connections. Ethernet/IP is highly configurable; one can fine-tune various aspects of the protocol communications depending on the application requirements.

The Ethernet/IP component implements a minimal CIP server with Ethernet/IP encapsulation. It is intended to be a toolset for the implementation of a product using Ethernet/IP. This software component does not comprise a "product" as described in the Ethernet/IP specification.

A "product" is a complete EUROS application using this software component. Therefore, the user of this component is the licensee of Ethernet/IP, not EUROS Embedded Systems GmbH.

It is the responsibility of the user to acquire a license and to integrate Ethernet/IP with the other software components that comprise a product. A number of object classes are pre-implemented (see below). The user has the option to implement additional standard classes or vendor-specific classes and to add them to the Ethernet/IP protocol stack.

Requirements:

The following  EUROS components are required when using the Ethernet/IP:

• Microkernel
• Process Manager
• Network component (TCP/IP)
• C library
• Ethernet port driver
• DHCP client (optional)

The POP3 library provides implementation of the Post Office Protocol and allows EUROS applications to retrieve electronic messages from remote servers over TCP/IP connections. If bundled with the secure sockets layer library, the combined libraries also support the STLS command and POP3 connections over TLS/SSL.

POP3 Client library is platform independent, written in ANSI C and can be used on any of the platforms build on EUROS. Since it relies on a standard BSD socket interface it can be integrated with EUROS TCP/IP stack (or any other third party stack supported by EUROS RTOS).

It supports all pop3 commands and states of a POP3 session. EUROS POP3 API offers functions for execution of both standard user defined commands. POP3 Client library detects not allowed cases of command execution, fails, timeouts, etc.