RepRapFirmware 3.0 first official beta is out

smoki3 · 22 Sept 2019, 07:31

I also have another wire behavior with stall detection on my corexy machine with the duet2.

If I start homing the machine executes the homey.g (also happens for X axis) as it should. But the randomly I get the massage homing failed. But no crash or something else. Everything is as it should just the message homing failed and the axis is not marked es homes.

I tried so many stall parameters but I don't this it has something to do with this, because the stall is working fine and the home is done fine. Just the axis get not marked as home then I get homing failed.

Is there a way to debug?

dc42 · 22 Sept 2019, 07:47

The Homing Failed message means that the homing switch was not triggered before the move completed. If using stall detection, it means no stall was detected.

smoki3 · 22 Sept 2019, 08:07

@dc42 said in RepRapFirmware 3.0 first official beta is out:

The Homing Failed message means that the homing switch was not triggered before the move completed. If using stall detection, it means no stall was detected.

But it is detected because it move to the end position and then it do the rest of the script (move a bit away from the end position end so on). Otherwise the printer should crash normally because it have to go another 400mm if the stall is not detected

T3P3Tony · 22 Sept 2019, 10:59

@kraegar please try 1.0.4.0 @chrishamm believes this is fixed

kraegar · 22 Sept 2019, 14:15

@T3P3Tony Will do, thanks for the quick update @chrishamm!

kraegar · 22 Sept 2019, 16:50

Looking much better so far!

smoki3 · 23 Sept 2019, 14:22

@dc42

As you can see here the drivers are detecting the stall very well.

https://photos.app.goo.gl/DMTiBbvibGsSs42Y7

But it looks like the signal get not processed correctly.

kraegar · 23 Sept 2019, 20:53

Testing yesterday and today has so far shown 1.0.4.0 to be stable, and fixed the quality issue that cropped up in 1.0.3.5

smoki3 · 25 Sept 2019, 06:21

@smoki3 said in RepRapFirmware 3.0 first official beta is out:

@dc42

As you can see here the drivers are detecting the stall very well.

https://photos.app.goo.gl/DMTiBbvibGsSs42Y7

But it looks like the signal get not processed correctly.

If I put a G92 X"xx.xx" in the homing scipt than it is working as it should

stewwy · 29 Sept 2019, 17:12

@wilriker , any chance I can look at your duet2 config files for RRF3, your machine is close to mine and I'm just getting ready to try RRF3?

wilriker · 29 Sept 2019, 20:48

@stewwy Yeah, no problem. I can provide it to you tomorrow. But be warned the post I link to in my signature is a bit outdated.

kinta · 1 Oct 2019, 13:18

This post is deleted!

stewwy · 2 Oct 2019, 14:21

Hi, could someone look at these, from my config.g and see if they are correct for RRF3?

; Endstops
M574 X1 S1 P"xstop" ; X home to min.
M574 Y2 S0 P"ystop" ; Y home to max. N0pen micro-switches.
M574 Z1 S2 P"zprobe.in" ; Define Z to use DC42 irProbe. Home to Min.

;ZProbe
M558 P1 C"zprobe.in" H3 F600 T6000 X0 Y0 Z1 ; Set Z probe type/mode 1. Not using on XY, but using it on Z. F400 dive speed T6000 travel speed
G31 P500 X15 Y-2 Z1.46 ; Z probe trigger value, offset in relation to nozzle. And trigger height adjustment
M671 X-50:325 Y110:110 S0.5 ; Leadscrew positions for bed tramming

Thanks in advance

Edit: I should mention I am using 2 motors for Z

triumphantduke · 21 Oct 2019, 02:48

@dc42 please don't take this the wrong way, but just for some planning purposes.. when do you think the next release will be out?

dc42 · 21 Oct 2019, 06:49

@triumphantduke said in RepRapFirmware 3.0 first official beta is out:

@dc42 please don't take this the wrong way, but just for some planning purposes.. when do you think the next release will be out?

Soon, perhaps tomorrow.

dc42 · 21 Oct 2019, 06:51

@stewwy said in RepRapFirmware 3.0 first official beta is out:

Hi, could someone look at these, from my config.g and see if they are correct for RRF3?

; Endstops
M574 X1 S1 P"xstop" ; X home to min.
M574 Y2 S0 P"ystop" ; Y home to max. N0pen micro-switches.
M574 Z1 S2 P"zprobe.in" ; Define Z to use DC42 irProbe. Home to Min.

;ZProbe
M558 P1 C"zprobe.in" H3 F600 T6000 X0 Y0 Z1 ; Set Z probe type/mode 1. Not using on XY, but using it on Z. F400 dive speed T6000 travel speed
G31 P500 X15 Y-2 Z1.46 ; Z probe trigger value, offset in relation to nozzle. And trigger height adjustment
M671 X-50:325 Y110:110 S0.5 ; Leadscrew positions for bed tramming

Thanks in advance

Edit: I should mention I am using 2 motors for Z

If you are using G30 commands to home Z in your homing files, you should remove the M574 Z command, because you have no Z endstop switch.

triumphantduke · 21 Oct 2019, 16:24

@dc42 haha okay, standing by eagerly