@xxx.edu Fri Jan 6 12:23:54 1995 Date: Fri, 6 Jan 95 09:15:28 GMT @xxx.edu @xxx.za Subject: Majordomo file: list 'diy_efi' file 'archive_num_1' -- >From Diy_Efi-Owner Thu May 5 02:04:29 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA11465; Thu, 5 May 94 02:04:29 GMT Received: from cs.utexas.edu by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) @xxx.edu diy_efi-outgoing id AA11459; Wed, 4 May 94 22:04:25 -0400 @xxx.edu>; Wed, 4 May 1994 21:04:00 -0500 Received: by levelland.cs.utexas.edu (5.64/Client-v1.4) id AA05690; Wed, 4 May 94 21:03:43 -0500 Date: Wed, 4 May 1994 21:03:41 -0500 (CDT) @xxx.edu> Subject: first post... To: Do-It-Yourself EFI @xxx.edu> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Diy_Efi-Owner Precedence: bulk @xxx.edu Whoa... A virgin mailing list, I feel so priveleged! :) OK- Let me introduce myself. I am a CS major at UT, and am currently employed with IBM. I worked for 4 years for Oceaneering International, specifically in the ROV devision. (ROV = Remotely Operated Vehicle). The ROV's that we build were sub-sea robots, used mostly by the Navy and the oil industry, but some use by excavators (Space Shuttle Challenger). So the purpose of the above information is to let you know that I have been around a lot of EE people, and I have helped build the electronics on these things. As a CS student, I am specializing in software development in the area of engineering-type tools. I'm good at programming, but I am lacking in the EE dept. I feel 110% confident that I could program an EFI system, but I don't have a good understanding of the hardware involved. I am familiar with A/D boards, however. Rather than diving headfirst into a project to development my on EFI, I would like to start out by monitoring the vehicle's computer with a computer. The best way for me to start out is probably to get an A/D board, and something that I will be able to use for a long time (IE- has enough functions so that I can do more with it as I learn). So any suggestions on a *cheap* a/d board? I went to the library this past summer and got info out of one of the EE mag's on making an A/D board, but it didn't look like it would do too well with a car. Not enough input/outputs. I have used Analog Devices boards, and GenPak boards. I tried to contact Analog Devices recently, but never was able to find them. GenPak is very expensive, and isn't really an option (unless they have some stuff that is cheaper than what we used at OI). One more thing- I have an '84 Z28, but for performance reasons, the computer now serves no purpose. I'm trying to think of a way to take advantage of the hardware sitting in there, and can't think of anything. Sorry that this wasn't too much about EFI, but if I can get set up, then I`ll be plugging away! I think that we can all learn a lot quicker if we share what we have, and I am willing to do some programming for the list. If anybody has a programming need, and a number of people on the list would use it, I would be happy to contribute. -Brian >From Diy_Efi-Owner Thu May 5 03:41:53 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA00536; Thu, 5 May 94 03:41:53 GMT Received: from localhost.eng.ohio-state.edu by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) @xxx.edu diy_efi-outgoing id AA00530; Wed, 4 May 94 23:41:51 -0400 @xxx.edu> To: DIY_EFI Subject: ok... second post Date: Wed, 04 May 94 23:41:51 -0400 From: John S Gwynne Sender: Diy_Efi-Owner Precedence: bulk @xxx.edu It's feeling a little used know... :) Let me introduce myself too. I'm a electrical engineering grad student. I graduated back in '86 with a BS... work for a while in the defense industry as a CPU hardware guy (I used 6809's and 68HC11's as controllers for airborne synthetic aperture radar systems).... and then returned to grad school. For a little over six years now I've been studying how to make low observable (stealth) aircraft. Well, now that I'm about to graduate that market is gone :(. Such is life. Anyways, my latest passion (rather resurgence) is playing with engines. Come to think of it, most of my toys all have engines (RC planes/boats/cars, dirt bike, Jeep,...). I liked what I read in Brian's post. If we can get a hand full of people together that can each contribute to a portion of an EFI project, I have no doubt that we can realize some of these dreams. That's a good lead into what I believe should be the first order of business. I personally believe, especially at this level of prototyping, that our first step should be to standardize on a bus configuration that each of us could adapt to. For instance, I have a small circuit to measure RPM that simply plugs into the tach port of my MSD unit. It's just a simple state machine based in a GAL chip that controls a 82C54 (10MHZ programmable timer) with a high speed comparator/conditioner (ok, looks like 14 components for conditioning and surge protection). Its use is simple and does not require CPU intervention. For everyone interested in taking advantage of this circuit and knowing that we will never get everyone to agree upon the same CPU, it would be to our advantage if we could agreed upon a common bus structure that would be compatible with each of these small sensor interface circuits. That also gives us the flexibility to change circuits easily for upgrades and enhancements. I'm thinking something *vary* simple that could be adapted to by everything from a parallel port of a laptop to a single board 68HC11. In other words a common point that we can work from since I feel its ridiculous to expect the entire design at once. This also gives us the ability to start small with simple "engine instrumentation" that will then expand into the final "engine management" system. I would like to hear comments for everyone on this as this is something that must be decided up-front. It will be much more difficult to work together if we all use the CPU bus directly (i.e., asynchronous 68000 type CPU bus vs the synchronous 68HC11 vs the parallel port on a lap top). IMHO, we need a common point between all of these approaches. John S Gwynne @xxx.edu _______________________________________________________________________________ T h e O h i o - S t a t e U n i v e r s i t y ElectroScience Laboratory, 1320 Kinnear Road, Columbus, Ohio 43212, USA Telephone: (614) 292-7981 * Fax: (614) 292-7292 ------------------------------------------------------------------------------- >From Diy_Efi-Owner Thu May 5 04:28:35 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA00867; Thu, 5 May 94 04:28:35 GMT Received: from knuth.mtsu.edu by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) @xxx.edu diy_efi-outgoing id AA00861; Thu, 5 May 94 00:28:32 -0400 Received: by knuth.mtsu.edu (Smail3.1.28.1 #17) id m0pyv3a-000AVPC; Wed, 4 May 94 23:29 CDT @xxx.edu> @xxx. Lusky) Subject: Introductions To: DIY_EFI Date: Wed, 4 May 1994 23:29:06 -0500 (CDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 702 Sender: Diy_Efi-Owner Precedence: bulk @xxx.edu So are we supposed to introduce ourselves when we join? Right now I'm a computer science undegrad at Middle Tennessee State University. I spent three years as a mechanical engineering major at UTexas-Austin, and way too much time on SAE student design competition projects. My electronics background is pretty much nill, but I have done some FI calibrations. The systems I've calibrated used the 91 GM v-8 TBI ECM or the EFI Technologies Performance Series ECU. I'm also familiar with some of the FI equipment used with CNG. -- @xxx.edu "Turbos are nice but I'd rather be blown!" 89 Jeep Wrangler - 258 / pile of junk! 80 Toyota Celica - 20R / 5spd >From Diy_Efi-Owner Thu May 5 05:18:31 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA01036; Thu, 5 May 94 05:18:31 GMT Received: from Rosie.UH.EDU by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) @xxx.edu diy_efi-outgoing id AA01029; Thu, 5 May 94 01:18:24 -0400 Received: from Jetson.UH.EDU by Jetson.UH.EDU (PMDF V4.2-11 #5185) id @xxx.EDU>; Thu, 5 May 1994 00:16:23 CDT Date: Thu, 05 May 1994 00:16:23 -0500 (CDT) @xxx.EDU Subject: Another Introduction - EFI Design To: DIY_EFI @xxx.EDU> @xxx.edu" Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT Sender: Diy_Efi-Owner Precedence: bulk @xxx.edu Well- Its great that a mailing list just for EFI ECU/M design is here. I'm a Computer Science student at UH now. But I'll be at UT in Austin next year. I've been real interested ECU/M operation and modification ever since I bought a Chevy in January. I am somewhat familiar with the GNC3 in the Grand Nationals and Turbo Trans-Ams. Right now I'm working on 5.7L TBI modification. As far as electronics, I am pretty handy with 8048s. Hope this mailing list takes off! Jeff Fisher @xxx.edu >From Diy_Efi-Owner Thu May 5 08:17:23 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA01266; Thu, 5 May 94 08:17:23 GMT Received: from suvm.acs.syr.EDU by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) @xxx.edu diy_efi-outgoing id AA01260; Thu, 5 May 94 04:17:19 -0400 Received: from gamera.syr.edu by SUVM.SYR.EDU (IBM VM SMTP V2R2) with TCP; Thu, 05 May 94 04:17:35 LCL Received: by gamera.syr.edu (5.0/Spike-2.0) id AA09714; Thu, 5 May 1994 04:18:25 +0500 @xxx.edu> To: DIY_EFI Subject: Another first post... Date: Thu, 05 May 1994 04:18:24 -0400 @xxx.edu> Content-Length: 1199 Sender: Diy_Efi-Owner Precedence: bulk @xxx.edu >development in the area of engineering-type tools. I'm good at >programming, but I am lacking in the EE dept. I feel 110% confident that >I could program an EFI system, but I don't have a good understanding of >the hardware involved. Well, I'm sort of the opposite. I'm a undergrad CS major with plenty of FI hardware experience. (I used to work summers in a junkyard as a mechanic. You learn FAST about all the systems, and how to modify/repair factory systems with little instrumentation) I'd love to build my own FI controller (see below), but I'm lacking in the engineering department. My current "eternal resto project" is a '71 Cutlass. It's a Olds 350 powered beast; in the late 70's/early 80's GM made a manifold for these motors that was setup for port FI. I have several of the manifolds, but need a controller. Right now, I'm just trying to amass as much information as possible. Of course, this list has to come alive 1 week before I leave school w/ easy mail access. (But it's better than never!) --> Bob Valentine <-- @xxx.edu <-- "Hard Acceleration Saves Costly Aggravation" >From Diy_Efi-Owner Thu May 5 15:28:36 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA03101; Thu, 5 May 94 15:28:36 GMT Received: from mtu.edu by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) @xxx.edu diy_efi-outgoing id AA03095; Thu, 5 May 94 11:28:33 -0400 Received: from barracuda4.me.mtu.edu.cael (barracuda4.me.mtu.edu) by mtu.edu with SMTP id AA21311 (5.65c/IDA-1.4.4); Thu, 5 May 1994 11:28:31 -0400 @xxx.edu> @xxx.edu> Subject: Re: your mail To: DIY_EFI Date: Thu, 5 May 94 11:28:30 EDT @xxx.edu>; from "John S Gwynne" at May 4, 94 8:02 pm X-Mailer: ELM [version 2.3 PL11] Sender: Diy_Efi-Owner Precedence: bulk @xxx.edu For some time now, I have been kicking around an idea for a pet project of mine. I have a 300 cubic inch straight six ford engine in a truck, and I am considering some sort of port efi. I think I can get it to work with a six cylinder setup off of something else. I have also been thinking of using a paxton supercharger on this setup. Any problems I may run into? I would want this to be totally closed loop, of course, and adjustable, as the truck currently is running a 4bbl, cam and headers, so it is not stock, and I would not want to try and adapt the lame stock ford efi. I thought about using a pro-jection or the like, but If I am going to do the work, I might as well go for max torque and mpg. Mark e-mail replies welcome @xxx.edu >From Diy_Efi-Owner Thu May 5 16:06:16 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA03466; Thu, 5 May 94 16:06:16 GMT Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) @xxx.edu diy_efi-outgoing id AA03454; Thu, 5 May 94 12:04:59 -0400 @xxx.edu> Date: Thu, 5 May 1994 10:45:54 -0500 @xxx.edu> To: DIY_EFI Subject: Intro ... Sender: Diy_Efi-Owner Precedence: bulk @xxx.edu An introduction, huh? After moving around NC,SC,TN, and IN, I'm finally settled in at Oak Ridge National Lab where I work as a development engineer in the Advanced Propulsion Technology Center. I'm an ME by trade. My graduate work at Purdue focused on misfire detection in spark ignition engines. My last job (prior to my wife's transfer to TN) was with Cummins Engine. I worked on the control algorithms and control systems for Cummins' new line of natural gas engines. Control algorithms are no problem. I need to know more about real time operating systems and some of the more esoteric hardware stuff. I have two projects that I'm pseudo-working on at the moment. One is an EFI system retrofit for my '72 Skylark. The second project is a single cylinder EFI setup for the 250cc engine in a friend's sprint car. Glad to see this list is getting going. Looking forward to a lot of good info. Jeff Armfield >From Diy_Efi-Owner Thu May 5 15:45:42 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA03178; Thu, 5 May 94 15:45:42 GMT Received: from [141.219.70.1] by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) @xxx.edu diy_efi-outgoing id AA03163; Thu, 5 May 94 11:40:19 -0400 Received: from barracuda4.me.mtu.edu.cael (barracuda4.me.mtu.edu) by mtu.edu with SMTP id AA21895 (5.65c/IDA-1.4.4); Thu, 5 May 1994 11:36:09 -0400 @xxx.edu> @xxx.edu> Subject: Re: ok... second post To: DIY_EFI Date: Thu, 5 May 94 11:36:08 EDT @xxx.edu>; from "John S Gwynne" at May 4, 94 11:41 pm X-Mailer: ELM [version 2.3 PL11] Sender: Diy_Efi-Owner Precedence: bulk @xxx.edu Ah, forgot to introduce myself.... I am a senior mechanical engineering student at Michigan Tech University, and my main focus is in engine design. I started school with Electrical Engineering, and finding out it wasn't my bag, switched. I am however, familiar with 6809, 68HC11 programming, and I guess I am just hung up on how to actually control the electronics of the setup. I am familiar with high-performance engines, and that is probably why most of us are on this list, because if we wanted stock engines, we could buy a stock car right? No flames please, correct me if I am wrong. Mark >From Diy_Efi-Owner Thu May 5 16:26:01 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA03804; Thu, 5 May 94 16:26:01 GMT Received: from doc.cc.utexas.edu by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) @xxx.edu diy_efi-outgoing id AA03798; Thu, 5 May 94 12:25:55 -0400 @xxx.1) id LAA09257; Thu, 5 May 1994 11:25:48 -0500 Date: Thu, 5 May 1994 11:25:46 -0500 (CDT) @xxx.edu> Subject: credentials To: DIY_EFI @xxx.edu> @xxx.edu> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Diy_Efi-Owner Precedence: bulk @xxx.edu Hi! I'm a mechanical engineering sophomore at the University of Texas, and I too love cars. As it stands, I don't possess a large working knowledge of electronic components (I am aware of the MC 6811 microcontroller, though) My specialty comes with the APPLICATION of engine control devices. I work at a company that builds automotive superchargers, and I enjoy extracting maximum horsepower. I'm here to learn, and would love to be of any assistance for anybody trying to build a system. I've got my own ideas for my personal car...a 1968 BMW 2002. Thanks! Erik Frank @xxx.edu >From Diy_Efi-Owner Thu May 5 17:18:22 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA04432; Thu, 5 May 94 17:18:22 GMT Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) @xxx.edu diy_efi-outgoing id AA04426; Thu, 5 May 94 13:18:21 -0400 Date: Thu, 5 May 94 13:18:21 -0400 From: jsg (John S Gwynne) @xxx.edu> Apparently-To: DIY_EFI Sender: Diy_Efi-Owner Precedence: bulk @xxx.edu (Message jsg:105) Received: from [192.105.104.3] by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/lib/mh/slocal -user jsg id AA04196; Thu, 5 May 94 12:57:40 -0400 Received: from by system3.lcs.gov.bc.ca with SMTP (1.37.109.6/16.2) id AA04255; Thu, 5 May 94 09:59:16 -0700 @xxx.ca X-Openmail-Hops: 1 Date: Thu, 5 May 94 09:58:30 -0700 Message-Id: <79A9A312@MHS> Subject: RE: intro & bus standard To: Diy_Efi-Owner Greetings from a small island in the Pacific Ocean. I am a ME working as a network analyst, no programming and no engineering. I have been trying to get started on a digital ignition system for about a year now. This is just a hobby for me so sometimes I find time for it and sometimes its on the back burner. I have been gathering tools and information to try and make this project as easy as possible. I now have a scope, signal gen., a HC11 EVB and a good book just about the HC11 with some automotive application examples. My biggest problem seems to be teaching myself assembler. I don't find assembler terribly exiting and would rather be using somebody else code; modifying it for my own purposes. I don't suppose any of the big developers have ever released any of their programs have they? Top secret stuff I hear. As for a bus standard I am not sure I exactly understand what the options are and for what reasons but I vote for whatever works with the 68HC11. Wes Evernden Victoria, BC ---------- I would like to hear comments for everyone on this as this is something that must be decided up-front. It will be much more difficult to work together if we all use the CPU bus directly (i.e., asynchronous 68000 type CPU bus vs the synchronous 68HC11 vs the parallel port on a lap top). IMHO, we need a common point between all of these approaches. John S Gwynne @xxx.edu _ >From Diy_Efi-Owner Thu May 5 17:24:02 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA04568; Thu, 5 May 94 17:24:02 GMT Received: from mtu.edu by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) @xxx.edu diy_efi-outgoing id AA04562; Thu, 5 May 94 13:24:01 -0400 Received: from cael1.me.mtu.edu.cael (cael1.me.mtu.edu) by mtu.edu with SMTP id AA00929 (5.65c/IDA-1.4.4); Thu, 5 May 1994 13:23:59 -0400 @xxx.edu> @xxx.edu> Subject: Re: credentials To: DIY_EFI Date: Thu, 5 May 94 13:23:56 EDT @xxx.edu>; from "The_Mechanic" at May 5, 94 11:25 am X-Mailer: ELM [version 2.3 PL11] Sender: Diy_Efi-Owner Precedence: bulk @xxx.edu > > Hi! > > I'm a mechanical engineering sophomore at the University of Texas, and I > too love cars. As it stands, I don't possess a large working knowledge > of electronic components (I am aware of the MC 6811 > microcontroller, though) My specialty comes with the APPLICATION of > engine control devices. I work at a company that builds automotive > superchargers, and I enjoy extracting maximum horsepower. I'm here to > learn, and would love to be of any assistance for anybody trying to build > a system. I've got my own ideas for my personal car...a 1968 BMW 2002. > > Thanks! > Erik Frank @xxx.edu > > Erik, what company do you work for? I am interested in blow-through systems at present, as I don't have a good base for a compressor to bolt onto with my I-6 project (Read previous post) Also, how does the blower pressure affect the fuel pressure of the efi systems? One more question, the pickup in question has a dual-tank system. Would I need to adapt two fuel pumps :( to the truck to utilize an efi retrofit? Mark ÿ