Yamaha MRX7 Control Driver

Version 0.23

Two-way control driver for the Yamaha MRX7-D (MTX/MRX series) audio DSP over the SCP protocol, on the network (TCP port 49280) OR RS-232C serial. One driver adapts to any project: you export your design's control list from ProVisionaire, import the CSV, and the driver builds fully wired functions, feedback variables and drop-to-wire tags for every zone, source, level, router, matrix crosspoint and external event in your design.

1. Add the driver and set up the connection

- Add the driver to your project. In Add-a-Device it appears as the "Yamaha MRX7" source (Receiver template).

- Under Connection, choose the Connection Type: Network (SCP over TCP/IP) or Serial (RS-232C), then fill in the matching fields.

- Network: enter the MRX7-D IP Address and Port (default 49280).

- Serial: choose the processor Serial Port wired to the MRX7-D RS-232C (DB-9), and set the Baud Rate to match the unit - Yamaha's factory default is 38400; the port also supports 115200.

- Under Licensing, enter your Licence Key, or leave it blank to run the 120-minute trial. During the trial the driver is fully functional; when it expires, control commands are blocked while status/feedback keeps running. Enter a key to unlock it permanently. The MAC For Key variable and the debug console "mac" command report the processor MAC used to generate a key.

- Under Options you can set the Volume Step (dB) used by Volume Up/Down (default 1 dB) and the Poll Interval in seconds (default 30) - how often the driver re-queries every mapped parameter.

2. Import your design (the ProVisionaire CSV)

Every control the driver exposes comes from your ProVisionaire design, so this step defines the whole driver.

- In ProVisionaire Design, open the MRX7-D and build a Remote Control Setup List containing the parameters you want to control (zone levels, on/off, source selects, matrix crosspoints, router outputs, external events, and so on). Each row is given a "No." - this is the SCP index the driver uses to address that parameter.

- Export the Remote Control Setup List as a CSV.

- In Driver Properties, set "Parameter CSV File" (under Control Objects) to that CSV. On selection the driver imports it. You can also right-click the driver in the workspace and choose "Import MRX7 Parameter CSV".

- The driver reads every row and automatically generates a wired Function, a feedback Variable and drop-to-wire Tags for each control - grouped into Zones, per-zone buttons, source buttons, routers, matrix crosspoints, levels, on/off controls and external events (see section 4).

- "Import Summary" (under Control Objects) reports how many objects and zones were imported.

Re-importing: every import regenerates the functions, variables and tags from the current CSV. Existing tags and export names are kept stable, so anything you have already programmed keeps working. After any re-import you must re-send the driver to the processor for the changes to take effect.

3. Naming your zones and sources

The ProVisionaire CSV carries the zone names but only a numeric range for sources, so you can label things for a friendlier UI:

- Source Names (one field per source, under the Source Names category, generated to match your project's source count): enter e.g. Fox 1, Fox 2, Sky. These names appear on the source-select tags and in the Source pick-lists, and are published as display variables you can bind to a label.

- Zone Names (Zone 1..N Name): leave blank to use the name from the imported CSV, or fill a field to rename that zone everywhere - tags, functions and variables.

- After changing any names, re-import (or the names refresh on the next regeneration) and re-send the driver.

4. What the driver gives you (functions, tags and feedback)

After import you will see these categories in Driver Properties. Two ways to program are provided: drop-to-wire Tags (fastest) and dropdown Functions (for macros and one-offs).

Tag auto-wiring (the fast way): each tag pairs a command with its matching feedback variable, so a single tag drop in IDesign wires BOTH the button macro AND the feedback. Every control offers a stable number tag and a friendly name tag - drop whichever you prefer:

- Zone on/off: "Zone 1 On" / "Kitchen On", "Zone 1 Off" / "Kitchen Off", "Zone 1 Mute" / "Kitchen Mute" (toggle). The Mute/Off feedback lights an Off button when the zone is off.

- Zone volume: "Zone 1 Volume Up" / "Kitchen Volume Up", "...Volume Down", and "Zone 1 Volume" / "Kitchen Volume" for a percent slider (drop it on a slider - it drives the level and reads back the knob position). "Zone 1 Volume Level" / "Kitchen Volume Level" is a text tag showing the level in dB.

- Zone source select: "Zone 1 Source 3" / "Kitchen Sky" wires the select button plus its "active" feedback boolean. On a selector zone the sources are exclusive (one active). On a matrix output each source is an independent crosspoint toggle (many can be on at once).

- Source name labels: "Source 3 Name" / "Source Name 3" is a text tag showing a source's friendly name; each zone also publishes its currently-selected source name.

- Zone name label: "Zone 1 Name" is a text tag showing the zone's name.

Zones (dropdown functions): generic functions where the zone is chosen from a pick-list - Zone Volume Up, Zone Volume Down, Zone Set Volume %, Zone Set Volume (dB), Zone Audio On, Zone Audio Off / Mute, Zone Audio Toggle, Zone Select Source. Useful in macros or when you prefer one function driven by a parameter.

Zone Buttons / Zone Source Buttons (tag auto-wire): the per-zone and per-source tag entries described above, ready to drag onto panel buttons.

Routers: for each router in your design, a "Set Output Source" function picks an output and the input to route to it (0 = off). Per-output source and source-name feedback variables are published.

Other On/Off: On / Off / Toggle for any standalone on/off control (named outputs, mutes) not folded into a zone, chosen from a pick-list.

Other Levels: Set %, Up and Down for any standalone level/fader not folded into a zone (e.g. input trims), with dB, raw and percent feedback.

Secondary Mixer Crosspoints: Toggle / On / Off for crosspoints of any matrix mixer (e.g. mic-select duckers) in the design.

External Events: a "Fire External Event" function fires any external event defined in your design, chosen from a pick-list.

System: Recall Preset (by number), Query Current Preset, Refresh (re-query everything), Reconnect, Set Raw (Index) / Query Raw (Index) - see section 6 - and Remote Logging On / Off.

5. Feedback

The driver polls all mapped parameters on connect and on the Poll Interval timer, and also listens for live changes pushed by the MRX7-D, so the UI tracks changes made from other controllers or the front panel. Feedback is delivered two ways:

- Via tags: because each tag pairs the command with its feedback variable, dropping the tag onto a button also binds its feedback (button state, slider position, dB/name text) - no separate wiring needed.

- Via variables: bind the published variables directly if you build custom UI. Per zone you get Audio On, Muted, Source (index), Source Name, per-source "active" booleans, and Level as raw / dB / percent. Global variables include Connected, Connection Status, Run Mode, Current Preset, the Source Name display strings, and the Licensing status set.

6. Adding, changing or scripting a control

Because every control comes from the ProVisionaire Remote Control Setup List, adding a zone, input or command is easy - two ways:

Add it in ProVisionaire (recommended):

- In ProVisionaire Design, add the new parameter to the Remote Control Setup List (it is given a new "No." index) and export the CSV again.

- In Driver Properties hit Import (or right-click "Import MRX7 Parameter CSV") to re-read the CSV, then re-send the driver to the processor.

- The new control gets its own wired Function, feedback Variable and tags automatically. Existing controls keep their tags and export names, so anything you have already programmed still works.

Ad-hoc, without re-importing:

- Use the built-in "Set Raw (Index)" and "Query Raw (Index)" functions (System category). Give the SCP index (the "No." from the Setup List) and, for Set, a value - the driver sends any command the MRX7 supports. Handy for a one-off, or before you have added a control to the CSV.

7. Diagnostics

- A telnet debug console is available on the Debug Console Port (default 12533; set to 0 to disable, under the hidden Debug category). Commands:

- status - transport, connection, mapped/polled counts, volume step and licence state.

- map - list the imported control map (index, type, base, range).

- poll - re-query all mapped objects. refresh - full refresh. reconnect - drop and reconnect.

- get <index> - query one parameter. set <index> <value> - set one parameter.

- vol <index> up | down | <n>% | <dB> - drive a level. mute <index> on | off.

- src <index> <n> - select a source. preset <n> - recall a preset. event <index> - fire an external event.

- mac - the processor MAC (for licence keys). licence - current licence state.

- rlog - toggle remote logging; rlog test - send a test line.

- Any other text is evaluated as JavaScript for deep diagnostics.

- Debug Level (hidden Debug category) sets TraceView verbosity: Off / Info / Verbose / Trace.

- Remote logging (Remote Logging category, or the Remote Logging On/Off functions) can stream driver logs to the developer endpoint for support. Leave OFF unless asked.

8. Events

The driver signals: Connected, Disconnected, Trial Warning (5 minutes left) and Trial Expired - wire these to macros for connection monitoring or licence reminders.

9. Troubleshooting

- No controls after loading: no CSV has been imported yet. Import the Parameter CSV and re-send the driver. The debug console "map" command shows "(empty)" until a CSV is imported.

- Network: won't connect: confirm the MRX7-D IP Address and that SCP/remote control is enabled on the device; the port must be 49280. The MRX has only a few network control slots - make sure another controller isn't holding them all. Use "reconnect" and "status" in the debug console.

- Serial: won't connect / garbage: confirm the Serial Port is the one wired to the MRX7-D DB-9, and that the Baud Rate matches the unit (try 38400, then 115200). Note: RTI cannot re-open a serial port at runtime, so after changing the serial port/baud - or if the cable is unplugged and replugged - re-send the driver to the processor.

- A control or zone is missing: it is not in the Remote Control Setup List - add it in ProVisionaire, re-export, re-import and re-send.

- Tags will not wire: make sure you re-sent the driver after importing, and that you are dropping the tag onto a compatible widget (slider tags belong on sliders, on/off tags on buttons).

Support

Smart Home Programming - https://smarthomeprogramming.com.au