JP3966276B2 - Information acquisition processing program, computer, and information acquisition processing system - Google Patents

Description

  The present invention relates to an information acquisition processing program for causing a computer to execute an information acquisition process in which the computer acquires device information updated on the device side from a device connected to the computer, and a computer that executes the information acquisition process And an information acquisition processing system comprising a computer that executes the information acquisition process and a device connected to the computer.

  2. Description of the Related Art Conventionally, a technique is known in which a computer acquires device information managed and updated on the device side from a device connected to the computer (see, for example, Patent Document 1 below).

  In the technology described in Patent Document 1 below, a computer acquires information (= device information) on the state of an image forming apparatus managed and updated in the image forming apparatus from the image forming apparatus connected to the computer. The acquired information is provided to the management computer via the network, and the management computer that receives this information comprehensively manages the information related to the image forming apparatus connected to the computer on the network. It is.

  There is also known a technique in which a computer acquires model identification information for identifying a model of the device from a device connected to the computer (for example, see Patent Document 2 below).

  In the technique described in Patent Document 2 below, a computer acquires model identification information for identifying a model of the image forming apparatus from an image forming apparatus connected to the computer, and the acquired model identification information and the like are networked. The server that has received the provision of the model identification information and the like through the server causes the computer to download an optimal device driver corresponding to the model of the image forming apparatus.

Note that the model identification information is invariant information determined for each model, and thus does not correspond to device information managed and updated on the device side.
JP 2000-293324 A Japanese Patent Laid-Open No. 2002-229751

  By the way, as a technique used in the technique as described in Patent Document 1, when the computer acquires information from the image forming apparatus, it is described in the printer job language (PJL) from the computer side to the image forming apparatus side. There is known a technique in which a received command (hereinafter also referred to as a PJL command) is given and information returned from the image forming apparatus side is read back on the computer side. PJL is a command language that enables various functions of an image forming apparatus to be controlled, and is a well-known language that was developed by Hewlett-Packard and later adopted by other companies.

  However, this PJL command has a wide variety of specifications that are uniquely expanded depending on the manufacturer and model of the image forming apparatus, and not all image forming apparatuses support the same type of PJL command. Absent.

  Therefore, in the technique described in Patent Document 1, when a PJL command is used, in order for the computer to acquire the desired information from the image forming apparatus, an appropriate PJL that can return the information to the image forming apparatus. Although there is a need to use a command, a technique for selecting an appropriate PJL command from among a large number of PJL commands is not disclosed in Patent Document 1.

  Moreover, although the point from which the computer acquires model identification information is disclosed in Patent Document 2, a technique for selecting an appropriate PJL command from among many PJL commands is also described in Patent Document 2. It has not been.

The present invention has been made to solve the above problems, along with providing the device by selecting the appropriate command, without processing of performing useless data transmission, to be able to computer running It is in .

The characteristic configuration employed in the present invention will be described below.
The information acquisition processing program of the present invention is
An information acquisition processing program for causing a computer to execute processing for acquiring device information, which is information about the device, from a device communicably connected to the computer,
An identification procedure for acquiring information indicating the model of the device from the device and identifying the model of the device;
Refer to command storage means in which a plurality of commands and information on one or a plurality of device models capable of responding to each command are stored in association with each other, and the device model identified in the identification procedure can respond A command selection procedure for selecting a command from the command storage means ;
An information request procedure for requesting the device to provide the device information by transmitting a command selected by the command selection procedure to the device;
An information acquisition procedure for acquiring the device information by receiving a response to the command transmitted by the information request procedure ;
When a plurality of commands are selected by the command selection procedure, the device information is requested by transmitting one command among the selected commands, and the command is obtained by the information acquisition procedure. On the condition that a response to the command is received, another command among the selected commands is transmitted to the device, while a response to the one command is not received by the information acquisition procedure. And an information request control procedure for controlling the information request procedure so as not to transmit the other command .

  When the computer executes each of the above procedures according to this information acquisition processing program, the computer acquires information indicating the device model from the device, identifies the device model, and a command associated with the identified model. Is selected from a plurality of commands. Therefore, even if a command corresponding to a certain device and a command not corresponding to a certain device are mixed in a plurality of commands, only the command corresponding to that device is selected. As a result, the command transmitted to the device is only the command corresponding to the device, and the desired device information can be acquired by receiving a response to the transmitted command.

Thus, the transmitted command can retrieve the desired device information. Further, unlike the case where the computer transmits a command not corresponding to the device, the computer does not need to perform useless data transmission processing. Furthermore, unlike the case where the computer receives a response to the command after transmitting a command not corresponding to the device, the computer does not need to perform useless data reception processing.

Note that the information acquisition processing program described above preferably has the following characteristics.
First, the computer includes a plurality of local ports that can be locally connected to the device.
A local port extraction procedure for extracting a local port to which the device is connected from the plurality of local ports;
Processing is performed so that the device connected to the local port extracted by the local port extraction procedure becomes a processing target of the identification procedure, the command selection procedure, the information request procedure, the information acquisition procedure, and the information request control procedure Process thread creation procedure to create a thread and
It is good to include.
And an additional device detection procedure for detecting that the device is newly connected to the local port,
The local port extraction procedure is a procedure for further extracting a local port to which the device newly detected by the additional device detection procedure is connected,
The processing thread creation means may be a procedure for creating the processing thread even for the newly detected device.
An end detection procedure for detecting whether one job that can be processed by the device has ended,
A job number counting procedure for counting the number of jobs input to the device in addition to the one job when the end detection procedure detects that the processing of the one job is completed,
In the identification procedure, information indicating the model of the device is acquired from the device on the condition that the number of jobs counted in the procedure for counting the number of jobs is equal to or less than a predetermined number, and the model of the device is identified. The procedure should be
If the computer executes each of the above procedures according to such an information acquisition processing program, the number of jobs is a predetermined number compared to counting the number of jobs regardless of whether or not one job that can be processed by the device is completed. It becomes difficult to miss the following timing, and the opportunity to acquire information from the device increases.
The identification procedure may be a procedure for acquiring information indicating the model of the device from the device every predetermined period and identifying the model of the device.
If the computer executes each of the above procedures according to such an information acquisition processing program, information indicating the device model can be acquired from the device every predetermined period even in an environment where the number of jobs does not become a predetermined number or less.
The command may include information for specifying the device information.

If it is an information acquisition processing program having a procedure for transmitting such a command, even if the device to which the command is transmitted is a device that can return a plurality of types of device information, a plurality of types of device information By specifying one of them, only the desired device information can be acquired . Therefore, after the computer acquires all the plural types of device information from the device, it is not necessary to perform a useless process such as selecting necessary device information and unnecessary device information from the device information.

In addition, the device information may include information related to the degree of use of replacement parts of the device.
If it is an information acquisition processing program having a procedure for acquiring such device information, information on the degree of use of the replacement parts of the device can be acquired, so that the user can determine the necessity of maintenance by referring to it. .

The device information may include information on the degree of consumption of the consumables of the device.
If it is an information acquisition processing program having a procedure for acquiring such device information, information on the degree of consumption of the consumables of the device can be acquired, and this is also referred to by the user to determine the necessity of maintenance. Can do.

The device information may include information related to the number of occurrences of abnormality in the device.
If it is an information acquisition processing program with a procedure for acquiring device information like this, it is possible to acquire information on the number of occurrences of abnormalities in the device. Sexual judgment can be made.

The information acquisition processing program of the present invention is
Information indicating the model of the device acquired in the identification procedure, information indicating an input / output I / F used for connection between the computer and the device, and the device information acquired in the information acquisition procedure The device stores association information stored procedure
It is good to include .

If the computer in accordance with the information acquisition processing program to execute the above steps, the computer, information indicating the information indicating the model of the device, the input and output I / F used in the connection between the computer and the device, the device information Are stored in association with each other. Therefore, when the user refers to the stored device information, the user can also refer to information indicating the device model associated with the device information and information indicating the input / output I / F.

  Therefore, even when there are multiple devices of the same model among multiple devices connected to a single computer, if a user wants to know which device information is obtained from which device, the user must One device can be easily specified based on the information indicating the model and the information indicating the input / output I / F.

In the identification procedure, when access to the device is not possible, information indicating that the access was not possible and input / output I / F used for connection between the computer and the device are indicated. An access error information storing procedure for storing information in association with each other may be included.

  In this case, the user can know that the device could not be accessed by referring to the stored information, particularly when a plurality of devices connected to one computer are connected. Even in such a case, the user can easily identify which input / output I / F the device connected to could not be accessed based on the information indicating the input / output I / F.

  In the information request procedure, when a command cannot be transmitted to the device, information indicating that the command could not be transmitted, information indicating the model of the device acquired in the identification procedure, and the computer A transmission error information storing procedure for storing information indicating the input / output I / F used for connection with the device in association with each other may be included.

  In this case, the user can know that the command could not be transmitted to the device by referring to the stored information, and in particular, the same model among a plurality of devices connected to one computer. Even if there are multiple devices, the user can send a command to any device connected to any input / output I / F based on the information indicating the device model and the information indicating the input / output I / F. It can be easily identified whether there was no.

  In the information acquisition procedure, when a response from the device cannot be received, information indicating that the device could not be received, information indicating the model of the device acquired in the identification procedure, and the computer A reception error information storing procedure for storing information indicating the input / output I / F used for connection with the device in association with each other may be included.

  In this case, the user can know that the response from the device could not be received by referring to the stored information, and in particular, the same model among a plurality of devices connected to one computer. Even when there are multiple devices, the user can receive a response from the device connected to any input / output I / F based on the information indicating the device model and the information indicating the input / output I / F. It can be easily identified whether there was no.

Next, the computer of the present invention
Devices and which is communicably connected to a computer that executes a process of acquiring the device information from the previous SL device,
Information indicating the model of the device is obtained from the device, and identification means for identifying the model of the device;
Command storage means for storing a plurality of commands and information of one or a plurality of device types capable of responding to each command in association with each other;
Command selection means for referring to the command storage means and selecting from the command storage means a command to which the model of the device identified by the identification means can respond ;
Information request means for requesting the device to provide the device information by transmitting a command selected by the command selection means to the device;
An information acquisition means for acquiring the device information by receiving a response to the command transmitted by the information request means ;
When a plurality of commands are selected by the command selection means, the device information is requested to be provided by transmitting one command among the selected commands, and the information acquisition means requests the one command. On the condition that a response to the command is received, another command among the selected commands is transmitted to the device, while a response to the one command is not received by the information acquisition unit. And an information request control means for controlling the information request means so as not to transmit the other command .

  In this computer, the identification unit obtains information indicating the model of the device from the device, identifies the model of the device, and the command selection unit selects a command associated with the model identified by the identification unit, Select from multiple commands. Therefore, even if a command corresponding to a certain device and a command not corresponding to a certain device are mixed in a plurality of commands, only the command corresponding to that device is selected. As a result, the command sent to the device by the information requesting unit is only the command corresponding to the device, and the information obtaining unit can obtain the desired device information by receiving a response to the transmitted command. it can.

Thus, the transmitted command can retrieve the desired device information. Further, unlike the case where the computer transmits a command not corresponding to the device, the computer does not need to perform useless data transmission processing. Furthermore, unlike the case where the computer receives a response to the command after transmitting a command not corresponding to the device, the computer does not need to perform useless data reception processing.

Furthermore, the information acquisition processing system of the present invention includes:
A computer and a device connected to the computer, wherein the device stores device information that is information about the device, and updates that update the device information on the device side as the device operates A system configured to execute a process of acquiring the device information from the device, the computer comprising:
The computer
Information indicating the model of the device is obtained from the device, and identification means for identifying the model of the device;
Command storage means for storing a plurality of commands and information of one or a plurality of device types capable of responding to each command in association with each other;
Command selection means for referring to the command storage means and selecting from the command storage means a command to which the model of the device identified by the identification means can respond ;
Information request means for requesting the device to provide the device information by transmitting a command selected by the command selection means to the device;
An information acquisition means for acquiring the device information by receiving a response to the command transmitted by the information request means ;
When a plurality of commands are selected by the command selection means, the device information is requested to be provided by transmitting one command among the selected commands, and the information acquisition means requests the one command. On the condition that a response to the command is received, another command among the selected commands is transmitted to the device, while a response to the one command is not received by the information acquisition unit. And an information request control means for controlling the information request means so as not to transmit the other command .

  In this information acquisition processing system, the computer includes the above-described units. Among these units, the identification unit acquires information indicating the model of the device from the device, identifies the model of the device, and executes a command. The selecting means selects a command associated with the model identified by the identifying means from a plurality of commands. Therefore, even if a command corresponding to a certain device and a command not corresponding to a certain device are mixed in a plurality of commands, only the command corresponding to that device is selected. As a result, the command sent to the device by the information requesting unit is only the command corresponding to the device, and the information obtaining unit can obtain the desired device information by receiving a response to the transmitted command. it can.

Thus, the transmitted command can retrieve the desired device information. Further, unlike the case where the computer transmits a command not corresponding to the device, the computer does not need to perform useless data transmission processing. Furthermore, unlike the case where the computer receives a response to the command after transmitting a command not corresponding to the device, the computer does not need to perform useless data reception processing.

As described above, according to the present invention, along with providing the device by selecting the appropriate command, without processing of performing useless data transmission, it is possible to make a computer can execute.

Next, an embodiment of the present invention will be described with an example.
FIG. 1 is a block diagram showing a network system in which a plurality of personal computers are connected to each other via a LAN (Local Area Network).

  The information acquisition processing system exemplified as an embodiment of the present invention is a device configured as a system that operates on personal computers 1, 1 ′, 1 ″... And connected to the personal computers 1, 1 ′, 1 ″. ... from the printers 3, 3 ', 3 "... to obtain printer information (device information in the present invention) managed and updated in each 3, 3', 3" ....

  In the present embodiment, the personal computers 1, 1 ′, 1 ″... Send printer information acquired from the printers 3, 3 ′, 3 ″, etc. to the personal computer 2 in response to a request from the personal computer 2. To provide. The personal computer 2 acquires printer information provided from the personal computers 1, 1 ′, 1 ″, and the printers 3, 3 ′,... Connected to the personal computers 1, 1 ′, 1 ″,. 3 "... Printer information is managed.

  In the following description, the personal computer 2 that manages printer information is referred to as a management PC 2, and personal computers 1, 1 ', 1 ",... Managed by the management PC 2 are referred to as managed PCs 1, 1', 1",.

  As shown in FIG. 2, the managed PC 1 includes a control unit 101 mainly composed of a CPU 111, a ROM 112, a RAM 113, and the like, and an I / F unit 102 for connecting the control unit 101 and various devices. A main body unit 11, an input unit 12 such as a keyboard and a pointing device, a display unit 13 such as a display, and an auxiliary storage unit 14 such as a hard disk.

  Windows (registered trademark) is installed in the main body 11 as an OS (Operating System), and functions commonly used by applications such as a printer I / F function unit 121, a LAN I / F function unit 122, and a print spooler 123. Is composed of software modules implemented as part of the OS. In addition, the OS also provides input / output functions such as keyboard input and screen output, and functions such as hard disk and memory management. As long as an equivalent function can be realized, the managed PC 1 may be mounted with another OS (for example, Linux (registered trademark), MacOS (registered trademark), etc.), but in the following description, The description will be continued on the assumption that the managed PC 1 has various functions provided by Windows (registered trademark).

  The I / F unit 102 of the main unit 11 includes a LAN I / F 114 such as a LAN card, USB (Universal Serial Bus), in addition to the I / F with the input unit 12, the display unit 13, and the auxiliary storage unit 14 described above. A printer I / F 115 such as a port or a parallel port is provided. The managed PC 1 is connected to the LAN via a LAN cable connected to the LAN I / F 114, and is connected via a printer cable connected to the printer I / F 115. The management PC 1 and the printer 3 are connected.

  The managed PC 1 is installed with software for realizing a function of acquiring printer information from the printer 3 connected to the managed PC 1 and providing the printer information to the management PC 2. This software is installed on the CPU 111. Is configured to function as the printer information acquisition unit 124.

The managed PCs 1 ′, 1 ″,... Are configured in the same manner as the managed PC 1 and have the same functions as the managed PC 1. Therefore, detailed description thereof is omitted.
The management PC 2 is basically configured in the same manner as the managed PC 1 and includes a main body unit 21, an input unit 22, a display unit 23, an auxiliary storage unit 24, and the like. The main body unit 21 includes Windows as an OS. (Registered trademark) is installed. As long as the management PC 2 can realize an equivalent function, another OS (for example, Linux (registered trademark), MacOS (registered trademark), etc.) may be mounted. However, in the following description, the management PC 2 The description will be continued on the assumption that various functions provided by Windows (registered trademark) are provided.

  This management PC 2 requests the computers on the network such as the managed PCs 1, 1 ′, 1 ″... To provide information regarding the printers 3, 3 ′, 3 ″. In response to the request, software for realizing a function of collectively managing printer information provided from other computers is installed.

  The printers 3, 3 ', 3 "... are managed printers to be managed by the management PC 2. These printers 3, 3', 3" ... are all compatible with a printer job language (PJL). It is a thing.

  Further, the printers 3, 3 ′, 3 ″,... Can return the IEEE1284 device ID (hereinafter referred to as 1284ID) to the managed PCs 1, 1 ′, 1 ″,... Via the printer I / F 115. . The 1284 ID is defined by the IEEE1284 standard when the I / F is parallel, and is known by the USB printer class specification when the I / F is USB.

  Next, processing of the printer information acquisition unit 124 executed in the managed PC 1 will be described based on the flowchart of FIG. This process is started when the managed PC 1 is activated. This process is executed in the same way on the managed PCs 1 ′, 1 ″..., But the description will be continued here taking the process executed on the managed PC 1 as an example.

  When this process is started, the managed PC 1 first creates a list of local ports to which the printer is connected (S101). In this process, all local ports corresponding to all printers connected to the managed PC 1 (in this embodiment, the printer 3) are registered in the list. Subsequently, one local port is extracted from the list created in S101 (S103), and a processing thread corresponding to the extracted local port is created (S105). The processes in S103 and S105 are repeated a number of times corresponding to the total number of local ports registered in the list (S107: NO). As a result, in addition to this processing, processing in the same number of processing threads as the total number of local ports is executed in parallel. In the newly created processing thread, the printer information (for example, information on the degree of use of replacement parts, such as drum replacement time, toner or ink remaining amount, etc., from the printer connected via the target local port of each processing thread) Acquire information on the consumption level of consumables, such as the remaining amount of recording paper, information on the number of occurrences of abnormalities, such as the number of paper jams, and various other information managed and updated on the printer 3 side. The process of recording in the result file 133 in the auxiliary storage unit 14 is abbreviated, and the details of the process will be described later.

  When the same number of processing threads as the total number of local ports are created (S107: YES), the setting time is read from the setting file 134, the time until the setting time is calculated (S109), and calculated in the processing of S109. The time is set in the timer (S111). The setting file 134 is a file stored in the auxiliary storage unit 14, and the setting time arbitrarily set by the administrator is recorded in the setting file 134. This timer generates a timer event when the time calculated in the process of S109 elapses after the process of S111.

  Subsequently, the managed PC 1 waits for the occurrence of a related event (S113). If the generated event is a printer addition event (S115: YES), the local port is added to the list (S117), and the added local A processing thread corresponding to the port is created (S119). The printer addition event is an event that occurs when, for example, a known plug-and-play function is used to detect whether the printer is turned on or a cable is inserted. The occurrence of this printer addition event indicates that a newly available printer has been added and the local port to which the printer is connected. Therefore, by updating the list by the processing of S117 and S119 and creating a processing thread corresponding to the local port added to the list, a processing thread that performs processing equivalent to the processing thread created in the processing of S105 is created. to add. When the process of S119 is completed, the process returns to S113.

  On the other hand, if the event that has occurred is not a printer addition event as a result of the determination in S115 (S115: NO), if the event that has occurred is a timer event (S121: YES), read / DB processing 2 is executed. (S123). The timer event generated here is due to the processing of S109 and S111 described above. In the reading / DB conversion process 2 in S123, a process of acquiring the status from all the printers connected to the managed PC 1 and recording it in the database (DB) is performed. Details of the process will be described later. Then, the timer is set to 24 hours (S125), and after 24 hours, a timer event occurs again, and the process returns to S113.

  As a result of the determination in S121, if the event that has occurred is not a timer event (S121: NO), the process ends if the event that has occurred is an end instruction event (S127: YES). The end instruction event is an event that occurs when the user performs a predetermined end operation using the input unit 12. On the other hand, if it is not an end instruction event (S127: NO), the process returns to the process of S113 and again waits for the occurrence of a related event. That is, when the managed PC 1 is in an operating state, this process does not end unless the user performs an end operation, and this process continues to be executed as a resident process on the managed PC 1.

  Next, processing of processing threads (hereinafter referred to as thread processing) created in the processes of S105 and S119 will be described with reference to the flowchart of FIG. As described above, this thread process is executed in parallel with the same number as the total number of local ports to which the printer is connected, and each of these thread processes is a thread process corresponding to one local port.

  When this thread process is started, the managed PC 1 waits for the occurrence of a printer-related event (S201). If the generated event is a print end event (S203: YES), the printer corresponding to this thread process is set as the output destination. The print jobs to be listed are listed (S205). Specifically, the printer information acquisition unit 124 acquires information from the print spooler 123 (see FIG. 2), and information (print job information) related to the print job that is queued at the time of the processing of S205 is listed. The The queue 131 is an aggregate in which print jobs requested for one printer are stored in the auxiliary storage unit 14 (or RAM 113) and are managed in order by the OS. Then, the number of jobs is counted with reference to the listed print job information (S207), and it is checked whether the number of jobs is equal to or less than a set value N (S209).

  In the present embodiment, the setting value N = 0, and it is checked whether the number of jobs is 0 in the processing of S209. The specific procedure for checking whether or not the number of jobs is 0 is most basically just to check whether or not the number of print job information listed in S205 is zero. However, in the case of this embodiment, the print job information listed in the process of S205 includes an item called job status. When transmission of output data is completed in one print job, the job status is first set to “Sent. Is set, and then the print job information itself is erased at a predetermined timing managed on the OS side. Therefore, even if there is only one print job information listed in the process of S205, if the information “sent” is set in the job status in the print job information, the corresponding job already exists. It can be regarded as not. Therefore, in the processing of S209 in this embodiment, not only when the number of listed print job information is 0, but also when the number of print job information is 1, the job status in the print job information is “Send”. If it is “completed”, it is determined that the number of jobs is zero.

  If the number of jobs is equal to or less than the set value N in the process of S209 (S209: YES), the managed PC 1 executes a model determination / DB write process (S211). The model determination / DB writing process in S211 is the process shown in detail in the flowchart of FIG.

  When the model determination / DB writing process is started, the managed PC 1 first obtains the 1284 ID described above from the target printer (S231). In the process of S231, if the target printer supports a device ID, 1284 ID can be acquired from the printer. On the other hand, in the case of a printer that does not conform to the IEEE1284 standard or a printer that conforms to the IEEE1284 standard but does not support the device ID, the 1284ID cannot be acquired from the printer.

  Therefore, the managed PC 1 checks whether or not the acquisition of 1284 ID has failed (S233), and if it has not failed (S233: NO), it checks whether or not it is a non-target printer (S235). The managed PC 1 has a list in which 1284 IDs are registered for all printer models that are assumed to be managed by this system. If the acquired 1284 ID is registered in the list, the managed PC 1 is determined to be a target printer. If the acquired 1284 ID is not registered in the list, it is determined that the printer is a non-target printer.

  In the process of S235, if it is the target printer (S235: NO), the reading / DB conversion process 1 is executed (S237). The reading / DB conversion processing 1 in S237 is the processing shown in detail in the flowchart of FIG.

  When the reading / DB conversion processing 1 is started, the managed PC 1 first opens the target printer (S301). At this time, a UEL command is sent to the target printer via the print spooler 123. With this process, the target printer can process the PJL command. The managed PC 1 executes command extraction processing from the command file 132 (S305). The command extraction process in S305 is the process shown in detail in the flowchart of FIG.

  When the command retrieval process is started, the managed PC 1 first selects the next row of the table (S331). The table to be read in the processing of S331 is a table stored in the command file 132. The command file 132 stores a table in a data format as shown in FIG. 8, and one line of this table is composed of a model item, a command item, a key item, and a label item.

  The model item is an area for storing information on a model (hereinafter referred to as a supported model) that can return a response to the PJL command for the PJL command generated from the character string stored in the command item and the key item in the same line. It is. More specifically, in the model item, information on the corresponding model is stored by a combination of “*”, “¥”, “−”, and “character string indicating the model name”. Among these, “*” represents all models, “¥” is used as a delimiter used when enumerating a plurality of “character strings indicating model names”, and “-” is a subsequent “character indicating model name” "Column" indicates that the model is excluded from the corresponding models listed before. For example, “Device1 ¥ Device2” on the first line of the table shown in FIG. 8 indicates that the model “Device1” and the model “Device2” are compatible models. Further, “* -Device1 ¥ Device2” in the second row of the table shown in FIG. 5 indicates that a model obtained by excluding the model “Device1” and the model “Device2” from all models is a compatible model. Furthermore, “*” in the third and fourth rows of the table shown in FIG. 4 indicates that all models are compatible models. The “character string indicating the model name” not following “*” and “−” corresponds to the respondable model information referred to in the present invention, and the “character string indicating the model name” following “-” is This corresponds to the unresponsive model information in the present invention.

  The command term and key term are areas for storing character strings used to generate a PJL command. When the PJL command is generated, the PJL command is generated in the format of “@PJL“ character string of command item ”“ character string of key item ”, for example, the first line of the table shown in FIG. If a PJL command is to be generated from data in the PJL command, a PJL command “@PJL INFO PAGES” is generated.

  The label term is an area for storing a character string representing the content of the printer information acquired by the PJL command for the PJL command generated from the character string stored in the command term and the key term in the same line. Note that the character string stored in the label item is used in the processing of S353 to S355 described later.

  Note that the data format table shown in FIG. 8 is often stored as a file having a highly versatile data structure such as CSV (Comma Separated Values) format, but substantially equivalent data is read and written. If possible, the physical structure and logical structure of the file storing the data are arbitrary.

  In the processing of S331, if no data has been read from the table, the first row of the table is selected as the next row, and if data has already been read up to the nth row of the table, If the (n + 1) th row is selected as the next row and data has already been read up to the last row of the table, it means that all rows have been completed.

  If it is not the end of all lines (S333: NO), the model item is read from the table for the selected one line (S335). Then, the character string stored in the model item is analyzed, and it is checked whether or not the model indicated by 1284ID previously acquired in the process of S231 is included (S337). For example, when the first row of the table shown in FIG. 8 is targeted, since the character string “Device1 ¥ Device2” is read in the process of S335, the model indicated by the previously acquired 1284ID is “Device1” or “Device2”. If "," in the process of S337, it is determined that the model indicated by 1284ID is included.

  In the process of S337, when the model indicated by 1284ID is included (S337: YES), the command (= character string stored in the command item) and data (characters stored in the key item) are sequentially applied to the selected one line. Column) is read (S339), and a transmission character string is generated (S341). For example, when the first row of the table shown in FIG. 8 is targeted, the character string “INFO” and the character string “PAGES” are read out in the process of S339, and the transmission “@PJL INFO PAGES” is executed in the process of S341. A character string (PJL command) is generated.

  In the process of S337, when the model indicated by 1284ID is not included (S337: NO), the process returns to S331, and the processes of S331 to S337 are repeated again. If it is determined that the model indicated by 1284ID is included in the process of S337 that is executed several times during this repetition process (S337: YES), the processes of S339 and S341 are executed.

  Then, when the processes of S339 and S341 are executed, or when the process of S331 to S337 is repeated several times, and all the lines are completed in the process of S333 (S333: YES), this process is performed. finish.

  When the processing of S331 to S341 is completed in this way, the processing of S303 shown in FIG. 6 is completed, and then the managed PC 1 checks whether all commands are completed (S305). Here, it is determined that the end of all commands is the end of all lines (S333: YES) in the processing of S333. In other cases, the transmission character string (S339 and S341) is processed. PJL command) is generated.

  Therefore, if not all commands are completed (S305: NO), the generated transmission character string (PJL command) is transmitted to the printer (S307). The data transmitted in the process of S307 is transferred to the print spooler 123 by the printer information acquisition unit 124, is put in the queue 131 as one print job, and is then processed in the same manner as a normal print job. 123 is passed to the printer I / F function unit 121 (see FIG. 2) and output to the printer side.

  Subsequently, it is checked whether or not the transmission is successful (S309). If the transmission is successful (S309: YES), information (printer information) transmitted from the target printer is received (S311). The process of S311 is a process of reading back the printer information returned from the printer side on the managed PC 1 side, but a more specific processing method differs depending on the target printer. For example, when the target printer is connected via a parallel I / F, the printer information acquisition unit 124 first checks whether there is information returned to the managed PC 1 side through the printer I / F function unit 121 of the OS. Thereafter, when the information exists, the information is received. If the target printer is connected via the USB I / F, the printer information acquisition unit 124 first receives information through the printer I / F function unit 121 of the OS, and the amount of information is 0. In such a case, the information reception is repeated again.

  However, in any case, after reception, it is checked whether or not the reception is successful (S313). If the reception is successful (S313: YES), some data is received, so that data is valid data. If the data is not valid data (S315: NO), the processing after S311 is performed again. If the data is valid data (S315: YES), DB (result file) writing processing is executed. (S317). The DB (result file) writing process in S317 is the process shown in detail in the flowchart of FIG.

  When the DB (result file) writing process is started, the managed PC 1 first analyzes the readback data and divides the key and the value (S351). The S351 process will be described with a specific example. For example, when a transmission character string “@PJL INFO PAGE COUNT”, which is a PJL command, is generated and transmitted to the printer based on the second line of the table shown in FIG. As the read back data, for example, the character string “@PJL INFO PAGE COUNT <CR> PAGE COUNT = 2209 <CR> <FF>” is received. In this received character string, the first half is the transmitted PJL command itself, “<CR>” after that is a line feed code, “PAGECOUNT =” is a character string added according to the PJL command, and “2098” is the device. The value managed in (in this case, the number of printed sheets), the “<CR>” after that is a line feed code, and the “<FF>” after that is a page break code. In the process of S351, this received character string is analyzed, and a process of extracting “KEY COUNT” as a key and “2098” as a value from the received character string is performed.

  Subsequently, the managed PC 1 reads the label corresponding to the key obtained by the process of S351 from the command file 132 (S353). Since the command file 132 stores a table in a data format as shown in FIG. 8 as described above, a character string serving as a label is read from the label section of this table.

  Then, a comma-delimited character string having a format of “model, port, label, value <CR>” is created (S355). In the character string created in the process of S355, “model” is a character string (for example, “Device1”) representing the model name corresponding to the 1284 ID acquired in the process of S231 described above, and “port” is A character string (for example, this process is called in a thread created for each local port, and only a specific local port is the target of processing) “LPT1”) and “label” are character strings read out in the process of S353 (for example, “Pages”), and “value” is a character string indicating the value extracted in the process of S351 (for example, “2098”). ). A character string formed by separating these character strings with a comma and adding a carriage return code <CR> at the end is created by the process of S355.

After that, the character string created by the process of S355 is written to the DB (result file 133) (S357), and this process ends.
When the processing of S351 to S357 is finished in this way, the processing of S317 shown in FIG. 6 is finished. By the process of S317, response information corresponding to the request for one command requested to the target printer by the process of S307 is recorded in the DB (result file 133) secured in the auxiliary storage unit 14. become.

  The processes in S303 to S317 are repeatedly executed until the end of all commands unless an error occurs in the middle (S305: NO). In this repetitive process, in the process of S303, a plurality of commands recorded in the command file 132 are extracted in order. When all the commands are processed (sent to the printer), all commands are completed (S305: YES). As a result, response information corresponding to requests for all commands requested to the target printer is recorded in the DB (result file 133) secured in the auxiliary storage unit 14. Thereafter, the target printer is closed (S319), and this process is finished.

An error may occur during the processing of S303 to S317.
Specifically, first, it may be determined that transmission has failed in the process of S309 (S309: NO). In this case, the managed PC 1 acquires the printer status (S321), writes the printer status in the DB (result file 133) (S323), closes the target printer (S319), and ends this processing. In the process of S323, a comma-delimited character string having the format “model, port, error cause, <CR>” is created, and this character string is written to the DB (result file 133). In this character string, “model” and “port” are the same as the character string used in the process of S355, and “cause of error” is a character string that can change depending on the status acquired in the process of S321. However, for example, if the PJL command cannot be accepted due to running out of paper, a character string “PE error” or the like is used because a status indicating running out of paper is obtained in the process of S321.

  Moreover, it may be determined that the reception has failed in the process of S313 (S313: NO). In this case, the managed PC 1 writes error information indicating reception failure in the DB (result file 133) (S325). Also in the process of S325, a comma-delimited character string having the format “model, port, error cause, <CR>” is created, and this character string is written to the DB (result file 133). In this character string, “model” and “port” are the same as the character strings used in the processing of S355 or S323. “Error cause” indicates that there is no response from the printer. For example, a character string “NotResponse” is used. Then, the target printer is closed (S319), and this process is finished. When closing the target printer, UEL is sent to the printer prior to closing, and the PJL command mode is canceled.

When the processing of S301 to S319 is completed as described above, the processing of S237 (reading / DB conversion processing 1) shown in FIG. 5 is finished (in this case, normal termination).
An error may occur in the process of S233 or S235.

  Specifically, first, in the process of S233, acquisition of 1284ID may fail (S233: YES). In this case, by returning to the processing of S231 up to 10 times (S241: NO), reacquisition of 1284ID is attempted. If the acquisition of 1284 ID fails (S241: YES) despite returning to the processing of S234 10 times, the managed PC 1 displays a power / cable confirmation message on the display unit 13 (S243).

  Here, the user can use the input unit 12 to perform an operation to input any instruction of OK / Cancel. If the user confirms the printer power supply or cable, and as a result, the cause of the error can be resolved, and the user wishes to continue this process, the user may input an OK instruction. If the user thinks that this process may be interrupted, the user may input a cancel instruction.

  When an OK instruction is input (S245: YES), the process returns to the process of S231, and the managed PC 1 restarts this process from the beginning. On the other hand, when the Cancel instruction is input (S245: NO), the managed PC 1 writes in the DB (result file 133) that the printer is not ready (S247) and ends this process (in this case, Error Exit). In the process of S247, a comma-delimited character string having the format “, port, error cause, <CR>” is created, and this character string is written to the DB (result file 133). In this character string, “port” is the same as the character string used in the processing of S355, S323, and S325. “Error cause” indicates that an appropriate 1284 ID has not been acquired. A character string “1284ID error”, etc. is used, and unlike the processes of S355, S323, and S325, an appropriate 1284ID has not been acquired, so “model name” may be included in the character string to be created. Since this is not possible, the part corresponding to “model name” is blank.

In the process of S235, if the printer is a non-target printer (S235: YES), the managed PC 1 displays a model confirmation message on the display unit 13 (S249).
Here, the user can use the input unit 12 to perform an operation to input any instruction of OK / Cancel. If the user confirms the model and, as a result, wishes to continue this process, the user may input an OK instruction. If the user thinks that this process may be interrupted, the user may input a cancel instruction.

  Thereafter, the process proceeds to the process of S245 described above, and if an OK instruction is input (S245: YES), the process returns to the process of S231, and the managed PC 1 restarts the process from the beginning. On the other hand, when the Cancel instruction is input (S245: NO), the managed PC 1 writes in the DB (result file 133) that the printer is not ready (S247) and ends this process (in this case, Error Exit). Note that the processes of S245 to S247 may be different in these two cases when the process of S243 is finished and when the process of S249 is finished. In which case, which was the case? It is possible to leave error information that can be understood. Further, in the process of S247, after determining which of the above two cases was made, it is possible to leave error information so as to know which case it was.

  When the processes of S231 to S247 are completed as described above, the process of S211 shown in FIG. 4 is completed. Thereafter, when the process of S211 is normally completed (S213: YES), the process of S201 is completed. On the other hand, if the process of S211 ends with an error while returning to the process, the present thread process ends. Also, when the number of jobs counted in the process of S207 exceeds the set value N (S209: NO), the process returns to the process of S201 as it is. Furthermore, if it is determined in the process of S203 that the event is not a print end event (S203: NO), the process directly returns to the process of S201.

  Therefore, the thread processing described above starts when a processing thread is created when there is a local port to which the printer is connected, and continues thereafter unless an error occurs. It will be. During this process, the number of print jobs is checked each time a print end event occurs. If the number of print jobs is equal to or less than the set value N, printer information is acquired from the printer connected via the local port. The printer information is written in a DB (result file 133) secured in the auxiliary storage unit 14. The error information is also written in the DB (result file 133) in a record format compatible with the case of writing printer information (in this embodiment, a comma-separated format (CSV format) with four items per line). As a result, a data group as illustrated in FIG. 10 is stored in the DB (result file 133).

Incidentally, by examining the number of print jobs whenever a print end event as described above process occurs, compared to determine the number of independent print job generation and printing end event, it the number of print jobs is equal to or smaller than a set value N This makes it difficult to overlook the timing of printing and increases the opportunity to acquire printer information from the target printer. In the present embodiment, since the set value N = 0, only when the number of print jobs becomes 0, the printer information is acquired from the target printer by the process of S211. For this reason, it takes no time to acquire printer information from the target printer because a print job that takes time to complete the printing process is queued first.

  By the way, the information recording to the DB (result file 133) by the thread processing is performed only when the number of print jobs becomes 0 as described above. Therefore, theoretically, print jobs are generated continuously. In such an environment, the number of print jobs does not easily become zero, and as a result, it may happen that information is not recorded in the DB (result file 133) only by the thread processing. However, in this system, in addition to this thread processing, the processing of S109 to S111 and S121 to S125 is also executed, so that when the preset installation time is reached, the DB (result file 133) Information recording is to be implemented.

  More specifically, as described above, in the present system, a timer event is generated when the set time arrives by the processes of S109 and S111. If a timer event occurs, the process of S123 ( Reading / DB conversion processing 2) is executed. More specifically, the process of S123 is as shown in the flowchart of FIG.

  When the reading / DB conversion processing 2 is started, the managed PC 1 first extracts one local port from the list (S401), counts print jobs that have the extracted local port as an output destination (S403), and the number of jobs. Whether or not is 0 is checked (S405). The processes of S403 and S405 may be performed by a method equivalent to the processes of S207 and S209 described above.

  If the number of jobs is not 0 as a result of the determination in S405 (S405: NO), the model determination / DB writing process is executed (S407), and then the process proceeds to S409, while the number of jobs is 0. If it is (S405: YES), the process proceeds to S409 without executing the model determination / DB writing process of S407.

  The model determination / DB writing process in S407 is the same as the process in S211 described above (specifically, the process shown in FIGS. 5 and 6), and thus detailed description thereof is omitted here. Similar to the above process, a process of acquiring printer information from the target printer and writing the printer information in a DB (result file 133) secured in the auxiliary storage unit 14 is executed. As described above, when the number of jobs is not 0, the model determination / DB writing process is executed because information is recorded in the DB (result file 133) by this process even in an environment where the number of print jobs is not 0. Because. On the other hand, when the number of jobs is 0, the model determination / DB writing process is not executed because the information recording by the thread processing described above should be performed when the number of jobs becomes 0. This is because it is considered that there is no change in the state of the target printer thereafter.

  Since the model determination / DB writing process is executed in a state where there is a print job, when a PJL command is transmitted, the print job generated along with the print job is the print that was previously in the queue 131. Appended to the end of the job. Therefore, the subsequent readback data is not returned until all the print jobs previously accumulated in the queue 131 are completed.

  If the process for all local ports on the list is not completed when the process proceeds to S409 (S409: NO), the process returns to S401. As a result, the processing of S401 to S409 is repeated the same number of times as the total number of local ports to which the printer is connected in the managed PC 1, and then the processing for all the local ports on the list is completed (S409: YES). This process is terminated.

As described above, in the managed PC 1, when the print end event occurs, if the number of print jobs is equal to or less than N (0 in the present embodiment), the process of S211 is executed, and the target printer quickly one printer information is acquired, each time the set time arrives, without becoming the number of print jobs is N or less (0 in this embodiment), the process of S407 is executed, the target printer or Lapu printer Information is acquired.

Next, processing executed in the management PC 2 will be described based on the flowchart of FIG. This process is started when the management PC 2 is activated.
When this processing is started, the management PC 2 first executes data processing (S601). This data processing is processing for using on the management PC 2 side the printer information acquired by the managed PC 1 from the printer 3 and recorded in the DB by the processing in the managed PC 1 described above. It becomes processing as shown in.

  In this process, first, the management PC 2 extracts managed PCs (S701). In the process of S701, one managed PC to be processed is extracted from the plurality of managed PCs 1, 1 ′, 1 ″... Here, it is assumed that the managed PC 1 has been extracted. Subsequently, the management PC 2 reads a file from the managed PC over the network (S703), and the file read here is received from the printer in the process of S313 by the managed PC 1 described above. This file is a DB (result file 133) in which the printer information is written, and this file has an attribute that allows reading from other PCs over the network on the managed PC 1 side. When there is a request from the management PC 2, the printer information read from the DB of the auxiliary storage unit 14 is provided to the management PC 2. It is configured to be able.

  Subsequently, information to be managed on the management PC 2 side (for example, log information such as the start time of this process and the file access time) is added to the printer information included in the read file. / Data processing for supplementing information necessary for display processing is performed (S705). Next, it is determined whether or not the above processing has been performed for all managed PCs (S707), and if there are other managed PCs (for example, managed PCs 1 ′, 1 ″...) That have not performed the above processing remaining (S707). : NO), the process returns to S701, and the same process is performed for other managed PCs.

  In this way, as a result of performing the processing of S701 to S705 on all managed PCs, a result file including printer information acquired from all managed PCs is created on the management PC 2 side. Then, based on the result file on the management PC 2 side, the management PC 2 executes output / display processing (S709). The output / display process in S709 is the process shown in detail in the flowchart of FIG.

  When the output / display process is started, the management PC 2 analyzes / formats the result file on the management PC 2 side (S721). Specifically, as formatting for output to a LOG file, when a character string as a headline is added, or when a LOG is displayed or printed later, the information for one line is folded at an unexpected position. In order to prevent this from happening, formatting such as adding a line feed code at an appropriate place is performed. Also, as the formatting for screen display, in addition to the formatting equivalent to the formatting for LOG output, the analysis of the place where the description (for example, a predetermined control character string called a tag) by HTML (HyperText Markup Language) is added, and Formatting to add a description is performed.

  Subsequently, the management PC 2 displays the screen display data created in the process of S721 (S723), and outputs the LOG output data to the LOG file (S725). Text data as illustrated in FIG. 15 is stored in the LOG file created by the processing of S725.

  In this text data, the name of the managed PC (in the case of the data illustrated in FIG. 15, “PC1” and “PC2”), the printer model name (in the case of the data illustrated in FIG. 15, “Device1”, “ Device 2 ”), local port name (in the case of data illustrated in FIG. 15,“ LPT1 ”,“ USB001 ”), and various printer information (in the case of data illustrated in FIG. 15,“ Pages = 2098 ”,“ Drum Life = 4039 ″,... In particular, every time one managed PC name is described, a description having the format “printer model name on local port name” is added to all printers connected to the managed PC. The printer information acquired from each printer is listed each time it is performed. For this reason, even when there are many printers of the same model in the system, the user is connected to a managed PC to determine what type of printer is connected to the managed PC. For a plurality of printers, it is possible to easily understand which model is connected to which local port. That is, the name of the managed PC, the model name of the printer connected to the managed PC, and the name of the local port used for connection between the printer and the managed PC are described. Therefore, even when there are several identical printer model names and identical local port names, the user can easily grasp which printer information each printer information belongs to.

  In the display and log output described above, in principle, all printer information acquired from the managed PC is output. In the printer information, printer maintenance (for example, drum replacement, (Information such as toner cartridge replacement and cleaning) may be included. Therefore, in the subsequent processing, processing for notifying the user by e-mail of printer information that is considered to be in a state of maintenance is performed.

  Specifically, after finishing the processing of S725, the management PC 2 selects one piece of printer information that has not yet been evaluated from all the individual printer information acquired from all managed PCs, and about the printer information. Then, the necessity for maintenance is evaluated in accordance with a predetermined evaluation standard (S727). As a specific example, for example, if the selected printer information is “Pages = 2098”, it is evaluated whether the value of 2098 sheets is larger than a predetermined number of sheets. In that case, it is evaluated that no maintenance is required.

  If it is evaluated that the maintenance is necessary (S729: YES), the address book file prepared in advance is searched using the name of the managed PC from which the printer information as the evaluation target is obtained as a key. The e-mail address (= the e-mail address of the user who manages the managed PC) recorded in association with the name of the managed PC as the key is acquired (S731).

  Next, a warning message file prepared in advance is searched using the label name (for example, “Pages”) in the printer information to be evaluated as a key, and the warning associated with the label name used as the key is searched. One format (warning message template) is selected (S733). As illustrated in FIG. 16, the warning message file is a record in which a combination of a label name and a warning format is used as one record, and the management PC 2 receives the printer information that has been evaluated. Once the label name is determined, the corresponding warning format can be selected from the warning message file.

  After selecting the warning format, the management PC 2 creates a warning text by entering the port name and model name in “% s” in the warning format (S735). As illustrated in FIG. 16, the warning format is a character string such as “Please replace the drum of% s connected to% s. Replace the toner.” The description “s” is included. In these “% s” portions, “local port name” and “model name” corresponding to the printer information to be evaluated are embedded. For example, in the case of the local port name “LPT1” and the model name “Device1”, a warning message “Please replace the drum of Device1 connected to LPT1. Replace the toner.” Is created. Become.

  Then, an e-mail with the warning text created in the process of S375 as the text is transmitted to the e-mail address acquired in the process of S731 (S737). In this way, the printer status can be centrally managed, and if there is an abnormality, the administrator can be immediately contacted.

  As described above, when the processes of S731 to S737 are completed, or when it is evaluated that the maintenance is not necessary in the process of S729 (S729: YES), the process is completed for one printer information to be evaluated. Therefore, it is checked whether printer information that has not yet been evaluated remains in all individual printer information acquired from all managed PCs (S739), and processing for all printer information must be completed. If (S739: NO), the process returns to S727. As a result, the processing of S727 to S739 is repeated by the same number as all the individual printer information acquired from all managed PCs. As a result of this repeated processing, when the processing for all the printer information is finished (S739: YES), this processing is finished.

  When the processing of S721 to S739 is completed in this way, the processing of S709 shown in FIG. 13 is completed. As a result, the processing of S701 to S709 is also completed, so the processing of S601 in FIG. Subsequently, the management PC 2 reads the investigation setting time from the setting file (S603), calculates the time until the next investigation setting time arrives, and sets the calculated time in the timer (S605). The setting file is a file stored in the auxiliary storage unit 24, and the setting time of investigation set by the administrator is recorded in the setting file. The timer generates a timer event when the time calculated in the process of S605 has elapsed after the process of S605.

  Subsequently, the management PC 2 waits for the occurrence of a related event (S607). If the generated event is a timer event (S609: YES), the timer is set to 24 hours (S611), and the timer event is again 24 hours later. The data processing is executed (S613). This data processing is the same as the processing of S601 described above, and details are shown in the flowchart of FIG. 13, but since this processing has already been described, description thereof is omitted here.

  If the event that has occurred is not a timer event as a result of the determination in S609 (S609: NO), the user performs a predetermined operation using the input unit 22 to manually start the data processing. If the instruction is issued (S615: YES), the data processing is also executed in this case (S613).

  Furthermore, when the result of determination in S615 is that the user has not manually activated (S615: NO), or when the data processing in S613 has been completed, if the event that has occurred is an end instruction event (S617: YES), this process ends. The end instruction event is an event that occurs when the user performs a predetermined end operation using the input unit 22. On the other hand, if it is not an end instruction event (S617: NO), the process returns to the process of S607 and again waits for the occurrence of a related event. That is, when the management PC 2 is in an operating state, this process will not be completed unless the user performs a termination operation, and this process will continue to be executed as a resident process on the management PC 2.

  In the present embodiment, the survey setting time set by the process of S605 is about 10 minutes later than the time set in the managed PCs 1, 1 ′, 1 ″... By the process of S111 described above. When such a time is set on the management PC 2 side, a timer event occurs on the management PC 2 side after about 10 minutes after a timer event occurs on the managed PC 1, 1 ′, 1 ″. It can be expected that there is a high possibility that the printer information is updated to the latest state on the managed PC 1, 1 ′, 1 ″... When the setting is made so that timer events occur almost simultaneously on the "... side and the management PC 2 side, or the managed PC 1, 1 ', 1" ... side on the management PC 2 side When the management PC 2 side reads the file on the managed PC 1, 1 ', 1 "... side, the file on the managed PC 1, 1', 1" ... side is updated. In this case, there is a high possibility that the printer information acquired on the management PC 2 side is not necessarily the latest state, but if configured as in this embodiment, the managed PCs 1, 1 ′, After the file on the 1 "... side is updated, the file on the managed PC 1, 1 ', 1" ... side is read from the management PC 2 side, so the printer information acquired on the management PC 2 side is in the latest state. The possibility is high.

  As described above, in the present embodiment, the managed PC 1 acquires the 1284 ID (information indicating the device model in the present invention) of the printer 3 from the printer 3, identifies the model of the printer 3, and S331 The PJL command associated with the identified model is selected from the plurality of PJL commands by the processes of ~ S341. Therefore, even if a PJL command corresponding to the printer 3 and a PJL command not corresponding to the printer 3 are mixed in a plurality of PJL commands, only the PJL command corresponding to the printer 3 is selected. As a result, the PJL command transmitted to the printer 3 is only the PJL command corresponding to the printer 3, and the expected printer information can be acquired by receiving a response to the transmitted PJL command.

Therefore, the PJL command transmitted can get the expected printer information. Unlike the case where the managed PC transmits a PJL command that does not correspond to the printer, the managed PC 1 does not need to perform useless data transmission processing. Furthermore, unlike the case where the managed PC receives and responds to the response after transmitting a PJL command not corresponding to the printer (for example, discards the data), the managed PC 1 performs useless data reception processing. There is no need.

  In the present embodiment, the managed PC 1 acquires the 1284 ID of the printer 3 from the printer 3, identifies the model of the printer 3, and transmits a PJL command to the printer 3. The printer information is obtained by requesting the provision of the printer information and receiving a response to the transmitted PJL command. Then, the model name of the printer 3 determined according to the 1284 ID of the printer 3, the local port name used for connection between the managed PC 1 and the printer 3, and the printer information are stored in association with each other. Therefore, when referring to the stored printer information, the user combines the model name of the printer 3 associated with the printer information and the local port name used for connection of the managed PC 1 to the printer 3 together. Can be referred to.

  Accordingly, even when a plurality of printers 3 connected to one managed PC 1 are connected and a plurality of the same models exist among the plurality of printers, which printer information is obtained from which printer When the user wants to know, the user can easily identify one printer 3 based on the printer model name and the local port name.

As mentioned above, although embodiment of this invention was described, this invention is not limited to said specific one Embodiment, In addition, it can implement with a various form.
For example, in the above-described embodiment, the single-function printer 3 corresponding to the PJL command is illustrated as an example of a device connected to the computer, but another device may be used.

  As a specific example, as a device corresponding to the PJL command, a multifunction device having a facsimile function, a copy function, an image scanner function and the like in addition to a printer function is known. It is included in the device.

  Further, it is not necessary to be a device having a printer function, such as the printer 3 or the above-described multifunction device. In this case, the command does not need to be a command compliant with PJL, and the command is sent to the device via the print spooler. There is no need to send. That is, even for various devices that do not support PJL commands, commands can be sent from the computer side to the device side via the input / output I / F with the computer side, and a response is sent from the device side to the computer side according to the command. If the device information managed and updated on the device side is included in the response, the present invention can be applied to such a device. As such a device, for example, an image scanner, a digital camera, a USB camera, various storage devices, a label printer, and the like can be considered.

  In the above embodiment, the managed PC 1 provides the printer information acquired from the printer 3 to the management PC 2 side, and the management PC 2 side manages the printer information collected from all the managed PCs 1, 1 ′, 1 ″. However, the configuration of the present invention can also be adopted when the managed PC 1 itself manages the printer information acquired from the printer 3 in the managed PC 1.

It is a block diagram which shows the structure of the hardware illustrated in the said embodiment. It is a block diagram which shows the structure of managed PC. It is a flowchart of the main process in a managed PC. 6 is a flowchart of thread processing in a managed PC. 10 is a flowchart of model determination / DB writing processing in a managed PC. It is a flowchart of the reading / DB conversion processing 1 in the managed PC. It is a flowchart of the command extraction process in a managed PC. It is a figure which shows the data stored in the command file. It is a flowchart of DB (result file) write processing in a managed PC. It is a figure which shows the data stored in DB (result file). It is a flowchart of the reading / DB conversion processing 2 in the managed PC. It is a flowchart of the main process in management PC. It is a flowchart of the data processing in management PC. It is a flowchart of the output / display process in management PC. It is a figure which shows the text data stored in the LOG file. It is a figure which shows the data stored in the warning message file.

Explanation of symbols

  1, 1 ', 1 "... managed PC (personal computer), 2 ... management PC (personal computer), 3, 3', 3" ... printer, 11, 21 ... main body, 12, 22 ... input unit, 13, 23 ... display unit, 14, 24 ... auxiliary storage unit, 101 ... control unit, 102 ... I / F unit, 111 ... CPU, 112... ROM, 113... RAM, 121... Printer I / F function unit, 122... LAN I / F function unit, 123... Print spooler, 124. 131... Queue, 132... Command file, 133... Result file (database), 134.

Claims (15)

An information acquisition processing program for causing a computer to execute processing for acquiring device information, which is information about the device, from a device communicably connected to the computer,
An identification procedure for acquiring information indicating the model of the device from the device and identifying the model of the device;
Refer to command storage means in which a plurality of commands and information on one or a plurality of device models capable of responding to each command are stored in association with each other, and the device model identified in the identification procedure can respond A command selection procedure for selecting a command from the command storage means ;
An information request procedure for requesting the device to provide the device information by transmitting a command selected by the command selection procedure to the device;
An information acquisition procedure for acquiring the device information by receiving a response to the command transmitted by the information request procedure ;
When a plurality of commands are selected by the command selection procedure, the device information is requested by transmitting one command among the selected commands, and the command is obtained by the information acquisition procedure. On the condition that a response to the command is received, another command among the selected commands is transmitted to the device, while a response to the one command is not received by the information acquisition procedure. And an information request control procedure for controlling the information request procedure so as not to transmit the other command . The computer includes a plurality of local ports that can be locally connected to the device,
A local port extraction procedure for extracting a local port to which the device is connected from the plurality of local ports;
Processing is performed so that the device connected to the local port extracted by the local port extraction procedure becomes a processing target of the identification procedure, the command selection procedure, the information request procedure, the information acquisition procedure, and the information request control procedure Process thread creation procedure to create a thread and
The information acquisition processing program according to claim 1, further comprising:   Including an additional device detection procedure for detecting that the device is newly connected to the local port;
  The local port extraction procedure is a procedure for further extracting a local port to which the device newly detected by the additional device detection procedure is connected,
  The processing thread creation means is a procedure for creating the processing thread for the newly detected device.
  The information acquisition processing program according to claim 2, wherein:   An end detection procedure for detecting whether one job that can be processed by the device is completed;
  A job number counting procedure for counting the number of jobs input to the device in addition to the one job when the end detection procedure detects that the processing of the one job is completed,
  In the identification procedure, information indicating the model of the device is acquired from the device on the condition that the number of jobs counted in the procedure for counting the number of jobs is equal to or less than a predetermined number, and the model of the device is identified. Is the procedure to
  The information acquisition processing method program according to any one of claims 1 to 3, wherein   The identification procedure is a procedure for acquiring information indicating the model of the device every predetermined period from the device and identifying the model of the device.
  The information acquisition processing program according to any one of claims 1 to 4, wherein   The command includes information for specifying the device information.
  The information acquisition processing program according to any one of claims 1 to 5, wherein   The device information includes information on the degree of use of replacement parts of the device.
  The information acquisition processing program according to any one of claims 1 to 6, wherein   The device information includes information on the degree of wear of the consumables of the device.
  The information acquisition processing program according to any one of claims 1 to 7, wherein   The device information includes information related to the number of occurrences of an abnormality in the device.
  The information acquisition processing program according to any one of claims 1 to 8, wherein Information indicating the model of the device acquired in the identification procedure, information indicating an input / output I / F used for connection between the computer and the device, and the device information acquired in the information acquisition procedure The device stores association information stored procedure
10. The information acquisition processing program according to claim 1 , further comprising: When unable to access to the previous SL device, and information indicating that could not the access, and information indicating the input and output I / F used in the connection between the said computer device, in association with claims 1 to 10 information obtaining processing program according to any one of which comprises an access error information storing procedure for storing. In the information request procedure, when a command cannot be transmitted to the device, information indicating that the command could not be transmitted, information indicating the model of the device acquired in the identification procedure, the computer and the device 12. The information acquisition according to claim 1, further comprising: a transmission error information storage procedure for storing information indicating the input / output I / F used for connection with the transmission error information in association with each other. Processing program. In the information acquisition procedure, when a response from the device could not be received, information indicating that the device could not be received, information indicating the model of the device acquired in the identification procedure, the computer and the device information acquisition according to any one of the information indicating the input and output I / F used in the connection, according to claim 1 to claim 12, characterized in that it comprises a reception error information storing procedure for storing in association with Processing program. Devices and which is communicably connected to a computer that executes a process of acquiring the device information from the previous SL device,
Information indicating the model of the device is obtained from the device, and identification means for identifying the model of the device;
Command storage means for storing a plurality of commands and information of one or a plurality of device types capable of responding to each command in association with each other;
Command selection means for referring to the command storage means and selecting from the command storage means a command to which the model of the device identified by the identification means can respond ;
Information request means for requesting the device to provide the device information by transmitting a command selected by the command selection means to the device;
An information acquisition means for acquiring the device information by receiving a response to the command transmitted by the information request means ;
When a plurality of commands are selected by the command selection means, the device information is requested to be provided by transmitting one command among the selected commands, and the information acquisition means requests the one command. On the condition that a response to the command is received, another command among the selected commands is transmitted to the device, while a response to the one command is not received by the information acquisition unit. And an information request control means for controlling the information request means so as not to transmit the other command .   A computer and a device connected to the computer, wherein the device stores device information that is information about the device, and updates that update the device information on the device side as the device operates A system configured to execute a process of acquiring the device information from the device, the computer comprising:
  The computer
  Information indicating the model of the device is obtained from the device, and identification means for identifying the model of the device;
  Command storage means for storing a plurality of commands and information of one or a plurality of device types capable of responding to each command in association with each other;
  Command selection means for referring to the command storage means and selecting from the command storage means a command to which the model of the device identified by the identification means can respond;
  Information request means for requesting the device to provide the device information by transmitting a command selected by the command selection means to the device;
  An information acquisition means for acquiring the device information by receiving a response to the command transmitted by the information request means;
  When a plurality of commands are selected by the command selection means, the device information is requested to be provided by transmitting one command among the selected commands, and the information acquisition means requests the one command. On the condition that a response to the command is received, another command among the selected commands is transmitted to the device, while a response to the one command is not received by the information acquisition unit. And information request control means for controlling the information request means so as not to transmit the other command.
  An information acquisition processing system comprising:

Images