Project 1 - Wiper control system and Vehicle speed calculation for ABS using Wheel Speed sensor
Q.Develop the Simulink model based on the given requirements and also create SLDD file and link the same to the model.
Perform the complete V and V workflow for the obtained model
Development of TFT Cluster Speedometer Software Component
Cluster Instrument receives the signals from other ECU 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.
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 |
|
} |
ANS:
1.Development of TFT Cluster Speedometer Software Component
Cluster Instrument receives the signals from other ECU 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.
for develop the model following are block used:
- Input and Output block: we used for take input signal and give output signal
- Dynamic saturation block: used for upper and lower limit assin
- constant block: used for assign the constant value aacording to req.
- divide block: for used divide the signal
- Gain block:used for multiplication with input
- rem block: for remainder
- compare to zero block: the Compare To Zero block compares an input signal to zero.
- ABS block: Abs block outputs the absolute value of the input. For signed-integer data types,
- Switch block:for....if...else...condition
- Subsystem: used for acc to req for reduce the space
- enable subsystem: used for activate system after 10ms
- Main model of Development of TFT Cluster Speedometer Software Component:
Following are workflow of project
- simulink model file
- SLDD file
- requirement tagging report
- model advisor JMAAB
- fixed-point tool
- SLDV design error detection report
- functional test MIL,SIL harness,coverage reports
- SLDV test genration report
- Auto code generation report,main,c&h files
- polyspace analysis report/output
- Test manager report-baseline& back to back testing
Main model of Development of TFT Cluster Speedometer Software Component:
Requirement 1:- Input_Processing
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, Display Speed = Average Vehicle Speed
When Average Vehicle Speed is > 250 kmph, Display Speed = 250 kmph
Requirement 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
Requirement 3:- Auxillary Data Filtering
Auxillary Data Filtering subsystem will be activated for every 10th millisecond
DisplaySpeed_Filter (t) = ((DisplaySpeed1 (t) x 0.78)/ Auxillary Filter Speed Value) - 0.03
Requirement4:- TFT Speed Output:-
If |(DisplaySpeedFilter - DisplaySpeed)| > 1.5
{
Vehicle Speed Display = DisplaySpeed
}
else
{
Vehicle Speed Display = DisplaySpeed Filter
}
SLDD FILE CREATE ACCORDING TO MODEL
following are pic
FINAL MODEL WITH SIGNAL RESOLVING.
Following are workflow of project
- simulink model file
- SLDD file
- requirement tagging report
- model advisor JMAAB
- fixed-point tool
- SLDV design error detection report
- functional test MIL,SIL harness,coverage reports
- SLDV test genration report
- Auto code generation report,main,c&h files
- polyspace analysis report/output
- Test manager report-baseline& back to back testing
requirement tagging report
model advisor JMAAB report
report
- fixed-point tool-test
before apply the fixed point tool box
prepare result
Collect_ranges
apply data types
- SLDV design error detection report
- SLDV test genration report
- functional test MIL,SIL harness,coverage reports
test cases upload
MIL test templates
coverage reports
Auto_code_generation
SIL harness templates and coverage analysis report
polyspace report
9. Poly space analysis report / outputs
Steps to create a Polyspace Report:
- 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.
10)Test manager report-baseline& back to back testing
here showed difference"zero"
