OPEN ENGINEERING REALITY · TRACK 001 · OPEN MOTION REALITY

FROM GPT TO MOTION.
Lower the cost of first physical success.

We are not building another motion-control-card company. We use mature, affordable industrial components as an accessible physical learning surface so engineers, students and makers can use GenAI to cross documentation, SDK, network and hardware boundaries faster.

研究正运动的目的不是与成熟运动控制方案竞争，而是降低全球爱好者和工程师第一次从 GPT 到真实执行成功的成本。

Reference Case 001 · ZMotion · 2026-05-30 Historical continuity record

RESEARCH TRACK C0-001 · Single-axis historical success does not prove robot or humanoid readiness.

WHY MOTION

Network-addressable motion is a bridge between AI intent and physical capability.

Mature hardware, lower entry costUse existing controllers, drives, motors and vendor SDKs instead of inventing every layer again.

GenAI crosses knowledge gapsLLMs help interpret manuals, libraries, APIs, failure codes and integration choices; human engineers verify the physical result.

Network does not equal remote safetyEthernet makes a controller addressable, but deterministic loops, limits, emergency behavior and safe state stay local.

Open reference, vendor-neutral destinationZMotion is the first historical reference case. Future tracks may use other motion-control ecosystems without changing the mother method.

REFERENCE CASE 001 · ZMOTION · 2026-05-30 HKT

One real servo result became a reusable engineering path.

Surviving HSIMC records index the original work item “正运动” at 2026-05-30 10:35:56 HKT. Recovered notes place the working context at 10:49:46 and the reported physical success at 12:19:13.

Historical stack:

HP Windows → C# / .NET Core 2.1 x64 → zauxdll.dll 2.1.1.0 / MiniZmcaux.cs → Ethernet → motion controller → Axis 0 → servo system → observed physical motion.

Recovered notes record connection ret=0, bounded OP0 switching ret=0, Axis 0 Single_Move and a short relative sequence: 1000, -1000, 2000, -2000, 500. Exact original build logs and the complete A2A thread are still being recovered, so the public record labels these as recovered historical engineering evidence rather than pretending every intermediate step is primary-source complete.

Controller identity remains under verification. XPLC532E is the current engineer recollection; an earlier summary used ZMC600M. We will keep both as candidates until primary machine/nameplate or original runtime evidence resolves the model.

FROM ONE AXIS TO ROBOTICS

The composition path is plausible; every higher level requires new validation.

1 AxisOne bounded motion capability with known units, state and local supervision.

Multi-axis / mechanismInterpolation, synchronization, homing, limits, feedback, recovery and machine geometry.

Manipulator / mobile robotKinematics, collision boundaries, force interaction, environment sensing and task-level safe states.

Humanoid / human-shared systemA research horizon only: far more sensing, dynamics, functional safety, supervision and independent acceptance are required.

GLOBAL INTENT · LOCAL DETERMINISM

Let intelligence travel. Keep consequential control local.

Global Intent

Research question, Work and human intent can originate anywhere.

LLM / e-Person

Interpret documentation, form candidates and reason about missing conditions.

MCP / capability interface

Discover and request bounded capability without confusing addressability with permission.

Local Runtime

Resolve machine state, Authority, limits, watchdog, safe mode and deterministic execution.

Physical Outcome

Controller, drive and actuator perform only the accepted local action.

Evidence

Read back the actual result and continue from evidence, not assumptions.

REFERENCE MATERIALS

Open our engineering path; keep supplier rights explicit.

The current ZMotion PC function-library manual states that the controller family supports direct PC online control with DLL libraries and examples for VC, VB, C#, Python and LabVIEW, and describes the common controller + drive + stepper/servo structure. The same manual separates software limits, hardware limits and alarm functions as safety mechanisms.

Official vendor-hosted PC programming manual · public V2.1.2Preview in browser; use the PDF viewer to download from the original vendor source. Restricted Research Team WorkspaceFor HSIMC working material and supplier-sensitive references that should not be exposed on the public surface.

HSIMC does not publicly mirror third-party SDK binaries or manuals merely because a password gate exists. Access control and redistribution rights are separate.

Safety boundary

Open Motion Reality does not authorize uncontrolled remote motion. A network-capable controller can be part of a global research workflow, but real-time control, emergency response, physical limits and human safety remain local and machine-specific. Humanoid, robot and manipulator use are future research scopes, not present product certification.

FROM GPT TO MOTION.Lower the cost of first physical success.