首页 > 其他分享 >Design of a Brake-By-Wire System for Car

Design of a Brake-By-Wire System for Car

时间:2024-07-16 08:56:55浏览次数:10  
标签:wheel Wire braking system failure reliability Design marks Brake

 

Portfolio for Safety-Directed Design of a Brake-By-Wire System for Car

Coursework for 661985 – Safety Critical Systems

Part 2 –Dynamic Reliability Analysis and System Adaptation for Electronic Stability

The Portfolio explores the iterative design of a Brake-By-Wire (BBW) system for cars.

This is Part 2 of the assignment and continues this exploration with dynamic reliability analysis,

considering adaptation of the system to prevent skidding for electronic stability purposes. Part2 is worth

60% of the Portfolio.

You will analyse this architecture using Markov Models. Calculation of reliability involves programming

exercises.

We continue to examine the systems presented in Part 1. Its architecture for the system is given in Figure 1

below:

ζ

Figure 1: The proposed architecture of the BBW system

System Specification

  • The BBW features separate braking on each wheel.
  • All components of the system are powered by a common power supply (PS).
  • An electromechanical pedal (PL) receives the braking demand from the driver and sends this as a

message (PLm) to two pedal nodes PN1, and PN2.

  • Two replicas of the message are sent by each pedal node to buses B1 and B2. PN1 sends PN1m,

while PN2 sends PN2m.

  • Four Wheel nodes (WN1 WN4) each read those four identical messages (PN1B1m, PN2B1m,

PN1B2m, PN2B2m) from the two buses.

  • As long as one of the messages is received a wheel node can create the braking output applied to

the corresponding wheel (WN1b ... WN4b).

PN1

PN2

WN1

WN2

WN3

WN4

PS

PLm

B1 B2

PN1m

PN2m

PN1B1m, PN2B1m

PN1B2m, PN2B2m

WN1b

WN2b

WN3b

WN4b

p

p

p

p

p

p

PL

PN1B1m, PN2B1m

PN1B1m, PN2B1m

PN1B1m, PN2B1m

PN1B2m, PN2B2m

PN1B2m, PN2B2m

PN1B2m, PN2B2m2

Failures

Each component in this system has only one failure mode that shares the name of the component. For

example:

  • The failure mode of component PS is PS
  • The failure mode of component B1 is B1

The failure mode of each component leads to the omission of all outputs. For example:

  • If PS fails, you get O-p (Omission of p)
  • If B1 fails, you get O-PN1B1m and O-PN2B1m
  • Regarding the dynamic reliability analysis:

o It is assumed that all components have two states Operational and Failure.

o It is assumed that the system is completely healthy at the starting point.

o The failure distribution of all components is exponential with constant failure rates.

In the absence of component failures, all four wheels apply the braking output and the car brakes correctly.

When components fail, the system may fail to brake on one or more wheels. The effects vary depending on

the number of wheel failures. For example:

  • If one wheel fails, the car brakes sufficiently but is likely to skid off its course.

In this case, to correct the skidding failure, an electronic stability program could release the wheel

that is diagonal to the wheel that fails to brake. The car then brakes slowly, and the stopping

distance is increased.

  • If all wheels fail, then the car experiences catastrophic loss of braking.

Assignment Tasks

Based on this design:

  1. Only consider the independent failure modes of the 4 Wheels in the BBW and assume that the rest

of the system is perfect. Each wheel failure will lead the BBW to hazardous states of asymmetrical

braking. In each of the 4 cases, skidding prevention is applied by locking the diagonal wheel leading

to moving the system to a corresponding recovery state with reduced braking capacity. We assume

that the skidding prevention mechanism is perfect, i.e. the probability of its failure is zero. We also

assume that any further wheel failure from asymmetrical braking or recovery states will lead the

BBW to a single terminally failed state. Draw a Markov model and explain the model construction

procedure (15 marks).

  1. Consider that in [1]. all wheels have the same failure rates of 0.0001 failure per hour and provide a

Python code to calculate and visualise the reliability curve for 2000 hours (15 marks).

  1. Only consider the failure modes of PL, PN1, PN2, B1, B2, and PS, assuming that the wheels are

perfect. Draw a Markov model which shows how the system moves into a state of complete loss of

braking and explain the model construction procedure. (15 marks).

  1. Consider that in [3], all failure modes have the same failure rate of 0.000623 failure/hours. Provide

a Python code to calculate and visualise the reliability curve for 2000 hours. (20 marks).

  1. Consider only failure modes of B1 and B2 and Assume all other components are perfect. Also,

assume they are repairable with a failure rate of 0.0002 and a repair rate of 0.01 repair per hour.

Construct a new Markov model to evaluate the Availability and MTBF of the Bus subsystem. Please

provide a Python code for steady-state availability and MTBF calculation. The intention is to only

evaluate the availability and MTBF of the Bus sub-system. (20 marks)

  1. Consider only the failure modes of PN1 and PN2 and assume all other components are perfect. Only

focus on the reliability of pedal nodes and explain how we can improve the reliability using

reconfigurable Triple Modular Redundancy (TMR) architecture supported with three hot standby 3

redundancies. For all components, please consider the fixed failure rate of 0.000432. Construct a

new Markov model to evaluate the reliability of the Pedal Node subsystem. Please provide a Python

code for reliability calculation and visualise the unreliability curve for 3000 hours (15 marks).

Notes:

  • Explain your solutions in [1-6] above with a short paragraph of text to show your understanding.

Avoid verbosity. Up to 30% of marks will be deducted for lack of explanation.

  • For computational problems [2, 4, 5 and 6], please submit your Python code in separate files. These

files should be named according to the question number (e.g., Question2.py, Question4.py, etc.).

Please ZIP the files with the final report and submit it as a single-file submission.

  • Ensure your code is runnable. If your code cannot be executed due to errors, it will be examined

manually, and marks will be awarded based on the effort and correctness of the approach.

标签:wheel,Wire,braking,system,failure,reliability,Design,marks,Brake
From: https://www.cnblogs.com/qq-99515681/p/18304446

相关文章

  • 满满干活-wireshark进阶篇《Wireshark的TCP协议数据包常见报错提示》,练就你火眼金睛,助
    文章目录概要1.TCPPORTNUMBERSREUSED当四元组相同时会出现报错2.TCPWINDOWFULL与TCPZEROWINDOW之你怎么还不回我啊与我不行了。3.TCPWindowUpdate之我又行了能工作了小结概要本文介绍Wireshark的数据包常见报错提示,包括TCPPORTNUMBERSREUSED和TCPW......
  • 【Qt Designer用Frame设置背景图片】不影响其它组件小技巧,控件层级设置,组件的继承
    QtDesigner用Frame设置背景图片、颜色不影响其它组件小技巧,控件层级设置,组件的继承在设置背景时,遇到一个问题,例如用frame当最后一层设置背景,加载资源图片后,会使frame内部组件继承相同格式,很麻烦。原语句用法border-image:url(:/images/login.png);内部组件会出现父......
  • and-design-vue设置dropdownClassName无效的问题
    样式发现是有插入的,但是没有生效,使用:deep也一样没有效果问题来源改组件是根app同级,所以使用:deep无效解决办法使用:global,需要加“!important”......
  • 一套基于 Ant Design 和 Blazor 的开源企业级组件库
    前言今天大姚给大家分享一套基于AntDesign和Blazor的开源(MITLicense)、免费的企业级组件库(喜欢AntDesign风格的同学推荐使用):AntDesignBlazor。项目特性提炼自企业级中后台产品的交互语言和视觉风格。开箱即用的高质量Blazor组件,可在多种托管方式共享。支持基于WebAs......
  • Linux使用tcpdump命令抓包并使用wireshark分析常见的场景和解读
    使用tcpdump抓包并使用Wireshark分析网络流量是一项重要的网络管理和故障排除技能。以下是一个简单的步骤指南,涵盖了从抓包到分析的常见场景。抓包安装tcpdump在大多数Linux发行版上,您可以使用包管理器安装tcpdump。例如,在基于Debian的系统上:sudoapt-getin......
  • Spring推荐使用构造注入而不使用 @Autowired 注解
    参考:https://www.youtube.com/watch?v=CT8dbbe783shttps://blog.csdn.net/qq_43371556/article/details/123529701https://blog.csdn.net/qq_33721382/article/details/104071801https://blog.csdn.net/fudaihb/article/details/139231192什么是依赖注入DI(Dependency......
  • Matlab之App Designer 如何导入Excle数据并进行分析处理
    一、背景介绍当所需处理和分析的数据量较大时,我们需要将数据导入至Matlab中进行处理,本文将采用案例讲解的方式,详细介绍如何采用AppDesigner建立数据导入及分析GUI界面,同时展示如何对Excel的数据进行导入,并进行处理和分析。二、采用MatlabApp Designer导入Excel数据,并进行......
  • @Autowired和@Resource有哪些区别
    一、注解的作用@Autowired和@Resource都是用来实现Bean的自动注入功能。二、@Autowired和@Resource的区别1、所属的包不同@Autowired是Spring的注解。@Resource是JSR-250的注解。IDEA有时候会在@Autowired注解上面提示Fieldinjectionisnotrecommended(字段注入是......
  • @AutoWired和@Resource的区别
    @AutoWired和@Resource的区别来源不同:@AutoWired是Spring提供的注解.@Resource是JavaEE提供的,来源于java.annotation包,是JSR-250的一部分,所以,@Resource不是Spring特有的,它可以使用在所有遵循JavaEE标准的项目中。注入方式不同:@AutoWired默认是按照byType进行依赖注......
  • 物理设计 (Physical design)
    ASIC设计全流程:ASICBack-endFlowRef:IC入门必备!数字IC中后端设计实现全流程解析(1.3万字长文)PhysicalDesign:Physicaldesign:convertnetlist(.v)intoGDSIIform(layoutform)Duringphysicaldesign,allmacros,cells,gates,transistors,etc.,withfixedshap......