Backend
Suspended-Fabric Robotic Manipulation Surfaces: Modelling, Design Space, and Multimodular Extensio
arXiv cs.RO0 views
arXiv:2610.41982v1 Announce Type: new Abstract: Robotic Manipulation Surfaces (RMS) reposition objects by deforming the surface on which they rest. A recent class of RMS suspends a continuous fabric sheet from a sparse grid of vertical linear actuators lowering the actuator density of such surfaces but how to design such surfaces so that objects can be controlled everywhere on it, and how to extend it beyond a single module so that objects can pass between modules and achieve parallel, remain open. This paper presents a separable catenary model of the suspended sheet that is fast to compute and provides both the surface shape for given actuator heights and the actuator heights for a desired local slope. The closed form inverse lets a simple PID controller position objects on the sheet, and the model relates fabric length, module span and actuator stroke to the reachable workspace, yielding a minimum fabric length bound and design charts for these surfaces. The approach is then extended to a multimodular platform in which neighbouring modules share actuators. On a $2 \times 2$ prototype, we demonstrate that centimetre-scale objects are transferred between modules and positioned within 0.03 m over a $1 m^2$ workspace with only nine actuators, enabling multi-object manipulation and opening the way to parallel manipulation.
Source:https://arxiv.org/abs/2610.41982PreviousDesign and Validation of a Robotic Knee Exoskeleton with Musculoskeletal Simulation-Derived Biological Torque ControlNextNexus-VLA: Bridging Human and Robot Experiences via a Shared Hierarchical Semantic Latent Space
Related posts
Human-in-the-loop architecture
0dev.to
Which Hosting Platforms Have an MCP Server So Claude Can Deploy Your App? (I Checked 5)
0dev.to
Can you flash Samsung firmware with a locked bootloader?
0dev.to
Learning AI should feel like building, not just watching
0dev.to
Swiggy Scraper in Python: Dish Prices and Menus by Location
0dev.to

Why Rust Finishes That Loop Before Python, PHP, JavaScript, and Go
0dev.to