Marlin G-code flavor to RRF flavor
-
Hi,
I am having to run G-code sliced in Marlin flavor on RRF machine, so I think I need some suggestion before printing,
1, is there some conversion software that I can convert the G-code flavor? I didn't find any
2, if I have to do it manually, what are the G-code that I should look for and replace that is Not standard in Marlin and RRF
3, if the G-code passes the on-board simulation, I think it should be mostly fine to print ?thank you!
-
Print moves and extrusion should be the same. There may be some differences in syntax for some configuration gcodes if those are included in the starting gcode. Have you run a simulation yet?
-
@cjccjj most Marlin GCode will work correctly in RRF. Here are the most important exceptions that I am aware of:
- In the M203 command, RRF uses mm/min but unfortunately Marlin broke with established use and uses mm/sec instead. M203 should not be generated by slicers (there s no need for them to do it), but some versions of PrusaSlicer and its derivatives generate it, usually near the start.
- G91 in RRF sets only the axes to relative motion. G91 in Marlin sets extruders to relative motion too. This can cause a problem in the user-definable end GCode, if it uses e.g. G91 followed by G1 E-5 to retract some filament from the hot end without resetting the filament position first.
- RRF always requires a tool to be selected in order to extrude. Marlin has no real concept of tools. So on a machine with just one nozzle, RRF requires an explicit or implicit T0 command whereas Marlin doesn't. However, GCode generated for Marlin typically uses M109 to heat the hot end, and if RRF sees that command when no tool is selected then it will select the lowest numbered tool implicitly.
-
@Phaedrux Yes, simulation reports issues mostly in starting gcode. I have made modification it will print fine I believe. Thank you.
-
@dc42 Thank you. This is very helpful, I have made changes accordingly I think it will print fine.