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

1)Ans:

Main Model:

SLDD file:

Requirement Tagging:

We can see the Requirement Tagging in Report:

Report:

JMAAB check:

Fixed Point Tool:

After the data type will be changed

MIL & SIL Functional Test cases:

MIL Harness:

Signal Builder Output:

Scope Output:

Coverage:

SIL Harness.

At first Build the model , and generate .mex file. to Build the model. now select the coding option as embedded coder.

Scope Output:

SIL Coverage:

SLDV Report And Analysis:

Click on Run button , which gives design verifier as compatible.

Now select the Test Generation Mode:

Advisor Report:

Auto Code Generation:

Polyspace Bug report:-

As we dont have the polyspace licence, only steps to find out the polyspace bug finder report is written below.

Baseline and BacktoBack Test:-

Go to apps and click apps-> simulink test->Test Manager

BaseLine Report:

Back to Back Testing:

To select the Test for Model component

Report:

2.Vehicle speed calculation for ABS using Wheel Speed sensor:

Aim : Develop Simulink/state flow model for the vehicle speed calculation unit inside the ABS system for the below conditions.

1) Simulink Model :

Subsystem:

Simulink DataDictionary:

3)Requirement Tagging:

Create the Functional and SwReq into the .xls files.

Linking the Requirement:

Requirement Report:

4)Model Advisor JMAAB Report:

5) Fixed-Point Tool :

Run the model Error Free then Goto the >> App>> Click on the Fixed point Tool.

Simulink Model :

6) SLDV Design Error Detection Report :

Goto the Model >> Click on the App>> Select the Design Verifier >> Design Error Detection>> Design Error Detection Setting.

Simulink Model :

7) Functional Test Cases, MIL,SIL Harness, Coverage Report :

Functional Test cases:

MIL Model:

Signal Builder:

MIL Scope Output:

MIL Coverage Report:

SIL Model:

SIL Output:

SIL Coverage Report:

code generated after running the model:

8)SLDV Test Generation Report:

9):Advisor Report:

10) Polyspace Analysis Report/Output :

Procedure to Analysis the Polyspace Report

Bug Finder :

• Firstly Generated the .C code
• 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.

Code Prover :

• Befour going to the Code Prover First setup the Configration setting.
• In Configuration go to the Code prover verification and under code prover verification option.
• Click on the Check Behavior and Enable the option (i,e Allow Negative Operand for left shifts).
• and also click on the Consider Non-Finite floats.
• Then After you go to the Precision
• In Precision Select the Precision level -2 and Verification Level is Software Safety Analysis Level-2.
  then After Click on Save Botton the Configration setting will be save.
  then After We Run the Code Prover.
• And After Click on the Dashboard option and see the Results.

12) Test Manager Report-Baseline & Back to Back Testing :

Baseline Testing :

Run the model>> goto the Simulink Test >>Click on the Simulink Test Manager >> then Click on New >> Test File>> Create Test Name.

BACK TO BACK Testing: