The temperatures for your prints can be controlled in the Slice Settings> Filament> Temperature.
This can be adjusted for each filament profile you are using which should automatically switch to X temp.
It hot end worked fine the first 500 hours and then stopped heating to the set point temperature. Nothing changed. Maybe the heating resistors need to be replaced.
Yup, that M107 must be it. It's the only difference between the two codes. Even if I put it at the very end of the start code it changes everything. No bed heating, slow homing...So, a little clarification, at the risk of making myself look stupid. The info I had about the M190, M104, M109 codes was coming from the RepRap wiki g-code page. My memory told me it was 3D printer g-code in general. I guess there are still inconsistencies between the 3D printer manufacturers. In fact, the M107 fan off command is deprecated in RepRap; maybe that's the problem. I believe the FlashForge control is based on RepRap.For now I am going to have to translate all my files through Replicatorg to clean out the M107, unless there is another way to get it out of there.Unless, of course, I am still doing something wrong...Still, nice piece of software! I've tried a few so far and this is my favorite.
Sounds like you need to run PID tuning. Here is a guide on how to do that.http://matterhackers.dozuki.com/Guide/PID+Tuning/6Here is also a general article on diagnosing temperature related issues.http://matterhackers.helpscoutdocs.com/article/53-printer-has-trouble-holding-temperature
@alc112 said:
If I open a gcode file in matter control with the feature turned on, will it aply the bed levelling to th gcode ifI export it and leave all the settings intact?Yes.@alc112 said:
When the machine is workingI see that Z vaues change constantly due to autolevel... will that be a problem when modifying the gcode? or how should I do that?
No, modifying the G-Code will not be a problem. Think of the auto-leveling process as a filter that the G-Code runs through on its way to the printer.
MatterControl does not handle warming up the same way as the other programs. Most programs will send an M190 S60 command to the printer, which tells it to stop and wait until the bed heats up to 60 C. The problem with this is that the printer will not listen to any more commands until the bed is finished heating. This means that, for instance, you cannot cancel your print without rebooting the printer.
To get around this, MatterControl intercepts all M190 commands and turns them into M140 commands. This tells the printer to start heating up, but not to wait. Then it checks the temperature periodically using M105 and once it is hot enough, it continues printing. Since your printer is not answering the M105, MatterControl never knows that it has heated up and does not continue printing.
It seems to me that this is a bug in your printers firmware that has only been revealed due to MatterControl's unusual behavior. It looks like the trouble starts with the G4 command, which tells the printer to pause for a brief moment. Can you try the following test so we can determine exactly what the printer is doing?
Open a terminal window and uncheck Filter Output. You should see MatterControl periodically sending M105 to the printer, asking for its temperatures. Type in G4 P1000 and see what happens. The printer should pause for exactly one second and then continue answering the M105s. If it stops answering them altogether, we know we have a problem. After rebooting the machine, please try the same test again with G4 S1.
Looks like your connection to MatterHackers Community was lost, please wait while we try to reconnect.
