s, and the specified command ex-pid (Examine-Pid) is executed: Breakpoint matched at #SDTREF (SDL, topeer spt (1) , 140 (35,35) , 1, 1) Instance of process type : toPeer Parent : null Offspring : null Sender : <<Block DLCa>> dispatch : 1 AtoB: 1 in state ready 8.1.7 Running several communicating Simulators Several Simulators can be started, and they can exchange SDL signals. For example, our V.76 SDL model can be split, and each instance of block type V76_DLC can run in one Simulator and communicate with its peer instance running in the other Simulator. A. Create a new directory, and copy all the files (except the MSCs) of the V.76 example into it. B. Load v76.sdt in the Organizer. C. If you added an observer process to the model as specified in Chapter 5, go back to the version without observer process: in the Organizer, select Edit > Connect, choose To an existing file, press the folder-shaped icon and connect to the file v76test.ssy. D. Open the system V76test and remove blocks DLCb and dataLink as indicated in Figure 8.12. USE V76; SYSTEM V76test (dlc2su) DLCaSU (su2dlc) DLCa : V76_DLC V76frame DLCaDL V76frame to / from the other Simulator Figure 8.12 System V76test split in two E. In the Organizer, press the Save button, select the system V76test and select Generate Make. Check that the options are correct, especially: Microsoft (or other) Simulation and Generate Makefile must be selected. 274 Validation of Communications Systems with SDL F. Press Full Make. G. In the Organizer, press the Simulate button. The first Simulator starts. H. In the Organizer, select Tools > SDL > Simulator UI. The second Simulator starts: select File > Open and choose V76test_smc.e. (or the equivalent Unix suffix). I. In each Simulator, select General > Start SDL Env: the two Simulators, represented in Figure 8.13, can now exchange SDL signals (through the PostMaster). SDL SimulatorUI-F:ADONNEES\TRANSMET\livreSimul\modelsSDT\pas_pour_ftp\76_2sim\V76test_smc.exe - File View Buttons Log General Execute Examine Change Show Trace Brea