Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Recommend a CNC selection
wayne_lapaire
Member Posts: 5 ✭
Best Answer
-
Ste_Wilson
Member Posts: 369 EDU
Welcome to onshape :)
The other good place for some help might be the kiri Moto forums.
0
Answers
Ummm..
More information and explanation of your problem is needed.
I have created an object in onshape and then opened the integrated kiri:moto app to generate a g-code file to send to a CNC cutter. The cutter I have is a Onefinity journeyman 50.
I select the CNC mode. When I use the Device pull down list, there is no entry for Onefinity machines. Furthermore, when I generate the g-code for both generic devices, as well as all of the other stock devices, the g-code does not match the cutpath files that are needed to drive the Onfinity machine.
I wanted to know from the forum if anyone has a solution or work around for getting a file created in onshape to drive the Onefinity machine. The machine works with files created with vCarve Pro, but I have not been able to export any files from onshape that can be imported by vCarve pro.
The best solution would be to have the Onfinity machines directly available in the Kiri:Moto app, but I don't have any idea of how to make that happen.
As is likely obvious, I don't have a lot of experience with this. I have just started using onshape, and I really like it for capability and ease of use.
Thanks for trying to help me.
You might start by contacting whoever makes or sells the Onefinity Journeyman 50 and see if they can give you direction or do something to provide support for it's use with Kiri.
With the CNC machines I'm familiar with (mostly metal cutting), this would involve creating a new postprocessor (or editing an existing post) that will work with your machine. That can be a simple or a very complex process depending on many factors
Here is a custom feature that @jeff_brown304 made that will generate g-code directly within Onshape!
https://forum.onshape.com/discussion/20285/introducing-camel-cam…
And Onshape will be releasing their CAM Studio in the future, should be soon now. However this will only be for pro users I think? Can't remember.
Learn more about the Gospel of Christ ( Here )
CADSharp - We make custom features and integrated Onshape apps! Learn How to FeatureScript Here 🔴
Welcome to onshape :)
The other good place for some help might be the kiri Moto forums.
https://forum.grid.space/
Thanks to both of you forr taking the time to provide well thought out answers for me. When I find the solution, I will post.
Regards,
Wayne
I worked with Vcarv a while back. If I remember correctly Vcar and another module were part of a package that accepted DFX files for 2d and STL files for 3d..
I use Camel from time to time for simple projects. There's a lot it can't do but it's very convenient for making rough templates and things. I should really post a tutorial sometime. And maybe add tabbing support.
A few years ago I imported a project from OnShape into Vcarve. I think I started by creating an OnShape drawing without borders or titles at 1:1 scale at least as big as the stock or the machine bed. Then I added a view of the part to manufacture. I turned off view simplification to ensure fine details in the rendering. Then I exported the drawing as a PDF and imported it into Vcarve.
The same general approach works well for exporting 2D geometry for use by other tools such as Adobe Illustrator and LightBurn. Sometimes you get duplicate lines in the renderer drawings but it gets the job done.
You can also Export as DXF directly from a Parts Studio but I tend to have more issues with DXF interchange.