Search Results

This paper proposes a solution to the challenge of developing vehicle software application functions which are decoupled from their intended target hardware platforms. Once developed, these software application functions can be utilised across any OEM vehicle platform and vehicle variants, saving the supplier time and money in terms of system development and giving a number of OEMs similar tried-and-tested system application software. The proposed solution is to use the Model Driven Architecture (MDA)1, a UML-based development approach that separates the specification of system functionality from the specification of the implementation of that functionality on a specific technology platform. MDA allows a vehicle function to be modelled in a semantically rich UML [1,2] model which is completely independent of any implementation detail.

ODX (Open Diagnostics data eXchange) is a standard diagnostic data format specified by the European ASAM group, to simplify the exchange of vehicle diagnostic data between manufacturers, suppliers and service dealerships. The ODX database contains diagnostic data for the whole vehicle together with details of all vehicle ECUs. This paper gives an overview of the main categories of data contained in the ODX diagnostic database. A Windows-based diagnostic application was developed to execute ISO 15765 diagnostic services on ECUs, using an ODX database to define the allowed services and parameters for each ECU. The paper describes the structure of the diagnostic application and the steps that were necessary to process the ODX and tailor it to a production ECU.

The development of vehicle control systems has evolved to become an exercise in the design and integration of complex, distributed hardware and software components. The various components are typically developed by geographically dispersed, multicultural teams from both OEMs and suppliers. This paper gives a brief overview of using the Unified Modelling Language (UML) as a means of capturing the requirements of real-time distributed systems in a graphical notation shared by all team members. UML is commonly used to model system concepts, albeit typically as system “sketches” without any formal definition of the model's semantics. This paper specifically addresses the additions to the latest version of UML that supports higher levels of abstraction, model-based development, executable models and the specification of non-functional requirements.

As automotive technology becomes more sophisticated the ability to troubleshoot and identify a malfunction becomes a more difficult and complex task, particularly without the assistance of specialised tools. A car manufacturer with the facility to identify and diagnose a malfunction before direct contact from the customer and possibly before the customer becomes aware that a problem exists would have a real competitive advantage in the market place. This paper proposes an architecture that may make this a reality. The architecture enables diagnostic information to be sent to a Case Based Reasoning (CBR) tool at the manufacturers premises when the car enters a hotspot (WI-FI enabled location). The CBR tool subsequently reviews diagnostic information to determine if a malfunction has occurred. If a malfunction is identified the customer is informed of the problem and is prompted to bring the car to a garage.

The Centre for Automotive Research WIT is developing a methodology and tool for optimally distributing OSEK Tasks throughout In-Vehicle Networks. This distribution methodology automates the OSEK Task - ECU allocation process, generating optimal solutions for the network, maximizing the number of OSEK Tasks per ECU and therefore allowing for either more complex functionality for the same ECU network or a reduction in the number of ECUs on the network. Overall, this should reduce development time and help save vehicle weight and costs.