I'm not certain, but I think that single step behavior may have been around a while. I am currently on 4336 and I think it's there. I quit using single step because of it, didn't realize it got a step behind, I thought it STOPPED. I figured it was because I use a macro, M43, for G43 tool length offset, and it couldn't step thru the macro, but maybe that isn't it. Brian HAS mentioned that single step is a bear to get right inside Mach4!!

One Major gripe im having with this any older Mach4 screensets is that Gcode extends are shown in machine coordinates and not in offset coordinates, i typically used viewing extends in Mach3 to check if i made any major errors in the gcode but now i would have to sit down with a calculator and work out if I hit anything in my G54. A modifier button to display extends in the working offset would be really welcome !

And maybe its my fault but where can i set up a start / end Gcode position ? I used to quickly set that in mach 3 with Safe Z depending on the work i was doing and it was really convenient.

I have updated my industrial ver to the release ver can you tell me the date for the 4 axis default screen set

thanks in advance

I'm not certain, but I think that single step behavior may have been around a while. I am currently on 4336 and I think it's there. I quit using single step because of it, didn't realize it got a step behind, I thought it STOPPED. I figured it was because I use a macro, M43, for G43 tool length offset, and it couldn't step thru the macro, but maybe that isn't it. Brian HAS mentioned that single step is a bear to get right inside Mach4!!

Who knows, it's not acceptable though. This is a fundamental function that needs to work!

Here's a trivial program that shows this behaviour and worse. Can someone at Mach do something about this please.
I thought I saw this jump when it executed the first line, so I took a note of the DROs
This is what they read prior to executing the first block...
X19.5989 Y16.6904
And this is what they read afterwards!
X19.4465 Y16.6683

This should have gone to X4.5 Y14.500 in the G01 block.

If you continue single stepping, it then stays one block out of sync until it executes the M5M30 when the displayed current line can't make up its mind what block it's on. Hardly surprising really since it's actually beyond the end of the program.

G01 X4.5 Y14.500 F1000
G01 X-11.5 Y-14.500
M5M30

Clearly something is very wrong here.

Note, I'm using backlash compensation, so maybe that has some bearing on it? Either way, it's not right and it doesn't give me any confidence it's going to go where it's told to.

Doesn't anyone test this before being released?

Are you using a profile from a previous build by chance?

Yes, I thought the idea was that profiles were transferrable between builds? Surely the behaviour of Mach is in the core software?

Be aware, that you may need to update the Motion Control Plugin as well, for them to work correctly.

If you use the ESS then it needs to be Build 260 or higher.

I upgraded to ESS V270 from when I changed from Mach 4 V4.2.0.3804 ESS V231, so I have both of the latest builds and now have this new problem which I didn't have before.
My guess is something changed in the Mach4 code between these two releases that messed up the single stepping.
Note, I've been using backlash compensation happily with the old versions, so it shoudn't be anything to do with that. I just mention it for completeness since I know a lot of people don't use it.

272 is the latest compiled against 2612

Here's hoping old profiles aren't the cause! If not, I don't know.......hope there's a nice way to get all the stuff out of an old profile in order to hand enter it all into a new profile. And don't tell me I should have documented it all along the way, I KNOW that, but didn't do it. Remember the old Mach Profile for Mach3 by Klaus? That spoiled me but I don't have THAT to extract an old profile. Unless, of course, there IS a way to get everything out of a profile?

Tom