JP2001309458A - Remote control system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a remote control system that can control devices with a single remote controller. SOLUTION: A video output and an audio output of a stationary VTR 10 are connected to a TV monitor 12. A camcorder 24 is connected to the stationary VTR 10 via an IEEE 1394 cable 28. A remote controller 18 is provided with an infrared signal transmission unit 20, that transmits an infrared signal to remotely control the stationary VTR 10 and the camcorder 24, and the stationary VTR 10 is provided with a unit 22, that receives the infrared ray signal from the unit 20. The remote controller 18 designates a object to be controlled and outputs a control signal thereto. The stationary VTR 10 is operated according to a received control signal, when the control object is itself and transfers the received control signal to the camcorder 24, when the camcorder 24 is a object to be controlled. The camcorder 24 is operated in accordance with the control signal transferred from the stationary VTR 10.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a remote control system, and more specifically, to a video interface, an audio signal, and a control command of a device via a digital interface (for example, IEEE1394 or the like) capable of bidirectional communication. The present invention relates to a remote control system for remotely controlling a plurality of connected devices.

[0002]

2. Description of the Related Art FIG. 15 is a schematic block diagram of a system in which a camera-integrated VTR is connected to a stationary VTR to which a TV monitor is connected via an IEEE1394 interface. 210 is a stationary VTR device, 212 is a TV monitor for displaying and outputting video / audio signals, 2
Reference numeral 14 denotes a video cable connecting the video output terminal of the stationary VTR 210 to the video input terminal of the TV monitor 212, and reference numeral 216 denotes an audio cable connecting the audio output terminal of the stationary VTR 210 to the audio input terminal of the TV monitor 212.

[0003] Reference numeral 218 denotes a remote control device for remotely controlling the stationary VTR device 210, which includes an infrared signal transmission unit 220. The stationary VTR device 210 includes an infrared signal receiving unit 2 that receives an infrared signal output from the infrared signal transmitting unit 220 of the remote control device 218.
22.

Reference numeral 224 denotes a camera-integrated VTR.
Reference numeral 226 denotes a remote control device for remotely operating the camera-integrated VTR device 224, and includes an infrared signal transmission unit 228. The camera-integrated VTR device 224 includes an infrared signal receiving unit 23 that receives an infrared signal output from the infrared signal transmitting unit 228 of the remote control device 226.
0 is provided.

[0005] Stationary VTR 210 and camera-integrated V
The TR device 224 is connected via an IEEE 1394 interface cable 232.

[0006] The video and audio recorded on the video tape loaded in the stationary VTR 210 are transferred to a camera-integrated VT.
When dubbing to a video tape loaded in the R device 224, the user uses the remote control device 218 to set the stationary VTR.
The device 210 is operated in the playback mode, and the TV monitor 212 is operated.
Remote controller 2 after confirming the image (and sound)
26 causes the camera-integrated VTR device 224 to operate in the recording mode. As a result, the video and audio signals reproduced by the stationary VTR 210 are transferred to the camera-integrated VTR 224 and recorded on the video tape of the camera-integrated VTR 224.

[0007]

In the conventional example, a stationary VT is used.
A remote control device 218 for controlling the R device 210 and a remote control device 226 for controlling the camera-integrated VTR device 224
Thus, a remote control device is required for each device, and the user has to operate the remote control device separately for the device to be controlled.

An object of the present invention is to provide a remote control system which eliminates such troubles.

[0009]

A remote control system according to the present invention includes a plurality of devices connected via an interface capable of transferring a control signal, and a control target for a predetermined device among the plurality of devices. A remote control system comprising a remote control device for supplying the specified control signal, wherein the predetermined device is a control target determining unit that determines whether a control target of a control signal from the remote control device is the own device or another device, When the control target is itself, control means for controlling each unit according to the received control signal, and when the control target is another device, control signal transfer means for transferring the received control signal to the other device. It is characterized by having.

[0010]

Embodiments of the present invention will be described below in detail with reference to the drawings.

In the embodiment of the present invention, since an IEEE 1394 serial bus is used as a digital interface for connecting each device, the IEEE 1394 serial bus will be described in advance.

With the advent of home digital VTRs and DVDs, it has become necessary to transfer data with a large amount of information such as video data and audio data in real time. An interface developed from such a viewpoint is IEEE 1394-1995 (High Pe
rformance Senal Bus). Hereinafter, it is called a 1394 serial bus.

FIG. 16 shows an example of a network system constituted by an IEEE 1394 serial bus. Equipment A, B, C, D, E, F, G, H
-B, A-C, B-D, D-E, C-F, C
-G and CH are connected by a twisted pair cable of a 1394 serial bus. These devices A to H are, for example, personal computers, digital VTRs, DVD devices, digital cameras, hard disks, monitors, and the like. According to the IEEE 1394 standard, a daisy chain method and a node branch method can be mixed as a connection method between devices, and connection with a high degree of freedom is possible.

Each of the devices A to H has its own unique ID, and recognizes each other so that the IEEE 13
One network is configured within a range connected by a 94 serial bus. In other words, only by sequentially connecting each digital device with one IEEE 1394 serial bus cable, each device plays a role of a relay and forms one network as a whole. Plug and Play (Pl), which is also a feature of the IEEE 1394 serial bus
ug & Play) function, when the cable is connected to the device, the device and the connection status are automatically recognized.

When any of the devices A to H is disconnected or a new device is connected, a bus reset is automatically executed,
The previous network configuration is reset, and a new network is rebuilt. With this function, IE
With the EE1394 serial bus, the configuration of the network can be freely changed and automatic recognition can be performed.

The data transfer rate is 100/200/40
0 Mbps is stipulated, and devices having a higher transfer rate support a lower transfer rate so that they can be connected to each other without any trouble.

The IEEE 1394 serial bus transfers asynchronous data (asynchronous data) such as control signals and real-time synchronous data (isochronous data) such as video data and audio data as data transfer modes. An isochronous transfer mode is provided. Asynchronous data and isochronous data are mixed in each cycle (usually 125 μs in one cycle), following a cycle start packet (CSP) indicating the start of a cycle, and prioritizing the transfer of isochronous data in the cycle. And transferred.

FIG. 17 is a schematic block diagram showing the configuration of the IEEE 1394 interface. The IEEE 1394 serial bus has a layer (hierarchical) structure as a whole. As shown in FIG. 17, the lowest is IEEE139.
4 is a serial bus cable having a connector port to which a connector of the cable is connected, and a physical layer and a link layer as hardware thereon.

[0019] The hardware section is substantially composed of an interface chip. The physical layer performs coding and control related to connectors, and the like, and the link layer controls packet transfer and cycle time.

The transaction layer of the firmware section manages data to be transferred (transacted) and outputs commands such as reading and writing. The serial bus management manages the connection status and ID of each connected device, and manages the configuration of the network.

The application layer of the software section differs depending on the software used. The application layer also defines how data is loaded on the interface, and is specifically defined by a protocol such as an AV protocol.

FIG. 18 is a schematic diagram of an address space in the IEEE 1394 serial bus. IEEE139
Each device (node) connected to the 4 serial bus always has a 64-bit address unique to each node. This address can refer not only to itself but also to other nodes. Thereby, communication in which the other party is specified becomes possible.

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

FIG. 19 is a sectional view of an IEEE 1394 serial bus cable. The IEEE 1394 serial bus cable has a power supply line in addition to two twisted pair signal lines. As a result, power can be supplied to a device having no power supply, a device whose voltage has been reduced due to a failure, and the like. Power line voltage is 8-40V, current is maximum current DC
It is specified as 1.5A.

Referring to FIG. 20, a DS-Link encoding system employed in the IEEE 1394 serial bus will be described. The IEEE-1394 serial bus uses DS-
A Link (Data / Strobe Link) coding scheme is employed. This DS-Link encoding method is suitable for high-speed serial data communication, and requires two signal lines. Main data is sent to one of the twisted pairs, and a strobe signal is sent to the other twisted pair.
The receiving side can reproduce the clock by taking the exclusive OR of the data and the strobe.

Advantages of using the DS-Link coding method include higher transfer efficiency as compared with other serial data transfer methods, the fact that a PLL circuit is not required, so that the circuit size of the controller LSI can be reduced. Since there is no need to send information indicating that the apparatus is in an idle state when there is no data to be transmitted, power consumption can be reduced by setting the transceiver circuit of each device to a sleep state.

FIG. 21 is a schematic diagram showing a network configuration of the IEEE 1394 serial bus. IEEE 1394
In a network, a node connected to only one node is called a leaf, and a node connected to a plurality of nodes is called a branch.

Next, the characteristic operation of the IEEE 1394 serial bus will be sequentially described. The bus reset sequence is as follows. In the IEEE 1394 serial bus, each connected device (node) is given a node ID, which is recognized as a network element. For example, when there is a change in the network configuration due to an increase or decrease in the number of nodes due to insertion / removal of a node or power on / off, etc., and it is necessary to recognize a new network configuration, each node that has detected the change places a bus on the bus. A reset signal is transmitted to enter a mode for recognizing a new network configuration. New participation in the network or withdrawal from the network is based on IEEE 139
It can be detected by a change in the bias voltage on the 4-port board.

At a node to which a bus reset signal has been transmitted from a certain node, the physical layer receives the bus reset signal, and at the same time, transmits the occurrence of a bus reset to the link layer and transmits the bus reset signal to another node. I do. After all the nodes finally detect the bus reset signal, the bus reset is activated. The bus reset may be started by hardware detection due to cable insertion / removal and network abnormality, or may be started by directly issuing a command to the physical layer by host control from a protocol or the like.

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 sequence for determining the node ID will be described.
After the bus reset, each node gives each node an ID to build a new network configuration. A general sequence from the bus reset to the determination of the node ID will be described with reference to FIGS. 22, 23, and 24.

FIG. 22 shows a flowchart of a series of bus operations from the occurrence of a bus reset to the determination of the node ID and the start of data transfer. The occurrence of a bus reset in the network is constantly monitored (S1). When a bus reset occurs due to power on / off of any of the nodes (S1), in order to know the connection status of a new network from the network reset state,
A parent-child relationship is declared between the connected nodes (S2). When the parent-child relationship is determined between all nodes (S3), one route is determined (S4). When the route is determined (S4), IDs are sequentially set for all nodes in a predetermined node order (S5, S6). When IDs are set for all nodes (S6), all nodes are set. Has recognized the new network configuration, and is ready for data transfer between nodes, and data transfer is started (S7). After S7, the process returns to S1, and the bus reset is monitored again.

FIG. 23 is a detailed flowchart of the processing from the bus reset to the determination of the route. When a bus reset occurs (S11), the network configuration is reset once. As a first step of re-recognizing the reset network connection status, a flag indicating a leaf (node) is set for each device (S12). Each device checks how many ports of its own are connected to other nodes (S13). According to the number of ports connected to other nodes, the number of undefined (parent-child relationship is not determined) ports is examined in order to start the declaration of the parent-child relationship from now on. Immediately after the bus reset, the number of ports connected to other nodes is equal to the number of undefined ports, but the number of undefined ports decreases as the parent-child relationship is determined.

Immediately after a bus reset, only the leaves can declare a parent-child relationship first. The leaf declares to the node connected thereto that it is a child and the other party is a parent (S15).

Since the number of undefined ports is 2 or more immediately after the bus reset (S14), the node which is a branch sets a flag of branch (S16).
Wait for the parent's notice in the parent-child relationship declaration from the leaf (S1
6). When the parent's notice is received, the number of undefined ports decreases by 1,
It returns to S14. While the number of undefined ports is 2 or more, S1
6. Repeat S17.

When the number of undefined ports becomes 1 (S1
4) It is possible to declare itself as a child to a node connected to the remaining port (S1).
5). Finally, a node having an undefined port number of 0 (for example, any one branch or exceptionally a leaf (a leaf that could not be declared as a child because it did not operate quickly even though a child could be declared)). ) (S14), the route flag is set (S18), and the route is recognized as a route (S14).
19).

In this way, after the bus reset, the parent-child relationship is established between all nodes in the network.

FIG. 24 is a flowchart showing the procedure from the determination of the route to the end of the ID setting. First, according to the sequence shown in FIGS. 22 and 23, each node
Assigned to leaf, branch or root. The processing differs depending on which one is used (S21). ID first
Can be set for a leaf, and IDs are set in ascending order of the leaf, branch, and route (node number = 0).

The number N of leaves existing in the network
(N is a natural number) is set (S22). Each leaf requests the root to give an ID (S23). If there are multiple requests, the route arbitrates these requests (S24) and gives the winning node an ID number,
The losing node is notified of the result of the failure (S25).
The leaf that failed to acquire the ID sends an ID request to the root again, and repeats the same operation (S26, S23). I
The leaf that has acquired D broadcasts the acquired ID information to all nodes (S27), and leaves counter N
Is reduced by 1 (S28). Until N becomes 0 (S29),
S23, S26, S27 and S28 are repeated.

Finally, all leaves broadcast ID information (S27), and when N = 0 (S28),
Shift to branch ID setting. The setting of the branch ID is the same as that of the leaf. That is, the number M of branches existing in the network (M is a natural number) is set (S3).
0). Each branch requests the root to give an ID (S31). If there are multiple requests, the root arbitrates these requests (S32), and the one node that won wins the I following the ID previously set on the leaf or branch.
A D number is given, and the losing node is notified of the failure result (S33). The branch for which ID acquisition failed,
An ID request is sent to the root, and the same operation is repeated (S3
4, S31). The branch that has acquired the ID broadcasts the acquired ID information to all nodes (S3).
5) The branch counter M is decremented by 1 (S36). Until M becomes 0 (S37), S31, S34, S35, S
Repeat 36.

M = 0, that is, all branches are nodes I
When D is acquired (S37), the root acquires the ID following the ID given to the leaf or branch immediately before as its own ID (S38), and broadcasts it to all other nodes (S39).

In this way, the parent-child relationship is determined between all nodes connected to the network, and the IDs of all nodes are determined.

In the example of the network configuration shown in FIG. 21, the node B is the root. Nodes A and C are directly connected below the node B, nodes D are directly connected below the node C, and nodes E and F are directly connected below the node D. A procedure for determining a root node and a node ID in this hierarchical structure will be described. After the bus reset, first, in order to recognize the connection status of each node, a parent-child relationship is declared between the directly connected ports of each node. In this parent-child relationship, the upper level of the hierarchical structure is the parent, and the lower level is the child.

In FIG. 21, it is the node A that first declares the parent-child relationship after the bus reset. Basically, 1
A node (leaf) in which a node connects to only one port can declare the parent-child relationship first. The leaf is obviously located at the edge of the network. Is recognized, and the parent-child relationship is determined from the node that operates earlier in that. Node (AB) declaring parent-child relationship
Between them, the port of the node A) is set as a child, and the port of the other side (node B) is set as a parent. Thus, a child-parent is determined between nodes AB, a child-parent is determined between nodes ED, and a child-parent is determined between nodes FD.

Further up in the hierarchy, this time, among nodes (branches) having a plurality of connection ports, a parent-child relationship is declared further higher in order from a node that has received a declaration of a parent-child relationship from another node. Go. In FIG. 21, first, the parent-child relationship between the node D is determined between DE and DF, and then the parent-child relationship for the node C is declared. As a result, node D-
A child-parent is determined between C. The node C that has received the declaration of the parent-child relationship from the node D declares the parent-child relationship to the node B connected to another port. As a result, a child-parent is determined between the nodes CB.

In this way, the hierarchical structure of the parent-child relationship as shown in FIG. 21 is determined. The node B that has become the parent in all finally connected ports becomes the root node. There is only one route in one network configuration.

If the node B that has received the parent-child relationship declaration from the node A has declared the parent-child relationship with another node C at an early timing, the node C may become the root. That is, depending on the timing of the parent-child declaration, there is a possibility that another node C or D may become the root, and the root node is not always constant even in the same network configuration.

After the root node is determined, the ID of each node is determined next. All nodes notify their determined node IDs to all other nodes (broadcast function). The information to be broadcast includes its own node number, information on the connected position, the number of ports it has, the number of ports it has connected, and information on the parent-child relationship of each port.

The procedure for assigning a node ID to each node is as follows:
As described above. That is, a number that increases in order from node number = 0 is assigned to each leaf node, and then a node number that follows each branch is assigned. The root owns the highest node ID number.

In this way, the node I of the entire hierarchical structure
The assignment of D is completed, the network configuration is reconstructed, and the bus initialization operation is completed.

Next, arbitration processing of the bus use right will be described. In the IEEE 1394 serial bus, the right to use the bus is always arbitrated prior to data transfer. The IEEE 1394 serial bus forms a logical bus-type network that transmits the same signal to all devices in the network by each device relaying the transferred signal, so arbitration is necessary to prevent packet collision. Becomes This allows only one node to transfer data at any given time.

The relationship between the request for the right to use the bus and the permission for the request is shown in FIGS. When arbitration begins, one or more nodes request a bus right towards the parent node. In FIG. 25, nodes C and F are nodes requesting the right to use the bus. The parent node (node A in FIG. 25) receiving the request further requests (ie, relays) the right to use the bus toward the parent node. This request is finally delivered to the route.

The root node that has received the bus use right request is
Determine which nodes will use the bus. This arbitration is the exclusive responsibility of the root node,
The node that has won the arbitration is granted bus use permission. In FIG. 26, use permission is given to the node C, and use of the node F is denied. The route sends a data prefix (DP) packet to the node that has lost arbitration to indicate that the request to bus has been rejected. The rejected node's request to use the bus is waited for the next arbitration.

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

FIG. 27 shows a detailed flowchart of the arbitration process. Before a node can initiate a data transfer,
The bus must be idle. In order to recognize that the bus is currently idle after the data transfer that has been performed earlier is completed, a predetermined idle time gap length (for example, a sub-action・ It is only necessary to wait for the gap to elapse.
It is confirmed whether or not a time corresponding to a predetermined gap length according to transfer data such as asynchronous data and synchronous data has elapsed (S41). This is because a request for the right to use the bus required to start the transfer cannot be issued unless the time corresponding to the gap length has elapsed.

When the time corresponding to the predetermined gap length has elapsed (S41), it is determined whether there is data to be transferred (S42). If there is data (S42), a bus use right is requested to the route (S43). This bus use right request signal 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 (S42), the process stands by.

Upon receiving one or more bus use right request signals (S44), the route checks the number of nodes requesting the bus use right (S45). If the number of nodes requesting the right to use the bus is 1, the node is permitted to immediately use the bus, and a permission signal is transmitted to the node (S48).
When the number of requests for the bus use right is plural (S4
5), the route determines one node that is permitted to use the bus (S46). This arbitration work does not always obtain permission from the same node, but is a fair one in which each node is given equal rights.

A permission signal is transmitted to one of the nodes which have requested the bus use right from the plurality of nodes whose use has been permitted by the root (S47, S48). The node permitted to use the bus starts transferring data (packets) immediately after receiving the permission signal.

A DP (data prefix) packet indicating arbitration failure is transmitted to the other nodes that have lost arbitration (S47, S49). The node that has received the DP packet returns to S41 and requests the right to use the bus again.

The asynchronous (asynchronous) transfer mode will be described. FIG. 28 shows the time transition of the asynchronous transfer. Subaction Gearup (subaction)
(gap) indicates an idle state of the bus. A node desiring to transfer determines that the bus can be used when the idle time reaches a fixed value, and requests a bus use right. The node permitted to use the bus in the arbitration sends data to the bus in a predetermined packet format. The node that has received the data returns a response code ack indicating the reception result of the transferred data after a short gap (ack gap) and returns a response or sends a response packet. This completes one unit of data transfer. The acknowledgment return code ack is made up of 4-bit information and a 4-bit checksum, and is used to notify the transmission source node of information indicating any of a success, a busy state, and a pending state.

FIG. 29 shows a packet format of the asynchronous transfer. The packet includes a header section, a data section, and data CRC for error correction. As shown in FIG. 29, the header section includes a destination node ID, a source node ID, a transfer data length, various codes, and the like.

Asynchronous transfer is one-to-one data transfer from one node to another node. Although the packet output from the transfer source node reaches each node in the network, each node ignores data other than its own. As a result, the data is taken in only one destination node.

The isochronous (synchronous) transfer mode will be described. The isochronous transfer mode is IEEE1394
It can be said that this is the biggest feature of the serial bus. The isochronous transfer mode is particularly suitable for transferring data that requires real-time transfer, such as video data and audio data. While the asynchronous transfer mode is a one-to-one data transfer, the isochronous transfer mode can transfer data from one transfer source node to all other nodes by using a broadcast function.

FIG. 30 shows a temporal transition in the isochronous transfer. The isochronous transfer is executed on the bus at regular intervals. This time interval is called an isochronous cycle. Isochronous cycle time is 125
μs. The cycle start packet indicates the start timing of each cycle and adjusts the time of each node. It is the cycle master that transmits the cycle start packet. After a predetermined idle period (subaction gap) has elapsed after the end of the transfer in the previous cycle, a cycle start packet indicating the start of the cycle. Send The time interval between the cycle start packet and the next cycle start packet is 125 μs.

As shown in FIG. 30 as channel A, channel B and channel C, a plurality of packets can be distinguished and transferred within one cycle by giving each packet a different channel ID. Thereby, data can be transferred in real time between nodes of different combinations at the same time.
Each node takes in only the data of the channel ID desired by itself. The channel ID does not represent a destination address, but merely gives a logical number to data. Thus, such a packet is broadcast from one source node to all other nodes.

Prior to the packet transmission of the isochronous transfer, the arbitration of the right to use the bus is performed as in the case of the asynchronous transfer. However, since the isochronous transfer is not one-to-one communication like the asynchronous transfer, there is no acknowledgment reply code ack in the isochronous transfer.

The isochronous gap is shown in FIG.
o gap indicates an idle period necessary for recognizing that the bus is idle before performing isochronous transfer. A node desiring isochronous transfer determines that the bus is free after this idle period, and outputs a bus use right request signal.

FIG. 31 shows a packet format of the isochronous transfer. The packet includes a header portion, a data portion, and data CRC for error correction. The header part is
As shown in FIG. 31, it has a transfer data length, a channel number, other various codes, and an error correction header CRC.

A bus cycle of the IEEE 1394 serial bus will be described. On the IEEE 1394 serial bus, isochronous transfer and asynchronous transfer can coexist. FIG. 32 shows a temporal transition of the transfer state on the bus when the isochronous transfer and the asynchronous transfer are mixed.

After the cycle start packet, the gap length in the idle period required to start the isochronous transfer (isochronous gap) is determined by the gap length in the idle period required to start the asynchronous transfer (subaction gap). In this case, the isochronous transfer is performed prior to the asynchronous transfer. This enables real-time transfer of image data or audio data by asynchronous transfer.

In the general bus cycle shown in FIG. 32, at the start of cycle #m, the cycle start
Packets are transferred from the cycle master to each node. As a result, the time is adjusted at each node. A node that intends to transfer data isochronously waits for a predetermined idle period (isochronous gap), requests and acquires the right to use the bus, and then transmits a packet onto the bus. In FIG. 32, the channel e, the channel s, and the channel k are sequentially and isochronously transferred. These three
After repeating the arbitration and the packet transfer for the channel, that is, when all the isochronous transfers in the cycle #m are completed, the asynchronous transfer becomes possible.

The node desiring asynchronous transfer is
After waiting for a time corresponding to a subaction gap in which an asynchronous transfer is possible, a request for the right to use the bus is made to the root. However, after the end of the isochronous transfer, the next cycle start packet (cycle sy
Asynchronous transfer is possible only when a sub-action gap for activating asynchronous transfer can be entered before nc). In cycle #m shown in FIG. 32, isochronous transfer for three channels,
Thereafter, asynchronous transfer (including ack) of two packets is performed. After the second asynchronous packet, a timing (cycle sync) at which the cycle # (m + 1) is to be started is reached, so that the transfer in the cycle #m ends here.

However, if the next cycle start packet CSP is reached during the asynchronous transfer or the isochronous transfer operation, the cycle master does not forcibly interrupt the transfer and sets an idle period after the transfer is completed. After waiting, a cycle start packet for the next cycle is output. In the next cycle, the start of the cycle is delayed,
Make the cycle end earlier. That is, one cycle is 12
If it lasts for 5 μs or more, the next cycle is shortened accordingly by 125 μs. In this way, IEEE13
The cycle time of the 94 bus can be exceeded or reduced on the basis of 125 μs. The isochronous transfer is always performed if necessary every cycle to maintain the real-time transfer. However, the asynchronous transfer may be transferred to the next and subsequent cycles due to the shortened cycle time. A cycle master manages the cycles on the bus, including this type of delay information.

FIG. 1 is a schematic block diagram of the first embodiment of the present invention. 10 is a stationary VTR device, 12 is a TV monitor for displaying and outputting video / audio signals, 14
Is the video output terminal of the stationary VTR 10 and the TV monitor 1
Video cable to connect two video input terminals, 16
Is an audio cable for connecting an audio output terminal of the stationary VTR 10 and an audio input terminal of the TV monitor 12.

Reference numeral 18 denotes a remote control device for remotely controlling the stationary VTR device 10, and an infrared signal transmission unit 20.
Is provided. The stationary VTR device 10 is a remote control device 1
8 is provided with an infrared signal receiving unit 22 for receiving an infrared signal output from the infrared signal transmitting unit 20.

Reference numeral 24 denotes a camera-integrated VTR having an infrared receiving unit 26 for receiving an infrared control signal from a remote controller (not shown). However, in this embodiment, the infrared receiving unit 26 is not used.

Stationary VTR 10 and Camera-integrated VT
The R device 24 is connected via an IEEE 1394 interface cable 28.

FIG. 2 is a plan view of an example of the remote controller 18. Reference numeral 30 denotes a switch for designating a control target. In this example, a stationary VTR device 10 and a camera-integrated VTR
The device 24 can be selected as a control target. 32 is V
A VTR operation key for operating the TR devices 10 and 24.

FIG. 3 shows an example of the content of an infrared control signal output from the remote controller 18 in response to the operation of the reproduction key of the VTR operation key 32. When the stationary VTR device 10 is selected by the switch 30, the remote controller 18 instructs reproduction as the control content in a header that specifies the stationary VTR device 10 as a control target, as shown in FIG. The control data is output continuously. When the camera-integrated VTR device 24 is selected by the switch 30,
As shown in FIG. 3 (2), the remote control device 18 continuously outputs control data for instructing reproduction as control content to a header specifying the camera-integrated VTR device 24 as a control target.

FIG. 4 is a schematic block diagram of the stationary VTR device 10. As shown in FIG. 40 is a rotary drum and magnetic tape mechanical system, 42 is a TV tuner, 44 is a video signal processing circuit, 46 is an audio signal processing circuit, and 48 is a mechanical system 4
0, a stationary VTR device 10 including a TV tuner 42, a video signal processing circuit 44, and an audio signal processing circuit 46.
A main control circuit (microcomputer) for controlling the entire system, 50 is a command control circuit (microcomputer) for processing control commands exchanged with the outside
It is. The command control circuit 50 also communicates with the main control circuit 48.

Reference numeral 52 denotes an output terminal of the video signal processed by the video signal processing circuit 44; 54, an output terminal of the audio signal processed by the audio signal processing circuit 46;
Is a remote control signal receiving unit that receives an infrared signal transmitted from the infrared remote control device and supplies the infrared signal to the main control circuit 48.

Reference numeral 58 denotes a multiplexer for time-division multiplexing and demultiplexing a video signal packet, an audio signal packet, and a command packet in accordance with the IEEE 1394 communication protocol; 60, an IEEE 1394 interface circuit; and 62, an IEEE 1394 connection terminal.

FIG. 5 is a schematic block diagram of the camera-integrated VTR 24. 70 is a mechanical system of a rotating drum and a magnetic tape, 72 is an imaging unit including a photographing lens and an imaging element, 74 is a camera signal processing circuit for processing an image signal output from the imaging unit 72, 76 is a video signal processing circuit, 78 Is a microphone, 80 is an audio signal processing circuit, 82 is a mechanism system 70, a camera signal processing circuit 74,
Video signal processing circuit 76 and audio signal processing circuit 8
A main control circuit (microcomputer) 84 for controlling the whole of the camera-integrated VTR device 24 including 0, a command control circuit (microcomputer) 84 for processing control commands exchanged with the outside. The command control circuit 84 also communicates with the main control circuit 82.

Reference numeral 86 denotes a multiplexer for time-division multiplexing of video signal packets, audio signal packets, and command packets in accordance with the IEEE 1394 communication protocol, 88 denotes an IEEE 1394 interface circuit, and 90 denotes an IEEE 1394 connection terminal.

The connection terminal 62 in FIG. 4 and the connection terminal 90 in FIG.
Are connected by an IEEE 1394 cable. Thereby, the stationary VTR device 10 and the camera-integrated VTR device 2
4 can mutually communicate video signals, audio signals, control commands, and the like.

FIG. 6 is a flowchart showing the operation of the main control circuit 48. The main control circuit 48 monitors the output signal of the remote control signal light receiving unit 56 and waits for reception of the remote control signal (S51). When a remote control signal is received (S5
1) From the header included in the remote control reception signal, it is determined whether the device to be controlled is itself (stationary VTR device 10) or another device (camera-integrated VTR device 24) (S52).
If the control target is itself (S52), the content of the control command is determined (S53), and each unit is operated with the content corresponding to the control command (S54). If the control target is another device (S52), the command control circuit 50 is instructed to transmit the control command to the control target via the IEEE 1394 interface 60 (S55).

FIG. 7 is a flowchart showing the operation of the command control circuit 50 in response to the command of S55. In response to the transmission command from the main control circuit 48, the command control circuit 50 first checks the operation state of the camera-integrated VTR device 24 to be controlled (S56). If it is determined from the confirmed operation mode state that the commanded control command can be transmitted, command transmission by IEEE 1394 is immediately started (S57).

FIG. 8 is a flowchart showing the operation of the command control circuit 84 of the camera-integrated VTR 24. The command control circuit 84 receives a control command from the stationary VTR device 10 via the IEEE 1394 interface 88 (S61) and transmits it to the main control circuit 82 (S61).
62). The main control circuit 82 controls each unit according to the content of the received control command.

As described above, the stationary VTR device 10 or the camera-integrated VTR device 24 finally operates according to the content specified by the user with the remote controller 18.

FIG. 9 is a schematic block diagram showing a second embodiment of the present invention. In this embodiment, the stationary VTR device 112 and the camera-integrated VTR device 1
14 are connected via IEEE 1394 interface cables 116 and 118, respectively. Remote control device 1
20 includes an infrared signal transmitting unit 122, and the TV monitor 110 includes an infrared signal receiving unit corresponding to the unit 122.

FIG. 10 is a plan view of an example of the remote control device 120. 130 is a switch for designating a control target. In this example, the TV monitor 110, the stationary VTR device 112, and the camera-integrated VTR device 114 can be selected as control targets. 132 is a VTR device 112,1
14 is a VTR operation key for operating the VTR 14. 134 is a TV
These are tuner operation keys for operating the channel and volume of the TV tuner of the monitor 110 and the stationary VTR device 112.

FIG. 11 shows an example of the content of an infrared control signal output by remote control device 120 when the channel key of the tuner operation key is operated. When the stationary VTR device 112 is selected by the switch 130, the remote control device 120 instructs, as shown in FIG. 11A, a channel switch as a control content in a header for specifying the stationary VTR device 112 as a control target. Control data to be output. TV monitor 11 by switch 130
0 is selected, the remote control device 120
As shown in FIG. 1 (2), the TV monitor 11
Control data for instructing channel switching is output as a control content to a header designating 0.

FIG. 12 is a schematic block diagram of the TV monitor 110. 140 is a TV tuner, 142 is a video signal processing circuit, 144 is an audio signal processing circuit, 1
46 is a TV tuner 140, a video signal processing circuit 14
A main control circuit (microcomputer) 148 that controls the entire TV monitor 110 including the audio signal processing circuit 144 and the audio signal processing circuit 144 is a command control circuit (microcomputer) that processes control commands exchanged with the outside. The command control circuit 148 is the main control circuit 14
Also communicate with 6.

Reference numeral 150 denotes a CRT for displaying an image of the video signal processed by the video signal processing circuit 142; 152, a speaker for outputting the audio signal processed by the audio signal processing circuit 144 as sound;
0, and receives the infrared signal transmitted from the main control circuit 14.
6 is a remote control signal receiving unit to be supplied to the remote controller 6

Reference numeral 156 denotes a multiplexer for time-division multiplexing and demultiplexing a video signal packet, an audio signal packet, and a command packet in accordance with the IEEE 1394 communication protocol; 158, an IEEE 1394 interface circuit; and 160 and 162, IEEE 1394 connection terminals.

The stationary VTR device 112 has the same configuration as that shown in FIG.
Has the same configuration as that shown in FIG. TV monitor 1
10 connection terminal 160 is an IEEE 1394 cable 1
IEEE 139 of the stationary VTR device 112 via the
4 connection terminal, and the connection terminal 16 of the TV monitor 110
2 is connected to an IEEE 1394 connection terminal of the camera-integrated VTR device 114 via an IEEE 1394 cable 118.

FIG. 13 is a flowchart showing the operation of the main control circuit 146. The main control circuit 146 monitors the output signal of the remote control signal light receiving unit 154 and waits for reception of the remote control signal (S71). When a remote control signal is received (S71), it is determined from the header included in the remote control signal whether the device to be controlled is itself (TV monitor 110) or another device (stationary VTR device 112 or camera-integrated VTR device 114). (S72). If the control target is itself (S72), the content of the control command is determined (S73), and each unit is operated with the content corresponding to the control command (S74). If the control target is another device (S7
2), using the control command as an object to be controlled
The command control circuit 148 is instructed to transmit the data via the interface 158 (S75).

FIG. 14 is a flowchart showing the operation of the command control circuit 148. In response to a command transmission command from the main control circuit 146, a control target is determined (S81).
If the control target is the stationary VTR device 112 (S8
1) The operation state is confirmed (S82), and if the instructed control command can be transmitted, the control command is transmitted to the stationary VTR device 112 (S83). When the control target is the camera-integrated VTR device 114 (S
81), the operation state is confirmed (S84), and if the instructed control command can be transmitted, the control command is transmitted to the camera-integrated VTR device 114 (S8).
5).

The stationary VTR device 112 or the camera-integrated VTR device 114 that has received the control command shifts to an operation mode according to the operation of the user.

[0100]

As can be easily understood from the above description, according to the present invention, a controlled device that has received a control signal determines whether or not itself is a control target, and determines that the controlled device itself is a control target. If there is, it operates according to the control content, and when another device is a control target, a control signal is transferred to the other device, so that a single remote control device remotely controls or operates a plurality of devices. be able to.

[Brief description of the drawings]

FIG. 1 is a schematic block diagram of a first embodiment of the present invention.

FIG. 2 is a plan view of the remote control device 18. FIG.

FIG. 3 is an example of the content of an infrared control signal output by a remote controller 18 in response to an operation of a playback key of a VTR operation key 32;

FIG. 4 is a schematic block diagram of the stationary VTR device 10;

FIG. 5 is a schematic block diagram of a camera-integrated VTR device 24;

6 is an operation flowchart of the main control circuit 48. FIG.

FIG. 7 is an operation flowchart of the command control circuit 50 in response to the command of S5.

FIG. 8 is an operation flowchart of the command control circuit 84;

FIG. 9 is a schematic configuration block diagram of a second embodiment of the present invention.

10 is a plan view of the remote control device 120. FIG.

FIG. 11 shows an example of the content of an infrared control signal output by the remote control device 120 when a channel key of the tuner operation key 134 is operated.

FIG. 12 is a schematic configuration block diagram of a TV monitor 110.

FIG. 13 is an operation flowchart of the main control circuit 146.

FIG. 14 is an operation flowchart of the command control circuit 148.

FIG. 15 is a schematic configuration block diagram of a conventional example.

FIG. 16 is an example of a network system configured by an IEEE 1394 serial bus.

FIG. 17 is a schematic block diagram of an IEEE 1394 interface.

FIG. 18 is a schematic diagram of an address space in an IEEE 1394 serial bus.

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

FIG. 20 is a timing chart of the DS-Link encoding method adopted in the IEEE 1394 serial bus.

FIG. 21 is a schematic diagram of a network configuration of an IEEE 1394 serial bus.

FIG. 22 is a flowchart of a series of bus operations from when a bus reset occurs to when a node ID is determined and data transfer can be performed.

FIG. 23 is a detailed flowchart of a process from bus reset to route determination.

FIG. 24 is a flowchart of a procedure from the determination of a route to the end of ID setting.

FIG. 25 is an explanatory diagram of a transmission path of a bus use right request signal.

FIG. 26 is an explanatory diagram of a transmission path of a bus use permission signal and a rejection signal.

FIG. 27 is a detailed flowchart of the arbitration process.

FIG. 28 is a schematic diagram of time transition of asynchronous transfer.

FIG. 29 is a schematic diagram of a packet format of asynchronous transfer.

FIG. 30 is a schematic diagram of time transition in isochronous transfer.

FIG. 31 is a schematic diagram of a packet format for isochronous transfer.

FIG. 32 is a schematic diagram of a time transition of a transfer state when isochronous transfer and asynchronous transfer are mixed.

[Explanation of symbols]

10: Stationary VTR device 12: TV monitor 14: Video cable 16: Audio cable 18: Remote control device 20: Infrared signal transmitting unit 22: Infrared signal receiving unit 24: Camera-integrated VTR device 26: Infrared receiving unit 28: IEEE1394 interface Cable 30: Control target designation switch 32: VTR operation key 40: Mechanical system 42: TV tuner 44: Video signal processing circuit 46: Audio signal processing circuit 48: Main control circuit 50: Command control circuit 52: Video signal output terminal 54: Audio signal output terminal 56: Remote control signal receiving unit 58: Multiplexer 60: IEEE 1394 interface circuit 62: IEEE 1394 connection terminal 70: Mechanical system 72: Imaging unit 74: Camera signal processing circuit 76: Video signal processing circuit 78: Microphone 80: Audio signal processing circuit 82: Main control circuit 84: Command control circuit 86: Multiplexer 88: IEEE 1394 interface circuit 90: IEEE 1394 connection terminal 110: TV monitor 112: Stationary VTR device 114: Camera Integrated VTR devices 116, 118: IEEE 1394 interface cable 120: Remote control device 122: Infrared signal transmission unit 124: Infrared signal reception unit 130: Control target designation switch 132: VTR operation key 134: Tuner operation key 140: TV tuner 142: Video Signal processing circuit 144: audio signal processing circuit 146: main control circuit 148: command control circuit 150: CRT 152: speaker 154: remote control signal reception Unit 156: Multiplexer 158: IEEE 1394 interface circuit 160, 162: IEEE 1394 connection terminal 210: Stationary VTR 212: TV monitor 214: Video cable 216: Audio cable 218: Remote controller 220: Infrared signal transmission unit 222: Infrared signal reception Unit 224: Camera-integrated VTR device 226: Remote control device 228: Infrared signal transmitting unit 230: Infrared signal receiving unit 232: IEEE 1394 interface cable

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) H04N 5/765 H04N 5/782 K 5/7826 Z F-term (Reference) 5C018 FA02 FA04 HA08 HA11 5C022 AC01 AC72 AC75 AC79 5C056 AA05 BA01 BA08 DA11 EA06 KA01 5K033 AA02 BA15 CB08 DA13 5K048 AA13 BA02 DA02 DA05 DA07 DB04 DC04 EA14 EB02 GC02 HA01 HA02 HA32

Claims (3)

[Claims] 1. A remote control comprising: a plurality of devices connected via an interface capable of transferring control signals; and a remote control device for supplying a control signal specifying a control target to a predetermined device among the plurality of devices. A control system,
The predetermined device is a control target determining unit that determines whether a control target of a control signal from the remote control device is the own device or another device,
When the control target is itself, a control unit that controls each unit according to the received control signal, and when the control target is another device, a control signal transfer unit that transfers the received control signal to the other device. A remote control system, comprising: 2. The remote control system according to claim 1, wherein the remote control device includes a control target specifying unit that specifies a control target. 3. The interface is an IEEE 139
The remote control system according to claim 1, wherein the remote control system has four interfaces.