M915 won´t accept R2 or R3

[vali3d]

@jay_s_uk I should be able to set both modes, when testet it does not detect the crash at R2/3.

[jay_s_uk]

@vali3d are you getting any stalls at all?
Are you explicitly setting the drivers as stealthchop? i.e. D3 in M569?

[vali3d]

@jay_s_uk when I set a R1 it log them in the console

[dc42]

@vali3d did you create the /sys/driver-stall.g file with appropriate contents to do what you want when a stall is detected?

[vali3d]

@dc42 I now created that file with some contents. Sadly that did not solve the Problem.

[vali3d]

@jay_s_uk The M569 looks like this:

M569 P0.0 S0                                                    
M569 P0.1 S1                                                    
M569 P0.2 S0                                                    
M569 P0.3 S1                                                    
M569 P0.4 S1                                                    
M569 P0.5 S1                                                   
M569 P2.0 S1
M569 P2.1 S1
M569 P1.2 S1
M569 P2.2 S1                                                    
M584 V0.3 W0.4 X0.5 Y0.1 Z0.0 A0.2 R0 S0 E1.2:2.0:2.1:2.2  

[jay_s_uk]

@vali3d what board are you using?

[vali3d]

@jay_s_uk MB6HC+2x EXP3HC (see https://forum.duet3d.com/topic/18329/duet-3-expansion-looses-connection)

[dc42]

@vali3d is it the drivers on the MB6HC that are not invoking the driver-stall.g file, or the ones on the 3HCs?

[vali3d]

@dc42 all relevant drivers are on the MB6HC

[vali3d]

I don´t think that there is a Problem with the file. The Problem is that the R3 cant be set. When I do M915 X S3 R3 and then M915 the configuration of the axis is on the default settig.

[dc42]

@vali3d I confirm this is a bug. I will fix it in the next RC, and I will probably make a test version available before then.