JP2002016750A - Image forming device and its control method and image forming system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To simplify the use of optional devices of a network printer. SOLUTION: A printer 104 connected to copying machines 103, 106 and an image data controller 102 through an IEEE 1394 bus checks an option state and a job state and broadcasts its state to other device in an isochronous mode when the state is subject to change from the transmission of a preceding state or a prescribed time elapses from the preceding transmission.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an image forming apparatus which realizes a systemized digital office environment in which a printer, a scanner, and a host computer are connected to a network and freely transfers data via the network, and its control. The present invention relates to a method and an image forming system.

[0002]

2. Description of the Related Art Recently, copiers have been multi-functionalized by digitization and systemization. In addition to the integration of the FAX function, the printer function is added to the network and the printer function is added. FIG. 2 shows an office network environment including a digital copying machine. Reference numeral 200 denotes a network such as Ethernet (registered trademark) to which network devices such as a personal computer, a printer, and a digital copier in the office are connected. 201 is a personal computer (hereinafter P)
C).

[0003] Reference numeral 202 denotes a digital copying machine; and 203, a controller for connecting the digital copying machine to a network. Reference numeral 204 denotes a color copying machine; and 205, a controller for connecting the color copying machine to a network. 206 is a printer with a staple sorter, and 207 is a printer with a sorter.

In FIG. 2, the staple option is not installed in either of the copying machines 202 and 204, and the staple option is installed in the printer 206. In order to allow the system to perform stapling of a copy in such a network environment,
The data read by the digital copier 202 is transferred to the printer 2
It is necessary to output at 06 and perform stapling. In this case, it is necessary to search for a device having a function desired by the user from the network devices.

[0005]

For this purpose, it is necessary to obtain option information of a printer for performing printing at a source of print data, for example, a digital copying machine 202 or the like. By referring to this information, the issuer of the print data can know which device has an optional function such as sorting or stapling, and can control the device. In addition, it is necessary to have a mechanism for obtaining information that changes every moment, such as the presence or absence of staples and the job processing status, in real time.

SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned prior art, and provides an image forming apparatus for providing status information thereof, particularly information including status information of optional devices, to a device connected thereto via a network. An object of the present invention is to provide a control method and an image forming system.

[0007]

To achieve the above object, the present invention has the following arrangement. That is, an image forming apparatus connected to a communication network, wherein the state obtaining means for obtaining a state of the image forming apparatus, and the state obtained by the state obtaining means are transmitted to a device connected to the communication network in a state. Transmission means for spontaneously transmitting the information.

[0008] Preferably, the transmitting means transmits the status information to all devices connected to the communication network.

Preferably, the transmitting means transmits the status information at predetermined time intervals or each time the status changes.

Preferably, the status information includes a status of an optional device including a staple sorter.

Preferably, the status information includes at least one of a status of jam detection, presence or absence of a tray paper, overloading of a tray, and presence or absence of a staple.

Preferably, the apparatus further comprises a storage unit for storing the received print data, and the status information includes information indicating a free space of the storage unit.

Preferably, the communication network is I
In accordance with the EEE1394 standard, the transmitting means transmits the status information to devices on the network by isochronous transfer.

Alternatively, the image forming apparatus includes any one of the above-described image forming apparatuses, and a network device that receives status information transmitted from the image forming apparatus and uses the image forming apparatus in accordance with the status information. Characteristic image forming system.

[0015] Preferably, the network device includes:
The state of the optional device of the image forming apparatus is determined from the state information, and the image forming apparatus is used according to the determination result.

Preferably, the network device includes:
The use state of the storage unit of the image forming apparatus is determined from the state information, and the image forming apparatus is used according to the determination result.

Preferably, the network device includes:
When the free space of the storage unit itself is insufficient, the use state of the storage unit of the image forming apparatus is determined from the status information, and the image forming apparatus having a sufficient free space is used.

[0018]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [First Embodiment] Here, in the present invention, a digital I / F for connecting each device is set to IEEE.
Since the 1394 serial bus is used, IEEE 1394
The serial bus will be described in advance.

<< Overview of IEEE 1394 Technology >> With the advent of home digital VTRs and DVDs, it is necessary to support real-time, high-information-volume data transfer of video data and audio data. In order to transfer such video and audio data in real time, and to transfer them to a personal computer (PC) or other digital devices, an interface capable of high-speed data transfer with necessary transfer functions is required. The interface developed from such a viewpoint is IEEE 1394-1995 (High Per
fomance Serial Bus) (hereinafter 1394 serial bus).

FIG. 32 shows an example of a network system configured using a 1394 serial bus. This system is provided with devices A, B, C, D, E, F, G, and H. A-B, A-C, B-D, D-E, C-F
The CG, the CG, and the C-H are connected by a twisted pair cable of a 1394 serial bus.
The devices A to H are, for example, PC, digital VTR, DV
D, digital camera, hard disk, monitor, etc.

The connection method between the devices is such that the daisy chain method and the node branch method can be mixed.
A highly flexible connection is possible.

Each device has its own unique ID, and by recognizing each other, constitutes one network in a range connected by a 1394 serial bus. One 1394 connection between each digital device
Just by sequentially connecting with a serial bus cable, each device plays a role of relay, and constitutes one network as a whole. In addition, it has a function of automatically recognizing the device and recognizing the connection status when the cable is connected to the device by the Plug & Play function, which is a feature of the 1394 serial bus.

In the system shown in FIG. 32, when a device is deleted from the network or newly added, the bus is automatically reset to reset the network configuration up to that time. Then, rebuild a new network. With this function, the configuration of the network at that time can be constantly set and recognized.

The data transfer rate is 100/200 /
It has a transmission rate of 400 Mbps, and a device having a higher transfer rate supports a lower transfer rate and is compatible.

The data transfer mode includes asynchronous data such as control signals (hereinafter referred to as A).
Asynchronous transfer mode for transferring sync data)
There is an isochronous transfer mode for transferring synchronous data (Isochronous data: hereinafter, iso data) such as real-time video data and audio data. This Asyn
In each cycle (usually 125 μS per cycle), the c data and the Iso data follow the transfer of the cycle start packet (CSP) indicating the start of the cycle,
o Data is transferred together in a cycle while giving priority to data transfer.

Next, FIG. 33 shows the components of the 1394 serial bus.

The 1394 serial bus has a layer (hierarchical) structure as a whole. As shown in FIG. 33, the most hardware is a 1394 serial bus cable, there is a connector port to which a connector of the cable is connected, and there are a physical layer and a link layer as hardware thereon. .

The hardware part is a substantial part of an interface chip. The physical layer performs coding and control related to connectors, and the link layer performs packet transfer and cycle time control.

The transaction layer of the firmware section manages data to be transferred (transacted), and issues commands such as Read and Write. The serial bus management is a part that manages the connection status and ID of each connected device and manages the configuration of the network.

The hardware and the firmware are the actual configuration of the 1394 serial bus.

The application of the software section
The layer differs depending on the software used, and is a part that defines how data is placed on the interface.
It is specified by a protocol such as the V protocol.

The above is the configuration of the 1394 serial bus.

Next, FIG. 18 shows a diagram of the address space in the 1394 serial bus.

Each device (node) connected to the 1394 serial bus always has a 64-bit address unique to each node. By storing this address in the ROM, the node address of the user or the other party can always be recognized, and communication specifying the other party can be performed.

The addressing of the 1394 serial bus is based on the IEEE 1212 standard, and the first 10 bits are used to specify the bus number.
The next 6 bits are used for specifying the node ID number. The remaining 48 bits become the address width given to the device,
Each can be used as a unique address space. The last 28 bits store information such as identification of each device and designation of use conditions as an area of unique data.

The above is the outline of the technology of the 1394 serial bus.

Next, the technical portion which can be said to be a feature of the 1394 serial bus will be described in more detail.

<< Electrical Specifications of 1394 Serial Bus >> FIG. 19 is a sectional view of a 1394 serial bus cable.

In the 1394 serial bus, a power supply line is provided in the connection cable in addition to the two twisted pair signal lines. As a result, power can be supplied to a device having no power supply, a device whose voltage has dropped due to a failure, and the like.

The voltage of the power supply flowing in the power supply line is 8 to 40.
V and the current are specified as the maximum current DC 1.5A.

<< DS-Link Coding >> A data transfer format D which is adopted in the 1394 serial bus.
FIG. 20 is a diagram illustrating the S-Link coding scheme.

In the 1394 serial bus, DS-Lin
The k (Data / Strobe Link) coding method is adopted.
This DS-Link coding scheme is suitable for high-speed serial data communication, and its configuration requires two signal lines. The main data is sent to one of the twisted pairs,
A strobe signal is sent to the other twisted pair.

On the receiving side, the clock can be reproduced by taking the exclusive OR of this communicated data and the strobe.

The advantages of using the DS-Link coding method include higher transfer efficiency compared with other serial data transfer methods, and the circuit size of the controller LSI can be reduced because a PLL circuit is not required.
Since there is no need to send information indicating the idle state when there is no data to be transferred, the power consumption can be reduced by setting the transceiver circuit of each device to the sleep state.

<< Bus Reset Sequence >> In the 1394 serial bus, each connected device (node) is given a node ID, and is recognized as a network configuration.

When there is a change in the network configuration, for example, a change occurs due to an increase or decrease in the number of nodes due to insertion / removal of a node or turning on / off of a power supply, etc. Each detected node sends a bus reset signal on the bus,
Enter the mode to recognize the new network configuration. The method of detecting the change at this time is performed by detecting a change in the bias voltage on the 1394 port board.

When a bus reset signal is transmitted from a certain node, the physical layer of each node transmits the bus reset signal to the link layer at the same time as receiving the bus reset signal, and transmits the bus reset signal to another node. . After all the nodes finally detect the bus reset signal, the bus reset is activated.

The bus reset is also started by a cable detection as described above, a start by hardware detection due to a network error or the like, and also by directly issuing a command to a physical layer by a host control from a protocol or the like.

Further, when the bus reset is activated, the data transfer is suspended, the data transfer during this period is waited, and after the end, the data transfer is resumed under a new network configuration.

The above is the bus reset sequence.

<< Node ID Determination Sequence >> After the bus reset, each node starts an operation of giving an ID to each node in order to construct a new network configuration. The general sequence from the bus reset to the determination of the node ID at this time will be described with reference to the flowcharts of FIGS.

The flowchart of FIG. 21 shows a series of bus operations from the occurrence of a bus reset until the node ID is determined and data transfer can be performed.

First, as step S101, the occurrence of a bus reset in the network is constantly monitored. If a bus reset occurs due to power ON / OFF of a node, the process proceeds to step S102.

In step S102, from the reset state of the network, a parent-child relationship is declared between the directly connected nodes in order to know the connection status of the new network. As step S103,
When the parent-child relationship is determined between all nodes, step S
One route is determined as 104. Until the parent-child relationship is determined for all node questions, the parent-child relationship is declared in step S102, and the route is not determined.

After the route is determined in step S104, the operation for setting a node ID for giving an ID to each node is performed in step S105. Node IDs are set in a predetermined node order, and I
The setting operation is repeatedly performed until D is given. When the IDs are finally set in all the nodes in step S106, the new network configuration is recognized in all the nodes. And data transfer is started.

In the state of step S107, a mode is again entered for monitoring the occurrence of a bus reset.
When the bus reset occurs, the setting operation from step S101 to step S106 is repeatedly performed.

The flow chart of FIG. 21 has been described above. The flow chart of FIG. 21 shows the portion from the bus reset to the route determination and the procedure from the route determination to the end of ID setting in a more detailed flow chart. Are shown in FIGS. 22 and 23, respectively.

First, the flowchart of FIG. 22 will be described.

When a bus reset occurs in step S201, the network configuration is reset once. The occurrence of a bus reset is constantly monitored in step S201.

Next, as step S202, as a first step of re-recognizing the reset network connection status, a flag indicating a leaf (node) is set for each device. Further, in step S203, each device checks how many ports it has are connected to other nodes.

In accordance with the result of the number of ports in step S204, the number of undefined (undetermined parent-child) ports is checked in order to start the declaration of the parent-child relationship.
Immediately after the bus reset, the number of ports = the number of undefined ports. However, as the parent-child relationship is determined, the number of undefined ports detected in step S204 changes.

First, immediately after the bus reset, only a leaf can declare a parent-child relationship first. A leaf can be known by checking the number of ports in step S203. In step S205, the leaf declares "I am a child and the other is a parent" to the node connected thereto, and ends the operation. Step S2
In step S204, immediately after the bus reset, the unrecognized port number> 1 is determined for the node which has a plurality of ports and is recognized as a branch in step S03.
At 207, the process waits to accept the "parent" in the parent-child relationship declaration from the leaf.

The leaf declares the parent-child relationship, and the branch that has received the declaration in step S207 appropriately returns to step S20.
Confirm the number of undefined ports of 4 and find that the number of undefined ports is 1
If it becomes, it becomes possible to declare “I am a child” in step S205 for the node connected to the remaining port. After the second time, step S204
Even if the number of undefined ports is checked in step S207, for a branch having two or more ports, the process waits again in step S207 to accept a "parent" from a leaf or another branch.

Finally, if any one of the branches, or exceptionally, leaves (because they did not operate quickly enough to make a child declaration) become zero as a result of the number of undefined ports in step S204, In this case, the declaration of the parent-child relationship of the entire network has been completed, and the only node for which the number of undefined ports has become zero (all are determined as parent ports) is flagged as a root in step S208, and the root is set in step S209. Is recognized.

In this manner, the process from the bus reset shown in FIG. 22 to the declaration of the parent-child relationship between all the nodes in the network is completed.

Next, the flowchart of FIG. 23 will be described.

First, in the sequence up to FIG.
Since the information of the flag of each node such as the branch and the route is set, it is classified based on this in step S301.

As a task of assigning an ID to each node, an ID can first be set from the leaf. The IDs are set in ascending order of leaf → branch → route (node number = 0).

At step S302, the number N (N is a natural number) of leaves existing in the network is set. Thereafter, in step S303, each leaf requests the root to give an ID. If there are a plurality of such requests, the route performs arbitration (operation of arbitration into one) in step S304, and proceeds to step S3.
As 05, an ID number is given to one winning node, and a failure result is notified to the losing node. In step S306, the leaf whose ID acquisition has failed fails issues an ID request again, and repeats the same operation. In step S307, the ID information of the node is transferred to all the nodes by broadcasting from the leaf whose ID has been acquired. One node I
When the broadcasting of the D information is completed, step S30
As 8, the number of remaining leaves is reduced by one. here,
In step S309, when the number of the remaining leaves is one or more, the operation from the ID request in step S303 is repeatedly performed, and finally, when all the leaves broadcast the ID information, N = 0 in step S309, and the next Moves to the branch ID setting.

The setting of the branch ID is performed in the same manner as in the case of the leaf.

First, as step S310, the number M (M is a natural number) of branches existing in the network is set. Thereafter, in step S311, each branch requests the root to give an ID. On the other hand, the root performs arbitration as step S312, and gives the branch in order from the winning branch to the next youngest number that has been given to the leaf. In step S313, the root notifies the branch that issued the request of ID information or a failure result, and in step S314, the branch whose ID acquisition has failed fails issues an ID request again and repeats the same operation. In step S315, the ID information of the node is broadcast and transferred to all the nodes from the branch where the ID has been obtained. When the broadcast of the one node ID information ends, the number of remaining branches is reduced by one in step S316. Here, step S
If the number of the remaining branches is 1 or more as 317, the operation from the ID request in step S311 is repeated.
The process is performed until all the branches finally broadcast the ID information. When all the branches have acquired the node IDs, M = 0 in step S317, and the branch ID acquisition mode ends.

At this point, since only the root node has not acquired the ID information at the end, step S
318 is set as the own ID number among the unassigned numbers, and the root I
Broadcast D information.

Thus, as shown in FIG. 23, the procedure from the determination of the parent-child relationship to the setting of the IDs of all the nodes is completed.

Next, the operation in the actual network shown in FIG. 24 as an example will be described with reference to FIG.

As an explanation of FIG. 24, (root) node B
Are directly connected to node A and node C,
Further, a node D is directly connected below the node C, and a node E and a node F are directly connected below the node D in a hierarchical structure. The procedure for determining the hierarchical structure, the root node, and the node ID will be described below.

After the bus reset, a parent-child relationship is declared between ports directly connected to each node in order to recognize the connection status of each node. The parent and child can be said to be such that the parent is higher in the hierarchical structure and the child is lower.

In FIG. 24, the node A first declares the parent-child relationship after the bus reset. Basically, a node (called a leaf) having a connection to only one port of the node can declare a parent-child relationship. Since the user can first know that the connection is only one port, he / she recognizes that this is the edge of the network, and the parent-child relationship is determined from the node that has operated earlier in the network. In this way, the port on the side that has declared the parent-child relationship (node A between AB) is set as a child,
The port on the other end (node B) is set as the parent. Thus, the child-parent between the nodes AB and the child-parent between the nodes E-D.
The parent and the node FD are determined as child-parent.

Further, one level up, this time, among nodes having a plurality of connection ports (referred to as branches), a parent-child relationship is declared further higher in order from a node that has received a parent-child relationship declaration from another node. To go.

In FIG. 24, first, when node D is between D and E,
After the parent-child relationship between F and F is determined, a parent-child relationship is declared for node C. As a result, child-child
Have decided with parents.

The node C receiving the parent-child relationship declaration from the node D becomes the node B connected to another port.
Declare a parent-child relationship. As a result, a child-parent is determined between the nodes C and B.

In this way, a hierarchical structure as shown in FIG. 24 is formed, and the node B which has become the parent in all finally connected ports is determined as the root node. There is only one route in one network configuration.

In FIG. 24, node B is determined to be the root node. This is because node B, which has received a parent-child relationship declaration from node A, makes a parent-child relationship declaration to other nodes at an early timing. If so, the root node may have moved to another node. That is, any node may become a root node depending on the transmission timing, and the root node is not always constant even in the same network configuration.

When the root node is determined, the process enters a mode for determining each node ID. Here, all nodes notify their determined node IDs to all other nodes (broadcast function).

The self ID information includes its own node number, information on the connected position, the number of ports it has, the number of connected ports, information on the parent-child relationship of each port, and the like.

As a procedure for assigning node ID numbers, it is possible to start from a node (leaf) having a connection to only one port, and node numbers = 0, 1, and 2 are assigned in this order.

The node having the node ID broadcasts information including the node number to each node. As a result, it is recognized that the ID number is “assigned”.

When all the leaves have acquired their own node IDs, the next step is to move to a branch, and the node ID number following the leaf is assigned to each node. Similarly to the leaf, the node ID information is broadcast sequentially from the branch to which the node ID number is assigned, and finally, the root node broadcasts its own ID information. That is, the root always owns the maximum node ID number.

As described above, the assignment of the node IDs of the entire hierarchical structure is completed, the network configuration is reconstructed, and the bus initialization operation is completed.

<< Arbitration >> In the 1394 serial bus, arbitration (arbitration) of the right to use the bus is always performed prior to data transfer. Since the 1394 serial bus is a logical bus-type network in which each device connected individually relays the transferred signal to transmit the same signal to all devices in the network, packet collision occurs. Arbitration is necessary to prevent This allows only one node to transfer at a given time.

As a diagram for explaining arbitration, FIG. 25A shows a diagram of a bus use request and FIG. 25B shows a diagram of a bus use permission, which will be described below.

When the arbitration starts, one or a plurality of nodes issue a bus use request to the parent node. Nodes C and F in FIG. 25A are nodes that have issued a bus use right request. The parent node (node A in FIG. 25) that has received this further issues (relays) a request for the right to use the bus toward the parent node. This request is finally delivered to the arbitration route.

The root node that has received the bus use request determines which node is to use the bus. This arbitration work can be performed only by the root node, and the node that has won the arbitration is given permission to use the bus. FIG.
In (b), use permission is given to the node C, and use of the node F is rejected.

A DP (data prefix) packet is sent to the node that has lost the arbitration to notify that the node has been rejected. The rejected node use request waits until the next arbitration.

As described above, the node that has won the arbitration and obtained the bus use permission can start transferring data thereafter.

Here, a series of arbitration flows will be described with reference to a flowchart shown in FIG.

In order for a node to be able to start data transfer,
The bus must be idle. In order to recognize that the data transfer that has been performed earlier is completed and that the bus is currently idle, a predetermined idle time gap length (eg, sub-action. Each node determines that its own transfer can be started by passing the gap.

In step S401, it is determined whether a predetermined gap length corresponding to each data to be transferred, such as Async data and Iso data, has been obtained. Unless the predetermined gap length is obtained, the request for the right to use the bus required to start the transfer cannot be made, so the process waits until the predetermined gap length is obtained.

If a predetermined gap length is obtained in step S401, it is determined in step S402 whether there is data to be transferred. If so, a request for a bus use right is issued in step S403 to secure a bus for transfer. Emit to the route. At this time, the transmission of the signal indicating the request for the right to use the bus is finally delivered to the route while relaying each device in the network, as shown in FIG. If there is no data to be transferred in step S402,
Wait as it is.

Next, when one or more bus use requests of step S403 are received by the route at step S404, the route checks the number of nodes that have issued use requests at step S405. If the selection value in step S405 is the number of nodes = 1 (the number of nodes that issued the use right request is one), the immediately subsequent bus use permission is given to that node. The selection value in step S405 is the number of nodes> 1
If (the number of nodes requesting the use is plural), the root performs an arbitration operation of deciding one node to which use permission is given in step S406. This arbitration work is fair, and the same node does not always obtain permission each time, and the right is equally given.

As step S407, step S40
At step 6, the node arbitrates the route from among the plurality of nodes that have issued the use request and selects one node whose use has been granted and another node that has lost. Here, for one node that has been arbitrated and has obtained use permission, or a node that has obtained use permission without arbitration with the number of use request nodes = 1 from the selection value in step S405, the route is set to that node as step S408. A permission signal is sent to it. The node that has received the permission signal starts transferring data (packets) to be transferred immediately after receiving the permission signal. Further, the nodes that have been defeated in the arbitration in step S406 and have not been permitted to use the bus are given step S406.
At step 409, a DP (data prefix) packet indicating arbitration failure is sent from the root, and the node that has received the packet returns to step S401 to issue a bus use request for performing transfer again, until the predetermined gap length is obtained. stand by.

The above is the description of the flowchart in FIG. 26 for explaining the flow of arbitration.

<< Asynchronous Transfer >> The asynchronous transfer is an asynchronous transfer. FIG. 27 shows a temporal transition state in the asynchronous transfer. The first sub-action gap in FIG. 27 indicates the idle state of the bus. When the idle time reaches a certain value, the node desiring transfer determines that the bus can be used and executes arbitration for acquiring the bus.

When the bus use permission is obtained by arbitration, the data transfer is executed in the form of a packet.
After the data transfer, the receiving node sets ack (reception confirmation return code) of the reception result for the transferred data to a.
After a short gap of ck gap, the transfer is completed by returning and responding or sending a response packet. The ack is composed of 4-bit information and a 4-bit checksum, and includes information such as success, busy status, and pending status, and is immediately returned to the source node.

Next, FIG. 28 shows an example of the packet format of the asynchronous transfer.

The packet has a header in addition to the data part and the data CRC for error correction. The header part has the destination node ID, the source node ID, the transfer data length and the like as shown in FIG. Various codes and the like are written and transferred.

Asynchronous transfer is one-to-one communication from a self-node to a partner node. The packet transferred from the transfer source node is distributed to each node in the network, but the address other than its own address is ignored, so that only one destination node reads the packet.

The above is the description of the asynchronous transfer.

<< Isochronous (Synchronous) Transfer >> Isochronous transfer is synchronous transfer. This isochronous transfer, which can be said to be the greatest feature of the 1394 serial bus,
In particular, this transfer mode is suitable for transferring data that requires real-time transfer, such as multimedia data such as VIDEO video data and audio data.

Also, if the asynchronous transfer (asynchronous) is 1
Unlike the one-to-one transfer, the isochronous transfer is uniformly transferred from one transfer source node to all other nodes by the broadcast function.

FIG. 29 is a diagram showing a temporal transition state in isochronous transfer.

The isochronous transfer is executed on the bus at regular intervals. This time interval is called an isochronous cycle. The isochronous cycle time is 125 μS. The cycle start packet indicates the start time of each cycle, and plays a role of adjusting the time of each node. A node called a cycle master transmits a cycle start packet, and after a transfer in a previous cycle is completed, a predetermined idle period (subaction gap) is passed, and then the start of this cycle is announced. Send a cycle start packet. The time interval at which this cycle start packet is transmitted is 125 μS.

FIG. 29 shows channel A, channel B,
As indicated by the channel C, a plurality of types of packets can be separately transferred by being given channel IDs in one cycle. This allows real-time transfer between a plurality of nodes at the same time, and the receiving node fetches only the data of the channel ID desired by itself. The channel ID does not represent the address of the transmission destination, but merely gives a logical number for the data. Therefore, the transmission of a certain packet is 1
From one source node to all other nodes,
It will be transferred by broadcast. Prior to the packet transmission in the isochronous transfer, arbitration is performed as in the asynchronous transfer. However, since the communication is not one-to-one communication as in the asynchronous transfer, there is no ack (reception confirmation reply code) in the isochronous transfer.

The iso gap (isochronous gap) shown in FIG. 29 indicates an idle period necessary for recognizing that the bus is empty before performing the isochronous transfer. After the predetermined idle period has elapsed, a node that wishes to perform isochronous transfer determines that the bus is free, and can perform arbitration before transfer.

Next, an example of a packet format for isochronous transfer will be described with reference to FIG.

Each packet divided into each channel has a header portion in addition to a data portion and an error correction data CRC, and the header portion has a transfer data length and a channel length as shown in FIG. NO, various codes and a header CRC for error correction are written and transferred.

The above is the description of the isochronous transfer.

<< Bus Cycle >> In actual transfer on the 1394 serial bus, isochronous transfer and asynchronous transfer can coexist. FIG. 31 shows a state of a temporal transition of the transfer state on the bus in which the isochronous transfer and the asynchronous transfer are mixed at that time.

The isochronous transfer is executed prior to the asynchronous transfer. The reason is that, after the cycle start packet, the isochronous transfer can be started with a gap length (isochronous gap) shorter than the gap length (subaction gap) of the idle period required to start the asynchronous transfer.
Therefore, the isochronous transfer is executed with priority over the asynchronous transfer.

In the general bus cycle shown in FIG. 31, a cycle start packet is transferred from the cycle master to each node at the start of cycle #m. As a result, each node adjusts the time, and after waiting for a predetermined idle period (isochronous gap), the node that should perform isochronous transfer performs arbitration and starts packet transfer. In FIG. 31, the channel e, the channel s, and the channel k are sequentially and isochronously transferred.

After the operations from the arbitration to the packet transfer are repeatedly performed for the given channel, when all the isochronous transfers in the cycle #m are completed, the asynchronous transfer can be performed.

When the idle time reaches the sub-action gap where asynchronous transfer is possible, it is determined that the node that wants to perform asynchronous transfer can shift to execution of arbitration.

However, the period during which the asynchronous transfer can be performed is the time (cycle sy) for transferring the next cycle start packet after the completion of the isochronous transfer.
nch) only when a sub-action gap for starting asynchronous transfer is obtained.

In cycle #m of FIG. 31, two packets (packet 1 and packet 2) of isochronous transfer for three channels and then asynchronous transfer (including ack) are transferred. After this asynchronous packet 2, a time (cycle) to start cycle m + 1
e sync), the transfer in cycle #m ends here.

However, the time (c) for transmitting the next cycle start packet during the asynchronous or synchronous transfer operation
If (cycle synch) is reached, a cycle start packet of the next cycle is transmitted after waiting for an idle period after the transfer is completed without forcibly interrupting the transfer. That is, when one cycle continues for 125 μS or more, it is assumed that the next cycle is shortened by that much from the reference 125 μS. As described above, the isochronous cycle can be exceeded or shortened on the basis of 125 μS.

However, the isochronous transfer is always executed if necessary every cycle to maintain the real-time transfer, and the asynchronous transfer may be transferred to the next and subsequent cycles due to the shortened cycle time.

The cycle information including such delay information is
Controlled by the master.

The above is the description of the IEEE 1394 serial bus.

<Structure of Print System> Next, the print system of this embodiment will be described focusing on a digital copying machine controller. FIG. 1 shows the print system. Reference numeral 100 denotes a conventional network to which a personal computer and a printer are connected. Reference numeral 101 denotes a network provided for image transfer. Reference numeral 102 denotes a controller for controlling input / output of image data. 103 is a color copier, 104 and 10
Reference numeral 5 denotes a printer, and reference numeral 106 denotes a monochrome digital copier. These are connected to the image data network 101. 107, 108, 109, 110, 111, 1
Reference numeral 12 denotes a personal computer (hereinafter, PC) connected to the network 100. When printing out from the PC, data is sent to a desired printer or copier via the network 100, the controller 102, and the image data network 101. Next, the image data controller 102 will be described.

<Image Data Controller> FIG. 3 is a block diagram of the image data controller 102. Reference numeral 301 denotes a CPU on the image data controller, which controls the exchange of data with a PC or a printer on a network. A data bus 302 of the CPU includes a card bus controller 304 and a ROM 30 which will be described later.
5, RAM 306, hard disk controller 307
Is connected. The card bus controller 304 controls the card bus 303 for mounting a function board for adding a function to the image data controller. The ROM 305 is a program memory in which control software for the image data controller is stored. A part of the program area is constituted by a flash ROM, and the program memory can be rewritten from a facsimile data modem 311 or an interface terminal (not shown) via a telephone line. The RAM 306 is composed of a DRAM or an SRAM, and is used as a work area for a normal program or as an image data memory. The hard disk controller 307 controls reading and writing of the hard disk 312. The hard disk 312 is used for storing image data and storing program software.
When data is compressed and read, data is also expanded.

Next, each functional board connected to the card bus 303 will be described. The network interface card 308 performs an interface for a network to which the PC and the image data controller in FIG. 1 are connected. In this configuration, a corresponding card can be installed on a physical interface that constructs a network such as Ethernet or token ring. The image network interface card 309 serves as a network interface for transferring image data between the color copier, the printer, the black and white digital copier and the image data controller in FIG. This image network needs to be configured with a high-speed bus that can transfer a large amount of image data. Therefore, in the present embodiment, a description will be given of IEEE 1394, which is a high-performance serial bus that has recently attracted attention.
It is not necessarily limited to this.

The raster image expansion card 310 expands the printer description language into bitmap data. This is not used when the printer on the image network individually supports the page description language. However, even when a dumb printer that simply prints bitmap data is connected on the image network, the PC on the network side can use the printer as a page description language compatible printer without being aware of the fact. . Further, it is possible to cope with the support of many page description languages by replacing a function board with a card bus. In addition, the program memory area of the raster image development card is
Alternatively, a raster image development program for a plurality of page description languages is stored in the hard disk 312 in advance in a loadable configuration like a RAM. Therefore, it is possible to load the page description language desired by the user from the hard disk 312 into the program memory of the raster image development card 310. The FAX / data modem card 311 is connected to a telephone line to perform FAX transmission / reception, and can be connected to a remote PC or workstation as a data modem.

<Operation of Image Data Controller> Next, the operation of the image data controller and the flow of data on the network will be described.

When page description language (PDL) data is sent from a PC on the network to perform printout, the printer 105 is selected from the PC 107 in FIG.
DL print is designated. At that time, the PDL data is transferred to the image data controller 102 via the network 100.
Is input to

In the image data controller shown in FIG. 3, PDL data is input to the raster image development card 310 via the network interface card 308.

FIG. 5 is a block diagram of a network interface card. Reference numeral 701 denotes a card bus interface, 702 denotes an Ethernet protocol controller which is widely used at present, 704 denotes a data transmission / reception buffer, and 704 denotes an Ethernet transceiver including an interface with a medium connected to a network such as 110base2 or 10baseT. 705 is
A connector corresponding to the network medium.

CPU 301 of image data controller
When the data transmitted via the network interface card is determined to be PDL data, the data is transmitted to the raster image development card.

FIG. 4 is a block diagram of a raster image development card. Reference numeral 601 denotes a card bus interface; 602, a raster image processor for expanding PDL data to generate bitmap data; 603, a ROM as a program area for the raster image processor; 604, a bitmap memory for storing bitmap data , 605 are bitmap memory controllers for controlling read / write of the bitmap memory. The PDL data input to the raster image development card is sent to a raster image processor 602 via a card bus interface 601, where bitmap data is generated and sent to a bitmap memory 604 via a bitmap memory controller 605. Is stored. Then, the bitmap data is transferred to the image network interface card 309.

FIG. 6 is a block diagram of the image network interface card. Reference numeral 801 denotes a card bus interface, and 802 denotes a fast-in / fast-out memory (hereinafter, FIFO) for transferring image data.
It is. Reference numeral 803 denotes an IEEE 1394 link controller chip which is a high-speed serial interface employed in this embodiment. Reference numeral 804 denotes an IEEE 1394 physical interface, and reference numeral 805 denotes a connector to which an image network interface cable is connected. Up to three connectors can be connected to one physical interface. CPU 3 of the image data controller 102
In step 01, in order to transfer bitmap data from the PC to the designated printer 105, data transfer is performed through the image network interface card in the following procedure.

Image data controller → Transfer printer data transmission request command ・ Printer → Image data controller Transfer data reception confirmation command ・ Image data controller → Printer Print data start command transfer ・ Image data controller → Printer bitmap data transfer ・ Image Data controller → Printer Transfer of print data end command ・ Printer → Image data controller Print data reception confirmation command In the data transfer mode of IEEE1394, the side which has transferred data to a predetermined destination and received receives an asynchronous transmission of data reception confirmation. There are a transfer mode and an isochronous transfer mode in which data is transferred to an unspecified transfer destination and no confirmation is sent from the receiving side. Here, the command is selected in the asynchronous transfer mode, and the bitmap data is selected in the isochronous transfer mode. In FIG. 6, command data is input to the link chip controller 803 via the card bus interface 801 and is transferred as asynchronous data. On the other hand, the bitmap data is once written to the FIFO 802 via the card bus interface 801. The link chip controller 803 uses the FI to transfer bitmap data in the isochronous transfer mode
The data is read from the FO 802 and the data is transferred.

FIG. 7 is a block diagram of the printer. Reference numeral 901 denotes a C that performs all controls in the printer such as mechatronic control of the printer and reception of bitmap data.
PU, 902 is a memory in which a program of the CPU 901 is stored, 903 is a RAM of the CPU 901, and 904 is a CP.
The U901 CPU address, data bus, and 905 are IEEE interfaces with the image network 101.
1394 link controller, 906 is IEEE139
4 is a physical interface, 907 is an IEEE 1394 connector, 908 is a fast-in, fast-out memory (hereinafter, FIFO) for temporarily storing bitmap data transferred by isochronous transfer, 909
Is 908 according to the operation timing of the printer engine.
A video data controller that controls reading of bitmap data from the FIFO, a laser driver 910 performs printing, an engine controller 911 performs a motor control of a printer engine, and an engine controller that performs a mechatronic control such as a sheet feeding control, and 912 denotes a printer engine. . An optional controller 913 is mounted on the printer. This is for performing communication with the printer CPU 901, inputting various sensors (jam detection, staple presence / absence detection, detection of the upper limit of tray loading) not shown, and motor drive control. A hard disk 914 stores image data to be printed out.

Next, command and data transfer between the image network interface card and the printer will be described with reference to FIG.

# 1001 A data transmission request command is transferred from the image data controller to a desired printer in the asynchronous transfer mode.

# 1002 The printer receives the data in the asynchronous transfer mode and confirms it (hereinafter ACK).
Is sent from the IEEE 1394 link controller 905 in FIG.

# 1003 In the printer, the CPU 901 receives a data transmission request command.

# 1004 The CPU 901 confirms the current status of the printer, and transfers a data transmission request permission command to the printer if a printout operation is possible. This command is IEEE1
The data is transferred by the 394 link controller 905 in the asynchronous transfer mode.

# 1005 In the image data controller, the ACK of the data transmission request permission command data is transmitted from the IEEE 1394 link controller 804 in FIG.

# 1006 In the image data controller, the CPU 301 receives a data transmission request permission command.

# 1007 Image data controller →
Image data transfer is performed in the printer isochronous transfer mode (this data transfer will be described later).

# 1008 The image data controller transfers a print data end command to the printer after the image data transfer ends.

# 1009 In the printer, the ACK of the print data end command is returned from the IEEE 1394 link controller 905 in FIG.

# 1010 In the printer, the CPU 901 receives a print data end command.

# 1011 A print data reception confirmation command is sent from the printer to the image data controller.

# 1012 In the image data controller, the ACK of the print data reception confirmation command is set to IEEE.
Returned from the 1394 link controller 804.

# 1013 The image data controller receives the print data reception confirmation command.

As described above, the command transfer by the asynchronous transfer and the image data transfer by the isochronous transfer are performed.

<Procedure for Isochronous Transfer of Image Data> Next, how image data transfer by isochronous transfer is performed will be described.

125 μS for isochronous data transfer
Each time, packet transfer is performed, and by securing a channel in advance, time guarantee of data transfer can be obtained.

Therefore, it is necessary for the image data controller to check the printer speed in advance for the printer to be transferred and secure a channel according to the performance. The operation of the image data controller will be described with reference to the flowchart of FIG.

# 1101 The image data controller checks the printer performance with the printer. Here, the BD cycle time (1H time) and the number of 1H pixels of the printer are checked.

# 1102 Next, the required channel width is calculated based on the confirmed printer performance. For example, in the case of 1H time = 375 uS, 1H pixel number = 7200 pixels, 7200/3 = 24 for every 125 μS packet.
It is necessary to temporally guarantee the data transfer of 00 pixels. For a binary printer, 2 per packet
What is necessary is to secure a data transfer channel for 400 bits.

In the # 1103 image data controller, I
A necessary transfer channel is secured via the IEEE 1394 link controller.

When the channel required for the # 1104 printer is secured, the image data controller attaches a start and end header of one page of image data to the image data, and attaches a start and end header of 1H of image data to the image data. Such transfer data generation is performed.

Here, what kind of transfer data is generated will be described with reference to FIG. 1 packet is 12
A shaded portion in the packet formed every 5 usecs indicates a channel that is secured. The shaded channel is composed of a header + image data. The header is page start, between pages, page end, 1H start,
The code consists of a code of 1H end within the 1H period, and enables the printer which has received the transferred data to recognize the position of the image data in the channel. For example, 240 out of 7200 pixels of 1H pixels
When data of 0 pixels is transferred for each channel of 1 packet, 3 packets and 3 channels correspond to 1H 7200
Pixel data transfer is performed. The image data generated at this time is as shown in the figure. In the case of image data transfer for n lines (n is a positive number), 3n channel data is transferred, and the header of the channel data is the page start (A0
h) 1H start (A8h) + image data, second packet is between pages (A2h), 1H period (AAh) + image data, third packet is between pages (A2h), 1H end (ADh) + image data Becomes In the same manner as described below, a header is added to the image data, and the data is transmitted. And the third
Page end (A5h) and 1H end (AD
h) + Image data is transferred, and transfer of image data for one page is completed.

Returning to the flowchart of FIG. 9, the transfer data generated by the image data controller in step # 1105 is transferred to the FIFO 802 of FIG. The size of the FIFO 802 must be at least as large as the data size to be transferred in one packet.

# 1106 After storing the transfer data in the FIFO 802, the IEEE 1394 link controller 803
To execute data transfer.

# 1107 As shown in FIG. 10, the transfer data is created while the header is attached to the image data, and the data transfer is repeatedly performed. The print data transfer is completed when the data transfer for one page is completed.

<Output Process in Printer> Next, the timing at which print output is performed after transfer data is received by the printer will be described with reference to the timing chart of FIG.

FIG. 11A shows a packet cycle. The hatched portion therein is the image data in the isochronous transfer mode.

FIG. 11B shows the timing of writing data to the FIFO 908 of FIG. The transferred data is an IEEE 1394 link controller 9
05 is written to the FIFO. FIG. 11C shows the BD timing of the printer. In this example, the timing is such that a BD occurs once in three packets. FIG. 11D shows the read timing of the FIFO 908. Data for 3 packets is F
After being written to the IFO, the FIFO is synchronized with the next BD.
O is read out. FIG. 11E shows a state during the printing operation, in which the printing operation is performed during the reading of the FIFO.

The transfer of image data via the image data network to the printer selected from the image data controller has been described above.

<Initialization Processing of IEEE Network> I
In EEE1394, a topology map is created after the power is turned on by the link controller, and all nodes connected on the network are recognized. At this time, node numbers are assigned to all nodes according to the physical connection state and initial settings, and one root node (parent) is selected from the nodes.

When a topology map is created in the image data network, it is necessary to initialize the image data controller so that it is always selected as the root node. As a result, the subsequent image data network management can be smoothly performed. The image network initialization control of the image data controller will be described with reference to the flowchart of FIG.

# 1501 All the IEEE 1394 physical interfaces connected to the image data network for the occurrence of the IEEE 1394 bus reset detect the bus reset and perform the reset release sequence.

# 1502 Each node on the image network performs a predetermined control on a port connected after a predetermined wait time, and waits for a node number allocation to create a topology map.

In step # 1503, if it is determined that the IEEE 1394 node of the image data controller is not the root node, the predetermined wait time is increased and reset (# 1504), and the bus reset sequence is run again in step # 1501. Recreate the topology map. Generally, a wait time sufficiently longer than the wait time at the time of bus reset of a printer, a color copier, a black-and-white digital copier, a scanner, or the like recognized by the image controller is set in the IEEE 1394 link controller of the image data controller. It is necessary to keep. This # 1
The determination as to whether the node is the root node of 503 must be repeated by increasing the wait time to a certain extent until the image controller becomes the root for the subsequent image data network management.

If the image data controller is selected as the root node in step # 1505, each node on the network is asked for its attribute information.

# 1506 Then, a node attribute table is created from the attribute information returned from each node. This table indicates whether the image controller exchanges image data. If data transfer is possible, grasp the performance of the device. In the case of a printer, the presence / absence of page scale, resolution, 1H time, 1H pixel number, number of prints, and the like are included.

# 1507 Inquire the attribute information of each node to all nodes.

As described above, by grasping the attributes of all devices on the network after the topology map is created by the image controller, the overhead of command transfer at the time of data transfer is reduced.

FIG. 13 is an attribute table created in step # 1506 in the flowchart of FIG. The image data controller manages devices connected to the image network. The items will be described.

The node number is assigned to each node when the topology map is created. Transfer speed is IEEE
400Mbps, 200Mbps, 100Mbps at transfer speeds supported by the 1394 physical interface
There is s. The power supply capability of the node is IEEE 139
4 indicates whether power can be supplied via the cable. Also shown here is receiving power supply. Next, the device type indicates how the node transmits and receives image data to and from the image controller, or whether the node does not transmit and receive image data at all. When the device is a scanner, it is an image data transmission device, and information such as black and white / color, or the number of bits per pixel (bit / pixel) and resolution (dpi) is managed in a table. If the device is a printer, it is an image data receiving device, and it is black and white / color, print output speed (ppm), bi
There is information of t / pixel and dpi. In the case of Digital Copier (registered trademark), since it has both functions of a scanner and a printer, information is managed as an image data transmitting / receiving device.

FIG. 14 shows each node on the image network of FIG. 1, ie, the color copier 103, the printer 105,
104 is an attribute table of the monochrome digital copier 106.

<Broadcast Transmission of Option Information> Next, the printers 104 and 105 of FIG.
A procedure for broadcasting the status of the option attached to itself in the isochronous transfer of No. 4 will be described.

The printer CPU 901 shown in FIG. 7 always monitors the status of the installed options via the option controller 913 in the same manner as always monitoring the status of the printer.

The description will be made by taking the printer 104 as an example. This printer is equipped with a staple sorter, and the optional controller in this staple sorter checks the status of the jam detection sensor, tray paper sensor, tray stack over sensor, staple stapleless sensor, etc., and determines whether the sorter is operable. Have confirmed.

FIG. 15 is a flowchart showing the operation of multicasting the printer mounting option status on the network.

In # 3401, the printer CPU 90
1 detects a predetermined sensor via the option controller 913 and checks whether the printer option is in an operable state.

Next, in step # 3402, whether printing is currently in progress or not.
Check if there are any jobs waiting to be printed, and if so, how many minutes later those jobs will end.

At # 3403, it is checked whether the status has changed since the previous status transmission. If there is a change, the process proceeds to # 3405 to transfer the status isochronously. If there is no change, the process proceeds to the next step # 3404.

In step # 3404, it is determined whether or not a predetermined number of cycles (one cycle is 125 sec) has elapsed since the previous printer status was multicast.
If it has passed, the process proceeds to # 3405.

Here, the number of cycles is managed by the IEEE 1394 link controller 905, and the CPU 9
01 is informed of the information. This prevents unnecessary transfer of the printer status over the network.

On the other hand, if it is determined that the predetermined number of cycles has not elapsed, the flow returns to # 3401. In step # 3404, the CPU 901 displays a printer status such as a print job operable state and the presence or absence of a spooled job in I
IEEE 1394 link controller 905, IEEE1
Multicast by isochronous transfer on the image data network 101 via the 394 physical interface 906.

The color copying machine 103 and the monochrome digital copying machine 106, which are the image data input devices on the image data network 101 in FIG. 1, receive the option status of the printers 104 and 105 multicast by isochronous transfer, respectively.

Next, a flow in the case where print data is transferred from the image data controller will be described with reference to FIG.

Image data controller CPU 30 shown in FIG.
In step 1, it is determined whether there is a print request via the image network. (# 3501) If there is a print request, the printer option status of isochronous transfer from the printer is checked. (# 3502) In # 3503, the CPUs 301 and 1 via the image network interface 309 by the CPU 301.
A printer is selected from information such as whether the option is in an operable state or not in a job waiting state based on the printer option status multicasted from 04 (# 3504).

At step # 3505, the print data is transferred to the selected printer.

On the other hand, if there is no print request in step # 3501, a print request waiting state is set.

Here, the broadcast of the printer option status has been managed when the option status has changed from the previous broadcast status or by checking the number of cycles with the IEEE 1394 link controller.

This is designed so that the status change of the option is large and the frequency of status transfer on the IEEE 1394 is not excessively increased. However, the broadcast transfer interval may be changed according to the installed options. For example, for a paper deck such as a paper deck having no possibility of state change, such as no paper and paper size, it is sufficient to transfer only when the state is changed without performing periodic broadcasting.

The image data network is connected to the IEEE
1394, but the client P
A normal network to which C is connected may be used.

When a device on the image network prints using a printer as described above, the option status is referred to from the printer status information broadcast and held, and the option status is determined according to the option to be used. , Decide which printer to use. In addition, by transmitting a command for controlling the optional device to be used together with the print data, the user can use the desired optional device without taking steps such as inquiring each time of printing.

As described above, in the print system of the present embodiment, a new state is broadcast-transmitted to the image network from the printer at predetermined time intervals or whenever there is a status change. For this reason, the devices on the image network can always keep track of the latest printer status, particularly the status of options, and use it according to the latest status. It has become possible.

[Second Embodiment] In the first embodiment, a case is described in which an option that is not mounted on a digital copying machine is used because it is mounted on a printer. In the present embodiment, a case will be described in which options installed in both devices are effectively used in accordance with the state of each option.

When the hard disk 312 of the image data controller shown in FIG. 3 runs out of free space in the image data waiting to be output, reading of the next image cannot normally be performed until sufficient free space is secured. In such a case, if an electronic sorter (hard disk) attached to another device can be used, a reading operation can be performed.

Therefore, the printer shown in FIG. 7 in this embodiment broadcasts the vacant state of the hard disk 914 to the network device in addition to the staple sorter information in the state information broadcast in the flowchart of FIG. The free space information is information such as whether there is a job currently being printed, when there is a job being printed, when to end the job, and how much free space is available.

Next, the data transfer control performed according to the presence or absence of the free space in the hard disk in the local controller and the option controller information when performing the copy operation in the digital copying machine will be described with reference to the flowchart of FIG. .

# 3601 If there is a scan request, the flow advances to # 3602. Otherwise, it waits for a scan request.

# 3602 CPU of data controller
If it is determined in 301 that there is no free space in the hard disk 312, the process proceeds to # 3606.

# 3606 The option status is obtained, and a printer equipped with a hard disk having sufficient free space is selected based on the information (# 360).
7).

# 3608 Image data controller 30
Data transfer is performed to the printer selected from 0. On the other hand, if there is free space on the hard disk,
A reading operation is performed in # 3603.

Next, writing to the hard disk is performed in # 3604, and printing is performed in # 3605.

By controlling the data transfer according to the option information broadcast as described above, it is possible to obtain an output efficiently.

In the present embodiment, the control in the case where there is no free space in the hard disk has been described. However, even in the case where there is no paper in the paper cassette or output to special paper, paper size information such as a printer, a paper deck, a manual feed, etc. Broadcasting the paper presence / absence information facilitates output to a desired material.

As described above, the network printer broadcasts information on its own resources to the network, so that the network device can effectively use the resources of the printer according to the information. For this reason, for example, when the load is concentrated on a specific copier or printer, the processing can be transferred to a printer with a lighter load, thereby distributing the load over the entire system and increasing the efficiency of resources without increasing the peak performance of each printer. Can be used

[0215]

[Other Embodiments] Even if the present invention is applied to a system including a plurality of devices (for example, a host computer, an interface device, a reader, a printer, etc.), an apparatus (for example, a copying machine) Machine, facsimile machine, etc.).

Further, an object of the present invention is to supply a storage medium (or recording medium) in which program codes of software for realizing the functions of the above-described embodiments are recorded to a system or an apparatus, and to provide a computer (or a computer) of the system or apparatus. Alternatively, this can be achieved by a CPU or an MPU) reading and executing the program code stored in the storage medium. In this case, the program code itself read from the storage medium implements the functions of the above-described embodiment, and the storage medium storing the program code constitutes the present invention. By executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an operating system (OS) running on the computer based on the instruction of the program code. This also includes a case where some or all of the actual processing is performed and the functions of the above-described embodiments are realized by the processing.

Further, after the program code read from the storage medium is written in the memory provided in the function expansion card inserted into the computer or the function expansion unit connected to the computer, the program code is read based on the instruction of the program code. This also includes the case where the CPU provided in the function expansion card or the function expansion unit performs part or all of the actual processing, and the processing realizes the functions of the above-described embodiments.

When the present invention is applied to the storage medium, the storage medium stores program codes corresponding to the above-described flowcharts (shown in FIG. 15, FIG. 16, or FIG. 17). .

[0219]

As described above, the image forming apparatus broadcasts its current state to all the nodes on the network, so that the devices on the network using the state each time it uses the state. Need not be confirmed, and the procedure can be simplified. In addition, since the status of the image forming apparatus is constantly grasped by the devices on the network, the load can be easily and effectively distributed. Data transfer using the desired option can be started.

[Brief description of the drawings]

FIG. 1 is a diagram of an image network print system of the present invention.

FIG. 2 is a diagram showing a conventional office network.

FIG. 3 is a block diagram of an image data controller.

FIG. 4 is a block diagram of a raster image development card.

FIG. 5 is a block diagram of a network interface card.

FIG. 6 is a block diagram of an image network interface card.

FIG. 7 is a block diagram of a printer.

FIG. 8 is a zigzag chart showing data transfer of commands and image data between an image data controller and a printer.

FIG. 9 is a flowchart of the image data controller when transferring image data.

FIG. 10 is a diagram showing a configuration of transfer data.

FIG. 11 is a timing chart for performing print output after receiving transfer data on the printer side.

FIG. 12 shows an IEEE1394 image data controller.
It is a flowchart of a bus initialization.

FIG. 13 is a diagram of an attribute table created by the image data controller.

FIG. 14 is a diagram of an attribute table for each node on the image network.

FIG. 15 is a flowchart illustrating an operation of multicasting the status of a printer option on a network.

FIG. 16 is a flowchart when print data is transferred from an image data controller.

FIG. 17 is a flowchart when print data is transferred from the image data controller.

FIG. 18 is a diagram showing an address map of a 1394 serial bus.

FIG. 19 is a sectional view of a 1394 serial bus cable.

FIG. 20 is a diagram for describing a DS-Link coding scheme.

FIG. 21 is a flowchart showing a flow from a bus reset to a determination of a node ID.

FIG. 22 is a flowchart showing a flow of determining a parent-child relationship in a bus reset.

FIG. 23: after the parent-child relationship is determined in the bus reset,
It is a flowchart which shows the flow until a node ID is determined.

FIG. 24 is a diagram for explaining a topology setting for determining an ID of each node on a 1394 serial bus.

FIG. 25 is a diagram for explaining arbitration on a 1394 serial bus.

FIG. 26 is a flowchart for explaining arbitration.

FIG. 27 is a basic configuration diagram illustrating temporal state transition of asynchronous transfer.

FIG. 28 is a diagram illustrating an example of the format of an asynchronous transfer packet.

FIG. 29 is a basic configuration diagram showing a temporal state transition of isochronous transfer.

FIG. 30 is a diagram illustrating an example of a format of an isochronous transfer packet.

FIG. 31 is a diagram illustrating an example of a bus cycle showing a state of a packet transferred on an actual bus on a 1394 serial bus.

FIG. 32 is a diagram illustrating an example of a network configuration connected using a 1394 serial bus.

FIG. 33 is a diagram illustrating components of a 1394 serial bus.

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) B65H 39/11 B65H 39/11 K 5C062 G03G 21/00 396 G03G 21/00 396 510 510 510 G06F 3/12 G06F 3/12 ADK F term (reference) 2C061 AP01 HJ03 HJ04 HJ08 HK08 HK19 HP08 HQ20 HV01 HV09 HV13 2H027 DA50 DC12 DC14 DC18 EE08 EJ08 EJ13 EJ15 FD08 GB03 GB08 HA12 ZA07 ZA09 3F050 BD03 3 BB10 EE04 KK07 NN20 5C062 AA05 AA29 AA35 AB38 AB40 AC38 AC56 AE14

Claims (19)

[Claims] 1. An image forming apparatus connected to a communication network, wherein the state obtaining means obtains a state of the image forming apparatus, and the state obtained by the state obtaining means is transmitted to a device connected to the communication network. An image forming apparatus comprising: a transmitting unit that spontaneously transmits the state information as state information. 2. The image forming apparatus according to claim 1, wherein the transmission unit transmits the status information to all devices connected to the communication network. 3. The image forming apparatus according to claim 1, wherein the transmission unit transmits the status information at predetermined time intervals or each time the status changes. 4. The image forming apparatus according to claim 1, wherein the status information includes a status of an optional device including a staple sorter. 5. The image forming apparatus according to claim 4, wherein the status information includes at least one of a status of jam detection, presence / absence of tray paper, overloading of trays, and presence / absence of staples. 6. The storage device according to claim 1, further comprising a storage unit configured to store the received print data, wherein the status information includes information indicating a free space of the storage unit. Item 10. The image forming apparatus according to item 1. 7. The communication network according to claim 1, wherein said communication network is IEEE 139.
7. The image forming apparatus according to claim 1, wherein the transmission unit transmits the status information to a device on a network by isochronous transfer in accordance with the standard. 8. An image forming apparatus according to claim 1, receiving status information transmitted from the image forming apparatus, and using the image forming apparatus in accordance with the status information. An image forming system comprising a network device. 9. The apparatus according to claim 8, wherein the network device determines a status of an optional device of the image forming apparatus from the status information, and uses the image forming device according to a determination result. Image forming system. 10. The apparatus according to claim 8, wherein the network device determines a use state of a storage unit of the image forming apparatus from the state information, and uses the image forming apparatus according to a result of the determination. The image forming system as described in the above. 11. When the free capacity of the storage unit of the network device is insufficient, the network device determines the use state of the storage unit of the image forming apparatus from the status information, and The image forming system according to claim 10, wherein a forming device is used. 12. A method for controlling an image forming apparatus connected to a communication network, comprising: a state obtaining step of obtaining a state of the image forming apparatus; and a state obtained by the state obtaining step, wherein the state obtained by the state obtaining step is connected to the communication network. A spontaneously transmitting state information as status information to the device. 13. The method according to claim 12, wherein the transmitting step transmits the state information to all devices connected to the communication network. 14. The control method for an image forming apparatus according to claim 12, wherein the transmitting step transmits the state information at predetermined time intervals or each time the state changes. 15. The control method for an image forming apparatus according to claim 12, wherein the status information includes a status of an optional device including a staple sorter. 16. The control of the image forming apparatus according to claim 15, wherein the status information includes at least one of a status of jam detection, presence / absence of a tray paper, overloading of a tray, and presence / absence of a staple. Method. 17. The storage device according to claim 12, further comprising a storage unit configured to store the received print data, wherein the status information includes information indicating a free space of the storage unit. 13. The method for controlling an image forming apparatus according to claim 1. 18. The communication network according to claim 13, wherein said communication network is IEEE13.
The method according to any one of claims 12 to 17, wherein the transmission step transmits the status information to a device on a network by isochronous transfer according to the H.94 standard. 19. A computer-readable storage medium storing a computer program for realizing the method for controlling an image forming apparatus according to claim 12 by a computer.