Anyone know when trigger macros stopped working properly? The associated macro now doesn't run until all movement has stopped rather than when the trigger atually fires. OEM triggers appear to work as normal. (currently using R3.043.066).

Ian

Ian, I'm guessing anything after 3.043.022.

Brett

Brett,

I checked the change log and there's no entry for 3.043.022 so I'm none the wiser!

It jumps from 3.042.039 to 3.043.036 and the only possibly significant note I see is...

//Many updates added and debugged to get to this stage...

What was the deal with 3.043.022?

Ian

3.43.022 has a bug in M6 macros that can cause Mach3 to lock up. It doesn't happen with the stock macros, though. But the M6 I use in my screenset to auto zero will lock it up every time. This  bug was fixed in 3.43.028, but 3.43.022 was still the lockdown version for well over a year until 3.43.062 I think.

Thanks Gerry!  That's the way I understood it as well but wasnt sure of version numbers.

Brett

Sorry guys, you've lost me. What's the relevancy of this to my question? Brett - I thought by your first reply you knew of something that 3.043.022 had something to do with it - I was trying to find out what 

Ian

Ian, like you, I'm trying to figure out when it broke.  I know there were some changes made after 3.043.022 that may have something to do with what your seeing.  Exactly what was changed and in what version, I do not know.

Brett

OK Brett - thanks. I'm trying to get some progress on making my probing (and other things) boiler-plate and I'm starting to think Sisyphus had it easy. Mach's breaking/fixing/breaking obsession is making me think I might just have to wait for 4.

Ian

   You made me Google Sisyphus.  I know Ian.  The inherent quirks in 3 make it tough for us to make changes as well as the programmers.  I think 4 will be much easier (predictable) and I'm looking forward to it.

Brett

  You made me Google Sisyphus.

Rock 'n' roll 

Ian