Just wondering if anyone has been successfully datalogging an '89 with a $6E using the XtremeALDL and TP5? I've read some posts that say to use TP4 and scannerpro so it can be done, but how about TP5? I just cant get it to connect consistently, maybe 1 out of 10 times and then it disconnects after about a minute or two.

Any help is appreciated - very appreciated.

 

Welcome to the 165, you might need to try another ecm.

 

I use TunerPro 4 with the APU1 from Moates and it works like a charm. There's a bunch of settings that can change the way it works so play around with all of them and see if that helps.

 

I use it all the time.....works great.

 

The car runs fine, and i can burn chips and make changes that way, but no logging - I do use a Tech1 GM scan tool to watch things in realtime though.

So youre saying its hit and miss with the 165 ECM? Something about their design is on the hairy edge of working right? Nice. I think thats what youre implying because I'm not the only one who's been posting as to how flaky their communication is.

 

I use tp4 and it connects most of the time and logs for alittle while. Sometimes it doesnt want to connect and may stop logging randomly. Always been a thing associated with 165 ecms

 

I have TP5, paid edition. So I guess I'll also need TP4 right? Also need to download scannerpro or is that a part of TP4?

Can the log files generated by TP4 be used in TP5? I Really like TP5 and its flexibility for dashboards, tables, etc.

 

I have a few 165 ecm, one I use for a test bench. the 165 is luck of the draw on connection.
I would be curious to know how the 808 $12p. Depending on what .ads you are using you might need to the pause for silence to get rid of the data glitching.

 

Mostly been using the 1227165_6E.ads from gearhead-efi's site. That file has Mark Mansur as its author, just guessing, but its probably ok

I have messed with adding the "listen for silence" at the end of the Mode1 macro, have gone from 10-90ms, some joy happened in the 15-25 range but those times when it connected were short lived.

What's the "808 $12p" ?

 

The 1227808 is a Holden commodore ecm used in austrailia. It is very similar to the 165. The $12p mask is speed density.
http://wbo2.com.au/~techedge.com.au/vehicle/1227808/

 

As far as i know log files in tp5 are different than tp4. I never been able to view one with the other. File extensions for things are different between the two

 

Why cant things ever be easy

 

life wouldn't be fun without challenges

 

right

 

TP4 connected once out of 8 tries - and even that for only a minute. I guess it must be my ECM.

I suppose I'm now looking for a 165 ECM that works. Gambling has never been good to me, so anyone have one they want to part with that works for sure?

 

Sending pm

 

I use the latest ver of TP5, and $6E on my '88 IROC with the 165 ecm. It works ok, not perfect, but good enough for me to get meaningfull data. I tend to like using the most updated version of this software. It has to have the most up to date bug fixes.

 

The ecm and memcal I checked out on my test bench should be there maybe today.Lmk how it works

 

Tried to leave a positive feedback for tunedperformance, but URL keeps coming up as fail.

Anyway, Brian is a great guy to deal with. He lent me a 165 ECM that he knew worked and a socketed memcal that I could plug my flash into, and it worked for me. My 165 Ecm was one of those "Luck of the draw" type that doesnt like to datalog. So I bought his at a reasonable price and now I'm happily logging and emulating and hopefully will be able to get the car running at its best. Thanks again Brian!

 

Hey Brian you got any more of them good '165 ECMs lying around?

 

I have one ecm left but I think it's spoken for. I'll find out this weekend if the guy wants it. If not I'll put it on a test bench to see how it connects to tunerpro.

 

ok cool. Thanks bud. If not I'm going to hang it up this season and save up for a modern engine management system like XFI.

 

Post #2 might apply
https://www.thirdgen.org/forums/tpi/...cm-issues.html