Control systems are built and shipped in the order at which the deposits are received. The date of order has no affect on the date that production begins - production only begins when a deposit is received.

Most systems ship within 3 weeks of the receipt of a deposit, but some systems take longer. Please contact us for a time quote.

A single controller card with no peripherals (no I/O, display, etc) is the smallest a system can get.  A single controller (such as the CVER9) without I/O peripherals still has full access to its ethernet port, which allows it to poll other Opus-Two equipment, iPads running TouchOSC, terminal functions, TFTP functions, etc).  Analog inputs are available, a fully customizable display interface, MIDI, and more allowing any of these protocols to be combined together with a custom config file.

While the software has a limit of 15 chamber arrays (1-15 , each capable of 30 cards, for a total of 450 chamber cards), there are practical limitations because sending chamber frames takes time.  If at all possible, on large instruments, panels should be consolidated vs independent.  For example, if two panels with 8 cards each are mounted next to each other, it is often worth simply using an Extender Card Kit to jumper from one panel to the next.  If using OpusPlane drivers, this consideration doesn’t have much effect, since a single OpusPlane backplane occupies 20 logical driver card spaces.

Each controller supports 1 OLED or VFD (we call these primary displays) with the option to add up to 8 bargraf or dual digit displays.  Each of the bargraf or dual digit displays are fully addressable from the config file and can show anything you want.  Typically, these are all located on a single ribbon chain, and can share a ribbon chain with the primary display if that is convenient.

The C64 and H64 cards are fundamentally the same in that the cards each have 64 pins and plug into each other to form a chain of cards.  H64 cards have 8 pin headers, C64 cards have 12 pin headers.  The H cards have the headers in a parallel arrangement, the C64 cards have the connectors arranged in one long “row”.  These cards make up chains that can be as long as is practically necessary (technically the chains can be 30 cards long, although that’s rarely needed).  The CVA console controller has 2 card chains, each allowing 20 cards for a total of 40.  The cards are typically assembled onto plywood panels by the end user, and power is wired to each card.  The OpusPlane is a chamber card solution where a pre-assembled backplane and card assembly is shipped to the organ builder.  The builder wires power (positive and negative), plugs in data, and instantly has up to 10 cards with up to 98 pins each ready to go.  This is the equivalent of having more than 15 cards in the same space that 6 would occupy using the traditional H or C cards.

With Opus-Two Magnetic Keying, you don’t need to wire contacts.  The system will self-calibrate on each startup to help minimize contact drift from season to season.  In addition, the pistons from the keyslip can be wired into the sensor rails, eliminating not just the I/O cards previously needed to accept keying, but also eliminating the I/O cards needed to drive pistons or LEDs.  Each key rail (each manual) has 25 piston inputs and 25 lamp outputs.  The lamp outputs are intended to drive LEDs, not incandescent bulbs.

Yes.  An Opus-Two universal translator can convert PipeTalk into any conceivable format.  With multiple data outputs (little endian, big endian, polarity inversions, programmable sync, and 5V/12V output selection), it is easy for a UTB to generate the data necessary to drive those cards.  Please be aware that this is not supported by the original manufacturer.

An Opus-Two DIBS adapter can be added to any controller to convert from a standard card chain to a DB25 output.  This output is pin-by-pin function selectable, ensuring compatibility with anything that is plugged into it.

That’s a tricky question to answer because a number of factors go into play.  For example, Opus-Two doesn’t “skip a beat” when a piston is pressed.  Opus-Two also doesn’t need extra time to process crescendo activity, expression shoe movement, or MIDI traffic.  That being said, the control system operates at 16ms cycle times, which provides 60 updates per second.  We have found that is about 50% faster than is required for a typical installation, but if the musician is very close to the pipes, having a faster response works out well to make the system seem invisible to the musician.

Access the terminal.  From the home screen, look near the bottom of the screen.  If the screen says “Currently running config:” and that is followed by a BaseOS version, then the system is using BaseOS, which is our latest build environment.  The version of the config file will follow that.  For example “Currently running config: BaseOS46 with CONF001.txt”.  If the system is running a compiled file, the currently running config will simply indicate the name of the compiled file.  You can press “a” to access the about screen which may indicate the toolset the file was built in.

There are several ways, but the easiest is to take a thumb drive 64GB or less (one should have been left with the system), and create a folder at the root level called “BASE”.  Contact Opus-Two support for the latest BaseOS file, and put it inside that folder.  Insert the thumb drive into the console controller, and the console controller will begin updating the software to that version.  It will then restart, and then re-compile the running config file.  A blinking blue LED on the controller is the confirmation that it is back up and running.

There are several ways, but the easiest is to take a thumb drive 64GB or less (one should have been left with the system), and create a folder at the root level called “GET”.  Insert the thumb drive into the controller, and the the controller will put the currently running config file inside the GET folder.  The drive may be removed after a few seconds.

There are several ways, but the easiest is to take a thumb drive 64GB or less (one should have been left with the system), and create a folder at the root level called “PUT”.  Put the new config file inside that folder.  Insert the thumb drive into the controller.  The LED will turn red while it attempts to ingest and compile the file.  If it is successful, the LED will turn blue.  If it is not successful, the LED will begin blinking green.  A debug file will then be dumped onto the thumb drive to show what was wrong with the file.

If the console is running BaseOS49 or later, press Set-Cancel to begin logging.  Recreate the problem.  Press Set-Cancel again to finish logging.  The log file will now be stored in the console controller.  Insert a thumb drive with a folder named “DUMP” on it, and the console will fully copy all files in its file system to the thumb drive, including the log file.

The only reasons to use a CVA are:

1)        2 complete sets of Midi In/Out/Thru

2)        More RibFlex ports

3)        More Analog Inputs

4)        Dual CardChain I/O ports for faster chain scanning

Technically, all Opus-Two products are standards compliant with Ethernet.  If you take any reasonable quality network switch, it can handle the traffic of an Opus-Two network.  The biggest advantage of an Opus-Two network switch is that it handles the powering of the organ as well as data in one cable.  When any console anywhere is turned on, all chambers power up and all blowers start.  A variety of compatibility accessories are available for any situation.

The trunk port is meant to connect two Opus-Two junction switches together.  Once this connection is made, the switches then “share” power status as well as data.  Any console on either switch will power on both switches.

Every 8 pins on the H64, C64, and Plane drivers are protected by an active current monitoring system.  Once the current on any individual group of 8 pins passes 5 amps, the monitoring system will shut down that group of 8 and activate a blue LED.  This LED is intended to provide information to a technician, helping them quickly locate the fault.  In addition, BackPlane boards have a physical glass fuse for each half of the driver card also limiting to whatever size fuse is installed (6A from the factory).

That error messaging is informing you that an overcurrent was detected in chamber #1, card 5, group 3.  This would be pins 17-25.  If you go to the chamber after this message appears, you will see a blue light at that header showing you where the fault is.  One of the 8 wires on that header is either short circuited or has too large a load on it.

Please don’t try.  We strongly prefer that you send us the spec and let us figure it out for you.  Please include all necessary information including stop list, number of keyboards (please don’t assume we know that based on the stop list), number of pistons, number of toe studs, number of swell shoes (including crescendo).  Please also include any special features the console needs (such as heads up digit displays or bargraphs).  For the pipe chambers, please send a chamber spec including which ranks are on primaries (and which are on which primaries), unit stops (note count and pitch for each), and number of expression outputs per chamber.  Don’t forget to include tremolos and stop actions for the primaries (please also indicate if each stop action requires 2 outputs).  Finally, let us know what method will be used to turn on rectifiers, whether we should supply that, and what activates the blower (and what we need to plan for that – 12V trigger, low voltage contact closure, high voltage contact closure, etc.).

Each pin can easily drive a load as low as the rail voltage.  So for a 14V system, a 14 ohm load could be connected to a pin with no trouble.  For a 24V system, a 24 ohm load would be the minimum.  Loads larger than this (lower resistance) can be used, but support should be contacted.

It is easy to install a combination action only system onto another brand relay.  If the system is expected to provide sforzando and crescendo (or any other blind functions), additional I/O capability should be provided for stop out (as well as stop in).  This ensures that the Opus-Two controller always knows the position of the actual stops in case a piston is pressed while a blind function is active.