-
-
Notifications
You must be signed in to change notification settings - Fork 520
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
Starting Gcode ignores M106 command under certain conditions #4411
Comments
Its somehow expected behaviour. According to the standard the M106 gcode the S parameter number has to be an integer from 0 to 255 (0 for 0% speed and 255 for 100%). So what is Your goal? To set to some percentage of full speed (like 0.2 which represents 20% of full speed)? |
The duet documentation states that values between 0.0 and 1.0 can be used, as well as 0-255. My goal is to use the first interval since it is much more intuitive (70% is S0.7 or S179, 15% is S0.15 or S38, you chose which fits you the best). |
Duet support means Reprap type gcode extension. I still use SS 2.4.58.5 and this version exports custom start gcode with M106 S0.2 (I have checked with gcode flavours set to Reprap, Klipper and Marlin). So it is (was) possible. I think we have to wait for Meril to make it clear (bug or intentional change). Have You set gcode flavour to Reprap in Your SS version? |
I came to the same conclusion, my custom gcode was from way earlier when the fans still started. I guess somehow this snuck its way into SS again in the meantime. I also checked beforehand that RepRap Firmware flavor was indeed selected. I hope this can help people that are now having the same issue! |
What happened?
Behaviour
The "Start G-code" ignores M106 when expressed as a decimal number between 0 and 1:
Since this doesn't concern the cooling or toolhead fans, I cannot work around this bug in the filament cooling menu.
This does not happen with values large enough (20 for example):
I guess this avoids PWM values that are too low for a fan to spin (0-255).
I am aware that this has been an issue before (#834 (comment)), but I presume the fix was only applied to numbers between 0 and 255.
A suitable fix would be to allow the number range between 0 and 1 (on a Duet 6hc running RepRap Firmware this command is recognized) or prevent the user from exporting the gcode as long as the argument is not in the correct range.
Project file & How to reproduce
Version
2.5.59
Operating system
Windows 10
Printer model
Voron 2.4r2 with Duet 6hc+3hc running RepRap Firmware
The text was updated successfully, but these errors were encountered: