pcmhacking.net

nice job six good to see you having a play its nice code to use thats for sure

Good to hear the flashtool is working now, will update the thread with the program link.

Well, I tried the '165 and $12P in my car tonight, results were....


Unsuccessful. I did get a very brief run out of it. I need to go through the XDF and see what I need to adjust to get it to run. I know there were a couple issues with pin compatibility of the adapter harness, mostly related to injector pin out and grounds. I'll move them on the adapter to making switching back and forth a little easier. I quickly moved them in the harness in the car to do the testing.

The one thing that has been odd, even on the bench is that desired idle speed is usually 20,000+ RPM.

Thats definately not normal. Im not sure what would cause that, though. Are you sending the ALDL through your chip emulator, and could that be changing baud rate to 9600 or something like that? Perhaps we should discuss in the thread about your car instead of here.

We can move the convo, but what ever is discovered might help someone else if they have the same issue...

I'm using an Ostrich 2.0 and Extreme ALDL for logging. Logging is working ok, through pin A8 of the '165.

RS232 echo is set in the ADX.

Well, I've been over the adapter harness and everything is pinned correctly.

The only issues I had earlier were one of the injector outputs swapped at the harness end. The '7749 has 3 injector outputs that are used, a pair are from one injector driver, the third is from the second injector driver. Depending on whether you want to use one or both injector drivers is what determines which pins are used. The other pin problem was also at the harness end, and was a ground for the injector driver, so I've actually connected both injector driver grounds together at the harness end, that will feed the '165 regardless of how I have the herness pinned (one injector driver or two, one ground changes positions).

I just downloaded V110.

After some playing I was able to get one of the V110 ADXs (OSE_$12P_v1.09_1BAR_TP5-fixed_for_tracing) to connect to a V110 bin (OSE_$12P_APNX_V6). I did have to add the RS232 echo.

Using V110 on the bench (too late to try in the car), desired idle speed looks proper at a believable 994 RPM. lol

Software and hardware mode and MEMCAL selection and detection are proper, both at 6 cyl. I had noticed with v111, after testing in car, the software and hardware selection and detections would change, at random, while they were stable when I last bench tested v111.


--==EDIT==--

just tested V111 again, and have a proper looking desired idle RPM, now at 1075. I've probably used a different ADX than I was earlier, though that shouldn't really make a difference.

I reckon you still have some kind of comms issue. V111 is very widely used, and I have not heard of the trouble you are having before. Is it possible that your copy of V111 has been corrupted somehow? I am absolutely certain that it outputs the correct idle rpm and the supplied adx read it fine. Its quite puzzling that v110 will work and v111 wont for you.

I was editing my previous post when you posted.

I seem to have v111 working now. So I will try it again in the car tomorrow.

Desired idle speed changes properly with coolant temp.

The only issue I still have is no change on the O2 sensor display. I haven't tested the WBO2 input yet...

you will notice it will say 8 cylinder in the adx until you start the car and it will change to 6 cylinder thats normal