P2 Error Numbers

Follow
Was this article helpful?
5 out of 9 found this helpful
Have more questions? Submit a request

Comments

15 comments

  • Avatar
    Stan Fisher

    you don't have error 312 listed..  I got this when I tried to update firmware fresh out of the box...  I ended up bricked after trying to recover via firmware updater..  and had to follow the "Screen firmware troubleshooting guide" and jumper the display board etc.  

     

    Update:   The description you added doesn't match that which is displayed with a 312.

    0
    Comment actions Permalink
  • Avatar
    Jonny Yeu

    Thanks, Stan! I'll update this page with the 312 error.

    0
    Comment actions Permalink
  • Avatar
    Frank Gnutzmann

    I got the 43 Error. But i couldn´t continue printing as the Palette2pro didn´t produce Filament anymore and the Filament was tangling loose arround in the buffer. Am working on stationary Transistion. Maybe the pullout is to fast? Trying a print w/ a Tower now.

    The Screen worked fine and the Reset Button shown was responsive. What else could Error 43 mean?

    Edit: the error could be reproduced w/ the same mcf file

    The last slice, after what he failed, was only ~3.6 cm Long. Could that be a reason?

    1
    Comment actions Permalink
  • Avatar
    Jonny Yeu

    Thanks for sharing, Frank! Could you please send us the MCF file that you experienced this issue with? support@mosaicmfg.com

    I'm not sure if that length of filament would have caused the issue, but we'll take a look!

    0
    Comment actions Permalink
  • Avatar
    arleas

    I just got an Error 43 where the palette 2 didn't continue the print.  Very frustrating after 10 hours of printing to look over at the printer and it's doing nothing in mid-air about 3 layers up.  As for the idea that it could be a super short segment producing the error, I was doing a print of the "Stuart the Rabbit Multi color" off of thingiverse and it had gotten to the part where it was doing the pupils of the eyes, but it was fine doing the little pink nose by itself so I don't know.

    0
    Comment actions Permalink
  • Avatar
    Jonny Yeu

    Sorry to hear that, arleas. Could you please send us your octoprint.log file from when you received the 43 error (support@mosaicmfg.com)? This would provide us with information about what may have caused this issue. We're working on helping to avoid these errors, and the log files can help us isolate the issue.

    0
    Comment actions Permalink
  • Avatar
    Kurt Skauen

    I have the same problem.

    The Palette 2 is the first appliance I have had in a very long time that I have to constantly power cycle because it hangs or just stop working (like empty file list when trying to start a print). Luckily so far it has mostly happen during initiation of a print.

    In general it seems that it must be power cycled between each print because it ends up in a broken state.

    But now I have a print that persistently fail within the first 5-10 layers. It is sliced with Simplify3D and converted using Chroma. It use 3 colors and is the first print where I have tried to use side-purge. So that might be related. It prints for a while and then I get error 43 before it cut the filament and stop splicing in more.

    I then gave up on multi-color printing and decided to try the multi-spool option to empty a few almost empty spools on a single-color print. I loaded up 3 spools in input 1-3 and started a print.

    Half way through the first layer it simply stopped feeding in new filament from the first spool. The printer drained the buffer, the blue light came on, and the printer extruder started grinding away on the filament.

    I'm soon ready to take a sledge hammer to my Palette 2...

    0
    Comment actions Permalink
  • Avatar
    Jonny Yeu

    Hi Kurt, I'm sorry to hear that you're experiencing this issue as well. If you're using a CANVAS Hub, could you please send us your octoprint.log files as well (support@mosaicmfg.com)? We've also found that some users were running plugins on their OctoPrint that were causing connection issues with their CANVAS Hub/Palette plugins, causing frequent 43 errors. We also expect to have a firmware release either today or tomorrow that should help with side transitioning issues.

    We're very sorry for the frustration that you've been experiencing but please feel free to reach out to us at anytime, we would be more than happy to help! 

    0
    Comment actions Permalink
  • Avatar
    Frank Gnutzmann

    Hello,

    after the last update from the Mosaic Plugins on my Octoprint i had the same issues with the need to restart the Palette2 between the prints. But i had also problems with autoconnect to the Palette2 from Octopi.

    I changed the USB Ports from the Printer and the Palette2. Now the Printer use usb1 and the palette2 usb0. Since then the autoconnect worked properly again and i didn´t had to Restart the Palette2 between the prints anymore.

    Greetings

    Frank

    0
    Comment actions Permalink
  • Avatar
    Patrice Pichery

    New Palette2 Pro freshly ordered. Opened, connected. Got 311 Error. Com not access denied. Tried 4 times. Is there something to repair it ? 

    0
    Comment actions Permalink
  • Avatar
    Jonny Yeu

    Hey Patrice, the 311 is usually fixed with a firmware re-flash. I see your support e-mail and will respond shortly.

    0
    Comment actions Permalink
  • Avatar
    Mrabushka

    I got the following error:

    "Error (Open (SetCommState): Unknown error code 31)"

    How do I fix this error?

    Documentation that came w/ Palette 2 Pro is terrible.  It doesn't even explain how to load filament into the unit.

    0
    Comment actions Permalink
  • Avatar
    Jonny Yeu

    Hi Mrabushka, when do you receive this error, is it during the firmware update? The error codes posted above will appear on Palette's screen.

    Concerning the loading of filament, Palette will prompt you to load filament whenever you start a print or print function. You would then insert filament into Palette's filament inputs.

    0
    Comment actions Permalink
  • Avatar
    Cabel McElderry

    Jonny can you help me. Here's the link to my slicer file: https://share.canvas3d.io/projects/4794eeef3e2915985c52481fc6189ce8

    Attached is the kind of result I get when I try to print anything multicolor outside of the calibration keychain (which has printed perfectly twice.)

    The filaments were for certain in the correct paths and loading was set perfectly to the mm.

    I've tried re-calibrating (why I've printed the calibration key chain twice) and it has no effect.

    Can you direct me? 

    Thanks much.

    0
    Comment actions Permalink
  • Avatar
    Jonny Yeu

    Hey Cabel, thanks for sharing this info with us. Do you have the ping/pong information from this print? Although you've already re-calibrated, I would ask if you could do so again following these steps:

    • Factory reset your unit to ensure that your original calibration values are erased (http://mm3d.co/calibration-troubleshooting)
    • Once reset, re-run the keychain calibration file. Please share pictures of your keychain and transition tower (http://mm3d.co/newkeychain-troubleshooting)
    • Once this is complete, run another print that uses around 15 m of filament. Please record the ping/pong values from this print. If you're using Accessory mode, this can be found during a print by going on Palette's screen, selecting the menu button (bottom right corner) and selecting Ping/Pong offsets. 

    Once we can review the information above, we'll be able to provide further assistance to help with the calibration issues that you're seeing here. If you'd prefer to send us an e-mail with this information rather than continue on this thread, please reach out to me at jonny@mosaicmfg.com.

    0
    Comment actions Permalink

Leave a comment