Open Source RoboticsRobots, software & learning

Veterobot

Robot / hardware build

A historical tracked mobile robot with released printable body designs, an Eagle interface board and onboard code in separate repositories. [1] [2] [3] [4]

Build & first use →Official websiteSource codeBill of materials

For
Experienced mobile robot builders; Researchers adapting tracked robot platforms [1]
Cost
No current cost yet. Upstream bill of materials [5]
Source rights
Some licenses are unresolved. Review licenses
Unknowns
host computer, tools, operating system not fully established. Review gaps

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware
License
none identified in the reviewed sources · license not fully assessed for mechanical design, software, documentation · Details by part

Requirements · Research details and dates

On this page

Overview

Veterobot is a historical tracked rover built around a Dagu Rover 5 chassis. Its public build sequence covers printing a body, buying the listed electronics, ordering and soldering an interface board, assembling the robot and installing software. The project files are split across upstream repositories: design-art has Blender and STL body parts, veter-cap has Eagle board and schematic files, and vehicle has onboard code. The similarly named veter repository is empty at the pinned snapshot, so it is not the design source. [1] [2] [3] [4]

Start with the build instructions and the historical parts list. The named configuration uses a Dagu Rover 5 base, BeagleBoard-xM, motor driver, sonar sensors and a compass. Inspect the printable body separately from the extern folder of modeled purchased parts; those meshes are not evidence that vendor hardware is open. Board manufacturing and software installation would need version and wiring reconciliation before a build. [1] [2] [3] [5]

No project-wide license was identified for the body or CAP board in the inspected archives. The vehicle code repository contains GPLv2 COPYING text, but this review has not resolved every file or submodule's terms. No printing, PCB fabrication, installation, driving or sensor test was performed. Current availability and total delivered cost are unknown. [2] [3] [4] [5]

Is this for you?

Known limitations
  • The apparent primary veter-team/veter repository is empty; actual design, CAP board and onboard code are separate pinned repositories.
  • The body archive includes third-party component meshes; their reuse rights are not inherited from the project's own printable panels.
  • Historical Dagu Rover 5, BeagleBoard-xM and sensor sourcing is unverified.
  • Mechanical and electronics design files have no identified project-wide reuse grant in the inspected archives.

Split repository and rights/sourcing review.

[1] [2] [3] [4] [5] · Editorial assessment

What you need

Dependencies
  • Dagu Rover 5 chassis
  • Printed Veter body components
  • Veter CAP PCB and through-hole components
  • BeagleBoard-xM and motor driver

[1] [2] [3] [5]

Hardware & parts

Upstream bill of materials [5]

Hardware configuration

Tracked rover with printed body

[1]

Controller

BeagleBoard-xM with Veter CAP interface board

[3] [5]

Sensors
  • Devantech sonar sensors
  • Compass module

[5]

Assembly & first use

Project documentation [1] [5]

Assembly

The project instructions sequence printing, purchasing, PCB ordering/soldering, mechanical assembly and software installation, with details in the linked wiki.

[1]

Cost

No current, complete configuration-specific build cost has been established for this profile.

3D preview

Preview not available yet. Printable body files are available in the split source, but third-party extern meshes and assembly placement need review before hosting a model.

Model sources

Printable body files are available in the split source, but third-party extern meshes and assembly placement need review before hosting a model.

What we checked

Source research only; no fabrication, hardware commissioning, software installation or performance test performed.

Not yet established

  • Requirements: operating system, host computer, tools
  • A step-by-step setup summary

Updates

Upstream last updated
Jul 10, 2013 [2]
Latest release
Not established
Profile updated
Oct 24, 2026
Sources last checked
Oct 24, 2026
Next review
Nov 24, 2026
Reviewed revision
body cd1260a53a483de65b541ce0925b0b6fdcd3a87f; Veter CAP f2f1bd50c3c3770f276f2728810c47380f59ce73; onboard code 1f23c21dc2b190aeb041d178285041352fd2fc5f (commit snapshots) · repository

Source files and licenses

The split original repositories contain real body, electronics and code artifacts, but rights, compatibility and sourcing remain unresolved.

LayerAvailability / license
mechanical designavailable · License not fully assessed
Printable STL and Blender body files inspected; no grant identified, and extern vendor meshes have separate rights. [1] [2]
electronicsavailable · No license identified
Veter CAP Eagle board/schematic available; no license grant identified in archive. [1] [3]
softwareavailable · License not fully assessed
Onboard code and GPLv2 COPYING text available; exact file-level terms and submodules require review. [1] [4]
documentationavailable · License not fully assessed
Build sequence and historical parts list are public; project-wide documentation rights unresolved. [1] [5]

No independent artifact in the selected configuration established during this review.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Correction guidance · Discussion is not enabled · Profile format 0.7.0-draft.5

Change history