Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

After doing some digging it appears that conventional Mach3-style post processors should work, but based on what I've read here: https://www.cnczone.com/forums/uccnc-control-software/301384-fed-uccnc.html it sounds like maybe the existing GRBL/Mach3 default post could just be modified so that all commands (specifically in the startup block) are divvied up with each command code getting its own line. By the sound of it UCCNC for some reason has issue with lines that have more than one G-code command. I will modify the existing default post processor and provide you with a link to a new one to test-drive.

Could you give me any details about what happens when you try to load up G-code generated using the default GRBL post? That may help me to quickly create a post for PixelCNC. Thanks!

Sorry not to answer your question yesterday, but I am still coming to grips with 3D technology (decades of 2D are not much preparation!).  I have not quite finished my Stepcraft (there's a missing but vital washer on its way), and I am still trying to get a STEP file done from an STL I've created. But I very much like the look of PixelNC, so much so that I wanted to buy it and use when I get up and running soon. Hence the request for a Stepcraft post processor to add to the myriads... As someone said, 'The nice thing about standards is that there are so many to choose from.'

I'm glad to hear you're taking the leap and wrangling a new dimension :) I will be doing some work on PixelCNC over the next few days to improve the post-processor functionality as a direct result of your request and v1.30a will include those improvements, plus the previous fixes/changes and the new pocketing operation I just finished. I'm aiming at the next weekend to have v1.30a out. I'm sure we'll be able to get PixelCNC going as your go-to CAM solution for toolpathing images. The next big feature I'm looking at is (ironically) supporting 3D model import, which will effectively generate a depthmap from a given 3D model from which toolpaths can then be generated. This should open up PixelCNC as an alternative workflow to many CNCers who have an existing 3D model based workflow that PixelCNC is not suited for. 2019 is going to be a big year for PixelCNC!

Keep your eye out for v1.30a, it will include a post for UCCNC - which will keep G/M command codes on separate lines. Also, I've opted to remove the image-size limitation from the free trial and instead impose a limit on operation toolpath motions, so that users can test out their high-res images.

Happy New Year!

:-)))