Chapter 2 Introduction To Cx-Server Projects; Cx-Server Projects; Cx-Server Project Concepts - Omron CX-PROGRAMMER V9 Operation Manual

OMRON
CHAPTER 2
Introduction to CX-Server Projects
This chapter describes how data is identified within CX-Server projects (in terms of PLCs, points and groups). It
also describes the CX-Server functions available for the purposes of configuring PLCs and points within a CX-
Server project.

CX-Server Projects

CX-Server is a middleware package which allows other software to access OMRON automation devices (PLCs,
temperature controllers, Memory Card Writer and PROM Writer) through various connection types. In order to
co-ordinate these communications, it handles information detailing the PLC devices attached to the PC and the
information being accessed on each device.
Such information is held in a CX-Server project file with a .CDM extension. This file contains all of the
information about the PLCs, which CX-Server can connect to and the addresses of interest in each PLC which
may be accessed.
Each CX-Server project file is separate and is similar in concept to a document. CX-Server can deal with many
CX-Server project files at a time, although often only one CX-Server project is used by the client software at
any time.
A number of steps are involved in the setting up of a CX-Server project. At a high-level, these can be regarded
as:
♦ Identifying the PLCs which the PC is to communicate with;
♦ Identifying the addresses (points) within the PLC which are to be accessed during communications;
♦ Establish the type of network to be used.

CX-Server Project Concepts

CX-Server projects consist of PLCs, Connected Devices, Networks and Points. The following paragraphs
describe the of PLCs, Networks and Points into a CX-Server project and introduce the Project Editor. Specific
setup of PLCs and Networks are described in Chapter 3 - Communications.
PLCs
A CX-Server project file contains a list of PLCs which are (potentially) connected to the PC. These PLCs do not
really have to be connected unless communications with them are to occur.
Each PLC has the following attributes:
♦ Device Name. A unique name with the CX-Server project file so that the PLC can be easily referenced (for
example, 'PumpRoom1').
♦ Comment. A free-form long comment which is only used for information by the user that is attached to the
unique device name.
♦ Device Type. The PLC device type (for example, CV500).
♦ Connection Type. How to connect to the PLC and the address of the PLC on the chosen network (for
example, direct one-to-one connection or via a gateway PLC, one that is already defined in the CX-Server
project).
♦ Type Options. A list of options which may be present on the PLC (for example, the amount of user-
memory, clock, EM configuration and CPU type).
♦ Connection Options. A list of options which may be available on the chosen network (for example, the
speed of communication on SYSMAC WAY, Toolbus, Modem configuration, or Network or Node
configuration details).
A full description of the communications possibilities for C-series PLCs, CV-series PLCs and CS/CJ/CP-series
PLCs is provided in Chapter 3 - Communications. Host Link Port and Peripheral Port settings are made via the
PLC Setup Component, refer to PLC Tools User Manual Chapter 4 - PLC Setup Component. Once the network
has been defined and configured, it can be tested to ensure that messages are being transmitted correctly.
The PLCs selected also affect which other setup procedures need to be performed; for example, the CV-series
and CS/CJ/CP-series requires setting up the IO Table and using the PLC Setup Component to establish specific
PLC characteristics. In addition it is possible to set up to three levels of networks and to communicate with these
networks, the initial, direct connection must be to a PLC acting as a gateway. To ensure that messages from the
Revision 2.0
PART 3: CX-Server Runtime
CHAPTER 2 – Introduction to CX-Server Projects
CX-Server Runtime_Page 7