|Forum topic by MrDan||posted 1090 days ago||1166 views||0 times favorited||20 replies|
1090 days ago
I finally saved enough pennies to buy the coveted Forrest Woodworker II (thin kerf) and I have to say I’m extremely disappointed.
Let me preface this by telling a brief story:
I picked up a Forrest Woodworker I from a flea market one day for $2. It was covered in pitch and amongst a ton of really crappy blades. (A diamond in the rough if you will) I figured for $2 it was worth it even if I had to replace a few carbide teeth and get the whole thing sharpened I’d still come out ahead.
So I took it home, cleaned off the pitch and made a few test cuts (rip cuts to be exact). The results were PHENOMENAL. (It was dull and 7 of the carbide teeth had small chips in them) Now, granted I had to use more force than normal to push the wood through the cut due the the teeth being dull, and I got a touch of burning on the edge—but the cut was like glass. No saw marks at all—and this is a WWI, which is not even supposed to be as good for ripping as a WWII.
So I was sold on Forrest from that moment on. A true believer.
Anyways yesterday I installed the recently purchased WWII and the results I got were NOTHING like the results from the dull WWI. Saw marks all along the ripped edge—it looked like the results from my thin kerf ryobi blade which I always had to touch up on the jointer due to the saw marks.
The first few cuts were without the recommended blade stabilizer, so I figured that was the problem and installed it next to the blade. The results with the stabilizer? WORSE. Even more saw marks along the ripped edge.
The only thing I can think of is that maybe the difference is the width of the blade. The dull WWI that I used was full kerf. I’m not sure why that would be better, as my table saw was designed for thin kerf…but maybe there’s just less vibration.
Anyway, I’m calling Forrest tomorrow to see what they say, but in the meantime I thought I’d ask anyone here if they have had any similar issues.
Thanks for any thoughts you might have on the issue.