You are not logged in. Please login or register.
SoliForum - 3D Printing Community → Help/Repair/Maintenance → Help - Printer stops extruding about an hour into print
That looks right did you have the boot pins jumped?
Wardjr, I am such a jackass, I unzipped that folder straight to the desktop and didn't place the executable in the new folder I created. I just saw it floating there popped it in the boot folder and all is well!! Sorry about that. I need some shut eye!
Thanks for all your help!! Although I didn't see the welcome message when I connected, I did turn my hotend temp up 250C and my SD3 didn't crash! So that is something completely new to me. Again, thanks for walking me through that.
I have seen that before but it's been a while and it's late. I'll be around all tomorrow so let's pick this up then.
Okay, I've had a good 8 hours rest. So here is what is happening. Like I mentioned, last night after the update I cranked the temp to 300C and my heater cartridge started to smoke and bubble a bit (I ordered a new one as well as a new thermister just in case).
I didn't see a welcome message like what was mentioned in your instructions but maybe I am looking in the wrong place for that. I do believe the firmware change took because normally my machine would crash if I tried to take it anywhere over 230C and it kept working at 300C.
This is what is happening today. I'll slice my code and start a print. Once it gets up to temp and would normally start, I get a pause notification saying that my printer has requested a pause and I have to hit the "continue printing button".
Everything prints fine until about the second layer when my hotend temperature drops off and becomes unresponsive. Here is a picture of the temp chart for your consideration: http://imgur.com/0A90mTY
The firmware did not take hold I am sure if you scrolled the error log just before you get the cold extrusion prevented you will have a max temp error. set your temp to 210 and it will not reach the 220 max temp. I have no idea how it managed to reach 300 unless there was a glitch that froze the system long enough to reach that temp. The power is cut to both the extruder and I assume that is the bed chart below it at the same time so this is the firmware shutting stuff off.
As far as the error you were getting for flashing the firmware if I remember correctly that is caused by a folder stored in the wrong location type of thing.
Suggestions:
1. upgrade R-H to V0.95F it is the last stable update that has pretty much the same interface as you are used to.
2. Try arduino 022 and see if that doesn't help things with the flash.
The firmware did not take hold I am sure if you scrolled the error log just before you get the cold extrusion prevented you will have a max temp error. set your temp to 210 and it will not reach the 220 max temp. I have no idea how it managed to reach 300 unless there was a glitch that froze the system long enough to reach that temp. The power is cut to both the extruder and I assume that is the bed chart below it at the same time so this is the firmware shutting stuff off.
As far as the error you were getting for flashing the firmware if I remember correctly that is caused by a folder stored in the wrong location type of thing.Suggestions:
1. upgrade R-H to V0.95F it is the last stable update that has pretty much the same interface as you are used to.
2. Try arduino 022 and see if that doesn't help things with the flash.
Okay, I will try to flash to .95F, although I had that one set up for a RoStock Max so I'm not sure if that will create any problems. I already am not able to connect to the SD3 through .95F though.
Okay, The newer version of Arduino doesn't let me open the configuration file and the older version of Arduino won't work with Teensy. I'm pretty well stuck at the moment.
You just need to move those hardware folders to the other version
You just need to move those hardware folders to the other version
I don't understand what you mean. Could you explain how to do that?
Also, as well as not knowing how to do that. My welcome message says I am running Marlin V1, and the website points to mendel-parts, and not solidoodle nor github. I'm not sure what it said in the first place I just want to check and make sure whether or not the firmware updated with you before I try moving things around again.
Also, I am attaching this picture to verify with you that I am in fact reaching temps of 300C. http://imgur.com/VnjZkiX
..and here is a picture of my recent crash with the log. This is starting to suck because I had this running pretty decent last night after I changed my extrusion steps. This firmware update is disheartening. http://imgur.com/uHA8VDN
I totally believe you reached the temps you stated. What I don't understand is since it looks like your firmware change must have taken (or you'd never reach those temps) what is telling the extruder output to drop to zero? I just don't think that is a firmware issue. Did you scroll that log at all to see if it showed an error?
More over if you just turn it on at say 220 and let it sit will it hold temp?
I totally believe you reached the temps you stated. What I don't understand is since it looks like your firmware change must have taken (or you'd never reach those temps) what is telling the extruder output to drop to zero? I just don't think that is a firmware issue. Did you scroll that log at all to see if it showed an error?
More over if you just turn it on at say 220 and let it sit will it hold temp?
I ran the CMD booting process again last night and got the text mentioned in your instructions "yada yada booting..." But again the welcome message was still the same as I posted above.. so I can't be 100% certain it took. The only reason I believe it did is because the temp shouldn't normally reach that level.
I browsed over the log and didn't see anything that stuck out. I had let the 300C temp sustain as I thought that would consume the most power and it let sit for about 5-10 minutes and it didn't shut itself off. I'll let it sit at 220 for 15 minutes and then try to run another print after that. Maybe I can post the complete log after the extruder shuts itself off.
I have a feeling something is happening with my g-code output, because as I mentioned, my printer is also forcing a pause right at the beginning of each print.
I'll post both the error log and g-code after I have done some testing. Again, thanks for your help wardjr, I really appreciate you taking the time to help with this.
I am thinking broken wire or connection somewhere. That pause at the beginning can be changed by changing your custom g-code that will look something like this
Feel free to copy that if yours is different.
I can't think of anything in the G-code that would shut off the heaters mid print. That is why I am thinking loose or bad connection. If when you go to print you end up with a fault try and capture the error code as that will tell us if it is an open circuit or a short somewhere.
Okay, I was able to sustain heat. I let it run at 220C for about 30 minutes with no issues.
I then started my print. The pause I am getting at the beginning of each print is like someone literally hit the pause button. It pops up like I hit the pause button, but I didn't do it, the machine is doing it on it's own. I then have to click continue print.
At the start of my print I get a low filament warning: http://imgur.com/Q0HYg92
When my extruder shuts off this is what I get: http://imgur.com/NX2LTol
Do you want me to post some of my G-code? I think posting the whole thing might be a little excessive, so if so just let me know how much.
M code 104 sets the temp to 0.
I am guessing that happens right after the filament alarm. You don't have a filament alarm so you need to find that in the configuration.h file and comment that out.
That is something that either got changed in the last update or you accidentally deleted the comment // slashes.
Either way it's an easy fix but you'll have to re-flash the firmware. The good news is you'll get some practice with flashing. Next user will thank you 
M code 104 sets the temp to 0.
I am guessing that happens right after the filament alarm. You don't have a filament alarm so you need to find that in the configuration.h file and comment that out.
That is something that either got changed in the last update or you accidentally deleted the comment // slashes.
Either way it's an easy fix but you'll have to re-flash the firmware. The good news is you'll get some practice with flashing. Next user will thank you
Right? A few more of these flashes and I'll be an expert. Problem is that I am unable to open that configuration in the new version of Arduino and teensyduino won't work with Arduino 022, so I'll be installing versions of Arduino until I find one that works. Hopefully this will fix it, I'll keep you updated.
You just need to pull the hardware folder into the main folder of the version you are using. It's just a drag and drop thing in windows explore. Not any different than saving and moving files normally.
The other thing is you can open the Config file from any location so it really doesn't matter.
Are you opening a marlin.pde or Marlin.ino?
The other thing is you can open the Config file from any location so it really doesn't matter.
Are you opening a marlin.pde or Marlin.ino?
Maybe I am doing this part wrong. I was trying to open the configuration.h file in arduino to edit it, then I was going to save it and move the .hex file into the bootloader folder and open DOS to run the bootloader.
wardjr wrote:The other thing is you can open the Config file from any location so it really doesn't matter.
Are you opening a marlin.pde or Marlin.ino?Maybe I am doing this part wrong. I was trying to open the configuration.h file in arduino to edit it, then I was going to save it and move the .hex file into the bootloader folder and open DOS to run the bootloader.
Your doing it right but by this point you most likely have more than one Marlin folder. You want to be opening the .ino file from the Marlin V1 beta folder (something like that). Then navigate to the configuration.h tab. Make your changes verify and save then work through the flash process.
I will have some time later to send you a link to the firmware. Maybe you just grabbed the wrong one. If you have a link post it and I can verify.
Just want to confirm what to delete out of here. I'm assuming that I just want to delete out the whole paragraph dealing with the filament alarm and nothing else. This is the appropriate text I found in the configuration.h file:
// Filament Alarm Pin (+684 Bytes)
// Must ensure PARK_HEAD_ENABLE is defined below as well!
//#define FILAMENT_ALARM_PIN 63 //RAMPS Pin for Microswitch on Filament Feed. D63 on AUX2 with a GND next to it.
#define FILAMENT_ALARM_PIN 4 //Sang Pin for Microswitch on Filament Feed. A4 pin, with a GND Next to it.
#define PAUSE_HEATER_DELAY 300 //Delay until heater disabled when paused in seconds
// Enable support for head parking/print pausing/filament changeover support (M600 + M601) (+2780 Bytes)
// REQUIRED FOR FILAMENT_ALARM!
#define PARK_HEAD_ENABLE
#include "Configuration_adv.h"
#include "thermistortables.h"
#endif //__CONFIGURATION
This is the version I downloaded: https://github.com/ozadr1an/Solidoodle- … guration.h I now see a newer version that was last edited 5 hours ago. I'm going to download that one and give it a go.
Nevermind, can you send me that link for the correct version? The one I found was for something else.
SoliForum - 3D Printing Community → Help/Repair/Maintenance → Help - Printer stops extruding about an hour into print
Powered by PunBB, supported by Informer Technologies, Inc.
