eWON General Reference Guide - eWON wiki

3.4 Tag Setup
3.4.1 Tag definition: Introduction
The eWON Monitoring Web Interface features are based on:
• The configurable monitoring of Tags
• The execution of scripts
General Reference Guide eWON Configuration
All the variables monitored by the eWON are defined as "Tags". A Tag is a value changing with time and coming from a data-source.
Typical data-sources are:
• eWON internal Inputs/Outputs
• Remote Inputs/Outputs (modbus, UnitelWay, DF1, MPI, ...)
• eWON memory Inputs/Outputs (updated by script)
The data source is called an "IO Server". An IO Server is the interface between the 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.
IO Server name
Topic Name
Item Name
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).
A description of the different IO Server syntax is given in chapter "The eWON IO Servers" on page 94. Once a Tag is configured with its Server
Name, Topic Name and Item Name, it is given a Tag name that will be used everywhere in the eWON.
3.4.1.1 DataType of Tags
Internally, all Tags are stored on 4 bytes and represent:
• a single precision FLOATING POINT format (IEEE float representation)
• a DWORD, an unsigned 32 bits integer
• an INTEGER, a signed 32 bits integer
• a BOOLEAN, a binary value
In addition, an Automatic choice is provided to let eWON store the value of the
tag in the best of the above DataTypes (depending of the IOServer register/
modifier type).
Is a kind of driver name. For each IO Server there is a specific Topic Name and Item Name
syntax. The following drivers are available: MODBUS, EWON, MEM, NETMPI, UNITE
(Unitelway), DF1, FINS, S7 3&400(MPI), S7 200(PPI) and S5-AS511.
Is used to group items inside an IO Server, for example the memory an IO Server uses the
blank topic ("") and the retentive topic ("ret"). All the Tags of the MEM IO Server defined in the
"ret" topic will have their value saved and restored when the eWON boots. All the IO servers
do not use Topic Name. In that case Topic Name must be empty.
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 using the IO Server.
Table 48: Tag’s data-source parameters
The DWORD and INTEGER types are available only since firmware 6.0.
Before firmware 6.0, all the tags were stored in single precision FLOAT format (IEEE float representation), and only 2 types were available
(Analog and Boolean). This means that you can only expect a maximum precision of 7 decimal digits.
That’s why, before Firmware6.0, the 32 bits Integer data read by an IOServer were automatically converted in the nearest float number
representation.
For a huge number, it will mean a truncation (ex: integer value 1600000015 will be stored as float 1600000000.0).
RG-001-0-EN ver 1.14 eWON® - 02/05/2012 - ©eWON sa Page 75