@jay_s_uk Ah....yes I may simply have my signage inverted....let me try that!
.....goes to try it....
Yes, that was it! How embarrassing! Thanks for the steer though!
@jay_s_uk Ah....yes I may simply have my signage inverted....let me try that!
.....goes to try it....
Yes, that was it! How embarrassing! Thanks for the steer though!
@jay_s_uk Thanks
I defined the Z probe offset as follows (also in config.g):
G31 P500 X40 Y20 Z0.53 ; set Z probe trigger value, offset and trigger height
At the endstop position (X=0) the nozzle is just on the edge of the bed - however this puts the Z-probe off the bed by ~40mm
I have a coreXY printer with a duet2 wifi board
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.1 (2022-06-01)
Duet WiFi Server Version: 1.23
The Z probe is inductive, and offset by 40mm in the X direction from the hot-end
I can home all axes fine - however, if I try to run G29 - bed compensation, the first probe point the head moves to shows up in DWC as X=10, Y=30
Unfortunately this puts the inductive probe 30mm off the edge of the bed - so the head crashes
I do not have a bed.g file
In the config.g I have:
M557 X50:250 Y50:250 S20
I thought this would mean the first probe point, when I ran G29, would be X=50, Y=50...any idea why it is not?
@o_lampe so far that is looking good....
I moved from a geared extruder that was relay hard to thread to this one - but didn't increase the current, despite the obvious need to have more torque!
Fingers crossed....
@gixxerfast Yes - the video was with no hot-end
Interestingly, I have found that post my changes today (replacing extruder mechanism and motor, checking calibration) , it can extrude into the air fine. I also shortened the bowden tube path slightly.
On a test extrusion, once it starts skipping, it will keep doing so, but a little hand assistance and it will then work fine. So it seems like once it starts to jam, it stays that way until released.
M906 gives me:
Motor current (mA) - X:800, Y:800, Z:800, E:800, idle factor 30%
It feels like there may be room to increase this...? The motot has a niminal maximum of 1.8A:
SL42STH40-1684A 1.8A
My entire config is:
; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu Apr 23 2020 19:55:13 GMT+0100 (British Summer Time)
; General preferences
G90 ; send absolute coordinates...
G21 ; use mm
M83 ; ...but relative extruder moves
M550 P"TronXY X5SA" ; set printer name
M669 K1 ; select CoreXY mode
; Network
M552 S1 ; enablee 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 forwards
M569 P3 S1 ; Extruder physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z1500.00 E100 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E100.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1500.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Axis Limits
M208 X00 Y00 Z0 S1 ; set axis minima
M208 X310 Y310 Z380 S0 ; set axis maxima
; Endstops
M574 X1 Y1 S0 ; set active low endstops
M574 Z1 S2 ; set endstops controlled by probe
; Filament Run Out Sensor
M591 D0 P1 C4 S1 ; Filament runout Sensor for Extruder E0 on E1 Endstop input P1 = signal HIGH.
; Z-Probe
M558 P5 I1 H5 F120 T6000 ; set Z probe type to inductive and the dive height + speeds
G31 P500 X20 Y20 Z0.53 ; set Z probe trigger value, offset and trigger height
M557 X90:280 Y90:280 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 B4138 R4700 ; set thermistor + ADC parameters for heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C
; Fans
M106 P2 S0 I0 F500 H-1 ; set fan 2 as part cooling fan
M106 P0 T45 S0.7 H1 ; set fan 0 as our hotend fan
; Tools
M563 P0 D0 H1 F2 ; define tool 0 uses part cooling fan 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
@gixxerfast said in Problems with direct drive extruder skipping:
wheel eats into the aluminum quite rapidly since for many of then there's no spacer underneath (I could remember this wrongly since it was a while since I used this type). I would checkout the idler wheel and arm before looking any further.
Ok. I have:
replaced the extruder with an idemntical type
Recalibrated extrtuder
Re-run bed calibration
Still getting a lot of extruder skipping. I wonder if the nozzle could be more blocked than it seems (it is certainly working, but maybe the pressure needed is higher than it should be...?)
I have an old titan extruder somewhere....perhaps I could try that. Should give me more torque...
@rjenkinsgb thanks. Yes, it moves freely with just a very slight but consistent "judder" as it turns.
I have checked the wiring, which seems ok, and will double check the mechanics later today.
I do have a spare motor as well if it comes to that
Thanks - I'll take a look tonight. I tried the tension much looser without much effect, but will try again.
When you say the wrong way around, how do you mean?
The motor turns, pushes the filament up from below and into the Bowden tube, in the direction of the hot end (when it's connected)
Thanks!
I have an X5SA printer with a Duet board with the following paramaters:
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.05.1 (2020-02-09b1)
WiFi Server Version: 1.23
Web Interface Version: 1.22.6
I am having an odd problem with my extruder.
Even when extruding filament into thin air - no hot-end at all - I am getting quite severe skipping, causing problems printing - see this video:
https://photos.app.goo.gl/zxSyeezumrJqYFRr7
The smallest assist from me from below and it will move slowly, but any idea what the problem may be? The extruder is direct drive - could that be a problem? But the torque required here should be minimal....I have adjusted the tension between the gear and the runner wheel without obvious effect
My steps per mm is:
M92 X80.00 Y80.00 Z1500.00 E100 ; set steps per mm
This seemed to be working - but since calibrating, the knocking has now become much worse
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SJ-6JKD4-3S86Q-TAX7F
Used output buffers: 3 of 24 (9 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93252 of which 304 recycled
Exception stack ram used: 648
Never used ram: 11156
Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3728) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 01:46:12 ago, cause: software
Last software reset at 2021-10-28 18:55, reason: User, spinning module GCodes, available RAM 11156 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 109.6ms, max retries 0
MCU temperature: min 30.2, current 34.1, max 34.4
Supply voltage: min 23.2, current 24.0, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/204
Driver 1: standstill, SG min/max 0/234
Driver 2: standstill, SG min/max 0/127
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2021-10-28 20:41:35
Cache data hit count 4294967295
Slowest loop: 26.43ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 95, MaxWait: 336963ms
Bed compensation in use: mesh, comp offset 0.321
=== DDARing ===
Scheduled moves: 11679, completed moves: 11679, 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
@PaulHew thanks
Mechanically and electrically all now works. Something I suspect though is wrong in my config still. My 20mmcalibration cube gets this far:
Which doesn't look great, before reliably lifting from the bed entirely. I have set Z quite a few times, and checked the bed temperature. This isn't a problem I had with the old stock board, so I suspect the issue is with my config....perhaps something to do with my extruder settings:
https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+4:+Calibration/40#s165
I'll double check them. Will get there though...try again tomorrow!
Thanks - that worked
And the M280 issue is also resolved - I had a deploy and retract probe file, but the inductive probe is always in place - so this was referring to a servo that did not exist
Cheers!
@PaulHew Cheers - I'll give it a go first thing in the morning
I think I am getting there - a "home z" now works, as does a "auto bed level compensation"
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu Apr 23 2020 19:55:13 GMT+0100 (British Summer Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G90 ; absolute positioning
G1 X50 Y50 F6000 ; go to first probe point
G30 ; home Z by probing the bed
; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning
However, a "homeall" complains that I have homes insufficient axis (even if run just after a sucesful home X and Y)
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu Apr 23 2020 19:55:13 GMT+0100 (British Summer Time)
G91 ; relative positioning
G1 H1 X-335 Y-335 ; move quickly to X or Y endstop and stop there (first pass)
G1 X5 Z5 F6000 ; go back a few mm
G1 H1 X-335 F360 ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-335 F360 ; move slowly to Y axis endstop once more (second pass)
G1 X50 Y50 ; Move z probe over bed
G1 H1 Z-405 ; then move slowly to Z axis endstop
G1 H1 Z5 F6000 ; lift Z relative to current position
G1 H1 Z-335 F1800 ; move Z down stopping at the endstop
G90 ; absolute positioning
In addition, the M280 z probe error still occurs - but from what I had seen of the guide you suggested, I had set the probe up as a type 5, which I think is correct....
It's an NPN inductive probe. It seems to trigger OK at present when I use "z home" - but "home all axis" causes dthe probe to crash into the bed when it gets to Z - so "home all" doesn't seem to make use of the "homez" gcode....
; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu Apr 23 2020 19:55:13 GMT+0100 (British Summer Time)
; General preferences
G90 ; send absolute coordinates...
G21 ; use mm
M83 ; ...but relative extruder moves
M550 P"TronXY X5SA" ; set printer name
M669 K1 ; select CoreXY mode
; 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 forwards
M569 P3 S0 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z1200.00 E420.00 ; set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Axis Limits
M208 X00 Y00 Z0 S1 ; set axis minima
M208 X310 Y310 Z380 S0 ; set axis maxima
; Endstops
M574 X1 Y1 S0 ; set active low endstops
M574 Z1 S2 ; set endstops controlled by probe
; Filament Run Out Sensor
M591 D0 P1 C4 S1 ; Filament runout Sensor for Extruder E0 on E1 Endstop input P1 = signal HIGH.
; Z-Probe
M558 P5 I1 H5 F120 T6000 ; set Z probe type to inductive and the dive height + speeds
G31 P500 X20 Y20 Z5.0 ; set Z probe trigger value, offset and trigger height
M557 X15:290 Y15:290 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 B4138 R4700 ; set thermistor + ADC parameters for heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C
; Fans
M106 P2 S0 I0 F500 H-1 ; set fan 2 as part cooling fan
M106 P0 T45 S0.7 H1 ; set fan 0 as our hotend fan
; Tools
M563 P0 D0 H1 F2 ; define tool 0 uses part cooling fan 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
Ah - some progress:
I updated my homez.g to be similar to yours above, and can now home the Z fine - though I do get the following error:
M280: Invalid servo index 3 in M280 command
"Home All" though still crashes the z into the bed. I haven't yet worked out the relationship between the homez.g, homey.g, homez.g, and homeall - It doesn't look like "homeall.g" simply calls he first three in sequence....
My config.g for z probe is:
; Z-Probe
M558 P5 I1 H5 F120 T6000 ; set Z probe type to inductive and the dive height + speeds
G31 P500 X50 Y50 Z5.0 ; set Z probe trigger value, offset and trigger height
M557 X15:290 Y15:290 S20 ; define mesh grid
And M115 gives me:
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-02-09b1
I had tried some G31 variations
The duet uses the offset here to set the X and Y position when the endstops are hit - but in my case this puts the Z sensor off the edge of the board - so after homing X and Y it will need to move in bot h X and Y before homing Z...
Hi,
I'm wiring a duet2 wifi up to an X5SA
All sensors and probes now seem to be working (though I think I killed one PWN fan channel...luckily I only need two!)
However, when the print head is at X=0, Y=0, the Z probe is off the side of the bed - which means when I do a home, the Z probe never detects
Does anyone know the appropriate gcode to tell the Z probe to home with an offset of say Z=50, Y=50?
M558 P5 X50 Y50 F500 T5000 H3
But this doesn't seem to have any effect...