@xxx.edu Tue Mar 7 17:27:55 1995 Date: Tue, 7 Mar 95 12:40:35 GMT @xxx.edu @xxx.za Subject: Majordomo file: list 'diy_efi' file 'archive_num_40' -- >From owner-diy_efi Thu Nov 3 01:30:21 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA20559; Thu, 3 Nov 94 01:30:21 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 AA20554; Wed, 2 Nov 94 20:30:19 -0500 @xxx.edu> To: DIY_EFI Subject: Re: The files... In-Reply-To: Your message of "Wed, 02 Nov 94 07:49:49 CST." @xxx.com> Date: Wed, 02 Nov 94 20:30:19 -0500 From: John S Gwynne Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI -------- @xxx.com> , you write: | Could you share more information about your development environment? | What you're using, any changes you needed to make, etc. Ok, here's a list of m68k *specific* tools that were built: m68k-sun-sunos4-ar archive and library maintainer m68k-sun-sunos4-as assembler m68k-sun-sunos4-c++ c++ m68k-sun-sunos4-c++filt demangle C++ symbols m68k-sun-sunos4-g++ GNU project C++ Compile m68k-sun-sunos4-gcc GNU project C m68k-sun-sunos4-ld the GNU linker m68k-sun-sunos4-nm list symbols from object files m68k-sun-sunos4-objcopy copy and translate object files m68k-sun-sunos4-objdump display information from object files m68k-sun-sunos4-ranlib generate index to archive m68k-sun-sunos4-size print the section sizes of an object file m68k-sun-sunos4-strings print the strings of printable characters in files m68k-sun-sunos4-strip remove symbols and relocation bits Of course other key components, like the pre-processor, are configured for the host and are not included in this table. As you see, a typical unix setup with make, emacs,... Most of these tools now build with almost no effort (I recall having more trouble making cross-development configurations on older versions). Also, check the archive. I walked through the process of compiling and loading a C program into my board for both a RAM and EPROM memory model. It's all automated :). (I had to write a few things like a loader script etc...) 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 Nov 3 01:49:39 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA20615; Thu, 3 Nov 94 01:49:39 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 AA20609; Wed, 2 Nov 94 20:49:36 -0500 @xxx.edu> To: DIY_EFI Subject: Re: The files... In-Reply-To: Your message of "Wed, 02 Nov 94 09:03:16 CST." @xxx.com> Date: Wed, 02 Nov 94 20:49:36 -0500 From: John S Gwynne Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI -------- @xxx.com> , you write: @xxx.edu> Wrote: | | Large? Just wait till version 1.0 comes out next month :). The ps | | file is indeed a schematic, but not a complete controller yet. The | | file prints five pages that, when taped together, yield a D-sized ^^^^ oops, that should be ten. | | drawing of the CPU portion of what will be a controller. For more | Speaking of RTEMS, how big is it? I know you posted this before, but where i | s | it available? If I ever get my linux machine back up and running, I'd like t | o | set these tools up myself.... On this system, the distribution (and nearly all of the build) is using 4.3 Meg. On the embedded controller it uses between 11k and 27k of RAM/ROM depending on how it is configured. You can ftp it from lancelot.gcs.redstone.army.mil in /pub/rtems. Look for version 3.1.03. 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 Nov 3 02:10:27 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA20820; Thu, 3 Nov 94 02:10:27 GMT Received: from eigen.ee.ualberta.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 AA20815; Wed, 2 Nov 94 21:10:24 -0500 @xxx.edu> Received: by eigen.ee.ualberta.ca (1.37.109.4/15.6) id AA13147; Wed, 2 Nov 94 19:10:17 -0700 @xxx.ca> Subject: Re: Fuel injected lawn mower To: DIY_EFI Date: Wed, 2 Nov 94 19:10:17 MST @xxx.net>; from "Andy Harrah" at Nov 2, 94 6:31 pm Mailer: Elm [revision: 70.85] Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI > drive electronics that watches the current ramp until the inductance saturates > and then back the current down to a 'hold' level. There are some decent > discussions of this in that blue Bosch injection book. Also, the Motorola > and National Semiconductor linear databooks describe chips to control > injectors. Not that we can get them, but they talk about how they work. You can get the Motorola MC3484 series from ElectroSonic up here. Last time I asked for them they had the lower current 2A injector drivers in stock, but not the TBI drivers. -Dale >From owner-diy_efi Thu Nov 3 03:08:08 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA22709; Thu, 3 Nov 94 03:08:08 GMT Received: from smtp.utexas.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 AA22700; Wed, 2 Nov 94 22:08:05 -0500 @xxx.edu>; Wed, 2 Nov 1994 21:04:10 -0600 @xxx.edu @xxx.edu>; Wed, 2 Nov 1994 21:01:37 -0600 @xxx.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 2 Nov 1994 21:02:03 -0600 To: DIY_EFI Subject: more mower Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI > All four-stroke cycle lawn mower engines and almost all four-stroke motorcycle > engine fire every revolution. All the newer distributor-less microprocessor > controlled car ignitions do as well. That extra spark just flaps in the >breeze. I'm going to end up using a Ford DIS coil to accomplish this. I don't know if I'll have a chance to put it on the mower, I'll probably just wait for the real application. The Ford coils use the dual fire setup. Lexus (LS 400) and some Nissans have a single coil for each cylinder. > My system takes interrupts off the TDC reference and calculates the RPM. > Based on the RPM, it looks up the advance from a centrigual advance type >table. > This value is then used to predict when to fire the next time, in advance of > actually receiving the TDC reference pulse. The reference pulse actually is > set to about 6 degrees BTDC so that it can be used to fire the coil directly. > This is used before the micro is up to speed, or if it crashes. > Currently there is no load input to calculations. The TTL level output of the > micro drives the ignition coil through a VW Rabbit amplifier module. That's neat. D