New drivers and firmware out
2.1 driver and 3.1.1 RC3 firmware. Trying now...
Re: New drivers and firmware out
Glad to see this update is out. The 2.0.0 drivers package shipped with filament profiles which contained conditional gcode to enable linear advance but the version of Slic3r shipped with it did not support the conditional gcode. I was very frustrated with my new machine until i made the upgrade. I am glad that the out of box experience for new users will be vastly improved now. Also glad to see the firmware update. I will be swapping that out as soon as my current print finishes up in a couple of hours.
Re: New drivers and firmware out
No improvement with internal Pi I'm afraid. Still very poor serial connection with many errors eventually leading to a crash. SD card is the only reliable way to print with the Mk3 at the moment.
I've also noticed that you have to reset the printer before every print. If you don't, and you try and run two prints without reseting then the Z axis is always a little too high on the second print. Not by much, probably only 0.25 mm, but that's enough to stop prints sticking. A reset before printing fixes this. Looks like the auto bed leveling gets confused if run twice.
Re: New drivers and firmware out
No improvement with internal Pi I'm afraid. Still very poor serial connection with many errors eventually leading to a crash. SD card is the only reliable way to print with the Mk3 at the moment.
I've also noticed that you have to reset the printer before every print. If you don't, and you try and run two prints without reseting then the Z axis is always a little too high on the second print. Not by much, probably only 0.25 mm, but that's enough to stop prints sticking. A reset before printing fixes this. Looks like the auto bed leveling gets confused if run twice.
Is this with the new firmware? I have not experienced that with RC2.
Re: New drivers and firmware out
Live Z seems to be missing once print starts.
Re: New drivers and firmware out
No improvement with internal Pi I'm afraid. Still very poor serial connection with many errors eventually leading to a crash. SD card is the only reliable way to print with the Mk3 at the moment.
I've also noticed that you have to reset the printer before every print. If you don't, and you try and run two prints without reseting then the Z axis is always a little too high on the second print. Not by much, probably only 0.25 mm, but that's enough to stop prints sticking. A reset before printing fixes this. Looks like the auto bed leveling gets confused if run twice.
Not having that problem with the Z height changing....
EDIT: It doesnt happen always but yes... im getting this aswell after all
Re: New drivers and firmware out
No improvement with internal Pi I'm afraid. Still very poor serial connection with many errors eventually leading to a crash. SD card is the only reliable way to print with the Mk3 at the moment.
I've also noticed that you have to reset the printer before every print. If you don't, and you try and run two prints without reseting then the Z axis is always a little too high on the second print. Not by much, probably only 0.25 mm, but that's enough to stop prints sticking. A reset before printing fixes this. Looks like the auto bed leveling gets confused if run twice.
Is this with the new firmware? I have not experienced that with RC2.
Had this problem with both RC2 and RC3. Not with the original version that shipped with the Mk3. Could be something to do with not applying the live Z correction correctly.
Re: New drivers and firmware out
Live Z seems to be missing once print starts.
Just checked, its there!
Re: New drivers and firmware out
How do you reproduce or confirm that live Z changed? I have not yet noticed it, but not sure that I have simply overlooked it.
Re: New drivers and firmware out
How do you reproduce or confirm that live Z changed? I have not yet noticed it, but not sure that I have simply overlooked it.
I happened to me once...
I printed something and then when i printed immediately after the nozzle was way up but the Z offset was the same....
After hitting the reset button that time it hasnt happened again..