pcmhacking.net

pretty rich lol

Tunerpro can get unstable with invalid sizes in the xdf or adx. Its written in c so it doesnt always crash straight away... Just sometimes later. I'd recommend testing with stock xdf and adx then gradually reapply any customisations to do with packet sizes and offsets.

The1 wrote:pretty rich lol

It is weird, the car did some really weird stuff when I put a new battery in it, was sucking gas something cronic, seems to have settled down. Non of the MAF or injector tables have been touched so there really is no reason for it to throw such wild numbers unless the O2 sensors are kaput, they do swing as per normal when it's up to temp and plenty of cross counts?

I'll run a new log on the weekend when I have the car with the new ADX, I am fairly certain however that it's always done it.

antus wrote:Tunerpro can get unstable with invalid sizes in the xdf or adx. Its written in c so it doesnt always crash straight away... Just sometimes later. I'd recommend testing with stock xdf and adx then gradually reapply any customisations to do with packet sizes and offsets.

Cheers, something to check out.

It doesn't work for my vt 1999 model v6 iim running the ALDLDroid app help please

What model USB interface are you using?
That has an effect. I've seen cheap one's current later model PCM's when writing ne BIN's etc.
Logging could be similair.

when i flash the vy enhanced code do i have to disable vats or will it be fine

disable vats, unless you have a tech2 to relink the pcm and bcm. This is the case for VX VY Flash PCM Models. For all VT VX VY Models if the PCM is changed it also applies, VS Models arn't linked.

updates VS N/A and L67 xdf's fixed Decel Tables.

Added IAC Tables to VY S/C xdf

updated VX V6 Flash XDF, added some items. Fixed a few comments in the VY V6 S/C ADX

just put vx enhanced in the wagon off for a drive and log or 3