VIDA 2014D/2015A Windows 11
-
@ilonapshe No selection of the diag tool usually means you are not running VIDA in Internet Explorer or Edge with IE Mode.
Do see the IE logo when VIDA is open?
-
@T5-T6-Schnappi Yes, it doesn’t matter, if I go into VIDA through IE, Edge with mode or through VIDA monitor. Got screenshots from all 3.
IE:
Edge with mode:
VIDA monitor at the bottom on the panel:
-
-
@T5-T6-Schnappi okay, thanks. Gonna see what i can do
-
Thank you again ZaanTerror, I got the VIDA software working on my windows 11 with a clone mongoose scanner, but I think there's only 2 things that I would probably change because it took me a while to get it running, maybe add a step by step install guide (I know we just need to run the setup.exe, but it didn't work out for me) and possible fixes if something doesnt work like it should (in a .txt file)? I had some problems with my java, SQL and with the login screen saying the language I had installed didn't match the language I was trying to login with, but i was selecting all the right stuff, in the end I did manage to fix everything with the help of ChatGPT, maybe if I had installed it in a fresh windows it would've went just fine, but since mine and probably most people downloading it isn't I guess it would've been probably easier if there were some guide in fixing common errors or whatever, but thanks a lot again!
-
@Eros Install guides in english and german for clean installs can be found here
If you have any useful additions just let me know them.If you want to replace an existing VIDA2014D installation, you need to fully remove that first. You have to stop and close VidaMonitor; stop all running SQL services; uninstall VIDA, Isoview, everything with SQL in it's name; reboot your computer; manually remove all folders containing the terms VIDA, Volvo, Ford, Isoview, SQL, Arbortext, also those that are hidden in various locations; check the Registry for leftovers and also delete them; reboot the computer again; then start ZaanTerrors Installer. Maybe I will write guide for this when I find the time and motivation to do it and add it to the install guides.
As a golden rule you shouldn't use your everyday computer for VIDA. It's better to use a dedicated machine for VIDA or create a Windows 2 Go USB drive and run VIDA from that, when your computer is already cluttered with all kinds of installed software.
The more stuff you have installed besides VIDA, the more things can and will interfere with it. Especially 3rd party antivirus/security softwares and the damages done to Windows by so called optimization/tuning softwares could give you a hard time trying to get VIDA up and running. -
-
-
-
@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.
