Notices
General Engine Management / Tuning Forum Discuss general EMS tuning concepts that do not pertain to a specfic brand or product.

No communication with obd2

Thread Tools
 
Search this Thread
 
Old May 6, 2014 | 12:00 PM
  #1  
black_out's Avatar
Thread Starter
Evolving Member
15 Year Member
Liked
 
Joined: Oct 2009
Posts: 139
Likes: 13
From: Casa Grande, AZ
No communication with obd2

I was in the middle of a flash when my car battery died at 97% (I know, should've been paying attention). I tried to reflash and ecuflash confirmed a successful reflash, however, the car would backfire through the intake manifold while cranking and fail to start. I tried connecting with evoscan which was working perfectly fine before the flash, and I receive a "no response from ecu" while checking for DTC's and it will continue to auto-reconnect over and over again if I try datalogging.


I assumed I fried the PCM and found a local known good PCM to try, I installed and flashed my ROM over, now the car won't even try to start, I've verified I have no spark and it seems to have no injector pulse, although I can't 100% verify this. If I try to connect with evoscan I get the exact same readings. I've tried both my 1.3u cable and 2.0 to rule out a cable issue (both worked fine before the flash), and have also tried a known working hand held obd2 scanner and received a "no communication" error.


I have 12v at the OBD port, I have ground, and I have continuity on the communication pin. I've also tried uninstalling and reinstalling evoscan and ecuflash from a hard wipe to verify a possible driver issue and still nothing. Battery level is more than sufficient. I can read/write all day long without issue, but no obd communication and no start- seems like a PCM issue correct? Although we've already verified my known good PCM will flash/start just fine in another evo. What am I missing here?
Reply
Old May 6, 2014 | 12:09 PM
  #2  
black_out's Avatar
Thread Starter
Evolving Member
15 Year Member
Liked
 
Joined: Oct 2009
Posts: 139
Likes: 13
From: Casa Grande, AZ
I was reading something about v2.9 and not having the correct setup in Map tracer, upon clicking on map tracer this is the error I get. Not sure if it's relatable as I'm pretty sure it said this before hand, but maybe this has some insight?

I should also mention the car is on v7 SD and I've tried both v2.7 and 2.9 evoscan as well.
Attached Thumbnails No communication with obd2-evoscan.jpg  
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
Bmocc
ECU Flash
1
Feb 3, 2017 10:50 PM
Dbisk87
ECU Flash
3
May 16, 2014 05:46 PM
Leftbehind126
ECU Flash
10
Jan 1, 2013 01:49 AM
neonglh
ECU Flash
1
Jun 25, 2011 09:26 AM
Malmoe_Sweden
ECU Flash
2
Sep 17, 2008 11:23 AM




All times are GMT -7. The time now is 02:15 AM.