So when printing models one at a time is there a way to make sure the pause location clears the tallest completed part? Or is it just easier to set the pause location accordingly?
and if thats the case is there a way to have custom gcode in start files that can comment out current pause location and uncomment the sequence location? Or is that just something i would have to do manually in the system files before printing?
Hello, So im commissioning my ratrig build for the first time and Im having an issue with one of the xy motors. I'm unsure if 'stalling" is the proper term for the issue but it just makes a horrendous noise and doesn't move the printhead in its diagonal direction when I individually command the motor for "Y". When i test the "X" motor it moves nice and smooth. Ive switched the motor mapping in the config and the issue swaps to the "x" diagonal direction. This is my first corexy build so im not sure how to properly troubleshoot this issue. Ive tried googling for a solution but im not having much luck. Any help would be much appreciated!
config to see if im overlooking something.
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"IWS RATRIG" ; set printer name
M669 K1 ; CoreXY
G21 ; Set Units to Millimeters
; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet
; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S1 ; physical drive 0.2 goes forwards
M569 P0.3 S0 ; physical drive 0.3 goes backwards
M569 P0.4 S0 ; physical drive 0.4 goes backwards
M569 P0.5 S1 ; physical drive 0.5 goes forwards
M584 X0.4 Y0.3 Z0.0:0.1:0.2 E0.5 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z800.00 ; set steps per mm
M906 X1600 Y1600 Z1600 I30 ; set motor currents (mA) and motor idle factor in per cent -- safe for Duet 3 mini 5+
M84 S30 ; Set idle timeout
M566 X400.00 Y400.00 Z6.00 E300 P1 ; set maximum instantaneous speed changes (mm/min)
M203 X10800.00 Y10800.00 Z1000.00 E7200 ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z100.00 E10000 ; set accelerations (mm/s^2)
; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X510 Y500 Z450 S0 ; set axis maxima
; Endstops
M574 X1 S1 P"io0.in" ; configure active high endstops
M574 Y2 S1 P"io1.in" ; configure active high endstops
M671 X-4.5:250:504.5 Y-4.52:505:-4.52 S5 ; define positions of Z leadscrews or bed levelling screws
M557 X50:450 Y50:450 P5 ; define 5x5 mesh grid
; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"Bed" ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 Q11 ; create bed heater output on out5 and map it to sensor 0, lower switching frequency to 11Hz
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S110 ; set temperature limit for heater 0 to 110C
;; Run Bed PID Tune!! Below is an example for a 300x300 bed
M307 H0 R0.366 K0.216:0.000 D8.44 E1.35 S1.00 B0
; Fans
M950 F0 C"out5" Q500 ; create fan 0 on pin out5 and set its frequency
M106 P0 C"Layer Fan" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"out3" Q500 ; create fan 1 on pin out3 and set its frequency
M106 P1 C"Hotend Fan" S1 H1 T45 ; set fan 1 name and value. Thermostatic control turned on for Hotend
M950 F2 C"out6" Q500 ; create fan 2 on pin out6 and set its frequency
M106 P2 C"Layer Fan 2" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off
; Tools
M563 P0 D0 H1 F0:2 ; 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
M950 H1 C"out1" T1 ; create nozzle heater output on out2 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S250 ; set the maximum temperature in C for heater
; EVA 2 / ORBITER2.0 / RAPIDO
M92 E690 ; set extruder steps per mm, 0.9 angle/step (LDO Pancake)
M906 E1200 I10 ; set extruder motor current (mA) and idle factor in per cent
M308 S1 P"temp1" Y"pt1000" ; configure sensor 1 as PT1000 on pin temp1
;; Run Heater PID Tune!!
M307 H1 R4.558 K0.565:0.162 D5.19 E1.35 S1.00 B0 V24.0
; Z-Probe
;; Inductive Probe
; M558 P5 C"!io3.in" H5 F400 T5000 ; set Z probe type to unmodulated and the dive height + speeds
; G31 P500 X-30 Y-15 Z0.20 ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed
;; BLTouch
M950 S0 C"io2.out" ; Create a servo pin on io2
M558 P9 C"io2.in" H5 F240 T10800 A5 ; set Z probe type to unmodulated and the dive height + speeds
G31 P25 X-28.00 Y-13.00 Z0.90 ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed
; Select default tool
T0
; Pressure Advance
M572 D0 S0.10
M501
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.0 (2022-03-15 18:59:15) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 0Z3DT-2N6KL-K65J0-409NA-27X1Z-77YJ0
Used output buffers: 3 of 40 (14 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 110492 of which 28 recycled
Never used RAM 27436, free system stack 190 words
Tasks: NETWORK(ready,14.9%,246) HEAT(notifyWait,0.0%,356) Move(notifyWait,0.0%,292) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,372) CanClock(delaying,0.0%,339) TMC(delaying,1.2%,81) MAIN(running,83.0%,428) IDLE(ready,0.1%,29) AIN(delaying,0.8%,264), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:05:49 ago, cause: software
Last software reset at 2023-02-23 08:52, reason: User, GCodes spinning, available RAM 27508, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 350119, completed 350119, timed out 0, errs 0
Step timer max interval 1461
MCU temperature: min 39.2, current 40.8, max 40.9
Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 31789, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 31789, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 31789, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 22, reads 31786, writes 12, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 22, reads 31786, writes 12, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 31789, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 19, reads 31789, writes 9, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2023-02-23 08:58:33
Cache data hit count 666457839
Slowest loop: 8.17ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 3, maxWait 293588ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 3, completed 3, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== 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
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 3149, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 1750/0/0
Tx timeouts 0,0,1749,0,0,1398 last cancelled message type 4514 dest 127
=== Network ===
Slowest loop: 16.97ms; fastest: 0.00ms
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 0
WiFi firmware version 1.26
WiFi MAC address e8:68:e7:e5:fa:fe
WiFi Vcc 3.38, reset reason Power up
WiFi flash size 2097152, free heap 23120
WiFi IP address 192.168.0.38
WiFi signal strength -42dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
@dc42 I dont think its actually skipping steps though. I really cant pinpoint the noise if its the hob gears or in the housing...
The tension arm never moves and the visible bearing doesnt bounce. And im also not seeing any hiccups in the print.
I went through teaching techs calibration site twice getting it dialed in and my e steps are spot on. I still had to dial the flow back to 72% in my slicer. But It could just be the rapidos long melt zone and having to print PETG slower than pla. So im not sure if thats some underlying issue or anything but everything is printing very well...
Maybe im just being paranoid about burning it out. Ive been monitoring it with a FLIR thermal camera and i havent seen it get above 92c ... generally hangs out around 85- 86c.
@phaedrux your a wizard man. totally a wire in the drag chain... as soon as the hotend moves to the far side of the bed the wire for the fan is bent and when it straightens out in the chain it comes back on. Thanks!
Ya it seems like m107 in the g code is turning off fan1 for some reason....
man what a frustrating issue....
It was printing flawlessly when I printed a part with a small first layer...
noticed the issue yesterday when i had a part with a large base and i had a jam by layer 2 because of heat creep 
;FLAVOR:RepRap
;TIME:26567
;Filament used: 97.598m
;Layer height: 0.5
;MINX:8.32
;MINY:11.374
;MINZ:0.5
;MAXX:323.257
;MAXY:313.949
;MAXZ:196.5
;Generated with Cura_SteamEngine main
T0
M190 S95
M104 S257
M109 S257
M82 ;absolute extrusion mode
G28 ; home all axes
G1 X5 Y10 Z0.2 F3000 ; get ready to prime
G92 E0 ; reset extrusion distance
G1 X160 E25 F600 ; prime nozzle
G1 X180 F5000 ; quick wipe
M83 ;relative extrusion mode
G10
;LAYER_COUNT:393
;LAYER:0
M107
M204 T500
M566 X540 Y540
G0 F12000 X33.244 Y38.514 Z0.5
G0 X26.042 Y51.51
M204 P700
;TYPE:SKIRT
G11
G1 F2700 E0.32429
G1 F1500 X26.208 Y50.643 E0.09371
G1 X26.346 Y50.005 E0.06929
G1 X26.583 Y49.023 E0.10724
G1 X26.742 Y48.469 E0.06118
G1 X27.034 Y47.602 E0.09711
G1 X27.287 Y46.895 E0.07971
G1 X27.453 Y46.486 E0.04686
G1 X27.893 Y45.518 E0.11287
G1 X28.217 Y44.849 E0.07891
G1 X28.412 Y44.484 E0.04393
G1 X28.935 Y43.588 E0.11013
G1 X29.309 Y42.981 E0.07568
G1 X29.554 Y42.617 E0.04658
G1 X30.143 Y41.815 E0.10563
G1 X30.617 Y41.196 E0.08276
G1 X30.893 Y40.866 E0.04567
G1 X31.575 Y40.112 E0.10792
G1 X32.14 Y39.515 E0.08725
G1 X32.492 Y39.176 E0.05188
G1 X33.244 Y38.514 E0.10635
G1 X33.755 Y38.079 E0.07124
G1 X34.018 Y37.869 E0.03573
G1 X34.373 Y37.603 E0.04709
G1 X35.491 Y36.818 E0.14501
G1 X35.848 Y36.588 E0.04508
G1 X36.341 Y36.298 E0.06072
G1 X37.413 Y35.704 E0.1301
G1 X37.714 Y35.549 E0.03594
G1 X37.957 Y35.434 E0.02854
G1 X38.83 Y35.051 E0.1012
G1 X39.457 Y34.789 E0.07214
G1 X39.729 Y34.684 E0.03095
G1 X40.128 Y34.545 E0.04485
G1 X40.82 Y34.326 E0.07705
G1 X41.556 Y34.105 E0.08157
G1 X41.841 Y34.028 E0.03134
G1 X42.256 Y33.931 E0.04524
G1 X43.048 Y33.768 E0.08584
G1 X43.703 Y33.643 E0.07079
G1 X44.016 Y33.593 E0.03365
G1 X44.471 Y33.534 E0.0487
G1 X47.181 Y33.137 E0.29075
G1 X49.818 Y32.674 E0.28421
G1 X52.457 Y32.136 E0.2859
G1 X55.019 Y31.537 E0.2793
G1 X57.624 Y30.847 E0.28606
G1 X60.224 Y30.082 E0.2877
G1 X62.718 Y29.27 E0.27842
G1 X65.282 Y28.353 E0.28906
G1 X67.75 Y27.391 E0.28118
G1 X70.222 Y26.347 E0.28485
G1 X72.647 Y25.241 E0.28293
G1 X75.082 Y24.045 E0.28798
G1 X77.408 Y22.821 E0.27901
G1 X79.765 Y21.493 E0.28718
G1 X82.042 Y20.125 E0.28198
G1 X84.288 Y18.687 E0.2831
G1 X86.513 Y17.172 E0.28574
G1 X89.167 Y15.242 E0.34835
G1 X89.438 Y15.057 E0.03483
G1 X90.336 Y14.486 E0.11296
G1 X90.913 Y14.138 E0.07153
G1 X91.287 Y13.933 E0.04527
G1 X92.302 Y13.427 E0.12039
G1 X92.9 Y13.147 E0.07009
G1 X93.181 Y13.025 E0.03252
@jay_s_uk crud sorry I already put everything back together before i saw the sd card thing...
but after inspecting the connectors and making sure polarity is correct and continuity is present for the proper wires to each fan...
put everything back together and it the hotend fan is now observing the thermostatic control....
but still running into the issue of it starting and stopping at the beginning of a print.
would it still be helpful to remove the sd card and power up the board?
@jay_s_uk Yes Ill open her up and check it out.
part cooling fan operates as it should and responds to the DWC. ... however the tool fan is also listed on the DWC and doesnt respond to the controls... they both slide together when i attempt to manipulate them and the hotend fan wont turn off even when cool and i ask it to with m107 (not sure if it would even respond to that or not)
@jay_s_uk Would it still always be on except for when its printing?
It ignores the thermostatic control and is just always on.
Then when I start a print It only starts and stops on the first few layers then goes back on full time. Its like the print file m107 is trying to kill my hotend fan for the first few layers at the same time its telling my part cooling fan to be off until layer 3.
@jay_s_uk thank you! I knew I had just been staring at it too long and was glossing over something simple. I’ll make sure it works in the morning.
So Im sorry to be posting so much. I just seem to be having issues after migrating to the newest firmware.
So my fan seems to come on and off during the first few layers. I did some searching and have seen others with the same issue and it looks like my hotend fan isnt properly defined to T0.
Ive tried a few changes but I cant seem to iron it out with anything i see to try and change. can anyone spot my issue in my config?
; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.13 on Sun Sep 18 2022 21:10:20 GMT-0400 (Eastern Daylight Time)
; General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Ender 5 Plus IWS" ; 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 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S0 ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.11 Y80.03 Z801.62 E692.9 ; set steps per mm
M556 S100 X0.16 ; skew correction
M566 X900.00 Y900.00 Z12.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X15000.0 Y15000.0 Z300.00 E7200 ; set maximum speeds (mm/min)
M201 X800.00 Y800.00 Z20.00 E3000 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E1100 I10 ; 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 X350 Y350 Z400 S0 ; set axis maxima
; Endstops
M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z
; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F180 T12000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X31 Y11 Z2.503 ; set Z probe trigger value, offset and trigger height
M556 S50 X0 Y0 Z0 ; set orthogonal axis compensation parameters
M557 X31:318 Y31:318 S21.2 ; 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 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S280 ; set temperature limit for heater 0 to 280C
M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.060000e-8 R4700 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C
; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S255 H1 T45 ; set fan 1 value. Thermostatic control is turned on
; Tools
M563 P0 S"Nozzle" D0 H1 F1 ; 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
M591 D0 P2 C3 S1 ; Filament Run out sensor
G29 S1 ; Load mesh bed
; Pressure Advance Presets
; CF PETG
; 0.8 Nozzle
M572 D0 S0.015 ; set pressure advance
;Retraction
M207 S0.8 R0.78 F3600 Z0.00 ; firmware retraction
; Miscellaneous
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
@dc42 so what would be my next step if im experiencing an extruder click every 30 seconds or so? Lower it?
@phaedrux I'm using your tuning macros from github.
I followed your setup instructions and found my settings via a retraction tower test ... Then updated the reported values to my config. So it has retraction settings set to .8/.78 @ 45mm/s in my m207 down below the custom settings.
And ive matched that everywhere.. in cura and also edited the "return retraction settings to default" macro to those settings as well.
and for whatever reason after that retraction tower test whenever i start a new print my reported retraction value is .8/ 1.78 @ 60mm/s
So i have to use the reset macro and then then other retraction macros to get back to my preferred setting...
I can get it back to my settings fairly quickly but Im trying to not have to navigate my macros as fast as i can while it's laying the first layer down.
@phaedrux so any idea whats causing the github macros to additively affect my retraction distances on the next print? Do they overwrite my config distances? or add to it? I found a good distance on a retraction test print. Then when i updated my config with the reported values on the next print my unretract distance was a combination of all the adjustments i made on the test print and instead of being .78mm it was 4.78mm.
do i need to use the reset retraction macro after i make the config change?
@phaedrux I did that but didnt realize you also need to still check the box for enable retraction in the cura settings. Im not sure if the numbers are arbitrary or if they affect anything relatively. but it is indeed working now... Im just almost to 3mm retraction to my .8 nozzle and still getting some oozing.
im just having trouble understanding the relationship of cura settings for retraction and acceleration compared to firmware settings... Does having everything enabled in the firmware overwrite curas generated values? or do i need to go through and match my firmware settings with everything in cura?
Like there are a whole lot of printer settings in that plugin that dont match my printer at all... Does the plugin start throwing anything off if its installed and not changed? or does having the settings all hidden except for the firmware retraction keep them from interfering?
