Project 1 - Wiper control system and Vehicle speed calculation for ABS using Wheel Speed sensor
Project1: Develop the simulink model based on the given discription for below challenge and also create SLDD file amd link the same to the model. Perform the complete V and V workflow for the obtained Model.
1. Wiper Control System
Develop Simulink/state flow model for wiper control system based on the given conditions.
Description of challenge:
1. If the density of the rain is medium, then wiper rotates with low speed & the output signal should be 100 rpm
2. If the density of the rain is medium, then wiper rotate with medium speed & the output signal should be 200 rpm
2. If the density of the rain is High, then wiper rotate with High speed & the output signal should be 500 rpm
2. Vehical speed calculation for ABS using wheel Speed sensor
Develop simulink/state flow for the vehical speed calculation unit inside the ABS system for the below conditions.
Description of challenge:
fl,fr,rl and rr are the wheel speed of front left, front right, rear left and rear right respectively
Mode1:- If all Wheel speed sensor are working (fl, fr, rl, rr = On) then Vehicle speed = (fl+fr+rl+rr)/4
Mode2:- If Front left (fl) sensor is down then Vehicle Speed = (fr+rl+rr)/3
Mode3:- If Front right (fr) sensor is down then Vehicle Speed = (fl+rl+rr)/3
Mode4:- If Rear left (rl) sensor is down then Vehicle Speed = (fl+fr+rr)/3
Mode5:- If Rear right (rr) sensor is down then Vehicle Speed = (fl+fr+rl)/3
Mode6:- If any two sensor are down then the Vehicle Speed = Average of remaining two sensor Mode7:- If three sensors are down then Vehicle speed = 0.
Block Used:
1) Input Block
2) Output Block
3) And Block
4) Constant Block
5) Matlab Function Block
6) Switch Block
Model:
SLDD File Creation:-
Create New SLDD file and add the all signales into it
Requirment Tagging:
1) Create the SWreq file in exel (.xlsx)
2) Link the Requirement to the model using Requirement editor. befor the creation of Requirement keep open the .xlsx file and select the Requirement ID
Creation of requirement Set :- Requirment Manager >> Requirment Editor >> Add Requriment >> Add custom ID >> Save the file
Link the requirement:- Go to the simulink model and select the system >> Right click on requirement >> Link from
Model Advisor- JMAAB compliance Report:
Open The model into simulink editor tab and click on "Model advisor" >> Select the Modeling standared for JMAAB and click on "Run Selected Check"
Fixed-Point Tool:
Fixed-point tool >> Iterative Fixed-Point conversion >> Prepare >> Collect Range >> Propose Data Type >> Apply Data type
SLDV Design error detection Report:
Design Verifier >> Select 'Design error Detection >> Error Detection Setting >> Cheak for Compatibility >> Detect design Error
SLDV Test Ganeration Report
Design Verifier >> Select 'Test Ganeration' >> Test Ganeration Setting >> Cheak for Compatibility >> Ganerate Test Error
Functional test case and MIL Testing:
Create Function test case in exel file and save as .xlsx format. >> Right click on model >> Test Harness >> Create test Harness >> Source and Sinks( Signal Editor) >> Advance properied (Normal)
Result : All result are zero meanse the MIL testing is done succesfully
Coverage Report:
SIL Testing : Write click on model >> Block parameter (Subsystem) >> Treat as Atomic unit
Result : All result are zero meanse the SIL testing is done succesfully
Coverage Report:
Autocode Ganeration:
Embedded coder >> Build
Polyspace Analysis:-
As we dont have the polyspace licence, only steps to find out the polyspace bug finder report is written below.
Polyspace Bug Finder is a static code analysis tool that can help you identify potential bugs in your MATLAB code. To generate a Polyspace Bug Finder report, you can follow these steps:
1. Open MATLAB and navigate to the directory where your code is located.
2. Open the Polyspace Bug Finder interface by typing "polyspace" in the MATLAB command window.
3. In the Polyspace Bug Finder interface, select "Create New Project" and give your project a name.
4. Select "MATLAB" as the programming language for your project.
5. In the "Project Settings" window, select the files you want to analyze and specify any additional analysis options.
6. Click "Run Analysis" to start the analysis process.
7. Once the analysis is complete, Polyspace Bug Finder will generate a report that lists any potential bugs it has identified in your code.
8. To view the report, select "View Report" in the Polyspace Bug Finder interface.
9. The report will display a list of potential bugs, along with detailed information about each bug and recommendations for how to fix it.
10. You can save the report in various formats, such as PDF, HTML, or XML, by selecting "Export Report" in the Polyspace Bug Finder interface.
11. Review the report and fix any potential bugs identified by Polyspace Bug Finder to improve the quality and reliability of your MATLAB code.
Polyspace code prover output:-
Polyspace Code Prover is a static analysis tool that can help you verify the absence of run-time errors in your MATLAB code. To generate a Polyspace Code Prover output, you can follow these steps:
1. Open MATLAB and navigate to the directory where your code is located.
2. Open the Polyspace Code Prover interface by typing "psrun" in the MATLAB command window.
3. In the Polyspace Code Prover interface, select "Create New Project" and give your project a name.
4. Select "MATLAB" as the programming language for your project.
5. In the "Project Settings" window, select the files you want to analyze and specify any additional analysis options.
6. Click "Run Analysis" to start the analysis process.
7. Once the analysis is complete, Polyspace Code Prover will generate an output that indicates whether your code is free of run-time errors.
8. To view the output, select "View Results" in the Polyspace Code Prover interface.
9. The output will indicate whether your code is free of run-time errors or if any errors were detected.
10. You can save the output in various formats, such as PDF, HTML, or XML, by selecting "Export Results" in the Polyspace Code Prover interface.
11. Review the output and address any errors identified by Polyspace Code Prover to ensure the correctness and reliability of your MATLAB code.
Test Manager Report- Baseline & Back-to-Back Testing
Baseline Testing:
Simulink test manager >> New test file >> Requirement >> keep open the requiremnet .xlsx file >> add requirement >> System under test >> current system >> Inputs >> create exel file and create input >> modifie the exel file. >> Baseline criteria >> capture >> save exel file >> it atomatic detect the output >> Coverage setting >> check on "Record covergae for system under test. >> Then Run the test
Baseline Test Report
Back to back testing:
Simulink test manager >> New test file >> Test for model componet >> select current modelb>> select Design Verifier to ganerate tect input >> Select Perform back to back testing >> save result in excel file >> Then Run the test
Back to back report:
