Mesh probe grid not in defined range on Y axis
-
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 probeRemove 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
