Skip to main content
User avatar

Crash? after print completion

I noticed after a long print that finished when I was away from home that the Palette 3 just had a white screen with no other info. The print had completed successfully, but the device was completely non-responsive.

I power cycled the Palette and it came back up, so I ran another print, this time checking it several times during the print and when it completed. The screen would occasionally blink white before returning to the status screen, and I was able to see the menu at the end of the print.

The following print that I ran, I intentionally left the palette sitting idle after the print and did not hit any buttons. After about a half hour, the screen went white and Canvas.io showed a yellow dot instead of a green one next to the device listing.

Another power cycle and the palette works again. Very strange, and frustrating glitch.

Answer this question I have this problem too

Is this a good question?

Score 0

Comments:

Adding some more details - it seems that sometimes the entire device doesn't crash, just the screen. Sending a new print to the Palette *sometimes* recovers it and the screen becomes responsive again. Very strange behavior.

by

Add a comment

1 Answer

User avatar

the Palette touch screen is running chromium and just rendering a web page. it's possible this is some sort of a chromium or X idle timeout. did you know you can reach your Palette's on-screen menu through a standard browser? just point your browser at the IP of the Palette port 5000. like this http://10.10.10.10:5000 if your Palette was on IP address 10.10.10.10 -- when you interact with the interface through a browser and click some actions (like start print), it will cause the Palette's touch screen to update.

Was this answer helpful?

Score 0

Comments:

I had just figured that out, very interesting that the control screen is exposed on a non-secured port.... not sure how I feel about that. Interestingly, when the screen on the Palette gets stuck white, the one on a PC browser does the same - so I think the problem lies somewhere in the javascript webapp they're running. A full refresh of the page on PC recovers the interface, and pressing any button from there seems to get the Palette to start recognizing again. Very strange indeed.

by

Add a comment

Add your answer

Author avatar Zeno LeHericy will be eternally grateful.
View Statistics:

Past 24 Hours: 0

Past 7 Days: 0

Past 30 Days: 0

All Time: 37

Contact Mosaic Support Team

© 2023 Mosaic Manufacturing Ltd.