[{"data":1,"prerenderedAt":355},["ShallowReactive",2],{"navigation_docs_en":3,"-en-hardware-mainboard":75,"-en-hardware-mainboard-surround":350},[4,25,65],{"title":5,"path":6,"stem":7,"children":8,"page":24},"Overview","\u002Fen\u002Foverview","en\u002F1.overview",[9,14,19],{"title":10,"path":11,"stem":12,"icon":13},"Introduction","\u002Fen\u002Foverview\u002Fintroduction","en\u002F1.overview\u002F1.introduction","i-lucide-home",{"title":15,"path":16,"stem":17,"icon":18},"System Architecture","\u002Fen\u002Foverview\u002Fsystem-architecture","en\u002F1.overview\u002F2.system-architecture","i-lucide-workflow",{"title":20,"path":21,"stem":22,"icon":23},"Partnership and Prototyping","\u002Fen\u002Foverview\u002Fpartnership-and-prototyping","en\u002F1.overview\u002F3.partnership-and-prototyping","i-lucide-handshake",false,{"title":26,"path":27,"stem":28,"children":29,"page":24},"Hardware","\u002Fen\u002Fhardware","en\u002F2.hardware",[30,35,40,45,50,55,60],{"title":31,"path":32,"stem":33,"icon":34},"Mainboard","\u002Fen\u002Fhardware\u002Fmainboard","en\u002F2.hardware\u002F1.mainboard","i-lucide-circuit-board",{"title":36,"path":37,"stem":38,"icon":39},"Power and Interconnect","\u002Fen\u002Fhardware\u002Fpower-and-signals","en\u002F2.hardware\u002F2.power-and-signals","i-lucide-battery",{"title":41,"path":42,"stem":43,"icon":44},"Modules and Mechanics","\u002Fen\u002Fhardware\u002Fmodules-and-mechanics","en\u002F2.hardware\u002F3.modules-and-mechanics","i-lucide-box",{"title":46,"path":47,"stem":48,"icon":49},"Manufacturing and Prototyping","\u002Fen\u002Fhardware\u002Fmanufacturing-files","en\u002F2.hardware\u002F4.manufacturing-files","i-lucide-file-stack",{"title":51,"path":52,"stem":53,"icon":54},"Module Interfaces","\u002Fen\u002Fhardware\u002Fconnector-map","en\u002F2.hardware\u002F5.connector-map","i-lucide-plug",{"title":56,"path":57,"stem":58,"icon":59},"Use Cases","\u002Fen\u002Fhardware\u002Forder-and-build","en\u002F2.hardware\u002F6.order-and-build","i-lucide-package-check",{"title":61,"path":62,"stem":63,"icon":64},"Board Viewer","\u002Fen\u002Fhardware\u002Finteractive-bom","en\u002F2.hardware\u002F7.interactive-bom","i-lucide-box-select",{"title":66,"path":67,"stem":68,"children":69,"page":24},"Firmware","\u002Fen\u002Ffirmware","en\u002F3.firmware",[70],{"title":71,"path":72,"stem":73,"icon":74},"Status and Roadmap","\u002Fen\u002Ffirmware\u002Fstatus-and-roadmap","en\u002F3.firmware\u002F1.status-and-roadmap","i-lucide-code-xml",{"id":76,"title":31,"body":77,"description":343,"extension":344,"links":345,"meta":346,"navigation":347,"path":32,"seo":348,"stem":33,"__hash__":349},"docs_en\u002Fen\u002F2.hardware\u002F1.mainboard.md",{"type":78,"value":79,"toc":325},"minimark",[80,84,88,93,96,112,115,119,122,125,139,143,148,151,154,158,161,178,181,185,188,191,195,198,201,205,208,211,225,229,232,253,256,260,263,266,275,278,305,309,312,316],[81,82,31],"h1",{"id":83},"mainboard",[85,86,87],"p",{},"The Keero mainboard is the core hardware unit of the platform. It concentrates the compute, interaction, power, and expansion responsibilities that make the rest of the system possible.",[89,90,92],"h2",{"id":91},"what-the-mainboard-is-meant-to-do","What The Mainboard Is Meant To Do",[85,94,95],{},"At product level, the mainboard acts as:",[97,98,99,103,106,109],"ul",{},[100,101,102],"li",{},"the processing core of the device",[100,104,105],{},"the connection point for sensors and interaction hardware",[100,107,108],{},"the power-management backbone",[100,110,111],{},"the interface layer for modular accessories",[85,113,114],{},"This is what allows Keero Bot to behave like a coherent platform rather than a collection of disconnected experiments.",[89,116,118],{"id":117},"why-the-board-matters","Why The Board Matters",[85,120,121],{},"From a system point of view, the mainboard is where the platform becomes believable.",[85,123,124],{},"It is the place where:",[97,126,127,130,133,136],{},[100,128,129],{},"compute meets interaction hardware",[100,131,132],{},"portable power becomes a real product concern",[100,134,135],{},"external modules connect back into one shared architecture",[100,137,138],{},"firmware can target one stable core instead of multiple ad-hoc boards",[89,140,142],{"id":141},"main-functional-areas","Main Functional Areas",[144,145,147],"h3",{"id":146},"compute","Compute",[85,149,150],{},"The board is built around an ESP32-S3 class architecture, giving the project a practical balance between embedded performance, connectivity, and firmware flexibility.",[85,152,153],{},"This makes the platform suitable for sensor-rich embedded interaction without pushing it into an unrealistic hardware scope.",[144,155,157],{"id":156},"sensing-and-interaction","Sensing and Interaction",[85,159,160],{},"The mainboard supports a multi-modal interaction stack that includes:",[97,162,163,166,169,172,175],{},[100,164,165],{},"camera input",[100,167,168],{},"audio input and output",[100,170,171],{},"haptic feedback",[100,173,174],{},"motion sensing",[100,176,177],{},"local display support",[85,179,180],{},"This multi-modal hardware story is one of the strongest parts of the project because it moves Keero Bot closer to a real device platform.",[144,182,184],{"id":183},"power","Power",[85,186,187],{},"The board includes a managed battery-oriented power subsystem designed for portable use and docking scenarios. Public documentation keeps this section conceptual rather than implementation-specific.",[85,189,190],{},"That is enough to communicate product intent while protecting lower-level production detail.",[144,192,194],{"id":193},"expansion","Expansion",[85,196,197],{},"The board exposes modular interfaces so the same core platform can support additional hardware such as docks, mobility systems, and future expansion concepts.",[85,199,200],{},"In other words, the mainboard is not only the current board. It is the base for the broader Keero hardware family.",[89,202,204],{"id":203},"design-philosophy","Design Philosophy",[85,206,207],{},"The mainboard was not designed as a generic breakout board. It was designed as a compact product-oriented core with enough integration to feel serious, while still leaving room for rapid iteration through attached modules.",[85,209,210],{},"That balance matters for:",[97,212,213,216,219,222],{},[100,214,215],{},"firmware experimentation",[100,217,218],{},"industrial design iteration",[100,220,221],{},"module prototyping",[100,223,224],{},"sponsor and partner evaluation",[89,226,228],{"id":227},"publicly-visible-hardware-scope","Publicly Visible Hardware Scope",[85,230,231],{},"The current public release communicates that the mainboard already integrates:",[97,233,234,236,239,242,245,248,250],{},[100,235,146],{},[100,237,238],{},"camera path",[100,240,241],{},"display path",[100,243,244],{},"audio path",[100,246,247],{},"haptic support",[100,249,174],{},[100,251,252],{},"development and module access",[85,254,255],{},"That is enough detail for high-level technical evaluation without exposing the project as a replication package.",[89,257,259],{"id":258},"schematic-previews","Schematic Previews",[85,261,262],{},"The following previews are included as visual architecture references, not as a production release substitute.",[85,264,265],{},"The public documentation also includes a schematic PDF for technical review:",[97,267,268],{},[100,269,270],{},[271,272,274],"a",{"href":273},"\u002Fkeero\u002Fpdf\u002Fkeero_mainboard_schematic.pdf","Open mainboard schematic PDF",[85,276,277],{},"The PDF is presented as part of the high-level documentation package, while the broader production release remains controlled.",[279,280,283,290,295,300],"div",{"className":281},[282],"keero-docs-gallery",[284,285],"img",{"alt":286,"className":287,"src":289},"Power sheet preview",[288],"keero-docs-image","\u002Fkeero\u002Fimages\u002FSCH_Schematic_1-Power_Sheet_2026-04-03.png",[284,291],{"alt":292,"className":293,"src":294},"MCU sheet preview",[288],"\u002Fkeero\u002Fimages\u002FSCH_Schematic_2-MCU_Sheet_2026-04-03.png",[284,296],{"alt":297,"className":298,"src":299},"Sensor sheet preview",[288],"\u002Fkeero\u002Fimages\u002FSCH_Schematic_3-Sensor_Sheet_2026-04-03.png",[284,301],{"alt":302,"className":303,"src":304},"OLED sheet preview",[288],"\u002Fkeero\u002Fimages\u002FSCH_Schematic_4-OLED_Sheet_2026-04-03.png",[89,306,308],{"id":307},"public-access-note","Public Access Note",[85,310,311],{},"This page intentionally stays at subsystem level. Production sources, editable layouts, and manufacturing-specific files are not part of the public documentation release.",[89,313,315],{"id":314},"board-render","Board Render",[279,317,320],{"className":318},[319],"keero-docs-embed",[284,321],{"alt":322,"className":323,"src":324},"Mainboard overview",[288],"\u002Fkeero\u002Fimages\u002FPCB.png",{"title":326,"searchDepth":327,"depth":327,"links":328},"",2,[329,330,331,338,339,340,341,342],{"id":91,"depth":327,"text":92},{"id":117,"depth":327,"text":118},{"id":141,"depth":327,"text":142,"children":332},[333,335,336,337],{"id":146,"depth":334,"text":147},3,{"id":156,"depth":334,"text":157},{"id":183,"depth":334,"text":184},{"id":193,"depth":334,"text":194},{"id":203,"depth":327,"text":204},{"id":227,"depth":327,"text":228},{"id":258,"depth":327,"text":259},{"id":307,"depth":327,"text":308},{"id":314,"depth":327,"text":315},"High-level overview of the Keero Bot mainboard and its role in the overall platform.","md",null,{},{"icon":34},{"title":31,"description":343},"e55IfLSTjjIKsWda10WrydtQUrcM8FJXqQR7OVKwCcY",[351,353],{"title":20,"path":21,"stem":22,"description":352,"icon":23,"children":-1},"Why Keero Bot is a strong fit for prototyping partners and hardware sponsors.",{"title":36,"path":37,"stem":38,"description":354,"icon":39,"children":-1},"High-level view of how Keero Bot approaches power, docking, and subsystem communication.",1775557595672]