Role
Built the Unity runtime, Flask / UDP bridge, safety logic, calibration flow, and the Jacobian-based IK extension.
Industrial XR x Robotics
VR Robot Teleoperation
A working pipeline that connects Quest 3 controller input to a Doosan A0912 robot through Unity, Flask, RoboDK, safety logic, and later an in-house Jacobian IK extension.
Quest 3
Flask
RoboDK
In-house IK
Problem
XR input had to map cleanly to a real industrial robot while handling latency, safety, and future expansion.
Outcome
Delivered a public demo pipeline from Quest 3 to Doosan A0912 and later expanded the structure from myCobot 280 to industrial hardware.
Why It Matters
This is a direct proof of industrial XR that survived control constraints, safety logic, and real-world demonstration.
Pipeline
Quest 3 -> Unity -> Flask -> RoboDK -> Robot
The project started as a VR interface for remote robot control and later grew into a more independent robotics stack. I kept the runtime stable while adding EMA filtering, safety boxes, deadman switch behavior, and calibration steps that reduced control drift.
After the first demo pipeline was proven, I extended the work into a Jacobian-based IK solver so the stack would not stay dependent on RoboDK alone.
Safety and failure handling: deadman switch, safe box constraints, and posture protection were treated as part of the core control loop, not optional polish.
Verification target: control latency and response stability were measured around a practical demo threshold so the system could be shown in public without feeling fragile.
Technical expansion: the later IK work was not a separate toy project. It was the continuation of the same control problem under tighter ownership.
Roles: industrial XR, robotics interface, and real-time control workflows.