Can´t print with extruder 2.
-
OK This is how it looks to me. In your config.g you have two tools, P0 and P1 and the operating and standby temperatures are set to 0 deg C for both tools (G10 P0 S0 R0 and the same for P1). That's fine because you don't want the tool to start heating as soon as you turn the machine on. Now in the start gcode you heat tool 1 (M109 S210 T1) but not tool 0. So when you switch to tool 0, it'll wait until it reaches 0 degC because that is what the operating (active) temperature is set to in your config.g and there isn't another command to override it.
So, what you need to do set the operating and standby temperatures for both tools in you start gcode. You could set them both the same i.e G10 P0 S210 R210 and G10 P1 S210 R210. If you do that, then when you change tools it will continue to print with no delay. However, you may find that you get filament oozing form the tool that isn't in use. So what most people do is set the standby temperature lower to (say 170) or whatever temperature you can use with no oozing. Then when you change tools, there will be a delay while the new tool heats up from standby (170) to active (210) then it will continue to print.
Finally, you should add G10 P0 S-273 R-273 (or just 0) and G10 P1 S-273 R-273 to your end gcode to reset the active and standby temperatures at the end of the print.
HTH
Ian
-
Just one more thing. I'm assuming you gcode file switches between T1 and T0. Not T1 and T2 because you haven't got a T2. By default the first tool in firmware is T0, the second T1, etc but many slicers use T1 for the first tool and T2 for the second. You change the behaviour of the firmware by using M563 S1 which effectively add 1 to every tool number. Then you can use T1 and T2 in you gode files but otherwise you need to use T0 and T1.
-
Tried this and it didn´t work.
And since I thought that I had something wrong in my toolchanging files I deleted these and just using extruder 2 (T1) at the moment, I have no T0 (Extruder 1) command anywhere right now just T1(even changed the last row in config to T1)
And still the same problem. -
OK so it looks like it isn't to do with tool changes. As I understand it from your first post, the tool heats OK, it starts to print and then it freezes and the web display shows the print progress as 100%, as if the print has finished. This only happens with T1 and never with T0, is that correct?
-
OK so it looks like it isn't to do with tool changes. As I understand it from your first post, the tool heats OK, it starts to print and then it freezes and the web display shows the print progress as 100%, as if the print has finished. This only happens with T1 and never with T0, is that correct?
Yes that's correct, never happens with T0, have had many successed prints when only using T0. I'm now trying with exactly the same g code, just changed T0 to T1 and the problem occurred
-
Is it possible there is a T0 command somewhere later in the Gcode?
Also does it freeze at eactly the same point each time?
-
Is it possible there is a T0 command somewhere later in the Gcode?
Also does it freeze at eactly the same point each time?
searched the whole code no T0, freezes at the same point every time, freezes on a normal G1 movement.
-
It could indicate a short in the extruder 1 or heater 2 wiring. Does heater 2 show a stable temperature?
When the print freezes, do the axes show as no longer homed in DWC? This would indicate that the Duet is resetting. If so, run M122 to see the last reset time and reason.
-
And yet if you run the same G-code with the initial T1 replaced with T0 it works fine?
Can you replicate this working with T0, not working with T1 on a different gcode file?
-
Is there anything other than a reset that could cause the print progress to go to 100%? If not, then I guess it has to be wiring issue on T1 that is triggering the reset, so a short or some such?
-
It could indicate a short in the extruder 1 or heater 2 wiring. Does heater 2 show a stable temperature?
When the print freezes, do the axes show as no longer homed in DWC? This would indicate that the Duet is resetting. If so, run M122 to see the last reset time and reason.
Heater 2 is showing a stable temperature.
When freezing the whole webinterface freezes, can´t do anything (and all axis show homed)Just tried an other g code with the same problem, working with T0 but not with T1, this time it freezes by the first layer doing the first G1.
The privious file froze at layer 4 -
(with the board powered down)
try swapping T0 and T1 and see if the fault moves or stays the same.
-
Is there anything other than a reset that could cause the print progress to go to 100%? If not, then I guess it has to be wiring issue on T1 that is triggering the reset, so a short or some such?
If there is a short this must be on the board, since I have tried switching the heaters/thermistors on the board.
Both heaters works as T0 but not T1 -
Tried to run one of the g codes that crashed earlier once more, this time manually line by line in the web interface and surprisingly it didn´t crash.
How can it be that everything freezes when I run the code in auto and not when I run it manually row by row? -
The buffer for the gcode may have a glitch,
-
Now it actually happened with T0 as well (for the first time), crashed with five layers remaining at a five-hour spiral vase print.
I'm going nuts, what can cause these crashes?
As I´ve said before, it happens every time with T1 but almost never with T0 (this was the first).
I can´t see anything wrong in the config or g codes (but I´m no expert needs to be said).
And I don´t think that it´s a wiring issue since the problem follows that extruder that is connected as T1 on the board.
Anyone else that experience mid-print faults, that might have a solution to my problem?
Could it be something wrong with my board? -
Now it actually happened with T0 as well (for the first time), crashed with five layers remaining at a five-hour spiral vase print.
I'm going nuts, what can cause these crashes?
As I´ve said before, it happens every time with T1 but almost never with T0 (this was the first).
I can´t see anything wrong in the config or g codes (but I´m no expert needs to be said).
And I don´t think that it´s a wiring issue since the problem follows that extruder that is connected as T1 on the board.
Anyone else that experience mid-print faults, that might have a solution to my problem?
Could it be something wrong with my board?Please explain what you mean by "crashes". Does the board reset? Run M122 to find out. If the "Last reset time" corresponds to when the print stopped unexpectedly, instead of before you started the print, tell us what it shows for "Last reset reason" and "Last software reset code".
-
Now it actually happened with T0 as well (for the first time), crashed with five layers remaining at a five-hour spiral vase print.
I'm going nuts, what can cause these crashes?
As I´ve said before, it happens every time with T1 but almost never with T0 (this was the first).
I can´t see anything wrong in the config or g codes (but I´m no expert needs to be said).
And I don´t think that it´s a wiring issue since the problem follows that extruder that is connected as T1 on the board.
Anyone else that experience mid-print faults, that might have a solution to my problem?
Could it be something wrong with my board?Please explain what you mean by "crashes". Does the board reset? Run M122 to find out. If the "Last reset time" corresponds to when the print stopped unexpectedly, instead of before you started the print, tell us what it shows for "Last reset reason" and "Last software reset code".
With crashes I mean that everything freezes, web interface showes 100% progress and then everything freezes.
I have noted that if I wait a couple of seconds then I´m able to disconnect and then reconnect and when I run M122 these are the resets codes:
Last reset 00:00:11 ago, cause: software
Last software reset code: 0x5004, available RAM 24636 bytes (slot 0) -
The software reset code info at https://duet3d.com/wiki/Error_codes_and_software_reset_codes indicates that a software reset occurred because the firmware was trying to write debug info or other essential info to the USB port, but writing was b!Locked because the port wasn't connected or the program at the other end had stopped reading data from it.. This should only occur if you enable debug output using the M111 S1 command.
Assuming you do not have the USB port connected, I suggest you connect it to a PC, load Pronterface or another USB host program, and connect to the printer. Then do something that normally provokes the problem and see what messages appear on the PC.
-
The software reset code info at https://duet3d.com/wiki/Error_codes_and_software_reset_codes indicates that a software reset occurred because the firmware was trying to write debug info or other essential info to the USB port, but writing was b!Locked because the port wasn't connected or the program at the other end had stopped reading data from it.. This should only occur if you enable debug output using the M111 S1 command.
Assuming you do not have the USB port connected, I suggest you connect it to a PC, load Pronterface or another USB host program, and connect to the printer. Then do something that normally provokes the problem and see what messages appear on the PC.
Pronterface messages this:
[ERROR] Can't read from printer (disconnected?) (SerialException): call to ClearCommError failed
Exception in thread Thread-20:
Traceback (most recent call last):
File "threading.pyc", line 808, in __bootstrap_inner
File "threading.pyc", line 761, in run
File "printrun\printcore.pyc", line 357, in _sender
File "printrun\printcore.pyc", line 623, in _send
File "encodings\utf_8.pyc", line 16, in decode
UnicodeDecodeError: 'utf8' codec can't decode byte 0xe4 in position 38: invalid continuation byte
