pscan.uk

Duncraig wrote:

Thanks, yes the counts for both coils varied as the engine ran . Pscan still not able to diagnose misfires or not on cylinders 3&4. Academic I suppose as the car is running perfectly.

The problem is that the factory T4 tool doesn't appear to be able to read cylinders 3&4 either. It's a bit difficult to make pscan do something that no other tool can do.

I think am okay to give a list of errors that pscan can read. I am not so keen on correlating them with codes because it took a huge amount of effort to reverse engineer these things.

ChristWolves wrote:

Question as above - Can the PSCAN tool support Rover 75 Diesel car ?

What system can PSCAN diagnose? Any token required to purchase?

Cheers mate!

Yes pscan does support the Rover 75 diesel.

The details of the Rover 75 coverage is here https://pscan.uk/features/75zt.html .

Coverage of the vehicle is not 100% as the 75 has many different ECUs, but development is ongoing. For example reconfiguration is not yet supported (for things like adding folding mirrors, coding in new ECUs etc). Also things like the ECU in the light switch or cruise control are not yet covered.

However all of the engine ECUs, airbags, ABS, body controller, immobiliser are covered.

There are no "tokens", no upgrade licenses, no VIN locks. You can just buy pscan and use it forever on all of your MG Rovers. The only restriction is that we don't support lending of your unit to other people nor group usage. I don't think that it's fair that we have to provide technical support to a group of people from one sale and that's the reason for this restriction.

maybe "during self test" or something like that would be easier to understand

It asks the engine ECU whether the sensor is active or inactive and puts the result of that query on screen.

julianfoulger wrote:

I hate to disagree but my unit is 227 (no hardware update) and I have never had any problems with comms with the engine on. What am I doing right? . My car is a 1998 MGF VVC:

The VVC was initially the worst for this and so I did a lot of work on the software so that when you are viewing live data it basically just displays the data whether it's good or bad.

This is not how these protocols are supposed to work. They are supposed to check for errors and fail or try again.

What I did with the MEM2J is a pretty nasty hack that it doesn't even really check it. Whatever garbage the MGF throws at pscan, it just tries it's best.

So if you look at the screen I am guessing that you will see random dashes and weird data appearing on the screen at times. Some cars are worse than others.

Later on we figured out a hardware fix that makes the data a lot more reliable.

Maybe I could look at whether a similar hack would work with MEMS1.9 ....

But in the end if you want the best experience then you will need the hardware mod.

227 has not been updated.

It looks like the software has crashed.

Reboot/restart the PC and try again.

How did you figure this out? If there is good evidence then I change it from "ignition switch" to "ignition on".

Andy55 wrote:

Hi, I'd be interested to hear from anyone who has a 75 1.8t and has used their Pscan to write a Saws remap to their ecu.

Hi Andy, I think that SAWS have done a few. It's a shame that no one replied. Did you decide to go ahead anyway?

There's another thread here https://www.the-t-bar.com/forum/pscan-uk-diagnostic-tool-forum/97624-pscan-diagnostic-tool in which someone said that a bad battery earth (in this case the captive nut to which the earth cable connects) caused failure of both ECU and lambda sensor. Maybe your live data glitches of 12V could be the same thing?