Skip to main content

The world's first multi-material slicer.

130 Questions View all

Why is canvas sending M0 command at the beginning of a print?

At the very beginning of a print on Canvas Hub using a gcode that was generated by Canvas, I see this in the terminal:

Changing monitoring state from "Operational" to "Starting"

Send: N0 M110 N0*125

Recv: ok

Changing monitoring state from "Starting" to "Printing"

Recv: TT::23.8323.83 //0.000.00 BB::24.3724.37 //0.000.00 @@::00 BB@@::00 Recv:

Changing monitoring state from "Printing" to "Pausing"

Info: Not sending M0 to printer, it's configured as a blocked command

Send: N1 M400*38

Recv: ok

Why is that happening? I don’t think it causes any issue but just wondering.

Answer this question I have this problem too

Is this a good question?

Score 0

Comments:

I have the same "problen" but Im using the plugins on my Raspberrypi with Octoprint. I cant start the print using the Octoprint webpage only via the Palette using the Cancashub tab and selecting the file. Otherwise the Palette isnt initializing. I think its because of the new Octoprint release.

I tried deleting the M0 command from the blocked command list under serial connection but that didnt help.

by

Add a comment

3 Answers

Hey @vorchak, the M0 pauses the print until Palette is ready and filament is loaded. Once the filament is made and loaded properly, pressing “start print” on Palette or in OctoPrint unpauses and the printer is able to start. The M0 is right at the top of the code because extrusion commands shouldn’t happen before filament is properly loaded. Hope that helps!

Was this answer helpful?

Score 0

Comments:

Hi @alina Thanks for the answer, I think the issue was caused by the latest Octoprint update, It is rejecting M0 as an invalid command. I do not know the reason for that or if the new behavior is even correct.

by

Add a comment

I just reset up my Palette 2 Pro now upgraded to S a couple of days ago after one year of not using it with a new Canvas Hub S and the new filament from Canvas. The issue of Octoprint blocking the M0 command is blocking successful use. I tried removing the block on the waiting command in Octoprint’s terminal filter setting but to no avail.

I’m unable to get filament properly and loaded and calibrated. Any ideas would be appreciated. I’m also posting something to the Octoprint Discord channel.

Was this answer helpful?

Score 0
Add a comment

The Octoprint Discord channel support says to read the following: https://github.com/OctoPrint/OctoPrint/i...

and then install the fix plugin at the end of the post.

I can’t get to that until tomorrow, but I’ll try it and report back.

Was this answer helpful?

Score 0

Comments:

Hey Mark, please don't delete the M0 command, it should be okay to just ignore the notification from OctoPrint. Could you clarify how it's affecting your ability to print with Palette?

by

Hi Alina,

Not trying to delete it. Just the opposite. I'm trying to get it back. By default now, Octoprint 1.5.1 suppresses the M0 command and does not send it to the Prusa. I get into a loop where the Prusa is trying to unload/load the filament that I eventually get past (not sure why), but by then the filament feed is off and the test prints don't print properly.

Mark

by

Applying the Hotfix for Octoprint mentioned above, you can now delete the M0 Command from the blocked Commands and everything works fine again. Remember to close the connection to the printer and reconnect, otherwise it will not work.

by

Add a comment

Add your answer

Tsung-Hsiang Hsueh will be eternally grateful.
View Statistics:

Past 24 Hours: 0

Past 7 Days: 2

Past 30 Days: 15

All Time: 373

Contact Mosaic Support Team

© 2021 Mosaic Manufacturing Ltd.