SmokyTyrz

Well, maybe not "Help!", but it got you in here. :-)

So I've got a msg out to TXS and am waiting to hear back. But I wanted to see if anyone here knows..

My UTEC was delivered with v2.7. But the base parameter and map files on TurboXS's website are still for v2.6 I was under the impression that the documentation cautions us not to mix and match. Even says this on the website by the downloads.

So is anyone here using 2.7 that started with a base map?

Thx
-Smoky

QuadCam

iTrader: (8)

when did they release 2.7?

SmokyTyrz

Not sure if it is available to anyone except those who are buying new units. My unit came with 2.7 on it already, which I thought was odd because (like you've noticed) only 2.6 is posted on the site.

I called TXS and they confirmed that 2.7 is the latest version for the Z.

So now I just need a base map and parameter file, or someone to confirm that it is ok to use the 2.6 files (and just double check params, etc).

QuadCam

iTrader: (8)

what is changed on 2.7?

you should be able to transscribe a base map from 2.6 to 2.7 if you do it manually. You ,may be able to auto upload it and have it work. otherwise, just do it by manually inputting the data tables.

Kenk2

iTrader: (7)

Yea I got version 2.7 also and I uploaded Jeremys map and parameters when I started tuning.. Everything went fine, no problems at all.

I wouldnt worry about it..

SmokyTyrz

Jermaine just emailed back and confirmed that I can just load the 2.6 files. I'll still re-enter the Param file manually though. Maybe both, just to be safe.

Jermained did say that if you are using Open-Loop Fuel to set the TPS% at 65%. Perhaps the default is different? I'm not using open-loop fuelling yet anyway, so it doesn't impact me.

QuadCam

iTrader: (8)

Jermaine just emailed me 2.7. I have a strange bug that is making tuning difficult. Maybe, 2.7 will help things.

Kenk2

iTrader: (7)

Hey QuadCam.. Whats the issue you have?

SmokyTyrz

Yes, do tell!

techcontrol

iTrader: (4)

Did anyones' utec vendor notify them of the 2.7 release? Also, if utecs are being shipped with 2.7 why is the website not updated to reflect this?

QuadCam

iTrader: (8)

my datalogs keep showing a pulse width of "15.50" miliseconds. The problem is the 15.50 is coming out of nowhere!!! I can't see where the "15.50" would come from. It was outside the range of the load sites , too.

for example, the previous pulsewidths wre 17.2x, 17.6x, and then 15.50, 15.50, 15.50. then the pulsewidth attempted to climb back again...16.xx, 17.xx. Then it dropped back 15.50, and stayed there for 5 more datalogs.

I recorded a couple times where I got knock when it leaned out by dropping to "15.50." One of the times, it dropped from a 20.xx ms Pulsewidth down to the "15.50." That is a 25% drop in fuel!!!

It is very odd to get the exact same number for 12 out of 20 logs points.

I just loaded 2.7 and kept my same maps. I need to datalog, but now I am not getting any more knock. I only got on it a couple of times ont he way back from work.

Kenk2

iTrader: (7)

I will pm you with my email addy.. Get some logs and email them to me.. I would like to see what is going on A/F wise at that range..

Kenk2

iTrader: (7)

Good question..

I am thinking they wanted to keep it under wraps and not make a huge deal of it.. I know that 2.7 has been around for about 6 weeks.. Since I had my first UTEC it was on there..

I am thinking it had alot to do with the 'grounding issue' they said they were having..

I am attaching my latest log as of last Sat morning.. I couldnt get to redline as I was approaching cars rather quickly.. I got rid of my knock issue in the 6000 rpm range.. pulled my stock timing and that seemed to take care of it... My stock timing is pretty outta control..

Sorry to hijack thread

SmokyTyrz

Ken when you say you pull timing, how many rpm rows ahead do you begin to make the change before the rpm-point where the issue you observed previously occured? Just curious if you've determined a rule-of-thumb for that yet.

Kenk2

iTrader: (7)

I change the whole row..

When you log, you want to do so under full load (TPS% @ 100) 97, 98, 99 is fine too.. That is pretty much full load.. Just floor it, start the log at 2000rom(spacebar) and hold on till rev limiter.. My case is 7100 or so your case, Rev-Up is what 6800..?? Hit spacebar again at rev limiter and theres your log.. Makw sure you set Hyperterminal to 'Capture' and name the log like 1.txt.. I start out at 1 and go to 2, 3, 4 etc etc.. Its pretty easy to get a hang of but make sure you capture before each log.. Do like 5 runs, and head home to read and look closely at the logs and see what you need to change A/F wise and timing wise..

SmokyTyrz

Ya..I think I've got all that in theory (seriously have read the manual way too many times...good writing actually!)

I was just wondering how many rows up in your log data do you begin to account for why knock occured, or why timing is jumping around.

For example, if in your log you noticed a knock at 6000 rpm. AFR was spot-on, but timing was pulled regardless. So you go in to retard timing a couple degrees to see if that smooths it out....

So do you initially focus only on the specific rpm/load site and pull 2 deg timing out in one spot and see if it was the right one. Or do you select a group or matrix of 2x2 3x3 or maybe 5x5 load sites and add 2 deg across all of the sites around the load site where the knock actually occured?

In other words, how many load sites +/- the trouble site do you make adjustments for timing and fuel? One at a time, or several at a time? If multiples, do you have a rule of thumb for how many load sites to adjust before it gets too difficult to track changes?

Kenk2

iTrader: (7)

If I had a knock count of say 4 or above, @ 6100 rpm's I would pull timing at 6000 and 6250..

From my latest logs, I had many knocks from 6100 to like 6850.. So from 6000-7000 RPM's I highlighted and changed that whole block..

For me, it seemed to get rid of my knock issues.. And trust me, in that rpm range I have the knock sensitivity set to like 55..

You have to just play around with it until you get it.. You will know once you get it 50-75%.. Car PULLS so much harder.. You can totally tell the difference!

mikead_99

iTrader: (5)

More importantly, to me anyway, is there any reason to get this version? I just got mine, shipped with 2.6, I'd rather flash it before installing it if it needs it. Without public access to 2.7, or a change description, I have no idea if this is worth pursuing or not.

Anyone wanna chime in?

Kenk2

iTrader: (7)

Install it and keep put the UTEC on 0 either by the remote switch or the dial on the UTEC. If all goes well I would worry about it or if you want email your vendor or TXS and ask them for the update..

mikead_99

iTrader: (5)

Well, I just shot turboxs an email regarding this. I asked them to send me a copy if it is worth making the change so hopefully I'll have some information about this shortly.