Content deleted Content added
Tag: Reverted |
ClueBot NG (talk | contribs) m Reverting possible vandalism by 73.233.0.109 to version by 2804:2488:1086:EBC0:546A:FB69:E025:6207. Report False Positive? Thanks, ClueBot NG. (3799007) (Bot) |
||
Line 36:
===Tight development schedules===
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|
▲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|da I like hahahah
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.
| |||