Challenge

Project 2 - Development of TFT Cluster Speedometer Software Component

SSurendra Rayapureddi6 Jun 2023

Answere :

Develop the Simulink model based on the given requirements and also create SLDD file and link the same to the model.

1) Aim : Development of TFT Cluster Speedometer Software Component.

Basic Information :

Cluster Instrument receives the signals from other ECU's via CAN bus interface. It also receives commands from the driver via steering wheel buttons. The signals are then processed by the Cluster ECU, after which the Cluster ECU may send the vehicle information to the LCD or light the LEDs and so forth, according to the results. Therefore, the Cluster ECU can be viewed as a carrier of the information flow.

The diagram below shows the overview of the system.

Requirements :

1.1 Calculating TFT Display Speed
Average Vehicle Speed would be displayed only if its between 2 kmph & 250 kmph. Any value outside this range will be discarded by its lower limit & upper limit
When Average Vehicle Speed is < 2 kmph, DisplaySpeed = 2 kmph
When Average Vehicle Speed is in between 2 kmph & 250 kmph, DisplaySpeed = Average Vehicle Speed
When Average Vehicle Speed is > 250 kmph, DisplaySpeed = 250 kmph

1.2 Main Data Filtering

Main Data Filtering subsystem will be activated for every 10th millisecond
DisplaySpeed1 (t) = ((DisplaySpeed (t) x 0.65)/ Main Filter Speed Value) 0.05

1.3 Auxiliary Data Filtering

Auxiliary Data Filtering subsystem will be activated for every 10th millisecond
DisplaySpeed_Filter (t) = ((DisplaySpeed1 (t) x 0.78)/ Auxillary Filter Speed Value) - 0.03

1.4 TFT Speed Output

If |(DisplaySpeedFilter - DisplaySpeed)| > 1.5

{

Vehicle Speed Display = DisplaySpeed

}

else

{

Vehicle Speed Display = DisplaySpeed Filter

}

Simulink Model:

Subsystem:

2.Simulink DataDictionary:

3.Requirements TaggingReport:

Create the Functional and SwReq File into the .xls File.

Click on the New Requirement set.

After that Click on Add Requirement.

Linking with Requirement:

Requirement Tagging Report:

4.Fixed Point Tool:

Run the Model Error Free >> Going to App>> Click on the Fixed-Point Tool >> Iterative Fixed Point Conversion.

Simulink Model:

Block After Applying Fixedpoint ToolBox:

Procedure to start FixedPointTool:

collectRange:

Propose DataType:

Apply DataType:

SLDD After Applying FixedPointTool:

5.Model Advisor(JMAAB)Compliance Report:

Going to the Simulink Model >> Click On Modelling >> Model Advisor

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

Simulink Model:

Functional Test Cases:

Model In Loop:

Sgnal Builder Waveform:

Main Data Inspector Output:

MIL Coverage:

Software In Loop:

Signal Builder Waveform:

SIL Data Inspector Output:

8. SLDV Test Generation Report :

goto the model and Run it without Error free >> App >> Design Verifier >> Click on the Test Generation.

Click on the test generation settings

Results of Design Error Detection:

Results Of Test Generation Report:

9.Auto code Generation .c & .h files:

10. Polyspace Analysis Report/Output :

1. Bug Finder :

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.

2. 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.

11. Test Manager Report- Baseline & Back to Back Testing :

Baseline Testing :

Goto the Model and run it. >> Click on the App >> Click on the Simulink Test >> After that Click on the Test Manager.

click on testcase File

After that select thr slreqx file and link to requirements