• Upcoming Events

    No upcoming events found

Archived

This topic is now archived and is closed to further replies.

  • 0

Vol-Fcr And Obd2 Usb-Cable Problem

Question

Posted

Hi Forum Members,

I am new to this forum, this is my first post. I found a topic here, but is unfortunately closed, so i decided to open a new one to get ideas (hopefully) to my problem.

I have a 1996 Volvo 850 with speedometer problems (sometimes it stops showing actual speed while driving - then odometer also stops).

I was told that it might be an ABS related problem. So I purchased an USB KKL 409.1 OBD2 cable (this) from ebay. I downloaded VOL-FCR SERIAL demo (also tried usb version - doesnt work at all). The cable's virtual port was set to com1 as suggested in the above linked topic.

The software was able to establish a connection to the car, it was able to query model and software IDs but then it failed reading trouble codes saying 'comms lost with car, null time out or message error'.. post-31746-124549049866_thumb.jpg

I dont know what might be the problem, I would be very thankful if someone could help me out with a good advice!

0

Share this post


Link to post
Share on other sites

36 answers to this question

Posted

Get a cheap-o ebay USB vagcom cable and be done with it. don't bother with serial...

0

Share this post


Link to post
Share on other sites

Posted

I did just this. The cable came today and worked fine. I cleared the SRS code that I set when I replaced to odometer gear and started the car while the passenger airbag was unhooked.

Get a cheap-o ebay USB vagcom cable and be done with it. don't bother with serial...

0

Share this post


Link to post
Share on other sites

Posted

I have a KKL VAG COM for 409.1 cable and VOL-FCR USB version. I am able to read engine,abs,srs and lock/immobilizer codes. I cannot however reset the service light or access the climate control system (the reason I bought the cable. I receive an error.

Anyone have any luck with these systems and what did you do?

0

Share this post


Link to post
Share on other sites

Posted

Fill out your sig so we know what car you are talking about.

0

Share this post


Link to post
Share on other sites

Posted

Sorry about that, done and it is a 1998 V70 base wagon.

0

Share this post


Link to post
Share on other sites

Posted

Cmercon:

What operating system and what version of the Vol-Fcr software are you using?

This seemed to work, but there was no luck communicating with "immobilizer" and "instruments": Plug in the USB-type cable, let Windows 7 "automatically" find the drivers, set port to com1, other advanced port settings set to default, connect cable to OBD-ii port, key at position II, then attempt communication with a module via Vol-FCR.

If you can see the correct "immobilizer" and "(combined)instruments" output, what are your settings?

0

Share this post


Link to post
Share on other sites

Posted

If using a VAG-COM 409.1 OBDII to RS232 cable make sure that the port is set to COM1.

If using a VAG-COM 409.1 OBDII to USB cable, it is necessary to install the appropriate drivers. Most of these cables use the same FTDI chip and the drivers can be located on this page (link).

NOTE

After the VCP drivers are installed and the cable connected, make sure the port is set up correctly in Control Panel - Device Manager - (look under Com Ports).

Under Properties - Port Settings set the following:

Bits per second: 9600

Data Bits 8

Parity None

Stop Bits 1

Flow Control None

Then Under Port Settings - Advanced set the following:

COM Port number: COM1

Receive (Bytes) 64

Transmit (Bytes 64

Latency Timer (msec) 3

Minimum Read timeout 100

Minimum Write Time out 100

0

Share this post


Link to post
Share on other sites

Posted

SlapShot -

Thanks. Those settings were tried, but still no luck. The VCP (virtual com port) drivers are current.

For the immobilizer there is a time-out error. It looks like communication never happens.

For instruments, "comms message" shows comms is established, and for a couple of seconds "comms status" shows "ok".

Shortly afterward (whether or not Read DTC is selected), module ID shows "invalid data".

The cable is a USB K-K-L 409 Vag-Com. Does a "K-L" type cable work where "K-K-L" would not?

0

Share this post


Link to post
Share on other sites

Posted

Try turning the baud rate lower than 9600 and the latency timer less than 3. I have one of those cheap china blue cables from eBay and everything works. Not saying my settings are ideal but they work on all the cars I've tried it on. Maybe you've got a wonky wiring issue or ground?

0

Share this post


Link to post
Share on other sites

Posted

Does everything work for you with both Windows 7 and XP? Does your cable work with both 1.3 and 1.7 versions of Vol-FCR?

I'm going to try the settings you suggested.

version 1.7 (not 1.3) does show the "instruments" module - same port settings. Still nothing for the immobilizer, though.

0

Share this post


Link to post
Share on other sites

Posted

Does everything work for you with both Windows 7 and XP? Does your cable work with both 1.3 and 1.7 versions of Vol-FCR?

I'm going to try the settings you suggested.

version 1.7 (not 1.3) does show the "instruments" module - same port settings. Still nothing for the immobilizer, though.

Works fine with Windows 7 (32 or 64 bit) and Windows XP. I'm using Vol-FCR 1.3.06...which can be "acquired" online. Where did you find 1.7 / is it a demo?

0

Share this post


Link to post
Share on other sites

Posted

Yep...the 1.7 I have is the demo version. I'm using Windows 7 64 bit (not with XP mode).

For accessing the power seat modules and instruments sometimes it takes several tries to get communications established.

I tried those settings...still no dice even with antivirus off. But it looks like for the "instruments" module, v1.3 software might be the problem (since the demo 1.7 at least shows comms where 1.3 shows invalid data).

Maybe the cable is part of the problem. I had codes read and remotes programmed at one time at a dealership. They didn't mention anything about inaccessible modules.

There is communication with the "lock and alarm" module.

0

Share this post


Link to post
Share on other sites

Posted

Gonna zombie this thread, hopefully you guys can help. Car is a 96 850 T5 Wagon. Using my laptop (Win 7) and my Vag cable along with Vol Fcr I can't read the ECU. I CAN read the trans, instruments and a few other things. Just not the Mot 4.4. The fact I can read the other things makes me think its pbviously not the cable or fuse issues. Checked fuses anyway. Also tried changing Com settings like above. It will not establish Comms with the Mot 4.4... Only the other things..

Ideas? I have a CEL that I need gone/fixed asap so I can pass inspection..

0

Share this post


Link to post
Share on other sites

Posted

Use a difference scanner then... If you still can't pull codes then you have a tranny code stored on the ECU that can't clear unless you clear the TCU..

0

Share this post


Link to post
Share on other sites

Posted

The 1996 850 Turbo uses M4.3 for the stock/factory Engine Control Unit. Unless you are running an ARD tune that is converted to M4.4, or at some point someone dropped in a M4.4 ecu from a S,V,C, or XC 70 you will have Bosch Motronic 4.3 ECU, which is not readable with VOL-FCR.

0

Share this post


Link to post
Share on other sites