Community
Search
Notices
Gas Engines Questions or comments about gas engines can be posted here

Canister Setup - Brison 2.4 (40cc)

Thread Tools
 
Search this Thread
 
Old 03-24-2005 | 09:24 PM
  #1  
Thread Starter
My Feedback: (42)
 
Joined: Jun 2002
Posts: 527
Likes: 0
Received 0 Likes on 0 Posts
From: Garland, TX
Default Canister Setup - Brison 2.4 (40cc)

I'm in the planning stages of my next project, a Ultra Hots (12-14lb fun-fly)
The plan is to use a Brison 2.4 (40cc) I have lying around.
I'm toying with the idea of putting a canister exhaust on it.

Objectives, using the "stock" Bennett muffler as a baseline:

1. Jaw dropping low sound (I know prop selection is important - Separate discussion?)
2. No degradation in performance (More power would be nice)
3. Equal/better throttle response and linearity (No steps on/off the pipe)
4. Budget maximum 1lb added weight
5. Budget maximum $150 added cost

Based on what I have read, I figure a 50-60cc can would work well.
(Any specific suggestions from people who have done this on this size motor?)

I probably could fabricate the header using pieces from KS.
(How about 12-14in length 3/4in ID pipe to start?)
(What trade people might I approach to fabricate one for me?)

I understand how to adjust/tune the length on a bench setup.
(How short a header should I expect to end up with?)

Note this is a pretty small powerplant, and noise is reasonably easy to keep under control.
e.g. I have a J&A Pitts muffler on my other one, and it does the job well.
Question is, should I even bother or wait until I build something bigger? (100cc+)

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are On



Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.