pcmhacking.net

can you log it with torque on android and work back from there?

antus wrote:can you log it with torque on android and work back from there?

I tried using torque and forscan, neither found anything.

That’s what made me worry that I’m not wired up correctly, but now had 4 wiring diagrams sent which are all the same and match what iv done. So I’m a bit stumped!

*Edit
If I put the PWM wires the other way, an ELM throws a bus error warning and the MDI throws writing errors so the PWM wires are certainly the correct direction on the EECV ecus.

Maybe you are missing some power wires.

On some bosch crap ecms, you need to wire power relay. It feeds signal to relay and add more power lines to ecm. Maybe that will be the case.

kur4o wrote:Maybe you are missing some power wires.

On some bosch crap ecms, you need to wire power relay. It feeds signal to relay and add more power lines to ecm. Maybe that will be the case.

It could only be power related, but after having 4 people provide wiring diagrams, they all match. I have also quadruple checked the pinout, and probed the plug pins onto the circuit board plug connections to verify the correct pins also.

Certainly a bit stumped!!

I've used bench setup & can read & write EEC with 104 pin plug with 13, 15, 16, 55, 71, 76, 97 & 102

What are you reading with and can you do Immo off?

with kess, yeah pretty sure it read/writes the immo section(saves having to use those J3 chips!

VX L67 Getrag wrote:I've used bench setup & can read & write EEC with 104 pin plug with 13, 15, 16, 55, 71, 76, 97 & 102

Another confirmation of the pinout I am using. I must be going mad!

Is this any different? When I was doing testing, it took all of this for me to make it work everytime. FEPS was 18v. Pay no attention to the wire colors, that is what I used on my universal 10 way at the time.

In-Tech, yep, thats another confirmation of pinout. The only thing that varies between diagrams is how many ground points are being used.

But we made progress!
After a bit of guidance with sending correct diagnostic commands and protocol headers ect.. we finally have communication!

Something that is important though, is I needed to power the ECU Battery power first, and then attach the ignition wires otherwise the ECU did not seem to recognize it was actually on. After doing that, and correct diagnostic requests... we finally got a response

I know this should not be that much of an accomplishment, but anything that takes close to a week of trial/error and research to complete is worthwhile to me.

Next up is running reliability tests with the current circuit at 41.6kpbs to send/receive hundreds of thousands of frames over the weekend. I will be able to verify if any frames fail or are missed by using secondary tools to monitor.
After that, its moving to testing out highspeed at 83.2kpbs.