1. CS Workshop 2007 PCS 3.0 Upgrade by Stefan Götte

2. CS Workshop Feb. 1./2. 2007 2 The Upgrade we followed up the instructions given at the CS homepage: 1.adding new "data" connector at ProcCases 2.adding a few error boxes 3.changing some event calls 4.changing the GUIs with 2 persons, the upgrade* was done within 1,5 month … … including the installation of new DMS etc. working as "Brezelbacken" * same functionality as before

3. CS Workshop Feb. 1./2. 2007 3 Thanks for your attention. And now something completely different …

4. CS Workshop Feb. 1./2. 2007 4 The Architecture of a Control System Device Layer Application Layer controlled shared User Layer

5. CS Workshop Feb. 1./2. 2007 5 The PCS: Communication before version 3.0 AL Instance ProcCases ProcState DSC Int Proc Event Call (Instance@node) DL Instance Flag Up? Yes! Node of Child? None! Singleton Existing? Flag Up? No! Set Flag Up Register Tags SensorNew Value CmdActor Cmd ? Set Save State Actor

6. CS Workshop Feb. 1./2. 2007 6 The PCS: Communication before version 3.0 DL Instance DSC Int Proc Event Call (Instance@node) Node of Child? AL Instance ProcCases ProcState phpcxx Tagnames? Set Remote Controlled Tagnames Register Tags Sensor New Value CmdActor New Value Cmd SCRCmd ? SCRCmd Set Save StateActor

7. CS Workshop Feb. 1./2. 2007 7 The PCS: Communication before version 3.0 AL Instance ProcCases ProcState DL InstanceDSC Int Proc Event Call (Instance@node) Inform Cmd Sensor 1New Value 1 New Value 2 New Value 3 Sensor 2 Sensor 3 CmdActor Stop Remote Control Unregister Tags Pull Flag Down Set Save StateActor Set Save StateActor Calc State SCR

8. CS Workshop Feb. 1./2. 2007 8 Review of the PCS before version 3.0 singleton functionality via "in use Flag method" © distributed operation via "in use Flag method" © fixed starting procedure (first children, afterwards mothers) reduced existing check (only at start up) undefined situation if a child died during operation "stupid" children, therefore duplication of communication to enable mothers to calculate states quite large protocol at instantiation or destruction of an object bottleneck: data transfer (images) obviously historically grown and not really fitted to the problem Therefore …

9. CS Workshop Feb. 1./2. 2007 9 The renewed PCS 3.0 Event Call (Instance) DSC Int Proc DL Instance Sensor 1 CmdActor Set Save State Actor DIM Publisher DIM Receiver Publish Tags get Tags Publish Status Sensor 2 Sensor 3 Calc State no link no info Set Save State* *: to other instances

10. CS Workshop Feb. 1./2. 2007 10 The renewed PCS 3.0 Event Call (Instance) DIM PublisherDIM Receiver DL Instance DSC Int Proc AL Instance ProcCases ProcState Set Remote Controlled CmdActorCmd SCRCmd Set Save StateActor get Status Publish Status Cmd Actor Calc State SCR Stop Remote Control Set Save State Actor Set Save StateActor

11. CS Workshop Feb. 1./2. 2007 11 Review of the PCS 3.0 singleton functionality distributed operation eased within a "system" (node unimportant) complete existing check, no undefined situation anymore children clever, therefore no duplication of communication protocol at instantiation or destruction eased new protocol: classes get commands and publish services -> children do not know their mothers … changing all this took 3 to 4 month (not finished yet …) PCS features of old version were possible but absolutely nasty in 3.0 better performance (data transfer, …) most of these features would have been possible also in versions before 3.0 using the DSC engine … but not that elegant! which must know their children!

12. CS Workshop Feb. 1./2. 2007 12 What we learned today … 1.From a certain point of complexity, designing the communication protocol for instances (at different layers) is the most difficult task developing a control system. 2.For this the support of the ECSG is required! 3.It is great fun to use the PCS …

13. CS Workshop Feb. 1./2. 2007 13 Last words: What I like … a DIM service _condition for Base Process classes is available an Icon Generator is available (no idea where it is …) the DB Tool works proper the DMS Viewer is nicer than ever … the DMS Server / DMS Client eased my life a lot … HB wrote a quick and dirty Tag Extractor for me …

14. CS Workshop Feb. 1./2. 2007 14 Last words: … and what I need let's search for the Icon Generator, inspect it and add it to the tools the DB tool needs to indicate (and edit) the comment row of the data base the DMS Server needs "Shutdown all" functionality the Tag Extractor should be inspected, debugged, and added to the tools