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

    Giant Delta printer Slow Homing issue.

    Scheduled Pinned Locked Moved
    My Duet controlled machine
    8
    84
    3.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.
    • jay_s_ukundefined
      jay_s_uk
      last edited by

      looking at the datasheet I think your timing are not correct for the driver.
      there needs to be at least a 6us setup time for direction
      I would maybe try a timing of T3:3:6:0

      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

      1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators
        last edited by

        Looking at the data fore the driver that you linked to, the other thing you may need to do is use the alternate connection method to the expansion board:

        • Connect PUL+ and DIR+ driver input to the +5V pin on one of the servo headers on the breakout board
        • Connect PUL- to STEP- on the breakout board, and DIR- to DIR-.

        The data says that you can leave ENA+ and ENA- not connected. This is probably best until you get everything working, however the Duet won't be able to turn the motors off. Therefore, when movement is working correctly, you may wish to connect ENA+ to +5V on the breakout board, and ENA- to ENA-. Use whichever of R0 and R1 works in the M569 commands.

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        1 Reply Last reply Reply Quote 1
        • sozkanundefined
          sozkan
          last edited by sozkan

          Hi,
          It finally succeeds, running smooth and correct in calibration, homing perfect, by changing ;

          • Connect PUL+ and DIR+ driver input to the +5V pin on one of the servo headers on the breakout board
          • Keep Remain PUL- to STEP- on the breakout board, and DIR- to DIR-.
          • Revert back the P values to "P0, P1, P2, P3" ( Because Correct one Create noise like ball bearings broken and move uncalibrated ). Therefore I cannot control the default direction (S values) ( But however on the drive I managed to change it ).

          In a conclusion, even if it is solved, working better with an incorrect parameter. However, a +5V connections make a good job.

          I still want to work with the correct parameters as you advise.

          Thank you very much.

          droftartsundefined 1 Reply Last reply Reply Quote 1
          • droftartsundefined
            droftarts administrators @sozkan
            last edited by

            @sozkan said in Giant Delta printer Slow Homing issue.:

            Revert back the P values to "P0, P1, P2, P3" ( Because Correct one Create noise like ball bearings broken and move uncalibrated ). Therefore I cannot control the default direction (S values) ( But however on the drive I managed to change it ).

            Your external axes will be using default timing. Send M569 P5 and see what it says. It did not run well because of the T parameter settings you used: M569 P5 S1 R1 T3:3:5:0

            From the product page you linked, there's this, which shows the timing you should be using:
            alt text
            M569 T parameter, where Taa:bb:cc:dd:
            aa = Minimum driver step pulse width, in microseconds = t3 in image = not less than 2.5us
            bb=step pulse interval, in microseconds = t4 in image = not less than 2.5us
            cc=direction setup time, in microseconds = t1/t2/t5 in image = at least 6us
            dd=direction hold time, in microseconds = t1/t2/t5 = at least 6us
            Enable signal t1 = assume that you have ENA+ an ENA- floating, so constantly enabled. Also, I think t3 and t4 are the wrong way around in the image, but they are the same value.

            From this, try:

            M569 P5 S1 R1 T2.5:2.5:6:6  ; Extruder drive 0 goes Forward
            M569 P6 S1 R1 T2.5:2.5:6:6  ; X:A drive 1 goes Forward
            M569 P7 S1 R1 T2.5:2.5:6:6  ; Y:B drive 2 goes Forward
            M569 P8 S1 R1 T2.5:2.5:6:6  ; Z:C physical drive 3 goes Forward
            

            Ian

            Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

            sozkanundefined 1 Reply Last reply Reply Quote 0
            • sozkanundefined
              sozkan @droftarts
              last edited by

              @droftarts said in Giant Delta printer Slow Homing issue.:

              @sozkan said in Giant Delta printer Slow Homing issue.:

              Revert back the P values to "P0, P1, P2, P3" ( Because Correct one Create noise like ball bearings broken and move uncalibrated ). Therefore I cannot control the default direction (S values) ( But however on the drive I managed to change it ).

              Your external axes will be using default timing. Send M569 P5 and see what it says. It did not run well because of the T parameter settings you used: M569 P5 S1 R1 T3:3:5:0

              From the product page you linked, there's this, which shows the timing you should be using:
              alt text
              M569 T parameter, where Taa:bb:cc:dd:
              aa = Minimum driver step pulse width, in microseconds = t3 in image = not less than 2.5us
              bb=step pulse interval, in microseconds = t4 in image = not less than 2.5us
              cc=direction setup time, in microseconds = t1/t2/t5 in image = at least 6us
              dd=direction hold time, in microseconds = t1/t2/t5 = at least 6us
              Enable signal t1 = assume that you have ENA+ an ENA- floating, so constantly enabled. Also, I think t3 and t4 are the wrong way around in the image, but they are the same value.

              From this, try:

              M569 P5 S1 R1 T2.5:2.5:6:6  ; Extruder drive 0 goes Forward
              M569 P6 S1 R1 T2.5:2.5:6:6  ; X:A drive 1 goes Forward
              M569 P7 S1 R1 T2.5:2.5:6:6  ; Y:B drive 2 goes Forward
              M569 P8 S1 R1 T2.5:2.5:6:6  ; Z:C physical drive 3 goes Forward
              

              Ian

              Hello. Thank you for your concern and effort.
              I was busy with upgrading mechanical hardware.
              I just came to this point once again. The problem is not solved yet. When P values changed to 5,6,7 sounds horrible and inccorrect. But when P values 1,2,3 it is working but not correct right?
              Please see the video I make on youtube : Link for video.

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

                In your video it looks like you're getting an error message when trying to save the config.g and reboot the board. Failed to download config.g.

                Are the updates you are making to config.g actually getting saved?

                Can you please provide the results of M122 and M98 P"config.g" ?

                Z-Bot CoreXY Build | Thingiverse Profile

                sozkanundefined 2 Replies Last reply Reply Quote 0
                • sozkanundefined
                  sozkan @Phaedrux
                  last edited by sozkan

                  @Phaedrux said in Giant Delta printer Slow Homing issue.:

                  In your video it looks like you're getting an error message when trying to save the config.g and reboot the board. Failed to download config.g.

                  Are the updates you are making to config.g actually getting saved?

                  Can you please provide the results of M122 and M98 P"config.g" ?

                  Please check the full code:

                  ; Configuration file for Duet WiFi (firmware version 3)
                  ; executed by the firmware on start-up
                  ;
                  ; generated by RepRapFirmware Configuration Tool v3.1.4 on Sun Sep 27 2020 20:52:39 GMT+0200 (Central European Summer Time)
                  
                  ; General preferences
                  G90                                                ; send absolute coordinates...
                  M83                                                ; ...but relative extruder moves
                  M550 P"Giant3D"                                    ; set printer name
                  M665 R600 L1200 B575 H1450                         ; Set delta radius, diagonal rod length, printable radius and homed height
                  ;M564 H0					     				   ; allow jog without homing
                  M666 X0 Y0 Z0                                      ; put your endstop adjustments here, or let auto calibration find them
                  
                  ; Network
                  M551 P"xxxxxx"                                ; set password
                  M587 S"WfiName" P"xxxxxx" I192.168.1.200
                  M552 S1                                            ; enable network
                  M586 P0 S1                                         ; enable HTTP
                  M586 P1 S0                                         ; disable FTP
                  M586 P2 S0                                         ; disable Telnet
                  
                  ; Drives
                  M569 P5 S0 R0 T3:3:5:0                                       ; Extruder drive 0 goes Forward
                  M569 P6 S1 R0 T2.5:2.5:6:6  ; X:A drive 1 goes Forward
                  M569 P7 S1 R0 T2.5:2.5:6:6  ; Y:B drive 2 goes Forward
                  M569 P8 S1 R0 T2.5:2.5:6:6  ; Z:C physical drive 3 goes Forward
                  M584 X6 Y7 Z8 E5                                  			 ; set drive mapping
                  
                  M350 X0 Y0 Z0 E0 I1                                ; configure microstepping without interpolation
                  M92 X114.29 Y114.29 Z114.29 E274.00                   ; set steps per mm (400/140) * 40 = 114.2857 ;; 400 step per rev ;; 140 mm one rev pulley ;;1:40 ratio gearbox 
                  M566 X1200.00 Y1200.00 Z1200.00 E1200.00           ; set maximum instantaneous speed changes (mm/min)
                  M203 X6000.00 Y6000.00 Z6000.00 E3000.00           ; set maximum speeds (mm/min)
                  M201 X500.00 Y500.00 Z500.00 E1000.00           ; set accelerations (mm/s^2)
                  M906 X1000 Y1000 Z1000 E800 I30                    ; 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 P1 C"zprobe.in+zprobe.mod" H5 F120 T6000      ; set Z probe type to unmodulated and the dive height + speeds
                  M558 H30                                           ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
                  G31 P500 X0 Y0 Z3.5                                ; set Z probe trigger value, offset and trigger height
                  M557 R350 S200                                     ; define mesh grid
                  
                  ; Heaters
                  M308 S0 P"bedtemp" Y"thermistor" T100000 B4138     ; 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 B1 S1.00                                   ; enable 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"pt1000" R4700                  ; configure sensor 1 as PT1000 on pin e0temp
                  M950 H1 C"e0heat" T1                               ; create nozzle heater output on e0heat and map it to sensor 1
                  M307 H1 B0 S0.50                                   ; disable bang-bang mode for heater  and set PWM limit
                  M308 S2 P"e1temp" Y"pt1000" R4700                  ; configure sensor 2 as PT1000 on pin e1temp
                  M950 H2 C"e1heat" T2                               ; create nozzle heater output on e1heat and map it to sensor 2
                  M307 H2 B0 S0.50                                   ; 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 S1 H2:1 T45                                ; set fan 0 value. Thermostatic control is turned on
                  
                  ; Tools
                  M563 P0 D0 H1:2 F0 S"Typhoon"                      ; define tool 0
                  G10 P0 X0 Y0 Z0                                    ; set tool 0 axis offsets
                  G10 P0 R0 S0                                       ; set initial tool 0 active and standby temperatures to 0C
                                                    ; set initial tool 1 active and standby temperatures to 0C
                  
                  ; Custom settings are not defined
                  
                  ; Miscellaneous
                  M575 P1 S1 B57600                                  ; enable support for PanelDue
                  M501                                               ; load saved parameters from non-volatile memory
                  M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
                  T0                                                 ; select first tool
                  
                  G91                         ; relative positioning
                  ;G1 H2 X-0.1 Y-0.1 Z-0.1 F1000      ; go down a few mm
                  
                  
                  Phaedruxundefined 1 Reply Last reply Reply Quote 0
                  • Phaedruxundefined
                    Phaedrux Moderator
                    last edited by

                    Also, in your video it looks like you have the DWC web files in your /system folder. They should not be there. (The CSS, FONTS, JS folders for example, and the html.gz files, etc.) Those files all belong in the /www folder on the SD card.

                    I think there may have been a few mistakes made during a firmware update.

                    Z-Bot CoreXY Build | Thingiverse Profile

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

                      @sozkan said in Giant Delta printer Slow Homing issue.:

                      Can you please provide the results of M122 and M98 P"config.g" ?

                      Z-Bot CoreXY Build | Thingiverse Profile

                      sozkanundefined 1 Reply Last reply Reply Quote 0
                      • sozkanundefined
                        sozkan @Phaedrux
                        last edited by

                        @Phaedrux it could be. Thank you for your attention. I am still on the learning curve.

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

                          You can see an example of the correct file structure here.

                          https://duet3d.dozuki.com/Wiki/SD_Card#Section_Creating_the_file_structure

                          Note that your /sys folder will also contain some .bin files for the firmware in addition to the listed .g config files.

                          It may be easiest to put the SD card into a PC to edit the file structure.

                          Z-Bot CoreXY Build | Thingiverse Profile

                          1 Reply Last reply Reply Quote 0
                          • sozkanundefined
                            sozkan @Phaedrux
                            last edited by sozkan

                            @Phaedrux said in Giant Delta printer Slow Homing issue.:

                            @sozkan said in Giant Delta printer Slow Homing issue.:

                            Can you please provide the results of M122 and M98 P"config.g" ?

                            I realize now, you want me to send a command to the machine right? I can do it by tomorrow.

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

                              Yes, M122 will give us some diagnostic information including verifying what firmware version is installed. And M98 P"config.g" will execute the config.g file as a macro and echo back any error messages which are otherwise missed during power on. This would help eliminate any other syntax errors in config.g.

                              Z-Bot CoreXY Build | Thingiverse Profile

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

                                This may not resolve your noisy motors, but it will at least ensure we're working with a correctly functioning setup.

                                Z-Bot CoreXY Build | Thingiverse Profile

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

                                  M569 P1 P2 P3 are fine if those cause the motors to move those are the correct ones. It's just targeting those driver numbers.

                                  https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M569_1_Stepper_driver_closed_loop_control

                                  Z-Bot CoreXY Build | Thingiverse Profile

                                  sozkanundefined 1 Reply Last reply Reply Quote 0
                                  • sozkanundefined
                                    sozkan @Phaedrux
                                    last edited by

                                    @Phaedrux
                                    I will definitely do and share the result by tomorrow.

                                    But I am sure there is no imperfection on hardware and wiring. Because motors are accurately working on illegal code, but creating horrible sound and incorrectly working on legal code. That's means I have done something working during the firmware upgrade?

                                    Because it is the latest stable update recently I messed up.

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

                                      And yes, reduce acceleration and jerk. That should help a bit.

                                      The motors are going to be loud. They are large and mounted to metal, but hopefully the adjusted timing and acceleration will make it a bit more bearable.

                                      @sozkan said in Giant Delta printer Slow Homing issue.:

                                      Because motors are accurately working on illegal code, but creating horrible sound and incorrectly working on legal code.

                                      It's not illegal code if it works.

                                      Z-Bot CoreXY Build | Thingiverse Profile

                                      sozkanundefined 1 Reply Last reply Reply Quote 0
                                      • sozkanundefined
                                        sozkan @Phaedrux
                                        last edited by

                                        @Phaedrux said in Giant Delta printer Slow Homing issue.:

                                        M569 P1 P2 P3 are fine if those cause the motors to move those are the correct ones. It's just targeting those driver numbers.

                                        https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M569_1_Stepper_driver_closed_loop_control

                                        It`s some how stable on motor step control, but with those settings, I cannot control Enable or disable the motor features as well as the direction due to the illegal numbering. Because event Mr. admin "dc42" suggests for the external motor drives the stepper breakout board legal codes P5,6,7,8. Somehow these legal settings only working enable and direction settings and unstable step signals for the motor.

                                        1 Reply Last reply Reply Quote 0
                                        • sozkanundefined
                                          sozkan @Phaedrux
                                          last edited by

                                          @Phaedrux said in Giant Delta printer Slow Homing issue.:

                                          And yes, reduce acceleration and jerk. That should help a bit.

                                          The motors are going to be loud. They are large and mounted to metal, but hopefully the adjusted timing and acceleration will make it a bit more bearable.

                                          @sozkan said in Giant Delta printer Slow Homing issue.:

                                          Because motors are accurately working on illegal code, but creating horrible sound and incorrectly working on legal code.

                                          It's not illegal code if it works.

                                          Since it is not functioning other variables except stepping, also according to the Firmware developer it is illegal 🙂

                                          sozkanundefined 1 Reply Last reply Reply Quote 0
                                          • sozkanundefined
                                            sozkan @sozkan
                                            last edited by

                                            @sozkan said in Giant Delta printer Slow Homing issue.:

                                            @Phaedrux said in Giant Delta printer Slow Homing issue.:

                                            And yes, reduce acceleration and jerk. That should help a bit.

                                            The motors are going to be loud. They are large and mounted to metal, but hopefully the adjusted timing and acceleration will make it a bit more bearable.

                                            @sozkan said in Giant Delta printer Slow Homing issue.:

                                            Because motors are accurately working on illegal code, but creating horrible sound and incorrectly working on legal code.

                                            It's not illegal code if it works.

                                            Since it is not functioning other variables except stepping, also according to the Firmware developer it is illegal 🙂

                                            Until I found a stable solution, I will continue with this achieved a motor enable issue by hardware and mechanical brake gearbox and right direction setup on external motor driver. I believe it might run G-codes sufficiently if there is no hidden failure.

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