EDM is a new topic to me. @Jonathan, how far are you with this development already? Are you going to generate NC code for the machine or how do you see the final result? Any automatic feature recognition down the road? Just curious.
I have developed a first version on top of Blender, the visual aspect of the software was very easy but, I found that having to deal with the whole blender interface would make it more difficult for other users to learn. Some features were very difficult (for me anyway) to implement.. That version do post NC code.
For this project I want to be able to at least have multiple tool in a single document, generate nc code, be able to easily turn on machine cycles at specific location..
Down the road I also would like to be able verify collisions , part gouging, tool path optimization, electrode design, AI pathfinding.. There is a lot of opportunities for me to add features!
So, so far in the current project, I can load and save my models..
I have a simple animation mechanism that supports linear and circular moves with A,B,C rotation (XYZ EULER) a tool class (I will probably have to redo, or at least redo how it is linked to the interface). Not a whole lot.. but it doesn't need a whole lot more to be usable so I am determined to continue.
I found a link to XDE, I think on this forum.. and it seems like that would be helpful for this project's purpose. I have so much to learn, between c++, opencascade, good programming practices, etc.
@Jonathan That sounds ambitious, good luck with that and feel free to share your (even negative) experiences. I can guess how hard it is to develop such a system from scratch. As for the XDE, this thing is mostly intended for working with CAD assemblies, although it can also be used as a metadata holder for parts (e.g., to associate colors or PMI). Quite a useful thing if you know how to work with it (and that's often the obstacle).
Apart from the complicated UI, how good is Blender for the CAD things? Would you recommend it as a sort of a generic CAD "platform"? Which things do you think are missing there?
You can start from exporting your assembly to a STEP file from Creo and reading it back into an XDE document. It's not seamless in the sense that you'll have this extra STEP file in between, but for the proof of concept it might be ok. Then your tool might be appended to the document. OCC was also developing some support for kinematics in the STEP format but this is unlikely going to be released in open source.