Can´t print with extruder 2.



  • I´m printing without any problems with extruder 1 but everything freezes when trying to print with extruder 2.
    The heater warms up as it should and starts printing but then everything freezes and print progress showen 100%.
    It happens at different points depending on which g.code I´m running, it always does the startup code with homing, warms up bed and extruder etc., but then it freezes when doing movements.

    Could there be something wrong with my DuetWifi board or is it in my codes?
    Have even switch places on my heaters/thermistors to rule out faulty components, they work as extruder 1 but not 2.
    My g-codes works with T0 but when changing to T1 this happens.

    Firmware Version: 1.17c (2017-01-14)
    Web Interface Version: HTML: 1.11, JS: 1.11a-dc42


  • administrators

    Have a look at what is in your tool change g-codes (tfree0.g etc)
    there could well be something in those that is causing an odd action.



  • I deleted all my tool change files since I thought these were the problem and I now manually activate T1 then ran my g code,
    doesn't help



  • It sounds to me a bit like a problem with the tool definitions and/or active/standby temperature settings. Can you post your config.g file and also your slicer start gcode commands (or the first part of a gcode file up to and including the first few moves).



  • G90
    M82
    M106 S0
    M140 S30
    M190 S30
    M104 S210 T1
    M109 S210 T1
    G28 ; home all axes
    G92 E0
    G1 E-1.0000 F1800
    G1 Z0.180 F1000
    ; layer 1, Z = 0.18
    T1
    ; tool H0.200 W0.400
    ; skirt
    G1 X135.491 Y138.003 F4800
    G1 E0.0000 F540
    G92 E0
    G1 X138.003 Y135.491 E0.1063 F1800
    G1 X138.224 Y135.400 E0.1135
    G1 X161.776 Y135.400 E0.8185
    G1 X161.997 Y135.491 E0.8256
    G1 X164.509 Y138.003 E0.9320

    M111 S0 ; Debug off
    M550 MHCoreXY ; Machine name and Netbios name (can be anything you like)
    M551 xxxxx ; Machine password (used for FTP)
    ;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits
    M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED ; MAC Address
    ;*** Wifi Networking
    M552 P0.0.0.0 S1 ; Enable WiFi

    M555 P1 ; Set output to look like RepRapfirmware
    ;M575 P1 B57600 S1 ; Comms parameters for PanelDue

    G21 ; Work in millimetres
    G90 ; Send absolute coordinates…
    M83 ; ...but relative extruder moves
    M667 S1 ; switch to CoreXY mode

    ; Axis and motor configuration
    M208 X0 Y0 Z0 S1 ; Set axis minima
    M208 X300 Y300 Z440 S0 ; Set axis maxima
    M569 P0 S1 ; Drive 0 goes forwards
    M569 P1 S0 ; Drive 1 goes forwards
    M569 P2 S0 ; Drive 2 goes forwards
    M569 P3 S1 ; Drive 3 goes forwards
    M569 P4 S1 ; Drive 4 goes forwards
    M574 X1 Y2 Z0 S0 ; set endstop configuration (all endstops at high end, active high)
    ;*** The homed height is deliberately set too high in the following - you will adjust it during calibration
    M350 X16 Y16 Z16 E16:16 I1 ; Set 16x microstepping with interpolation
    M92 X100 Y100 Z1600 ; Set axis steps/mm
    M906 X1200 Y1200 Z1200 E400:400 I30 ; Set motor currents (mA) and increase idle current to 60%
    M201 X1000 Y1000 Z100 E2000:2000 ; Accelerations (mm/s^2)
    M203 X6000 Y6000 Z800 E12000:12000 ; Maximum speeds (mm/min)
    M566 X600 Y600 Z60 E2400:E2400 ; Maximum instant speed changes mm/minute
    M84 S30

    ; Thermistors heaters
    M143 S260 ; Set maximum heater temperature to 280C
    M305 P0 T100000 B4138 C0.0000000000000000 R4700 L0 H0 ; Set thermistor + ADC parameters for heater 0
    M305 P1 T100000 B4388 C0.0000000000000000 R4700 L0 H0 ; Set thermistor + ADC parameters for heater 1
    M305 P2 T100000 B4388 C0.0000000000000000 R4700 L0 H0 ; Set thermistor + ADC parameters for heater 2
    M570 S180 ; Hot end may be a little slow to heat up so allow it 180 seconds
    M570 H1 P10 T15
    M570 H2 P10 T15
    M307 H1 A295.5 C122.8 D9.4 B0
    M307 H2 A295.5 C122.8 D9.4 B0

    ; Tool definitions
    M563 P0 D0 H1 ; Define tool 0
    G10 P0 X0 Y0 ; Set tool 0 axis offsets
    G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures
    ;*** If you have a single-nozzle build, comment the next 2 lines
    M563 P1 D1 H2 ; Define tool 1
    G10 P1 X18 Y0 ; Set tool 1 axis offsets
    G10 P1 S0 R0 ; Set tool 1 operating and standby temperatures
    M92 E154:154 ; Set extruder steps per mm

    ; Z probe and compensation definition
    ;*** If you have a switch instead of an IR probe, change P1 to P4 in the following M558 command
    M558 P1 X0 Y0 Z0 H3 F300 T12000 ; Z probe is an IR probe and is not used for homing any axes
    G31 X0 Y0 Z1.39 P500 ; Set the zprobe height and threshold (put your own values here)

    ;*** If you are using axis compensation, put the figures in the following command
    M556 S78 X0 Y0 Z0 ; Axis compensation here

    T0 ; select first hot end



  • 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?



  • @deckingman:

    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


  • administrators

    Is it possible there is a T0 command somewhere later in the Gcode?

    Also does it freeze at eactly the same point each time?



  • @T3P3Tony:

    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.


  • administrators

    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.


  • administrators

    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?



  • @dc42:

    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


  • administrators

    (with the board powered down)

    try swapping T0 and T1 and see if the fault moves or stays the same.



  • @deckingman:

    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,


Locked
 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.