Webserver: Robot Control & Monitoring Interface

What this includes

• A browser interface served from the robot's own onboard computer, so there is nothing to install on your machines and nobody needs ROS 2 to operate it.
• The robot's URDF model drawn with every joint, beside live camera and LiDAR streams, with the raw ROS 2 topic data underneath them for diagnostics.
• A VNC session onto the onboard computer, for the work a web form cannot cover: changing a Wi-Fi network, running something locally.
• Waypoints set against the robot's existing SLAM map, with actions attached to them, such as capturing an image on arrival.
• Tool-centre-point waypoints for arm control, through the inverse kinematics solver. Arm-equipped platforms only.
• Start and stop for every onboard service: camera, navigation, audio, the web server itself. Walking modes switch here too, on the platforms that have them.
• Speech, through a text-to-speech engine and a connector to a language model such as the OpenAI Realtime Speech API, with a context window you define.
• Teleoperation, supported and switched off by default. It stays off until you ask for it to be enabled.
• This is a front end onto systems that already exist on the machine. Outdoor SLAM navigation, arm teleoperation and speech interaction appear here only where they have been built and deployed for that specific robot.
• Ongoing support, customisation and further development are not included. They are charged by the hour, like the rest of our engineering.