MultiDyne Acquires MRMC, Expands into Camera Robotics and Motion Control
MultiDyne has absorbed the assets of MRMC — Mark Roberts Motion Control — folding a 60-year-old camera robotics manufacturer into its signal-transport portfolio.

Asset Scope and Product Overlap
MultiDyne's stated reasoning rests on complementary, non-overlapping product lines. MultiDyne handles fiber-optic transport, camera interface, and signal processing. MRMC handles robotic camera systems, automated tracking, motion control rigs, and virtual production automation. No shared SKUs, no shared engineering teams reported in the announcement. That separation matters operationally: there is no immediate rationale for a forced roadmap consolidation, and existing MRMC tolerances for repeat-frame accuracy, encoder latency, and rig payload should remain on their current specifications until MultiDyne publishes revised product briefs. Frank Jachetta, MultiDyne's CEO, frames the move as extending reach to "the point of image acquisition itself" — language that signals intent to integrate upstream but stops short of announcing product-line changes.
Operational Continuity
Neil Maycock, already on MultiDyne's leadership team, takes over as Managing Director of MRMC. UK manufacturing and engineering stay in place. For rental houses and sports broadcasters running MRMC heads, sliders, and tracking rigs on active contracts, the immediate variables to monitor are: warranty terms, service-level agreements, firmware update cadence, and parts availability for legacy units. MultiDyne's fiber and interface channels will likely accelerate MRMC's global distribution footprint, but distribution expansion tends to introduce 60-to-90-day pricing volatility during channel re-mapping. Buyers holding pending POs should confirm pricing locks before the integration window.
What to Verify Before the Next Purchase Cycle
For anyone specifying robotics on a 2026 production, three data points are worth requesting directly from MultiDyne Robotics and Motion Control: the maintenance schedule for existing MRMC controllers, the roadmap status of any announced but unreleased motion-control platforms, and the integration path between MultiDyne's signal transport layer and MRMC's rig controllers. Cross-vendor latency budgets — the sum of transport, processing, and robotic actuation delays — are the metric that will actually change once engineering teams begin sharing documentation. Until MultiDyne publishes revised tolerance figures, assume current MRMC-published specs remain authoritative. The combined entity now spans signal acquisition through camera movement, which is a meaningful scope expansion on paper; whether that produces tighter integration or simply a longer sales deck remains to be tested in the field.