Trong các Simulator, chọn các quá trình chuyển đổi xuyên dlca dlc (1): từ waitua đầu vào t320: như thể hiện trong hình 4,46, biên tập hiển thị đầu vào tương ứng đậm (T320). Trong các chi nhánh ELSE, bạn sẽ thấy đầu ra của DLCstopped, mà gây ra vấn đề. | Interactive Simulation 83 A. Return to the previous simulation step by pressing the undo H Simulator button. B. In the Simulator select the transition38 trans dlca dlc 1 from_waitua_input_t320 as shown in Figure the Editor displays in bold the corresponding input T320 . In the ELSE branch you see the output of DLCstopped which caused the problem. Figure Searching for the unexpected signal bug C. In the Editor select Navigate Up the block type V76_DLC is now displayed as in Figure you see that signal DLCstopped goes to process dispatch through the signal route DLCs . D. In the Editor select process dispatch and do Navigate Down and Navigate Next Partition you see that under state waitUA the input of signal DLCstopped is missing. Correct the bug You will add the missing input of signal DLCstopped under state waitUA in process dispatch. A. When the Simulator is running the Editor prevents you from modifying the SDL model exit from the Simulator answering No to the question to enable the modification features of the Editor. Do not exit from the Editor. 38 The firable transition trans dlca dlc 1 from_waitua_input_t320 is preceded by a it reminds you that you executed it before the undo. 84 Validation of Communications Systems with SDL B. In Windows or Unix make a copy of the file into but continue working on which becomes version 2 . C. In process dispatch partition part2 select the input of DLCstopped under state ready copy it select the state waitUA and paste the whole transition is inserted as shown in Figure . Figure Missing input of signal DLCstopped added under state waitUA D. In the pasted transition don t forget to change the nextstate - into nextstate ready otherwise you will be stuck in state waitUA. E. Save the SDL model. Simulate to check the bug correction To check that the bug has been corrected you will load and automatically replay the scenario stored in Section . See Section .
