Comment by evilduck
7 months ago
Another cynical take would be that SawStop has secretly invested heavily in a saw blade manufacturers to profit from more blades being destroyed when the stop event occurs.
7 months ago
Another cynical take would be that SawStop has secretly invested heavily in a saw blade manufacturers to profit from more blades being destroyed when the stop event occurs.
Competitor's versions of this don't destroy the blade. The reason competition no longer exist is because SawStop sued based on the limb detection, not the blade repositioning tech.
Expect better than SawStop to appear when able, and this issue to go away.
I'm actually kind of surprised that any implementation destroyed the blade. Like I don't actually care that the blade is moving, I care where the blade is moving. It seems like a trigger to yank the blade under the table would be the easier and more obvious way to do it.
A few-milliseconds yank covering up to a couple inches of blade height feels like a harder engineering problem than "trigger brakes already right near the blade to grab the shit out of the blade"
2 replies →
I have had two brake activations in as many weeks, one on a dado stack (don’t ask). Neither destroyed the blade. Both blades will be back in service within a week.
Just putting out there: the popular idea that blades are always trash after an activation is not true.
That said, cheap big box store blades without carbide teeth will die a horrible death.
Carbide teeth are actually the part that gets destroyed on SawStop activations. Carbide is very brittle, so the sudden stop fractures it.
4 replies →