i tuned my HSR383 with tunerpro (now i have tunerpro RT) and just giving wat the engine wanted. now that summers approaching i want the tune to be much better. I just recieved my extreme ALDL with cables from moates, i already had the G1 that i installed on the car in novemeber.

my problem is i cant seem to datalog. i orignally couldnt get tunerpro RT to reconize the ALDL cable, so i went through the mess of figuring out the com ports. i finally got tunerpro RT to reconize the ALDL but i cant datalog! every time i hit record... it says error. i also cant hit the intialize attached hardware... bc it says no hardware is detected. I can get it to say ALDL connected tho. can anyone tell me a step by step way to get tunerpro RT working right to get a datalog?!?

im running windows 2000 on a cr@ppy IBM laptop that my dad had laying around. only has 2 USB ports and the one im plugged into is com5.

does the key need to be in the ON position or does the car need to be running? how do i get it to datalog? sry im a nube with datalogging. moates should put instructions with there products. i did print out some instructions for stand-alone datalogging off moates.net but its not working. i even chose the ADS file that was the 165 6E... since im running a MAF ECM with a AUJP bin, and a 6Eexpanded.xdf. i also have the xtreme ALDL set to 10k like moates states.

i really want to datalog since the weather is nice and i have some time off from work right now. any help would be great thanks!

 

first yes the key needs to be on, either running or not, go into the hardware settings under com 5 and set the latency timer to 1, then hook up to the vehicle, check that the switch on the aldl box is switched to 10k then go to the tools tab then aldl then setup in tuner pro rt (tp rt) then select the .ads (definition file) that matches your computer browse the datastream folder in tp for a match to your computer. if you cant find it there check the downloads section of tp's website and download. for instance i have a 89 gta with a 165 computer running the $6e bin def so i use the 1227165_6e.ads . then go to tools tab and go to preferences then the aldl/emmulation tab and set the interface to max32/2 and set the com port to com 5 (this is not auto configured). after all of that go to the view tab then toolbars and check the aldl option. this is very helpful later. then click the opposing arrows icon in the new section of the toolbar to connect to the computer. this should work if it doesnt then let me know and i'll get into it a little further but usually it is because the interface is not properly set up.

 

i followed ur instructions. i got the ALDL to connect. i have the target sample rate at 10hz. i did set the latency timer to 1 for COM5.

my original ECM was running a 32B bin i believe but i upgraded to the 6E so i could have the cold start injector delete. also bc 6E gives me alot more tuning tables. so i run the 6E expanded.xdf, i set the ADS to the 6E file u stated and thats what i had before... will the 6E.ads work with the 6E expanded?

still have the same problem. when i hit the record button to create a log it says error created log! ugh. how do i set up a log? theres no button for create new log/save new log etc. how do i get the log to create?

 

AUJP is $8D mask, it doesn't run in the 165 ECM.
If you run the $6E ads I doubt you will get anything with it.
The connection commands are not the same and the data stream is different.
Not sure what you are doing with the SD bin file

 

sry i might have messed up the bin... its prob not a AUJP bin. its from orr89rocz. it was his tune for his 89 iroc with a 350tpi MAF car... but without the cold start. thats what i needed since i had a cold start injector which i deleted when switching to the HSR.

its a 89 bin, for a MAF, it runs fine on the stock 165ECM and i edit the bin with a 6E expanded xdf. maybe it was a AUPJ or something lol idk i get the bin files mixed up sometimes. i kno my stock was a 32 or a 32B (i get those confused to bc i was tuning my 87 formula and my dads 86 TA... both had the same but one had a B at the end.

 

to record a data log with TunerPro 4, you need to make a log file to record to. to do this go to ALDL setup.
look on the right side where it says "Data Logging" and click the "Select Log File For Rec/Play" button.
when the window opens up, find the folder where you want to save your data logs in.
now choose a file name for that log and hit the "Open" button.
you should get a warning "This file does not exist." with the question "Create the file?" tell it yes.
now when you record a data log, it should save it to that file. when you hit stop recording, you should get a pop up window. you can type something into it and then hit Ok. the file should save for later viewing.
by putting in a different number, letter, or name in the pop up window after you hit stop, you can have multiple data logs in that one file.
doing that can quickly get confusing, plus you end up with a big log file after a while.
so make a new log file each time you data log.

something i do is i name my bins with just numbers starting with 1.
when i make any changes to that bin, i use the "Save Bin As,.." feature and name the new bin 2 and leave bin 1 as it is and use progressively higher numbers for each new bin.
this allows me to easily go back if the new bin doesn't work as good as the last bin did.
i also make a new log file for each bin and use the same number for the log as the bin im logging from.
using the Compare feature i can see the changes i've make as i go along.
at the start of each month, i move all the previous months' bins, logs, and notes to another folder and name that folder for the month and year the files are for.
then i start over naming the first bin and log for the new month 1.
i delete the older files when i feel i don't need them anymore.

 

so that worked... i finnally got my first couple of datalogs. kinda annoying that i cant leave the datalog running and watch real time the ALDL DASH on the laptop.

heres a couple of problems i had

1.) first datalog only ran 666 steps before it stopped recording (laptop didnt go to sleep either)
2.) i tried to run another datalog under the same log but with a different name ( i.e 1,2,3 etc) and when i hit record it says datalogging but it doesnt record any steps.
3.) i ran 2 more datalogs having to create new logs each time, but each would record for a different amount of time. 2nd log was like 583 steps, and my last log was 919steps.

also when i watch the log, i see the 02 sensor mv... jump around but it will flash into the red... does this mean im out of my target A/F? i also notice my block learn/intergrator will bounce around and sometimes flash red. typically we want the BLM to be around 130 right? and the intergrator too? wats it means when the BLM is 118 or the intergrator is way high like 150 etc? also i can compare logs right? with the compare feature in tunerpro RT?

thanks for all the help guys.

 

i don't know why it would stop recording. i don't recall ever having that problem myself. im sure someone else can help you with that.

the change in colors is the alarm setting, to me its more of a personal preference thing as i find it a bit distracting.
if/when the colors change can be changed by adjusting the alarm setting in the ADS file.
i prefer using changing colors for things like knock retard, AE, PE and DECEL.

the compare feature is for comparing the bin file your working on with another one. for comparing i usually have one completely stock file, one that i've done basic changes to, and the last good working bin.
to compare data logs, you would need to either bounce back and forth between the log files, or use a second computer to play one of the files.

the O2 voltage will bounce around, a lot.
the ECM targets ~14.7:1 air fuel ratio.
at 14.7:1, most engines burn cleaner for average emissions.
lower CO goes up, higher NOx goes up.
for the cat to work, the mixture needs to go from slightly rich to slightly lean. the ECM adds a little fuel and then removes it, which is why the O2 voltage is bouncing from high to low.
if the ECM sees the O2 voltage low longer than it sees it high, the ECM adds fuel which you see as a BLM or INT # higher than 128

BLM is the course fuel setting, or long term fuel trim.
INT is the fine fuel setting, or short term fuel trim.
BLM changes based on what the INT doing.
128/128 is the preferred BLM/INT reading.
at 128/128, the ECM isn't adding or removing fuel.
if the BLM is above 128, the ECM is adding fuel for a lean condition.
if the BLM is below 128, the ECM is pulling fuel for a rich condition.
the farther away from 128, the more the ECM is correcting for the condition.
thats where tuning the fuel maps come in at.
tuning to 128/128 in all the cells is ideal, but i don't think its possible to do. there are just too many factors involved, some beyond our control such as the gasoline you buy.
at least i've never heard of anyone who has done it, if someone says they did it, i want to see the data logs, LOL.
but for what ever reason, we seem to keep chasing that elusive, perfect 128/128.

 

thanks denn-shah!

yea i kno why the 02 bounces around but its really all over the place, it turns red when its like 80mv and then jumps to 896mv lol. from what ive read that you cant get the 128/128. but its usually ideal to get +/- 5 from the 128/128. some of the best tuners cant get within +/-3 of the ideal 128/128.

some ppl also say not to trust the BLMs etc... but i will look closely at my BLMs/INT when i look at my logs again and see how they are performing. so 14.7 for efficiency hahaha i might get 8-10mpg. WOT should be wat like 12.1:1?

i still cant figure out why its not allowing me to keep datalogging. its like its running out of memory or something. I dnt even think the old laptop has 1g of DDR... its prob like 512MB. im gona have to mess with the USB ports and see if its cutting power to them but i doubt it.

 

I've got the same problems, it's the 165 ECM at 8192 baud. The 8192 output on the 165 ECM is not reliable, but 160 baud is reliable and can log all day long using WinALDL. It's not as pretty as Tunerpro RT, but, WinALDL still outputs all the data you need just maybe not at the refresh rate you would want. Moates.net indicated a couple years back that some of the older USB->serial boxes may be having some problems with electrical noise on the channel and that two solid capacitors are needed on the USB data lines to clean up the noise. But he said that all newer versions (2005+) of the adapter he produces have that modification already on it.

I am going to order another newer setup from him and it might fix it, who knows? We'll see.

 

then idk why mine wont log all day long since i just purchased mine 2 weeks ago.

 

Try WinALDL for logging and tunerpro for programming.

See if you can log in WinALDL for longer.

Pretty sure it's the 8192 output on the 165 ECM as I can sorta get it working for a little bit before I get synch errors in Tunerpro RT.

WinALDL works fine. It just doesnt update as fast as Tunerpro RT.

Try it and see?

 

i was on the phone with craig moates tday and thats what he said. he said that some of the 165 ECMs will cause the issue and some wont. no way around it.

 

I can attest to that. My friends 87 camaro would log all day long.

Both my replacement and my original 165 ecm can't.

Its pretty wonky. Hopefully WinALDL will get you the info you need.

 

i tired to do some things tnite that craig told me to try.

i started a datalog with the engine idling, once it connected to the ALDL port i switched the ALDL box from 10ohm to infinite. the log lasted about 2000steps... longest so far up untill that point. but it did cut out and freeze the datalog. so i then did the next thing that craig told me to do. which was after if froze, turn the key off and wait about 20seconds then turn the key back on and see if the log will start off where it stopped. so i did, turned the key back on but had to reconnect back to the ALDL port with the switch at 10ohm on the ALDL box. then it started recording where it left off, so i have one of those 165 ECMs that like to cause issues with datalogging in tunerpro RT.

weird thing is that i started a new log right after that and this log continuned to over 8000steps until i had to shut it off bc i reached my destination. so i got a full datalog of about 10min or so. im pretty exicted. not sure what caused the log datalog but im happy.