saw chain id needed

Arborist Forum

Help Support Arborist Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

AVB

ArboristSite Operative
Joined
Jun 30, 2010
Messages
469
Reaction score
164
Location
Elora, TN
I trying to help a gentlemen over on the AnswerArmy site that needs his chain id on his 435e.

Here is info he has provided.
The bar/chain is .325", 50 mils, DL66. It is pixel, has sign on it, but I am still not sure if this is H30 chain, or SP33G? The SP33G I don't even see on Husqvarna chain table. These two chains have all the parameters identical, except for cutting angle (80 degrees, vs 85 degrees, and the tooth height (30 mils vs 25 mils). And each chain needs different sharpening tool, per User Manual. The only marking on the chain links I see is number 22 stamped on the cutting teeth and number 30 on the running links. If I was going to guess, this 30 refers to H30, does it? But also there is H22 chain, semi-chisel, with all the same parameters as H30. Do you see my confusion now?

Thanks in advance for any help.
 
https://www.husqvarna.com/us/accessories/chainsaw-chains/h22-325-1-3-mm/501840966/

https://www.husqvarna.com/us/accessories/chainsaw-chains/h30-pixel-325-1-3-mm/501840656/

looks to me like the h22 is not pixel or Narrow kerf and is rated for 5 more cc of displacement. These are most likely made by Oregon with Husqvarna stampings. the SP33 seems to be the made by Husky chain to replace the h30. https://www.husqvarna.com/us/access...sp33g-semi-chisel-pixel-325-1-3-mm/581643666/

95 class Oregon is comparable to h30. Oregon now has speedcut chain for the pixel 0.325

If you mean the little device with rollers as the sharpening tool, that rests on top of the chassis and needs put the file something like 20% above the top plate so it would not seem unreasonable to need a seperate tool. I have one for the discontinued lg chain in 0.325 not sure what the Husqvarna lettering is for that one. the Oregon or Stihl guides that attach to the file should work for that size file regardless of the chain coding. Or use no file guide.
 
Back
Top