Running Upload - ABB 800xA User Manual

Running Upload

Node Structure
Alarm and events for objects not uploaded will be discarded in the subscriber
system. If alarms and events for actions related to nodes in the provider are wanted
the Node Administration structure should be uploaded to the subscriber. Navigate to
the Node Administration structure in the upload browser and select the node group
"All Nodes" in the provider. Include children and references and upload to the
Control Structure in the subscriber.
Composite Graphic
When uploading composite VBPG with references to instances in the Control
Structure, the objects must be uploaded explicitly to the control structure.
A large upload that involves deploy of several Visual Basic graphic aspects
continuously may cause a large memory usage, to avoid large memory usage, a
large upload should be divided into smaller parts; each part should not exceed
more than 4,000 graphic aspects.
Running Upload
Before an upload is started a complete consistency check should be performed in the
provider system on the objects configured to be uploaded. Consistency problem
may prevent a correct upload operation.
The performance of the provider and subscriber system will be affected during an
upload.
The upload reads the upload configuration and creates proxy objects in the
subscriber system for the objects and structures selected from the provider system.
The proxy objects are placed in the subscriber according to the specification in the
upload configuration.
The proxy objects created in the subscriber will get a new object identity (GUID).
This allows upload from several provider systems containing exactly the same
configuration. Aspects categories configured to be copied at upload, and all aspects
having OPC properties, Log configurations, and Log templates, not configured to be
ignored at upload, will be uploaded to the proxy objects.
46
Section 3 Configuration
3BSE037076-510 D