Skip to main content

Canvas Hub Plugin stuck at verifying palette 2 connection

First time trying to use my Palette 2s - I have Octoprint on Raspberry pi 3b+ - going through the first time setup I made sure the palette was connected fine as was the printer - sending the gcode from Canvas cloud was cool and worked fine sending it to Octoprint. But when trying to do the first print setup, Octoprint is\was stuck at a screen saying “verifying palette 2 connection before starting print” While I was trying to figure out what to do - the printed homed and started printing - even with the octo page still stuck at this same point, Screen shot attached.

Block Image

I couldn’t do the first time setup because I couldn’t control the pi anymore - so I heated the hotend and bed via the printers control panel and manually fed in the pla for the cleaning part - then fed in the pla from the palette. So it going ahead and printing while Octoprint is still in that same screen.

Any ideas why?

Answer this question I have this problem too

Is this a good question?

Score 3

Comments:

so to resolve this stupid screen - I had to refresh it - and thank god it hasn’t come back since. One less screw up!

by

Add a comment

2 Answers

Hey @razz0r, glad to hear this issue was resolved - it sounds like the Hub needed to reestablish its connection to your Palette. Please let us know if you continue to experience this issue in the future!

Was this answer helpful?

Score 0
Add a comment

I have the same problem but the Palette 2s Pro never even makes any filament to feed into the printer. If I click “Start Print” on the Palette and select my print file, it freezes until I reboot it.

I’ve tried restarting everything, disconnecting and reconnecting, sending a clear all to the palette from Octoprint (which works so I know they’re talking to each other). Nothing seems to work. Any help is appreciated.

Was this answer helpful?

Score 0

Comments:

Hey Ben, are you starting the print on OctoPrint? If you are in connected mode (using a Hub), you should not have to start the print from the Palette screen - after you start the print on OctoPrint, Palette should say "Initializing" and then prompt you to load filament. Are you stuck on the "Initializing" screen?

by

I'm starting the print from Octoprint. I've been printing just fine with my Palette for a couple of months and took a break for a few weeks. When I came back to it, now it's doing this "verifying palette 2 connection before starting print" thing. Previously, I would start from Octoprint and not have to touch the Palette to start the print just as you describe. Now, though, I start the print in Octoprint, immediately 2 things happen: 1. My printer starts warming up and 2. a grey screen pops up on Octoprint with a message "verifying palette 2 connection before starting print" with no buttons or any way to clear the message. And it just sits there forever until I refresh the page. Nothing happens on the Palette at all. When I refresh the page and go to the Palette plugin tab in octoprint, I see that it says "0 of 3 splices" so it's getting the message somehow but just never doing what it's supposed to do. And it's connected - I double checked before and after refreshing the page. Thanks for your help @alina !1!

by

By the way, I also reset my Palette to factory settings and verified that it has the latest firmware. Same for Octoprint plugin.

by

@ben Hm, since it sounds like everything was working correctly before, I think the issue is likely physical - can you try a different USB cable to connect your Hub to Palette? Have you updated everything on OctoPrint when prompted? Could you also share an OctoPrint log from a day that this error occurred (instructions here: mm3d.co/octoprint-logs)? You can send the log to alina@mosaicmfg.com if you have trouble attaching it here. Thanks!

by

I figured it out. I have a rather long start GCODE (bed leveling, purging, etc.) that I recently moved from Cura slicer to Octoprint. When the GCODE is in the slicer, I have no problem with Palette. When it's in Octoprint, Octoprint runs the entire start GCODE before handing over control to the Palette. The error that pops up about connectivity is a red herring. it has nothing to do with connectivity, everything to do with how Octoprint handles GCODE. Anyway, it's working as expected now. Thank you for your help!

by

Show 3 more comments

Add a comment

Add your answer

Chris Wilke will be eternally grateful.
View Statistics:

Past 24 Hours: 0

Past 7 Days: 2

Past 30 Days: 4

All Time: 230

Contact Mosaic Support Team

© 2021 Mosaic Manufacturing Ltd.