0xdeadbeef

Good to hear though this could be related to different retraction settings. Z-Suite uses rather low values (0.5mm) for everything but ZGlass, S3D uses 1mm as default. With the "external materials" setting you could change the retraction distance also in Z-Suite. While I'm at it: 1.0.3 Allows to select the minimum firmware revision embedded into the header. Improved handling of erratic G-Code files. Added support for G-Code pause command (M226).

@stylus: So did it work now? @Nagisa: Fan speed editing is about the last major thing left on my list. I just haven't had a good idea how to let the user define the fan speed. The more or less best idea I had up to now was to let the user load a CSV file (like <layer>,percentage or <z-height>,percentage) that is used to override any fan speed setting in Z-Code. But of course there might be situations where you might want to change the fan speed inside a layer instead of at layer entrance/exit. Any suggestion is welcome.

OK, couldn't stop thinking of that pause command. So there's another release today, namely 1.0.2: Fixed inconsistency in fan speed graph. Added support for G-Code pause command (M226). Avoided removal of pause commands when removing raft. Validity of bed/extruder temperatures already displayed in main window (red=invalid)

Anyway, I uploaded a new version 1.0.1 that just outputs a warning when there is no proper model in G-Code but will still allow you to save it as ZCode. As a side note, I also started to think about that unloading thing some months ago since a beta tester asked me if it was possible. At that time, I gave him this script as base but AFAIK he never tested it: ;Gcode G28 ; home all axes G92 X0 Y0 Z0 E0 ; set all axes to 0 G0 F180 Z15 ; move up extruder G92 E0 ; set E to 0 M109 S210 ; set extruder temperature to 210°C G1 F600 E-30 ; retract 30mm M104 S0 ; turn off extruder G91 ; set relative positioning G28 X Y ; home xy G90 ; set absolute positioning M106 S0 ; turn off fan Notes: ZTool (and g2z) expect the GCode to start with a comment (";"). This is used as quick validation when opening an unknown stream ZTool (and g2z) will warn about missing bed or extruder temperatures and enforce default values (80°C for the bed and 275°C for the extruder) AFAIK the firmware will also always use 80°C bed temperature if it's missing (Z-Suite 0.9.6b didn't create a command for bed temperature). Of course in ZTool you can patch the bed temperature down to 30°C to decrease the heat up time. The command M25 (SD card pause) is ignored. If at all I would support M226, but currently I don't. Have fun.

I kinda fear that ZTool and g2z might choke on minimum scripts like this. Both use the same backend which searches for layers and tries to determine the printing resolution which currently ends in a numerical exception if there is no model. Above that, it's a bit hard to determine what the firmware would make of this. Like it seems to expect certain start sequences as it does its auto-leveling magic in between ZCode commands even though there is no command that actually triggers the auto-leveling. Besides, an unload command with different temperatures was promised for the next firmware revision.

As some of you might know, before RaftAway and g2z there was ZDump which I started to develop in spring 2016. It started as a way to dump and analyze ZCode (hence its name) but soon became a tool to patch and convert ZCode. As Zortrax made clear they didn't want me to release details about ZCode and other parties expressed their disapproval of a tool that would allow patching temperatures in software, I decided not to release it. RaftAway and g2z (which initially only supported official Z filaments) were my way to try to let other people participate in some of ZDump's features without offending Zortrax or the producers of hardware mods. Now that Zortrax removed the temperature restrictions, only the ZCode dumping and analysis features stopped me from releasing ZDump. Hence I decided to drop these things for a public release and rename the whole thing to ZTool as the previous name didn't make much sense any more. So here is the public release of ZTool (based on the never released v0.2.5 of ZDump): https://www.dropbox.com/sh/91jdv24taxeayof/AACiBRHvH_d0FjRbo0cKEkwOa?dl=0 Profiles for G-Code: https://www.dropbox.com/sh/tmv5imtvw120r5b/AADyGH0L23Jfq8k0qyVntXdTa?dl=0 Feature wise it's a superset of RaftAway and g2z with some additional things like preview, fan speed graph and support removal. Display features Display embedded ZCode header information Display extruder and bed temperature Display fan speed graph over Z position Layer preview Edit features Edit extruder and bed temperature Move the model up (and down) a given offset Limit the fan speed to a maximum threshold (%) Increase retraction in order to reduce strings and blobs in prints Modify the extrusion rate of the first model layer, in order to improve bed adhesion and bottom surface quality when printing without a raft Modify the extrusion rate of the rest of the model Reduce printing speed in order to print flexible filaments and others that cannot cope with high extrusion rates. Increase printing speed to decrease printing time (while sacrificing quality) Remove raft Remove support within a defined polygon between a given start and end layer Change HW version, firmware version and material profile embedded in the header Conversion features Import G-Code which allows converting G-Code created by other slicers to ZCode As usual, there's a manual in rich text format (RTF) included. Have fun.

First of all, I would never claim to be a 3D printing expert just because I understand the details of ZCode. Actually I'm printing much less and with much less interesting materials than most other people here or in the Zortrax forum. So honestly my plan was to write the converter and let more experiences users do the work to develop proper profiles. Unfortunately, this hasn't really worked out yet during the ~12months of the unofficial beta phase as only surprisingly few people feel the urge to report back no matter whether they succeeded or failed. This being said you can be sure that Zortrax put a lot of effort into the raft creation by Z-Suite and I don't think that every aspect of it can be achieved when using other slicers. Some people tend to think that the material profiles in Z-Suite would only differ in temperatures, but this is far from true. Actually there are more internal parameters in Z-Suite than in any other slicer I know. E.g. there is not only a different set of parameters for the raft, but for several parts of the raft (bases, grid, surface/interface) and the 1st model layer. IMHO part of the magic is also done by controlling the fan. E.g. Z.Suite usually disables the fan while the raft is printed and jumps up to 20% just after the raft interface layer and before the 1st model layer starts. To some degree you can simulate this e.g. in S3D by setting the fan to 20% at the Nth layer (if there are N-1 raft layers). For support interfaces at higher layers, this will get a bit tricky though.

It's good to know that the m300 works as well. Only got feedback for the m200 up to know. Anyway: there's a reason why I didn't post about g2z in the official forum. I really try to avoid provoking Zortrax and what you're doing right now in their forum isn't really going to help anybody.

Actually I decided to stay anonymous and unpaid at least until Zortrax officially withdraws the threats to sue me for reverse engineering Z-Code. Regarding the "separation distance": I didn't actually look at this detail, but the translation from G-Code to ZCode is as direct and 1:1 as possible, so usually every print/retraction move, Z hop or speed change should be translated 1:1. So given that I didn't mess anything up, I would assume this should work just as with G-Code. Side note: as I commented above, the end code might be problematic for the m300: G0 F1800 Z180 ; move up extruder (needs to be changed for m300) This moves the Z position to 180mm (the maximum height for the m200). Honestly I'm not sure if this is really necessary, it's just that Z-Suite jumps to a Z position slightly above the model and I tried to simulate this. Now for the m300 (and a model which is at least 180mm high), this Z position might not suffice. Maybe it's better to change the Z180 to Z300 (300mm). Dunno if the bed always moves down automatically or not. Btw: I'll release another tool soon (weekend maybe). Like the superset of RaftAway and g2z.

In the light of the support of external material in Z-Suite, I removed the temperature limitations from g2z. Just be sure to select one of the new "based" profiles. Like "ABS based" will use the temperatures from G-Code while "Z-ABS" will still use the predefined temperatures. Again, I didn't enforce the new firmware 1.1.0 for the new profiles but would recommend to use it. Dunno how older firmware versions will react to the new profiles. Download as usual: https://www.dropbox.com/sh/cgt3evjontdbpjm/AADYV5T384EDeFjAgKgIB5kha?dl=0 [EDIT] Updated to 1.0.2b to add temperature range check when taking over temperatures from G-Code.

I uploaded v1.0.1 which adds support for Z-ESD and improves comment parsing for Cura (and S3D)... Download link is unchanged: https://www.dropbox.com/sh/cgt3evjontdbpjm/AADYV5T384EDeFjAgKgIB5kha?dl=0 Side note: I didn't change the header to e.g. require firmware 1.0.6 as Z-Suite 1.9.0 does. Still I wouldn't recommend using that Z-ESD profile on an older firmware revision.

For the protocol: I just noticed that the S3D profile mysteriously disappeared when I uploaded the profiles folder instead of the 7z archive (because some folks who still live in the 20th century couldn't extract it). I have no idea why this happened though, but I uploaded the S3D profile again. I'd also want to emphasize that just throwing G-Code at the tool won't give proper results. Specifically he start/end codes/scripts included in the provided profiles are necessary. Start: G28 ; home all axes G92 X0 Y0 Z0 E0 ; set all axes to 0 G0 F180 Z15 ; move up extruder G92 E0 ; set E to 0 End: G0 F1800 Z180 ; move up extruder (needs to be changed for m300) M104 S0 ; turn off extruder G91 ; set relative positioning G28 X Y ; home xy G90 ; set absolute positioning M106 S0 ; turn off fan There are some other settings though that are needed in addition. Apart from dimensions and speed limits, there are e.g. settings like "Allow zeroing of extrusion distances" in S3D (should be switched off) or "Verbose G-code" in the Slic3r Print Settings (should be switched on).

It's not a trick but yes, actually I wrote one before working on the G-Code to ZCode converter. IMHO it's more of a gimmick though for a couple of reasons like: 1) G-Code is printer specific to some degree. Not all printers support all commands, comments are handled differently etc. So I guess different printer profiles would be needed and honestly I didn't (and still don't) see much sense to invest time in this. 2) There is no 1:1 relationship between G-Code and ZCode. Some of the information stored in ZCode would get lost or could only be stored in comments 3) Z-Suite slices Zortrax filaments for Zortrax printer and there are no configuration options to change this. From initial layer height to retraction/extrusions settings and temperatures: printing anything else than Zortrax filaments on anything else than a Zortrax printer would be problematic. I guess even printing on a Wanhao Duplicator 6 wouldn't work without G-Code patching due to lack of perforated bed and fixed initial layer height. Even things like a slightly different extruder friction and fan efficiency are problematic. 4) Z-Suite is not publicly available (you need to enter your serial number to download and install it), so Zortrax could argue people using it to slice for other printers would violate their IP. So, honestly, I don't think I will ever release a standalone ZCode to G-Code converter. At least not as long as there are much more interesting options. Like e.g. a standalone support removal tool ;)

So there it is, the first (AFAIK) freely available G-Code to ZCode converter: Download from Dropbox https://www.dropbox.com/sh/cgt3evjontdbpjm/AADYV5T384EDeFjAgKgIB5kha?dl=0 Slicer Profiles: https://www.dropbox.com/sh/tmv5imtvw120r5b/AADyGH0L23Jfq8k0qyVntXdTa?dl=0 There is a manual (g2z.rtf) and a folder with profiles for different slicers included ("profiles"). These profiles include necessary settings and start/end codes, so use them as starting point for your own ones instead of starting from scratch. Currently there are basic profiles for S3D, Slic3r, Cura and IdeaMaker. I'd recommend to use S3D though since this is the only version that was actually tested AFAIK. Note that g2z parses the comments created by S3D, Cura or Slic3r to allow correct display of support and model print moves in Z-Suite. This was not adapted or tested for G-Code created by IdeaMaker and thus will most probably not work. Anyway, all the supplied profiles are meant as a starting point, i.e. to use export settings that g2z will understand and to use the correct start/end codes. About everything else in the profiles is up to you to change to improve your printing experience. Be aware you're leaving the comfort zone of Z-Suite and will experience failed prints due to lacking raft adhesion etc. Note when using S3D, it's recommended to use the newest version of S3D (3.1.x) since the previous version (3.0.x) tended to create tons of multiple or pointless G-Code lines. The Slic3r profile is the newest profile and AFAIK it's more or less completely untested. It was created for the Prusa Edition (with variable layer height) so I'd recommend to use this version if you intend to use Slic3r. [EDIT] The restriction to support only official temperature profiles was removed with 1.0.2. Now only the "Z" profiles will enforce official temperature profiles while the "based on"/external profiles will use the temperatures from the G-Code. There are no other restrictions. Try printing with 50µm (or even variable layer height) and nothing will stop you from using Z-ABS on a m300. As soon as Zortrax adds a Z-PLA profile (which they kinda promised for 2017), I will add it to g2z. And hey, it's free... Have fun.