Jaime Arduino UNO Q AI Robot

Arduino® UNO™ Q 4GB

Arduino App Lab

Microservo 360

<html><body>One of the most interesting features of the Arduino UNO Q is its dual architecture: an MCU and an MPU capable of working together to build complex devices. I decided to build a robot driven by an AI agent running on the MPU, while assigning basic tasks—such as wheel movement and sensor readings—to the MCU. <figure><img src="https://projects.arduinocontent.cc/14ffcf77-2f4b-4c71-a62d-693d40063247.png"/><figcaption></figcaption></figure>With this approach, it is not necessary to write thousands of heuristic rules in advance to solve every possible problem. Instead, the AI agent running on the robot can decide how to orchestrate movements and sensor data in scenarios that were not even anticipated when the robot was built. <figure><img src="https://projects.arduinocontent.cc/37dc911b-e762-48d3-83b1-7be45b0e8505.png"/><figcaption></figcaption></figure>For example, when placed in a parking garage, the robot can be asked to find the first available spot and park, count the available spots, or even create a map of the parking lot. All of this can be achieved using a simple set of primitive functions combined with contextual information. The project involves several layers, and it is difficult to predict whether the results will meet the initial expectations. Nevertheless, it is well worth attempting. <h3>The Parts</h3><h3></h3><figure><img src="https://projects.arduinocontent.cc/16e86817-00f5-4c1d-8147-e76ebe4c561c.png"/><figcaption></figcaption></figure> The robot’s most fundamental capability is movement. One possible approach would be to use two precision motors with a motor shield or an H-bridge, together with sensors that determine the exact position of the wheels. However, because the goal is to keep the electronics to a minimum, I decided to use two continuous-rotation micro servos instead. They are powered from the same source and require only one signal wire each to control their movement and direction. For orientation and navigation inside the parking garage, the robot uses three sensors: an ultrasonic distance sensor with a single analog output instead of separate trigger and echo pins, a line-tracking sensor that detects floor markings, and a magnetometer. The complete parts list is: • 1 × <a href="https://docs.arduino.cc/hardware/uno-q/">Arduino UNO Q 4 GB </a>• 2 × <a href=" $ https://www.dfrobot.com/product-1579.html?tracking=hOuIhw4fDaJRTdy4abz04npbQC78dqxBkqVt7XMFYxEXj2s0ukWgm71wbut0ewUP $ ">SER0037 360-degree micro servos </a>• 1 × Gravity <a href=" https://www.dfrobot.com/product-1862.html?tracking=hOuIhw4fDaJRTdy4abz04npbQC78dqxBkqVt7XMFYxEXj2s0ukWgm71wbut0ewUP ">Ultrasonic Sensor V1.0 </a>• 1 × <a href="https://www.dfrobot.com/product-2626.html?tracking=hOuIhw4fDaJRTdy4abz04npbQC78dqxBkqVt7XMFYxEXj2s0ukWgm71wbut0ewUP ">HW-102 magnetometer using the QMC5883L chip </a>• 1 × <a href="https://amzn.to/4fAvCbk">ITLine Tracker sensor </a>• 1 × <a href="https://amzn.to/45nuDGK ">switch </a>• 2 × <a href="https://amzn.to/3RUF0yG">18650 batteries </a>Regarding the power supply, the Arduino UNO Q does not boot from a single 18650 battery because it requires at least 7 V through the VIN pin. I therefore used two 18650 batteries connected in series, providing approximately 8 V. <h3>The Circuit</h3><h3></h3><figure><img src="https://projects.arduinocontent.cc/157b9ff1-4366-43aa-a395-c8c7bf46e293.png"/><figcaption></figcaption></figure> • Left-wheel servo connected to D13 • Right-wheel servo connected to D12 • Ultrasonic sensor connected to A0 • Line sensor connected to A1. Strictly speaking, the sensor can provide a digital output by adjusting its sensitivity potentiometer, but using the analog output provides greater flexibility. • HMC5883L/QMC5883L magnetometer connected to SDA and SCL All positive leads from the servos and sensors are connected to the Arduino’s 3.3 V output, while all negative leads are connected to any available Arduino GND pin. The two batteries are connected in series, and the resulting power supply is connected to VIN and GND on the Arduino. <h3>The Architecture</h3><figure><img src="https://projects.arduinocontent.cc/8effad1c-3733-446e-839e-8c681e84728e.png"/><figcaption></figcaption></figure> The robot’s architecture is organized into three layers: 1. The MCU primitive-functions layer 2. The MCU–MPU bridge layer 3. The Python command layer The MCU provides the following primitive functions: • Move forward or backward for a specified number of seconds • Move forward or backward until reaching a specified line number. If an obstacle is detected first, stop and report that condition. • Move forward until the measured distance is less than a specified value • Rotate left or right for a specified number of seconds • Face forward, left, or right, using the magnetometer for minor heading corrections • Read the sensors These primitive functions are exposed to the MPU through a bridge that must remain accessible to the OpenClaw AI agent while running in the background. The bridge provides bidirectional, synchronous communication between the Debian Linux environment and the UNO Q microcontroller. When Python sends a command—either manually or through OpenClaw—the command is serialized using MsgPack and transmitted through a UNIX socket to bridge.py. The bridge then forwards the request to the Arduino firmware through the Arduino_RouterBridge library. The system waits for either a response from the MCU or a timeout. This ensures that every action can determine whether the command was executed successfully before returning its response. To manage simultaneous movement commands, such as moving forward and turning right, and to prevent contradictory actions from being executed at the same time, bridge.py implements mutual exclusion using a thread lock named self.moveLock. Whenever a command involves physical movement, its execution thread attempts to acquire the lock. If the robot is already performing another movement, the new command waits until the previous thread releases the lock. The command layer is implemented in the robot.py script. It can be used to test movements and sensors from the command line, and it is also used by OpenClaw to control the robot autonomously. <h3>Software Setup</h3><h3></h3><figure><img src="https://projects.arduinocontent.cc/26ed2548-6517-4e38-b495-a7ded6766586.png"/><figcaption></figcaption></figure>Install Arduino App Lab. Open Arduino App Lab and connect the board using a USB-C cable. Log in to your Arduino account. Install the following libraries: • Servo 1.3.0 • GyverMag 1.0.0 Open the MCU sketch and select Run at startup. Open a terminal and run: <pre><code class="code">curl -fsSL https://openclaw.ai/install.sh | bash </code> </pre>OpenClaw supports multiple AI model providers and messaging channels. This project uses OpenAI and Telegram, but other supported providers and channels can also be used. Obtain a Telegram Bot Token and Chat ID Open Telegram and search for @BotFather. Send: <pre>/newbot </pre>Follow the instructions to create a new bot and save the token provided by BotFather. Search for your new bot, open the conversation, and press Start. Then send a message to @userinfobot to obtain your personal Telegram chat ID. Enter the bot token and chat ID in the OpenClaw configuration. Connect to the Arduino UNO Q through SFTP using the same credentials configured for the board. Upload the OpenClaw skill to: <pre>/home/arduino/.npm-global/lib/node_modules/openclaw/dist/extensions/browser/skills/parking </pre>Copy bridge.py and robot.py to the root directory of the project. Run the bridge in the background: <pre>nohup python3 bridge.py &gt; bridge.log 2&gt;&amp;1 &amp; </pre>Run the OpenClaw TUI, or send a message to OpenClaw through Telegram. Ask it to install the parking skill and move the robot forward for one second to confirm that the system has been configured correctly. Every call to robot.py is logged to standard output with a timestamp, method name, and arguments. <h3>3D-Printed Parts</h3><figure><img src="https://projects.arduinocontent.cc/b03761b2-f419-4667-9fb9-fdeea4f0cf59.png"/><figcaption></figcaption></figure>Designing the robot was not a minor task. The enclosure had to accommodate several components while maintaining adequate balance and allowing the robot to move correctly. The printed parts consist of: • A chassis with an integrated battery holder • Two wheels • A top cover Several printing and modeling iterations were required before arriving at a suitable component arrangement. I added grooves to the wheels. However, when the robot is used on a slippery surface, better traction can be achieved by printing the wheels in a flexible material such as TPU or by applying small amounts of hot glue to the tread. To keep the front of the chassis elevated, I used a simple screw. It works, but it also introduces friction. Replacing it with a freely rotating caster wheel or ball caster would be preferable. The Parking Garage The test parking garage consists of a corridor with parking spaces on the right-hand side. Because the robot uses relatively simple sensors, a line is placed at the entrance of each parking space. This allows the robot to determine when it has reached the entrance to a spot. A wall is positioned at the back of each parking space so that it can be detected by the ultrasonic distance sensor. This layout is entirely arbitrary. It could be expanded by adding internal lanes, parking spaces on both sides, or a more complex route. The robot could also be adapted to other environments simply by modifying its skill, as explained below. <h3>The Skill</h3><figure><img src="https://projects.arduinocontent.cc/1efbd2f5-6251-427e-bc3c-12461cb24020.png"/><figcaption></figcaption></figure>To provide the local AI agent with contextual information about its role as an autonomous robot operating inside a parking garage, I created an OpenClaw skill. A skill is essentially a Markdown file with the .md extension. It functions as a modular, pluggable software component that connects the reasoning capabilities of the AI assistant—the OpenClaw agent or LLM—with the robot’s primitive functions. The skill contains information such as: • The parking garage layout • The number and location of the parking spaces • Rotation parameters • Movement constraints • Available robot commands • Rules for determining whether a spot is occupied All of this information is written in natural language. <h3>Magnetometer Calibration</h3>After turning on the robot, rotate it through several complete 360-degree movements around the X axis. Then open a terminal and run: <pre>python3 robot.py setup </pre>Follow the on-screen instructions to record the forward, left, and right headings. <h3>Prompting the Robot</h3><h3></h3><figure><img src="https://projects.arduinocontent.cc/a66cb553-c202-4a02-80b9-f534345be8ca.png"/><figcaption></figcaption></figure> The goal is to communicate with the robot through Telegram and ask it to solve tasks for which it was never explicitly programmed. The robot solves these tasks by combining its primitive functions according to the context provided by the skill. For example, when asked: Is the first parking spot available? The robot can use the information in the skill to construct the following plan: 1. Move forward until it reaches the line marking the entrance to the first parking space. 2. Rotate right so that its ultrasonic sensor faces the parking space. 3. Measure the distance. 4. Determine whether the sensor can detect the rear wall or whether another object is blocking it. If an object is detected before the expected wall position, the spot is considered occupied. 5. Respond in natural language. <figure><img src="https://projects.arduinocontent.cc/226bcdb2-a030-43bc-9cfc-22f9104f6d84.png"/><figcaption></figcaption></figure> Other example prompts include: • Park in the first available spot. • How many parking spaces are there? • Draw a map of the parking lot. • How many spots are empty? • Simulate a drunk driver. • What is the occupancy rate? Why Is It Called Jaime? The robot is called Jaime because that was the name used in the Latin American Spanish version of Get Smart—known as Super Agente 86—for the character originally named Hymie. <a href="https://getsmart.fandom.com/wiki/Hymie">https://getsmart.fandom.com/wiki/Hymie </a><h3>Final Notes</h3><figure><img src="https://projects.arduinocontent.cc/60bc549f-4b30-4c1b-9b85-54ea268bca8e.png"/><figcaption></figcaption></figure> The primary goal of this project was to keep both the hardware and software architectures as simple as possible. Even so, the same foundation could be extended to create a considerably more capable autonomous robot. Adding a camera, for example, would provide the local AI agent with much richer information about its surroundings, allowing it to make better-informed decisions and perform more sophisticated behaviors. The current design also requires the batteries to be removed for charging. Integrating an onboard lithium-ion charging circuit would make the robot significantly more practical for everyday use. From a development perspective, building an agentic AI robot with the Arduino UNO Q proved to be a smooth experience. The platform demonstrates that the traditional trade-off between using either a microcontroller or a microprocessor is no longer necessary. By combining both on the same board, real-time hardware control can be delegated to the MCU, while the MPU executes AI models and performs high-level reasoning. Perhaps the most important takeaway, however, is conceptual rather than technical. <figure><img src="https://projects.arduinocontent.cc/d002e3e6-65b3-4410-b242-9da2b9535934.png"/><figcaption></figcaption></figure> The central challenge is no longer the implementation of individual behaviors, but the design of devices capable of autonomous decision-making. Instead of hardcoding every possible situation, we can provide a robot with primitive actions, sensor data, contextual knowledge, and an AI agent capable of orchestrating these elements to solve problems that were never explicitly anticipated. This approach enables genuinely emergent behaviors, allowing the robot’s capabilities to extend well beyond what its creators originally envisioned. <h3>Videos</h3><h3><a href="https://www.youtube.com/shorts/6l1wQNMgGkE">https://www.youtube.com/shorts/6l1wQNMgGkE</a></h3><a href="https://www.youtube.com/shorts/SLtP8H7JJoM">https://www.youtube.com/shorts/SLtP8H7JJoM</a><h3></h3><figure><iframe src="https://www.youtube.com/watch?v=_GZKD7dg9gM"></iframe></figure><h3>Files</h3>Source code: <a href="https://github.com/ronibandini/Jaime">https://github.com/ronibandini/Jaime </a>3D-printable files: <a href="https://cults3d.com/en/3d-model/gadget/jaime-arduino-uno-q-ai-agentic-robot">https://cults3d.com/en/3d-model/gadget/jaime-arduino-uno-q-ai-agentic-robot </a><h3>Contact</h3>Roni Bandini • LinkedIn: https://www.linkedin.com/in/ronibandini/ • Instagram: https://www.instagram.com/ronibandini/ </body></html>

Jaime Arduino UNO Q AI Robot

An Agentic AI Robot Built on the Arduino UNO Q