![]() Does this mean you want to derive coordinates and length measurements from the objects and use these as parameters for individual G-code instructions? Would you also need to model your work path, or parts of your machinery? You say you want to generate G-code "in the context of 3D modeling". I still don't understand the connection between these two pieces of the puzzle, though. "%") as the header, export the table as a CSV, then change the extension from. The simplest way would be to render each line of code as a string, combine those strings into a list, put that list in to a one-column table with the first line (e.g. I think it might also be possible to import ASCII STL files from BlocksCAD if that would be preferable.Īs for the G-code, it's fairly easy to generate and export a text file in NodeBox. This would be a subset of what you can do in BlockSCAD or OpenSCAD. I think within a day or so I should be able to craft a simple proof of concept network that allows you to extrude, rotate, place and display simple objects. I am noodling around with a 3D rotation node posted by another Nodebox user, Rioch, back in 2013. But perhaps it could be done for a special purpose project that only requires a subset of capabilities. I still think writing a general purpose CAD tool that could also export G-code would be challenging to do in a robust, general purpose way. I've been thinking about this and learning more about CADCAM and G-Code. I suspect I'll have to write my own tool - we'll see. Feel free to start a separate thread if you'd like to have a conversation about this.īut I want to do it in the context of 3D modeling, and using a Node/block editor - as noted, I'm currently using BlockSCAD:Īnd I just find that the most workable way for me to do design work. If you can describe exactly what kind of text files you want to export maybe Nodebox could help. Nevertheless I am always happy to explore ideas. Even if you could do it there would probably be easier ways to accomplish what you want. But I'm skeptical that you could stretch it into a usable and efficient one-stop CADCAM tool just by adding nodes. It can certainly be part of an overall workflow. Nodebox can create drawings and export them as text files. What kind of text files do you want to export? Some kind of XML file to drive CAM tools of some sort? I'm not clear what your end goal is and what your proposed workflow would look like. It's certainly possible to create Nodebox nodes which would draw 2D perspectives of simple 3D objects, but recreating OpenSCAD would be a heavy lift. ![]() I assume you can already create 2D shapes in Nodebox and import them as SVGs into OpenSCAD for extrusion, but I gather you want to do more than this. Once we've done so, could we allow writing out a text file? So, could we connect Nodebox to the kind of 3D modeling which OpenSCAD does? ![]() Right now I'm limping along doing modeling in BlockSCAD and then exporting to OpenSCAD - the problem is the latter won't write out text files, and what one can capture as a DXF or SVG from it is limited (and STLs won't work for my purposes, since I can't find any CAM tools which will use the tooling which I wish to use efficiently enough). I'd like to use Nodebox, or something like to it - the thing is, I want to do 3D though. This first post is a recap of the initial conversation: This thread is a branch from a discussion that started under the General Discussion "Why I Still Care About Nodebox".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |