Production · Practical guide

Green-GO: back up configurations and recover intercom stations

If a station loses channels after a change, preserve what still works before loading another configuration. With Green-GO 5, the Control file, local device settings and startup configuration are distinct. This guide helps plan a backup and recovery rehearsal for MCXD and WBPX stations.

Identify stations, configurations and backups

Before attempting recovery, identify the stations, firmware, command used and result observed.

Check where rehearsal settings were saved and decide which device or file will supply the configuration for recovery. The steps below follow Green-GO Control 5 and the manuals for the named models. Tests on the actual setup remain to be done.

A change to a user or device: record its scope

The configuration guide, Channel configuration distinguishes two places to edit channels. A change to a user enters the configuration file and applies to linked devices. A change in the device view is sent only to that unit and is not added to the file. If a setting worked on one pack, record where it was changed.

Before editing, note the open view, user, device and channel. If a setting should follow a role to other stations, check the user's configuration. If it applies only to one unit, record its local values too. You can then compare the file with the station without assuming they match.

Under User assignments, the manufacturer warns that loading or changing a user can overwrite local settings. Device profiles also apply changes immediately to linked devices of the corresponding type. Check the scope before confirming, especially when one user is assigned to several units.

A change to a user or device: record its scope
Where it is edited in Control 5	Documented scope	What to retain
User channels	File and linked devices	User, channels and file revision
Device channels	That unit only; not added to the file	Unit, channel and local values
User device profile	Linked devices of the corresponding type	Profile model and units that will receive the change

Saving the file and saving to devices are separate steps

Under Application Tools → File menu, SAVE and SAVE AS write a .gg5 file to the computer. Use SAVE AS with a date and revision before intervening, and keep the earlier copy. Record any local settings separately; saving the file does not establish that those differences are included.

Save to devices stores the running configuration of adopted devices as their permanent startup configuration. The orange indicator shows a difference between the running and stored startup configurations. The manufacturer warns that this operation interrupts communication for up to one second and says not to use it during the show.

Set aside a rehearsal window, identify the units present and review what they will save before using the function. Then check the planned conversations. To check independence from Control, close Control while keeping the network and antennas running, and test startup on a station reserved for that purpose. Record observations without Control and after startup separately; those tests have not been performed here.

Back up before combining files with MERGE. The same File menu section warns that MERGE can overwrite items with the same ID and cannot be undone. Merging a file is not the same as restoring an entire earlier revision.

Saving the file and saving to devices are separate steps
Action	Where the configuration is stored	What still needs checking
SAVE / SAVE AS	.gg5 file on the computer	Saved revision and separately recorded local differences
Save to devices	Permanent startup on adopted devices	Units present, conversations and rehearsal startup
MERGE	Combines parts with the current file; may overwrite IDs	Earlier backup and comparison of affected items

JOIN and ADOPT: choose the source of the configuration

Under Connections → Network → Join a Config, JOIN loads the selected device's configuration into Control and replaces the one open there. Save changes to the current file first. If you intend to use a station's stored configuration, identify that unit before confirming.

Under Adopt Devices, ADOPT moves selected units into the configuration open in Control. It overwrites their current configuration and interrupts their communication in the previous one. Review the selection and dialog: selecting every discovered device may affect stations you did not mean to change.

With ADOPT and JOIN, decide which direction the configuration must travel. If a unit appears on the network but cannot join the conversation, record its state and compare its configuration before adopting it. Presence on the list does not validate its channels. After adoption, check the assigned user and repeat talk and listen tests with each intended recipient.

In the local menus of MCXD and WBPX, Config → Join Config has a different scope: it loads a configuration available on the network into that device. The list omits the configuration already in use. Check Info → Config first; its absence from Join Config does not mean it was lost.

JOIN and ADOPT: choose the source of the configuration
Where the action runs	Source → destination	What it may replace
JOIN in Control	Selected device → Control	File currently open in Control
ADOPT in Control	Control configuration → selected units	Previous configuration and membership of those units
Join Config on MCXD or WBPX	Configuration on network → that unit	Configuration used by the device

MCXD and WBPX: compare configurations before reloading a user

The MCXD manual, Info → Config and WBPX manual, Info → Config show Name, Stamp and ID. Record these along with Info → Firmware and Info → Serial. ID identifies the configuration; Name helps recognize it and Stamp records its timestamp. Compare them with the reference station and file revision.

If stations use different configurations, confirm which revision belongs to the event and who holds it before loading anything. If they match, compare the user and affected channels with the rehearsal matrix. A matching ID alone does not prove listen, Talk or local settings work.

Info → Reset to Defaults → Reload User reloads the current user and its settings on both models. It does not automatically restore yesterday's state. Save local values first and confirm which user will load; the command name does not imply an earlier backup.

Both manuals warn that clearing the cache removes the local configuration and returns the unit to Factory Default. That action is outside this proposed recovery sequence. If a specific manufacturer instruction calls for it, first prepare the file, local settings and procedure for the exact model.

Rehearse recovery and hand off open issues to operations

Use a test station and an identified conversation partner outside live operation. Preserve the starting file and values, and record one intervention. Then verify two-way conversation, Listen and Talk on affected channels, and the intended reach of other users. Compare the reference station as well to catch changes applied to more units.

At handoff, distinguish a saved file, configuration saved to devices, and conversations actually tested. Mark every absent unit or unit without a startup test. The next crew needs that information even if one station passed.

Complete the Green-GO backup and recovery worksheet. Relate it to the direction, camera and stage matrix (Spanish) and the conference continuity plan. If configurations match but the fault depends on location, use the intercom coverage guide (Spanish).

To plan preparation with GLMedia, send station models, versions, positions and available rehearsal time to the technical production and coordination service. The record should distinguish tests completed from items still open.

Frequently asked questions

Why can a Green-GO channel change on a device be missing from the file?

Control 5 distinguishes editing a user from editing a device. A user change enters the file and reaches linked units; a device change applies only to that unit. Record the view used and save local values before loading another user.

Does saving the .gg5 file mean MCXD or WBPX will start with the rehearsed settings?

The file is stored on the computer. Save to devices stores the running configuration as the permanent startup configuration on adopted devices. Schedule it outside the show, then check conversations and startup on the test station.

Can I use Save to devices during a show?

The manufacturer says not to: it interrupts communication for up to one second. Reserve a window outside operation and check the units and configuration before saving. The documented interruption time does not replace testing each path afterward.

Does the orange Save to devices indicator mean there is a fault?

It indicates a difference between the running configuration and the one stored for startup. Review the change and plan saving outside the show. The indicator does not identify why channels were lost.

Do JOIN and ADOPT do the same thing in Green-GO Control?

JOIN takes the chosen device's configuration and replaces the one open in Control. ADOPT sends Control's configuration to selected units and overwrites what they were using. Preserve both states and choose the direction before confirming.

If my configuration is absent from Join Config, was it deleted?

On MCXD and WBPX, that list omits the configuration already in use. First check Info → Config → Name, Stamp and ID. Compare them with the reference station before loading another configuration.

Does Reload User restore a previous MCXD or WBPX configuration?

It reloads the current user and its settings. It does not automatically select an earlier backup. Save local differences and verify the intended user before running it; then repeat listen and response tests.

Does MERGE always preserve users already in the .gg5 file?

According to the manual, it may replace items with the same ID and cannot be undone. Save a copy before merging and compare affected items. Combining content does not prove that a complete event revision was restored.