XR18 or MR18 will not connect: console, router and tablet checks

Draw each device’s path to the router

XR18 and MR18 support Ethernet, Wi-Fi Client and Access Point. If the console is wired to the router, its connection is Ethernet even when the tablet uses Wi-Fi. In Wi-Fi Client the console joins an existing wireless network; in Access Point it provides its own. Identify this distinction in the Midas MR18 and Behringer XR18 specifications and record the mode in use.

On a simple local network, connect the console to LAN. The WAN or Internet port normally serves the router’s external connection. If that router supports port reassignment, check its manual for each port’s current function. Microsoft’s Ethernet guide also distinguishes these paths.

Check REMOTE, DHCP and 169.254 addresses

In the X AIR V1.0 manual, page 14 and MR18/MR12 manual, page 12, DHCP Client requests an address from a DHCP server. With an external router providing that service, check the REMOTE selector for the actual connection, the console’s client mode and its address in the router’s lease list. Compare the control device’s IP and mask too; do not enter 192.168.1.1 merely because a manual screenshot shows it.

The manuals distinguish DHCP Server from DHCP Client. The console uses 192.168.1.1 when acting as a DHCP server; this mode is optional on Ethernet and normal in Access Point. Its client address pool is 192.168.1.101–192.168.1.132. Access Point supports up to four simultaneous clients: the pool size does not increase this limit.

On Ethernet without an available DHCP server, the manuals describe an automatic console address between 169.254.1.0 and 169.254.254.255. This does not prove the router issued a lease. If only the computer shows 169.254, the console’s address still needs identifying; that alone does not diagnose a faulty cable either.

With static IP, compare address, mask and gateway with the network plan and rule out duplicate addresses. Save the values before correcting them. Changing active-connection parameters can disconnect the app; first prepare alternate access and a return to the original mode.

In Windows, inspect connection properties in Network & internet settings and record IP and mask. Microsoft’s network and DHCP guide locates these settings. Compare them with console values and router leases before changing either endpoint.

Change one variable and reconnect

After each change, repeat the same test and record what happened. Changing cable, mode and address together may restore control, but leaves the failing stage unidentified.

1. Compare cable and LAN port

   Use a verified cable between console and router, then try another LAN port. If observing LEDs, check the meaning of their colors and flashing patterns for that model.

2. Check the tablet’s network

   Confirm the network name and whether it shares the console’s LAN. If the router provides several networks, inspect its configuration: the same router does not guarantee communication between them.

3. Try a wired computer

   Connect it to the same LAN and open the compatible app. If it finds the console, continue along the wireless path or the device that failed.

4. Compare a second control device

   Try another tablet or computer and record network, app and result. This distinguishes a problem specific to the first device from one shared by the setup’s paths.

Rehearse how to recover control

Test the wired connection with the computer that will be available. Save the show and a record of network, mode and control devices. The official pages support computer or wired LAN control; prepare and rehearse that alternative before the event so it is usable if the tablet fails.

Local control may still work when Windows reports no Internet. Check whether the app reaches the console before treating that message as a mixer fault. Microsoft’s guide to Wi-Fi without Internet explains the difference between local access and an external connection.

On iPad, also check the app’s Local Network permission

If the tablet is on the correct network and another computer controls the console, check app permission. Record its name: the manual distinguishes X AIR for iPad from X AIR EDIT for computers. Compare the controls and versions of the app in use.

On iPad, open Settings > Privacy & Security > Local Network. If the control app appears, confirm access is enabled. Apple documents this permission from iPadOS 14. Even when browsing works, verify that this app may access local devices.

If the app is missing from the list or keeps closing, record iPad model, system version, app version and when it fails. Retain the station that already connects as backup; a missing permission and an app crash require different checks.

Compare off program: reconnect, check whether meters appear and leave control open while rehearsing the show. Keep the verified computer available as an alternative. Enabled permission is one concrete check; stability during the event needs its own rehearsal.

When connecting another station, check synchronization direction

Before connecting another computer, decide whether to receive the current mix or load prepared settings. Save a reference for input names, sends, mutes and levels that must remain.

In X AIR EDIT, the V1.0 manual, pages 15 and 28 distinguishes Mixer → PC from PC → Mixer. Choose Mixer → PC to receive current console settings on the computer. The other direction transfers computer settings to the mixer.

Rehearse the connection off program with an identifiable state. On the second station, verify the selected unit and compare saved settings before changing the mix. Record app and version; another program may present connection differently.

Keep an identified show copy. If stations show different values, stop transfer, check connection and synchronization direction, and read console state again. Loading a prepared show requires a check separate from connectivity.

Limit each device to its monitor mix

Associate each control device with a monitor bus and its physical output. Use names that trace the path from send to listening destination.

In Mixing Station, select Personal Monitoring in the device’s connection profile. This mode restricts access to its mix and excludes input processing. Check separately whether the profile permits bus processing.

For password-protected buses, consult XR/MR Security: Main LR protects No restrictions access. Other apps, including official X AIR apps, ignore this protection. Check the app on each device. Before setting protection, back up snapshot 64: it stores the password and scope.

Off program, make a small change to an identified send from each device. Check that the intended bus and physical output respond while other mixes keep their settings. Restore the initial value after observing the result. If another monitor responds, stop and check profile, bus and output patch before moving more faders.

Test what happens when the tablet locks

If XR18 control is lost when the tablet locks, check whether Wi-Fi also disconnects. Record app and system; rejoining the network and reconnecting the app are separate checks.

For Mixing Station on iOS, its documentation warns that turning the screen off closes its connections. It recommends keeping the screen on; the app does so by default. Check reconnection on return.

Rehearse before the show: display an identified channel, lock, unlock and verify its meters return. Do not change settings during this check. If it also fails with the screen on, record when it happens to continue diagnosis.

Show the same channel on two Mixing Station screens

With two screens for an XR18 or MR18, faders can remain on one and EQ on the other. App-Link synchronizes application parameters, such as selected channel, between Mixing Station instances.

In App settings > App-Link, turn on Enable at both stations and Channel select where selection should be sent. Use the same Group Name. Devices must share a subnet and permit broadcast; also check that Pro functionality is available.

Before the show, select two channels in succession and check the EQ shown on the other station without moving faders. Use different groups for independent controls.

The tablet lost control while USB audio remains active

USB type B carries multichannel audio; Ethernet and Wi-Fi provide remote control. These paths are separated in the X AIR manual and MR18 guide, revision 24/06/2025, pages 20–21. App disconnection does not prove recording stopped, and a running time counter does not prove continuous audio in the file.

First inspect the recording or playback program: selected device, transport state, time progression, track meters and error messages. Also check listening at the intended destination without changing routing. If active, preserve this setup while diagnosing control; restarting the console, unplugging USB or changing sample rate can introduce another interruption.

From the control computer already connected and prepared on the same LAN, try reaching the identified unit. If it responds but the tablet does not, continue with tablet SSID, local permission and app. If wired control also fails, check the recorded address, REMOTE and LAN connections. Do not change the recording computer’s network to improvise another station.

On reconnection, receive current console settings using the control station’s synchronization direction. Compare unit, meters and saved values before touching the mix; do not transfer an offline state to test the link.

During preparation, rehearse control loss and recovery with a sample recording and the intended setup. Close the take normally and listen to the complete file; record any discontinuity’s position and the time of each change. Separate connections do not guarantee continuity during every intervention. For XR18, also use the USB detection, send and return guide (Spanish).

Restore the previous network without confusing reset with Initialize

Before changing the network, save REMOTE, DHCP or static mode, IP, mask, gateway, SSID and each station’s connection. Save the current scene on the computer and record which alternate link already reaches that console. Scene and network record cover different data; do not assume loading a scene restores an IP address.

If a static IP prevents connection, the X AIR manual, page 14 and MR18 manual, page 12 propose another connection mode to regain access and correct parameters. Use the prepared alternative, read configuration and restore recorded values for the initial link. Return to that mode and reconnect from the intended station; if it fails, return to alternate access and inspect the last change.

For MR18, the 2025 quick-start guide, printed page 20 distinguishes RESET for 2 seconds to reset networking from 10 seconds to restore all settings to factory defaults. For XR18, X AIR manual page 14 documents a 2-second network reset. The 10-second procedure cited here applies to MR18; confirm the exact revision’s documentation before applying another scope.

In the Connection tab, Initialize restores factory console settings and erases its configuration, according to X AIR page 28 and M AIR page 27. By contrast, Initialize in M AIR GUI Preferences, page 28, clears saved window layout. Identify tab and function before pressing it.

Off program, verify restoration using the correct console, active meters and preserved mix values. If alternate access also fails, retain saved data and confirm the model’s procedure before resetting networking. Complete the XR18/MR18 control and recovery worksheet with initial state, each change and verified return.