Method for the diagnosis of driver outputs and diagnosis pulse manager

• US 20060229795A1
• Filed: 07/19/2004
• Published: 10/12/2006
• Est. Priority Date: 07/31/2003
• Status: Abandoned Application

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: Laufer, Andreas, Thiveos, Konstantin
• Application Number:
  US10/566,561
• Publication Number:
  US 20060229795A1
• Time in Patent Office: Days
• US Class Current: 701/114
• CPC Class Codes: G01R 31/007 using microprocessors or computers
• CPC Class Codes: G01R 31/31715 Testing of input or output circuits; test of circuitry between the I/C pins and the functional core, e.g. testing of input or output driver, receiver, buffer
• CPC Class Codes: G01R 31/31924 Voltage or current aspects, e.g. driver, receiver

Abstract

The invention relates to a method for the diagnosis of driver outputs (20) and to a diagnosis pulse manager (10) that can supply a pulse to a driver output (20) in order to carry out a diagnosis of said driver output. As a plurality of diagnosis pulses may be required simultaneously for the system requirements (12), a diagnosis pulse requirement register (14) and a diagnosis pulse execution register (16) are provided such that a plurality of simultaneous requirements (12) can be stored. On the basis of the buffering of requirements (12), a plurality of stored pulse requirements can be successively taken into account according to pre-determined rules.

Claims

1-16. -16. (canceled)

17. In a method of diagnosing a driver output, wherein a pulse is fed to the driver output for the purpose of reading out a diagnosis result at the driver output, the improvement which comprises:

storing a requirement of a pulse existing for the driver output;

successively taking into account a plurality of stored requirements in accordance with predetermined rules.

18. The method according to claim 17, which comprises storing a plurality of simultaneously existing requirements.

19. The method according to claim 17, wherein the driver is installed in a motor vehicle.

20. The method according to claim 17, which comprises:

storing the requirements in a diagnosis pulse requirement register as binary values;

transmitting the requirements stored in the diagnosis pulse requirement register into a diagnosis pulse execution register; and

selectively erasing the diagnosis pulse requirement register after the transmission of the requirements into the diagnosis pulse execution register.

21. The method according to claim 20, which comprises transmitting the requirements from the diagnosis pulse requirement register into the diagnosis pulse execution register only if no requirements are stored in the diagnosis pulse execution register.

22. The method according to claim 20, which comprises:

prior to transmitting the requirements from the diagnosis pulse requirement register into the diagnosis pulse execution register, deleting the requirements which are no longer stored in the diagnosis pulse requirement register from the diagnosis pulse execution register.

23. The method according to claim 20, which comprises, after a given requirement stored in the diagnosis pulse execution register has been taken into account, deleting the given requirement from the diagnosis pulse execution register.

24. The method according to claim 17, wherein the predetermined rules are based on at least one of the following criteria:

different driver outputs have a different priority; and

a requirement assigned to a specific driver output may be taken into consideration or not.

25. The method according to claim 24, which comprises defining the priorities of the driver outputs by configuration of a control and prioritization unit.

26. The method according to claim 24, which comprises dynamically adapting the priorities of the driver outputs in accordance with operating states of the motor vehicle.

27. A diagnosis pulse manager for feeding pulses to driver outputs in dependence on system requirements, for the purpose of reading out diagnosis results at driver outputs, the pulse manager comprising:

a diagnosis pulse requirement register for storing an existing requirement of a pulse for a driver output; and

wherein a plurality of stored requirements are able to be taken into account successively in accordance with predetermined rules.

28. The diagnosis pulse manager according to claim 27, wherein said diagnosis pulse requirement register is configured to store a plurality of simultaneously existing requirements.

29. The diagnosis pulse manager according to claim 27 configured for drivers in a motor vehicle.

30. The diagnosis pulse manager according to claim 27, wherein:

said wherein diagnosis pulse requirement register is configured to store the requirements as binary values;

a diagnosis pulse execution register is connected to receive the requirements stored in said diagnosis pulse requirement register; and

said diagnosis pulse requirement register is erased after the requirements have been transferred into said diagnosis pulse execution register.

31. The diagnosis pulse manager according to claim 30, wherein the requirements are transmitted from said diagnosis pulse requirement register into said diagnosis pulse execution register only if no requirements are stored in said diagnosis pulse execution register.

32. The diagnosis pulse manager according to claim 30, wherein, before the requirements are transmitted from said diagnosis pulse requirement register into said diagnosis pulse execution register, requirements that are no longer stored in said diagnosis pulse requirement register are also deleted from said diagnosis pulse execution register.

33. The diagnosis pulse manager according to claim 27, wherein, after a requirement stored in said diagnosis pulse execution register has been taken into account, the requirement is deleted in said diagnosis pulse execution register.

34. The diagnosis pulse manager according to claim 27, wherein the predetermined rules are based on at least one of the following criteria:

different driver outputs have a different priority; and

a requirement assigned to a specific driver output may or may not be taken into consideration.

35. The diagnosis pulse manager according to claim 34, which further comprises a control and prioritization unit configured to define the priorities of the driver outputs.

36. The diagnosis pulse manager according to claim 34, wherein the priorities of the driver outputs are subject to dynamic change in dependence on operating states of the motor vehicle.