Hi,
I'm seeing an interesting issue. When I connect to the printer via the machine config panel to print, things work fine the first time. However if I stop a print, or go back to the model window to make changes to the process, the extruder temperature will not respond. Instead it falls back to the off position. Disconnecting and reconnecting the software to the printer is required to get the extruder temp top respond again.
Has anyone else noticed this?
Re: Extruder temp problem with multiple prints
I used to see that all the time but havent had a issue since the new version. 1.0.7
I might suggest uninstall all version that you have and re-install with the new version.
Just in case there is something lingering from a previous version.
I might suggest uninstall all version that you have and re-install with the new version.
Just in case there is something lingering from a previous version.
Re: Extruder temp problem with multiple prints
I'm runninf 1.07, but I do still have 1.05 and 6 on the drive. I'll do a wipe and a fresh install and see if that fixes the problem.
Thanks!
GB
Thanks!
GB
Re: Extruder temp problem with multiple prints
I am seeing this exact same problem on my M2.
I find in creator, doing multiple emergency stops, I can get it to heat again.
or by power cycling the bot.
Thing is, I have also had this happen using printrun.
I did start with version 1.0.6 of creator, and moved to 1.0.7 ... and haven't installed 1.0.10
I can not say if it has stopped or not with 1.0.7 but I did have problems repeating the issue for josh at makergear... so maybe it has something to do with it.
I've made rick and josh at maker gear aware of this and josh has worked with me quite a bit on it, and although I questioned what seemed to be odd behaviors on heat up with some overshoot and undershoot on the initial heat up, rick assured me that's normal and within tolerances, , so far the bot itself has received a clean bill of health, and otherwise prints fine.
The only advice I have been given so far is to not use the temperature controls in gcode, and set the temperature manually. I've not had the chance to test that solution in depth.
Curiously enough, at least with my bot, if you try an PID autotune of the PID that fails ( issue the m303 command ) this might be a different problem or no problem at all due to the fact auto tune was in beta at the version of firmware the m2 comes with.
First prints seem to always work, second prints if I stop and make changes is where I usually see the problem.
and I find it under the same circumstances usually. I stop the print to make some change then I cant get it to heat on restart.
even doing them manually.
now... having said that... I did notice there is a difference in behavior at times.
on the first print. the head and the bed heats at the same time.
I've noticed that sometimes on subsequent heat ups, the bed must get up to temperature first, before the head will heat.
now, I haven't had the time to do any significant prints since my last chat with josh and rick, but thought id impart what I know now and see if we can come up with more details that might assist.
I'll hopefully be doing some significant printing this coming weekend. and can speak more on weather 1.0.7 and 1.0.10 is more stable with this issue and can re try using slc3r/printrun in a bit more of a controlled way.
it could very well be that I was using slic3r/printrun after creator, and just seeing problems started by the 1.0.6 version of creator.
I find in creator, doing multiple emergency stops, I can get it to heat again.
or by power cycling the bot.
Thing is, I have also had this happen using printrun.
I did start with version 1.0.6 of creator, and moved to 1.0.7 ... and haven't installed 1.0.10
I can not say if it has stopped or not with 1.0.7 but I did have problems repeating the issue for josh at makergear... so maybe it has something to do with it.
I've made rick and josh at maker gear aware of this and josh has worked with me quite a bit on it, and although I questioned what seemed to be odd behaviors on heat up with some overshoot and undershoot on the initial heat up, rick assured me that's normal and within tolerances, , so far the bot itself has received a clean bill of health, and otherwise prints fine.
The only advice I have been given so far is to not use the temperature controls in gcode, and set the temperature manually. I've not had the chance to test that solution in depth.
Curiously enough, at least with my bot, if you try an PID autotune of the PID that fails ( issue the m303 command ) this might be a different problem or no problem at all due to the fact auto tune was in beta at the version of firmware the m2 comes with.
First prints seem to always work, second prints if I stop and make changes is where I usually see the problem.
and I find it under the same circumstances usually. I stop the print to make some change then I cant get it to heat on restart.
even doing them manually.
now... having said that... I did notice there is a difference in behavior at times.
on the first print. the head and the bed heats at the same time.
I've noticed that sometimes on subsequent heat ups, the bed must get up to temperature first, before the head will heat.
now, I haven't had the time to do any significant prints since my last chat with josh and rick, but thought id impart what I know now and see if we can come up with more details that might assist.
I'll hopefully be doing some significant printing this coming weekend. and can speak more on weather 1.0.7 and 1.0.10 is more stable with this issue and can re try using slc3r/printrun in a bit more of a controlled way.
it could very well be that I was using slic3r/printrun after creator, and just seeing problems started by the 1.0.6 version of creator.
-
Simplify3D
- Site Admin
- Posts: 310
- Joined: Sun Feb 10, 2013 8:28 pm
Re: Extruder temp problem with multiple prints
Are you guys printing from SD or from USB? And when it isn't responding to setting temperatures, is that from a manual command or by running another G-Code file that has M104/M140 commands inside it?
This sounds like it might be a firmware problem since the process of setting the temperature is fairly straightforward (i.e. just send "M104 S180"). But the PID code on the microcontroller is fairly complex. Can anyone confirm if this happens with the latest Marlin release?
This sounds like it might be a firmware problem since the process of setting the temperature is fairly straightforward (i.e. just send "M104 S180"). But the PID code on the microcontroller is fairly complex. Can anyone confirm if this happens with the latest Marlin release?
Re: Extruder temp problem with multiple prints
My prints are all from USB lately.
I notice the problem whenever I complete a print, and want to print a new item (or another copy). It doesn't seem to matter whether I issue the command manually by typing it in, using the set temp controls from the config panel, or g-code embedded command.
I notice the problem whenever I complete a print, and want to print a new item (or another copy). It doesn't seem to matter whether I issue the command manually by typing it in, using the set temp controls from the config panel, or g-code embedded command.
Re: Extruder temp problem with multiple prints
this happens to me when printing from usb I do not print from sd
I've never noticed it happening on the first print.
it seems to happen when I abort the print, make a change then go back to print.
I do notice the temperatures are reporting, as usually I see the temperatures still dropping.
at that point, if I stop the print and then try to set the temperatures manually from the command gui, they either also don't set, or maybe one of the two bed or hotend will set but not the other.
usually I can get it to work if I do multiple emergency stops, or power cycle the bot
I've never noticed it happening on the first print.
it seems to happen when I abort the print, make a change then go back to print.
I do notice the temperatures are reporting, as usually I see the temperatures still dropping.
at that point, if I stop the print and then try to set the temperatures manually from the command gui, they either also don't set, or maybe one of the two bed or hotend will set but not the other.
usually I can get it to work if I do multiple emergency stops, or power cycle the bot
