2010
DOI: 10.1016/j.mechatronics.2010.05.003
|View full text |Cite
|
Sign up to set email alerts
|

Towards automation of control software: A review of challenges in mechatronic design

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Year Published

2012
2012
2024
2024

Publication Types

Select...
5
4

Relationship

0
9

Authors

Journals

citations
Cited by 59 publications
(7 citation statements)
references
References 41 publications
0
5
0
Order By: Relevance
“…3, which illustrates the top-level system architecture). The tool can connect to further development stages, such as performance analysis or control software generation (Alvares Cabarera et al, 2010). Other possibilities would be connecting functional descriptions with user-level upfront information such as workflow that would eventually guarantee and increase the usability of the product in connection with functions (van Beek & Tomiyama, 2011).…”
Section: Three Possible Directions To Make Function Modeling More Pramentioning
confidence: 99%
See 1 more Smart Citation
“…3, which illustrates the top-level system architecture). The tool can connect to further development stages, such as performance analysis or control software generation (Alvares Cabarera et al, 2010). Other possibilities would be connecting functional descriptions with user-level upfront information such as workflow that would eventually guarantee and increase the usability of the product in connection with functions (van Beek & Tomiyama, 2011).…”
Section: Three Possible Directions To Make Function Modeling More Pramentioning
confidence: 99%
“…3, which illustrates the top-level system architecture). The tool can connect to further development stages, such as performance analysis or control software generation (Alvares Cabarera et al, 2010).…”
Section: Three Possible Directions To Make Function Modeling More Pramentioning
confidence: 99%
“…The development of mechatronic systems requires the collaboration of the mechanical, electronic, control, and software domains in a design team. The team can obtain the design and instrumentation by applying a mechatronic design strategy where mechanical, electronic, control, and computer engineering areas must collaborate to obtain a specific mechanism [34]. The typical approach is a sequential design, as shown in Figure 1.…”
Section: Methodsmentioning
confidence: 99%
“…Yet, such a transformer does not completely exist and still evolving (Wang & Dagli, 2008). Hence, these approaches have some shortcomings regarding automatically driving a simulation model from the descriptive model (Alvarez Cabrera et al, 2010;Fleck et al, 2013;Matei & Bock, 2012;Mayerhofer et al, 2013;Mijatov et al, 2015;Moses, 2002).…”
Section: -Modelling the Operational Policies As The Model Invariantsmentioning
confidence: 99%