Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs

PostProcessor for Duet2 CNC Controller

A topic by Dave_P created 97 days ago Views: 38 Replies: 1
Viewing posts 1 to 2

Hello. I have just discovered PixelCNC, it is a really clever idea, well done!! I trying  out the 64bit V1.33a version and am having problems with my DUET2 controller board running the gcode from PixelCNC.  I am using the Marlin Metric post processor it looka like my controller dosent like the spindle speed commands in the start of the gcode file. As an example, the following fails on my board:-

; Generated By: PixelCNC v1.33a, Post: Marlin Metric.txt v1.00
G21 G90 G91.1
G00 X0.0 Y0.0 Z0.0 F2100
G00 Z5.0 F480
; Tool: 1
T1 ; Spindle: CW 10000
M03
; Operation: operation01, tool01
G00 Z3.00
G00 X9.57 Y-28.69
G01 Z-0.70 F200 S10000
G01 X9.25 Y-28.32 F300
G01 X8.94 Y-27.73 F300
G01 X8.82 Y-27.51 F300

and on...

After editing to comment out the tool selection and remove the S10000 speed parameter as follows the gcode runs:-

; Generated By: PixelCNC v1.33a, Post: Marlin Metric.txt v1.00
G21
G90
G00 X0.0 Y0.0 Z0.0 F2100
G00 Z5.0 F480
; Tool: 1
 ;T1 ; Spindle: CW 10000 ;M03
; Operation: operation01, tool01 G00 Z3.00
G00 X9.57 Y-28.69
G01 Z-0.70 F200
G01 X9.25 Y-28.32 F300
G01 X8.94 Y-27.73 F300
G01 X8.82 Y-27.51 F300

Could you suggest how to modify the Marlin Post processor to cater for this.

Many thanks

Dave

Developer

Thanks for your interest in PixelCNC! Modifying the post-processor is very simple. Make a copy of your metric Marlin post processor to edit so you don't permanently modify your existing post - unless you're confident you'll never need the original. 

Open it up and at the bottom are the definitions for various command block types. You will see the set of commands for SpindleOff/CW/CCW followed by their definitions in double-quotes. Simply remove all the text between the double quotes for each of the three 'Spindle' block definitions, leaving only the starting/ending double-quote characters. This will effectively render any and all spindle command blocks null and void so that whenever PixelCNC internally sees that it's when it should emit a command for the spindle it will just output nothing instead. Easy peasy!

I would suggest also removing the text between the double-quotes for the ToolChangeBlock, so that it too is just a pair of double-quotes. That should remove any tool-change command blocks from outputted G-code as well.

Let me know if you have any further questions and keep your eye out for v1.34a on August 1st, big things are happening!

Good luck!