-
-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how to add other machines? #403
Comments
You can add new machines to the
It's an arbitrary format that some other developer came up with. I've considered converting everything to STL files but STL has no provision for storing other info so you'd have to have a separate STL for each part of the machine. It makes sense to just add the triangles directly to the JSON file rather than referencing an external TCO or STL files. The TCO contains lists of triangles, lines and vertices.
This is messy. It would be very helpful if we had some sort of machine editor. You would need to be able to load a triangle mesh (probably from STL) for each axis and the base and then specify home positions (i.e. 3D offsets which put the mesh into the home position), and the relationships between the axes. On some machines, for example, the x-axis moves with the y-axis and the z-axis moves with both axes. But that's not always the case. You could have a stationary z-axis and a moving base or lots of other combinations. An editor would let you position the parts of the machine at their homes, specify their limits and then save the result as a machine definition. Once the machine editing is sorted out it would be great to detect collisions or moves beyond the machine's limits. |
I've replace the TCO format with pure JSON. Now the machine files are in compressed JSON |
Wow! That was quick 🙂
But do you really want to add a machine editor? That sounds like a lot of work. Or what exactly do you have in mind there? I personally wouldn't need a fancy STL type visualisation. |
I was not thinking about a whole 3D editor but an editor where you could load in the 3D parts created in some other CAD program.
You do make a good point. The first thing to do would be to make it possible to just edit the existing machine parameters and save them as your own machine. Importing the 3D drawings is more involved. |
It sure would be nice to model machines in CAD packages (e.g. FreeCAD, OpenSCAD, TinkerCAD, Blender, Fusion360, etc.) and export meshes in a common format (e.g. .obj, .step, .stl) that could be converted and assembled into machines either in Camotics or even with something as simple as a python script included in the machines directory that could convert a collection of meshes into a json file that could be edited to finish the machine? I'm trying to make a suggestion that would balance enabling the community without hand typing vertices, lines, and triangles, and also not distracting Camotics mainstream development |
I looked into the json but TBH I couldn't really make much sense of it yet.
Why doesn't this have dimensions but is mostly 1 based? I would love to add my customized PrintNC somehow. It would be super cool if you could give some guidance, @jcoffland |
I see - rotate and translate. But how are the dimensions defined? Through the related 3d model I assume? |
It's been a long time since I looked at this. The source code is the best place to find out how this all works. |
I can't find the I've checked https://github.com/CauldronDevelopmentLLC/CAMotics/tree/master/src/camotics/machine |
CAMotics no longer uses the TCO format. The machine files are bzip2 compressed JSON. See the |
Sure - but neither the old TCO format nor the JSON format has the 3D Model information. |
The JSON files contain all the part data. The parts contain |
This is the
|
Just realized the I am running an old version (1.2.0). I guess that's why. |
1.2.0 is the latest release, so still using the .tco format until the next release. |
@tcurdt, @jcoffland I wrote a python script to create Camotics machines from X3D .xhtml files for my local Workshop 88 Makerspace. I thought you might like it. Here is the script https://github.com/Workshop88/camotics_machine_maker I hope this works for you, at least until the next Camotics release. Is there somewhere more public I should post this? |
Wow that is awesome work. Thank you for sharing. You could post a message on the CAMotics users group. https://groups.google.com/g/camotics-users |
I wanted to add a custom machine but run into a few hurdles raising many questions:
.tco
file defines the 3D view of the machine - what format is that?The text was updated successfully, but these errors were encountered: