Machine Edition View Data Collector

Machine Edition View Data Collector
Table Of Contents
Machine Edition View Data Collector.......................................................................................................................5
System Requirements (Machine Edition View Data Collector) ....................................................................................5
Enabling the Machine Edition View Data Collector .....................................................................................................7
To add the Machine Edition View Data Collector to a Machine Edition project: ................................................7
Configuration Tab for the Machine Edition View Data Collector.................................................................................8
Summary of the Machine Edition View Data Collector Features..................................................................................9
Configuring Tags for Collection (Machine Edition View Data Collector)..................................................................11
Supported Data Types (Machine Edition View Data Collector) .................................................................................12
Understanding Qualities (Machine Edition View Data Collector) ..............................................................................13
Understanding Time Stamps (Machine Edition View Data Collector)........................................................................14
Machine Edition View Data Collector Implementation Guidelines ............................................................................15
Collecting from multiple Machine Edition Projects................................................................................................15
Polled and Unsolicited Collection...........................................................................................................................15
High Compression Rates with Repeated Bad Quality.............................................................................................15
Performance issues..................................................................................................................................................15
QuickPanel View/Control storage space considerations .........................................................................................17
Index ............................................................................................................................................................................17
iii

The Machine Edition View Data Collector allows for efficient communication between Historian 2.0 and above
and Machine Edition 5.0 or greater. Once installed, the Machine Edition View Data Collector allows you to
collect thousands of point attributes and values per second from a running Machine Edition project.
The Machine Edition View Data Collector is installed with Machine Edition and is available to Historian when
enabled in a Machine Edition project.
For more information on the Machine Edition View Data Collector, refer to the following topics:
System Requirements (Machine Edition Collector)
Enabling the Machine Edition View Data Collector
Summary of the Machine Edition View Data Collector Features
Configuration Tab for the Machine Edition View Data Collector
Configuring Tags for Collection (Machine Edition View Data Collector)
Supported Data Types (Machine Edition Collector)
Understanding Qualities (Machine Edition View Data Collector)
Understanding Timestamps (Machine Edition View Data Collector)
Machine Edition View Data Collector Implementation Guidelines
System Requirements (Machine Edition View

Data Collector)
The following software is required to use the Machine Edition View Data Collector:
Machine Edition 5.0 or greater is required for use with Windows NT targets
Machine Edition 5.0 SP2 or greater is required for QuickPanel View/Control models.
Historian 3.0 or greater is required for use with QuickPanel View/Control targets.
Historian 2.0 or greater with the following SIMs installed is required for use with Windows
NT targets:
Historian iH20_291501 SIM (iHistorian:General)
Historian iH20_286551 SIM (CIMPLICITY HMI Data Collector)
NOTE: The View Collector is supported only on Windows NT, Intermediate QuickPanel View/Control, and
Loaded QuickPanel View/Control target
Index
Enabling the Machine Edition View Data

Collector
The Machine Edition View Data Collector is installed with Machine Edition View. The collector will start and
stop automatically when the associated project is started and stopped. Refer to the Machine Edition
documentation for more information.
To add the Machine Edition View Data Collector to a Machine Edition project:
1.
Go to the Logging Groups node in View Target.
2.
Select Historian as the logging type in the Property Inspector
3.
Set the server name in the Server Name property.
4.
Download and start the Machine Edition Machine Edition project.
The next time you start Historian, the collector and its status will be shown on the Main screen. To configure
the collector, go to the Collectors Maintenance screen. The collector's name will consist of the computer name,
the project name, and the target name, with a suffix of "CME" appended. For example, the collector for a
project named MyProject will appear as:
MEDev1_MyProject_TargetName_CME
If you rename your Machine Edition project after configuring the Machine Edition data collector in Historian, it
will automatically start using the new project name. Historian will not update the tag database to the new
interface, however. In order to continue collecting data from the Machine Edition project, you will need to edit
the Collector Name property of the tags in the Historian tag database to match the new interface name.
Configuration Tab for the Machine Edition View

Data Collector
There is no collector-specific configuration for the Machine Edition View Data Collector in Historian. Refer to
the Machine Edition help for more information on configuring the Machine Edition data collector.
Index
Summary of the Machine Edition View Data

Collector Features
The following table outlines the features of the Machine Edition View Data Collector.
Feature
Capability
Browse Source For Tags
Yes
Browse Source For Tag Attributes
No
Polled Collection
Yes
Minimum Poll Interval
100 ms
Unsolicited Collection
Yes
Timestamp Resolution
milliseconds or seconds
Accept Device Timestamps
No
Floating Point Data
Yes
Integer Data
Yes
String Data
Yes
Binary Data
No
Array Data
No
10
Index
Configuring Tags for Collection (Machine

Edition View Data Collector)
You can specify tags for collection in Historian Administrator by browsing the collector, or adding tags
manually.
The following table outlines the tag attributes available when browsing:
Historian Tag Browse Attribute
Machine Edition Variable Property
Source Address
Variable Name
Description
Description
The browse will show only tags with supported data types. For more information on supported data types, see
Supported Data Types (Machine Edition Collector).
Historian will show only tags contained within the master copy of the Machine Edition project. When entering
tags manually, it is important to match the Historian tag data type with the data type of the Machine Edition
variable data type.
11
Supported Data Types (Machine Edition View

Data Collector)
The following table maps Machine Edition Point Map data types to their Historian Data Type equivalents:
12
Machine Edition Variable Data Type
Recommended Historian Data Type
BOOL, LREAL
Double Float
DINT
Double Int ( 4 bytes signed )
STRING
Variable String
Index
Understanding Qualities (Machine Edition View

Data Collector)
The following table maps Machine Edition Qualities to Historian Qualities:
Machine Edition QUALITY Attribute Value
Historian Quality, Subquality stored
Valid
Good, ihOPCNonSpecific
Invalid
Bad, ihOPCNonspecific
Invalid-PLC Error
Invalid-Network Error
Invalid-Remote
When repeated bad quality data samples for a tag are received, the Machine Edition data collector will show a
high compression rate, even with collector compression disabled. Historian will only store the first bad quality
sample. The remaining bad quality samples will be dropped.
13
Understanding Time Stamps (Machine Edition

View Data Collector)
Time stamps are determined by local time on the server the Machine Edition View data collector is connected
to.
14
Index

Implementation Guidelines
Collecting from multiple Machine Edition Projects
The Machine Edition View Data Collector for Historian can be configured to run only on the same workstation
as the Machine Edition project it is collecting from. A collector can only collect from a single project.
Polled and Unsolicited Collection

Polled collection is useful only if you need a raw sample stored periodically. The value stored will be the last
value reported to the collector by the Machine Edition View runtime.
Unsolicited collection is recommended over polled collection, as the Machine Edition View Data Collector will
only receive new data when a variable has changed on the Machine Edition project (for example, when a new
value has been received, or a property of the variable has changed).
In unsolicited collection, any change to a Machine Edition variable will cause data to be collected.
The Historian tag collection interval is not used by unsolicited collection. Any time data is reported from the
Machine Edition View runtime to the collector, the collector passes this information to the Historian server,
even if the rate is faster than the collection interval of the tag.
High Compression Rates with Repeated Bad Quality

When repeated bad quality samples for a tag are received from the View runtime, the Machine Edition View
Data Collector will show a high collector compression rate, even with collector compression disabled. The
repeated bad samples for a tag are compressed out by the collector and not reported to the Historian server.
Performance issues
The View Historian Collector runs as a separate process on the HMI target. Therefore, overall performance of
the HMI may decrease when using the Collector, especially if you are logging large amounts of data. In extreme
cases, this can cause loss of logged data.
When configuring the Collector, it is recommended that you use Unsolicited data instead of Polled data. When
15
using Polled data, the Collector continually polls View Runtime for new data values at the specified Historian
tag collection interval. When using Unsolicited data, the Collector will receive new data only when the variable
has changed in the Machine Edition project.
The following table lists the typical maximum number of variable retrievals per second that you can log before
performance significantly degrades.
Target
Type of Logged
Data
Data Type
Limit on variable
retrievals per
second
Windows NT
Polled Data
LREAL, BOOL, DINT
3000
STRING (5 characters)
1000
LREAL, BOOL, DINT
8000
2000
LREAL, BOOL, DINT
50
20
LREAL, BOOL, DINT
900
150
Unsolicited Data
QuickPanel
View/Control
Polled Data
Unsolicited Data
NOTE: Limits in this table are estimated values for illustrative purposes only. The exact maximum number of
variables that can be logged per second depends on many factors, such as the size of the HMI project, the
amount of memory on the workstation, the speed of the network, and the number of scripts or operations being
executed by View Runtime at any one time.
When using unsolicited data, logged data is sent by the collector in "bursts". That is, many logged variable
changes may be sent in the same transmission. Only variables whose value has changed are included in this
transmission. This means that you can log values for many more variables than the limit indicated in the table,
as long as the number of variables that change per second does not exceed that limit.
When using polled data, the collector sends the variable's value regardless of whether or not it has changed.
This means that the limit indicated in the table is effectively a limit on the number of variables you should log
16
Index
per second.
QuickPanel View/Control storage space considerations

Memory and disk space on a QuickPanel View/Control target is very limited. When logging data to the
Historian Collector, keep in mind the limitations of your target hardware.
When browsing for variables to log in the Historian Collector, the entire variable list for the project is stored in
memory. While browsing, each variable uses approximately 100 bytes of memory while transferring data to and
from the logged list. Before configuring the Historian Collector, ensure that the target unit has enough memory
to browse all variables in the application's variable list.
The Store and Forward feature is a backup mechanism to prevent the loss of logged data when the connection to
the Historian server is lost. If the Historian Collector is disconnected from the Historian server, data is
temporarily stored in a local directory on the target. When the connection is restored, all temporarily logged
data is sent to the collector, the logged data is erased, and logging continues as before.
When the Store and Forward feature is used, each logged data item requires storage space both in volatile
memory and on disk (non-volatile memory). Therefore, when configuring the Store And Forward Buffer Size
and Minimum Disk Free Space properties, ensure that you have enough storage space to store the desired
amount of logged data should the connection to the Historian Collector be lost. Each variable change consumes
the following storage space:
1 byte per character in the variable's name.

Several bytes for the variable's new value (4 bytes for LREAL/BOOL/DINT; the Max Length of the
variable for STRING data).
8 bytes of overhead (for timestamp and data quality information).
In addition to space for variables (either for browsing or for the Store and Forward feature), the Historian
Collector itself consumes between 2 and 3 MB of program memory.
Index
C
Machine Edition Data Collector ............................7
collectors
Machine Edition ....................................................5
configuration
D
data collectors
Machine Edition ....................................................5
17
supported data types ............................................11
features
understanding qualities ........................................12
understanding timestamps ...................................13
Machine Edition Data Collector ................................5
Machine Edition Data Collector
features ..................................................................8
implementation guidelines...................................14
overview ................................................................5
18
summary of features

Machine Edition View Data Collector

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Machine Edition View Data Collector

Încărcat de

Drepturi de autor:

Formate disponibile

Machine Edition View Data Collector