rehome.g not found
-
The video link is set to private and I can't see it.
-
@Phaedrux, sorry, it's now set to public, it should be visible
-
So just to make sure I understand what I'm seeing. You're starting a print, and it goes to do it's homing process and it keeps detecting erroneous stall conditions and rehoming?
But you get no stall detections like this any other time?
-
@Phaedrux , No, it occurs during the probing of the bed (G32) befoee printing. On other occasions it works fine, I mean if I run start.g from dwc as a test, not before printing. Is it possible that the problem arises from the lack of M204 in config.g?
In this case where does it get the acceleration values ? -
@Marco-Bona From your video, it looks like the homing is happening 3 times. Is that correct? Or does it just go on repeating?
Lack of M204 shouldn't matter, it will just be set to default. Send M204 on it's own to see the set values, eg mine is not set in config.g, reports
M204 Maximum printing acceleration 10000.0, maximum travel acceleration 10000.0Ian
-
@Phaedrux, @droftarts, The homing works correctly, in the video starting from 40 seconds leadscrew leveling (M671) is performed and then probing for mesh compensation with G32 is performed. As you can see from the video, a stall is detected at 40 seconds even before starting to probe.
The really strange thing is that after adding M204 in config.g the frequency with which the wrong stall detection occurs has decreased. -
If homing is correct, and stall is only in print, isn't that print uses faster travel speeds and acceleration than homing? From my experience this can trigger stall detection if sensitivity is too high (too low S param value).
-
@BoA , This is correct, but I don't understand why if I run start.g from dwc, the commands are executed correctly while if start.g is called when starting the print motors keep stalling. I didn't find much explanation on setting the S value so I went a bit random (now it's set to 6) but occasionally when starting print an incorrect stall is detected.
-
@Marco-Bona Shortcut would be to disable stall detection action by setting R0 instead of R3 (sensorless homing still works)
On my printer I have 2 macros with different speed/acceleration limits - one for homing - more sensitive setting lower speeds, and second for normal print to avoid false stall detection.
Perhaps there are some commands in print gcode that change aceleration etc.
-
@BoA ,I'm not using sensorless homing, I have normal optical sensors as limit switches, I use stall detection to prevent the motors from losing steps or the head colliding during printing.
-
@Marco-Bona OK then. I would just increase S level until no false stall detection occurs.
And just a stupid question - do You actually have rehome.g in sys folder ? -
@BoA , Sorry for the confusion, initially for wrong name, rehome.g was not found (there was a space after the g), then the problem became that an incorrect motor stall is detected. In all honesty I don't know what to feel anymore because I have inconsistent data.
-
Ok, What is Your current M915 configuration?
-
@BoA , this is the one with which I found myself best
M915 X Y T20000 S6 H51 F1 R3 -
I just tried to trigger stall detection on my printer. And it works ONLY when printing. In any other cases it allows motors to stall and do nothing.
That might be the reason why it is triggered only during print.
IMO You have too low H value.
Did You try formula from https://duet3d.dozuki.com/Wiki/Stall_detection_and_sensorless_homing ?
-
@BoA , now it's clear. I got that value from 3D Printer Calc Toolbox, the formula should be same, although I have some doubts about actual current value (I set 2.24 A). Rated current is set on 2.8A
