f the first exception scenario D. Enter the command print state; the Simulator answers: > print state btoa (1) ! state = ready atob (1) ! state = ready dlcb!dispatch ! state = waitparmresp dlca!dispatch ! state = ready We see that process dispatch in block DLCb is in state waitParmResp. If we look at the SDL model, under this state no input or save of signal v76frame are specified. Thus, this signal has been discarded. 7.4.1.4 Correct the exception To prevent the signal from being lost, you will add a save of signal v76frame in state wait- ParmResp of process dispatch. A. Exit from the Simulator (answering No to the question). Do not exit from the Editor. B. In Windows (or Unix), make a copy of the file v76.pr into v76_v3.pr. Exhaustive Simulation 225 waitParmResp L_SetparmResp V76frame V76frame (XIDresp 0) VIA dlcDL ready Figure 7.46 Missing save of signal v76frame added C. In process dispatch, partition part1, select the input L_SetParmResp under the state wait- ParmResp, and add a save containing v76frame, as illustrated in Figure 7.46. D. Save the SDL model. 7.4.1.5 Simulate to check the bug correction To check that the bug has been corrected, you will load and automatically replay the scenario v76.x1.scn. A. In the SDL Editor, unload all files except v76.pr. B. If the ObjectGeode Launcher is not running, in the Editor select Tools > SDL & MSC Sim- ulator. C. In the ObjectGeode Launcher, remove any file other than v76.pr, press the Build button, then, if there are no errors, press the Execute button. D. The Simulator starts: press on Start MSC. E. In the Simulator, select File > Scenario > Load, open v76.x1.scn, and press the button Redo: All. The Simulator replays the scenario and the exception no longer exists. Do not exit from the Simulator. 7.4.2 One second to detect missing input L_ReleaseReq 7.4.2.1 Run the exhaustive simulation A. In the Simulator, press on init K then press on redo four times. B. Select Execute > Verify: enter 20000 for States Limit, press Verify and confirm the verifica- tion startup