PDA

View Full Version : Problem with tabs



awalt1250
11-10-2013, 05:27 PM
I am having problems with anomalies being introduced near my tabs. I'm not sure what to call them...maybe divots? This problem only happens near a tab. The problem area is the same general diameter as the bit.

See the attached pictures. I'm running a shopbot desktop with vcarve pro, cutting 1/2" baltic birch using a 1/4" upcut spiral. This is the first time I've seen this happen. Total time on the machine is maybe 10 running hours.

Any help or suggestions would be appreciated.

Bob Eustace
11-10-2013, 05:57 PM
Andy I dont think its anything to do with tabs. Try converting your part to "bezier" and you should get a smooth job.

myxpykalix
11-10-2013, 06:16 PM
go into node editing, click on your vectors and then see if they are smooth or come to sharp points. If so do like Bob says and turn them into bezier curves.

awalt1250
11-10-2013, 07:31 PM
The shapes are bezier curves already..not seeing any sharp points that large on them. Would small points get magnified?

I'm going to try 3d tabs, increase the number of passes from two to three, and slow down the feed rate to reduce the load on the mill.

Bob Eustace
11-10-2013, 08:06 PM
Try a downcut Andy as your problem could be the job moving slightly. You could post a pic of your hold down set up and tell us the feed rate and depth of cut. 3D tabs are generally the norm as they don't slow the machine down. The Desktop is the most accurate machine in the range according to the experts here.

srwtlc
11-10-2013, 09:40 PM
Bit deflection/recovery as the machine slows to make the tab and then takes off again. Try the 3d tabs and see if it's better. Stop the cut after the first pass, before it makes the tab pass and see if it's present then.

myxpykalix
11-10-2013, 09:44 PM
you might also get some scrap material and redo your toolpaths and eliminate the tabs and rerun the toolpaths in scrap to see if you get the same results. If you do then you know the tabs are not the problem.

Or you could relocate your tabs and rerun the file on scrap to see if it does it also in the same location relative to the tabs to confirm it.:confused:

steve_g
11-10-2013, 10:26 PM
I agree with Scott... what speed and DOC are you using?

SG

myxpykalix
11-11-2013, 04:05 AM
I respectfully disagree with Scott. I can't imagine that the bit deflects to that degree, that would make the same issues at each slowdown/speedup location.
Plus i can't imagine that the machine can speed up and have to slow down in such a small space.

I still think it is a vector issue. Have you checked to see if you have any duplicate vectors hiding anywhere?

One way to check this is to do like i suggested about redoing the file and changing tab location and seeing if that problem follows to the new location.

This isn't the first time i've been right (OR WRONG!):eek::D:rolleyes::confused:

steve_g
11-11-2013, 08:41 AM
Jack...
It’s all just speculation! Here’s how I see it happening:
Spiral tool path at a high chipload factor. Bit is deflecting and any machine slop is all preloaded in one direction. Machine stops to negotiate first tab and all preload and deflection is relaxed. Continuing on after first tab and does not develop chipload of pre tab cutting because remaining cut is shallow and likely does not reestablish full speed due to ramping at remaining tabs...

Now, I could just as easily make a case for another point of view! I went with this one because I ASSUMED that this was a vector that had been cut previously successfully without tabs.

SG

genek
11-11-2013, 11:14 AM
not happening on all tabs look close. My opinion There is a small out of aline there or a node is out of line with the rest.

Jack...
It’s all just speculation! Here’s how I see it happening:
Spiral tool path at a high chipload factor. Bit is deflecting and any machine slop is all preloaded in one direction. Machine stops to negotiate first tab and all preload and deflection is relaxed. Continuing on after first tab and does not develop chipload of pre tab cutting because remaining cut is shallow and likely does not reestablish full speed due to ramping at remaining tabs...

Now, I could just as easily make a case for another point of view! I went with this one because I ASSUMED that this was a vector that had been cut previously successfully without tabs.

SG

myxpykalix
11-11-2013, 06:31 PM
Steve,
This is why i put the caveat:
This isn't the first time i've been right (OR WRONG!) because i'm just guessing!:D
Sometimes you hit on the right solution...sometimes not:mad:

Because in my mind bit deflection is a "random occurance" to me and from what i read it was happening in the same location. So i surmised, what is it about that location would cause those reoccuring problems. My thought..the vectors.

I like trying to solve a puzzle like this and going over the various solutions to try to figure it out. So i'd like to know finally what the problem is...:confused:

awalt1250
11-11-2013, 07:28 PM
I think I have found a solution to my problem, and it was not the tabs after all. The tabs were a symptom of the problem.

I drew up and cut another file using shapes (circle and rectangle) that had not been edited or modified. i.e bezier curves, points etc. and got the same results at the tabs.

As it turns out, my spindle mount wobbles back and forth if you grab ahold of the spindle itself.

This brings up a whole new question... How do you get a wrench down in there to tighten the allen screws? There are four screws that move as the spindle moves. When I first got the shopbot and cut my spoilboard, I remember it had slight ridges in it. Maybe that was the first indicator something was wrong.

See attached picture

gundog
11-11-2013, 08:27 PM
On mine I run the Y car to the end of my x travel near 96" that allows me to lower my spindle fully past the edge of the table the 6 cap screws are accessible. I would also check your tram on the spindle to table.

Mike

awalt1250
11-16-2013, 10:26 PM
Finally solved it. I had to make a custom tool to reach the screw heads without taking the Z apart. The Bot runs much better now.