hey guys,

I've been searching the boards for the past hour or so, looking for some confirmation or definitive proof that winALDL will work on my 87 TPI (350)

I've noticed from the documentation fo the software that it seems to lean towards TBI..

Does anyone run this combo, or have experience?

If it's not supported, then what other choices do I have for scanning ? I don't need complete prom burning/engine management, just a win/dos based scanner.

Thanks,
Ben

 

Check this site out I think it will be what your looking for. http://ice.prohosting.com/moates/gmecm/index.html

 

WinALDL works with MAF TPI, but it only reads the 160 baud data stream. It will not update as fast as the 8192 baud scanners, only every second or so.

 

Yeah, I noticed that last night when working with it.

Are there any 8192 windows based scanners (freeware) ?

I'd like to keep the GUI, but not have to suffer the 160 baud bottleneck.

 

Whats wrong with Craig Moates freeware?

 

I want a win GUI (graphical user interface)

I'm not a big fan of the character based one, It's a little tough to see (4" LCD in dash for computer output) all the small print, i'd rather have a big GUI "dash" display like winaldl has, with RPM, O2 readings, speed, MAF, and TPS displayed.

 

If you want a freeware program that has a GUI and does 8192 I would recommend helping either the authors of WinALDL write an 8192 interface. Or you could help write a GUI for Craigs software.
Craigs software does data logging. It is the most powerful aspect of the tool(I think). Most people learn much more by reviewing data after driving the car, not while driving it. My recommendation is to start the data logging function and close the laptop so you won't be tempted to look at the screen. Just my opinion.
Give it a try, you might like it.
J

 

Thanks for the info, I was playing with it tonight, and I'm impressed with the software. i just have a deep, deep hatred for character based applications. With the logging part, I have a few questions (didn't get a chance to check that part of it out yet)


How does it display the log of the run? Bar graph, chart with seconds -> values, etc.

 

I ordered my ALDL-RS232 cable and it should arrive Monday. I'll start work on a Windows version of a scanner with graphing, printing, etc., then.

This has been discussed in this thread:

https://www.thirdgen.org/techbb2/sho...threadid=90822

 

Have any of you guys tried using winaldl on a computer controled carb. car. I'm assuming thats what is ment by clcc car 84-86. When i went to hook up my cable there wasn't a pin for the data pin E. It was just missing. Any one have a clue?

 

You may not like character based applications but what would you do differently to get good data in a timely fashion? I don't see how a GUI application will provide any benefit. Craig's software will log a bunch of data in a .csv file which can be opened in Excel or other spreadsheet program where it can be examined at your leisure, any way you want. I haven't used the plots yet but just having a means of data collection is a huge step.

 

You should use the 'D' pin with carbed ECM's

 

freescan is windows based and has datalogger. It works on 89 vettes so it should work on an 86.

 

Pure aesthics.... I'd rather look at a nice big gauge, needle sweep type, than a blue screen with a crap load of numbers.

 

11 Sec GTA :-)

There is another issue you should be aware of in favor of the DOS based nature of Craig's program. In Windows, where you would need to be to do the GUI type diplay you favor, the software doesn't get the kind of direct control/access to the port into which the data is coming. This leads to all sorts of potential problems with timing and data points being dropped, especially with older, slower, laptops. Craig's choice of OS to run under (DOS) gives you a nice compact reliable capture mechanism to get the data and then to display you have all sorts of pretty options.

Do a search and you will see a lot of discussion of just this issue.

 

On the contrary, you can get direct access to the port in Win9x. You use a C++-based function with inline assembly to directly write to the address (03f8h).

Windows NT/2000 won't permit this unless the function is running in Kernel mode, like a device driver.

 

I was playing with both programs all weekend.. and as expected, I've found pros and cons on each..

The only thing I do not like about winALDL is the 160 baud.. it's just not fast enough. But, it does a slick interface with GREAT logging capabilities, the ascii file it writes cleanly imports into excel... Craig's software is easier to read than I expected with sun glare on the screen.. (4" LCD in dash for PC display).. it also has great logging, I just am filled with such a deep hatred for character based apps, that I'm biased against.


I just want to give props to the coders for these programs, they are great.. and have saved me big time, as I found out I'm running a little lean around 4100 rpms (melted pistons are not good.) Thanks again,

-Ben

 

Synapsis

When I say Windows, I am assuming Win2K. Don't have much use for the versions prior to it and don't miss them at all :-). Still even with direct access, there is a lot more going on with the processor than with DOS alone. I also prefer a GUI to a character based interface, just wanted to point out to 12 sec GTA some of the considerations involved in choosing the DOS based route. This has been hashed over here before :-).

 

Yeah, there are benefits to both ways. Personally, if my laptop was a P133 with 16 megs of ram, I'd be running the DOS version on it and be totally happy with it. But my laptop is a P3-550, so adding Windows to the equation isn't too much of a processor hit when it comes to serial comms. (Windows not too much a processor hit? Did I say that?)

Now if I could only get Craig's software to communicate with my car. I built a cable and couldn't get it to work, so I bought a cable from AKM and it's doing the same exact thing it was with my cable... there goes $95 =/

 

WinAnything.......shouldn't be a problem if written as a device driver. Talented you are if you can understand and write it. Not to mention own the DDK tools.
Good luck,
J

 

Luckily for me, my company pays for the DDKs.

I finally got *one* piece of software to communicate with the car. It just happens to be Datamaster. Now for that pesky reg code...

Next I can throw my serial comms sniffer on Datamaster to see how it communicates with the ECM, then start coding my own software that'll let me graph more than just 4 items... and at a higher rate.

I'm must be a true geek, I'm getting excited about coding.

 

If you want to get with me offline, I can walk you through getting my DOS-based stuff working, and then you can have full vision of the communications by perusing the source all you want. Just let me know and I'll give you some ideas based on what kind of difficulties you're having getting the program to work.

-Craig