• Tags
  • Documentation
  • Order
  • Register
  • Login
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.
  • undefined
    sozkan @Phaedrux
    last edited by 22 Oct 2020, 19:37

    @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
    • undefined
      Phaedrux Moderator
      last edited by 22 Oct 2020, 19:39

      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

      undefined 1 Reply Last reply 22 Oct 2020, 19:47 Reply Quote 0
      • undefined
        sozkan @Phaedrux
        last edited by 22 Oct 2020, 19:46

        @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
        • undefined
          sozkan @Phaedrux
          last edited by 22 Oct 2020, 19:47

          @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 🙂

          undefined 1 Reply Last reply 22 Oct 2020, 19:51 Reply Quote 0
          • undefined
            sozkan @sozkan
            last edited by 22 Oct 2020, 19:51

            @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
            • undefined
              sozkan @Phaedrux
              last edited by 23 Oct 2020, 14:32

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

              M98 P"config.g"

              Hi,
              I have just done your advise:
              result :
              10/23/2020, 4:31:32 PM M122
              === Diagnostics ===
              RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2-beta1 running on Duet WiFi 1.02 or later
              Board ID: 08DGM-917DA-G4MS8-6JTD4-3S86J-19SHA
              Used output buffers: 3 of 24 (21 max)
              === RTOS ===
              Static ram: 23916
              Dynamic ram: 98532 of which 120 recycled
              Exception stack ram used: 544
              Never used ram: 7960
              Tasks: NETWORK(ready,125) HEAT(blocked,138) MAIN(running,328) IDLE(ready,20)
              Owned mutexes: WiFi(NETWORK)
              === Platform ===
              Last reset 00:03:52 ago, cause: power up
              Last software reset at 2020-10-22 20:24, reason: User, GCodes spinning, available RAM 8036, slot 0
              Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
              Error status: 0x028
              MCU temperature: min 30.7, current 32.4, max 32.6
              Supply voltage: min 24.2, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
              Driver 0: position 276494, standstill, SG min/max not available
              Driver 1: position 276494, standstill, SG min/max not available
              Driver 2: position 276494, standstill, SG min/max not available
              Driver 3: position 0, standstill, SG min/max not available
              Driver 4: position 0, standstill, SG min/max not available
              Driver 5: position 0
              Driver 6: position 0
              Driver 7: position 0
              Driver 8: position 0
              Driver 9: position 0
              Driver 10: position 0
              Driver 11: position 0
              Date/time: 2020-10-23 16:31:31
              Cache data hit count 407671411
              Slowest loop: 65.60ms; fastest: 0.15ms
              I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
              === Storage ===
              Free file entries: 10
              SD card 0 detected, interface speed: 20.0MBytes/sec
              SD card longest read time 1.0ms, write time 28.7ms, max retries 0
              === Move ===
              Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
              Bed compensation in use: none, comp offset 0.000
              === MainDDARing ===
              Scheduled moves: 19, completed moves: 19, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
              === AuxDDARing ===
              Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
              === Heat ===
              Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
              === GCodes ===
              Segments left: 0
              Movement lock held by null
              HTTP is idle in state(s) 0
              Telnet is idle in state(s) 0
              File is idle in state(s) 0
              USB is idle in state(s) 0
              Aux is idle in state(s) 0
              Trigger is idle in state(s) 0
              Queue is idle in state(s) 0
              LCD is idle in state(s) 0
              Daemon is idle in state(s) 0
              Autopause is idle in state(s) 0
              Code queue is empty.
              === Network ===
              Slowest loop: 217.22ms; fastest: 0.09ms
              Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
              HTTP sessions: 1 of 8

              • WiFi -
                Network state is active
                WiFi module is connected to access point
                Failed messages: pending 0, notready 0, noresp 2
                WiFi firmware version 1.23
                WiFi MAC address 80:7d:3a:3f:f6:73
                WiFi Vcc 3.38, reset reason Turned on by main processor
                WiFi flash size 4194304, free heap 22848
                WiFi IP address 192.168.43.196
                WiFi signal strength -67dBm, reconnections 0, sleep mode modem
                Clock register ffffffff
                Socket states: 0 0 0 0 0 0 0 0
                10/23/2020, 4:30:44 PM Error: Temperature reading fault on heater 1: sensor open circuit
                Error: Temperature reading fault on heater 2: sensor open circuit
                10/23/2020, 4:30:42 PM M98 P"config.g"
                HTTP is enabled on port 80
                FTP is disabled
                TELNET is disabled
                Error: Driver 6 does not support x0 microstepping with interpolation
                Driver 7 does not support x0 microstepping with interpolation
                Driver 8 does not support x0 microstepping with interpolation
                Driver 5 does not support x0 microstepping with interpolation
                Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
                Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 258C
              undefined 1 Reply Last reply 23 Oct 2020, 15:56 Reply Quote 0
              • undefined
                Phaedrux Moderator @sozkan
                last edited by 23 Oct 2020, 15:56

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

                RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2-beta1 running on Duet WiFi 1.02 or later

                I would say in your current situation of commissioning and tuning you should stick with firmware 3.1.1

                Upload this zip file as is, don't extract it, to the system tab in the web interface.

                https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet2and3Firmware-3.1.1.zip

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

                Error: Driver 6 does not support x0 microstepping with interpolation
                Driver 7 does not support x0 microstepping with interpolation
                Driver 8 does not support x0 microstepping with interpolation
                Driver 5 does not support x0 microstepping with interpolation

                M350 X0 Y0 Z0 E0 I1

                I think you're going to need to specify a microstepping value. 0 won't work. Try 1.

                Z-Bot CoreXY Build | Thingiverse Profile

                undefined 1 Reply Last reply 23 Oct 2020, 16:07 Reply Quote 0
                • undefined
                  sozkan @Phaedrux
                  last edited by 23 Oct 2020, 16:07

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

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

                  RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2-beta1 running on Duet WiFi 1.02 or later

                  I would say in your current situation of commissioning and tuning you should stick with firmware 3.1.1

                  Upload this zip file as is, don't extract it, to the system tab in the web interface.

                  https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet2and3Firmware-3.1.1.zip

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

                  Error: Driver 6 does not support x0 microstepping with interpolation
                  Driver 7 does not support x0 microstepping with interpolation
                  Driver 8 does not support x0 microstepping with interpolation
                  Driver 5 does not support x0 microstepping with interpolation

                  M350 X0 Y0 Z0 E0 I1

                  I think you're going to need to specify a microstepping value. 0 won't work. Try 1.

                  I will definitely try your advice soon. I was formating file structure, I can't connect web interface anymore now. I have backed up fully the SD card. Reverted back but still not connecting.

                  undefined 1 Reply Last reply 23 Oct 2020, 16:11 Reply Quote 0
                  • undefined
                    Phaedrux Moderator
                    last edited by 23 Oct 2020, 16:11

                    Your SD card needs a file structure like this: https://duet3d.dozuki.com/Wiki/SD_Card#Section_Creating_the_file_structure

                    The web interface files need be placed in the /www folder and come from here: https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/DuetWebControl-SD-3.1.1.zip

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      sozkan @sozkan
                      last edited by 23 Oct 2020, 16:11

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

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

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

                      RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2-beta1 running on Duet WiFi 1.02 or later

                      I would say in your current situation of commissioning and tuning you should stick with firmware 3.1.1

                      Upload this zip file as is, don't extract it, to the system tab in the web interface.

                      https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet2and3Firmware-3.1.1.zip

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

                      Error: Driver 6 does not support x0 microstepping with interpolation
                      Driver 7 does not support x0 microstepping with interpolation
                      Driver 8 does not support x0 microstepping with interpolation
                      Driver 5 does not support x0 microstepping with interpolation

                      M350 X0 Y0 Z0 E0 I1

                      I think you're going to need to specify a microstepping value. 0 won't work. Try 1.

                      I will definitely try your advice soon. I was formating file structure, I can't connect web interface anymore now. I have backed up fully the SD card. Reverted back but still not connecting.

                      I normally install the beta update using the web interface. The CSS and www folders appeared in the sys folder after that.

                      undefined 1 Reply Last reply 23 Oct 2020, 16:12 Reply Quote 0
                      • undefined
                        Phaedrux Moderator @sozkan
                        last edited by 23 Oct 2020, 16:12

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

                        I normally install the beta update using the web interface. The CSS and www folders appeared in the sys folder after that.

                        Did you upload the full zip file without extracting it first?

                        You must not extract the zip file.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        undefined 1 Reply Last reply 23 Oct 2020, 16:22 Reply Quote 0
                        • undefined
                          sozkan @Phaedrux
                          last edited by 23 Oct 2020, 16:22

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

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

                          I normally install the beta update using the web interface. The CSS and www folders appeared in the sys folder after that.

                          Did you upload the full zip file without extracting it first?

                          You must not extract the zip file.

                          yes I did in the past with zip in beta version upgrade. But this case I cannot connect web interface. Panedue console says it connected to the IP : 192.168.1.200 but on my hotspot network it shows unknow IP connection. I have uploaded the firmware files in the SD card that you sent me now and reinstall firmware using the PaneDue interface with "M997 S0 to install the firmware" and "M997 S1 to install the WiFi module firmware" so successfully updated. After I send M115 to confirm the new firmware version it is still beta version remain and not connected.

                          1 Reply Last reply Reply Quote 0
                          • undefined
                            Phaedrux Moderator
                            last edited by 23 Oct 2020, 16:35

                            It sounds like your /www folder may be missing still?

                            Z-Bot CoreXY Build | Thingiverse Profile

                            undefined 1 Reply Last reply 23 Oct 2020, 17:10 Reply Quote 0
                            • undefined
                              sozkan @Phaedrux
                              last edited by 23 Oct 2020, 17:10

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

                              It sounds like your /www folder may be missing still?

                              I actually revert the backup which is previously connecting with no issue.
                              This problem just appeared. I have tried to connect different SSID name, I could not save into controller gives error on the saving list. It seems like the controller relying on "config.json" keep connecting old parameters. By the way, I have reinstalled back beta firmware just to see if it will connect.

                              1 Reply Last reply Reply Quote 0
                              • undefined
                                Phaedrux Moderator
                                last edited by 23 Oct 2020, 17:20

                                config.json is just used by the online config tool

                                Can you post a photo of what your SD card file structure looks like now?

                                Since you have a PanelDue it may be a good idea to add some macros to your SD card macros folder to aid in diagnostics.

                                https://github.com/Duet3D/RRF-machine-config-files/tree/master/DBotCoreXY/x0r-wifi-RRF3/macros/Diagnostics

                                At the bottom of that list are 3 wifi macros which you can customize with your SSID name to make clearing and adding the wifi network easy from the paneldue.

                                Sending M997 S1 should reflash the wifi server firmware in case something went wrong on the last update.

                                If you send M122 from a USB connection you can see the wifi server status at the end. The response is too large for the PanelDue to display.

                                Z-Bot CoreXY Build | Thingiverse Profile

                                undefined 2 Replies Last reply 23 Oct 2020, 17:57 Reply Quote 0
                                • undefined
                                  sozkan @Phaedrux
                                  last edited by 23 Oct 2020, 17:57

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

                                  config.json is just used by the online config tool

                                  Can you post a photo of what your SD card file structure looks like now?

                                  Since you have a PanelDue it may be a good idea to add some macros to your SD card macros folder to aid in diagnostics.

                                  https://github.com/Duet3D/RRF-machine-config-files/tree/master/DBotCoreXY/x0r-wifi-RRF3/macros/Diagnostics

                                  At the bottom of that list are 3 wifi macros which you can customize with your SSID name to make clearing and adding the wifi network easy from the paneldue.

                                  Sending M997 S1 should reflash the wifi server firmware in case something went wrong on the last update.

                                  If you send M122 from a USB connection you can see the wifi server status at the end. The response is too large for the PanelDue to display.

                                  Thanks. Macros help to reset the wifi module. I am in DWC now finally.

                                  1 Reply Last reply Reply Quote 0
                                  • undefined
                                    sozkan @Phaedrux
                                    last edited by sozkan 23 Oct 2020, 18:06

                                    @Phaedrux !DuetSysStr.png
                                    I have added files on the sys folder before downgrade to the stable 3.11 version. I will update using the web interface.

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      Phaedrux Moderator
                                      last edited by 23 Oct 2020, 18:14

                                      I'm a little confused.

                                      Are you on 3.2 beta still, or 3.1.1?

                                      I think maybe some other files may be missing.

                                      You could try updating with 3.0 first, and then 3.1.1

                                      https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip

                                      https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet2and3Firmware-3.1.1.zip

                                      Remember to upload the entire intact zip file to the system tab. Don't extract.

                                      Z-Bot CoreXY Build | Thingiverse Profile

                                      undefined 1 Reply Last reply 23 Oct 2020, 18:21 Reply Quote 0
                                      • undefined
                                        sozkan @Phaedrux
                                        last edited by 23 Oct 2020, 18:21

                                        @Phaedrux I have actually Upgraded to 3.0 at first. later 3.11 and latest beta. Presently I have downgraded to 3.1.1 using DWC .

                                        I have checked your previous recommendation Micro Stepping "1" it is still remain horrible sound ;

                                        ; 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 X1 Y1 Z1 E1 I1                                ; configure microstepping without interpolation
                                        
                                        1 Reply Last reply Reply Quote 0
                                        • undefined
                                          sozkan
                                          last edited by sozkan 11 Nov 2020, 17:15 11 Nov 2020, 16:47

                                          Hi again.

                                          It was seemed resolved. But cracking sound revealed again on different homing variations.

                                          if one of the motors for each other and if two of the three-axis reaches the limit switches, the last motor starts on a noisy signal and can't complete the move distance. During the home Cracking noisy sound. The failing reason seems running less than the specified home distance. But the distance is correct.
                                          Please see the video on this issue:
                                          https://www.youtube.com/watch?v=2GGh0wQdLYQ

                                          I believe the hardware is fine. Because once it is successfully homed, working calibrated and smooth.

                                          if once fails on homing, and If I move the motors manually away from limit switches, homing again smooth. the somehow nosy signal appears if two limits switch on.

                                          I also doubted if limit switches contact cause power loss? Should I put a resistor in series to try?

                                          it is currently on the config file.

                                          ; Drives
                                          M569 P5 S0 R0 T3:3:5:0      ; Extruder drive 0 goes Forward
                                          M569 P2 S1 R0 T2.5:2.5:6:6  ; X:A drive 1 goes Forward
                                          M569 P3 S1 R0 T2.5:2.5:6:6  ; Y:B drive 2 goes Forward
                                          M569 P4 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 I0                                ; configure microstepping without interpolation
                                          

                                          It says Y-axis not homed which is connected on E4 for on the breakout board. But during the Delta move, Y-axis toward the Z-axis direction, and Z motor moves more.

                                          undefined 1 Reply Last reply 11 Nov 2020, 16:55 Reply Quote 0
                                          • First post
                                            Last post
                                          Unless otherwise noted, all forum content is licensed under CC-BY-SA