Question: Displaying messages
-
Is there a decent method to display messages during a print?
M117 doesn't stay on screen very long, doesn't put the message into the console log, and has a bug that causes spurious "string too long" errors, only some of which can be dealt with by putting M400 first.
M118 often only puts the message into the console log and doesn't display on screen.
M291 mode 0 puts a huge message box up even if you're in the process of babystepping on the PanelEue, and there's no way to get rid of it without also closing the babystepping window. Mode 1 still puts the box up in front of what you're doing and you have to close it.
I'd either like something that simply respects that you're doing something (like M117 does), or something that puts the message where you can read it but it isn't in the way of your work. But I'd like to be able to keep the messages around a bit longer than M117 does, and if possible, put them in the console log too, in addition to displaying on screen/panel.
-
I used M291 a lot but they have closed or been closed by the time I get to actually printing which is when I adjust the babystepping.
What messages are you displaying once printing has actually started?
Frederick
-
@fcwilt Mostly layer counts after things have started.
-
@donstauffer said in Question: Displaying messages:
@fcwilt Mostly layer counts after things have started.
Layer counts via a M291?
How are you using them?
Thanks.
Frederick
-
@fcwilt Using them?
-
@donstauffer said in Question: Displaying messages:
@fcwilt Using them?
Well if you are displaying layer counts via M291 commands you must be doing so for some reason.
Yes? No?
Frederick
-
@fcwilt To keep track of what layer I'm on.
-
@donstauffer said in Question: Displaying messages:
@fcwilt To keep track of what layer I'm on.
The DWC already does that for you. Is it because the M291 is easier to read?
Thanks.
Frederick
Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6
-
@donstauffer said in Question: Displaying messages:
M117 ... has a bug that causes spurious "string too long" errors, only some of which can be dealt with by putting M400 first.
That is fixed in RRF 3.4beta.
-
@fcwilt I actually don't especially like how big M291 messages are. M117 is almost what I want. It seems to respect things you're in the process of doing on the PanelDue, and it shows both on the PanelDue and on the web interface. But I don't have the ability to make it appear in the console log (there's probably a way to do that with another command), and the messages boxes often don't hang around long enough (not that I want to have to clear them manually, but it varies, and sometimes it's a only few seconds). The display of layers includes the layer number and Z coordinate, and that can show on the PanelDue (which I think doesn't show the layer number, at least on most screens) and the web interface (which I think shows both on most screens but not all).
But most often I display messages during the startup script, before a skirt starts printing. Those aren't layer numbers or heights. The info varies, but mostly tells you what it's currently doing.
It seems like every message option has some of the features I want but none has them all. Any that interferes with babystepping is no good. Any that doesn't show on the PanelDue doesn't quite do it. Any that doesn't always show on the web interface isn't that great. And not logging to the web interface console doesn't keep a record after the message disappears. Maybe I'm missing something or being picky. It's not a huge big deal, but I gather the only options are M117, M118 and M291.
I'm not that fond of my CR-10s Marlin, but it does have a dedicated message line at the bottom that's very good (though short). A message stays there until cleared in code and doesn't interrupt anything in order to display. Something equivalent plus logging so I can look through past messages would be ideal. That's the kind of thing.
-
@donstauffer said in Question: Displaying messages:
But most often I display messages during the startup script, before a skirt starts printing. Those aren't layer numbers or heights. The info varies, but mostly tells you what it's currently doing.
I do the same.
But I still cannot wrap my head around using M291 to display layer height information since that information is already displayed in the DWC.
Thanks.
Frederick
