WO2008127243A1

WO2008127243A1 - Multiple source networked diagnostic data logging

Info

Publication number: WO2008127243A1
Application number: PCT/US2007/009188
Authority: WO
Inventors: Bryan P. Mcguan
Original assignee: Robert Bosch Gmbh
Priority date: 2007-04-16
Filing date: 2007-04-16
Publication date: 2008-10-23

Abstract

Methods and systems for logging data communicated in a test network are disclosed. One method includes initiating a communication session among one or more applications executing on computing systems distributed through the test network and one or more vehicle communications interfaces in the test network. The method also includes logging data communicated during the session to a target data repository, the target data repository defined by a name and a system location within the test network. The method further includes terminating the communication session.

Description

MULTIPLE SOURCE NETWORKED DIAGNOSTIC DATA LOGGING

Technical Field

The present disclosure relates to system testing and diagnostics, such as in automotive systems. More specifically, the present disclosure relates to systems and methods for multiple source networked diagnostic data logging.

Background

Modern automobiles have multiple on-board computers which are interconnected via automobile-specific communications buses (ISO 9141 , CAN, etc.). Diagnostic and reprogramming access to these on-board computers, commonly referred to as electronic control units ("ECUs") is provided by a vehicle communications interface ("VCI"). A VCI is typically a small, self contained computing system", designed to interface with automotive control systems. VCIs can work in conjunction with a personal computer, which can host diagnostic software for assistance in testing and calibrating an ECU, such as a diagnostic scan tool system which monitors data transmitted to the ECU.

During development and testing of diagnostic software, it is often desirable to see data passed among PCs, VCIs, ECUs, and other vehicle control systems. This development can occur in an environment in which multiple PCs are connected to multiple VCIs, forming a number of concurrent data communication sessions. Viewing data in multiple sessions can be difficult because data from each ^• session is stored separately on local systems, and it is difficult to synchronize. One solution requires a global clock with which all PCs and VCI must synchronize in order to properly timestamp data stored by that source. The synchronized data can be merged to view data transmitted across multiple systems. However, maintaining an added level of synchronization adds complexity to an already complex development and testing environment.

Therefore, improvements are desired. Summary

The above and other problems are solved by the following: In a first aspect, a method for logging data communicated in a test network is disclosed. The method includes initiating a communication session among one or more applications executing on computing systems distributed through the test network and one or more vehicle communications interfaces in the test network. The method also includes logging data communicated during the session to a target data repository, the target data repository defined by a name and a system location within the test network. The method further includes terminating the communication session.

In a second aspect, a system for logging data communicated in a test network is disclosed. The system includes a memory configured to store data logged in the test network. The system further includes a programmable circuit operatively connected to the memory. The programmable circuit is configured to execute program instructions to initiate a communication session among one or more applications executing on computing systems distributed through the test network and one or more vehicle communications interfaces in the test network. The programmable circuit is further configured to execute program instructions to log data in the memory that is communicated during the session to a target data repository, the target data repository defined by a name and a system location within the test network. The programmable circuit is also configured to execute program instructions to terminate the communication session.

In a third aspect, a method of logging data communicated in a test network is disclosed. The method includes linking a data logger to one or more components in an automotive test network. The method also includes initiating a data logging session. The method further includes initiating a communication session among one or more applications executing on computing systems distributed through the automotive test network and one or more vehicle communications interfaces in the automotive test network. The method includes logging data communicated during the session to a target data repository, the target data repository defined by a name and a system location within the test network. The method also includes detecting completion of data communication among the one or more applications. The method additionally includes terminating the communication session.

Brief Description of the Drawings Figure 1 shows methods and systems for networked data logging in a possible embodiment of the present disclosure;

Figure 2 shows a schematic of an exemplary test environment in which aspects of the present disclosure may be implemented;

Figure 3 shows a schematic of an exemplary test sub-environment for a session, according to a possible embodiment of the present disclosure;

Figure 4 shows an exemplary computing environment with which various aspects of the present disclosure may be implemented;

Figure 5 shows further methods and systems for networked data logging in a possible embodiment of the present disclosure; and Figure 6 shows an exemplary log file that can be created using the methods and systems of the present disclosure.

Detailed Description

Various embodiments of the present invention will be described in detail with reference to the drawings, wherein like reference numerals represent like parts and assemblies throughout the several views. Reference to various embodiments does not limit the scope of the invention, which is limited only by the scope of the claims attached hereto. Additionally, any examples set forth in this specification are not intended to be limiting and merely set forth some of the many possible embodiments for the claimed invention. The logical operations of the various embodiments of the disclosure described herein are implemented as: (1) a sequence of computer implemented steps, operations, or procedures running on a programmable circuit within a computer, (2) a sequence of computer implemented steps, operations, or procedures running on a programmable circuit within a motor vehicle or vehicle test system; and/or (3) interconnected machine modules or program engines within the programmable circuits. In general the present disclosure relates to networked data logging as related to diagnosing and reprogramming vehicle communication interface modules (VCIs) that is useable in a multi-session, multi-VCI environment. The present disclosure provides methods and systems by which networked test environments can be coordinated to log data communicated via various communication links to a remote, networked location. According to certain aspects of the present disclosure, that data logged can be coordinated into a single data file remote from the communicating systems, such that the logged data is synchronized and is written in a sequential order into a single file on that remote system. Other methods and systems are disclosed as well.

Figure 1 shows methods and systems for networked data logging in a possible embodiment of the present disclosure. The system 100 logs data from multiple sessions, corresponding to multiple sources of data, in a single, networked location that can be remote from the source of the data being logged. In one example of operation of the system, data can be logged regarding a plurality of vehicle communication interface modules, or communications between those modules and a plurality of personal computers.

Operational flow in the system 100 is instantiated at a start operation 102. The start operation 102 corresponds to initial setup of a test network, such as connection of a plurality of personal computers to a plurality of VCIs, which are in turn connected to corresponding control systems of tested automobiles. An exemplary test network is described below in conjunction with Figure 2. Operational flow proceeds to an initialization module 104, which corresponds to initiating a communication session among one or more applications executing on computing systems distributed through the test network and one or more vehicle communications interfaces in the test network. Various applications may begin execution on one or more computing systems that are within the test network, or on the VCIs or electronic control units of various automobiles in the network. The applications can include software for reprogramming the ECUs, or otherwise directs the unit to share data with external computing systems. For example, the application could be a simulation application resident on a computing system that is configured to transmit data to an ECU in an automobile, via a VCI, and to observe a test of the ECU. The application generally opens a communication conduit, such as a socket, in order to transmit data to other physical or logical systems in the test network. In certain embodiments, the application transmits data in a session, which refers to a software-managed communications link between one or more VCIs and external computing systems, such as to provide access to ECUs to the external computing systems. Other methods by which data may be communicated between software systems and across networks may be implemented as well.

In certain embodiments, the initialization module 104 further corresponds to initialization of a data logging system. The data logging system can include a variety of components, and generally includes software configured to detect data transmitted by the application, such as through the assigned communication socket. The data logging system can include a plurality of data logging software agents assigned to a plurality of communications sockets, such as sockets defined at an interconnected PC or VCI.

In further embodiments, initialization of the data logging system is performed separately, and occurs prior to initializing the system and corresponding software application that is to be observed by the data logging system.

Operational flow proceeds to a log module 106. The log module 106 stores data that is communicated in the session, i.e. through the socket, via one or more of the data logging agents. The log module 106 logs data associated with the session, as defined in the VCI. The data is stored at a location and in a data repository that is predefined, either by default in the system 100 or by a user of the system. For example, a user of the system can provide a filename and directory in a remote computing system communicatively connected to the test network, and communications from the selected socket or other data link can be stored in a repository at that location. If multiple data logging agents are located throughout a test network, each of the logging agents can send data to the file for storage. Other methods by which data from a number of sources in the test network can be stored in a single, remote data repository may be used as well.

Operational flow proceeds to a termination module 108. The termination module 108 corresponds to termination of one or both of the logging or the execution of the applications in the test network. Termination can correspond to, for example, closing of a communication connection, or ending a data operation, such that no additional data is stored in the data repository. Operational flow terminates at an end operation 110, which corresponds to ending execution of the system 100.

Referring now to the system 100 as a whole, it is noted that the system 100 is general in that it is not dependent on any particular operating system. While the Microsoft Windows operating system is used in one embodiment of the present disclosure, this is solely because it is the predominant operating system of automotive shop computers; the methods and systems described herein have been tested on both Windows and Linux systems and have no internal restrictions as to application, e.g., on PalmOS, MacOS X, FreeBSD, or other common operating systems.

Referring now to Figure 2, a schematic of an exemplary test environment 200 is shown in which aspects of the present disclosure may be implemented. In the embodiment shown, the test environment is an automotive test environment in which communications links from computing systems to ECUs and corresponding VCIs are monitored. In the environment 200, a plurality of personal computers 202a-c are linked to a plurality of VCIs 204a-b via a Local Area Network (LAN) 206. The VCIs 204a-b in turn use a proprietary interface to communicate with various electrical control systems in one or more automobiles 208, such as ECUs. In the embodiment shown, a LAN 206 is used to connect the VCIs 204a-b and the PCs 202a-c; however, other standard communications networks can be used as well.

The plurality of personal computers 202a-c provide an interface allowing users to develop applications to interface with and test automotive control systems. The personal computers can be, for example, generalized personal computers such as those described below in Figure 4. One or more of the personal computers 202a-c can be used as a data server, and be configured to store data related to tests performed on the automotive control systems via the VCIs 204a-b.

In the embodiment shown, the personal computer 202c includes data log management software 210, and is configured to receive logged data transmitted to it from the other PCs 202a-b, VCIs 204a-b, or other computing systems capable of communicating via the network 206. The personal computer 202c stores a data repository, shown as a log file 212j managed by the data log management software, which stores sequential, chronological records of control and data communicated among the PCs 202a-c and VCIs 204a-b on the LAN 206. The data repository can be accessed by a variety of well known applications used for data analysis, such as a spreadsheet program or other program, in order to view and determine the specific data communicated in the environment 200. An example log file 212 is described below in conjunction with Figure 6.

The dashed and dotted lines on Figure 2 illustrate an example in which data from three communications sessions is stored into a single log file 212. In the example shown, a first session is opened between a first PC 202a and a first VCI 204a. A second session is opened between a second PC 202b and the first VCI 204a. A third session is opened between the second PC 202b and a second VCI 204b. Control and data communications occur on the LAN 206 between the PCs and corresponding VCIs based on the session, as managed by the VCIs 204a-b. Each VCI can manage a large number of communications sessions with one or more PCs. Data can be logged to a log file 212 in a third PC 202c from any of the open sessions, from the perspective of either the PC, or the VCI, or both. In the example shown, data is logged from the perspective of PC 202a in the first session, as managed by VCI 202a. Data is logged from both the perspective of the PC 202b and the VCI 204a for the second session, and from the VCI 204b only for the third session.

In the embodiment shown all of this data is stored in the data file 212 in a chronological, sequential order on PC 202c. In an alternative implementation, each session is separately stored in a different data file 212. Furthermore, other numbers and combinations of PCs, VCIs, and communication sessions are possible, and depend generally on the architecture of the particular environment 200 used, as well as the tests run and the data to be tracked in that environment 200.

Figure 3 shows a schematic of an exemplary test sub-environment 300 according to a possible embodiment of the present disclosure. The exemplary sub-environment illustrates a possible combination of devices for which a communications session can be defined. A communications session refers to an established communication link between a vehicle communication interface and an external computing system,; however, communications sessions may exist in which the vehicle communication interface does not link to a computer, and instead establishes a communication conduit to other software within the VCI itself, such as by establishing a socket useable by the communicating software to allow data communications to occur.

In the embodiment shown, the sub-environment includes a computing system, shown as PC 302, as well as a vehicle communication interface 304 and an electronic control unit 306. The PC 302 provides a user interface to direct tests or other communication with control systems of an automobile. The PC 302 can be any of a number of generalized computing systems, such as described below in Figure 4. The VCI 304 provides a link to the ECU, which typically resides within or is intended to reside within an automobile. The VCI 304 generally includes control software to manage communications from computing system 302 to the ECU 306, such as by providing session management software for separating and arbitrating communications. The VCI 304 can be a generalized computing system such as described below in conjunction with Figure 4; however, it also will include the necessary proprietary connection hardware and software to establish communications with the ECU, as described below. The ECU 306 is a specialized programmable circuit configured to perform specialized tasks within an automobile, such as monitoring and controlling physical actions within the automobile (i.e. fuel supply, emissions monitoring, etc.). The sub-environment also includes two links 308, 310, each connecting the PC 302 to the VCI 304, and connecting the VCI to the ECU, respectively. The PC to VCI link 308 can be a standard network link, such as a portion of a local area network, a direct networked connection, a serial connection, or other communicative connection provided by the two computing systems. The VCI to ECU link 310 is typically a custom interface, and may allow access to a data interface and memory within the ECU for testing and reprogramming of the ECU, as necessary.

Referring now to FIG. 4, an exemplary environment for implementing embodiments of the present disclosure includes a general purpose computing device in the form of a computing system 400, including at least one processing system 402. A variety of processing units are available from a variety of manufacturers, for example, Intel or Advanced Micro Devices. The computing system 400 also includes a system memory 404, and a system bus 406 that couples various system components including the system memory 404 to the processing unit 402. The system bus 406 might be any of several types of bus structures including a memory bus, or memory controller; a peripheral bus; and a local bus using any of a variety of bus architectures. Preferably, the system memory 404 includes read only memory

(ROM) 408 and random access memory (RAM) 410. A basic input/output system 412 (BIOS), containing the basic routines that help transfer information between elements within the computing system 400, such as during start up, is typically stored in the ROM 408. Preferably, the computing system 400 also includes a secondary storage device 413, such as a hard disk drive, for reading from and writing to a hard disk (not shown), and/or a compact flash card 414.

The hard disk drive 413 and compact flash card 414 are connected to the system bus 406 by a hard disk drive interface 420 and a compact flash card interface 422, respectively. The drives and cards and their associated computer readable media provide nonvolatile storage of computer readable instructions, data structures, program modules and other data for the computing system 400.

Although the exemplary environment described herein employs a hard disk drive 413 and a compact flash card 414, it should be appreciated by those skilled in the art that other types of computer-readable media, capable of storing data, can be used in the exemplary system. Examples of these other types of computer-readable mediums include magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, CD ROMS, DVD ROMS, random access memories (RAMs), read only memories (ROMs), and the like. A number of program modules may be stored on the hard disk 413, compact flash card 414, ROM 408, or RAM 410, including an operating system 426, one or more application programs 428, other program modules 430, and program data 432. A user may enter commands and information into the computing system ^■ 400 through an input device 434. Examples of input devices might include a keyboard, mouse, microphone, joystick, game pad, satellite dish, scanner, digital camera, touch screen, and a telephone. These and other input devices are often connected to the processing unit 402 through an interface 440 that is coupled to the system bus 406. These input devices also might be connected by any number of interfaces, such as a parallel port, serial port, game port, or a universal serial bus (USB). A display device 442, such as a monitor or touch screen LCD panel, is also connected to the system bus 406 via an interface, such as a video adapter 444. The display device 442 might be internal or external. In addition to the display device 442, computing systems, in general, typically include other peripheral devices (not shown), such as speakers, printers, and palm devices.

When used in a LAN networking environment, the computing system 400 is connected to the local network through a network interface or adapter 452. When used in a WAN networking environment, such as the Internet, the computing system 400 typically includes a modem 454 or other means, such as a direct connection, for establishing communications over the wide area network. The modem 454, which can be internal or external, is connected to the system bus 406 via the interface 440. In a networked environment, program modules depicted relative to the computing system 400, or portions thereof, may be stored in a remote memory storage device. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computing systems may be used.

The computing system 400 might also include a recorder 460 connected to the memory 404. The recorder 460 includes a microphone for receiving sound input and is in communication with the memory 404 for buffering and storing the sound input. Preferably, the recorder 460 also includes a record button 461 for activating the microphone and communicating the sound input to the memory 404.

A computing device, such as computing system 400, typically includes at least some form of computer-readable media. Computer readable media can be any available media that can be accessed by the computing system 400. By way of example, and not limitation, computer-readable media might comprise computer storage media and communication media.

Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and that can be accessed by the computing system 400. Communication media typically embodies computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above should also be included within the scope of computer-readable media. Computer-readable media may also be referred to as computer program product.

Figure 5 shows further methods and systems for networked data logging in a possible embodiment of the present disclosure. The system 500 provides collection and storage of data in a test environment, such as an automotive test environment, through use of data collection agents, or data acquisition interfaces. The system 500 The system 500 is generally separated into three phases: a setup phase, a data collection and operation phase, and a termination phase. These phases correspond generally to the steps of the system 100 of Figure 1 ; however, the specific modules described in the various phases of the system 500 are not necessarily required to be executed in the same order (or at all) in the system 100 of Figure 1.

Operational flow within the system 500 instantiates at a start operation 502. The start operation 502 corresponds to initial setup of a test environment, such as the automotive test environment exemplified in Figure 2, above, including a plurality of computing systems, vehicle communication interfaces, and electronic control units interconnected via communication links. Operational flow proceeds to an interface generation module 502. The interface generation module 502 establishes interfaces at which data will be logged. The interface generation module 502 assigns data acquisition agents to one or more interfaces within a test environment. Operational flow proceeds to a data logger linking module 504. The data logger linking modules links the data acquisition agents to the layers and interfaces in the target applications in one or both of the personal computers and vehicle communication interfaces in the test environment for which data logging is desired. The result of the modules 502, 504 dictates the applications and application layers whose communicative output is logged in the • system 500.

Operational flow proceeds to a log initialization module 506. The log initialization module 506 initiates a data logging session, such as by providing a desired location and name for a data repository that will hold the log data. In one possible embodiment, this corresponds to a filename and network location for a log data file. A possible file format is described below in conjunction with Figure 6.

Operational flow proceeds to a system initialization module 508. The system initialization module 508 initiates communications in the test environment, thereby starting the flow of control and data communications in the test environment, which will be logged. In one embodiment, the log initialization module 506 executes prior to the system initialization module 508 to ensure that all system communications are captured by the data logging agents. In a further embodiment, the log initialization module 506 executes after the system initialization module 508, so as to capture communicated data during a desired portion of a communication sequence occurring in the test environment.

Operational flow proceeds to a log module 510. The log module 510 captures all data passing the linked interfaces (from modules 502, 504, above), which is in turn written to the target data repository designated in the log initialization module 506. The log module 10 optionally inserts a timestamp into the target data repository alongside the captured data. The timestamp can be an elapsed time since initialization of the log, and can be inserted with data as it is written to the data repository. The system 500 therefore does not depend on synchronizing of the various components in the test environment. Operational flow proceeds to a completion detection module 512.

The completion detection module 512 detects the end of the sequence to be logged, such as when no additional data is being written to the data repository. Operational flow proceeds to a termination module 514, which terminates the logging session. Operational flow within the system 500 terminates at an end operation 516, corresponding to completion of execution of the data logging system 500.

Figure 6 shows an exemplary log file 600 that can be created using the methods and systems of the present disclosure. The log file 600 as shown is provided in a line delimited, comma separated ASCII format, such that it can be loaded into any of a number of spreadsheet programs or other software applications for further analysis. The log file 600 includes a timestamp, a session identifier, a source identifier, a destination identifier, and the data being transferred from the identified source to the identified destination as part of that session. Other data can be included in the log file as well, based on the specific implementation of the data logging software and the capabilities of the computing systems used. Other data file formats can be used as well.

The various embodiments described above are provided by way of illustration only and should not be construed to limit the invention. Those skilled in the art will readily recognize various modifications and changes that may be made to the present invention without following the example embodiments and applications illustrated and described herein, and without departing from the true spirit and scope of the present invention, which is set forth in the following claims.

Claims

Claims:

1. A method of logging data communicated in a test network, the method comprising: initiating a communication session among one or more applications executing on computing systems distributed through the test network and one or more vehicle communications interfaces in the test network; logging data communicated during the session to a target data repository, the target data repository defined by a name and a location within the test network; and terminating the communication session.

2. The method of claim 1 , wherein the target data repository is a single data file.

3. The method of claim 1 , wherein the test network is an automotive test network.

4. The method of claim 1, further comprising, prior to initiating the communication session, linking a data logger to one or more components in the test network.

5. The method of claim 1, wherein logging data begins prior to initiation of a communication session.

6. The method of claim 1, further comprising, prior to terminating the communication session, detecting completion of data communication among the one or more applications.

7. The method of claim 1, wherein the communication session occurs over one or more sockets assigned among the one or more applications distributed in the test network.

8. The method of claim 1, wherein the communication session exists among one or more computing systems and a vehicle communication interface.

9. The method of claim 8, wherein the vehicle communication interface connects to one or more electronic control units of an automobile.

10. The method of claim 8, wherein the vehicle communication interface initiates the communication session.

11. The method of claim 1 , wherein the target data repository resides on a computing system communicatively connected to the systems executing the one or more applications.

12. A system for of logging data communicated in a test network, the system comprising:

A memory configured to store data logged in the test network; A programmable circuit operatively connected to the memory, the programmable circuit configured to execute program instructions to: initiate of a communication session among one or more applications executing on computing systems distributed through the test network and one or more vehicle communications interfaces in the test network; log data in the memory that is communicated during the session to a target data repository, the target data repository defined by a name and a system location within the test network; and terminate the communication session.

13. The system of claim 12, wherein the target data repository is a single data file.

14. The system of claim 12, wherein the programmable circuit is further programmed to, prior to initiating the communication session, link a data logger to one or more components in the test network.

15. The system of claim 12, wherein the test network is an automotive test network.

16. The system of claim 12, wherein the programmable circuit is programmed to log data prior to initiation of a communication session.

17. The system of claim 12, wherein the programmable circuit is further programmed to, prior to initiating the communication session, link a data logger to one or more components in the test network.

18. The system of claim 12, wherein the target data repository resides on a computing system communicatively connected to the systems executing the one or more applications.

19. The system of claim 12, wherein the communication session exists among one or more computing systems and a vehicle communication interface.

20. The system of claim 12, wherein the vehicle communication interface initiates the communication session.

21. A method of logging data communicated in a test network, the method comprising: linking a data logger to one or more components in an automotive test network; initiating a data logging session; initiating of a communication session among among one or more applications executing on computing systems distributed through the automotive test network and one or more vehicle communications interfaces in the automotive test network. logging data communicated during the session to a target data repository, the target data repository defined by a name and a system location within the test network; detecting completion of data communication among the one or more applications; terminating the communication session.