METHOD FOR CHECKING A FAULT STATUS OF A MOBILE UTILITY UNIT

Abstract

A method for checking a fault status of a mobile utility unit by a maintenance station includes generating via control electronics status data representing a fault status of the mobile utility unit, storing the status data as fault data in a fault memory via the control electronics, classifying via a data processing unit the fault data under different fault classes to identify an applicable fault class, and initiating via the data processing unit a procedural measure for the mobile utility unit according to the identified fault class.

Claims

1. A method for checking a fault status of a mobile utility unit by a maintenance station, comprising: generating via control electronics status data representing a fault status of the mobile utility unit; storing the status data as fault data in a fault memory via the control electronics; classifying via a data processing unit the fault data under different fault classes to identify an applicable fault class; and initiating via the data processing unit a procedural measure for the mobile utility unit according to the identified fault class.

2. The method as claimed in claim 1, wherein the identified fault class includes one or more of the following: (a) no fault-related work is needed on the mobile utility unit; (b) fault-related work needs to be carried out on the mobile utility unit by the maintenance station; and (c) fault-related work needs to be carried out on the mobile utility unit by maintenance personnel.

3. The method as claimed in claim 1, wherein the procedural measure includes one or more of the following: (a) enabling via the data processing unit the mobile utility unit for further work; (b) performing via the data processing unit an automated measure on the mobile utility unit; and (c) disabling via the data processing unit the mobile utility unit for further work.

4. The method as claimed in claim 1, wherein the maintenance station performs the classifying step.

5. The method as claimed in claim 1, wherein the maintenance station performs the initiating step.

6. The method as claimed in claim 1, wherein the mobile utility unit includes the fault memory and the control electronics.

7. The method as claimed in claim 1, wherein the maintenance station includes the data processing unit.

8. The method as claimed in claim 1, further comprising: transmitting the fault data to the maintenance station via a data interface of the mobile utility unit.

9. The method of claim 8, further comprising: receiving the fault data via a communications interface of the maintenance station.

10. The method as claimed in claim 1, wherein the mobile utility unit includes a utility vehicle.

11. The method as claimed in claim 1, wherein the mobile utility unit includes an agricultural or forestry vehicle.

12. The method as claimed in claim 1, wherein the mobile utility unit includes an autonomous vehicle.

13. A method for checking a fault status of a mobile utility unit by a maintenance station, comprising: generating via control electronics of the mobile utility unit status data representing a fault status of the mobile utility unit; storing the status data as fault data in a fault memory of the mobile utility unit via the control electronics; classifying via a data processing unit of the maintenance station the fault data under different fault classes to identify an applicable fault class; and initiating via the data processing unit a procedural measure for the mobile utility unit according to the identified fault class.

14. The method as claimed in claim 13, wherein the identified fault class includes one or more of the following: (a) no fault-related work is needed on the mobile utility unit; (b) fault-related work needs to be carried out on the mobile utility unit by the maintenance station; and (c) fault-related work needs to be carried out on the mobile utility unit by maintenance personnel.

15. The method as claimed in claim 13, wherein the procedural measure includes one or more of the following: (a) enabling via the data processing unit the mobile utility unit for further work; (b) performing via the data processing unit an automated measure on the mobile utility unit; and (c) disabling via the data processing unit the mobile utility unit for further work.

16. The method as claimed in claim 13, further comprising: transmitting the fault data to the maintenance station via a data interface of the mobile utility unit; and receiving the fault data via a communications interface of the maintenance station.

17. A method for checking a fault status of a mobile utility unit by a maintenance station, comprising: generating via control electronics of the mobile utility unit status data representing a fault status of the mobile utility unit; storing the status data as fault data in a fault memory via the control electronics; classifying via a data processing unit of the maintenance station the fault data under different fault classes to identify an applicable fault class, the identified fault class including one or more of the following: (a) no fault-related work is needed on the mobile utility unit, (b) fault-related work needs to be carried out on the mobile utility unit by the maintenance station, and (c) fault-related work needs to be carried out on the mobile utility unit by maintenance personnel; initiating via the data processing unit a procedural measure for the mobile utility unit according to the identified fault class, the procedural measure including one or more of the following: (a) enabling via the data processing unit the mobile utility unit for further work, (b) performing via the data processing unit an automated measure on the mobile utility unit, and (c) disabling via the data processing unit the mobile utility unit for further work; transmitting the fault data to the maintenance station via a data interface of the mobile utility unit; and receiving the fault data via a communications interface of the maintenance station.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The above-mentioned aspects of the present disclosure and the manner of obtaining them will become more apparent and the disclosure itself will be better understood by reference to the following description of the embodiments of the disclosure, taken in conjunction with the accompanying drawing, wherein:

[0035] The FIGURE is a schematic of a mobile utility unit and a maintenance station.

[0036] Corresponding reference numerals are used to indicate corresponding parts in the drawings.

DETAILED DESCRIPTION

[0037] The embodiments of the present disclosure described below are not intended to be exhaustive or to limit the disclosure to the precise forms disclosed in the following detailed description. Rather, the embodiments are chosen and described so that others skilled in the art may appreciate and understand the principles and practices of the present disclosure.

[0038] FIG. 1 shows schematically a mobile utility unit 10 and a maintenance station 12, which is external to the utility unit 10. The maintenance station 12 is used for maintaining the utility unit 10, in particular for checking a fault status of the utility unit 10. Various method steps of the method for checking the fault status are presented in the form of a flow diagram in FIG. 1.

[0039] The mobile utility unit 10 is a utility vehicle, for example, in particular a tractor. The utility unit 10 is brought, either by a driver or as an autonomous or semi-autonomous vehicle without a driver, to the maintenance station 12 for maintenance and in particular for checking a fault status.

[0040] Various fault statuses stat_F are detected, and corresponding status data D_stat is generated, in the utility unit 10 (for instance, using suitable control electronics). This status data D_stat is stored (after optional further processing) as fault data D_F in a fault memory 14 of the utility unit 10.

[0041] The utility unit 10 has a data interface 16 for transmitting the fault data D_F to the maintenance station 12. The transmission of the fault data D_F is requested by a data-communications mechanism, for instance by the maintenance station 12. The latter has a communications interface 18, which receives the transmitted fault data D_F and, if applicable, also deals with further data transfer.

[0042] The communications interface 18 is connected to a data processing unit 20, in which the received fault data D_F is classified under different provided fault classes F1, F2, F3. This classification is used to identify the fault class F1 or F2 or F3 that applies to the particular fault data D_F. The processing unit 20 comprises for the purpose of analyzing, assessing and classifying the fault data D_F corresponding functionalities, for instance a microprocessor, a memory and/or a database and suitable algorithms.

[0043] The maintenance station 12 initiates at least one procedural measure according to the identified fault class F1, F2, F3. The exemplary embodiment discloses a total of four different procedural measures M1, M2, M3, and M4.

[0044] The identification of fault class F1 means that no fault-related work is needed on the utility unit 10, i.e., the fault status stat_F is not critical. Therefore, the maintenance station 12 initiates a procedural measure M1, as a result of which the maintenance unit 12 enables the utility unit 10 for further work, for instance by sending specific control signals to the utility unit 10.

[0045] In the case of fault class F2 being identified, fault-related work needs to be carried out on the utility unit 10 by the maintenance station 12. The maintenance station 12 then initiates the procedural measure M2, according to which the fault status stat_F is handled in the maintenance station 12 or by the maintenance station 12, for instance topping up a (operating) fluid level, cleaning any sensors, increasing a tire pressure.

[0046] If fault class F3) is identified as applicable, maintenance personnel are required. The fault status stat_F then cannot be handled solely by the maintenance station 12. Therefore the maintenance station 12 initiates first the procedural measure M3, according to which any further work by the utility unit 10 is disabled (for instance by suitable control signals to the utility unit 10). This disabling can be cleared again by maintenance personnel as part of the fault-related work on the utility unit 10. In addition, the maintenance station 12 initiates a procedural measure M4, which results in specific information M_info being output. This information M_info is output for instance visually or audibly via an indicator unit, and is aimed at relevant people, for example, drivers, users, maintenance personnel. The information M_info includes an indication of the necessary fault-related work on the utility unit 10 by maintenance personnel.

[0047] While embodiments incorporating the principles of the present disclosure have been disclosed hereinabove, the present disclosure is not limited to the disclosed embodiments. Instead, this application is intended to cover any variations, uses, or adaptations of the disclosure using its general principles. Further, this application is intended to cover such departures from the present disclosure as come within known or customary practice in the art to which this disclosure pertains and which fall within the limits of the appended claims.