[Diy_efi] Haltech Data Logging
Lee M. Lemoine
llemoine
Wed Sep 20 02:44:55 UTC 2006
The haltech > dos.txt would work fine if you didn't have to pass
parameters. its not a strict data logging program, and there are no
command-line switches to configure like your mentioning. If you've got
WinXP the only thing that comes to mind is to install a printer driver that
writes to disk. this way the dos emulator will pipe the output to a windows
printer, which simply writes the data to disk. i've done this before, i
think win98 has a "file writer" or "print to disk" function as a "generic"
or "Microsoft" brand printer in the 'add printers' section.
Let me know what you come up with, again, short notice not much time to
research.
-- LL
On 9/19/06, Bill - Comcast <b.shaw at comcast.net> wrote:
>
> Data that is printed to the screen.
>
> Bill
>
> Ben P wrote:
> >
> > so what does that print to the text file? The data that it saves,
> > displays, or everything that the program 'sees'?
> >
> >> From: Bill - Comcast <b.shaw at comcast.net>
> >> Reply-To: diy_efi at diy-efi.org
> >> To: diy_efi at diy-efi.org
> >> Subject: Re: [Diy_efi] Haltech Data Logging
> >> Date: Tue, 19 Sep 2006 09:21:00 -0400
> >>
> >> Can you pipe the output to a text file?
> >>
> >> If your program's name is haltech.exe and you want the data to end up
> >> in a file called test1.txt, try a command line like this....
> >>
> >> haltech > test1.txt
> >>
> >> hth,
> >>
> >> Bill
> >>
> >> Ben P wrote:
> >>> well taking a screenshot of the data logging process in windows XP
> >>> results in all of the data coming out in words (with the simple DOS
> >>> borders coming out like ASCII art). I have since discovered that
> >>> highlighting all of the 'picture' in microsoft word, converting it
> >>> into a monospace text (courier new), and changing the size to 8
> >>> point (i think thats it anyway) results in an ASCII picture, with
> >>> all relevant data in the appropriate columns. However taking a shot
> >>> of anything with real graphics (like the bar graph tuning screen on
> >>> haltech units) results in meaningless mumbo jumbo (same characters
> >>> as opening the datalog files in text, maybe a link here?).
> >>>
> >>> Taking a screenshot in Windows 98 however results in a normal
> >>> screenshot (i believe this is because windows XP runs a dos emulator
> >>> in windows, rather than a visual version of dos, as 98 does). This
> >>> really sucks because 98 can't use memory sticks, and the computer
> >>> hooked up to the dyno doesnt have a cd burner. So i have to put it
> >>> on floppy, which is a long forgotten (for good reason) art...
> >>>
> >>> however I still can't get the data to view in anything other than
> >>> the haltech program.
> >>>
> >>> Is it possible to tell a dos program to 'print' to a .txt file
> >>> instead of the actual printer? as this would allow me to select the
> >>> relevant data and put it into a word document for ease of viewing.
> >>>
> >>> Tomorow I will have a shot at hotwiring DOS on the 98 machine to
> >>> open the datalog file in its own text viewer, maybe that will come
> >>> up with something.
> >>>
> >>> any ideas/clues?
> >>>
> >>> thanks
> >>> Ben
>
> _______________________________________________
> Diy_efi mailing list
> Diy_efi at diy-efi.org
> Subscribe: http://lists.diy-efi.org/mailman/listinfo/diy_efi
> Main WWW page: http://www.diy-efi.org/diy_efi
>
--
Sincerely,
Lee M. Lemoine
KB1NQI - Amateur Radio
http://www.turbochargedsoul.com/
'06 Subaru Legacy GT Limited - 250/250 AWD 5EAT
'93 Chevy Cavalier Z24 Convertible - 300/330 FWD 5MT (Mclaren Turbo!)
More information about the Diy_efi
mailing list