I have a first-generation P2 V40, and VIDA and VCX Nano won't play ball with it (but still works on non-S40/V40 cars)

Apparently VIDA won't read VINs from S40/V40s, so they need to be entered manually, which was done. When heading to the Diagnostics tab, the "Verifying VIN" window that normally pops up instead simply flashes on the screen for a fraction of a second and nothing further happens.

In fact, VIDA can indeed connect to the car, because when selecting a profile for another car (an S60 which connects normally) just to try something different and then heading to the Diagnostics tab, the "Verifying VIN" window does pop up, and the "Communication with CEM", "Communication with DIM" etc. message does appear (afterwards complaining that "The connected vehicle is not the same as the specified vehicle.)

Image description

When first selecting "Read Vehicle" in the "Vehicle Profile" tab, VIDA notifies me that it cannot read VINs from S40/V40 cars ("VIN cannot be read out from this vehicle type"), so clearly it can connect to the car.

Image description

The V40 needs to have an airbag problem diagnosed.

Below is some diagnostic output from the logs. Do you have any ideas? Other people have this problem as well on their S40/V40 cars (as seen by searching for "VIN cannot be read out from this vehicle type." and V40 OR S40), but no one ever knew what the solution was, and no one ever reported back.

From VIDA.log:

VIDA release: VIDA2014D

20:43:19,372 [SoftwareProductI][001][Event] Database: DiagSwdlRepository, SP: GetSWDLSupportedVehicleModels

20:43:19,543 [DotNetPreLoader ][001][Info] PreLoad time: 00:00:01.5003894

20:43:45,527 [UiBase ][001][User] DIAGNOSTICS tab entered. VIN: YV1VW17K91FXXXXXX

20:43:45,574 [CarComRepository][001][Event] Database: CarCom, SP: vadis_GetHwSettings, VehicleProfile: 0b00c8af804cb2ca,0b00c8af8020663c,0b00c8af802068fd,0b00c8af802095a4,

20:43:45,918 [VehicleInformati][001][User] Activate VehicleInformationForm

20:43:45,996 [CarStatus ][00D][Info] Init CarStatus

20:43:46,075 [NavImageProvider][001][Info] Database: DiagSwdlRepository, SP: GetNavImage

20:43:46,121 [NavImageProvider][001][Event] Loading image 'http:\\localhost\Vida\Diagnostics\navimage\0800c8af81cfe671_0_0.cgm'

20:43:46,137 [VehicleInformati][001][User] Activate VehicleInformationForm

20:43:46,137 [CarStatus ][001][Info] Start reading CarStatus

20:43:46,137 [CarStatusWF ][001][Info] CarStatus read conditions not correct

Image description

Edit: Removed fluff that belonged in a separate whinging thread, which will get posted later in the appropriate place, because the whinging isn't over yet.

I couldn't get VIDA and VXDIAG working on my phase 2 V40. I ended up using VOL-FCR software with a cheap eBay cable. This works with phase 1 turbo models and all phase 2 models I believe.

Thank you, I have an ancient VAG-COM cable from my Mitsubishi Magna days. Will keep this thread updated with useful information, to assist future generations.

4 days later

Small update. VOL-FCR 1.7.6 will connect to the 2001 V40, read the engine computer just fine and even showed an error code, but returns "Invalid Data" when trying to read the error codes from the SRS ECU/computer, although it does connect (Comms Status OK).

Image description EMS ECU

Image description SRS ECU

Apparently (according to an experienced poster called "gatos" on another forum), one will need an Autel EU702 or the Volvo VCT2000 and VADIS to connect to the SRS ECU.
I'd rather spend big bucks on a proper scan tool than anything Volvo/Euro-specific or a mechanic.
Will update this thread in the future.

If anyone has scan tool suggestions, proven to work on the elusive 2001 V40 SRS ECU, please let me know.

I can imagine most of these cars having been made into fine cutlery by now, but am eager to get this problem fixed. The idiotically-flimsy side airbag wire connector below the seat was loose, that was all, but we'll see - maybe the ECU decided to brick itself just for giggles, like they do on other similar models.

Just a teaser: in a future post to come, I'll detail how I used epoxy to solve the infamous VVT plunger/piston oil leak that had spewed synthetic whale extract all over my beautiful new German-made timing belt.
Sure; there is the ordinary way to solve such problems, but why settle for ordinary when you can have extraordinary! More on that later.

Image description

My Vida with a genuine dice unit works perfectly.

I also have a VCT2000 with 2011A but haven't used it for 10 years.

There's no problem scanning it but I fit into the mechanic that you don't want to pay.

Success! To scan and clear the V40's DTCs I used an "app" named "850 OBD-II" from "xiaotec" https://xiaotec.fi/?lang=en&a=10 and the "OBD-II Engine Code Reader with Bluetooth® Technology" for $109 (but used to be 70) from Jaycar https://www.jaycar.com.au/obd-ii-engine-code-reader-with-bluetooth-technology/p/PP2145

Image description

The dongle from Altronics was a more basic model, and did not work in this case: https://www.altronics.com.au/p/x6015-bluetoothobdtwo-scanner-dongle/
I suspect that a lot of eBay dongles won't work either due to most of them being neutered clones that only work with the most basic of OBD commands.

Image description

Not endorsing the use of smartphones or "apps" here (no smartphones of mine have a SIM card), but in this case it worked and the car can be driven again without the SRS airbags being disabled.
Why the error codes were triggered in the first place might be due to the left impact sensor getting moist/corroded (haven't investigated yet) and the seat/buckle being put under great strain - the man who used to sit in the passenger seat of this car was… a very big and strong man with arms easily 7 times the circumference of mine.

Image description

I didn't know that a genuine DiCE unit would work and was under the impression that a VCT2000 was required, because I had seen posts from people who had used a DiCE unit complaining about this problem even before the VCX NANO was released, but it may have been a dodgy DiCE clone then.
In this case, I'll likely just purchase a proper DiCE unit next since Volvos (P1 and P2) will probably be the only cars for me into the future now.

You're a good guy Mike, my aversion to paying mechanics goes back to traumatic childhood experiences that I might share on here in a future whinging thread of mine.

For now, I'll make an offer that'll get a separate thread in the future: I will lend out my Bluetooth dongle and "smart"phone, or my VCX NANO and laptop for a day or so, to any genuine Volvo owner in SA who's had similar issues, at no cost. For now, this will likely mean dropping it off at your place or meeting publicly. In the future, I'll start posting them out to genuine people in OZ who will pay the postage/handling.

In other news, I'm getting closer to creating that "Epoxied VVT" thread, because the epoxy has been holding up well so far. There appears to be another much smaller oil leak from the VVT hub area though, but maybe even more epoxy will fix that one too. 😉
The S60's DIM is starting to play up, so the option of getting the car crushed into a cube is looking better again, but I'll try replacing it with a similar 2nd hand unit first, or maybe just reflowing the solder. We'll see.

© 2013-2023 Oz Volvo. All rights reserved. | Forum Rules | Privacy Policy