I just thought I'd share the news

What you'll find in this repack:

* Updated CEL Shiftlight Script + ASM (Thanks to Civic_TSI)

* Updated autoexec.txt (Thanks to Civic_TSI)

* Updated FTL / FTS script + asm now includes boost cut opion! To use just set a cut/resume you're comfortable with. One thing to note is set the cut/resume BELOW an RPM that your car can build that boost. If you're confused by that.. i dunno what to tell you.

---

A couple Honda-Tech members *ahem* ragged on Uberdata for not having a boostcut, well they can go eat their hat now

You can get the repack by following this link:

http://www.ecimulti.org/uberdata/

Thanks for all the help & support.

 

Good stuff...

<---- :: patiently awaits datalogging and RTP update ::

 

Looks good! Heres my question though my car has had issues that limit my testing abiltites and I am going to be retuning a friends car on the dyno on the 17th with uberdata and I am going to be pushing the limits of this software and I need to know how stable these new versions are because we cannot afford to waste dyno time. We hope to be making more power than anyone else has with this software on a b18a with internals. The last time we tuned the car(smaller turbo) we used version 1.3 and it went pretty decent, 273 on a mustang dyno and a maxed out turbo with pump gas. We will be returning with a rebuilt motor and a much larger turbo. I know I heard 1.6x has had problems initially and have not been able to test for myself so if theres any reason it may give us some trouble I will have to use 1.3 but on the other hand I love the new features and software. I am also getting a code 3(map sensor) when we shut down in the higher rpms with 1.3 that we never had before and its the same map we tuned and ran all last year. I think I will try this on his car tonight, but I only have a week or so to decide because once we are at the dyno there is no turning back. Is anyone using the newer versions with 3 bar? Are there still bugs or any concerns with 1.6x? Which would you rather put your trust in?

 

I suggest making your tune with 1.63, get it right. Then import into 1.65 and see what it does... which wont waste your time.

 

I just downloaded the program..but I honestly dont' know where i can set the boost cut....anybody know?

Khoi

 

sweet... already downloaded!

thanks for the heads up.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by GimpyAccord &raquo;</TD></TR><TR><TD CLASS="quote">I suggest making your tune with 1.63, get it right. Then import into 1.65 and see what it does... which wont waste your time.</TD></TR></TABLE>

Is 1.63 accepted as being pretty stable and bug free now? is anybody using the 3 bar with 1.6x yet? I know I heard several little things at first or cars that just were not running as well with 1.6x came out as they were with 1.2. I think it looks great and I am excited to try it on my project very shortly but unfortunately I have no first hand experience with anything after 1.2 and 1.3(premium version back then) and tuning on the dyno is not the time for me to be testing it and find problems or waste any time.


Modified by omahaturbocivic at 1:26 PM 3/8/2004

 

boost cut should be under the rev limits tab...make sure you open the .bin file for your car first

 

Are you asking where to set the boost cut, or are you asking what you should set the cut/resume RPMs at?

 

1.63 is pretty stable and accepted.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by GimpyAccord &raquo;</TD></TR><TR><TD CLASS="quote">1.63 is pretty stable and accepted.</TD></TR></TABLE>
Thats what I want to hear! Ill try 1.65 out tonight on his car and let him run that for now. If all goes well between now and the 17th thats what ill use when we dyno tune and crank the boost up, if something happens ill try 1.63 next otherwise its back to 1.3. Man this software has come a long way! i really hope 1.65 turns out to be pretty solid! If I did not have a cel right now for a messed up dizzy I would go burn and test some chips on my lunch hour.

 

why have we started posting uberdata news on here again?

And i believe markc is running uberdata with a 3bar map sensor.

 

because i wanted certain members to see that we have boostcut now, since they felt the need to slam dunk us on that re: VTC Civic's overboost failure. Anyway im done in this thread.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by GimpyAccord &raquo;</TD></TR><TR><TD CLASS="quote">1.63 is pretty stable and accepted.</TD></TR></TABLE>

I'll second that. When I dyno tuned my car we were using 1.63 and it ran flawlessly.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by DIY Turbo &raquo;</TD></TR><TR><TD CLASS="quote">why have we started posting uberdata news on here again?

And i believe markc is running uberdata with a 3bar map sensor.</TD></TR></TABLE>

Not with 3-bar yet, but very soon. Within the next few days.

I have it running VERY WELL with version 1.65 and 880cc injectors. I got my wideband on Friday and have been partial throttle tuning ever since. Runs smooth as butta now.

 

yay, hondata for sale. any takers?

 

you can make any version work with a 3 bar map sensor if you are ballsy enough to do all the voltage division. le tme tell you its very tricky dicky.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Sohc Driver &raquo;</TD></TR><TR><TD CLASS="quote">I just downloaded the program..but I honestly dont' know where i can set the boost cut....anybody know?

Khoi</TD></TR></TABLE>

bump

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by 94goldjungsr &raquo;</TD></TR><TR><TD CLASS="quote">you can make any version work with a 3 bar map sensor if you are ballsy enough to do all the voltage division. le tme tell you its very tricky dicky.</TD></TR></TABLE>

I originally thought about looking into that before there was any 3bar over a year ago, unforutnatley I dont think my friend will like paying 100+ an hour while I sit down and get confused over mathwork after every pull . Ive got the map all imported over to 1.65 and added a low boostcut and shiftlight to test so I will see how it runs tonight. If all goes well between now and next week ill use it on the dyno with some serious boost.

Now what I would like to see is if I could add more resolution to the map by moving the scalars (mainly rpm although map would be great too) around without potentially adding more problems. When I tuned with version 1.3 last year we got the a/f a flat 11.5 in the 5psi and 10psi range but around 15psi that the window got a bit larger and we had to settle for close enough, the operator said thats typical of many standalones but I think it would be nice to be able to get it a little bit tighter.

 

I am a little confused on how the boost cut works. Hopefully I can explain what I am thinking and someone can set me straight. Here goes:

boost controller set at 8 psi
boost cut set at 10 psi

- you are at the line and you launch
- the boost controller/wastegate hold steady at 8 psi
- shift to second
- boost is still steady at 8 psi
- shift third
- now lets say that you spike to 11 psi at 6500 rpm

For this situation, what would be a good boostcut and resume rpm? I would think that you would set the boostcut to 6100 and resume at 6000. Is this correct?

Also, what if you spike to 11 psi at 8000 rpm? Now you will have to wait for the engine to slow down to 6000, right?

Lastly, I am not a programmer, but is this based off of the FTS script, because if it is, doesn't the FTS script's 'rpm shift cut' supercede your rev limiter? Will the 'boostcut cut' supercede the rev limiter too? If so, then where would you set the boostcut?

I hope all this makes sense. Thanks in advance.

 

From what I understand you need to pick an rpm where it cannot build that amount of boost, so say if your turbo spools full boost at 4000 set it at 3800 or something lower. 6000 would be too high because if you spiked below 6000 nothing would happen I am guessing? Now what I am curious is if you spike boost will the engine be off untill it gets down to 3800 or will it resume when the boost goes below the value? I am guessing it will remain off because otherwise without a resume boost point a bit lower than the cut point it would stutter real fast as the boost moved in and out of the cut point. Either way its a nice safety feature. I guess I should find out pretty quick when I go test it here in a minute.

 

i did it on the street for about 3 hours before i got a car running well... definitely not somethign id do on the dyno. its mostly guess work until you figure out the algorithm

 

i guess a good way to test..is to just set the boost cut below what your boost setting is on the controller..and see how it works..

Khoi

 

Well I guess the only way to find out is to go testing. Here are the settings that I am going to try. I'll post back with the results.

boostcut cut : 6050
boostcut resume : 5935
boostcut psi : 4.9

 

That's about the right way to setup your boost cut. You have the rpms set the right distance apart. MarkC was working on setting the boost cut rpms automatically (current rpms minus a hundred or two), but untill then just set your rpms to a known safe level where boost is low (like 3-4000rpms) and set the boost cut pressure and be happy. Be warned: when you hit the cut, it's pretty harsh... You'll know if you've hit it.