Are they all the same tune or before and after changes. And it would help if you were specific about the areas that you are having a problem with. Time stamp or screen shots.Quote:
Originally Posted by mychevyisntheavy
Printable View
Are they all the same tune or before and after changes. And it would help if you were specific about the areas that you are having a problem with. Time stamp or screen shots.Quote:
Originally Posted by mychevyisntheavy
Here are screen shots of your 3 logs, I understand your confusion.Quote:
Originally Posted by mychevyisntheavy
These can't be from that one tune file as one is in Open loop, the other 2 are closed too and day and night apart... (the open loop log graph is from AFR error on wideband, the other 2 are fuel trim errors)...
Attachment 163262 Attachment 163263 Attachment 163264
i am trying not to go in pe, im slowly pushing the pedal down but steadly pushing to the floor. trying to get the cells filled up not flooring it from a dig. just slow as i merge onto the highway.
all three are from the same tune. in the vehicle special functions . i do turn off the open loop and the ltft settings right, or just leave those things alone.?Quote:
Originally Posted by dhoagland
ive never have done a wide open dig yet with this thing i know the tune is way off. im gonna get it dyno tuned here soon and then you guys will be done with my dumass, sorry, i just cant get this im trying my best. just cant do it. and i work on crap as a mechanic, but not this type of stuff id go broke if i did. why did they change from carburetors and distributors...thanks alot for your input.
i went back to where you guys told me to us both afr, and tirms . i using that tune. im gonna log with this tune. so here in abit ill back in here with this tune and the log for this tune. i will not make any changes to the tune, ill log the scan and up load it in here with the tune untoched. so you guys can look it over. all i know to do.:banghead::mad::bigshock:
Just post logs and tune as a pair each time. And the tune should be the one that was in the vehicle at the time the log is made, prior to any corrections. If you post them as a pair every time, there isn't any confusion. No need to post a tune prior to making the log. The more orderly you do this, the easier it is to help you.Quote:
Originally Posted by mychevyisntheavy
ok here is the tune before i touch it. here is the log of the same tune. slow steady throttle. :banghead:
does this look right to you guys, smh. this was done with the ltft&stft from my scanner
this tune was tuned with afr error, in my scanner
see why im having problems!!!!! which do i go bye..??????
Slow down, one pair at a time. It gets extremely confusing for everyone trying to help you. If this says this:
Attachment 163274
Don't even worry about what the wideband says at this point, unless it is really high or low, if it is showing around 14.7 your trims are doing what they are supposed to do.
I took the unedited pair you posted and applied the log to the tune and did some smoothing, give it a try if you'd like, post a log of it if you try it.
Attachment 163275
YesQuote:
Originally Posted by twenglish1
Try this and post results
sorry fellows just been really busy, ill post one tomorrow. i just want to thank you guys alot.
have any of you guys seen a ve that looks like mine, really this things is god awful. smh.:doh:
Sorry I missed this earlier...Quote:
Originally Posted by mychevyisntheavy
I never use the special functions to put the vehicle in open loop or disable fuel trims when I'm logging, I'm not saying that some people don't I've just never heard of it...
I was taught to put the tune in what ever mode you are going to be logging.
So what I believe you are trying to do is Speed Denisity (so MAF Fail in the tune file), Closed Loop, using Long Term and Short Term Fuel trims to create an Air Fuel Error log in your graph to adjust your VE table...
So once your tune is set for your desired Tuning mode, and the last time I looked it was, you just go out and drive as smooth as you can and collect data.
rest the codes it had; mass air flow, knocks, and it has this on going trans it sometimes doesnt see the shifter.(which gear it is in). rest those. i did reset the idle to to get the counts between 40 - 60 on the iac. other than that i havent did nothing to the tune. can you look at the idle area , its doing better but it dips in gear. if in park its great but in gear it smooth then falls , it did die few times. once i come uo to like a stop light or anytime im in gear with the brake once i let go of the brake its fine. i think it might need less follower. the ve look horriable to the eye.Quote:
Originally Posted by dhoagland
sorry, i log one earlier and put in the errors and changed the reds to the greenish color. and just smooth one time. a over all smooth. just onces. only thing i did was, i changed the cracker to see if i could stop the idle surging. if you watch the log at the end its still doing it but alittle better. it didnt die this time. looks like the iac goes to zero or 1, then catches its self. i did tune it with the last log, and drove to get a new log, here they both are. pss. a i changed the iac sensor with one i had. its new. so let me see how this does. but the tuning no i havent changed it this is the tune and the lastest log.
pssss. on the tuning if like for instances you have; 94.55 in on cell and 93.66 and 99.68 . i interpolated from 99.68 to 94.55changing the 93.66 so that its in line. i made those chanes if i saw that any area was out of line. then smooth one time . this is right? i hope?
The colors don't really mean anything, and someone would have to use your xml configuration to see them the way you see them.
the colors im seeing is from the ltft&stft. using the math to make error table by half%. some areas is like a blueish green, and other areas is like pink... to make the pink into the bluesish green color you hit the smooth or interpolate between the blueish green so like bluis green say (57.21 blueish green) and (61.48 is pink)(then blueish green 63.01) interpolate to make the pink to a lower bluish green. once i have the whole errors a blueish green in color and following in order of numbers i smooth one time.
Are you talking about on the scanner or the editor? My editor is set up to change colors when the values are changed. I've never tried to setup colors for values in the editor otherwise and don't see that as helpful. But then again, I don't really use colors in the scanner either.Quote:
Originally Posted by mychevyisntheavy
i get the error from the scanner. once i load the error into the ve, in the editor, it changes color to a blueish green, or a pinkish red. and to make the pinkish red to the bluish green smooth between the bluish green or the table itself. in the editor. its how ive been making the ve. into the shape it is. not from just hitting the smooth button till u cant change it anymore. i just hit it one time after ive lined all the cells up in order. in up to down from left to right. so there is not spike or a big dip. smooth transition in all directions. but not to smooth. its how i got to this point.Quote:
Originally Posted by gtstorey
unless im doing it all wrong, do i change the bluish green to pink. or do i change the pink to bluish green. remeber im a newbie here
and im no advance tuner either lol:secret:
You may need to pay more attention to the number of hits for each cell in the scanner and less to the colors in the editor before you start smoothing. Weigh toward the cells with more hits.
My editor may do that when smoothing, but I'm paying attention to the numbers, not the color.
right im looking at he numbers so the they follow in order. like 57.68, 56.88, 58.99. i tune it to change the( 56.88 to like 57.78). but what im asking is the color in the tuneable ve table is in bluish color and a pinkish coor. do i tune out the bluish color or the pinkish color. which way. is itQuote:
Originally Posted by gtstorey
I determine which ones have the most cell hits and hold those as boundary. I don't worry about the colors.
i think im doing this all wrong. my ve looks not a ve. its a huge ass valley it cant be right.im taking the higher numbers and making them go lower in every cell that has a error. it has to be wrong . i should be building a mountian , it is a huge bowl that i have made. look at it
its not right at all it has to be wrong. its way im having so many problems with this, im tuning it backwards, it has to be wrong. im lowering every cell that has a error.
Have you considered hiring Alvin or edcmat-l1 to remote tune this for you instead of the later "dyno" tune?
have no clue who this is. im about to pull the motor back out anyways. to do the up grades. im no tuner thats for sure, but i can work on this things. ill figure it out . i do think im doing it backwards, the ve looks way off from other ve ive looked . this motor is no baby. the ve should be bigger. its a bowl. look at it. i went the wrong way in tuning. i should have made the numbers bigger. it has to be the reason im having knock issues. i knew something wasnt right. i just dont think im was going in the right direction the whole time. i guess thats way i kept coming here asking question hoping to get help. thinking id figure it out. but yea, i mean look at the ve. in the diagram pic. its a bowel. i built a bowel. lol. so yea, im gonna start going the other way with the tuning. slowly move the ve upwards. i should have the stuff i need to make my changes this month coming and then get is dyno tuned bye someone that knows way more.
Why are you so worried about what the VE looks like? When you are done tuning it properly the VE will take whatever shape and contain whatever values it needs to accurately model the airflow characteristics of the engine. You are completely looking at this the wrong way. Here is a perfect world scenario, if you have a cell with a positive fuel trim, say +10%, that means the PCM had to add 10% to the corresponding VE cell to achieve the target air fuel mixture. It shows up in the data when you log, then you add 10% to that cell in the tune so the PCM doesn't have to make the correction next time. Then when you log again that same cell will show up as a 0% fuel trim correction and is now tuned.