robe DLC_a v76test!DLCa; This creates the probe DLC pointing toward the block DLCa in the SDL system v76test. The observer obs1 will use this probe to access the contents of the block. F. Double-click on obs1 the Editor opens the observer obs1, empty. G. Enter the observer shown in Figure 5.75, and save it. An observer is similar to an SDL process, except that: the transitions are not triggered by incoming signals but by the events occurring in the SDL model (WHEN), the ERROR and SUCCESS states must be defined to indicate to the Simulator which states are expected and which are unexpected. observer obs1 wait4conf it:= INPUT L_EstabReq TO DLC a it:= OUTPUT L_EstabConf FROM DLC_ a We store the After the output, DLC_num := it L_EstabReq ! p1 we check that parameter of it ! L EstabConf ! p1 L_EstabReq the parameter into DLC_num of L EstabConf is the same than DLC_num) the parameter Now we wait SUCCESS STATE ok; wait4conf for L EstabConf of L _EstabReq ERROR STATE bad; DLC_num Integer; Figure 5.75 The GOAL observer obs1 In Figure 5.75, the self-declared variable it is used like a hook to memorize the INPUT or the OUTPUT in order to access the parameter of the signals. The first WHEN could be translated as: when an input of signal L_EstabReq to probe DLC_a is observed, execute the transition until state wait4conf. 5.3.5.2 Compile the SDL model plus the GOAL observer A. In the SDL Editor, load the V.76 SDL model, plus the GOAL observer contained in obs_ex2.obs. B. Unload any other files from the SDL Editor, and quit (do NOT minimize) the ObjectGeode Launcher if running. Automatic Observation of Simulations 161 In the SDL Editor, select Tools > SDL & MSC Simulator. The ObjectGeode Launcher appears: check that its left area only contains v76.pr and obs_ex2.obs. D. Press the Build button: this checks your SDL model and the GOAL observer and translates them into C code. 5.3.5.3 Replay the simulation scenario testl A. Press the Execute button to start the Simulator. The Simulator main window appears. As opposed to observer M