Merged Lexia & Diagbox threads

[Mikrosoft]

Ok all up and running as i had my witeless turned off lol.

What is my RPO number?

Update found the RPO but it still wont read the box i get this message.

[Ben82]

Ok all up and running as i had my witeless turned off lol.

What is my RPO number?

Check the label that has your tyre pressures on it.. Your RPO should be in the
10600-10900 ish range i believe.

Alternatively post or PM the last 8 digits of your VIN and one of us can find out for you

[Ben82]

Ok all up and running as i had my witeless turned off lol.

At the RPO screen, unplug the USB cable for the lexia from your computer and reconnect it give it a moment then proceed.

[Mikrosoft]

Thanks Ben I just dragged it all back indoors will give it another go after a strong coffee lol.

[Mikrosoft]

Well i think its connected now but not fully talking to the ecu keeps telling me to switch off and on the ignition then turn on dipped beam and it connects but says no in every column

I will admit im all new to this so will take some getting used too here are some screen grabs of various bits and bobs and mostly i get cannot connect messages.

[Ben82]

Well you're making some progress at least.

I'm not sure about your issue, did your device come with a far earlier version of lexia? there was a blacklisting of the clones around Diagbox 5.29 and to use beyond that I believe it needs a chip replacing. Otherwise you can stick to 5.29, I believe if it's updated your device, it may have "semi-bricked" it, and it needs a reflash to a lower firmware.

Offer is still stands if you're not too far I don't mind bringing my lexia and laptop along (or you can bring it here/to a central location), and we can eliminate the device, car, or software as an issue.
I don't have my C5 with me though, so you/we can't try your lexia on mine.

[Mikrosoft]

Thanks Ben will keep that in mind I'm in ashford and yes your right it is 2 years old it was bought and used once using 5.29 and then never used again my friend gave it to me when I got my c5 but he lost the disc.

So 3 options

1. Get lexia chipped
2. Use 5.29 software (is this a viable option)
3. Buy a new lexia box

What would you recommend.

[Hell Razor5543]

It is also possible (for a fee, obviously) for the lexia firmware to be updated so that it can handle above Diagbox 5.29. I know that Easy Diagnostics do this (but as they are currently updating their website I cannot find the link). That may be an option you might want to consider, regardless of where you get the firmware upgrade from.

[Ben82]

#2 should be viable, and is the cheapest option (i.e. no cost), you have already confirmed Diagbox fires up the Lexia application for your car, So there should be very little difference in Lexia in 5.29 compared to the version you are running... I've never run 5.29, but pretty confident for your car you won't lose out on anything compared to the current version.

#1 if you can find somewhere that does it (I know easydiagnostics do it - think it was for about £40ish), and there are a few other places.
#3 would cost £60-£120 depending on where you look at getting it from.

EDIT: Should also say, if you want to meet up somewhere around Maidstone I don't mind I would suggest trying to go back down to 5.29 though first.

[Mikrosoft]

Cheers yes I will uninstall and install 5.29 is there something I need to do to any files after uninstalling or just restart and install 5.29

[Ben82]

I would suggest making sure all the diagbox files have gone.. they install in (at least):
C:\APP
C:\AWROOT
c:\BackupDB

[Mikrosoft]

Cheers Ben much appreciated

[Mandrake]

Your interface has firmware 4.3.0 on it which is the latest firmware. If the interface is one of the Chinese clones it won't work with this firmware version, nor will Diagbox later than V5.29 work with it. I don't think your interface will be bricked though.

I'd suggest similar to Ben:

1) Uninstall Diagbox and then delete the directories Ben lists if they still exist, then reboot.

2) Install Diagbox V5.29. You can download a copy here if you don't have it:

https://mega.co.nz/#F!mMAkSKbY!XLBJ5AGUSi4WN0fmYwEfIg" onclick="window.open(this.href);return false;

Note: you don't necessarily have to upgrade from V5.02 (the initial install version) to V5.29, V5.29 is the LAST version you can run on a clone interface. V5.02 will more than likely do everything you need so rather than going through the whole install, update, update.... process just install V5.02 and try it.

3) If you're still having problems you might need to manually downgrade the firmware of your interface. You can do this with a program called PSA Interface Checker, which you'll find a copy of here:

https://mega.co.nz/#!OJZyzCiB!EfVmqzZmz ... MTwbIPfGPQ" onclick="window.open(this.href);return false;

I'm not actually sure what firmware version is the best for Diagbox V5.02 - V5.29 as there are many different firmware files provided with the interface checker app all the way from 2.0.1 to 4.2.9. I'd suggest maybe try V4.1.6 or V4.2.0

Let us know how you get on. Chances are when you run V5.02 it will automatically downgrade the firmware to the correct version for you, or that if you downgrade manually to a very old version it will automatically upgrade to the correct version. Check the firmware version either in PSA Interface checker, or in the tool configuration Lexia screen you showed a screenshot of.

[Mikrosoft]

Thanks Mandrake im just installing 5.02 now but its a bit late to pop it on the car so will test it all tomorrow evening i do like my gadgets so i love to tinker.

Will 5.02 do everything i need it too like reset service light and fault find for me.

Would also like to enable the cd changer in case i want to fit a bluetooth kit.

[Ben82]

Thanks Mandrake im just installing 5.02 now but its a bit late to pop it on the car so will test it all tomorrow evening i do like my gadgets so i love to tinker.

Will 5.02 do everything i need it too like reset service light and fault find for me.

Would also like to enable the cd changer in case i want to fit a bluetooth kit.

Don't see why it shouldn't