Serenity-UAV (Stab-Rabbit-coding) errors

3 recurring problems engineers report in Serenity-UAV (Stab-Rabbit-coding), ranked by impact.

#201 by errors trackedECADPLMMCAD

Recurring Serenity-UAV (Stab-Rabbit-coding) errors, by impact

  1. 1A reshaped Observer board outline and slot keepouts leave copper running to or past the new edge, giving 9 hard copper-to-edge clearance violations, 8 at 0.0 mm against a 0.5 mm rule, and KiCad CI fails.ECAD · Agent failure · 1 report74
  2. 2A UAV project pins its design revision at Rev U by moving the "Current design revision" header from Rev T to Rev U in 27 subsystem README, WBS and TODO files, plus the root README, docs index and tool BOM pointers. The new bom_revU.json is "a row-for-row carry-forward of bom_revT", and "the known BOM lag items remain documented as open." Subsystems keep their own generation names (PCB "Rev T", landing gear "R6", wing "S1g", nacelle "S4c"). The list of work carried into Rev U is "summarised from commit subjects, not signed off," and there is a rev-S git tag but no rev-T.PLM · Agent failure · 1 report74
  3. 3tools/check_bom_mesh_sync.py now fails CI when a printed part's Unit_Mass_g differs from its mesh mass, and lists printed rows with no mesh as NOT COVERED. Densities now come from one file checked against the 3D Systems sheets, moving hover weight from 13.80 to 14.12 lbm. The assembly check found the nozzle spigot overlapping the cartridge by 1,562 mm3, fixed by shortening the cartridge 3 mm, and no route for 4 x 10 AWG from the spar bore, with 1.5 mm free radius against 6.64 mm needed.MCAD · Agent failure · 1 report74

How it fails

  1. Agent failure3

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.