@xxx.edu Sat Aug 12 10:11:23 1995 Date: Sat, 12 Aug 1995 05:00:00 GMT @xxx.edu @xxx.za Subject: Majordomo file: list 'diy_efi' file 'archive_num_7' -- >From Diy_Efi-Owner Fri May 6 20:03:11 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA13059; Fri, 6 May 94 20:03:11 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 AA13053; Fri, 6 May 94 16:03:10 -0400 @xxx.edu> To: DIY_EFI Cc: jsg Subject: admin stuff/ doc/ etc Date: Fri, 06 May 94 16:03:09 -0400 From: John S Gwynne Sender: Diy_Efi-Owner Precedence: bulk @xxx.edu -------- - please be careful *not* to send postings to 'DIY_EFI-owner'. Send postings to 'DIY_EFI'. Same goes for request to 'Majordomo' - I will try to enable file retrieval through this mail server over the weekend. - I intend to start a "Input/Output Description Document" that will be retrievable through this server. I want this to become specific enough that we can build the hardware from it. - Don't panic with "we should be doing this or that..." the list is only three days old and and I don't think anyone of us wants to do anything irrational. Once the newness wears-off and we get organized, then we will get serious about making decisions. (IMHO) I (as well as many of you) have spent months working on our own versions of EFI. I spent the last four month drawing up schematics for a 68HC000 based controller that I have already ordered part for. (not to mention the time I spent getting gcc to work as a cross-compiler on "my" SGI!) I will be flexible though in terms of changing controllers as I hope the rest of you will also. This decision on CPU's will *not* be made until our requirements *as a group* are well defined. - At some point I believe we'll have to vote on design issues. I would like to find a volunteer that would organize the necessary software for this. Some questions I would also liked answered are (and *please* don't just start a discussion on this now--think about it): - How many *will* actually build "something". - How much are you willing to spend? - How will those who can't build hardware, get hardware to help on software? If you wish to become the "official" pollster, e-mail me at "DIY_EFI-owner". thanks. 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 Fri May 6 20:58:20 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA13605; Fri, 6 May 94 20:58:20 GMT Received: from stdvax.gsfc.nasa.gov by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) @xxx.edu diy_efi-outgoing id AA13599; Fri, 6 May 94 16:58:16 -0400 Date: Fri, 6 May 1994 16:56:43 -0400 (EDT) @xxx.GOV (DIRK BROER) @xxx.GOV> Subject: Crank Triggered ignition To: DIY_EFI X-Vmsmail-To: @EFI Sender: Diy_Efi-Owner Precedence: bulk @xxx.edu >In any case, the timing position sensor type needs to be determined. I'm >told that this piece is the "weak link" in the Electromotive TEC-II >system. What do people think is the best way to go here? The TEC-II >uses a 60 tooth wheel and sensor to read crank postion. (a 120 tooth >wheel is available for distributor installations) Other crank triggered >ignition systems use magnets imbedded in the front pulley or harmonic >balancer. Others use optical triggers. What say? Anyone out there have >any practical experience? Do tell... A typical crank triggered ignition system - for racing - consists of a wheel with 4 bumps(magnetic) on it (Timing wheel). Position is sensed by a magnetic pickup. A typical system would have two pickups - one at 10 deg BTDC to start the car and another at 35 deg BTDC for the "run" mode. The crank triggered ignition replaces the points or electronics in the distributer The distributer is used to decide which cylinder should fire. Similar is the pickup arangement in GM's HEI distributer. This distributer has multiple (8 for a V-8) points on a toothed wheel. The signal to the control module looks like: _________/\ ___________ \/ The control module works like normal points as far as the coil is concerned >From Diy_Efi-Owner Fri May 6 22:28:44 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA00544; Fri, 6 May 94 22:28:44 GMT Received: from rpi.edu by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA00537; Fri, 6 May 94 18:28:39 -0400 @xxx.edu Received: from client.its.rpi.edu (goya.its.rpi.edu) by rpi.edu (4.1/SMHUB41); @xxx.edu Received: by client.its.rpi.edu (4.1/SUB16); @xxx.edu @xxx.edu> Subject: Re: Some thoughts and questions on EFI To: DIY_EFI Date: Fri, 6 May 1994 18:28:34 -0400 (EDT) @xxx.edu> from "The_Mechanic" at May 5, 94 09:43:37 pm X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 437 Sender: Diy_Efi-Owner Precedence: bulk Reply-To: DIY_EFI > > A couple of quick questions (from an electronics-ignorant ME type guy): > > - the 68HC11 microcontroller chip is an 8 bit unit, right? Is there a > similiar chip available in a 16 bit architecture? Would it even be > nescessary? > Hope this replied to the right address :-). But yes, there should be a 68HC16 now which is 16 bit architecture...I think Chrysler is going to be using it in their new computers. -- Greg >From Diy_Efi-Owner Sat May 7 04:53:57 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06109; Sat, 7 May 94 04:53:57 GMT Received: from localhost.eng.ohio-state.edu by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA06103; Sat, 7 May 94 00:53:56 -0400 @xxx.edu> To: DIY_EFI Subject: adm: File server now running Date: Sat, 07 May 94 00:53:56 -0400 From: John S Gwynne Sender: Diy_Efi-Owner Precedence: bulk Reply-To: DIY_EFI -------- The file server is now running. Send "help" (in the body of the message; @xxx. You will find the file "archive_current" in there now which has all the past post to DYI_EFI. I'll try to put something in cron to cycle files on a weekly bases soon. For now it's just one file. Late comers to the group should read this. Oh, by the way. If you have Mosaic checkout URL: http://hertz.eng.ohio-state.edu/ Anyone want to do a home page for DIY_EFI? 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 Sat May 7 05:48:06 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06423; Sat, 7 May 94 05:48:06 GMT Received: from fsa.cpsc.ucalgary.ca by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA06417; Sat, 7 May 94 01:48:04 -0400 Received: from aa.cpsc.ucalgary.ca (aa.cpsc.ucalgary.ca [136.159.4.5]) @xxx.ca>; Fri, 6 May 1994 23:45:08 -0600 @xxx.ca (Robert Fridman) Received: by aa.cpsc.ucalgary.ca (1.2; from fridman@localhost) @xxx.ca>; Fri, 6 May 1994 23:46:53 -0600 @xxx.ca> Subject: Re: WWW home page To: DIY_EFI Date: Fri, 6 May 1994 23:46:52 -0600 (MDT) @xxx.edu> from "John S Gwynne" at May 7, 94 00:53:56 am Content-Type: text Content-Length: 467 Sender: Diy_Efi-Owner Precedence: bulk Reply-To: DIY_EFI John S Gwynne said: > > -------- > Oh, by the way. If you have Mosaic checkout > URL: http://hertz.eng.ohio-state.edu/ > Anyone want to do a home page for DIY_EFI? > I'll have a go at it. I've set up an http server already. Send me private mail and we can hash out the details. RF. ------------------------------------------------------------------------- 83 R100 DoD 749 Robert Fridman @xxx.ca 84 320i >From Diy_Efi-Owner Sat May 7 19:26:44 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA10446; Sat, 7 May 94 19:26:44 GMT Received: from localhost.eng.ohio-state.edu by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA10440; Sat, 7 May 94 15:26:42 -0400 @xxx.edu> To: DIY_EFI Cc: jsg Subject: admin: Document distribution Date: Sat, 07 May 94 15:26:41 -0400 From: John S Gwynne Sender: Diy_Efi-Owner Precedence: bulk Reply-To: DIY_EFI -------- After considering several formats, I'm now inclined to use a hyper-text document through the WWW and Mosaic as the primary distribution. For those that do not yet have access to this, a postscript version at ftp.nau.edu (/public/graphics/gif/racing/DYI_EFI), and an ASCII stripped down version (no figures--straight HTML) will be placed on the file server. Mosaic is available for nearly all workstations, PC's, etc. If you have internet access, I strongly recommend installing Mosaic. It's free; you have no excess :). I would like to hear your comments. Post to DIY_EFI or email to DIY_EFI-owner. 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 Sat May 7 21:30:45 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA11057; Sat, 7 May 94 21:30:45 GMT Received: from fsa.cpsc.ucalgary.ca by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA11051; Sat, 7 May 94 17:30:43 -0400 Received: from fsf.cpsc.ucalgary.ca (fsf.cpsc.ucalgary.ca [136.159.2.6]) @xxx.ca>; Sat, 7 May 1994 15:27:45 -0600 @xxx.ca (Robert Fridman) Received: by fsf.cpsc.ucalgary.ca (1.2; from fridman@localhost) @xxx.ca>; Sat, 7 May 1994 15:28:27 -0600 @xxx.ca> Subject: Re: admin: Document distribution To: DIY_EFI Date: Sat, 7 May 1994 15:28:27 -0600 (MDT) @xxx.edu> from "John S Gwynne" at May 7, 94 03:26:41 pm Content-Type: text Content-Length: 1044 Sender: Diy_Efi-Owner Precedence: bulk Reply-To: DIY_EFI John S Gwynne said: > > -------- > > After considering several formats, I'm now inclined to use a hyper-text > document through the WWW and Mosaic as the primary distribution. For those > that do not yet have access to this, a postscript version at ftp.nau.edu > (/public/graphics/gif/racing/DYI_EFI), and an ASCII stripped down version > (no figures--straight HTML) will be placed on the file server. Mosaic is > available for nearly all workstations, PC's, etc. If you have internet > access, I strongly recommend installing Mosaic. It's free; you have no > excess :). > > I would like to hear your comments. Post to DIY_EFI or email to DIY_EFI-owner. A program called lynx exists which handles all www protocols and runs on ASCII terminals. You get full hypertext functionality but no graphics. Its available through anon. ftp from ftp2.cc.ukans.edu:/pub/lynx. RF. ------------------------------------------------------------------------- 83 R100 DoD 749 Robert Fridman @xxx.ca 84 320i >From Diy_Efi-Owner Sun May 8 01:52:29 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA12102; Sun, 8 May 94 01:52:29 GMT Received: from [202.14.102.1] by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA12096; Sat, 7 May 94 21:52:25 -0400 @xxx.5) id NAA03083; Sun, 8 May 1994 13:47:36 +1200 @xxx.nz> @xxx.nz> Subject: What can we measure ? To: DIY_EFI Date: Sun, 8 May 1994 13:47:35 +1200 (NZST) X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 1303 Sender: Diy_Efi-Owner Precedence: bulk Reply-To: DIY_EFI I mentioned before that we should determine what we wanted a controller to do before we specified what should do it. Perhaps prior to that, we might discuss what parameters can be be measured, and what the relative usefulness is. For example, the exhaust pipe O2 sensor. What is available is pretty well restricted in its range of uses. I'll be using leaded fuel, so that rules that out. What about in an alky engine. Is an O2 sensor any use ? As I understand it, the O2 sensor gives us an indication of the efficiency of combustion but with a fairly slow response time. What other measurable parameters are there that could be used over a wider range of fuel types ? My interest in DIY_EFI is not to re-invent the standard factory device by effectively cloning it out of a mixture of other peoples bits. We have a slightly different perspective than the auto manufacturer. ie. We are not solely driven by the emmisions vs. $$$ equation. Yes, it has to be realistic in the $ department and we don't want to be belching black smoke, but we have some lattitude in the way the money is spent. I don't mind having a thermocouple in each exhaust port if that is going to give me more information about what's going on inside. Anybody care to discuss the relative merits of the sensors available ? Steve. >From Diy_Efi-Owner Sun May 8 02:44:27 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA12420; Sun, 8 May 94 02:44:27 GMT Received: from knuth.mtsu.edu by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA12414; Sat, 7 May 94 22:44:22 -0400 Received: by knuth.mtsu.edu (Smail3.1.28.1 #17) id m0pzyrG-000AVVC; Sat, 7 May 94 21:44 CDT @xxx.edu> @xxx. Lusky) Subject: Re: What can we measure ? To: DIY_EFI Date: Sat, 7 May 1994 21:44:46 -0500 (CDT) @xxx.nz> from "Steve Baldwin" at May 8, 94 01:47:35 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 3245 Sender: Diy_Efi-Owner Precedence: bulk Reply-To: DIY_EFI Steve Baldwin writes: > I mentioned before that we should determine what we wanted a controller > to do before we specified what should do it. > Perhaps prior to that, we might discuss what parameters can be be > measured, and what the relative usefulness is. > For example, the exhaust pipe O2 sensor. What is available is pretty > well restricted in its range of uses. I'll be using leaded fuel, so that > rules that out. What about in an alky engine. Is an O2 sensor any use ? Since you are using leaded fuel, is it safe to assume this is a racecar? If so, then part throttle and idle fuel economy and emissions are near 0 concern for you and you won't run closed loop, and if anything you'd want to run leaner than the O2 sensor can read accurately when you are under those conditions (although the M85 judges at F-SAE '93 majorly disagreed with me on that). An O2 sensor is useable with alky, CNG, propane, etc. One thing to remember about the O2 sensor and closed loop is that it is on top of the open loop system... closed loop is useless if you don't have the open loop calibration correct. > As I understand it, the O2 sensor gives us an indication of the > efficiency of combustion but with a fairly slow response time. What > other measurable parameters are there that could be used over a wider > range of fuel types ? Not directly. The O2 sensor tells you whether you are at stoichiometric or not, and which side you are on if you aren't. It doesn't tell you a whole lot about how far your A/F ratio is to either side of stoich, tho. When you ask what else could be used, I have to ask used for what? The O2 sensor is used for feedback for closed loop control at idle and part throttle to mantain stoichiometry for best overall catalyst efficiency when running on gasoline and using 3-way cats. > My interest in DIY_EFI is not to re-invent the standard factory device > by effectively cloning it out of a mixture of other peoples bits. We > have a slightly different perspective than the auto manufacturer. ie. We > are not solely driven by the emmisions vs. $$$ equation. Yes, it has to > be realistic in the $ department and we don't want to be belching black > smoke, but we have some lattitude in the way the money is spent. I don't > mind having a thermocouple in each exhaust port if that is going to give > me more information about what's going on inside. You don't need an FI system to have a thermocouple in each exhaust port... they provide nice info on cylinder balance, and can quickly point out problems. UEGO's are also realllly nice, but they're kinda expensive. As far as reinventing the OEM ECM goes, I see it as something to shoot for! The OEM stuff is considerably more advanced than the current aftermarket ECM's that I've played with. I'd like to be able add custom stuff in addition to the features already found in factory ECM's. Now I'm not saying that we should reverse engineer an OEM ECM--from what I've seen of them, there are enough proprietary pieces that it would be simpler to build something from scatch. -- @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 Sun May 8 09:27:33 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA13678; Sun, 8 May 94 09:27:33 GMT Received: from proffa.cc.tut.fi by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA13672; Sun, 8 May 94 05:27:30 -0400 @xxx.edu; Sun, 8 May 1994 12:27:23 +0300 @xxx.fi> @xxx.fi> Subject: Connecting analog signals To: DIY_EFI (DIY EFI) Date: Sun, 8 May 1994 12:27:23 +0200 (EET DST) X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1524 Sender: Diy_Efi-Owner Precedence: bulk Reply-To: DIY_EFI Hello, my name is Jari Porhio and I'm studying automation engineering here at Tampere Univ. of Technology. What comes to the hardware we choose to use, I would like to repeat what couple of you already said. Let's not design a new one-card microcomputer, let's use something which is readily available and working. I don't care what's printed on top of the processor, but I have one card very similar to the miniboard and it cost only $60 (including 68HC11A1, 32 K RAM, 32 K PROM, some minor components and a pc-board). Right now I'm thinking how to use these AD-converters on this chip, but unfortunately I don't have too much experience in practice. Instead of creating a chaos here, I thought I could ask some of you to email your thoughts to me and I would make a summary we could use later too. So this is Request For Comments ;) on Connecting analog signals to a processor. I think there are two possible situations, it must be cheap and simple (you know what you're doing) or it must be as flexible as possible (you don't have a clue). Specs: - AD-converter range 0...5/10/whatever V - very different kind of signals, potentiometers, O2-sensors, knock sensors - lowpass/bandpass filters required, bw of n kHz (active or passive?) - signal amplification and adaption to ADC range (offsets?) - peak limits - ? P.S. you can correct my grammar, if you do it nicely :) ____________________________________________________________________________ @xxx.fi : No offence :) >From Diy_Efi-Owner Mon May 9 20:35:31 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA21006; Mon, 9 May 94 20:35:31 GMT Received: from Rosie.UH.EDU by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA21000; Mon, 9 May 94 16:35:29 -0400 Received: from Jetson.UH.EDU by Jetson.UH.EDU (PMDF V4.2-11 #5185) id @xxx.EDU>; Mon, 9 May 1994 15:35:13 CDT Date: Mon, 09 May 1994 15:35:13 -0500 (CDT) @xxx.EDU Subject: Miniboard is the way to go... for now 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 Reply-To: DIY_EFI The miniboard sounds like the way to go. Instead of debating microcontroller options we can focus on EFI if we just use the miniboard. @xxx.edu -Jeff ÿ