Multi-point electronic control system protocol

• US 7,529,268 B1
• Filed: 09/27/2002
• Issued: 05/05/2009
• Est. Priority Date: 09/27/2001
• Status: Expired due to Fees

• Current Assignee: Hamilton Sundstrand Corporation (Raytheon Technologies Corporation d/b/a RTX)
• Original Assignee: Hamilton Sundstrand Corporation (Raytheon Technologies Corporation d/b/a RTX)
• Inventors: Solanki, Vijaykumar J.
• Primary Examiner(s): Moe; Aung S
• Assistant Examiner(s): Mered; Habte
• Application Number:
  US10/256,668
• Time in Patent Office: 2,412 Days
• Field of Search: 370/465, 370470-476, 370/252, 370/362, 370449-451, 370/462, 710/15, 710107-125, 710305-310, 710/45, 709208-211
• US Class Current: 370/462
• CPC Class Codes: H04L 12/403 with centralised control, e.g. polling

Abstract

A generic software protocol allows communication between multiple devices within an electronic control system as well as between an electronic control system and an external monitoring device. The generic software protocol is reflected in embedded software in each device in the electronic control system. By using the same protocol in all of the electronic control system devices, the protocol reduces computer processing overhead while providing a predictable, yet flexible framework for device communication.

Claims

1. An electronic control system having a plurality of devices and connected to a communication interface, comprising:

a source device identifier indicating a source device sending a command record;

a destination device identifier indicating a destination device receiving the command record;

a command description containing a command code corresponding to a message from the source device to the destination device; and

a message type identifier indicating that the command record is a control request, the control request including a bus master request that asks the destination device to assume control over the communication interface,

wherein all of said plurality of devices connected to the communication interface use the communication protocol to communicate with each other via the communication interface,

wherein the destination device acting as the bus master sends the bus master request to another one of said plurality of devices after a predetermined time period.

2. The communication protocol of claim 1, wherein the command description further comprises at least one from the group consisting of:

a command data length field; and

a data byte field, wherein the command data length field indicates a length of the data byte field.

3. The communication protocol of claim 2, wherein the data byte field contains at least one selected from the group consisting of a memory location, a data block size, data to be written to the memory location, status information, a custom command, a buffer identification, a fill character, a number of byte pages, cyclical redundancy check data, variable data, and a number of transmissions.

7. The communication protocol of claim 1, wherein each device in the electronic control system receives a unique identifier for use as a source device identifier and as a destination device identifier.

8. The communication protocol of claim 1, wherein a device assumes control over the communication interface from a bus master only long enough for the device to send a current command.

4. An electronic control system, comprising:

an electronic control unit;

a memory module; and

a user interface, wherein the electronic control unit, the memory module, and the user interface are connected to a communication interface and communicate with each other via the communication interface using embedded software that implements a communication protocol, the communication protocol comprising

a source device identifier indicating a source device sending a command record;

a destination device identifier indicating a destination device receiving the command record; and

a command description containing a command code corresponding to a message from the source device to the destination device,

wherein devices other than the electronic control unit may obtain bus master status by accepting a bus master request from another device.

5. The electronic control system of claim 4, wherein the electronic control unit, the memory module, and the user interface exchange control over the communication interface when the command record is a bus master request.

6. The electronic control system of claim 5, wherein the electronic control unit exchanges control over the communication interface with the memory module, the user interface, or another device only long enough for the memory module, user interface, or other device to send a current command.

9. The electronic control system of claim 4, wherein when the electronic control system powers up the electronic control unit is automatically granted a bus master status.

10. The electronic control system of claim 4, wherein when a device has a bus master status all other devices in the electronic control system have a slave status.

11. The electronic control system of claim 10, wherein the electronic control unit, the memory module, and the user interface are devices.

12. The electronic control system of claim 4, wherein the electronic control unit will only accept a bus master request if a bus resource is required.

13. The electronic control system of claim 4, wherein the electronic control unit will reject a bus master request and reset an internal timer if a bus resource is not required.

14. The electronic control system of claim 4, wherein the electronic control unit will automatically assume bus master status if it does not receive a bus master request within a predetermined amount of time.