COPALP supplies a complete range of services and support in order to help you in the development of your communication stack.
Reliability, stability, reactivity and availability characterize the COPALP know-how.
COPALP has implemented a portable BACNET stack in their straton® product for very small devices as for PLC controllers. The ‘C’ ANSI code of the stack implementation is portable to any hardware platform with minimal effort. The biggest advantage of the COPALP implementation is a very small footprint for the program and its associated memory space.
The CAN protocol is an international standard. Based on this standard several protocols are available on the market, some are standardized like CANopen and other are proprietary.
COPALP through this new configuration tool provides customers with an open standard tool to configure all these protocols.

The Energy and Water industries require more and more complex protocols and control applications to meet the growing demands for more information, more often. DNP3 (distributed network protocol) slave for straton® is a new components for the COPALP’s customers in order to facilitate the integration of industry-standard protocols and applications and is simplifying the configuration process by providing the end customer with easy to use graphical tools.

The implementation of EtherNet/IP in the straton products supports both Scanner and Adapter. The configuration is convenient through an integrated configuration tool to create the mapping of the CIP I/O assemblies for the server as well as the client. Additionally a client configuration tool allows the exchanging of EtherNet/IP tag based devices such as PLCs.

A communication stack for IEC 60870 is available for the IEC 60870-5-101 (serial) and IEC 60870-5-104 (TCP/IP) connections.
The IEC60870 protocol is a standard mainly in the ernergy market.

IEC 61850 is a new worldwide accepted standard that defines the communication between electrical switchgear, control equipment in substation automation and the related system requirements. 
The PROFINET IO controller stack is composed of two C++ APIs. The first encapsulates all functions required by the runtime application, which are configuration of cyclic data exchange, device connection management and data exchange using a shared memory area.
The second can be used for device discovery and configuration. It enables the user application to search for PN-IO devices in the local network and configure their PN-IO names. Further it is possible to read the current module and sub-module configuration.