Sowbot / Feldfreund

Separate reported simulation from field results

The README reports multi-row mission following in Gazebo and explicitly lists remaining Jazzy hardware validation. It separately reports iteration of visual row following against a lettuce crop. Those statements concern different subsystems and do not establish that the entire navigation, localization and monitoring stack has passed a complete field qualification. The repository also describes itself as experimental and under active development. [S001]

Its current hardware sketch names two Avaota A1 boards using Allwinner T527 processors, with an ESP32 controller. Later controller and operating-system designs appear as future architecture or roadmap items. They should not be recorded as installed features of the selected configuration. The README also contains older setup sections, so the snapshot needs internal configuration reconciliation before deployment. [S001]

Measure the physical quantities that the configuration leaves open

The FusionCore configuration sets all three GNSS antenna lever-arm coordinates to zero and explicitly says they need measurement on the physical robot. It accepts RTK-fixed position updates with the selected fix threshold; that setting is a filter policy, not proof of measured positioning accuracy. [S006]

The same file has inconsistent IMU comments: an introductory comment says the BNO085 is wired and publishing, while a later heading still says the IMU is not yet wired. This review records that ambiguity instead of deciding the physical integration state from one comment. The robot and running topics would need inspection to resolve it. [S006]

The monitoring configuration contains a battery-voltage condition at 44.0 V marked for confirmation against the BMS cutoff. That is an unfinished hardware-specific value, not a catalog recommendation. The upstream README also requires an independent physical emergency stop and says software stops are not a substitute. No safety function or stop performance was tested here. [S001] [S007]

Preserve the separate firmware revision

The Lizard setup guide specifies commit 87ab4e198d3af2a274e60292ee204b722f939b5e, says it matches the Docker integration, and keeps the firmware in a separate checkout. It identifies an ESP32-S3 build using the Espressif IDF 5.3.1 container. The preserved ROS archive therefore does not include the complete matching firmware tree or its submodule payloads. [S005]

The source repository uses MIT, but external packages, perception weights and planned datasets need their own evidence and license review. The archive does not establish a complete robot CAD package, electronics manufacturing set or delivered build cost. No Docker build, firmware flashing, calibration, motion test or agricultural field trial was performed by this catalog. [S001] [S003] [S004] [S005]