Hardware-in-the-loop simulation: Difference between revisions

Revision as of 16:02, 4 October 2020

Revision as of 02:26, 16 October 2020

Line 36:

===Tight development schedules===

The tight

The tight development schedules associated with most new automotive, aerospace and defense programs do not allow embedded system testing to wait for a prototype to be available. In fact, most new development schedules assume that HIL simulation will be used in parallel with the development of the plant. For example, by the time a new [[Internal combustion engine|automobile engine]] prototype is made available for control system testing, 95% of the engine controller testing will have been completed using HIL simulation{{citation needed|date=March 2015}}.

D,

development

schedules associated with most new automotive, aerospace and defense programs do not allow embedded system testing to wait for a prototype to be available. In fact, most

The tight development schedules associated with most new automotive, aerospace and defense programs do not allow embedded system testing to wait for a prototype to be available. In fact, most new development schedules assume that HIL simulation will be used in parallel with the development of the plant. For example, by the time a new [[Internal combustion engine|automobile engine]] prototype is made available for control system testing, 95% of the engine controller testing will have been completed using HIL simulation{{citation needed|date=Marchda I like hahahah 2015}}.

The aerospace and defense industries are even more likely to impose a tight development schedule. Aircraft and land vehicle development programs are using desktop and HIL simulation to perform design, test, and integration in parallel.