You either need to enjoy the bulk of the folks you work with, or work somewhere else...
Type: Posts; User: HayreAss
You either need to enjoy the bulk of the folks you work with, or work somewhere else...
Yeah, I figured YOU were kidding...
But that other dude seems to believe a lot of his own nonsense...
And he's VERY insistent.
Can someone explain to me, in simple terms, how redundant code 'slows down the process'?
If you are hand coding, it adds the time it takes to type the redundant code. But a post processor posts it...
I understood.
It simply no longer works that way.
It works as explained in post #5 now.
It's almost EXACTLY what I posted! I mean, XY values are different, and no M3 or line number, but the machine would parse it the same, despite the following statement.
Other than the physical...
Well, that led me down a short rabbit hole.
I downloaded some 'bonus content' from the Haas videos, and what do you know?
They actually teach folks to use an almost identical line to what my posts...
So, interestingly enough, and contrary to what you may have read earlier in this thread, not only CAN our work offsets be called out on the same line as our first X-Y move, as most of us already...
Just walked in to my shop for the first time this week.
Fired up my 2012 with the CW/CCW buttons, and the 2019 with FWD/REV
Tested this in both machines, and it worked exactly as I described in...
Did you do
S command > start > CW?
On both of my machines, that does it after a boot up, or any time I want to change speeds.
True, the old controls had CW and CCW instead of FWD and REV.
But it sure seemed pretty clear that was what he was asking about.
Dude.
You flat out stated you can’t use the FWD button to start the spindle. It’s for the tool changer.
When in fact running the spindle is the only thing that button WILL do.
You certain I’m...
600 amp 3 phase panel.
Haas just likes to say power surge when they can’t explain an issue.
Now, we have dropped a phase twice in 5 years, due to trees falling and taking a line out upstream....
FWIW, I’m neither a job shop, or a production house.
I make and sell my own, boutique products.
Running 2 dozen of one particular program at a time is higher production for me.
I may run that...
M89
M5
G0 G53 Z0.
M1
For the win in my shop.
No time lost.
The next tool is staged right after the earlier tool change, so not a concern.
Tool is still in the spindle if I need to run it...
So, if your machine is set to have M6 turn on the spindle, I imagine you put your speed on that line as well?
What happens if you don’t?
Does it come on at the last speed like the spindle forward...
Yeah. I was responding to your pre edited post.
About M6 turning in the spindle and coolant.
Many of us prefer more granular control.
I certainly don’t want to wait for a tool change to stop my spindle, nor do I want the spindle and coolant to come on with one.
I could see occasions...
Right?
It was like that for weeks while waiting on Haas to come take a look.
I think the program may actually still be there, but I am leaving for the weekend.
MANY power cycles, etc...
There...
Right, it would have zero effect.
That was the point I was trying to make to mactec, but he can't seem to grasp it.
And in this instance, the engineers in Oxnard and the tech got pictures, video,...
Because that info is already here, and it can't be explained.
I tried to simplify the issue, for the simple minded.
It's a VF2-SS
And it was repeatable.
Engineer sat here dumbfounded.
...
Yeah, mine run a lot too.
Not 24/7, but 50 -70 hours a week.
And in 10 years, this is my first glitch of this type.
We are talking 1 tool here. Not tools.
A
Single
Tool
Misbehaving in
The new controls require an S command before the spindle forward button will do anything.
Whether via MDI or the program.
But, once the machine has read a speed, FWD will fire it up at whatever...
It is the same story though.
Well, with reading comprehension it is.
I specified that the tool cut fine on multiple offsets, just not G56.
The tool offset table is irrelevant, really. And the work...
Ahh, you specified tool offset...
Same story though.
As I mentioned earlier, the tool cut fine on other work offsets, and is still the same value that it was before.
My machine is also set up so...
Yeah, well if you could get over yourself, and read, you would know that the offset was correct.
It was probed.
Then it was re-probed.
Then everything was calibrated.
Then it was probed again....
Yeah, my original code, from post #9 in this thread is still running.
Including the code that apparently CAN'T be used like we use it...
It's made close to 100 more parts since I was told it...
It's not.
He just really, really wants it to be.
No, they don't call that a glitch they call that an error, or a crash if it crashes.
A glitch is when it is NOT behaving as expected. Differently than it is presenting itself, etc...
As happened...
It feels like you really should just delete my entire reply, since the post I am replying to was deleted.
Hell, the only actual insult that I made is still there!