Matt,
This is entirely feasible, and sounds like a perfect application for a CAP! Their main benefit is removing complexity/tediousness from the operator/robot programmer at the cost of some up-front software development. We produce a welding CAP (which is the same thing in principle) and we do pretty much exactly what you’re describing.
There’s a pretty big learning curve to developing a CAP, but in my opinion it’s fun and worth it. I’m going to mention this now, just so you’ve heard it, and might remember it if/when you get to that point:
When saving a robot position using the getRobotMovementCallback(), be sure to store both the Pose variable AND the JointPositions variable, as this is not something you can retroactively obtain if you were to save a program and then update the CAP to include it.
That probably doesn’t make sense right now, but it will when you start storing positions.
Also, just food for thought, it may be possible to somehow export the circuit board itself as some kind of G-Code to generate the robot path, and then write a post-processor to insert the commands for actually soldering , etc. You could possibly go straight from the PCB file to a robot program. The CAP is a happy medium between tedious manual programming, and generated path data.