Preparation and troubleshooting
grandMA3 onPC command wing: preparing real show output
A programming and playback surface that works with a computer. Specify the complete system, from the showfile to reception on stage.
Proposed test, scope and alternatives
The standard model needs an external computer running grandMA3 onPC; distinguish it from command wing XT. Confirm the exact software release, supported operating system and peripherals before committing to a show.
The current specification lists 4,096 parameters. This is processing capacity, not a connector count or a fixed universe allowance: patch attributes determine usage. The cited documentation caps an onPC system at 4,096; adding nodes does not exceed that ceiling.
The rear panel provides two DMX OUT ports, one DMX IN and USB type B for the computer. Ethernet distribution requires specifying the computer network interface, protocol and receiving nodes. An image in a visualizer does not prove reception at a fixture.
- Save a show copy and record software, profiles, parameter usage and universe destinations. Preserve the original before conversion or testing.
- Connect the wing and confirm recognition. Map each universe to a physical output or network destination; a port letter alone does not establish its function.
- With the operating area clear, propose a single-fixture test using simple values. Check reception, masters and patch, then rehearse the agreed recovery process after a disconnection.
Start with your date, venue and approximate needs. We can assess equipment, configuration and operation within an agreed scope.
Does it run without a computer?
The standard command wing requires grandMA3 onPC on an external computer. An integrated-computer system is a different variant to assess separately.
Do more nodes add parameters?
They may add connectors and distribution. In the documented onPC system they do not raise the 4,096 limit. Confirm enabling hardware and software before purchasing.
Can I divide 4,096 by 512 to size the show?
That calculation does not necessarily describe the show. Parameters and DMX slots are different concepts; inspect the actual patch count.
Why does visualization work while stage output does not?
Check recognized hardware, enabled output, universe mapping, network or cable and reception. Visualization alone does not verify that chain.
Should I reset when a wing is missing?
Preserve the show first, then check power, USB and configuration for the installed release. A global reset does not identify the cause.
What belongs in a quote request?
Date, venue, approximate fixture count, available patch, operator and required outputs. We can assess a wing-and-computer package, extra distribution or a standalone console for the show.