Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Initial print cancelled

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    2
    6
    307
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • dvdrielundefined
      dvdriel
      last edited by

      Hi all,

      I just converted a tripodmaker to a Duet3D powered machine. Everything went well so far and I am loving the platform, however I can't manage to get my first print going ;).

      Everytime I try to start my first test print I'm getting this message: 8d223877-1bd8-4a82-b364-9cce4f19009a-image.png

      I don't really understand the order in which the Duet board executes all files.

      What I am trying to do:

      1. start heating up the bed and nozzle
      2. home
      3. auto calibrate
      4. start print

      I added a start.g file which contains:
      G28
      G32

      In my config.g I added M564 H0 in the end.

      What am I doing wrong?

      Thanks in advance

      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        It would really help if you posted your config.g, homeall.g, bed.g and the file you're trying to print. Also include what duet you have, what kind of printer it is, what firmware version you're using.

        Have you tested your homeall.g (G28) and bed.g (G32) separately?

        Using M564 H0 and having something misconfigured in your homing or calibration files could place the head somewhere where it shouldn't actually be. Or perhaps you have a move that is physically impossible. At least that's what the error message is saying.

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • dvdrielundefined
          dvdriel
          last edited by

          Thank you for the response!

          Here is the info:

          Printer: tripodmaker (delta)
          Board: Duet 2 WiFi (2WiFi)
          Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.1.1 (2020-05-19b2)

          I have first configured everything separately. All hardware is working correctly and G28 and G32 are executed properly when used individually.


          config.g:

          Network
          M552 S1 ; enable network
          M586 P0 S1 ; enable HTTP
          M586 P1 S1 ; enable FTP
          M586 P2 S0 ; disable Telnet

          ; Drives
          M569 P0 S0 ; physical drive 0 goes forwards
          M569 P1 S0 ; physical drive 1 goes forwards
          M569 P2 S0 ; physical drive 2 goes forwards
          M569 P3 S0 ; physical drive 3 goes forwards
          M584 X0 Y1 Z2 E3 ; set drive mapping
          M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
          M92 X133.33 Y133.33 Z133.33 E400.49 ; set steps per mm
          M566 X1200.00 Y1200.00 Z1200.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
          M203 X18000.00 Y18000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
          M201 X1000.00 Y1000.00 Z1000.00 E1000.00 ; set accelerations (mm/s^2)
          M906 X1400 Y1400 Z1400 E1400 I10 ; set motor currents (mA) and motor idle factor in per cent
          M84 S30 ; Set idle timeout

          ; Axis Limits
          M208 Z0 S1 ; set minimum Z

          ; Endstops
          M574 X2 S1 P"xstop" ; configure active-high endstop for high end on X via pin xstop
          M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop
          M574 Z2 S1 P"zstop" ; configure active-high endstop for high end on Z via pin zstop

          ; Z-Probe
          M558 P5 C"!zprobe.in" H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds
          G31 P500 X-7 Y-24 Z2.03 ; set Z probe trigger value, offset and trigger height
          M557 R85 S20 ; define mesh grid

          ; Heaters
          M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp
          M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
          M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
          M140 H0 ; map heated bed to heater 0
          M143 H0 S120 ; set temperature limit for heater 0 to 120C
          M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
          M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
          M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

          ; Fans
          M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
          M106 P0 C"BOTTOM" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off
          M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
          M106 P1 C"EXTRUDER" S1 H1 T45 ; set fan 1 name and value. Thermostatic control is turned on
          M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
          M106 P2 C"BED" S1 H-1 ; set fan 2 name and value. Thermostatic control is turned off

          ; Tools
          M563 S"Printhead 1" P0 D0 H1 F1; tool 0 uses extruder drive 0 and heater 1
          G10 P0 S0 R0 X0 Y0 ; set tool 0 temperatures and offsets

          ; Custom settings are not defined

          M501
          M564 H0



          config-override.g:

          M665 L355.000:355.000:355.000 R154.109 H353.453 B150.0 X1.986 Y-4.096 Z0.000
          M666 X-18.496 Y-17.246 Z35.742 A0.96 B26.36
          ; Heater model parameters
          M307 H0 A148.7 C1166.3 D8.1 S1.00 V24.0 B0
          M307 H1 A459.0 C176.5 D8.8 S1.00 V24.3 B0
          ; Workplace coordinates
          G10 L2 P1 X0.00 Y0.00 Z0.00
          G10 L2 P2 X0.00 Y0.00 Z0.00
          G10 L2 P3 X0.00 Y0.00 Z0.00
          G10 L2 P4 X0.00 Y0.00 Z0.00
          G10 L2 P5 X0.00 Y0.00 Z0.00
          G10 L2 P6 X0.00 Y0.00 Z0.00
          G10 L2 P7 X0.00 Y0.00 Z0.00
          G10 L2 P8 X0.00 Y0.00 Z0.00
          G10 L2 P9 X0.00 Y0.00 Z0.00



          homeadelta.g:

          G91 ; relative positioning
          G1 H1 X450 Y450 Z450 F1800 ; move all towers to the high end stopping at the endstops (first pass)
          G1 H2 X-5 Y-5 Z-5 F1800 ; go down a few mm
          G1 H1 X10 Y10 Z10 F180 ; move all towers up once more (second pass)
          G1 Z-5 F6000 ; move down a few mm so that the nozzle can be centred
          G90 ; absolute positioning
          G1 X0 Y0 F6000 ; move X+Y to the centre



          start.g
          G28
          G32



          test print g code:
          ;FLAVOR:Marlin
          ;TIME:13493
          ;Filament used: 12.4555m
          ;Layer height: 0.2
          ;MINX:-57.8
          ;MINY:-57.8
          ;MINZ:0.3
          ;MAXX:57.8
          ;MAXY:57.8
          ;MAXZ:99.9
          ;Generated with Cura_SteamEngine 4.6.1
          M140 S60
          M105
          M190 S60
          M104 S210
          M105
          M109 S210
          M82 ;absolute extrusion mode
          G28
          G92 E0
          G92 E0
          G1 F1500 E-6.5
          ;LAYER_COUNT:499
          ;LAYER:0
          M107
          G0 F3600 X57.8 Y29.908 Z0.3
          ;TYPE:SKIRT
          G1 F1500 E0
          G1 F900 X57.764 Y31.366 E0.07276
          G1 X57.637 Y32.996 E0.15433
          G1 X57.414 Y34.603 E0.23527


          Thanks in advance!

          1 Reply Last reply Reply Quote 0
          • Phaedruxundefined
            Phaedrux Moderator
            last edited by

            You forgot bed.g.

            So because you have start.g it will run that file first, which runs G28 (homedelta) and then G32 (bed.g), and then it carries on with the sliced gcode file, which also has a G28 in the slicer start gcode. Depending on what you have in your bed.g you probably don't want that second G28 in the slicer start gcode because you've already done it in start.g

            Until I see bed.g I can't really say more about what's going on.

            What does your printer actually do when you start the print? It seems like only 2 seconds pass between you hitting print and it saying it can't reach a physical position. Does it move at all? Does it home to the top?

            Also, do you have a zprobe? What is it? Do you ever call it in your bed.g to find the position of Z0?

            Z-Bot CoreXY Build | Thingiverse Profile

            1 Reply Last reply Reply Quote 0
            • dvdrielundefined
              dvdriel
              last edited by

              Thanks for the reply. I found the issue that made the print cancel, it was the last G1 command in my homedelta.g: G1X0 Y0. For some reason this is seen as a unreachable move. I took it out since the print head should be centered after homing anyway.

              I have a npn conductive Z- probe. What do you mean by using the z-probe to find z=0, that's what happens when I run G32 right? Doesn't it calculate the delta height using the given z-probe trigger distance?

              If you have time please have a look at my other topic about calibrating this delta machine, that's where I really got stuck.

              Phaedruxundefined 1 Reply Last reply Reply Quote 0
              • Phaedruxundefined
                Phaedrux Moderator @dvdriel
                last edited by

                @dvdriel said in Initial print cancelled:

                G1X0 Y0. For some reason this is seen as a unreachable move.

                Probably because it would require a carriage moving up past the end stop. Would probably need to lower all the towers a bit in the Z direction and then it would work.

                @dvdriel said in Initial print cancelled:

                that's what happens when I run G32 right?

                I'm not sure, I haven't seen your bed.g yet.

                Z-Bot CoreXY Build | Thingiverse Profile

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Unless otherwise noted, all forum content is licensed under CC-BY-SA