Week 18
Robot Assistant Project.

This project introduces an assistant robot designed to transform how the community, faculty, and visitors experience Universidad Indoamérica’s Technological Park. More than a single device, it is the first step of an exploratory project: a creative platform that brings tools, disciplines, and efforts from across the community into one shared, evolving endeavor.

It is conceived as a common ground where students from engineering, design, software, and the Fab Labs can converge — a real, physical problem on which to test ideas, prototype solutions, and learn by building something that lives and moves through the campus. The project also carries a deliberate social robotics dimension: by placing a robot in the everyday life of the park, it aims to normalize human-robot interaction so coexistence becomes natural rather than a novelty.

Its value lies as much in what it makes possible as in what it does — an open framework that invites contribution, iteration, and experimentation rather than a closed, finished product.

As a creative platform, the robot turns the Technological Park into a working laboratory: each function is an opportunity for a different group to design, fabricate, program, and integrate a piece of the whole. The robot is a screen-free physical companion that communicates through movement, light, and sound cues, following pre-recorded routes stored in memory to link laboratories, offices, and shared spaces. In this way it embodies the institution’s positioning as Ecuador’s first Technological Park of Innovation and Entrepreneurship — a campus where technology serves people and the community builds the very tools that define its future.

Stage One — Initial Functions

The first stage establishes the robot as everyday infrastructure: a presence that carries, informs, and serves the spaces where innovation happens.

• Campus courier. Moves documents, samples, tools, and materials between distant labs and offices through onboard secure compartments that open only at the destination.
• Components & tool transport. Carries robotic components, electronic parts, and shared tools between the Robotics Lab, Fab Lab, and offices — fittingly, the courier of the very parts used to build robots like itself.
• Mobile noticeboard. Carries printed announcements, posters, and QR cards as it circulates, becoming a moving channel that reaches every block without screens.
• Maintenance scout. Flags anomalies it encounters — burnt-out lights, blocked paths, open doors — feeding a simple facilities report.
• Scheduled timekeeper. Marks the rhythm of the campus day on a fixed schedule, signaling class changes and break times with light and sound cues.
• Document & print delivery. Collects finished prints, plots, or bound documents from print stations and delivers them to the requesting lab or office.
• Onboarding companion. Runs a simple “follow me” introductory route for first-week students or new staff, leading them past key labs and service points.

Stage Two — Expanded Functions

The second stage builds on the proven foundation, adding roles that deepen the robot’s value once core operation is established.

• Supply replenishment runner. Detects when consumables, paper, or first-aid kits run low and carries the refill — closing a real operational loop.
• Environmental & safety monitor. Logs temperature, humidity, air quality, and noise, responding to critical thresholds with distinct cues — a mobile early-warning layer.
• Space-usage logger. Records which areas are most active, generating usage data for space management, resource planning, and accreditation.
• Mobile charging & tool station. Comes to you when your laptop dies, carrying outlets, USB ports, chargers, adapters, and clickers.
• After-hours security patrol. Patrols the empty campus at night — lighting dim areas, detecting motion or open doors, and recording its rounds.
• Wayfinding & accessibility anchor. Provides a dependable physical escort for visitors with reduced mobility or anyone new.
• Lost-and-found drop point. Receives found items in a designated compartment and returns them to a central desk.
• Roaming project showcase. Displays rotating student and faculty work, becoming a moving portfolio of the park’s output.
• Event companion. Takes a fixed-position role at fairs and open houses, animating the space and generating marketing content.
• Special Fab Lab functions. Integrates with fabrication spaces to support material transport, equipment monitoring, and project workflows.

The project draws on three established traditions. Delivery and service robots in campuses, hospitals, and hotels teach an operational lesson — a robot earns its place through reliable, repeated usefulness — and reveal the central UX challenge of sharing space with a machine. Guide and reception robots in museums and airports showed that people respond to a robot’s expressiveness and predictability far more than to raw capability, though they leaned on screens and conversation, a dependency this project deliberately sets aside. Social robotics research treats human-robot coexistence as something that must be cultivated over time — the precedent most directly aligned with this project’s intent.

What distinguishes this initiative is its synthesis and setting. Most precedents optimize a single function for an external user. This project treats the robot as a creative platform built by and for its own community — a localized experiment in how a community grows accustomed to robotics from the inside.

The work is fundamentally one of systems integration: a 70 cm omnidirectional cylindrical platform integrating holonomic four-wheel drive, a layered mechanical structure, secure cargo compartments, an onboard compute-and-control architecture, a navigation and obstacle-avoidance sensor suite, and a light-and-sound signaling system — all condensed into a single coherent object engineered to be accepted, trusted, and shaped by the community.

• Physical form. A cylindrical body of stacked sections — drive base, cargo compartments, electronics-and-power bay, and signaling top — each with its own resolved place within the form.
• Locomotion system. An omnidirectional drive on four omni wheels for smooth, holonomic movement and predictable reorientation along memory-based routes.
• Compartment system. Secure, lockable compartments sized for real cargo, resolving dividers, latching, open/closed sensing, and screen-free destination selection.
• Interaction language. A vocabulary of light and minimal sound that signals what the robot is doing — the concrete expression of the social robotics intent.
• Route & behavior logic. The system that records, stores, and plays back routes, coordinating drive and sensors and sequencing functions and cues.
• Electronic & control architecture. A modular integration of compute, motor control, power, sensing, and signaling so future teams can add stage-two functions without redesigning the whole.
• Identity. A name, character, and presence that turn a machine into a recognized member of the campus.

Purchased components are the organs; the body that houses and connects them is designed and fabricated in-house. The build pairs off-the-shelf electronics with custom Fab Lab fabrication.

• Compute & control. Raspberry Pi for high-level route logic and sequencing; Arduino Mega / ESP32 for real-time motor and sensor control; one motor driver per wheel.
• Movement. Four omni wheels (100–150 mm) and geared DC motors with quadrature encoders, sized for approximately 10–20 kg plus cargo.
• Navigation & sensing. Wheel encoders with line/marker following for fixed routes; ultrasonic and IR sensors plus bump switches for safety; an IMU for stable heading.
• Power. A LiFePO4 / Li-ion pack (12–24 V), BMS, DC-DC converters, fusing, an emergency cut-off, and a matched charger.
• Compartments. Servo or solenoid latches, reed/microswitch door sensors, and physical destination buttons or selectors.
• Signaling output. Addressable LED strips and a status ring as the primary expressive channel, plus a minimal piezo/DFPlayer sound emitter.
• Fabricated in-house. The skeleton, sectional cylinder body, drive deck, compartments, mounts and housings, and interface surfaces — laser-cut, 3D-printed, and CNC-milled in the Fab Lab.

Components are sourced primarily from local and regional suppliers to keep lead times short and ease replacement and iteration; only parts un available locally come from specialized online distributors, and custom structural elements are fabricated in-house rather than purchased.

The build draws on a focused set of digital fabrication processes, moving in sequence from design to integration.

• CAD. Models the complete assistant as a single coordinated assembly, verifying clearances for purchased parts and generating files for every downstream process. Nothing is made until resolved here.
• Computer-controlled cutting. Produces flat structural and surface elements — level plates, internal ribs, press-fit joints, panels, and light diffusers — fast and cheap to iterate.
• CNC machining. Produces the load-bearing drive-deck base plate, holding the wheel geometry rigidly under the full weight of robot and cargo.
• Embedded programming. Writes the firmware that drives motors, reads encoders, polls sensors, and executes the route record-and-playback logic.
• Input & output devices. Integrates encoders, line/marker sensors, ultrasonic and IR sensors, the IMU, and compartment door sensors — each placed to serve a specific function.
• Networking & communications. Links the high-level controller and the real-time microcontroller so a distributed set of electronics acts as one coherent behavior.
• Interface programming. The screen-free destination interface and the behavioral logic that translates capabilities into legible light and sound cues.
• System integration. Fits mechanical, electronic, control, and signaling subsystems into one cylinder — routing power, balancing weight, ensuring access — making it reliable enough to operate among people daily.

Naming the open questions honestly is part of the work; they define what still needs to be tested, decided, or designed.

• Movement & navigation: Will the holonomic drive move reliably across the park’s real floors, and is the memory-based route system precise and repeatable over distance, or will drift require correction waypoints? Can it stop for and navigate around people safely while completing routes?
• Form & fabrication: Will the stacked-section cylinder stay rigid and balanced once loaded, with a low enough center of gravity to prevent tipping, and can sections be fabricated and revised independently within the Fab Lab’s capacity?
• Power & autonomy: How long can it operate per charge, is that a useful working block, and how and where will it recharge within the campus rhythm?
• Compartments & courier: Are compartments sized for real cargo, is screen-free destination selection genuinely intuitive, and are contents secure enough to earn trust?
• Interaction & acceptance: Is the light-and-sound language legible without instruction, and will the community accept and use the robot rather than treat it as a novelty?
• Function & value: Which stage-one functions deliver real daily value, does the robot measurably reduce friction, and is the architecture truly open for future contributions?
• Institutional viability: Are components reliably available locally, is the budget sufficient once markups and replacements are counted, who owns and maintains the robot, and how is success measured?

The most decisive questions are the three the project cannot succeed without: reliable, safe movement among people; genuine community acceptance; and at least one function with real daily value. The rest refine the assistant — these three determine whether it earns its place at all.