Notifications
Clear all

Bed Preheat Error Fw 3.1 (April 1st)  

  RSS
Alexander
(@alexander-3)
Trusted Member
Bed Preheat Error Fw 3.1 (April 1st)

Hi,

today I got a Bed Preheat Error for the first time with my printer. I printed a tiny ABS part (Dishwasher roller 22mm dia) with the standard settings of the latest Slic3r.

The only change I did: 20% fan after the first layer. Otherwise the parts don't turn out well.

The problem occured after more than 10 layers. Switched off the printer, started the print once more: same result: after roughly 2mm (0,15 resolution) the error appeared.

Coincidence: the day before I updated from 3.6 (which worked well) to 3.7 (final).

I printed a bigger part in ABS yesterday (after FW Update) and the error did not occur. I, however, did not activate the coller to 20%,

Since the printer worked fine before I think I can rule out cabling errors.

What fixed it for me for the time being: lowering the temp for the rest layers from 110° to 95°. This is a clear prove to me that there are no cable issues.

This post is primarily to make PRUSA aware of this problem. I can live with that now. Since I read that this problem seems to occur from time to time after upgrading FW (not only this version) I thought I share my experience. Maybe someone is able to really figure out what's going on.

Posted : 20/04/2019 12:04 pm
--
 --
(@)
Illustrious Member
Re: Bed Preheat Error Fw 3.1 (April 1st)

It may be how the 3.7 controls the heaters using a different algorithm. I've seen weird heat errors on parts that deflect air upwards, and the print fan running will cool the nozzle - dramatically - when it passes over portions of the part. Turn off the print fan in these cases has helped me. A hot end printing sock is another solution.

Posted : 20/04/2019 11:34 pm
joreal
(@joreal)
Estimable Member
Re: Bed Preheat Error Fw 3.1 (April 1st)

I am also having bed pre heat error. I replugged my cables but still the same. My only work around was to set the second to the last layer bed temperature to 60C for the PETG material.

It still persists even after updating to 3.7. I hope it's a firmware problem not hardware.

Posted : 21/04/2019 3:41 pm
Share: