X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Thu, 18 May 2006 10:41:07 -0400 Message-ID: X-Original-Return-Path: Received: from imf20aec.mail.bellsouth.net ([205.152.59.68] verified) by logan.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 1117988 for lml@lancaironline.net; Wed, 17 May 2006 21:33:22 -0400 Received-SPF: none receiver=logan.com; client-ip=205.152.59.68; envelope-from=aadamson@highrf.com Received: from ibm64aec.bellsouth.net ([68.19.102.121]) by imf20aec.mail.bellsouth.net with ESMTP id <20060518013233.LDX23162.imf20aec.mail.bellsouth.net@ibm64aec.bellsouth.net> for ; Wed, 17 May 2006 21:32:33 -0400 Received: from Typhoon ([68.19.102.121]) by ibm64aec.bellsouth.net with ESMTP id <20060518013233.YKYJ22396.ibm64aec.bellsouth.net@Typhoon> for ; Wed, 17 May 2006 21:32:33 -0400 From: "Alan K. Adamson" X-Original-To: "'Lancair Mailing List'" Subject: Engine performance prediction software X-Original-Date: Wed, 17 May 2006 21:32:29 -0400 X-Original-Message-ID: <006401c67a1a$edadda50$0501a8c0@highrf.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcZ6Gu0en3QKzvfSRA+PZJCWiIrhEg== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 I've been tinkering with some pretty cool Python code that for the IO-360A, or the O-360A/C creates a very nice table of output similar to the below. (for the O-360A as an example). ---------------------------------------------------------------------------- ------------------------ | Press. | Std. | 100 HP -- 55% Rated | 117 HP -- 65% Rated | 135 HP -- 75% Rated | Alt. | Alt. | Approx. Fuel 7.8 Gal/Hr | Approx. Fuel 9 Gal/Hr. | Approx. Fuel 10.6 Gal/Hr | 1000 |Temp. | | | | Feet |deg F | RPM & Man. Press. | RPM & Man. Press. | RPM & Man. Press. ---------------------------------------------------------------------------- ------------------------ | | | 2100 | 2200 | 2300 | 2400 | 2100 | 2200 | 2300 | 2400 | 2100 | 2200 | 2300 | 2400 | 0| 59| 21.0 | 20.3 | 19.8 | 19.3 | 23.5 | 22.7 | 22.1 | 21.6 | 26.1 | 25.1 | 24.5 | 23.9 | 1000| 55| 20.7 | 20.0 | 19.5 | 19.0 | 23.3 | 22.4 | 21.8 | 21.3 | 25.8 | 24.8 | 24.2 | 23.6 | 2000| 51| 20.4 | 19.7 | 19.2 | 18.8 | 23.0 | 22.1 | 21.6 | 21.1 | 25.5 | 24.5 | 23.9 | 23.3 | 3000| 48| 20.2 | 19.4 | 19.0 | 18.5 | 22.7 | 21.8 | 21.3 | 20.8 | 25.2 | 24.2 | 23.6 | 23.1 | 4000| 44| 19.9 | 19.2 | 18.7 | 18.3 | 22.4 | 21.5 | 21.0 | 20.5 | 24.9 | 23.9 | 23.3 | 22.8 | 5000| 41| 19.7 | 18.9 | 18.5 | 18.0 | 22.1 | 21.3 | 20.8 | 20.3 | FT | 23.6 | 23.1 | 22.5 | 6000| 37| 19.4 | 18.7 | 18.2 | 17.8 | 21.9 | 21.0 | 20.5 | 20.0 | FT | FT | 22.8 | 22.3 | 7000| 34| 19.1 | 18.4 | 18.0 | 17.6 | 21.6 | 20.8 | 20.3 | 19.8 | FT | FT | FT | 22.0 | 8000| 30| 18.9 | 18.2 | 17.8 | 17.4 | 21.4 | 20.5 | 20.0 | 19.6 | FT | FT | FT | FT | 9000| 26| 18.7 | 18.0 | 17.6 | 17.2 | FT | 20.3 | 19.8 | 19.3 | FT | FT | FT | FT | 10000| 23| 18.5 | 17.8 | 17.3 | 17.0 | FT | FT | 19.6 | 19.1 | FT | FT | FT | FT | 11000| 19| 18.3 | 17.6 | 17.1 | 16.7 | FT | FT | FT | 18.9 | FT | FT | FT | FT | 12000| 16| 18.0 | 17.3 | 17.0 | 16.6 | FT | FT | FT | FT | FT | FT | FT | FT | 13000| 12| FT | 17.2 | 16.7 | 16.4 | FT | FT | FT | FT | FT | FT | FT | FT | 14000| 9| FT | FT | 16.6 | 16.2 | FT | FT | FT | FT | FT | FT | FT | FT | 15000| 5| FT | FT | FT | 16.0 | FT | FT | FT | FT | FT | FT | FT | FT ---------------------------------------------------------------------------- ------------------------ It simply takes the numbers off the Lycoming engine charts (from the owners manuals), and then does some math. He's built a library in Python that does most of the extrapolation and conversions. It's actually pretty simple code, but does take a little programming knowledge and some very basic Python knowledge (www.python.org). I'm working on an IO-540AB version at the moment. Probably the toughest part is taking some altitude values and converting them to Density Ratios, but Kevin wrote some code that does that as well. Seeing as we've been on this "technical" kick for a few days (thanks Rick Titsworth), I figured I'd post this. If anyone is interested, I can probably provide basic support, but I'm no crack python programmer.... Yet :)... I've reprinted most of the required information from Kevin here. http://legacyfg.jconserv.net/viewtopic.php?t=78 Have fun, Alan