Niscon Raynok
Motion control used in themed entertainment and arena work, usually integrated by the automation vendor. Data access is a project-level decision.
What it is
Raynok is Niscon's motion control platform, used for theatrical, arena and themed entertainment automation: multi-axis machinery running cued and often show-length sequences, with position feedback per axis and a safety architecture held separate from the motion control. It appears frequently in permanent installations and in large-scale arena and spectacular work, where automation is engineered as part of the venue or the attraction rather than assembled per production. In that context the system is commissioned, documented and maintained under a project or service agreement, and changes route through the party responsible for it. What a given installation can expose to third parties is a project-level decision made during engineering, not a general property of the platform, so treat it as something to ask about rather than something to look up.
How we work with it
On installation-scale work, get into the conversation during engineering rather than after commissioning. Ask what interfaces the integrator is already building, because a themed or arena project usually has a show control layer sitting above the automation, and the cheapest position feed is often one that layer already carries. Establish who owns change control after handover, since an integration nobody can maintain will be removed at the first service visit. Agree coordinate frames, units and axis naming as documentation rather than as a conversation. Keep the path read-only and off any safety-related network, publish in a form the lighting and media systems already consume, and define behaviour on loss of data at the consumer. Commissioning is the realistic window for proper testing.
Permanent installations have an engineering phase; a request made then costs a fraction of one made after handover
There is often a show control layer above the automation already carrying the data you want
Change control after handover decides whether the integration survives the first service visit
What an installation exposes is a project decision, not a general property of the platform
Right when
- You are in the design phase and the interface can still be written into the automation scope of work
- The automation runs long, repeatable, machine-driven sequences that lighting and media should follow exactly
- A show control layer already exists that can carry position without anyone touching the motion controller
Look elsewhere when
- The project is already commissioned and any change reopens a signed-off, tested scope
- The subjects are performers or guests moving freely, which machinery axes cannot describe
What protocol does Raynok output?
That is not answerable in general terms. Interface capability in this class of system is defined per project, during engineering, and depends on what was specified, what the integrator built, and what the operator will permit after handover. Anyone quoting a definitive answer without naming the installation is guessing. Ask the automation integrator about the specific site, and ask early enough that the answer can still change.
When should we raise this on an installation project?
During the engineering phase of the automation scope, before hardware is committed. At that point an output is a line item. After commissioning it becomes a change to a signed-off system, with retesting, documentation and sometimes recertification attached, and the party responsible for the automation has every reason to decline. The cost difference between those two moments is large and entirely avoidable.