pcmhacking.net

this is the current bin...
balancer timing mark setup seems to be okay i.e. at TDC etc.
static timing is set at 10 (9.84) deg. same as SR Angle and forced diag. mode.
fuel pressure around about 39psi (if reading on guage is accurate)

Log file (output3.xdl) follows...

Log file attached, is that better?

Justt wiring in the LC-1 now, and wideband O2 when the headers cool down. Hopefully it won't need to be activated, or whatever in the bin file.

I think I've git bi-directional comms, but don't know how to test if it works, or how to use write from TP V5.

When installing a wideband O2 sensor with Innovate LC-1 controller. Rather than install another bung in the header, easier to take out the existing O2 sensor and use that 'parking spot'...

$12P has a wideband input on D8, when that is connected does it still expect to see a narrowband O2 signal on D7?

well the o2 sensor is not really going lean anymore when you stand on it, but its also not moving as much as i would epect to see ....

anyways the wideband should remedy that issue .... you can run the car without the o2 sensor it will just put the engine light on cause its disconnected .....

Great, happy that it's not too lean that things might burn.
I'll install the WB O2 in the morning when I can see better what I'm doing.
I guess I could bridge D7 & D8, to avoid the CEL?

I expected more power than what's coming out at the moment.

I'll go test my bi-directional comms, and try to change a bin setting through TP RT.

Thanks to everyone for your assistance today

bridging those pins will not work!

as far as power, your along way off having it at its best, it will take alot of logs and tuning to get it right .... that tune you using is for a stock commodore v8, its not going to be close at all, and if anything will just be a good starting point to get it running and tune from there.

you need to get realtime tuning working aswell as the wideband then you'll be on your way!

The next post has the stock bin and definitions for TP, (asking for Road Speed calculation or VSS outputs).

Is there anything that I can get out of those files to bring my tuning base closer to the Camaro than to the Commodore VR?

I just noticed that the Road Speed is not correct. That would account for a lot of incorrect ECU responses.

What is the output of a VR Manual (BCLF) VSS (Vehicle Speed Sensor) in PPR (I guess that's Pulses Per Rotation of something)?

If I have that I'll compare it to my VSS output and adjust the calculation.

Be great if you also know the output of an '87 Camaro MAF TPI VSS... OR where I can find the calculation in the attached files.

it doesn't look like VSS settings are defined in the XDF....

my suggestion would be to get a gps or something and cruise along at a certain speed and adjust the vss in the tune till it matches the gps readings

the sensor in the VR is a 10 pulse per rev. from what ive read elsewhere the camaros usually use 4000 pulses per mile. so it would be about 2500 pulses per kilometer. try that and if the speed is still wrong do as holden202 suggested and fine tune the pulses per kilometer until the speed int he datalog matches reality. remembreing everyhting in the tune is set up for kph not mph