MG CAR OWNERS FORUM

Just so you know, I drive a 2014 diesel Ford Mondeo Edge.

I listened the advice and spent a pretty penny on an ODBII cable.

It appears to be somewhat flimsy when I insert it into the port, however it appears to have solved the problem at hand.

Two of the banks are shown as red and lean, and they're giving the same readings as the other two banks; this leads me to assume that it thinks the car is running on petrol. Additionally, it identifies the car as a 1989 Focus.

I didn't give it much thought after that.

A Focus from 1989? Holy cow! A truly unique creature.

It is not really the fault of Forscan if the OBD2 adapter is not securely fastened in the USB port. The issue lies more with the hardware. Is it possible that you have tried connecting it to different USB ports on your laptop or other devices?
Is the adapter's driver software up-to-date?
Do you know if Forscan can detect it? 'Simulation' or 'Emulation' mode is available in several diagnostic apps.

Are you sure you purchased a compatible adapter? You can verify this on the Forscan website. For example, did you buy one of the ones that were suggested for use with Forscan on the website?

There isn't enough detail regarding your actions to rule out a million possible causes. Additionally, you might want to consider checking out or commenting on the forscan forum: Welcome to the FORScan forum!

However, I would assume that the cable you are using was not properly configured in the connection settings, causing forscan to encounter numerous failures on the link. This is because forscan is attempting to use a protocol and speed that is not compatible with your current setup. Verify that your cable's settings are a good fit. A 115200bps FTDI version is included in the "Official" vlinker.

Thank you all for your responses; I suspected it was probably me. Ha ha!

I was really dissatisfied with the ODBLink EX cable I purchased because of how poorly it fit into the socket.

The year 1998 Is there a way to test the software without the dongle by focusing the demo config on forscan?

I thought the dongle was only for demo purposes; are you sure it's scanning the vehicle?

Tell me the hardware specs you're using it with.

The dongle was red last nite when I plugged it in, okay. After I installed the drivers and right-clicked the dongle in the Windows settings menu, it said that everything is working well.

I went into the settings and looked for the "devices" menu item, but when I went to choose a USB device, it was blank and greyed out.

The dongle appears more orangey red in colour than green.

Whose drivers were downloaded? Which one is better, FTDI or CH340?