"Print again?" - first layer inconsistencies

Just curious if anyone has noticed any differences in the printed model when using the LCD touch screen to “print again” ?

I have 4 X1c printers and have observed this on each of them. If I send the print job to the printer from the slicer over the network - first time, prints perfectly - then I remove the print and the calibration lines (I do not disturb the build plate) - model comes off easily - clean the build plate and print again, this time using the LCD touch screen. I confirm the proper selected filament and build plate are shown and continue.

I have noticed that the first layer does not look the same - usually more layer lines are noticeable.

I am not sure what the difference would be - it could just be an odd thing - but it has happened.

I clean the bed start the job from the computer and the print is perfect again

Thanks for looking

When you “print again” which check boxes do you have checked? I always turn off calibration and timelapse but keep the bed leveling enabled. As a point of reference I do not see a difference in prints from sending/print again/print from SD. I often will use “print again” dozens and dozens of times.

1 Like

I’ve noticed this too, and it took me a few prints using the “print again” option on the printer to realize that it was printing erroneously, it’s almost like it chooses a different plate or first layer settings. I didn’t want to bother figuring out why, I just stopped using it.

1 Like

YES! - I saw this too! Another time I noticed this inconsistency was with the LCD UI - I printed with a textured PEI - verified from the slicer - printed perfectly, I go to use “print again” and this time the LCD shows a smooth PEI sheet and it does not allow you to change it. I guarantee there is some bugs here.

usually - i leave them default - when this happens - i noticed it does not create the flow calibration like it does when printing the first time.

What firmware version are you running? I can try to replicate the issue.

1 Like

Hey Jon - version 1.10 - which I believe is the latest cause I have not been prompted to update