lshuck
01-07-2010, 08:55 PM
I have a PRS BT48 Standard using PW 2.015 and Sb 3.6.12.
On 3 occasions with 2 within the last 5 days when making a profile cut and after running through the first of several parts in the file the bit has started a decline and bored into the spoilboard.
All parts received the same parameters when specifying the tool path (.5 cut per pass with .47 as depth). The bit starts to dive on an inclined plane and in one case (still using an older Sb) I did not catch it in time and the bit broke. The second time with the updated Sb I caught it but it left the bit in the material.
I Thought I might not have tightened the bit enough but I used the same technique I always do.
After the first recent dive, I contact SB and Frank said he had not heard of that problem but recommended upgrading to the current Sb to 3.6.5. as a precautionary measure.
I checked the run file and could not see any instruction that would explain the diving and upgraded the Sb to3.6.5.
Then, today when cutting Sample LinkerLogs with a the updated Sb, a new bit and a new collet I had the same experience. I then redid the tool path and the second time it worked fine.
Any of you had this problem and if so what did you find to correct it? Or any ideas?
Les
On 3 occasions with 2 within the last 5 days when making a profile cut and after running through the first of several parts in the file the bit has started a decline and bored into the spoilboard.
All parts received the same parameters when specifying the tool path (.5 cut per pass with .47 as depth). The bit starts to dive on an inclined plane and in one case (still using an older Sb) I did not catch it in time and the bit broke. The second time with the updated Sb I caught it but it left the bit in the material.
I Thought I might not have tightened the bit enough but I used the same technique I always do.
After the first recent dive, I contact SB and Frank said he had not heard of that problem but recommended upgrading to the current Sb to 3.6.5. as a precautionary measure.
I checked the run file and could not see any instruction that would explain the diving and upgraded the Sb to3.6.5.
Then, today when cutting Sample LinkerLogs with a the updated Sb, a new bit and a new collet I had the same experience. I then redid the tool path and the second time it worked fine.
Any of you had this problem and if so what did you find to correct it? Or any ideas?
Les