New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: option to use mm^3 for E values #1746

Closed
whosawhatsis opened this Issue Feb 1, 2014 · 10 comments

Comments

Projects
None yet
3 participants
@whosawhatsis

whosawhatsis commented Feb 1, 2014

I've recently implemented M200 in Marlin, which makes it possible to send the filament diameter to the firmware and then send E values in units of volume (cubic millimeters) instead of sending an extrusion length (with filament diameter data already baked-in). This makes it possible to adjust the filament diameter after slicing, and is needed for the UFID project or printers with a built-in filament measuring device. Slic3r just needs to be able to send the M200 code and output E values in these units, bypassing the step where extrusion length is calculated from filament diameter and just sending the volume measurement.

@alexrj

This comment has been minimized.

Show comment
Hide comment
@alexrj

alexrj Feb 7, 2014

Member

I will do that, thank you for the idea :)

Member

alexrj commented Feb 7, 2014

I will do that, thank you for the idea :)

@alexrj alexrj added this to the 1.2.5 milestone Jan 5, 2015

@alexrj

This comment has been minimized.

Show comment
Hide comment
@alexrj

alexrj Jan 5, 2015

Member

@whosawhatsis, how are multiple extruders supported with M200?

Member

alexrj commented Jan 5, 2015

@whosawhatsis, how are multiple extruders supported with M200?

@whosawhatsis

This comment has been minimized.

Show comment
Hide comment
@whosawhatsis

whosawhatsis Jan 5, 2015

Same as with M104/109, diameter value goes to the active extruder unless you include a tool number on the same line, so for a dual extruder you would see something like this:

M200 D1.75 T0
M200 D1.8 T1

whosawhatsis commented Jan 5, 2015

Same as with M104/109, diameter value goes to the active extruder unless you include a tool number on the same line, so for a dual extruder you would see something like this:

M200 D1.75 T0
M200 D1.8 T1

@alexrj

This comment has been minimized.

Show comment
Hide comment
@alexrj

alexrj Jan 5, 2015

Member

Great!

Member

alexrj commented Jan 5, 2015

Great!

@whosawhatsis

This comment has been minimized.

Show comment
Hide comment
@whosawhatsis

whosawhatsis Jan 5, 2015

BTW, as with M104/109, you should scan the start gcode for an M200 and not insert another one if it's there. It can be advantageous to insert it in a specific place in the start code, such as after a priming procedure.

whosawhatsis commented Jan 5, 2015

BTW, as with M104/109, you should scan the start gcode for an M200 and not insert another one if it's there. It can be advantageous to insert it in a specific place in the start code, such as after a priming procedure.

@alexrj

This comment has been minimized.

Show comment
Hide comment
@alexrj

alexrj Jan 5, 2015

Member

Good idea. Done! :-)

Member

alexrj commented Jan 5, 2015

Good idea. Done! :-)

@alexrj

This comment has been minimized.

Show comment
Hide comment
@alexrj

alexrj Jan 7, 2015

Member

Discussion followup at:
47e4e8b#comments

Member

alexrj commented Jan 7, 2015

Discussion followup at:
47e4e8b#comments

alexrj added a commit that referenced this issue Jan 9, 2015

@alexrj alexrj closed this Jan 9, 2015

@alexrj alexrj added the Done label Jan 9, 2015

@braddo99

This comment has been minimized.

Show comment
Hide comment
@braddo99

braddo99 Jan 9, 2015

Is this compatible with triffid's trick where you put 1.12838 as the filament diameter then set the diameter in the firmware? I would have thought that if volumetric is set in the slicer then perhaps filament diameter would be greyed out, as it's to be set in firmware. Or is it that if M200 isn't set, the gcode will just continue in non-volumetric mode?

braddo99 commented Jan 9, 2015

Is this compatible with triffid's trick where you put 1.12838 as the filament diameter then set the diameter in the firmware? I would have thought that if volumetric is set in the slicer then perhaps filament diameter would be greyed out, as it's to be set in firmware. Or is it that if M200 isn't set, the gcode will just continue in non-volumetric mode?

@whosawhatsis

This comment has been minimized.

Show comment
Hide comment
@whosawhatsis

whosawhatsis Jan 9, 2015

@braddo99 Yes. What this does is ignore the filament diameter setting for gcode calculation and just export units of cubic millimeters. The filament diameter setting isn't greyed-out for (at least) two reasons:

  1. Filament settings are separate from machine settings, and you can use the same filament settings with a different printer profile and vice versa.
  2. Keeping the value in there allows you to use a replacement variable to fill in the value in an M200 line in your start code.

whosawhatsis commented Jan 9, 2015

@braddo99 Yes. What this does is ignore the filament diameter setting for gcode calculation and just export units of cubic millimeters. The filament diameter setting isn't greyed-out for (at least) two reasons:

  1. Filament settings are separate from machine settings, and you can use the same filament settings with a different printer profile and vice versa.
  2. Keeping the value in there allows you to use a replacement variable to fill in the value in an M200 line in your start code.
@braddo99

This comment has been minimized.

Show comment
Hide comment
@braddo99

braddo99 commented Jan 10, 2015

thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment