ate connected and instance 1 of process DLC in block DLCb is in state connected. A. Start the Simulator to simulate the V.76 model alone. B. In the Simulator command line, type the stop condition8 (the \ means continue on next line): stop if (DLCa ! DLC (1) ! state = connected) and (DLCb!DLC (1) !state = connected) You can also use the menu command Edit > Stop Conditions to enter, delete or modify a stop condition; in such case, do not type stop if. Several stop conditions may be entered: they are considered as being linked by an or operator. 8 To easily get the correct syntax for the name of an entity in the simulator, first use the print command; for example, here, if you enter print state, you get the pathnames to all the states in the model, which you can copy and paste to build your stop condition. Automatic Observation of Simulations 137 C. Replay9 the connection establishment scenario: select File > Scenario > Load, choose cnxl.scn. Press the button All: at the end of the scenario replay ¹0, the Simulator displays a line showing that the stop condition is satisfied, as depicted in Figure 5.41. F:ADONNEESATRANSMET\livreSimul\modelsOGW76\v76 File Edit View Execute Tools Help About selection: + DECISION V76para ! present; Stop if Filter + RESET (T320); Watch Print reset t320 from dicaldic(1) + OUTPUT EstabConf output I estabconf from dicaldic(1) via user to env_dlcasu Traces: Defaults Off NEXTSTATE connected; stop condition: (dicaldlc(1) ! state = connected) and (dicbidic(1)! state = connected Save Restore 15 transitions executed end of scenario execution SDL tracking Start MSC Watch... Firabe Transitions: dicaldispatch rom_ready_input_I_datareq with I_datareq(0 8E) from env_dicasu MSC-driven: dicaldispatch from_ready_input_l_datareq with I_datareq(1 39) from env_dicasu Activate 15/15 Now: 0 Redo: Figure 5.41 The stop condition is satisfied 5.3.1.2 More stop conditions The syntax of the stop if command is identical to the syntax of the filter command. Stop conditions can also be inserted into the model startu