🎯 Priority Tasks & Known Pitfalls - Blade Generation System

🎯 Priority Tasks (Next Sprint)

Priority	Task	Phase	Notes
HIGH	Pre-Release Python/OVM Analysis	Validation	Run Python analyzer on ALL production macros before testing release. Mandatory gate.
HIGH	Offline Programming System (Weld Data Export)	Phase 12+	Weld detection → torch vectors → CSV/JSON/XML → Nachi/OTC Daihen formats. Foundation for robot integration.
HIGH	Weight & CoG Calculation	New	Foundation for stability analysis
HIGH	Complete gravity offset arc-to-arc	Phase 10	VDM-based vertex projection needed
HIGH	Weld Detection System	Phase 12	Required for robot reach study
MEDIUM	Robot Reach Study	New	Kinematic-free accessibility analysis
MEDIUM	Fix fxBladeFromSection transformation	Phase 3	Use blade line rotation, not centroid math
MEDIUM	Test Mode Framework	Phase 6	Standardize testing approach
LOW	Blade Orphan Detection	Phase 7	Validation utility
LOW	3-Tier Architecture Design	New	API contracts and deployment options

⚠️ Known Pitfalls & Edge Cases

Thick Blade Edge Case

If blade thickness approaches pocket size, normal-based face selection may pick wrong faces. Need fallback to area calculation or bounding box comparison.

Transform Order for Rotations

Must follow: Translate to origin → Rotate → Translate back (T⁻¹·R·T). Wrong order causes geometry to orbit around world origin.

SLD Command Gotchas

sld sec CONSUMES the sheet - don't try to delete it after
sld tap requires i_ws_body_set global - local sets fail silently
No sld fac are command exists - use kurve conversion or normal filtering
VDM value parameters must be variables, not literals

Robot Reach Study Limitations

The reach study is NOT a kinematic simulation. It only checks distance from robot base to weld points. Does not account for joint limits, singularities, or collision avoidance.