Hello Guest it is March 28, 2024, 01:27:30 PM

Author Topic: Odd behaviour?  (Read 5974 times)

0 Members and 1 Guest are viewing this topic.

Offline Hood

*
  •  25,835 25,835
  • Carnoustie, Scotland
    • View Profile
Re: Odd behaviour?
« Reply #10 on: May 14, 2016, 12:38:07 PM »
If you could get the run signal to Mach then you could have the M3 macro look at it before allowing code to run, problem likely would be when you get the problem with the macro not being read Mach just continues anyway I think.
So that would not work :(


Ok so maybe you  could add a custom macro after each M3 and have that custom macro look for the signal and if not present within a set time do an E-Stop.

Hood

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Odd behaviour?
« Reply #11 on: May 14, 2016, 12:50:58 PM »
I'm sure there is a way forwards here, will look further, odd that the plasma has never done it though.

Offline Hood

*
  •  25,835 25,835
  • Carnoustie, Scotland
    • View Profile
Re: Odd behaviour?
« Reply #12 on: May 14, 2016, 01:29:43 PM »
I don't know why some people get it and others, like me, never see it.
I have used Mach since the Mach2 days and have had a manual Bridgeport conversion, a CNC Bridgeport, Beaver NC5 mill, Computurn lathe, Conect lathe,  Chiron VMC and a coil winder and I have never once had that problem.

Might be worthwhile making a new profile from scratch and seeing if that helps, or even deleting the macro folder and starting Mach up and it will create new macros for you.

Hood

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Odd behaviour?
« Reply #13 on: May 14, 2016, 01:38:06 PM »
Hmm, odd.

I'm using the 2010 screenset so the macros came with that, not sure about the M03 though I think thats standard.

I'll give her a bit longer before reinstalling as its all working well apart from this very intermittent issue.

Offline Hood

*
  •  25,835 25,835
  • Carnoustie, Scotland
    • View Profile
Re: Odd behaviour?
« Reply #14 on: May 14, 2016, 01:44:47 PM »
Well if you can get a spindle running signal from the VFD to Mach then you can make a macro and you wont have to worry.
Hood

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Odd behaviour?
« Reply #15 on: May 14, 2016, 01:56:00 PM »
would seem to be a reasonable addition, it is pretty important that the spindle is running i guess ;)

Offline ger21

*
  • *
  •  6,295 6,295
    • View Profile
    • The CNC Woodworker
Re: Odd behaviour?
« Reply #16 on: May 14, 2016, 01:58:26 PM »
Delete the M3 completely, and create a new one from scratch in Notepad or whatever editor you use.
Just type
DoSpinCW()





and save as "m3.m1s"

From what I've seen, if you create a new one, it usually stays OK.

And no, I don't supply that macro with the screenset. only the ones unique to the screenset.
Gerry

2010 Screenset
http://www.thecncwoodworker.com/2010.html

JointCAM Dovetail and Box Joint software
http://www.g-forcecnc.com/jointcam.html

Offline ger21

*
  • *
  •  6,295 6,295
    • View Profile
    • The CNC Woodworker
Re: Odd behaviour?
« Reply #17 on: May 14, 2016, 01:59:12 PM »
And fwiw, it's never happened to me either.
Gerry

2010 Screenset
http://www.thecncwoodworker.com/2010.html

JointCAM Dovetail and Box Joint software
http://www.g-forcecnc.com/jointcam.html

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Odd behaviour?
« Reply #18 on: May 14, 2016, 02:05:10 PM »
Weird init ;)

Will try with my edited version tomorrow.

Offline mc

*
  •  382 382
    • View Profile
Re: Odd behaviour?
« Reply #19 on: May 14, 2016, 03:27:34 PM »
I had it randomly on my lathe. I also had it once where it turned the spindle off instead of reducing speed. That one wouldn't of been so bad, but it knocked both the turret and spindle out of alignment, as well as shattering a relatively new drill  >:(

I've got to admit, I definitely don't miss Mach on my lathe!