My machine is a maincon upgrade ...
Can't help you otherwise, but that right there is where your problem possibly lies!
UPGRADE!
I have machines with '01 lathe, '01 mill, '03 lathe and '06 mill controls,
They are FALWLESS!!!
Not a single mishap ever, no matter what. They either don't like it from the get-go or run it exactly forever.
Then, I've got a 2016 NextGen controlled machine.
Yes, I understand that yours isn't an NG, but the so called "upgrade" might have been produced by the same fucking college ( or worse, Google ) dropouts
who write the current NfG garbage!
I used to swear that there was nothing that a Haas control can do wrong once it's inside of it, no matter what.
Nowadays however ....
( Rant On )
My fancy NextGen control has seen 5 ( yes that is Five ) upgrades ( Read: FIXES ) in 18 months, and it is still a piece of shit compared to
the 5, 10, 15, 20 year old control!
A bit over a year ago I have yelled at D.D. Machine ( PM member ) for ranting at Haas every time he got a chance to do so about the NextGen garbage.
Well, now 18 months later, I am almost at that point!
While this may or may not have any relation to the OP, but here it is ( yupp, it is a RANT!!! ) :
The current group of assholes at Haas Automation ( aka HaasCNC ) who has any direct knowledge, job description, access, responsibility or in any way
connected to the fuckheads that write code on the new ( or upgrades to the old as it may ) controls should not be fired, rather fired upon!
Really Morons!!!
In the last 18 months I have lost more than 1K in tools running programs which ran on a '06 control for years!
Approx that much lost in tools just because the JOG was sporadically fucked up ( though you did fix that about a year ago )
BUT!
You fucking shitheads KNEW THEN, and KNOW NOW that the M97 Pnnnn call for a G8X cycle is fucked up!!!
You knew that the P value in the G8X cycle is overridden when an M97 is used for hole locations!
The P value in the G8X is some(fucking)how overwritten by the M97 P call!
You dickheads KNEW that! Knew that back in September of 2016! And yet? It still ain't fixed!
Do you want me to go on a bit further ( directed at the children coders at Haas Automation ) ?
You want me to send you a picture of a part that was destroyed by a fucked up G86 cycle that was manually interrupted and chips cleared by spindle reversal?
(Rant temporarily over )
I used to hate Google programmers (because nowadays they suck ).
I now hate Google because the ones that did not make the cut (there) ended up at Haas and are actively fucking shit up and don't know any better!