VIDA 2014D on XC60

[Clan]

Originally Posted by rxtian

OK I changed the A8 to 55 and the G to an F which VIDA accepted as a VIN, but the first thing it does is communicate with the CEM to verify the VIN - which fails and locks out diagnostics.

Any advice on how this trick is done?

if the vida version is say 2014 with support for 2015 , they would not put support in for 2 years ahead i guess... what i was wondering is what happens if you just enter the model V60 for example and model year 2015 for example , would it communicate on a 2017 model ?

[rxtian]

Originally Posted by Clan

if the vida version is say 2014 with support for 2015 , they would not put support in for 2 years ahead i guess... what i was wondering is what happens if you just enter the model V60 for example and model year 2015 for example , would it communicate on a 2017 model ?

I just tried that - when you click to the tab that communicates with the car, the first thing it does it verify the VIN... and realised it’s not a 2015 car.

[cheshired5]

Originally Posted by rxtian

Any tips on the order to do this in?

I can edit the G to an F for the model year, but it still cant accept the VIN - presumeably because I have the 190 D4 not the 181? Trying to find the characters for the 181...

From my buyers who have later model years, I believe they manually create a vehicle profile using their chassis number but with the model letter changed.
They also make sure that the region code is EUR/INT then click OK then click read vehicle.
If your engine is one that was introduced after Vida 2014d was designed, Vida won't recognise the engine code or have any technical data to communicate with it.

I'll try to remember which of my buyers have done the amendments and ask them precisely what they did.

Originally Posted by Clan

worth a try some time as long as the car system doesn't crash !

I think it will either work or it won't and doubt it will kind of work then suddenly throw a problematic hissy fit.

[rxtian]

Yeah I don’t think there’s any danger - especially just for reading diagnostic info.

From my experimenting, you can’t get to the diag section without entering a VIN or reading a vin (even if you select the most similar car using the drop downs).

If you let it read the VIN it immediately kicks off.

If you enter the most similar VIN possible (just changing model year and A8 to 55 for the 190 to 181hp d4’s) - it will start Comms with the car, then lock out at vin verification.

Maybe if you have an engine which spans the model years it works because there is no check on the model year character when “verifying” the VIN.

I’m an electronic engineer who works in the automotive sector so I’m tempted to make a CAN bridge which edits the VIN read UDS reply... I’d imagine most of the DTC codes between the 190 and 181 D4s are similar enough that it would still be of use!

[b1mcp]

Thanks for the useful replies. That gives me what I need.

[Clan]

Originally Posted by cheshired5

From my buyers who have later model years, I believe they manually create a vehicle profile using their chassis number but with the model letter changed.
They also make sure that the region code is EUR/INT then click OK then click read vehicle.
If your engine is one that was introduced after Vida 2014d was designed, Vida won't recognise the engine code or have any technical data to communicate with it.

I'll try to remember which of my buyers have done the amendments and ask them precisely what they did.


I think it will either work or it won't and doubt it will kind of work then suddenly throw a problematic hissy fit.

hmm it did about 14 years ago when VADIS changed to VIDA when i tried to communicate with a 2001 V70 ...( counterfeit copy) ,luckily disconnecting the battery brought it back .

[Keefie]

Hi

Not sure if you're all aware of the fact that you can modify the VIDA database tables to read and decode the car VIN with DICE. I've used the Microsoft SQL Server Management Studio to view, add, alter the VIDA database tables and other functions.

I've got VIDA 2014D running with the patch for extended date to 31/12/2130 and the updated "fake 2015A" databases (see https://forums.swedespeed.com/showth...ithout-USB-key).

To my knowledge, the "fake 2015A" works with vehicles from 1997 up to 2016 - not sure of the cut off date and it may vary with vehicle model; it worked on my son's March 2015 V60, but not his wife's February 2016 V60. However, I modified the database table to change the year date and it read and decoded her car VIN with DICE (see https://forums.swedespeed.com/showth...-v60-amp-2014d). I tried a number of comms options and they all seemed to work okay.

As always, you try things at your own risk.

Best wishes.

[rxtian]

Thanks for the info!

It looks like people were onto the right track with the tables, but I can’t see that anyone managed to put it all together to communicate on a 2016 model year car...?