Diagnostic system and diagnostic method

The diagnostic system allows manufacturers to set judgment conditions for vehicle diagnostics through a communication device and platform, addressing the challenge of high development costs and enabling automated vehicle condition assessment.

JP7771728B2Active Publication Date: 2025-11-18SHIMADZU SEISAKUSHO LTD
View PDF 9 Cites 0 Cited by

Patent Information

Application Number
JP2021207761
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-12-22
Publication Date
2025-11-18
Estimated Expiration
2041-12-22

AI Technical Summary

Technical Problem

Developing a diagnostic system for mobile objects like cargo handling vehicles requires advanced system technology and high development costs, which is challenging for providers of varying sizes, even if they have sensor-based diagnosis know-how.

Method used

A diagnostic system comprising a communication device, diagnostic unit, memory with a platform, and registration unit that allows manufacturers to set judgment conditions for diagnosing vehicle conditions without requiring system development, using a platform administrator and user-defined settings.

Benefits of technology

Provides a setting environment for automatically diagnosing vehicle conditions, enabling providers to offer diagnostic services without system development costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007771728000001
    Figure 0007771728000001
  • Figure 0007771728000002
    Figure 0007771728000002
  • Figure 0007771728000003
    Figure 0007771728000003
Patent Text Reader

Abstract

To provide a necessary setting environment for automatically diagnosing the state of a cargo vehicle without requiring system development from a coachbuilder.SOLUTION: A diagnosis system (1) includes a communication device (80), a diagnosis unit that diagnoses the state of a cargo vehicle (10) on the basis of sensor detection information inputted to the communication device (80), a memory (102) in which a diagnosis platform is constructed, and a registration unit that registers, into the platform, a determination condition for diagnosing the state of the cargo vehicle (10) on the basis of a plurality of sensor detection information sets. A terminal device registers a determination condition for diagnosing the state of the cargo vehicle (10) into the diagnosis platform in response to a user operation, and the diagnosis unit outputs diagnosis information based on the determination condition registered in the diagnosis platform (S13).SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present disclosure relates to diagnostic systems and methods. [Background technology]

[0002] Loading vehicles such as trucks and forklifts can be broadly divided into a main body, known as a chassis, and an attached body. Various attached bodies, such as a loading device and a wing body, are attached to the main body depending on the application. For example, a loading device has the function of raising and lowering the loading platform using a hydraulic unit. A truck's wing body has the function of opening both side walls of a box-shaped storage area like wings using a hydraulic unit.

[0003] Generally, the main body of a cargo handling vehicle is manufactured by a vehicle body manufacturer. The body is manufactured by a hydraulic unit manufacturer or the like. The vehicle body manufacturer delivers the main body of the cargo handling vehicle to a body manufacturer. The hydraulic unit manufacturer delivers a hydraulic unit or a body including a hydraulic unit to the body manufacturer. The body manufacturer mounts the body on the vehicle main body. This completes the cargo handling vehicle. The body manufacturer delivers the cargo handling vehicle to a transportation company. The body manufacturer visits the transportation company as needed to perform maintenance on the cargo handling vehicle.

[0004] Patent Document 1 describes that it is important to detect an abnormality in the hydraulic pressure device, which is the power source of the cargo handling device, early on and repair the hydraulic pressure device before it breaks down. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Publication No. 2020-133817 Summary of the Invention [Problem to be solved by the invention]

[0006] It is important to detect abnormalities in the hydraulic system or other components of the vehicle at an early stage and to notify the user of the abnormality. A vehicle must be able to perform its basic functions as a moving object. Therefore, it is desirable for providers of vehicles to provide users with a diagnostic service that can comprehensively diagnose the condition of the vehicle, including the running system.

[0007] Generally, mobile objects, including cargo handling vehicles, are composed of various devices, including running devices. The status of the various devices that make up the mobile object can be diagnosed by using the signals output by sensors attached to these devices. Providers of mobile objects, such as vehicles, will likely consider developing more useful diagnostic systems by utilizing their own know-how for appropriately diagnosing the status of the various devices that make up the mobile object, such as the locations at which sensors are attached and the conditions for determining abnormalities based on sensor signals.

[0008] However, developing a diagnostic system often requires advanced system technology and high development costs. Because providers vary in size, it is difficult for all providers to develop their own diagnostic systems, even if they have know-how in sensor-based diagnosis.

[0009] An object of the present disclosure is to provide a setting environment necessary for automatically diagnosing the condition of a mobile object, such as a cargo handling vehicle, to a party that provides the mobile object to a user, without requiring system development. [Means for solving the problem]

[0010] A diagnostic system according to one aspect of the present disclosure is a diagnostic system for diagnosing the condition of a moving body, comprising: a communication device mounted on the moving body and communicating with multiple sensors provided on the moving body; a diagnostic unit for diagnosing the condition of the moving body based on detection information from the multiple sensors input to the communication device; a memory managed by a platform administrator and having a platform built therein that accepts settings for diagnosing the condition of the moving body; and a registration unit for registering in the platform judgment conditions for diagnosing the condition of the moving body based on the detection information from the multiple sensors, the judgment conditions being determined by a user who is different from the platform administrator and is the manufacturer of the moving body or components of the moving body; and the diagnostic unit outputs diagnostic information based on the judgment conditions registered in the platform.

[0011] A diagnostic method according to an aspect of the present disclosure is a diagnostic method for diagnosing the condition of a mobile body, the mobile body being equipped with a communication device that communicates with a plurality of sensors provided on the mobile body, and including the steps of acquiring detection information from the plurality of sensors from the communication device, accessing a platform managed by a platform administrator that accepts settings for diagnosing the condition of the mobile body, registering judgment conditions for diagnosing the condition of the mobile body based on the detection information from the plurality of sensors in the platform, the judgment conditions being determined by a user who is different from the platform administrator and is the manufacturer of the mobile body or a component of the mobile body, and outputting diagnostic information based on the judgment conditions registered in the platform. [Effects of the Invention]

[0012] According to the present disclosure, it is possible to provide a setting environment necessary for automatically diagnosing the condition of a mobile object such as a loading vehicle to a user without the need for system development. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram illustrating a configuration of a diagnostic system (first embodiment). [Figure 2]FIG. 1 is a diagram showing a cargo handling vehicle equipped with a hydraulic unit. [Figure 3] FIG. 10 is a diagram illustrating communication between a management device and a sensor of a cargo handling vehicle used by a transportation company. [Figure 4] FIG. 1 is a block diagram showing a configuration of a communication device. [Figure 5] FIG. 2 is a diagram illustrating a channel configuration of a communication device. [Figure 6] FIG. 10 is a diagram illustrating an example of diagnostic information that can be set in the diagnostic platform. [Figure 7] FIG. 2 is a diagram illustrating communication between a management device, a cargo handling vehicle used by a transport company, and a terminal device used by a body manufacturer. [Figure 8] FIG. 2 is a diagram illustrating an example of data managed by a management device. [Figure 9] 10 is a diagram showing an example of diagnostic setting information managed by the management device for each vehicle model ID. FIG. [Figure 10] FIG. 10 is a diagram showing a diagnostic setting screen provided by the diagnostic platform. [Figure 11] FIG. 10 is a diagram for explaining diagnostic categories selectable on a diagnostic setting screen. [Figure 12] FIG. 10 is a diagram showing a diagnostic information screen. [Figure 13] FIG. 10 is a diagram showing an example of a data list displayed on a display device of a hydraulic unit manufacturer. [Figure 14] FIG. 10 is a diagram showing an example of a data list of unit IDs set as requiring diagnostic service displayed on a display device of a hydraulic unit manufacturer. [Figure 15] FIG. 10 is a diagram showing an example in which a service fee for a bodybuilding manufacturer is displayed on a display device of a hydraulic unit manufacturer. [Figure 16] FIG. 10 is a diagram showing an example of a data list displayed on a terminal device of a body manufacturer. [Figure 17] FIG. 10 is a diagram showing an example of a service charge being displayed on a display device of a body manufacturer. [Figure 18] 10 is a flowchart showing the flow of processing related to the registration of a unit ID, a body manufacturer ID, and a vehicle registration number, and the setting of a service flag. [Figure 19] 10 is a flowchart showing the flow of a diagnostic setting process. [Figure 20] 10 is a flowchart showing a process flow relating to collection of sensor detection information and output of diagnostic information. [Figure 21] 10 is a flowchart showing a process flow relating to the transmission of diagnostic information and a service fee. [Figure 22] FIG. 10 is a diagram illustrating a configuration of a diagnostic system (second embodiment). [Figure 23] FIG. 10 is a diagram illustrating communication between a management device and a remote device (second embodiment). [Figure 24] FIG. 10 is a diagram showing an example in which the state of a cargo handling vehicle is diagnosed on a communication board provided in a hydraulic unit (third embodiment). [Figure 25] FIG. 10 is a diagram showing an example of diagnosing the state of a cargo handling vehicle in a communication device (Embodiment 4). [Figure 26] FIG. 10 is a diagram illustrating a configuration of a diagnostic system (fifth embodiment). [Figure 27] FIG. 13 is a block diagram showing the configuration of a communication device used in the fifth embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference numerals, and description thereof will not be repeated.

[0015] Embodiment 1 <System configuration> Figure 1 shows the configuration of the diagnostic system 1. The diagnostic system 1 functions in conjunction with the business flows of hydraulic unit manufacturers, vehicle manufacturers, body manufacturers, and transportation companies. Figure 1 shows the processing flow, including the business flows of each of these manufacturers or companies, along with step numbers.

[0016] The vehicle manufacturer manufactures the body of the cargo handling vehicle 10. The body of the cargo handling vehicle 10 is also called a chassis. The body includes, for example, a main body including seats and a loading platform also called a body. The vehicle manufacturer delivers the manufactured vehicle bodies to various bodybuilding manufacturers A, B, ... of different scales (step S1).

[0017] The hydraulic unit manufacturer manufactures the hydraulic unit 14, which is an example of a unit that constitutes at least a part of the body. The hydraulic unit manufacturer has a management device 100 installed. The hydraulic unit manufacturer manages each of the manufactured hydraulic units 14 using a serial number in the management device 100. This serial number is called a unit ID. The hydraulic unit 14 is equipped with a communication device 80 that stores the unit ID. Each hydraulic unit 14 can be identified by the unit ID. The communication device 80 has a function to communicate with the management device 100. The unit ID is an example of first identification information. The hydraulic unit manufacturer is the administrator of the diagnostic platform, which will be described later.

[0018] The hydraulic unit manufacturer delivers the hydraulic units 14 equipped with the communication devices 80 to various body manufacturers A, B, . . . of different scales (step S2).

[0019] The body manufacturer mounts the hydraulic unit 14 on the vehicle body (step S3). This allows various types of cargo handling vehicles 10 to be assembled, such as gate vehicles, wing vehicles, and forklifts. Figure 1 shows a gate vehicle as an example of the cargo handling vehicle 10.

[0020] The bodybuilder attaches sensors 40 to various devices constituting the cargo handling vehicle 10, such as a battery unit and an engine unit, which are components other than the hydraulic unit (step S4). The bodybuilder attaches sensors 40 required for each vehicle model of the cargo handling vehicle 10 at required locations. The bodybuilder may attach sensors 40 to various parts constituting the hydraulic unit 14. Alternatively, manufacturers of components other than the hydraulic unit may themselves attach sensors 40 required for those components at required locations. Alternatively, vehicle manufacturers may attach sensors 40 required for the vehicle at required locations. The diagnostic system 1 according to this embodiment diagnoses the conditions of the various devices constituting the cargo handling vehicle 10 based on signals output by these sensors 40. Bodybuilders and component manufacturers will likely utilize their own know-how to devise locations for attaching sensors 40 for each vehicle model. Note that the hydraulic unit manufacturer may attach various sensors 40 to the hydraulic unit 14 in advance. In the following, for simplicity of explanation, bodybuilders and component manufacturers will be referred to simply as bodybuilders.

[0021] The body manufacturer connects the wiring of the sensor 40 to the communication device 80 (step S5).

[0022] The bodybuilder delivers the assembled cargo handling vehicle 10 to various transport companies X, Y, . . . of different scales (step S6).

[0023] The transportation company applies to a national agency for registration of the cargo handling vehicle 10. The transportation company notifies the original body manufacturer of the vehicle registration number issued upon the registration application (step S7). For example, a person in charge at the transportation company may use a computer to send the vehicle registration number together with information that can identify the cargo handling vehicle 10 to the computer of the original body manufacturer.

[0024] The bodybuilder decides whether or not to provide diagnostic services for the cargo handling vehicle 10 with the notified vehicle registration number (step S8). By accessing the management device 100, the bodybuilder can diagnose the condition of the cargo handling vehicle 10 based on the sensors 40 attached to the cargo handling vehicle 10. The bodybuilder decides whether or not to provide diagnostic services for each of the multiple cargo handling vehicles 10 delivered to the transportation company.

[0025] Hydraulic unit manufacturers provide diagnostic services to bodybuilders for a fee. In order to use the diagnostic service, bodybuilders must pay a service fee to the hydraulic unit manufacturer. The service fee is set, for example, according to the number of cargo handling vehicles 10 for which the diagnostic service is provided. If all cargo handling vehicles 10 delivered to a transportation company were to be subject to the diagnostic service, the service fee would be high. For this reason, bodybuilders select the target cargo handling vehicles 10 so that the diagnostic service can be carried out effectively, taking into consideration the circumstances of the transportation companies with which they do business.

[0026] The criteria for whether or not to provide diagnostic services to a transportation company will differ depending on the vehicle manufacturer A, B, etc. For example, vehicle manufacturer A may set criteria based on the size of the transportation company. Vehicle manufacturer B may set criteria based on the sales amount or number of deliveries of cargo handling vehicles 10 to the transportation company.

[0027] Bodybuilder C may extract, from among multiple transport companies with which it does business, transport companies that it believes tend to use cargo handling vehicles 10 frequently, and may subject the cargo handling vehicles 10 delivered to the extracted transport companies to diagnostic services. In general, it is expected that the more orders a transport company receives for delivery work, the more frequently it will use the cargo handling vehicles 10.

[0028] Bodybuilder D may select, from among multiple transport companies with which it does business, transport companies that it believes tend to frequently use hydraulic units 14, and may designate the cargo handling vehicles 10 delivered to those companies as target vehicles for diagnostic services. Bodybuilder E may inquire about requests for diagnostic services from transport companies, and designate the cargo handling vehicles 10 delivered to transport companies that request diagnostic services as target vehicles for diagnostic services.

[0029] The bodybuilders A, B, etc. decide whether or not to provide diagnostic services to the cargo handling vehicles 10 delivered to the transport company according to their own criteria. Of course, the bodybuilders do not need to make this decision for each transport company. For example, among multiple cargo handling vehicles 10 delivered to the same transport company, one or more specific cargo handling vehicles 10 may be designated as vehicles eligible for diagnostic services.

[0030] The diagnostic service may be, for example, a service to inspect the cargo handling vehicle 10 at regular intervals. The diagnostic service may be a service to replace parts of the cargo handling vehicle 10 at regular intervals. The bodybuilder may add a service to the diagnostic service that provides useful information about delivery operations using the cargo handling vehicle 10.

[0031] After determining whether or not diagnostic services are required for each cargo handling vehicle 10, the bodybuilder notifies the hydraulic unit manufacturer of various information regarding the cargo handling vehicle 10 (step S9). The various information includes the unit ID, bodybuilder ID, vehicle model ID, vehicle registration number, transport company name, and whether or not diagnostic services are required. For example, a person in charge at the bodybuilder may use a computer to send this information to the computer of the hydraulic unit manufacturer.

[0032] The body manufacturer ID included in the various information is identification information for identifying body manufacturers A, B, etc. The hydraulic unit manufacturer can identify the body manufacturer involved in the installation of the hydraulic unit 14 by the body manufacturer ID linked to the cargo handling vehicle 10. The body manufacturer ID is an example of second identification information.

[0033] The vehicle model ID included in the various information is identification information provided by the bodybuilder to identify the vehicle model of the cargo handling vehicle 10. The bodybuilder identifies the vehicle model of the cargo handling vehicle 10 by the vehicle model ID. The vehicle model ID is an example of third identification information.

[0034] The hydraulic unit manufacturer registers the various pieces of information notified by the body manufacturer in the management device 100 (step S10). The management device 100 includes a processor 101 and a memory 102. The management device 100 is an example of a diagnostic device. The management device 100 constitutes a server. For example, the processor 101 registers the various pieces of information in the memory 102 in response to information input by an administrator. The processor 101 is an example of a control device. The processor 101 may receive the various pieces of information from the body manufacturer's computer and register the received various pieces of information in the memory 102.

[0035] A diagnostic platform and a diagnostic result notification system are built in the memory 120. The diagnostic platform provides the bodybuilder with an environment for making various settings used in diagnosing the cargo handling vehicle 10. The diagnostic result notification system notifies the hydraulic unit manufacturer, bodybuilder, or transportation company of various diagnostic results based on the settings of the diagnostic platform.

[0036] The bodybuilder uses the diagnostic platform to set up a diagnosis for each vehicle type of the cargo handling vehicle 10 (step S11). The diagnostic settings include information about the device to be diagnosed, the sensors 40 used for the diagnosis, and threshold values ​​that serve as the criteria for judgment. By using the diagnostic platform, the bodybuilder can set up a diagnosis that makes use of their own know-how without having to develop their own system. By using the diagnostic result notification system, the bodybuilder can obtain information about the diagnostic results according to the settings made on the diagnostic platform. Hereinafter, the information about the diagnostic results will be referred to as diagnostic information.

[0037] The transportation company operates a transportation business using the delivered cargo handling vehicle 10. The operating rate of the cargo handling vehicle 10, the mileage, and the operating rate of the hydraulic unit 14 mounted on the cargo handling vehicle 10 vary depending on the size, type, and business situation of the transportation company. The sensor 40 attached to the cargo handling vehicle 10 detects various information according to the location where the sensor 40 is attached.

[0038] The communication device 80 mounted on the hydraulic unit 14 has the function of communicating with the management device 100 via a network 50 such as the Internet. The sensor 40 attached to the cargo handling vehicle 10 transmits detected values ​​to the communication device 80. The communication device 80 transmits the detection information of the sensor 40 to the management device 100 (step S12). The management device 100 collects the detection information of the sensor 40 for each hydraulic unit ID of the cargo handling vehicle 10 to which the sensor 40 is attached. Hereinafter, the detection information of the sensor 40 will also be referred to as sensor detection information.

[0039] The management device 100 collects sensor detection information sent from cargo handling vehicles 10 for which the diagnostic service setting is set to service required. The management device 100 does not collect sensor detection information sent from cargo handling vehicles 10 for which the diagnostic service setting is set to service disabled. This is because the sensor detection information is used for the diagnostic service for each cargo handling vehicle 10.

[0040] The management device 100 provides the diagnostic information of the cargo handling vehicle 10 to the bodybuilder (step S13). The diagnostic information of the cargo handling vehicle 10 is provided to the bodybuilder by a diagnostic result notification system. The diagnostic information of the cargo handling vehicle 10 includes, for example, failure information of the hydraulic unit 14 mounted on the cargo handling vehicle 10, information notifying of a drop in battery voltage of the cargo handling vehicle 10, etc. The type of diagnostic information varies depending on the diagnostic settings of the bodybuilder.

[0041] The diagnostic information provided by the management device 100 is information generated for each cargo handling vehicle 10. The management device 100 provides bodybuilding manufacturer A with diagnostic information for the cargo handling vehicle 10 corresponding to the hydraulic unit 14 delivered to bodybuilding manufacturer A. The management device 100 provides bodybuilding manufacturer B with diagnostic information for the cargo handling vehicle 10 corresponding to the hydraulic unit 14 delivered to bodybuilding manufacturer B.

[0042] The management device 100 provides the bodybuilder with diagnostic information on the cargo handling vehicle 10 for which the diagnostic service setting is set to require service. The management device 100 does not provide the bodybuilder with diagnostic information on the cargo handling vehicle 10 for which the diagnostic service setting is set to not require service. In other words, the management device 100 provides diagnostic information only for the cargo handling vehicle 10 that the bodybuilder has designated as the target for the diagnostic service.

[0043] The management device 100 transmits the diagnostic information to a terminal device of the body manufacturer. The management device 100 may also transmit the diagnostic information to a mobile terminal of a person in charge at the body manufacturer. The management device 100 may also transmit the diagnostic information to a terminal device located at the transportation company of the cargo handling vehicle 10. The management device 100 may also transmit the diagnostic information to the cargo handling vehicle 10. A communication terminal that receives the diagnostic information may be installed in the cargo handling vehicle 10. The management device 100 may also transmit the diagnostic information to a mobile terminal carried by the driver of the corresponding cargo handling vehicle 10.

[0044] The bodybuilder grasps the condition of the cargo handling vehicle 10 delivered to the transport company based on the diagnostic information. The bodybuilder takes action according to the diagnostic information of the cargo handling vehicle 10 (step S14).

[0045] For example, based on the diagnostic information of the cargo handling vehicle 10 delivered to transportation company X, bodybuilder A learns that the number of times the hydraulic unit 14 mounted on the cargo handling vehicle 10 has been driven exceeds a reference value. In this case, a worker from bodybuilder A may visit transportation company X to inspect the hydraulic unit 14. For example, based on the diagnostic information of the cargo handling vehicle 10 delivered to transportation company Y, bodybuilder B learns that the battery voltage of the cargo handling vehicle 10 has dropped abnormally. In this case, a worker from bodybuilder B may visit transportation company Y to inspect the battery.

[0046] By using the diagnostic platform and the diagnostic result notification system, the bodybuilder can provide value-added services to the transportation company, which has the advantage of increasing sales of the cargo handling vehicle 10.

[0047] In return for providing the diagnostic platform and the diagnostic result notification system to the bodybuilder, the hydraulic unit manufacturer charges the bodybuilder a service fee (step S15). The service fee varies depending on, for example, the number of cargo handling vehicles 10 that are set to require diagnostic service.

[0048] For example, let's say that out of 50 cargo handling vehicles delivered by bodybuilder A to transport company X, 40 are set to require diagnostic service, and out of 30 cargo handling vehicles delivered by bodybuilder A to transport company Y, 15 are set to require diagnostic service. In this case, the hydraulic unit manufacturer will charge bodybuilder A a service fee equivalent to 55 vehicles. In this way, the hydraulic unit manufacturer charges service fees to bodybuilders A, B, etc.

[0049] In return for providing the diagnostic service, the bodybuilder charges the transportation company a service fee (step S16). The service fee varies depending on, for example, the number of cargo handling vehicles 10 that are set to require diagnostic service. Bodybuilders A, B, etc. may each determine the amount of the service fee to be charged to the transportation company with which they do business.

[0050] <Hardware Structure of Management Device 100> The hardware structure of the management device 100 will be described. The management device 100 includes a processor 101 and a memory 102. The processor 101 is typically an arithmetic processing unit such as a CPU (Central Processing Unit) or an MPU (Multi-Processing Unit). The processor 101 realizes the processing of the management device 100 by reading and executing programs stored in the memory 102. Note that while FIG. 1 illustrates an example of a configuration in which the management device 100 has a single processor 101, the management device 100 may also be configured to have multiple processors 101.

[0051] The memory 102 is realized by a nonvolatile memory such as a RAM (Random Access Memory), a ROM (Read Only Memory), or a flash memory. The memory 102 stores various information notified in step S9, the detection information of the sensor 40 transmitted in step S12, programs executed by the processor 101, and data used by the processor 101. The programs executed by the processor 101 include programs related to the diagnostic platform and the diagnostic result notification system.

[0052] In addition, memory 102 may be a CD-ROM (Compact Disc - Read Only Memory), a DVD-ROM (Digital Versatile Disk - Read Only Memory), a USB (Universal Serial Bus) memory, a memory card, a FD (Flexible Disk), a hard disk, an SSD (Solid State Drive), a magnetic tape, a cassette tape, an MO (Magnetic Optical Disc), an MD (Mini Disc), an IC (Integrated Circuit) card (excluding memory cards), an optical card, a mask ROM, or an EPROM, as long as it can non-temporarily record a program in a format readable by processor 101.

[0053] As explained above, the hydraulic unit manufacturer provides a diagnostic platform and a diagnostic result notification system by using the management device 100. The management device 100 manages various data including diagnostic information for the cargo handling vehicle 10. The management device 100 identifies each cargo handling vehicle 10 by the unit ID of the hydraulic unit 14 mounted on that cargo handling vehicle 10. The management device 100 stores the unit ID in association with the transport company that owns the cargo handling vehicle 10 and the body manufacturer that delivered the cargo handling vehicle 10 to the transport company.

[0054] The management device 100 receives various information according to the type of sensor 40 from the cargo handling vehicles 10 used by the transport company and stores the received information by unit ID. The management device 100 provides the bodybuilding manufacturer with diagnostic information generated based on the sensor detection information in response to the bodybuilding manufacturer's request or periodically. The management device 100 provides the bodybuilding manufacturer with diagnostic information, particularly for cargo handling vehicles 10 that the bodybuilding manufacturer has set in advance as requiring service.

[0055] <Configuration of cargo handling vehicle 10> FIG. 2 is a diagram showing a cargo handling vehicle 10 equipped with a hydraulic unit 14. The cargo handling vehicle 10 includes a loading platform 11 and a cargo handling device 12. The cargo handling device 12 includes a loading platform 13 and a hydraulic unit 14. The hydraulic unit 14 shown in FIG. 2 includes, for example, a pressure reducing device. The hydraulic unit 14 raises and lowers the loading platform 13. Another example of the hydraulic unit 14 is a drive device used to open and close the wings of the cargo handling vehicle 10.

[0056] <Communication between the management device 100 and the sensors of the cargo handling vehicle 10> 3 is a diagram showing communication between the management device 100 and a sensor 40 of a cargo handling vehicle 10 used by a transportation company. The management device 100 is managed, for example, by a hydraulic unit manufacturer. The cargo handling vehicle 10 is used, for example, by a transportation company.

[0057] The cargo handling vehicle 10 is composed of a main body 20 and a body frame 30. Various body units 251, 252, 253, etc. are mounted on the main body 20. The body units 251, 252, 253, etc. include engine-related parts, drivetrain-related parts such as clutches, steering-related parts, suspension-related parts, accelerator and brake-related parts, exterior parts, interior parts, electrical parts, air conditioner-related parts, and driving assistance system-related parts. Sensors 40 are attached to the body units 251, 252, 253, etc. by the body frame manufacturer as needed.

[0058] The body 30 includes a hydraulic unit 14. The hydraulic unit 14 includes components such as a hydraulic cylinder 141, a tank 142, a pump 143, a valve 144, and a motor 145, for example.

[0059] The hydraulic cylinder 141 has the function of moving the loading platform 13 of the cargo handling vehicle 10 in and out below the loading platform 11. A liquid such as mineral oil is stored in the tank 142. The pump 143 discharges the liquid stored in the tank 142 toward the hydraulic cylinder 141. A valve 144 controls the flow of the liquid. A motor 145 drives the pump 143. Sensors 40 are attached to these components by the hydraulic unit manufacturer or the body manufacturer as needed. For example, the sensor 40 may be attached at an appropriate location to detect the pressure of the liquid discharged from the tank 142 toward the hydraulic cylinder 141. The sensor 40 may be attached at an appropriate location to detect that the motor 145 has been driven.

[0060] The hydraulic unit 14 further includes a communication device 80. The communication device 80 stores the unit ID of the hydraulic unit 14. The body manufacturer connects the wiring of the sensors 40 attached to the body units 251, 252, 253, ... of the main body 20 to the communication device 80. The body manufacturer or hydraulic unit manufacturer connects the wiring of the sensors 40 attached to the hydraulic unit 14 to the communication device 80.

[0061] The communication device 80 communicates with the management device 100 via the network 50. The communication device 80 transmits the detection information of the sensor 40 together with the unit ID to the management device 100. A diagnostic platform and a diagnostic result notification system are constructed in the management device 100. The diagnostic platform stores diagnostic setting information and diagnostic information. The diagnostic setting information is information set by the body manufacturer to diagnose the condition of the cargo handling vehicle 10. The diagnostic setting information is stored in the diagnostic platform for each vehicle model ID of the body manufacturer. The diagnostic information is information generated based on the diagnostic setting information and sensor detection information. The diagnostic information is stored in the diagnostic platform for each unit ID. The management device 100 transmits the diagnostic information to the body manufacturer's terminal device, etc. via the diagnostic result notification system.

[0062] <Configuration of communication device 80> 4 is a block diagram showing the configuration of a communication device 80. The communication device 80 includes a first channel group 81, a second channel group 82, a third channel group 83, a microcomputer 84, and a communication module 85. Wiring of the sensor 40 is connected to the first channel group 81, the second channel group 82, and the third channel group 83. The first channel group 81 has 10 channels. The second channel group 82 has 5 channels. The third channel group 83 has 5 channels.

[0063] The microcomputer 84 is connected to the first channel group 81, the second channel group 82, the third channel group 83, and the communication module 85. A unit ID is stored in the microcomputer 84. The communication module 85 has an antenna for wireless communication with a base station and outputs information to the outside via radio waves. An address for communicating with the management device 100 is stored in advance in the microcomputer 84. The microcomputer 84 transmits sensor signals received from the first channel group 81, the second channel group 82, and the third channel group 83 to the management device 100 via the communication module 85, along with the unit ID.

[0064] <Channel Configuration of Communication Device 80> 5 is a diagram for explaining the channel configuration of the communication device 80. The specifications of the first channel group 81, the second channel group 82, and the third channel group 83 are as shown in FIG.

[0065] The first channel group 81 is made up of 10 channels V1 to V10. The voltage range that can be input to the first channel group 81 is 0V (Volt) to 36V. The output resolution of the first channel group 81 is in units of 0.1V. The output timing of the first channel group 81 is every 0.5 seconds.

[0066] The second channel group 82 is made up of five channels V11 to V15. The voltage range that can be input to the second channel group 82 is 0V to 36V. The output resolution of the second channel group 82 is in units of 0.1V. The output timing of the second channel group 82 is every 180 seconds.

[0067] The third channel group 83 is made up of five channels V16 to V20. The voltage range that can be input to the third channel group 83 is 0V to 5V. The output resolution of the third channel group 83 is in units of 0.01V. The output timing of the third channel group 83 is every 180 seconds.

[0068] Therefore, a voltage of up to 36 V can be input to the first channel group 81 and the second channel group 82 as a signal from the sensor 40. A voltage of up to 5 V, which is lower than 36 V, can be input to the third channel group 83 as a signal from the sensor 40.

[0069] The detection information of the sensors 40 connected to the first channel group 81 and the second channel group 82 can be determined with a resolution of 0.1 V. The detection information of the sensors 40 connected to the third channel group 83 can be determined more precisely with a resolution of 0.01 V, which is lower than 0.1 V.

[0070] The detection information of the sensors 40 connected to the first channel group 81 can be identified in monitoring periods as short as 0.5 seconds. The detection information of the sensors 40 connected to the second channel group 82 and the third channel group 83 can be identified in monitoring periods of 180 seconds, which are longer than 0.5 seconds.

[0071] 5 is merely an example, and various modifications are contemplated. The microcomputer 84 of the communication device 80 may have a function that allows it to change at least a portion of the specifications of the first channel group 81, the second channel group 82, and the third channel group 83.

[0072] Fig. 6 is a diagram for explaining examples of diagnostic information that can be set in the diagnostic platform. The bodybuilder can obtain various diagnostic information of the cargo handling vehicle 10 by attaching sensors 40 to various devices that make up the cargo handling vehicle 10 and then setting judgment conditions corresponding to the sensors 40 in the diagnostic platform. Fig. 6 shows several examples of diagnostic information.

[0073] FIG. 6 shows "pressure," "temperature," "voltage," "oil level (height)," "rotations," "time," "number of times," and "GPS (Global Positioning System)" as detection targets. Of these, all except "GPS" can be detected by a sensor 40 attached to the cargo handling vehicle 10. "GPS" shown in FIG. 6 means acquiring location information of the cargo handling vehicle 10. In other words, the location information of the cargo handling vehicle 10 acquired using GPS may be collected by the management device 100 via the communication device 80.

[0074] The bodybuilder can generate various diagnostic information by using the detection information of one sensor 40 or by combining the detection information of two or more sensors 40. The diagnostic information is classified into, for example, fault diagnosis information, abnormality diagnosis information, maintenance diagnosis information, abnormal operation history, and driving and operation history.

[0075] The fault diagnosis information indicates that the target device is not operating. The fault diagnosis information includes motor failure in the electrical system, failure due to motor seizure, magnetic switch failure (malfunction), magnetic switch failure (welding), solenoid valve failure in the electrical system, solenoid valve failure in the hydraulic system, relief valve failure, pump failure, and low battery voltage.

[0076] The abnormality diagnosis information indicates that the target device is operating but an abnormality has occurred in the target device, such as a low oil level in the tank, a set pressure warning for the relief valve, a low battery voltage, and excessive internal leakage in the valve block.

[0077] The maintenance diagnostic information indicates that replacement of the target device is recommended or that maintenance of the target device is recommended, and includes information such as when to replace motor brushes, contactors, hydraulic oil, and filters.

[0078] The abnormal operation history indicates a history of operations that are not recommended, and includes abnormalities in the duration of continuous operation of the target device, motor temperature abnormalities, and abnormalities in the frequency of operation of the target device.

[0079] The operation and operation history indicates the operation history and operation history of the target cargo handling vehicle 10. The operation and operation history includes an operation record of the body 30, a diagnosis history of the target device, a treatment history of the target device, and an in-storage temperature record.

[0080] The types and specific examples of diagnostic information have been explained above using Fig. 6. Bodybuilders who use the diagnostic platform to set up diagnostics can set various types of diagnostic information according to their own standards, without being bound by the types and specific examples of diagnostic information explained above.

[0081] <Communication between the management device 100, the cargo handling vehicle 10, and the terminal device 200> 7 is a diagram showing communication between the management device 100, a cargo handling vehicle 10 used by a transport company, and a terminal device 200 used by a body manufacturer. The management device 100 and a communication device 80 mounted on the cargo handling vehicle 10 communicate via a network 50. The management device 100 and the terminal device 200 of the body manufacturer communicate via the network 50.

[0082] The management device 100 is connected to a display device 150 that displays various information. The management device 100 may be configured to include the display device 150.

[0083] The management device 100 conceptually includes an acquisition unit 111, a calculation unit 112, a transmission unit 113, an output unit 114, and a storage unit 115. The acquisition unit 111, the calculation unit 112, the transmission unit 113, and the storage unit 115 are realized by the processor 101 and the memory 102 shown in FIG. 1. The output unit 114 is configured by, for example, a display interface that outputs display information to the display device 150. The processor 101 outputs various information to the output unit 114.

[0084] Transport companies X, Y, etc. deliver goods using cargo handling vehicles 10 delivered from bodywork manufacturers A, B, etc. A communication device 80 is provided in the hydraulic unit 14 of the cargo handling vehicle 10. The communication device 80 transmits sensor detection information together with a unit ID to the management device 100. The management device 100 receives the unit ID and the sensor detection information.

[0085] The acquisition unit 111 acquires sensor detection information together with the unit ID. The acquisition unit 111 stores the sensor detection information in the storage unit 115 for each unit ID. The storage unit 115 stores diagnostic setting information set by the body manufacturer using the diagnostic platform. The calculation unit 112 calculates diagnostic information for the cargo handling vehicle 10 for each unit ID based on the sensor detection information and the diagnostic setting information. This generates various diagnostic information to be provided to the body manufacturer. The calculated diagnostic information is stored in the storage unit 115 for each unit ID.

[0086] A service charge unit price α for the body manufacturer and a service charge unit price β for the shipping company are stored in the storage unit 115. It is desirable to design the management device 100 so that the administrator of the management device 100 can appropriately set the service charge unit price α and the service charge unit price β.

[0087] The service charge unit price α for vehicle manufacturers may be different for each vehicle manufacturer. Similarly, the service charge unit price β for shipping companies may be different for each shipping company. In this case, it is desirable to design the management device 100 so that the administrator of the management device 100 can set the service charge unit price α for each vehicle manufacturer. Similarly, it is desirable to design the management device 100 so that the administrator of the management device 100 can set the service charge unit price α for each vehicle manufacturer.

[0088] The calculation unit 112 calculates the service fee for the diagnostic service for each of the bodybuilding manufacturers A, B, etc., using the service fee unit price α for the bodybuilding manufacturers. The calculation unit 112 calculates the service fee for the diagnostic service for each of the shipping companies X, Y, etc., using the service fee unit price β for the shipping companies.

[0089] The service fee for the bodybuilder is calculated by multiplying the number of hydraulic units 14 (more specifically, communication devices 80) delivered to the bodybuilder by the unit price α of the service fee for the bodybuilder. However, the hydraulic units 14 that are subject to the calculation of the service fee are limited to those whose unit IDs correspond to the requirement for diagnostic service.

[0090] The service fee for the transportation company is calculated by multiplying the number of cargo handling vehicles 10 delivered to the transportation company by the unit price β of the service fee for the transportation company. However, the cargo handling vehicles 10 that are subject to the calculation of the service fee are limited to those whose unit IDs correspond to the cargo handling vehicles 10 that require diagnostic service.

[0091] The service fee for the bodybuilder and the service fee for the shipping company calculated by the calculation unit 112 are stored in the storage unit 115.

[0092] The transmission unit 113 transmits the diagnostic information and the service fee stored in the storage unit 115 to the bodybuilding manufacturer. At this time, the transmission unit 113 transmits the diagnostic information and the service fee for each bodybuilding manufacturer.

[0093] For example, the transmitting unit 113 transmits to the body manufacturer A diagnostic information corresponding to the unit ID of the hydraulic unit 14 delivered by the hydraulic unit manufacturer to the body manufacturer A. The transmitting unit 113 transmits to the body manufacturer B diagnostic information corresponding to the unit ID of the hydraulic unit 14 delivered by the hydraulic unit manufacturer to the body manufacturer B. However, only the diagnostic information corresponding to the unit ID set to require diagnostic service is transmitted from the transmitting unit 113 to the body manufacturer.

[0094] When bodybuilder A delivers loading / unloading vehicles 10 to shipping company X and shipping company Y, the transmission unit 113 transmits a service fee for bodybuilder A, a service fee for shipping company X, and a service fee for shipping company Y to bodybuilder A. Here, the service fee for shipping company X is a fee that bodybuilder A should charge to shipping company X. Similarly, the service fee for shipping company Y is a fee that bodybuilder A should charge to shipping company Y.

[0095] The terminal device 200 of the body manufacturer receives the information transmitted from the transmission unit 113 and displays the received information. The person in charge at the body manufacturer can understand the condition of the cargo handling vehicle 10 that is the subject of the diagnostic service based on the diagnostic information displayed on the terminal device 200. By looking at the service fee displayed on the terminal device 200, the person in charge at the body manufacturer can understand the service fee to be paid to the hydraulic unit manufacturer and the service fee to be charged to the transport company with which the body manufacturer does business.

[0096] The display device 150 connected to the management device 100 displays various types of information stored in the storage unit 115. For example, the management device 100 displays various types of information corresponding to instructions from the administrator on the display device 150. The various types of information include diagnostic information, service fees for bodybuilders, and service fees for shipping companies.

[0097] <Data Managed by Management Device 100> Fig. 8 is a diagram showing an example of data managed by the management device 100. In particular, Fig. 8 shows data stored in the management device 100 in association with a unit ID.

[0098] The management device 100 stores unit IDs in association with the body manufacturer ID, vehicle model ID, vehicle registration number, and transport company name. The unit ID is a unique number. The management device 100 can identify each hydraulic unit 14 by the unit ID. The hydraulic unit 14 is mounted on the cargo handling vehicle 10. The communication device 80 mounted on the hydraulic unit 14 stores the unit ID. Therefore, the management device 100 can identify each cargo handling vehicle 10 by the unit ID.

[0099] The management device 100 can identify the delivery destination of the hydraulic unit 14 by the body manufacturer ID. The management device 100 can identify the vehicle type of the cargo handling vehicle 10 for each unit ID by the vehicle type ID. The management device 100 can identify the cargo handling vehicle 10 to which the hydraulic unit 14 is attached by the vehicle registration number. The management device 100 can identify the delivery destination of the cargo handling vehicle 10 by the name of the transport company.

[0100] The management device 100 can identify the body manufacturer by the alphabet included in the body manufacturer ID. For example, A corresponds to body manufacturer A, and B corresponds to body manufacturer B. The four digits to the right of the alphabet are numbers used by the body manufacturer to identify each hydraulic unit 14. If the purpose is only to identify the body manufacturer, this number is not necessary. The data shown in Figure 8 includes the body manufacturer name corresponding to the body manufacturer ID. These companies are Company A and Company B.

[0101] The management device 100 can identify the body manufacturer by the alphabet included in the vehicle model ID, and can identify the vehicle model of the body manufacturer by the number included in the vehicle model ID. For example, Ac corresponds to body manufacturer A, and Bc corresponds to body manufacturer B. The four digits to the right of the alphabet correspond to the vehicle model of each body manufacturer.

[0102] The data shown in FIG. 8 includes a service flag associated with a unit ID. The service flag is a flag for identifying whether or not a diagnostic service is available. In the data shown in FIG. 8, the service flags corresponding to unit IDs 0000001 to 0000005, 0000007, and 0000008 are set to ON. This means that the cargo handling vehicle 10 identified by the corresponding unit ID is subject to diagnostic service. In the data shown in FIG. 8, the service flags corresponding to unit IDs 0000006, 0000009, and 00000010 are set to OFF. This means that the cargo handling vehicle 10 identified by the corresponding unit ID is not subject to diagnostic service.

[0103] The management device 100 sets the service flag to ON or OFF according to an instruction input by the administrator.

[0104] The data shown in Fig. 8 includes diagnostic information. The management device 100 generates diagnostic information for unit IDs whose service flags are set to ON. The management device 100 does not generate diagnostic information for unit IDs whose service flags are set to OFF. In Fig. 8, the description "No Service" means that the management device 100 does not generate diagnostic information.

[0105] Note that Fig. 8 shows data in a state before the management device 100 generates the diagnostic information. Therefore, the specific contents of the diagnostic information are not shown in Fig. 8. Specific examples of the diagnostic information have already been mentioned, so the description will not be repeated here.

[0106] <Diagnosis setting information managed by vehicle model ID> FIG. 9 is a diagram showing an example of diagnostic setting information managed by the management device 100 for each vehicle model ID. As shown in FIG. 9, the management device 100 stores diagnostic setting information for each vehicle model ID. For example, the management device 100 stores "Diagnosis Type 1 (Arbitrary Name Setting)" in association with the vehicle model ID "Ac0001." Note that the "Arbitrary Name Setting" field displays characters arbitrarily entered by bodybuilder A during setup. For example, bodybuilder A may enter the name of the vehicle model in the "Arbitrary Name Setting" field. The management device 100 uses "Diagnosis Type 1 (Arbitrary Name Setting)" as a label and stores detailed setting data corresponding to that label in memory 102.

[0107] <Diagnosis setting screen> FIG. 10 is a diagram showing a diagnostic setting screen 210 provided by the diagnostic platform. FIG. 11 is a diagram for explaining diagnostic categories selectable on the diagnostic setting screen 210. The diagnostic platform provides each bodybuilder with an environment for making diagnostic settings. For example, FIG. 10 shows the diagnostic setting screen 210 displayed on the terminal device 200 of bodybuilder A. The diagnostic setting screen 210 displays a plurality of setting sheets 211 that allow diagnostic settings to be made for each vehicle model ID. In the setting sheets 211, judgment conditions for diagnosing the condition of the cargo handling vehicle 10 are registered in accordance with operations by the bodybuilder's staff.

[0108] At the top of the setting sheet 211, there is a field for inputting the name of the diagnosis type. The body builder can input any name in this field. This name is reflected in "Diagnosis type 1 (name can be arbitrarily set)" shown in FIG. 9. As already explained, for example, the body builder can input the name of the vehicle model in this field.

[0109] A field for inputting a vehicle model ID is provided at the beginning of the setting sheet 211. The person in charge at the body manufacturer inputs the vehicle model ID to be the target of the setting on the setting sheet 211 in this field. The diagnostic platform identifies the cargo handling vehicle 10 to which the setting is to be applied based on the vehicle model ID input in this field.

[0110] Specifically, when the management device 100 receives the sensor detection information and the unit ID from the cargo handling vehicle 10, it identifies the vehicle model ID stored in association with the unit ID. The management device 100 reads out the diagnostic settings corresponding to the vehicle model ID. The management device 100 processes the received sensor detection information based on the read out diagnostic settings. As a result, the settings set in the setting sheet 211 are applied to the diagnosis of the corresponding vehicle model of the cargo handling vehicle 10.

[0111] The setting sheet 211 includes a field for selecting a diagnostic category (diagnosis category), a field for inputting a diagnosis name (diagnosis name), a field for specifying a channel of the sensor 40 to be used for the diagnosis (first sensor, second sensor, etc.), a field for specifying a threshold value corresponding to the channel (first sensor threshold, second sensor threshold, etc.), a field for specifying a time (time), a field for inputting a diagnostic target (diagnosis), and a field for inputting the number of diagnoses (number of diagnoses). In the setting sheet 211, a judgment condition to be used for the diagnosis can be input for each row.

[0112] In the field for selecting a diagnostic category, options such as operating diagnosis, monitoring diagnosis, and count diagnosis are available. The diagnostic categories will now be described with reference to FIG. 11. In operating diagnosis, the diagnostic object is diagnosed by sensing at a relatively short period (e.g., 0.5 seconds). For operating diagnosis, the channels of the first channel group 81 shown in FIG. 5 are used. For monitoring diagnosis, the diagnostic object is diagnosed by sensing at a relatively long period (e.g., 180 seconds). For monitoring diagnosis, the channels of the second channel group 82 or the third channel group 83 shown in FIG. 5 are used.

[0113] The operation diagnosis is likely to be selected when an event corresponding to a diagnosis name has occurred when the detection value of the sensor 40 exceeds the threshold value for a relatively short period of time. The monitoring diagnosis is likely to be selected when an event corresponding to a diagnosis name has occurred when the detection value of the sensor 40 exceeds the threshold value for a relatively long period of time. The length of each time period is entered in the time column shown in FIG.

[0114] As shown in FIG. 11, the frequency diagnosis targets the number of times an event is detected by sensing. For example, in FIG. 10, the row with the diagnosis name "Time to replace CCC" is classified into the frequency diagnosis category. "DD activated" is entered in the diagnosis target column. "100 times" is entered in the diagnosis count column. Therefore, the diagnosis name "Time to replace CCC" corresponds to diagnosing that it is time to replace device "CCC," based on the determination condition that the number of times the event "device DD activated" has been detected has reached 100 times. There is no need to enter the channel, threshold, and time of sensor 40 in the frequency diagnosis row.

[0115] Any diagnosis name can be entered in the diagnosis name field. For example, if the name of one device constituting the cargo handling vehicle 10 to be diagnosed is "AAA," the person in charge at the body manufacturer can enter any diagnosis name such as "AAA failure," "AAA abnormality," or "AAA replacement time" in the diagnosis name field.

[0116] Each row has multiple columns for specifying the channel and threshold of the sensor 40 used for diagnosis. FIG. 10 shows some of the columns for specifying the channel and threshold. For example, the column for the first sensor corresponds to the column for the first sensor threshold. The column for the second sensor corresponds to the column for the second sensor threshold. The column for the third sensor corresponds to the column for the third sensor threshold. The channel of the communication device 80 is input into each sensor column. The threshold for judging the detection value of the corresponding sensor 40 is input into each sensor threshold column.

[0117] The person in charge at the bodybuilder may input only one channel or multiple channels as the channel of the sensor 40 to be used for diagnosis. For example, only the V1 channel is input in the row of "AAA failure" in FIG. 10. The V2 and V3 channels are input in the row of "BBB abnormality" in FIG. 10. For example, when the V2 and V3 channels are input, if the detection value of the sensor 40 corresponding to V2 exceeds the threshold value 10 (Volt) and the detection value of the sensor 40 corresponding to V3 exceeds the threshold value 20 (Volt), the judgment condition for determining that an event to be diagnosed has occurred is met.

[0118] In the setting sheet 211, the person in charge at the bodybuilder can set the first sensor, the second sensor, ... in that order from among the multiple sensors. The diagnostic platform accepts an operation to input the first sensor threshold, the second sensor threshold, ... in the setting sheet 211. For example, the first sensor threshold is a value for determining whether the detection value of the first sensor satisfies the first condition. For example, the second sensor threshold is a value for determining whether the detection value of the second sensor satisfies the second condition. In the setting sheet 211, "time" is a value for determining whether the duration of the first condition or the second condition satisfies the third condition that establishes a predetermined judgment condition. Also, in the setting sheet 211, "number of diagnoses" is a value for determining whether the number of times the first condition or the second condition is established satisfies the third condition that establishes a predetermined judgment condition.

[0119] The person in charge at the body manufacturer performs diagnostic settings for each vehicle type using the setting sheets 211 in the number corresponding to the number of vehicle types required. In this way, diagnostic setting information for each vehicle type is registered in the diagnostic platform.

[0120] <Diagnosis information screen> Fig. 12 is a diagram showing the diagnostic information screen 220. The person in charge at the body manufacturer accesses the management device 100 using the terminal device 200. Thereafter, the person in charge at the body manufacturer specifies the cargo handling vehicle 10 for which diagnostic information is to be obtained. As a result, the terminal device 200 displays the diagnostic information screen 220 as shown in Fig. 12.

[0121] Basic information and detailed diagnosis information are displayed on the diagnostic information screen 220. Furthermore, one or more pieces of additional information are displayed on the diagnostic information screen 220. In Fig. 12, the battery voltage and the number of times the hydraulic unit has operated are displayed as examples of the additional information.

[0122] The basic information field displays the name of the transport company that owns the cargo handling vehicle 10, the vehicle registration number, the unit ID, the body manufacturer ID, and the vehicle location. The vehicle location is determined using GPS.

[0123] The diagnostic detail information field displays the type of diagnosis, diagnostic content (diagnosis name), diagnosis date and time, response status, and response date and time. By looking at the diagnostic information screen 220, the person in charge at the body manufacturer can understand the past diagnostic content and current diagnostic content of the target cargo handling vehicle 10.

[0124] <Example of Data List Display (Management Device 100)> In response to an instruction input by the administrator, the management device 100 displays the data shown in Fig. 8 on the display device 150. An example of this will be described with reference to Fig. 13.

[0125] Fig. 13 is a diagram showing an example of a data list displayed on the display device 150 of a hydraulic unit manufacturer. When an administrator inputs a predetermined instruction into the management device 100, a data list 151 is displayed on the screen of the display device 150, as shown in Fig. 13. The data list 151 includes the various data described using Fig. 8. The screen of the display device 150 further includes a details button 153 and a service fee button 154.

[0126] When the details button 153 is clicked with a mouse or the like, diagnostic information for the cargo handling vehicle 10 identified by the corresponding unit ID is displayed on the screen. When the click operation of the details button 153 is accepted, a screen similar to the diagnostic information screen 220 described using Figure 12 is displayed on the display device 150. Here, a more detailed description of the screen displayed when the click operation of the details button 153 is accepted will be omitted. Note that "No Service" indicates that the corresponding unit ID is not subject to diagnostic service. When the service fee button 154 is clicked with a mouse or the like, the service fee for the corresponding unit ID is displayed on the screen. This screen will be described in detail later.

[0127] <Example of data list display (requires diagnostic service)> Fig. 14 is a diagram showing an example in which a data list 152 of unit IDs that are set to require diagnostic service is displayed on a display device 150 of a hydraulic unit manufacturer. When an administrator inputs a predetermined instruction into the management device 100, the data list 152 of unit IDs that are set to require diagnostic service is displayed on the screen of the display device 150, as shown in Fig. 14. The screen shown in Fig. 14 includes a details button 153 and a service fee button 154, similar to the screen shown in Fig. 13.

[0128] <Display of service fees for bodybuilders> Fig. 15 is a diagram showing an example in which the service fee for the bodybuilder is displayed on the hydraulic unit manufacturer's display device 150. For example, the administrator clicks on the service fee button 154 on the screen shown in Fig. 13. Then, as shown in Fig. 15, the service fee for the bodybuilder 155 is displayed at the bottom of the screen.

[0129] Service fee 155 displays the fee for each bodybuilder with which the hydraulic unit manufacturer does business. The screen shown in Figure 15 displays the service fees for Company A and Company B. According to data list 151, the hydraulic unit manufacturer has delivered seven hydraulic units 14 to Company A. Of these, the number of hydraulic units 14 for which the service flag is set to ON is six. Also, according to data list 151, the hydraulic unit manufacturer has delivered three hydraulic units 14 to Company B. Of these, the number of hydraulic units 14 for which the service flag is set to ON is one.

[0130] Therefore, service fee 155 indicates that the number of unit IDs providing services to company A is 6, and the number of unit IDs providing services to company B is 1. Furthermore, service fee 155 indicates the service fee calculated by multiplying the number of IDs by the service fee unit price α for company A and company B.

[0131] By looking at the display of service fee 155, the manager of the hydraulic unit manufacturer can identify the amount of service fee to be charged to Company A and the amount of service fee to be charged to Company B.

[0132] <Example of Data List Display (Terminal Device 200)> Fig. 16 is a diagram showing an example in which a data list 201 is displayed on the terminal device 200 of a body manufacturer. In particular, Fig. 16 shows an example in which the data list 201 is displayed on the terminal device 200 of body manufacturer A. The terminal device 200 of body manufacturer A is connected to the management device 100 via a network 50. The terminal device 200 of body manufacturer A receives various information related to the hydraulic unit 14 delivered from the hydraulic unit manufacturer from the management device 100. The terminal device 200 displays the information received from the management device 100 as shown in Fig. 16.

[0133] The data list 201 includes the unit ID of the hydraulic unit 14 that bodybuilder A purchased from the hydraulic unit manufacturer, and various information associated with the unit ID. The various information associated with the unit ID includes the bodybuilder ID, vehicle model ID, transport company name, vehicle registration number of the cargo handling vehicle 10, service flag setting, and diagnostic information corresponding to the unit ID.

[0134] 16, the names of transport companies are listed in the leftmost column. However, the terminal device 200 may change the position of the data to be arranged in each column in response to an operation by a person in charge at the bodybuilding manufacturer.

[0135] By checking the screen shown in FIG. 16, the person in charge at the bodybuilder can identify the cargo handling vehicles 10 for which diagnostic services are being provided, by transport company.

[0136] The screen of the display device 150 further includes a details button 203 and a service fee button 204 .

[0137] When the details button 203 is clicked with a mouse or the like, diagnostic information for the corresponding unit ID is displayed on the screen. Details of this screen have already been explained using FIG. 12. Note that "No Service" indicates that the corresponding unit ID is not covered by the diagnostic service. When the service fee button 204 is clicked with a mouse or the like, the service fee for the corresponding unit ID is displayed on the screen.

[0138] <Display of Service Charge (Terminal Device 200)> Fig. 17 is a diagram showing an example of service charges being displayed on the terminal device 200 of the bodybuilder. For example, the person in charge at the bodybuilder clicks on the service charge button 204 on the screen shown in Fig. 16. Then, as shown in Fig. 17, service charges 205 and 206 are displayed at the bottom of the screen.

[0139] The service fee 205 is a service fee charged to the bodybuilder by the hydraulic unit manufacturer. According to the data list 201, Company A has purchased seven hydraulic units 14 from the hydraulic unit manufacturer. Of these, the number of hydraulic units 14 whose service flags are set to ON is six.

[0140] Therefore, the service fee 205 indicates that the number of unit IDs for which Company A is receiving service from the hydraulic unit manufacturer is 6. Furthermore, the service fee 205 indicates the service fee calculated by multiplying the number of IDs by the service fee unit price α.

[0141] The service fee 206 is a service fee that the body manufacturer can charge to the transport company. According to the data list 201, body manufacturer A has delivered five cargo handling vehicles 10 to transport company X. According to the data list 201, it can be seen that all of the cargo handling vehicles 10 delivered by body manufacturer A to transport company X are subject to the diagnostic service.

[0142] According to the data list 201, body manufacturer A has delivered two cargo handling vehicles 10 to transportation company Y. According to the data list 201, it can be seen that one of the two cargo handling vehicles 10 delivered by body manufacturer A to transportation company Y is the subject of the diagnostic service.

[0143] Therefore, the service fee 206 indicates that the number of unit IDs providing services to company X is 5, and the number of unit IDs providing services to company Y is 1. Furthermore, the service fee 206 indicates the service fee calculated by multiplying the number of IDs by the service fee unit price β for company X and company Y.

[0144] By looking at the display of the service fee 206, the person in charge at the bodybuilder can identify the service fee that can be charged to Company X and the service fee that can be charged to Company Y.

[0145] 18 is a flowchart showing the flow of processing related to the registration of the unit ID, body manufacturer ID, and vehicle registration number, and the setting of the service flag. The processing based on this flowchart is executed by the management device 100.

[0146] First, the management device 100 determines whether a unit ID has been input (step S101). If a unit ID has not been input, the management device 100 proceeds to step S103. If a unit ID has been input, the management device 100 registers the input new unit ID (step S102). For example, the management device 100 registers the unit ID in the memory 102 by storing the input unit ID in the memory 102.

[0147] The management device 100 may accept input of a unit ID from a keyboard. The management device 100 may collectively register multiple IDs recorded on a recording medium or multiple IDs received via a network.

[0148] Next, the management device 100 determines whether or not a body manufacturer ID to be linked to the unit ID has been input (step S103). If a body manufacturer ID has not been input, the management device 100 proceeds to step S105. If a body manufacturer ID to be linked to the unit ID has been input, the management device 100 links the input body manufacturer ID to the corresponding unit ID and registers it in the memory 102 (step S104).

[0149] Next, the management device 100 determines whether a vehicle model ID to be linked to the unit ID has been input (step S105). If a vehicle model ID has not been input, the management device 100 proceeds to step S107. If a vehicle model ID to be linked to the unit ID has been input, the management device 100 links the input vehicle model ID to the corresponding unit ID and registers it in the memory 102 (step S106).

[0150] Next, the management device 100 determines whether a vehicle registration number to be linked to the unit ID has been input (step S107). If a vehicle registration number has not been input, the management device 100 proceeds to step S109. If a vehicle registration number to be linked to the unit ID has been input, the management device 100 links the input vehicle registration number to the corresponding unit ID and registers it in the memory 102 (step S108).

[0151] Next, the management device 100 determines whether or not an input indicating that service is required has been received for the unit ID (step S109). More specifically, the management device 100 determines whether or not an input specifying a unit ID and an input instructing that the service flag for that unit ID be changed from OFF to ON have been received. For example, the initial setting of the service flag is OFF. In step S109, it is determined whether or not an input to change the initial setting to ON has been received.

[0152] If there is no such input, the management device 100 proceeds to step S111. If there is such input, the management device 100 changes the service flag of the corresponding unit ID from OFF to ON (step S110).

[0153] Next, the management device 100 determines whether or not an input to change whether or not a service is required has been received (step S111). More specifically, the management device 100 determines whether or not an input to change the setting of a service flag has been received. This input includes the unit ID of the unit whose setting is to be changed.

[0154] If there is no such input, the management device 100 ends the processing based on this flowchart. If there is such input, the management device 100 changes the service flag of the corresponding unit ID according to the input specification (step S112), and ends the processing.

[0155] As a result of the management device 100 executing the processes based on the flowchart described above, the various pieces of information shown in FIG. 8 are stored in the memory 102 of the management device 100 for each unit ID.

[0156] 19 is a flowchart showing the flow of the diagnostic setting process. The process based on this flowchart is executed by the management device 100 and the terminal device 200.

[0157] First, the terminal device 200 generates a request for diagnostic settings and transmits the generated request for diagnostic settings to the management device 100 (step S251). The request for diagnostic settings is generated by a person in charge of the bodybuilding manufacturer operating the terminal device 200. The request for diagnostic settings includes a bodybuilding manufacturer ID and a password. The person in charge of the bodybuilding manufacturer may create new diagnostic settings using the setting sheet 211 shown in FIG. 10 or may modify diagnostic settings that have already been created. When modifying diagnostic settings that have already been created, the person in charge of the bodybuilding manufacturer includes the vehicle model ID in addition to the bodybuilding manufacturer ID and password in the request for diagnostic settings.

[0158] The management device 100 determines whether or not a request for diagnostic settings has been received (step S201). If a request for diagnostic settings has not been received, the management device 100 terminates the processing based on this flowchart. If a request for diagnostic settings has been received, the management device 100 determines whether or not the password included in the request for diagnostic settings is correct (step S202). The management device 100 manages passwords for each bodywork manufacturer ID. If the password is incorrect, the management device 100 terminates the processing based on this flowchart.

[0159] If the password is correct, the management device 100 determines whether or not a new diagnostic setting is requested (step S203). If a new diagnostic setting is requested, the management device 100 generates new diagnostic setting data (step S204). Next, the management device 100 transmits the generated diagnostic setting data to the terminal device 200 (step S205). As a result, the diagnostic setting screen 210 shown in FIG. 10 is displayed on the terminal device 200.

[0160] Next, the terminal device 200 accepts an operation by the person in charge to input a diagnostic setting (step S252). The management device 100 determines whether or not setting completion information has been received from the terminal device 200 (step S206). The management device 100 continues the processing of step S206 until the setting completion information is received. Eventually, the operation of inputting the diagnostic setting on the terminal device 200 is completed. Then, the person in charge performs a setting completion operation on the terminal device 200. Upon accepting the setting completion operation, the terminal device 200 transmits the setting completion information to the management device 100 (step S253). Upon receiving the setting completion information, the management device 100 registers the input diagnostic setting in the memory 102 and ends the processing (step S207). As a result, a new diagnostic setting is created.

[0161] If a request is made to modify an already created diagnostic setting, the management device 100 determines NO in step S203. In this case, the management device 100 reads the diagnostic setting data to be modified from the memory 102 using the vehicle model ID included in the diagnostic setting request (step S208). Next, the management device 100 transmits the read diagnostic setting data to the terminal device 200 (step S205).

[0162] The terminal device 200 accepts an operation for inputting a diagnostic setting by the person in charge, as in the case of creating a new diagnostic setting (step S252). The management device 100 determines whether or not setting completion information has been received from the terminal device 200 (step S206). The management device 100 continues the processing of step S206 until the setting completion information is received. Eventually, the operation of inputting the diagnostic setting (the operation of updating the setting) on ​​the terminal device 200 is completed. Then, the person in charge performs a setting completion operation on the terminal device 200. Upon accepting the setting completion operation, the terminal device 200 transmits setting completion information to the management device 100 (step S253). Upon receiving the setting completion information, the management device 100 registers the input diagnostic setting in the memory 102 and ends the processing (step S207). This updates the diagnostic setting.

[0163] The above-described flowchart configures a registration unit that registers judgment conditions in the platform. The registration unit functions to allow a person in charge of the vehicle manufacturer to determine judgment conditions for diagnosing the condition of a moving object (such as a component mounted on the moving object) and set the judgment conditions by operating the terminal device 200. Alternatively, the person in charge of the vehicle manufacturer may determine judgment conditions for diagnosing the condition of the moving object and notify the hydraulic unit manufacturer, who is the platform administrator, by email or other means, and the hydraulic unit manufacturer may then operate the terminal device to set the judgment conditions. Here, for the sensor 40 arranged on the hydraulic unit 14 side shown in FIG. 3 among the multiple sensors 40, the person in charge of the hydraulic unit manufacturer may be configured to determine the judgment conditions and set the diagnostic settings. This is because the hydraulic unit manufacturer has more know-how about the judgment conditions for the hydraulic unit than the vehicle manufacturer. In this case, for example, a terminal device operable by the person in charge of the hydraulic unit manufacturer may be connected to the management device 100. The person in charge of the hydraulic unit manufacturer operates the terminal device to set the diagnostic settings for the sensor 40 arranged on the hydraulic unit 14 side. With this configuration, a registration unit is configured that registers judgment conditions determined by the platform administrator (a person in charge at the hydraulic unit manufacturer) as judgment conditions for sensors attached to hydraulic equipment, and registers judgment conditions determined by a user (a person in charge at a body manufacturer or a component manufacturer, etc.) as judgment conditions for sensors attached to the main body or components other than hydraulic equipment. Note that the person in charge at the hydraulic unit manufacturer may directly operate the management device 100 to set the diagnosis of the sensor 40 arranged on the hydraulic unit 14 side.

[0164] 20 is a flowchart showing the flow of processing related to the collection of sensor detection information and the output of diagnostic information. The processing based on this flowchart is executed by the management device 100.

[0165] First, the management device 100 receives the sensor detection information and the unit ID from the communication device 80 of the cargo handling vehicle 10 (step S301).

[0166] Next, the management device 100 checks the service flag corresponding to the unit ID (step S302). Next, based on the check in step S302, the management device 100 determines whether the cargo handling vehicle 10 corresponding to the unit ID is a target for which a diagnostic service is provided (step S303).

[0167] If the cargo handling vehicle 10 corresponding to the unit ID is not a target for which diagnostic services are provided, the management device 100 ends the process. As a result, the management device 100 does not collect the sensor detection information corresponding to that unit ID.

[0168] The management device 100 may collect sensor detection information for each unit ID, regardless of whether the cargo handling vehicle 10 corresponding to the unit ID is a target for which the diagnostic service is provided. In this case, it is desirable for the management device 100 to restrict the provision of diagnostic information of cargo handling vehicles 10 that are not a target for which the diagnostic service is provided to the terminal device 200 of the bodybuilder.

[0169] If the cargo handling vehicle 10 corresponding to the unit ID is a target for which diagnostic services are to be provided, the management device 100 collects the acquired sensor detection information by unit ID (step S304). Next, the management device 100 reads the vehicle model ID corresponding to the unit ID from the memory 102 (step S305). Next, the management device 100 reads the diagnostic setting corresponding to the vehicle model ID from the memory 102 (step S306). Next, the management device 100 generates diagnostic information based on the read diagnostic setting and sensor detection information (step S307). In other words, the management device 100 judges the acquired sensor detection information based on the diagnostic setting and generates diagnostic information according to the diagnostic setting. Next, the management device 100 stores the generated diagnostic information by unit ID in the memory 102 (step S308).

[0170] Next, the management device 100 outputs the generated diagnostic information (step S309). For example, the management device 100 outputs the diagnostic information to the display device 150. The management device 100 may output the diagnostic information to the terminal device 200 of the body manufacturer via the network 50. The management device 100 may output the diagnostic information to a mobile terminal of a person in charge at the body manufacturer via the network 50.

[0171] Next, the management device 100 determines whether there has been an input instructing to output a list of data (step S310). The administrator of the management device 100 inputs a command instructing to output a list of data from a keyboard or the like. In this case, the management device 100 determines YES in step S310.

[0172] When an input instructing to output a data list is received, the management device 100 outputs a data list of unit IDs (step S311). The output data list is displayed on the display device 150, for example, in the format shown in Fig. 14. The management device 100 may output the data list to a printer.

[0173] Next, the management device 100 determines whether there has been an input instructing output of data with the service flag set to ON (step S312). The administrator of the management device 100 inputs a command instructing output of data with the service flag set to ON from a keyboard or the like. In this case, the management device 100 determines YES in step S312.

[0174] When there is an input instructing to output data with a service flag ON, the management device 100 selects the data of the unit ID with the service flag ON and outputs the selected data (step S313). The output data is displayed on the display device 150, for example, in the format shown in Fig. 15. The management device 100 may output such data to a printer.

[0175] After outputting the data in step S313, or after making a NO determination in either step S310 or step S312, the management device 100 ends the processing based on this flowchart.

[0176] 21 is a flowchart showing the flow of processing related to the transmission of diagnostic information and service fees. The processing based on this flowchart is executed by the management device 100.

[0177] First, the management device 100 determines whether or not a request for list information has been received from the terminal device 200 of the bodybuilding manufacturer (step S401). The request for list information includes the bodybuilding manufacturer ID and password.

[0178] If a request for list information has not been received, the management device 100 ends the processing based on this flowchart. If a request for list information has been received, the management device 100 determines whether the password included in the request for list information is correct (step S402). If the password is incorrect, the management device 100 ends the processing based on this flowchart.

[0179] If the password is correct, the management device 100 transmits the list information stored in the memory 102 corresponding to the requested body manufacturer to the terminal device 200 (step S403). As a result, the terminal device 200 displays, for example, a data list 201 shown in Fig. 16. The data list includes a details button 203 and a service fee button 204.

[0180] Next, the management device 100 determines whether operation information of the details button 203 has been received (step S404). When the details button 203 displayed on the terminal device 200 is clicked, operation information of the details button 203 is transmitted from the terminal device 200 to the management device 100.

[0181] If the management device 100 has not received operation information of the details button 203, the processing proceeds to step S406. If the management device 100 has received operation information of the details button 203, the management device 100 transmits diagnostic information of the unit ID corresponding to the operated details button 203 to the terminal device 200 (step S405). As a result, the terminal device 200 displays, for example, a diagnostic information screen 220 shown in FIG. 12.

[0182] The person in charge at the bodybuilding manufacturer can check the diagnostic information of the selected cargo handling vehicle 10 by looking at the screen of the terminal device 200. The person in charge at the bodybuilding manufacturer can refer to the diagnostic information and consider whether or not to go for maintenance on the cargo handling vehicle 10 in question.

[0183] Next, the management device 100 determines whether or not operation information of the service fee button 204 has been received (step S406). When the service fee button 204 displayed on the terminal device 200 is clicked, operation information of the service fee button 204 is transmitted from the terminal device 200 to the management device 100.

[0184] If the management device 100 has not received operation information of the service fee button 204, it ends the processing based on this flowchart. If the management device 100 has received operation information of the service fee button 204, it calculates a service fee for each shipping company with which the bodybuilding manufacturer does business (step S407). The service fee calculated here is a service fee that the bodybuilding manufacturer can charge to the shipping company. Furthermore, the management device 100 calculates a service fee for the bodybuilding manufacturer (step S408). The service fee calculated here is a service fee that the bodybuilding manufacturer will be charged by the hydraulic unit manufacturer.

[0185] Next, the management device 100 transmits the service charges calculated in steps S407 and S408 to the terminal device 200 (step S409), and ends the processing based on this flowchart. As a result, the terminal device 200 displays the service charges 205 and 206 shown in FIG. 17.

[0186] By looking at the screen of the terminal device 200, the person in charge at the body manufacturer can identify the service fee that the body manufacturer will be charged by the hydraulic unit manufacturer and the service fee that the body manufacturer can charge to the shipping company.

[0187] As described above, according to this embodiment, hydraulic unit manufacturers can provide high-value-added diagnostic services to body manufacturers and transportation companies. Here, the benefits of hydraulic unit manufacturers providing the comprehensive diagnostic service according to this embodiment will be described in more detail.

[0188] Hydraulic unit manufacturers have a great deal of technical know-how regarding the hydraulic unit 14. Therefore, it is conceivable that hydraulic unit manufacturers would provide a service of diagnosing the condition of the hydraulic unit 14 to bodybuilders or transportation companies for a fee. However, the hydraulic unit 14 is only one of many devices that make up the cargo handling vehicle 10. By expanding the scope of the diagnostic service to include the many devices that make up the cargo handling vehicle 10, hydraulic unit manufacturers can provide bodybuilders and the like with diagnostic services that offer higher added value.

[0189] However, hydraulic unit manufacturers do not necessarily have the technical know-how to diagnose the condition of all of the devices that make up the cargo handling vehicle 10. Much of the technical know-how regarding the main body of the cargo handling vehicle 10 is often held by body manufacturers or component manufacturers other than hydraulic unit manufacturers, rather than by hydraulic unit manufacturers. Therefore, if body manufacturers or component manufacturers can independently develop systems for diagnosing the condition of their own cargo handling vehicles 10, they may be able to provide transportation companies with diagnostic services with high added value. By attaching sensors 40 to appropriate locations on the various devices of the cargo handling vehicle 10 and utilizing their own know-how to devise conditions for judging the information detected by the sensors 40, the body manufacturers or component manufacturers will be able to appropriately diagnose the condition of the various devices that make up the cargo handling vehicle 10.

[0190] However, the scale of vehicle body manufacturers or component manufacturers varies. Not all vehicle body manufacturers or component manufacturers have the technical capabilities and development funds necessary to develop a diagnostic service. In fact, many medium-sized or small vehicle body manufacturers or component manufacturers may lack such technical capabilities and development funds. Therefore, even if a vehicle body manufacturer or component manufacturer has know-how regarding the installation position of the sensor 40 and the judgment conditions, it is difficult for the vehicle body manufacturer to independently develop a diagnostic system that utilizes such know-how.

[0191] Therefore, in this embodiment, a hydraulic unit manufacturer provides a diagnostic platform that enables a body manufacturer or component manufacturer to utilize its own know-how to diagnose the cargo handling vehicle 10. This embodiment is characterized in that the unit ID of the hydraulic unit 14 is managed in association with the body manufacturer or component manufacturer, transport manufacturer, cargo handling vehicle 10, and the model of the cargo handling vehicle 10, thereby making it possible to identify information necessary for providing a diagnostic service.

[0192] In this embodiment, the hydraulic unit manufacturer provides the body manufacturer or component manufacturer with a communication device 80 that acquires the detection information of the sensor 40 and a diagnostic platform that allows diagnostic settings to be made without employing a system engineer.

[0193] According to this embodiment, the bodybuilder can be provided with the setting environment necessary to automatically diagnose the state of the cargo handling vehicle 10 without the bodybuilder having to develop a system. Therefore, the bodybuilder can set up the diagnosis based on their own know-how even if they do not have system design know-how.

[0194] In this embodiment, the hydraulic unit manufacturer can charge the body manufacturer the fee for the hydraulic unit 14, to which the fee for the communication device 80 is added, and the service fee for the diagnostic service. As a result, the hydraulic unit manufacturer can improve its profits compared to when delivering a hydraulic unit not equipped with the communication device 80 to the body manufacturer. Note that the communication fee between the communication device 80 and the management device 100 may be included in the fee for the diagnostic service, or the hydraulic unit manufacturer may charge the body manufacturer separately from the fee for the diagnostic service.

[0195] In this embodiment, the cargo handling vehicle 10 is given as an example of a moving body. However, the moving body is not limited to the cargo handling vehicle 10. A general vehicle other than the cargo handling vehicle 10 may also be the subject of diagnosis. In this case, a communication device 80 storing a unit ID may be installed in any unit mounted on the general vehicle. Alternatively, only the communication device 80 storing the unit ID may be provided.

[0196] According to this embodiment, information that can identify whether or not the cargo handling vehicle 10 delivered to the transportation company is eligible for the diagnostic service is provided to the bodybuilder, which reduces the burden on the bodybuilder of determining whether or not the cargo handling vehicle 10 delivered to the transportation company is eligible for the diagnostic service.

[0197] Furthermore, according to this embodiment, the service flag can be set arbitrarily for each cargo handling vehicle 10. Therefore, the body manufacturer does not need to subject all cargo handling vehicles 10 delivered to the transportation company to the diagnostic service. Therefore, the body manufacturer can limit the number of cargo handling vehicles 10 that are subject to the diagnostic service, taking into consideration various circumstances. Therefore, the body manufacturer can keep the service fee paid to the hydraulic unit manufacturer to an appropriate amount.

[0198] Furthermore, according to this embodiment, the bodybuilder is provided with a service fee for each shipping company, which reduces the burden on the bodybuilder of managing the service fee for each shipping company.

[0199] Thus, according to this embodiment, it is possible to provide high quality services to the delivery destination of the cargo handling vehicle 10, while reducing the burden of managing information relating to the provision of the services.

[0200] Embodiment 2 Next, a second embodiment will be described. Fig. 22 is a diagram showing the configuration of a diagnostic system 2 according to the second embodiment. Fig. 23 is a diagram showing communication between a management device 300 and a remote device 500 according to the second embodiment. In the second embodiment, a management device 300 is provided instead of the management device 100 of the first embodiment. The management device 300 communicates with the remote device 500 via the Internet or the like.

[0201] In the first embodiment, the unit ID and various information associated with the unit ID are stored in memory 102 of management device 100. On the other hand, in the second embodiment, the unit ID and various information associated with the unit ID are stored in remote device 500.

[0202] 23, the management device 300 includes a processor 301, a memory 302, a communication interface 303, and a display interface 304. The management device 300 communicates with a remote device 500 via the communication interface 303. The management device 300 and the remote device 500 may communicate via the network 50 shown in FIG. 22, or may communicate via another network. The management device 300 is connected to the display device 150 via the display interface 304. The management device 300 may be configured to include the display device 150.

[0203] The remote device 500 comprises a memory 502 for storing data.

[0204] 23, the management device 300 instructs the remote device 500 to store various information in the memory 502. The various information includes the unit ID, the body manufacturer ID, the vehicle model ID, the vehicle registration number, the name of the shipping company, and information indicating whether or not service is required. The information indicating whether or not service is required is a service flag.

[0205] More specifically, the management device 300 instructs the remote device 500 to store information corresponding to the registration processes of steps S102, S104, S106, and S108 in Fig. 18. Furthermore, the management device 300 instructs the remote device 500 to perform the processes of steps S110 and S112, which are related to setting a service flag. These instructions are transmitted from the communication interface 303 of the management device 300 to the remote device 500.

[0206] As shown in FIG. 22, the detection information of the sensor 40 of the cargo handling vehicle 10 is transmitted to a remote device 500 via a network 50.

[0207] The remote device 500 stores various information by unit ID in the memory 502 based on commands from the management device 300. The remote device 500 collects detection information from the sensors 40 of the cargo handling vehicle 10 by unit ID. The remote device 500 generates diagnostic information based on commands from the management device 300.

[0208] The management device 300 is connected to the display device 150 in the same manner as in the first embodiment. In response to an instruction input by the administrator, the management device 300 requests the remote device 500 to transmit various pieces of information stored for each unit ID. The management device 300 displays the various pieces of information received from the remote device 500 on the display device 150. As a result, the display device 150 connected to the management device 300 displays the information as shown in FIGS. 13 to 15. The management device 300 transmits the various pieces of information received from the remote device 500 to the terminal device 200 of the bodybuilder. As a result, the terminal device 200 displays the information as shown in FIGS. 10, 12, 16, and 17.

[0209] Thus, the second embodiment differs from the first embodiment in that information related to the unit ID is stored in the remote device 500. In other respects, the second embodiment is similar to the first embodiment.

[0210] According to the second embodiment, there is no need to provide the management device 300 with a large capacity memory required to store information related to unit IDs. This reduces the cost of the management device 300. Note that a plurality of remote devices 500 may be provided. The management device 300 may store information in a distributed manner across a plurality of remote devices 500.

[0211] Embodiment 3 The third embodiment will be described with reference to Figure 24. Figure 24 is a diagram showing an example in which the state of the cargo handling vehicle 10 is diagnosed by a communication board 400 provided in the hydraulic unit 14. As shown in Figure 24, the hydraulic unit 14 is provided with the communication board 400. The communication board 400 is equipped with a communication device 80 and a microcomputer 104, which is an example of a control device. The microcomputer 104 diagnoses the state of the cargo handling vehicle 10 based on a diagnostic program received from the management device 100.

[0212] The microcomputer 104 includes a diagnostic unit 97 and a memory 96 that stores a diagnostic program. The communication device 90 has the same configuration as that of the first embodiment.

[0213] The management device 100 stores diagnostic setting information corresponding to the vehicle model ID of the cargo handling vehicle 10. The communication device 80 transmits a program request including a unit ID to the management device 100. The management device 100 identifies the vehicle model ID of the cargo handling vehicle 10 on which the communication device 80 is mounted based on the unit ID. The management device 100 transmits a diagnostic program including diagnostic setting information corresponding to the vehicle model ID to the communication device 80.

[0214] The communication device 80 transmits the received diagnostic program to the microcomputer 104. The microcomputer 104 stores the received diagnostic program in the memory 96. The sensor 40 is connected to the communication device 80. The sensor 40 is attached to the main body 20 and the body 30 of the cargo handling vehicle 10 in the same manner as the configuration shown in FIG. 3. The main body 20 and the body 30 are not shown in FIG. 24.

[0215] The communication device 80 receives detection information from the sensors 40 from the first channel group 81, the second channel group 82, and the third channel group 83. The communication device 80 transmits the received detection information from the sensors 40 to the microcomputer 104. A diagnostic unit 97 included in the microcomputer 104 diagnoses the condition of the cargo handling vehicle 10 based on the received detection information from the sensors 40 and a diagnostic program stored in the memory 96. The diagnostic unit 97 generates diagnostic information indicating the results of the diagnosis. The diagnostic unit 97 transmits the generated diagnostic information to the communication device 80. The communication device 80 transmits the diagnostic information and the unit ID to the management device 100. The management device 100 stores the received diagnostic information in an area corresponding to the unit ID. The management device 100 uses a diagnostic result notification system to transmit the diagnostic information to the terminal device 200 of the corresponding body manufacturer.

[0216] As shown in Fig. 24, the cargo handling vehicle 10 may be equipped with a display device 15 for displaying diagnostic information. In this case, the microcomputer 104 transmits the diagnostic information to the display device 15. For example, by looking at the display device 15, the driver of the cargo handling vehicle 10 can quickly grasp the condition of the cargo handling vehicle 10.

[0217] Embodiment 4 A fourth embodiment will be described with reference to Fig. 25. Fig. 25 is a diagram showing an example in which the state of a cargo handling vehicle 10 is diagnosed in a communication device 90. In the fourth embodiment, the memory 96 and the diagnosing unit 97 described in the third embodiment are provided in the communication device 90. That is, the microcomputer 94 of the communication device 90 has the function of the diagnosing unit 97 described in the third embodiment.

[0218] The communication device 90 transmits a program request including the unit ID to the management device 100. The management device 100 identifies the vehicle model ID of the cargo handling vehicle 10 on which the communication device 90 is mounted based on the unit ID. The management device 100 transmits to the communication device 90 a diagnostic program including diagnostic setting information corresponding to the vehicle model ID.

[0219] The microcomputer 94 of the communication device 90 stores the received diagnostic program in the memory 96. The sensors 40 are connected to the first channel group 81, the second channel group 82, and the third channel group 83. The sensors 40 are attached to the main body 20 and the body 30 of the cargo handling vehicle 10 in the same manner as in the configuration shown in Fig. 3. The main body 20 and the body 30 are not shown in Fig. 25.

[0220] The microcomputer 94 receives detection information from the sensors 40 from the first channel group 81, the second channel group 82, and the third channel group 83. A diagnostic unit 97 included in the microcomputer 94 diagnoses the condition of the cargo handling vehicle 10 based on the received detection information from the sensors 40 and the diagnostic program stored in the memory 96. The diagnostic unit 97 generates diagnostic information indicating the results of the diagnosis. The diagnostic unit 97 transmits the diagnostic information and the unit ID to the management device 100. The management device 100 stores the received diagnostic information in an area corresponding to the unit ID. The management device 100 uses a diagnostic result notification system to transmit the diagnostic information to the terminal device 200 of the corresponding body manufacturer.

[0221] In the fourth embodiment, similarly to the third embodiment, the display device 15 for displaying the diagnostic information may be mounted on the cargo handling vehicle 10. In this case, the diagnosing unit 97 transmits the diagnostic information to the display device 15.

[0222] Embodiment 5. The fifth embodiment will be described with reference to Figures 26 and 27. Figure 26 is a diagram showing the configuration of a diagnostic system 3 according to the fifth embodiment. Figure 27 is a block diagram showing the configuration of a communication device 95 used in the fifth embodiment.

[0223] The communication device 95 used in the fifth embodiment stores a communication device ID instead of a unit ID. As shown in Fig. 27, the communication device ID is stored in the microcomputer 84 of the communication device 95. The communication module 85 transmits a sensor signal from the sensor 40 together with the communication device ID to the management device 100 via the communication module 85. Note that the unit ID may be stored in the microcomputer 84 in addition to the communication device ID.

[0224] The diagnostic system 3 according to the fifth embodiment uses a communication device ID instead of a unit ID to realize the various functions described in the first to fourth embodiments. For example, Fig. 26 shows that the communication device ID is included in the various information notified to the hydraulic unit manufacturer by the body manufacturer instead of the unit ID (step S9).

[0225] In the fifth embodiment, the management device 100 stores the communication device ID in association with the body manufacturer ID, vehicle model ID, vehicle registration number, and transport company name. The management device 100 collects sensor detection information for each communication device ID of the cargo handling vehicle 10 to which the sensor 40 is attached. The management device 100 calculates diagnostic information of the cargo handling vehicle 10 for each communication device ID based on the sensor detection information and diagnostic setting information. In the fifth embodiment, the function of the unit ID used in the first to fourth embodiments is replaced by the communication device ID. For example, in the flowchart shown in FIG. 18, various pieces of information are registered in association with the unit ID, but in the fifth embodiment, various pieces of information are registered in association with the communication device ID. In the fifth embodiment, the communication device ID corresponds to an example of first identification information.

[0226] [Aspect] It will be understood by those skilled in the art that the above-described embodiment and its modifications are specific examples of the following aspects.

[0227] The processor 101 of the management device 100 is an example of a diagnosing unit that diagnoses the state of a moving body based on detection information from multiple sensors input to the communication device. The hydraulic unit manufacturer is an example of a platform manager. A component manufacturer other than a body manufacturer or hydraulic unit manufacturer is an example of a user who is a manufacturer of the vehicle 10 or a component of the vehicle 10, and is different from the platform manager. S407 to S408 show an example of a fee calculation unit. The flowchart shown in FIG. 19 is an example of a registration unit that registers judgment conditions in the platform.

[0228] (Article 1) A diagnostic system according to one embodiment is a diagnostic system for diagnosing the condition of a moving body, and includes: a communication device mounted on the moving body and communicating with a plurality of sensors provided on the moving body; a diagnostic unit for diagnosing the condition of the moving body based on detection information from the plurality of sensors input to the communication device; a memory managed by a platform administrator and having a platform built therein that accepts settings for diagnosing the condition of the moving body; and a registration unit for registering in the platform judgment conditions for diagnosing the condition of the moving body based on the detection information from the plurality of sensors, the judgment conditions being determined by a user who is different from the platform administrator and is the manufacturer of the moving body or components of the moving body; and the diagnostic unit outputs diagnostic information based on the judgment conditions registered in the platform.

[0229] According to the management device described in paragraph 1, it is possible to provide an environment in which a person who provides a moving object such as a cargo handling vehicle to a user can diagnose the state of the moving object without the need for system development.

[0230] (2) The diagnostic system described in paragraph 1 further includes a terminal device managed by a user, and when the terminal device accesses the platform, the registration unit registers the judgment conditions in the platform in accordance with the operation of the user of the terminal device.

[0231] According to the diagnostic system described in paragraph 2, it is possible to register judgment conditions according to the desires of the user of the terminal device.

[0232] (Item 3) The diagnostic system according to item 1 or 2 further comprises a management device including a diagnostic unit, a registration unit, and a memory, and the communication device communicates with the management device via a network.

[0233] According to the diagnostic system described in paragraph 3, a setting environment necessary for automatically diagnosing the condition of a mobile object such as a cargo handling vehicle can be provided to a person who provides the mobile object to a user, without the need for system development.

[0234] (Clause 4) The diagnostic system described in clause 1 further comprises a communication board mounted on the mobile body and a management device including a memory, the communication board being equipped with a communication device and a diagnostic unit, the diagnostic unit communicating with the management device via a network, the management device transmitting judgment conditions registered in the platform to the diagnostic unit, and the diagnostic unit outputting diagnostic information based on the judgment conditions received from the management device.

[0235] According to the diagnostic system described in paragraph 4, the state of the moving body can be diagnosed by the moving body itself.

[0236] (Clause 5) In the diagnostic system described in any one of clauses 1 to 3, the communication device stores first identification information for identifying the communication device, and the communication device outputs detection information from the multiple sensors and the first identification information to the diagnostic unit.

[0237] According to the diagnostic system described in paragraph 5, the diagnostic unit can identify the vehicle from which the detection information of the plurality of sensors is output, using the first identification information.

[0238] (Clause 6) In the diagnostic system described in any one of clauses 1 to 5, the mobile body is composed of a vehicle including a vehicle body, hydraulic equipment, and components other than the hydraulic equipment, the multiple sensors include sensors attached to the hydraulic equipment and sensors attached to the body or components other than the hydraulic equipment, the platform administrator is the manufacturer of the hydraulic equipment, and the registration unit registers judgment conditions determined by the platform administrator as judgment conditions for the sensors attached to the hydraulic equipment, and registers judgment conditions determined by the user as judgment conditions for the sensors attached to the vehicle body or components other than the hydraulic equipment.

[0239] According to the diagnostic system described in Section 6, the judgment conditions determined by the platform administrator and the judgment conditions determined by the user can be reflected in the registered contents.

[0240] (Clause 7) In the diagnostic system described in any one of clauses 1 to 6, the platform is configured to allow input of judgment conditions and a diagnosis name for each diagnostic object, and the diagnostic unit outputs the diagnosis name set for the diagnostic object when the judgment conditions set for the diagnostic object are satisfied.

[0241] According to the diagnostic system described in Section 7, the diagnostic content can be identified.

[0242] (Item 8) In the diagnostic system described in Item 7, the platform is configured to be able to select one of a plurality of categories for each diagnostic object, the plurality of categories including a first category and a second category, the first category being a category selected when detection information from a sensor among the plurality of sensors used to set the judgment conditions is acquired at a first period, and the second category being a category selected when detection information from a sensor among the plurality of sensors used to set the judgment conditions is acquired at a second period longer than the first period.

[0243] According to the diagnostic system described in paragraph 8, it is possible to select an appropriate period for the sensor information depending on the diagnostic target.

[0244] (Clause 9) In the diagnostic system described in clause 7 or clause 8, the communication device has a plurality of channels that respectively input electrical signals from a plurality of sensors, the plurality of channels including a first channel and a second channel, the first channel and the second channel differing in at least one of the input voltage range and the output resolution, and the platform is configured to accept an operation to specify whether the sensor related to the judgment condition among the plurality of sensors corresponds to the first channel or the second channel when inputting the judgment condition for each diagnostic object.

[0245] According to the diagnostic system described in paragraph 9, it is possible to select an appropriate channel depending on the diagnostic target.

[0246] (Clause 10) In the diagnostic system described in any one of clauses 1 to 9, the multiple sensors include a first sensor and a second sensor, and the platform is configured to accept an operation to input a first threshold, a second threshold, and a third threshold, wherein the first threshold is a value for determining that the detection value of the first sensor satisfies a first condition, the second threshold is a value for determining that the detection value of the second sensor satisfies a second condition, and the third threshold is a value for determining that the duration of the first condition or the number of times the first condition is met satisfies a third condition that makes the judgment condition met.

[0247] According to the diagnostic system described in paragraph 10, appropriate judgment conditions can be set depending on the diagnostic target.

[0248] (Item 11) The diagnostic system according to item 5 further comprises a fee calculation unit that calculates fees for platform services provided to users.

[0249] The diagnostic system described in Section 11 makes it possible to identify fees for platform services provided to users.

[0250] (Clause 12) In the diagnostic system described in Clause 11, the platform is configured to accept input of second identification information for identifying a user, and when the second identification information is input, the registration unit registers the second identification information on the platform for each first identification information corresponding to the communication device delivered to the user, and the fee calculation unit calculates a fee for the platform's services to be provided to the user based on the second identification information and the service unit price.

[0251] According to the diagnostic system described in Section 12, payment of fees for platform services can be charged to each user.

[0252] (Clause 13) A diagnostic method according to another aspect is a diagnostic method for diagnosing the condition of a moving body, the moving body being equipped with a communication device that communicates with a plurality of sensors provided on the moving body, and including the steps of acquiring detection information from the plurality of sensors from the communication device, accessing a platform managed by a platform administrator that accepts settings for diagnosing the condition of the moving body, registering judgment conditions for diagnosing the condition of the moving body based on the detection information from the plurality of sensors in the platform, the judgment conditions being determined by a user who is different from the platform administrator and is the manufacturer of the moving body or a component of the moving body, and outputting diagnostic information based on the judgment conditions registered in the platform.

[0253] According to the diagnostic method described in paragraph 13, a setting environment necessary for automatically diagnosing the condition of a moving object such as a cargo handling vehicle can be provided to a person who provides the moving object to a user, without the need for system development.

[0254] The embodiments disclosed herein should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the description of the above embodiments, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0255] 1,2 Diagnostic system, 10 Loading vehicle, 11 Loading platform, 12 Loading device, 13 Loading platform, 14 Hydraulic unit, 15,150 Display device, 20 Main body, 30 Body, 40 Sensor, 50 Communication network, 80,90,95 Communication device, 81 First channel group, 82 Second channel group, 83 Third channel group, 84,94,104 Microcomputer, 85 Communication module, 96 Memory, 97 Diagnostic unit, 100,300 Management device, 101,301 Processor, 102,148,302,502 Memory, 111 Acquisition unit, 112 Calculation unit, 113 Transmission unit, 114 Output unit, 115 Storage unit, 141 Hydraulic cylinder, 142 Tank, 143 Pump, 144 Valve, 145 Motor, 146 Pressure sensor, 147 Motor sensor, 151, 152, 201 Data list, 153, 203 Details button, 154, 204 Service fee button, 155, 205, 206 Service fee, 200 Terminal, 210 Diagnostic setting screen, 220 Diagnostic information screen, 251-253 Body unit, 303 Communication interface, 304 Display interface, 400 Communication board, 500 Remote device.

Claims

1. A diagnostic system for diagnosing a state of a moving body, comprising: a communication device mounted on the moving body and configured to communicate with a plurality of sensors provided on the moving body; a diagnosis unit that diagnoses a state of the moving object based on detection information of the plurality of sensors input to the communication device; a memory in which a platform is configured, the platform being managed by a platform administrator and accepting settings for diagnosing the state of the mobile object; a registration unit that registers, in the platform, judgment conditions for diagnosing the state of the moving object based on the detection information of the plurality of sensors, the judgment conditions being determined by a user who is a manufacturer of the moving object or a component of the moving object and who is different from the platform administrator; the diagnostic unit outputs diagnostic information based on the judgment conditions registered in the platform; the moving body includes a first moving body and a second moving body; The determination condition is: a first determination condition for diagnosing a state of the first moving object based on detection information of the plurality of sensors; a second determination condition for diagnosing the state of the second moving body based on the detection information of the plurality of sensors; The registration unit registering the first determination condition determined by a first user who is a manufacturer of the first mobile object or a component of the first mobile object in the platform; A diagnostic system that registers the second judgment condition determined by a second user who is a manufacturer of the second mobile object or a component of the second mobile object in the platform.

2. The registration unit accepts access from a terminal device managed by the user, The terminal device a first terminal device managed by the first user; a second terminal device managed by the second user; The registration unit When the first terminal device accesses the platform, the first determination condition according to an operation of the first user of the first terminal device is registered in the platform; The diagnostic system according to claim 1 , wherein when the second terminal device accesses the platform, the second judgment condition corresponding to an operation of the second user of the second terminal device is registered in the platform.

3. Each of the first moving body and the second moving body includes a plurality of moving bodies classified by vehicle type, The registration unit accepting an operation for registering the first determination condition in the platform for each vehicle type in response to an operation by the first user; The diagnostic system according to claim 1 or 2, further comprising: a step of receiving an operation for registering the second determination condition for each vehicle type in the platform in response to an operation by the second user.

4. a management device including the diagnosis unit, the registration unit, and the memory; 4. The diagnostic system according to claim 1, wherein the communication device communicates with the management device via a network.

5. a communication board mounted on the moving body; a management device including the memory; the communication board is equipped with the communication device and the diagnostic unit, the diagnostic unit communicates with the management device via a network; the management device transmits the judgment conditions registered in the platform to the diagnosis unit; 4. The diagnostic system according to claim 1, wherein the diagnostic unit outputs diagnostic information based on the determination condition received from the management device.

6. First identification information for identifying the communication device is stored in the communication device; 6. The diagnostic system according to claim 1, wherein the communication device outputs the detection information of the plurality of sensors and the first identification information to the diagnostic unit.

7. the moving body is configured by a vehicle including a vehicle body, a hydraulic device, and a component other than the hydraulic device, the plurality of sensors include a sensor attached to the hydraulic equipment and a sensor attached to the vehicle body or a component other than the hydraulic equipment, the platform operator is a manufacturer of the hydraulic equipment; The diagnostic system according to any one of claims 1 to 6, wherein the registration unit registers judgment conditions determined by the platform administrator as judgment conditions for sensors attached to the hydraulic equipment, and registers judgment conditions determined by the user as judgment conditions for sensors attached to the vehicle body or components other than the hydraulic equipment.

8. the platform is configured to allow input of the judgment conditions and diagnosis names for each diagnostic subject; The diagnostic system according to any one of claims 1 to 7, wherein the diagnostic unit outputs the diagnosis name set for the diagnostic object when the judgment condition set for the diagnostic object is satisfied.

9. the platform is configured to allow selection of one of a plurality of categories for each of the diagnostic subjects; the plurality of categories includes a first category and a second category; the first category is a category selected when detection information of a sensor used to set the determination condition is acquired in a first period from among the plurality of sensors, The diagnostic system according to claim 8 , wherein the second category is a category selected when detection information from a sensor among the plurality of sensors used to set the judgment conditions is obtained at a second period longer than the first period.

10. the communication device includes a plurality of channels for receiving electrical signals from the plurality of sensors, respectively; the plurality of channels includes a first channel and a second channel; At least one of an input voltage range and an output resolution is different between the first channel and the second channel; The diagnostic system of claim 8 or claim 9, wherein the platform is configured to accept an operation to specify whether a sensor among the plurality of sensors related to the judgment condition corresponds to the first channel or the second channel when the judgment condition is input for each diagnostic object.

11. the plurality of sensors includes a first sensor and a second sensor; the platform is configured to receive an input operation of a first threshold, a second threshold, and a third threshold; the first threshold value is a value for determining whether the detection value of the first sensor satisfies a first condition, the second threshold value is a value for determining whether the detection value of the second sensor satisfies a second condition, A diagnostic system described in any one of claims 1 to 10, wherein the third threshold is a value for determining whether the duration of the first condition or the number of times the first condition is met satisfies a third condition that makes the judgment condition met.

12. The diagnostic system according to claim 6 , further comprising a fee calculation unit that calculates a fee for the platform service provided to the user.

13. the platform is configured to accept input of second identification information for identifying the user; the registration unit, when the second identification information is input, registers the second identification information for each of the first identification information corresponding to the communication device delivered to the user in the platform; The diagnostic system according to claim 12 , wherein the fee calculation unit calculates a fee for the platform service to be provided to the user based on the second identification information and a service unit price.

14. A diagnostic method for diagnosing a state of a moving body, comprising: the mobile body is equipped with a communication device that communicates with a plurality of sensors provided in the mobile body; acquiring detection information of the plurality of sensors from the communication device; accessing a platform managed by a platform administrator and accepting settings for diagnosing the state of the mobile unit; a step of registering, in the platform, judgment conditions for diagnosing the state of the moving object based on the detection information of the plurality of sensors, the judgment conditions being determined by a user who is a manufacturer of the moving object or a component of the moving object and who is different from the platform administrator; outputting diagnostic information based on the judgment conditions registered in the platform; the moving body includes a first moving body and a second moving body; The determination condition is: a first determination condition for diagnosing a state of the first moving object based on detection information of the plurality of sensors; a second determination condition for diagnosing the state of the second moving body based on the detection information of the plurality of sensors; The registering step includes: registering the first judgment condition determined by a first user who is a manufacturer of the first mobile object or a component of the first mobile object in the platform; and registering the second judgment condition determined by a second user who is a manufacturer of the second mobile object or a component of the second mobile object in the platform.

Citation Information

Patent Citations

  • Plant diagnosing system

    JP1999344589A

  • Method and device for gathering vehicle information

    JP2001076012A

  • Dynamic management system, dynamic management information center device and dynamic management method

    JP2002117476A

  • Thermosensitive automatic switch with absence mode function

    JP2007200046A

  • Systems and methods for providing content to vehicles in exchange for vehicle information

    JP2009521019A