in response to the needs our community has expressed over the years, we’re sharing a new tool which allows you to convert .gcode to .zcode and .zcodex2 files. It is available in the Download section at Zortrax Support Center: Downloads - Zortrax. The tool requires installing Java on your computer.
Navigating through the converter is easy and exporting a .zcode or .zcodex file takes place in a few steps. The detailed operating instructions are available in the README text file you can access after the installation.
This seems to be a great news!
Anyway, I have just tried to convert a gcode file (originally made with Cura v5.2.1 for the Elegoo Neptune 2S) for my M200 Plus, but when I try to open it with Zsuite it gives me the error “Error while opening file”…
Thank you for the Gcode Converter, Zortrax Team.
I was able to successfully use Prusa Slicer on our M200 to print a 3d bench boat on one of our M200 printers. I used the stock MK3S+ profile, just changing the build volume.
The features I most like about Prusa Slicer and Cura is the ability to use Gyroid infill and control the number of perimeters.
Please let the team know that a list of supported gcodes would be very useful.
For instance, does M201 acceleration control work?
M600 pause for filament change?
thanks for sharing this awesome tool. This is great news!
I’ve done some tests, and basically, all worked fine for me.
After playing with the GCODE, I’ve discovered that some typical commands work as expected, for example, the M106 command to set the fan speed.
However, the community would appreciate a list of the supported GCODE commands.
It would also be great to have the possibility to specify the material type since the actual version of the tool sets a default value to Z-ABS, and therefore the printer warns for the wrong material when the print starts.
So, we all hope for further information about this tool…
What would be great is to have a zortrax z-suite equivalent profile for cura or prusa slicer, or at least know the acceleration and speed settings that should be provided as a base. Yet this still seems like a band-aid solution for an inferior software/firmware. Why not open the firmware to accept gcode files as well as zcode files natively. This will allow for seemless slicing from both sides open and closed source. the hardware can definitely support this. if only the developers would…
I put in a gcode and when I try to preview or save it, it freezes.
What could be the cause of this problem?
I would be very happy if you could give me some sample zee code that I can use with some success.