SwedeSpeed - Volvo Performance Forum banner
Cancel
Create thread New Garage Forums

Vida for 2016+ p3 cars

3 reading
Jump to Latest
110K views 160 replies 64 participants last post by  RS3100  
Z
#1 · (Edited)
Update: 12/12/2020; Updated SQL for 2018 cars.
Update: 6/27/2020; Updated guide to make changes to database for all models.

This is version 2 of guide. This updated version is easier to use and by following it you will modify VIDA's database to not reject your VIN based on the year. As far as I know it looks like this is what should be sold on eBay as "VIDA 2015A".

Before I provide detailed instructions, enter don't do this warning:
I provide NO guarantee and if you damage your computer/car I'm not taking any responsibility for this. Before you start, backup your VIDA bacause it might stop working.

Here is the guide:
  1. Download and install SQL Server and Management Studio (SSMS)
  2. Open a new window for SQL query, copy and paste the text below and hit Execute. Below is the screenshot of what you should see at the end.


    DELETE FROM [basedata].[dbo].[VINDecodeModel] WHERE YearCode = 'G' OR YearCode = 'H' OR YearCode = 'J' ;

    INSERT INTO [basedata].[dbo].[VINDecodeModel] ( VinStartPos, VinEndPos, VinCompare, fkVehicleModel, fkModelYear, fkBodyStyle, fkPartnerGroup, ChassisNoFrom, ChassisNoTo, YearCodePos, YearCode, ObjVersion)
    SELECT VinStartPos, VinEndPos, VinCompare, fkVehicleModel, fkModelYear, fkBodyStyle, fkPartnerGroup, ChassisNoFrom, ChassisNoTo, YearCodePos, 'G', ObjVersion
    FROM [basedata].[dbo].[VINDecodeModel]
    WHERE YearCode = 'F';

    INSERT INTO [basedata].[dbo].[VINDecodeModel] ( VinStartPos, VinEndPos, VinCompare, fkVehicleModel, fkModelYear, fkBodyStyle, fkPartnerGroup, ChassisNoFrom, ChassisNoTo, YearCodePos, YearCode, ObjVersion)
    SELECT VinStartPos, VinEndPos, VinCompare, fkVehicleModel, fkModelYear, fkBodyStyle, fkPartnerGroup, ChassisNoFrom, ChassisNoTo, YearCodePos, 'H', ObjVersion
    FROM [basedata].[dbo].[VINDecodeModel]
    WHERE YearCode = 'F';

    INSERT INTO [basedata].[dbo].[VINDecodeModel] ( VinStartPos, VinEndPos, VinCompare, fkVehicleModel, fkModelYear, fkBodyStyle, fkPartnerGroup, ChassisNoFrom, ChassisNoTo, YearCodePos, YearCode, ObjVersion)
    SELECT VinStartPos, VinEndPos, VinCompare, fkVehicleModel, fkModelYear, fkBodyStyle, fkPartnerGroup, ChassisNoFrom, ChassisNoTo, YearCodePos, 'J', ObjVersion
    FROM [basedata].[dbo].[VINDecodeModel]
    WHERE YearCode = 'F';


    Image
  3. Enjoy VIDA and if you feel thankful you can buy me a beer: @zjev

This is my own work but I got the idea from discussion on facebook from 2018 facebook.com/groups/1921217794833193/permalink/2149268555361448/

Cheers and enjoy your Volvo!
 
C
#4 ·
Awesome work! I only have a copy of VIDA 2013A. Is it possible to get a copy of VIDA 2014D with the edited database?
 
Save
Reply Quote Like Like
Z
#5 ·
I don't have all the knowlege on the differences between 2016 - 2018 P3 VIN numbers and it would probably take some serious time to add these changes for all possible combinations. I did provide a way to modify some of the data to read your own VIN.

I would recommend downloading 2014D from here: https://forums.swedespeed.com/showthread.php?481385-VIDA-Dice-2014D-VM-Image-Download-Link
and then changing the database based on the guide I wrote.
 
Z
#8 ·
VovoXC60 said:
" Weekend is here and I had a few hours for writing this down."

Really... copy and paste is that tough? At least give the guy credit where you got this...
Click to expand...
Wrote this myself and posted to both Swedespeed and matthewsvolvosite. Not going to argue with someone on the internet the second time. If you don't believe me then check the comments here https://www.facebook.com/groups/1921217794833193/permalink/2527582727530027/

And I did give credit to the Facebook post where I got the idea from.
 
A
#14 ·
Hi Zjev - I'm a little confused as to the steps for Win10. I've got my old 2014D disc and a new laptop. Originally I was planning on setting up a VM with Win7, but then saw another VM with Win10, vs installing directly. Not sure which way to go.

For your 2016+ fix, does it matter what version of SSMS I install? Anything special for V60 (instead of S60)?
https://sqlserverbuilds.blogspot.com/2018/01/sql-server-management-studio-ssms.html

I found RickHaleParker's thread "INTALLING VIDA 2014D FOR THE FIRST TIME WINDOWS 10 HOME" https://www.matthewsvolvosite.com/forums/viewtopic.php?t=84636 & https://www.matthewsvolvosite.com/forums/viewtopic.php?f=40&t=83834&start=50

Seems the repack and 2099 patch fixed the timeout issues?

And a monster thread for Vida2014D on Win10 Pro -https://forums.swedespeed.com/showthread.php?242441-Volvo-VIDA-2014D-and-Windows-10-Pro
 
Save
Reply Quote Like Like
A
#17 ·
zjev, Roxana's VM worked fantastic - thanks. It now has a Win10 version. I downloaded SSMS 18.4, copied it onto the VM by adding a shared drive, installed SSMS, and followed your instructions (VIN was within range for our 2016 V60, and I changed the 2015 Year Code from F to G). VIDA took the VIN (when I changed to the AME partner group).

Crossing my fingers it works when I try connecting with DICE tonight!

Thanks for making & sharing this tutorial.
 
Save
Reply Quote Like Like
Z
#18 ·
askulte said:
zjev, Roxana's VM worked fantastic - thanks. It now has a Win10 version. I downloaded SSMS 18.4, copied it onto the VM by adding a shared drive, installed SSMS, and followed your instructions (VIN was within range for our 2016 V60, and I changed the 2015 Year Code from F to G). VIDA took the VIN (when I changed to the AME partner group).

Crossing my fingers it works when I try connecting with DICE tonight!

Thanks for making & sharing this tutorial.
Click to expand...
How did it go with DICE?
 
Z
#30 ·
The tutorial I wrote above explains how to do it - buy you need to know the VIN. It would theoretically be possible to do all the changes and upload VIDA somewhere but I'm not going to spend the time doing it. I would rather help other members to figure out how and what they have to change.
 
P
#40 ·
Great! I modified my Virtualbox machine linked here, and now my VIDA2014d accepts 2015 and 2016 vins! Virtual machine runs Win7, so I downloaded earlier SSMS version 16.5.3, and it worked.

I tested several 2015 and 2016 cars from various ads, all got accepted! Only 2017 and 2018 vin were not recognized, except one /maybe produced at the end of 2016/. I tested P3 platform cars.
 
J
#47 ·
again thanks, but all that's done ok - I'm pretty good with PC's, and this sort of stuff used to be my bread and butter - I've also ran it in compatability mode, as administrator, etc etc - but it just dissapears off into nowhere - My VM install of Win7 Pro and Vida has got SQL server 2008 installed, which I'm assuming is part of the VIDA system, but does that sound right to everyone ?
 
A
#50 · (Edited)
Have been on moderation.

So yes, tryed script, it works for others 2016MY, but it is dose not affected for me, car is MY2017.
VIN is YV1DZ40CCH2chassi with B4204T11, TG-81SC AWD. PartneGroup EUR.

Tryed to make changes in rows with cars 2015, but still not decoded =\
in rows with H and VinCompare DZ make Chaasis from 1

My target is TCM to check transmission oil temeprature.

Image


UPD:

HAH! MY2017 XC60 works. My fault is partner group.. 1003 it is INT... so it works!

Image
 
R
#51 ·
Ive just performed this mod, this is what I have.
VIN:YV1FW79C0G1312297
Seems to find this but does not complete the engine data or drive RHS.
When I connect DICE to vehicle and the engine is running (verified connection with VDASH) and go to diagnostics and details it does not recover any details, its reading but then does not fill in any of the fields.
The status below 'print' says 'connected' battery symbol gives 0.0v and ket pos is 0
 
Z
#52 ·
That's 2016 V60 and it should be working. I'm visiting my parents for three more weeks and will be able to look at it after.

The only issues I heard about was from a guy with a brand new engine that was not available before 2015 and it wasn't in VIDA.

Did you try changing all partner groups? The VIN is going to be recognized usually under only one partner group.
 
SwedeSpeed - Volvo Performance Forum
posts
4.1M
members
192K
Since
2000
A forum community dedicated to Volvo owners and enthusiasts. Come join the discussion about performance, builds, modifications, classifieds, troubleshooting, maintenance, new releases, and more!
Full Forum Listing
Explore Our Forums
R Forum (2004-2007) S40 & V50 (2005-2012) XC90 (SPA: 2016 - ) S60, S60CC & V60, V60CC (2011-2018) XC90 (2003 - 2014)