@xxx.edu Fri Jan 6 12:24:02 1995 Date: Fri, 6 Jan 95 09:15:32 GMT @xxx.edu @xxx.za Subject: Majordomo file: list 'diy_efi' file 'archive_num_16' -- >From Diy_Efi-Owner Tue Jun 7 19:52:33 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA22581; Tue, 7 Jun 94 19:52:33 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 AA22575; Tue, 7 Jun 94 15:52:31 -0400 @xxx.edu> To: DIY_EFI Subject: Re: EMI In-Reply-To: Your message of "Tue, 07 Jun 94 13:32:02 EDT." @xxx.GOV> Date: Tue, 07 Jun 94 15:52:31 -0400 From: John S Gwynne Sender: Diy_Efi-Owner Precedence: bulk Reply-To: DIY_EFI -------- @xxx.GOV> , you write: | I suspect that rather than a high speed cpu, you might want to consider off | -loading some of the calculations. For example - frequency counting. | | So you get a high accuracy clock.. divide down the output frequencies so | that you have a 1Hz clock to gather slow data and maybe a 1K Hz clock to | gather fast data. At the pulse you latch whatever data is there (and maybe | reset the counters). The cpu can then read the latched data at is leasure | and make adjustments accordingly. I currently have a backplane, that accepts 4.5x6.5in plugboards, running with 600nS read and write times. This (unofficial) "DIY_EFI_bus" provides the interface to the data acquisition/sensors circuits which may freely acquire data. This bus uses all HCT logic and seems to work fine. The cards that plug into this bus do "off load" burdens like frequency counting as I posted in the article "a 82c54 based computer tachometer". My goal at this point is to add a relatively fast CPU with enough resource to easily run software written in C (I would even like to use floats!). While I will maintain the slow external bus, I want a fast internal CPU bus. On two side-by-side plugboards, I would like to have the complete CPU portion of this controller (I may separately shield these two cards). Thanks for you comments on the AS. Hopefully ALS is somewhere between AS and HCT in terms of noise immunity. I sense a rocky-road ahead.... :( Anyone else with comments? 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 owner-diy_efi Thu Jun 9 22:01:41 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA03996; Thu, 9 Jun 94 22:01:41 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.91/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 AA03991; Thu, 9 Jun 94 18:01:39 -0400 @xxx.edu> To: diy_efi Subject: test posting -- disregard Date: Thu, 09 Jun 94 18:01:39 -0400 From: John S Gwynne Sender: owner-diy_efi Precedence: bulk Reply-To: 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 owner-diy_efi Wed Jun 15 14:47:30 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA08170; Wed, 15 Jun 94 14:47:30 GMT Received: from aces1.acenet.auburn.edu by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.91/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 AA08165; Wed, 15 Jun 94 10:47:27 -0400 Received: from aces6.acenet.auburn.edu by acenet.auburn.edu (4.1/SMI-4.1 aces1 1.0) id AA23708; Wed, 15 Jun 94 09:47:24 CDT Date: Wed, 15 Jun 94 09:47:24 CDT @xxx.edu> @xxx.edu> To: DIY_EFI Subject: OEM EFI mods? X-Sun-Charset: US-ASCII Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI While the list is reasonably quiet seems like a good time to ask... Are any FAQs available for production EFIs? Chilton manuals are *very* limited when it comes to inner workings. I'd like to adapt/modify an OEM system and avoid the hassles associated with a complete design....at least for the moment. Would a discussion on the subject be appropriate/welcomed here? -greg @xxx.edu Lead Specialist, Network Support VOICE: (205) 844-9660 Alabama Cooperative Extension Service FAX: (205) 844-3501 Auburn University, AL 36849-5646 >From owner-diy_efi Wed Jun 15 15:34:58 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA08414; Wed, 15 Jun 94 15:34:58 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.91/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 AA08409; Wed, 15 Jun 94 11:34:55 -0400 Received: by hwking.cca.rockwell.com (5.65/DEC-Ultrix/4.3) id AA22165; Wed, 15 Jun 1994 10:34:51 -0500 Received: by ohura.cca.rockwell.com (5.65/DEC-Ultrix/4.3) id AA08910; Wed, 15 Jun 1994 10:34:49 -0500 @xxx.com> To: DIY_EFI @xxx.com Subject: Re: OEM EFI mods? In-Reply-To: Your message of "Wed, 15 Jun 94 09:47:24 CDT." @xxx.edu> Date: Wed, 15 Jun 94 10:34:47 -0500 @xxx.com X-Mts: smtp Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI >Are any FAQs available for production EFIs? Chilton manuals >are *very* limited when it comes to inner workings. I'd >like to adapt/modify an OEM system and avoid the hassles >associated with a complete design....at least for the moment. >Would a discussion on the subject be appropriate/welcomed here? No problem here. I've been net-surfing for the same info, with not a lotta luck. Mitchell's manuals give better diagrams of things, as well as the manufacturer's service manuals. The tech schools usually get a lot of in-depth info from the man's, but I never could find any ECM diagrams. I wonder if the ECM rebuilders would be any help. They probably have a non-disclosure agreement against that, though. The tech school stuff had waveforms of crank/cam trigger timing, as well as more fuel system details. When they come out with this OBD-II thing, it will probably be easier to get information. The OBD spec itself is to be published by the SAE, I think. What are you trying to adapt? Dig @xxx.com >From owner-diy_efi Wed Jun 15 16:26:22 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA09176; Wed, 15 Jun 94 16:26:22 GMT Received: from fsa.cpsc.ucalgary.ca by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.91/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 AA09171; Wed, 15 Jun 94 12:26:18 -0400 Received: from aa.cpsc.ucalgary.ca (aa.cpsc.ucalgary.ca [136.159.4.5]) @xxx.ca>; Wed, 15 Jun 1994 10:23:56 -0600 @xxx.ca (Robert Fridman) Received: by aa.cpsc.ucalgary.ca (1.2; from fridman@localhost) @xxx.ca>; Wed, 15 Jun 1994 10:25:02 -0600 Date: Wed, 15 Jun 1994 10:25:02 -0600 @xxx.ca> To: DIY_EFI Subject: diy_efi WWW page Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI Hello all. The diy_efi WWW server is still running and waiting for additional material. The WWW server is fully functional but is still in its infancy and desperately needs more information. If you have written anything up to do with EFI or have references about pertinent articles or know of any supliers of material required for building EFI systems (sensors, electronics, software) send them to me. If there are any projects which you are interested in pursuing or are working on, send me a writeup or a short note. Or if you want to provide information about yourself (currently, there are two entries) send that in as well. If you are not connected directly to the Internet, you can still contribute material by sending it to me and I'll insert it into the WWW home page. Finally, if you don't know what the World Wide Web is or how to access it, send me mail and I'll explain the nitty gritty details. RF. ------------------------------------------------------------------------- 83 R100 DoD 749 Robert Fridman @xxx.ca 84 320i >From owner-diy_efi Thu Jun 23 03:27:56 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA24143; Thu, 23 Jun 94 03:27:56 GMT Received: by coulomb.eng.ohio-state.edu (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 AA24138; Wed, 22 Jun 94 23:27:54 -0400 Date: Wed, 22 Jun 94 23:27:54 -0400 From: jsg (John S Gwynne) @xxx.edu> Apparently-To: DIY_EFI Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI >From owner-diy_efi Thu Jun 23 03:40:34 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA24372; Thu, 23 Jun 94 03:40:34 GMT Received: by coulomb.eng.ohio-state.edu (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 AA24367; Wed, 22 Jun 94 23:40:33 -0400 Date: Thu, 16 Jun 1994 17:34:18 -0500 @xxx.edu> @xxx.edu> To: DIY_EFI Subject: Re: diy_efi WWW page Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI greetings: you offered, and i'll take you up on it. www. i know what it stands for, and some of the basics, but could use a faq-like starter (or the man page (or pointer thereto) for an ascii version (i dial in to the local university for my unix access). help? you offered, and i'll take you up on it. www. i know what it stands for, and some of the basics, but could use a faq-like starter (or the man page (or pointer thereto) for an ascii version (i dial in to the local university for my unix access). help? later, :) kc >From owner-diy_efi Thu Jun 23 03:46:48 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA24466; Thu, 23 Jun 94 03:46:48 GMT Received: by coulomb.eng.ohio-state.edu (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 AA24461; Wed, 22 Jun 94 23:46:47 -0400 Date: Fri, 17 Jun 94 09:02:33 CDT @xxx.edu> @xxx.edu> To: DIY_EFI Subject: Re: OEM EFI mods? X-Sun-Charset: US-ASCII Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI > Mitchell's manuals give better diagrams of things, as well as the > manufacturer's service manuals. The tech schools usually get a lot > of in-depth info from the man's, but I never could find any ECM > diagrams. I wonder if the ECM rebuilders would be any help. They > probably have a non-disclosure agreement against that, though. ... > > What are you trying to adapt? What I'll be doing should be a simple retrofit of a GM EFI to an old Camaro. What exact system I'll start with will depend on price, availability and the valued opinions of others who've done such conversions. I'd really like to know what was happening inside the "black box" before I install one on my prize and joy. Buying the commercially available SW for modifying parameters seems like a terrible copout. The system will first be installed on a well (over?) cammed 283ci. A 400 will replace the 283 when she blows, or needs major work, or when I get my next bonus....whichever comes first. Adjustability is an obvious factor for my EFI selection. I know of people who've done the conversion, but it surprises me that there aren't writeups available on the net. I'm hoping this line of questions will change that, or at least uncover those things that are available. And then there's that well kept secret about the format and meaning of the data of the EPROM...... -greg >From owner-diy_efi Thu Jun 23 03:46:52 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA24473; Thu, 23 Jun 94 03:46:52 GMT Received: by coulomb.eng.ohio-state.edu (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 AA24468; Wed, 22 Jun 94 23:46:51 -0400 @xxx.edu> @xxx.ca> Subject: Re: OEM EFI mods? To: DIY_EFI Date: Tue, 21 Jun 94 17:29:12 MDT @xxx.com" at Jun 15, 94 10:34 am Mailer: Elm [revision: 70.85] Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI > Mitchell's manuals give better diagrams of things, as well as the > manufacturer's service manuals. The tech schools usually get a lot > of in-depth info from the man's, but I never could find any ECM > diagrams. I wonder if the ECM rebuilders would be any help. They > probably have a non-disclosure agreement against that, though. And modifying the hardware doesn't help much anyways. All of the work is done inside the CPU... the key here is software. You're *not* going to get any information on that stuff, not from anybody. I *could* tell you how to get a start on modifying the stuff, but I've already been in enough trouble with this stuff already.... -Dale >From owner-diy_efi Thu Jun 23 03:46:45 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA24459; Thu, 23 Jun 94 03:46:45 GMT Received: by coulomb.eng.ohio-state.edu (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 AA24454; Wed, 22 Jun 94 23:46:44 -0400 Date: Thu, 16 Jun 1994 17:34:18 -0500 @xxx.edu> @xxx.edu> To: DIY_EFI Subject: Re: diy_efi WWW page Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI greetings: you offered, and i'll take you up on it. www. i know what it stands for, and some of the basics, but could use a faq-like starter (or the man page (or pointer thereto) for an ascii version (i dial in to the local university for my unix access). help? later, :) kc >From owner-diy_efi Thu Jun 23 03:55:32 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA24580; Thu, 23 Jun 94 03:55:32 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 AA24575; Wed, 22 Jun 94 23:55:30 -0400 @xxx.edu> To: DIY_EFI Subject: oops... mailer fixed... Date: Wed, 22 Jun 94 23:55:29 -0400 From: John S Gwynne Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI -------- I unknowingly disabled the mailer several days ago... but it's fixed now (I think :) ). The last three postings were "laying around" for a couple of days. Sorry. 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 owner-diy_efi Thu Jun 23 03:58:58 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA24798; Thu, 23 Jun 94 03:58:58 GMT Received: by coulomb.eng.ohio-state.edu (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 AA24792; Wed, 22 Jun 94 23:58:52 -0400 Date: Wed, 22 Jun 94 23:58:52 -0400 From: jsg (John S Gwynne) @xxx.edu> Apparently-To: diy_efi Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI help >From owner-diy_efi Thu Jun 23 15:22:14 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA26610; Thu, 23 Jun 94 15:22:14 GMT Received: from aztec.al.bldrdoc.gov 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 AA26605; Thu, 23 Jun 94 11:22:11 -0400 @xxx.edu> Date: 23 Jun 1994 09:22:36 -0700 @xxx.gov> Subject: RE: Re: diy_efi WWW page To: DIY_EFI Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI I second the motion. I only know what WWW stands for and have some idea of what it can do. While most people might only have ascii acess to WWW, I would like to know how to surf with my p.c. hooked up to a network. Could you give an introduction hand holding session for the beginner? Like what software to use and where to get it? I'm looking foward to contributing to the WWW, but only if I can figure it out! Thanks! -Steven Ciciora >From owner-diy_efi Thu Jun 23 16:26:35 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA27028; Thu, 23 Jun 94 16:26:35 GMT Received: from fsa.cpsc.ucalgary.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 AA27018; Thu, 23 Jun 94 12:26:26 -0400 Received: from aa.cpsc.ucalgary.ca (aa.cpsc.ucalgary.ca [136.159.4.5]) @xxx.ca>; Thu, 23 Jun 1994 10:23:22 -0600 @xxx.ca (Robert Fridman) Received: by aa.cpsc.ucalgary.ca (1.2; from fridman@localhost) @xxx.ca>; Thu, 23 Jun 1994 10:25:09 -0600 Date: Thu, 23 Jun 1994 10:25:09 -0600 @xxx.ca> To: DIY_EFI Cc: DIY_EFI @xxx.edu> Subject: Re: diy_efi WWW page Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI Thanks for the response. I'll do a write up on WWW and the various ways you can access it. For all the people that mailed me privatly, look for your answeres on this list. RF. >From owner-diy_efi Fri Jun 24 20:43:16 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA04769; Fri, 24 Jun 94 20:43:16 GMT Received: from uxa.cso.uiuc.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 AA04764; Fri, 24 Jun 94 16:43:11 -0400 Received: by uxa.cso.uiuc.edu id AA10572 @xxx.edu); Fri, 24 Jun 1994 15:42:56 -0500 Date: Fri, 24 Jun 1994 15:42:56 -0500 @xxx.edu> @xxx.edu> To: DIY_EFI Subject: Using the MC68332? Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI So - has anyone out there (if there *is* anyone out there!) ever used the Motorola 68332, or related product? I've heard a lot of great things about this chip, but how much work is needed to develop a system? Is there a commonly available compilier, preferably in C? How about an evaluation or prototype system, which has the RAM, EEPROM (flash would be nice), A/D's, serial port, etc? I'm really interested in this chip, esp. because of it's supposed built in functions for finding missing teeth, etc. I've had bad experiences trying to do that with analog (phase locked loop) systems - I'd like to try the digital route this time. Thanks for any info - Peter J Nelson @xxx.edu >From owner-diy_efi Fri Jun 24 21:03:58 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA05059; Fri, 24 Jun 94 21:03:58 GMT Received: from hp-cv.cv.hp.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 AA05054; Fri, 24 Jun 94 17:03:55 -0400 Received: from hp-pcd.cv.hp.com by hp-cv.cv.hp.com with SMTP (1.36.108.7/15.5+IOS 3.22+CV 1.0ext) id AA21036; Fri, 24 Jun 1994 14:03:55 -0700 Received: from hpcvts.cv.hp.com by hp-pcd.cv.hp.com with SMTP (1.37.109.8/15.5+IOS 3.22+OM+CV 1.0) id AA26979; Fri, 24 Jun 1994 14:03:54 -0700 Received: by hpcvts.cv.hp.com (15.11/15.5+IOS 3.22[SMTP-rly]+CV 1.0leaf) id AA09339; Fri, 24 Jun 94 14:05:38 pdt @xxx.com> @xxx.com> Subject: Re: Using the MC68332? To: DIY_EFI Date: Fri, 24 Jun 94 14:05:37 PDT @xxx.edu>; from "Peter J Nelson" at Jun 24, 94 3:42 pm Mailer: Elm [revision: 64.9] Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI > So - has anyone out there (if there *is* anyone out there!) ever >used the Motorola 68332, or related product? I've heard a lot of great >things about this chip, but how much work is needed to develop a system? >Is there a commonly available compilier, preferably in C? How about >an evaluation or prototype system, which has the RAM, EEPROM (flash would >be nice), A/D's, serial port, etc? > I'm really interested in this chip, esp. because of it's supposed built >in functions for finding missing teeth, etc. I've had bad experiences trying >to do that with analog (phase locked loop) systems - I'd like to try the >digital route this time. Motorola has EVBs for the 68332. You can also find data about the chip at bode.ee.alberta.ca ( i hope that is correct ). There is a port for a C compiler available along with freeware assemblers. The Motorola databook for this chip gives a sample of an engine management system, fuel injection, crank trigger, and ignition. They don't give you any circuits but hint that it shoud be pretty simple. Cary McCallister ÿ