Frontend
Force-Closure Condition for Cooperative Multi-robot Pushing of Rectangular Objects
arXiv cs.RO0 views
arXiv:2611.13268v1 Announce Type: new Abstract: In cooperative object manipulation, the placement of pushing contacts determines whether force closure can be achieved and agents can generate arbitrary forces and torques on the object correspondingly. This study derives a necessary and sufficient closed-form condition for the planar force closure of a rectangular object, a common object shape in everyday settings, under four frictionless pushing contacts. For a rectangle of length $b$ and width $a$, force closure holds if and only if $(l_1+l_3-b)(l_2+l_4-a)<0$, where $l_1,l_2,l_3,l_4$ are the four edge contact locations. This condition is independent of the object's center of mass and is used to verify contact configurations before contact force allocation. When the condition is not satisfied, the signs of the two factors indicate which opposing contact pair should be adjusted. The condition and adjustment rule are then integrated into a full-pose trajectory-tracking framework as a geometric feasibility layer to demonstrate their use in control. Static wrench feasibility tests validate the proposed condition, while narrow-passage floating-body simulations show that maintaining a force-closure configuration reduces the RMS tracking errors in $x$, $y$, and unwrapped yaw from $12.05$ m, $18.11$ m, and $535.96^\circ$ to $2.24$ m, $2.66$ m, and $2.69^\circ$, respectively.
Source:https://arxiv.org/abs/2611.13268PreviousCurie's Jarvis: Autonomous Robotic Chemistry Experiments from Printed ProtocolsNextRaMOD: Moving-Object Detection from Raw mmWave Radar Cubes under Ego Motion
Related posts
800 MB of Arrays Nobody Asked For
0dev.to WebDev

One link to get into a client's App Store Connect, GitHub and DNS, without a shared password
0dev.to WebDev
The 7 Nuxt 4 changes that actually break apps (and how to find them in 10 seconds)
0dev.to WebDev
Why Disabling Downloads Does Not Revoke a Signed URL
0dev.to Security
OAuth Redirect URIs Need a Test Trust Boundary
0dev.to Security
Wazuh rule with <hostname> matches in wazuh-logtest but never fires for agent events
0dev.to Linux