Data communication system and method for communicating data in a vehicle

#Certain vehicles (e.g., powered vehicles or vehicle consists) include communication systems that periodically obtain measurements related to the health, operations, or control of the vehicle. For example, locomotives in a rail vehicle consist (“consist” referring to a group of vehicles linked to travel together along a route, including possible coordinated control by one or more wired and/or wireless connections) may include communication systems that periodically receive measurements related to operations of the locomotive, such as speed, horsepower, temperature, brake pressure measurements, and the like. These measurements represent data parameters of the vehicle, and the values of the data parameters may periodically change. For example, measurements of speed of a traction motor may be a first data parameter, measurements of brake pressures may be a second data parameter, and so on.

#The values of the data parameters may be requested and used by computerized services or applications running on the vehicle and/or running off-board the vehicle. These services or applications perform various functions based on the data parameters. For example, the services or applications may control tractive operations and/or braking operations of the vehicle, monitor performance of the vehicle over time, record events of the vehicle, and the like. The systems that acquire the data parameters and that are native to the vehicle, such as the systems that are initially installed in the vehicle, may use a communication protocol to form and communicate data messages that include the values of the data parameters. Other services or applications may use a different communication protocol that uses a different format to communicate and/or use the data messages that include the data parameters.

#The different protocols used to communicate with the various systems, services, and applications can require different communication configurations to be used. For example, in order for a single device to communicate with systems, services, and/or applications using different communication protocols, the single device may need to have different communication configurations stored thereon. The communication configurations can dictate the rules and criteria used for communicating with the systems, services, and/or applications according to the different protocols.

#FIG. 1 is a schematic diagram of one embodiment of a vehicle data communication system disposed on-board a powered vehicle.

#FIG. 2 is a schematic diagram of an interface gateway device shown in FIG. 1 in accordance with one embodiment.

#FIG. 3 is another schematic illustration of the interface gateway device shown in FIG. 1 in accordance with one embodiment.

#The foregoing brief description, as well as the following detailed description of certain embodiments of the inventive subject matter, will be better understood when read in conjunction with the appended drawings. To the extent that the figures illustrate diagrams of the functional blocks of various embodiments, the functional blocks are not necessarily indicative of the division between hardware circuitry. Thus, for example, one or more of the functional blocks (for example, processors or memories) may be implemented in a single piece of hardware (for example, a general purpose signal processor, microcontroller, random access memory, hard disk, and the like). Similarly, the programs may be stand alone programs, may be incorporated as subroutines in an operating system, may be functions in an installed software package, and the like. The various embodiments are not limited to the arrangements and instrumentality shown in the drawings.

#As used herein, an element or step recited in the singular and proceeded with the word “a” or “an” should be understood as not excluding plural of said elements or steps, unless such exclusion is explicitly stated. Furthermore, references to “one embodiment” of the present inventive subject matter are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the recited features. Moreover, unless explicitly stated to the contrary, embodiments “comprising” or “having” an element or a plurality of elements having a particular property may include additional such elements not having that property.

#FIG. 1 is a schematic diagram of one embodiment of a vehicle data communication system 100 disposed on-board a powered vehicle 102. In the illustrated embodiment, the vehicle 102 is illustrated as a rail vehicle, such as a locomotive. Alternatively, the vehicle 102 may be another type of rail vehicle (such as a non-powered cargo car) or a non-rail vehicle, such as a different type of off-highway vehicle (OHV) or other vehicle. The system 100 is shown in FIG. 1 as being disposed entirely on-board the single vehicle 102. Alternatively, the system 100 may be distributed among several interconnected vehicles, such as by being partially disposed on each of several vehicles that include the vehicle 102 and that are mechanically coupled in a consist or other group.