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

    Mini5 to 1LC to smart effector wiring and control

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    4
    38
    1.4k
    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.
    • opentoideasundefined
      opentoideas @dc42
      last edited by

      @dc42 @jay_s_uk so I have added a M500 to the end of bed.g

      my thinking is that now having homed and levelled the settings are now stored and a home all command will now accurately home based on the probed height?

      just running a final mesh with everything hot to see if there is much variation from cold and soon printing again

      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @opentoideas
        last edited by

        @opentoideas heres my bed routine

        ; Auto calibration routine for large delta printer
        M561                    ; clear any bed transform
        M190 S60
        M568 P0 S200
        M116 P0
        if heat.heaters[1].current > 175
        ; If the printer hasn't been homed, home it
           if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
              G28
        ; Probe the bed and do auto calibration
           G1 X0 Y0 Z5
           G30
           G1 X0 Y80 Z10 F10000        ; go to just above the first probe point
           while true
              if iterations = 5
                 abort "too many auto calibration attempts"
              G30 P0 X0.00 Y80.00 Z-99999
              if result != 0
                 continue
              G30 P1 X51.42 Y61.28 Z-99999
              if result != 0
                 continue
              G30 P2 X78.78 Y13.89 Z-99999
              if result != 0
                 continue
              G30 P3 X69.28 Y-40.00 Z-99999
              if result != 0
                 continue
              G30 P4 X27.36 Y-75.18 Z-99999
              if result != 0
                 continue
              G30 P5 X-27.36 Y-75.18 Z-99999
              if result != 0
                 continue
              G30 P6 X-69.28 Y-40.00 Z-99999
              if result != 0
                 continue
              G30 P7 X-78.78 Y13.89 Z-99999
              if result != 0
                 continue
              G30 P8 X-51.42 Y61.28 Z-99999
              if result != 0
                 continue
              G30 P9 X0.00 Y40.00 Z-99999
              if result != 0
                 continue
              G30 P10 X34.64 Y20.00 Z-99999
              if result != 0
                 continue
              G30 P11 X34.64 Y-20.00 Z-99999
              if result != 0
                 continue
              G30 P12 X0.00 Y-40.00 Z-99999
              if result != 0
                 continue
              G30 P13 X-34.64 Y-20.00 Z-99999
              if result != 0
                 continue
              G30 P14 X-34.64 Y20.00 Z-99999
              if result != 0
                 continue
              G30 P15 X0 Y0 Z-99999 S6
              if result != 0
                 continue
              if move.calibration.final.deviation <= 0.02
                 break
              echo "Repeating calibration because deviation is too high (" ^ move.calibration.final.deviation ^ "mm)"
        ; end loop
           echo "Auto calibration successful, deviation", move.calibration.final.deviation ^ "mm"
           G1 X0 Y0 Z5 F10000                ; get the head out of the way
           G30
           G1 X0 Y0 Z25
        

        i heat it up, run a G30, G32 and then G30 again.
        Then the heightmap can be loaded and the print started

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        opentoideasundefined 1 Reply Last reply Reply Quote 0
        • opentoideasundefined
          opentoideas @jay_s_uk
          last edited by opentoideas

          @jay_s_uk interesting. Gave it a go and had to increace the tollerance to 0.03 as my average was 0.025 to 0.032

          spoke too soon..... now holding closer to 0.1

          I suspect that this is telling me I need to improve the mechanical accuracy of the machine and unless the tramming of the legs has been bumped out I suspect that my printed adapter for the arms is the most likely culprit.

          • arm spacing looks bad so tomorrow will try to sort that out with shims as they are all under.

          This will be solved soon once the linear rails arrive and I can swap to the magball mounts on the smart effector but its something to fettle while I wait

          jay_s_ukundefined 1 Reply Last reply Reply Quote 1
          • jay_s_ukundefined
            jay_s_uk @opentoideas
            last edited by

            @opentoideas yea, 0.1 is pretty poor.
            Magballs and the smart effector PCB carriages should solve some of that. Hopefully there's no other slop in the system

            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

            opentoideasundefined 1 Reply Last reply Reply Quote 0
            • opentoideasundefined
              opentoideas @jay_s_uk
              last edited by

              @jay_s_uk before the change I was pretty consistent at about 0.014

              It seems likely the printed caraige adapter is the culpret so I will start with getting the arms parallel hopefully that removes a good chunk of the error

              opentoideasundefined 1 Reply Last reply Reply Quote 1
              • opentoideasundefined
                opentoideas @opentoideas
                last edited by opentoideas

                Well I was wrong. while the arm spacing was out they were within 0.5mm of each other but what I did discover was that one of my arms had a very sloppy ball joint.

                it must have been one of the 2 spares that I had and got swapped in by mistake when I swapped things around.

                changed it and back to a deviation of 0.014 on the first run

                1 Reply Last reply Reply Quote 1
                • opentoideasundefined
                  opentoideas
                  last edited by opentoideas

                  @dc42 I am having a problem with my fans when printing

                  ; Fans
                  M950 F0 C"20.out1" Q500                               ; create fan0 on pin 20.out1 and set its frequency part cooling
                  M106 P0 S1 H-1                                        ; set fan0 value. Thermostatic control is turned off 
                  M950 F1 C"20.out2" Q500                               ; create fan 1 on pin 20.out2 and set its frequency hotend
                  M106 P1 S1 H1 T45                                     ; set fan1 value. Thermostatic control is turned on 
                  M950 F2 C"out5" Q500                                  ; create fan 2 on pin out5 and set its frequency Duet cooling
                  M106 P2 S1 H-1                                        ; set fan 2 value. Thermostatic control is turned off
                  M950 F3 C"out6" Q500                                  ; create fan 3 on pin out6 and set its frequency PSU cooling
                  M106 P3 S1 H2 T30                                     ; set fan 3 value. Thermostatic control is turned on
                  

                  this is as per the documentation with part cooling on out1 and hotend on out2 on the 1lC

                  when I print the hotend fan gets shutdown which I believe relates to the slicer using the deprecated M107. I found a thread suggesting part cooling set to fan0 and hotend to fan1 and so I swapped them above but still get the same result with the hotend fan shutting off at start of print.

                  is this a quirk of the 1lC or have I made a daft error?

                  jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                  • jay_s_ukundefined
                    jay_s_uk @opentoideas
                    last edited by

                    @opentoideas post your M563 from your config

                    Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                    opentoideasundefined 2 Replies Last reply Reply Quote 0
                    • opentoideasundefined
                      opentoideas @jay_s_uk
                      last edited by

                      @jay_s_uk doh, daft error it is!

                      for some reason the configuration tool has mapped F0:1

                      grr thanks again. fingers crossed

                      1 Reply Last reply Reply Quote 1
                      • opentoideasundefined
                        opentoideas @jay_s_uk
                        last edited by

                        @jay_s_uk sorry to throw in another question, did you ever change out the Predator motors? linear rails and magball arms are almost here and I find myself wondering about the standard motors on the Predator.

                        since it will all be coming apart they would be easy to change but there is little to no information on the stock motors.

                        reading the Duet wiki there is lots of technical info about motor choice but without any info on the current steppers other than likely 1.8deg but then sellers like E3d provide little info on the motors they sell other than the likely replacement is 0.9deg

                        does it matter, are the stock steppers good enough or is it worth changing them?

                        I see in your blog you tried a 0.9 stepper but I got the impression that didn't work more as the motor wasn't a suitable rating rather than anything else.

                        jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                        • jay_s_ukundefined
                          jay_s_uk @opentoideas
                          last edited by

                          @opentoideas I've changed the motors from the stock ones to 0.9 degree E3D ones. the high torque ones. High Torque Motor (1).pdf
                          ideally, deltas should have 0.9 degree motors are they benefit from the extra steps.
                          the motors I got previously were rubbish.

                          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                          opentoideasundefined 1 Reply Last reply Reply Quote 0
                          • opentoideasundefined
                            opentoideas @jay_s_uk
                            last edited by

                            @jay_s_uk thanks, that was what I was thinking and at least I will then know the spec I am working with.

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