with SDL Service User A Group Command : 1-r-q EstabReq(0) DataReq(0,5) Release( (0) Entry PId State proc1:1 start Service User B Group EstabResp Command Figure 8.10 Four buttons added to the Simulator F. Press the button Group in Service User B and select Add. G. Type EstabResp in the field Label, and Output-To L_EstabResp <<Block DLCb> dispatch in the field Definition. Press OK. H. Save the buttons definitions: select Buttons > Save As and enter def.btns. At the next launch of the Simulator, you will automatically get the newly created buttons. I. You can now test the new buttons to transmit signals to the SDL model. 8.1.5 Adding buttons to the Validator The same principles as those for the Simulator apply to add buttons to the Validator. Note that the buttons defined in Section 8.1.4.2 cannot be used in the Validator, as the command Output-To does not exist. The file names are different: def.btns becomes val_def.btns, def.cmds becomes val_def.cmds and def.vars becomes val_def.vars. 8.1.6 Setting breakpoints in the Simulator Breakpoints can be specified in the Simulator, to stop the simulation when a certain SDL symbol is reached, or on a transition, on a signal output, or on the modification of a variable. One or more Simulator commands can be executed automatically when a breakpoint is reached. To set a breakpoint on the input of signal V76frame in process type toPeer: A. Start the Simulator on the V.76 model. B. In the Simulator, select Breakpoint > Connect sdle. A new Breakpoints menu appears the SDL Editor. C. In the Editor, open the process type toPeer, select the input of signal V76frame and do Breakpoints > Set Breakpoint in the Prompt window, enter ex-pid. A red stop symbol appears near the input, as shown in Figure 8.11. PROCESS TYPE toPeer ready V76frame (V76par) Figure 8.11 A breakpoint on an input symbol Other Simulator Features 273 D. In the Simulator, press on Send To, select signal L_SetParmReq, choose < < Block DLCa> > dispatch, and press on Go: when the breakpoint is reached, the execution stop