make c2d a standard file type, so that other software can use it. Maybe program an extension for QCad, that their QCadCam can write c2d (would be great for me, I love and use QCad…), participating in free software / open source can widespread the use of a file type. GL!
Carbide motion can read gcode files (.nc) So the other software you mentioned should be able to output files that you can run on your Shapeoko. You may need to find the correct post processor for that software. (by the way Carbide Create Pro can output the files as either gcode or carbide3d format, both of which Carbide Motion can read if you are going the other way. I am not sure I understand the use case you are indicating.
John
John,
tried that once with some special cases for raspberry pie. Some countersunk M1.5 had to be made, some 1.5mm acrylic. Used QCad Cam for that purpose, checked whether the countersunk screws would still have enough grip. In QCad Cam it looked ok. The exported GCode .nc was not readable in CM. Had to go through an online optimizer. CM could read it now, but cut was a desaster, good I used an extra spoilboard, but broke some 1/16 bits.
Now I do some vcarve cutting boards, they come not near the precision I expect from my work, and would like to check the depth profile of the cuts for him and her.
Going through different softwares does not always deliver what is promised and / or expected.
Therefore I think it would be nice to have as much as possible under one umbrella.
Sounds more like a formatting issue from that cad program rather than a carbide motion issue. But I am not an expert on gcode formatting nor rasp pi implementation.
I’ve run gcode from both vectric vcarve and autocad fusion with no issues.
1 Like
Oh is there a proper post processor for shapeoko for quad?
What sort of projects are you creating in QCAD which you are having difficulty doing in/working with in Carbide Create?
None, QCad works just fine. In a galaxy far far away there was a time long ago where CC could not simulate the tool path. That was when I tried to visualize the tool path, and therefore aquired QcadCam, paid it and used it some weeks: CC introduced their tool path simulation as integral part. Now I do not need QcadCam any more. As I said: QCad produces all DXF I need, and CC reads them nicely.
I am not too happy with my inserts, the gaps between hims and hers are wider than I would accept them for me, therefore I tried to figure how I could visualize the profile, a cut through the material. Forum members showed me a great workaround, what I use already with success: I am about to cut a acrylic sheet with countersunk holes, with all calculation back and forth eventually I prefer to see what I get, so now I can see for myself how deepn the countersunk hole goes into the acrylic sheet, do I need another straight hole, or does the 90deg vcarve bit cut deep enough for the screw, etc.
John: Maybe. As long as I use software when something is odd the hardware tech always solves the issue with blaming the software, and the software hotline recommends to repair the hardware. Much worse with cooperation between different softwares, imagine only how different browsers show the same code. May be the same here, that the external software codes the G-code right, and CM cannot read that specific -maybe although according to the rules correct- dialect?
Therefore I prefer to use the same software family, without breaks and transfers. Just my preference. And I find the carbide family quiet powerful, why not broaden it’s acceptance. But it is just a suggestion.
I don’t work for them, I was just trying to help you trouble shoot your problem.
I think C3D file format is intentionally closed source, so they can get paid for their work. (which I fully support folks getting paid for their work). I think they went to that approach so that if you wanted to save out in Gcode rather than c3d you had to pay for CC Pro. I think too many folks using machines other than Shapeokos or Nomads were just directing their customers to Carbide Create (the free level), and so were not paying for all the work to write these complex pieces of software.
You also didn’t answer my question as to whether you had a proper post-processor installed for this QCad?
John
John, tried different postprocessors with QCadCam, since there is no proprietary specific postprocessor for CM. QCad is very good, excellent 2d CAD, just QCadCam could not write a proper nc file, or CM could not read it. Hence my idea to keep it under one software family. And I am rather happy with CC, of course I use CCpro, what else…
So you are happy with Cc Pro/CM software combo, and don’t use anything else, so I don’t understand the need to have c3d files readable outside the c3d environment.
John, define happiness.
I found a workaround for visualizing a perpendicular cut view. I find it useful for some usecases to visualize how this looks. Since CC does not offer this, I made the suggestion to think of making the file type accessible for other 3d software that possibly can provide such a view. And that is only useful after the cut properties / paths together with bit / cut geometry are assigned to the project, just the design does of course not show the cut itself.
I enjoy this hobby since I really enjoy problem solving. I am glad my suggestion of simulating a pocket to cut off part of your piece to get a cross-sectional view is working for you. If you want QCad to do something (either create C3D files or gcode that is in the right dialect) that’s something they need to do on their side. Even if they had the full specs for the C3D file format, someone would have to write the code to have QCad create it. The gcode the Shapeooko controllers need is fully documented (I want to say some version of GRBL but I have not dug in to it) so they should be able to write the code to put it in that format. There is no business case I can think of for Carbide3D to do any of that for some other companies software, when there is a perfectly functional documented gcode pathway.
Since there is not a clear problem to brainstorm and solve, I’m out.
And to get philosophical, only you can define happiness for you.
John
Given that QCAD uses a fully programmable post-processor for G-code system:
then it should be possible to work up a post-processor which does exactly what one wishes in G-code, then that G-code could be loaded into Carbide Motion to verify as a wireframe (and it should be possible to use a 3rd party surface previewer such as Cutviewer, or the system I’ve been working on: GitHub - WillAdams/gcodepreview: OpenPythonSCAD library for moving a tool in lines and arcs so as to model how a part would be cut using G-Code or described as a DXF. ) — it’s just a matter of coding things up to work as desired.
1 Like