code59 log results

Sean Donn

New member
I began code59 tuning for the first time today and saved a log to see if I can get some help from you guys. Uunfortunately I do not know a good way to share the xdl file. I am running wyosyclone's 40lb bin, code59_3bar_1.6_v18.xdf, and a160.adx. I am unsure if my method is right, but I used a delco chip that I had piggybacked on the ecu and rewrote it with wyo's starter bin file. I then drove around for a couple minutes and collected the data linked below.

update: after changing to a different .adx file, I logged a new file that is much better than the one linked below. I then encountered the white smoke issue discussed in my following posts. any input on what it could be from would be greatly appreciated
 
Last edited:

Sean Donn

New member
Re: code59 log results

Today, I uploaded the tp5 beta .6 adx file and attempted to work out the fueling for my truck.

After getting my desired afr at idle by messing with the f28 table, I drove around and logged a run. my highest boost level that I reached was in the 19psi range. At this time I experienced some white smoke coming from behind the horn button on the steering wheel. There was no smell and it was not a lot but it was smoke. Because of this I chose not to drive the truck anymore until someone could shed some knowledge on me. anyway, After I logged a run I converted to a .csv file and then made an attempt to autotune to get a better f29x table. The excel autotune did not offer me a corrected table despite me entering my bin f29x, f29 afr, and csv file from excel. (the csv file didnt seem to exactly replace the info in the RAW DATA section. I also changed the value to 3.50 for stock injectors and the number of samples to 1.) it then said "autotune used 0 sample to correct 0 of 512 VE units with 0 of them being boost values" or something along those lines.

MY QUESTIONS ARE: what do I need to do to get a corrected f29x table?
Why the white smoke? before code 59 (using previous chip) I never had something like this while accelerating with relatively high boost levels.

Thanks in advance
 

skwayb

NWSTP
Re: code59 log results

Autotune only works with Tunerpro 4 out of the box. We haven't made a version that works with Tunerpro 5 yet since the log export is different.
 

Quickstop [UK]

Combating adversyty.
Re: code59 log results

The contacts in the column are the horn and the turn signals. A bit deeper in you have the cruise and wiper switch and the hazard lights.

White smoke from the column is bizarre. Have you taken it apart recently? Do all the accessories/ indicators work?

Take the horn button off carefully as there's a wire on the back and then see if that helps. Sounds like a short in there somewhere.

No smell of burning?
 

Sean Donn

New member
Re: code59 log results

no smell of burning and I found it especially odd to only happen during high rpms. It actually happened twice and the white smoke rose from behind the horn button for about 5 seconds. after that the smoke dissipated and I drove around lightly for another 5 minutes and everything was normal. The horn and turn signals work. I will take it apart this weekend. for me, the fact that there was no smell kind of eliminated a firewall issue but smoke is smoke and it's f**king scary feeling like you're about to blow up when you're driving. especially when you just messed with fuel tables for the first time.

any help is appreciated and thanks, Quickstop [UK], for your response
 

dgoodhue

BuSTeD 4.3
Re: code59 log results

If you just started tuning, you should work on the part throttle in vacuum first then slowly work yourself into part throttle boost, the last part of tuning should be wot. I hope that white smoke isn't blow by leaking past covers and into the interior.
 

wildphil

I Love My Ty's
Re: code59 log results

If you just started tuning, you should work on the part throttle in vacuum first then slowly work yourself into part throttle boost, the last part of tuning should be wot. I hope that white smoke isn't blow by leaking past covers and into the interior.


Please listen to this advise. You have a lot of tuning to do before you do to 1lb of boost. I just hope its not to late. 19lbs of boost on no tune=new engine most of the time.
 

Sean Donn

New member
Re: code59 log results

the truck is running fine so I'm almost positive it is not "too late", however I'm realizing that I made some rookie mistakes today. The smoke very well could be blow by and if it is I'm not sure where to begin tackling an issue. I was also under th impression that the .bin I was using was suitable for boosted driving to a certain extent and my truck is almost identicle to the truck that .bin was created for. should I just continue tuning and tweaking at a slower more controlled pace or is this short smoke incident something I should thoroughly look into beforehand? Thanks for all the responses
 

Sean Donn

New member
Re: code59 log results

dgoodhue I see that you answered this question for someone back in 2009. I do know that I have a small oil leaking issue. I've seen it myself when the truck was up on a lift. a couple oil droplets were collecting under there. When my truck came back from Sportmachines they also informed me of this issue, but said that it is rather expected with a 20 year old truck and isn't an issue considering it's not much oil.
 

WyoSyclone

Active member
Re: code59 log results

I began code59 tuning for the first time today and saved a log to see if I can get some help from you guys. Uunfortunately I do not know a good way to share the xdl file. I am running wyosyclone's 40lb bin, code59_3bar_1.6_v18.xdf, and a160.adx. I am unsure if my method is right, but I used a delco chip that I had piggybacked on the ecu and rewrote it with wyo's starter bin file. I then drove around for a couple minutes and collected the data linked below.

update: after changing to a different .adx file, I logged a new file that is much better than the one linked below. I then encountered the white smoke issue discussed in my following posts. any input on what it could be from would be greatly appreciated


I'm familiar with that BIN :D
Looking at your log I only see up around 7lbs of boost, which is what I would expect with that one at your TPS values. To really get it dialed in I would recommend you get your wideband integrated into your ECM - then we can look at your AFR's and be safe in taking the tune further.
 

Sean Donn

New member
Re: code59 log results

I'm looking over it and it shows a ton of knock retard. I'm beginning to feel like a bit of a retard myself :(
I have a feeling some people are going to sh*t on me when they look at this file
 
Last edited:

WyoSyclone

Active member
Re: code59 log results

I'm looking over it and it shows a ton of knock retard. I'm beginning to feel like a bit of a retard myself :(
I have a feeling some people are going to sh*t on me when they look at this file

Gotta run to work, but, look for sources of false knock. That looks like something physically hitting something (not internal to the motor). Check for a broken motor mount, downpipe hitting, all the normal things (search on here for knock and kr).

Looking at the timing I would guess your base timing is off by about 5 degrees (too far advanced). Locate top dead center, check mark on balancer, then recheck timing.

I'll look a bit more after I get back from work this evening.
 
Top