M2 Temperature Problem

[Daniel Sánchez Tello]

I've been a week having this problem without any results!!! please help me!!! 

I checked the extruder connection and it is OK. Unplugged the extruder connection on top, and checked conductivity with a multmeter to the RAMBo, and seems OK. I don't know what else can i do!!!

Temperature is ok... on the bottom says, 

Printer is online. Hotend:19.5/0.0 Bed 19.6/0.0 @:0

Connecting...

start

Printer is now online.

echo: External Reset

Marlin 1.0.0 RC2

echo: Last Updated: 2012-08-15rtf | Author: johnny

echo: Free Memory: 4734  PlannerBufferBytes: 1232

echo:Using Default settings:

Error:1

: Extruder switched off. MINTEMP triggered !

Error:Printer stopped deu to errors. Fix the error and use M999 to restart!. (Temperature is reset. Set it before restarting)

echo:SD card ok

ok T:19.5 /0.0 B:19.6 /0.0 @:0

If I type M999

SENDING:M999

Resend:1

Error:1

: Extruder switched off. MINTEMP triggered !

Error:Printer stopped deu to errors. Fix the error and use M999 to restart!. (Temperature is reset. Set it before restarting)

[Joshua Wills]

Have you modified the firmware at all?

[Daniel Sánchez Tello]

no, should I?

[Daniel Sánchez Tello]

No, should I?...

[Joshua Wills]

Daniel - I sent you a direct email, hopefully I can assist you better there.

[Joshua Wills]

Are you sure that you have not modified the firmware?  The firmware that I install on every RAMBo that ships out the door, has a modified date that it echoes at boot of "echo: Last Updated: 2012-05-30 | Author: johnny".

Would you mind downloading the firmware from http://groups.google.com/group/makergear/browse_thread/thread/ae6b3b434cfd8220 , and uploading it to your electronics, so we have a known-good starting point?

[Daniel Sánchez Tello]

Joshua thank you very much!!! It was the firmware... As soon as I upload it the printer got connected, and start printing. But I want to know how this happened, because I just learned how to change the firmware on the RAMBo, was because I pressed the reset button on pronterface or in the RAMBo? When you reset the RAMBo, it reuploads a default firmware?

Again thanks for your concern and help!!! MG is the best! 

Daniel

[Joshua Wills]

No, resetting the board simply resets the installed firmware to it's stock condition.  The only way for the firmware to have been messed up in the way it was before you just fixed it, is if, during my initial upload process, something went awry and Arduino didn't say anything about it.  Which means that my verification test didn't catch the issue, causing you all this grief.  I now know of something else to look for when checking the boards before we ship them, so hopefully it will not happen again.  That it happened in the first place I am sorry for.

[Mike Sharp]

I'm experiencing this same problem. I've reloaded the firmware that you had linked to and still getting the error.

RECEIVED: Marlin: 1.0.0 RC2

RECEIVED: echo: Last Updated: 2012-05-30 | Author: johnny

Last Updated: 2012-05-30 | Author: johnny

RECEIVED: echo: Free Memory: 4775 PlannerBufferBytes: 1232

Free Memory: 4775 PlannerBufferBytes: 1232

RECEIVED: echo:Using Default settings:

Using Default settings:

RECEIVED: Error:0

RECEIVED: : Extruder switched off. MINTEMP triggered !

RECEIVED: Error:Printer stopped deu to errors. Fix the error and use M999 to restart!. (Temperature is reset. Set it before restarting)

SENT: M105

RECEIVED: ok T:0.0 /0.0 B:24.6 /0.0 @:0

[Daniel Sánchez Tello]

Try the last one that they came out with a few moths ago it is working perfect for me

--
You received this message because you are subscribed to a topic in the Google Groups "MakerGear - Make Today, Change Tomorrow" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/makergear/R7_XZDdMT3o/unsubscribe.
To unsubscribe from this group and all its topics, send an email to makergear+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[David Sharp]

Check your thermistor connection.  If the thermistor isn't connected, the temp will read 0, and cause marlin to assume that the thermistor has fallen off and to prevent a melt-down of your extruder, shut down power.

Dave

[MiseryBot]

I have been having a similar problem.

Since the beginning the temperature reading has always been noisy. Printing with PLA seems to still work OK. There is just some random time at the print start until enough readings happen to have a small enough noise level to start the print. I have "Stabilize Temperature At Startup" UNCHECKED, this seems to help some with PLA.

Today I am trying to print ABS, and the printer never starts the print. Just sits there waiting for the temp to stabilize.

I have attached screen shots.

I verified that I have the "echo: Last Updated: 2012-05-30 | Author: johnny" firmware.

Any ideas on how to proceed? Thanks for any help you can offer.

[MiseryBot]

Here is the problem:

> I have "Stabilize Temperature At Startup" UNCHECKED

I did not realize that there are TWO settings for that. One for the heated bed and one for the extruder. 

Working now.

Still does not explain the wildly fluctuating temperature readings . . . .

[Dale Reed]

MB,

 

Looks like one or more of the PID gains on the extruder temperature loop is too high.  Try the PID autotune procedure (by manually sending G-codes) documented at:

 

http://www.soliwiki.com/PID_tuning

 

Dale

[Leor Buch]

I have the same error:

Connecting...

start

Printer is now online.

echo: External Reset

Marlin 1.0.0 RC2

echo: Last Updated: 2012-09-26 | Author: 3dstuffmaker

echo: Free Memory: 1518  PlannerBufferBytes: 1232

echo:Using Default settings:

Setting hotend temperature to 220.000000 degrees Celsius.

Error:0

[ERROR] Error:0

: Extruder switched off. MINTEMP triggered !

Error:Printer stopped deu to errors. Fix the error and use M999 to restart!. (Temperature is reset. Set it before restarting)

[ERROR] Error:Printer stopped deu to errors. Fix the error and use M999 to restart!. (Temperature is reset. Set it before restarting) 

how can I solve this?

[Stoni Beauchamp]

I too have had this same error for over a week.  At first it wasn't every time, though I couldn't figure out what was different when it happened.  It would usually happen sometime on the first layer.  Now it happens every time before the print even starts no matter what I try.  I recently replaced my extruder motor so I thought possibly loose connection some where.  Joshua suggested testing the resistances for the thermistor and connectors, but everything seems to check out ok.  I can use the jog controls and do anything I want (heat, move, extrude) with no problems.  It only happens as soon as I begin a gcode.

I have tried reinstalling the firmware, to no avail.  I've tried with the bed off.  I've tried with different temperatures.  Nothing seems to work and I'm getting frustrated.  Anyone have any other ideas to try?

[Stoni Beauchamp]

Ok after even more troubleshooting I figured out that it was indeed a short in the wiring, just not in the places I was looking before.  I figured if it was a wiring problem that it would have developed in the connectors since I had changed out my hotend quite a bit, or in the board connectors.  Instead, it ended up being just outside the black wire housing that sits atop the extruder motor. It had just worn the two thermistor wires almost in two.  I didn't notice that before because about the only position that it would short out was at z home (would bend the wire harness just the right way I guess).  

That explains how I was able to get some smaller prints done that were done in the middle of the bed.  After a couple splices, I'm back in action.