Hello

Been new to this type of chiptuning, so it is possible that this problem have a simple solution, I don't know.....
Couldn't find the solution in the forum thow...

Recently, bought the autoprom...
Started to install the socket, burned the AZTY1406 bin on a M27c256B eprom that was lying here for a while.... just to have it as start position and as backup...
This way I can keep my 27sf512 chips to burn the results of the tuning....
Connected the autoprom to the ALDL and the laptop, running tunerpro RT.

Loaded the ADX file, and started logging.
The engine runned like it did before with the original memcal
Seems like nothing of the values in tunerpro is correct........
For example: VCC 0.40v
a lot of values constantly switching from not ready to ready....
in the dash RPM stil goes from 0 to 100 and back, no matter how I'm driving....
etc....

Somebody been there??

grtz, D

 

Is the ADX file for the $88 mask? Does the SES/CEL do a blink off at key-on, engine-off?

RBob.

 

Don't know if the ses-light blinks....
never mention it...
Engine runs, and files are for the 88

Grtz, D

 

the light is important because it could be in limp home mode and not even know it. they can run pretty well in some cases.

 

The SES light comes on when ACC on. Goes out after start the engine.

grtz, D

 

> For example: VCC 0.40v

It may be an ADX issue, I'm not sure what parameter is VCC. Also, the $88 mask sends chatter packets. TunerPro needs to send a data packet request at the right time to get the chatter to stop and the ECM to send data packets.

It may be that TunerPro is using the chatter packets thinking they are data packets.

RBob.

 

Any idea how to solve this?

 

I've never used TunerPro for data logging. But have written my own applications to data log before TunerPro existed. So I know what it takes to do so, not only for $88 but also for other masks.

Best I can do is to suggest those areas that can cause data logging issues.

RBob.