advertisement
Glossary ETAS
168
SBC
Electrohydraulic brake system ( S ensotronic B rake C ontrol)
SCOOP
S ource Co de, O bjects, and P hysics
SCOOP-IX
SCOOP I nterface E x change language.
INTECRIO V4.6 supports SCOOP-IX versions V1.0, V1.1, V1.2 and V1.4.
SP s ervice p
SWC
Atomic AUTOSAR software component; the smallest non-dividable software unit in AUTOSAR.
UDP
U ser D atagram P rotocol
UML
U nified M odeling L anguage
VFB
V irtual f unction b us in AUTOSAR
XCP
Universal measurement and c alibration p rotocol; the x generalizes the various transportation layers that can be used.
INTECRIO V4.6 supports XCP version V1.0.
XETK emulator test probe (ETK) with ethernet interface
XML
E x tensible M arkup L anguage
8.2
Terms
Actuator
Executing hardware unit. It forms the physical interface between electronic signal processing and mechanics.
Application mode
An application mode is part of the operating system; it describes different possible states of a system, such as the application mode EEPROM programming mode, starting or normal operation.
AUTOSAR software component
Back animation
Animation of the model in BMT with measured values from the running experiment. Calibration variables can be calibrated from inside the BMT.
INTECRIO V4.6 - User’s Guide
ETAS Glossary
Basic software
Bypass experiment
In a bypass experiment, parts of an electronic control unit program are executed on the experimental target (ES1000, ES900 or RTPRO-PC). This requires a special hook in the code.
INTECRIO V4.6 supports several types of bypass experiments: XCP bypass on CAN or UDP, as well as hook-based and service-based ETK bypass.
Connection, dynamic
Connection between signal source and sink that can be changed at runtime without a new build process.
Connection, static
Connection between signal source and sink that cannot be changed at runtime.
Crossbar
Manages and controls the connections between modules, functions and hardware in a non-AUTOSAR environment.
Embedded Coder TM
; extends the capabilities provided by the Simulink Coder to support specification, integration, deployment, and testing of production applications on embedded targets.
Environment system
Environment systems are used to model the plant model for virtual prototyping. They are built out of modules and functions, the same way as software systems.
Event
An event is an (external) trigger that initiates an action of the operating system, such as a task.
Event interface
FlexRay
FlexRay is a scalable and fault tolerant communication system for highspeed and deterministic data exchange. FlexRay’s time-division multiplexing facilitates the design of modular or safety-related distributed systems.
Its high bandwidth of 10 MBaud on two channels helps to cope with the high network load caused by the increasing amount of innovative electronic systems in modern vehicles.
The communication system’s specifications are released by the FlexRay consortium which is widely supported by vehicle manufacturers and suppliers worldwide.
Fullpass experiment
In a fullpass experiment, the complete electronic control unit program is executed on the experimental target.
INTECRIO V4.6 - User’s Guide 169
170
Glossary ETAS
Function
A grouping object for software systems that does not feature its own functionality. Modules or functions are assembled and connected in a function; they are thus clearly arranged and can be easily reused.
Graphical framework
The window that displays after the start of INTECRIO. The different INTEC-
RIO components are integrated in the graphical framework.
Hardware system
A hardware system contains the complete description of a hardware topology, consisting of the descriptions of the associated ECUs (experimental targets) as well as the descriptions of the interfaces (bus systems) between the devices.
Integration
The convergence of model code, which may have been developed by different partners or with different tools, to control algorithm, the configuration of this algorithm for the hardware on which it is supposed to run, and finally the creation of an executable file.
Implementation
An implementation describes the conversion of the physical task definition
(of the model) into executable fixed-point code. An implementation consists of a (linear) conversion formula and a limiting interval for the model values.
INTECRIO
INTECRIO is a tool that combines, i.e. integrates, the parts of the control algorithm created with different behavioral modeling tools that allows for creating and configuring a hardware system and the connection of this hardware system with the control algorithm.
M ATLAB
®
High-performance language for technical calculations; contains mathematical calculations, visualization and programming in one environment.
M ATLAB
® Coder TM
Introduced in M ATLAB /Simulink R2011a; the code generator for M ATLAB code.
Module
A module in INTECRIO contains the generic description of a functionality for an electronic control unit. For example, it corresponds to an ASCET project or a Simulink model.
OS configurator and OSC
The task of the operating system configuration is carried out within
INTECRIO the OS configurator and the OSC editor. The OSC is part of the
OS configurator, an easy to handle editor for the operating system configuration that provides the user with a quick overview of the system and allows for editing the configuration in an application-oriented display.
INTECRIO V4.6 - User’s Guide
ETAS Glossary
Process
A process is a simultaneously executable functionality that is activated by the operating system. Processes are specified in modules and do not feature any arguments/inputs or result values/outputs.
Processor
Project Configurator
The project configurator is part of the integration platform of INTECRIO. It is used to specify software systems and system projects.
Project Integrator
The project integrator combines all the components of the system (modules and functions, hardware interfacing, OS configuration, etc.) into an executable file.
Prototype
Completely executable file for an experimental target system. Such a prototype shows the software functions in practical use – entirely with different goal directions and in a different appropriation.
Rapid prototyping
The execution of a software on an experimental target, i.e. a computer with an interface to the vehicle.
RTA-Trace
Software tracing tool that can monitor system behavior over a versatile interface to the ECU.
Real-Time Prototyping for PC
Real-Time Workshop ®
Real-Time Workshop ® Embedded Coder TM
In M ATLAB /Simulink R2010b or lower, an add-on for the R ealT ime W orkshop; extends the capabilities provided by the Real-Time Workshop to support specification, integration, deployment, and testing of production applications on embedded targets.
Runnable entity
Runtime environment
Sensor
Sensors convert a physical or chemical (usually nonelectrical) quantity into an electrical quantity.
Service point
A service point is an encapsulation of a process in the ECU software. It provides data transfer actions to and from the target system; these actions can be enabled and configured by the user.
INTECRIO V4.6 - User’s Guide 171
172
Glossary ETAS
Service point cluster
A group of service points that are executed in the ECU with the same priority (service points located in the same ECU task).
Service point cluster group
A group of service point clusters. The group contains all service points of all tasks that can potentially be invoked at the same time in the ECU.
Simulink ®
Tool for modeling, simulation and analysis of dynamic systems. The models can be imported in INTECRIO.
Simulink ® Coder TM
Introduced in M ATLAB /Simulink R2011a; the code generator for Simulink and Stateflow models. Requires the M ATLAB Coder.
Stateflow ®
Tool for modeling and simulation of complex event-controlled systems. It is seamlessly integrated in M ATLAB /Simulink.
Stateflow ® Coder TM
In M ATLAB /Simulink R2010b or lower, code generator for Stateflow. It is seamlessly integrated in M ATLAB /Simulink.
In M ATLAB /Simulink R2011a or higher, the Stateflow Coder functionality is included in the Simulink Coder.
Software system
A software system contains the generic parts of the ECU description: modules, functions and connections.
System project
A system project combines a hardware system, a software system, an environment system (if applicable), the mapping of the signals and the configuration of the operating system in a common project and allows for the generation of executable code.
Task
A task is an ordered collection of processes that can be activated by the operating system. Attributes of a task are its application modes, activation trigger, priority and modes of its scheduling. Upon activation, the processes of the task are executed in the specified order.
Validation
Process for the evaluation of a system or a component with the purpose of determining whether the application purpose or the user expectations are met. Therefore, the validation is the check whether the specification meets the user requirements, whether the user acceptance is reached by a function after all.
Verification
Process for evaluating a system or a component with the purpose of determining whether the results of a given development phase correspond to the specifications for this phase. Therefore, software verification is the check whether an implementation of the specification specified for the respective development step is sufficient.
INTECRIO V4.6 - User’s Guide
ETAS Glossary
Virtual prototyping
Function developers create virtual prototypes of electronic vehicle functions and test them on the PC.
Workspace
The workspace combines all the data generated while working with
INTECRIO. From the WS browser, i.e. the tree view of the workspace, you can call up all the components of INTECRIO.
X-Pass experiment
Mixture of bypass and fullpass experiment. The experimental target
(ES1000, ES900, RTPRO-PC) utilizes the ECU with bypass hooks as interface to the outside world.
INTECRIO V4.6 - User’s Guide 173
advertisement