Professional Documents
Culture Documents
Reproduction,use or disclosure to third parties without express authority is strictly forbidden. ABB Automation GmbH; 2004
CONTENTS 1.GENERAL..............................................................................................................2 2.REFERENCES.......................................................................................................2 3.TERMINOLOGY.....................................................................................................2 4.THE FUNCTION OF THE TESTED ITEM..............................................................2 5.THE SCOPE OF THE TYPE TEST........................................................................3 6.PRODUCTION OF THE ITEM TO BE TESTED.....................................................3 7.TYPE TEST RESPONSIBLE AND APPROVAL....................................................3 8.TYPE TEST EQUIPMENT......................................................................................3 Hardware configuration...................................................................................3 Auxiliary software for the test..........................................................................3 9.THE TYPE TEST RECORD...................................................................................4 10.THE TYPE TEST PROCEDURES........................................................................4 10.1Start Setup.exe from Engineering Studio.......................................................4 10.2Topology Designer...........................................................................................6 10.3Function Designer with IO Allocation...........................................................16 10.4Function Designer Online Functions............................................................33 10.5Document Manager, Parameter Manager.....................................................44 10.6Bulk Data Manager.........................................................................................48 10.7Reuse Assistant..............................................................................................55 10.8Script Manager................................................................................................62 10.9Generic Functions..........................................................................................71 10.10Backwards compatibility and supported upgrade paths...........................74
Appr. Resp.dept.
11.04.20 05 Approved
Doc.kind Title
No. of p.
79
Page
Doc. no.
3BDS011247
en
1. GENERAL This document defines the procedures for the type test item Specific Functions and Workflows of Engineering Workplace Engineering Studio 4.1.0/0
2. REFERENCES The following documents are related to the items and to this document: Identity 3BDS011223R4101 3BDS011222R4101 3BSE034678R4101 3BSE036342R4101 3BDS011224R4101 3BDS011225R4001 Title Engineering Workplace Reference 800xA System Configuration 800xA System Installation 800xAUpgrade Function Designer Reference Topology Designer Reference
3. TERMINOLOGY The following terms and definitions are used in this document: Terms PPA CBM EP EB DM PM BDM SM RA TD FUD Definitions Process Portal A Control Builder M Engineering Platform Engineering Base Document Manager Parameter Manager Bulk Data Manager Script Manager Reuse Assistant Topology Designer Function Designer
4. THE FUNCTION OF THE TESTED ITEM The function of the tested item is to provide functions and workflows for Engineering Workplace Engineering Studio.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
5. THE SCOPE OF THE TYPE TEST The purpose of the type test is to verify that the product runs in combination with other System Extensions within Industrial IT 800xA System Configuration.
6. PRODUCTION OF THE ITEM TO BE TESTED The item to be tested shall be produced in a similar way as in normal production. 7. TYPE TEST RESPONSIBLE AND APPROVAL The project manager and DEAPR/LQ shall approve the type test record.
8. TYPE TEST EQUIPMENT Hardware configuration The following hardware configuration shall be used for the type test: PC equipped with - at least 1 GB RAM - at least 20Gbyte hard disk - access to LAN and Printer Auxiliary software for the test The following auxiliary software shall be used for the test (see 3BSE034678R101 - 800xA System Installation): Process Portal A Control Builder Soft Controller AC800M OPC Server MDAC hotfix Q823490 Engineering Studio including: Engineering Base Document Manager Parameter Manager Bulk Data Manager Function Designer Topology Designer Reuse Assistant Script Manager Service Pack MS SQL Server Desktop Engine 8.00.761
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
9. THE TYPE TEST RECORD The type test record is 3BDS011247_C-TTR Short Type Test Engineering Studio_400.doc The following files/documents are necessary and are inside subfolder Data: - Create Control Structure.xls - Create Functional Structure.xls - Document Scrap 'Document_AspectN...' - Handel Function Diagrams with BDM.doc - ExampleForScriptManager.afw - Test2.doc - Import.bat - 1_Object_Type_Structure_Demo.afw - 2_Reuse_Design_Structure_Generic_Drive_System.afw
10. THE TYPE TEST PROCEDURES Install Product and load System Extensions
10.1
Start Setup.exe from Engineering Studio Select item Customized MSSQL 2000 Desktop >> press button Exit select item Engineering Base >> press button Exit >> select Complete installation select item Function Designer >> press button Exit >> select Complete installation select item Reuse Assistant >> press button Exit >> select Complete installation select item Script Manager >> press button Exit >> select Complete installation
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
1. Start Configuration Wizard >> select System Administration >> button Next >> select System >> button Next >> select System Extension Load >> button Next >> Tab Applications Select Engineering Base >> press button arrow-right (>) select DM & PM Application >> press button arrow-right (>) select AC800M Connect >> press button arrow-right (>) select AC800M Signal Extension >> press button arrow-right (>) select Reuse Assistant >> press button arrow-right (>) select Topology Designer >> press button arrow-right (>) select Topology Designer for >> press button arrow-right (>) select Function Designer >> press button arrow-right (>) select Function Designer for (AC800M Connect) >> press button arrow-right (>) Result:
Press button Next >> press button Finish. Wait while system extensions are being loaded.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
10.2 1.
Select Control Structure, right click on Root, Domain and select New Object.
Result:
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
Result:
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
5. Save contents of the sheet Bulk Data Manager Save If an error occurs create the Control Structure manually. Result:
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
7. Open Topology Aspect in Diagram view and select File New Select Skeleton > AC 800M Single
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
10
Result:
8. Repeat Step 6 7 for Object ControllerM2 9. Select Object ControllerS1 right click Diagram Result:
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
11
10. Open Topology Aspect in Diagram view and select Blank template Result:
Save and close the Diagram view 11. Select Root Object in Control Structure and add new Topology Aspect Result:
12. Open Topology Aspect in Diagram view and select skeleton Control Network
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
12
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
13
Result:
Move the Objects to the network symbols. There is a snapping mechanism, which fetches the Objects.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
14
Result:
13. Select Object ControllerM2 in Diagram view and right mouse click Go to Child Diagram. ?
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
15
Result:
10.3
Build Functional Structure and create a control loop and allocate hardware IO. 1. Select the aspect Project at the object Project1x in Control Structure Right mouse click on aspect Config View. Insert libraries according picture below.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
16
2. Select Aspect Application on Object Application1 in Control Structure right mouse click on aspect Config View. Connect libraries according picture below.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
17
3. Open Bulk Data sheet Create Functional Structure.xls Change path in line 7 (which Lib is loaded ProcessObjExtLib 1\0\-0 or 2\0\-0) e.g. [Direct][Object Type Structure]Object Types.Control System.AC800M/C Connect.Libraries.ProcessObjExtLib 2\0\-0.Control Module Types. UniM.Control Structure.UniM
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
18
5. Save contents of the sheet Bulk Data Manager Save If an error occurs create the Functional Structure manually. Result:
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
19
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
20
Result:
8. Select Insert Symbol and add Function Block SinGen (Object Type Structure Object Type Control System AC800 M/C Connect Libraries Group BasicLib1.3\1 Function Block Types SinGen,Function Block Types)
9. Select the Symbol SinGen right mouse click Aspect Properties ? Change the Name to LevelControl1SinGen1
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
21
10. Select Insert Symbol and add Function Block ABS (real)
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
22
11. Show the hidden ports select the function block right mouse click Show hidden ports select ports to show according to diagram picture below
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
23
Result:
13. Select object LevelControl1 Right mouse click Allocatable Group. Allocate to Application _1
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
24
Result:
3BDS011247
en
25
14. Select object LevelControl1 Right mouse click Allocatable Group Generate Configuration Data
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
26
Result:
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
27
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
28
Result:
16. Go to Functional Structure and drag and drop object LevelControl1 into IO Allocation right window. All signals below will be shown.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
29
Result:
17. Select all signals and drag and drop it to the Boards on the left side of the IO Allocation window. The signals will be allocated into the Control Structure blow the appropriated boards. Result:
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
30
18. Select in IO Allocation window Option Automatic Write Allocation into CBM. Answer the IO Allocation question with yes. IO signal information will be updated into CBM. Check result in CBM Hardware editor. The boards should be locked (Read-only) form IO Allocation.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
31
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
32
10.4
1. Connect Application to Soft Controller. In Control Structure select object Application_1 and Press CRT + Shift, Move with the mouse the object Application below object ControllerS1. Remark: If this is not working, go to Control Builder select Connected Application below ControllerS1 and connect the Application_1.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
33
2. Go to Control Builder and select Application_1 Right mouse click Task Connection. Connect to ControllerS1.Fast
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
34
3. Select ControlerS1 in the Control Builder right mouse click System Identity.
Enter the IP address <IPAddres:2> of your computer. You can get it by enter command ipconfig in the DOS box and set Simulate Hardware.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
35
For ControllerM1 and Controller M2 fill in different System Identities. 4. Go to Control Structure and select object ControlNetwork11 and aspect OPC Data Source Definition. Configures the service group according your Service Provider. Result:
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
36
Start the OPC Server with the shortcut icon on the desktop. Enter the IP address <IPAddress:2> of your computer. If the connection is successful you will get following picture. Result:
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
37
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
38
Result:
7. Open the Function aspect on object LevelControl1 in the Diagram view. Select the ABS symbol right mouse click Add to Display List. Repeat this action for PidSimpleCC and ThreePosCC. Select Online Subscribe for Life Data in the Function Designer. You will get online values on your diagram.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
39
Result:
8. Select LC1AInCC2 right mouse click MainFacePlate Force the output with 50.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
40
10. Select LevelControl1TPosCC1 right mouse click MainFacePlate Open the max dialogue.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
41
11. Navigate to Control Builder and MainFacePlates to see more details and change values
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
42
Example:
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
43
10.5
1. Create generic object in the Functional Structure below Root DM_PM_Test Create new Document aspect with the name TagSheet within the DM_PM_Test object.
2. Create new Parameter aspect of the category TagData within the DM_PM_Test object.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
44
Result:
3. Select Document aspect TagSheet Right mouse click Set file and Select File Template.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
45
5. Modify in the document the cells Pressure Min, Norm, Max, Unit.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
46
6. Open the TagData in the Preview window and check the result.
7. Modify the S_TempMin, S_TempNorm, S_TempMax, S_TempUnit in the preview window of the TagData.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
47
8. Check result in TagSheet document. Close the document and open it again or Bulk Data Manager Update all 9. Open the TagSheet new or use command Bulk Data Manager Update all
10.6
1. Select an object in the Functional Structure right mouse click Advanced Bulk Data Manager. The Bulk Data Manager based on Excel will be opened.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
48
Result:
3. Select a Functional Structure aspect and Drag & Drop it into the Excel sheet. Press ok on Configure Properties.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
49
Result:
4. Select the Document Aspect TagSheet in the Object DM_PM_Test and Drag & Drop it into the Excel sheet. From the Configure Properties select ApprDat, ApprName, ChkDept, ChkName.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
50
Result:
5. Select the Parameter Aspect TagData on the object DM_PM_Test and Drag & Drop it into the Excel sheet. From the Configure Properties select A_TempMax, A_TempMin, A_TempNorm, A_TempUnit.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
51
Result:
6. Select the object DM_PM_Test and Drag & Drop it into the Excel sheet. The properties according the Bulk Data Sheet will be read from the Plant Explorer.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
52
Result:
7. Modify the Properties and save it back to the Plant Explorer Bulk Data Manager Save (Document.AspectName in E1 is no not enough now Document Manager Documents/ Document.AspectName)
8. Open the TagSheet aspect in the preview area on the object DM_PM_Test and check result.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
53
Result:
9. Open the TagData aspect in the preview area on the object DM_PM_Test and check the result.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
54
Result:
10.7
Reuse Assistant
1. Open file Import.bat Object Type group Demo will be loaded into the Object Type Structure Reuse instruction will be loaded into the Reuse Design Structure. 2. Create a generic Object in the Functional Structure MyReuseInstruction and below a Object DriveSystem1 of the Object Type Generic Drive System2 Object Type Structure Demo
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
55
Result:
3. Select the aspect ReuseAssistentBuilder on the object DriveSystem1 and open the WizardView.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
56
Result:
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
57
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
58
5. If the questions complete the wizard jumps to the beginning. Press Execute. Check the result.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
59
Result:
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
60
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
61
10.8
Script Manager
1. Load with Import/Export tool the file ExampleForScriptManager.afw, Action Import All
Result:
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
62
2. Create new aspects ArticleData below LevelControl1UniM1, LevelControl1DIS1, LevelControl1DIS2, LevelControl1DOS1 and LevelControl1DOS2
4. Output of the parts list. Select the aspect PartsList below LevelControl1, Single Control Module Type. Right click View Document Result:
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
63
5. Print the parts list. Select the aspect SimulationForScript below LevelControl1, Single Control Module Type. Right click Main View PrintOnEvent True - Apply
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
64
6. Signal trace function (SoftController online). Select the aspect SimulationForScript below LevelControl1, Single Control Module Type. Right click Main View Fault True - Apply
Result:
7. Create new aspect script with the name script_MBox within the DM_PM_Test object.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
65
Result:
8. Select Script_Mbox, all menu entries and tool bar buttons are enabled Result:
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
66
Input=inputbox("Read(2) or Write(1)") if input = 2 then ReadNow end if if input = 1 then WriteNow end if sub Hallo2() msgbox "Hallo2" end sub sub WriteNow writedata "Hallo1",2 msgbox "written" end sub sub ReadNow Dim x x = readdata("Hallo1") msgbox "readed" end sub Result:
10. Set Trigger in Dialog Tools Script Options Trigger Conditions Aspect Change to the aspect name
Doc. no. Lang. Rev. ind. Page
3BDS011247
en
67
11. Enable all menu verbs in Dialog Tools Script Options Trigger Conditions Menu Verbs ObjectVerb
3BDS011247
en
68
first press Cancel or > 2 no massage box enter 1 massage box written should pop up enter 2 - massage box readed should pop up
13. Save the Word document test2.doc into the root C: Create new aspect script with the name script_Doc within the DM_PM_Test object, see point 1 14. Select Script_Doc, all menu entries and tool bar buttons are enabled and add the following code in the script editor: dim MyApp set MyApp = CreateObject("Word.Application") MyApp.Documents.Open("C:\Test2.doc") MyApp.Visible = True Dim MySelection set MySelection = MyApp.Selection 'MySelection.TypeText("Na so was 2!") Result:
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
69
15. Set Trigger in Dialog Tools Script Options Trigger Conditions Aspect Change to the aspect name. Result:
16. Select aspect TagData, change something, Word starts and shows the document test2
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
70
10.9
Generic Functions Open Import Export tool via Plant Explorer Explorer. Drag & Drop the objects DM_PM_Test, LevelControl1and MyReuseInstruction from the Functional Structures into the Import Export tool with dependencies. Result:
Save the file with the name Export_FunctionalStructure_With_Dependencies.afw Open Import Export tool via Plant Explorer Explorer. Drag & Drop the objects DM_PM_Test, LevelControl1and MyReuseInstruction from the Functional Structures into the Import Export tool without dependencies.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
71
Result:
2. Save the file with the name Export_FunctionalStructure.afw Open Import Export tool via Plant Explorer Explorer. From the Control Structure Drag & Drop the objects Applications and Controllers into the Import Export tool without dependencies.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
72
Result:
Save the file with the name Export_ControlStructure.afw 3. Cut and Paste Copy in Functional Structure the object DM_PM_Test paste it and rename the new object. Check the result. Copy the TagSheet document aspect and the TagData aspect and paste into another object. Check result. Copy in Functional Structure the object LevelControl1 paste it and rename the new object. Check the result in the Functional Structure, Control Structure and Control Builder. 4. Delete Delete object DM_PM_Test in the Functional Structure. Result: The objects and his aspects have to be deleted. Delete object LevelControl1 in the Functional and Control Structure. Delete all Signal Objects in the Control Structure below ControllerS1 IO boards. Result: All objects and the aspects from the LevelControl1 have to be deleted. Delete object MyReuseInstruction in the Functional Structure. Delete also the object DrvSystem12_Motor in the Control Structure below Unallocated_Inst_App object. Result: All objects and aspects from the MyReuseInstruction have to be deleted 5. Import with Dependencies
Doc. no. Lang. Rev. ind. Page
3BDS011247
en
73
Import the Export done in chapter 10.9.1 step 1 (export with dependencies) Import the Export done in chapter 10.9.1 step 3 (export without dependencies) Import the Export done in chapter 10.9.1 step 5 (export without dependencies)
10.10
Document Aspect see Topology Aspect(s) below One Property Transfer Aspect Create a generic object (AesPropertyTransferTest) on root level of the Functional Structure. Add an AesPropertyTransfer aspect and an ArticleData aspect to it. Configure the AesPropertyTransfer aspect as: source aspect : ArticleData, Source Property: Description target aspect : Name, target Property: Description Enter string "testTransfer" for property "Description" on aspect ArticleData. Press the button "TransferNow" in the AesPropertyTransfer aspect and verify that the string "testTransfer" arrives at Name:Description Topology Aspect(s) Load System extensions "Topology Designer" and "Topology Designer for AC800M" select Control Structure goto Root \ Control Network 1 \ Project1 \ Controllers \ PM1_11AC03 Open Topology Aspect in Preview area -> CPU component shown Select Diagram view File \ New with Skeleton "AC800M PB FF Single" If Topology components ( i.e. IO-Modules, CI840 ) are not snapped, use CTR.SHIFT.S If Topology components ( i.e. IO-Modules, CI840 ) still are not snapped, connect manually Do the same ( create Topology diagrams ) for all other controllers too Create Topology aspect on Controllers Open Diagram view, File / New with Skeleton "Control Network" Snap three of the controllers to the bottom connections of the Control Network Create a Document aspect with name "Topology Diagram Document" Fill in Title1, Title2, PrepDate and Owner
One new generic Object with a Script Aspect, the Script shall contain the following statement msgbox I am Compatible! and shall be executed e.g. via Aspect menu
Doc. no. Lang. Rev. ind. Page
3BDS011247
en
74
One new Reuse Instruction, which creates one generic Object with Name "I am compatible" in Location Structure, from this a RI-Type is generated, from this a Reuse Instruction is generated in the Locations Structure and then executed, result must be the created object "I am compatible Then a new Backup has to be created !
Remark: All listed System Extensions except AC800M Connect Data Upgrade have to be installed. b. Restore the data from the Backup.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
75
Result: Verify that the Aspects described on the page before are working as described there. Open Function Aspect of Functional Structure\Root\1 PM1\10 Allgemein\10A Allgemein\_10AC001 Verify that the diagram looks like the figure below.
Verify that SignalInformation and SignalParameter of underlying \_10AC001_TM03_ object look like the 2 figures below.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
76
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
77
2. Restore a Backup generated with SV 4.0 The Backup of the item above has to be restored in a SV40 System and then rebackuped (this has to be done only one time in life, as long as the backup-files dont get lost). Perform the same actions and check the same results for the rebackuped Backup as in 1. Restore a Backup generated with SV 3.1 above. 3. Upgrade System generated with SV 2.1
The following has to be done once on the SB2.1 Test-PC. Create a new System and extend it by the following items Document Aspect Create a generic Aspect Object DM_Test Create a Document aspect with name "DM_Test Document" Fill in Title1, Title2, PrepDate and Owner Set a File for the Document, use a Word template Parameter Aspect Create a generic Aspect Object PM_Test with an article Aspect Create a ArticleData aspect with name "PM_Test" Fill in some data into the properties category and article One Property Transfer Aspect Create a generic object (AesPropertyTransferTest) on root level of the Functional Structure. Add an AesPropertyTransfer aspect and an ArticleData aspect to it. Configure the AesPropertyTransfer aspect as: source aspect : ArticleData, Source Property: Description target aspect : Name, target Property: Description Enter string "testTransfer" for property "Description" on aspect ArticleData. Press the button "TransferNow" in the AesPropertyTransfer aspect and verify that the string "testTransfer" arrives at Name:Description
One new generic Object with a Script Aspect, the Script shall contain the following statement msgbox I am Compatible! and shall be executed e.g. via Aspect menu
One new Reuse Instruction, which creates one generic Object with Name "I am compatible" in Location Structure, from this a RI-Type is generated, from this a Reuse Instruction is generated in the Locations Structure and then executed, result must be the created object "I am compatible
Then upgrade this system to SV41 according to upgrade instructions SV41 and check the Aspect Objects and Aspects in the upgraded system.
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
78
REVISION Rev. ind. A B Page (P) Description Chapt. (C) All 10.2 / 9. 10.3 / 3. 10.3 / 8 All All General Show Topology Aspect Change path Path description Test for Version SP1 Test for Version 800xA 4.1.0/0 Approved version Review/Approval chapter deleted, as separate review record exists Title changed Adaptation for SV 3.1 SP2 Adaptation for SV 4.1 Approved version Date Dept./Init. 10.10.03, WBo 11-01-03,WBo
C Dd1 D
E Fd1 F
Doc. no.
Lang.
Rev. ind.
Page
3BDS011247
en
79