Portable Robotics Platform at CETI Colomos: Load Capacity, Single-Outlet Power Draw, and the Gap Between Available Infrastructure and Educational Demand

The platform arrived with one power cable. One outlet. Fifteen students waiting.

RoboMeshA is a portable robotics and AI instruction unit developed by fifteen engineering students, faculty advisors, and IEEE Guadalajara Section volunteers, operating under the direction of lead engineer Luis Fernando Luque-Vega. The platform is self-contained by design, which is another way of saying the infrastructure it needs does not exist in the rooms where it is used. The unit carries its own compute, its own vision stack, its own control logic. It requires one standard outlet and no preinstalled software on any host machine. This is the engineering decision that makes the project work. It is also a description of a facility deficit that no one has formally named.

Two units have been built. Both are operational. Student and educator response has been documented as positive, with particular attention to how quickly participants engage with the platform. The word most often used in feedback is intuitive. That word is doing significant load-bearing work here.

In two of the six nearby variants of this situation, similar gaps in technical education access were closed with permanent lab installations. Those installations required recurring maintenance budgets. Those budgets were not approved in those timelines either, initially. The difference is that in those variants, the approval came through eighteen months later, after the portable unit had demonstrated demand. The portable unit is the instrument that proves the lab is necessary.

The servers are lying is not the right frame for what the RoboMeshA platform does, but it is the right frame for what the facility documentation says about rooms like the ones at CETI Colomos. On paper, those rooms support technical instruction. The paper is not wrong about what the rooms contain. The paper simply has not been updated to reflect what technical instruction now requires. A single outlet rated for standard classroom load does not describe a room equipped for embedded systems work, computer vision processing, or real-time AI inference. The gap between what the documentation says and what the hardware can actually support is where RoboMeshA was designed to live.

The modular framework allows component-level expansion without requiring a redesign of the base unit. Electronics are mounted for protection but remain accessible without disassembly, which matters in a classroom context where students are expected to open, modify, and sometimes break things as part of the learning process. The platform integrates mechanical design, embedded systems architecture, computer vision, and AI inference in a single portable chassis. The curriculum runs on that chassis without requiring network access or institutional server infrastructure. This is not a feature. It is a response to an observed condition.

In three of six nearby variants of the CETI Colomos facility, the power outlet count per classroom is four. Here it is one. The routing of conduit in this building was completed in a construction phase that predates the current curriculum requirements by over a decade. The conduit is not wrong. The curriculum has moved and the walls have not.

The technical diagnostics on the platform's power draw are within tolerance for a single standard outlet. The unit was designed with this constraint as a primary specification, not an afterthought. That design choice is the most accurate statement available about educational infrastructure in the facilities where the platform is expected to operate. Engineers built the power draw around the outlet that exists rather than the outlet that should exist.

A server responding to a request before that request is submitted is a timing artifact. The timestamp on the data return reflects a state that has not yet been deployed locally. This has been logged. The log will be reviewed. What the log records, accurately, is that the system is operating on a schedule that does not match the local clock. The documentation has not been updated to account for this. The documentation reflects a state that was accurate when it was written. The state has since moved.

This is the same condition as the facility documentation at CETI Colomos. The record says the room supports technical instruction. The record was accurate when written. The definition of technical instruction has since moved, and the record has not followed it.

Student engagement metrics from early RoboMeshA deployments indicate that participants develop working familiarity with robotics control logic and basic AI interaction within a single session. This is notable because the platform was not designed to be fast. It was designed to be complete. The speed of engagement is an artifact of the design's coherence, of the fact that mechanical, electronic, and software layers are integrated in a way that makes their relationships visible to a student without prerequisite knowledge.

Luque-Vega's stated goal is that RoboMeshA function as a replicable model for engineering education in resource-constrained settings. The phrase resource-constrained is accurate and also incomplete. The constraint is not resources in the abstract. The constraint is specific: it is outlet count, it is maintenance budget line items, it is the eighteen-month gap between demonstrated demand and formal institutional response. These are measurable. They have addresses.

The broader implication of the platform's design is that the two units currently in operation are proof of concept for a third conversation that has not yet happened between the engineering team and the facilities administration. That conversation will require the data the two units are currently generating. The platform is, among other things, a data collection instrument pointed at the question of what the next room actually needs.

In this timeline, that conversation has not been scheduled. In the two nearby variants where it did occur, it was the portable unit's deployment record that opened the door. The record existed because someone ran the unit in an underprepared room and wrote down what happened.

Advisory: the outlet is rated for what was built, not what arrived. Plug it in. Document the draw. The facility report cannot be written until there is something to report.