[Feature Request] Implement G-Code M191

This is a request for implementing Gcode “M191 Snn”, “wait for chamber temperature to reach nn”.

Since there is no active heating of the chamber, the chamber temperature depends on the heating of the bed and it can take some 15 minutes before it reaches 45°C and actual printing with ABS, ASA, etc. can start.
Until now, I have to pause the printing until the temperature is OK.

Snapmaker Orca supports the wait (M191) in its filament settings, so, that would improve the automation of the printing process.

For the sake of convenience, how about editing the title to read “[Feature Request] Implement G-Code M191”? It’s great if a thread title explains what the thread is about!

Because Snapmaker is not actively reading all threads, open a ticket please:

A thread means we can chew it over as well.

Are you sure about that? This is a really small forum. Trust me… They read them.

Especially if you ask @Simon_Zhi to help, please

Just use a macro to create M191

gcode_macro M191

gcode:
{ set min = params.S|float }
;; From Heat-Soak Macro
;; fire up the heater
SET_HEATER_TEMPERATURE HEATER=heater_bed TARGET=105
;; run the fans to circulate air
_FAN_SOAK
;; home the printer
G28
;; put the bed and nozzle where they’re a safe distance apart
G90
G1 X60 Y60 Z80
TEMPERATURE_WAIT SENSOR=“temperature_sensor bme680” MINIMUM={min}

This is for a Nevermore so the tempature_sensor might be different.

Here’s the entire article about it. Macros to use M106 and M191 with Nevermore - Reemo's 3D Printing Notes

If you post it here, they might read it. If you send a ticket, they will read it.

I wouldn’t want to discourage things being discussed on the open forum, there may be alternative ideas which would not otherwise get aired.

Why not both?

I’m not excluding either option, but I do think it might be better to discuss an idea and refine it before pulling the trigger on raising it with staff. Somebody comes along with “I need X”, then the community kicks it around for a while and refines the idea to Y, but then to accommodate a slightly different use case it matures to Z. If X got into the system, staff effort would be wasted and we might end up with X not Y or Z.

Snapmaker are clearly using input from the community to guide and inform their efforts, and there are clearly a lot of experienced enthusiasts here with a wide range of knowledge and technical ability, so let’s act as a filter and guide them. The forum users are bound to react to an idea far faster than staff, so a few days’ delay before raising a ticket isn’t likely to be significant – and by refining ideas first, saving staff effort, might even end up with implementation more quickly.

In this particular case, M191 seems to be a niche requirement, and an alternative idea of implementing it as a macro has been suggested, so perhaps that is good enough and a support ticket to have it implemented in the base firmware may have been unnecessary (not that I know anything about macros – but I’m sure others do and can pass judgement, not least the OP!).

What about a bed heater

What do you mean?

I don’t agree.
the possibility to wait for a given chamber temperature, depending on the type of filament, is useful for everybody doing multi-material and/or using ASA, ABS, … So it’s not a niche.

In the second place, the Macro kindly given by Gramps-Too works on his Nevermore, but we don’t know if the sensor of the chamber temp currently is accessible on the U1. Given that M191 is not implemented points to the opposite direction.

Although I sympathize with your idea “Let’s all chew on it”, you know the saying “a camel is a horse designed by a committee”?

…but only when the committee lacks leadership and vision. There are aphorisms to “prove” any case you want!