wonderware ide 培训的手册文档第7章,共21章

Lab 7 –Configuring Change Control and PropagationIntroductionIn this lab, using the derivation hierarchy, you will control the changes made to derived objects by locking attributes. Additionally, you will use this feature to propagate the changes from templates to existing derived objects. This helps to establish standards in the Galaxy.ObjectivesUpon completion of this lab, you will be able to:Control changes to derived objects by locking attributesPropagate changes from templates to derived objectsLock the Attributes in $TankIn the following steps, you will lock attributes, which prevent changes to those attributes on derived objects. You will then observe that the changes have been propagated down the derivation hierarchy.1.Click on the Derivation tab to display the Derivation view.The derivation from the $UserDefined template to the Mixer_001instance is displayed.2.Double-click the $Tank template to display the configuration editor and ensure LT.PV is selected.3.In the Description field, enter Tank Level value.4.In the Engineering units field, change the value from Gallons to Liters.5.For both the Description and Engineering units attributes,click the lock icon.6.Expand the Enable I/O scaling area by clicking on the down arrow button.7.Next to the Scaling group, click the lock icon.This locks all of the attributes in this group.8.Click the lock icons to unlock the following attributes:EU value: MaximumEU range value: MaximumThis enables you to use this template for a variety of derived tanks where the maximum attributes differ depending on the tank type. These attributes can then be customized when derived objects are created.9.In the Field attributes list, click TT.PV.10.In the Description field,enter Tank Temperature value and lock the attribute.11.In the Engineering units field, change the value to Celsius and lock the attribute.12.In the Enable I/O scaling area, lock all of the attributes except for the maximum attributes, as donebefore, for the LT.PV field attribute.13.Save and close the configuration editor.14.In the Check In dialog box,Comment field,enter Locking attributes and click OK.The Check In dialog box appears.Notice the messages display that the $Mixer derived template and the Mixer_001instance were updated, because they are derived from the $Tank template.15.Click Close.In the Derivation view, notice the icon next to the Mixer_001instance showing that it requires redeployment for the changes to take effect. You will redeploy this instance later.Verify the Propagation to an InstanceNext, you will verify that the changes you made in the previous steps have propagated to the instance.16.Double-click on the Mixer_001instance to open the configuration editor.17.In the Inherited field attributes list, click on LT.PV and expand the Enable I/O scaling area.The previously locked attributes are now grayed out and cannot be changed, but the unlocked attributes can still be changed.18.Click on TT.PV to view that the same configuration applies to the locked and unlocked attributes.19.Click on the Close button to close the configuration editor.Lock the Attributes in $MixerNext, you will lock some of the attributes within the mixer template.20.Double-click the $Mixer template to open the configuration editor.21.In the Field attributes list, ensure TP1.Cmd is selected.22.In the Description field, enter Command to start/stop Transfer Pump1and lock the attribute.23.In the following field attributes, type the following descriptions and lock the attributes:All of the field attributes are now configured.24.In the Inherited field attributes area, click on LT.PV and expand the Enable I/O scaling group.25.Lock the Scaling Maximum values.26.Click on TT.PV and change the following attributes:EU value: Maximum450.0and lockedEU range value: Maximum455.0and locked27.Save and close the configuration editor.28.In the Comment field, enter Locking attributes and click OK.The Check In dialog box appears.Notice that the changes have propagated down the hierarchy structure to the Mixer_001instance.29.Click Close.Verify PropagationNext, you will verify that the changes have propagated to the instance.30.Open the Mixer_001configuration editor.31.In the Inherited field attributes list, click on each of the TP1.Cmd,TP1.PV,TP2.Cmd, and TP2.PVattributes to confirm that the descriptions are locked and cannot be edited.32.Click on the LT.PV and TT.PV attributes and expand the Enable I/O scaling group to confirm that thescaling maximum attributes have been locked.33.Close the configuration editor.Redeploy the Mixer InstanceNow, you will redeploy the instance to runtime.34.Right-click Mixer_001and select Deploy.35.Keep the default options and click OK.36.When the progress shows 100% completed, click Close.-This page intentionally left blank -。