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

Extruder temperature problem (160 deg) #2963

Closed
modeljjy opened this issue Feb 1, 2016 · 11 comments
Closed

Extruder temperature problem (160 deg) #2963

modeljjy opened this issue Feb 1, 2016 · 11 comments

Comments

@modeljjy
Copy link

modeljjy commented Feb 1, 2016

Hi, this is James. I have a question about the extruder temp. I have a Lulzbot TAZ 4 model with one extruder.
The temperature of extruder is not risen up to the desired temperature (220 deg) for ABS, just remaining within 160 deg. I already changed the extruder, heat resistor, and firmware. But same results. I do not think the mainboard (RAMBO v.1.3.) have the problem.
Today, I found some messages in Cura.

Here are the message:

Recv: echo: Last Updated: Feb 20 2015 10:55:07 | Author: (Aleph Objects, Inc, TAZ  config)
Recv: Compiled: Feb 20 2015
Recv: echo: Free Memory: 3114  PlannerBufferBytes: 1296
Recv: echo:Stored settings retrieved
Recv: Error:0
Recv: : Extruder switched off. MINTEMP triggered !
Changing monitoring state from 'Operational' to 'Error: 0: Extruder switched off. MINTEMP t...'
Recv: Error:Printer stopped due to errors. Fix the error and use M999 to restart. (Temperature is reset. Set it after restarting)
Recv: echo:SD init fail
Recv: start
Recv: echo: External Reset
Recv: Marlin 1.0.0
Recv: echo: Last Updated: Feb 20 2015 10:55:07 | Author: (Aleph Objects, Inc, TAZ  config)
Recv: Compiled: Feb 20 2015
Recv: echo: Free Memory: 3114  PlannerBufferBytes: 1296
Recv: echo:Stored settings retrieved
Recv: Error:0
Recv: : Extruder switched off. MINTEMP triggered !
Recv: Error:Printer stopped due to errors. Fix the error and use M999 to restart. (Temperature is reset. Set it after restarting)
Recv: echo:SD init fail
Recv: 

Somebody help me! I really want to fix it. If you have a solution, I will give a reward for any way.

Regards,
James

@brainscan
Copy link

Can you post your configuration.h etc for people to look at please? Also what temp does it show when at room temperature?

Sent from my iPhone

On 1 Feb 2016, at 22:04, modeljjy [email protected] wrote:

Hi, this is James I have a question about the extruder temp I have a Lulzbot TAZ 4 model with one extruder
The temperature of extruder is not risen up to the desired temperature (220 deg) for ABS, just remaining within 160 deg I already changed the extruder, heat resistor, and firmware But same results I do not think the mainboard (RAMBO v13) have the problem
Today, I found some messages in Cura

Here are the message:
Recv: echo: Last Updated: Feb 20 2015 10:55:07 | Author: (Aleph Objects, Inc, TAZ config)
Recv: Compiled: Feb 20 2015
Recv: echo: Free Memory: 3114 PlannerBufferBytes: 1296
Recv: echo:Stored settings retrieved
Recv: Error:0
Recv: : Extruder switched off MINTEMP triggered !
Changing monitoring state from 'Operational' to 'Error: 0: Extruder switched off MINTEMP t'
Recv: Error:Printer stopped due to errors Fix the error and use M999 to restart (Temperature is reset Set it after restarting)
Recv: echo:SD init fail
Recv: start
Recv: echo: External Reset
Recv: Marlin 100
Recv: echo: Last Updated: Feb 20 2015 10:55:07 | Author: (Aleph Objects, Inc, TAZ config)
Recv: Compiled: Feb 20 2015
Recv: echo: Free Memory: 3114 PlannerBufferBytes: 1296
Recv: echo:Stored settings retrieved
Recv: Error:0
Recv: : Extruder switched off MINTEMP triggered !
Recv: Error:Printer stopped due to errors Fix the error and use M999 to restart (Temperature is reset Set it after restarting)
Recv: echo:SD init fail
Recv:

Somebody help me! I really want to fix it If you have a solution, I will give a reward for any way

Regards,
James


Reply to this email directly or view it on GitHub.

@KiteLab
Copy link
Contributor

KiteLab commented Feb 2, 2016

Ether its extremely cold,
or your thermistor is unconnected now.

@bobsalter
Copy link

Im having a similar problem. Everything looks good, bed heats but extruder never quite makes it, gets to within 10 of set temp then goes down and up forever

@o3dodgesrt4
Copy link

similar issue here on my delta... target temp is 220... gets to 200-206C and then turns off and hard reboots... sometimes it just fluctuates and never stabilizes... even after a auto PID tune... iv replaced the hotend (E3dv5) with the complete E3Dv6 kit and still had the same issue..then i replaced the ramps 1.4 with a known working one from my mendel90, and same issue...iv been fighting it for weeks now trying to figure it out, but to no avail...

@thinkyhead
Copy link
Member

Do you see this problems with version 1.0.2 or just in the current RC? There have been some changes to the thermal-protection code. However, the heating itself should still be reliable.

@bobsalter
Copy link

1 and 1.0.2 run perfectly. Problem for me is only in current RC

Bob

@o3dodgesrt4
Copy link

current RC for me as well.. im using 1.0.2 right now and it works fine for my delta... whats weird is that the current RC seems to work just fine for my mendel90 but not my delta...both printers using the same equipment, RAMPS1.4, full graphics lcd, e3dv6 performance kit, mechanical endstops, heaters are identical brands and watts, Temp sensors are identical brands and resistances.

@thinkyhead
Copy link
Member

Y'all should try the RCBugFix branch just to confirm this hasn't already been fixed (either intentionally or as a side-effect).

I'll just post these links here for our convenience:

It also occurs to me that we can look at the History for an individual file. So we should especially review commits to temperature.cpp if it comes down to that.

Meanwhile try to isolate the issue by turning options on and off. Settings to play with include USE_WATCHDOG, THERMAL_PROTECTION_HOTENDS, THERMAL_PROTECTION_BED, PIDTEMP, BANG_MAX, PID_FUNCTIONAL_RANGE… probably some others. This will help narrow down the cause.

@jbrazio
Copy link
Contributor

jbrazio commented Apr 28, 2016

Thank you for your interest making Marlin better and reporting this issue but this topic has been open for a long period of time without any further development. Marlin has been under heavy development for the past couple of months and moving to it's last mile to finish the RC cycle and release Marlin v1.1.0. We suggest you to try out the latest RCBugfix branch and reopening this issue if required.

@jbrazio jbrazio closed this as completed Apr 28, 2016
@o3dodgesrt4
Copy link

Yup no prob. Close it if it wasnt already..
On Apr 28, 2016 12:04 PM, "João Brázio" [email protected] wrote:

Thank you for your interest making Marlin better and reporting this issue
but this topic has been open for a long period of time without any further
development. Marlin has been under heavy development for the past couple of
months and moving to it's last mile to finish the RC cycle and release Marlin
v1.1.0
. We suggest you to try out the latest RCBugfix
https://github.com/MarlinFirmware/Marlin/archive/RCBugFix.zip branch
and reopening this issue if required.


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#2963 (comment)

@jbrazio jbrazio modified the milestone: 1.1.0 Jul 16, 2016
@github-actions
Copy link

github-actions bot commented Apr 5, 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 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants