g1/g2/g3 error but I can't identify it?

dc42

@terbospaghetti what does the Z coordinate read in DWC when you get these errors?

terbospaghetti

Z0.2

dc42

@terbospaghetti what happens if you change the lower Z axis limit from 0 to -1 in yur M208 command? I think the Z offset of 0.265mm for the second tool is stopping the print head going low enough, because at 0.2mm commanded Z height it would need to go to -0.65mm machine height.

terbospaghetti

@dc42 that seems to have done the trick! Thank you

o_lampe

@terbospaghetti said in g1/g2/g3 error but I can't identify it?:

M584 X0.0 U0.5 Y0.1 Z0.2:0.3 E1.0:1.1 ; set drive mapping
; Tools
...
M563 P1 S"E1" D1 H2 X3 F0 ; define tool 1 ADDED X3 TO MAP U AXIS TO X AXIS

Is X3 correct? IMHO it's X0.5

dc42

X3 is correct, it means map the X axis to axis #3 which is U.

jltx

@dc42

I'm not sure if this is a bug in 3.3 but was unexpected. I was running into same trouble as terbospaghetti expect while using baby stepping from DWC. It would take my command and update the Z offset in the display without actually accomplishing the move. I later saw the error messages in the console. But the odd behavior was that some Gcode streaming from the SD card would get dropped. I was adjusting Z during the skirt and suddenly it would jump into the part first layer. Then in the part I could get it to skip some moves if I produced too many errors from baby stepping.

dc42

@jltx that sounds as if it could be a new bug in RRF 3.3. Movement is handled by a separate Move task in 3.3, so it's quite possible that failure to sync the Main task (which does babystepping) and the Move task is the problem. I've added it to the investigations list.

CR3D

@dc42 is this Problem solved from RRF 3.3?

dc42

@cr3d I believe this is fixed in 3.4beta, however I can't be sure as I have not reproduced it.

CR3D

@dc42 ok thanks. We will test it.

I hope there will be a "final" firmware soon, that we can use the new one for the next machines

dc42

@cr3d have you tested RRF 3.4.0rc2 to see whether you still have this issue?

dc42

@cr3d I am closing this issue due to lack of response. Feel free to open it again if you can reproduce it using RRF 3.4.0 stable.