@xxx.edu Fri Jan 6 12:23:24 1995 Date: Fri, 6 Jan 95 09:15:33 GMT @xxx.edu @xxx.za Subject: Majordomo file: list 'diy_efi' file 'archive_num_17' -- >From owner-diy_efi Fri Jun 24 22:14:09 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA05463; Fri, 24 Jun 94 22:14:09 GMT Received: from system3.lcs.gov.bc.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 AA05458; Fri, 24 Jun 94 18:14:05 -0400 Received: from by system3.lcs.gov.bc.ca with SMTP (1.37.109.6/16.2) id AA06462; Fri, 24 Jun 94 15:15:46 -0700 @xxx.ca X-Openmail-Hops: 1 Date: Fri, 24 Jun 94 15:14:57 -0700 Message-Id: <1931E353@MHS> Subject: Re: Using the MC68332? To: DIY_EFI Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI I found it. It's an ftp site and there is a u at the begining of alberta. bode.ee.ualberta.ca ---------- From: owner-diy.efi; cmcalstr To: DIY.EFI Subject: Re: Using the MC68332? Date: Friday, June 24, 1994 2:05PM <> > 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 >From owner-diy_efi Fri Jun 24 22:57:18 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA05521; Fri, 24 Jun 94 22:57:18 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 AA05516; Fri, 24 Jun 94 18:57:16 -0400 @xxx.edu> To: DIY_EFI Cc: jsg Subject: Re: Using the MC68332? In-Reply-To: Your message of "Fri, 24 Jun 94 15:42:56 CDT." @xxx.edu> Date: Fri, 24 Jun 94 18:57:16 -0400 From: John S Gwynne Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI -------- @xxx.edu> , you write: | 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? The last I heard, the evaluation boards where in the $700 range for the cheapest of the series. I can build (and have started) a 16MHz 68HC000 with 512k EPROM, 16k battery backed-up SRAM, 512k DRAM, timer(s), UART, status LED's, and wacthdog timer for about $375. Sound like a lot of EPROM/DRAM? I envision a system that can store everything for, say, the past 20 seconds and recall it latter for diagnostic purposes. I would also like to play with predictive filters on the MAP and TPS inputs to improve throttle response (ie., no explicit acceleration enrichment term in the injector duration equation). Maybe even a little fuzzy logic? I figured that I would start with this CPU and then switch to one of the CPU32's when the prices drop. They are software compatible (for the most part). GNU's GCC and GAS seem like the best choice for a compiler and cross-assembler. I have both running now and am in the process of wire-wrapping the 68HC000 board(s). 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 Sat Jun 25 02:41:51 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06284; Sat, 25 Jun 94 02:41:51 GMT 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 Sat Jun 25 02:42:44 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06296; Sat, 25 Jun 94 02:42:44 GMT 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 Sat Jun 25 02:45:23 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06311; Sat, 25 Jun 94 02:45:23 GMT 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 Sat Jun 25 02:51:08 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06384; Sat, 25 Jun 94 02:51:08 GMT 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 Sat Jun 25 02:55:20 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06422; Sat, 25 Jun 94 02:55:20 GMT 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 Sat Jun 25 02:56:46 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06434; Sat, 25 Jun 94 02:56:46 GMT 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 Sat Jun 25 02:58:02 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06445; Sat, 25 Jun 94 02:58:02 GMT 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 Sat Jun 25 02:59:02 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06457; Sat, 25 Jun 94 02:59:02 GMT 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 Sat Jun 25 02:59:22 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06468; Sat, 25 Jun 94 02:59:22 GMT 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 Sat Jun 25 02:59:43 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06479; Sat, 25 Jun 94 02:59:43 GMT 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 Sat Jun 25 02:59:52 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06490; Sat, 25 Jun 94 02:59:52 GMT 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 Sat Jun 25 03:00:30 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06505; Sat, 25 Jun 94 03:00:30 GMT 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 Sat Jun 25 03:00:41 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06516; Sat, 25 Jun 94 03:00:41 GMT 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 Sat Jun 25 03:00:51 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06527; Sat, 25 Jun 94 03:00:51 GMT 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 Sat Jun 25 03:01:00 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06539; Sat, 25 Jun 94 03:01:00 GMT 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 Sat Jun 25 03:01:50 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06550; Sat, 25 Jun 94 03:01:50 GMT 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 Sat Jun 25 03:02:53 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06563; Sat, 25 Jun 94 03:02:53 GMT 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 Sat Jun 25 03:05:54 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA06579; Sat, 25 Jun 94 03:05:54 GMT 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 ÿ