d&b audiotechnik D12

No. Remote carries CAN-Bus/RIB. To control the D12 from R1, d&b specifies an R60 USB to CAN or R70 Ethernet to CAN interface; an Ethernet switch does not replace that interface.

With R60, the path is computer → USB → R60 → CAN → D12. With R70, it is computer → Ethernet → R70 LAN → CAN → D12. Any Ethernet switch belongs on the LAN side before the R70. The two R70 CAN connectors are wired in parallel.

For the CAN section, use shielded cables and metal RJ45 connectors with the shield connected at both ends. A cable fitting the socket does not confirm its shielding or the port protocol.

1. Identify the actual interface, R1 version and rack firmware. Trace control and audio separately: Remote is not an audio input.
2. If the interface is R70, check that Ethernet reaches LAN and the D12 amplifiers connect to CAN. Compare the configured IP address and subnet with the computer; do not copy a default address without checking the existing network.
3. Compare the amplifiers shown in R1 with the plan and their identifiers. If only part of the system is missing, follow the CAN bus checks below. If none appear, first check interface power, connection and identification.
4. If the interface model is unknown, hold off on connecting and find its documentation. Do not plug Remote directly into the switch as a test.

No. The two channels drive the active system’s frequency sections; the setup is selected on A and its signal and settings are linked to B. OUT A/B do not represent two independent mixes in this mode.

Before reassigning an output, compare the selected mode with the patch and cabling. For LINE/ARC, follow the J8 page and the exact cabinet model.

The adapter alone is not enough. The J8/J12 manual requires EP5 and five-wire cabling for SenseDrive; at least one cabinet must connect to OUT A of the D12. The extra conductor, EP5 pin 5, returns an LF reference to the amplifier to compensate for the cable.

TI 340 includes a section on fixed installations. Its scope does not authorize building an adaptation for J8.

1. Identify the cabinet variant and D12 outputs. Check the entire EP5 path and its five conductors, not just the adapter housing.
2. With the amplifier off and the cable disconnected at both ends, check the sense conductor and the rest of the pin map before reconnecting. Do not make a bridge in the rack to simulate the reference that must come from the cabinet.
3. For NL8, the published tables show a sense contact, but the connection text requires EP5. Confirm that combination with d&b before connecting: the difference between table and text remains unresolved.

Compare the physical amplifier order with the R1 list and locate the first missing device. Check dbCAN-ID values as well: every node needs a unique identifier across the whole network, not just within its rack.

The bus needs 120 Ω termination at both ends. With an R70 at one end and only one CAN connector in use, enable TERMINATE and terminate the opposite end. If the R70 is in the middle and uses both CAN connectors, leave interface termination off and terminate both far ends. Do not add a plug-in terminator to the R70 when its internal termination is already enabled.

1. Save the project and record dbCAN-ID values, cable order, terminators and detected devices before changing anything. If IDs repeat, check and correct the local assignment against the plan, preserving the previous assignment so it can be restored.
2. Inspect the cable between the last detected D12 and the first missing one, its connectors and shielding at both ends. Also check topology and both terminations; where devices go missing guides the search but does not prove that amplifier is faulty.
3. If using R70, record its indicators. Steady ERR means Bus off; flashing ERR means a CAN error. Rapidly flashing LAN confirms an active Ethernet connection, not communication with every D12. Check the remaining states against this page’s table.
4. As a test outside event operation, check a short section with a verified cable. If you shorten the bus, maintain correct termination at its two new ends. Record which devices reappear and reconnect sections one at a time; compare the result after each change.
5. Restore the documented path and configuration when the test ends. If the fault persists, retain the map, states and messages to inspect the isolated section or device. Do not perform a blind R70 factory RESET: it restores configuration, including network settings.

Check two separate paths: computer–R70 over Ethernet, then R70–D12 over CAN. A rapidly flashing LAN indicator shows an active Ethernet link; it does not yet confirm access to the interface or detection of the amplifiers.

1. Record the computer and R70 IP addresses and subnet masks, and whether the network uses DHCP. The R70 factory address is 192.168.1.70, with DHCP enabled; do not assume it still uses that address on a network with a DHCP server. Every device needs its own IP address.
2. With DHCP, find the address assigned to the R70 in the server lease list or the interface discovery facility of your R1 version. Open that address in a browser. If the web interface loads, access to the R70 works; continue with CAN and the dbCAN-IDs.
3. Without DHCP, check the subnet and avoid duplicate addresses. For a direct connection to an R70 still using its factory address, the manual uses 192.168.1.71 and subnet mask 255.255.255.0 on the computer. This is an example for that connection, not an address to copy into the event network.
4. If the R70 must be configured for a network without DHCP, save its existing settings first. In its web interface, LAN Parameters lets you disable Obtain an IP address automatically and enter Host Name, IP Address and Subnet Mask. The manual requires Save and Device Restart: schedule this outside operation because restarting interrupts the control session. Then reconnect using the new IP address.
5. If the web interface responds but R1 cannot detect the R70, check the selected network interface and firewall rules. Manual 1.4 specifies fixed UDP port 33333 and adjustable TCP port 30000; verify the actual port setting and the documentation for the installed R1 version. You do not need to disable the entire firewall to check one rule.
6. If R1 detects the R70 but some D12s are missing, continue with the CAN checks on this page. Record each change and restore saved settings unless the test justifies keeping it. Do not use Factory Default as the first attempt: it also changes the network configuration.

You can prepare the ArrayCalc design without an R70 connected. ArrayCalc calculates the system from project data; R1 uses that file to organize control. The R70 connects the computer’s Ethernet network to the D12 CAN bus. Audio takes a separate path to the amplifier inputs.

Controlling a D12 from R1 does not give it ArrayProcessing. TI 385, edition 10.4, documents J Series operation with D12, 30D and D80, but ArrayProcessing with D80 and 30D. For J8 with D12, prepare LINE/ARC according to the design; do not try transferring an AP configuration to correct a coverage difference.

1. Work on a copy of the project. Complete loudspeaker models and order, geometry, amplifiers, channel assignments and Remote IDs before preparing the file for R1. Record both software versions and firmware; a template with different models or IDs needs adapting.
2. Open the file prepared from ArrayCalc in R1 and compare loudspeakers, amplifiers, IDs and groups with the plan. Offline preparation lets you organize controls without connected amplifiers. Devices drawn in the project are not proof that they are present on the network.
3. During preparation, check the assignment against the physical D12s before sending settings. R1’s Wink function flashes the amplifier display to help identify it. If it is not the expected rack, correct the assignment before changing levels, filters or MUTE.
4. Check control detection, the audio patch and signal at each destination separately, with the correct setup and a test level. If R1 sees the amplifiers but there is no program audio, trace audio from the console or processor; the R70 does not carry it.
5. If the installation differs from the project, update the design and save another version. Keep the original file and settings so you can return to the documented state. Simulation and a device list do not replace checks on the assembled system.