@dc42 / community unfortunately I am still having issues with this. Tool changes occur with movements in the physical X axis direction and Z direction and are very crash prone as the difference in z offsets increases. Can anybody share a solution to what I'm sure is a silly mistake somewhere on my part? Anybody able to share working IDEX configs with larger Z offsets between XUVW carriage tools?
Posts made by DocCox
-
RE: IDEX U axis z-offset crashing into bed
-
RE: half-assed web UI update put printer down. Need help!
@vlad
Shame
Software's hard, and in this instance customer service looks to be way harder.
Its not a freebie forum - but you're probably not paying a subscription for software updates either. If you want exactly what you paid for you can always stick with the working version you already had.Best of luck - I cant help with the update but I can give advice to resolve the biggest issue. Temper tantrums dont get you very far in life.
-
RE: Duet Web Control Scrolling Issue
@danl I had the same issue today. I resolved it by closing out the tab, shutting down the browser, and reloading. No idea why it occurred- and it was only happening on one device
-
RE: Extruder stepper not turning
Andy - is your hotend warm when trying to retract? It sounds like the stepper is stalled - and if your filaments cooled down and stuck to the sides of your heatbreak and nozzle or simply over-retracted and jammed it's a good possibility.
I'd go back to the original cable - and remove the filament manually before troubleshooting further just to rule out a stall due to a jam or low current on the stepper
-
RE: IDEX U axis z-offset crashing into bed
Sorry - anytime the print uses tool 3 it fails to raise the tool the requested z-offset height before it starts moving it towards the bed. It moves on the u and z axis simultaneously instead of moving the z axis first to clear the bed
-
IDEX U axis z-offset crashing into bed
Hello folks - I have an IDEX build with multiple tools - the most recent addition (super volcano) requires a large z offset on tool 3/U axis
I've got it setup identical to the V6s and Volcanoes before (which all worked) - just a change in the z offset. The issue is instead of changing Z height and then moving on the X axis the duet attempts to do both at the same time and slams into my bed.
I've searched around and I'm not seeing any other reports - is there a simple setting tweak needed somewhere?
========================================================================================================
Edit: More information and clarification
The X axis contains 2 extruders and a single tool - its a Chimera+. The only offset here is a X20 for the second nozzle (Extruder 0, Extruder 1, Tool 0)
The U axis contains 1 tool with 1 extruder. It's a SuperVolcano. The only offset here is Z-22.8 (Extruder 3, Tool 1)When starting a print that uses Tool 1/Extruder 3 (SuperVolcano/U axis) the Z axis starts to increase as the U axis decreases - As the U axis approaches the bed from its parked position. This continues up until the point the SuperVolcano heat block collides with the side of the bed. The Z axis needs to travel 22.8MM BEFORE the U axis completes -80mm of travel. At a relative U-88 from homed however, the Z axis has only traveled approximately +10MM from the probed 0 provided by Tool 1 (X Axis)
The way the machine is built right now tools have ~80-100MM on either side of the bed to park. There's a clearence of >100MM at Z0 where tools are above the table the printer sits on (To allow for the SuperVolcano, and to allow for purging filament off of the side)
I am very new to the Duet still - I had attempted to write everything and get this configured following the wiki. I have also attempted to configure this (with the exception of the U axis) using the configuration tool but I receive the following error every time I attempt to do so
When The U axis/Extruder 3/Tool 1 is not the first tool in a print - this issue still occurs. I did add G1 R2 X0 U0 Y0 Z0 to tpostx.g for each tool (The only threads with any solutions ive found mentioned it, or selecting tools 'twice'?) and it didn't resolve the issue
-
RE: BlTouch installed fine, but fails mid mesh
@phaedrux you're a great help, I really appreciate it.
The probe ran without issue for 10 minutes before I called it. I decided to try again while moving the x axis back and forth and at almost the exact same point it failed to probe. The little blue light dimmed slightly.I swapped in the true probe, and repeated the test and it happened again, almost the exact same spot.
With your help I'm convinced it has to be wiring related. Tomorrow it's going to get a new wiring harness that's 2 meters without any extensions -
RE: BlTouch installed fine, but fails mid mesh
@phaedrux how do I put it in a continuous test mode?
This one is bent, the other one is brand new. They're both genuine per the key on them and both having the issues
-
RE: BlTouch installed fine, but fails mid mesh
@phaedrux Sorry, trying to do 10 things at once earlier tangled in wires. Firmware is 2.02, I will update the original post if I can
From Settings -> General
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.02(RTOS) (2018-12-24b1)
WiFi Server Version: 1.21
Web Interface Version: 1.22.6
From Settings -> Machine Properties
Z-Probe
Type:Unknown (9)
Trigger Height:1.5 mm
Trigger Value: 50
Current Value: 0
From config.g
; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves; Network
NETWORK SECTION REMOVED; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes backwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80.00 Y80.00 Z800.00 E408.80 ; 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.00 Y800.00 Z800.00 E800.00 I70 ; 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 X400 Y400 Z500 S0 ; Set axis maxima; Endstops
M574 X1 Y1 S0 ; Set active low and disabled endstops
M558 P9 X0 Y0 Z1 H10 F100 R0.2 T6000 A5 B1 ; Set Z Probe to type Switch or Digital output where Z probe connector is used. Used for z only
G31 P50 X35 Y-7 Z1.50 ; Set Z probe trigger value, offset and trigger height z was .82; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M307 H7 A-1 C-1 D-1 ; Disable heater 7 on PWM channel for BLTouchM557 X20:380 Y20:380 S20 ; Define mesh grid
; Heaters
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 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 P1 S1 I0 F500 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P0 S1 I0 F500 H1 T45 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on; Tools
M563 P0 S"Nozzle" D0 H1 ; 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; Automatic power saving
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power lossFrom homeall.g
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v2 on Fri Mar 01 2019 12:49:15 GMT-0700 (Mountain Standard Time)
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
M98 Pdeployprobe.g ; deploy mechanical Z probe
G1 S1 X-405 Y-405 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 X5 Y5 F6000 ; go back a few mm
G1 S1 X-405 Y-405 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X-15 Y27 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed
; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 S2 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning
M98 Pretractprobe.g ; retract mechanical Z probe
from homez.g
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v2 on Fri Mar 01 2019 12:49:15 GMT-0700 (Mountain Standard Time)
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G90 ; absolute positioning
G1 X-15 Y27 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 S2 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning
From deployprobe.g
; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v2 on Fri Mar 01 2019 12:49:14 GMT-0700 (Mountain Standard Time)
M280 P7 S10 I1
From retractprobe.g
; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v2 on Fri Mar 01 2019 12:49:14 GMT-0700 (Mountain Standard Time)
M280 P7 S90 I1
From bed.g
; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v2 on Fri Mar 01 2019 12:49:14 GMT-0700 (Mountain Standard Time)
M561 ; clear any bed transform
M98 Pdeployprobe.g ; deploy mechanical Z probe
G29 ; probe the bed and enable compensation
M98 Pretractprobe.g ; retract mechanical Z probe
-
RE: BlTouch installed fine, but fails mid mesh
Here is a short video mid mesh level where it fails
BlTouch Failure -
BlTouch installed fine, but fails mid mesh
I received my Duet from filastruder the other day - everything but the BLTouch and AC heated beds working correctly
Firmware is 2.02, most recent version of the blTouch, I've followed all the setup guides and the probe correctly homes and responds/reports. When I start my mesh level the probe travels and responds normally until about the 7th location where it fails to re-deploy and crashes into the bed. Any idea what's going on here? I've replaced the probe and wiring with a 2nd one I have around - same results at the same place.
I have increased the dive height to 35, slowed the probe process way down to 60, etc