1998 S70 Check Engine Light but No Code

ferocity02 · Post by **ferocity02** » 01 Nov 2015, 19:03

I disconnected the battery and unplugged the TCM and ECU overnight, Check Engine light is still present and turns on a few seconds after starting.

I ordered a VAG-COM cable from Amazon ($14 shipped) and downloaded demo version of VOL-FCR to ensure it works before I get a full version. I have an older 32-bit laptop with Windows XP that I will try to use. It works well on my BMW with K+DCAN cable with INPA software.

Post by **esl_97_850_T5** » 02 Nov 2015, 00:03

For your '98 S70 GLT...

Brick-Diag Free v0.0.6.6 also works with VAG-COM cable.

You'll probably find Vol-FCR Full (in conjunction with some form of OBDII emission diagnostic scanning) fine enough to avoid most trips to the dealer for code reading.

If not, Brick-Diag Free v0.0.6.6 (for $1-$2 and no extra hardware) may fill in some gaps. But it also requires some alternative source of OBDII emission diagnostic scanning.

And if those don't work, there's ways to use ELM327 devices (which are functionally equivalent to ELM327 v1.4 or higher) to read/clear DTCs for ECUs which Vol-FCR and Brick-Diag Free communicate with. Occasionally, those ELM327 solutions even work to connect to ECUs which Vol-FCR or Brick-Diag can not connect to. There's free Windows software and free Android software. Searching for "ElmBasic Android app on Google Play", "Elm 327 Terminal app", "Elm327 OBD Terminal" by Qbek, "volvo850diag" on Windows, or "kwpd3b0_interpreter", etc will get you headed in the right direction as far as the possible ELM327 solutions for solving 1998 S70 Check Engine Light but No Code problems. Also, in the https://www.matthewsvolvosite.com/forums ... 19#p382819 post, there's a paragraph on XantheFIN's "Volvo 850 OBD-II" Android app *BETA4* which can already read/interpret/clear '98 V70 AW 50-42 codes and which can already read OBDII emission diagnostic codes.

ferocity02 · Post by **ferocity02** » 02 Nov 2015, 11:42

Thanks for the advice! Will Brick-Diag Free be able to read special Volvo codes relating to the transmission, ABS, etc?

I currently use an ELM 327 bluetooth adapter and the Torque app on my phone, but it's only good for generic OBDII codes.

Post by **esl_97_850_T5** » 02 Nov 2015, 15:14

ferocity02,

Yes, Brick-Diag Free v0.0.6.6 will read (and clear) special Volvo codes relating to transmission, ABS, COMBI, SRS, etc. -- at least it has on my '97 850 T5. Also, the primary page documenting its functionality -- the Brick-Diag manual (requires registration/login; is in German, so it's best viewed with Google Chrome with auto-translation turned on) -- has a table at the bottom, which clearly shows which ECUs Brick-Diag Free v0.0.6.6 handles for the various Volvo models/years. I believe it can read/interpret/clear the codes for all the '98 S70/V70/XC70 ECUs which Vol-FCR Full can read/interpret/clear the codes. The primary thing it can not do that Vol-FCR Full can do is "Reset Service Light". That facility is disabled in Brick-Diag Free v0.0.6.6. Another thing to note is the Vol-FCR Full code descriptions are oftentimes more specific than the Brick-Diag Free English translations.

To my knowledge, the Torque app is good for generic OBDII codes, some vendor specific codes, but *not* for our '96-'98 Volvo 850/S70/V70/XC70 specific codes from auto transmission, ABS, COMBI, SRS, etc.

As far as your ELM327 Bluetooth adapter, it may or may not be able to read the '98 S70/V70 Volvo specific codes. It depends on if it has ELM327 v1.4 (or higher) functionality or not. The response from the ATI command is not useful in determining if the ELM327 has v1.4 functionality. Does your ELM327 Bluetooth respond to the "ATIIA 6E" command as "OK" or something like "ELM327 v1.5" or "ELM327 v2.1"?

If your ELM327 device responds to "ATIIA 6E" with the ELM327 version identification (like an ATI command does), then your ELM327 device is a partial-ELM327-compatible and can not be used to read the special Volvo '98 S70/V70 codes.

However, if your ELM327 device responds to "ATIIA 6E" with "OK", then we can do some further checks to figure out if it is fully ELM327 v1.4 compatible enough to talk to the auto transmission, ABS, COMBI, SRS, etc. ECUs in order to read/clear their special Volvo codes.

esl_97_850_T5

ferocity02 · Post by **ferocity02** » 02 Nov 2015, 15:45

I do not know how to send the EML327 module a command. I bought it about 4 years ago so I don't know if that helps.

I have a VAG-COM cable coming anyways which will probably be easier to setup with VOL-FCR than the bluetooth module.

Thanks again for the help!

Post by **esl_97_850_T5** » 02 Nov 2015, 20:20

Vol-FCR and Brick-Diag Free can use VAG/COM KKL cable, but **not** any ELM327 module.

You're welcome.

I'll leave it to others to answer any Vol-FCR and VAG-COM questions. There's plenty on this forum experienced with those tools.

ferocity02 · Post by **ferocity02** » 09 Nov 2015, 21:50

UPDATE:
I was able to clear the code!

First I bought a VAG-COM cable from Amazon: https://www.amazon.com/gp/product/B00871 ... ge_o01_s00

If the link breaks it was called: [New Version] Findway VAG-COM KKL 409.1 USB Interface diagnostic cable for AUDI & Volkswagen - OBD2 / OBDII

The cable came with drivers and awful directions, but it was easy enough to setup. The cable needs to be set on COM1 for Vol-FCR. If you plug it into a different USB port then it might change COM number, so make sure you use the same USB port on your computer if you have more than one.

Then I downloaded a Demo version of Vol-FCR from the developer's website. Even though the cable has a USB connection you need to use the serial version of Vol-FCR. I think this is because the cable has a builtin USB-serial converter? I used the demo version only to verify that the cable, software, and computer work. You can scan codes but it doesn't reveal what all of the codes mean, and it won't clear codes. My car has Motronic 4.4.

Then I found a full older version of Vol-FCR online. With this I can clear the codes. The program kept giving me an error: "Comms lost with Car, Time Out (TD)" after 10-15 seconds of inactivity. Luckily it didn't stop me from scanning and clearing codes. It would NOT reset the service light... annoying.

Codes:
EFI-666 DTC in transmission CM: I think this is a generic "Hey! The TCM has a code" code. This caused the check engine light too.
AT-124 Mode selector switch, signal too low: I think this happened because I turned on the ignition with the PNP/range switch unplugged.

I cleared both codes and went for a short drive... no issues at all, CEL stayed off

Kinda strange that the code didn't clear itself after several drives like engine faults codes typically do.

Post by **abscate** » 10 Nov 2015, 02:59

Some codes are cleared if they don't test out after a given number of drive cycles but many do not. They are sticky and need a dealer or scanner clear.

EFI-666. Scary code from the beast