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

Continue blocking during printing.

Scheduled Pinned Locked Moved
My Duet controlled machine
5
15
529
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
    Fedekossel1
    last edited by Fedekossel1 3 Oct 2020, 22:47 10 Mar 2020, 22:43

    Hi guys, lately I've been having some serious problems with my delta, for no reason it stops during the press. I have a version 2.05, and web control 2.07 At first I read a discussion of a user who specified the problem was due to 256 microsteps, I had 256 microsteps so I put 16 microsteps interpolation to 256. But the result has not changed. I always have those blocks, everything stays on even the fans, I can only use the emergency stop button. I also replaced the sd memory with a quality thinking it might be there the problem, Place here my configuration

    ; Configuration file for Duet WiFi (firmware version 2.03)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v2.0.4 on Tue Oct 01 2019 19:52:44 GMT+0200 (hora de verano de Europa central)

    ; General preferences
    G90 ; send absolute coordinates...
    M83 ; ...but relative extruder moves
    M550 P"kossel" ; set printer name
    M665 R185 L360.27 B150 H365 ; Set delta radius, diagonal rod length, printable radius and homed height
    M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them

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

    ; Drives
    M569 P0 S1 ; physical drive 0 goes forwards
    M569 P1 S1 ; physical drive 1 goes forwards
    M569 P2 S1 ; physical drive 2 goes forwards
    M569 P3 S1 ; physical drive 3 goes forwards

    M350 X16 Y16 Z16 I1 ; Configure microstepping with interpolation
    M350 E16 I0 ; Configure microstepping without interpolation
    M92 X160 Y160 Z160 ; Set steps per mm for X,Y and Z
    M92 E830 ; Set steps per mm for Extruder

    M566 X1000.00 Y1000.00 Z1000.00 E900.00 ; set maximum instantaneous speed changes (mm/min)
    M203 X18000.00 Y18000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
    M201 X900.00 Y900.00 Z900.00 E800.00 ; set accelerations (mm/s^2)
    M906 X1700 Y1700 Z1700 E1100 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 Y2 Z2 S1 ; set active high endstops

    ; Z-Probe
    M558 P8 R0.4 H5 F800 T3000 ; set Z probe type to effector and the dive height + speeds
    G31 P100 X0 Y0 Z-0.21 ; set Z probe trigger value, offset and trigger height
    M557 R120 S20 ; define mesh grid

    ; Heaters
    M305 P0 T100000 B4092 R4700 ; set thermistor + ADC parameters for heater 0
    M143 H0 S120 ; set temperature limit for heater 0 to 120C
    M305 P1 T100000 B4725 C7.060000e-8 R4700 ; set thermistor + ADC parameters for heater 1
    M143 H1 S280 ; set temperature limit for heater 1 to 280C

    ; Fans
    M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
    M106 P1 S1 I0 F500 H1 T40 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
    M106 P2 S0 I0 F500 H-1 ; electronic fan
    ; Tools
    M563 P0 D0 H1 F0 ; 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

    ; Custom settings are not defined

    ; Miscellaneous
    M501 ; load saved parameters from non-volatile memory


    Diagnosis command
    M122
    === Diagnostica ===
    RepRapFirmware per Duet 2 WiFi / Ethernet versione 2.05 in esecuzione su Duet WiFi 1.02 o successivo
    ID scheda: 08DGM-9T6BU-FG3SW-6J9FD-3SN6M-TVSZG
    Buffer di output usati: 1 di 24 (15 max)
    = == RTOS ===
    Ram statico: 25712 Ram
    dinamico: 92620 di cui 380
    ram di stack di eccezioni riciclati usati: 448
    Ram mai usati: 11912
    Compiti: NETWORK (pronto, 628) HEAT (bloccato, 1232) MAIN (in esecuzione, 348) IDLE (pronto, 160)
    Mutex di proprietà:
    === Piattaforma ===
    Ultimo ripristino 00:14:21 fa, causa: accensione
    Ultimo ripristino del software al 2020-03-08 12:35, motivo: Utente, modulo di rotazione GCodes, disponibile RAM 11896 byte (slot 3)
    Codice di reimpostazione software 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Stato errore: 10
    voci file libere
    rilevate : 9 Scheda SD 0 rilevata, velocità interfaccia: 20,0 MByte / sec
    tempo di scrittura blocco più lungo: 235 ms 0,7
    Temperatura MCU: min 44,3, corrente 53,0, max 53,2
    Tensione di alimentazione: min 24,5, corrente 24,7, max 24,8, eventi di sottotensione: 0, eventi di sovratensione: 0, alimentazione buona: sì
    Driver 0: fermo, SG min / max 0 / 99
    Driver 1: fermo, SG min / max 0/97
    Driver 2: fermo, SG min / max 0/103
    Driver 3: fermo, SG min / max 0/1023
    Driver 4: fermo, SG min / max non disponibile
    Data / tempo: 2020-03-08 13:26:45
    Conteggio risultati dati cache 2063208117 Ciclo
    più lento: 1256,78 ms; più veloce: 0,07 ms
    errori I2C nak 0, invio timeout 0, ricezione timeout 0, finishTimeout 0, reset 0
    === Move ===
    singhiozzo: 363416, FreeDm: 90, MinFreeDm: 84, MaxWait: 306358ms
    Compensazione del letto in uso: nessuna , comp offset 0.000
    === DDARing ===
    Mosse pianificate: 2350, mosse completate: 2310, StepErrors: 0, LaErrors: 0, Underruns: 0, 1
    === Heat ===
    Riscaldatori del letto = 0 -1 -1 - 1, ChamberHeaters = -1 -1 Il
    riscaldatore 0 è acceso, I-accum = 0,0 Il
    riscaldatore 1 è acceso, I-accum = 0.3
    === GCodes ===
    Segmenti rimasti: 1
    Record stack: 2 allocati, 0 in uso
    Blocco movimento detenuto da null
    http è inattivo negli stati 0
    telnet è inattivo negli stati 0 Il
    file sta eseguendo "G1 X-23.857 Y19.214 E0.0409" in stato (s) 0
    seriale è inattivo in stato (s) 0
    aux è inattivo in stato (s) 0
    demone è inattivo negli stati 0 la
    coda è inattiva negli stati 0 l'
    autopausa è inattiva negli stati 0 La
    coda del codice è vuota.
    === Rete ===
    Ciclo più lento: 1257,00 ms; più veloce: 0,08 ms
    Stati del risponditore: HTTP (0) HTTP (0) HTTP (0) HTTP (0) FTP (0) Telnet (0) Telnet (0)
    Sessioni HTTP: 1 di 8

    WiFi -
    Stato della rete in esecuzione Il
    modulo WiFi è collegato al punto di accesso
    Messaggi non riusciti: in attesa 0, non già 0, noresp 1
    Versione firmware
    WiFi 1.23 Indirizzo MAC WiFi ec: fa: bc: 31: 7e: cd
    WiFi Vcc 3.37, motivo di ripristino Acceso dal processore principale
    Dimensione flash WiFi 4194304, heap gratuito 23296
    Indirizzo IP WiFi 192.168.43.42
    Potenza del segnale WiFi -50dBm, riconnessioni 0, modem in modalità sospensione
    Stati socket: 0 0 0 0 0 0 0 0

    undefined 1 Reply Last reply 11 Mar 2020, 03:43 Reply Quote 0
    • undefined
      Phaedrux Moderator @Fedekossel1
      last edited by 11 Mar 2020, 03:43

      @Fedekossel1 said in Continue blocking during printing.:

      === Move ===
      singhiozzo: 363416

      You still have a high number of hiccups.

      If you send M350 in the gcode console, what does it reply with?

      M350 E16 I0 ; Configure microstepping without interpolation

      Why do you have interpolation disabled on the extruder?

      Z-Bot CoreXY Build | Thingiverse Profile

      undefined 1 Reply Last reply 11 Mar 2020, 06:30 Reply Quote 0
      • undefined
        Fedekossel1 @Phaedrux
        last edited by 11 Mar 2020, 06:30

        @Phaedrux I have to give the command M350 Just freezes?

        1 Reply Last reply Reply Quote 0
        • dc42undefined
          dc42 administrators
          last edited by 11 Mar 2020, 09:01

          Power up your printer, then send the M350 command. It will report what microstepping is selected.

          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

          undefined 1 Reply Last reply 11 Mar 2020, 09:53 Reply Quote 0
          • undefined
            Fedekossel1 @dc42
            last edited by 11 Mar 2020, 09:53

            @dc42 I just did the M350 command. Oddly enough, it gives me this result

            Microstepping - x:256, y:256, z:256, e:16:16

            In my configuration posted above I clearly put 16 interpolated microsteps at 256, excluding extruder that I will now also put at 256 interpolation,

            1 Reply Last reply Reply Quote 0
            • undefined
              AndreS
              last edited by 11 Mar 2020, 13:39

              check your config-override.g

              undefined 1 Reply Last reply 11 Mar 2020, 14:43 Reply Quote 0
              • undefined
                Fedekossel1 @AndreS
                last edited by 11 Mar 2020, 14:43

                @AndreS
                ; config-override.g file generated in response to M500 at 2020-03-10 10:27
                ; This is a system-generated file - do not edit
                ; Delta parameters
                M665 L360.270:360.270:360.270 R185.353 H364.129 B150.0 X0.229 Y0.060 Z0.000
                M666 X1.793 Y-1.094 Z-0.699 A0.00 B0.00
                ; Heater model parameters
                M307 H0 A90.0 C700.0 D10.0 S1.00 V0.0 B1
                M307 H1 A340.0 C140.0 D5.5 S1.00 V0.0 B0
                M307 H2 A340.0 C140.0 D5.5 S1.00 V0.0 B0
                M307 H3 A340.0 C140.0 D5.5 S1.00 V0.0 B0
                M307 H4 A340.0 C140.0 D5.5 S1.00 V0.0 B0
                M307 H5 A340.0 C140.0 D5.5 S1.00 V0.0 B0
                M307 H6 A340.0 C140.0 D5.5 S1.00 V0.0 B0
                M307 H7 A340.0 C140.0 D5.5 S1.00 V0.0 B0
                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

                1 Reply Last reply Reply Quote 0
                • jay_s_ukundefined
                  jay_s_uk
                  last edited by 11 Mar 2020, 14:53

                  @Fedekossel1

                  Try sending

                  M350 X16 Y16 Z16 E16 I1
                  

                  Once the machine has started up. Then resend M350 and make sure it reports back 16 microsteps for each axis.

                  If it does, it means that a file somewhere still has incorrect values for M350, causing the wrong values to be loaded on start up

                  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

                  undefined 1 Reply Last reply 11 Mar 2020, 14:59 Reply Quote 0
                  • undefined
                    Fedekossel1 @jay_s_uk
                    last edited by 11 Mar 2020, 14:59

                    @jay_s_uk
                    I just tried, I always 256 microsteps, besides the config are in other places the parameters of microsteps?

                    dc42undefined 1 Reply Last reply 11 Mar 2020, 15:28 Reply Quote 0
                    • undefined
                      Fedekossel1
                      last edited by 11 Mar 2020, 15:02

                      I found inside config.g.bak all the steps at 256 microsteps, I change them to 16?

                      jay_s_ukundefined 1 Reply Last reply 11 Mar 2020, 15:24 Reply Quote 0
                      • jay_s_ukundefined
                        jay_s_uk @Fedekossel1
                        last edited by 11 Mar 2020, 15:24

                        @Fedekossel1

                        config.g.bak doesn't get loaded at system start up

                        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 @Fedekossel1
                          last edited by dc42 3 Nov 2020, 15:28 11 Mar 2020, 15:28

                          @Fedekossel1 said in Continue blocking during printing.:

                          @jay_s_uk
                          I just tried, I always 256 microsteps, besides the config are in other places the parameters of microsteps?

                          That's the problem! Change XYZ to x16 microstepping with interpolation. If your E steps/mm is 400 or above, set that to x16 with interpolation too. If it is less than 400, set E microstepping to x64.

                          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

                          undefined 1 Reply Last reply 11 Mar 2020, 18:05 Reply Quote 0
                          • undefined
                            Fedekossel1 @dc42
                            last edited by 11 Mar 2020, 18:05

                            @dc42
                            I fixed, it's normal that it doesn't tell me giving the command M350 "example" X:16 (on),
                            ?
                            From config I put
                            M350 X16 Y16 Z16 E16 I1

                            Typing the M350 command gives me this result

                            M350
                            Microstepping - X:16, Y:16, Z:16, E:16:16```

                            dc42undefined 1 Reply Last reply 12 Mar 2020, 08:52 Reply Quote 0
                            • undefined
                              Fedekossel1
                              last edited by 11 Mar 2020, 22:50

                              I just set all the axes correctly to 16 microsteps interpolated to 256, with the same gcode that froze, now goes without stopping. I keep you updated these days if I get problems or blocks during printing. At the moment I thank everyone!

                              1 Reply Last reply Reply Quote 0
                              • dc42undefined
                                dc42 administrators @Fedekossel1
                                last edited by 12 Mar 2020, 08:52

                                @Fedekossel1 said in Continue blocking during printing.:

                                @dc42
                                I fixed, it's normal that it doesn't tell me giving the command M350 "example" X:16 (on),
                                ?
                                From config I put
                                M350 X16 Y16 Z16 E16 I1

                                Typing the M350 command gives me this result

                                M350
                                Microstepping - X:16, Y:16, Z:16, E:16:16```

                                Check that you have entered the I1 parameter correctly. That's letter i followed by digit 1.

                                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 0
                                1 out of 15
                                • First post
                                  1/15
                                  Last post
                                Unless otherwise noted, all forum content is licensed under CC-BY-SA