System information

General Reference Guide IO Servers Configuration
RG-001-0-EN ver 1.5 eWON® - 20/03/2009 - ©ACT'L sa Page 85
5 The eWON IO Servers
5.1 Introduction
This introduction repeats some information already introduced in chapter “Tag definition: Introduction” on page 67.
An IO Server is the interface between a changing value and the eWON monitoring engine. It is a kind of driver. Any variable from any data source
must have a common representation for all IO Servers in order to define common interface in the eWON.
The data-source representation in the eWON uses 3 fields for the definition of a Tag:
• The IO Server Name
• The Topic name
• The Item Name
A Tag’s data-source will be uniquely identified with these 3 parameters:
Important note: For optimisation purpose, the eWON may disable the polling of “invalid tags” (See “IO Server Init” on page 86).
5.2 IO servers setup
Some of the IO servers are configurable.
The IO setup window proposes a list of IO servers:
Figure 71: eWON IO servers scrolling list
Click on the Edit hyper link or select another IO server to display its edition window.
There are 3 possible cases regarding the IO server configuration:
• The IO server is not configurable
• The IO server has a dedicated configuration page (ex: MODBUS, UNITE, NETMPI, DF1, ...)
• The IO server uses the standard IO server configuration page.
IO Server name:
Is a kind of driver name. For each IO Server there is a specific Topic Name and Item Name syntax.
Example: MODBUS, EWON, MEM
Topic Name:
Is used to group items inside an IO Server, for example the memory IO Server uses the blank topic
("") and the retentive topic ("ret"). All Tags of the MEM IO Server defined in the "ret" topic will have
their value saved and restored when the eWON boots.
All IO servers do not use a Topic Name. In that case the Topic Name field must be left empty.
Item Name:
The item name is a string of characters; its syntax is specific to each IO Server.
The Item Name describes the physical variable to monitor that uses the IO Server.
For example, the MODBUS IO Server needs to poll registers or coils from a slave, so it uses an item name representation to
define the register type, register address and slave address. (Example "40001,5" => Where 4 means "read write register",
0001 is the register number and 5 is the slave Modbus address).
Table 55: Tags data-source parameters