pcmhacking.net

Hi all.

I'm struggling to get an 808 from a 5lt VN commodore to connect to tunerpro, it simply fails to find hardware. TX light flashes but no RX. So far I have tried the following:

Checked port settings are correct
Cable Echo/no echo
3 different NVRAMs with different $12p tunes on them
3 different ECUs all with the read write wire soldered on per instructions
2 different USB cables
I have deleted and re-loaded tunerpro

Only thing I have not replaced is the USB comms adaptor that is soldered to the ecu. I only have the one and first time using this one in particular. I have not had this issue with previous 808 connections.
The wiring from ECU to the pins of the USB adaptor bells out fine.

Any ideas what else I can try? Customers car I want to get rid of and the next batch of 808 Comms adaptors are 3-4 weeks away.

Cheers
Barbs

TX flashing means you have the right com port. ECM Adapter is unlikely to fail, but its possible there is a problem on the wire for receive. Look for physical damage or loose wire between the comms and the 808. Its possible if the customer had it they shorted something, but unlikely.

Most likely is there is something wrong with the file you are writing to the nvram or you writing it incorrectly. If you read it as a calibration by clicking down in tunerpro then its missing the operating system. If its not a stacked bin, and you are not stacking it, then it wont work even if you have the operating system in it. So write the stacked bin out the zip file and put that in the car, connect, (it should connect) then load the file you want to put on the car in tunerpro, and hit up to send the calibration in once the operating systems is in place and its communicating. Alternatively do a calibration write with oseflashtool once its running, another way to get the calibration on it. But no additional point since you want oseplugin working very next thing anyway.

Thanks Antus.
One thing I will try is loading a stacked bin. I only selected to load the 32kb $12p v8 bin that comes in the v112 folder. Hopefully this is my error and it sorts itself out from here. I'll let you know.

Barbs