Life after UTEC, couple questions

[mad_VIII]

Hello Folks,

So I am a recent UTEC convert. I picked up a pre-owned v2 box with P&P harness a couple weeks ago. Got everything installed last week including the GM3bar and TunaPro analogue output using the plx profile. I'm using ECUFlash for the major adjustments after tweaking things in ECU+. Things are going great so far, with the bad @ss data logging I have managed to make some very effective revisions to my timing maps.

Question about timing logging:
So far, the only thing I miss is the UTEC's timing logging... it had resolution to the 10ths so you woud see 14.2 14.4 14.6 etc rather than 14 14 15. So is there anyway to improve the resolution in the timing logging Tom? Or is this a limitation of the way the stock ecu reports the data?

Question about palm logging:
I'm waiting on my palm M505 serial cable so I can start using that for logging and in car adjustment/monitoring. What is the limit on the log size with a plam device? I have a 128 meg sd card in the 505, but I'm not sure if I can tell ecu+ plam to log to the sd card?

[tlcoll1]

mad_VIII -

Timing logging is currently 1 degree only. I might make that more accurate in the future (the firmware keeps way more accurate numbers internally), but it's currently hardwired to integer degrees. BTW, the crank sensor isn't really precise enough to give you better than about a degree accuracy anyway. The UTEC numbers may show better than a degree, but are almost certainly bogus.

On the Palm, log size is limited by memory. Files are about 6 minutes per megabyte. I'm not sure, off the top of my head, how to get the Palm to use the SD card for storage, but I'm not sure you really care. Typical logs are 30 seconds or something for a WOT run - you don't usually drive around just logging for long periods of time.

Tom

[Mach V Dan]

Originally Posted by mad_VIII

Question about timing logging:
So far, the only thing I miss is the UTEC's timing logging... it had resolution to the 10ths so you woud see 14.2 14.4 14.6 etc rather than 14 14 15.

I think I asked TurboXS about this once long ago. If I remember right, it really is reporting 1 degree increments, but the datalogging frequency doesn't necessarily overlap the timing changes. So if you have 500ms on 16 degrees and 100ms on 17 degrees, and the datalogging interval is 600ms, that segment of the log will show 16.2 or whatever. (These numbers are totally fake; I'm just trying to illustrate my point.)

So basically it's as Tom said.

--Dan
Mach V

[MalibuJack]

You'll find that to be pretty true on most...

The nature of the hardware we have to work with makes it difficult to really give sub-degree values and expect them to be accurately honored..

In reality, it may be great to talk about resolutions greater than .5 of a degree, but I doubt it will be really of much use unless your looking to get that extra 1 HP out of the engine..