Got cable and installed the x64 driver. Computer said yes!

However, on plugging the cable in, I get the double tone sound that indicated device not recognised, and computer says NO!

I have tried all 3 x USB ports, and switching the cable switch each time, still won't find a driver. I've also rebooted laptop a few time too, no difference.

I've just tossed £23 down the drain, haven't I?

Where did you get that driver?

Try the CH340 driver from this page. Links & Help (fwscart.com)

I bought the obdlink ex and connected to a win xp laptop and also a win 11 laptop without issue. Haven’t plugged into the car yet though. Most seem to recommend the vklinker and cheaper I believe.

both Forcan recommended I belive

12 minutes ago, TomsFocus said:

Where did you get that driver?

Try the CH340 driver from this page. Links & Help (fwscart.com)

Tom, I got the driver on the same site, but obviously downloaded the wrong one! The one you directed me to, seems to have worked, and on plugging the cable in it appears to be recognised! Thank you...

Now, I assume I just plug into car, turn on ignition, and in ForScan, just hit the DTC button?

10 minutes ago, StephenFord said:

Now, I assume I just plug into car, turn on ignition, and in ForScan, just hit the DTC button?

Yeah.  You need to connect the car to Forscan before reading DTC's, but it'll tell you what to do, all fairly intuitive.

Well, I popped my ForScan cherry this morning, feeling pretty smug LOL Though every module displayed a green tick for full bill of health. The only item was the following which I'm pretty sure is insignificant. Nothing to direct of the 'stutter' issue I'm having...

What an anti-climax.   Congrats for using Forscan though!   

The U1900 fault was probably triggered when the cluster was removed for repair, you can clear that one.

Next step is trying some live data during a drive.  If you can make the stutter happen while recording, that would be ideal.  Again, no chance of module damage as it's only reading data.  If you click the graph icon below the DTC icon, you should get a list of PIDs.  I'm not sure how many you'll have on that engine.  I'd be looking for throttle body, MAP sensor, anything to do with fuel pressure or injectors, possibly spark advance, plus RPM & road speed.  Hopefully we'll be able to see the stutter on one of the graphs to get a better understanding of what's happening.

16 minutes ago, TomsFocus said:

The U1900 fault was probably triggered when the cluster was removed for repair, you can clear that one.

Next step is trying some live data during a drive.

I'll do a 'google' on live data, how to use it, and report back when I have some info. Oh, how do you 'clear' that fault above?

20 minutes ago, StephenFord said:

Oh, how do you 'clear' that fault above?

On the bottom row of your picture, there are two buttons with yellow triangles.  Clicking the right hand side one will reset the DTC's.

2 minutes ago, TomsFocus said:

On the bottom row of your picture, there are two buttons with yellow triangles.  Clicking the right hand side one will reset the DTC's.

You must feel like a dad pushing his kid on his first bicycle ride 😂 Thanks again Tom...

Here is the official documentation for using the Windows version 

https://forscan.org/documentation_13.html 

You can stroll down to setting up gauges.

Personally I would go into Tests next and click on Mode 6 Test and run it. There may or may not be a Misfire Count for Individual Cylinders. It would be useful to know if one or more Cylinders are misbehaving or if all of them are by the same amount as the each other. The rest of the info in Mode 6 is likely to be double dutch and will not mean much to anyone.

There is also normally a Key On Engine Running self test for the PCM, just follow the Instructions. 

To add to what Tom said, I would also bring up the Accelerator Position PID as well as the Throttle one, when analysing the data later it will be useful to know where your right foot was when the car was misbehaving as well as what the Throttle was commanded to do.

There may also be PID's for individual Cylinder Misfiring that you can Live Monitor at the same time as everything else for the reasons stated earlier.

Congrats on the birth of your new child, there'll be teething and late nights but it will be worth it.

Good morning Stephen, late to the party but well done on connecting up and using FORScan. looks like the car is actually in good health apart from the stutter issue. As Tom has already said the 'U' code will most likely just date back to when the IC was repaired.

39 minutes ago, Tizer said:

Personally I would go into Tests next and click on Mode 6 tated earlier.

Well, I just did a mode 6, this is what I got...

1 hour ago, StephenFord said:

Well, I just did a mode 6, this is what I got...

That is unfortunate, older models are sometimes not catered for in FORScan to the same extent as newer  models and it looks like Cylinder Misfire Counters are not catered for in Mode 6 for your car.

There are likely to be PID's for Misfires though that you can Live Monitor while driving.