Jump to content
Volvospeed Forums

Vol-Fcr And Obd2 Usb-Cable Problem


akka

Recommended Posts

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!

Link to comment
Share on other sites

  • Replies 36
  • Created
  • Last Reply

I made the serial version of the program work but I bought an actual serial interface cable to do it. I am at my cabin at the moment and I can't give you the specific number of the cable. There are a couple of versions of USB to serial converters that have been said to work but I have no specifics. The big problem is that most laptops don't have a serial connector anymore - I knew there was a reason I kept the old IBM think pad around even with the dead batteries. Rumor has it that there is a cracked full functioning version of the program on bit torrent.

I will be back in the city on Sunday and if no one else has given you the specifics on the cable I will post back the numbers on the one that worked for me.

...Lee

Link to comment
Share on other sites

FCR only works on 96-98 volvos.

The serial cable works best

You need to Crack the software, they only include a demo and it says lost communication when you try to read or erase dtc..

email me @ justanothervolvo@gmail.com

I can help you out ; )

As for your speedometer, possibly ignition switch, Try gently turning the key back and forth when the can is running.

Possibly ignition switch, when the car is runnig gently wiggle key back and forth and see if that helps.

Link to comment
Share on other sites

if you are able to adjust your virtual comm port settings, slow it down, less then 9600. Try also adjusting UART settings. If that's an acutal screen shot, you got the usb cable to work, as it can atleast qury the controller. However, you'll need the crack for the software.

Link to comment
Share on other sites

If you are using the USB cable, then most likely you are not running on the COM1 port. COM1 is typically reserved for the serial port. Try the other COM ports. You can also look in your Device Manager to find exactly which port it's running on.

Link to comment
Share on other sites

Thank you guys for the answers!

Actually Jordan was right, playing with the COM port settings (setting it less then 9600) helped, now i am able to read DTCs.

The cable and software i used were: obd2 kkl usb cable with ft232b chip inside from ebay, vol-fcr 1.3.6 serial version and the driver from http://www.ftdichip.com/Drivers/VCP.htm

If you guys could share with me the difference between the 1.3.6 and the newer software versions (what has the newer more?) i would be thankful!

Link to comment
Share on other sites

You can search for it on ebay and usually purchase it with a cable. I'm sure if you really search you can find it other places... Below is the support info from the program.... On their website is a link that will take you to a chart that shows the Volvo models and what functions are available to each model. Its a decent program, but worth no more then $30.00. Becareful on cars with Motronic 4.3- it won't pull OBDII or diag. codes... It tells you how to use the OBDII port to pull blink codes eg(2-1-1)

Vol-FCR, Fault Code Reader for Volvo Cars. Version Beta 1.3.06

Copyright cr-diagnostics © 2002, 2003.

Supplied by:

ilexa

PO Box 111

Truro

Cornwall

United Kingdom

TR2 4YF www.onboarddiagnostics.co.uk/volfcr

For technical support:

Tel 0870 7543 827 Mon-Fri 09:00-18:00 (GMT) or Fax 0870 7543 829 Anytime.

e-mail volfcr@onboarddiagnostics.co.uk

This program is designed to read & reset fault codes on Volvo cars.

The program has no connection with the Volvo Car Corporation.

The program will only work on Comm Port 1.

Some S/V 40 engine functions have not been implemented and are disabled.

No liability can be accepted for use of the program or the information presented.

You may wish to print information from the program, the easiest way to do this is to press the Alt + Print Screen keys to take a snap shot of the screen then press 'Go Back' to stop comms and finally paste the screen into a program such as Wordpad, save the result and print / e-mail as required.

-Scroll Down for more-

On ‘96/’97 850 cars with the 16 way ‘OBDII’ socket, and some other models, some of the control modules use ‘flash’ codes, this program is not designed to work with these modules.

The controls for these have been coloured yellow in the program.

THE USE OF THE FOLLOWING INFORMATION IS ENTIRELY AT THE USERS RISK

To retrieve the flash codes the following procedure can be adopted:

Connect an LED, with the correct polarity, in series with a 1k8 ohm resistor, between pin 16 (+) and pin X, where X is the pin corresponding with the module to be read. Connect a push to make switch between pin X and pins 4 or 5 (-).

The circuit can then be used in the same way as the pre ’96 diagnostic sockets, situated in the engine compartment.

For

Motronic 4.3 or Fenix 5.2, X = 3.

ECC , X = 6, Timer Type 4, X = 9.

Cruise Control, X = 13; 900 & S/V 90 ABS, X = 12 .

Link to comment
Share on other sites

  • 1 year later...

Thank you guys for the answers!

Actually Jordan was right, playing with the COM port settings (setting it less then 9600) helped, now i am able to read DTCs.

The cable and software i used were: obd2 kkl usb cable with ft232b chip inside from ebay, vol-fcr 1.3.6 serial version and the driver from http://www.ftdichip.com/Drivers/VCP.htm

If you guys could share with me the difference between the 1.3.6 and the newer software versions (what has the newer more?) i would be thankful!

Has anyone figured out the com port settings when using the ftdichip driver? I can read codes fine, however, when I attempt to clear the codes I receive the com error. I have set connection speeds to 9600 buad but there are additional settings in the com port advance tab that probably need to be changed. Unfortunately, I do not have time to wait for a serial cable nor do I have access to a loptop with a serial port. Any help would be very much appreciated. I need to pass va inspection this week.

Link to comment
Share on other sites

...If you guys could share with me the difference between the 1.3.6 and the newer software versions (what has the newer more?) i would be thankful!

Newer versions are not anymore serial to obdII port.They are usb to obdII port and the other difference is that they can display live data.

Link to comment
Share on other sites

I don't know about the computer stuff since I just bought a reader from ebay for like 30 bucks done. as for the speedo if you have a 96 850 then your speed sensor comes from the abs. most likely its the module. there is a guy on here the is good at fixing them and is well priced. as for the tach. not working there is a cog in the re that is relatively easy to replace, just go slow and you wont have a problem. this is what I used to fix mine. My link

Link to comment
Share on other sites

VOL FCR and vag come cable ($10) worked great for me.

Only a few times I had to set the COM port in device manager, because it was not recognizing number other than 1 IIRC.

I used it for both of my 97 854GLTs and also on 96 base.

Link to comment
Share on other sites

VOL FCR and vag come cable ($10) worked great for me.

Only a few times I had to set the COM port in device manager, because it was not recognizing number other than 1 IIRC.

I used it for both of my 97 854GLTs and also on 96 base.

Zombie Thread, bringing it back from the dead laugh.gif

This thread is days short of 2 years old laugh.gif

Link to comment
Share on other sites

Archived

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


×
×
  • Create New...