Image Processing Reference
In-Depth Information
one single development environment, covering all protocols used, in order to ensure end-to-end
timing predictability, still providing the necessary architectural freedom to choose the most economic
solution for the task.
19.16.9 Gatewaying
A network normally consists of multiple network segments using different protocols. Signals may be
transferred from one segment to another through a gateway node. As implemented throughout the
whole tool chain of Volcano automotive group, gatewaying of data even across multiple protocols
is automatically configured in VNA. In this way, VNA allow any node to subscribe any signal gen-
erated on any network without needing to know how this signal is gatewayed from the publishing
node. Handling of timing requirements over one or more gateways is also handled by VNA. he Vol-
cano solution requires no special gatewaying hardware and therefore provides the most cost-efficient
solution to signal gatewaying.
19.16.10 Data Export and Import
The VNA tool enables the OEMs to get a close integration between VNA and functional modeling
tools and to share data between different OEMs and subcontractors, e.g., node developers.
Support of emerging standards such as FIBEX and XML will further simplify information sharing
and become a basis for configuration of third party communication layers.
Volcano tool chain includes networking software running in each ECU in the system. his software
uses the configuration data to control the transmission and reception of frames on one or more buses
and present signals to the application programmer. One view of the Volcano network software is as
a “communications engine” under the control of the system integrator. The view of the application
programmer is different: the software is a black box into which published signals are placed, and out
of which can be summoned subscribed signals.
The main implementation goals for Volcano target software are as follows:
•
Predictable real-time behavior, no data-loss under any circumstances
•
Efficiency (low RAM usage, fast execution time, small code size)
•
Portability(lowcostofmovingtoanewplatform)
19.17 Volcano Configuration
Building a configuration is a key part of the Volcano concept. A configuration is, as already men-
tioned, based around details, such as how signals are mapped into frames allocation of identifiers,
and processing intervals.
For each ECU, there are two authorities acting in the configuration process: the system integrator
and the ECU supplier. he system integrator provides the Volcano configuration for the ECU regard-
ing the network behavior at the system level, and the supplier provides the Volcano configuration data
fortheECUintermsoftheinternalbehavior.
19.18 Configuration Files
The Volcano configuration data is captured in four different types of iles. hese are
•
Fixed information
(agreed between the supplier and system integrator).
•
Private information
provided by the ECU supplier. he ECU supplier does not necessarily
have to provide this information to the system integrator.
