Hexy

Centering and port assignment matter during assembly

The archive includes native SolidWorks parts and assemblies alongside STEP, STL and DXF files. The assembly guide describes repeated leg construction, fitting servo horns while the joints are centered, and connecting each joint to its assigned controller port. File presence was checked, but dimensions, material fit and fabrication completeness were not validated. [S006] [S014]

The preserved Servotor32 example initially disables all servo outputs, then commands ports 0–3 to a 1500 pulse setting before processing serial input. That supports the guide's centering workflow for this particular example. It does not establish what firmware is installed on an existing board, and centering before horn attachment does not replace later joint-offset checks. [S006] [S012]

Identify the power arrangement before following a guide

The original power guide distinguishes servo and logic supplies. It gives a 4.8–7 V board servo-power range, recommends rechargeable NiMH/NiCd cells rather than alkaline packs, and describes resets when servo load pulls the shared supply down. Its external-supply example is regulated 5 V with at least 5 A capability. Those historical board limits are not an endorsement of an unidentified replacement servo. [S007]

The later power-board kit replaces the original black AA holders and changes the battery-shelf spacing. Its guide says a separate logic supply should normally be unnecessary with that kit, unlike the older battery-only arrangement. Keep those instructions separate: a different power board changes both mounting and the assumptions behind troubleshooting a reset. Current kit availability and a complete delivered budget remain unknown. [S006] [S007] [S008]

The preserved software is a legacy stack

PoMoCo's README describes 9600-baud communication and matching historical firmware changes. The preserved Servotor32 initialization also uses 9600 baud and attempts to reconfigure an attached Bluetooth module before switching its serial rate. A board or adapter with different firmware/settings needs explicit reconciliation. No serial connection or Bluetooth configuration was tested here. [S010] [S011]

The host entrypoint uses Python 2-style print statements, and its GUI imports Tkinter and ConfigParser under their older names. The serial code also imports pyserial and uses time.clock. These sources should not be presented as a tested current Python 3 installation. PoMoCo loads motion files from its Moves directory; inspect the joint mapping and motion definitions before running them on a restored mechanism. No host application or motion script was executed. [S010] [S013]

Hardware and software licenses need separate treatment

Hexy's frame README and Servotor32's hardware declaration name Creative Commons Attribution-ShareAlike 3.0 United States, but link to the unported 3.0 URL. That jurisdiction mismatch remains unresolved. The available CAD and board files are therefore recorded separately from a confirmed exact hardware license; this review does not silently choose one version. [S001] [S009] [S014]

Servotor32's software and PoMoCo have MIT terms in their respective READMEs, subject to any separately applicable third-party notices. The website guides establish historical assembly and power instructions, not current stock or permission to republish every photograph. No parts were fabricated, board flashed, servos calibrated or walking performance measured for this entry. [S005] [S006] [S009] [S010]