I just would like to recomend this program to anyone who is looking for a scanner for there maf TPI cars. I can't comment on wether it works for SD but it does work greaton maf, I like it better than Diacom. I built this cable, http://www.techedge.com.au/vehicle/aldl8192/8192hw.htm I jest left out the 160baud lines and it works great.

Traxion if you read this I think your tech article could benifit from a link to Craigs site and a little write up that explains what it works on and with what cable and that it's free. I know that when I first read the article the thought of spending $500 plus dollars on a scantool almost scared me away from doing any prom burning all together. The scantool is invaluable as you stated, and Craigs program is great for the budget minded prom burner.

Can anyone confirm that it works on SD, cause I'm thinkin about switching.

Thanks

 

Anyone interested in having a G-Tech-like functionality built into the program? Something like:
1) Hit '7' to select the 1/4 mile page.
2) Stage for pass, hit spacebar.
3) Once the car rolls to like 3 mph, trigger the timing sequence.
4) Display 60', 1/8, 1/4 mile times and speeds.
5) Hit spacebar to do it all again
It wouldn't be 100% accurate, since I'd do it by integrating vehicle speed over time, but it'll be close in the absence of wheel spin. Maybe allow a separate file dump during the pass to simplify later analysis.
This feature could generate some tickets, let me disclaim responsibility now.

[This message has been edited by Craig Moates (edited May 12, 2001).]

 

Actually it sounds like a neat idea...one more tool to tune with maybe. What about those of us who run mostly 1/8 mile?

------------------
John Guynn
1988 IROC 5.7

 

Sounds like an excellent idea, Craig. Especially if you get it setup for the 160 baud ECM's as well as the 8192 baud ones. The 1/4 mile stuff wouldn't be very accurate at all with the 160 baud, but might be fun to play with.

Ken

 

Hey gang, I think I read about something like this on DYI-EFI but instead the guy was using a stop watch and using the pulses from the speedo to trigger the "on" and "off" on the stop watch.....giving a quarter mile time for tuning purposes. The article mentioned that for the first several pulses it did no start the stop watch to account for tire spin.

I think this would be even easier to put together a program together to serve the same function. It would allow you to measure mods & bin changes and the real world improvements/results without going to the track everytime or having a gtech. I would love to have something like this available to help fine tune my spark tables.

Build it! Build it!

------------------
87 Iroc 5.7, AFR190, SLP Cam(218/224), SLP 1 5/8 headers & cat back, Random CAT, SLP Runners, 48mm TB, custom chip(by me), Vigilante & Probuilt trans.

 

I have actually built a spreadsheet in Excel that takes data from a translated Diacom DBF file that will graph a 1/4 mile with a reasonable degree of accuracy.

I just start recording prior to the run and then graph the data once the car begins to move until it completes either the 1/4 mile or as fast as you went (ie for 0-60 mph times).

The difficulty is the correcting for wheelspin if you use the MPH per frame to calculate distance travelled. Excessive wheelspin makes the calculation think you've travelled more distance than you really have.

Good luck in getting this feature made within Craig's software. Though it is subject to inaccuracies, it does help in quantifying performance results. Especially if you compare from a common starting point (ie 10 or 20 mph where the wheelspin has stopped) to a common ending point (say 60 or 100 mph).

It isn't as feasible with a 160 baud ecm due to the slow transmitting rate, but with a 8192 baud ecm, you are getting just over 6 frames/second which corresponds to an error of around .15 seconds.

 

Yeah that would definatley be cool. Although I think I'll need to update my laptop, this 386 is hardly getting a frame per second.

 

Sorry Canadian, but I believe that is a function of the ALDL transfer speed and not your laptop. Any 386 should be able to handle a 8192 baud rate to the parallel port, so no matter how fast the CPU is, it is still limited to the transfer rate of the incoming data. If your ECM only transmit at 160, you are limited to that speed.

 

I have an 89 tpi, with the 165 ecm, that runs on 8192 baud right? I'm using pin M, (bottom right). Is that the wrong pin?

I don't know whats going on then, but I do know that even in no ecm test mode, with Craigs program where it generates random numbers, the laptop still only runs at .9 Hz or less than one per second where as my PC runs the test mode at 18Hz. Doesn't that mean that the laptop just can't keep up?

Glenn does this program work with Speed Density or have you tried it?

Thanks

[This message has been edited by CanadianBeast (edited May 11, 2001).]

 

Hmmm...That's awfully slow, something's wrong. Either that or I've just forgotten how slow 386's can be!

The 18Hz is fine, since that's dictated by the resolution of the PC's BASIC clock (50ms) and the program awaits an increase in the time prior to initiating an update.

You should be getting 8-10Hz acquisition rate, 5-7Hz with the disk logging activated. At least that's what I get with the 486-50 I'm using.

When you startup the program, after you enter the options, it should pause and then give you a value for number of counts associated with a 0.001 second delay. The larger this number is, the faster your PC is. This is kind of a self-pacing routine. What number does it give you? For instance, on my desktop (GHz Celery) it gives '580'. What are you getting on the 386? If you're getting 0.9Hz on the 386 in test mode, I'm guessing it's just dead-slow.


[This message has been edited by Craig Moates (edited May 12, 2001).]

 

My laptop is giving a nuber of 2, this is obviuosly really slow, do you think the laptop is actually that slow or is smoething wrong?
Thanks for the help

 

I was wondering could there be anything running in the background that is taking up cumputing power. If so how will I find it. This laptop doesn't have windows or anything like that installed and it's running dos 6.2.

Can anyone recomend the minimum requirments of a laptop to run Win95. I'd like to get one that will run tunercat, if I can't get this one working. Also is there a way to run the pocket programmer off of 12 volt?

Thanks