IPD sale XeMODeX - Experts in Volvo Electronics Volvo modules repair and programming
Please use the MVS Amazon link when you buy anything at all! It helps this site. Thanks very much!

Get email notification of topic replies. Log in or register (free). Amazon Link Buy anything with this and it helps MVS!

VIDA for 2016+ P3 cars

Help, Advice, Owners' Discussion and DIY Tutorials for the groundbreaking new Volvo S60 2011+, V60 2015+ XC60 2010-2018.
Post Reply
barcode
Posts: 7
Joined: Mon Jan 27, 2020 7:51 pm
Year and Model: 2016 S60, 2015 V60
Location: Miami, Florida
Been thanked: 1 time

VIDA for 2016+ P3 cars

Post by barcode »

Long time member, just needed to change my username..

Here is the deal breaker. I figure out how to connect VIDA 2014D to my (new :D ) 2016 S60 and I think this procedure (reserve at least an hour if you're confident with changing data in a database) should work for all P3 cars.
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.

Here is the guide:
  1. Download and install Microsoft SQL Server Express 2014 (if using windows 7)
    1. https://www.microsoft.com/en-us/downloa ... x?id=42299
    2. Download SQL Management Studio (MgmtStudio 64BIT\SQLManagementStudio_x64_ENU.exe for 64bit system)
  2. Open the SQL Server Management Studio and open the “basedata” database
    p1.png
  3. I will provide directions to add 2016 S60 to the database. Read through the following and modify the information for your own car. You might have to modify the bold text.
    1. Note that the VIN: LYV402FM7GB092244 in not accepted by VIDA. We will modify the database to recognize this VIN.
      p2.png
  4. We will tell VIDA that this VIN is a part of 2015 model year. First we have to find ID of 2015 model year in “dbo.ModelYear”. Right click on dbo.ModelYear and select “Select Top 1000 Rows”. 2015 model year has ID “1205”.
    p3.png
  5. Similarly list “dbo.VehicleModel” and find the ID of your car. S60 has the ID 1038.
    p4.png
  6. Similarly list “dbo.VINDecodemodel”. This table is used to determine the model and year of a car based on your VIN. We will have to locate a similar car (understand VIN comparisons) that fails ONLY because of the year code in the VIN. We will modify a record that matches our car in everything but the YearCode field.
    1. Modify the SELECT statement to add a filter on your vehicle model by adding “where fkVehicleModel=1038” at the end of the statement. Click F5 to apply this filter.
      p5.png
    2. Scroll through the fields until you find your ModelYear (in the fkModelYear column). Now you have to compare your VIN. Read the data in VinCompare column. This string has to match your car’s VIN between the VinStartPos and VinEndPos positions. Below you can see that the highlighted row matches my VIN since FM is at 7th and 8th position in the VIN.
      p5.png
    3. Looking at the rest of the row, the ChassisNoFrom and ChassisNoTo (chassis number from and to) doesn’t contain our car. The chassis number (last 6 digits, 092244 in our case) is lower than 332000.
    4. The YearCodePos tells you the position of the year code in the VIN. The highlighted row doesn’t correspond to our car because our 10th digit is “G”.
  7. We now modify this row to match our VIN. We will lower the ChassisNoFrom to include 092244 and change the YearCode. Fortunately, I don’t need VIDA to read 2015 cars so I’m going to modify this row. It might be the case that VIDA will stop reading 2015 S60 cars because of this modification. The row ID is -2042382967 (from the picture the first number in the row)
    1. Right click on dbo.VINDecodeModel and select “Edit Top 200 Rows”
      p6.png
      .
    2. We need to add a filter to show only the one particular row. Click on Show SQL Pane button (in red box)
      p7.png
    3. Add “WHERE ID = -2042382967” and execute the statement by Ctrl+R or by hitting this button:
      p8.png
    4. Edit the fields as mentioned before.
      p9.png
    5. Click on the next row for the changes to save. The red exclamation marks should disappear.
      p10.png
    6. Restart your computer (or restart SQL server and VIDA), enter your VIN.
      p11.png
  8. Enjoy VIDA and if you feel thankful you can buy me a beer: https://www.buymeacoffee.com/jewY8ab
This is my own work but I got the idea from discussion on facebook from 2018 facebook.com/groups/1921217794833193/permalink/2149268555361448/

Cheers!
User avatar
RickHaleParker
Posts: 4779
Joined: Mon May 25, 2015 2:30 pm
Year and Model: See Signature below.
Location: Kansas
Has thanked: 3 times
Been thanked: 616 times

Re: VIDA for 2016+ P3 cars

Post by RickHaleParker »

Two versions of SQL Server 2014 Express & Express Adv. Does it matter which one?

You got any tips on upgrading from SQL Server 2008 to SQL Server 2014 on a windows 10 machine and getting 2014 to work with VIDA 2014D. I tried it and VIDA monitor would not connect to the database.
1998 C70, B5234T3, 16T, AW50-42, Bosch Motronic 4.4, Special Edition package.
2003 S40, B4204T3, 14T twin scroll AW55-50/51SN, Siemens EMS 2000.
2004 S60R, B8444S TF80 AWD.
2005 XC90 T6 Executive, B6294T, 4T65 AWD, Bosch Motronic 7.0.
barcode
Posts: 7
Joined: Mon Jan 27, 2020 7:51 pm
Year and Model: 2016 S60, 2015 V60
Location: Miami, Florida
Been thanked: 1 time

Re: VIDA for 2016+ P3 cars

Post by barcode »

Totally forgot about this. I have my VIDA in Windows 7 and the new SQL server cannot be installed on Windows 7.
You don't want to upgrade the SQL Server!! If you upgrade it then VIDA won't connect as in your case.
You need to install just the monitoring tools using the installator. Once you install the monitoring tools, both versions should connect to the SQL server from VIDA.
I can take a screenshot of the installation and post it here. Give me a few hours.
User avatar
RickHaleParker
Posts: 4779
Joined: Mon May 25, 2015 2:30 pm
Year and Model: See Signature below.
Location: Kansas
Has thanked: 3 times
Been thanked: 616 times

Re: VIDA for 2016+ P3 cars

Post by RickHaleParker »

I think I found part of the problem. I installed SQL Server 2014 64 bit. Vida is 32 bit.
I rolled back the SQL Server 2014 64 bit install. Vida is working again.
Perhaps I should use the SQL Server 2014 32 bit to upgrade from 2008 to 2014 ...

My OS is Windows 10 64 bit.
2020-02-09 (3).png
1998 C70, B5234T3, 16T, AW50-42, Bosch Motronic 4.4, Special Edition package.
2003 S40, B4204T3, 14T twin scroll AW55-50/51SN, Siemens EMS 2000.
2004 S60R, B8444S TF80 AWD.
2005 XC90 T6 Executive, B6294T, 4T65 AWD, Bosch Motronic 7.0.
barcode
Posts: 7
Joined: Mon Jan 27, 2020 7:51 pm
Year and Model: 2016 S60, 2015 V60
Location: Miami, Florida
Been thanked: 1 time

Re: VIDA for 2016+ P3 cars

Post by barcode »

No need to install SQL Server. This might interfere with VIDA. You want to install Management studio that will let you connect to VIDA's SQL server.
This is what can be used for Windows 10: https://docs.microsoft.com/en-us/sql/ss ... rver-ver15

Once you open it you should see something that looks like the screen below. The default settings should let you connect to VIDA. Do NOT use the settings you can see on the picture - this is if you have VIDA in virtual machine...
p1.png
xHeart
Posts: 2792
Joined: Sat Dec 03, 2011 8:05 am
Year and Model: 13XC90/01V70X/97N854
Location: Great Lakes - USA
Has thanked: 25 times
Been thanked: 46 times

Re: VIDA for 2016+ P3 cars

Post by xHeart »

barcode wrote: Sun Feb 09, 2020 2:26 pm No need to install SQL Server. This might interfere with VIDA. You want to install Management studio that will let you connect to VIDA's SQL server.
This is what can be used for Windows 10: https://docs.microsoft.com/en-us/sql/ss ... rver-ver15

Once you open it you should see something that looks like the screen below. The default settings should let you connect to VIDA. Do NOT use the settings you can see on the picture - this is if you have VIDA in virtual machine...
I'm running VIDA 2014D on Windows 10/HP laptop successfully. Does the above procedure work for non virtue machine setup?
--
Golden Retriever | 2014D VIDA DiCE | 2020 V60CC | 2013A XC90 +150mi/241km | 2001 V70XC +200mi/322km | 1997 Volvo 850 +180mi/289km
Past: German Shepherd | 1989 Volvo 740 GL | 1979 Volvo 240
barcode
Posts: 7
Joined: Mon Jan 27, 2020 7:51 pm
Year and Model: 2016 S60, 2015 V60
Location: Miami, Florida
Been thanked: 1 time

Re: VIDA for 2016+ P3 cars

Post by barcode »

xHeart wrote: Sat Oct 10, 2020 6:34 am
barcode wrote: Sun Feb 09, 2020 2:26 pm No need to install SQL Server. This might interfere with VIDA. You want to install Management studio that will let you connect to VIDA's SQL server.
This is what can be used for Windows 10: https://docs.microsoft.com/en-us/sql/ss ... rver-ver15

Once you open it you should see something that looks like the screen below. The default settings should let you connect to VIDA. Do NOT use the settings you can see on the picture - this is if you have VIDA in virtual machine...
I'm running VIDA 2014D on Windows 10/HP laptop successfully. Does the above procedure work for non virtue machine setup?
Yes, there is not difference for this between running VIDA virtually or on the metal.
User avatar
RickHaleParker
Posts: 4779
Joined: Mon May 25, 2015 2:30 pm
Year and Model: See Signature below.
Location: Kansas
Has thanked: 3 times
Been thanked: 616 times

Re: VIDA for 2016+ P3 cars

Post by RickHaleParker »

xHeart wrote: Sat Oct 10, 2020 6:34 am Does the above procedure work for non virtue machine setup?
It got to be done in the same environment.
If you are running Vida on real metal do it on metal. If you are running Vida in a Virtual Machine do it in the same Virtual Machine.
1998 C70, B5234T3, 16T, AW50-42, Bosch Motronic 4.4, Special Edition package.
2003 S40, B4204T3, 14T twin scroll AW55-50/51SN, Siemens EMS 2000.
2004 S60R, B8444S TF80 AWD.
2005 XC90 T6 Executive, B6294T, 4T65 AWD, Bosch Motronic 7.0.
Post Reply
  • Similar Topics
    Replies
    Views
    Last post