JP2017146802A - Software rewriting system for work vehicle and software rewriting method for work vehicle - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a software rewriting system of a work vehicle capable of preventing the erroneous rewriting of software.SOLUTION: A software rewriting system of a work vehicle comprises: a management server for managing software to be used by a control device of a work vehicle, and for generating authentication information related to the rewriting of the software; and portable electronic equipment for acquiring the software and the authentication information. The control device comprises: a collation part for collating the authentication information acquired from the management server with the authentication information acquired by the portable electronic equipment; and a rewriting part for, when the authentication information matches on the basis of collation by the collation part, rewriting the software of the control device by the software acquired by the portable electronic equipment.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a work vehicle software rewriting system and a work vehicle software rewriting method.

  2. Description of the Related Art Conventionally, there has been known an electronic control device for a work vehicle that rewrites software of the work vehicle using a setting device that rewrites and sets software (Patent Document 1).

Japanese Unexamined Patent Publication No. 8-255009

  However, in the electronic control device for a work vehicle described in Patent Document 1, since a serviceman selects software for update and rewrites the software, there is a possibility that erroneous software rewrite occurs.

According to a first aspect of the present invention, a work vehicle software rewriting system manages software used in a work vehicle control device, and generates a management server that generates authentication information related to the software rewriting, and the software. A portable electronic device that obtains the authentication information, and the control device collates the authentication information obtained from the management server with the authentication information obtained by the portable electronic device; A rewriting unit that rewrites the software of the control device with the software acquired by the portable electronic device when the authentication information matches based on the verification by the unit.
According to a second aspect of the present invention, a work vehicle software rewriting method includes a work vehicle control device, a management server that manages software of the control device and generates authentication information related to the software rewrite, A software rewriting method in a software rewriting system including the software and a portable electronic device that acquires the authentication information from a management server, wherein the control device acquires the authentication information from the management server, and After the portable electronic device is connected, the authentication information acquired by the control device is collated with the authentication information acquired by the portable electronic device, and when the authentication information matches, the portable electronic device The software of the control device is rewritten with the software acquired by the

  According to the present invention, since the work vehicle software is rewritten based on the verification result of the authentication information separately acquired by the work vehicle and the portable electronic device, it is possible to prevent the software from being rewritten.

1 is a side view of a hydraulic excavator 100 that is an example of a work vehicle. 1 is a block diagram showing a configuration example of a software rewriting system 10 according to a first embodiment. (A) is a figure explaining an example of the database of the management server 11. FIG. FIG. 6B is a diagram illustrating an example of a database of the terminal 13. FIG. 6C illustrates an example of a database of the portable electronic device 14. (A) is a flowchart showing an example of processing in the terminal 13. FIG. 5B is a flowchart illustrating an example of processing in the management server 11. (A) is a flowchart which shows an example of the process in the portable electronic device 14. FIG. FIG. 6B is a flowchart illustrating an example of processing in the control device 15 of the excavator 100.

(First embodiment)
FIG. 1 is a side view of a hydraulic excavator 100 that is an example of a work vehicle. For convenience of explanation, the front and rear and the vertical direction of the excavator 100 are defined as shown in FIG. The hydraulic excavator 100 includes a traveling body 101 and a revolving body 102 provided on the traveling body 101 so as to be able to swivel. A front working device 103 is provided at the front of the revolving structure 102.

  The front work device 103 includes a boom 104, an arm 105, and a bucket 106. The boom 104 is attached to the swing body 102 so as to be rotatable in the vertical direction with respect to the swing body 102. The boom 104 is driven up and down by the boom cylinder 104a.

  The arm 105 is attached at the tip of the boom 104 so as to be rotatable in the vertical direction with respect to the boom 104. The arm 105 is driven by the arm cylinder 105a to move up and down. The bucket 106 is attached at the tip of the arm 105 so as to be rotatable in the vertical direction with respect to the arm 105. The bucket 106 is driven by a bucket cylinder 106a. The swivel body 102 is provided with an operator cab 107 on which an operator is boarded and a counterweight 109.

  The excavator 100 further includes a control device 15. The control device 15 is configured to include an arithmetic processing unit having a processor such as a CPU or FPGA, a ROM and RAM that are storage devices, and other peripheral circuits. The control device 15 controls each part of the excavator 100 using software stored in the storage device.

  FIG. 2 is a block diagram illustrating a configuration example of the software rewriting system 10 according to the first embodiment. The software rewriting system 10 includes a management server 11, a terminal 13, a portable electronic device 14, and a hydraulic excavator 100 that is an example of a work vehicle.

The excavator 100 includes a communication unit 16. The control device 15 of the excavator 100 is connected to the communication unit 16. The communication unit 16 can communicate with the management server 11 via the network 12. The control device 15 includes a collation unit 20 and a rewriting unit 21. The collation unit 20 collates authentication information related to software rewriting described later. The rewriting unit 21 rewrites the software of the control device 15 when the authentication information matches based on the collation by the collation unit 20.
As long as data can be exchanged between the management server 11 and the excavator 100, the network 12 is not limited to one using wireless communication. Data may be exchanged between the management server 11 and the excavator 100 via a storage medium or the like instead of via the network 12.

  The management server 11 is configured to include a computer (information processing device), and stores and manages software of the excavator 100 in a database or the like. The management server 11 is provided at a management base that manages maintenance information of the excavator 100, for example. The management server 11 includes, as maintenance information of the excavator 100, software version information stored in the control device 15 of the excavator 100, sales area information indicating a region where the excavator 100 is sold, customization information of the excavator 100, and the like. Remember and manage. The management server 11 can communicate with the excavator 100 via the network 12. The management server 11 is further connected to the terminal 13 via a network such as the Internet or a LAN, and can communicate with the terminal 13.

  The terminal 13 includes a computer (information processing device). The terminal 13 is installed, for example, at a sales office of a maintenance service company or the like, and is provided at a location remote from the excavator 100. The terminal 13 stores and manages information such as maintenance work performed by a service person or the like. The terminal 13 has an input device such as a keyboard. The terminal 13 receives body information of the excavator 100, information about the portable electronic device 14, and information about a rewriting tool, which will be described later, by operating an input device by a service person or the like. Here, the vehicle body information of the hydraulic excavator 100 is information for specifying the hydraulic excavator 100 and includes a vehicle body ID and a production number assigned to each vehicle body. The information on the portable electronic device 14 is information for specifying the portable electronic device 14, and is, for example, a device ID or a serial number assigned to each portable electronic device 14. The information on the rewriting tool is information for specifying the rewriting tool, and includes a tool ID and a manufacturing number assigned to each rewriting tool.

  The portable electronic device 14 is carried by a service person who moves to a work site where the excavator 100 is used. The portable electronic device 14 is, for example, a USB memory or a notebook personal computer. The portable electronic device 14 stores a rewriting tool, and rewrites the software of the excavator 100 using the rewriting tool. The rewriting tool is application software for controlling software rewriting of the excavator 100.

  The rewriting of the software of the excavator 100 is performed for the purpose of expanding the functions of the excavator 100 or adding functions. Software rewriting is, for example, software update or software installation. The software update includes both software upgrade and version down.

  FIG. 3A is a diagram for explaining an example of the database of the management server 11. In the database of the management server 11, the vehicle body ID of the excavator 100, the software ID of software used in the excavator 100, software version information, the device ID of the portable electronic device 14 acquired via the terminal 13, and rewriting A tool ID of the tool and a registration area for authentication information are provided. The vehicle body ID, the software ID, and the version information are registered in advance in the management server 11. The device ID of the portable electronic device 14 transmitted from the terminal 13 is stored in the device ID registration area. The tool ID transmitted from the terminal 13 is stored in the tool ID registration area. In the authentication information registration area, authentication information generated by the management server 11 is stored. The authentication information is generated based on, for example, a software ID, a device ID, and a tool ID. In the example shown in FIG. 3A, authentication information generated by combining a software ID, a device ID, and a tool ID is shown. The database further stores sales area information (not shown) of the excavator 100.

  FIG. 3B is a diagram illustrating an example of the database of the terminal 13. The database includes a vehicle ID of a hydraulic excavator, a software ID of software used in the hydraulic excavator, a device ID of the portable electronic device 14, a tool ID of a rewriting tool, and a registration area for authentication information. In the registration area of the vehicle body ID, the device ID, and the tool ID, the serviceman operates the terminal 13 to input and store the vehicle body ID, the device ID, and the tool ID. In the registration area of the software ID, when the terminal 13 transmits the vehicle body ID to the management server 11, the software ID of the software to be updated that is extracted by referring to the database of the management server 11 is registered. Further, in the authentication information registration area, authentication information generated by referring to the database of the management server 11 when the terminal 13 transmits the vehicle body ID to the management server 11 is registered.

  FIG. 3C is a diagram for explaining an example of the database of the portable electronic device 14. The database includes the vehicle ID of the hydraulic excavator, the software ID of the software used in the hydraulic excavator, the device ID of the portable electronic device 14 itself, the tool ID of the rewriting tool stored in the portable electronic device 14, and authentication information. Registration areas are provided. The vehicle body ID, the software ID, and the authentication information are stored by transferring the information stored in the database of the terminal 13.

  With reference to FIG. 4 and FIG. 5, the software rewriting process by the work vehicle software rewriting system 10 will be described. 4A is a flowchart showing an example of processing in the terminal 13, and FIG. 4B is a flowchart showing an example of processing in the management server 11.

  In step S100, the terminal 13 determines the vehicle body information (for example, vehicle body ID) of the excavator 100, the information on the portable electronic device 14 (for example, device ID), and the information on the rewriting tool (for example, the tool) input by a serviceman or the like ID) is transmitted to the management server 11, and the process proceeds to step S110.

  In step S200, the management server 11 receives the vehicle body information of the excavator 100, the information of the portable electronic device 14, and the information of the rewriting tool from the terminal 13, and proceeds to step S210.

  In step S210, the management server 11 searches whether there is software for updating the excavator 100 specified from the vehicle body information based on the vehicle body information of the excavator 100 acquired in step S200, and rewrites the software. It is determined whether or not the hydraulic excavator 100 uses. When the software used in the excavator 100 is an update target, the management server 11 determines that the software used in the excavator 100 is a rewrite target. If an affirmative determination is made in step S210, the process proceeds to step S220. If a negative determination is made in step S210, the process illustrated in FIG.

  In step S220, if there is software for updating the excavator 100, the management server 11 transmits a rewrite permission signal to the terminal 13, and proceeds to step S230.

  In step S <b> 110, the terminal 13 determines whether a rewrite permission signal has been received from the management server 11. If a positive determination is made in step S110, the process proceeds to step S120. If a negative determination is made in step S110, the process illustrated in FIG. In step S120, the terminal 13 transmits a software download request to the management server 11, and proceeds to step S130.

  In step S230, the management server 11 receives a software download request from the terminal 13, and proceeds to step S240.

  In step S <b> 240, the management server 11 generates authentication information relating to software rewriting of the excavator 100. For example, the management server 11 generates authentication information based on the software ID of the excavator 100, the device ID of the portable electronic device 14, and the tool ID of the rewriting tool. The management server 11 transmits the generated authentication information together with the update software to the terminal 13 and proceeds to step S250. In the software rewriting system 10 according to the present embodiment, the authentication information generated by the management server 11 is stored in each of the portable electronic device 14 and the control device 15 of the excavator 100 as described later. When the portable electronic device 14 is connected to the control device 15 of the excavator 100, this authentication information is collated, and when the verification of the authentication information is established, the software of the control device 15 can be rewritten.

  In step S130, the terminal 13 receives the update software and authentication information from the management server 11, and proceeds to step S140. In step S140, after the portable electronic device 14 is connected to the terminal 13, the terminal 13 transmits update software and authentication information to the portable electronic device 14, and ends the process illustrated in FIG. . The portable electronic device 14 receives and stores update software and authentication information transmitted from the terminal 13.

  In step S250, the management server 11 transmits the generated authentication information to the excavator 100 via the network 12, and ends the process illustrated in FIG. The communication unit 16 of the excavator 100 receives the authentication information via the network 12. The control device 15 of the excavator 100 acquires authentication information transmitted from the management server 11 via the communication unit 16 and stores it in the storage device.

FIG. 5A is a flowchart showing an example of processing in the portable electronic device 14.
FIG. 5B is a flowchart illustrating an example of processing in the control device 15 of the excavator 100.

  In step S300, the portable electronic device 14 is directly connected to the hydraulic excavator 100 when the portable electronic device 14 is a USB memory or the like, or via a dedicated cable or the like when the portable electronic device 14 is a notebook personal computer or the like. It is connected to the control device 15. It is also possible to connect by wireless communication. After the portable electronic device 14 is connected to the control device 15, the authentication information acquired from the terminal 13 is transmitted to the control device 15 of the excavator 100, and the process proceeds to step S310.

  In step S400, the control device 15 receives the authentication information from the portable electronic device 14, and proceeds to step S410. In step S410, the collation unit 20 of the control device 15 collates the authentication information acquired from the portable electronic device 14 with the authentication information acquired from the management server 11, and determines whether or not the authentication information matches. . If an affirmative determination is made in step S410, the process proceeds to step S420. If a negative determination is made in step S410, the process illustrated in FIG.

  In step S420, the control device 15 generates a rewrite permission signal for permitting the software rewrite operation by the portable electronic device 14, transmits the generated rewrite permission signal to the portable electronic device 14, and proceeds to step S430.

  In step S <b> 310, the portable electronic device 14 determines whether a rewrite permission signal has been received from the control device 15. If an affirmative determination is made in step S310, the process proceeds to step S320. If a negative determination is made in step S310, the process illustrated in FIG.

  In step S320, the portable electronic device 14 activates the rewriting tool. The rewriting tool automatically selects update software corresponding to the authentication information based on the matched authentication information. For example, the rewriting tool extracts the software ID of the software from the authentication information, and selects the software using the software ID. The portable electronic device 14 rewrites the software of the control device 15 with the selected update software using a rewriting tool. When the rewriting of the software of the control device 15 is completed, the portable electronic device 14 ends the process illustrated in FIG.

  In step S430, the rewriting unit 21 of the control device 15 rewrites the software of the control device 15 with the software selected by the portable electronic device 14. When the rewriting of the software is completed, the control device 15 ends the process shown in FIG.

According to the embodiment described above, the following operational effects can be obtained.
(1) The software rewriting system 10 of the hydraulic excavator 100 manages software used by the control device 15 of the hydraulic excavator 100, and obtains software and authentication information, a management server 11 that generates authentication information related to software rewriting. Portable electronic device 14. The control device 15 compares the authentication information acquired from the management server 11 with the authentication information acquired by the portable electronic device 14 and the portable electronic device when the authentication information matches based on the verification by the verification unit. And a rewriting unit 21 for rewriting the software of the control device 15 by the software acquired by the device 14. In the present embodiment, the authentication information acquired by the control device 15 and the authentication information acquired by the portable electronic device 14 are collated, and the software is rewritten when the authentication information matches. Can be prevented.

(2) The management server 11 generates authentication information based on information about software and information on the portable electronic device 14. The control device 15 selects software based on the matched authentication information. In the present embodiment, authentication information is generated based on the information related to the update software and the information of the portable electronic device 14, and the update software is selected based on the matched authentication information to perform the software update operation. Therefore, the reliability in the software rewriting process can be improved.
(3) The software rewriting system 10 of the excavator 100 further includes a terminal 13 that transmits vehicle body information of the excavator 100 to the management server 11. The management server 11 determines whether or not the software used for the excavator 100 is an update target based on the vehicle body information. When it is determined that the software is the update target, the management server 11 determines the update target software and authentication information. Transmit to the terminal 13. The portable electronic device 14 acquires software and authentication information stored in the terminal 13. Since it did in this way, the security of the data communication in the software rewriting system 10 can be improved.

The following modifications are also within the scope of the present invention, and one or a plurality of modifications can be combined with the above-described embodiment.

(Modification 1)
In the above-described embodiment, the example in which the authentication information is generated based on the software ID of the software, the device ID of the portable electronic device 14, and the tool ID of the rewriting tool has been described, but the present invention is not limited to this. For example, the authentication information may be generated based on any information, or the authentication information may be generated including the vehicle body ID of the excavator 100. The software rewriting system 10 may be configured to generate authentication information based on the software ID of the software and the device ID of the portable electronic device 14.

(Modification 2)
In the above-described embodiment, the example in which the authentication information is collated in the control device 15 has been described. However, the portable electronic device 14 may collate the authentication information. For example, the portable electronic device 14 may receive the authentication information from the control device 15 and collate the authentication information acquired from the control device 15 with the authentication information acquired from the management server 11. Note that, in each of the control device 15 and the portable electronic device 14, it may be determined whether or not the authentication information matches.

(Modification 3)
In the above-described embodiment, the example in which the update software is selected based on the matched authentication information has been described. However, when the authentication information matches, the control device 15 transmits the vehicle body ID together with the rewrite permission signal to the portable electronic device 14, and the portable electronic device 14 updates the update software based on the matched authentication information and the vehicle body ID. May be selected. For example, the portable electronic device 14 may store the vehicle body ID and software in association with each other, and may select the software based on the vehicle body ID acquired from the control device 15.

(Modification 4)
In the above-described embodiment, the example in which the portable electronic device 14 is connected to the terminal 13 and the update software and the authentication information are transmitted to the portable electronic device 14 has been described. However, data communication between the portable electronic device 14 and the terminal 13 may be performed via a storage medium such as a USB memory. Note that the software of the excavator 100 may be rewritten in a state where a storage medium storing update software or the like is connected to the portable electronic device 14.

(Modification 5)
In the above-described embodiment, the hydraulic excavator 100 has been described as an example of the work vehicle. However, the present invention is not limited to this, and other examples such as a wheel loader, a forklift, a telehandler, a lift truck, a dump truck, and a crane are available. The present invention can also be applied to a work vehicle.

  Although various embodiments and modifications have been described above, the present invention is not limited to these contents. Other embodiments conceivable within the scope of the technical idea of the present invention are also included in the scope of the present invention.

DESCRIPTION OF SYMBOLS 10 Software rewriting system, 11 Management server, 13 Terminal, 14 Portable electronic device, 15 Control apparatus, 20 Verification part, 21 Rewriting part, 100 Hydraulic excavator (work vehicle)

Claims (4)

A management server that manages software used in the control device of the work vehicle and generates authentication information related to rewriting of the software;
The software and a portable electronic device that acquires the authentication information,
The controller is
A verification unit for verifying the authentication information acquired from the management server and the authentication information acquired by the portable electronic device;
And a rewriting unit for rewriting software of the control device by the software acquired by the portable electronic device when the authentication information matches based on the verification by the verification unit. . In the work vehicle software rewriting system according to claim 1,
The management server generates the authentication information based on information on the software and information on the portable electronic device,
The control device selects the software on the basis of the matched authentication information. In the work vehicle software rewriting system according to claim 1,
A terminal that transmits vehicle information of the work vehicle to the management server;
The management server determines whether or not software used for the work vehicle is an update target based on the vehicle body information. When the management server determines that the software is an update target, Sending authentication information to the terminal;
The terminal stores the update target software received from the management server and the authentication information,
The work electronic software rewriting system characterized in that the portable electronic device acquires the software and the authentication information stored in the terminal. A control device for a work vehicle, a management server that manages software of the control device, generates authentication information related to rewriting of the software, and a portable electronic device that acquires the software and the authentication information from the management server A software rewriting method in a software rewriting system comprising:
The control device acquires the authentication information from the management server,
The authentication information acquired by the control device and the authentication information acquired by the portable electronic device are collated,
When the authentication information matches, the software of the control device is rewritten with the software acquired by the portable electronic device.

Images