[3.5beta1] Movement issue on CNC/6xd + some minors

chernogorsky

Few issues on CNC / d3-6xd / SBC
Switched back to 3.4.5 after a broken bit (

it starts enforcing {} rules in IF condition (I know that its in doc somethere)
38.2 38.3 return non zero result quite often. Wich may lead to broken probe. (Im using same probing script for few months on 3.4.5 without any false positive. Only overprotective movement saved me that time)
M291 S2 in a programm does not continue by M292 P0/M292/pressing OK. After the widown closed it still in processing state with no window/reaction to M292. M292 P0/M292/pressing OK works fine with M291 S3.
Unknown movement issue. On a test milling it hangs on some Z, one time it just hangs there, one times it hangs on Z-3.708 (I see that number in GUI/object model (pendant) ) and continue to press downards with slow pace (probably with the same of the last command) without any update to GUI/object model, nor getting next command in line (gcode attached). Was stopped by pause button (GUI).

Last one is the most disturbing

dc42

@chernogorsky thanks for your report. Please explain exactly what you mean in #1 in your list.

dc42

@chernogorsky does your machine use multiple Z motors, and do you use the G32 command to level them? If so then please see https://forum.duet3d.com/post/303514.

chernogorsky

@dc42
#1 - I had multiple lines like
if exists(param.X)
set var.dirX = param.X
and they works before 3.5b1

in 3.5b1 I have to switch to
if {exists(param.X)}
set var.dirX = param.X

I remeber that it was mentioned somethere, but it was not emphisized (ASFAIK) as breaking changes in 3.5b1

chernogorsky

@dc42
I have multiple Y axis, leveled by multiple end-stops
but Z is single axis

It's a CNC mode

dc42

@chernogorsky said in [3.5beta1] Movement issue on CNC/6xd + some minors:

@dc42
#1 - I had multiple lines like
if exists(param.X)
set var.dirX = param.X
and they works before 3.5b1

in 3.5b1 I have to switch to
if {exists(param.X)}
set var.dirX = param.X

I remeber that it was mentioned somethere, but it was not emphisized (ASFAIK) as breaking changes in 3.5b1

Thanks. In CNC mode RRF has always treated ( ) as enclosing comments, except when inside " " or { }. If those lines containing exists(...) were previously working without being enclosed in { } then I think this must have been something to do with running in SBC mode. Perhaps DSF behaved differently from RRF in previous versions.

chrishamm

@chernogorsky I can run your example file and macro statements without enclosing them in { } on my 3.5-b1 SBC setup. Can you tell me how they fail on your setup?

IMO everything after a keyword up to ; or \n should treated as a keyword argument so the DSF code parser reads the contents of unencapsulated ( ... ) as well. It is a RRF-specific add-on to NIST-conform G-code anyway so it doesn't need to remain 100% compatible on those lines.

T3P3Tony

@chernogorsky said in [3.5beta1] Movement issue on CNC/6xd + some minors:

M291 S2 in a programm does not continue by M292 P0/M292/pressing OK. After the widown closed it still in processing state with no window/reaction to M292. M292 P0/M292/pressing OK works fine with M291 S3.

@chernogorsky please let me know if this issue is resolved in 3.5.0beta3

possibly related to:
https://forum.duet3d.com/topic/30885/m291-oddities-on-both-dwc-and-paneldue-v3-5-0b1/8

dc42

@chernogorsky said in [3.5beta1] Movement issue on CNC/6xd + some minors:

M291 S2 in a programm does not continue by M292 P0/M292/pressing OK. After the widown closed it still in processing state with no window/reaction to M292. M292 P0/M292/pressing OK works fine with M291 S3.

We created an issue https://github.com/Duet3D/RepRapFirmware/issues/738 for this and it is in the process of being fixed.

T3P3 created this issue in Duet3D/RepRapFirmware

[3.5beta1] Movement issue on CNC/6xd + some minors

closed M291 S2 not unblocking/Unblocking after timeout. #738