Strict Standards: Declaration of AuthPriv::doAuthByCookie() should be compatible with Auth::doAuthByCookie($name) in /home4/smith/public_html/faq/admin/lib/eleontev/Auth/AuthPriv.php on line 28

Strict Standards: Declaration of AuthPriv::authToCookie() should be compatible with Auth::authToCookie($name, $period = , $data = , $path = ) in /home4/smith/public_html/faq/admin/lib/eleontev/Auth/AuthPriv.php on line 28

Strict Standards: Declaration of AuthPriv::removeCookie() should be compatible with Auth::removeCookie($name) in /home4/smith/public_html/faq/admin/lib/eleontev/Auth/AuthPriv.php on line 28

Strict Standards: Declaration of AuthPriv::isPriv() should be compatible with Auth::isPriv() in /home4/smith/public_html/faq/admin/lib/eleontev/Auth/AuthPriv.php on line 28

Strict Standards: Declaration of AuthPriv::checkPrivAction() should be compatible with Auth::checkPrivAction() in /home4/smith/public_html/faq/admin/lib/eleontev/Auth/AuthPriv.php on line 28

Strict Standards: Non-static method PHP_Compat::loadFunction() should not be called statically in /home4/smith/public_html/faq/admin/common_share.inc.php on line 21

Strict Standards: Non-static method PHP_Compat::loadFunction() should not be called statically in /home4/smith/public_html/faq/admin/lib/Pear/PHP/Compat.php on line 95

Strict Standards: Non-static method PHP_Compat::loadFunction() should not be called statically in /home4/smith/public_html/faq/admin/lib/Pear/PHP/Compat.php on line 95

Strict Standards: Non-static method PHP_Compat::loadFunction() should not be called statically in /home4/smith/public_html/faq/admin/lib/Pear/PHP/Compat.php on line 95

Strict Standards: Declaration of SettingModel::getRecords() should be compatible with & AppModel::getRecords($limit = , $offset = ) in /home4/smith/public_html/faq/admin/modules/setting/setting/inc/SettingModel.php on line 17

Strict Standards: Declaration of SettingModel::save() should be compatible with AppModel::save(&$obj) in /home4/smith/public_html/faq/admin/modules/setting/setting/inc/SettingModel.php on line 17

Strict Standards: Declaration of KBClientView::stripVars() should be compatible with & BaseView::stripVars($values, $skip_keys = , $server_check = ) in /home4/smith/public_html/faq/client/inc/KBClientView.php on line 13

Strict Standards: Non-static method Registry::instance() should not be called statically in /home4/smith/public_html/faq/client/inc/common.inc.php on line 79

Strict Standards: Non-static method DBUtil::connect() should not be called statically in /home4/smith/public_html/faq/client/inc/common.inc.php on line 92

Strict Standards: Non-static method KBClientBaseModel::getSettings() should not be called statically in /home4/smith/public_html/faq/index.php on line 38

Strict Standards: Non-static method KBClientLoader::getManager() should not be called statically in /home4/smith/public_html/faq/index.php on line 62

Strict Standards: Non-static method AuthPriv::isAuth() should not be called statically in /home4/smith/public_html/faq/client/inc/KBClientLoader.php on line 69

Strict Standards: Non-static method Auth::_isAuth() should not be called statically in /home4/smith/public_html/faq/admin/lib/eleontev/Auth/AuthPriv.php on line 126

Strict Standards: Non-static method AuthPriv::getUserId() should not be called statically in /home4/smith/public_html/faq/client/inc/KBClientLoader.php on line 70

Strict Standards: Non-static method AuthPriv::getPrivId() should not be called statically in /home4/smith/public_html/faq/client/inc/KBClientLoader.php on line 71

Strict Standards: Non-static method AuthPriv::getRoleId() should not be called statically in /home4/smith/public_html/faq/client/inc/KBClientLoader.php on line 72

Strict Standards: Non-static method KBClientLoader::getView() should not be called statically in /home4/smith/public_html/faq/index.php on line 63

Strict Standards: Declaration of AppAjax::getJavascript() should be compatible with xajax::getJavascript($sJsURI = '', $sJsFile = NULL) in /home4/smith/public_html/faq/admin/lib/core/app/AppAjax.php on line 23

Strict Standards: Only variables should be passed by reference in /home4/smith/public_html/faq/client/inc/default/view/KBClientView_entry.php on line 748

Strict Standards: Only variables should be assigned by reference in /home4/smith/public_html/faq/client/inc/default/view/KBClientView_entry.php on line 628

Strict Standards: Only variables should be assigned by reference in /home4/smith/public_html/faq/client/inc/default/view/KBClientView_entry.php on line 640

Strict Standards: Only variables should be assigned by reference in /home4/smith/public_html/faq/client/inc/KBClientPageRenderer.php on line 73

Strict Standards: Only variables should be assigned by reference in /home4/smith/public_html/faq/client/inc/KBClientPageRenderer.php on line 74
SMITH Manufacturing | Frequently Asked Questions
Bookmark and Share
 
PRODUCTS
 
SUPPORT
 
EVENTS & NEWS
 
SMITH Catalog
 
Join SMITH Xtreme Team
 
Made in USA | Established 1990
 
Search:     Advanced search
Browse by category:
Knowledgebase | Ask a Question |

Our cutters cracked during our grooving operation. This is the first time it has happened and it is only a few cutters cracking in the same position after only 10,000 feet.

We finished the follow up-checks on the cutters we produced for you (3158.0, 3158.1). Nothing appears out of the ordinary with the cutters and tested in our tolerances. The 3158 from the CPU12 that had lost a few pins and cracked in half tested for hardness in the 42-48 range. The ones that cracked in half tested no harder in the middle of the cutter than the the previous batch or the older batch.

We believe there is a problem with your machine, operator, surface, or set-up. The 3158 from the CPU10 (different site) showed none of the same issues as the ones used on the CPU12. The problems with the 3158s that were sent back from the CPU10 is it appears they were packed too tightly, and froze up on the shaft. Multiple cutters show wear on just one or two of the tips. None of these cutters appear to have lost any carbide; even on the excessively worn tips, the carbide remained intact.  

Final analysis: the drum was set up too tightly, as nothing else appears to be wrong with the cutters.

This article was:  
Add comment
Also listed in
folder Cutters

Prev   Next
     content

Others in this category
document What is the best way to prepare new concrete surfaces for thermoplastic pavement markings?
document I have joint compound to remove and only own an SPS10. What do I do?
document I have a KR10 Scarifier with a 6 - 9/16" shafted 10" drum. What is the best cutter to remove industrial coatings and epoxy bed mortar on concrete achieving a CSP6 profile? Are they your carbide strip-it or flail cutters?
document I need to remove 30,000 SF of waterproof membrane coatings on a parking deck. A waterblast contractor did a great job and charged us $1.00 per foot, but when a new operator started using the equipment, he wasnt able to achieve the same removal results and started damaging the surface, requiring us to apply a lot of waterproof membrane coating. Our current contractor is using 4 walk-behind scarifiers and are only getting 2500 SF per day. We are renting a parking lot for $5,000 per month, and expect the job to be completed in that time, do you have any recommendations to getting the job completed faster?
document How can we achieve a shotblast finish using a scarifier on concrete?
» More articles



 
© 2015 SMITH Manufacturing Co., Inc. - 1610 S. Dixie Highway, Pompano Beach, FL 33060-8913
Toll Free: 1-800-653-9311 | Ph: 954-941-9744 | Fax: 954-545-0348
Specifications and data are subject to change without notice.
Web Analytics