Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bed Heating issues with LIN_ADVANCE #5034

Closed
waynestallwood-kcom opened this issue Oct 16, 2016 · 9 comments
Closed

Bed Heating issues with LIN_ADVANCE #5034

waynestallwood-kcom opened this issue Oct 16, 2016 · 9 comments
Labels
Bug: Potential ? Needs: More Data We need more data in order to proceed

Comments

@waynestallwood-kcom
Copy link

I've noticed with LIN_ADVANCE enabled on RC7 that smaller object prints with short layer times seem to result in the printer not being able to keep the bed warm, (hardware confirmed ok as bed heats and stays heated when printer not printing or printing larger more complex layers)

This seems to be related to layer complexity rather than setup or slicer because printing 5 of the same item at the same time on the bed solves the problem and the print can complete. Otherwise the print aborts eventually

https://s3-eu-west-1.amazonaws.com/ws-share/Printer_crash.tiff

Discoverd on a E3D BigBox , Marlin running on a Rumba, running at 4500.0 mm/min, 11500 baud as suggested when enabling LIN_ADVANCE, PID's calibrated for Hotend and Bed (Bed set to PID mode)

@Blue-Marlin
Copy link
Contributor

Blue-Marlin commented Oct 16, 2016

My crystal ball let me see this story.
Your slicer detects a short layer time and orders the part fan to run. Because the nozzle is still very deep the bed is cooled, the heater can't keep up and the temperature is dropping. After a while you get a thermal protection error including a kill.
Likely this is completely independent from LIN_ADVANCE.
Please retry without advance.
Please try with longer min layer times.
Please try to heat your bed to 80°C, drive your nozzle to the middle of the bed and switch on the part fan. Can the heater keep up?

@Roxy-3D
Copy link
Member

Roxy-3D commented Oct 16, 2016

If indeed it is a small part with a short layer time... Try moving it some where else on the bed so the fan is not cooling the bed location with the thermistor that measures the bed temperature.

@Blue-Marlin
Copy link
Contributor

@Roxy-3D
If the sensor is in the middle of the bed your way is mostly counter-productive - because the part usually is shielding the sensor area.

@Roxy-3D
Copy link
Member

Roxy-3D commented Oct 16, 2016

Mostly, I was hoping to get another data point in order to understand the problem. I don't know the shape of the object being printed, or where the sensor is. We also do not know if the part is covering up the sensor but that would be good to know. If it is covering up the sensor, the fan is probably not entering into the equation.

@waynestallwood-kcom
Copy link
Author

Sorry I was trying to attach some files to help with this (including the gcode I printed with) Part does cover the sensor and fan is set very very low (20% in this case) I've not seen problems with my fan cooling the bed before like this and my 24v bed usually has enough heating power to cope (80 is nowhere near what it can cope with) but it's a good thought. I'll retest tomorrow without fan and close the issue if I can't reproduce it like that.

@AndyZuerich
Copy link

AndyZuerich commented Oct 18, 2016

Hi,

just another idea (but I am not really sure if this applies at all, therefore it is just a thought, and possibly my thought is completely wrong):
Please have a look at this issue [https://github.com//issues/4931]
Could it be possible that the thermal manager is not working properly when the layer complexity is too high (as you described)? When you print 5 of the same items, you always have the movement between the items (which might be high speed, but without complex calculation), and then the printer has time to call the heater manager.
As @thinkyhead described in the other issue, the heater manager is possibly not called regularly enough.

@thinkyhead thinkyhead added Bug: Potential ? Needs: More Data We need more data in order to proceed labels Oct 22, 2016
@boelle
Copy link
Contributor

boelle commented Nov 5, 2016

@thinkyhead what is the status on this one?

@thinkyhead
Copy link
Member

what is the status

Mysterious. But the advance code has gotten a lot of good tweaks recently. I'll close this for now and if the problem is still lingering we can always re-open it.

@github-actions
Copy link

github-actions bot commented Apr 2, 2022

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug: Potential ? Needs: More Data We need more data in order to proceed
Projects
None yet
Development

No branches or pull requests

6 participants