Project 1 - Wiper control system and Vehicle speed calculation for ABS using Wheel Speed sensor

1.

The model has been developed and enclosed as Wiper.slx.A data dictionary has also been created and the same has been enclosed as WiperData.sldd.This was done using the following steps:

I.Modeling Tab is chosen in the Simulink Editor.

II.Model Settings is clicked to open the Model Properties.

III.In Model Properties External Data is chosen and then 'New' was clicked to create a new dictionary.

IV.Now the data dictionary was saved with the above-mentioned name.

JMAAB compliance checking was done using Model Advisor and the report is attached as report_493.

On the APPS Tab of the model Under Code Generation the icon Fixed Point Tool is clicked.A Dialog Box opens where 'New' option is chosen.From there 'Optimized Fixed Point Conversion' is selected and finally 'Prepare' icon is clicked.

The resulting report shows 60% progress as there are some issues which are required to be addressed to obtain 100% progress.The screenshot is enclosed as Wiper_FPT.

Using APPS tab 'Design Verifier' option was chosen from MODEL VERIFICATION,VALIDATION AND TEST template.

Although the model was found compatible and Test Generation was started yet the process halted due to an internal error vide the screenshots Wiper_TstGen and WiperSLDV_Error enclosed.The Simulink Design Verifier Report is attached herewith as WiperSLDV_Rep

For the purpose of creating the Test Harness after opening the model right clicking was done on the Subsystem.In the Test Harness heading 'Create' option was chosen.A Dialog Box opens.In the Dialog Box for Input 'Constant' was selected and next OK option was clicked.This resulted in creation of harness vide Wiper_Harness1 enclosed.

The Coverage Report is enclosed as Wiper_Coverage.

For creating the Polyspace Report the following step by step approach is used.

• Initially, open the Polyspace in that new project click on start new project.
• The Project Properties dialogue box will open in that give the project name as we saved in the MATLAB,then select the location where it we need to save after that click Next or use the default location.
• Then ,it asks for the Projrct source,click on browserand select the folder where th .c file are generated then optionally we can add the include folder then clock on finish,the polyspace environment will open.
• In the configuraton settings option called Target & compiler select the source code language as c,change the target processor as X86_64.
• In the coding standards & code Metrics in that enable the check MISRA C:2004 also select the calculate the code metrics option
• After that go to bug finder analysis under that select the default one.
• Go to reporting enable the generate report option and ouput formet as PDF or any file we need
• Finally save the polyspace and run the Bug Finder.

The following step by step approach is followed for performing the Baseline testing.

I.The model is opened.Next APPS icon was chosen and 'Simulink Test' is clicked.

II.Then 'Simulink Test Manager' is clicked.This causes opening of a Dialog Box.

III.Under the REQUIREMENTS tag at first ADD is clicked,then link EDITOR is clicked.Next in the Dialog Box 'New' is clicked, document type was chosen to be 'Requirement Set'.The file is browsed and 'Apply' & 'OK' were ticked.

IV.Under the 'System Under Testing' the model is opened and the Subsystem is selected.Next 'Simulation' is selected and 'Model Settings' is clicked.

V.Under INPUTS the option CREATE is clicked.

VI.An Excel file Input-data is created and the same is linked by browsing.

VII.Mapping of Input data was done.

VIII.Then mapping of Baseline data is required to be done

IX.Enable Coverage has to be ticked.

X.'Decision' is required to be chosen as the Coverage Matrix.

XI.After this all the settings are needed to be saved by Right clicking on the model and using the 'Save' option.

XII.Next the 'Run' button has to be clicked to get the results.

However, after mapping of inputs the subsequent steps were not possible to perform since the system flashed an error vide Wiper_BaseError screenshot attached.

For back to back testing the following step by step approach is adopted.

I.The model is opened and the Subsystem is selected.

II,The APP tab was clicked and Simulink Test tab was chosen from Model Verification,Validation & Test section.

III.Next 'Simulink Test Manager' was clicked.

IV.Then New>Test for Model Component was clicked.

V.To specify the top model Use Current Model button next to the Top Model field was clicked.Then 'Use Currently selected components' was clicked.

VI.Then 'Next' was clicked and 'Component input from Test Model' was used as Test Input.

VII.'Next' was clicked to select the Testing Method.Also 'Perform Back to Back Testing' was ticked.

VII.For Simulation 1 'Normal' was selected while for Simulation 2 'SIL' was selected.

VIII.'Next' was clicked.For specifying the file format EXCEL was chosen and for specifying the location to save test data default location name was used.

IX.Then 'Done' was clicked.The Test Harness and Test Cases are created and the wizard closes.

X.To run the back to back testing 'Run' button was clicked.

The process stops because of a technical error vide the error report Wiper_b2b enclosed.The supporting compiler was downloaded,but installation was not possible because of technical limitation.

2.

The model has been developed and enclosed as New_Veh_Spd_Cal.slx.The data dictionary for the model is also enclosed vide NewVehSpd.sldd.

In case of this model as well identical procedures have been followed to generate report.All the generated reports are attached herewith.As seen from NewVehSpd_FPT there is 80% completion in this case.It is clear from New_Veh_Spd_SLDV that out of 166 objectives 163 have been processed.

Generating C code for the model was not possible due to some technical problem and screenshot of the messages are attached herewith.

It is clear that Baseline test for the model was performed successfully and the report is enclosed as newReport.pdf.However, back to back testing was unsuccessful as seen from New_Veh_Spd_b2berror.