Jump to content


Photo

+bow Help

Experiencing difficulties

1 reply to this topic

#1 Seven7h Man

Seven7h Man

    Member

  • Members
  • 147 posts

Posted 25 May 2009 - 08:04 PM

I hate to post a help thread but here it goes. I just finished my first +bow, to the best of Slug's instructions, and i'm experiencing some difficulties with the prformance of the gun. The first thing is that the gun is a BITCH to prime. My Dad, let alone me, can berly cock it. The second thing is that in the evnt I am able to get it to the 3rd notch, the speed of the plunger is nothing copared to Slug's videos and ice's videos. In an atempt to fix it, I removed the plunger tube and lubed it with some more silicon liquid wrench. I reasembled the gun and to my suprise there was very minamal improvement. I did this about twice more, using liberal amounts each time, still with same mediocre preformance. I am compleatly puzzled about what to do, I can get a test fireing vid up by tomarrow night if requested. Any help at all would be greatly apreciated. Thanks.
  • 0

#2 Ryan201821

Ryan201821

    Prince Edward

  • Contributors
  • 1,892 posts

Posted 25 May 2009 - 08:43 PM

First of all, there is a +bow DIY thread which is pinned at the top of this forum. You should have posted this there.

Sounds like there is way too much friction which is causing the plunger head to travel slow. It could be a couple of things. First check that your plunger head is perpendicular with the nylon rod (plunger rod). If the end of the plunger rod isn't cut exactly straight, the plunger head will probably be crooked, thus causing friction.

Use a different lube. Specifically in the +bow, silicone grease has worked the best for me. In my experience, the more viscous lubricants tend to soak in the neoprene washer actually expanding the washers outer diameter. This also creates more friction, making the lubricant do the opposite of what it is intended to do.

As far as your problem concerning issues with priming the gun, it sounds like the added friction is causing this.
  • 0


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users