Topics created by rzi

@rzi I've updated that Gcode section to say that it should be just a single set of parentheses:

Alternatively, comments can be enclosed in a single pair of parentheses, e.g. (comment). Comments cannot include double or nested parentheses, e.g. (comment (a bit more comment)), and they must start and end on the same line.

To be fair, I didn't even realise a comment could be in parentheses!

Ian

Please change the end of line settings in YAT so that we can see the full M122 report with proper formatting.

yat.png

@Phaedrux It was a user error. I have two CNC machines. On my old machine I also control the dust extractor. with the M106 command autogenerated from my postprocessor. My new machine has nothing connected so it hits an error, naturally. Still, you pushed me in the the right direction by mentioning other config files, so thanx. 😃

Thanx! woprks very well now. This is what I ended up with.

M558 K0 P5 C"!io2.in" F100; create probe #1 for use with M585, active low

G38.2 X596 P0 G10 P2 L20 X0 G0 X{move.axes[0].userPosition-1} G38.2 X0 P0 G0 X{move.axes[0].userPosition/2} G10 P2 L20 X0 G38.2 y810 P0 G10 P2 L20 Y0 G0 Y{move.axes[0].userPosition-1} G38.2 Y0 P0 G0 Y{move.axes[1].userPosition/2} G10 P2 L20 Y0

Unless you have disabled marlin compatibility mode, you should get an OK response when each command has either finished processing, or if it is a movement command, been placed in the movement queue. You can wait until the movement queue is empty by sending the M400 command and waiting for the OK response to that.

@rzi said in Any progress with variables / parameters?:

Sounds super! Not that far away then. Are you planning to do a similar implementation as in: http://linuxcnc.org/docs/html/gcode/overview.html#_parameters

Or are you heading in some other direction?

Best regards
Rickard

I looked at the linuxcnc implementation, and it's horrible. There is another thread on this topic in which I linked to the draft specification of what I am implementing.

@dc42 said in Probe center of hole?:

2.03RC4 is now released. Thanks @wilriker for the PR.

Damn, you guys are fast as lightning! Thanx

@rzi said in Using E0 or E1 as endstop for Z axis.:

@dc42 I upgraded to 2.03 so now it's working, obviously 😃

However, when I'm using E1 (M574 Z2 S1 C4) as endstop for Z, it seems as when I'm trying to use the normal Z endstop for my touch plate, it ignores the M585 Z20 E2 L0 F500 S1 and uses the endstop configured with M574.

I'll need to make further code changes to allow M585 to work with custom endstop numbers again. Meanwhile, you could use M574 commands around your M585 command instead of using a custom endstop number in M585.

ps
Is it a HW restriction that makes the E stops only avalible as active high?

There is no such restriction.