Injector Duty Monitor

steve ravet Steve.Ravet at arm.com
Mon Jan 4 20:51:01 GMT 1999



Bruce Plecan wrote:
> 
> -----Original Message-----
> From: steve ravet <Steve.Ravet at arm.com>
> To: diy_efi at efi332.eng.ohio-state.edu <diy_efi at efi332.eng.ohio-state.edu>
> Date: Monday, January 04, 1999 12:46 PM
> Subject: Re: Injector Duty Monitor
> 
> Yes, but after you do the zip thing.........  He mentioned pwmeter, which is
> zip,
> ya fine, unzip, and I still can't see anything, other than a drop down
> window.
> Just for grins try something with a .asm file extension, on a windows
> machine.
> Some of us don't make a living with this stuff, and hit dead ends.
>   Yes I do have the winzip, and that ain't the problem.  It's what comes
> next......

OK.  In the case of pwmeter, you get these files:

 PWMETER.C
 AT892051.H
 PWMETER.HEX
 PWMETER.PS
 PWMETER.S01
 PWMETER.TXT


pwmeter.txt is a document that tells you what everything else is

pwmeter.c is a C program, along with at892051.h.  You need a C compiler
to use these, and it needs to be specific to the device that you are
going to put the program into (looks like an Atmel microcontroller,
similar to PIC).

pwmeter.hex is a hex file.  That's the end result of compiling the C
program, and the .hex file is ready to be read into a device programmer.

pwmeter.ps is a postscript file, can be read by the program
"ghostscript" or can be sent straight to a postscript printer.  Most
likely a schematic.  

pwmeter.s01 is a schematic that could be read by Tango schematic
software, if you had it.  Since you probably don't, just print out the
postscript file instead.

With that said, the pwmeter.txt is skimpy on details.  How exactly does
this thing tell you what the pulse width is?  I don't have ghostscript
installed so I can't read the .ps file.  Georg, got any more details?

--steve



More information about the Diy_efi mailing list