eation of an instance of process DLC in block DLCa: stop if create DLCa!DLC Automatic Observation of Simulations 139 To detect the death of any process instance: stop if stop To detect the call of any procedure: stop if call To detect the call of procedure CRCok in instance 1 of process DLC located in block DLCb: stop if is active (DLCa!DLC (1) ) and call DLCb!DLC (1) ! CRCok As you can see, any event or combinations of events in the SDL model can be detected by stop conditions during the simulation. However, stop conditions cannot detect the correct sequencing of signals: for that, you must use MSCs. 5.3.2 Simulate with a basic MSC You will simulate the V.76 SDL model, observed by a basic MSC. Basic means that the MSC contains a single scenario, as opposed to a hierarchy of scenarios linked by temporal operators (such as AND, OR, REPEAT.. To simplify, we reuse the basic MSC testl.msc, generated by the Simulator in Chapter 4. Naturally, you could use another MSC drawn from scratch with the Editor, or rework an existing MSC. 5.3.2.1 Compile the SDL model plus the MSC A. In the SDL Editor, load the V.76 SDL model plus the MSC testl.msc (generated in Section 4.3.2.4). B. Unload any other files from the SDL Editor. C. Quit (do NOT minimize) the ObjectGeode Launcher if running. D. In the SDL Editor, select Tools > SDL & MSC Simulator. The window represented in Figure 5.42 appears. X v76.ogl ObjectGeode Launcher File Edit View Insert Build Options SDL & MSC Simulator Working directory (Default) : F:ADONNEES\TRANSMET\livreSimul\models0GW76 v76.pr test1.msc Build Ready Figure 5.42 The ObjectGeode Launcher with an MSC 140 Validation of Communications Systems with SDL E. Check that the left area only contains v76.pr and testl.msc, as in Figure 5.42, otherwise select any file to remove and do Edit > Remove. F. Select File > Save to save the current settings in the file v76.ogl in your current directory (feature not available in the Unix version). G. Press the Build button: this checks your SDL model and the MSC, as shown in