VIDA 2014D/2015A Windows 11
-
@Di5B Do you run VIDA on native hardware or in a VM? Dedicated VIDA machine, or is it your everyday computer with lots of other software installed and lots off unnecessary background processes? Is any 3rd party antivirus or security software installed? What hardware specs?
-
Troubles troubles and troubles.
Finally got the Mongoose(obviously from aliexpress). laptop sees it. VIDA sees it. But when I try do diagnostic to my XC70 2006 VIDA says that all mongoose device is in-use by other app. I have only VIDA and Vdash installed from here and can't figure out how I can resolve that problem. -
-
@KonK Do you try to replace an existing VIDA or is it a clean install? Do you want to install it in a virtual machine or on native hardware? What version of Windows?
Please locate the following folder: C:\Program Files\Microsoft SQL Server\170\Setup Bootstrap\Log , there should be one or more subfolders with date and time as name, open the newest one and locate the file named "Detail.txt". It should have details what is the problem somewhere at the end. -
Hi everyone,
I'm trying to use VIDA 2014D with a Mongoose Pro JLR interface on a 2007 Volvo V70.
The connection itself seems to work:
- VIDA loads the Mongoose driver correctly
- VIN is successfully read
- the vehicle gets identified correctly
However, I have a strange issue with VIDA itself:
After logging in:
- both "Information" and "Diagnostics" tabs are greyed out.
After identifying the vehicle:
- "Information" becomes available,
- but "Diagnostics" remains permanently greyed out/unavailable.
So the problem does NOT seem to be complete communication failure, because VIDA can clearly talk to the car and read the VIN.
Has anyone seen this before?
Any ideas would be greatly appreciated.
-
@jexyq Hi, happened to me once before. I unplugged everything, shut off the car, restarted the PC. Then -> car ignition, plug in JLR, plug in USB (get a USB device notification), start vida, and be very patient. I manually typed in my VIN at VIDA profile.
-
@odder Thanks for the suggestion!
I actually just tried exactly what you described, step by step and in that precise order, but unfortunately, nothing changed. In my case, I have never been able to get it to work even once, which makes me think the problem might lie somewhere deeper.
Thanks for the quick reply tho, really appreciate it!
-
@jexyq does the car communicate with Vdash through your adapter?
Are you able to enter the diagnostic tab "offline" with no car connected? If you just enter your VIN or just define your car without the VIN, and than click ok?
Are you using the correct login? You need to login to the correct partner group which equals the market your car was initially meant for. Never use "Admin".
Have you tried to disable VIN decoding by going to computer settings in VIDA and then manually entering the VIN (VIN Dekoder off in red letters must be shown next to the VIN boxes), specify your car, then enter ok (don't click read next to the communication tool!), and than go to the diagnostic tab? This works even on most P1 and P3 cars that are officially not supported by VIDA2014D. As long as your adapter works.
What are your hardware specs CPU, RAM, SSD? VIDA requires a fast SSD and 4 or more GB of RAM to be halfway responsible. Maybe you need to be more patient for the diag database to load. This sometimes takes a several seconds even on my fastest computer with 16GB RAM and really, really fast NVMe SSD.
Are you sure that your adapter is okay? Most Mongoose clones from aliexpress, for example, don't have the original Atmel chipset or even a mongoose at all inside their chassis and are basically dead on arrival or don't work as expected. Mostly those garbage adapters don't properly communicate with either the HS or LS CAN leading to exactly the problem you have. VIN gets recognized. But full Diagnostics/Communication with the car is impossible.
-
@T5-T6-Schnappi
Yes, VDash works perfectly through the adapter.I don't really understand how that would work offline. I assumed the car has to be connected in order to access Diagnostics. In any case, I tried entering the VIN manually both with the car connected and with the cable disconnected, and it still doesn't work.
Yes, I'm using INT, which is the correct partner group for my car, at least according to the D5T5 lookup tool.
I just tried your procedure step by step: disabled VIN Decoder, entered the VIN manually, specified the car, clicked OK without using the "Read" button next to the Communication Tool. Unfortunately, Diagnostics tab is still grayed out.
My hardware isn't the greatest (Intel Celeron N2840 @ 2.58 GHz, 8 GB RAM, SSD), but I waited for about 30 minutes, so I doubt it's simply a matter of the diagnostic database taking time to load.
As for the adapter, I believe it's fine. Both HS-CAN and LS-CAN work perfectly in VDash, so the adapter itself and the drivers seem to be communicating with the car correctly.
-
@jexyq I would suspect your installation to be somehow borked then. You can use most functions of VIDA without being connected to a car. If diagnostics still don't work that way, it's time for a re-install.
Stop VidaMonitor
Exit VidaMonitor
Uninstall VIDA
Unistall SQL Server
Unistall everything else with SQL in it's name
Unistall Isoview
Reboot the computer
Delete all folders containing VIDA, Volvo, Ford, Isoview in their name
Delete : C:\Program Files\Microsoft SQL Server
Reboot again
Install VIDA from scratchYour Hardware is not the best, but good enough to run VIDA.
-
Hi people,
Is this software specifically for Windows 11, or can it be used on older windows versions/VirtualBox?
And if only Win11, does it have full functionality i.e. Diagnostics/Vehicle communication/Advanced... shows the VCT2000 button to initiate process?I have vida 2014D installed on an old Win7 laptop but for some reason it has stopped showing the VCT2000 button/icon to start diagnostic processes. I wanted to do a forced DPF regeneration but as well as the VCT2000 icon not showing it also has nothing to the right of the advanced tap in vehicle communication. I beleive this is something to do with ActiveX controls being blocked.
So after hours of messing about I came to the conclusion that a Vida version for virtualBox should solve all my issues. That is until I saw this version for Win11.
Some helpful advice would be mucho gracias...
TIA
-
@Bobeee This version of VIDA is heavily modernized "under the hood" to work on 64bit Windows 10/11 only. And running VIDA in a VM is not recommended at all, even if it works. You can create a Windows To Go USB drive or stick with this tool and run VIDA from that, if you want to run a VIDA only environment.
Everything works exactly the same as all other versions of VIDA2014D. Just the VIN decoder is extended to recognize some P1s and P3s up to modelyear 2019.
The hardware requirements are slightly higher than for the original VIDA2014D as the SQL server is updated from SQL 2008 to SQL 2025. As well as a lot of other things that are replaced with more modern versions.
Of course software updates/reloads don't work like all other offline VIDAs.
The Installer made by ZaanTerror makes it really easy to install if you do a clean install btw.
Replacing an existing VIDA requires a little effort before you can install the new version. -
@T5-T6-Schnappi Hi,
I did a clean install and tried all the steps you suggested. I’m pretty sure the issue was actually on my side - I hadn’t manually filled in the dropdown lists for Transmission, Steering, and Body style.
I can’t be 100% certain if that was the only problem, because I ran out of patience and installed Windows 7, so I can’t confirm if it would have worked on Windows 10 - but I’m about 90% sure it would have.
Bit embarrassing how it turned out… anyway, thanks a lot for all your help.
-
I am having a weird issue on my laptop.(w11) I have installed here, Vida from @ZaanTerror and vdash, latest version.
if I start vdash, vida monitor crashes.
if i uninstall net framework 3.5 and then reinstall it, vida works perfectly, until i start Vdash again...any toughts ? anyone had the same issue? help ?
-
@sizan This is "normal". The same thing happens with the original VIDA2014D. VIDA will still work as long as VidaMonitor was fully started before it crashes. Just restart your computer after using Vdash to be sure that everything works as expected. The DICE and Mongoose drivers sometimes also get blocked after using Vdash until you reboot.
Nothing a reboot can't fix or to worry about.
