Software update support device, inspection system management device and inspection system

Abstract

To efficiently update the version of software by reducing the resting time of an inspection device as much as possible.SOLUTION: A software update support device is for supporting update of software executed by a device configuring an inspection system, and includes: a management information acquisition unit for acquiring management information for managing software; a management information storage unit for storing the management information; a device information acquisition unit for acquiring device information; a device information storage unit for storing the device information; an update software storage unit for storing software for update; an update condition reception unit for receiving the setting of an update condition; an update plan generation unit for generating an update plan of the software to be updated, on the basis of management information including management information of the software to be updated, the device information, and the update condition; an update plan storage unit for storing the update plan; and an update information provision unit for providing the software for update and the update plan of the software to be updated, using the software for update.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a software update support device that supports updating of software executed in devices that constitute an inspection system, an inspection system management device, and an inspection system. [Background technology]

[0002] An SMT (Surface Mount Technology) inspection system is configured with a PC on an inspection device connected to a network, a PC for teaching, visual inspection, and analysis, and a server. When upgrading software running on such computers on a network, it is necessary to terminate and replace the currently running application, so the upgrade work is usually performed on each computer (see Patent Documents 1 to 3). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2012-18575 [Patent Document 2] Japanese Patent Application Laid-Open No. 2004-139572 [Patent Document 3] Japanese Patent Application Laid-Open No. 2002-268892 Summary of the Invention [Problem to be solved by the invention]

[0004] In small-scale systems, software upgrades can be performed during breaks, etc., but in medium-scale or larger systems with five or more inspection devices, the time required to stop the line for the upgrade is long, and in such medium-scale or larger systems, the upgrade work requires the involvement of multiple workers.

[0005] The present invention has been made in view of the above-mentioned problems, and has as its object to minimize the downtime of an inspection device and efficiently update the software of the entire inspection system. [Means for solving the problem]

[0006] To solve the above problems, the present invention provides: A software update support device that supports updating of software executed in any device constituting an inspection system including an inspection device that inspects an object to be inspected, a management information acquisition unit that acquires management information for managing the software; a management information storage unit that stores the management information; a device information acquisition unit that acquires device information that is information about the device; a device information storage unit that stores the device information; an update software storage unit that stores update software used to update the software; an update condition receiving unit that receives settings of update conditions that are conditions related to the software update; an update plan generation unit that generates an update plan for the software to be updated based on the management information including the management information of the software to be updated, the device information, and the update conditions; an update plan storage unit that stores the generated update plan; an update information providing unit that provides the update software and the update plan of the software to be updated by the update software; The present invention is characterized by comprising:

[0007] According to this, an update plan for software to be updated is generated based on management information for the software to be updated, information about the devices that constitute the inspection system, and update conditions. That is, the update plan can be generated based on the status of the devices that constitute the inspection system, including the inspection device, which affects the downtime of the inspection device. Therefore, by updating the software of the devices that constitute the inspection system according to the update plan generated in this manner, the downtime of the inspection device due to the software update can be kept short, and software updates for the entire inspection system can be efficiently implemented. Furthermore, when generating the update plan, the user can set how to consider the status of the devices that constitute the inspection system, including the inspection device, which is an update condition. This allows for efficient software updates that are in line with the status of the entire inspection system.

[0008] In addition, in the present invention, The update condition may be set so that the timing for updating the software to be updated is based on the past operating conditions of the device on which the software to be updated is executed.

[0009] This allows an update plan to be generated in which the timing of updating the software to be updated is set based on the past operating status of the device on which the software to be updated is executed.The update plan generated in this manner therefore makes it possible to keep inspection device downtime to a short period of time and efficiently upgrade the software of the entire inspection system.

[0010] In addition, in the present invention, The update condition may be such that the timing for updating the software to be updated is set to when the software to be updated becomes available in the device on which the software to be updated is executed.

[0011] This allows an update plan to be generated that sets the timing for updating the software to be updated when it becomes possible to update the device on which the software to be updated is executed.This update plan generated in this manner allows the inspection device to be kept down for a short period of time, and software upgrades can be efficiently carried out for the entire inspection system.

[0012] In addition, in the present invention, The update condition may be such that the timing for updating the software to be updated is set based on the state of another device related to the device on which the software to be updated is executed.

[0013] This allows an update plan to be generated in which the timing of updating the software to be updated is set based on the status of other devices related to the device on which the software to be updated is executed.The update plan generated in this manner therefore makes it possible to keep inspection device downtime to a short period of time and efficiently upgrade the software of the entire inspection system.

[0014] In addition, in the present invention, The update condition may be set so that a user specifies a date and time for updating the software to be updated.

[0015] This allows an update plan to be generated that sets the date and time for updating the software to be updated as specified by the user, so that the update plan generated in this manner can minimize the downtime of the inspection equipment and efficiently upgrade the software of the entire inspection system.

[0016] In addition, in the present invention, As the update condition, the timing of updating the software to be updated may be set based on a production plan for the object to be inspected.

[0017] This allows an update plan to be generated in which the timing for updating the software to be updated is set based on the production plan for the item being inspected.The update plan generated in this manner can therefore limit the downtime of the inspection equipment to a short period of time and efficiently upgrade the software of the entire inspection system.

[0018] The present invention also provides An inspection system management device that manages the inspection system, a system-side device information storage unit that stores the device information; a system-side management information storage unit that stores the management information; an update software acquisition unit that acquires the update software; an update software storage unit that stores the update software; an update plan acquisition unit that acquires the update plan; an update plan storage unit that stores the update plan; an update software and update plan distribution unit that distributes the update software and the update plan to the device on which the software to be updated is executed; Equipped with The update software acquisition unit and the update plan acquisition unit acquire the update software and the update plan from the update support device according to any one of claims 1 to 7, respectively.

[0019] According to this, an update plan for the software to be updated is generated based on management information for the software to be updated, information about the devices that constitute the inspection system, and update conditions. In other words, the update plan can be generated based on the status of the devices that constitute the inspection system, including the inspection device, which affects the downtime of the inspection device. Therefore, by having the inspection system management device acquire the update plan and update software generated in this manner and distributing them to the devices on which the software to be updated is executed, the downtime of the inspection device due to software updates in the devices that constitute the inspection system can be kept short, and software updates for the entire inspection system can be efficiently implemented. Furthermore, when generating the update plan, the user can set how to consider the status of the devices that constitute the inspection system, including the inspection device, which is the update condition. This allows for efficient software updates that are in line with the status of the entire inspection system.

[0020] The present invention also provides The inspection system including the inspection system management device according to claim 8, The device is characterized by having an update control unit that updates the software to be updated using the update software distributed from the inspection system management device in accordance with the update plan distributed from the inspection system management device.

[0021] According to this, the devices that make up the inspection system update the software to be updated using update software distributed from the inspection system management device in accordance with the update plan distributed from the inspection system management device, thereby minimizing the downtime of the inspection devices and enabling efficient software upgrades of the entire inspection system.

[0022] The present invention also provides The software update support device according to any one of claims 1 to 7; The device constituting the inspection system; An inspection system comprising: The device is characterized by including an update control unit that updates the software to be updated using the update software provided by the software update support device in accordance with the update plan provided by the software update support device.

[0023] According to this, the devices that make up the inspection system update the software to be updated using the update software provided by the software update support device in accordance with the update plan provided by the software update support device, thereby minimizing the downtime of the inspection devices and enabling efficient software upgrades of the entire inspection system. [Effects of the Invention]

[0024] According to the present invention, it is possible to keep the downtime of the inspection device to a short time and efficiently update the software of the entire inspection system. [Brief explanation of the drawings]

[0025] [Figure 1] 1 is a schematic configuration diagram of a production line according to an embodiment of the present invention. [Figure 2] 1 is a diagram illustrating the overall configuration of an inspection system according to an embodiment of the present invention. [Figure 3] FIG. 2 is a functional block diagram of an upgrade support server according to an embodiment of the present invention. [Figure 4] FIG. 3 is a functional block diagram of a management terminal according to an embodiment of the present invention. [Figure 5] FIG. 2 is a functional block diagram of a management server according to an embodiment of the present invention. [Figure 6] FIG. 2 is a functional block diagram of a line server according to an embodiment of the present invention. [Figure 7] FIG. 2 is a functional block diagram of a teaching terminal and an analysis terminal according to an embodiment of the present invention. [Figure 8] 1 is a functional block diagram of an inspection device according to an embodiment of the present invention. [Figure 9] FIG. 2 is a functional block diagram of a viewing terminal according to an embodiment of the present invention. [Figure 10] FIG. 10 is a sequence diagram of an upgrade according to an embodiment of the present invention. [Figure 11] FIG. 10 is another sequence diagram of the upgrade according to the embodiment of the present invention. [Figure 12] FIG. 10 is a diagram showing an example of an upgrade plan and results screen according to an embodiment of the present invention. [Figure 13] FIG. 10 is a diagram showing an example of a version upgrade condition setting screen according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0026] [Application example] Hereinafter, application examples of the present invention will be described with reference to the drawings.

[0027] 1, one production line 100 constituting an inspection system 1, which is an example of an object to which the present invention is applied, includes a solder printing device 100a, a post-solder-printing inspection device 100b, a mounter 100c, a post-mount inspection device 100d, a reflow furnace 100e, and a post-reflow inspection device 100f. Each of the inspection devices 100b, 100d, and 100f inspects the condition of the printed circuit board at the exit of each process and automatically detects defects or suspected defects (hereinafter, these devices will be collectively referred to as inspection devices 40).

[0028] Fig. 2 is a block diagram showing a schematic configuration of the entire inspection system 1 including a plurality of the above-mentioned lines. The inspection system 1 includes a management terminal 20, a management server 30, line servers 40-1, 40-2, teaching terminals 50-1, 50-2, an analysis terminal 60, inspection devices 70-1, 70-2, and a visual inspection terminal 80-1. An upgrade support server 10 is connected to the management terminal 20 via a network NW2 (hereinafter, when multiple devices are collectively described, the subnumbers will be omitted). The devices that make up the inspection system 1 are not limited to the above-mentioned devices. Furthermore, the number of each device described above is merely an example and is not limited to this.

[0029] A software upgrade method in the inspection system 1 will be described with reference to FIG. 10. Using a screen such as that shown in FIG. 13, the upgrade support server 10 proposes upgrade conditions, such as implementing an upgrade at a date and time predicted from past operating conditions when the inspection device 70 or the like will be out of operation (step S101), and a person in charge (e.g., an operator) sets the upgrade conditions (step S102). The upgrade support server 10 generates an upgrade plan based on the set upgrade conditions and transmits it to the management terminal 20 together with the upgrade module (step S103-1). Depending on the upgrade conditions, the operator may set the upgrade date and time using the upgrade plan and results screen 201 (see FIG. 12) displayed on the upgrade plan and results display unit 20h of the management terminal 20 (step S103-2).

[0030] The upgrade module and the upgrade plan are transmitted from the management terminal 20 to the management server 20. The upgrade module and the upgrade plan for upgrading the software executed in the line server 40, the inspection device 70, the teaching terminal 50, etc. are transmitted from the management server 20 (steps S105, S106, S107, S108) or from the line server 40 (steps S109, S110) in response to an acquisition request from each device.

[0031] With reference to FIG. 12, the upgrade module and the upgrade that is performed after the upgrade plan is acquired will be described using the line server 40 and the inspection device 70 connected to the line server 40 as examples. First, in the line server 40, the upgrade control unit 40a checks whether the time for the upgrade defined in the upgrade plan has arrived for the application being executed on the line server 40-1 (step S201). If it is determined that the time for the upgrade has arrived, the upgrade control unit 40a terminates the application to be upgraded (step S202), updates the module of the application to be upgraded to the acquired upgrade module (step S203), and starts the upgraded application (step S204).

[0032] The upgrade control unit 70a of the inspection device 70 checks whether the time for the upgrade defined in the upgrade plan has arrived for the application running on the inspection device 70 based on the upgrade plan stored in the upgrade plan storage unit 70i (step S205). If it determines that the time for the upgrade has arrived, it checks the status of the line server 40 (i.e., checks whether the upgrade of the line server 40 has been completed) (step S206). If the upgrade has been completed, it terminates the application of the inspection device 70 (step S207), updates the application module to the upgraded module (step S208), and starts the upgraded application (step S209). The status check is performed because, when the line server 40 performs a predetermined process based on data acquired from the inspection device 70, the line server 40 running an application that has not yet been upgraded may not be able to properly process data output from the inspection device 70 whose application has already been upgraded, which may result in an error. 11 shows an example of a version upgrade method between the line server 40 and the inspection device 70, but a version upgrade is also performed in a similar procedure between the line server 40 and the visual inspection terminal 80. Furthermore, a version upgrade is also performed in a similar procedure between the management server 30 and the teaching terminal 50 and the analysis terminal 60.

[0033] Thus, according to the present invention, by transmitting the upgrade module and upgrade plan acquired by the management terminal 20 to the management server 30, it is possible to upgrade the software of the entire inspection system 1 while keeping the downtime of the inspection equipment to a short period of time.

[0034] Example 1 Hereinafter, the configuration of an inspection system 1 according to a first embodiment of the present invention will be described with reference to the drawings. However, the configuration of the device described in this embodiment should be modified as appropriate depending on various conditions. In other words, it is not intended that the scope of the present invention be limited to the following embodiment.

[0035] FIG. 1 shows a production line 100 according to this embodiment. As described above, the production line 100 includes, for example, a solder printing device 100a, a post-solder printing inspection device 100b, a mounter 100c, a post-mount inspection device 100d, a reflow oven 100e, and a post-reflow inspection device 100f. The solder printing device 100a prints solder paste onto the electrodes of a printed circuit board. The mounter 100c places multiple electronic components to be mounted on the printed circuit board on the solder paste. The reflow oven 100e is a heating device that solders the electronic components placed on the printed circuit board to the printed wiring on the board. The inspection devices 100b, 100d, and 100f inspect the condition of the printed circuit board at the exit of each process and automatically detect any defects or potential defects.

[0036] As shown in FIG. 2, the inspection system 1 includes multiple production lines 100. Here, an example including two production lines is described, but the number of production lines 100 included in the inspection system 1 is not limited to this. The inspection system 1 includes a management terminal 20, a management server 30, line servers 40-1 and 40-2, teaching terminals 50-1 and 50-2, an analysis terminal 60, inspection devices 70-1 and 70-2, and a visual inspection terminal 80-1. In the inspection system 1, the management server 30, line servers 40-1 and 40-2, teaching terminals 50-1 and 50-2, and analysis terminal 60 are connected to a network NW1. The inspection devices 70-1 and 70-2 and the visual inspection terminal 80-1 are connected via the line server 40-1, and the inspection devices 70-3 and 70-4 and the visual inspection terminal 80-2 are connected via the line server 40-1. The management terminal 20 is also connected to the management server 30. Furthermore, the management terminal 20 is connected to an upgrade support server 10 via a network NW2.

[0037] The upgrade support server 10, management terminal 20, management server 30, line servers 40-1 and 40-2, teaching terminals 50-1 and 50-2, analysis terminal 60, and visual inspection terminals 80-1 to 80-2 may be configured as general-purpose computer systems including a CPU (processor), a main storage device (memory), an auxiliary storage device (hard disk, etc.), an input device (keyboard, mouse, controller, touch panel, etc.), an output device (display, printer, speaker, etc.), and a communication device. Alternatively, they may be configured as portable computer systems such as tablet terminals. Furthermore, the inspection devices 70-1 to 70-4 may be configured as general-purpose computer systems including a CPU (processor), a main storage device (memory), an auxiliary storage device (hard disk, etc.), and a communication device, and may also include an input device (keyboard, mouse, controller, touch panel, etc.) and an output device (display, printer, speaker, etc.).

[0038] (Configuration of the version upgrade support server) 3 shows a functional block diagram of the upgrade support server 10. This is a device that uses an upgrade module to generate a plan for upgrading application software (hereinafter also simply referred to as an app) executed in each device of the inspection system 1, and transmits the plan together with the upgrade module to the management terminal 20.

[0039] Upgrade support server 10 includes upgrade plan generation unit 10a, upgrade condition acquisition unit 10b, upgrade plan storage unit 10c, upgrade module storage unit 10d, upgrade information transmission unit 10e, SM information acquisition unit 10f, SM information storage unit 10g, inspection system information acquisition unit 10h, and inspection system information storage unit 10i. Here, upgrade support server 10 corresponds to the software update support device of the present invention.

[0040] Software management information storage unit 10g stores software management information acquired through software management information acquisition unit 10f. This software management information is information for managing software, such as version information and past upgrade history of software running on management server 30, in-servers 40-1 and 40-2, teaching terminals 50-1 and 50-2, analysis terminal 60, inspection devices 70-1 to 70-4, and visual inspection terminals 80-1 and 80-2 (hereinafter simply referred to as each device) that make up inspection system 1. Software management information storage unit 10g stores this software management information in association with each device. Here, software management information acquisition unit 10f and software management information storage unit 10g correspond to the management information acquisition unit and management information storage unit of the present invention, respectively.

[0041] The inspection system information storage unit 10i stores inspection system information acquired through the inspection system information acquisition unit 10h. This inspection system information includes the operating status and history of each device that constitutes the inspection system 1. The inspection system information also includes information about the system configuration of the inspection system 1. The information about the system configuration is information that represents the relationship between each device that constitutes the inspection system 1, and includes information that specifies the order in which software is upgraded, such as the relationship in which information output from one device is used for processing in another device. The inspection system information storage unit 10i stores this inspection system information in association with each device. The inspection system information acquisition unit 10h and the inspection system information storage unit 10i correspond to the device information acquisition unit and the device information storage unit of the present invention, respectively.

[0042] Upgrade module storage unit 10d stores upgrade modules used to upgrade software executed in each device constituting inspection system 1. The upgrade modules are not limited to replaceable components of the software executed in each device, but may be the entire software. In this manner, upgrade modules for each device constituting inspection system 1 are stored in upgrade support server 10. Furthermore, information such as version information and capacity of the upgrade modules stored in upgrade module storage unit 10d is output to upgrade plan generation unit 10a. Furthermore, the version information of the upgrade modules stored in upgrade module storage unit 10d is stored in software management information storage unit 10g. Here, the upgrade modules and upgrade module storage unit 10d correspond to the update software and update software storage unit of the present invention, respectively.

[0043] The upgrade plan generating unit 10a generates an upgrade plan that is a plan for upgrading software running in each device that constitutes the inspection system 1. The upgrade plan is generated based on software management information, inspection system information, information about the upgrade module, and upgrade conditions acquired through the upgrade condition acquiring unit 10b. Details of the upgrade conditions and the upgrade plan will be described later. Here, the upgrade plan generating unit 10a and the upgrade condition acquiring unit 10b correspond to the update plan generating unit and the update information receiving unit of the present invention, respectively.

[0044] The upgrade plan generated by the upgrade plan generating unit 10a is stored in the upgrade plan storage unit 10c in association with each device constituting the inspection system 1. Here, the upgrade plan generating unit 10a corresponds to the upgrade plan storage unit of the present invention.

[0045] The upgrade modules stored in the upgrade module storage unit 10d and the upgrade plan stored in the upgrade plan storage unit 10c are transmitted from the upgrade information transmission unit 10e to the management terminal 20 via the network NW2. At this time, an upgrade plan is generated and transmitted for software that is to be upgraded, and all of the software executed in each device constituting the inspection system 1 is upgraded. Here, the upgrade information transmission unit 10e corresponds to the update information providing unit of the present invention.

[0046] (Administrative terminal configuration) 4 shows a functional block diagram of the management terminal 20. The management terminal 20 is a device that manages software executed in each device that configures the inspection system 1.

[0047] Management terminal 20 includes an upgrade plan generation and editing unit 20a, an upgrade module acquisition unit 20b, an upgrade module storage unit 20c, an upgrade module transmission unit 20d, an upgrade plan acquisition unit 20e, an upgrade plan storage unit 20f, an upgrade plan transmission unit 20g, an upgrade plan and performance display unit 20h, an upgrade condition acquisition unit 20i, a software management information acquisition unit 20j, a software management information storage unit 20k, an inspection system information acquisition unit 20m, an inspection system information storage unit 20n, and an inspection system information and software management information transmission unit 20o. These functional units are realized, for example, by executing a program such as a system management application on a CPU or the like.

[0048] The upgrade plan generating and editing unit 20a generates or edits an upgrade plan. The upgrade plan may be one provided by the upgrade support server 10 and used as is, or may be an edited version, or may be one generated by specifying the software to be upgraded, the scheduled date and time of upgrade, etc., using an upgrade plan and results screen 201 (described later).

[0049] The upgrade module acquisition unit 20b acquires an upgrade module provided from the upgrade support server 10. Specifically, the upgrade module acquisition unit 20b is configured according to the form of provision of the upgrade module, and may include a communication unit as in the case where the upgrade module is received via the network NW2, or may include a reading unit if the upgrade module is provided stored on a storage medium.

[0050] The upgrade module storage unit 20c stores the upgrade module acquired by the upgrade module acquisition unit 20b.

[0051] The upgrade module transmission unit 20d transmits the upgrade module stored in the upgrade module storage unit 20c to the management server 30.

[0052] The upgrade plan acquisition unit 20e acquires an upgrade plan provided by the upgrade support server 10. Like the upgrade module acquisition unit 20b, the upgrade plan acquisition unit 20e is configured according to the form in which the upgrade plan is provided.

[0053] The upgrade plan storage unit 20f stores the upgrade plan acquired by the upgrade plan acquisition unit 20e.

[0054] The upgrade plan transmission unit 20g transmits the upgrade plan stored in the upgrade plan storage unit 20f to the management server 30.

[0055] The upgrade plan and performance display section 20h displays an upgrade plan and performance screen 201 (see FIG. 12) including information such as the upgrade plan and performance of past upgrades.

[0056] The upgrade condition acquisition unit 20i is an upgrade condition acquisition unit for acquiring upgrade conditions selected or set by the user, and is configured by, for example, an input device.

[0057] Software management information acquisition unit 20j acquires software management information from management server 30 or each device below management server 30 that constitutes inspection system 1. This software management information is information for managing software, such as version information of software running on each device that constitutes inspection system 1 and the history of past version upgrades.

[0058] SM information storage unit 20k stores SM information acquired by SM information acquisition unit 20j. Here, SM information storage unit corresponds to the system-side device information storage unit of the present invention.

[0059] The inspection system information acquisition unit 20m acquires inspection system information from the management server 30 or each device below the management server 30 that constitutes the inspection system 1. This inspection system information includes the operating status and history of each device that constitutes the inspection system 1. The inspection system information also includes information about the system configuration of the inspection system 1.

[0060] The inspection system information storage unit 20n stores the inspection system information acquired by the inspection system information acquisition unit 20m. Here, the inspection system information storage unit 20n corresponds to a system-side device information storage unit.

[0061] The inspection system information / software management information transmission unit 20o transmits the software management information stored in the software management information storage unit 20k and the inspection system information stored in the inspection system information storage unit 20n to the upgrade support server 10 via the network NW2.

[0062] (Administration Server Configuration) 5 shows a functional block diagram of the management server 30. The management server 30 is a device that cooperates with the management terminal 20 to perform integrated management of the devices that make up the inspection system 1, including the management server 30 and the devices below it.

[0063] The management server 30 includes an upgrade control unit 30a, a software storage unit 30b, a software management unit 30c, a device information storage unit 30d, a software management information and device information transmission unit 30e, an upgrade module acquisition unit 30f, an upgrade module storage unit 30g, an upgrade plan acquisition unit 30h, an upgrade plan storage unit 30i, an upgrade module and upgrade plan distribution unit 30j, a system device information acquisition unit 30k, and a software management information acquisition unit 30m. These functional units are executed by the management server using an upgrade module according to, for example, the upgrade plan. This is realized by executing, in a CPU or the like, a program such as an upgrade application for the management server 30 that upgrades the software to be updated and manages the upgrades of the software executed in other devices that constitute the inspection system 1. Here, the management server 30, or the management terminal 20 and the management server 30, correspond to the inspection system management device of the present invention.

[0064] The upgrade control unit 30a upgrades the software executed by the management server 30. Furthermore, since the management server 30 manages the upgrades of the software executed in each device below the management server 30 that constitutes the inspection system 1, the upgrade control unit 30a also has a function of managing the upgrades of each device. The upgrade control unit 30a corresponds to the update control unit of the present invention.

[0065] The software storage unit 30b stores software executed by the management server 30.

[0066] Software management unit 30c manages the versions of software executed by management server 30, the history of past upgrades, etc. Software management unit 30c also stores software management information, such as software versions and the history of past upgrades, acquired by software management information acquisition unit 30m from devices other than management server 30 among the devices constituting inspection system 1. Here, software management unit 30c corresponds to the system-side management information storage unit of the present invention.

[0067] The device information storage unit 30d stores information including the operating status and history of the management server 30. The device information storage unit 30d also stores system device information, which is information including the operating status and history of devices other than the management server 30, among the devices constituting the inspection system 1, acquired by the system device information acquisition unit 30k. Here, the device information storage unit 30d corresponds to the system-side device information storage unit of the present invention.

[0068] SM information / device information transmitter 30 e transmits device information and SM information of management server 30 to management terminal 20 .

[0069] The upgrade module acquisition unit 30f acquires an upgrade module transmitted from the management terminal 20. This upgrade module is not limited to one for upgrading the software executed in the management server 30, but also includes one for upgrading the software executed in each device below the management server 30 that constitutes the inspection system 1. Here, the upgrade module acquisition unit 30f corresponds to the update software acquisition unit of the present invention.

[0070] The upgrade module storage unit 30g stores the upgrade modules acquired by the upgrade module acquisition unit 30f. As described above, the upgrade modules include those for software executed in devices other than the management server 30, and therefore the upgrade modules are stored in association with the devices on which the software to be upgraded is executed.

[0071] The upgrade plan acquisition unit 30h acquires an upgrade plan transmitted from the management terminal 20. This upgrade plan is not limited to one related to the upgrade of software executed in the management server 30, but also includes one related to the upgrade of software executed in each device below the management server 30 that constitutes the inspection system 1. Here, the upgrade plan acquisition unit 30h corresponds to the update plan acquisition unit of the present invention.

[0072] The upgrade plan storage unit 30i stores the upgrade plans acquired by the upgrade plan acquisition unit 30h. As described above, the upgrade plans include those for software executed in devices other than the management server 30, and therefore the upgrade plans are stored in association with the devices in which the software to be upgraded is executed.

[0073] Of the upgrade modules stored in the upgrade module storage unit 30g, those for software executed in devices other than the management server 30, and of the upgrade plans stored in the upgrade plan storage unit 30i, those for software executed in devices other than the management server 30, are distributed by the upgrade module / upgrade plan distribution unit 30j to devices in which software upgrades will be performed. For devices directly connected to the management server 30 via the network NW1, such as the line servers 40-1 and 40-2, teaching terminals 50-1 and 50-2, and analysis terminal 60 shown in FIG. 2, the upgrade modules and upgrade plans are transmitted from the management server 30 to these devices. 2, for devices connected to the management server 30 via the network NW1 and the line servers 40-1 and 40-2, the upgrade modules and upgrade plans are transmitted from the management server 30 to the line servers 40-1 and 40-2, and then transmitted from the line servers 40-1 and 40-2 to the respective devices. Here, the upgrade module and upgrade plan distribution unit 30j corresponds to the update software and upgrade plan distribution unit of the present invention.

[0074] The system device information acquiring unit 30k acquires system device information, which is information including the operating status and history of each device other than the management server 30, from among the devices constituting the inspection system 1. The acquired system device information is stored in the device information storage unit 30d together with the device information of the management server 30.

[0075] Software management information acquisition unit 30m acquires software management information such as software versions and past upgrade histories from devices other than management server 30 among the devices constituting inspection system 1. The acquired software management information is stored in software management unit 30c together with the software management information of management server 30.

[0076] Of the devices that make up the inspection system 1, device information and software management information from devices other than the management server 30 are transmitted from the software management information / device information transmitting unit 30e to the management terminal 20 together with the device information and software management information of the management server 30.

[0077] (Line Server Configuration) Fig. 6 shows a functional block diagram of the line servers 40-1 and 40-2. Since the line servers 40-1 and 40-2 have similar configurations, the subnumbers of the reference numerals will be omitted in the description common to the line servers 40-1 and 40-2, including the description referring to Fig. 6.

[0078] The line server 40 is a server that manages the production process of the printed circuit board production line under the control of the management server 30.

[0079] The line server 40 includes a version upgrade control unit 40a, a software storage unit 40b, a software management unit 40c, a device information storage unit 40d, and a software management information / device information transmission unit. The inspection system 1 includes a software upgrade module acquisition unit 40e, an upgrade module acquisition unit 40f, an upgrade module storage unit 40g, an upgrade plan acquisition unit 40h, an upgrade plan storage unit 40i, an upgrade module / upgrade plan distribution unit 40j, a system device information acquisition unit 40k, and a software management information acquisition unit 40m. These functional units are realized, for example, by executing, in a CPU or the like, a program such as an upgrade application for the line server 40 that upgrades the software to be updated that is executed in the line server 40 using an upgrade module in accordance with the upgrade plan, and manages the upgrade of software that is executed in other devices below the line server that constitute the inspection system 1.

[0080] The upgrade control unit 40a upgrades the software executed in the line server 40. Furthermore, since the line server 40 manages the upgrades of the software executed in each device below the line server 40 that constitutes the inspection system 1, the upgrade control unit 40a also has a function of managing the upgrades of each device. The upgrade control unit 40a corresponds to the update control unit of the present invention.

[0081] The software storage unit 40b stores software executed by the line server 40.

[0082] The software management unit 40c manages the versions of the software executed by the line server 40, the history of past version upgrades, and the like.

[0083] The device information storage unit 40d stores information including the operating status of the line server 40 and its history.

[0084] Software management information / device information transmitter 40 e transmits the device information and software management information of line server 40 to management server 30 .

[0085] The upgrade module acquisition unit 40f acquires an upgrade module transmitted from the management server 30. This upgrade module is not limited to one for upgrading the software executed in the line server 40, but also includes one for upgrading the software executed in each device below the line server 40 that constitutes the inspection system 1.

[0086] The upgrade module storage unit 40g stores the upgrade modules acquired by the upgrade module acquisition unit 40f. As described above, the upgrade modules include those for software executed in devices other than the line server 40, and therefore the upgrade modules are stored in association with the devices on which the software to be upgraded is executed.

[0087] The upgrade plan acquisition unit 40h acquires the upgrade plan transmitted from the management server 30. This upgrade plan is not limited to upgrades of the software executed in the line server 40, but also includes upgrades of the software executed in each device below the line server 40 that constitutes the inspection system 1.

[0088] The upgrade plan storage unit 40i stores the upgrade plan acquired by the upgrade plan acquisition unit 40h. As described above, the upgrade plan includes upgrade plans for software executed in devices other than the line server 40. Therefore, the upgrade plan is stored in association with the device in which the software to be upgraded is executed. The version upgrade plan is stored in association with the device on which the software to be upgraded is executed.

[0089] Of the upgrade modules stored in the upgrade module storage unit 40g, those for software executed in devices other than the line server 40, and of the upgrade plans stored in the upgrade plan storage unit 40i, those for software executed in devices other than the line server 40, are distributed by the upgrade module / upgrade plan distribution unit 40j to the devices in which the software upgrade will be performed. In the inspection system 1 shown in FIG. 2, the line server 40-1 transmits the upgrade modules and upgrade plans to the inspection devices 70-1 and 70-2 and the visual inspection terminal 80-1. The line server 40-2 transmits the upgrade modules and upgrade plans to the inspection devices 70-3 and 70-4 and the visual inspection terminal 80-2.

[0090] The system device information acquiring unit 40k acquires system device information, which is information including the operating status and history of each device other than the line server 40, from among the devices constituting the inspection system 1. The acquired system device information is stored in the device information storage unit 40d together with the device information of the line server 40.

[0091] The software management information acquisition unit 40m acquires software management information, such as software versions and past upgrade histories, from each device other than the line server 40 among the devices constituting the inspection system 1. The acquired software management information is stored in the software management unit 40c together with the software management information of the line server 40.

[0092] Of the devices that make up the inspection system 1, device information and software management information from devices other than the line server 40 are transmitted from the software management information / device information transmitting unit 40e to the management server 30 together with the device information and software management information of the management server 40.

[0093] (Teaching terminal configuration) Fig. 7 shows a functional block diagram of the teaching terminals 50-1 and 50-2. The teaching terminals 50-1 and 50-2 are devices that create inspection programs to be executed in the inspection devices 70-1 to 70-4. Because the teaching terminals 50-1 and 50-2 have the same configuration, the subnumbers of the reference numerals will be omitted in the description common to the teaching terminals 50-1 and 50-2, including the description that refers to Fig. 7.

[0094] The teaching terminal 50 includes an upgrade control unit 50a, a software storage unit 50b, a software management unit 50c, a device information storage unit 50d, a software management information / device information transmission unit 50e, an upgrade module acquisition unit 50f, an upgrade module storage unit 50g, an upgrade plan acquisition unit 50h, an upgrade plan storage unit 50i, and a related device information acquisition unit 50j. These functional units are realized, for example, by executing in a CPU or the like a program such as an upgrade app for the teaching terminal 50 that upgrades the software to be updated that is executed on the teaching terminal 50 using an upgrade module in accordance with the upgrade plan.

[0095] The upgrade control unit 50a upgrades the software executed on the teaching terminal 50. The upgrade control unit 50a corresponds to the update control unit of the present invention.

[0096] The software storage unit 50b stores software executed by the teaching terminal 50. It is remembered.

[0097] The software management unit 50c manages the version of the software executed on the teaching terminal 50, the history of past version upgrades, and the like.

[0098] The device information storage unit 50d stores information including the operating status of the teaching terminal 50 and its history.

[0099] The software management information / device information transmission unit 50 e transmits the software management information of the teaching terminal 50 and the inspection device information to the management server 30 .

[0100] The upgrade module acquisition unit 50f acquires the upgrade module transmitted from the management server 30.

[0101] The upgrade module storage unit 50g stores the upgrade module acquired by the upgrade module acquisition unit 50f.

[0102] The upgrade plan acquisition unit 50h acquires the upgrade plan transmitted from the management server 30.

[0103] The upgrade plan storage unit 50i stores the upgrade plan acquired by the upgrade plan acquisition unit 50h.

[0104] The related device information acquisition unit 50j acquires information on related devices that are devices related to the execution of a version upgrade of software executed on the teaching terminal 50, among the devices constituting the inspection system 1, such as whether the version of software executed on the management server 30 and the inspection devices 70-1 to 70-4 has been completed. Which devices correspond to related devices is determined by the configuration of the inspection system 1. Here, related devices correspond to other devices of the present invention.

[0105] The analysis terminal 60 is a terminal that analyzes quality status, etc. based on the inspection data of the inspection devices 70-1 to 70-4, but since the functional block configuration is similar to that of the teaching terminals 50-1 and 50-2, the functional blocks related to the analysis terminal 60 are shown with symbols in parentheses in Figure 7, and their explanation is omitted.

[0106] (Configuration of inspection equipment) Fig. 8 shows a functional block diagram related to software upgrades for the inspection devices 70-1 to 70-4. Since the inspection devices 70-1 to 70-4 have the same configuration, the subnumbers of the reference numerals will be omitted in the description common to the inspection devices 70-1 to 70-4, including the description referring to Fig. 8.

[0107] The inspection device 70 includes an upgrade control unit 70a, a software storage unit 70b, a software management unit 70c, an inspection device information storage unit 70d, a software management information / inspection device information transmission unit 70e, an upgrade module acquisition unit 70f, an upgrade module storage unit 70g, an upgrade plan acquisition unit 70h, an upgrade plan storage unit 70i, and a related device information acquisition unit 70j. These functional units are realized, for example, by executing, in a CPU or the like, a program such as an upgrade application for the inspection device 70 that upgrades software to be updated and that is executed in the inspection device 70 using an upgrade module in accordance with the upgrade plan.

[0108] The upgrade control unit 70a performs an upgrade of the software executed in the inspection device 70. The upgrade control unit 70a corresponds to the update control unit of the present invention.

[0109] The software storage unit 70b stores software executed by the inspection device 70.

[0110] The software management unit 70c manages the versions of the software executed by the inspection device 70, the history of past version upgrades, and the like.

[0111] The inspection device information storage unit 70d stores information including the operating status and history of the inspection device 70.

[0112] Software management information and inspection device information transmission unit 70 e transmits software management information and inspection device information of inspection device 70 to management server 30 .

[0113] The upgrade module acquisition unit 70f acquires the upgrade module transmitted from the line server 40.

[0114] The upgrade module storage unit 70g stores the upgrade module acquired by the upgrade module acquisition unit 70f.

[0115] The upgrade plan acquisition unit 70h acquires the upgrade plan transmitted from the line server 40.

[0116] The upgrade plan storage unit 70i stores the upgrade plan acquired by the upgrade plan acquisition unit 70h.

[0117] The related device information acquisition unit 70j acquires information on related devices that are related to the execution of a version upgrade of the software executed in the inspection device 70, among the devices constituting the inspection system 1, such as whether the version of the software executed in the line server 40 is complete or not. Which devices correspond to related devices is determined by the configuration of the inspection system 1. Here, the related devices correspond to other devices of the present invention.

[0118] (Visual terminal configuration) Fig. 9 shows a functional block diagram of the visual inspection terminals 80-1 and 80-2. The visual inspection terminals 60-1 and 60-2 are devices for visually checking images of printed circuit boards captured by the inspection devices 70-1 to 70-4. Since the visual inspection terminals 80-1 and 80-2 have the same configuration, the subnumbers of the reference numerals will be omitted in the description common to the visual inspection terminals 80-1 and 80-2, including the description referring to Fig. 9.

[0119] The visual inspection terminal 80 includes an upgrade control unit 60a, a software storage unit 60b, a software management unit 60c, a device information storage unit 60d, a software management information / device information transmission unit 60e, an upgrade module acquisition unit 60f, an upgrade module storage unit 60g, an upgrade plan acquisition unit 60h, an upgrade plan storage unit 60i, and a related device information acquisition unit 60j. These functional units are realized, for example, by executing in a CPU or the like a program such as an upgrade application for the visual inspection terminal 80 that upgrades software to be updated that is executed on the visual inspection terminal 80 using an upgrade module in accordance with the upgrade plan.

[0120] The upgrade control unit 80a performs an upgrade of the software executed on the visual inspection terminal 80. The upgrade control unit 80a corresponds to the update control unit of the present invention.

[0121] The software storage unit 80b stores software executed by the visual inspection terminal 80.

[0122] The software management unit 80c manages the version of the software executed on the visual inspection terminal 80, the history of past version upgrades, and the like.

[0123] The device information storage unit 80d stores information including the operating status of the visual inspection terminal 80 and its history.

[0124] The software management information / device information transmission unit 80 e transmits the software management information of the visual inspection terminal 80 and the inspection device information to the management server 30 .

[0125] The upgrade module acquisition unit 80f acquires the upgrade module transmitted from the line server 40.

[0126] The upgrade module storage unit 80g stores the upgrade module acquired by the upgrade module acquisition unit 80f.

[0127] The upgrade plan acquisition unit 80h acquires the upgrade plan transmitted from the line server 40.

[0128] The upgrade plan storage unit 80i stores the upgrade plan acquired by the upgrade plan acquisition unit 80h.

[0129] The related device information acquisition unit 80j acquires information on related devices that are related to the execution of a version upgrade of the software executed on the visual inspection terminal 80, among the devices constituting the inspection system 1, such as whether the version of the software executed on the line server 40 has been completed. Which devices are related devices depends on the configuration of the inspection system 1.

[0130] (How to upgrade) The processing procedure for upgrading software will be described with reference to the sequence diagram of Fig. 10. Specifically, Fig. 10 shows the procedure from when an upgrade plan is generated in the upgrade support server 10, to when it is transmitted together with an upgrade module to the management terminal 10, and finally to when it is transmitted to each device constituting the inspection system 1.

[0131] First, the upgrade support server 10 notifies a person in charge (e.g., an operator) that software executed in each device constituting the inspection system 1 will be upgraded, and also proposes upgrade conditions for generating an upgrade plan (step S101). This notification may be sent by email to the person in charge, as will be described later, or may be displayed on the display unit of an appropriate terminal connected to the upgrade support server 10.

[0132] The person in charge sets the proposed upgrade conditions by selecting them or the like by replying to the email or the like (step S102).

[0133] The upgrade support server 10 generates an upgrade plan based on the set upgrade conditions and transmits it to the management terminal 20 together with the upgrade modules (hereinafter, unless otherwise specified, this term will include upgrade modules for all software to be upgraded) (S103-1). In the management terminal 20, the upgrade modules acquired through the upgrade module acquisition unit 20b are stored in the upgrade module storage unit 20c, and the upgrade plan acquired through the upgrade plan acquisition unit 20e is stored in the upgrade plan storage unit 20f. The upgrade plan is generated for the software to be upgraded.

[0134] In addition to carrying out upgrades in each device constituting the inspection system 1 according to the upgrade plan transmitted from the upgrade support server 10, as will be described later, the person in charge can also select upgrade conditions in which the person in charge specifies the upgrade date and time. In such a case, the person in charge can instruct the upgrade plan generating and editing unit 20a to edit the upgrade plan by setting the upgrade date and time using an input device constituting the upgrade condition acquisition unit 20i for the upgrade plan acquired from the upgrade support server 10 (step S103-2). Furthermore, the management terminal 20 can also edit the upgrade plan acquired from the upgrade support server 10 by using the upgrade plan generating and editing unit 20a to change the upgrade conditions, etc., or by specifying more detailed upgrade conditions.

[0135] Furthermore, an upgrade plan can also be generated in the management terminal 20 by a person in charge inputting upgrade conditions such as the upgrade start date and time using an input device constituting the upgrade condition acquisition unit 20i, using an upgrade plan and performance screen 201 (see FIG. 12) generated by the upgrade plan generation and editing unit 20a of the management terminal 10 and displayed on the upgrade plan and performance display unit 20h. In this case, only the upgrade module is acquired from the upgrade support server 10 or the provider of the upgrade module.

[0136] The upgrade module and upgrade plan stored in the management terminal 20 are transmitted to the management server 30 (step S104). In the management server 30, the upgrade module and upgrade plan are received by the upgrade module acquisition unit 30f and the upgrade plan acquisition unit 30h, and stored in the upgrade module storage unit 30g and the upgrade plan storage unit 30i, respectively. The management terminal 20 and the management server 30 may be connected directly or via the network NW1. For upgrades of software executed on the management server 30, the software version information, scheduled date and time, etc. are stored in the software management unit 30c, the status is managed, and the upgrade control unit 30a executes the upgrade of the target software in accordance with the upgrade plan.

[0137] The devices that make up the inspection system 1 are divided into devices that are connected to the management server 30 through the network NW1 and devices that are connected to the management server 30 via line servers 40-1 and 40-2, and the prescribed procedures differ depending on the connection relationship with the management server 30. In the inspection system 1 shown in Fig. 2, the teaching terminals 50-1 and 50-2 and the analysis terminal 60 are directly connected to the management server 30, the inspection devices 70-1 and 70-2 and the visual inspection terminal 80-1 are connected to the management server 30 via the line server 40-1, and the inspection devices 70-3 and 70-4 and the visual inspection terminal 80-2 are connected to the management server 30 via the line server 40-2.

[0138] First, the teaching server 30 is directly connected to the management server 30 via the network NW1. The upgrade control unit 50a of the terminal 50 and the upgrade control unit 60a of the analysis terminal 60 transmit an upgrade module acquisition request to the management server 30 (step S105).

[0139] In response to this, the upgrade control unit 30a in the management server 30 causes the upgrade module / upgrade plan distribution unit 30j to transmit the upgrade module and upgrade plan for each of the teaching terminal 50 and the analysis terminal 60 to each device (step S106). At this time, in the teaching terminal 50, the upgrade module and upgrade plan are received by the upgrade module acquisition unit 50f and the upgrade plan acquisition unit 50h and stored in the upgrade module storage unit 50g and the upgrade plan storage unit 50i, respectively, and the version information, scheduled date and time, etc. are stored in the software management unit 50c, and the status is managed. Also, in the analysis terminal 60, the upgrade module and upgrade plan are received by the upgrade module acquisition unit 60f and the upgrade plan acquisition unit 60h and stored in the upgrade module storage unit 60g and the upgrade plan storage unit 60i, respectively, and the version information, scheduled date and time, etc. are stored in the software management unit 60c, and the status is managed.

[0140] Next, the procedure for the devices connected via the line servers 40-1 and 40-2 will be described. Regarding the upgrade modules and upgrade plans for the line server 40, the inspection device 70, and the visual inspection terminal 80, the upgrade control unit 40a of the line server 40 transmits an upgrade module acquisition request to the management server 30 (step S107).

[0141] In response to this, the management server 30 transmits to the line server 40 an upgrade module and an upgrade plan for each of the line server 40, the inspection device 70, and the visual inspection terminal 80 (step S108). At this time, in the line server 40, the upgrade module and the upgrade plan are received by the upgrade module acquisition unit 40f and the upgrade plan acquisition unit 40h, and are stored in the upgrade module storage unit 40g and the upgrade plan storage unit 40i, respectively. For upgrades of software executed in the line server 40, the software version information, scheduled date and time, etc. are stored in the software management unit 40c, and the status is managed.

[0142] Next, the inspection devices 70-1 and 70-2 and the visual inspection terminal 80-1 transmit an upgrade module acquisition request to the line server 40-1 (step S109). Similar processing is performed between the inspection devices 70-3 and 70-4 and the visual inspection terminal 80-2 and the line server 40-2, and therefore a description thereof will be omitted.

[0143] In response to the acquisition request, the upgrade module and upgrade plan for the inspection device 70 and the visual inspection terminal 80 are transmitted from the upgrade module / upgrade plan distribution unit 40j to the respective devices from the line server 40 (step S110). At this time, in the inspection device 70, the upgrade module and upgrade plan are received by the upgrade module acquisition unit 70f and the upgrade plan acquisition unit 70h and stored in the upgrade module storage unit 70g and the upgrade plan storage unit 70i, respectively, and the software version information, scheduled date and time, etc. are stored in the software management unit 70c, and the status is managed. Also, in the visual inspection terminal 80, the upgrade module and upgrade plan are received by the upgrade module acquisition unit 80f and the upgrade plan acquisition unit 80h and stored in the upgrade module storage unit 80g and the upgrade plan storage unit 80i, respectively. At the same time, the software version information, scheduled date and time, etc. are stored in the software management unit 80c, and the status is managed.

[0144] With reference to Figure 11, the procedure for performing a software upgrade in accordance with the upgrade module and upgrade plan stored in each device will be described. Figure 11 shows the case of an inspection device 70 connected to a line server 40. Although not shown in Figure 11, the visual inspection terminal 80 is upgraded in the same procedure as the inspection device 70 in relation to the line server 40. Furthermore, the teaching terminal 50 and the analysis terminal 60, which are directly connected to the management server 30 via the network NW1, are upgraded in the example shown in Figure 11 in a procedure in which the line server 40 is replaced with the management server 30 and the inspection device 70 is replaced with the teaching terminal 50 and the analysis terminal 60.

[0145] First, in the line server 40, the upgrade control unit 40a checks whether or not the time for upgrading the application executed in the line server 40-1 as defined in the upgrade plan has arrived (step S201). If the upgrade control unit 40a determines that the time for an upgrade has arrived, it terminates the application to be upgraded (step S202). Then, with the application to be upgraded terminated, the upgrade control unit 40a updates the module of the application to be upgraded to the upgrade module stored in the upgrade module storage unit 40g (step S203) and starts the upgraded application (step S204). In this way, the upgrade of the application running on the line server 40 is completed. With the completion of the upgrade, the current version information of the application stored in the software management unit 40c is updated, and management information such as the version information of the upgraded application and the date and time of completion of the upgrade is stored in the software management unit 40c and transmitted from the software management information / device information transmission unit 40e to the management server 30.

[0146] Next, the version upgrade of the application executed in the inspection device 70 will be described. The upgrade control unit 70a of the inspection device 70 checks whether the time for the upgrade specified in the upgrade plan has arrived for the application being executed on the inspection device 70, based on the upgrade plan stored in the upgrade plan memory unit 70i (step S205). When the upgrade control unit 70a determines that the time for an upgrade has arrived, the upgrade control unit 70a executes a status check of the line server 40 (step S206). This status check is performed by confirming with the upgrade control unit 40a of the line server 40 whether the upgrade of the related app has been completed in the line server 40. In the line server 40, the upgrade control unit 40a determines whether the upgrade of the related app has been completed based on the upgrade history stored in the software management unit 40c, and notifies the inspection device 70 of the result. The inspection device 70 acquires this result via the related device information acquisition unit 70j. If the upgrade of the related app has been completed, the upgrade app of the inspection device 70 proceeds to step S17. However, if the backup of the related app has not been completed, the upgrade app waits for its completion. This is because, when the line server 40 performs a predetermined process based on data acquired from the inspection device 70, the line server 40 running an application that has not yet been upgraded may not be able to properly process the data output from the inspection device 70 whose application has already been upgraded, which may result in an error. The order of upgrades (priority) may be included in the upgrade plan based on information related to the configuration of the inspection system 1, but the upgrade control unit 70a may determine the order of upgrades regardless of the content of each individual upgrade plan. In this case, the line server 40 corresponds to the other device of the present invention in comparison with the inspection device 70.

[0147] When the upgrade control unit 70a of the inspection device 70 confirms in step S17 that the upgrade in the line server 40 has been completed, it terminates the target application of the inspection device 70 (step S207). Then, with the target application being upgraded terminated, the upgrade control unit 70a updates the module of the target application to the upgrade module stored in the upgrade module storage unit 70g (step S208) and starts the upgraded application (step S209). In this way, the upgrade of the application running in the inspection device 70 is completed. When the upgrade of the application is completed, management information such as version information of the upgraded application and the date and time of completion of the upgrade is stored in the software management unit 70c and transmitted from the software management information / inspection device information transmission unit 70e to the management server 30.

[0148] (Version upgrade plan / performance screen) FIG. 12 shows an example of an upgrade plan and results screen 201 displayed on the upgrade plan and results display section 20h of the management terminal 20. As shown in FIG. For each device, the following items are provided: the current version of the software running, the planned version of the upgrade, the upgrade status, the planned date and time of the upgrade, and the date and time of completion of the upgrade. This information is managed and stored in the software management unit 30c of the management server 30 and the software management unit 40c of each device, and is transmitted to the management server 30 via the software management information / device information transmission unit 40e. The management server 30 acquires this information via the software management information acquisition unit 30m and stores it in the software management unit 30c along with management information for the software executed on the management server. This information is transmitted from the software management unit 30e of the management server 30 to the management terminal 20. The management terminal 20 acquires this information via the software management information acquisition unit 20j and stores it in the software management information storage unit 20k. The upgrade plan generation / editing unit 20a generates the upgrade plan / achievement screen 201 based on this information and displays it in the upgrade plan / achievement display unit 20h.

[0149] The names displayed in the name column of the upgrade plan and results screen 201 are the management server, I-line server 1, inspection devices I-VT-S530-0100 and I-VT-S1080-0100 connected to I-line server 1, visual inspection terminal Iv-CA-001 connected to inspection device I-VT-S530-0100, visual inspection terminal Iv-CA-002 connected to inspection device I-VT-S1080-0100, I-line server 2, inspection device I-VT-S530-0200 connected to I-line server 2, and teaching terminal Iv-TS-001.

[0150] The current version and the planned upgrade version of the app running on management server 20 are both Ver.1.01.00A, the status is complete, and in addition to the planned date and time 2021 / 10 / 13 12:00, the completion date and time 2021 / 10 / 13 12:05 are displayed, which indicates that the app upgrade has been completed on management server 20.

[0151] Similarly, the app version upgrade has been completed for I-Line Server 1. On the other hand, the current version of the app for the inspection device I-VT-S530-0100 is Ver. 1.00.00A, the planned upgrade version is Ver. 1.01.00A, and the status is "upgrading" and the completion date and time is not displayed, so the current version It can be seen that the inspection device I-VT-S1080-0100 is currently being upgraded. Furthermore, the current version of the application is Ver. 1.00.00A, the planned upgrade version is Ver. 1.01.00A, the status is "inspection in progress," and the completion date and time is not displayed, indicating that the upgrade is not yet complete. Regarding the status of such upgrades, management information stored in the software management units 70c of each device is transmitted to the management server 30 and managed in an integrated manner by the software management unit 30c. The information stored in the software management unit 30c of the management server 30 is transmitted from the software management information / device information transmission unit 30e to the management terminal 20. In the management terminal 20, this information is acquired by the software management information acquisition unit 20j and stored in the software management information storage unit 20k. The upgrade plan generation and editing unit 20a generates the above-mentioned upgrade plan and results screen 201 based on this information.

[0152] Furthermore, the visual inspection terminal Iv-CA-001 connected to the inspection device I-VT-S530-0100 has the current app version Ver. 1.00.00A, the planned upgrade version Ver. 1.01.00A, and the status is "Waiting for the inspection device I-VT-S530-0100 upgrade to be completed." The completion date and time are not displayed, indicating that the upgrade has not yet begun. The visual inspection terminal Iv-CA-002 connected to the inspection device I-VT-S1080-0100 also has the current app version Ver. 1.00.00A, the planned upgrade version Ver. 1.01.00A, the status is "Waiting for the inspection device I-VT-S1080-0100 upgrade to be completed." The completion date and time are not displayed, indicating that the upgrade has not yet begun.

[0153] Furthermore, for I-Line Server 2 and the testing device I-VT-S530-0200 connected to I-Line Server 2, the current version of the app is Ver. 1.00.00A, but no data is displayed for the planned upgrade version and planned date and time, and the status is displayed as unplanned, which indicates that no upgrade is planned.

[0154] Furthermore, for teaching terminal Iv-TS-001, the current version of the app and the planned upgrade version are both Ver. 1.01.00A, the status is Completed, and in addition to the scheduled date and time 2021 / 10 / 13 12:00, the completion date and time 2021 / 10 / 13 12:10 are displayed, which indicates that the app upgrade for teaching terminal Iv-TS-001 has been completed.

[0155] The planned upgrade version described above may be input by the person in charge using an input device and edited or updated on the upgrade plan and results screen 201 displayed on the upgrade plan and results display unit 20h of the management terminal 20, or the upgrade plan generating and editing unit 20a may read it from the upgrade module stored in the upgrade module storage unit 20c registered by the person in charge and edit or update the upgrade plan and results screen 201. As for the scheduled date and time, the person in charge may edit or update the upgrade plan and results screen 201 on the upgrade plan and results display unit 20h of the management terminal 20, or the upgrade plan generating and editing unit 20a may read it from the upgrade plan stored in the upgrade plan storage unit 20f and edit or update the upgrade plan and results screen 201.

[0156] In the above example, the software upgrade process has been described, in which the person in charge uses the management terminal 20 to store the upgrade module in the upgrade module storage unit 20c, and edits and updates the upgrade plan on the upgrade plan and results screen 201 displayed on the upgrade plan and results display unit 20h. The acquisition of the upgrade module and upgrade plan and the implementation of the upgrade can be realized in various forms, including the examples described above.

[0157] When the upgrade support server 10 operated by the provider of the upgrade module and the inspection system 1 are connected via cloud, the following configurations are possible. In this case, a proposal email of the new software release schedule and upgrade progress is sent to the person in charge of the operation of the inspection system 1, and the upgrade module is automatically or manually downloaded to the management terminal 20 according to the content selected by the person in charge based on the proposal, and an upgrade plan can also be provided.

[0158] Management server 30 of inspection system 1 stores, in software management unit 30c and device information storage unit 30d, management information on software executed in each device below management server 30 that constitutes inspection system 1, as well as device information (inspection system information) such as the operating status and history of each device. Software management information acquisition unit 10f and inspection system information acquisition unit 10h of upgrade support server 10 can acquire this information from management terminal 20 or management server 30. The software management information and inspection system information acquired in this manner are stored in software management information storage unit 10g and inspection system information storage unit 10i of upgrade support server 10, respectively.

[0159] The upgrade plan generating unit 10a of the upgrade support server 10 can generate and propose an upgrade plan such as the following example based on the operating status of the inspection system 1 described above. (1) Based on the past operating status of the inspection system 1, the version upgrade is carried out during "non-operational downtime (break time, shift change time, etc.)." (2) Assuming that the upgrade is carried out as quickly as possible, the upgrade is carried out if it is possible for each device in the inspection system 1. (3) When the inspection equipment is in standby mode, the status of the equipment in the upstream process is monitored, and the software installed in the inspection equipment is upgraded during the short downtime. (4) The customer manually sets the desired date and time. (5) Upgrades are carried out based on production plans (such as setup times) from MES (Manufacturing Execution System) etc.

[0160] The upgrade support server 10 allows the user to select which of the above conditions (1) to (4) the upgrade plan should be generated under, and generates the upgrade plan based on the selected condition. These are upgrade conditions included in the upgrade plan, and are hereinafter referred to as upgrade conditions. The upgrade support server 10 can acquire the above upgrade conditions using the upgrade condition acquisition unit 10b.

[0161] For example, a proposal email of a new software release schedule and upgrade conditions is sent to the person in charge of the operation of the inspection system 1. The destination of the proposal email is not limited to the management terminal 20, but may be sent to an appropriate computer device managed by the person in charge. The person in charge selects one of the upgrade conditions described in the email and sends a reply email. In the upgrade support server 10, the upgrade condition acquisition unit 10b reads out the reply email from the person in charge or the selected upgrade conditions, and based on this, the upgrade plan generation unit 10a generates an upgrade plan based on the upgrade conditions. The person in charge downloads the upgrade module and upgrade plan from the site linked to in the proposal email and stores them in the upgrade module storage unit 20c and upgrade plan storage unit 20f of their own management terminal 20. The person in charge follows the upgrade plan provided by the upgrade support server 10. The upgrade may be implemented by using the upgrade plan and results screen 201 generated based on the provided upgrade plan, or the upgrade plan may be edited and the modified or changed upgrade plan may be implemented.

[0162] (Version upgrade condition selection screen) The method for acquiring the upgrade conditions from the person in charge on the operator side of the inspection system 1 is not limited to the above-mentioned sending and receiving of emails. 13 shows an example of an upgrade condition selection screen 202 for allowing a person in charge to select and set upgrade conditions. As described above, the upgrade condition selection screen 202 shown here may be a screen that is displayed when a link described in an email notifying the release of new software is accessed, or may be a screen that is displayed by pop-up or the like on the management terminal 10 or an appropriate terminal connected to the upgrade support server 10 via the network NW1.

[0163] At the top of the version upgrade condition selection screen 202, a message is displayed informing the user of the release of new software: "Software version 2.00 will be released on March 1, 20022." Below that, a message is displayed prompting you to select a method for upgrading: "Please select a method for upgrading."

[0164] In the middle of the upgrade notification screen, four options for the upgrade method are displayed together with radio buttons 202a to 202d.

[0165] The first option is "2022 / 3 / 1" along with the words "will be held at the following time." A specific scheduled start date and time such as "Scheduled to start at 12:00" is displayed. This scheduled start date and time may be changeable. This is an option when the upgrade is to be carried out at a specific date and time that has been proposed or input. This scheduled start date and time may be proposed by predicting a stop time when the inspection device 70, etc. will not be in operation based on past operating conditions, as in the above-mentioned upgrade condition example (1), or may be changeable or set by input by the user, as in the upgrade condition example (4).

[0166] The second option displays the phrase "Perform when the inspection equipment is in standby mode" and information about the timing, "Perform by monitoring the line status after 10:00 on March 1, 2022." This is an option for monitoring the status of the inspection equipment and performing the upgrade during a short downtime of the inspection equipment after a specific date and time that is proposed or entered, as in the above-mentioned upgrade condition example (3). This specific date and time can also be proposed based on the production plan (setup implementation time), as in the upgrade condition example (5).

[0167] The third option displays the phrase "Perform after the download is complete," along with information about the timing, "After 0:00 on March 1, 2022." This option is for upgrading when the upgrade module is downloaded after the specific date and time suggested or entered, and corresponds to the "fastest" upgrade, as in the example upgrade condition (2) above.

[0168] The fourth option displayed is "Do not upgrade."

[0169] At the bottom of the upgrade condition selection screen 202, information about new software functions is displayed as "New functions in Ver. 2.00."

[0170] Additionally, an "OK" button 202e and a "Later" button 202f are displayed on the right side of the lower section of the upgrade condition selection screen 202. Select one of the radio buttons 202a to 202d and press the "OK" button 202e to finalize the selection of the upgrade method, or press the "Later" button 202f to select the upgrade method later.

[0171] In this way, the upgrade support server 10 proposes the above-mentioned upgrade conditions based on information about the devices that make up the inspection system 1, and generates an upgrade plan based on the upgrade conditions selected and set by the person in charge. That is, an upgrade plan can be generated based on the status of the devices that make up the inspection system, including the inspection devices, that affect the downtime of the inspection devices. Therefore, by updating the software of the devices that make up the inspection system 1 in accordance with the upgrade plan generated by such an upgrade support server, downtime of the inspection device 70 due to the software update can be kept short, and software updates for the entire inspection system 1 can be carried out efficiently.

[0172] [Modification] In the above-described first embodiment, the upgrade support server 10, which is connected to the management terminal 20 constituting the inspection system 1 via the network NW2, generates an upgrade plan based on the selected upgrade conditions and transmits it together with the upgrade module to the management terminal 20. As described above, the upgrade support server 10 is not limited to being provided outside the inspection system 1, but can also be provided within the inspection system 1. In this case, the management terminal 20, or the management terminal 20 and the management server 30 work together to perform the functions of the upgrade support server 10.

[0173] For example, the functions of upgrade plan generation unit 10a and upgrade condition acquisition unit 10b of upgrade support server 10 are respectively performed by upgrade plan generation / editing unit 20a and upgrade condition acquisition unit 20i of management terminal 20. Furthermore, the functions of software management information acquisition unit 10f, software management information storage unit 10g, inspection system information acquisition unit 10h, and inspection system information storage unit 10i of upgrade support server 10 are respectively performed by software management information acquisition unit 20j, software management information storage unit 20k, inspection system information acquisition unit 20m, and inspection system information storage unit 20n of management terminal 20. Furthermore, the functions of upgrade plan storage unit 10c and upgrade module storage unit 10d of upgrade support server 10 are respectively performed by upgrade plan storage unit 20f and upgrade module storage unit 20c of management terminal 20. Furthermore, the function of the upgrade information transmission unit 10e of the upgrade support server 10 is performed by the upgrade plan transmission unit 20g and the upgrade module transmission unit 20d of the management terminal 20.

[0174] At this time, the processing of steps S101 to S103-1 and S103-2 in the sequence diagram shown in Fig. 10 is performed between the operator and the management terminal 20, except for the transmission of the upgrade module (the processing from step S104 onwards is the same). That is, the inspection system 1 acquires only the upgrade module from the upgrade provider, and the operator selects and specifies the upgrade conditions using the management terminal 10, whereby an upgrade plan based on these upgrade conditions is generated and distributed from the management server 20 to each device constituting the inspection system 1. This makes it possible to keep the downtime of the inspection devices to a short time and efficiently upgrade the software of the entire inspection system 1.

[0175] In addition, the person in charge of the version upgrade module provider (e.g., SE (Sales Engineer) )) can visit the customer or access the customer's management terminal 20 via the network, store the upgrade module in the management terminal 20, input the upgrade plan, and carry out the upgrade.

[0176] <Appendix 1> An update support device (10) that supports updating of software executed in any of devices (20, 30, 40-1, 40-2, 50-1, 50-2, 60, 70-1 to 70-4, 80-1, 80-2) that constitute an inspection system (1) including inspection devices (70-1 to 70-4) that inspect an object to be inspected, a management information acquisition unit (10f) that acquires management information for managing the software; a management information storage unit (10g) for storing the management information; a device information acquisition unit (10h) that acquires device information that is information about the device; a device information storage unit (10i) for storing the device information; an update software storage unit (10d) for storing update software used for updating the software; an update condition receiving unit (10b) that receives settings of update conditions that are conditions related to the software update; an update plan generation unit (10a) that generates an update plan for the software to be updated based on the management information including the management information of the software to be updated, the device information, and the update conditions; an update plan storage unit (10c) that stores the generated update plan; an update information providing unit (10e) that provides the update software and the update plan for the software to be updated by the update software; A software update support device (10) comprising: [Explanation of symbols]

[0177] 1: Inspection system 10a: Version upgrade plan generation section 10b: Version upgrade condition acquisition section 10c: Version upgrade plan memory section 10d: Version upgrade module storage section 10e: Version upgrade information transmission section 10f: Software management information acquisition unit 10g: Software management information storage unit 10h: Inspection system information acquisition section 10i: Inspection system information storage section 20: Management terminal 30: Management Server 40-1, 40-2: Line server 50-1, 50-2: Teaching terminal 60: Analysis terminal 70-1 to 70-4: Inspection equipment 80-1, 80-2: Visual terminal

Claims

1. A software update support device that supports updating of software executed in any device constituting an inspection system including an inspection device that inspects an object to be inspected, a management information acquisition unit that acquires management information for managing the software; a management information storage unit that stores the management information; an apparatus information acquisition unit that acquires apparatus information, which is information about the apparatus, including information about a system configuration of the inspection system; a device information storage unit that stores the device information; an update software storage unit that stores update software used to update the software; an update condition receiving unit that receives settings of update conditions that are conditions related to the software update; an update plan generation unit that generates an update plan for the software to be updated in the device on which the software to be updated is executed, based on the management information including the management information of software to be updated that is the target of update among the software, the device information, and the update conditions; an update plan storage unit that stores the generated update plan; an update information providing unit that provides the update software and the update plan for the software to be updated by the update software to the device on which the software to be updated is executed; A software update support device comprising:

2. 2. The software update support device according to claim 1, wherein the update condition is set based on a past operating state of the device on which the software to be updated is executed.

3. 2. The software update support device according to claim 1, wherein the update condition is set so that the timing for updating the software to be updated is when the software to be updated becomes available in the device on which the software to be updated is executed.

4. The software update support device according to claim 1, characterized in that the update condition is set so that the timing of updating the software to be updated is based on the state of other devices related to the device on which the software to be updated is executed.

5. 2. The software update support device according to claim 1, wherein the update condition is a date and time designated by a user as a timing for updating the software to be updated.

6. 2. The software update support device according to claim 1, wherein the update condition is set based on a production plan for the inspection object, the timing for updating the software to be updated.

7. An inspection system management device that manages the inspection system, a system-side device information storage unit that stores the device information; a system-side management information storage unit that stores the management information; an update software acquisition unit that acquires the update software; an update software storage unit that stores the update software; an update plan acquisition unit that acquires the update plan; an update plan storage unit that stores the update plan; an update software and update plan distribution unit that distributes the update software and the update plan to the device on which the software to be updated is executed; Equipped with 7. An inspection system management device, wherein the update software acquisition unit and the update plan acquisition unit acquire the update software and the update plan, respectively, from a software update support device according to claim 1.

8. The inspection system including the inspection system management device according to claim 7, The inspection system is characterized in that the device is equipped with an update control unit that updates the software to be updated using the update software distributed from the inspection system management device in accordance with the update plan distributed from the inspection system management device.

9. The software update support device according to any one of claims 1 to 6, The device constituting the inspection system; An inspection system comprising: The inspection system is characterized in that the device is equipped with an update control unit that updates the software to be updated using the update software provided from the software update support device in accordance with the update plan provided from the software update support device.

Images