Homing issues
-
I have my Duet 1.19 wifi set up for low end homing. I can home the x alone and it is perfect. I can do the same with the Y axis. But when X or Y is already at its home location. The other axis runs into the end stop and I have to estop the machine and reset it. the only error I get , is a Bad Grid error that tells me to set it to 58.4 mm. My bed size is 1200 x 1200 x 225mm . I am confused why they will work separately but not in unison!!!
-
That's a large printer!
1. Please share your homing files and your config.g file.
2. Is this a Cartesian printer, or a CoreXY?
3. Which firmware version are you running?
4. What type of homing switches are you using for X and Y, and how have you connected them to the Duet?
-
It is a Cartesian printer, it is also pellet fed extruder.
I just got the complete set up From Roland so its the 1.19 version
Here's what I have,
Using proximity sensors for XYZ, The Smart Probe for bed level and auto Z. ALL Switch's are lighting up on the board individually.
If one switch is still active will effect the ohers during homing?
I need for the XandY to go home and the Z-home to go all the way up to clear any large part when homing.
Thank you, I know this breaks your rules, but I have got orders for this machine on hold till I get this Fixed; Configuration file for Duet WiFi (firmware version 1.17 to 1.19)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Thu Nov 30 2017 11:19:42 GMT-0600 (CST); General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X1200 Y1200 Z200 S0 ; Set axis maxima; Endstops
M574 X1 Y1 Z2 S0 ; Set active low endstops
M558 P1 X0 Y0 Z0 H5 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the dive height + speeds
G31 P600 X0 Y0 Z5 ; Set Z probe trigger value, offset and trigger height
M557 X15:1185 Y15:1185 S20 ; Define mesh grid; Drives
M569 P0 S0 ; Drive 0 goes backwards
M569 P1 S0 ; Drive 1 goes backwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I0 ; Configure microstepping without interpolation
M92 X120.306205 Y120.306205 Z1058.157 E200 ; Set steps per mm
M566 X900 Y900 Z12 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X12000 Y12000 Z1200 E1200 ; Set maximum speeds (mm/min)
M201 X500 Y500 Z250 E250 ; Set accelerations (mm/s^2)
M906 X2400 Y2400 Z2400 E2000 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Heaters
M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
M305 P0 T100000 B4138 C0 R4700 X151 ; Set thermistor + ADC parameters for heater 0 and remap it to channel 151
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 C0 R4700 X150 ; Set thermistor + ADC parameters for heater 1 and remap it to channel 150
M143 H1 S280 ; Set temperature limit for heater 1 to 280C; Tools
M563 P0 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; Network
M550 PDPP XLS DPE ; Set machine name
M552 S1 ; Enable network
; Access point is configured manually via M587 by the user
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet; Fans
M106 P0 S0.3 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on; Custom settings are not configured
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool on Thu Nov 30 2017 11:19:42 GMT-0600 (CST); Relative positioning
G91; Lift Z
G1 Z5 F6000; Course home X and Y
G1 X-1205 Y-1205 F1800 S1; Move away from the endstops
G1 X5 Y5 F6000; Fine home X and Y
G1 X-1205 Y-1205 F360 S1; Absolute positioning
G90; Go to first bed probe point and home Z
G1 X15 Y15 F6000
G30; Uncomment the following line to lift the nozzle after probing
;G1 Z5 F100; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool on Thu Nov 30 2017 11:19:42 GMT-0600 (CST); Lift Z relative to current position
G91
G1 Z5 F6000
G90; Move quickly to X axis endstop and stop there (first pass)
G1 X-1205 F1800 S1; Go back a few mm
G91
G1 X5 F6000
G90; Move slowly to X axis endstop once more (second pass)
G1 X-1205 F360 S1; Lower Z again
G91
G1 Z-5 F6000
G90
; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool on Thu Nov 30 2017 11:19:42 GMT-0600 (CST); Lift Z relative to current position
G91
G1 Z5 F6000
G90; Move quickly to Y axis endstop and stop there (first pass)
G1 Y-1205 F1800 S1; Go back a few mm
G91
G1 Y5 F6000
G90; Move slowly to X axis endstop once more (second pass)
G1 Y-1205 F360 S1; Lower Z again
G91
G1 Z-5 F6000
G90
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool on Thu Nov 30 2017 11:19:42 GMT-0600 (CST); Lift Z relatively to current position
G91
G1 Z5 F6000; Back to absolute positioning
G90; Go to first bed probe point and home the Z axis
G1 X15 Y15 F6000
G30; Uncomment the following lines to lift Z after probing
;G91
;G1 Z5 F100
;G90 -
The endstop switches should not interact the way that you describe. Your files look OK to me.
Please go to Settings->Machine Properties in the web interface. You will see the endstop states seen by the firmware shown there. Do the endstop states read correctly when you trigger the X and Y endstop switches, whether you trigger them separately or both together?
What sort of proximity switches are they, and how have you connected them to the Duet?
-
I am using "uxcell SN04-N DC 10-30V NPN 3-wire 4mm Approach Sensor Inductive Proximity Switch" at each home location. I am using a 12v Aux power supply to operate LEDs, Separate cooling fans and the proximity switches. I have the trigger wire connected to the Duetwifi board and they work in single operation. Here is something I noticed, when X,Y or Z homes, the switch is still active (triggered ON, Light ON). If one axis is still triggered, would that keep the other switches from triggering? If so, how do I get it to offset far enough to turn off the trigger after each axis homes?
-
The endstop inputs on the Duet are independent. So I think there must be something about how you have them mounted or wired that is causing interference between them. When X and Y are both homed, are the 2 proximity sensors very close to each other? if so then the magnetic field from one might interfere with the other.
Have you done the test I suggested, to see what endstop information the firmware is receiving when you move one axis towards the endstop position when the other is already homed?
-
OK, Switched the end stop Proximity switches to micro-switches (2-wire) now X & Y home correctly but Z is still and issue. I need Z to Home at the full up Position before probing the table. It still dive towards the table, I can trip the sensor (IR Probe from Duet3D. Light turns on but doesn't stop the z axis
-
