SAE Technical Paper Series 2003
DOI: 10.4271/2003-01-1024
|View full text |Cite
|
Sign up to set email alerts
|

A New Environment for Integrated Development and Management of ECU Tests

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2003
2003
2017
2017

Publication Types

Select...
3
2
2

Relationship

1
6

Authors

Journals

citations
Cited by 25 publications
(4 citation statements)
references
References 1 publication
0
4
0
Order By: Relevance
“…this can be achieved, if all the necessary elements of the process are provided by one testing tool. An example is the tool AutomationDesk, [7], [8] ( Figure 14).…”
Section: Mtest In Automationdesk Figure 14: Automationdeskmentioning
confidence: 99%
“…this can be achieved, if all the necessary elements of the process are provided by one testing tool. An example is the tool AutomationDesk, [7], [8] ( Figure 14).…”
Section: Mtest In Automationdesk Figure 14: Automationdeskmentioning
confidence: 99%
“…This allows the different users of the different development steps to select tests that make sense in the current scenario. This is especially important for large test projects, where it is not possible for the test operator to check the applicability of each test manually [1].…”
Section: Flexible and Modular Hardware And Software Conceptmentioning
confidence: 99%
“…I/O boards, together with signal conditioning for level adaptation to the automotive voltages required by the ECU, provide the interface to the ECU pins. Figure 2 shows a typical hardware-in-the-loop system architecture [1]. The most important components of an HIL system are described below.…”
Section: What Needs To Be Considered When Configuring/selecting a Simmentioning
confidence: 99%
See 1 more Smart Citation