WEBVTT 00:00:07.200 --> 00:00:08.360 Welcome. 00:00:08.559 --> 00:00:10.160 Today I would like to show you 00:00:10.160 --> 00:00:12.960 How you can easily add or remove signals 00:00:13.080 --> 00:00:15.720 In huge Simulink models with MES MoRe. 00:00:23.279 --> 00:00:24.920 The first action I want to show you 00:00:24.960 --> 00:00:27.320 Is called Add Cross-Hierarchy Signal. 00:00:27.920 --> 00:00:29.960 This action allows you to add a signal 00:00:29.960 --> 00:00:31.900 Across your subsystem hierarchy 00:00:32.000 --> 00:00:33.840 With just a few clicks. 00:00:34.659 --> 00:00:37.480 You can add signals from lower levels to higher levels 00:00:37.680 --> 00:00:38.880 Or the other way around. 00:00:39.760 --> 00:00:42.280 Or from one subsystem to a subsystem 00:00:42.360 --> 00:00:44.596 In a completely different part of the model. 00:00:45.120 --> 00:00:48.320 The location of the source and target blocks doesn’t matter 00:00:48.320 --> 00:00:51.120 As long as they are within the same model. 00:00:52.320 --> 00:00:55.339 In this example I will add a signal from top to bottom. 00:00:56.239 --> 00:00:59.320 For this I can either select the source block 00:01:01.280 --> 00:01:03.680 Or an existing source signal. 00:01:05.439 --> 00:01:08.120 Then I start the action Add-Cross Hierachy Signal 00:01:08.320 --> 00:01:09.760 From the MoRe menu 00:01:11.100 --> 00:01:13.060 Which opens a dialog. 00:01:15.600 --> 00:01:19.040 Now I can easily navigate in the model to the target block 00:01:28.320 --> 00:01:29.640 And select it. 00:01:31.759 --> 00:01:34.960 Then I choose Get Selected Block in the dialog 00:01:35.920 --> 00:01:38.320 And start the action with Ok. 00:01:42.799 --> 00:01:44.020 MES MoRe then creates 00:01:44.044 --> 00:01:46.520 All necessary port blocks and signal lines 00:01:46.640 --> 00:01:49.040 To connect the source block to the target block. 00:02:02.560 --> 00:02:05.320 MES MoRe names all the created ports 00:02:06.159 --> 00:02:07.800 According to the source name. 00:02:19.840 --> 00:02:21.240 In the second example 00:02:21.490 --> 00:02:23.630 The name of the ports cannot be determined 00:02:23.640 --> 00:02:24.840 Via the source. 00:02:32.480 --> 00:02:35.020 In this case after selecting the target block 00:02:44.800 --> 00:02:47.600 You can specify a name for the ports in the dialog. 00:02:51.920 --> 00:02:53.840 Additionally, in this example 00:02:53.880 --> 00:02:56.080 The target block is a subsystem. 00:02:57.440 --> 00:02:59.698 In this case MES MoRe can create 00:02:59.722 --> 00:03:02.599 A new target port for you on the subsystem. 00:03:15.519 --> 00:03:17.140 The next two actions are called 00:03:17.160 --> 00:03:18.960 Add Input Signal from Higher Level 00:03:19.040 --> 00:03:21.760 and Add Output Signal up to Higher Level. 00:03:23.040 --> 00:03:26.800 These actions allow you to quickly add new external signals 00:03:27.000 --> 00:03:29.570 Without leaving the subsystem you're working on. 00:03:30.799 --> 00:03:33.100 Imagine you're working on a functional subsystem 00:03:33.100 --> 00:03:35.120 Somewhere down in your model hierarchy. 00:03:36.720 --> 00:03:38.440 At some point you realize 00:03:38.440 --> 00:03:40.280 You need another input signal here. 00:03:41.640 --> 00:03:44.000 You know exactly which higher level subsystem 00:03:44.000 --> 00:03:46.020 Needs to provide the signal. 00:03:47.040 --> 00:03:48.820 Now you can add this input signal 00:03:48.820 --> 00:03:51.280 Without leaving the current subsystem. 00:03:52.319 --> 00:03:55.120 To do this, simply choose the action 00:03:55.200 --> 00:03:56.880 Add Input Signal from Higher Level 00:03:57.339 --> 00:03:58.560 From the MoRe menu. 00:04:02.239 --> 00:04:03.619 In the dialog of the action 00:04:03.620 --> 00:04:05.400 You can select the source level 00:04:05.820 --> 00:04:07.360 And the name of the signal. 00:04:14.040 --> 00:04:15.120 When you click Ok 00:04:16.020 --> 00:04:18.200 MES MoRe will create the new input signal 00:04:18.240 --> 00:04:20.160 Coming from the selected higher level. 00:04:30.160 --> 00:04:31.875 The selected source system 00:04:31.899 --> 00:04:34.080 Is typically the top level system 00:04:34.080 --> 00:04:37.120 Which means the signal comes from outside of the model. 00:04:38.240 --> 00:04:41.360 Or also typically, a level whose inputs 00:04:41.360 --> 00:04:44.680 And outputs are automatically generated 00:04:44.680 --> 00:04:45.800 By other tools. 00:04:46.320 --> 00:04:49.020 For example, the root level of a software unit. 00:04:52.000 --> 00:04:53.232 The action allows you 00:04:53.256 --> 00:04:54.800 To fully concentrate on your work 00:04:54.800 --> 00:04:56.489 On the current subsystem 00:04:56.513 --> 00:04:58.520 And worry about the external connections later. 00:05:04.880 --> 00:05:06.655 Or you may want to create 00:05:06.679 --> 00:05:08.700 The interface of the subsystem first 00:05:08.700 --> 00:05:11.100 Without having to leave it. 00:05:13.680 --> 00:05:17.080 For output signals you can use the action 00:05:17.080 --> 00:05:19.520 Add Output Signal up to Higher Level. 00:05:21.039 --> 00:05:22.650 For an output signal you can also 00:05:22.800 --> 00:05:23.840 Select the source block 00:05:24.190 --> 00:05:26.440 Where the new output signal should start. 00:05:44.240 --> 00:05:45.570 The next action is called 00:05:45.650 --> 00:05:47.720 Remove Cross-Hierarchy Signal Backward. 00:05:50.320 --> 00:05:51.920 Instead of adding a signal 00:05:51.944 --> 00:05:54.040 You now want to remove the signal. 00:05:54.880 --> 00:05:58.260 Imagine your model contains a signal called "c" 00:05:59.360 --> 00:06:01.200 In this case, the signal branches 00:06:01.210 --> 00:06:02.720 To two different subsystems. 00:06:07.120 --> 00:06:09.840 Imagine you are currently working on a subsystem 00:06:09.840 --> 00:06:12.420 Somewhere inside this upper subsystem 00:06:12.420 --> 00:06:14.320 That makes use of the signal c. 00:06:26.319 --> 00:06:28.840 During your work on the subsystem 00:06:28.940 --> 00:06:32.640 You may find that you no longer need that input signal 00:06:34.080 --> 00:06:36.400 Maybe because the requirements have changed 00:06:36.920 --> 00:06:38.200 Or you have solved the problem 00:06:38.230 --> 00:06:39.560 With a different approach 00:06:39.619 --> 00:06:42.180 That makes this signal obsolete. 00:06:44.240 --> 00:06:46.500 Now you want to remove the signal backwards 00:06:46.500 --> 00:06:48.560 To the source block of the signal 00:06:48.901 --> 00:06:51.341 Or if the signal branches 00:06:51.440 --> 00:06:53.200 Backward to the branch point. 00:06:54.960 --> 00:06:57.840 With MES MoRe you can select the signal to be removed 00:06:58.600 --> 00:07:02.960 And start the action Remove Cross-Hierarchy Signal Backward from the menu. 00:07:10.080 --> 00:07:11.880 In the dialog you can choose the block 00:07:11.880 --> 00:07:13.760 At which you want to stop the removal. 00:07:14.880 --> 00:07:18.240 The dialog lists all virtual blocks on the signal path 00:07:18.240 --> 00:07:20.800 Backward to the source block of the signal. 00:07:23.360 --> 00:07:25.200 You can double click on all elements 00:07:25.200 --> 00:07:27.420 To highlight the corresponding block in the model. 00:07:39.039 --> 00:07:41.480 Typically, you want to remove the signal backwards 00:07:41.480 --> 00:07:44.129 To the source block or branch point of the signal. 00:07:44.630 --> 00:07:47.030 This is the last item on the list. 00:07:50.800 --> 00:07:54.120 When you click Ok, MoRe removes the signal backward 00:07:54.120 --> 00:07:55.760 To the selected stop block. 00:08:00.240 --> 00:08:04.240 The action has removed only the upper signal branch 00:08:04.240 --> 00:08:06.440 And the other branch remains untouched. 00:08:09.840 --> 00:08:12.440 The signal is removed all the way 00:08:12.445 --> 00:08:15.005 To the point where we started the action. 00:08:28.879 --> 00:08:30.360 The action can also be used 00:08:30.400 --> 00:08:32.696 If the corresponding signal is part of a bus. 00:08:49.760 --> 00:08:52.500 The action automatically removes the signal 00:08:52.500 --> 00:08:55.320 From all bus creators and bus selectors 00:08:55.320 --> 00:08:57.320 On the signal path backward. 00:09:22.560 --> 00:09:26.240 The next action is called Remove Cross-Hierarchy Signal Forward. 00:09:26.959 --> 00:09:30.200 The use case is a bit different from the backward removal. 00:09:30.959 --> 00:09:33.259 Imagine you're working on this part of the model 00:09:35.040 --> 00:09:36.800 The interface has changed 00:09:36.800 --> 00:09:39.720 And this signal c is no longer available. 00:09:41.480 --> 00:09:44.400 In this case, you want to remove the signal forward 00:09:44.400 --> 00:09:46.240 Along all its branches. 00:09:49.120 --> 00:09:51.920 But in addition to the removal you want to know 00:09:51.920 --> 00:09:54.440 Where the signal was used before 00:09:54.780 --> 00:09:57.200 Because you need to adjust these parts of your model 00:09:57.300 --> 00:09:59.780 After the removal. 00:09:59.920 --> 00:10:02.200 With MES MoRe you can select the signal 00:10:02.200 --> 00:10:03.880 Where you want to start the removal 00:10:05.920 --> 00:10:09.480 Then launch the Remove Cross-Hierarchy Signal Forward action 00:10:09.480 --> 00:10:10.560 From the MoRe menu. 00:10:16.480 --> 00:10:18.920 After the removal, a dialog appears 00:10:18.940 --> 00:10:20.160 That lists all blocks 00:10:20.360 --> 00:10:23.040 That lost their input signal due to the removal. 00:10:24.480 --> 00:10:26.100 You can double click on the items 00:10:26.100 --> 00:10:27.640 To highlight the block in the model. 00:10:33.360 --> 00:10:35.719 You can then adjust the model accordingly. 00:10:40.000 --> 00:10:41.720 The next action can be used 00:10:41.720 --> 00:10:44.319 To convert Goto/From blocks to signal lines. 00:10:50.800 --> 00:10:53.120 Converting Goto/From blocks to signal lines 00:10:53.120 --> 00:10:55.080 Can improve the readability of the model 00:10:55.080 --> 00:10:58.400 As the true signal flow becomes more obvious. 00:11:00.079 --> 00:11:01.720 With MES MoRe you can convert 00:11:01.720 --> 00:11:03.820 Either the selected Goto/Froms 00:11:03.839 --> 00:11:07.099 Or all Goto/Froms in the current subsystem at once. 00:11:08.399 --> 00:11:11.040 For converting individual Goto/From connections 00:11:11.040 --> 00:11:14.359 You can select either the Goto or the From block. 00:11:16.800 --> 00:11:18.199 If you select a From block 00:11:18.200 --> 00:11:20.479 That has other From blocks with the same tag 00:11:24.240 --> 00:11:26.920 Only the selected From block will be converted. 00:11:38.640 --> 00:11:40.360 If you select the Goto block 00:11:41.519 --> 00:11:45.080 Then all associated From blocks will be converted. 00:11:53.680 --> 00:11:55.600 If you select nothing at all 00:11:55.680 --> 00:11:58.400 Then all Goto/From blocks in the current subsystem 00:11:58.500 --> 00:11:59.500 Will be converted. 00:12:09.360 --> 00:12:10.440 After the conversion 00:12:10.460 --> 00:12:12.260 You can start rearranging the blocks 00:12:12.260 --> 00:12:14.240 To make the data flow more obvious. 00:12:27.600 --> 00:12:30.960 This is usually a good starting point for further refactoring.