From owner-diy_efi Wed Dec 7 18:56:42 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA08014; Wed, 7 Dec 94 18:56:42 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-1.92/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 AA08003; Wed, 7 Dec 94 13:56:39 -0500 Message-Id: <9412071856.AA08003@coulomb.eng.ohio-state.edu> To: DIY_EFI Subject: admin: mail problems? In-Reply-To: Your message of "Wed, 07 Dec 94 12:58:07 EST." <9412071758.AA13205@ivan.prior.com> Date: Wed, 07 Dec 94 13:56:39 -0500 From: John S Gwynne Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI -------- In message <9412071758.AA13205@ivan.prior.com> , you write: | My goal is to have an easy to start, reliable, engine ready for next summer. wow... next summer... that's fast. And you have a "real" job too? :). | BTW: If I try to get any files from Majordomo@coulomb.eng.ohio-state.edu | I recieve the following message: | | > From Majordomo-Owner@coulomb.eng.ohio-state.edu Wed Dec 7 11:16:56 1994 | > Date: Wed, 7 Dec 94 16:09:03 GMT | > To: MSargent@gallium.com | > From: Majordomo@coulomb.eng.ohio-state.edu | > Subject: Majordomo file: list 'diy_efi' file 'litlist.ps' | > Reply-To: Majordomo@coulomb.eng.ohio-state.edu | | | > MAIL DELETED BECAUSE OF LACK OF DISK SPACE I can confirm that two individuals have had the archive bounce due to length (Mike, you were one of them). I'm working on this problem and should had a "fix" soon. has anyone else had this "lack of disk space" error? I find it hard to believe that this is a problem here as all of my error are logged. Try having someone else mail you a *large* file. John S Gwynne Gwynne.1@osu.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 owner-diy_efi Wed Dec 7 20:27:37 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA09218; Wed, 7 Dec 94 20:27:37 GMT Received: from uunet.ca by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/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 AA09213; Wed, 7 Dec 94 15:27:30 -0500 Received: from gateway.prior.com ([142.77.252.4]) by mail.uunet.ca with SMTP id <87328-3>; Wed, 7 Dec 1994 15:21:04 -0500 Received: by gateway.prior.com (4.1/SMI-4.1) id AA04955; Wed, 7 Dec 94 15:12:23 EST Received: from odin.prior.com(192.139.238.33) by gateway.prior.com via smap (V1.3) id sma004953; Wed Dec 7 15:12:06 1994 Received: from ivan.prior.com by odin.prior.com (4.1/SMI-4.1) id AA25141; Wed, 7 Dec 94 15:11:08 EST Received: by ivan.prior.com (931110.SGI/930416.SGI) for @odin.prior.com:DIY_EFI@coulomb.eng.ohio-state.edu id AA13985; Wed, 7 Dec 94 15:22:45 -0500 Date: Wed, 7 Dec 1994 15:22:45 -0500 From: MSargent@gallium.com (Michael F. Sargent) Message-Id: <9412072022.AA13985@ivan.prior.com> To: DIY_EFI Subject: Re: admin: mail problems? Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI John S Gwynne writes: > | My goal is to have an easy to start, reliable, engine ready for next summer. > wow... next summer... that's fast. And you have a "real" job too? :). I don't necessarily expect to build my own EFI system from scratch. I will happily use an aftermarket ECU (i.e., from Accel, DFI, NOS, etc.) if it will do the job. My interest here is see what parts and pieces I can use and how to adapt them to my unique situation. +--------------------------------------------------------------------------+ | Michael F. Sargent | Net: msargent@gallium.com | Phone: 1(613)721-0902 | | Gallium Software Inc.| | FAX: 1(613)721-1278 | +--------------------------------------------------------------------------+ From owner-diy_efi Wed Dec 7 23:02:31 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA09910; Wed, 7 Dec 94 23:02:31 GMT Received: from shiva.trl.OZ.AU by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/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 AA09904; Wed, 7 Dec 94 18:01:49 -0500 Received: by shiva.trl.OZ.AU id AA21184 (5.65c/IDA-1.4.4 for DIY_EFI@coulomb.eng.ohio-state.edu); Thu, 8 Dec 1994 10:01:14 +1100 From: Craig Pugsley Message-Id: <199412072301.AA21184@shiva.trl.OZ.AU> Subject: Re: New Chip, Great Idea To: DIY_EFI Date: Thu, 8 Dec 1994 10:01:13 +1100 (EST) In-Reply-To: from "Nate" at Dec 7, 94 01:58:14 am X-Mailer: ELM [version 2.4 PL20] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1859 Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI > > I got some information on a new chip, this is a great idea for those of > you who design stuff that uses a HC11 or 8051 and need more ports and > less board space used. > > The chips are the "PSD" family. They contain Eprom, RAM, address decode > logic, ports and such. Most of the stuff you normaly have as seperate > chips. The chip has a window for erase of the Eprom. > > They have many models, so you should ask for the information sheets they > have. Any part numbers? (I want to look on our CD rom) Also of similar description is the Xicor 88C64, which is an 8k EEPROM specifically designed as a 'single chip memory for single chip micros'. It has the following features: -8k (Flash?) EEPROM -Memory can be segmented into multiples of 1k, and designated as program memory or data memory (Important for some chips as these address ranges overlap/are the same) -10,000+ write cycles (Needs no special voltages to write to chip) -'Data protection': You must a 3 byte sequence before a write, this stops rogue processors from killing everything in the memory -'Write protect' of any of the 1k blocks (EG write protect the program) -'Dual plane architecture' - allows you to continue reading after a write is initiated (As a write takes a few mS to finish) -No 'glue logic' required for 8051 family or 68HC11 family, all latches etc on chip. This chip seems just about perfect for DIY_EFI memory, however I don't know if it's available in larger sizes. Price (in australia) is around $US20 (incl.tax.) for 1 offs., which is still a bit cheaper than an EPROM and a RAM with extra board space etc. I thought I might put the serial download code in the first 1k, and write protect it, then put the downloaded code into 4k, and data in the last 3k. But first I'm getting my basic setup with eprom and sram going. Craig. pugsley@trl.oz.au From owner-diy_efi Wed Dec 7 23:09:52 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA09940; Wed, 7 Dec 94 23:09:52 GMT Received: from geni9.arl.mil by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/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 AA09935; Wed, 7 Dec 94 18:09:49 -0500 Received: by lamp0.arl.army.mil (5.65/DEC-Ultrix/4.3) id AA02637; Wed, 7 Dec 1994 18:09:44 -0500 Message-Id: <9412072309.AA02637@lamp0.arl.army.mil> To: 412071758.AA13205@ivan.prior.com Cc: DIY_EFI Subject: efi and boats Date: Wed, 07 Dec 94 18:09:44 -0500 From: faustini@lamp0.arl.army.mil X-Mts: smtp Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI Hi Mike, My name is Louis Faustini. I am an electrical engineer and an absoloute addict of cars, boats, motorcycles, and of course, computers. I design and build embeded systems for control of high-power microwave systems for the Army, to pay the rent/loans. I am currently working on a EFI system for my 1980 Mercuri Capri, (on its 3rd and best bult engine) I am also interested in building an EFI system for my 1994 Kawasaki XI jetski. Its nice to hear that I'm not the only one who wants to put computers, electricity, and gasoline on the water!!! Let me know how you're merc motor comes along. If you have any questions feel free to ask me.. ----- Lou Faustini From owner-diy_efi Sun Dec 11 21:40:23 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA28354; Sun, 11 Dec 94 21:40:23 GMT Received: from merlin.nando.net by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/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 AA28349; Sun, 11 Dec 94 16:40:20 -0500 Received: by merlin.nando.net (4.1/davel-nando/june94) id AA19357; Sun, 11 Dec 94 16:39:15 EST Date: Sun, 11 Dec 1994 16:39:15 -0500 (EST) From: David Cooley To: DIY_EFI Subject: SAE J1850 & OBDII Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI Hello, Am working on my own J1850 OBDII interface. Have several different ways to go about this, and several chipsets are in hand. I am not familiar with 68HC05 and 68HC11 programming. This is my block. Any help as to where to get either c to 68xx compilers or what the best route to learn 68xx assembly would be appreciated. Thanks, Dave cooldave@nando.net From owner-diy_efi Mon Dec 12 11:29:50 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06671; Mon, 12 Dec 94 11:29:50 GMT Received: from merlin.nando.net by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/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 AA06666; Mon, 12 Dec 94 06:29:47 -0500 Received: by merlin.nando.net (4.1/davel-nando/june94) id AA00730; Mon, 12 Dec 94 06:28:42 EST Date: Mon, 12 Dec 1994 06:28:42 -0500 (EST) From: David Cooley To: DIY_EFI Subject: Hello Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI Hello.. Forgot to introduce myself. I am Dave Cooley. No college, worked for Hughes Aircraft for 5 yrs in Test equipment and pc repair, now have worked for 6 yrs for Siemens Medical Systems repairing and maintaining MRI and Cat scan systems. As I mentioned before, I am designing and building my own J1850/OBDII interface to hook onboard computers to laptops. The J1850 BUS looks like a very good system for this project to interface all facets together with and is very simple. CPU hooks to 2 chips and the output is at J1850. It is a single wire, High noise immune system. Harris semiconductor makes the chips and they will interface with just about any micro. They are also very inexpensive. Harris makes most of the internals for the Chrysler PCM's, and has a lot of dedicated chips. IE Knock Sensor system (1 chip) Injector drivers, Electronic ignition drivers etc. Their parts are all very inexpensive and the CPU's of these PCM's are based on the motorols MC68HC05. Harris calls it the HIP7030A0. It is a 6805 without eeprom or ram. $25.00 retail. Just like the 'hc05, it comes as masked rom, eeprom, ram etc. I am sort of reverse engineering, as they are designing for the Auto makers PCM usage, but I just have to change the code in my controller. This bus interface will also allow the design of an ECM here to be OBD_II compliant and possibly be used on the road legally. By 1998, all vehicles in the US have to be OBD_II compliant. Just a suggestion, but this will keep this project on top of technology! Best part, again, is low cost. The 2 interface chips are 6.00 each retail. Thanks, Dave Cooley cooldave@nando.net From owner-diy_efi Mon Dec 12 13:54:55 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06883; Mon, 12 Dec 94 13:54:55 GMT Received: from gold.tc.umn.edu by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/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 AA06878; Mon, 12 Dec 94 08:54:52 -0500 Received: by gold.tc.umn.edu; Mon, 12 Dec 94 07:53:50 -0500 Date: Mon, 12 Dec 1994 07:53:49 -0600 (CST) From: Ryan A Erickson Subject: Re: Hello To: DIY_EFI In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI On Mon, 12 Dec 1994, David Cooley wrote: > Hello.. > Forgot to introduce myself. > I am Dave Cooley. No college, worked for Hughes Aircraft for 5 yrs in > Test equipment and pc repair, now have worked for 6 yrs for Siemens > Medical Systems repairing and maintaining MRI and Cat scan systems. > As I mentioned before, I am designing and building my own J1850/OBDII > interface to hook onboard computers to laptops. The J1850 BUS looks like > a very good system for this project to interface all facets together with > legally. By 1998, all vehicles in the US have to be OBD_II compliant. Actually, by 1996 all vehicles in the US must be OBDII compliant. The Clean Air Act of 1990 will allow the EPA to accept Califormia systems through 1998. So OBDII is required by 1996 but if the manufacturer can't make it they must at least meet California requirements through 1998 when California and OBDII requirements are identical. It should be noted that the LT1 Corvette and 3.8L Buick Regal were OBDII compliant as of MY 1994. The only thing these cars don't do is enable the malfunction indicator lamp (MIL), or another "Check Engine" light. They do store the codes in memory though, so a technician with the TECH 1 can read the faults. For 1995, the 4.3L GMC Sonoma/Jimmy and Chev S-10/S-10 Blazers are fully OBDII compliant. Also the 2.3L Quad 4's in the new Cavaliers and Pont. Sunfires should be fully OBDII compliant. Finally, the 1995 Camaro's and Firebird's should be fully OBDII compliant. I am not sure about any companies other than GM but I would think that at least Ford would probably have a couple vehicles out there with OBDII as well. Ryan From owner-diy_efi Mon Dec 12 15:01:16 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA07202; Mon, 12 Dec 94 15:01:16 GMT Received: from geni10.arl.mil by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/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 AA07197; Mon, 12 Dec 94 10:01:13 -0500 Received: by lamp0.arl.army.mil (5.65/DEC-Ultrix/4.3) id AA01319; Mon, 12 Dec 1994 10:01:11 -0500 Date: Mon, 12 Dec 1994 10:01:11 -0500 Message-Id: <9412121501.AA01319@lamp0.arl.army.mil> X-Sender: faustini@geni10.arl.mil Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: DIY_EFI From: faustini@lamp0.arl.army.mil (Lou Faustini) Subject: Re: Hello X-Mailer: Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI Excuse my ignorance, but what is OBDII ?? Is it some diagnostic standard? ----Louis Faustini From owner-diy_efi Mon Dec 12 15:28:48 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA07436; Mon, 12 Dec 94 15:28:48 GMT Received: from hwking.cca.rockwell.com by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/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 AA07431; Mon, 12 Dec 94 10:28:43 -0500 Received: by hwking.cca.rockwell.com (5.65/DEC-Ultrix/4.3) id AA02808; Mon, 12 Dec 1994 09:28:40 -0600 Received: by star.cca.rockwell.com (5.65/DEC-Ultrix/4.3) id AA06753; Mon, 12 Dec 1994 08:00:28 -0600 Message-Id: <9412121400.AA06753@star.cca.rockwell.com> To: DIY_EFI Subject: Re: Hello In-Reply-To: Your message of "Mon, 12 Dec 94 06:28:42 EST." Date: Mon, 12 Dec 94 08:00:22 -0600 From: sdbartho@cca.rockwell.com X-Mts: smtp Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI >By 1998, all vehicles in the US have to be OBD_II compliant. >Just a suggestion, but this will keep this project on top of technology! I read somewhere (think it was Hot Rod) that the OBD_II bill didn't pass in the House. Did they finally push it through? Another side effect of OBD_II was that all new ECMs were to be potted so that tampering with the system would be difficult. I don't really like the sound of this. Dig sdbartho@hwking.cca.rockwell.com Syclone/Typhoon mailing list. Feel the power of the wind. From owner-diy_efi Mon Dec 12 15:49:26 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA07627; Mon, 12 Dec 94 15:49:26 GMT Received: from uunet.ca by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/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 AA07622; Mon, 12 Dec 94 10:49:23 -0500 Received: from gateway.prior.com ([142.77.252.4]) by mail.uunet.ca with SMTP id <86675-4>; Mon, 12 Dec 1994 10:48:27 -0500 Received: by gateway.prior.com (4.1/SMI-4.1) id AA11544; Mon, 12 Dec 94 10:42:57 EST Received: from odin.prior.com(192.139.238.33) by gateway.prior.com via smap (V1.3) id sma011542; Mon Dec 12 10:42:51 1994 Received: from ivan.prior.com by odin.prior.com (4.1/SMI-4.1) id AA00342; Mon, 12 Dec 94 10:41:19 EST Received: by ivan.prior.com (931110.SGI/930416.SGI) for @odin.prior.com:DIY_EFI@coulomb.eng.ohio-state.edu id AA05627; Mon, 12 Dec 94 10:53:34 -0500 Date: Mon, 12 Dec 1994 10:53:34 -0500 From: MSargent@gallium.com (Michael F. Sargent) Message-Id: <9412121553.AA05627@ivan.prior.com> To: DIY_EFI Subject: MAIL DELETED BECAUSE OF LACK OF DISK SPACE Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI > I can confirm that two individuals have had the archive bounce due to > length (Mike, you were one of them). I'm working on this problem and > should had a "fix" soon. My local sys admin fixed up some disk space on our gateway machine and I can now get most files from the list server. However, I can't get archive_current (1.3 MB). I presume somewhere along the path a mailer is throwing this away because it's way too big. It's probably not at my end any more because I no longer get any response, where before I got the "MAIL DELETED ..." message. Does anyone have a copy of archive_current on an Anonymous FTP site? I'd like to catch up on what's been happening before I start shooting off my big mouth. The DIY EFI WWW site has about 300 KB of messages, but nothing since May 94. Thanks, Mike +--------------------------------------------------------------------------+ | Michael F. Sargent | Net: msargent@gallium.com | Phone: 1(613)721-0902 | | Gallium Software Inc.| | FAX: 1(613)721-1278 | +--------------------------------------------------------------------------+ From owner-diy_efi Mon Dec 12 16:09:07 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA07768; Mon, 12 Dec 94 16:09:07 GMT Received: from dns004.ford.com by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/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 AA07763; Mon, 12 Dec 94 11:09:04 -0500 Received: from srlns1.srl.ford.com (SRLNS1.SRL.FORD.COM [128.5.192.132]) by dns004.ford.com (8.6.7/8.6.6) with ESMTP id LAA22181 for ; Mon, 12 Dec 1994 11:09:03 -0500 From: tsakiris@ed8200.ped.pto.ford.com Received: from ed8200.ped.pto.ford.com (ed8200.ped.pto.ford.com [19.3.98.21]) by srlns1.srl.ford.com (8.6.8/FordSRL 1.0) with SMTP id LAA29547 for ; Mon, 12 Dec 1994 11:09:01 -0500 Received: by ed8200.ped.pto.ford.com (5.65/DEC-Ultrix/4.3) id AA12651; Mon, 12 Dec 1994 11:08:58 -0500 Received: from localhost by pt9254.ped.pto.ford.com (5.65/PED-CLIENT) id AA08582; Mon, 12 Dec 1994 11:08:58 -0500 Message-Id: <9412121608.AA08582@pt9254.ped.pto.ford.com> To: DIY_EFI Cc: Anthony Tsakiris Subject: Re: Hello In-Reply-To: Your message of "Mon, 12 Dec 94 10:01:11 EST." <9412121501.AA01319@lamp0.arl.army.mil> Date: Mon, 12 Dec 94 11:08:56 -0500 X-Mts: smtp Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI FYI: OBD-II = On-Board Diagnostics II (a system intended to indentify component and systems failures which prevent a vehicle from meeting emissions regulations) Anthony Tsakiris From owner-diy_efi Mon Dec 12 16:30:23 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA07984; Mon, 12 Dec 94 16:30:23 GMT Received: from wotan.compaq.com by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/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 AA07979; Mon, 12 Dec 94 11:30:21 -0500 Received: from twisto.eng.hou.compaq.com by wotan.compaq.com with smtp (Smail3.1.28.1 #12) id m0rHDdk-000vJ3C; Mon, 12 Dec 94 10:30 CST Received: from bangate.compaq.com by twisto.eng.hou.compaq.com with smtp (Smail3.1.28.1 #10) id m0rHDdf-000uIHC; Mon, 12 Dec 94 10:30 CST Message-Id: Received: by bangate.compaq.com with VINES ; Mon, 12 Dec 94 10:30:14 CST Date: Mon, 12 Dec 94 10:27:13 CST From: Steve=Ravet%Prj=Eng%PCPD=Hou@bangate.compaq.com Subject: re: Re: Hello To: diy_efi Cc: Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI tsakiris@ed8200.ped.pto.ford.com Wrote: | FYI: | | OBD-II = On-Board Diagnostics II | | (a system intended to indentify component and systems failures | which prevent a vehicle from meeting emissions regulations) | | Anthony Tsakiris | It's more than that, it also defines a standard one or two wire serial bus that the ECM uses to communicate with sensors and other equipment (including diagnostic equipment), and a standard for the information packets that are placed on the bus. So one diagnostic computer will work for all cars. This would indeed be a good feature to include on a diy-efi computer. --steve