15800 on a stock 260

[jhellwig]

I was playing with my new tach from bailys today. Held it to the 260 and pulled the trigger. Got it to 14.5k. Tried it again and it got clear up to 15800. I know that is way to fast but how can this be happening on a fairly new and unabused 260? Or am I just doing something wrong with the way I am using the tach? I always did think the saw seamed to run awfully fast at wot out of the cut but chalked it up to being a new saw that I wasn't used to.

I know that isn't even as fast as the saw has run because it sounded slower to my ear than other times.

 

[computeruser]

At least you've now got the tach to train your ears with!

 

[Trigger-Time]

If saw was not good and warmed up.......maybe set it a little
richer, cut some wood to get it up to temp then recheck it.

 

[jhellwig]

It runs even faster after it has been warmed up good. It was no where near warmed up though. I fear there might be some issue with the saw causing it.

 

[Trigger-Time]

It runs even faster after it has been warmed up good. I fear there might be some issue with the saw causing it.

If the tach is right........richen it up
Has muffler been modded?

 

[jhellwig]

No I have not modded the muffler yet. I have to wait till next weekend to mess with the saw further.

 

[Trigger-Time]

Are you using gas with ethanol in it?

Thats all I got.........need to wait on the experts :bang:

 

[jhellwig]

Are you using gas with ethanol in it?

Surprisingly enough not this time. At leased not that I know of. 91 octane from the busiest gas station around so who knows how old, mixed with ethanol and cruddy it is.

 

[Cut4fun]

I had missed a few tunes by ear too before getting a tach to double check myself. Here is a old winter post.
I then messed with winter project 5000 and my by ear was way off on it, it tached 15,340 rpms, reset it down to 13,300 now too.
Most of my other stock 5000's seem to run best a little lower then the above one.

 

[Trigger-Time]

Surprisingly enough not this time. At leased not that I know of. 91 octane from the busiest gas station around so who knows how old, mixed with ethanol and cruddy it is.

Ethanol will make one run leaner (faster)........I don't know if thats it or not.

 

[Cut4fun]

Why not pull the plug and look at it (check coloring ), then set the carb to 4 stroking and then back it off a hair (leaning it) and then tach it to see where its at.
Have you ever adjusted on the carb before?

 

[jhellwig]

I had missed a few tunes by ear too before getting a tach to double check myself. Here is a old winter post.
I then messed with winter project 5000 and my by ear was way off on it, it tached 15,340 rpms, reset it down to 13,300 now too.
Most of my other stock 5000's seem to run best a little lower then the above one.

I wouldn't doubt that if I tuned it by ear that it could probably be that far off but I haven't adjusted anything on the saw other than the chain.

And the plug color looks good to me.

 

[jhellwig]

Hrm. Turned the H out almost a half turn and that droped it to 14.5k. Jump from four stroking to two stroke by tone. Must have an air leak. Back to the dealer for warenty work.


Maybe dads constand bogging of the saw is the only thing that saved it.

 

[SawTroll]

I was playing with my new tach from bailys today. Held it to the 260 and pulled the trigger. Got it to 14.5k. Tried it again and it got clear up to 15800. I know that is way to fast but how can this be happening on a fairly new and unabused 260? Or am I just doing something wrong with the way I am using the tach? I always did think the saw seamed to run awfully fast at wot out of the cut but chalked it up to being a new saw that I wasn't used to.

I know that isn't even as fast as the saw has run because it sounded slower to my ear than other times.

Sort of reminds me of my 361, when I got a tach, but my numbers were more modest.
It tached at 14280 after a few minutes on idle, then at 14600 - got it down to 14080, and left it there (15" bar, 8-pin 3/8").....