SMOG HELP: OBDII won't connect
#16
Evolving Member
Thread Starter
iTrader: (5)
Join Date: Feb 2011
Location: sacramento
Posts: 371
Likes: 0
Received 0 Likes
on
0 Posts
Yeah this has nothing to do with the tune being locked. A tune being locked would stop you from flashing not logging and definitely not pulling OBD. Since another tool is able to read the OBD it could just be a specific setting with the ROM that is causing an issue with the smog computer. Not sure how modded the car is, but what would be interesting would be to put a bone stock ROM on the car and see if it reads or not.
I could try putting a bone stock rom on the car. I tried reading my rom from my car yesterday and it wouldn't read it from ECUflash. It read it just fine from EVOscan but then when I tried to load the rom into ecuflash it didn't work again. So maybe that's a sign that it's locked?
#17
Evolved Member
iTrader: (2)
I know they meant low car battery, I just figured if the car battery was low none of the scanning tools would work (evoscan, OBD2 scanner).
Ref is my last resort... if I go I'm planning on putting the stock cat and airbox back on... I'd still have aftermarket injectors, cams, and cat-back exhaust though... so not sure if that would even work I've heard refs are *****
My car is bone stock on the outside, even the engine bay looks stock. black recirculated BOV (could replace with stock) and perrin intake filter (can replace with stock box).
Ref is my last resort... if I go I'm planning on putting the stock cat and airbox back on... I'd still have aftermarket injectors, cams, and cat-back exhaust though... so not sure if that would even work I've heard refs are *****
My car is bone stock on the outside, even the engine bay looks stock. black recirculated BOV (could replace with stock) and perrin intake filter (can replace with stock box).
Please save yourself a headache and stay away from a ref.. They actually know their ****, and they know EVos like to be modded
Last edited by BEKevo; Feb 28, 2013 at 10:19 PM.
#18
Evolved Member
iTrader: (22)
I could try putting a bone stock rom on the car. I tried reading my rom from my car yesterday and it wouldn't read it from ECUflash. It read it just fine from EVOscan but then when I tried to load the rom into ecuflash it didn't work again. So maybe that's a sign that it's locked?
#19
Evolving Member
Thread Starter
iTrader: (5)
Join Date: Feb 2011
Location: sacramento
Posts: 371
Likes: 0
Received 0 Likes
on
0 Posts
I'm able to flash the car though. I've changed maps a few times (turning on NLTS, then turning it off). I wouldn't be able to do that if the ecu was locked, right?
I haven't tried using ecuunlocker yet but I may try it
I haven't tried using ecuunlocker yet but I may try it
#22
Evolved Member
iTrader: (2)
If you can access "NLTS", you've accessed the ROM aka your ECU shouldn't be locked. Especially if you've changed the maps a couple times. I wouldn't mess with an Ecuunlocker, unless you didn't have to. Who previously tooned your car? TSComp? You should talk to him, if so.
#23
Evolving Member
iTrader: (3)
Yeah this has nothing to do with the tune being locked. A tune being locked would stop you from flashing not logging and definitely not pulling OBD. Since another tool is able to read the OBD it could just be a specific setting with the ROM that is causing an issue with the smog computer. Not sure how modded the car is, but what would be interesting would be to put a bone stock ROM on the car and see if it reads or not.
What voltage should be on pin 62 on the ECU? Is pin 62 the voltage source?
Thanks.
Last edited by golruss; Feb 18, 2018 at 06:43 PM.
#24
Evolved Member
iTrader: (12)
Anyone figure this out? I'm having the same issue at the emissions center with a USDM IX. Readiness monitors all pass and no cels, but the state inspector's scanner won't connect. Apparently the voltage is reading really low from the OBD to the scanner at around 2 volts instead of 12V+ which apparently means it's not communicating. I helped the inspector get it to start reading, but the calibration ID wasn't something they have in their database. The only adjustment to the stock ROM is the immobilizer is disabled as the immobilizer is unknown. I'm wondering if this is the issue. Anyone of the previous posters and OP have the immobilizer disabled? I also have the clutch safety switch disconnected, but don't believe that would cause an issue or is related.
Also, I've tried two different ECU's and two different ROM's 88590015 and 88950016.
Also, I've tried two different ECU's and two different ROM's 88590015 and 88950016.
#25
Evolving Member
iTrader: (3)
Anyone figure this out? I'm having the same issue at the emissions center with a USDM IX. Readiness monitors all pass and no cels, but the state inspector's scanner won't connect. Apparently the voltage is reading really low from the OBD to the scanner at around 2 volts instead of 12V+ which apparently means it's not communicating. I helped the inspector get it to start reading, but the calibration ID wasn't something they have in their database. The only adjustment to the stock ROM is the immobilizer is disabled as the immobilizer is unknown. I'm wondering if this is the issue. Anyone of the previous posters and OP have the immobilizer disabled? I also have the clutch safety switch disconnected, but don't believe that would cause an issue or is related.
Also, I've tried two different ECU's and two different ROM's 88590015 and 88950016.
Also, I've tried two different ECU's and two different ROM's 88590015 and 88950016.
The following users liked this post:
10isace (May 20, 2019)
#26
Evolved Member
iTrader: (12)
My problem was the baud rate in the bin file got changed for some reason during a dyno tuning session. Make sure that "BaudRate 1_OBD" is set to 15625. My immobilizer is not disabled. ROM 96534706. In my case I could read and edit the ROM but state computer could not connect to it. Hope this helps.
#28
Evolved Member
iTrader: (12)
My cheap scanner works flawlessly with correct Readiness Monitors passing and no CEL's. The Snap On scanners at the state inspector's wouldn't communicate. They have like 3 or 4 of them. Their emissions computer communicates though, but that PC looks ancient. Mitsubishi's scanner wouldn't connect just like the state inspectors. So my theory is the cheaper scanners are using the same parameters as EvoScan. EvoScan reads no problem and all Readiness Monitors are passing on stock ROM 88590015 and 88590016, but just won't communicate for the ref's needs. He said that's highly unusual. So I'm really crossing my fingers for the OBD Baud rate to fix it. Not sure how to read that on the scanner, unless I spring for a Snap On scanner (which I'm looking into).
Thanks for your help!!!
Thanks for your help!!!
#29
if you've tried multiple ECU'S with multiple ROMS, we could maybe eliminate those. How about wiring? trace back any modified wires, and check grounds all over?... i know nothing but just a thought... if the battery was relocated could there be insufficient voltage going to ECU? How are the pins looking for the OBD port? etc etc.
#30
Evolved Member
iTrader: (12)
if you've tried multiple ECU'S with multiple ROMS, we could maybe eliminate those. How about wiring? trace back any modified wires, and check grounds all over?... i know nothing but just a thought... if the battery was relocated could there be insufficient voltage going to ECU? How are the pins looking for the OBD port? etc etc.
Last edited by 10isace; May 27, 2019 at 09:22 PM.
Thread
Thread Starter
Forum
Replies
Last Post