code $59 ?

STORM TROOPER

New member
ok every time i copy from autotune and paste in bin after i save it and pull it back up to look at it its not the same as what I saved..

51.56 53.91 54.69 55.47 56.64
53.52 54.30 54.69 55.47 56.64
54.30 54.30 54.69 55.86 57.03
53.91 54.30 54.69 55.86 57.03
53.91 54.30 55.08 55.86 57.03
53.91 54.30 55.08 56.25 57.42
53.91 54.30 55.08 56.25 57.81
53.13 66.02 60.55 54.30 58.20
52.73 64.84 50.39 55.86 66.02
51.95 61.33 60.94 60.08 62.50
50.78 59.38 68.46 56.59 57.94
50.00 51.17 74.53 47.29 57.88
49.22 50.78 75.37 55.71 55.81
48.83 50.00 60.94 58.23 46.12
48.44 50.00 55.86 48.04 42.37
55.47 57.42 67.19 68.75 67.19

this is after
51.56 53.91 54.69 55.47 56.64
53.52 54.30 54.69 55.47 56.64
54.30 54.30 54.69 55.86 57.03
53.91 54.30 54.69 55.86 57.03
53.91 54.30 55.08 55.86 57.03
53.91 54.30 55.08 56.25 57.42
53.91 54.30 55.08 56.25 57.81
53.13 66.02 60.55 54.30 58.20
52.73 64.84 50.39 55.86 66.02
51.95 61.33 60.94 60.16 62.50
50.78 59.38 68.36 56.64 57.81
50.00 51.17 74.61 47.27 57.81
49.22 50.78 75.39 55.86 55.86
48.83 50.00 60.94 58.20 46.09
48.44 50.00 55.86 48.05 42.19
55.47 57.42 67.19 68.75 67.19
is there a peramiter that im missing or that I need to change?
 

jpalmer

New member
Re: code $59 ?

I think everyone is busy this weekend Steve. Just wait patiently and if that does not work, i know someone who is good with this stuff that will help you out.
 

dgoodhue

BuSTeD 4.3
Re: code $59 ?

I will try to explain this quickly as I can. It's normal The numbers are changing because of the resolution of table, the number is changing to nearest level. The VE table is 8 bits so there are 256 values or levels with maximum of VE of 100. So 100/256 = ~.39 per level

The middle value of the VE is 128, which 50. The next value of 129 computes to 50.39, if Autotune suggests 50.25, tunerpro will change the value to closest value which is 50.39 when you save the VE table.
 

STORM TROOPER

New member
Re: code $59 ?

I will try to explain this quickly as I can. It's normal The numbers are changing because of the resolution of table, the number is changing to nearest level. The VE table is 8 bits so there are 256 values or levels with maximum of VE of 100. So 100/256 = ~.39 per level

The middle value of the VE is 128, which 50. The next value of 129 computes to 50.39, if Autotune suggests 50.25, tunerpro will change the value to closest value which is 50.39 when you save the VE table.

:tup: thanks
 

skwayb

NWSTP
Re: code $59 ?

The next version of Autotune I am working on will do the rounding before you paste it back into Tunerpro so this problem goes away. Just waiting for a few others to check it out before I release a beta version of Autotune 2.5
 

STORM TROOPER

New member
Re: code $59 ?

The next version of Autotune I am working on will do the rounding before you paste it back into Tunerpro so this problem goes away. Just waiting for a few others to check it out before I release a beta version of Autotune 2.5

sweet keep up the good work...next question I put my other chip back in and the afr was off from what my guage was saying in tunerpro, is there a way to fix or adjust this?
 

WyoSyclone

Active member
Re: code $59 ?

sweet keep up the good work...next question I put my other chip back in and the afr was off from what my guage was saying in tunerpro, is there a way to fix or adjust this?

Make sure you have the correct wideband selected in TP. Some of the early BINs available in the downloads had two widebands selected - go through all of them and make sure only the wideband you're using is selected... if you have a wideband that requires calibration (Innovate, and probably others), make sure you go through that process.
 

STORM TROOPER

New member
Re: code $59 ?

so Im in the middle of trying to fine tune this baby and was wondering should I be getting some knock counts while giving it gas? Im going along at about 30-35 and if I give it about 1/2 gas it takes arround 90 counts almost every time. Is this normal? is there a way to tune it out? tia
 

Mr.Smith

New member
Re: code $59 ?

I will try to explain this quickly as I can. It's normal The numbers are changing because of the resolution of table, the number is changing to nearest level. The VE table is 8 bits so there are 256 values or levels with maximum of VE of 100. So 100/256 = ~.39 per level

The middle value of the VE is 128, which 50. The next value of 129 computes to 50.39, if Autotune suggests 50.25, tunerpro will change the value to closest value which is 50.39 when you save the VE table.

You lost me at hello...
 

STORM TROOPER

New member
Re: code $59 ?

so Im in the middle of trying to fine tune this baby and was wondering should I be getting some knock counts while giving it gas? Im going along at about 30-35 and if I give it about 1/2 gas it takes arround 90 counts almost every time. Is this normal? is there a way to tune it out? tia

anyone?
 

WyoSyclone

Active member
Re: code $59 ?

The knock counts don't matter, the KR does. If you read Tooky's info over at PowerTunePlus, he mentions that one of the versions of Datamaster was revised in a manner such that the knock counts really don't mean much.

Look for what KR does... when you're starting out tuning it won't be unusual to see it up around 6 degrees KR, or even higher. You want to work on eliminating the KR via optimized AFR's and timing, as related to your boost target. You may have to work up to your boost target in steps, playing with timing as you go. Make sure you've got good gas.

HTH.
 

jpalmer

New member
Re: code $59 ?

The 180000* temps here can't help much either. It felt pretty good today Steve, and still faster than mine. :oops:
 

STORM TROOPER

New member
Re: code $59 ?

thanks Wyo, next question I downloaded someone elses bin, I have not seen any kr during my tuneing is there a way to check and see if its on or is there a way to adjust this? thanks
 

turbodig

Active member
Re: code $59 ?


Run the truck at about 2000 RPM.

Tap on the alternator bracket with a hammer.

You should see KR.

Unless the tables have been messed with, knock counts and KR are linked.

I get as much info out of knock counts as I do out of KR. There are many poorly calibrated KR tables around, and the KR numbers will vary with what's in the tables.

In particular, *where* knock counts are in relation to shift points, boost spikes, AFR changes, and timing changes is useful information.

Once you get a base tune working well with minimal or no knock counts/KR, you'll want to verify this with a plug check. The plugs are the only true way to know what's going on, cyl-to-cyl.

70% of tuning in SyTys is fixing the broken stuff, either mechanically, electrically, or fuel-wise.
Once you identify and fix those issues, you can really start to make progress.
 

WyoSyclone

Active member
Re: code $59 ?

I get as much info out of knock counts as I do out of KR. There are many poorly calibrated KR tables around, and the KR numbers will vary with what's in the tables.

In particular, *where* knock counts are in relation to shift points, boost spikes, AFR changes, and timing changes is useful information.

That's good info, Dig.... thanks for post. Since I'm just getting past the elimination of KR on my Sy, I'll go back and look at the counts to see if I can see any useful info.
I would guess that one would look for whether the counts gradually ramp up, or whether they start more spontaneously? I can imagine mechanical/tuning issues causing each scenario.
I think a person could keep digging (no pun intended) for decades with the tuning/log info and still keep learning. :D
 

turbodig

Active member
Re: code $59 ?

That's good info, Dig.... thanks for post. Since I'm just getting past the elimination of KR on my Sy, I'll go back and look at the counts to see if I can see any useful info.
I would guess that one would look for whether the counts gradually ramp up, or whether they start more spontaneously? I can imagine mechanical/tuning issues causing each scenario.
I think a person could keep digging (no pun intended) for decades with the tuning/log info and still keep learning. :D

As you're scrolling through a log, (speaking in DM terms here) watch where knock counts increase in relation to RPM, particularly.

For example - if you see knock counts increase by a big jump as the RPMs drop on a shift, but then don't move again until the next shift point (regardless of what KR is doing), it would point to either:

1) A noise related event at the shift - motor mount, DP rattle, fuel lines tapping, converter, etc.
2) A real knock event that happens as the engine is being loaded heavily.

Taking out lower-rpm high-load timing and adding a bit of fuel will generally reduce the magnitude of the event if it was real, but it won't do much if it's noise generated.

Counts that count up to large numbers in nonsense places tend to indicate noise or a problem in how the chip was installed.

Mid RPM counts that count up, followed by a timing pull-back and the counts stopping, then the timing re-applies, and the counts come back... pretty obviously real knock.

Also - you can correlate counts to AFR events - lean spikes, or persistent richness (numbers <10.0 for a longish stretch of time). Correct the AFR issue, and you generally see the knock go away.

As I said before, once you think you have something 'decent', check the plugs. Probably good to cut the first set (or maybe 2) up so you get a good read of the porcelain deep inside the plug. Once you know the general 'lay of the land' as far as your cyl-to-cyl balance and overall fueling, you can generally just spot-check a plug or two.
 
Top