JP2021109518A - Work machine management system - Google Patents

Abstract

To prevent theft of a work machine.SOLUTION: A work machine management system 100 includes a work machine 1 and a portable communication terminal 2. A terminal controller 130 of the portable communication terminal 2 has a management application for releasing a security lock state of restricting a function of the portable communication terminal 2 instead of a previously installed standard application, and releases the security lock state and transmits identification information inherent to the portable communication terminal 2 to the work machine 1 when a release code input from an input part 134 of the portable communication terminal 2 coincides with a previously registered registration code. The control device 150 permits activation of the work machine 1 when the identification information transmitted from the portable communication terminal 2 coincides with previously registered registration information 155.SELECTED DRAWING: Figure 3

Description

The present invention relates to a work machine management system.

In work machines such as hydraulic excavators, wheel loaders, and dump trucks used for civil engineering work, construction work, demolition work, etc., one work machine may be operated by a plurality of operators. For example, at a work site, a worker may be replaced by another worker when taking a break, and the work machine may be operated by another worker, or the work machine may be operated by a service worker during inspection. be. Further, when the work machine is transported, the work machine is operated by the transporter. Further, when the work machine is rented, the worker of the work machine differs depending on the rental destination.

In this way, since the work machine is operated by a plurality of operators, it is desirable to make it easy to change operators, but if anyone can operate the work machine, the work machine is stolen. May be done. Therefore, conventionally, a technique for preventing theft of a work machine has been proposed (see Patent Document 1).

In Patent Document 1, when a mobile terminal is connected to a connection terminal of a work machine, the authentication information transmitted from the mobile terminal and the authentication information stored in the storage unit are collated, and if both match, input is performed. A technique is disclosed in which an operation for a performed operation can be performed, and when the two are different, the operation of the working machine and the traveling body is prohibited. According to the technique described in Patent Document 1, the operator does not need to remember the password or the like.

JP-A-2018-114978

However, in the technique described in Patent Document 1, authentication is performed by physically connecting the mobile terminal to the work machine. Therefore, for example, if the mobile terminal is stolen, the work machine may also be stolen. ..

An object of the present invention is to prevent theft of a work machine.

The work machine management system according to one aspect of the present invention includes a work machine and a mobile communication terminal that wirelessly communicates with the work machine. The work machine includes a control device that controls the start and stop of the work machine based on a command transmitted from the mobile communication terminal. The mobile communication terminal includes an input unit operated by an operator and a terminal controller that transmits commands for starting and stopping the work machine based on a signal from the input unit. The terminal controller has a management application that releases a security lock state that limits the functions of the mobile communication terminal in place of a pre-installed standard application, and when the security lock state is set, the input is made. It is determined whether or not the release code input from the unit matches the pre-registered registration code, and when it is determined that the release code input from the input unit matches the registration code, the security lock The state is released, the identification information unique to the mobile communication terminal is transmitted to the work machine, the control device acquires the identification information transmitted from the mobile communication terminal, and the acquired identification information is registered in advance. It is determined whether or not the identification information matches the registered information, and if the acquired identification information matches the registered information, the work machine is allowed to start.

According to the present invention, theft of the work machine can be prevented.

The figure which shows the work machine management system which concerns on embodiment of this invention. The figure which shows the structure of the work machine management system. Functional block diagram of the work machine management system. The figure which shows an example of the release code input screen displayed on the touch panel. The figure which shows an example of the start-up screen displayed on a touch panel. The figure which shows an example of the authentication failure screen displayed on the touch panel. The figure which shows an example of the activation success screen displayed on a touch panel. The figure which shows an example of the monitoring screen displayed on the touch panel. Functional block diagram for the security lock feature of the terminal controller. FIG. 5 is a flowchart showing the contents from the release code input screen display process (S101) to the terminal ID transmission process (S109) executed by the terminal controller of the mobile communication terminal. A flowchart showing the contents of the terminal authentication process executed by the security controller of the hydraulic excavator. The flowchart which shows the content from the authentication result acquisition process (S112) to the operation time transmission process (S127) executed by the terminal controller of a mobile communication terminal. The flowchart which shows the content of the start / stop control processing executed by the security controller of a hydraulic excavator. A flowchart showing the contents of the operation information display process executed by the terminal controller of the mobile communication terminal. A flowchart showing the contents of the security lock process executed by the terminal controller of the mobile communication terminal. The flowchart which shows the content of the mode setting process executed by the terminal controller of the mobile communication terminal of the work machine management system which concerns on modification 1 of this Embodiment. The functional block diagram of the work machine management system which concerns on modification 2 and modification 3 of this embodiment. The figure which shows an example of the expiration date screen displayed on the touch panel of the mobile communication terminal which concerns on the modification 3 of this embodiment. The flowchart which shows the content of the terminal authentication processing executed by the security controller of the hydraulic excavator which concerns on the modification 3 of this embodiment.

The work machine management system 100 according to the embodiment of the present invention will be described with reference to the drawings. In this embodiment, an example in which the work machine is a crawler type hydraulic excavator will be described.

FIG. 1 is a diagram showing a work machine management system 100 according to an embodiment of the present invention. The work machine management system 100 includes a work machine and a mobile communication terminal 2 that performs wireless communication with the work machine. The work machine is a machine used for civil engineering work, construction work, demolition work, and the like. In this embodiment, an example in which the work machine is a crawler type hydraulic excavator 1 will be described.

The hydraulic excavator 1 is a swivel motor that swivels the lower traveling body 10, the upper swivel body 11 provided on the lower traveling body 10 so as to be swivel, the working device 12 provided on the upper swivel body 11, and the upper swivel body 11. (Not shown) and a traveling motor 19 for traveling the lower traveling body 10. The work device 12 includes a boom 13 rotatably provided on the upper swivel body 11, an arm 14 rotatably provided at the tip of the boom 13, and a bucket rotatably provided at the tip of the arm 14. A boom cylinder 16 for driving a boom 13, an arm cylinder 17 for driving an arm 14, and a bucket cylinder 18 for driving a bucket 15 are provided.

The upper swivel body 11 has a swivel frame, a driver's cab 22 provided on the left side of the front portion of the swivel frame, and an engine chamber provided on the rear side of the driver's cab 22 in the swivel frame. In the engine chamber, there are an engine 20 as a power source, a hydraulic pump driven by the engine 20, a hydraulic device such as a valve for controlling the flow of working fluid discharged from the hydraulic pump 193 (see FIG. 2), and a vehicle body. A battery 21 for supplying power and a battery 21 are housed in the battery 21. The driver's cab 22 is provided with a driver's seat on which the operator sits and an operating device such as an operating lever operated by the operator.

Further, in the engine room, the vehicle body control controller 160 that controls the basic operation of the hydraulic excavator 1, the engine controller 170 that controls the engine 20, and the mobile communication terminal 2 are authenticated and transmitted from the mobile communication terminal 2. A security controller 150 as a control device for controlling the start and stop of the hydraulic excavator 1 is provided based on the command to be issued.

The mobile communication terminal 2 is, for example, a mobile information terminal such as a tablet (slate device) or a smartphone, receives operation information transmitted from the hydraulic excavator 1, and displays the operation information on a touch panel 134 as a display unit. Further, as will be described later, the mobile communication terminal 2 has a function as an electronic key for starting and stopping the hydraulic excavator 1.

FIG. 2 is a diagram showing the configuration of the work machine management system 100. The mobile communication terminal 2 includes a touch panel 134 that is an input unit and a display unit, a wireless communication device 135, and a terminal controller 130 that controls each unit of the mobile communication terminal 2 such as the touch panel 134 and the wireless communication device 135. The touch panel 134 is generated by a well-known resistive film method that detects a touch-operated position based on a voltage change when the display screen is pressed with a finger, a touch pen, or the like, or by touching the display screen with a finger. A well-known capacitance method that detects a touch-operated position based on a change in capacitance (charge) can be adopted.

The terminal controller 130 includes a CPU (Central Processing Unit) 131 as an operating circuit, a volatile memory 132 called a so-called RAM (Random Access Memory) as a storage device, and a non-volatile memory 133 such as an EEPROM and a flash memory as a storage device. It is composed of a microcomputer provided with an input / output interface (I / O interface) (not shown) and other peripheral circuits.

A program capable of executing various operations is stored in the non-volatile memory 133 of the terminal controller 130. That is, the non-volatile memory 133 of the terminal controller 130 is a storage medium capable of reading a program that realizes the functions of the present embodiment.

When the power of the mobile communication terminal 2 is turned on, the CPU 131 accesses the non-volatile memory 133, reads the OS (Operating System) 136, and starts the OS (Operating System) 136. A plurality of applications including a standard security application (hereinafter referred to as a standard application) 137 and a management application 138 are stored in the non-volatile memory 133. Each application operates under the control of OS 136. Further, the non-volatile memory 133 stores the terminal ID 154 of the mobile communication terminal 2 and the registration code 156. The terminal ID 154 is identification information (for example, a device ID) unique to the mobile communication terminal 2. The registration code 156 is a release code (password) for releasing the security lock (screen lock) state of the mobile communication terminal 2, and is composed of, for example, a combination of numbers.

The hydraulic excavator 1 is a wireless communication device 125 that wirelessly communicates with the mobile communication terminal 2, a sensor 191 for monitoring the state of the hydraulic excavator 1, and an engine rotation speed setting device that sets a target rotation speed of the engine 20. It includes an engine control dial 192, a security controller 150, a vehicle body control controller 160, and an engine controller 170. The sensor 191 detects, for example, a pressure sensor provided in the hydraulic system for driving the work device 12, an attitude sensor for detecting the posture of the work device 12, and an operation amount of the operation device provided in the driver's cab 22. There is an operation amount sensor and the like.

The wireless communication device 125 has a communication interface including a communication antenna having a band such as a 2.4 GHz band or a 5 GHz band as a sensitive band as a communication method for a short distance. The wireless communication device 125 directly exchanges information (data) with the mobile communication terminal 2 without going through a wireless base station. The wireless communication device 125 is a wireless communication system based on, for example, the IEEE (The Institute of Electrical and Electronics Engineers, Inc.) 802.11 standard with the wireless communication device 135 included in the mobile communication terminal 2. Wireless communication is performed based on (registered trademark). The communication method is not limited to this, and for example, a communication method such as ZigBee (registered trademark) or Bluetooth (registered trademark) can be adopted.

Each of the controllers 150, 160, 170 has a CPU 151,161,171 as an operating circuit, a volatile memory 152,162,172 as a storage device, a so-called RAM, and a non-volatile memory such as an EEPROM and a flash memory as a storage device. It includes a memory 153, 163, 173, an input / output interface (I / O interface) (not shown), and other peripheral circuits. Each controller 150, 160, 170 may be configured by one microcomputer or may be configured by a plurality of microcomputers. Further, another controller may have some or all of the functions of the controllers 150, 160, 170. Programs capable of executing various operations are stored in the non-volatile memories 153, 163, and 173 of the controllers 150, 160, and 170. That is, the non-volatile memories 153, 163, and 173 of the controllers 150, 160, and 170 are storage media that can read the program that realizes the functions of the present embodiment.

The controllers 150, 160, and 170 are connected to each other so as to be able to communicate with each other via an in-vehicle network 120 called a CAN (Controller Area Network). The in-vehicle network 120 may use a communication standard other than CAN, for example, Ethernet (registered trademark).

The vehicle body control controller 160 controls the operations of the hydraulic equipment 193, the electronic equipment, and the like mounted on the hydraulic excavator 1 based on the signal from the sensor 191.

The engine controller 170 controls the engine speed by adjusting the injection amount of fuel injected into the cylinder of the engine 20 by the fuel injection device 195. The engine control dial 192 is provided in the driver's cab 22, and its operation signal is input to the vehicle body control controller 160. The vehicle body control controller 160 calculates the target rotation speed of the engine 20 based on the operation signal of the engine control dial 192 and outputs the target rotation speed to the engine controller 170.

Further, the engine 20 is provided with a rotation speed sensor 194 for detecting the rotation speed (rotation speed) of the engine 20, and outputs the detected rotation speed (actual rotation speed) of the engine 20 to the engine controller 170. The engine controller 170 controls the fuel injection device 195 so that the actual rotation speed of the engine 20 detected by the rotation speed sensor 194 becomes the target rotation speed input from the vehicle body control controller 160.

The security controller 150 controls the start and stop of the vehicle body control controller 160 and the engine controller 170 based on the signal from the mobile communication terminal 2. Further, the security controller 150 controls the start and stop of the engine 20 based on the signal from the mobile communication terminal 2. The non-volatile memory 153 of the security controller 150 stores unique identification information (terminal ID) of the mobile communication terminal 2 as registration information (registration ID 155).

An ACC relay 157, an IG relay 158, and a starter relay 159 are connected to the security controller 150. As will be described later, the security controller 150 turns these relays on and off by operating the activation switch unit 112a (see FIG. 5) formed on the touch panel 134 of the mobile communication terminal 2.

The ACC relay 157 is a relay for supplying or shutting off the electric power from the battery 21 to, for example, an accessory (ACC) device such as a radio, a vehicle body control controller 160, and an engine controller 170. When the ACC relay 157 is turned on, that is, when the ACC relay 157 is closed, power is supplied from the battery 21 to the accessory devices and the controllers 160 and 170. When the ACC relay 157 is turned off, that is, when the ACC relay 157 is opened, the power supply from the battery 21 to the accessory system devices and the controllers 160 and 170 is cut off.

The IG relay 158 is a relay for supplying or shutting off the electric power from the battery 21 to an ignition (IG) device such as an air conditioner. When the IG relay 158 is turned on, that is, when the IG relay 158 is closed, power is supplied from the battery 21 to the ignition system device. When the IG relay 158 is turned off, that is, when the IG relay 158 is opened, the power supply from the battery 21 to the ignition system device is cut off.

The starter relay 159 is a relay for supplying or shutting off the electric power from the battery 21 to the starter motor (not shown) for starting the engine 20. When the starter relay 159 is turned on, that is, when the starter relay 159 is closed, electric power is supplied from the battery 21 to the starter motor, the starter motor operates, and the engine 20 starts.

FIG. 3 is a functional block diagram of the work machine management system 100. As shown in FIG. 3, the terminal controller 130 of the mobile communication terminal 2 executes the management application (program) 138 (see FIG. 2) stored in the non-volatile memory 133 to display the display control unit 141 and the release code. It functions as an authentication unit 122B, a terminal ID transmission control unit 143, an authentication result acquisition unit 144, an operation information acquisition unit 145, a start switch operation monitoring unit 146, an engine operation determination unit 147, and a lock control unit 124B. The security controller 150 of the hydraulic excavator 1 executes a program stored in the non-volatile memory 153 to execute a terminal ID authentication unit 181, an operation time determination unit 182, a command generation unit 183, an operation information transmission control unit 184, and an operation information transmission control unit 184. , Functions as an engine operation determination unit 185.

The display control unit 141 uses a predetermined display control signal as a display unit based on an input signal from the touch panel 134 as an input unit operated by the operator, an input signal from the input switch 196 (see FIG. 2), and the like. It is output to 134, and a predetermined display image is displayed on the touch panel 134. The display control unit 141 displays the release code input screen 111 (FIG. 4) is displayed.

The lock control unit 124B is in a security lock (screen lock) state in which the display control unit 141 displays the release code input screen 111 to limit the functions of the mobile communication terminal 2 until the correct release code is input. In the security lock state, the screen is locked on the release code input screen 111, the start screen 112 (see FIG. 5) described later is not displayed, and the hydraulic excavator 1 is started using the mobile communication terminal 2. I can't let you. Further, in the security lock (screen lock) state, various applications (for example, a Web browser) installed in the mobile communication terminal 2 cannot be used. In this way, in the state where the security lock is applied, the functions of the mobile communication terminal 2 are restricted except for some functions (for example, the unlock code authentication function). As will be described later, the security lock state is released by the lock control unit 124B when the authentication of the release code is successful. The lock control unit 124B puts the mobile communication terminal 2 in the security lock state again when a predetermined condition is satisfied after the security lock state is released.

FIG. 4 is a diagram showing an example of the release code input screen 111 displayed on the touch panel 134. As shown in FIG. 4, the release code input screen 111 is a screen on which the release code can be input by the operation of the operator, and the number input unit 111a for inputting the numbers from 0 to 9 and the input are canceled. To return the release code input screen 111 to the initial state, enter the cancel section 111b, the OK button section 111c that is operated after the number input is completed, and the release code such as "Enter the passcode." It has a message image 111d prompting the operator.

In the release code authentication unit 122B shown in FIG. 3, the security lock release code (hereinafter, also referred to as an input code) input from the touch panel 134 is stored in advance in the non-volatile memory 133 when the security lock state is set. It is determined whether or not the registration code 156 (see FIG. 2) is matched. When the unlock code authentication unit 122B determines that the input code matches the registration code 156, the lock control unit 124B releases the security lock state. Further, when the release code authentication unit 122B determines that the input code matches the registration code 156, the terminal ID transmission control unit 143 determines the terminal ID 154 stored in the non-volatile memory 133 of the mobile communication terminal 2 (see FIG. 2). ) Is transmitted to the hydraulic excavator 1 via the wireless communication device 135.

The terminal ID authentication unit 181 acquires the terminal ID 154 transmitted from the mobile communication terminal 2 via the wireless communication device 125. The terminal ID authentication unit 181 determines whether or not the acquired terminal ID 154 matches the registration ID 155, which is a terminal ID registered in advance in the non-volatile memory 153, and wirelessly transmits the determination result (terminal ID authentication result). It transmits to the mobile communication terminal 2 via the communication device 125.

When the acquired terminal ID 154 matches the registration ID 155, the terminal ID authentication unit 181 determines that the authentication is successful, and transmits the determination result (authentication result) to the mobile communication terminal 2 via the wireless communication device 125. If the acquired terminal ID 154 does not match the registration ID 155, the terminal ID authentication unit 181 determines that the authentication has failed, and transmits the determination result (authentication result) to the mobile communication terminal 2 via the wireless communication device 125.

When the terminal ID authentication unit 181 determines that the acquired terminal ID 154 matches the registration ID 155, the command generation unit 183 activates the hydraulic excavator 1 (that is, activates the vehicle body control controller 160, the engine controller 170, and the engine 20). Set the permission mode to allow. As will be described later, when the permission mode is set, a signal (operation of the activation switch unit 112a) indicating that the activation switch unit 112a (see FIG. 5) is operated from the mobile communication terminal 2 corresponding to the terminal ID 154. When the time t) is acquired, a command for controlling the start and stop of the hydraulic excavator 1 is generated according to the operation time t. Further, in the state where the permission mode is set, the signal of the ignition switch (not shown) provided in the driver's cab 22 is enabled, and the start and stop of the hydraulic excavator 1 is controlled based on the signal of the ignition switch. Generate a command for.

When the terminal ID authentication unit 181 determines that the acquired terminal ID 154 does not match the registration ID 155, the command generation unit 183 sets a prohibition mode for prohibiting the activation of the hydraulic excavator 1. In the state where the prohibition mode is set, the signal of the ignition switch provided in the driver's cab 22 is invalidated, and the activation of the hydraulic excavator 1 is prohibited even when the ignition switch is operated. In the state where the permission mode is set, when the engine 20 is stopped after the vehicle body control controller 160 and the engine controller 170 of the hydraulic excavator 1 are started, the command generation unit 183 sets the prohibition mode. ..

The authentication result acquisition unit 144 acquires the authentication result of the terminal ID from the hydraulic excavator 1 via the wireless communication device 135. When the authentication result acquired by the authentication result acquisition unit 144 is a result indicating that the authentication of the terminal ID is successful, the display control unit 141 causes the touch panel 134 to display the activation screen 112 (see FIG. 5). When the authentication result acquired by the authentication result acquisition unit 144 is a result indicating that the authentication of the terminal ID has failed, the display control unit 141 causes the touch panel 134 to display the authentication failure screen 113 (see FIG. 6). ..

FIG. 5 is a diagram showing an example of the activation screen 112 displayed on the touch panel 134. As shown in FIG. 5, the start screen 112 is a screen capable of starting and stopping the hydraulic excavator 1 by an operator's operation, and has a start switch unit 112a for operating the start and stop of the hydraulic excavator 1. .. As will be described later, when the engine 20 is stopped, the engine 20 can be started by touching (holding down) the start switch unit 112a. Further, when the engine 20 is in operation, the start switch unit 112a is touch-operated (long-pressed) to stop the engine 20.

FIG. 6 is a diagram showing an example of the authentication failure screen 113 displayed on the touch panel 134. As shown in FIG. 6, the authentication failure screen 113 is a screen showing that the authentication of the mobile communication terminal 2 has failed, and is an image 113a showing that the operation of starting and stopping the engine 20 is prohibited. It also has a message image 113b notifying the operator that the authentication has failed and that the terminal ID needs to be registered, such as "The terminal ID has not been registered. Please contact the administrator." While the authentication failure screen 113 is displayed, the mobile communication terminal 2 cannot start or stop the engine 20.

The start switch operation monitoring unit 146 shown in FIG. 3 transmits commands for starting and stopping the hydraulic excavator 1 based on an input signal from the touch panel 134. Specifically, the start switch operation monitoring unit 146 monitors the operation state of the start switch unit 112a on the start screen 112, and transmits the operation time t of the start switch unit 112a as a command for starting and stopping the hydraulic excavator 1. .. When the start switch operation monitoring unit 146 contacts the start switch unit 112a with a finger, a touch pen, or the like, the start switch operation monitoring unit 146 determines that the start switch unit 112a is in an operated state (operation state). When the start switch operation monitoring unit 146 does not touch the start switch unit 112a with a finger, a touch pen, or the like, the start switch operation monitoring unit 146 determines that the start switch unit 112a is in an unoperated state (non-operation state).

The start-up switch operation monitoring unit 146 measures the time t during which the operation state of the start-up switch unit 112a is maintained (for example, the time from when the finger touches the start-up switch unit 112a until it leaves). The start switch operation monitoring unit 146 transmits the measured operation time t of the start switch unit 112a to the hydraulic excavator 1 via the wireless communication device 135.

The operation time determination unit 182 acquires the operation time t of the start switch unit 112a from the mobile communication terminal 2 via the wireless communication device 125. The operation time determination unit 182 determines whether or not the operation time t is equal to or greater than the threshold value t0.

The engine operation determination unit 185 determines whether or not the engine 20 is operating based on the signal from the engine controller 170. The engine controller 170 outputs information on the rotation speed (actual rotation speed) of the engine 20 detected by the rotation speed sensor 194 (see FIG. 2) to the engine operation determination unit 185.

When the actual rotation speed N of the engine 20 detected by the rotation speed sensor 194 is equal to or higher than the threshold value N0, the engine operation determination unit 185 determines that the engine 20 is in operation, and the actual rotation speed N of the engine 20 is the threshold value. If it is less than N0, it is determined that the engine 20 is not operating (the engine 20 is stopped). The threshold value N0 is a threshold value for determining whether or not the engine 20 is operating, and is stored in advance in the non-volatile memory 153 (see FIG. 2) of the security controller 150. The threshold value N0 is set to a value smaller than the minimum rotation speed set by the engine control dial 192 (see FIG. 2) and larger than 0 (zero), for example.

The command generation unit 183 performs engine start control for starting the engine 20 when the operation time t of the start switch unit 112a is equal to or greater than the threshold value t0 and the engine 20 is stopped. The command generation unit 183 generates a command for turning on the ACC relay 157 and the IG relay 158 in the engine start control, and outputs the command to the ACC relay 157 and the IG relay 158. Further, the command generation unit 183 generates an engine start command for starting the engine 20, and outputs the generated start command to the vehicle body control controller 160 and the engine controller 170. When the engine start command is input, the engine controller 170 controls the starter relay 159, the fuel injection device 195, and the like to start the engine 20. The engine controller 170 determines whether or not the engine 20 has been successfully started (completed), and outputs the determination result to the security controller 150. When the engine 20 is successfully started, the engine controller 170 outputs information indicating that the engine 20 is successfully started to the security controller 150.

The command generation unit 183 performs engine stop control for stopping the engine 20 when the operation time t of the start switch unit 112a is equal to or greater than the threshold value t0 and the engine 20 is in operation. The command generation unit 183 generates an engine stop command for stopping the engine 20 in the engine stop control, and outputs the engine stop command to the engine controller 170. The engine controller 170 stops the engine 20 when an engine stop command is input.

The command generation unit 183 turns on the ACC relay 157 when the operation time t of the start switch unit 112a is less than the threshold value t0, the engine 20 is stopped, and the ACC relay 157 is turned off. Is generated and output to the ACC relay 157. As a result, the ACC relay 157 is turned on. In the command generation unit 183, the operation time t of the start switch unit 112a is less than the threshold value t0, the engine 20 is stopped, the ACC relay 157 is turned on, and the IG relay 158 is turned off. In this case, a command for turning on the IG relay 158 is generated and output to the IG relay 158. As a result, the IG relay 158 is turned on. In the command generation unit 183, the operation time t of the start switch unit 112a is less than the threshold value t0, the engine 20 is stopped, the ACC relay 157 is turned on, and the IG relay 158 is turned on. In this case, a command for turning off the ACC relay 157 and the IG relay 158 is generated and output to the ACC relay 157 and the IG relay 158. As a result, the ACC relay 157 and the IG relay 158 are turned off.

The operation information transmission control unit 184 outputs information indicating that the engine 20 has been successfully started acquired from the engine controller 170, information such as the actual rotation speed of the engine 20, the temperature of the engine cooling water, and the like (operation information of the hydraulic excavator 1). get. Further, the operation information transmission control unit 184 acquires information (operation information of the hydraulic excavator 1) such as the operating time of the hydraulic excavator 1 and the remaining amount of fuel from the vehicle body control controller 160. The operation information transmission control unit 184 transmits the acquired operation information of the hydraulic excavator 1 to the hydraulic excavator 1 via the wireless communication device 125.

The operation information acquisition unit 145 acquires the operation information of the hydraulic excavator 1 from the hydraulic excavator 1 via the wireless communication device 135. When the operation information acquisition unit 145 acquires information indicating that the engine 20 has been successfully started, the display control unit 141 causes the touch panel 134 to display the startup success screen 114 (see FIG. 7).

FIG. 7 is a diagram showing an example of the activation success screen 114 displayed on the touch panel 134. As shown in FIG. 7, the start success screen 114 has a start switch unit 112a and a message image 114a informing the operator that the start of the engine 20 has been successful, such as "the engine has started."

The engine operation determination unit 147 shown in FIG. 3 determines whether or not the engine 20 is in operation based on the actual rotation speed N of the engine 20 included in the operation information acquired by the operation information acquisition unit 145. The engine operation determination unit 147 determines that the engine 20 is in operation when the actual rotation speed N of the engine 20 is equal to or higher than the threshold value N0, and when the actual rotation speed N of the engine 20 is less than the threshold value N0, the engine 20 Is not operating (the engine 20 is stopped).

When the engine operation determination unit 147 determines that the engine 20 is in operation and an operation for displaying the monitoring screen is performed on the touch panel 134, the display control unit 141 displays the monitoring screen on the touch panel 134 ( (See FIG. 8) is displayed.

FIG. 8 is a diagram showing an example of the monitoring screen 115 displayed on the touch panel 134. As shown in FIG. 8, the monitoring screen 115 includes a water temperature meter image 115a showing the temperature of the engine cooling water, a fuel meter image 115b showing the remaining amount of fuel, and a set temperature image 115c showing the set temperature of the air conditioner. , A set frequency image 115d representing a set frequency of radio broadcasting, a date and time image 115e representing a date and time, and a surrounding image 115f taken by a camera mounted on the hydraulic excavator 1.

When the engine operation determination unit 147 shown in FIG. 3 determines that the engine 20 is stopped, the lock control unit 124B causes the display control unit 141 to display the release code input screen 111 (see FIG. 4) on the touch panel 134. , A security lock state that limits the functions of the mobile communication terminal 2. In the present embodiment, the lock control unit 124B determines whether or not the touch panel 134 is operated based on the input signal from the touch panel 134, the engine 20 of the hydraulic excavator 1 is stopped, and the touch panel 134. When the state in which is not operated has elapsed a predetermined time t1, the mobile communication terminal 2 is set to the security lock state.

In the present embodiment, the terminal controller 130 puts the mobile communication terminal 2 in the security lock state by the management application 138. Therefore, a process of invalidating the security lock function by the standard application 137 pre-installed in the mobile communication terminal 2 is performed.

FIG. 9 is a functional block diagram of the security lock function of the terminal controller 130. The standard application 137 is pre-installed (pre-installed) from the factory shipment of the manufacturer of the mobile communication terminal 2. The management application 138 is installed after the manufacturer of the mobile communication terminal 2 is shipped from the factory.

When the management application 138 is not installed, the terminal controller 130 functions as the unlock code registration unit 121A, the unlock code authentication unit 122A, and the lock control unit 124A by executing the standard application 137.

When the security lock is released, the release code registration unit 121A uses the information input from the touch panel 134 (for example, a combination of numbers) as the registration code 156 by operating the touch panel 134 by the operator, and is non-volatile. Register in the sex memory 133.

The unlock code authentication unit 122A uses the information (for example, a combination of numbers) input from the touch panel 134 as the security lock unlock code (input code) by operating the touch panel 134 by the operator in the security lock state. get. The unlock code authentication unit 122A determines whether or not the input code matches the registration code 156.

When the unlock code authentication unit 122A determines that the input code matches the registration code 156, the lock control unit 124A releases the security lock state. When the unlock code authentication unit 122A determines that the input code does not match the registration code 156, the lock control unit 124A maintains the security lock state.

In this embodiment, the management application 138 is installed in the terminal controller 130. Therefore, the terminal controller 130 functions as the unlock code registration unit 121B, the unlock code authentication unit 122B, the lock control unit 124B, and the standard lock invalidation unit 123 by executing the management application 138.

The release code registration unit 121B has the same function as the release code registration unit 121A, the release code authentication unit 122B has the same function as the release code authentication unit 122A, and the lock control unit 124B has the same function as the lock control unit 124A. Has a function.

The standard lock invalidation unit 123 invalidates the functions of the release code registration unit 121A and the release code authentication unit 122A. For example, the standard lock invalidation unit 123 invalidates the function of comparing the input release code (input code) with the registered release code (registration code 156) in the release code authentication unit 122B. As a result, the security lock state is not released in the lock control unit 124A. Further, when the operation for registering the release code by the standard application 137 is performed, the standard lock invalidation unit 123 stores the input information as the registration code 156 in the non-volatile memory 133 by the release code registration unit 121A. The function of the release code registration unit 121A is invalidated so as not to cause the problem.

In the present embodiment, the management application 138 (cancellation code authentication unit 122B) compares the input code with the registration code 156 in place of the standard application 137 pre-installed in the mobile communication terminal 2, and whether the input code is correct or not. Performs an authentication process to determine whether or not. Then, when the input code matches the registration code 156 and it is determined that the authentication is successful, the management application 138 (lock control unit 124B) releases the security lock state. Further, instead of the standard application 137, the management application 138 (release code registration unit 121B) registers the release code for releasing the security lock state. In this way, the management application 138 has a function of substituting the registration and authentication of the unlock code in the standard application 137, and the management application 138 puts the mobile communication terminal 2 in the security lock state or releases the security lock state. ..

The contents of the process executed by the work machine management system 100 will be described with reference to FIGS. 10 to 15. FIG. 10 is a flowchart showing the contents from the release code input screen display process (S101) to the terminal ID transmission process (S109) executed by the terminal controller 130 of the mobile communication terminal 2. The processing of the flowchart shown in FIG. 10 is started by, for example, turning on the power of the mobile communication terminal 2 by a power switch (not shown) or operating the input switch (home button) 196, and has a predetermined control cycle. It is executed repeatedly.

As shown in FIG. 10, in step S101, the terminal controller 130 causes the touch panel 134 to display the release code input screen 111 (see FIG. 4), and proceeds to step S104. The operator can input the release code by operating the number input unit 111a of the release code input screen 111 shown in FIG. 4 and operating the OK button unit 111c.

As shown in FIG. 10, in step S104, the terminal controller 130 compares the release code input by the touch operation of the touch panel 134 with the registration code 156 stored in the non-volatile memory 133, and inputs the code. Performs an authentication process to determine whether the unlock code is correct. If the input release code (input code) matches the registration code 156 in step S104, the terminal controller 130 determines that the release code is correct (that is, the authentication is successful), and proceeds to step S107. If the input release code (input code) does not match the registration code 156 in step S104, the terminal controller 130 determines that the release code is incorrect (that is, authentication has failed), and returns to step S101.

In step S107, the terminal controller 130 releases the security lock of the mobile communication terminal 2 and proceeds to step S109. When the security lock of the mobile communication terminal 2 is released, various applications (for example, a Web browser) installed in the mobile communication terminal 2 can be used by operating the touch panel 134.

In step S109, the terminal controller 130 transmits the terminal ID 154 by the wireless communication device 135, and ends the process shown in the flowchart of FIG.

FIG. 11 is a flowchart showing the contents of the terminal authentication process executed by the security controller 150 of the hydraulic excavator 1. The processing of the flowchart shown in FIG. 11 is started by connecting the battery 21 to the security controller 150, and is repeatedly executed in a predetermined control cycle. The security controller 150 and the battery 21 are usually connected by a normally closed relay.

As shown in FIG. 11, in step S140, the security controller 150 acquires the terminal ID 154 received by the wireless communication device 125, and proceeds to step S143.

In step S143, the security controller 150 performs a terminal authentication process for determining whether or not the acquired terminal ID 154 matches the registration ID 155 registered in the non-volatile memory 153. If it is determined in step S143 that the acquired terminal ID 154 matches the registration ID 155, the terminal authentication is regarded as successful and the process proceeds to step S148. If it is determined in step S143 that the acquired terminal ID 154 does not match the registration ID 155, the terminal authentication is considered to have failed and the process proceeds to step S149.

In step S148, the security controller 150 transmits a determination result (authentication success information) indicating that the authentication was successful to the mobile communication terminal 2 by the wireless communication device 125, and ends the process shown in the flowchart of FIG. In step S149, the security controller 150 transmits a determination result (authentication failure information) indicating that the authentication has failed to the mobile communication terminal 2 by the wireless communication device 125, and ends the process shown in the flowchart of FIG.

FIG. 12 is a flowchart showing the contents from the authentication result acquisition process (S112) to the operation time transmission process (S127) executed by the terminal controller 130 of the mobile communication terminal 2. The processing of the flowchart shown in FIG. 12 is started when the terminal ID transmission processing (S109) of FIG. 10 is completed.

As shown in FIG. 12, in step S112, the terminal controller 130 performs an authentication result acquisition process from the hydraulic excavator 1. In step S112, when the authentication result (authentication success information or authentication failure information) from the hydraulic excavator 1 is acquired by the wireless communication device 135, the process proceeds to step S115.

In step S115, the terminal controller 130 determines whether or not the terminal authentication with the hydraulic excavator 1 is successful based on the acquired authentication result. When the acquired authentication result is the authentication success information, the terminal controller 130 determines that the terminal authentication with the hydraulic excavator 1 has succeeded, and proceeds to step S118. If the acquired authentication result is the authentication failure information, the terminal controller 130 determines that the terminal authentication with the hydraulic excavator 1 has failed, and proceeds to step S121.

In step S118, the terminal controller 130 causes the touch panel 134 to display the startup screen 112 (see FIG. 5), and proceeds to step S124. The operator can start the vehicle body control controller 160, the engine controller 170, and the engine 20 by operating the start switch unit 112a shown in FIG.

As shown in FIG. 12, in step S124, the terminal controller 130 determines whether or not the start switch unit 112a has been operated based on the signal from the touch panel 134. If it is determined in step S124 that the start switch unit 112a has been operated, the process proceeds to step S127. The operation determination of the start switch unit 112a is repeated until the start switch unit 112a is operated.

In step S127, the terminal controller 130 measures the time t when the start switch unit 112a is operated by a timer (not shown), and when the start switch unit 112a is in the non-operation state, the measured operation time t is measured by the wireless communication device 135. Is transmitted to the hydraulic excavator 1 and the process shown in the flowchart of FIG. 12 is completed.

In step S121, the terminal controller 130 causes the touch panel 134 to display the authentication failure screen 113 (see FIG. 6), and ends the process shown in the flowchart of FIG.

FIG. 13 is a flowchart showing the contents of the start / stop control process executed by the security controller 150 of the hydraulic excavator 1. The processing of the flowchart shown in FIG. 13 is started when the authentication success information transmission processing (S148) of FIG. 11 is completed.

As shown in FIG. 13, in step S160, the security controller 150 determines whether or not the acquired operation time t of the activation switch unit 112a is equal to or greater than the threshold value t0. In step S160, if it is determined that the operation time t is equal to or greater than the threshold value t0, the process proceeds to step S163, and if it is determined that the operation time t is less than the threshold value t0, the process proceeds to step S173.

In step S163, the security controller 150 determines whether or not the engine 20 is operating based on the actual rotation speed N of the engine 20 detected by the rotation speed sensor 194. In step S163, when the actual rotation speed N of the engine 20 is equal to or greater than the threshold value N0, the security controller 150 determines that the engine 20 is in operation and proceeds to step S166. In step S163, when the actual rotation speed N of the engine 20 is less than the threshold value N0, the security controller 150 determines that the engine 20 is stopped and proceeds to step S169.

In step S166, the security controller 150 executes engine stop control for stopping the engine 20, and ends the process shown in the flowchart of FIG. In the engine stop control, the security controller 150 generates an engine stop command and outputs the engine stop command to the engine controller 170.

In step S169, the security controller 150 executes engine start control for starting the engine 20, and ends the process shown in the flowchart of FIG. In the engine start control, the security controller 150 generates a command for turning on the ACC relay 157 and the IG relay 158 and outputs the command to the relays 157 and 158, and also generates an engine start command and outputs the command to the engine controller 170. ..

In step S173, the security controller 150 performs a process of determining whether or not the engine 20 is operating, as in step S163. When it is determined in step S173 that the engine 20 is in operation, the process shown in the flowchart of FIG. 13 ends. If it is determined in step S173 that the engine 20 is stopped, the process proceeds to step S175.

In step S175, the security controller 150 determines whether or not the ACC relay 157 is in the off state (open state). If it is determined in step S175 that the ACC relay 157 is in the off state, the process proceeds to step S177. If it is determined in step S175 that the ACC relay 157 is not in the off state (is in the on state), the process proceeds to step S179.

In step S177, the security controller 150 generates a command for turning on the ACC relay 157, outputs the command to the ACC relay 157, and ends the process shown in the flowchart of FIG.

In step S179, the security controller 150 determines whether or not the IG relay 158 is in the off state (open state). If it is determined in step S179 that the IG relay 158 is in the off state, the process proceeds to step S181. If it is determined in step S179 that the IG relay 158 is not in the off state (is in the on state), the process proceeds to step S183.

In step S181, the security controller 150 generates a command for turning on the IG relay 158, outputs the command to the IG relay 158, and ends the process shown in the flowchart of FIG.

In step S183, the security controller 150 generates a command for turning off the ACC relay 157, outputs the command to the ACC relay 157, and proceeds to step S185. In step S185, the security controller 150 generates a command for turning off the IG relay 158, outputs the command to the IG relay 158, and ends the process shown in the flowchart of FIG.

FIG. 14 is a flowchart showing the contents of the operation information display process executed by the terminal controller 130 of the mobile communication terminal 2. The processing of the flowchart shown in FIG. 14 is started when the operation time transmission processing (S127) of FIG. 12 is completed.

As shown in FIG. 14, in step S130, the terminal controller 130 performs an operation information acquisition process for the hydraulic excavator 1. In step S130, when the wireless communication device 135 acquires the information indicating that the engine 20 has been successfully started as the operation information from the hydraulic excavator 1, the process proceeds to step S132.

In step S132, the terminal controller 130 causes the touch panel 134 to display the activation success screen 114 (see FIG. 7), and ends the process shown in the flowchart of FIG. When a predetermined operation is performed on the touch panel 134 by the operator after the activation success screen 114 is displayed, the terminal controller 130 acquires various operation information (S130) and responds to the operation information on the touch panel 134. The monitoring screen 115 having an image is displayed (S132).

FIG. 15 is a flowchart showing the content of the security lock process executed by the terminal controller 130 of the mobile communication terminal 2. The processing of the flowchart shown in FIG. 15 is started when the display processing of the activation success screen 114 is completed in step S132 of FIG.

As shown in FIG. 15, in step S134, the terminal controller 130 acquires the actual rotation speed N of the engine 20 of the hydraulic excavator 1 via the wireless communication device 135, and proceeds to step S135.

In step S135, the terminal controller 130 determines whether or not the engine 20 is operating based on the actual rotation speed N of the engine 20 acquired in step S134. In step S135, when the actual rotation speed N of the engine 20 is equal to or greater than the threshold value N0, the terminal controller 130 determines that the engine 20 is in operation and returns to step S134. In step S135, when the actual rotation speed N of the engine 20 is less than the threshold value N0, the terminal controller 130 determines that the engine 20 is stopped, and proceeds to step S137.

In step S137, the terminal controller 130 determines whether or not the touch panel 134 has not been operated for a predetermined time. In step S137, when the signal from the touch panel 134 is not input, the terminal controller 130 starts the time measurement by the timer. When the signal from the touch panel 134 is input before the predetermined time t1 elapses in the state where the signal from the touch panel 134 is not input, the terminal controller 130 sets the measurement time ta by the timer to 0 (by the timer reset process). Zero). When the signal from the touch panel 134 is not input for the predetermined time t1 or more, the terminal controller 130 determines that the touch panel 134 has not been operated for the predetermined time, and proceeds to step S139. The process of step S137 is repeated until it is determined that the touch panel 134 is not operated for a predetermined time.

In step S139, the terminal controller 130 executes a security lock process that puts the mobile communication terminal 2 in the security lock state, and ends the process shown in the flowchart of FIG.

According to the above-described embodiment, the following effects are exhibited.

(1) The work machine management system 100 includes a hydraulic excavator (work machine) 1 and a mobile communication terminal 2 that wirelessly communicates with the hydraulic excavator 1. The hydraulic excavator 1 includes a security controller (control device) 150 that controls the start and stop of the hydraulic excavator 1 based on a command (operation time t) transmitted from the mobile communication terminal 2. The mobile communication terminal 2 includes a touch panel (input unit) 134 operated by an operator and a terminal controller 130 that transmits a command (operation time t) for starting and stopping the hydraulic excavator 1 based on a signal from the touch panel 134. Be prepared. The terminal controller 130 has a management application 138 that sets a security lock state that limits the functions of the mobile communication terminal 2 and releases the security lock state, instead of the standard application 137 that is installed in advance. The terminal controller 130 determines whether or not the release code (input code) input from the touch panel 134 matches the registration code 156, which is the release code registered in advance, when the security lock state is set. When it is determined that the release code (input code) input from the touch panel 134 matches the registration code 156, the security lock state is released and the identification information (terminal ID 154) unique to the mobile communication terminal 2 is transferred to the hydraulic excavator 1. Send. The security controller 150 acquires the identification information (terminal ID 154) transmitted from the mobile communication terminal 2, and the acquired identification information (terminal ID 154) is used as registration information (registration ID 155) which is pre-registered identification information. It is determined whether or not they match, and when the acquired identification information (terminal ID 154) matches the registration information (registration ID 155), the hydraulic excavator 1 is allowed to start.

In this way, in the work machine management system 100, the management application 138 installed in the mobile communication terminal 2 substitutes the function of the standard application 137 pre-installed in the mobile communication terminal 2, and the release code input by the operator. When matches the registration code 156, the security lock state is released and the terminal ID 154 is transmitted to the hydraulic excavator 1. When the terminal ID 154 matches the registration ID 155, the activation of the hydraulic excavator 1 is permitted. Therefore, even if the mobile communication terminal 2 is stolen, the security lock is applied to the mobile communication terminal 2, so that the hydraulic excavator 1 can be prevented from being stolen. That is, according to the present embodiment, it is possible to provide the work machine management system 100 in which only a specific authorized person can operate the hydraulic excavator 1 by a simple method.

(2) The release code for releasing the security lock of the mobile communication terminal 2 is also used as the release code for releasing the activation prohibition state of the hydraulic excavator 1. Therefore, the amount of information stored by the operator can be kept low, so that the burden on the operator can be reduced.

(3) The terminal controller 130 determines whether or not the engine 20 of the hydraulic excavator 1 is stopped, and when the engine 20 of the hydraulic excavator 1 is stopped, puts the mobile communication terminal 2 in the security lock state. Therefore, when the operator stops the engine 20 of the hydraulic excavator 1 and leaves the driver's cab 22, even if the mobile communication terminal 2 is left behind in the driver's cab 22, the mobile communication terminal 2 is automatically secured. Since it is in the locked state, it is possible to prevent the hydraulic excavator 1 from being stolen.

(4) The terminal controller 130 determines whether or not the touch panel 134 is operated based on the input signal from the touch panel 134, the engine 20 of the hydraulic excavator 1 is stopped, and the touch panel 134 is operated. When the non-existing state elapses for a predetermined time t1, the mobile communication terminal 2 is set to the security lock state. Therefore, after the engine 20 of the hydraulic excavator 1 is stopped, the mobile communication terminal 2 is prevented from being in the security lock state while the operator is operating the mobile communication terminal 2. Therefore, after stopping the engine 20, the operator operates the mobile communication terminal 2 to check the operation information of the hydraulic excavator 1, change the registration code 156, and set the mobile communication terminal 2. It can be changed.

The following modifications are also within the scope of the present invention, and it is possible to combine the configurations shown in the modifications with the configurations described in the above-described embodiments, or to combine the configurations described in the following different modifications. Is.

<Modification example 1>
In the above embodiment, the management application 138 exerts the security lock function of the mobile communication terminal 2 in place of the standard application 137 regardless of whether or not the enable mode in which the security lock function by the standard application 137 is enabled is set. Although examples have been described, the present invention is not limited thereto.

With reference to FIG. 16, a mode setting process executed by the terminal controller 130 of the mobile communication terminal 2 of the work machine management system 100 according to the first modification of the present embodiment will be described. When the security lock state is released, the terminal controller 130 sets the mode of the standard application 137 to the effective mode in which the security lock function of the standard application 137 is exerted in response to the mode switching operation of the standard application 137 by the operator. , And set to one of the invalid modes in which the security lock function of the standard application 137 is not exerted.

As shown in FIG. 16, in step S210, the terminal controller 130 determines whether or not the security lock function of the standard application 137 is set to the effective mode. If it is determined in step S210 that the security lock function of the standard application 137 is set to the effective mode, the process proceeds to step S220. If it is determined in step S210 that the security lock function of the standard application 137 is set to the invalid mode, the process proceeds to step S230.

In step S220, the terminal controller 130 sets the standard mode in which the security lock function is exerted by the standard application 137, and ends the process shown in the flowchart of FIG. In step S230, the terminal controller 130 sets the management mode for exerting the security lock function by the management application 138, and ends the process shown in the flowchart of FIG.

When the standard mode is set, the terminal controller 130 functions as the above-mentioned unlock code registration unit 121A, unlock code authentication unit 122A, and lock control unit 124A by executing the standard application 137. As a result, the standard application 137 (lock control unit 124A) puts the mobile communication terminal 2 in the security lock state, and the release code input screen 111 is displayed on the touch panel 134. When the release code is input from the touch panel 134, the standard application 137 (release code authentication unit 122A) executes the authentication process. Further, if the authentication is successful, the security lock state is released by the standard application 137 (lock control unit 124A). Further, when the operator performs an operation for changing the registration code 156, the standard application 137 (release code registration unit 121A) registers the input information as the registration code 156 in the non-volatile memory 133.

When the standard mode is set, the terminal controller 130 disables the security lock function by the management application 138. When the release code authentication unit 122A determines that the input release code (input code) matches the registration code 156, the terminal ID transmission control unit 143 (see FIG. 3) has identification information unique to the mobile communication terminal 2. The terminal ID 154 is transmitted to the hydraulic excavator 1.

When the management mode is set, the terminal controller 130 functions as the above-mentioned unlock code registration unit 121B, unlock code authentication unit 122B, and lock control unit 124B by executing the management application 138. As a result, the management application 138 (lock control unit 124B) puts the mobile communication terminal 2 in the security lock state, and the release code input screen 111 is displayed on the touch panel 134. When the release code is input from the touch panel 134, the management application 138 (release code authentication unit 122B) executes the authentication process. Further, if the authentication is successful, the security lock state is released by the management application 138 (lock control unit 124B). Further, when the operator performs an operation for changing the registration code 156, the management application 138 (release code registration unit 121B) registers the input information as the registration code 156 in the non-volatile memory 133.

When the management mode is set, the terminal controller 130 disables the security lock function by the standard application 137. When the release code authentication unit 122B determines that the input release code (input code) matches the registration code 156, the terminal ID transmission control unit 143 (see FIG. 3) has identification information unique to the mobile communication terminal 2. The terminal ID 154 is transmitted to the hydraulic excavator 1.

As described above, in this modification, the terminal controller 130 determines whether or not the effective mode in which the security lock function by the standard application 137 is enabled is set, and the security lock function by the standard application 137 is set to the effective mode. If so, the standard application 137 puts the mobile communication terminal 2 in the security lock state or releases the security lock state. When the security lock function by the standard application 137 is set to the invalid mode, the terminal controller 130 puts the mobile communication terminal 2 in the security lock state or releases the security lock state by the management application 138.

Therefore, according to this modification, the hydraulic excavator 1 can be easily activated by performing the security lock release operation by the standard application 137 that is familiar to the user.

<Modification 2>
In the above embodiment, the security controller 150 has only one registration ID 155 used for the authentication of the mobile communication terminal 2, but the present invention is not limited to this. As shown in FIG. 17, the security controller 350 may have a registration ID 155 used for authentication of a plurality of mobile communication terminals 2.

In the example shown in FIG. 17, the registration ID 1 and the registration ID 2 different from the registration ID 1 are stored in the non-volatile memory 153 of the security controller 350. It should be noted that three or more registration IDs can be registered. As described above, in this modification, the terminal ID unique to each of the plurality of mobile communication terminals 2 is registered as the registration information (registration ID) in the security controller 350. Therefore, when there are a plurality of operators who operate the hydraulic excavator 1, the hydraulic excavator 1 can be activated by using the mobile communication terminals 2 owned by each of the plurality of operators, which is convenient.

<Modification example 3>
Further, the expiration date E may be set in the registration ID 155. The expiration date E can be arbitrarily set by, for example, the administrator of the hydraulic excavator 1. In the example shown in FIG. 17, the expiration date E is set for each of the plurality of registration IDs. The registration ID 1 and the corresponding expiration date E1 and the registration ID 2 and the corresponding expiration date E2 are stored in the non-volatile memory 153 of the security controller 350.

The security controller 350, which functions as the terminal ID authentication unit 381, acquires the terminal ID 154 transmitted from the mobile communication terminal 2 via the wireless communication device 125. The terminal ID authentication unit 381 determines whether or not the acquired terminal ID 154 matches any of the registration IDs 1 and ID 2 stored in advance in the non-volatile memory 153.

When the acquired terminal ID 154 matches any of the registration IDs 1 and 2, the terminal ID authentication unit 381 determines whether or not the expiration date E corresponding to the matched registration ID has passed. The terminal ID authentication unit 381 determines that the authentication is successful when the acquired terminal ID 154 matches any of the registration IDs 1 and 2 and the expiration date E corresponding to the matching registration ID has not passed. The determination result (authentication result) is transmitted to the mobile communication terminal 2 via the wireless communication device 125. If the acquired terminal ID 154 does not match any of the registration IDs 1 and 2, the terminal ID authentication unit 381 determines that the authentication has failed, and determines the determination result (authentication result) via the wireless communication device 125 to the mobile communication terminal. Send to 2. When the acquired terminal ID 154 matches either the registration ID 1 or the ID 2 and the expiration date E corresponding to the matched registration ID has passed, the terminal ID authentication unit 381 has passed the expiration date E. As a result, it is determined that the authentication has failed, and the determination result (authentication result) is transmitted to the mobile communication terminal 2 via the wireless communication device 125.

The authentication result acquisition unit 344 acquires the authentication result of the terminal ID transmitted from the hydraulic excavator 1 via the wireless communication device 135. When the authentication result acquired by the authentication result acquisition unit 344 is a result indicating that the authentication of the terminal ID is successful, the display control unit 341 causes the touch panel 134 to display the start screen 112 (see FIG. 5). When the authentication result acquired by the authentication result acquisition unit 344 is a result indicating that the authentication of the terminal ID has failed, the display control unit 341 causes the touch panel 134 to display the authentication failure screen 113 (see FIG. 6). .. When the authentication result acquired by the authentication result acquisition unit 344 is a result indicating that the expiration date E of the terminal ID has passed, the display control unit 341 displays the expiration date screen 316 on the touch panel 134 (see FIG. 18). ) Is displayed.

FIG. 18 is a diagram showing an example of the expiration date screen 316 displayed on the touch panel 134. As shown in FIG. 18, the expiration date screen 316 is a screen showing that the expiration date E of the terminal ID of the mobile communication terminal 2 has passed, and the operation of starting and stopping the engine 20 is prohibited. It has an image 113a indicating that the terminal ID has expired, and a message image 316a notifying the operator that the terminal ID has expired, such as "The ID has expired. Please contact the administrator." .. When the expiration date screen 316 is displayed, the engine 20 cannot be started or stopped by the mobile communication terminal 2.

FIG. 19 is a flowchart showing the contents of the terminal authentication process executed by the security controller 350 in the hydraulic excavator 1 according to the third modification. In FIG. 19, instead of step S143 in FIG. 11, the processes of steps S343, S344, S345, S246, and S347 are performed. In FIG. 19, the same processing as that of FIG. 11 is designated by the same reference numeral (step number), and a portion different from the processing of FIG. 11 will be mainly described.

In step S343, the security controller 350 determines whether or not the acquired terminal ID 154 matches the registration ID 1 registered in the non-volatile memory 153. If it is determined in step S343 that the acquired terminal ID 154 matches the registration ID 1, the process proceeds to step S344. If it is determined in step S343 that the acquired terminal ID 154 does not match the registration ID 155, the process proceeds to step S345.

In step S345, the security controller 350 determines whether or not the acquired terminal ID 154 matches the registration ID 2 registered in the non-volatile memory 153. If it is determined in step S345 that the acquired terminal ID 154 matches the registration ID 2, the process proceeds to step S346. If it is determined in step S345 that the acquired terminal ID 154 does not match the registration ID 2, it is considered that the authentication has failed, and the process proceeds to step S149.

In step S344, the security controller 350 determines whether or not the expiration date E1 registered in the non-volatile memory 153 has passed based on the current date and time information by the timer function. If it is determined in step S344 that the expiration date E1 corresponding to the registration ID 1 has passed, it is assumed that the authentication has failed due to the expiration of the expiration date E, and the process proceeds to step S347. If it is determined in step S344 that the expiration date E1 corresponding to the registration ID 1 has not passed, it is considered that the authentication is successful, and the process proceeds to step S148.

In step S346, the security controller 350 determines whether or not the expiration date E2 registered in the non-volatile memory 153 has passed based on the current date and time information by the timer function. If it is determined in step S346 that the expiration date E2 corresponding to the registration ID 2 has passed, it is assumed that the authentication has failed due to the expiration of the expiration date E, and the process proceeds to step S347. If it is determined in step S346 that the expiration date E2 corresponding to the registration ID 2 has not passed, it is considered that the authentication is successful, and the process proceeds to step S148.

In step S347, the security controller 350 transmits a determination result (authentication result) indicating that the authentication has failed due to the expiration of the expiration date E to the mobile communication terminal 2 via the wireless communication device 125, and the figure shows the figure. The process shown in the flowchart of 19 is terminated.

In this modification, for example, when the rental company rents the hydraulic excavator 1, if the operator changes for each period, the expiration date E is set for each registration ID of the mobile communication terminal 2 owned by the plurality of operators. Can be done. Further, when the hydraulic excavator 1 is transported, the transporter can be temporarily operated by setting the registration ID and the expiration date E of the mobile communication terminal 2 of the person who operates the hydraulic excavator 1. You can also do it.

As described above, in the present modification, even if the acquired terminal ID 154 matches the registration ID, if the expiration date E of the registration ID has passed, the security controller 350 of the hydraulic excavator 1 Do not allow startup. Therefore, when a person other than the owner of the hydraulic excavator 1 temporarily operates the excavator 1, the security can be enhanced while maintaining the convenience.

<Modification example 4>
In the above embodiment, the case where the work machine is a crawler type hydraulic excavator 1 has been described as an example, but the present invention is not limited to this. The present invention can be applied to various work machines including a work device operated by an actuator, such as a wheel type hydraulic excavator, a wheel loader, a forklift, a crawler crane, and a dump truck.

<Modification 5>
The method of disabling the security lock function by the standard application 137 is not limited to the example described in the above embodiment.

<Modification 6>
In the above embodiment, an example in which the identification information unique to the mobile communication terminal 2 is the terminal ID (for example, device ID) 154 has been described, but the present invention is not limited thereto. The identification information unique to the mobile communication terminal 2 used for authentication by the hydraulic excavator 1 may be in any format such as a set of characters or numbers, a telephone number, and an e-mail address.

<Modification 7>
In the above embodiment, the security controllers 150 and 350 authenticate the terminal ID and acquire the operation time t of the start switch unit 112a from the authenticated mobile communication terminal 2 to the vehicle body control controller 160 and the engine controller 170. Although an example of outputting an activation command has been described, the present invention is not limited to this. When the security controllers 150 and 350 include a controller other than the vehicle body control controller 160 and the engine controller 170 (for example, a monitor controller, a battery controller, a retrofitted controller, etc., which are not shown), a start command is output to those controllers as well. do.

<Modification 8>
In the above embodiment, an example in which the release code for releasing the security lock of the mobile communication terminal 2 is composed of a combination of numbers has been described, but the present invention is not limited to this, and various release codes are adopted and based on the release code. Authentication can be performed. For example, the release code may be a combination of a plurality of characters such as an alphabet. The release code can also be fingerprint data. In this case, the mobile communication terminal 2 reads the operator's fingerprint by the scanner function and performs fingerprint authentication. The unlock code can also be face data. In this case, the mobile communication terminal 2 photographs the operator's face by the camera function and performs face recognition. Further, the release code can be graphic pattern data. In this case, the mobile communication terminal 2 performs graphic authentication based on a graphic pattern detected by tracing a plurality of points (for example, nine points) on the touch panel 134.

<Modification example 9>
In the above embodiment, the terminal controller 130 functioning as the engine operation determination unit 147 is operating the engine 20 based on the actual rotation speed N of the engine 20 transmitted by the security controller 150 functioning as the operation information transmission control unit 184. Although an example of determining whether or not the above is the case has been described, the present invention is not limited to this. For example, the hydraulic excavator 1 may acquire a signal indicating that the engine 20 is stopped via the vehicle-mounted network 120 and transmit it to the mobile communication terminal 2. In this case, the engine operation determination unit 147 determines that the engine 20 of the hydraulic excavator 1 is stopped when the signal indicating that the engine 20 is stopped is acquired.

Further, the engine operation determination unit 147 may determine that the engine 20 is stopped when the start switch unit 112a performs an operation to stop the engine 20. The engine operation determination unit 147 may determine whether or not the engine 20 is in operation by taking into consideration not only the actual rotation speed N of the engine 20 but also the states of the ACC relay 157 and the IG relay 158. For example, the engine operation determination unit 147 may determine that the engine 20 is stopped when the actual rotation speed N of the engine 20 is less than the threshold value N0 and the IG relay 158 is in the off state.

<Modification example 10>
In the above embodiment, when the engine operation determination unit 147 determines that the engine 20 is stopped, the lock control unit 124B sets the security lock state to limit the function of the mobile communication terminal 2. The invention is not limited to this. The lock control unit 124B may put the mobile communication terminal 2 in the security lock state based on the signal input from the touch panel 134 by operating the touch panel 134 by the operator.

<Modification 11>
In the above embodiment, when it is determined that the release code input from the touch panel 134 matches the registration code 156, the terminal controller 130 releases the security lock state and transmits the terminal ID 154 to the hydraulic excavator 1. However, the present invention is not limited to this. The timing of transmitting the terminal ID 154 can be arbitrarily set. For example, the terminal controller 130 may display the start screen 112 when the release code matches the registration code 156, and may further transmit the terminal ID 154 when the start switch unit 112a is operated. In this case, when the acquired terminal ID 154 matches the registration ID 155, the security controller 150 generates a command to activate the hydraulic excavator 1 according to the operation time t of the start switch unit 112a, and outputs the command to the controllers 160 and 170. do.

Although the embodiments of the present invention have been described above, the above embodiments are only a part of the application examples of the present invention, and the technical scope of the present invention is limited to the specific configurations of the above embodiments. do not have.

1 ... Hydraulic excavator (work machine), 2 ... Mobile communication terminal, 20 ... Engine, 100 ... Work machine management system, 130 ... Terminal controller, 134 ... Touch panel (input unit), 137 ... Standard application, 138 ... Management application, 150 , 350 ... Security controller (control device)

Claims (6)

In a work machine management system including a work machine and a mobile communication terminal that wirelessly communicates with the work machine.
The work machine includes a control device that controls the start and stop of the work machine based on a command transmitted from the mobile communication terminal.
The mobile communication terminal includes an input unit operated by an operator and a terminal controller that transmits a start / stop command of the work machine based on a signal from the input unit.
The terminal controller
Instead of the pre-installed standard application, it has a management application that releases the security lock state that limits the functions of the mobile communication terminal.
When the security lock state is set, it is determined whether or not the release code input from the input unit matches the pre-registered registration code.
When it is determined that the release code input from the input unit matches the registration code, the security lock state is released, and identification information unique to the mobile communication terminal is transmitted to the work machine.
The control device is
The identification information transmitted from the mobile communication terminal is acquired, and the identification information is acquired.
It is determined whether or not the acquired identification information matches the registration information which is the identification information registered in advance.
When the acquired identification information matches the registration information, the work machine is allowed to start.
A work machine management system characterized by that. In the work machine management system according to claim 1,
The terminal controller
It is determined whether the engine of the work machine is stopped, and
When the engine of the work machine is stopped, the mobile communication terminal is put into the security lock state.
A work machine management system characterized by that. In the work machine management system according to claim 2.
The terminal controller
Based on the input signal from the input unit, it is determined whether or not the input unit is operated.
When the engine of the work machine is stopped and the input unit is not operated for a predetermined time, the mobile communication terminal is put into the security lock state.
A work machine management system characterized by that. In the work machine management system according to claim 1,
In the control device, identification information unique to each of the plurality of mobile communication terminals is registered as the registration information.
A work machine management system characterized by that. In the work machine management system according to claim 1,
An expiration date is set for the registration information,
The control device does not allow the start of the work machine when the expiration date of the registration information has expired even if the acquired identification information matches the registration information.
A work machine management system characterized by that. In the work machine management system according to claim 1,
The terminal controller determines whether or not an effective mode in which the security lock function by the standard application is enabled is set.
When the security lock function by the standard application is set to the enable mode, the security lock state is released by the standard application.
When the security lock function by the standard application is set to the invalid mode, the management application releases the security lock state.
A work machine management system characterized by that.

Images