Embedded Controller
01An OS-based controller is built into the gripper module.
Son
SDR-native gripper module with an embedded controller and middleware-level interface.
Unlike grippers that expose only motor-control, firmware, or low-level fieldbus interfaces, Son is designed as a network-connected robotic module with its own OS-based controller and SDR-level communication path.
Son gripper hero image placeholder
Future verified platform visual or technical asset
Conventional gripper interface
Many grippers provide interfaces close to the actuator layer, requiring additional controller configuration, firmware handling, fieldbus setup, or separate integration work before they become usable inside a robotic system.
Son approach
Son moves the integration boundary upward by embedding an OS-based controller and exposing a middleware-level interface that can connect directly into networked robotic workflows.
Integrated architecture
Son combines gripper mechanics, embedded control, middleware communication, and network-level connectivity into a deployable end-effector module.
Son architecture placeholder
Future verified platform visual or technical asset
An OS-based controller is built into the gripper module.
Manipulation commands are handled through a higher-level module interface.
The control path is designed around middleware communication rather than only firmware-level commands.
The module is designed to connect directly at the network level for system integration.
Workflow
By exposing a higher-level module interface, Son is prepared for workflows that involve middleware commands, teleoperation, data collection, and AI-based robotic application development.
Son workflow diagram placeholder
Future verified platform visual or technical asset
Features
Son includes an internal controller running at the module level, not only a motor driver or low-level actuator interface.
Gripper operation is exposed through a middleware-level interface prepared for software-defined robotic workflows.
The module can connect at the network layer without requiring a separate low-level fieldbus configuration path.
Prepared for teleoperation, data collection, AI workflow integration, and practical manipulation workflows.
Technical summary
Son is positioned as a gripper module with a higher-level control interface, not as a low-level actuator component or fieldbus-only peripheral.
Verified mechanical and electrical specifications can be added later when final platform material is ready.
Son inquiry