Work machine

Abstract

To provide a work machine capable of appropriately notifying the status of optional equipment.SOLUTION: When a work machine receives status information from a standard equipment or an optional equipment, and when the set value of a first parameter included in the status information is registered in a setting table (S11: Yes), an alarm device is caused to notify the status indicated by the status information at a notification level set in the setting table in correspondence with the set value (S12), and if the set value of the first parameter included in the status information is not registered in the setting table (S11: No), the alarm device is caused to notify the status indicated by the status information at a notification level set in a notification level table in correspondence with a set value of a second parameter included in the status information (S14).SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] The present invention relates to a work machine to which optional equipment can be attached or detached. [Background technology]

[0002] 2. Description of the Related Art There have been known working machines to which optional equipment (e.g., extension attachments, extension levers) can be attached or detached in place of or in addition to standard equipment (e.g., engines, hydraulic pumps, standard attachments, standard levers) that are installed as standard.

[0003] In such a work machine, a technology has been disclosed in which, when an optional device is attached, information about the optional device is stored in a memory, and an abnormality in the optional device is notified based on the information stored in the memory (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2013-151786 A Summary of the Invention [Problem to be solved by the invention]

[0005] The technology of Patent Document 1 assumes that optional equipment is provided by the work machine manufacturer itself. However, for optional equipment provided by manufacturers other than the work machine manufacturer (i.e., third parties), it is difficult to collect information on the optional equipment in advance, which poses a problem that it is difficult to appropriately determine and report the importance of an abnormality.

[0006] The present invention has been made in consideration of the above-mentioned circumstances, and has an object to provide a work machine that is capable of appropriately notifying the status of optional equipment. [Means for solving the problem]

[0007] In order to achieve the above object, the present invention provides a working machine which is equipped with standard equipment as standard, an alarm device which notifies information, and a main controller which causes the alarm device to notify the status of the equipment indicated by status information, and in which optional equipment different from the standard equipment can be attached / detached, the status information includes a first parameter and a second parameter which comply with a predetermined communication protocol, and the main controller has a memory which stores a main setting table in which an alarm level by the alarm device is set in correspondence with each setting value of the first parameter which can be set in the status information transmitted by the standard equipment, and an alarm level table in which the alarm level is set in correspondence with each setting value which can be set in the second parameter, and the main controller comprises: When the main controller receives the status information from the standard device or the optional device, and if the setting value of the first parameter included in the status information is registered in the main setting table, the main controller causes the alarm device to notify the status indicated by the status information at the alarm level set in the main setting table in correspondence with the setting value, and when the main controller receives the status information from the standard device or the optional device, and if the setting value of the first parameter included in the status information is not registered in the main setting table, the main controller causes the alarm device to notify the status indicated by the status information at the alarm level set in the alarm level table in correspondence with the setting value of the second parameter included in the status information. Effect of the Invention

[0008] According to the present invention, it is possible to appropriately notify the status of an optional device. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0009] [Figure 1] FIG. 2 is a side view of the hydraulic excavator. [Diagram 2] FIG. 1 is a hardware configuration diagram of a hydraulic excavator equipped with only standard equipment. [Diagram 3] FIG. 1 is a hardware configuration diagram of a hydraulic excavator equipped with optional equipment. [Figure 4] FIG. 13 is a diagram showing a data layout of state information. [Diagram 5] FIG. 13 is a diagram showing the setting values ​​of a failure type, a device name, and a source controller. [Figure 6] 13 is a data example of this setting table. [Figure 7] 13 shows examples of data in a notification method table (A), a notification level table (B), and a provisional setting table (C). [Figure 8] 4 is a flowchart of a notification control process. [Figure 9] 13 is a flowchart of a level update process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] [Configuration of hydraulic excavator 1] An embodiment of a hydraulic excavator 1 (working machine) according to the present invention will be described with reference to the drawings. However, specific examples of the working machine are not limited to the hydraulic excavator 1, and may be any machine capable of attaching and detaching optional equipment in addition to standard equipment, such as a wheel loader, a dump truck, or a crane vehicle. Furthermore, in this specification, front, back, left, and right are based on the viewpoint of an operator who is riding on and operating the hydraulic excavator 1, unless otherwise specified.

[0011] Fig. 1 is a side view of a hydraulic excavator 1. Fig. 2 is a hardware configuration diagram of the hydraulic excavator 1 equipped with only standard equipment. As shown in Fig. 1, the hydraulic excavator 1 includes a lower traveling body 2 and an upper rotating body 3 supported by the lower traveling body 2. The lower traveling body 2 and the upper rotating body 3 are examples of a vehicle body.

[0012] The lower traveling body 2 includes a pair of left and right crawlers 4 which are endless tracks. The pair of left and right crawlers 4 rotate independently when driven by a traveling motor 5. As a result, the hydraulic excavator 1 travels. However, the lower traveling body 2 may be of a wheeled type instead of the crawlers 4.

[0013] The upper rotating body 3 is supported on the lower traveling body 2 so as to be rotatable by a swing motor 6. That is, the upper rotating body 3 swings relative to the lower traveling body 2 as the swing motor 6 rotates. The upper rotating body 3 mainly includes a swing frame 7 serving as a base, a cab (operator's seat) 8 disposed on the front left side of the swing frame 7, a counterweight 9 disposed at the rear of the swing frame 7, and a front work machine 10 (working device) attached to the front center of the swing frame 7 so as to be rotatable in the vertical direction.

[0014] The cab 8 is disposed adjacent to the front working implement 10 in the left-right direction (width direction of the vehicle body). More specifically, the cab 8 is disposed to the left of the front working implement 10 (one side in the left-right direction). However, the location of the cab 8 is not limited to the example described above, and the cab 8 may be disposed on one side of the front working implement 10 in the left-right direction.

[0015] The cab 8 defines a space for an operator to ride in and operate the hydraulic excavator 1. Inside the cab 8, there are arranged a seat for the operator to sit on, an alarm device 41 for notifying the operator seated on the seat of information, and a standard operating device 42 to be operated by the operator seated on the seat.

[0016] The notification device 41 is an example of a notification device that notifies information to an operator in the cab 8. A specific example of the notification device 41 is not particularly limited, and may be, for example, a display that displays information (video, image, message), a speaker that outputs voice or warning sound, or a lit or blinking LED lamp.

[0017] The standard operating device 42 receives operations by the operator for operating the hydraulic excavator 1. When the operator operates the standard operating device 42, standard equipment described below operates (for example, the lower traveling body 2 travels, the upper rotating body 3 rotates, and the front working implement 10 operates). Specific examples of the standard operating device 42 include a lever, a steering wheel, and a pedal.

[0018] The front working implement 10 includes a boom 11 supported on the upper rotating body 3 so as to be able to be raised and lowered, an arm 12 supported at the tip of the boom 11 so as to be able to rotate (crowd, dump), a bucket 13 (standard attachment) supported at the tip of the arm 12 so as to be able to rotate (crowd, dump), a boom cylinder 14 that drives the boom 11, an arm cylinder 15 that drives the arm 12, and a bucket cylinder 16 that drives the bucket 13. Note that specific examples of the standard attachment are not limited to the bucket 13, and may include a grapple, cutter, crusher, breaker, etc. The counterweight 9 is used to balance the weight with the front working implement 10, and is a heavy object that has an arc shape when viewed from above.

[0019] 2, the hydraulic excavator 1 includes a communication device 51. The communication device 51 is a device that communicates with an external device (not shown) through a communication line (for example, the Internet or a public line). The communication device 51 is also an example of a notification device that notifies information to a manager who manages the hydraulic excavator 1.

[0020] 2, the hydraulic excavator 1 is equipped with an engine 61. The engine 61 burns, for example, fossil fuel to generate driving force for driving the hydraulic excavator 1. The hydraulic excavator 1 is also equipped with a rotation speed sensor 62 that detects the rotation speed of the engine 61, and a temperature sensor 63 that detects the temperature of a coolant that cools the engine 61.

[0021] Although not shown, the hydraulic excavator 1 may also include a hydraulic pump that pumps hydraulic oil using the driving force of the engine 61, a generator that generates electricity using the driving force of the engine 61, a battery that stores the electricity generated by the generator, an aftertreatment device that purifies exhaust gas discharged from the engine 61, an air conditioning device that adjusts the temperature inside the cab 8, and the like. Furthermore, although not shown, the hydraulic excavator 1 may also include a pressure sensor that detects the pressure of hydraulic oil supplied to hydraulic equipment (for example, the travel motor 5, the swing motor 6, the boom cylinder 14, the arm cylinder 15, the bucket cylinder 16, and the hydraulic pump), an oil temperature sensor that detects the temperature of the hydraulic oil, and the like.

[0022] The traveling motor 5, the swing motor 6, the boom cylinder 14, the arm cylinder 15, the bucket cylinder 16, the alarm device 41, the standard operating device 42, the communication device 51, and the engine 61 are examples of standard equipment. Sensors that detect the state of the engine 61 (e.g., the RPM sensor 62 and the temperature sensor 63) are other examples of standard equipment. Sensors that detect the state of the hydraulic pump, the generator, the battery, the aftertreatment device, the air conditioning device, and the hydraulic equipment (e.g., the pressure sensor and the oil temperature sensor) are other examples of standard equipment. Standard equipment refers to components that are installed in the hydraulic excavator 1 as standard. Standard equipment refers to components that are installed in the hydraulic excavator 1 when it is shipped from the manufacturer, for example.

[0023] 2, the hydraulic excavator 1 includes a main controller 30, an electrical equipment controller 40, a communication controller 50, and an engine controller 60. The electrical equipment controller 40, the communication controller 50, and the engine controller 60 are examples of a sub-controller. However, specific examples of the sub-controller are not limited to the above examples.

[0024] The main controller 30 controls the overall operation of the hydraulic excavator 1. The electrical equipment controller 40 controls the operation of electrical equipment (e.g., an alarm device 41, a standard operating device 42) mounted on the hydraulic excavator 1, and monitors the status of the electrical equipment. The communication controller 50 controls communication between the hydraulic excavator 1 and an external device (i.e., the operation of the communication device 51), and monitors the status of the communication device 51. The engine controller 60 controls the operation of the engine 61, and monitors the status of the engine 61 through various sensors (62, 63). Since the basic configuration of each of the controllers 30, 40, 50, 60 is the same, the main controller 30 will be described below.

[0025] The main controller 30 includes a central processing unit (CPU) 31 and a memory 32. The memory 32 is, for example, a read only memory (ROM), a random access memory (RAM), a hard disk drive (HDD), or a combination of these. The main controller 30 realizes the processes described below by the CPU 31 reading and executing program codes stored in the ROM or HDD. The RAM is used as a work area when the CPU 31 executes the programs.

[0026] However, the specific configuration of the main controller 30 is not limited to this, and may be realized by hardware such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0027] The controllers 30, 40, 50, and 60 are configured to be able to communicate with each other via a CAN (Controller Area Network) 100. That is, the controllers 30, 40, 50, and 60 communicate with each other in a manner conforming to the CAN protocol. The CAN protocol is an example of a predetermined communication protocol. However, specific examples of the communication protocol are not limited to the CAN protocol, and may be TCP / IP, Ethernet, Wi-Fi, etc.

[0028] 1, a cutter 71 can be attached to and detached from the tip of the arm 12 in place of the bucket 13. That is, the cutter 71 can be rotatably supported on the tip of the arm 12. The cutter 71 is an example of an extension attachment for grasping and demolishing an object (e.g., a building, etc.). However, specific examples of the extension attachment are not limited to this, and may be a grapple, a hook for suspending a load, or the like.

[0029] The cutter 71 mainly includes a pair of blades 72a, 72b, a pair of hydraulic cylinders 73a, 73b, and a turning motor 74. The pair of blades 72a, 72b are configured to be rotatable in a direction to open and close relative to each other. The pair of hydraulic cylinders 73a, 73b turn the corresponding blades 72a, 72b. The turning motor 74 rotates the cutter 71 (the pair of blades 72a, 72b and the pair of hydraulic cylinders 73a, 73b) clockwise and counterclockwise.

[0030] Fig. 3 is a hardware configuration diagram of the hydraulic excavator 1 equipped with optional devices. As shown in Fig. 3, when a cutter 71 is attached to the tip of the arm 12, an attachment controller 70 is connected to the CAN 100, and an extended operating device 43 is connected to the electrical equipment controller 40. The attachment controller 70 controls the operation of the cutter 71 and monitors the state of the cutter 71 through various sensors (75, 76). The pressure sensor 75 detects the pressure of the hydraulic oil supplied to the hydraulic cylinders 73a, 73b and the swing motor 74. The attitude sensor 76 detects the attitude of the cutter 71. The extended operating device 43 receives, for example, an operator's operation to operate the cutter 71.

[0031] An extension attachment including the cutter 71 is one example of optional equipment. Furthermore, sensors that detect the state of the cutter 71 (e.g., pressure sensor 75, attitude sensor 76) are another example of optional equipment. Furthermore, the extension operating device 43 is another example of optional equipment. However, specific examples of optional equipment are not limited to the above-mentioned examples. Optional equipment is a component that can be attached or detached to the hydraulic excavator 1 at will. Furthermore, optional equipment is a component of the hydraulic excavator 1 that is different from the standard equipment. Optional equipment refers to, for example, a component provided by a manufacturer other than the manufacturer of the hydraulic excavator 1 (i.e., a third party).

[0032] As one example, an optional device (e.g., the cutter 71, the pressure sensor 75, and the attitude sensor 76) may be connected to a sub-controller (e.g., the attachment controller 70) newly connected to the CAN 100. As another example, an optional device (e.g., the extended operating device 43) may be connected to an existing sub-controller (e.g., the electrical equipment controller 40) already connected to the CAN 100.

[0033] The standard devices and optional devices (hereinafter, these may be collectively referred to as "on-board devices") transmit status information to the main controller 30 via the sub-controllers 40, 50, 60, 70. In other words, the sub-controllers 40, 50, 60, 70 transmit status information of the connected on-board devices to the main controller 30. The status information is information indicating the status of the on-board devices (for example, current status, operating condition, possibility of failure, etc.).

[0034] [Status information data layout] FIG. 4 is a diagram showing the data layout of the status information. FIG. 5 is a diagram showing the setting values ​​of the failure type, device name, and source controller. As shown in FIG. 4, the data layout of the status information is determined by the communication protocol of each of the controllers 30, 40, 50, 60, and 70. The status information may be fixed-length data or variable-length data. The status information includes, for example, a plurality of parameters (for example, failure type, device name, source controller). However, the data layout of the status information and the parameters included in the status information are not limited to the example of FIG. 4.

[0035] The fault type is information indicating the type of fault of the onboard device. As shown in FIG. 4, the fault type is stored at X [Bytes] from the beginning of the status information. Also, as shown in FIG. 5(A), the fault type is determined in advance by the contents represented by each of a plurality of setting values ​​("0001" to "0004"). The combination of PSN (Suspect Parameter Number) and FMI (Failure Mode Identifier) ​​in the CAN protocol is an example of a fault type.

[0036] The device name is information that indicates the type of installed equipment. As shown in FIG. 4, the device name is stored at the Y [byte] position from the beginning of the status information. Also, as shown in FIG. 5(B), the contents represented by each of a plurality of setting values ​​("01" to "04") of the device name are predetermined. The device name in the CAN protocol is an example of a device name.

[0037] The source controller is information indicating the sub-controller 40, 50, 60, 70 that is the source of the status information. As shown in FIG. 4, the source controller is stored at a position Z [Bytes] from the beginning of the status information. Also, as shown in FIG. 5(C), the contents represented by each of a plurality of setting values ​​("001" to "004") of the source controller are predetermined. The SA (Source Address) in the CAN protocol is an example of a source controller.

[0038] The main controller 30 grasps the data layout of the status information in advance. That is, the main controller 30 can extract the failure type, device name, and setting value of the source controller from the status information received from the mounted device. Also, the correspondence between the setting value and the content of each parameter shown in FIG. 5 is assumed to be stored in advance in the memory 32 of the main controller 30. Also, the setting value and content of the source controller shown in FIG. 5(C) may be newly added every time a new subcontroller is connected to the CAN 100. For example, the main controller 30 may receive the setting value "009" and content "attachment controller" of the source controller from the newly connected subcontroller 70 by address claim according to the CAN protocol, and register them in the table of FIG. 5(C).

[0039] [Examples of data in various tables] Fig. 6 shows an example of data in the permanent setting table. Fig. 7 shows an example of data in the notification method table (A), notification level table (B), and provisional setting table (C). Each table shown in Fig. 6 and Fig. 7 is stored in the memory 32 of the main controller 30.

[0040] The main setting table shown in Fig. 6 is a table for setting the notification level of the status information transmitted from the standard device. More specifically, the main setting table is a table in which the notification level by the notification device 41 is set in association with each of all setting values ​​of the first parameters (combination of fault type and transmission source controller) that can be set in the status information of the standard device. The main setting table includes one or more main setting records. The main setting record includes the fault type, the transmission source controller, the fault content, and the notification level, which will be described later with reference to Fig. 7(A).

[0041] A final setting record including a setting value of the first parameter that can be set in the standard equipment status information is already registered in the final setting table when the hydraulic excavator 1 is shipped. The main controller 30 may also add a final setting record received from the server via the communication device 51 to the final setting table. Furthermore, the main controller 30 may add a final setting record input via a management terminal connected to the CAN 100 to the final setting table.

[0042] The notification method table shown in FIG. 7(A) is a table for setting a notification method. The notification method table includes one or more notification records. The notification record includes a notification level and a notification method. The notification level indicates the importance of the notification. In other words, the higher the notification level, the higher the importance of the notification. The notification method refers to a specific method of notification using the notification device 41 and the communication device 51. As an example, the notification method "message" is a notification method in which a message is displayed on a display. As another example, the notification method "warning buzzer" is a notification method in which a warning buzzer is output from a speaker. The notification method "server notification" is a notification method in which a message is transmitted to a server via the communication device 51.

[0043] Notification records are already registered in the notification method table when the hydraulic excavator 1 is shipped. The main controller 30 may also add to the notification method table a notification record received from the server via the communication device 51. Furthermore, the main controller 30 may also add to the notification method table a notification record input via a management terminal connected to the CAN 100.

[0044] The notification level table shown in Fig. 7(B) is a table for setting the notification level of the status information transmitted from the optional device. More specifically, the notification level table is a table in which notification levels are set in association with all setting values ​​that can be set in the second parameter (device name). The notification level table includes one or more notification level records. The notification level record includes a device name and a notification level.

[0045] An alert level record including a setting value of the second parameter that can be set in the status information of the optional device is already registered in the alert level table at the time of shipment of the hydraulic excavator 1. Furthermore, the main controller 30 may add an alert level record received from the server via the communication device 51 to the alert level table. Furthermore, the main controller 30 may add an alert level record inputted via a management terminal connected to the CAN 100 to the alert level table.

[0046] The provisional setting table shown in Fig. 7(C) is a table for setting the notification level of the status information actually transmitted from the optional device. More specifically, the provisional setting table is a table in which the notification level is set in association with each setting value of the first parameter that was actually set in the status information of the optional device. The provisional setting table may include one or more provisional setting records. The provisional setting record includes a failure type, a transmission source controller, a notification level, a registration date and time, and a notification count.

[0047] The registration date and time is the date and time when the provisional setting record is registered. The notification count is a diagram showing the number of times notification of the status information indicated in the provisional setting record is performed. The main controller 30 can specify the notification frequency of the status information indicated in the provisional setting record using the registration date and time and the notification count. Specifically, notification frequency = notification count / (current date and time - registration date and time). That is, the registration date and time and the notification count are examples of information for specifying the occurrence frequency of the status information. However, the information for specifying the occurrence frequency of the status information is not limited to these. Furthermore, the provisional setting record may include information for specifying the duration of the status information in addition to or instead of the information for specifying the occurrence frequency of the status information.

[0048] No provisional setting records are registered in the provisional setting table when the hydraulic excavator 1 is shipped. Then, the main controller 30 registers provisional setting records in the provisional setting table in a notification control process which will be described later with reference to Fig. 8.

[0049] In this embodiment, the combination of the fault type and the source controller is an example of a first parameter. Also, in this embodiment, the device name is an example of a second parameter. The first parameter and the second parameter are, for example, the fault type, the source controller, the device name, or a combination thereof. That is, the status information includes the first parameter and the second parameter that comply with a predetermined CAN protocol.

[0050] It is preferable that the variation of the setting value of the second parameter is smaller than the variation of the setting value of the first parameter. This allows the number of records in the notification level table shown in Fig. 7(B) to be smaller than the number of records in the main setting table shown in Fig. 6. However, specific examples of the first parameter and the second parameter are not limited to the above examples. As another example, when each of the controllers 30, 40, 50, 60, and 70 communicates in a method conforming to TCP / IP, the IP address may be the first parameter and the port number may be the second parameter.

[0051] [Notification control processing] Fig. 8 is a flowchart of the notification control process. The notification control process is a process for causing one or both of the notification device 41 and the communication device 51 to notify the status of the onboard equipment indicated by the status information. The main controller 30 executes the notification control process shown in Fig. 8 when receiving status information from the sub-controllers 40, 50, 60, 70 (in other words, the onboard equipment) via the CAN 100. The notification control process will be described below on the assumption that the hydraulic excavator 1 has the configuration shown in Fig. 3. It is also assumed that the provisional setting record of Fig. 7(C) has not yet been registered in the provisional setting table.

[0052] First, the main controller 30 extracts the setting values ​​of the first parameters (fault type and transmission source controller) from the received status information. Then, the main controller 30 judges whether or not the setting values ​​of the extracted first parameters are registered in the permanent setting table of Fig. 6 (S11). The setting values ​​of the first parameters included in the status information received from the standard device are registered in the permanent setting table. On the other hand, the setting values ​​of the first parameters included in the status information received from the optional device are not necessarily registered in the permanent setting table.

[0053] As an example, when status information including a fault type setting value of “0002”, a sending controller setting value of “002”, and a device name setting value of “01” is received from the engine 61 via the engine controller 60, the main controller 30 determines that the setting value of the first parameter (=0002+002) included in the status information is registered in the main setting table of FIG. 6 (S11: Yes).

[0054] In this case, the main controller 30 causes the notification device 41 and the communication device 51 to notify the state of the engine 61 indicated by the status information at a notification level (=level 3) set in this setting table in association with the set value (=0002+002) (S12). That is, the main controller 30 notifies the radiator failure by displaying a message on the display, outputting a warning buzzer from the speaker, and transmitting a message to the server via the communication device 51. The message to be displayed on the display (transmitted to the server) may be, for example, registered in advance in this setting table, or may be included in the status information, or may be a combination of these.

[0055] As another example, when status information including a fault type setting value of “0003”, a sending controller setting value of “009”, and a device name setting value of “02” is received from the cutter 71 via the attachment controller 70, the main controller 30 determines that the setting value of the first parameter (=0003+009) included in the status information is not registered in the main setting table of FIG. 6 (S11: No).

[0056] In this case, the main controller 30 judges whether or not the setting value of the first parameter (=0003+09) is registered in the provisional setting table of Fig. 7(C) (S13). Note that the setting value of the first parameter included in the status information received for the first time from the optional device is not registered in the provisional setting table. On the other hand, the setting value of the first parameter included in the status information received from the optional device for the second or subsequent time is registered in the provisional setting table.

[0057] Then, when the main controller 30 determines that the setting value (=0003+009) of the first parameter included in the status information has not yet been registered in the provisional setting table (S13: No), it causes the notification device 41 to notify the status of the optional device indicated in the status information at the notification level (=level 2) set in the notification level table in correspondence with the setting value (=02) of the second parameter included in the status information (S14).

[0058] That is, the main controller 30 notifies the user of the status of the cutter 71 indicated by the status information by displaying a message on the display and outputting a warning buzzer from the speaker. As one example, the message displayed (or transmitted) in step S15 may be the same as that in step S12. As another example, the message displayed (or transmitted) in step S15 may be a simpler message than that in step S12, such as a combination of the device name and failure type setting values ​​included in the status information. The same applies to step S17.

[0059] Next, the main controller 30 sets the notification level of the notification executed in step S14 in the provisional setting table in association with the setting value of the first parameter included in the state information (S15). That is, the main controller 30 registers in the provisional setting table a provisional setting record including the notification level of the notification executed in step S14 (=Level 2), the setting value of the first parameter included in the state information (=0003+009), the registration date and time (=Current date and time), and the number of notifications (=1 time), as shown in Fig. 7(C).

[0060] On the other hand, when the main controller 30 determines that the setting value (=0003+009) of the first parameter included in the status information is already registered in the temporary setting table (S13: Yes), it executes a level update process (S16) which will be described later with reference to Fig. 9. Then, the main controller 30 causes the notification device 41 to notify the status of the cutter 71 indicated in the status information at the notification level (=level 2) set in the temporary setting table in association with the setting value (=0003+009) of the first parameter included in the status information (S17).

[0061] [Level update process] 9 is a flowchart of the level update process. The level update process is a process for updating the notification level of the provisional setting record registered in the provisional setting table. In other words, the level update process is a process for updating (raising) the notification level of the state indicated by the state information when the same state information is repeatedly transmitted from the optional device.

[0062] First, the main controller 30 adds 1 to the notification count (=1) of the corresponding provisional setting record (more specifically, identified in step S13) (S21). Next, the main controller 30 calculates (updates) the notification frequency using the registration date and time and the notification count after the increment (S22). Then, the main controller 30 compares the updated occurrence frequency with a predetermined threshold value (S23).

[0063] An example of a case in which the updated occurrence frequency is equal to or greater than the threshold value is when the same status information is repeatedly transmitted from an optional device, and it is considered that the status of the optional device indicated by the status information should be strongly notified to the operator in the cab 8 or the manager of the hydraulic excavator 1.

[0064] Then, when the main controller 30 determines that the updated occurrence frequency is equal to or greater than the threshold (S23: Yes), it raises the notification level of the corresponding provisional setting record by one level (S24). That is, in step S17 when step S24 is executed, the main controller 30 notifies the status of the optional device indicated by the status information at the updated notification level (= level 3). On the other hand, when the main controller 30 determines that the updated occurrence frequency is less than the threshold (S23: No), it skips the process of step S24.

[0065] According to the above embodiment, for example, the following advantageous effects are achieved.

[0066] According to the above embodiment, the status of the standard equipment is notified based on this setting table, and the status of the optional equipment is notified based on the notification level table. This makes it possible to appropriately notify abnormalities in the optional equipment even if the statuses of all the optional equipment indicated by the status information are not known in advance.

[0067] According to the above embodiment, the first parameter of the status information received for the first time from the optional device and the notification level provisionally set based on the notification level table are registered in the provisional setting table, so that when the same status information is received next time, notification of the same notification level can be performed. However, the process of step S15 can be omitted.

[0068] Furthermore, according to the above embodiment, by raising the notification level when the occurrence frequency of the same status information (i.e., the notification frequency) is high, the operator or manager can be made aware of the status of the optional device and can be prompted to take appropriate measures. Note that in addition to or instead of the notification frequency, the notification level may be raised based on the duration of the status indicated by the status information. However, the process of step S16 may be omitted.

[0069] The above-described embodiments are illustrative examples of the present invention, and are not intended to limit the scope of the present invention to these embodiments. Those skilled in the art can implement the present invention in various other forms without departing from the gist of the present invention. [Explanation of symbols]

[0070] 1: Hydraulic excavator 2: Lower running body 3: Upper rotating body 4: Crawler 5: Driving motor 6: Swing motor 7: Swivel frame 8: Cab 9: Counterweight 10: Front work machine 11: Boom 12: Arm 13: Bucket 14: Boom cylinder 15: Arm cylinder 16: Bucket cylinder 30: Main controller 31 :CPU 32: Memory 40: Electrical equipment controller 41: Notification device 42:Standard operating device 43: Extended operation device 50: Communication controller 51: Communication equipment 60: Engine controller 61: Engine 62: Rotational speed sensor 63: Temperature sensor 70: Attachment controller 71: Cutter 72: Blade 73: Hydraulic cylinder 74: Swing motor 75: Pressure sensor 76: Attitude sensor 100:CAN

Claims

1. A work machine including standard equipment that is installed as standard, a notification device that notifies information, and a main controller that causes the notification device to notify the status of the equipment indicated by status information, and in which optional equipment different from the standard equipment can be attached and detached, the state information includes a first parameter and a second parameter conforming to a predetermined communication protocol; The main controller a main setting table in which a notification level by the notification device is set in association with each setting value of the first parameter that can be set in the status information transmitted by the standard device; a memory that stores a notification level table in which the notification levels are set in association with each of the setting values ​​that can be set for the second parameter; when the main controller receives the status information from the standard device or the optional device, and when a setting value of the first parameter included in the status information is registered in the final setting table, causes the notification device to notify the status indicated by the status information at the notification level set in the final setting table in association with the setting value; a main controller, when receiving the status information from the standard equipment or the optional equipment, and when the setting value of the first parameter included in the status information is not registered in the main setting table, causing the notification device to notify the status indicated by the status information at the notification level set in the notification level table in correspondence with the setting value of the second parameter included in the status information.

2. 2. The work machine according to claim 1, the memory further stores a provisional setting table in which the notification level is set in association with each setting value of the first parameter that is actually set in the status information received from the optional device; When the setting value of the first parameter is not registered in the main setting table, the main controller: when the setting value of the first parameter has not yet been registered in the provisional setting table, making the notification device notify at the notification level set in the notification level table in correspondence with the setting value of the second parameter, and setting the notification level in the provisional setting table in correspondence with the setting value of the first parameter; When the setting value of the first parameter has already been registered in the provisional setting table, the work machine is characterized in that the notification device is caused to issue an alert at the notification level set in the provisional setting table in correspondence with the setting value of the first parameter.

3. 3. The work machine according to claim 2, the provisional setting table includes information for identifying an occurrence frequency of the state information, The main controller updating an occurrence frequency of the status information when the setting value of the first parameter included in the received status information is registered in the provisional setting table; A work machine characterized in that, when the updated occurrence frequency is equal to or greater than a threshold value, the notification level set in the provisional setting table is increased.

4. 2. The work machine according to claim 1, the standard device and the optional device are connected to a sub-controller capable of communicating with the main controller via a CAN; A work machine characterized in that the communication protocol is a CAN protocol.

5. 5. The working machine according to claim 4, a work machine characterized in that each of the first parameter and the second parameter is information indicating a type of failure, information indicating the sub-controller that sent the parameter, information indicating the type of the standard equipment or the optional equipment, or a combination of these.

Images