Recent Mach3 Releases and OEMButton(1000)

[HimyKabibble]

I have a pendant, operated by a macropump driver.  One of the functions is CycleStart, which is actuated by OEMButton(1000).  Starting with v49 (I don't think this was a "public" release), and continuing through v53, each time I hit an M00 or toolchange, I have to send the OEMButton(1000) twice before execution proceeds.  Has anyone else seen this?

Regards,
Ray L.

[BR549]

DO you have a while Ismoving()  statement after the  OemButton(1000) call?

Try    Button(0) instead

(;-) TP

[HimyKabibble]

DO you have a while Ismoving()  statement after the  OemButton(1000) call?

Try    Button(0) instead

(;-) TP

Terry,

The while loop is unnecessary - this is a fire-and-forget function, activated by a manual button on the pendant, and it's worked perfecly for years, until these last few releases.  The same OEMButton is used for the on-screen CycleStart button (which, inexplicably, still works fine....).

Regards,
Ray L.

[BR549]

RAY one of the BIG problems lately is the CB loosing control of the threads the later versions ARE the worse so far ESPECIALLY with button code and for some reason BUTTON code is the worst offender.

Macropump code is not imune to the problem either.

 BEFORE you say it is not needed TRY IT(;-) It has solved MANY eveils here. It forces MACH to pay attention when it really needs to. Otherwise it is known to ignore and skip things .

I have seen what you are seeing many times.

Just a thought, (;-) TP

[HimyKabibble]

Terry,

This issue was introduced about two months ago, in a test build Brian did to address one of my (many!) problems.  It only seems to affect OEMButton calls issued from within the macropump.  The change Brian made had to do with trying to block many/most button calls when a program is running, so my guess is he's not properly tracking the state, and blocking too much.  The macropump exits immediately after issuing the OEMButton call, so adding a while loop will do nothing to return control back to Mach any more than it already is.  Besides, it is a real bug, and NEEDS to be fixed, not just worked around.

Regards,
Ray L.

[BR549]

Ray the double tap issue is NOT new (;-)

In plasma work I still see the ignore the M3 problem as well.

(;-) TP