<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Robot Teleoperation on Fondsites</title><link>https://fondsites.com/tags/robot-teleoperation/</link><description>Recent content in Robot Teleoperation on Fondsites</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 29 May 2026 13:43:57 +0300</lastBuildDate><atom:link href="https://fondsites.com/tags/robot-teleoperation/feed.xml" rel="self" type="application/rss+xml"/><item><title>Robot Operator Interfaces: How Machines Ask for Help</title><link>https://fondsites.com/physical-ai-lab/guidebooks/robot-operator-interfaces/</link><pubDate>Sun, 17 May 2026 09:12:00 +0300</pubDate><guid>https://fondsites.com/physical-ai-lab/guidebooks/robot-operator-interfaces/</guid><description>&lt;p&gt;A useful robot has to communicate before it needs rescuing.&lt;/p&gt;
&lt;p&gt;That sounds obvious until a robot gets stuck in an aisle, stops beside a doorway, refuses to pick an object, or returns to its dock without finishing the job. The machine may have good reasons. Its map may disagree with the room. Its battery may be low. A protective stop may have fired. A camera may be dirty. A person may be standing inside a safety zone. A grasp planner may be uncertain about the object pose. To the people around it, though, the first visible fact is simpler: the robot stopped, and now someone has to decide what to do.&lt;/p&gt;</description></item></channel></rss>