Frequently asked questions

Chilly 3D is an ongoing robotics development project documented by Chilly ApS. The published work covers concept design, servo-joint development, early electronics and 3D-printed leg components. The website records both progress and technical challenges.

No completed, autonomous robot has been verified in the published project record. Existing photographs document real parts and prototypes, while the full-body illustration represents the design concept. Check the Development Journal for the latest confirmed progress.

The early development journal documents six tested and addressed servos, revisions to the hip, knee and ankle joints, and several rounds of printing and fitting leg components. These are historical milestones, not a claim that the entire robot is assembled.

The published introduction describes the ambition to develop a small humanoid robot capable of movement and, eventually, intelligent interaction. The shape provides an engineering goal; actual balance, movement and other capabilities must be demonstrated through testing.

Start with the Chilly 3D project page for an overview, then read the Development Journal for dated work, revisions, photographs and engineering decisions. New achievements should be documented there when confirmed.

The original Robotics site identifies Blender 5.2 as its 3D design tool, with a combination of manual modelling, Python-assisted work and ChatGPT-assisted problem solving. Software versions and workflows may change as development progresses.

Digital models help engineers define dimensions, check whether parts fit together, understand movement clearances and revise components before manufacturing. They are a practical starting point, not a substitute for physical testing.

Start with verified component dimensions, model mounting and movement clearances, allow for the manufacturing process, and print a test part. Actual fit should then be checked and documented; a CAD fit alone does not guarantee a working joint.

Robotic joints have competing requirements: strength, size, assembly access, movement range, wiring and manufacturability. Early printed parts expose problems that can be corrected in the next design revision.

Only drawings or files explicitly released through the Documents section are available for download. Working CAD models and incomplete revisions are not automatically public; the project will identify approved files when they are ready.

The original project pages identify a Bambu Lab P2S with an AMS 2 Pro. The historical documentation lists a build volume of 256 × 256 × 256 mm. Equipment information should be rechecked whenever the workshop setup changes.

PETG is documented as the initial printing material. ABS and polycarbonate were discussed as possible alternatives if later mechanical requirements justify them; this is not confirmation that those alternatives have been used.

Small prototypes let the team evaluate dimensions, mounting points, joint motion and assembly details before committing time and material to larger components. The Chilly 3D journal specifically describes repeated printing and redesign.

Fused-filament printed parts can behave differently along and across layer lines. Orientation, wall thickness, infill, temperature and load direction all affect results, so critical parts should be evaluated under representative loads.

No. Appearance and fit do not establish load capacity, fatigue life or impact resistance. Important parts require appropriate design margins, repeatable printing and physical tests before being trusted in a moving robot.

A robot joint must not only rotate but also transmit actuator torque while controlling range, alignment, stiffness and repeatability. Its design may also need room for fasteners, bearings, wiring and service access.

These joints determine much of the leg geometry and movement range for the humanoid concept. The early Chilly 3D journal records several revisions to these assemblies, including printed fit checks.

Backlash is unwanted movement or free play when the direction of force or drive changes. Too much backlash can reduce positioning accuracy and make motion harder to control, especially when multiple joints interact.

Torque depends on the weight being supported, the distance to the load, acceleration and dynamic effects. A useful first calculation combines force with its perpendicular lever arm, then adds sensible margins and confirms the result experimentally.

A suitable test plan checks assembly fit, joint limits, deformation, fastener security, repeated motion and representative loads. Specific results should only be published after the corresponding tests have been carried out.

The September 2026 journal records six Feetech STS3215-C018 serial-bus servos. They were individually tested and given addresses for the left and right ankle, knee and hip joints.

The published address plan assigns 11, 12 and 13 to the left ankle, knee and hip, and 21, 22 and 23 to the matching right-side joints. These are historical identification records, not confirmation of the final robot wiring.

A serial-bus interface provides a means to configure, communicate with and test compatible servos. The early project lists two Feetech FE-URT-2 units for this work. Integration details should follow the relevant manufacturer specifications.

The September journal lists a 12 V, 30 A power supply among the first components. That is its documented rating, not a measurement of how much current the robot uses during operation.

Motors can draw substantial current under load or at stall. Suitable wiring, connectors, overcurrent protection, voltage management and controlled testing help protect components and reduce the risk of overheated wiring or unintended motion.

The currently documented historical material does not verify a completed robot-control software system. This section will describe actual code, interfaces and test results as they become available.

Depending on its design, a robot may need actuator commands, sensor acquisition, communication, motion limits, fault handling, logging and higher-level decision-making. The exact Chilly 3D software architecture will be documented when confirmed.

A controller typically sends commands through the motor system’s supported interface and reads available feedback such as position or load. Protocol details, timing and error handling must match the actual hardware and manufacturer documentation.

Low-speed, limited-range tests help confirm direction, addressing, safe travel limits and fault behaviour before attempting coordinated movements. This reduces the chance of damaging printed parts or stressing motors.

Confirmed examples, explanations and approved source files can be shared through technical articles or Documents when ready. Unverified drafts or unfinished code should not be presented as tested releases.

The public project history identifies AI and voice interaction as development objectives, but it does not verify a completed onboard AI implementation. ChatGPT assistance during engineering work is not the same as an operational AI-controlled robot.

AI tools can help explain problems, generate ideas or review code during development. An AI system integrated into a robot must additionally receive real inputs, produce defined outputs and interact safely with actual hardware.

Vision and audio normally require appropriate sensors, drivers, processing and application software. Cameras, microphones and other components mentioned in a roadmap should be described as planned until procurement and integration are confirmed.

It should not be relied upon as the sole movement-safety mechanism. Independent motion limits, reliable control logic and appropriate hardware protections remain important even when AI provides higher-level instructions.

Start with a clearly defined task and repeatable tests. Record the hardware and software versions, response behaviour, errors, latency and safety limitations rather than judging a feature only by a successful demonstration.

It is the dated record of work on the robot, including engineering decisions, physical prototypes, electronics tests, design revisions and challenges. It is maintained as a normal WordPress blog.

The published timeline begins in September 2026 with the Chilly 3D concept, followed by the first electronics, servo-joint development and early leg assembly revisions. Reading posts chronologically shows how the design evolved.

The restored project photographs are originals supplied by the site owner. CAD and concept renderings are distinguished from photographs of constructed or tested hardware.

Yes. A useful engineering journal records problems, discarded designs and revised decisions as well as milestones. Those details help explain why a design changes and what was learned.

Use the Journal search and available post categories, then follow links from the relevant Engineering pages. New entries are published through the standard WordPress Posts workflow.

The Documents section is intended for published project PDFs, drawings, specifications, test records and other technical reference material approved for sharing. Only entries actually published by Chilly Robotics appear there.

Select View PDF on a published document. The PDF Library provides a page-viewing overlay when supported by the browser and server; otherwise the original PDF can be opened directly.

Yes. Published document entries provide a Download button for the linked PDF. Availability depends on whether a document has been uploaded and released.

No. The Documents library lists published document entries, not every local engineering file. Drafts, private work files and unapproved revisions stay out of the public library.

Check the title, description and any revision or date shown in the document itself. Where multiple revisions exist, the site should identify the released version clearly and avoid presenting superseded drafts as current.