Electronic drum connections · declared evidence

Four connection questions hidden behind a drum trigger plug.

A practical workflow from declared requirements to a controlled observation record.

1. State the behavior before choosing the cable

Write down the exact pad and module input, then the zones and optional choke/position behavior you need. A dual-zone description is not a wiring specification. A piezo-plus-switch arrangement and two piezos need not be interpreted by the same mode. Three-zone analog implementations also have model-specific exceptions.

Use Trigger Compatibility Preflight to distinguish documented support from a plug-only assumption. Unknown is a request for evidence, not “incompatible” or “works.”

2. Budget resources before splitting

Mark dedicated kick/control inputs, existing assignments, and any extra resources required for a multi-input cymbal. Some digital assignments can reserve a related analog input. Only then form an interchangeable pool. Every group in that pool must handle the planned dual-zone pads; different groups belong in separate runs.

The Input Allocation Planner reserves non-split groups for dual-zone pads first. For four groups, two split-eligible groups, two dual-zone and four single-zone pads, it needs two documented splits. One more dual-zone pad would remove enough split capacity to break that target. A general audio Y lead does not establish support.

3. Give foot position its own path

For a supported analog hi-hat, a strike path and a controller path provide different information. A module can play a hit while never seeing foot position. A binary switch cannot promise continuous intermediate openings. An integrated digital assembly is an exact supported system, not interchangeable with arbitrary USB equipment.

Use Hi-Hat Controller Route Planner. Read the documented input function rather than just a CONTROL/TRIG label, and never cross-connect a strike pad to a powered controller input to experiment. Consult the exact manual for calibration; no universal resistance or polarity rule is offered here.

4. Isolate the first unresolved observation

Establish a documented compatible baseline. Observe one target hit at the module’s available trigger indication, then its intended audio output. A missing observation remains unknown. Activity at the trigger stage with a silent monitor leads to kit/mapping/output checks, not automatically to replacing a cable.

The Connection Fault Isolator records approved one-variable substitutions. “Fault follows pad” can include the pad profile; “lead changed result” implicates a path without certifying a defect. Do not combine trials or apply generic sensitivity/reset settings.

A record you can take to support

Copy or print the result to preserve input labels, counts, observations, page URL and confidence boundary. Keep exact model/firmware and physical jack mapping in your own notes. The site does not inspect connected hardware, store model records or capture audio.