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

    Issues after prime

    Scheduled Pinned Locked Moved Solved
    Beta Firmware
    4
    132
    6.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.
    • Heartleander81undefined
      Heartleander81 @Phaedrux
      last edited by

      @phaedrux
      I changed it in the slicer.
      when I enter the startcode (saved as "startGcode") on the Board not at slicer

      G32 G29 S1 P "hightmap.csv" 
      G92 E0 
      G1 X5 Y5 Z30 F6000.0 
      G1 E40 F600 
      G1 E40 F200 
      G1 Y20 F2000 
      G1 Y50 Z0.2 F2000 
      G1 Y90 E20 F300 
      G92 E0 
      G1 Y120 F1200
      
      

      entries should that fit then? Because in the actual Gcode comes first one G92 E0.000 followed by G1 E-0.600

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

        @heartleander81 said in Isusses after prime:

        G1 E-0.600

        Is that not just a retraction being inserted by the slicer?

        Z-Bot CoreXY Build | Thingiverse Profile

        Heartleander81undefined 2 Replies Last reply Reply Quote 0
        • Heartleander81undefined
          Heartleander81 @Phaedrux
          last edited by

          @phaedrux

          yes, but that makes my printer the problem. Ill test M83 later.

          1 Reply Last reply Reply Quote 0
          • Heartleander81undefined
            Heartleander81 @Phaedrux
            last edited by Heartleander81

            @phaedrux

            I have change it.
            In Config.g is M83
            Slicer M83

            When I test the following startcode

            G32
            G29 S1 P"heightmap.csv"
            G1 X5 Y5 Z30 F6000.0 
            G1 E40 F600
            G1 E40 F200
            G1 Y20 F2000
            G1 Y50 Z0.2 F2000
            G1 Y90 E20 F300
            G1 Y120 F1200
            
            

            The Prime is good but I have the issuse how in the Youtube Video.

            Who is the fail?

            1 Reply Last reply Reply Quote 0
            • Heartleander81undefined
              Heartleander81
              last edited by

              When I make the first G1 move slower then F4000 ore the first G1 E-0.6 slower then F300 ore i delet the first G1 E-0.6, I doun't have the problem.

              All what I test the same issuse.

              Is any on my toolboard Config wrong?

              1 Reply Last reply Reply Quote 0
              • Heartleander81undefined
                Heartleander81
                last edited by

                I have install after 2 weeks the tool Board rev 1.1 with Accelerometer.
                The first prints All good. Over night came this isusse. Then I make any test and then, why ever was all good but only for 2 prints and the issuse was back.

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

                  @heartleander81 said in Isusses after prime:

                  G31 P500 X22.775 Y-5.21 Z0.00

                  Your Z probe trigger height hasn't been measured yet.
                  https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

                  Please post the results of M122 and M122 B121

                  Also send M98 P"config.g" and post the results.

                  Can you also share your homing files?

                  Z-Bot CoreXY Build | Thingiverse Profile

                  Heartleander81undefined 2 Replies Last reply Reply Quote 0
                  • Heartleander81undefined
                    Heartleander81 @Phaedrux
                    last edited by

                    @phaedrux
                    Oh I have set it not to 0
                    But then I load M501 for the right trigger height.

                    Give me one Moment I Post it All.

                    1 Reply Last reply Reply Quote 0
                    • Heartleander81undefined
                      Heartleander81
                      last edited by Heartleander81

                      Config.g

                      ; Configuration file for Duet 3 (firmware version 3)
                      ; executed by the firmware on start-up
                      ;
                      ; generated by RepRapFirmware Configuration Tool v3.1.4 on Wed Aug 26 2020 16:14:58 GMT+0200 (Mitteleuropäische Sommerzeit)
                      
                      ; General preferences
                      G90                                                                   ; send absolute coordinates...
                      M83                                                                   ; ...but relativ extruder moves
                      M550 P"Duet3"                                                         ; set printer name
                      M912 P0 S-2                                                           ; setzt CPU Temp korrektur
                      M669 K1                                                               ;switch to core X/Y mode
                      G4 S2
                      ; Drives
                      M569 P0.1 S0 D2                                                         ; X physical drive 0.1 goes backwards
                      M569 P0.2 S0 D2                                                        ; Y physical drive 0.2 goes backwards
                      M569 P0.0 S1                                                          ; Z1 physical drive 0.0 goes forwards
                      M569 P0.4 S1                                                          ; Z2 physical drive 0.4 goes forwards
                      M569 P0.3 S1                                                          ; Z3 physical drive 0.3 goes forwards
                      M569 P0.5 S1                                                          ;    physical drive 0.5 goes forwards
                      M569 P20.0 S1 D2                                                    ; E physical drive 0.0 Driver0 tool goard goes forwards
                      
                      
                      M584 X0.1 Y0.2 Z0.0:0.4:0.3 E20.0                                      ; set drivers mapping
                      M350 X16 Y16 Z16 E16 I1                                               ; configure microstepping with interpolation
                      M92 X80.40 Y80.40 Z800.00 E717.97                                     ; set steps per mm
                      M566 X1250.00 Y1250.00 Z200.00 E1000.00                                 ; set maximum instantaneous speed changes (mm/min)
                      M203 X30000.00 Y30000.00 Z600.00 E16000.00                            ; set maximum speeds (mm/min)
                      M201 X3000.00 Y3000.00 Z200.00 E2000.00                               ; set accelerations (mm/s^2)
                      M906 X1150 Y1150 Z1050 E750 I50                                       ; set motor currents (mA) and motor idle factor in per cent
                      M84 S120                                                              ; Set idle timeout
                      
                      ; Axis Limits
                      M208 X0 Y0 Z-1 S1                                                     ; set axis minima
                      M208 X305 Y300 Z295 S0                                                ; set axis maxima
                      
                      ; Endstops
                      M574 X1 S1 P"20.io1.in"                                                ; configure active-high endstop for low end on X via pin 1.io1.in
                      M574 Y1 S1 P"io1.in"                                                  ; configure active-high endstop for low end on Y via pin io1.in
                      M574 Z1 S2
                      
                      ; Z-Probe
                      M950 S0 C"20.io0.out"                                                  ; create servo pin 1.io0.out for BLTouch
                      M558 P9 C"^20.io0.in" H3 A10 S0.005 F700 T6000                         ; set Z probe type to bltouch and the dive height + speeds old H5 F200 T4000
                      G31 P500 X22.775 Y-5.21 Z0.00                                         ; set Z probe trigger value, offset and trigger height
                      M557 X30:285 Y11:266 S25.5                                            ; define mesh grid
                      M671 X-21.018:155.191:331.4 Y-20.717:307.493:-20.717 S50              ; Z lift Point Position
                      
                      ; Heaters
                      M308 S0 A"Bett" P"temp0" Y"thermistor" T100000 B4138                  ; configure sensor 0 as thermistor on pin temp0
                      M950 H0 C"out0" T0                                                    ; create bed heater output on out0 and map it to sensor 0
                      M307 H0 B0 R0.139 C807.2 D40.94 S1.00 V24.8                           ; disable bang-bang mode for the bed heater and set PWM limit
                      M140 H0                                                               ; qmap heated bed to heater 0
                      M143 H0 S140                                                          ; set temperature limit for heater 0 to 120C
                      M308 S1 A"Vulcano" P"20.temp0" Y"thermistor" T100000 B4725 C7.060000e-8  ; configure sensor 1 as thermistor on pin temp1
                      M950 H1 C"20.out0" T1                                                    ; create nozzle heater output on 20.out0 and map it to sensor 1
                      M307 H1 B0 R2.775 C211.7:169.1 D3.87 S1.00 V24.7                      ; disable bang-bang mode for heater  and set PWM limit
                      M308 S2 A"Elektro" P"temp3" Y"thermistor" T100000 B4100               ; configure sensor 1 as thermistor on pin temp1
                      M308 S3 Y"mcu-temp" A"MCU"                                            ; configure sensor 4 as thermistor on pin e1temp
                      M308 S4 Y"drivers" A"Stepper"                                         ; configure sensor 3 as temperature warning and overheat flags on Duet
                      M308 S5 A"Raspi" P"temp2" Y"thermistor" T100000 B4138                 ; Raspi cooling Fan
                      
                      ; Fans
                      M950 F1 C"20.out2" Q500                                                  ; create fan 1 on pin 20.out2 and set its frequency
                      M106 P1 C"Hotend" S1 H1 T50                                           ; set fan 1 name and value. Thermostatic control is turned on
                      M950 F0 C"out4" Q8000                                                 ; create fan 0 on pin out4 and set its frequency
                      M106 P0 C"Bauteil1" S0 H-1                                            ; set fan 0 name and value. Thermostatic control is turned off
                      M950 F2 C"out9" Q500
                      M106 P2 H5 T50:60                                  	                  ; create fan 2 on pin out8 and set its frequency                        
                      M950 F3 C"out8" Q500
                      M106 P3 H3:4 T45:60								                      ; set fan 3 value
                      
                      M563 P0 S"Vulcano" 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
                      M955 P20.0 I10                                                       ;Accelerometer 20:0 type LIS3DH with orientation 10 samples at 1344Hz with 10-bit resolution
                      M564 S1 H0
                      M150 X1
                      
                      ; Miscellaneous
                      M575 P1 S3 B115200                            ;57600 enable Display
                      M911 S21 R22 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"                   ; set voltage thresholds and actions to run on power loss
                      M501                                                                 ; load saved parameters from non-volatile memory
                      
                      

                      Homeall.g

                      ; homeall
                      G91                       ; relative mode
                      G1 Z5 F600
                      G1 H1 Y-340 F6000         ; course home X
                      G1 Y4 F6000
                      G1 H1 Y-10 F600           ; fime home X
                      G1 Y100 F6000
                      G1 H1 X-340 F6000         ; course home Y
                      G1 X4 F5000            ; move away from the endstops
                      G1 H1 X-10 F600           ; fine home Y
                      G90                       ; back to absolute mode
                      
                      ; The following code assumes you are using a Z probe to do Z homing.
                      ; Adjust the XY coordinates in the following to place the Z probe over a suitable spot,
                      ; preferably near the centre of the bed if your Z probe supports that
                      
                      G1 X131.4 Y139.4 F6000
                      M401
                      G30
                      
                      

                      M122

                      
                      === Diagnostics === 
                      RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (SBC mode) 
                      Board ID: 08DJM-9P63L-DJ3T8-6J1DA-3SD6P-KV4H9 
                      Used output buffers: 1 of 40 (11 max) 
                      === RTOS === 
                      Static ram: 150904 
                      Dynamic ram: 62268 of which 212 recycled 
                      Never used RAM 140808, free system stack 184 words 
                      Tasks: SBC(ready,16.0%,338) HEAT(delaying,0.0%,325) Move(notifyWait,0.1%,284) CanReceiv(notifyWait,0.0%,774) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,24.0%,59) 
                      MAIN(running,59.8%,922) IDLE(ready,0.0%,29), total 100.0% 
                      Owned mutexes: HTTP(MAIN) 
                      === Platform === 
                      Last reset 04:34:37 ago, cause: reset button 
                      Last software reset at 2021-08-15 16:22, reason: User, none spinning, available RAM 137520, slot 1 
                      Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a 
                      Error status: 0x00 
                      Aux0 errors 0,0,0 
                      Step timer max interval 166 
                      MCU temperature: min 42.3, current 46.6, max 46.8 
                      Supply voltage: min 25.0, current 25.0, max 25.1, under voltage events: 0, over voltage events: 0, power good: yes 
                      12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0 
                      Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 
                      Driver 0: position 0, standstill, reads 33617, writes 19 timeouts 0, SG min/max 0/143 
                      Driver 1: position 0, standstill, reads 33621, writes 15 timeouts 0, SG min/max 0/0 
                      Driver 2: position 40000, standstill, reads 33621, writes 15 timeouts 0, SG min/max 0/0 
                      Driver 3: position 0, standstill, reads 33618, writes 19 timeouts 0, SG min/max 0/153 
                      Driver 4: position 0, standstill, reads 33618, writes 19 timeouts 0, SG min/max 0/158 
                      Driver 5: position 0, standstill, reads 33626, writes 11 timeouts 0, SG min/max 0/0 
                      Date/time: 2021-08-16 18:30:16 
                      Slowest loop: 0.79ms; fastest: 0.04ms 
                      === Storage === 
                      Free file entries: 10 
                      SD card 0 not detected, interface speed: 37.5MBytes/sec 
                      SD card longest read time 0.0ms, write time 0.0ms, max retries 0 
                      === Move === 
                      DMs created 125, maxWait 89292ms, bed compensation in use: none, comp offset 0.000 
                      === MainDDARing === 
                      Scheduled moves 2, completed moves 2, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], CDDA state -1 
                      === AuxDDARing === 
                      Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 
                      === Heat === 
                      Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 
                      === GCodes === 
                      Segments left: 0 
                      Movement lock held by null 
                      HTTP* is doing "M122" 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 
                      SBC is idle in state(s) 0 
                      Daemon is idle in state(s) 0 
                      Aux2 is idle in state(s) 0 
                      Autopause is idle in state(s) 0 
                      Code queue is empty. 
                      === CAN === 
                      Messages queued 148116, received 197133, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 176, free buffers 49 (min 48), ts 82389/82388/0 
                      Tx timeouts 0,0,0,0,0,0 
                      === SBC interface === 
                      State: 4, failed transfers: 1, checksum errors: 0 
                      Last transfer: 0ms ago 
                      RX/TX seq numbers: 64954/64954 
                      SPI underruns 0, overruns 0 
                      Disconnects: 0, timeouts: 0, IAP RAM available 0x2c810 
                      Buffer RX/TX: 0/0-0 
                      === Duet Control Server === 
                      Duet Control Server v3.3.0 Code buffer space: 4096 Configured SPI speed: 8000000Hz 
                      Full transfers per second: 35.83, max wait times: 28.7ms/0.0ms 
                      Codes per second: 0.01 
                      Maximum length of RX/TX data transfers: 2568/808
                      

                      M122 B20

                      M122 B20
                      Diagnostics for board 20: 
                      Duet TOOL1LC firmware version 3.3 (2021-06-15 16:12:58) 
                      Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1) 
                      Never used RAM 2680, free system stack 2789 words 
                      Tasks: Move(notifyWait,0.0%,153) HEAT(delaying,0.5%,107) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.1%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,8.6%,57) 
                      MAIN(running,75.8%,352) IDLE(ready,0.0%,27) AIN(delaying,15.0%,142), total 100.0% 
                      Last reset 04:44:52 ago, cause: software 
                      Last software reset data not available 
                      Driver 0: position 0, 718.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 71, reads 26324, writes 12, timeouts 6, DMA errors 0, failedOp 0x41, steps req 0 done 0 
                      Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 
                      Peak sync jitter 0/6, peak Rx sync delay 217, resyncs 0/0, no step interrupt scheduled 
                      VIN: 25.3V 
                      MCU temperature: min 44.0C, current 44.7C, max 48.8C 
                      Ticks since heat task active 126, ADC conversions started 17092120, completed 17092119, timed out 0, errs 0 
                      Last sensors broadcast 0x00000002 found 1 130 ticks ago, loop time 0 
                      CAN messages queued 203765, send timeouts 66, received 153030, lost 0, free buffers 37, min 37, error reg 100000 Last cancelled message type 4512 dest 127 
                      dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0 
                      Accelerometer detected: yes, status: 00 
                      I2C bus errors 0, naks 0, other errors 0
                      

                      M98 P"config.g"

                      M98 P"config.g"
                      Accelerometer 20:0 with orientation 10 samples at 1344Hz with 10-bit resolution
                      
                      1 Reply Last reply Reply Quote 0
                      • Heartleander81undefined
                        Heartleander81
                        last edited by Heartleander81

                        ; config-override.g file generated in response to M500 at 2021-01-25 11:01
                        
                        ; Z-Probe
                        G31 P500 Z4.35    ; for trigger height
                        
                        1 Reply Last reply Reply Quote 0
                        • Heartleander81undefined
                          Heartleander81 @Phaedrux
                          last edited by

                          @phaedrux

                          Ok I hope that is all what you need

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

                            @heartleander81 said in Isusses after prime:

                            G32 G29 S1 P "hightmap.csv"

                            What do you have in bed.g?

                            Have you tried with mesh compensation disabled?

                            Z-Bot CoreXY Build | Thingiverse Profile

                            Heartleander81undefined 1 Reply Last reply Reply Quote 0
                            • Heartleander81undefined
                              Heartleander81 @Phaedrux
                              last edited by

                              @phaedrux

                              ; bed.g
                              ; called to perform automatic bed compensation via G32
                              ;
                              ; generated by RepRapFirmware Configuration Tool v3.1.4 on Wed Aug 26 2020 16:14:58 GMT+0200 (Mitteleuropäische Sommerzeit)
                              M561 ; clear any bed transform
                              G29 S2 ; clear bed high map
                              
                              G28 ; home
                              M401
                              G30 P0 X25.159 Y16.257 Z-99999 ; probe near a leadscrew 
                              G30 P1 X25.159 Y266.257 Z-99999 ; new
                              G30 P2 X285.159 Y266.257 Z-99999 ; x154.53 old
                              G30 P3 X285.159 Y16.257 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors 
                              G28Z
                              M402
                              
                              

                              If I edit the G-code that it does everything at z-height, say 5mm, then it's the same with the X-axis. runs on stops - extruder is doing something - X axis continues to run. As mentioned, if I delete or comment out the first Retract G1 E-0.6000 F1200 from the sliced ​​file, there are no problems with the X axis or the extruder

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

                                @heartleander81 said in Isusses after prime:

                                if I delete or comment out the first Retract G1 E-0.6000 F1200 from the sliced ​​file, there are no problems with the X axis or the extruder

                                This still very much sounds like it's in absolute extrusion mode and it's pausing while it's trying to move the extruder to undo all of the previous extrusion commands.

                                Z-Bot CoreXY Build | Thingiverse Profile

                                Heartleander81undefined 1 Reply Last reply Reply Quote 0
                                • Heartleander81undefined
                                  Heartleander81
                                  last edited by

                                  I apologize if my sentences read clumsily or unkindly. I work with google translators because my english is very bad. I am very, very grateful for the help that I am getting because I am slowly becoming desperate.

                                  1 Reply Last reply Reply Quote 0
                                  • Heartleander81undefined
                                    Heartleander81 @Phaedrux
                                    last edited by

                                    @phaedrux
                                    ok i understand that and is understandable. but why is he doing this? in the start code it runs great in the M83 and after that I no longer give an M82 command. I switched Simplify3D to M83 and the sliced ​​code also looks like it.

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

                                      @heartleander81 said in Isusses after prime:

                                      M955 P20.0 I10

                                      Can you try commenting out the accelerometer command?

                                      Z-Bot CoreXY Build | Thingiverse Profile

                                      Heartleander81undefined 2 Replies Last reply Reply Quote 0
                                      • Heartleander81undefined
                                        Heartleander81 @Phaedrux
                                        last edited by

                                        @phaedrux
                                        Have I do yesterday. But with M82.

                                        I can try it in 30 min.

                                        1 Reply Last reply Reply Quote 0
                                        • Heartleander81undefined
                                          Heartleander81 @Phaedrux
                                          last edited by

                                          @phaedrux

                                          Is the same

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

                                            your video is very short and a little confusing to me. It looks like it goes into slow motion? Is that to show the stuttering? Can you upload a new video that's a bit longer and doesn't go to slow mo? Describe for us exactly at what point each piece of gcode is executing from the time you hit print to the time you see the problem.

                                            Z-Bot CoreXY Build | Thingiverse Profile

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