[{"data":1,"prerenderedAt":400},["ShallowReactive",2],{"navigation_docs_en":3,"-en-firmware-tracks-mobility-module":80,"-en-firmware-tracks-mobility-module-surround":397},[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,75],{"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",{"title":76,"path":77,"stem":78,"icon":79},"Tracks Mobility Module","\u002Fen\u002Ffirmware\u002Ftracks-mobility-module","en\u002F3.firmware\u002F2.tracks-mobility-module","i-lucide-bot",{"id":81,"title":76,"body":82,"description":390,"extension":391,"links":392,"meta":393,"navigation":394,"path":77,"seo":395,"stem":78,"__hash__":396},"docs_en\u002Fen\u002F3.firmware\u002F2.tracks-mobility-module.md",{"type":83,"value":84,"toc":372},"minimark",[85,89,98,101,106,109,112,128,132,135,138,142,148,165,168,176,180,186,200,203,207,212,215,220,250,254,257,273,277,282,285,289,311,315,318,322,354,358,361],[86,87,76],"h1",{"id":88},"tracks-mobility-module",[90,91,92,93,97],"p",{},"The ",[94,95,96],"code",{},"tracks"," module is the most concrete public firmware slice of Keero Bot today.",[90,99,100],{},"It is the part of the project that already bridges firmware, mechanics, wiring, and a clear mobility use case.",[102,103,105],"h2",{"id":104},"why-it-matters","Why It Matters",[90,107,108],{},"This module is important because it shows that Keero Bot is not only a mainboard concept.",[90,110,111],{},"It already has a real path toward:",[113,114,115,119,122,125],"ul",{},[116,117,118],"li",{},"movement",[116,120,121],{},"embodied AI experiments",[116,123,124],{},"demoable physical interaction",[116,126,127],{},"repeatable module-level iteration",[102,129,131],{"id":130},"attribution-and-project-lineage","Attribution and Project Lineage",[90,133,134],{},"The mobility concept is inspired by the ESP-SparkBot direction.",[90,136,137],{},"Because of that, Keero keeps the mechanical references and public credits visible instead of pretending the module started from a blank page. The Keero contribution is the adaptation, firmware work, platform integration direction, and the updated controller approach.",[102,139,141],{"id":140},"what-is-keero-specific","What Is Keero-Specific",[90,143,144,145,147],{},"The current Keero ",[94,146,96],{}," implementation is centered around:",[113,149,150,153,159,162],{},[116,151,152],{},"Keero-authored open-source firmware",[116,154,155,156],{},"an updated module PCB direction using ",[94,157,158],{},"ESP32-C3-WROOM-M2",[116,160,161],{},"Arduino and PlatformIO compatibility",[116,163,164],{},"integration thinking that fits the broader Keero modular platform",[90,166,167],{},"In practice, that means:",[113,169,170,173],{},[116,171,172],{},"the mobility idea acknowledges its inspiration",[116,174,175],{},"the working firmware and adaptation path are clearly Keero work",[102,177,179],{"id":178},"firmware-scope","Firmware Scope",[90,181,182,183,185],{},"The public ",[94,184,96],{}," firmware already demonstrates several real subsystems:",[113,187,188,191,194,197],{},[116,189,190],{},"motion control",[116,192,193],{},"lighting control",[116,195,196],{},"battery and power monitoring",[116,198,199],{},"serial command parsing for testing and control",[90,201,202],{},"That is enough to present the module as active engineering work rather than a placeholder.",[102,204,206],{"id":205},"reference-bill-of-materials","Reference Bill of Materials",[90,208,92,209,211],{},[94,210,96],{}," module is documented here with practical reference parts that were used during bring-up and mobility testing.",[90,213,214],{},"This is not presented as a locked production BOM. It is a public reference set for developers who want to understand the module stack and mechanical direction.",[216,217,219],"h3",{"id":218},"core-mobility-platform","Core mobility platform",[113,221,222,232,239],{},[116,223,224,225],{},"tracked chassis reference:\n",[226,227,231],"a",{"href":228,"rel":229},"https:\u002F\u002Fwww.aliexpress.com\u002Fitem\u002F1005011612359536.html?spm=a2g0o.order_list.order_list_main.52.1a141802qpneZl",[230],"nofollow","AliExpress reference link",[116,233,234,235],{},"pogo interconnect, 4-pin:\n",[226,236,231],{"href":237,"rel":238},"https:\u002F\u002Fwww.aliexpress.com\u002Fitem\u002F1005010390646641.html?spm=a2g0o.order_list.order_list_main.70.1a141802qpneZl",[230],[116,240,241,242,245,246],{},"DC motors, 3V, quantity ",[94,243,244],{},"2",":\n",[226,247,231],{"href":248,"rel":249},"https:\u002F\u002Fwww.aliexpress.com\u002Fitem\u002F1005005699205905.html?spm=a2g0o.productlist.0.0.75e3MQOnMQOn9t",[230],[102,251,253],{"id":252},"integration-notes","Integration Notes",[90,255,256],{},"At a public level, the mobility module should currently be understood like this:",[113,258,259,262,267,270],{},[116,260,261],{},"the mechanics follow the SparkBot-inspired tracked format",[116,263,264,265],{},"the Keero PCB\u002Fcontroller direction was updated around ",[94,266,158],{},[116,268,269],{},"the module now fits an Arduino and PlatformIO workflow more naturally",[116,271,272],{},"the pogo connector provides a compact path for docking or module-to-mainboard connection",[102,274,276],{"id":275},"prototyping-context","Prototyping Context",[90,278,92,279,281],{},[94,280,96],{}," module also reflects the practical prototyping side of Keero Bot.",[90,283,284],{},"Its mobility direction, controller adaptation, and public hardware documentation were developed as part of the broader prototype effort supported by PCBWay. That support matters because modules like this benefit from repeated fabrication, testing, and iteration rather than a single static build.",[102,286,288],{"id":287},"visual-references","Visual References",[290,291,294,301,306],"div",{"className":292},[293],"keero-docs-gallery",[295,296],"img",{"alt":297,"className":298,"src":300},"Tracks 3D overview",[299],"keero-docs-image","\u002Fkeero\u002Fmodules\u002Ftracks\u002Fimages\u002Ftracks-3d.png",[295,302],{"alt":303,"className":304,"src":305},"Tracks wiring overview",[299],"\u002Fkeero\u002Fmodules\u002Ftracks\u002Fimages\u002Ftracks-wiring.png",[295,307],{"alt":308,"className":309,"src":310},"Tracks overall wiring overview",[299],"\u002Fkeero\u002Fmodules\u002Ftracks\u002Fimages\u002Ftracks-overall-wiring.jpeg",[102,312,314],{"id":313},"open-mechanical-reference-files","Open Mechanical Reference Files",[90,316,317],{},"The mobility mechanics are intentionally shared here together with attribution context, since this part of the module direction is openly acknowledged as inspired by the original SparkBot approach.",[102,319,321],{"id":320},"downloads","Downloads",[113,323,324,330,336,342,348],{},[116,325,326],{},[226,327,329],{"href":328},"\u002Fkeero\u002Fmodules\u002Ftracks\u002F3d\u002Ftracks_Body_top.STL","Tracks body top STL",[116,331,332],{},[226,333,335],{"href":334},"\u002Fkeero\u002Fmodules\u002Ftracks\u002F3d\u002Ftracks_body_btm.STL","Tracks body bottom STL",[116,337,338],{},[226,339,341],{"href":340},"\u002Fkeero\u002Fmodules\u002Ftracks\u002F3d\u002Ftracks_driver_wheel.STL","Tracks driver wheel STL",[116,343,344],{},[226,345,347],{"href":346},"\u002Fkeero\u002Fmodules\u002Ftracks\u002F3d\u002Ftracks_idle_wheel.STL","Tracks idle wheel STL",[116,349,350],{},[226,351,353],{"href":352},"\u002Fkeero\u002Fmodules\u002Ftracks\u002F3d\u002Ftracks_idle_wheel_cover.STL","Tracks idle wheel cover STL",[102,355,357],{"id":356},"public-positioning","Public Positioning",[90,359,360],{},"For open documentation purposes, this module is a good example of the Keero release model:",[113,362,363,366,369],{},[116,364,365],{},"firmware is public",[116,367,368],{},"module mechanics can be shared when attribution and origin matter",[116,370,371],{},"platform-level production details still stay more selective",{"title":373,"searchDepth":374,"depth":374,"links":375},"",2,[376,377,378,379,380,384,385,386,387,388,389],{"id":104,"depth":374,"text":105},{"id":130,"depth":374,"text":131},{"id":140,"depth":374,"text":141},{"id":178,"depth":374,"text":179},{"id":205,"depth":374,"text":206,"children":381},[382],{"id":218,"depth":383,"text":219},3,{"id":252,"depth":374,"text":253},{"id":275,"depth":374,"text":276},{"id":287,"depth":374,"text":288},{"id":313,"depth":374,"text":314},{"id":320,"depth":374,"text":321},{"id":356,"depth":374,"text":357},"Public notes about the Keero mobility module firmware, attribution, and open assets.","md",null,{},{"icon":79},{"title":76,"description":390},"gpSUL9BLmSQBmEoT4-M8-7nN84smdf2ulyog_R6OQqo",[398,392],{"title":71,"path":72,"stem":73,"description":399,"icon":74,"children":-1},"Current firmware position and the broader roadmap for the Keero Bot platform.",1775642732145]