[{"data":1,"prerenderedAt":257},["ShallowReactive",2],{"navigation_docs_en":3,"-en-hardware-power-and-signals":75,"-en-hardware-power-and-signals-surround":252},[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":36,"body":77,"description":245,"extension":246,"links":247,"meta":248,"navigation":249,"path":37,"seo":250,"stem":38,"__hash__":251},"docs_en\u002Fen\u002F2.hardware\u002F2.power-and-signals.md",{"type":78,"value":79,"toc":235},"minimark",[80,84,88,93,96,109,112,115,119,122,125,139,143,146,157,160,163,167,170,173,187,191,194,211,214,218,221,224],[81,82,36],"h1",{"id":83},"power-and-interconnect",[85,86,87],"p",{},"Power and connectivity are central to the Keero Bot platform because the system is intended to move between portable operation, prototyping benches, and future docked or modular configurations.",[89,90,92],"h2",{"id":91},"power-strategy","Power Strategy",[85,94,95],{},"The public architecture of Keero Bot communicates three important points:",[97,98,99,103,106],"ul",{},[100,101,102],"li",{},"the platform is battery-capable",[100,104,105],{},"charging and power management are integrated into the core board",[100,107,108],{},"different subsystems are treated as separate functional domains, not as one flat undifferentiated power plane",[85,110,111],{},"That tells collaborators and sponsors that the board was designed with real product behavior in mind, even though the detailed implementation remains private.",[85,113,114],{},"Publicly, this is exactly the right level of visibility: enough to show maturity, not enough to expose the whole implementation recipe.",[89,116,118],{"id":117},"why-this-is-important-for-the-platform","Why This Is Important For The Platform",[85,120,121],{},"Keero Bot is meant to support more than a fixed bench setup.",[85,123,124],{},"That means the power and interconnect story has to support:",[97,126,127,130,133,136],{},[100,128,129],{},"bring-up and debugging",[100,131,132],{},"portable operation",[100,134,135],{},"future docked behavior",[100,137,138],{},"add-on modules with different physical roles",[89,140,142],{"id":141},"docking-and-external-access","Docking and External Access",[85,144,145],{},"Keero Bot is designed to support more than one interaction mode:",[97,147,148,151,154],{},[100,149,150],{},"direct development access",[100,152,153],{},"battery-powered standalone use",[100,155,156],{},"docked or accessory-assisted operation",[85,158,159],{},"This is where the modular strategy becomes important. The core board can stay stable while future accessories change the physical behavior of the system.",[85,161,162],{},"That makes the platform easier to prototype in stages and easier to present in sponsor conversations.",[89,164,166],{"id":165},"interconnect-philosophy","Interconnect Philosophy",[85,168,169],{},"The platform exposes enough board-level interconnect to make module development practical, but the public docs present this at capability level rather than at replication level.",[85,171,172],{},"In practice, the public story is:",[97,174,175,178,181,184],{},[100,176,177],{},"modules can exchange data with the mainboard",[100,179,180],{},"power can be shared where appropriate",[100,182,183],{},"docking is part of the intended user journey",[100,185,186],{},"the architecture supports iterative accessory development",[89,188,190],{"id":189},"public-interface-categories","Public Interface Categories",[85,192,193],{},"At a high level, the visible interconnect map includes categories for:",[97,195,196,199,202,205,208],{},[100,197,198],{},"power entry and battery integration",[100,200,201],{},"firmware and development access",[100,203,204],{},"camera and display attachment",[100,206,207],{},"audio and user interaction hardware",[100,209,210],{},"module and dock expansion",[85,212,213],{},"This communicates a serious board structure without turning the page into a public pinout package.",[89,215,217],{"id":216},"why-this-matters","Why This Matters",[85,219,220],{},"For an open firmware and modular hardware project, robust interconnect design is what makes the roadmap believable.",[85,222,223],{},"It shows that Keero Bot is being developed as:",[97,225,226,229,232],{},[100,227,228],{},"a reusable system foundation",[100,230,231],{},"a candidate for multiple hardware form factors",[100,233,234],{},"a platform that can grow through modules instead of repeated full-board redesigns",{"title":236,"searchDepth":237,"depth":237,"links":238},"",2,[239,240,241,242,243,244],{"id":91,"depth":237,"text":92},{"id":117,"depth":237,"text":118},{"id":141,"depth":237,"text":142},{"id":165,"depth":237,"text":166},{"id":189,"depth":237,"text":190},{"id":216,"depth":237,"text":217},"High-level view of how Keero Bot approaches power, docking, and subsystem communication.","md",null,{},{"icon":39},{"title":36,"description":245},"6d81Dz840PKspdy26Njn6-YCN7pjuWqbk3whwaJKSNo",[253,255],{"title":31,"path":32,"stem":33,"description":254,"icon":34,"children":-1},"High-level overview of the Keero Bot mainboard and its role in the overall platform.",{"title":41,"path":42,"stem":43,"description":256,"icon":44,"children":-1},"High-level description of the Keero Bot modular hardware strategy and current physical concepts.",1775557595687]