[M SERIES PLUS / M300 DUAL / ENDUREAL] 2.7.0 firmware release

Firmware 2.7.0 has just been released.

You can download it from downloads section of the support center.
Direct links: M200 Plus, M300 Plus, M300 Dual, Endureal

Changelog available below:

  • Added option to load model material onto the support hotend for multi-material printing
  • Added G-code support
  • Added manual nozzle offset Z calibration for Endureal printer
  • Other fixes, improvements and changes in firmware architecture

About G-code support:

We currently support G-code files generated by PrusaSlicer and Ultimaker Cura. We parse the headers accordingly, verify the dimensions of the build area, read the print time, etc.

G2/G3 arc and M900 linear advance commands are supported.

To print G-codes, enable G-code support in the Working Options menu and disable filtering by printer type in the Files menu to display G-code files.

Basic parameters of the printers for adding a printer profile to your preferred software:

  • Work Area Dimensions (XYZ):
    • M200 Plus: 200 x 200 x 175 mm
    • M300 Plus: 300 x 300 x 312 mm
    • M300 Dual: 265 x 265 x 300 mm
    • Endureal: 390 x 300 x 300 mm
  • Relative positioning for E axis
  • No offset added for second extruder in dual extrusion mode (offset is handled by firmware)

Any feedback is welcome!

good news for the community!

I hope SO much this comes to the inventure too. I have a whole print farm of those and this would basically save it from being discontinued.
Thanks for finally going these steps! If this would have happened earlier, it would have been so good for Zortrax!

When loading a gcode file, the following message appears:

Can you please send the gcode to maciej.zaborowski@zortrax.com so I can test it? I admit, more work around gcode support is cerainly to do.

What slicer software did you use?

Prusa Slicer and Cura. I tested several files, the effect is identical. I sent the files.

Thank you! I got it. Will investigate further and get back to you tomorrow.

After investigation I can share 2 conclusions/bugs:

  • For gcode lines where there is no space separating command and arguments (ie. β€œG28X0” instead of β€œG28 X0”), the command won’t be parsed and will be ignored. Quick fix to that is to edit file in text editor and replace all occurences of β€œG28” (without space) to "G28 " (with space).
  • If you are using printer in language where decimal separator is comma instead of dot then you may experience error as in picutre. Quick fix is to change language to english.

Those will be fixed in next update.

Thank you for your assistance!

1 Like