Why an Organ Problem Comes and Goes

A fault that is not present when the technician arrives cannot be traced by any listening or console-side method, because every such method narrows the search only while the symptom is happening. The listening tests, isolating a swell shoe or tremulant, triangulating across stops, watching what happens when the blower is shut down, and disconnecting control-system boards each depend on the fault being present at the time, and even then none of them identifies the failed part without opening the instrument. An intermittent fault therefore adds a second problem on top of the first: the instrument has to be caught misbehaving before the usual narrowing can begin. That is why a description from memory is weaker than a record made at the time, and why a single visit may end with the family narrowed but the part unconfirmed.

When several apparently unrelated symptoms come and go together, one shared upstream condition is a more economical explanation than several independent parts failing in step. The candidates for that shared condition are the organ power supply, the communication bus between control-system boards, and the wind supply. In a Syndyne system, one unterminated communication port produces system-wide communication problems, and Peterson states that an undersized rectifier makes stop actions appear dead; each is a single condition that shows up as a scatter of symptoms. Coincident independent failures do occur, so this is a reasoning principle rather than a rule, but a fault report listing several symptoms with a common onset should say so plainly. Supply-side causes are explained on rectifier and power-supply failures, and the broader split between the two systems is on electrical failure versus pneumatic failure.

Switch contacts are a recognized source of intermittent faults, which is why the industry has designed around them. Peterson’s case for its semiconductor switching is that it replaces thousands of switch contacts that can pit, corrode, or need adjustment, and the American Institute of Organbuilders’ guidelines call for striking, wiping, self-cleaning contact devices with redundant contacts and silver-alloy or gold-plated surfaces. Neither statement reports field failure rates; one is a manufacturer’s product claim and the other is advisory design guidance. A key contact that is dirty or faulty is, in the account given by Josh Dove for Viscount North America, a cause of crackling, whooshing, or intermittently working keys, with a qualified technician required in every case; that is a vendor’s attribution rather than an independently evidenced one. Where the intermittent note lives at one key, the pipe-organ key-contact problems page owns the symptom, and a piston that sometimes fires and sometimes does not is covered by why console pistons become unreliable.

Erratic behavior in a solid-state control system can also come from what shares its supply. Peterson’s installation instructions state that unsuppressed magnets, such as add-on chime keyboards or volume controls, can cause erratic behavior; Peterson says this of its own systems, and the same mechanism is plausible elsewhere without being established for other manufacturers. Peterson’s June 1993 notice to installers of solid-state equipment reported a correlation between unexplained failures and occasional erratic operation and Astron rectifiers having an internal connection from the DC negative output terminal to earth ground, with sixty-cycle hum in the DC circuit, increased vulnerability to lightning damage from static charge buildup, and notes or stops that may not turn off dependably. Peterson’s commissioning guide also treats supply ripple as a measurable fault condition while listing board seating, cable insertion, and address configuration as alternative explanations for erratic control behavior. These are technician findings rather than owner checks, and the supply criteria themselves belong on the rectifier page. A note that sometimes will not turn off is a cipher, and pipe-organ ciphers have their own page.

Aged flexible tubing is a documented cause of intermittent and progressive pneumatic faults. John Bishop, writing in The Diapason about the instruments he services, states that seventy-year-old rubber tubing is likely to be crumbling apart; that is a practitioner’s observation about what he encounters, not a measured service life or an industry rule. It matters for this page because tubing that is deteriorating rather than failed outright produces faults that are intermittent before they are progressive, so a pneumatically operated note or stop can come and go for a period before it stops entirely. Once the symptom has settled into a constant one, the dead-notes page and the page on tracing silent stops, ranks, chests, and divisions cover those symptoms, and sustained hissing or low pressure is on air leaks, hissing, and low wind pressure. The condition of organ leather in an electro-pneumatic action is explained in what happens when organ leather fails.

Not every intermittent misbehavior in a control system is a broken part. Syndyne’s MS8400 builder manual includes a test for address conflicts to identify duplicate board addresses, which documents configuration conflict, rather than component failure, as a recognized cause of misbehavior in a distributed control system; the existence of the test shows that the condition is recognized, not how often it occurs in service. Peterson records a case in which a driver integrated circuit on an ICS output board had shut down because of an overload, so a protective response, rather than a destroyed component, presented as an output that had stopped working. A protective shutdown and a failed driver look identical from the console, which is exactly why the distinguishing evidence sits at the board rather than at the keyboard. For an owner, the practical point is that an output that stops and later returns is not evidence that nothing is wrong, and not evidence of which of these conditions is present.

A fault that returns each winter, or each time the building is heated for a service, has a documented environmental explanation. The American Institute of Organbuilders states that stable temperatures inside an organ are usually reached three to six hours after the building system is turned on, and the British Institute of Organ Studies states that rapid changes in temperature upset the tuning of an organ. Neither body says which mechanical faults are reversible with temperature and which are not, so a symptom that fades once the instrument has equilibrated has been narrowed to an environmental family, not explained. The Diocese of Chester states that new church heating systems can have a significant impact on organs, particularly if they provide short intermittent bursts of heat, and the Institute of British Organ Building documents remedial work after a heating installation costing more than 55,000 pounds. That is advisory guidance without measurement rather than a damage threshold, so a cluster of faults that began after a heating change should be reported with the date of that change.

Humidity produces its own intermittent family, and here the attribution matters because the source sells humidity control. Condair, a humidifier manufacturer, states that excessive humidity causes wooden parts to swell and misalign moving parts or cause a cipher, makes leather parts such as valve pouches and gaskets soft and susceptible to mold, and causes condensation-induced corrosion of metal pipes. Read as that company’s own account rather than independent evidence, it still describes mechanisms that track the season and the building rather than the age of the instrument. This page states neither a humidity target nor a leather service life; the organ leather page owns leather condition, a cipher that has become persistent belongs to the ciphers page, and keys that bind with the weather are on why pipe organ keys stick or return slowly.

Record what the instrument did, when, and under what conditions, because a written record made in the moment is evidence a technician can use and a description from memory is not. Note the date and time, how long the building had been heated or left unheated, exactly which notes, stops, pistons, or divisions misbehaved, whether several different symptoms began together, and what had recently changed in the building or at the console, including any add-on device wired to the organ. Several symptoms with a common onset point toward one shared condition in the organ power supply, the communication bus, or the wind supply, so the pattern is worth more than any single entry. Safe owner action stops at checking circuit breakers and looking for obvious foreign objects between the keys; David E. Wallace of Wallace and Company draws that boundary for suspected electrical or keyboard faults, and everything beyond it belongs to a technician. That is one builder’s stated boundary rather than a published standard, and it assumes the breaker panel is safely reachable in your building.

A fault that returns after it has been repaired is evidence about the environment, not only about the replacement part. Where a contact fault is traced to contamination from grit, salt, a spilled drink, or rodent activity, cleaning or replacing the contact alone leaves the source of contamination in place, so the same symptom recurring points back at the surroundings of the console. That principle is drawn from John Bishop’s accounts of grit and salt at the console, of sugary coffee requiring replacement of several octaves of guide-pin bushings, and of rodent activity at keyboards, together with Peterson’s account of contacts pitted from prior electrical use; it is an inference from those cases rather than a rule any of them states. The same logic applies to the seasonal family: a fault that comes back with the heating season after a repair is telling you about the building’s heating regime rather than about the work. A recurrence record therefore needs the date of the previous repair alongside the date of the return.