Design of an Automatic Management System for vehicles

Design of an Automatic Management System for vehicles

This paper describes the design and implementation of a system responsible of the automotive monitoring and diagnosis of a vehicle using the standard OBDII (On Board Diagnostics), a mobile application on the Android Platform and the implementation of a Web server developed using PHP (Hypertext Preprocessor). For the development a mobile terminal Samsung Galaxy ACE, a vehicle Kia Rio R 2013 and an BAFX OBDII Bluetooth communication device were used. Also a fault code simulator was implemented to allow the system’s testing without the need of a real connection with the vehicle.

Since its creation over 100 year ago, the car has positioned itself as the predominant mean of transport in the world and it has become a key instrument for the functioning of society. However, over the last decades, the world has experienced an intense process of environmental awareness, where the automobile plays a significant role by being one of the main pollution sources that exist in the planet.The standard OBDI was created with the objective of monitoring the pollution levels of light levels. OBDI is in charge of monitoring the engine’s main components and its implementation in new vehicles became mandatory in the United States since 1991 [1]. The current OBDII standard was developed in 1996 as a result of stricter environmental measures in the United States and its implementation in new vehicles has being mandatory since that year. Currently the OBDII standard has been implemented in most new vehicles around the world and it is main tool for a complete automotive diagnosis.

OBDII is not only able to determine errors in the vehicle operation; it is also capable of providing information in real time about different parameters of the system.Currently many companies require that their vehicles to be in constant use, this causes them to be at risk of mechanical failures, capable of compromising not only their integrity but also the occupants security. These failures can cause the vehicle stoppage for repair, which represent a problem in terms of cost and logistics for the owners. Therefore, a system that integrates the information provided by the OBDII standard with a user- friendly interface, allows companies and vehicle owners to be aware of the mechanical condition of their unit, being able to identify and solve car problems and prevent potential catastrophic damage to them.The implementation of this system ensures the reliability of the vehicles and safety of the occupants concerning the mechanical part


A. Mobile ApplicationConsidering the developed system has two operation mo des, two different test procedures were determined.1) Local Monitoring Mode Tests:In local monitoring mode, the chosen method to test the performance was based on field tests with system running on the test vehicle. 20-minute routes were done in both urban and highway environments and a footage of the routes was done in order to detect problems in reading OBDII frames.

It was indeed found that the five parameters of interest are read and interpreted correctly by the system under different conditions.

2) Diagnostic Mode TestThe diagnostic mode seeks to find fault codes stored in the vehicle computer, if the vehicle does not have any problem, the system does not detect any code. While it was not possible to find errors in the test vehicle, the system demonstrates a proper operation by showing that indeed any fault code is stored and by sending this data to the server Web, application users ma y see the message “No Errors” indicating the condition of the vehicle. Figure 10 shows the system operation in diagnostic mode.In order to evaluate the system performance of a vehicle that contain errors, a Java application to simulate the answers that would provide a vehicle to be diagnosed was implemented. Just as BAFX OBDII device, the computer where the developed application runs, acts as a server in Bluetooth communication, i.e. responds to requests sent by the mobile application.The simulator receives the same frames that would normally receive the automobile computer. When the command requesting the diagnosis is received, the Java application randomly generates fault codes defined in the standard OBDII.

3) Mobile Application PerformanceThe mobile application developed requires the consumption of various smartphone’s resources for its operation. The mai n evaluated resources are:•Energy Consumption•Data Usage•RAM MemoryStarting with the terminal battery load at 100% load and a mobile data of 15 Mbytes and after covering a distance of 20 kilometers in 35 minutes with the application running, the percentage of energy consumption was 7 % and data consumption was 460 Kbytes. The RAM consumed by the application during execution as shown in the smartphone, was86 MB.

B. Web ApplicationIn order to test the operation of the Web application, the testing vehicle diagnosis and diagnosis using the developed simulator was made. In both cases, the results were sent to the server to verify that the data was not lost.The four tests are:•Test 1: The developed Java application was used to simulate the fault generation in a vehicle. The simulator generated 8 codes randomly.•Test 2: Likewise, the test was repeated with the simulator, this time only one code was generated.•Test 3: The diagnosis was performed on the test vehicle, turning in only one code. The received code P0000 indicates the absence of errors in the vehicle.•Test 4: Tera Term software terminal was used to send three frames simulating fault codes.