What I would really like to see is a fix to the software so that those of us above 2500 ft altitude don't constantly get the P1444 engine code.

It only happens on VQ35's with a UTEC and above 2500 ft (whether N/A, F/I, stock, or highly modified), but everytime someone has talked to someone from TurboXS, the reply is always something along the lines of "it can't be the UTEC's fault..."

Oh well.

 

I spoke with TXS today, and they reported back that no UTECs (Subaru, EVO, G/Z, etc) have the GUI interface! They are experiencing computer programmer related issues.....(sounds like they need to beat their geeks into submission!!!!)

 

The GUI interface , is this the Windows base programing ?

 

it is going to be windows based.....along with significant updates. I did get word that "closed loop boost control" will be updated to included target boost values, rather than the current "unit-less" values.

 

Wow. Jermaine showed me the Subie gui version of it at SEMA. It looked very cool.

I wonder if it was just a hollowed out gui front end with no real UTEC software behind it.

If they still don't have it completed on anything, they should probably just outsource the writing of the gui program to another software company that can get it done for them quickly.

It would be a reasonable investment.

 

Agree! That would have been the smartest move. Or...

http://www.jeffsoftware.com/software.php?product=UTI

^^ At least this would have been a good start.

 

I inquired via email to turboxs. They responded that the hardware was already present in the current units to support cam phasing, but the software did not yet support it. The reply also stated that the two-step/launch control was planned for inclusion in the software as well, but did not elaborate on any hardware implications.

This was back in the summer of 06.

 

I recall that being posted somewhere as well... Whatever...

 

with TXS being an australian company, the US division doesn't have a whole lot to do with the programming, updates, etc of the UTECs. They have to wait to see what comes out of Australia.

 

Im yet to buy a TXS but honestly. All the threads around it I see a whole bunch of false promises. Nothing seems to ever get done.

I think i'll be going FCON at this rate.

 

On my revup... I am able to set the rev limiter with the Open Loop Fueling Parameter turned on. The rev limit functionality is not available if the Open Loop Fueling Parameter is turned off.

 

you can set it, but it doesn't do anything.

 

TURBOSX ain't gonna make good on this anytime soon...


So I'm gonna post this again for all the SLOW people.

http://www.jeffsoftware.com/software.php?product=UTI

Working GUI, Logger, and Anaylizer can be found right here. ^^^

 

Do you have any idea why it doesn't work? I would like to know for my own curiosity.

 

EErrrrrrrr What did he say?

 

Do you use uti? Last summer I tried it and worked with him to get some of the 350z and UEGO functions working but I gave up. It is decent software but really made for the Suby's. It didn't really work well on the Z at that time (and the UEGO didn't work which I needed). Some nice features though.
I ended up using mps_uteclogger to tweak my tune (and get rid of misfire codes) which did not have as many features but it worked. I guess I should check the latest updates of both.

 

I'm also using the mps_uteclogger so I understand what you mean. My point was that the UTI would have been a good starting point for a decent programer. TurboSX has been promissing a GUI for almost a year (might have been longer) and what... Nothing. TurboSX has provided very little support for a product they seem to know very little about. Face it. The Hyperterminal interfact is crap. There are better user interfaces used on lesser systems and it shouldn't be that way.

 

The hyperterminal interface doesnt really bother me. It would be nice to have a GUI for logging/analysis and some auto-tuning methods. The uti features are very nice though.
TXS has a reputation for making promises for features and either not delivering or taking forever, at least around here. In the meantime it is still one of the better products for the Z (price/performance).

 

The UTI works vwery well. I have no issues on my G.

also, the hyperteminal interface is only an issue if you've never fiddled with the UTEC. A GUI would be nice and cute, but it is not needed. It would make analysis easy, but the essentials are all there.

the biggest thing the UTEC needs is better temp/atmospheric conditions corrections...that is far more important than a GUI.

 

What do you use for A/F logging with UTI -txs tuner??? I wanted to use the UEGO since I already had it working but I never did get a reliable working version of the sw.

I agree about the temp correction stuff. I'm still not sure if mine is setup right and I had to beg forever to get that excel spreadsheet.