Movable body inspection method

The method addresses ambiguity in diagnosing remote-controlled vehicle abnormalities by using maintenance information and machine learning to identify issues in the vehicle, inspection device, or remote control device, enhancing diagnostic accuracy and efficiency.

JP2024168846AActive Publication Date: 2024-12-05TOYOTA JIDOSHA KK

Patent Information

Application Number
JP2023085849
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-25
Publication Date
2024-12-05
Estimated Expiration
2043-05-25

AI Technical Summary

Technical Problem

Conventional inspection methods fail to accurately identify whether abnormalities in vehicles under remote control are due to the vehicle, the inspection device, or the remote control device, leading to ambiguity in diagnosing the root cause of issues.

Method used

A method for inspecting a movable object that includes instructing the object to achieve a predetermined target value, measuring the output value, acquiring maintenance information, and using this information to identify which component - the remote control device, inspection device, or inspection target - is abnormal, utilizing machine learning models to enhance accuracy and productivity.

Benefits of technology

The method reliably identifies the source of abnormalities by leveraging maintenance information and machine learning, simplifying the diagnostic process and improving productivity by reducing unnecessary inspections.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024168846000001_ABST
    Figure 2024168846000001_ABST
Patent Text Reader

Abstract

To provide a technique that can specify, with high reliability, a factor causing abnormality in a result of inspection of a movable body that is movable by remote control.SOLUTION: An inspection method for a movable body that is movable by remote control includes: a first step of giving, from a remote controller to a movable body as an inspection target, an instruction to drive the movable body so as to adjust an output value related to a movement of the movable body to a predetermined target value; a second step of measuring the output value by using an inspection device inspecting the movable body to acquire a measured value; a maintenance information acquisition step of acquiring maintenance information on the history of maintenance executed on at least one of the remote controller and the inspection device; and an abnormality specification step of, when the difference between the target value and the measured value is not within a predetermined reference range, specifying which of the remote controller, inspection device, and an inspection target has an abnormality by using the acquired maintenance information.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a method for inspecting a moving object. [Background technology]

[0002] For example, Patent Document 1 discloses an inspection system in which an operator runs a vehicle on a roller device and inspects the vehicle's speedometer for abnormalities using the sensor vehicle speed acquired by the vehicle's speed sensor and the roller vehicle speed acquired by the roller device. In this inspection system, if the roller vehicle speed is not within a predetermined reference range, it is determined that the vehicle's speedometer is abnormal. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-60459 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, even if an abnormality is detected using an inspection device, it is not necessarily an abnormality in the vehicle, and may be, for example, an abnormality in the inspection device. Furthermore, when an inspection is performed while the vehicle is running by remote control, it may be an abnormality in the remote control device that executes the remote control. In the conventional technology, when an abnormality occurs, there is a problem in that it is not possible to identify whether the cause of the abnormality is the vehicle, the inspection device, or the remote control device. [Means for solving the problem]

[0005] The present disclosure can be realized in the following forms.

[0006] (1) According to one aspect of the present disclosure, there is provided a method for inspecting a mobile body that can be moved by remote control, the method including: a first step of issuing an instruction from a remote control device to a mobile body as an inspection target to drive the mobile body so that an output value related to the movement of the mobile body becomes a predetermined target value; a second step of measuring the output value using an inspection device that inspects the mobile body to obtain a measured value; a maintenance information acquisition step of acquiring maintenance information related to a history of maintenance performed on at least one of the remote control device and the inspection device; and an abnormality identification step of identifying which of the remote control device, the inspection device, or the inspection target has an abnormality by using the acquired maintenance information when a difference between the target value and the measured value is not within a predetermined reference range. According to this form of inspection method, in an inspection using a remote control device and an inspection device on a mobile body that can be moved by remote control, it is possible to identify with high reliability whether the cause of the abnormality is in the mobile body being inspected, the inspection device, or the remote control device. (2) In the inspection method according to the above aspect, the maintenance information may be information regarding a timing at which the maintenance was performed on at least any one of the devices. According to the inspection method of this aspect, the cause of the abnormality can be identified with high reliability by a simple method that utilizes the timing of maintenance execution. (3) In the inspection method of the above aspect, in the abnormality identification process, if the timing at which the second process was performed is within a predetermined period of time from the execution timing included in the acquired maintenance information, it may be determined that there is no abnormality in the device on which the maintenance was performed. According to the inspection method of this aspect, the abnormality identifying process can be simplified in accordance with the maintenance information within a predetermined period from the timing of performing maintenance. (4) The inspection method of the above aspect may further include a learning step of training a machine learning model using past data on input / output of the remote control device, past data on input / output of the inspection device, past data on the maintenance information, and past data on normality or abnormality of the remote control device, the inspection device, and the inspection object. In the abnormality identification step, it may be identified which of the remote control device, the inspection device, or the inspection object has an abnormality, using the trained machine learning model. According to this type of inspection method, by using a machine learning model that has been trained using past data, it is possible to improve inspection productivity and the accuracy of identifying the cause of anomalies. (5) In the inspection method of the above embodiment, in the abnormality identification process, if the second process is performed within a predetermined period from the execution timing of the maintenance performed on at least any of the devices, an output is executed to the effect that the probability that the device on which the maintenance was performed is free of abnormality is higher than the probability that the maintenance was not performed. (6) In the inspection method according to the above aspect, the maintenance information may be information regarding whether or not an abnormality has been detected in at least any of the devices during the maintenance. According to the inspection method of this embodiment, the cause of the abnormality can be identified with high reliability by a simple method of utilizing the presence or absence of an abnormality during maintenance. (7) In the inspection method of the above aspect, in the abnormality identification process, if the maintenance information includes information indicating that an abnormality has been detected in at least one of the devices during the maintenance, a determination may be made that there is an abnormality in at least one of the devices in which the abnormality was detected. According to the inspection method of this aspect, the anomaly identification process can be simplified by simply checking whether or not there is an anomaly during maintenance. (8) In the inspection method of the above form, in the abnormality identification process, if the maintenance information includes information indicating that an abnormality has been detected in the maintenance of at least one of the devices, and further includes information that a component that caused the abnormality in at least one of the devices in which the abnormality was detected has been replaced, a determination is made that there is no abnormality in at least one of the devices in which the abnormality was detected, or an identification process is executed to identify whether or not there is an abnormality in at least one of the devices in which the abnormality was detected. According to the inspection method of this aspect, it is possible to properly identify the cause of an abnormality, taking into consideration the case where an abnormality that occurred during maintenance has been repaired. (9) In the inspection method of the above aspect, the maintenance information may be information regarding whether or not an abnormality in at least any of the devices has been detected continuously or intermittently during the maintenance. According to the inspection method of this embodiment, the cause of the abnormality can be identified with high reliability by a simple method of checking the presence or absence of continuous or intermittent abnormalities during maintenance. (10) In the inspection method of the above aspect, in the abnormality identification process, when the maintenance information includes information that an abnormality in at least one of the devices has been detected continuously or intermittently during the maintenance, an output may be provided indicating that there is an abnormality in at least one of the devices in which the continuous or intermittent abnormality has been detected. According to the inspection method of this embodiment, the abnormality identification process can be simplified by a simple method of checking for the presence or absence of continuous or intermittent abnormalities during maintenance. The present disclosure can also be realized in various forms other than the inspection method, for example, in the form of an inspection system for a moving body, an inspection device, a manufacturing method for a moving body, a control method for an inspection system, a control method for an inspection device, a computer program for realizing the control method, a non-transitory recording medium on which the computer program is recorded, etc. [Brief description of the drawings]

[0007] [Figure 1]FIG. 1 is an explanatory diagram showing a schematic configuration of an inspection system according to a first embodiment of the present disclosure. [Diagram 2] FIG. 2 is a block diagram showing the internal functional configuration of an ECU. [Diagram 3] FIG. 2 is a block diagram showing the internal functional configuration of the inspection control device. [Figure 4] 4 is a flowchart showing a processing routine of the inspection method according to the first embodiment. [Diagram 5] 13 is a flowchart showing a processing routine of an abnormality identifying step. [Figure 6] FIG. 11 is a block diagram showing the internal functional configuration of an inspection control device that executes an inspection method according to a second embodiment. [Figure 7] 10 is a flowchart showing a processing routine of an abnormality identifying step according to the second embodiment. [Figure 8] 13 is a flowchart showing a processing routine of an abnormality identifying step in the inspection method according to the third embodiment. [Figure 9] 13 is a flowchart showing a processing routine of an abnormality identifying step in an inspection method according to a fourth embodiment. [Figure 10] 13 is a flowchart showing a processing routine of an inspection method according to a fifth embodiment. [Figure 11] 13 is a flowchart showing a processing routine of an abnormality identifying step in the inspection method according to the fifth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] A. First embodiment: 1 is an explanatory diagram showing a schematic configuration of an inspection system 500 according to a first embodiment of the present disclosure. The inspection system 500 is used, for example, in a factory that manufactures vehicles 100 that can run by remote control. The inspection system 500 includes an inspection device 200 and a remote control device 300. The inspection system 500 inspects whether the vehicle 100 can run normally at a predetermined running speed by remote control.

[0009] The vehicle 100 may be, for example, a passenger car, a truck, a bus, or a construction vehicle. The vehicle 100 is preferably an electric vehicle (BEV: Battery Electric Vehicle). The vehicle 100 is not limited to an electric vehicle, and may be, for example, a gasoline vehicle, a hybrid vehicle, or a fuel cell vehicle. The vehicle 100 includes a vehicle communication unit 190, a power receiving device 150, a motor 140, a battery 120, a wheel speed sensor 170, and an ECU (Electronic Control Unit) 180.

[0010] The vehicle communication unit 190 performs wireless communication with devices outside the vehicle 100 connected to the network 72, such as the inspection device 200 and the remote control device 300, via the access point 70 in the factory. The vehicle communication unit 190 transmits output values ​​corresponding to the inspection items of the inspection device 200, such as the running speed of the vehicle 100, the braking force of the brakes, the rotation speed of the wheels 160, and the charging rate (SOC: State Of Charge) of the battery 120, to the remote control device 300 or the inspection device 200.

[0011] The power receiving device 150 includes, for example, a power receiving circuit and a power receiver (not shown). The power receiver is a power supply inlet or the like corresponding to a power supply connector of the charging device. Instead of the power receiver, a power receiving resonant circuit may be provided for receiving power supplied from the charging device via a power transmitting resonant circuit by non-contact power supply using an electromagnetic induction phenomenon. The power receiving circuit is, for example, a rectifier and a DC / DC converter. When AC power is supplied from the power receiver, the power receiving circuit converts the supplied AC power into DC power by the rectifier. The converted DC power is supplied to the battery 120 via the DC / DC converter.

[0012] The motor 140 is, for example, an AC synchronous motor, and functions as an electric motor and a generator. When the motor 140 functions as an electric motor, the motor 140 is driven by the electric power stored in the battery 120 as a power source. The output of the motor 140 is transmitted to the wheels 160 via a reduction gear and an axle. When the vehicle 100 decelerates, the motor 140 functions as a generator that utilizes the rotation of the wheels 160, and generates regenerative electric power.

[0013] The rotation of the wheels 160 is one form of a "moving motion" that is a motion for the moving body to move. The wheels 160 are one form of a "moving part" that is a part of the moving body that performs the moving motion. The brakes 162 that stop the rotation of the wheels 160 are one form of a "stopping part" that is provided on the moving body and stops the moving motion of the moving body.

[0014] The battery 120 is a rechargeable secondary battery such as a lithium ion battery or a nickel metal hydride battery. The battery 120 stores electric power and the like used for traveling the vehicle 100. When electric power supplied from a charging device to the power receiving device 150 and regenerative electric power generated by the motor 140 are supplied to the battery 120, the battery 120 is charged and the charging rate of the battery 120 increases. A PCU (Power Control Unit) having an inverter, a boost converter, and a DC / DC converter may be connected between the battery 120 and the motor 140.

[0015] The wheel speed sensor 170 detects the rotation speed of each wheel 160. The wheel speed sensor 170 calculates the running speed of the vehicle 100 using the detected rotation speed of each wheel 160. Specifically, the wheel speed sensor 170 performs a calculation process such as averaging the rotation speeds of each wheel 160, and then calculates the running speed of the vehicle 100 using the rotation speed per unit time. Note that at least a part of the function of calculating the running speed of the vehicle 100 may be executed by the vehicle speed acquisition unit 316 or the ECU 180 of the remote control device 300 that acquires the rotation speed of the wheels 160 from the wheel speed sensor 170.

[0016] A device provided in a moving body and detecting an output value related to the movement of the moving body is also called a "moving body detection unit." The "output value related to the movement of the moving body" may include the moving speed of the moving body and various output values ​​from which the moving speed of the moving body can be derived. The output value detected by the moving body detection unit is also called a "moving body side output value."

[0017] A device provided in the vehicle 100 and detecting an output value related to the traveling of the vehicle 100 is also referred to as a "vehicle detection unit." The wheel speed sensor 170 is one form of the "vehicle detection unit." The "output value related to the traveling of the vehicle 100" may include the traveling speed of the vehicle 100 and various output values ​​from which the traveling speed of the vehicle 100 can be derived, such as the number of rotations of the wheels 160, the rotation speed of the wheels 160, and the torque of the wheels 160. The traveling speed of the vehicle 100 detected by the vehicle detection unit is also referred to as a "vehicle-side speed."

[0018] FIG. 2 is a block diagram showing an internal functional configuration of the ECU 180. The ECU 180 is mounted on the vehicle 100 and executes various controls of the vehicle 100. The ECU 180 includes a storage device 186 such as an HDD (hard disk drive), an SSD (solid state drive), an optical recording medium, or a semiconductor memory, and a CPU 182 as a central processing unit. Vehicle speed data 188 is stored in a readable / writable area of ​​the storage device 186. The vehicle speed data 188 is a vehicle-side speed obtained from the wheel speed sensor 170. The storage device 186 stores a computer program for realizing at least a part of the functions provided in this embodiment. The CPU 182 executes various computer programs stored in the memory to realize functions such as the driving control unit 184.

[0019] The driving control unit 184 executes driving control of the vehicle 100. "Driving control" refers to various controls for driving each actuator that exerts the functions of "running," "turning," and "stopping" of the vehicle 100, such as adjusting acceleration, speed, and steering angle. In driving control of the vehicle 100 by remote control, the driving control unit 184 controls each actuator mounted on the vehicle 100 according to a remote control request received from the remote control device 300 via the vehicle communication unit 190.

[0020] In this embodiment, the actuators include an actuator of a drive device for accelerating the vehicle 100, an actuator of a steering device for changing the traveling direction of the vehicle 100, and an actuator of a braking device for decelerating the vehicle 100. The drive device includes a battery 120, a motor 140, and wheels 160. The actuator of the drive device includes the motor 140. The actuators may further include an actuator for swinging the wipers of the vehicle 100, an actuator for opening and closing the power windows of the vehicle 100, and the like.

[0021] When a driver is on board the vehicle 100, the driving control unit 184 can control the actuators in response to the operation of the driver to drive the vehicle 100. The driving control unit 184 can also drive the vehicle 100 by controlling the actuators in response to a control command transmitted from the remote control device 300, regardless of whether a driver is on board the vehicle 100 or not.

[0022] Returning to FIG. 1, the remote control device 300 executes driving control of the vehicle 100 by remote control. For example, the remote control device 300 transports the vehicle 100 in a manufacturing process in a factory by automatically driving the vehicle 100. Transporting the vehicle 100 using automatic driving by remote control is also called "self-driving transport". The remote control device 300 can move the vehicle 100 by remote control without using a transport device such as a crane or a conveyor. When the inspection device 200 inspects the vehicle 100, the remote control device 300 automatically drives the vehicle 100 in accordance with a request from the inspection device 200.

[0023] The remote control device 300 includes a CPU 310 as a central processing unit, a storage device 320, and a remote communication unit 390. These are connected to each other via an internal bus, an interface circuit, etc. The remote communication unit 390 communicates with the vehicle 100, the inspection device 200, etc. via the network 72.

[0024] The storage device 320 is, for example, a RAM, a ROM, a HDD, or an SSD. As described below, the storage device 320 stores vehicle speed data 322 and maintenance information 324. When the computer program stored in the storage device 320 is executed by the CPU 310, the CPU 310 functions as a remote control unit 312, a vehicle speed acquisition unit 316, and a vehicle information acquisition unit 318. However, some or all of these functions may be configured by hardware circuits.

[0025] The vehicle information acquisition unit 318 acquires vehicle identification information of the vehicle 100 from a process management device or the like installed in each process. The "vehicle identification information" refers to various information that can individually identify the vehicle 100. The vehicle identification information includes, for example, ID information given to each vehicle 100, such as a vehicle identification number (VIN: Vehicle Identification Number), and a manufacturing number used for production management. The vehicle identification information may further include specification information of the vehicle 100, such as the model, color, and shape. The vehicle identification information is not limited to information for identifying a single vehicle 100, and may include information for identifying a plurality of vehicles 100 for each predetermined unit, such as a lot number. The vehicle identification information can be acquired, for example, from a radio frequency identification (RF-ID: Radio Frequency Identification) tag attached to the vehicle 100 via short-range wireless communication or the like. The vehicle identification information may be acquired by reading a two-dimensional code attached to the vehicle 100 with a camera or the like.

[0026] The vehicle speed acquisition unit 316 acquires the traveling speed of the vehicle 100 detected by the vehicle 100, i.e., the vehicle-side speed. In this embodiment, the vehicle speed data 188 owned by the vehicle 100 is acquired via the remote communication unit 390. The vehicle speed acquisition unit 316 may acquire the rotation speed of the wheels 160 from the wheel speed sensor 170 to calculate the traveling speed of the vehicle 100. The acquired vehicle-side speed is stored in the storage device 320 as vehicle speed data 322 associated with the vehicle identification information.

[0027] The maintenance information acquisition unit 314 acquires maintenance information 324 related to the maintenance performed on the remote control device 300. "Maintenance information" refers to various information related to the history of maintenance of the device for the purpose of servicing, upkeep, maintenance, inspection, etc. of the device. It is preferable that the maintenance of the device does not include minor content that does not affect the function of the device, and is content that can be sufficiently estimated to enable the target device to operate normally, or content that can be sufficiently estimated to enable the target device to have an abnormality. The maintenance information is used in the inspection method of this embodiment.

[0028] The "maintenance history" may include information on the results of the maintenance, such as information on whether an abnormality was detected during maintenance, and information on parts and components that were repaired or replaced during maintenance. The "maintenance history" may also include information on the history of maintenance, such as the timing of when maintenance was performed, and information on the maintenance over time. The maintenance information acquisition unit 314 acquires, as the maintenance information 324, information on the maintenance manually input by a worker who performed the maintenance of the remote control device 300. The maintenance information acquisition unit 314 may acquire the maintenance information 324 from a management device that manages the maintenance information of the remote control device 300 and the inspection device 200. The acquired maintenance information 324 is stored in the storage device 320.

[0029] The remote control unit 312 transmits a control signal requesting remote control of the vehicle 100 to the vehicle 100 via the remote communication unit 390. When the vehicle 100 receives the request for remote control, driving control is realized by the ECU 180, and as a result, the vehicle 100 runs automatically.

[0030] During self-driving transport, the remote control unit 312 acquires vehicle information from a vehicle detector arranged on the road in the factory. "Vehicle information" means information including at least one of an image of the vehicle 100 and position information of the vehicle 100. For example, a camera can be used as the vehicle detector. The camera is communicatively connected to the remote control device 300 by wireless communication or wired communication. The camera is fixed at a position where it can capture an image of the vehicle 100 traveling on the road in the factory, and acquires an image of the vehicle 100 as vehicle information. Note that the vehicle detector may acquire the position of the vehicle 100 instead of or together with the image of the vehicle 100. When acquiring the position of the vehicle 100, various detectors capable of detecting the position of the vehicle 100, such as LiDAR, infrared sensor, laser sensor, ultrasonic sensor, and millimeter wave radar, are used as the vehicle detector. In addition, the "vehicle information" may further include the traveling direction of the vehicle 100 or the orientation of the vehicle 100. The running direction and orientation of the vehicle 100 can be acquired, for example, by detecting the shape of the vehicle 100 or parts of the vehicle 100. However, the running direction and orientation of the vehicle 100 may be estimated by acquiring only the position of the vehicle 100 using a vehicle detector and using changes in the vehicle 100 over time.

[0031] The remote control unit 312 creates control values ​​for each actuator while analyzing the acquired vehicle information, and causes the ECU 180 to execute driving control of the vehicle 100 using the created control values. For example, the remote control unit 312 adjusts the relative position of the vehicle 100 with respect to a target route preset on a road based on the analysis of the vehicle information, thereby causing the vehicle 100 to travel along the target route.

[0032] The inspection device 200 uses the running speed detected by a device external to the vehicle 100, such as the inspection device 200, to inspect whether the vehicle 100 can run normally by remote control. The running speed of the vehicle 100 detected by the inspection device 200 is also called the "inspection side speed" or simply the "measurement value." A device provided in the inspection device 200 for detecting an output related to the running of the vehicle 100 is also called the "inspection detection unit." Furthermore, when the inspection device 200 determines that there is an abnormality in the inspection result, it identifies whether the abnormality is in the vehicle 100, the remote control device 300, or the inspection device 200.

[0033] The inspection device 200 includes a roller device 250, an inspection control device 210, and an inspection communication unit 290. The inspection communication unit 290 communicates with the remote control device 300, the vehicle 100, and the like via the network 72.

[0034] The roller device 250 acquires the traveling speed of the vehicle 100, which is one form of "output value related to the traveling of the vehicle 100". The roller device 250 includes a roller 256, a motor 252, and a speed sensor 254. As shown in FIG. 1, when the vehicle 100 is placed in a position where it can be inspected by the inspection device 200, the roller 256 is in contact with the circumferential surface of the wheel 160 of the vehicle 100. In this state, the roller 256 rotates in accordance with the rotation of the wheel 160.

[0035] The motor 252 can rotate the rollers 256 with a predetermined torque and rotation speed. When the rotation direction of the wheels 160 when the vehicle 100 moves forward is defined as a forward direction and the rotation direction when the vehicle 100 moves backward is defined as a reverse direction, the motor 252 can rotate the wheels 160 in either the forward direction or the reverse direction by switching the rotation direction of the rollers 256.

[0036] The speed sensor 254 is a sensor that detects the rotation speed of the roller 256. For example, a rotary encoder or the like can be used as the speed sensor 254. The speed sensor 254 calculates the traveling speed of the vehicle 100 using the detected rotation speed of the roller 256. The traveling speed of the vehicle 100 may be calculated by the inspection control device 210 that acquires the rotation speed of the roller 256 from the speed sensor 254. The speed sensor 254 is one form of an "inspection detection unit."

[0037] 3 is a block diagram showing the internal functional configuration of the inspection control device 210. The inspection control device 210 includes a CPU 212 as a central processing unit, and a storage device 220. These are connected to each other via an internal bus, an interface circuit, etc.

[0038] The storage device 220 is, for example, a RAM, a ROM, an HDD (hard disk drive), an SSD (solid state drive), etc. When the CPU 212 executes a computer program stored in the storage device 220, the CPU 212 functions as an inspection unit 214 and an abnormality identification unit 216. However, some or all of these functions may be configured by hardware circuits.

[0039] The maintenance information acquisition unit 218 acquires maintenance information 224 related to the maintenance performed on the inspection device 200. The maintenance information acquisition unit 218 acquires, as the maintenance information 224, information related to the maintenance manually input by a worker or the like who performed the maintenance of the inspection device 200. The maintenance information acquisition unit 218 may acquire the maintenance information 224 from a management device or the like that generally manages the inspection device 200 and the maintenance information of the inspection device 200. The acquired maintenance information 224 is stored in the storage device 220.

[0040] The inspection unit 214 uses the inspection side speed acquired by the roller device 250 to inspect whether the vehicle 100 to be inspected can run normally by remote control. When the inspection result of the inspection unit 214 indicates an abnormality, the abnormality identification unit 216 executes an abnormality identification step, which is a processing routine for identifying the cause of the abnormality. In the abnormality identification step, the abnormality identification unit 216 uses the maintenance information 224 of the inspection device 200 and the maintenance information 324 of the remote control device 300 to identify which of the remote control device 300, the inspection device 200, or the inspection target has an abnormality. The result of the inspection by the inspection unit 214 and the result of identification of the cause of the abnormality by the abnormality identification unit 216 are stored in the storage device 220 as the inspection result 222.

[0041] 4 is a flowchart showing a processing routine of the inspection method according to the first embodiment. This flow is started by the inspection unit 214 that detects that the vehicle 100 to be inspected has arrived at the inspection process or that the vehicle 100 to be inspected has started self-propelled transportation toward the inspection process. The arrival of the vehicle 100 at the inspection process can be obtained, for example, from the detection result of the vehicle 100 by a sensor, a camera, or the like provided at the inspection process.

[0042] In step S10, the remote control unit 312 automatically drives the vehicle 100 by remote control, and places the vehicle 100 in a position where the vehicle can be inspected by the inspection device 200. That is, the remote control unit 312 drives the vehicle 100 by remote control, and places the vehicle 100 on the roller device 250 as shown in FIG.

[0043] In step S20, the remote control unit 312 transmits a command signal to start the inspection to the inspection device 200. Upon receiving the command signal, the inspection unit 214 starts the inspection. Before starting the inspection, the inspection unit 214 may acquire vehicle identification information from the vehicle 100 to be inspected, and compare the acquired vehicle identification information with the vehicle identification information of the inspection target scheduled in terms of production management.

[0044] In step S30, the inspection unit 214 instructs the vehicle 100 to be inspected to drive at a predetermined running speed as a target value. More specifically, the inspection unit 214 outputs a command signal to the remote control device 300 to run the vehicle 100 at a predetermined running speed. The remote control unit 312 that receives the command signal drives the actuator of the vehicle 100 to be inspected by remote control to automatically run the vehicle 100 at a predetermined running speed. The "running speed predetermined as a target value" is also referred to as the "inspection speed" below. The inspection speed can be set to any speed, such as 40km / hr, 60km / hr, etc. Step S30 is also referred to as the "first step".

[0045] In step S40, the vehicle speed acquisition unit 316 acquires the vehicle side speed from the wheel speed sensor 170. When the acquired running speed reaches the inspection speed, the remote control unit 312 drives the vehicle 100 to maintain the inspection speed. In step S50, the vehicle speed acquisition unit 316 outputs to the inspection device 200 that the acquired vehicle side speed has reached the inspection speed.

[0046] In step S70, the inspection unit 214 acquires the inspection side speed as a measured value from the roller device 250. Step S70 is also called the "second step". In step S80, the inspection unit 214 checks whether the difference between the acquired inspection side speed and the target value given as an instruction is within a first range. The first range can be set to any range, such as ±5 km / hr, ±10 km / hr, or between ±10 km / hr and ±5 km / hr. The first range may be set according to legally required conditions. The first range is also called the "reference range". If the difference between the inspection side speed and the target value is within the first range (S80: YES), the inspection unit 214 transitions the process to step S84 and outputs a message indicating that there is no abnormality in the inspection target.

[0047] If the difference between the inspection side speed and the target value is outside the first range (S80: NO), the inspection unit 214 shifts the process to step S82. In step S82, the inspection unit 214 determines that there is an abnormality, and shifts the process to step S100. In step S100, the abnormality identifying unit 216 executes an abnormality identifying step.

[0048] If it is determined that there is an abnormality, it is presumed that the cause is an abnormality in the inspection device 200, an abnormality in the vehicle 100, or an abnormality in the remote control device 300. Examples of abnormalities in the inspection device 200 include an abnormality in the roller device 250, such as the roller 256 or the speed sensor 254 not operating normally, and an abnormality in the software or hardware of the inspection control device 210. Examples of abnormalities in the vehicle 100 include a failure of the wheel speed sensor 170 and an abnormality in the ECU 180. Examples of abnormalities in the ECU 180 include an abnormality in the program stored in the storage device 186 and an abnormality in the instruction value. Examples of abnormalities in the remote control device 300 include an abnormality in the program stored in the storage device 220, an abnormality in the control value, and an abnormality in communication of the remote communication unit 390.

[0049] 5 is a flowchart showing a processing routine of the anomaly identifying step. In step S110, the anomaly identifying unit 216 acquires the maintenance information 224 of the inspection device 200 and the maintenance information 324 of the remote control device 300. The maintenance information 224 of the inspection device 200 may be executed before step S170 described later. In this embodiment, the anomaly identifying unit 216 checks information on the execution timing of the maintenance performed on the inspection device 200 and the remote control device 300 from the acquired maintenance information 224 and maintenance information 324. Step S110 is also referred to as a "maintenance information acquisition step."

[0050] In step S120, the abnormality identification unit 216 checks whether maintenance on the remote control device 300 has been performed within a predetermined period from the timing when the inspection unit 214 acquires the inspection side speed, i.e., the timing when the second step is performed. The abnormality identification unit 216 may check whether the timing when the second step is performed or the current time is within a predetermined period from the execution timing of the maintenance on the remote control device 300. In this case, the "predetermined period" is a period during which the effect of the maintenance on the remote control device 300 can be sufficiently obtained. In other words, the predetermined period is a period during which it is sufficiently possible to estimate that the remote control device 300 after the maintenance can operate normally. If the timing when the second step is performed is outside the predetermined period from the execution timing of the maintenance (S120: NO), the abnormality identification unit 216 shifts the process to step S130.

[0051] In step S130, the abnormality identification unit 216 executes an auxiliary inspection. The "auxiliary inspection" means that the abnormality identification process performs the above-mentioned steps S10 to S80 using a normal vehicle 100 that has been prepared in advance to check for the presence or absence of an abnormality. However, the "auxiliary inspection" only needs to include at least the same steps as the first and second steps described above. The auxiliary inspection is one form of an identification process for identifying whether or not there is an abnormality in the remote control device 300.

[0052] The term "normal vehicle 100" refers to a vehicle 100 whose output value related to the running of the vehicle 100 is normal. The normal vehicle 100 is a vehicle 100 in a state in which it is sufficiently possible to estimate that there is no abnormality in the output value related to the running of the vehicle 100, such as a vehicle 100 that has been determined to be normal by the inspection of the inspection device 200 while the vehicle 100 is being driven manually without the remote control device 300, a vehicle 100 immediately after maintenance has been performed, a vehicle 100 that has been determined to be normal using the inspection device 200 immediately after maintenance, or a vehicle 100 that has been determined to be normal by an inspection device other than the inspection device 200 instead of or together with the inspection device 200. The normal vehicle 100 may be any one of these vehicles 100, or a plurality of vehicles 100 that are any combination of these vehicles 100. In this embodiment, in the auxiliary inspection, the normal vehicle 100 is inspected for the presence or absence of an abnormality by performing steps S10 to S80 shown in FIG. 4 using the inspection device 200. The normal vehicle 100 may be a product vehicle 100, or may be a non-product vehicle used exclusively for inspection.

[0053] If the timing at which the second step is performed is within a predetermined period from the timing at which maintenance is performed on the remote control device 300 (S120: YES), the abnormality identification unit 216 shifts the process to step S124 and determines that there is no abnormality in the remote control device 300. In this case, the abnormality identification unit 216 omits steps S130 and S140 and shifts the process to step S170. That is, if the second step is performed within a predetermined period from the timing at which maintenance is performed, the auxiliary inspection, which is a specification step for specifying whether or not there is an abnormality in the remote control device 300, is omitted, and then it is determined that there is no abnormality in the remote control device 300. Note that instead of or in addition to omitting the auxiliary inspection, a normal output step of outputting that there is no abnormality in the remote control device 300 may be executed. By configuring in this way, the step of specifying whether or not there is an abnormality in the remote control device 300 according to the confirmation result of the maintenance information can be simplified, and the productivity of the inspection method according to this embodiment can be improved.

[0054] In step S140, the anomaly identifying unit 216 checks the result of the auxiliary inspection. That is, the inspection unit 214 checks whether the difference between the inspection side speed acquired using the normal vehicle 100 and the target value is within a second range. The second range can be set to any range, such as ±5 km / hr, ±10 km / hr, or between ±10 km / hr and ±5 km / hr. In this embodiment, the second range is set to the same range as the first range. However, the second range and the first range may be set to be different from each other. For example, the inspection conditions of the auxiliary inspection may be made stricter by setting the second range to a range narrower than the first range.

[0055] If the difference between the inspection side speed and the target value is outside the second range and it is determined in the auxiliary inspection that there is an abnormality (S140: NO), the abnormality identifying unit 216 transitions the process to step S150 and outputs a message indicating that there is an abnormality in the remote control device 300. Step S150 is also referred to as the "third step." In step S160, the abnormality identifying unit 216 issues a message to the manager of the remote control device 300 indicating that there is an abnormality in the remote control device 300 or to prompt repair of the remote control device 300, and ends this flow.

[0056] If the difference between the inspection speed and the target value is within the second range and it is determined that there is no abnormality in the auxiliary inspection (S140: YES), the abnormality identifying unit 216 shifts the process to step S170. In step S170, the abnormality identifying unit 216 checks whether or not maintenance has been performed on the inspection device 200 within a predetermined period from the timing when the second process was performed. In this case, the "predetermined period" is a period during which the effect of the maintenance on the inspection device 200 can be sufficiently obtained. In other words, the predetermined period is a period during which it is sufficiently estimated that the inspection device 200 after the maintenance can operate normally. If the timing when the second process was performed is outside the predetermined period from the timing when the maintenance was performed (S170: NO), the abnormality identifying unit 216 shifts the process to step S180.

[0057] In step S180, the abnormality identification unit 216 performs a subsequent inspection using a plurality of vehicles 100 different from the vehicle 100 to be inspected. The "subsequent inspection" means that the vehicle 100 to be inspected and a plurality of vehicles 100 different from the normal vehicle 100 are used to inspect whether or not there is an abnormality by carrying out steps S10 to S80 shown in FIG. 4. The subsequent inspection is one form of an identification process for identifying whether or not there is an abnormality in the inspection device 200. The subsequent inspection process may include at least the first process and the second process.

[0058] The multiple vehicles 100 used in the subsequent inspection process are preferably multiple vehicles 100 scheduled to be inspected consecutively following the vehicle 100 to be inspected. The subsequent inspection of the multiple vehicles 100 also serves as a regular inspection of the multiple vehicles 100, thereby suppressing a decrease in productivity of the inspection process due to the subsequent inspection. The number of multiple vehicles 100 used in the subsequent inspection may be preset to any number equal to or greater than two. From the viewpoint of improving inspection accuracy, it is preferable for the number of vehicles 100 to be large.

[0059] If the timing at which the second step is performed is within a predetermined period from the timing at which maintenance is performed on the inspection device 200 (S170: YES), the abnormality identifying unit 216 shifts the process to step S174 and determines that there is no abnormality in the inspection device 200. In this case, the abnormality identifying unit 216 omits steps S180 and S190 and shifts the process to step S220. That is, if the second step is performed within a predetermined period from the timing at which maintenance is performed, the subsequent inspection, which is a specification step for specifying whether or not there is an abnormality in the inspection device 200, is omitted, and then it is determined that there is no abnormality in the inspection device 200. Note that instead of or together with the omission of the subsequent inspection, a normal output step of outputting that there is no abnormality in the inspection device 200 may be executed. By configuring in this way, the step of specifying whether or not there is an abnormality in the inspection device 200 according to the confirmation result of the maintenance information can be simplified, and the productivity of the inspection method according to this embodiment can be improved.

[0060] In step S190, the results of the inspections performed by the multiple vehicles 100 are confirmed. If the difference between the acquired inspection speed and the instructed target value is outside the third range for at least one vehicle 100 among the multiple vehicles 100 in the subsequent inspection (S190: NO), the abnormality identifying unit 216 transitions the process to step S200 and outputs a message indicating that the inspection device 200 has an abnormality. The third range can be set to any range, such as ±5 km / hr, ±10 km / hr, or between ±10 km / hr and ±5 km / hr. In this embodiment, the third range is set to the same range as the first range. However, the third range and the first range may be set to be different from each other. For example, the inspection conditions for the subsequent inspection may be made stricter by setting the third range to a range narrower than the first range. In step S210, the abnormality identifying unit 216 notifies the manager of the inspection device 200 or the like that the inspection device 200 has an abnormality or urges the inspection device 200 to be repaired.

[0061] In step S190, if the difference between the acquired inspection side speed and the target value given as an instruction is within the third range for all of the multiple vehicles 100 in the subsequent inspection (S190: YES), the abnormality identification unit 216 transitions to step S220 and outputs a message indicating that the vehicle 100 being inspected has an abnormality. Step S220 is also referred to as the "fourth step." In step S230, the remote control unit 312 remotely controls the vehicle 100 being inspected to travel from the inspection step to a repair step where the vehicle 100 can be repaired, and ends this flow.

[0062] As described above, the inspection method of this embodiment includes a maintenance information acquisition step of acquiring the maintenance information 224 and the maintenance information 324 related to the history of maintenance performed on the remote control device 300 and the inspection device 200, and an abnormality identification step of identifying which of the remote control device 300, the inspection device 200, and the inspection target has an abnormality by using the acquired maintenance information 224, 324 when the difference between the inspection side speed and the target value is not within a predetermined reference range. Therefore, in the inspection of the vehicle 100 that can be driven by remote control using the remote control device 300 and the inspection device 200, it is possible to identify with high reliability which of the vehicle 100 that is the inspection target, the inspection device 200, and the remote control device 300, has an abnormality as a cause of the abnormality.

[0063] According to the inspection method of the present embodiment, the anomaly identifying unit 216 checks, as the maintenance information, information on the timing of maintenance performed on the remote control device 300 and the inspection device 200. The cause of the anomaly can be identified by the simple method of checking the timing of maintenance. In addition, by utilizing the effect of maintenance on the device in identifying the cause of the anomaly, it is possible to simplify the identification of the cause of the anomaly.

[0064] According to the inspection method of this embodiment, in the anomaly identification step, if the timing at which the second step is performed is within a predetermined period from the timing at which maintenance is performed on the remote control device 300 and the inspection device 200, it is determined that there is no anomaly in the remote control device 300 and the inspection device 200 on which maintenance has been performed. Therefore, the auxiliary inspection and the subsequent inspection can be omitted according to the maintenance information, and the anomaly identification step can be simplified during the period in which the effects of maintenance on the devices can be obtained.

[0065] B. Second embodiment: 6 is a block diagram showing an internal functional configuration of an inspection control device 210b that executes an inspection method according to the second embodiment. The inspection control device 210b differs from the inspection control device 210 shown in the first embodiment in that the inspection control device 210b includes a storage device 220b in which a trained model 226 is stored, instead of the storage device 220. The other configurations are the same as those of the inspection control device 210.

[0066] The trained model 226 is a machine learning model that detects anomalies. The trained model 226 outputs the probability of anomalies in the inspection device 200, the remote control device 300, and the inspection target by inputting input / output data during inspection of the inspection device 200, the remote control device 300, and the inspection target, and maintenance information into the trained model 226.

[0067] The trained model 226 is, for example, a machine learning model using a neural network (NN). For example, a model having an architecture such as a recurrent neural network (RNN), a convolutional neural network (CNN), a general regression neural network, or a random forest is suitable for the machine learning model. In this embodiment, a learning model having an RNN with a recurrent structure such as a long short-term memory (LSTM) capable of long-term time series analysis is adopted. The machine learning model may be a machine learning model using an algorithm such as k-Nearest Neighbor, Hotelling's theory, LOF (local outlier factor), or naive Bayesian algorithm instead of a neural network. In addition, various methods such as regression analysis such as multiple regression analysis and multivariate analysis may be used to predict the abnormality probability, in addition to machine learning.

[0068] The trained model 226 has been trained using past data of input / output data of the inspection device 200, the remote control device 300, and the inspection target, past data of the inspection result 222 by the corresponding inspection system 500, past data related to maintenance information, and past data related to normality or abnormality of the remote control device 300, the inspection device 200, and the inspection target. As a learning method for the neural network, a support vector machine (SVM) or a backpropagation method is preferably used. Note that, not limited to both the input data and the output data of each device, only either the input data or the output data may be input to the machine learning model. By inputting the input / output data at the time of inspection of the inspection device 200, the remote control device 300, and the inspection target, and the maintenance information into the trained model 226, the abnormality probability of each of the inspection device 200, the remote control device 300, and the inspection target is output. At this time, for example, within a predetermined period from the timing of performing maintenance, the probability that the device on which the maintenance has been performed is free of abnormality is higher than the probability in a period in which the maintenance has not been performed.

[0069] 7 is a flowchart showing a processing routine of the anomaly identification step according to the second embodiment. In step S300, a machine learning model is trained using past data of the inspection device 200, the remote control device 300, and the input / output data of the inspection target, past data of the inspection results 222 by the corresponding inspection system 500, past data related to maintenance information, and past data related to normality or abnormality of the remote control device 300, the inspection device 200, and the inspection target. Step S300 is also called a "learning step." The learning step may be performed in advance separately from the anomaly identification step.

[0070] In step S302, the anomaly identifying unit 216 inputs the input / output data of the inspection target to the trained model 226. The input / output data of the inspection target is, for example, various input / output data obtained from the vehicle 100 during the inspection shown in Fig. 4, such as the rotation speed of the motor 140 of the vehicle 100 at the time of the inspection, the vehicle speed data 322 which is the vehicle side speed obtained from the wheel speed sensor 170, the control value for each actuator of the vehicle 100 by the driving control unit 184, and the output value of each actuator. Note that, from the various input / output data obtained from the vehicle 100, only factors significant to the inspection result may be extracted.

[0071] In step S310, the anomaly identifying unit 216 inputs the input / output data of the remote control device 300 to the trained model 226. The input / output data of the remote control device 300 refers to various input / output data obtained from the remote control device 300 during the inspection shown in Fig. 4, such as the control value transmitted from the remote control device 300 to the vehicle 100 during remote control during the inspection, the inspection time, and the vehicle speed data 322. Of the various input / output data obtained from the remote control device 300, only factors significant to the inspection result may be extracted.

[0072] In step S320, the anomaly identifying unit 216 inputs input / output data of the inspection device 200 to the trained model 226. The input / output data of the inspection device 200 refers to various input / output data obtained from the inspection device 200 during the inspection shown in Fig. 4, such as the inspection side speed obtained from the roller device 250, the torque, rotation number, and rotation speed of the motor 252 and roller 256 during the inspection, the inspection time, and the inspection result 222. Note that only factors significant to the inspection result may be extracted from the various input / output data obtained from the inspection device 200.

[0073] In step S330, the anomaly identifying unit 216 acquires the maintenance information 224, 324 and inputs it to the trained model 226. Of the maintenance information 224, 324, only factors that are significant for the inspection results may be extracted and input to the trained model 226.

[0074] In step S340, the trained model 226 outputs the anomaly probability for each of the inspection device 200, the remote control device 300, and the inspection target based on the data input in steps S302 to S330. In step S350, the anomaly identification unit 216 compares each anomaly probability with a threshold value arbitrarily set in advance to identify the cause of the anomaly. For example, the anomaly identification unit 216 identifies a device or an inspection target whose anomaly probability is equal to or greater than a predetermined threshold value as the cause of the anomaly.

[0075] As described above, the inspection method of the present embodiment further includes a learning step of learning a machine learning model using past data related to the input / output of the remote control device 300, past data related to the input / output of the inspection device 200, past data related to the maintenance information 324, and past data related to normality or abnormality of the remote control device 300, the inspection device 200, and the inspection target. In the anomaly identification step, the trained model 226 is used to identify which of the remote control device 300, the inspection device 200, and the inspection target has an abnormality. Therefore, by using the trained model 226, it is possible to improve the productivity of the anomaly identification step and the accuracy of identifying the cause of the abnormality.

[0076] C. Third embodiment: FIG. 8 is a flowchart showing a processing routine of an abnormality identification step of the inspection method according to the third embodiment. In this embodiment, the abnormality identification step differs from the abnormality identification step of the inspection method according to the first embodiment in that it includes steps S120c and S170c instead of steps S120 and S170, and further includes steps S122 and S172. In the above-described first embodiment, an example was shown in which the timing of maintenance execution, out of the maintenance information, is used to identify the cause of the abnormality. In contrast, in this embodiment, information out of the maintenance information, regarding whether or not an abnormality was detected in the remote control device 300 and the inspection device 200 during maintenance, is used to identify the cause of the abnormality.

[0077] In step S120c, the abnormality identification unit 216 checks the maintenance information and checks whether the maintenance information includes information indicating that an abnormality was detected in the remote control device 300 during maintenance. In this case, the "abnormality" does not have to include a minor abnormality that does not impair the function of the remote control device 300. Furthermore, the maintenance to be checked for whether an abnormality was detected is not limited to all maintenance performed in the past, and may be only maintenance within a predetermined period of time or the most recent maintenance, or may be a predetermined number of maintenances performed in the past.

[0078] If the maintenance information does not include information indicating that an abnormality in the remote control device 300 was detected during maintenance (S120c: NO), the abnormality identification unit 216 transitions the process to step S130. If the maintenance information includes information indicating that an abnormality in the remote control device 300 was detected during maintenance (S120c: YES), the abnormality identification unit 216 transitions the process to step S122.

[0079] In step S122, the abnormality identification unit 216 further checks the maintenance information 324 to check whether the cause of the abnormality detected in step S120c has already been removed. "The cause of the abnormality has been removed" means that the cause of the abnormality has been identified, the identified cause has been removed, and the target device has been brought into a state in which it can be sufficiently estimated that it can operate normally. For example, if an abnormality caused by a component failure is detected during maintenance and the failed component has been replaced with a new one, this corresponds to a state in which the component that caused the abnormality has been removed.

[0080] If the maintenance information does not include information that the cause of the abnormality of the remote control device 300 has been removed (S122: NO), the abnormality identifying unit 216 transitions to step S150 and outputs a message indicating that there is an abnormality in the remote control device 300. That is, the auxiliary inspection, which is a identifying step for identifying whether or not there is an abnormality in the remote control device 300, is omitted, and an abnormality output step of outputting a message indicating that there is an abnormality in the remote control device 300 is executed.

[0081] When the maintenance information includes information indicating that the cause of the abnormality of the remote control device 300 has been removed (S122: YES), the abnormality identifying unit 216 shifts the process to step S130 and executes the auxiliary inspection. In other words, since maintenance was performed on the remote control device 300 and an abnormality was detected during the maintenance, the presence or absence of an abnormality in the remote control device 300 is confirmed by the auxiliary inspection. However, this is not limited to the above, and when it is sufficiently possible to estimate that the abnormality of the remote control device 300 has been removed and that the remote control device 300 will operate normally, the abnormality identifying unit 216 may determine that there is no abnormality in the remote control device 300, omit the auxiliary inspection, and shift the process to step S170c.

[0082] In step S170c, the abnormality identifying unit 216 checks the maintenance information and checks whether the maintenance information includes information indicating that an abnormality was detected in the inspection device 200 during maintenance. In this case, the "abnormality" does not have to include a minor abnormality that does not impair the function of the inspection device 200. If the maintenance information does not include information indicating that an abnormality was detected in the inspection device 200 during maintenance (S170c: NO), the abnormality identifying unit 216 shifts the process to step S180. If the maintenance information includes information indicating that an abnormality was detected in the inspection device 200 during maintenance (S170c: YES), the abnormality identifying unit 216 shifts the process to step S172.

[0083] In step S172, the abnormality identifying unit 216 further checks the maintenance information 224 to check whether the cause of the abnormality detected in step S170c has already been removed. If the cause of the abnormality in the inspection device 200 has not been removed (S172: NO), the abnormality identifying unit 216 transitions the process to step S200 and outputs a message indicating that the inspection device 200 has an abnormality. That is, the subsequent inspection process, which is a specification process for specifying whether the inspection device 200 has an abnormality, is omitted, and an abnormality output process is executed to output a message indicating that the inspection device 200 has an abnormality.

[0084] When the maintenance information includes information indicating that the cause of the abnormality of the inspection device 200 has been removed (S172: YES), the abnormality identifying unit 216 shifts the process to step S180 and executes the subsequent inspection process. In other words, since maintenance was performed on the inspection device 200 and an abnormality was detected during the maintenance, the subsequent inspection process is performed to check whether or not there is an abnormality in the inspection device 200. However, this is not limited to the above, and when it is sufficiently possible to estimate that the inspection device 200 will operate normally after the abnormality of the inspection device 200 has been removed, the abnormality identifying unit 216 may determine that there is no abnormality in the inspection device 200, omit the subsequent inspection process, and shift the process to step S220.

[0085] As described above, according to the inspection method of the present embodiment, the abnormality identifying unit 216 checks, as the maintenance information, information on whether or not an abnormality has been detected in at least either of the remote control device 300 and the inspection device 200 during maintenance. By using the simple method of checking the presence or absence of an abnormality during maintenance, the cause of the abnormality can be identified with high reliability.

[0086] According to the inspection method of this embodiment, in the abnormality identification process, if the maintenance information includes information indicating that an abnormality has been detected in either the remote control device 300 or the inspection device 200 during maintenance, and further includes information that a component that caused the abnormality in either device in which the abnormality was detected has been replaced, a process for identifying the device in which the component that caused the abnormality has been replaced is executed. Even if an abnormality is detected during maintenance, if the cause of the abnormality is removed, there is a possibility that the device is not abnormal. Therefore, it is possible to execute appropriate abnormality cause identification taking into account the case where the abnormality during maintenance is repaired.

[0087] D. Fourth embodiment: 9 is a flowchart showing a processing routine of an abnormality identification step of the inspection method according to the fourth embodiment. In this embodiment, the abnormality identification step differs from the abnormality identification step of the inspection method according to the first embodiment in that steps S120d and S170d are provided instead of steps S120 and S170. In the above-described first embodiment, an example was shown in which the timing of execution of maintenance was used among the maintenance information. In contrast, in this embodiment, information regarding whether or not abnormalities in the remote control device 300 and the inspection device 200 were detected continuously or intermittently during maintenance is used among the maintenance information.

[0088] In step S120d, the abnormality identification unit 216 checks the maintenance information and checks whether the maintenance information includes information indicating that an abnormality has been continuously or intermittently detected in the remote control device 300 during maintenance. "Continuous detection of abnormality" means that an abnormality has been continuously detected in maintenance operations that are equal to or greater than two predetermined first thresholds. The first threshold may be set using any number of times that is estimated to be sufficiently high that the probability of an abnormality in the target device is high. "Intermittent detection of abnormality" means that an abnormality has been detected within a predetermined period or in a predetermined number of maintenance operations that are equal to or greater than two predetermined second thresholds. The predetermined period and number of times and the second threshold may be set using any period and number of times that is estimated to be sufficiently high that the probability of an abnormality in the target device is high. In this case, "an abnormality detected continuously or intermittently" does not have to include a minor abnormality that does not impair the function of the remote control device 300. An abnormality that is detected continuously or intermittently may include both a case where the same abnormality is detected continuously or intermittently, and a case where different abnormalities are detected continuously or intermittently.

[0089] If the maintenance information does not include information indicating that a continuous or intermittent abnormality was detected in the remote control device 300 during maintenance (S120d: NO), the abnormality identification unit 216 moves the process to step S130. If the maintenance information includes information indicating that a continuous or intermittent abnormality was detected (S120d: YES), the abnormality identification unit 216 moves the process to step S150 and executes an output indicating that the remote control device 300 has an abnormality. In other words, the device in which a continuous or intermittent abnormality is detected is assumed to have a high possibility of the abnormality recurring, and the auxiliary inspection or subsequent inspection, which is the identification step, is omitted, and an abnormality output step is executed to output that the device has an abnormality. Note that in this embodiment, it is preferable not to apply the case where the abnormality is removed as in step S122 shown in FIG. 8.

[0090] In step S170d, similarly to step S120d, the anomaly identifying unit 216 checks the maintenance information and checks whether the maintenance information includes information indicating that an anomaly has been continuously or intermittently detected in the inspection device 200 during maintenance. In this case, the "anomaly detected continuously or intermittently" does not have to include a minor anomaly that does not impair the function of the inspection device 200. In addition, the anomaly detected continuously or intermittently may include both a case in which the same anomaly is detected continuously or intermittently and a case in which different anomalies are detected continuously or intermittently.

[0091] If the maintenance information does not include information indicating that a continuous or intermittent abnormality was detected in the inspection device 200 during maintenance (S170d: NO), the abnormality identifying unit 216 transitions the process to step S180. If the maintenance information includes information indicating that a continuous or intermittent abnormality was detected (S170d: YES), the abnormality identifying unit 216 transitions the process to step S200 and executes an output indicating that an abnormality exists in the inspection device 200. Note that in this embodiment, it is preferable not to apply the case where the abnormality is removed as in step S172 shown in FIG. 8.

[0092] As described above, according to the inspection method of the present embodiment, the abnormality identifying unit 216 checks, as maintenance information, information regarding whether or not an abnormality has been detected continuously or intermittently in at least any of the devices during maintenance of the remote control device 300 and the inspection device 200. By using the simple method of checking whether or not an abnormality has occurred continuously or intermittently during maintenance, the cause of the abnormality can be identified with high reliability.

[0093] According to the inspection method of this embodiment, in the anomaly identification step, if the maintenance information includes information indicating that an anomaly has been continuously or intermittently detected in either the remote control device 300 or the inspection device 200 during maintenance, an output is made indicating that an anomaly has occurred in the device in which the anomaly has been detected. Therefore, the identification step can be omitted and the anomaly identification step can be simplified by the simple method of checking for the presence or absence of a continuous or intermittent anomaly during maintenance.

[0094] E. Fifth embodiment: FIG. 10 is a flowchart showing a processing routine of the inspection method according to the fifth embodiment. In the inspection method according to the first embodiment, an example of inspecting an abnormality related to the traveling speed of the vehicle 100 is shown, but in the inspection method according to the present embodiment, whether the brake 162 of the vehicle 100 operates properly is inspected. As shown in FIG. 11, this flow differs from the inspection method according to the first embodiment shown in FIG. 4 in that steps S30e, S50e, S70e, and S80e are provided instead of steps S30, S50, S70, and S80, that step S72 is further provided, and that step S40 is not provided. Note that this flow may be continuously executed while the vehicle 100 is placed in the inspection device 200, for example, after the inspection according to the first embodiment is completed. In this case, steps S10 and S20 of this flow can be omitted.

[0095] In step S30e, the inspection unit 214 issues an instruction to the vehicle 100 to be inspected to operate the brake 162, which is a stopping unit, to stop the rotation of the wheels 160, i.e., to stop the running operation of the vehicle 100. More specifically, the inspection unit 214 outputs a command signal to the remote control device 300 to operate the brake 162 so as to achieve a braking force as a predetermined target value. The remote control unit 312 that receives the command signal operates the brake 162 of the vehicle 100 to be inspected by remote control so as to achieve a predetermined braking force, thereby stopping the running operation of the vehicle 100. Step S30e is also referred to as a "stop instruction process".

[0096] In step S50e, the remote control unit 312 outputs to the inspection device 200 a message indicating that the brake 162 has been operated according to the target value. In step S70e, the inspection unit 214 drives the motor 252 of the roller device 250 to rotate the roller 256. Specifically, the inspection unit 214 rotates the roller 256 in contact with the wheel 160 to apply an external force to the wheel 160 for rotating the wheel 160 in the forward direction. The "external force for rotating the wheel 160 in the forward direction" is, for example, a force applied to the outer periphery of the roller 256 by the motor 252, or a torque of the roller 256 corresponding to the force. The inspection unit 214 gradually increases the torque of the roller 256 until the rotation of the wheel 160 is detected by the speed sensor 254 or the like.

[0097] In step S72, when roller 256 rotates, inspection unit 214 detects the rotation of roller 256, i.e., the rotation of wheel 160, by speed sensor 254. Inspection unit 214 acquires the torque applied to roller 256 at the timing of detecting the rotation of wheel 160. Steps S70e and S72 are also referred to as an "external force acquisition step."

[0098] In step S80e, it is confirmed whether the difference between the torque applied to the roller 256 at the timing when the rotation of the wheel 160 is detected and the torque corresponding to the braking force as a target value is within a predetermined target external force range. The target external force range can be set to any range, such as ±5 Nm (Newton-meter) for torque or ±5 N (Newton) for external force. In step S80e, it is possible to check whether the brake 162 is applying a braking force to the wheel 160 according to the target value. In addition, it is also possible to check for a defect in which the wheel 160 does not rotate even when a predetermined external force is applied with the brake 162 activated.

[0099] If the difference between the torque applied to roller 256 and the torque corresponding to the braking force as the target value is within the target external force range (S80e: YES), inspection unit 214 shifts the process to step S84 and outputs that there is no abnormality. If the difference between the torque applied to roller 256 and the torque corresponding to the braking force as the target value is outside the target external force range (S80e: NO), inspection unit 214 shifts the process to step S82, determines that there is an abnormality, and shifts to step S100e to execute the abnormality identification process according to the second embodiment.

[0100] 11 is a flowchart showing a processing routine of an anomaly identifying step in an inspection method according to the fifth embodiment. The present embodiment is different from the anomaly identifying step shown in the first embodiment in that step S140e is provided instead of step S140 and step S190e is provided instead of step S190, but otherwise is the same.

[0101] In step S140e, the result of the inspection using a normal vehicle 100 is confirmed. More specifically, steps S10 to S80e shown in FIG. 10 are executed using a normal vehicle 100. It is inspected for a plurality of vehicles 100 whether the difference between the torque applied to the roller 256 and the torque corresponding to the braking force as the target value is within the auxiliary target external force range. The auxiliary target external force range can be set in the same manner as the target external force range. In this embodiment, the auxiliary target external force range is the same range as the target external force range. In a normal vehicle 100, if the difference between the torque of the roller 256 and the torque of the target value is outside the auxiliary target external force range (S140e: NO), the process proceeds to step S170, and an output is issued indicating that there is an abnormality in the remote control device 300.

[0102] In step S190e, the results of the inspection using the multiple vehicles 100 are confirmed. More specifically, steps S10 to S80e shown in Fig. 10 are executed using the multiple vehicles 100. If the difference between the torque of the rollers 256 and the torque of the target value is within a predetermined subsequent target external force range in all of the multiple vehicles 100 (S190e: YES), the process proceeds to step S1220, and an output is issued indicating that an abnormality has occurred in the inspection target.

[0103] If the difference between the torque of the rollers 256 and the target torque value is outside a predetermined subsequent target external force range in at least one vehicle 100 among the multiple vehicles 100 (S190e: NO), the process proceeds to step S200, and an output is issued indicating that there is an abnormality in the inspection device 200. In this embodiment, the subsequent target external force range is set to the same range as the target external force range.

[0104] As described above, according to the inspection method of this embodiment, in the inspection of the brakes 162 of the vehicle 100 that runs by remote control, as in the above-described first embodiment, it is possible to identify that the cause of the abnormality is the remote control device 300 among the vehicle 100 to be inspected, the inspection device 200, and the remote control device 300. Also, in the inspection of the brakes 162, as in the above-described first embodiment, the maintenance information is used to simplify the abnormality identification process, thereby improving productivity.

[0105] F. Other Embodiments: (F1) In the above embodiments, examples have been shown in which results of maintenance performed on both the remote control device 300 and the inspection device 200 and maintenance information relating to the history of the maintenance are utilized. In contrast, results of maintenance performed on either one of the remote control device 300 or the inspection device 200 and maintenance information relating to the history of the maintenance may be utilized.

[0106] (F2) In the above third embodiment, an example of the inspection method including steps S122 and S172 has been described. In contrast, either step S122 or step S172 may not be included, and both steps S122 and S172 may not be included. When step S122 is omitted, if the maintenance information includes information indicating that an abnormality has been detected in the remote control device 300 during maintenance (S120c: YES), the abnormality identifying unit 216 determines that there is an abnormality in the remote control device 300 and shifts the process to step S150. When step S172 is omitted, if the maintenance information includes information indicating that an abnormality has been detected in the inspection device 200 during maintenance (S170c: YES), the abnormality identifying unit 216 determines that there is an abnormality in the inspection device 200 and shifts the process to step S150.

[0107] According to the inspection method configured in this manner, when the maintenance information includes information indicating that an abnormality has been detected during maintenance in either the remote control device 300 or the inspection device 200, the abnormality identification step is omitted to determine whether or not there is an abnormality in the device in which the abnormality has been detected, and a determination is made that there is an abnormality in the device in which the abnormality has been detected. Therefore, the abnormality identification step can be simplified by the simple method of checking whether or not there is an abnormality during maintenance.

[0108] (F3) In the above embodiments, an inspection method for inspecting whether the traveling speed of the vehicle 100 and the brake 162 of the vehicle 100 are appropriate has been described as an example. In contrast, the present disclosure can be applied to an inspection method for inspecting the appropriateness of detection values ​​by various detectors provided on the vehicle 100, such as an acceleration sensor, a sensor for detecting the charging rate of the battery 120, and a sensor for detecting the distance to a target outside the vehicle 100.

[0109] (F4) In the above embodiment, an example was shown in which, in step S180, a plurality of vehicles 100 scheduled to be inspected immediately after the inspection target vehicle 100 are used as the plurality of vehicles 100 different from the inspection target. In contrast, a plurality of arbitrarily selected vehicles 100 not related to the inspection schedule may be used.

[0110] (F5) In each of the above embodiments, an example was shown in which the CPU 310 of the remote control device 300 functions as the remote control unit 312, the maintenance information acquisition unit 314, the vehicle speed acquisition unit 316, and the vehicle information acquisition unit 318. However, all or part of the functions of the remote control unit 312, the maintenance information acquisition unit 314, the vehicle speed acquisition unit 316, and the vehicle information acquisition unit 318 may be realized by the CPU 212 of the inspection control device 210.

[0111] (F6) In the above first embodiment, an example was shown in which the subsequent inspection process is executed when the difference between the acquired inspection side speed and the target value is outside the second range in the vehicle 100 that is normal in the auxiliary inspection. In contrast, the subsequent inspection process may be omitted. In this case, a process may be provided in which, in step S140, when the difference between the acquired inspection side speed and the target value is within the second range in the normal vehicle 100, an output is issued to the effect that there is an abnormality in either the inspection target or the inspection device 200, or that there is no abnormality in the remote control device 300.

[0112] (F7) In the above first embodiment, when an output is given indicating that the inspection target has an abnormality, the inspection target is moved by remote control to a location where it can be repaired. In contrast, when the inspection target has an abnormality, another process such as a notification to a manager may be executed instead of or in addition to moving the inspection target by remote control.

[0113] (F8) In the above embodiments, the vehicle 100 is a passenger car, a truck, a bus, a construction vehicle, and the like. However, the vehicle 100 is not limited to these, and may include various automobiles such as two-wheeled vehicles and four-wheeled vehicles, trains, and the like. Also, various moving bodies other than the vehicle 100 may be used. "Moving body" means an object that can move. Moving bodies include, for example, electric vertical take-off and landing aircraft (so-called flying cars), ships, aircraft, robots, linear motor cars, and the like. In this case, the expressions "vehicle" and "car" in this disclosure can be appropriately replaced with "moving body", and the expression "running" can be appropriately replaced with "moving". Moreover, the inspection device 200 detects the moving motion of the moving part that moves the moving body instead of the rotation of the wheels 160, and acquires the inspection side speed of the moving moving body.

[0114] (F9) The vehicle 100 may have a configuration capable of moving by remote control. For example, the vehicle 100 may be in the form of a platform having the configuration described below. Specifically, the vehicle 100 may have a configuration for performing the functions of "running," "turning," and "stopping" by remote control. That is, the "vehicle 100 capable of moving by remote control" may not have at least some of the interior parts such as the driver's seat and dashboard attached, may not have at least some of the exterior parts such as the bumper and fender attached, and may not have a body shell attached. In this case, the remaining parts such as the body shell may be attached to the vehicle 100 before the vehicle 100 is shipped from the factory, or the remaining parts such as the body shell may be attached to the vehicle 100 after the vehicle 100 is shipped from the factory in a state in which the remaining parts such as the body shell are not attached to the vehicle 100.

[0115] (F10) In the inspection method of each of the above embodiments, in the abnormality identification step, if it is within a predetermined period from the acquired timing of performing maintenance, an example has been shown in which the auxiliary inspection and the subsequent inspection are omitted and the normal output step is executed. In contrast, regardless of the timing of performing maintenance, the auxiliary inspection and the subsequent inspection may be omitted, or the normal output step may be executed, triggered by the performance of maintenance.

[0116] (F11) In the inspection method of the third embodiment described above, an example was shown in which the anomaly identification step includes an anomaly output step in which, if an anomaly is detected in either the remote control device 300 or the inspection device 200 during maintenance, the auxiliary inspection and the subsequent inspection are omitted and an output is made indicating that the device in which the anomaly is detected has an anomaly. In contrast, in the case of an inspection method that uses the trained model 226 as in the second embodiment, the identification step does not need to be omitted and the anomaly output step does not need to be executed.

[0117] (F12) In the inspection method of the fourth embodiment described above, an example was shown in which the anomaly identification step includes an anomaly output step in which, if an anomaly is continuously or intermittently detected in either the remote control device 300 or the inspection device 200 during maintenance, the auxiliary inspection and the subsequent inspection are omitted and an output is made indicating that the device in which the anomaly is detected has an anomaly. In contrast, in the case of an inspection method that uses the trained model 226 as in the second embodiment, the identification step does not need to be omitted and the anomaly output step does not need to be executed.

[0118] The control and the method described in the present disclosure may be realized by a special-purpose computer provided by configuring a processor and a memory programmed to execute one or more functions embodied in a computer program. Alternatively, the control unit and the method described in the present disclosure may be realized by a special-purpose computer provided by configuring a processor with one or more dedicated hardware logic circuits. Alternatively, the control unit and the method described in the present disclosure may be realized by one or more special-purpose computers configured by a combination of a processor and a memory programmed to execute one or more functions and a processor configured with one or more hardware logic circuits. In addition, the computer program may be stored in a computer-readable non-transitory tangible recording medium as instructions executed by a computer.

[0119] The present disclosure is not limited to the above-mentioned embodiment, and can be realized in various configurations without departing from the spirit of the present disclosure. For example, the technical features in the embodiments corresponding to the technical features in each aspect described in the Summary of the Invention column can be appropriately replaced or combined to solve some or all of the above-mentioned problems or to achieve some or all of the above-mentioned effects. Furthermore, if the technical feature is not described as essential in this specification, it can be appropriately deleted. [Explanation of symbols]

[0120] 70...access point, 72...network, 100...vehicle, 120...battery, 140...motor, 150...power receiving device, 160...wheel, 162...brake, 170...wheel speed sensor, 180...ECU, 182...CPU, 184...driving control unit, 186...storage device, 188...vehicle speed data, 190...vehicle communication unit, 200...inspection device, 210, 210b...inspection control device, 212...CPU, 214...inspection unit, 216...abnormality identification unit, 218...maintenance information acquisition unit, 220, 220b...storage device, 222...inspection results, 224...maintenance information, 226...trained model, 250...roller device, 252...motor, 254...speed sensor, 256...roller, 290...inspection communication unit, 300...remote control device, 310...CPU, 312...remote control unit, 314...maintenance information acquisition unit, 316...vehicle speed acquisition unit, 318...vehicle information acquisition unit, 320...storage device, 322...vehicle speed data, 324...maintenance information, 390...remote communication unit, 500...inspection system

Claims

1. A method for inspecting a movable object that can be moved by remote control, comprising the steps of: a first step of giving an instruction from a remote control device to a moving object as an inspection target to drive the moving object so that an output value related to the movement of the moving object becomes a predetermined target value; a second step of measuring the output value using an inspection device that inspects the moving body and acquiring a measurement value; a maintenance information acquisition step of acquiring maintenance information relating to a history of maintenance performed on at least one of the remote control device and the inspection device; and an abnormality identification process for identifying, when a difference between the target value and the measured value is not within a predetermined reference range, which of the remote control device, the inspection device, or the inspection object has an abnormality by using the acquired maintenance information. Testing method.

2. The inspection method according to claim 1, The maintenance information is information regarding the timing of execution of the maintenance on at least one of the devices. Testing method.

3. The inspection method according to claim 2, In the abnormality identification step, when the timing at which the second step was performed is within a predetermined period from the execution timing included in the acquired maintenance information, it is determined that there is no abnormality in the device on which the maintenance was performed. Testing method.

4. The inspection method according to claim 1, Further, a learning process is provided for learning a machine learning model using past data on input / output of the remote control device, past data on input / output of the inspection device, past data on the maintenance information, and past data on normality or abnormality of the remote control device, the inspection device, and the inspection target, In the anomaly identification step, it is identified which of the remote control device, the inspection device, and the inspection target has an anomaly by using the trained machine learning model. Testing method.

5. The inspection method according to claim 4, In the abnormality identification step, when the second step is performed within a predetermined period from the execution timing of the maintenance performed on at least any one of the devices, an output is executed to the effect that the probability that the device on which the maintenance has been performed is free of an abnormality is higher than the probability that the maintenance has not been performed. Testing method.

6. The inspection method according to claim 1, The maintenance information is information regarding whether or not an abnormality has been detected in at least any of the devices during the maintenance. Testing method.

7. 7. The inspection method according to claim 6, In the abnormality identification step, when the maintenance information includes information indicating that an abnormality has been detected in at least one of the devices during the maintenance, it is determined that an abnormality exists in at least one of the devices in which the abnormality has been detected. Testing method.

8. 7. The inspection method according to claim 6, In the abnormality identification step, if the maintenance information includes information indicating that an abnormality has been detected in the maintenance of at least one of the devices, and further includes information that a member that caused the abnormality in at least one of the devices in which the abnormality has been detected has been replaced, it is determined that there is no abnormality in the at least one of the devices in which the abnormality has been detected, or a identification step is executed to identify whether or not there is an abnormality in the at least one of the devices in which the abnormality has been detected. Testing method.

9. The inspection method according to claim 1, The maintenance information is information regarding whether or not an abnormality in at least any of the devices is detected continuously or intermittently during the maintenance. Testing method.

10. The inspection method according to claim 9, In the abnormality identification step, when the maintenance information includes information indicating that an abnormality has been continuously or intermittently detected in at least one of the devices during the maintenance, an output is made indicating that an abnormality exists in at least one of the devices in which the continuous or intermittent abnormality has been detected. Testing method.

Citation Information

Patent Citations

  • Method for predicting vehicle remote control failure in advance, vehicle control unit and remote controller

    CN115431997A

  • JP1975136801A

  • Travel testing apparatus of automatic guided vehicle

    JP2008101993A

  • Transfer system of vehicle

    JP2021062790A

  • Self-propelled vehicle power train evaluation

    US4610159A

Cited By

  • Motor inspection device, motor inspection method, and program

    JP2026145608A

  • Motor inspection method, motor inspection device, and program

    JP2026145699A

  • Motor inspection device, motor inspection method, and program

    JP2026145828A

  • Motor inspection method, motor inspection device, and program

    JP7707463B1

  • Motor inspection device, motor inspection method, and program

    JP7751763B1