Device and method for monitoring a genset using a controller area network bus interface

• US 20040010349A1
• Filed: 07/12/2002
• Published: 01/15/2004
• Est. Priority Date: 07/12/2002
• Status: Abandoned Application

• Current Assignee: Basler Electric Company
• Original Assignee: Basler Electric Company
• Inventors: Rodriguez, Miguel, Allen, Bruce, Compare, Fabio, Perez, Larry, Malone, Doug
• Application Number:
  US10/194,695
• Publication Number:
  US 20040010349A1
• Time in Patent Office: Days
• US Class Current: 700/287
• CPC Class Codes: H02P 9/02 Details of the control

Abstract

A genset monitoring and control device that interactively monitors and can control a genset having an internal network over which engine data is communicated is implemented with a network interface for coupling with the genset'"'"'s internal network to receive engine data therefrom and pass data and commands thereover. The genset monitoring and control device'"'"'s processor uses the engine data received directly from the genset'"'"'s internal network via the network interface to control and monitor the operation of the genset. Also, the genset monitoring and control device can request various engine data from the genset'"'"'s internal network, and command new data to be collected in response to a command. The internal network is preferably a controller area network (CAN), and the engine data is preferably communicated on the CAN in the SAE J1939 messaging protocol.

Claims

1. A device for monitoring and controlling a genset, said genset having an internal network over which engine data is communicated, said device comprising:

a network interface for coupling with said internal network to receive said engine data therefrom; and

a processor in communication with said network interface that is configured to process said received engine data to thereby control and monitor the operation of said genset.

2. The device of claim 1 wherein said internal network is a controller area network (CAN), wherein said CAN has a bus on which said engine data is communicated, and wherein said network interface is a CAN receiver for coupling with said CAN bus to receive said engine data therefrom.

3. The device of claim 2 wherein said engine data is communicated on said CAN bus as at least one message frame, and wherein said processor is programmed with a software module configured to (1) extract said engine data from said at least one message frame, and (2) process said extracted engine data to thereby control and monitor the operation of said genset.

4. The device of claim 3 wherein said at least one message frame is formatted according to a higher layer protocol (HLP), and wherein said software module is also configured to extract said engine data from said at least one message frame in accordance with said HLP.

5. The device of claim 4 wherein said HLP is a J1939 protocol.

6. The device of claim 5 wherein said engine data comprises a value for an engine parameter, said engine parameter being any of the group consisting of battery voltage, coolant level, coolant temperature, crank case pressure, operating hours, revolutions per minute (RPMs), turbo boost pressure, fuel consumption, fuel delivery pressure, fuel filter differential pressure, fuel consumption rate, oil filter differential pressure, oil pressure, oil temperature, and percent engine load.

7. The device of claim 6 wherein said engine data further comprises at least one diagnostic trouble code (DTC), each DTC being indicative of a problematic condition of said engine.

8. The device of claim 7 wherein said engine is configured to respond to a request for engine data by communicating said requested engine data on said CAN bus, wherein said CAN receiver is a CAN transceiver for coupling with said CAN bus to receive said engine data therefrom and transmit a request for engine data thereto, and wherein said processor is also configured to communicate a request for engine data to said CAN transceiver for subsequent transmission on said CAN bus.

9. The device of claim 8 further comprising a display in communication with said processor and at least one input in communication with said processor that is configured for a user to select at least a portion of said engine data to be displayed on said display, and wherein said software module is also configured to provide said selected engine data to said display for display thereon.

10. The device of claim 9 wherein said device input is also operable for a user to initiate a request for engine data, said software module also being configured to create at least one J1939 message frame that includes said engine data request and provide that at least one J1939 message frame to said CAN transceiver for transmission on said CAN bus.

11. The device of claim 10 wherein said engine data request is a request for at least one engine parameter value.

12. The device of claim 10 wherein said engine data request is a request for at least one currently active DTC.

13. The device of claim 10 wherein said engine data request is a request for at least one previously active DTC.

14. The device of claim 10 wherein said processor has a plurality of threshold alarm values stored therein, each threshold alarm value having a corresponding engine parameter, and wherein said software module is also configured to (1) determine whether an alarm condition exists by comparing an extracted value for an engine parameter with that engine parameter'"'"'s corresponding stored threshold alarm value, and (2) if an alarm condition is determined to exist, provide a signal to said display that is operative to indicate the existence of said determined alarm condition.

15. The device of claim 14 wherein said processor has a plurality of threshold pre-alarm values stored therein, each threshold pre-alarm value having a corresponding engine parameter, and wherein said software module is also configured to (1) determine whether a pre-alarm condition exists by comparing an extracted value for a engine parameter with that engine parameter'"'"'s corresponding stored threshold pre-alarm value, and (2) if a pre-alarm condition is determined to exist, provide a signal to said display that is operative to indicate the existence of said determined pre-alarm condition.

16. The device of claim 10 further comprising a communications device in communication with said processor that is configured to communicate at least a portion of said extracted engine data to a peripheral device.

17. The device of claim 16 wherein said extracted engine data of which at least a portion is communicated to said peripheral device is at least one DTC.

18. The device of claim 16 wherein said peripheral device is a computer having software stored thereon that is executable to (1) receive and process said extracted engine data communicated thereto by said communications device, said computer including a display for displaying at least a portion of said extracted engine data communicated thereto.

19. The device of claim 18 wherein said software stored on said computer is also executable to (1) receive and process a request for engine data from a user, and (2) communicate said engine data request to said processor by way of said communications device, said software module also being configured to create at least one J1939 message frame that includes said engine data request and provide that at least one J1939 message frame to said CAN transceiver for transmission on said CAN bus.

20. The device of claim 5 wherein said software module is configurable to process a message frame formatted in any of a plurality of message profiles for said J1939 protocol.

21. The device of claim 6 wherein said software module is also configured to invoke a failsoft function for an engine parameter in the event that a message frame for that engine parameter is not received within a configurable interval of time, said failsoft function being operable to set a value for that engine parameter.

22. A method of controlling and monitoring the operation of a genset, said genset having an internal network over which engine data is transmitted, said engine data being indicative of how said genset is operating, said method comprising:

interfacing with said internal network of said genset;

receiving engine data transmitted on said internal network; and

processing said received engine data to thereby control and monitor the

operation of said genset.

23. The method of claim 22 wherein said internal network is a controller area network (CAN) having a CAN bus on which said engine data is transmitted, and wherein said interfacing step includes interfacing with said CAN bus.

24. The method of claim 23 wherein said receiving step includes receiving a value for an engine parameter, said engine parameter being a member of the group consisting of battery voltage, coolant level, coolant temperature, crank case pressure, operating hours, revolutions per minute (RPMs), turbo boost pressure, fuel consumption, fuel delivery pressure, fuel filter differential pressure, fuel consumption rate, oil filter differential pressure, oil pressure, oil temperature, and percent engine load.

25. The method of claim 24 wherein said receiving step includes receiving a diagnostic trouble code (DTC), said DTC being indicative of a problematic condition of said engine.

26. The method of claim 25 wherein said DTC receiving step includes receiving a list of currently active DTCs.

27. The method of claim 26 wherein said DTC receiving step also includes receiving a list of previously active DTCs.

28. The method of claim 27 wherein said engine data is transmitted on said CAN bus as at least one message frame formatted in a J1939 protocol, and wherein said processing step includes extracting said engine data from said at least one J1939 message frame.

29. The method of claim 28 wherein said processing step further includes:

retrieving a stored threshold alarm value that corresponds to an engine parameter; and

determining whether an alarm condition exists by comparing said stored threshold alarm value for a particular engine parameter with that engine parameter'"'"'s value that is extracted from a J1939 message frame.

30. The method of claim 29 wherein said processing step further includes:

retrieving a stored threshold pre-alarm value that corresponds to an engine parameter; and

determining whether a pre-alarm condition exists by comparing said stored threshold pre-alarm value for a particular engine parameter with that engine parameter'"'"'s value that is extracted from a J1939 message frame.

31. The method of claim 28 wherein said processing step further includes:

receiving input from a user that corresponds to a selection of a particular engine parameter value for display; and

displaying said selected engine parameter value on a display.

32. The method of claim 31 wherein said processing step further includes:

receiving input from a user that corresponds to a selection of a currently active DTC for display; and

displaying said selected currently active DTC on a display.

33. The method of claim 32 wherein said processing step further includes:

receiving input from a user that corresponds to a selection of a previously active DTC for display; and

displaying said selected previously active DTC on a display.

34. The method of claim 28 further comprising:

receiving input from a user that corresponds to a request for engine data;

formatting said engine data request according to said J1939 protocol to thereby create a J1939 request message frame

transmitting said request message frame on said CAN bus; and

receiving said requested engine data via said CAN bus.

35. The method of claim 34 wherein said engine data request is a request for a value of an engine parameter.

36. The method of claim 34 wherein said engine data request is a request for a list of currently active DTCs.

37. The method of claim 34 wherein said engine data request is a request for a list of previously active DTCs.

38. The method of claim 28 wherein said engine data is transmitted on said CAN bus as at least one message frame formatted in any of a plurality of messaging profiles for said J1939 protocol, and wherein said processing step further includes selecting a configuration profile that identifies said J1939 protocol messaging profile used by said engine and extracting said engine data from said at least one J1939 message frame in accordance with said selected configuration profile.

39. The method of claim 28 further comprising:

interfacing with a peripheral device; and

communicating at least a portion of said extracted engine data to said peripheral device.

40. The method of claim 39 wherein said extracted engine data of which at least a portion is communicated to said peripheral device is at least one DTC.

41. The method of claim 39 further comprising:

receiving input from said peripheral device that corresponds to a request for engine data;

transmitting said request for engine data on said CAN bus; and

receiving said requested engine data via said CAN bus.

42. The method of claim 28 further comprising:

receiving input from a user that corresponds to a request to clear at least one of the group consisting of said list of currently active DTCs and said list of previously active DTCs;

formatting said DTC clear request according to said J1939 protocol to thereby create a J1939 request message frame;

transmitting said request message frame on said CAN bus.

43. The method of claim 28 further comprising:

tracking an amount of time between receipt of successive message frames for a particular engine parameter; and

performing a failsoft function for that particular engine parameter if the amount off time between receipt of successive message frames for that particular engine parameter exceeds a configurable threshold value.

44. A device for coupling with, and controlling and monitoring a genset, said genset having an engine control module (ECM) that transmits a plurality of message frames on a controller area network (CAN) bus, said message frames being formatted according to a J1939 protocol and containing engine data therein, said engine data being indicative of how said engine is operating, said device comprising:

a CAN bus interface for coupling with said CAN bus and configured to receive said message frames transmitted thereon; and

a processor in communication with said CAN bus interface and configured to extract said engine data from said received message frames and process said extracted engine data to thereby monitor said engine.

45. The device of claim 44 wherein said ECM is also responsive to a request for engine data by transmitting at least one message frame that contains said requested engine data on said CAN bus, wherein said processor is further configured to (1) receive input from a user that corresponds to a request for engine data, (2) convert said received engine data request into a J1939 message frame that contains said engine data request, and (3) provide that J1939 message frame to said CAN bus interface for transmission on said CAN bus, and wherein said CAN bus interface is also configured to transmit a J1939 message frame that contains a request for engine data on said CAN bus.

46. The device of claim 45 wherein said engine data comprises at least one value for at least one engine parameter, each engine parameter being a member of the group consisting of battery voltage, coolant level, coolant temperature, crank case pressure, engine operating hours, revolutions per minute (RPMs), turbo boost pressure, fuel consumption, fuel delivery pressure, fuel filter differential pressure, fuel consumption rate, oil filter differential pressure, oil pressure, oil temperature, and percent engine load.

47. The device of claim 45 wherein said engine data comprises at least one diagnostic trouble code (DTC), said DTC being indicative of a problematic condition of said engine.

48. The device of claim 47 wherein said engine data comprises a list of currently active DTCs.

49. The device of claim 47 wherein said engine data comprises a list of previously active DTCs.

50. A system for controlling and monitoring the operation of a genset, said system comprising:

an engine having an internal network over which engine data is broadcast;

a genset monitoring and control device for coupling with said internal network to receive said engine data broadcast thereon and processing said received engine data to thereby monitor the operation of said genset.

51. The system of claim 50 wherein said internal network is a controller area network (CAN), said CAN having a bus on which said genset monitoring and control device comprises a CAN bus interface for coupling with said CAN bus to receive said engine data and a processor in communication with said CAN bus for processing said received engine data to thereby monitor the operation of said genset.

52. The system of claim 51 wherein said engine data is broadcast on said CAN bus as a plurality of CAN message frames formatted according to a J1939 protocol, and wherein said processor is further configured to extract said engine data from said message frames.

53. The system of claim 52 wherein said genset monitoring and control device is further configured to transmit a message frame on said CAN bus containing a request for engine data from said genset.

54. A device for interactively monitoring and operating at least one genset, said at least one genset having an internal network over which engine data is communicated to and from an ECM, said ECM being associated with it'"'"'s own genset, said device comprising:

a network interface for coupling with said internal network to receive said engine data and to transmit commands thereover to and receive engine data from said ECM; and

a processor in communication with said network interface, said processor being configured to process received engine data to thereby monitor the operation of said genset and transmit commands to said ECM for collection of engine data and control of genset operation.

55. The device of claim 54 wherein said device further comprises a remote connection port, said remote connection port being configured to support transmissions of data and commands between said device and a remote controller.

56. The device of claim 55 wherein said remote controller comprises a PC, said PC being programmed to control the device and thereby permit remote interactive monitoring and control of said at least one genset.

57. The device of claim 56 wherein said internal network is a controller area network (CAN), wherein said CAN has a bus on which said engine data and commands are communicated, and wherein said network interface is a CAN receiver for coupling with said CAN bus to receive said engine data therefrom.

58. A method of interactively monitoring and controlling the operation of a genset, said genset having an internal network over which engine data and commands are transmitted, said engine data being indicative of how said genset is operating and said commands being for operation of said genset, said method comprising:

interfacing with said internal network of said genset;

receiving engine data transmitted on said internal network;

transmitting requests for engine data over said internal network; and

processing said received engine data to thereby monitor and control the operation of said genset.

59. The method of claim 58 further comprising providing a remotely located PC, said PC being programmed to connect to and operate said device.

60. The method of claim 59 wherein the step of transmitting commands includes transmitting commands to start up and run said genset.

61. The method of claim 58 wherein said internal network is a controller area network (CAN) having a CAN bus on which said engine data is transmitted, and wherein said interfacing step includes interfacing with said CAN bus.

62. The method of claim 61 wherein said genset includes an ECM, and wherein said commands include powering on said ECM to thereby collect data.

63. The method of claim 62 wherein said outputs include starting and running the genset.

64. The method of claim 62 further comprising providing a remotely located PC, said PC being programmed to connect to and operate said device.

65. A device for interactively monitoring and controlling a genset, said genset having an ECM networked therewith via a CAN bus, said device including a processor connected to the CAN bus, said processor having a remote communications port for transmitting and receiving data from a remote PC, said PC being programmed to operate the device and thereby provide for remote control and monitoring of said genset, said device being configured to power up said ECM to thereby operate said genset and demand data collection.

66. The device of claim 65 wherein said ECM produces engine data corresponding to engine parameter values, and wherein said device is configured to process said engine data and perform actions in response thereto.