Related singularity question

Started by mowens, May 06, 2021, 01:37 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

mowens

So the machine is up and running but the singularity is still a problem. Originally we had the part programmed with A axis doing all of the heavy lifting. That was fine except that on one side A axis would over travel by less than a degree. We tried all we could think of to know avail. We even got the software people involved. That's when we tried making B axis primary which resulted in the crash. So my question. Using A axis is not working. B axis was not quite parallel to C axis when the crash occurred. I would like to tilt B axis so that it is a couple more degrees away from parallel with C axis. I don't  know if that would be enough to avoid another crash. It won't show up in my simulation. I'm decent at math but by no means great.
Is there some way to calculate how close to parallel I'm getting? How close to parallel can I come before causing an issue?
I'm almost stumped.
"I would gladly risk feeling bad at times if it also meant that I could taste my dessert." - Data

Tim Johnson

#1
Would the manufacturer be able to give an answer? Can you re-fixture or move the part to where the A-axis can do the heavy lifting again?
FJB

mowens

#2
We could raise the side where we get the over travels a little bit. That would solve the over travel on one side but cause over travel on the other. Still it's an option worth investigating. It's a large layup mandrel mounted on risers so we are limited on what we can do tooling wise but we could do that. I'll bring it up tomorrow.
Thanks!
"I would gladly risk feeling bad at times if it also meant that I could taste my dessert." - Data

mowens

#3
I suggested this solution to the engineer (TE) but he didn't like it. He preferred a slash and burn method that would finish the part but wouldn't yield any usable data. He called another programmer over and didn't tell me. When I asked TE why he was here TE was very evasive. The stupid part is I was glad the other guy was there. And to top it all off he suggested the exact same thing I did. The idea for which I got from here.
I told TE all you had to do was tell me you asked ___ to come take a look. He claimed he thought someone else told me.
Smells like chicken poop to me.
"I would gladly risk feeling bad at times if it also meant that I could taste my dessert." - Data

byte

#4
Quote from: mowens post_id=10797 time=1620333447 user_id=74So the machine is up and running but the singularity is still a problem. Originally we had the part programmed with A axis doing all of the heavy lifting. That was fine except that on one side A axis would over travel by less than a degree. We tried all we could think of to know avail. We even got the software people involved. That's when we tried making B axis primary which resulted in the crash. So my question. Using A axis is not working. B axis was not quite parallel to C axis when the crash occurred. I would like to tilt B axis so that it is a couple more degrees away from parallel with C axis. I don't  know if that would be enough to avoid another crash. It won't show up in my simulation. I'm decent at math but by no means great.
Is there some way to calculate how close to parallel I'm getting? How close to parallel can I come before causing an issue?
I'm almost stumped.

I could create a Mastercam Extension or Application to check the gcode vectors for issues, I know how to calculate vectors.
I can also supply sample code and instructions if you want to do it on your own.
I would need an example Mastercam & Nc file of a good situation and bad situation.
Ideally your post would be able to take care of this for you, but until it does...

mkd

#5
@theebyte, I think they do all that in catia.
 Pretty awesome we know somebody that can do THAT!!!

Tim Johnson

#6
Quote from: mowens post_id=10831 time=1620419950 user_id=74I suggested this solution to the engineer (TE) but he didn't like it. He preferred a slash and burn method that would finish the part but wouldn't yield any usable data. He called another programmer over and didn't tell me. When I asked TE why he was here TE was very evasive. The stupid part is I was glad the other guy was there. And to top it all off he suggested the exact same thing I did. The idea for which I got from here.
I told TE all you had to do was tell me you asked ___ to come take a look. He claimed he thought someone else told me.
Smells like chicken poop to me.


It sucks that people do crap like that in a professional setting. It's not like keeping Aunt Betty out of the picture.
FJB