Our previous application Ser. No. 11/190,494 filed Jul. 27, 2006, is formed of a rolling rack which holder breaker modules that provide power that is sent over a cable to breakout boxes. The same rack can handle many different kinds of power, e.g., 115 and 220, as well as multiple different phases etc. The safety systems in the rack prevent the wrong voltage from being applied to the breakout boxes. An interlock system only supplies power after all connections are made, thereby protecting workers against being shocked during installation.
The present application describes a special communication system added to the power switch.
A breaker module such as 104 is connected via a trunk cable 108 to a breakout box. Each breakout box such as 110 includes a number of outlets 112 thereon. The outlets 112 are configured for a certain kind of power. Power is only supplied through the trunk cable 100 when an appropriate breakout box for the outlets is properly attached. That is, if the outlets such as 112 are configured to supply 115 V power, e.g., they have the form and layout of a 115 V power socket, then power will only be supplied when 115 V is available on the trunk cable 108. The operation of this system is also described in our co-pending application, described above.
In addition,
In addition, each breaker module may include connections for multiple different DMX channels 210, and multiple different Ethernet ports 215. Each of these data channels also includes at least one status indicator. In this embodiment, the DMX channel 210 includes LEDs 211 that indicate valid DMX receive, RDM receive, and transmit. The Ethernet connectors 215 have associated LEDs 216 which indicate Ethernet link, transmit and receive.
There are also separate trunk LEDs 220 that indicate valid trunk data link and data flow.
Hence the front of house breakout module allows connection to and powering of multiple different controlling consoles. Each console can be connected to one of the inputs 420, 422, and can be controlled, e.g., to determine a universe for the data from that console.
The control can be carried out using interface controller 424 and its associated display 426 as described herein.
The breakout module includes a number of outlets which may include both 115 v outputs such as 402 as well as 208 v outlets 404. This facilitates powering both voltages of consoles that may connect to the module.
The front of house breaker module that connects to and provides power for the FOH breakout module, is shown in
Front of house AB switch is shown in
As an example of operation, two universes from a primary console could be input into the front of house breakout module. These two universes are labeled as 0a and 1a. The 0 and 1 represent the universe, and the “a” designation represents the specific console that is connected.
Two mirrored universes could be added from a backup console. These mirrored universes are labeled 0b and 1b, 0 and 1 for the universe designation, and b for the backup console. Universes from both consoles are active on the network all the time. This makes it possible to verify that both consoles are running by simply checking the system status. The third system C may be used for additional inputs such as a tech console.
The AV switch, which is in fact a virtual switch and not a real switch, indicates the current system state using its backlit selector switches even if this has been changed elsewhere.
The breaker modules and racks can accept a number of different kinds of inputs, and can route them to various outputs using the user interface and the menu display. For example, this accepts Ethernet, DMX 512 as well as DMX 512 over Ethernet. Each of these protocols can be handled simultaneously. Different systems can also be used, where each input from each system may be individually numbered, e.g., A, B, and C, depending on the system that sends it. Therefore, there may be multiple different consoles each connected to a specified universe. For example, with three consoles each connected to universe 0, console A is labeled universe 0a, console B is universe 0B, etc. Any of the consoles can be selected as a default at any moment.
The breakout box can be mounted in one of several different ways.
The menu display 205 on the data system can used to configure, test and access the internal status information. The button bar soft programmable buttons 260 as shown in
Exemplary menus that can be displayed on the unit may include:
Input/Output Summary
Different menus may have different functions. The input output summary menu shows the configuration of the DMX rack inputs and the DMX outputs on each of the trunk breakout boxes.
The source default is system a, as shown by the last line of the input summary which shows SRC: a.
Similarly, the front of house module can have an I/O summary as shown in
This shows the configuration of the 10 DMX 512 rack inputs, and the two outputs 000 and 001. Each input universe has a letter which indicates which of the three sources is being used for that universe. For example, 001a indicates that universe 1 is associated with source a. Again, source a is the current default in this picture.
The rack inputs have a menu shown in
That can be configured by highlighting the universe and selecting either the up menu or the down menu. When finished, “done” can be pressed to confirm that a proper operation is completed. In a similar way, the front of house inputs can be configured as shown in
And the rack inputs can be configured as shown in
Source selection shows the number of modules on the network that are currently using each input system as its default. A highlighted source is the current source for the module, which can be changed by selecting a, b or c from the last row of the menu as shown in
A system overview screen is shown in
The system universes display shows the universes that are active on the network as shown in
Up to four universes can be displayed at any one time. Each display shows the universe number (here 0000), and the source (here b), the module where that universe is defined as an input (here rack 250) and the port for that input to be connected (here port zero). The left and right arrows allow different universes to be displayed.
Different operations can also be carried out in an analogous way, including defining system racks and front of house, defining the name display configuration reset and light options.
The DMX monitors shows the current data for a DMX universe as shown in
The DMX universe number is shown in the title here 000b. The “next” key triggers to the next universe. The first number of each line is the channel offset, followed by the five channels of data.
According to an embodiment, each of the DMX inputs receive a system identifier which is a letter a, b or c, in addition to a universe number which can be in this embodiment between 0 and 255. The input receives system and universe, but the output only has a universe number; thereby enabling control by whatever hardware is selected as active to create and control that universe. Each DMX output transmits its assigned universe for the currently active system.
The active system can be selected from the AB switch box or from any menu. The AB switch can be connected to any desired breakout box anywhere in the system, since it is a logical, not physical switch.
An advantage of this system is that it enables multiple universes to be controlled from multiple different consoles. For example, two universes can be controlled from the primary console into the front of house breakout box. These two universes can be labeled as 0a and 1a. Two other mirrored universes can be used from the backup console labeled 0b and 1b. Since the universe numbers on these are the same, they both carry the same universe of information. However, the system information is different. All universes are active at all times. When system a is selected, console a controls the universe by sending universes 0a and 1a; while system b is controllable via the switch to allows sending universes 0b and 1b.
Although only a few embodiments have been disclosed in detail above, other embodiments are possible and the inventors intend these to be encompassed within this specification. The specification describes specific examples to accomplish a more general goal that may be accomplished in another way. This disclosure is intended to be exemplary, and the claims are intended to cover any modification or alternative which might be predictable to a person having ordinary skill in the art. For example, other commands and command forms can be used. DMX is listed as the preferred command format, but any other format, and specifically any time-division multiplexed format could be used for this control.
Also, the inventors intend that only those claims which use the words “means for” are intended to be interpreted under 35 USC 112, sixth paragraph. Moreover, no limitations from the specification are intended to be read into any claims, unless those limitations are expressly included in the claims. The computers described herein may be any kind of computer, either general purpose, or some specific purpose computer such as a workstation. The computer may be a Pentium class computer, running Windows XP or Linux, or may be a Macintosh computer. The computer may also be a handheld computer, such as a PDA, cellphone, or laptop.
The programs may be written in C, or Java, Brew or any other programming language. The programs may be resident on a storage medium, e.g., magnetic or optical, e.g. the computer hard drive, a removable disk or media such as a memory stick or SD media, or other removable medium. The programs may also be run over a network, for example, with a server or other machine sending signals to the local machine, which allows the local machine to carry out the operations described herein.
This application is a continuation application of U.S. Ser. No. 11/958,308 filed Dec. 17, 2007, now U.S. Pat. No. 8,421,268 issued Apr. 16, 2013, which claims priority from Provisional Application No. 60/871,109, filed Dec. 20, 2006, the disclosure of which is herewith incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
6761470 | Sid | Jul 2004 | B2 |
7889051 | Billig et al. | Feb 2011 | B1 |
7940673 | Ballard et al. | May 2011 | B2 |
7961075 | Kuenzler et al. | Jun 2011 | B2 |
8053993 | Brockmann | Nov 2011 | B2 |
8214061 | Westrick et al. | Jul 2012 | B2 |
20060044117 | Farkas et al. | Mar 2006 | A1 |
20060163945 | Bornhorst et al. | Jul 2006 | A1 |
20060170376 | Piepgras et al. | Aug 2006 | A1 |
Number | Date | Country | |
---|---|---|---|
20130300197 A1 | Nov 2013 | US |
Number | Date | Country | |
---|---|---|---|
60871109 | Dec 2006 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11958308 | Dec 2007 | US |
Child | 13863535 | US |