Extruder stops at the same position in the GCode

sn0w1995

Hello all,

Recently I have a strange problem that I have not been able to solve. I have a Renkforce RF2000, which is equipped with two extruders. The extruder in question is attached to the side of the printer and does not move when printing. I want to print fiber-reinforced samples, so I generate the Gcode myself in a program I wrote, which has always worked well so far.
Currently I want to print tensile specimens with fiber reinforcement.
In my problem, I am printing three samples side by side. From a certain layer, where fiber strands are inserted, fiber strands are surrounded by normal plastic. The printer does the same for the first sample and then switches to the second and from that point on the extruder stops spinning. The extruder also can no longer be controlled to pull back or extrude filament. Only when I restart the printer it works again, but breaks off at the same point during printing.

The previous 20 layers everything works fine. The wiring also looks good. I am using firmware 2.0.5.

Does anyone know how I fix the problem?

Thanks in advance!

jay_s_uk

@sn0w1995 can you post a gcode example of where it happens?

sn0w1995

@jay_s_uk

Attached is exactly the layer. The left outlines are printed. Then the print head moves to the right side to print these outlines as well and from this point on the extruder motor can no longer be controlled.

Duet Example.gcode

Phaedrux

Can you gather the results of M122 when the motor has stopped?

Does it still happen on a dry run without filament?

sn0w1995

@Phaedrux

Here is the M122 right after the motor stopped working (I can only post part of the code because otherwise the post will be reported as spam.):

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SJ-6J1DD-3SJ6P-TBY3G
Used output buffers: 1 of 24 (7 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93568 of which 0 recycled
Exception stack ram used: 472
Never used ram: 11320
Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3728) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:05:07 ago, cause: power up
Last software reset at 2023-01-06 17:46, reason: Unknown, spinning module Platform, available RAM 11132 bytes (slot 2)
Software reset code 0x00b0 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x20001ff4 Task 0x5754454e
Stack: 0040c0c1 0040c0c6 21000000 00000000 40ba7c00 00000000 00000000 43910000 41800000 3e178897 3e1cd04f be07a50f 421dd6a9 00000000 47688900 37d33333 4354c416 00000000 40853000 80000010 0040c0bd 10000000 e000ed04
Error status: 0
Error status: 0

Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 17.9, current 28.9, max 29.0
Supply voltage: min 23.9, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/1023
Driver 1: ok, SG min/max 0/115
Driver 2: ok, SG min/max 0/167
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2023-01-07 09:20:51
Cache data hit count 851506708
Slowest loop: 247.02ms; fastest: 0.06ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 157, MinFreeDm: 106, MaxWait: 125029ms
Bed compensation in use: mesh, comp offset 0.000
=== DDARing ===
Scheduled moves: 548, completed moves: 539, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.4

sn0w1995

@sn0w1995

I can't post the rest of the code, unfortunately, because of spam protection. I have packed the code into a txt file.

M122.txt

I have also connected another motor and let it run freely and there the same problem occurs.

Edit: I also tried printing the top layers to check if it has something to do with the z-height, but there the problem does not occur.

Phaedrux

I've upvoted some of your posts so hopefully you can post more now. Also make sure you've validated your email address from the forum signup process.

sn0w1995

@Phaedrux
Thank you!

I printed a similar sample today and I had no problems with these. It must have something to do with the layer geometry. I still can't explain the error.

I have attached my config.

; General preferences
G90                                                ; send absolute coordinates...
M83                                                ; ...but relative extruder moves
M550 P"Renkforce Umbau Markforged"                  ; set printer name

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

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

M584 X0 Y1 Z2 E3:4                                 ; set drive mapping
M350 X16 Y16 Z16 E16:16 I1                         ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z1285.00 E115.00:60.00            ; set steps per mm


M566 X600.00 Y600.00 Z12.00 E120.00:120.00         ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z1800.00 E1200.00:1200.00 ; set maximum speeds (mm/min)
;M201 X3000.00 Y3000.00 Z250.00 E250.00:250.00      ; set accelerations (mm/s^2)
M201 X4000.00 Y4000.00 Z250.00 E1000.00:1000.00      ; Test 06 11 2021
M906 X1500 Y1500 Z1500 E800:800 I30                   ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                            ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                                   ; set axis minima
M208 X195 Y195 Z130 S0                             ; set axis maxima


; Schrittweite Korrektur
M579 X0.958 Y0.958


; Endstops
M574 X1 Y1 S0                                      ; set active low and disabled endstops
M574 Z1 S2                                         ; set endstops controlled by probe

; Z-Probe
M307 H3 A-1 C-1 D-1                                ; disable heater on PWM channel for BLTouch
M558 P9 H5 F120 T6000                              ; set Z probe type to bltouch and the dive height + speeds
G31 P25 X7 Y35.5 Z3.3     		              ; set Z probe trigger value, offset and trigger height 3,5-3,55 3.65 27.10.21,,    Z2.85 am 19.09.22
M557 X7:207 Y40:256.0 S20                            ; define mesh grid

; Heaters
M307 H0 B0 S1.00                                   ; disable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B3950 R4700                        ; set thermistor + ADC parameters for heater 0
M143 H0 S120                                       ; set temperature limit for heater 0 to 120C
M305 P1 T100000 B3950 R4700                        ; set thermistor + ADC parameters for heater 1
M143 H1 S280                                       ; set temperature limit for heater 1 to 280C
M305 P2 T100000 B3950 R4700                        ; set thermistor + ADC parameters for heater 2
M143 H2 S280                                       ; set temperature limit for heater 2 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:2 T45                        ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Tools
M563 P0 S"Filamentextruder" 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
M563 P1 S"Faserextruder" D1 H2 F0                  ; define tool 1
G10 P1 X18.51 Y0 Z0				;Änderung vom 19.09.2022 - Test Faser offset
;G10 P1 X20 Y0 Z0                                   ; set tool 1 axis offsets
G10 P1 R0 S0                                       ; set initial tool 1 active and standby temperatures to 0C

; Custom settings
M307 H5 A-1 C-1 D-1				   ; disable heater on PWM channel for Servo

; Miscellaneous
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

dc42

@sn0w1995 your M122 report shows that the machine has stalled without completing all the queued movement. Unfortunately the firmware you are running is quite old and the diagnostics in that version provide insufficient detail to diagnose the problem further. Please consider upgrading to version 3.4.5 firmware. This will require changes to your config.g file. See https://docs.duet3d.com/User_manual/RepRapFirmware/Migration_RRF2_to_RRF3.

Phaedrux

If you do decide to update the firmware...

If you still have access to DWC. Upload these zip files, one at a time in the system tab. Don't extract them first. Reboot after each. Use M115 in the gcode console to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.4.5/Duet2and3Firmware-3.4.5.zip

That will get your firmware and DWC up to date.

You can see the change logs here:
https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x

For your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
https://configtool.reprapfirmware.org/Start

Backup your existing config files in the sys folder in case you want to switch back to RRF2. It’s easy to switch back and forth, just upload the zip file for the version you want and then upload your config files.

These documents will come in handy during the conversion.
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
https://docs.duet3d.com/en/User_manual/RepRapFirmware/Migration_RRF2_to_RRF3
https://docs.duet3d.com/en/User_manual/Reference/Gcodes