I must have mis clicked in the upload... it's there now. No need for a datalog unless glitch is gone, then I can use them to improve the adx...

So let me know how V1.2 works, if still a glitch I will add more pause or another repeat... sounds like it's getting better? One step at a time or we can pass where we need to be and create more problems. Needless to say this is easier when I have the car... but at least if we get it done another entire class of vehicles has an adx to work on and improve.

EDIT:I had some time so there is also a V1.3 to try after V1.2...

 

Yea its alot better!!! Tomorrow afternoon Ill datalog with the V1.2 and hope that works, If so ill attatch the datalog file up here. Im new at all of this tuning but dam* its addicting!

 

Since your addicted and willing to test I made a small change in each. You know where to get them. They go to V1.4. now... I need a little feedback on each so I know if I did the right thing, or wrong thing... but since you have seen improvement already I think if you try these in order we will find the stable part... then may pass it and get worse...

 

ok sounds good. i plan to do a good hour of logging tommorow.. ill let ya know the updates on them

 

Does that car have a digatal dashboard?

 

nope, all stock stuff. Ill be logging once i get home from work....2pm. Ill let ya know if that glitch is gone with the datastream V2.1

 

When you get to trying them, try them in order and note how glitch responds. I am trying to make this work from ALDL file for this car.

Then try V2, it is completely differant...

This ALDL.ds is 148.ds is $88 and has a mode 7. but not much info, actually no info? Well looking at 140.ds $A1 which is same ecm and engine (different car) with mode 7 but much more detailed commands. Even address for data is almost identical in every instance.

$88-V2.adx has a silence of $FO , then resume data $FO with pause...

But $FO is usually a poll to digital dash, data is usually from $F4. Look at 140.ds and most other aldl data files.

Anyway that was just info for others who want to learn ALDL.ds files and fix glitches in ADX files. For fasteddi just try them in order and let's see if we can get one working for $88... I don't know why this one wants data from $FO instead of $F4?

If none of these work solid I have an idea of going straight to $F4 (like $A1 and all others), but it would have to silence $FO and your dash would not work while datalogging... not even sure yet you have digital dash. Hard to do these by Internet rather than hands on...wish I had some lessons from Mark at TP or Saar before he retired...

 

Ok got logging this afternoon and no glitches at all with V1.3 I tried to fill as many boxes in the BLM tables as possible by also keeping the car in a low gear, higher RPMs and low and high load/Kpa. Drove arround for a bit, about 12 miles. It was a little cold though so the MAT was low, for the whole trip.

For some reason V1.2 would not work right for me. Kept saying connected(in blue) then error(in red) over and over.

Heres the lof file. Check it out and tell me what ya think. Thanks for the files to stop the glitching!!!!!

I attached the ziped file of the datalog.

 

Using $F4 for a packet header with the $88 mask won't work. The ECM won't recognize it.

What mode 7 is for is to request a scheduler message. There is a table of 16 entries that the ECM round robins through. If any entry is other then $0000 the ECM will use the address in the table as a packet definition table.

In $88, AZTY, there is one entry of the 16 that is filled in. This is what causes the chatter.

No digi-dash in fasteddi's car. The ALDL stream is only used for the ECM, no other devices are attached.

RBob.

 

Well all i know is my datalgging worked with no glitches, an what you guys are talking about is a little over my head.... So im just going to use that 88-V1.3 datastream

Definitly no digital dash here, sorry so say but i never liked them in cars exspecially muscle cars, sports cars....

 

Well he stopped at V1.3 which was 40ms pause and repeat data macro twice instead of once. Since he connected twice and may not have restarted car, it may have got a good connection? We need to find out if next time it connects first shot? Or needs disconnected and try again?

If he made it to, and I wish he would try someday V.2 it would silence $FO then ask for data replay which is from what your telling me what should happen. Silence chatter, ask for data. All other settings are same as V1.3. When I did this to the $EE LT1 it connects first shot every time! Without it could take a few connects to get good data.

Glad your getting data fasteddi!

Do please try V2 first next time and see how she does. If I learn some more here with testers I may be able to make these work first shot.

I got rid of the others, only V1.3 which you say works! And V2 are left with original ads for TPV4...

 

Well its so cold out that it takes the car a bit to warm up so i can datalog but as soon as I rough in a newer bin file then burn the rprom, ill use the v.2 and see if it works for me.

Im having issues on how/to change the ve table and not take 3 hours to manually calculate the new value(I.E BLM of 128/110=1.16 then multiply that by the existing VE value.) Thats gonna take forever! LOL

 

There's faster ways but I'll leave that to the more experianced tuners...ok here's one... if you take your history average for that cell it will give you the calulation needed in VE table/cell... then use the Execute button and fill in value, choose + or -... play with it your catching on fast!

I am trying to concentrate learning this adx/ALDL stuff because of a void when Robert retired... you helped me learn and we helped another catagory of car get an ADX!

With what RBob was telling me I think any ALDL.ds file that has a mode 7 should silence chatter then ask for proper data reply. Beyond the usual Pause fix. TunerProV5 is just to fast! You have to pause the reply!

 

Ok then say this cell is 105 history average. I would divide 128 by 105 then get 1.12 then type that in and push execute for that bin VE cell?? or take 105 divided by 128 and get .82 then use that value to change the bin VE value for that cell??

Id do that process for all the individual cells i have data for, then smooth them all out..correct??

 

do a search on here for VE fixer and you might find the thread. once you save your datalog you send it to Msoft excel and VE fixer will calc each correction factor for each cell. then you copy and paste it back into your VE table. or you can score an emulator and go thru each cell and make small adjustments until you reach the desired value. HTH

 

thanks! I found one VE fixer file for excel on moates site. Seems to work easy.

 

This way, and use the multiply function of the TP tool set:

The reason is that the ECM is pulling fuel out, so need a smaller VE value.

RBob.

 

Didnt quite understand those programs too well so i just did it the long way(took a hour), I just doing the hand calculations then modded the values in the current bin file tables. Since i only had about 3/4 of the history table set up the graph still looked like mountains after i entered all the new values. I then smoothed them out by hand as best as possible, and hopefully didnt change too many of the values. I know its my first attempt at moding bin files but well see what happends. Hopefully that moates adapter and such comes today or tommorow so i can pit the new chip/file in and log. Im sure its way off still but im taking baby steps......

 

I should have said History STD deviation gives a calculation. But you have to look at history average to see if it's lean? Above 128 then + that number in History STD deviation in VE corresponding table cell. If it's rich, below 128 then - the number in History STD Deviation in VE corresponding table cell. Then another data log... rinse and repeat...

I'm lucky to have excel spreadsheets I have learned to use for all ECM/PCM I do. But I do use this function above when Emulating to get closer!

But first yours are off! There are very rich numbers in there from when your car was warming up at 112 degrees. Even totally warmed up you were at 177 degrees, I don't know what effect that has in this mask?

Car needs to be totally warmed up before recording data. Your adjusting main VE that everything else uses to make adjustments off of.

Some masks have main VE and an Adder, some guys add the adder in Main VE. I do not and leave it alone and only work Main VE. On some masks like $42 if you ad adder to main the numbers come up higher then 100%? If you end up needing fuel beyond VE table RPM then add some to adder table which goes to higher RPM.

Some guys turn of AE and PE when warmed up to get a good data log. I do disable PE to get more BLM cells but leave AE alone cuz it drives like poop without! And it's always there anyway, if you have a bog at certain RPM after main VE BLM is close to 128 you can add some AE...

Remember close to 128 is good. Weather and temp change it so what is perfect 128 today will not be if weather tomorrow is different.

Smoothing has it's purpose but can ruin a good tune. Even back in carb days you have to give an engine what it wants, same with EFI! Engine has different needs at different loads and RPMs. The farther you are from stock the farther it will be NOT SMOOTH! Just because smooth looks good to a human does not mean the motor will run good. Give it what it wants! I believe that was quoted here from Grumpy (RIP)!

Since you want to race this, you should have a wideband O2 sensor and tune WOT in open loop! For race day! No need for O2 adjustments to keep close to 14.7 to 1 AFR on race day. There are also parameters to set for WOT AFR or increase but they are different in masks. Yours has Power Enrich Mode AFR vs RPM... like above it is an adjustment based off main VE...

HTH!

 

You also have an IAC ERROR that needs to be fixed. No errors when doing a data log. Who knows what effect it has on ECM and will have on data.

 

Wow well now im really confused....LOL.

In my first logs i didnt warm the car up but the latest I did...... Why does it say 116 temp at start up when at the beginning of the log I was at 170 degrees Coolent temp??

I didnt start recording my latest log till the coolent temp was at about 170#. It has a 180# t-stat and I manually turn the fan on/off, which i kept off the whole time. So recording in the 170-180# coolent temp is fine, correct?

My $ does have a Main VE, Idle Ve, and a VE adder. I only corrected the main and idle VE tables. Then smothed them out just so they didnt have so many vallys since I only had 3/4 of the history table BLM filled up. I just guessed on the values that I didnt have in the history table......

Moates stuff didint come in the mail today..I hope it comes tommorow because in a few days its gonna be too cold to datalogg. Its about 40-45 out the last few days but next week is in the 20's. So id like to get the best VE set up I can and get it burned on the chip by tommrow night so I can get my feet wet in burning a chip then logging it to see the outcome, then continue to tune.

I do look to get a wide band 02 sensor if i can find a affordible set up for the WOT tuning. I really have no idea how to tune by that. Just keep the car close to 14.7 give or take for what the engine runs best at, right???

 

What could cause my IAC error?? I replaced that sensor about 5 months ago. And seems to run right? Should i just clear the code and see if that corrects the error?

 

Now that I look at it the idle position values are at little weird. There form 30-40 someitmes which is norma..l then 0 or 5. mabey a bad conection/vaccum leak??? Remember i just ported the heads and installed a cam a month ago. I did the idle relearn. Seems like the more i drive it the better it idles, because at first it loped at idle as if there was a massive cam in it..

 

You're really zooming up the learning curve! When are you sleeping? I just got the cable etc. from Moates and will start on the software tonight. This is a really useful thread.

 

thanks base 91 hope all goes well when you start too!

Another question of a problem....my TPS signal is .65 vts at idle. Is that correct because of what I read it should be a little lower in the .45 vts range. Mabey that is a side effect of the IAC error.

 

The 116 degree start up temp, is the coolant temp of the engine when it was started/key on. Since you let the engine warm up before logging, that is why the log starts at 170 degrees.

 

so did i do it wrong? Or should i not connect the aldl till after i warm it up then start it. Does the start up temp affect the recorded log?

 

An IAC error is set when the idle doesn't hold at the proper RPM. IOW, the ECM is losing control of the idle speed.

Good possibility that there is a vacuum leak. Or that the IAC is sticky. The IAC steps seen in the log is a commanded value, not where the IAC actually is.

RBob.

 

0.65 volts is OK for the TPS at idle. It is not adjustable and the ECM auto-zeros it.

RBob.

 

If the throttle body blade wasnt completly sealed when shut , would that set off the error?? code 35..

 

Throttle blade is never completly shut. It has a minimum air setting... open a tad. When completely shut and you start engine it's very hard to push pedal then snaps open. Hence a minimum air setting, then IAC controls more air for idle.

Most common a vacuum leak, could be anywhere, is your throttle blade a little loose? IAC will also get dirty like RBob said, clean it but don't let brakeclean or ? drain into electric end. Have plug end up and spray it clean, check passage ways for IAC that they are not clogged up...

I may have been off there but first BLMs I saw where all 100. Not that way at end when idling. So just trying to advise data log should start totlaly warmed up, closed loop.

Clear the error see if it comes back look for vacuum leaks.

 

Ok ill get on it tommrow. the passages arnt clogged and the IAC is very new. Posssibly a vaccume leak i suppose. Ill data log tommorow if i can get the error so stay cleared.

 

Don't forget to try V2! I'd really like to know if it works? Also if V1.3 connects first shot every time! Or is it hit and miss?

V2 is same as V1.3 but has an engine connection (silence, ask for data) really it should work better. But I need feedback so I can learn and do these for others!

 

starting to have some issues with V1.3... when I connect it sometimes it goes(connected then error) over and over and over. Even if I dont hook the car up. But then sometimes it works. Make any sence. I really hope to fix this tommorow, get the moates stuff burn off a chip if i can get the code 35 to stay clear on the car and see if i can get some logging with a newer bin file since i dont have to work tommorow.

Im going to try v2 right now and see if it does the same thing as V1.3 is doing to me right now.

 

Ok for some reason v1.1 v1.2 and v1.3 are all doing the Error in red, then connected in blue, there flashing back and forth. But when i load the original 88.adx file it does not do that it jsut says connecting since i just have the cable hooked to the computer and not the car.

Any ideas???? I know that original 88.adx is worthless for me becasue of the glitches.

also those were the only 3 files i had v1.1 v1.2 and v1.3. I though there was another (v2) but its not on the gearhead thread anymore and i cant find it. Thanks for any halp because i really got a day full of work on this tuning tommrow and its my only day for a bit to get some stuff done. Thanks!!!

 

any ideas why every adx file is making my tunerpro program go into non responding mode except the adx file that has no history table... im really hating computers right now.

 

Heres the update. For some reason my tunerprort v5 does not wana work correctly on my lapto. (non responsive program) So i installed tuner pro Rt V4 which i dont like but i did data log and made a new eprom on the programmer which was amazingly easy. I then data logged again and will look over the excel tables later as the tuner pro rt v4 didnt have history tables for the BLM. So needless to say i need to get that V5 tunerpro working. I was finally getting the hang of that software.

From what i did see though my BLMs were better at crusing speeds and throughout slow acceleration. For the most part they were arround 125-130 for both the int and blm values, but there were still the problems when i was coasting to a stop. It was lean. so i need to play some more.

You wana laugh??? Ok after i took the chip out and laptop and such i left in my daily driver for a bit then returned to see it was raining, so i started up the camaro and it was idleing high as HEL*. Im like what the heck did i do.......ya there was no eprom chip in there and it was running on limp home mode... opppps!!! Though you all would get a laugh out of that.

 

is DFCO active when coasting to a stop?

 

Im a beginner whats DFCO?

 

Ok i ended up getting logging on tunerpro rt5. Ill put up my history tables. it looks better then before but still needs work. Only drove a good 15 minuets, was gettin low on gas.

I dont have many low 100's in the bml values so thats better, i guess im on the right track slowly.

 

oh my bad, its decelleration fuel cut off. when you are coasting down with foot off the throttle, the ecm cuts fuel for economy and for added engine braking.


which cell does it idle in? idle speed at what kpa?

 

Idle speed when im coasting? When i slow from 40mph it in the 1200 Rpms @45 Kpa Cell. It pretty much stays in that cell till im going like 5mph.

So its just staying lean because of the DFCO mode?? So that readings ok? Itll have 138BLM for a split second then, instantly to 100 BLM, once i start coasting.

 

Heres the latest data logg after i finally got the IAC error to go away and not come back... those tables still need work... FLUSTRATING! BLM #'s went down since the IAC error stayed off.

 

Just ignore DFCO BLM cell readings for now, cells that are lower MAP then idle. When you decelerate it will be higher vacuum then idle/lower MAP kpa then idle...

and fix why you go open loop for no reason?

 

Yea why th hel* does it go into open loop every now and again for a few seconds?? Im not sure what would even cause that...

Im looking on the bin now for where you would change the values if i have a lower t-stat. Theres gotta be somwhere in here that i can change the temp for when its fully warmed up from the stock 195% t-stat value. Then ill check the 02 sensor and the wires, i have a spare o2 sesor that i know it good, just in case thats whats throwing it into open loop here and there.

 

Im looking at the min and max temp for enabled closed loop timer in my bin file. When converted the temps for max temp to enable were about 180 and the min was 170. And these values were also 120 seconds durration for the timer.

Since these temps were border line of my running temps be the cause of the open loop turning off and on every now and again?? Im not sure but ill play with the bin a little bit and see if i can get that fixed. ??? yea Im a little lost on how to proporly change the values for a lower running temp..

 

Closed loop CTS threshold:

L86DC FCB 136 ; 62c, closed loop coolant threshold

Closed loop BLM learn CTS threshold:

L86DF FCB 107 ; 40.25øC, closed loop learn coolant enable

Also, if the injector PW goes below 1.3 msec the ECM will drop out of BLM learn mode.

Note that there are only 3 BLM cells: idle, cruise, & decel. With the decel cell being a bit strange. IIRC, it uses the cruise value that is modified then plugged into the decel BLM cell. I don't believe that it will actively learn the decel cell.

Lots of strange code in the $88 mask. Another great one is how the INT is locked at it's current value when entering PE mode. Trying rolling into the throttle and note the INT when the ECM enters PE mode.

Since the AE is lacking the INT will sky-rocket, dragging the BLM with it. Then lock both the INT & BLM at a high value for PE mode. Can you say sloggy rich? Have a patch for that one around here someplace.

RBob.

 

Ok i logged for the last time today. the ave. history looks ok but I also looked at the recent running average #'s and those look a little worse now then the history average #'s. Does anyone know why the ecu shifts from closed to open loop sometimes?? The Pause W M doesnt drop below 1.3 when it does this. And it only goes into open loop for a second. then goes back into closed loop for a while. I attatched a newer data log. Seems better i suppose but its really hard to get them all near 128+ or - 5 figures.

 

EGR and CCP disabled?

RBob.

 

I have the EGR on the car still so i havent disabled it. It goes on and off while im datalogging.

I havent changed anything to dissable the canister purge CCP. I dont know whered you would see any values of it while datalogging.

Sorry im not sure how to answer your post since i havent attempted to change much else in the bin except the VE tables, I disabled the air system, and tempeture threshholds to match the lower t-stat i have. Should i lower the temp threshhold to enable the CCP. Its 56#c on the stock values??? Same question with the enable ERG valve, should i change that to be lower??