STI Forum  |  Shop  |  Sponsors  |  Advertise Rules  |  FAQ  |  Members List  |  Calendar
IWSTI.com: Subaru STI Forum
 
Home  |  Register  |  Today's Posts  |  Go Premium Mark Forums Read Create a Member Journal  |  Vendor Deals  |  Member Classifieds

New IWSTI license plate promotion!PLEASE VOTE/RESPOND TO THIS THREAD!Special Order 2008+ IWSTI Gear!

Welcome to IWSTI.com, the largest STI specific forum on the internet, where you can interact with other STI enthusiasts, create a member journal, and receive answers to your questions. Registration is fast, simple and absolutely free, so please register today to start enjoying IWSTI membership privileges! Problem registering? Please contact support.
Go Back   IWSTI.com: Subaru STI Forum > STi Technical Discussion > ECU Tuning & Performance Electronics


Reply
 
Thread Tools
Old 06-12-2008, 06:14 AM   #1
Authorized Vendor
 
Fav Mod: Innovative Tuning
Location: Buffalo, NY
Posts: 216
Join Date: Jan 2006
Trader Rating: (0)
Default Hydra 2.6 Fixes/Comments

I wanted to share a couple things I've experienced with the new 2.6 Hydra on a customer's STi, some good and some bad (but avoidable).

Because we had to figure the problems out on our own, I thought I'd share the fixes and save you guys the trouble!

1) The dwell settings on the base files I was sent were actually high enough that the coils were being overcharged, causing misfires at high RPM at full boost on a GT35R. This may not cause misfires on setups flowing less air, but since it's an overcharging problem rather than an undercharging problem, I recommend setting the coil dwell time to safer levels even if you don't experience misfires. Now that the dwell has been lowered the car pulls all the way out cleanly and I was able to raise the boost as well.

2) Total map corruption on the Hydra box and file on my laptop with no warning or error messages from the software, leaving the car stuck on the side of the road. Make sure you change the preferences so non critical messages and status messages are displayed. You would think that map file incompatibility (said the map file didn't match the software version), file error, and firmware compatibility errors would be critical messages, but they didn't display until these preferences were changed.

3) I'm 99% sure the map corruption was a result of the FIFO buffer serial port settings rather than a Hydra issue. As per instructions for Autronic, Motec, and others, but not Hydra, I disabled the FIFO buffer and haven't had a communication issue cause map corruption since then. I'm using a real serial port (no USB to serial converter). The FIFO buffer isn't mentioned anywhere in the Hydra manual at this time, but maybe they'll consider adding a note about it after seeing this.

Hydra 2.6 does have a com stats feature which allowed me to diagnose this issue. With the FIFO buffer on (default for Windows) the status reading would hit 40% immediately and over time (very slowly), go up to 98% (maybe it would go higher, but I didn't want to wait any longer). With the FIFO buffer on, it hit 98% immediately and counted up from there slowly.

I did not have to do this on Hydra 2.5, perhaps since the data stream was smaller.

So there you have it...change the coil dwell, allow all software messages, and check your com stats and disable the FIFO buffer if you don't immediately get around 98% on the status monitor.



On the good side:

I like the new 3d rpm/tps tables for launch control and flat shifting fuel and ignition cut cycles. While that level of control isn't necessary for many people, it's nice to have it available and at least on the flat shifting side that flexibility can be very effective if set up properly.

The "new" features like add/subtract and multiply/divide by floating point value make tuning take less than half the time it did on Hydra 2.5 so that's a big step in the right direction towards what the other standalones have offered for years.

The layout of the tables makes a lot more sense. Rather than random functions being under menus designated by numbers, they're organized under menus with real names like "2D Fuel Trims" rather than "Control 1".

Being able to select which parameters to log and having a realtime graph and buffer setup are also big steps forward for Hydra as is not having to shut the car off, back on, and load the whole map file to the ECU to make changes permanent.

The 2d fuel cut lower limit is a nice little addition too.

I'll report back with more info as I have it.

-Mike


This ad is not endorsed by this member. Please register or login to hide this ad.
Inn-Tune is offline   Reply With Quote
Old 06-14-2008, 06:44 AM   #2
Authorized Vendor
 
Fav Mod: Innovative Tuning
Location: Buffalo, NY
Posts: 216
Join Date: Jan 2006
Trader Rating: (0)
Default Re: Hydra 2.6 Fixes/Comments

I had a little issue with flat shifting. I went through the whole circuit and was scratching my head because the clutch switch wasn't getting switched 12+ from the Hydra 2.6. If I hadn't tested it and just went out and drove the car it would have worked, but I like to test our installs before driving off.

Here's why...Under the "Map Group" menu go to "Settings 1". Then go to "user logic" via the pull-down or arrows. "User 1" is set so the output to the clutch switch has no power until you're over 3500 rpm. If you're sitting at idle or with the key on and the engine not running, don't think your wiring is incorrect if the circuit isn't working. Change this setting to 50 rpm, get the car idling, and re-test. You probably have it hooked up just fine. Then if you want to set the User 1 RPM back up higher so you don't hear the relay click while engaging/disengaging the clutch while at idle, and to use the relay less, go right ahead.

As long as this RPM setting is lower than the RPM you start cutting cycles for launch control or flat shifting, it won't keep them from working.

-Mike

Last edited by Inn-Tune : 06-14-2008 at 06:54 AM.
Inn-Tune is offline   Reply With Quote
Old 06-17-2008, 01:50 PM   #3
Authorized Vendor
 
Car: 02 WRX 675whp 584ftt
Fav Mod: 8 1600cc injectors
Location: Winchester VA
Posts: 480
Join Date: Jan 2006
Trader Rating: (0)
Default Re: Hydra 2.6 Fixes/Comments

Mike,

Hey we are still having issues with the serial communications.

Even with the FIFO settings off...This only happens when the car is still running and I make more then 4 or 5 changes at a time...

Just gets old when you have to wait forever for the file to load back to the ECU. The verify feature was a nice addition....that will atleast tell you if the Laptop and ECU files are jiving...and pretty quickly.

Also, with the big cams we are using in an 06STi I found that the Mapping for the AVCS is way off...not only is it off at the top but down low too...Found this to be true on a car with stock cams today also.

I believe something is still wrong with the CTS calibration...since the fans turn on before thermostat opens. The temp at the sensor, read by an infared gun, shows 145F and the Hydra reads 185F. The gauge cluster reads low when the HYDRA reads to its up to temp also...I was advised by Hydra to replace the sensor which we did and still no fix.

BTW! When I reported this problem to HYDRA we re-used the customers UTEC to see if it did it, that answer was a big no. So today I threw in the BETA AEM EMS and the problem disappeared!

It would be really nice if you could build your own dashboard templates for the tuning of the HYDRA...It takes a few extra hours of navigation to find the basics when you start to tune the new 2.6V...I had to make a cheat sheet!

Regardless...we have this car tuned very well so far on the 2.6V HYDRA. So far the car has made 400+whp and 385+fttq at 16psi on pump gas. Going to take the car home tonite for some street tuning. Hopefully we will have this car back on the dyno tommorrow using C16 racefuel...see if we can break 500whp at 20psi... (GT35R with a 1.06AR exhaust housing and one of our built setups)

Howard


This ad is not endorsed by this member. Please register or login to hide this ad.

Last edited by AR Fab : 06-17-2008 at 01:59 PM. Reason: clarifications before I get flamed.. :)
AR Fab is offline   Reply With Quote
 
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


All times are GMT -8. The time now is 03:30 PM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Designed & Powered by Domain Architect