Mike T. or ? Schip removal
Mike T. or ? Schip removal
Thread Starter
|
Senior Member
Joined: Mar 2001
Posts: 994
Likes: 0
From: Sparks, Nevada
Sorry for double.
I remove schip the recommended way..disconnect battery first.
If you dont do that way...what, if anything happens?
Recently had frastrating time...trb. code set...but got erased when i removed chip.
TIA.....OT
I remove schip the recommended way..disconnect battery first.
If you dont do that way...what, if anything happens?
Recently had frastrating time...trb. code set...but got erased when i removed chip.
TIA.....OT
Former Sponsor
Joined: Mar 1998
Posts: 13,385
Likes: 4
From: Virginia
Hi OT,
A number of things can happen, all of which is too detailed to get into here on the boards, that's a Tech Support issue that will have to be covered via phone.
Anytime you have a problem that sets a code of the type that will trigger a check engine light, if it's a problem that is real rather than just temporary and transitional in nature, then the check engine light will come right back after clearing the PCM. It might take a few miles, maybe 40-50 miles, but it will come back, and it won't be long, either.
I would not change our procedure to install or to remove the Superchip, the PCM needs to be disconnected first regardless of any codes, etc.
Give us a call to go over this in detail,
A number of things can happen, all of which is too detailed to get into here on the boards, that's a Tech Support issue that will have to be covered via phone.
Anytime you have a problem that sets a code of the type that will trigger a check engine light, if it's a problem that is real rather than just temporary and transitional in nature, then the check engine light will come right back after clearing the PCM. It might take a few miles, maybe 40-50 miles, but it will come back, and it won't be long, either.
I would not change our procedure to install or to remove the Superchip, the PCM needs to be disconnected first regardless of any codes, etc.
Give us a call to go over this in detail,
Thread Starter
|
Senior Member
Joined: Mar 2001
Posts: 994
Likes: 0
From: Sparks, Nevada
Hi MikeT. If you see this....
Tks. for reply. Trying to get clear on the PO605code and scan.
Simply put..yes or no?
Chip installed...PO605 error code shows on scan. OK Also at same time "check engine light" on..trb.code is set..will the scan also show the DTC codes..or just PO605?
In otherwords...do you have to remove the chip to read/scan trb. codes?
TIA....OT
Tks. for reply. Trying to get clear on the PO605code and scan.
Simply put..yes or no?
Chip installed...PO605 error code shows on scan. OK Also at same time "check engine light" on..trb.code is set..will the scan also show the DTC codes..or just PO605?
In otherwords...do you have to remove the chip to read/scan trb. codes?
TIA....OT
Former Sponsor
Joined: Mar 1998
Posts: 13,385
Likes: 4
From: Virginia
Hi OT,
Ahh, and there's the rub, as depending on exactly what hardware/software you use for the diagnostic scan, you may or may not be able to retrieve codes with a chip present on J3. For example, with Ford's WDS system you cannot communicate with the PCM with any performance chip attached to the J3 connector, as it will not pull up the vehicle's VIN#, so the WDS laptop just freezes. Many techs don't like WDS either, especially those who worked with SBDS and are into performance.
As long as whatever you are using to scan for codes can still communicate with the PCM, then sure, you can scan for codes *with* the chip installed. If your scan tool can communicate with the PCM with the chip attached, then you can retrieve any OBD-II codes, you just won't be able to get the extended manufacturer-specific data.
You will *always* have the P0605 code present anytime the chip is present, but that goes away after removing the chip. Also, a P0605 code from a chip being present at J3 will *not* cause a check engine light.
I hope that helps!
Ahh, and there's the rub, as depending on exactly what hardware/software you use for the diagnostic scan, you may or may not be able to retrieve codes with a chip present on J3. For example, with Ford's WDS system you cannot communicate with the PCM with any performance chip attached to the J3 connector, as it will not pull up the vehicle's VIN#, so the WDS laptop just freezes. Many techs don't like WDS either, especially those who worked with SBDS and are into performance.
As long as whatever you are using to scan for codes can still communicate with the PCM, then sure, you can scan for codes *with* the chip installed. If your scan tool can communicate with the PCM with the chip attached, then you can retrieve any OBD-II codes, you just won't be able to get the extended manufacturer-specific data.
You will *always* have the P0605 code present anytime the chip is present, but that goes away after removing the chip. Also, a P0605 code from a chip being present at J3 will *not* cause a check engine light.
I hope that helps!