I've borrowed a VAGCOM USB lead and downloaded the demo VOL-FCR software. The software picks up that the lead is there but no joy on. Dec 28, 2017 - Now looking into VOL-FCR software and the connector cable you need to connect the computer to the OBD2 port. I run Linux for everything.
Hey guys, Old thread but maybe someone has some info pertaining to my problem. I purchased the Volvo FCR cable from ebay with a serial port end instead of the usb. For some reason I thought the serial version was better than the usb. Of course, my laptop has no serial ports so I also bought a ExpressCard serial port.
I set the add on serial port in device manager to com1. The FCR program can't communicate with the car. I tried lowering the baud rate and adjusting the Uart settings but still no go. Will a usb to serial adapter work or should I just try to find an FCR cable that has the usb plug? 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?
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 (). 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. 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.
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.
Retrieved 8 April 2013. • ^ Farber, Stephen (January 28, 2008)..
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.
I have a CEL that I need gone/fixed asap so I can pass inspection.