Mesh probe grid not in defined range on Y axis
-
I have test M557 X0:300 Y80:300 S20 and no warning, stuck at Y=218.
The head move to Y=300 with G1 gcode.my config.g:
; Configuration file for Duet WiFi (firmware version 2.03)
; executed by the firmware on start-up
;; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder movesM669 K1 ; switch to CoreXY mode
; Network
M550 P"COREXY" ; Set machine name
M552 S1 ; Enable network
;*** Access point is configured manually via M587
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet; Drives
M569 P0 S0 ; Drive 0 goes forwards (X)
M569 P1 S0 ; Drive 1 goes forwards (Y)
M569 P2 S0 ; Drive 2 goes forwards (Z)
;M569 P4 S0 ; Drive 4 goes forwards (Z) ; for Bed levelling using multiple independent Z motor drivers
;M569 P5 S0 ; Drive 5 goes forwards (Z) ; for Bed levelling using multiple independent Z motor drivers
M569 P3 S1 ; Drive 3 goes backwards (E0);M584 X0 Y1 Z2:4 E3 ; three Z motors connected to driver outputs Z
;M671 X-74:-74:330 Y-30:330:150 S1.0 ; Z leadscrews are at (-74,-30), (-74,330) and (330,150), 1mm compensation maxM350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z400 E820 ; Set steps per mm with 1/16 and BMG extruder with 0.9° stepper
M566 X1200 Y1200 Z60 E3000 ; Set maximum instantaneous speed changes (mm/min)
M203 X30000 Y30000 Z1000 E6000 ; Set maximum speeds (mm/min)
M201 X5000 Y5000 Z500 E10000 ; Set accelerations (mm/s^2)
M906 X1400 Y1400 Z1400 E1200 I30 ; Set motor currents (mA) and motor idle factor
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y-3 Z0 S1 ; Set axis minima
M208 X300 Y300 Z200 S0 ; Set axis maxima; Endstops
M574 X1 Y1 S1 ; Set active high and disabled endstops; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M307 H3 A-1 C-1 D-1 ; Disable heater 3 on PWM channel for BLTouch
M558 P9 H5 F150 T4000 B1 ; Set Z probe type to bltouch and the dive height + speeds
G31 P25 X0 Y82 Z1.030 ; Set Z probe trigger value, offset and trigger height
;M557 X0:300 Y80:218 S20 ; Set Z probe point or define probing grid
M557 X0:300 Y80:300 S20; Heaters
M307 H0 A254.7 C545.2 D0.9 S1.00 V24.4 B0 ; Disable bang-bang mode for the bed heater and set PWM limit
M307 H1 A564.6 C201.7 D6.1 S1.00 V24.1 B0 ; Disable bang-bang mode for the nozzle heater and set PWM limit
M305 P0 T100000 B4725 C7.060000e-8 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 S275 ; Set temperature limit for heater 1 to 275C; Fans
M106 P0 S0 I0 F500 H-1 C"HotEnd_Fan" ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45 C"Extruder_Fan" ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 H100:101:102 T45:55 L0.3 C"Electronic_Fan" ; set fan 2 value, turn on at 30% if the CPU temperature reaches 45C, and increase to full speed gradually as the temperature rises to 55C; 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; Automatic saving after power loss is not enabled
; Custom settings
M305 P101 S"DuetDriversTemp" ; temperature warning and overheat flags on the TMC2660 on Duet
M305 P102 S"DuexDriversTemp" ; temperature warning and overheat flags on the TMC2660 on Duex
M912 P0 S6.0 ; calibrate CPU temperature
;M556 S80 X0.125 Y0 Z0.5 ; axis skew compensation
M307 H2 A-1 C-1 D-1 ; Disable heater 2 on PWM channel for LED strip
M42 P2 S0 ; LED strip on heater 2 off; Miscellaneous
T0 ; Select first tool;M501 ; Read stored parameters from EEPROM
;M80 ; Turn 24V power supply ON
-
This post is deleted! -
M584 is commented because it's for future use of 3 z steppers. Actually I use two z steppers in serial so M584 is not used.
If you see my previous post M557 with Y=218 don't work. The y offset probe is 82, so the first value reachable is 80. I have warning for Y lower.
In order to reduce test time I use the second line with M557 P2, and I test with the maximum Y to see if I have warning for probe points not reachable and if the probe goes far that 118.I don't know why I have to put the maximum y bed size in M557, in this case the last probe point is Y=218 so good.
I don't have a config.override file.
I have do some tests with different values for Y in M557, and I have always the probe offset substracted from the defined Y value in M557 for the maximum Y probing.
I have 2.03 firmware
-
Can you post your homing files as well?
-
Why ? homing files are not concerned by probing, not ?
I could post it when I come back to home -
I want to see if there is something in them like a g92 to set an x y position that could be interfering.
-
@pipersw said in Mesh probe grid not in defined range on Y axis:
M584 is commented because it's for future use of 3 z steppers. Actually I use two z steppers in serial so M584 is not used.
Where is the M584 command that is currently in use?
Frederick
-
I have cleaned my config file, I joined all the configuration files :
13_1567539625081_stop.g 12_1567539625081_sleep.g 11_1567539625080_retractprobe.g 10_1567539625080_resume.g 9_1567539625080_pause.g 8_1567539625080_homez.g 7_1567539625080_homey.g 6_1567539625079_homex.g 5_1567539625079_homeall.g 4_1567539625079_heightmap.csv 3_1567539625079_deployprobe.g 2_1567539625079_config.g 1_1567539625078_cancel.g 0_1567539625078_bed.g
-
I don't think it matters, but you've got a rogue G31 inside your M558 command
M558 P9 H3 F100 T6000 A10 S0.03 R0.5 B0 G31 P25 ; Set Z probe
Remove the G31 P25 and see if it makes a difference. Could explain why the offset isn't seeming to work.
But maybe that error wasn't there previously in which case, I'm at a loss. The other files look ok.
-
Hi,
I downloaded your most recent posted config.g file and I still don't see a M584 command.
Perhaps there are defaults settings being used but I think it best to have an explicit command just to play it safe.
The noise you are hearing may be related to the speed of the move(s).
Frederick
-
@fcwilt said in Mesh probe grid not in defined range on Y axis:
Hi,
I downloaded your most recent posted config.g file and I still don't see a M584 command.
Perhaps there are defaults settings being used but I think it best to have an explicit command just to play it safe.
The noise you are hearing may be related to the speed of the move(s).
Frederick
I will add it. thx.
config.g:
; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder movesM669 K1 ; switch to CoreXY mode
; Network
M550 P"HYPERCUBE_EVO_NGEN" ; Set machine name
M552 S1 ; Enable network
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet; Drives
M569 P0 S0 ; Drive 0 goes forwards (X)
M569 P1 S0 ; Drive 1 goes forwards (Y)
M569 P2 S0 ; Drive 2 goes forwards (Z)
M569 P3 S1 ; Drive 3 goes backwards (E0)M584 X0 Y1 Z2 E3:4 ; Set drive mapping
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z400 E820 ; Set steps per mm with 1/16 and BMG extruder with 0.9° stepper
M566 X1200 Y1200 Z60 E3000 ; Set maximum instantaneous speed changes (mm/min)
M203 X30000 Y30000 Z1000 E6000 ; Set maximum speeds (mm/min)
M201 X5000 Y5000 Z500 E10000 ; Set accelerations (mm/s^2)
M906 X1400 Y1400 Z1400 E1200 I30 ; Set motor currents (mA) and motor idle factor
M84 S30 ; Set idle timeout