DICE / VIDA Shows Only Faults From PRIOR Tests Topic is solved

Post by **packetfire** » 03 Sep 2012, 11:08

So, I did battle with the completely undocumented "VIDA 2012A" package, and got it installed on a laptop by upgrading the laptop from Windows XP Home To Windows XP Pro. (The process took several attempts, and a manual re-install of the "IsoView" and "SQL Server" packages from internet downloads, as the packages on the CD was apparently mangled. Be warned.)

After fiddling about with the thing for an annoying period of time, I got the software to talk to the DICE interface, and ran a scan of the car. It found only two faults after 15 mins of connection at idle, but listed one of them multiple times under different possible symptoms:

FAULT: CEM-1C05 30-power supply Signal too low DTC is found not active.

EXPLAIN: Fault found by the DTC Test during previous operation cycle.
The DTC Test was not completed during current operation cycles.
The condition for completion is not fulfilled.

SYMPTOMS: (At top of each page of print-out for each line in test results)
Related to Starting, Engine hard to start/cranks slowly, Unsure when/at all times, AB
Related to Starting, Engine does not start, Unsure when/at all times, BJ
Related to Warning lights and chimes, Generator warning indication/no indication, HA
Related to Headlights, Bulbs blow frequently, LC
Related to Battery, Dead battery, LM
Related to Battery, Weak or low electrical power, LN
=======================

And

CEM-8F43 Relay, rear washer motor Signal too low DTC is found not active
No fault found by the DTC Test during current operation cycle but previously.
If possible, fulfill operational conditions where fault is active and can be found again.

SYMPTOMS: Related to Rear window washer, Does not work, EQ
=======================

So, how does one create the "condition for completion"?
And how does one "fulfill operational conditions where fault is active"?

Should I verify or clear the error in the rear washer by washing the rear windows while the DICE is connected?
The "power supply" issue has likely been fixed, as both battery and voltage regulator have been recently replaced.
So the question here is more "how to clear the old DTC"?

I guess I should consider myself lucky to have so few issues arising, but I hope someone has a user manual for DICE to explain how to really put a car through its paces and get a complete set of DTCs.

Post by **jimmy57** » 03 Sep 2012, 11:20

To get those to go away you have to go erase all DTC's and then go back a few screens and when the pop up shows up after profiling and selecting some action that says, ".....UPDATE........CANCEL...." Click UPDATE so VIDA re-reads everything.

The history of those codes will remain in VIDA for a long time so you will have a trace of them if you go back in much later unless you scan 40 other cars and the memory gets full and displaces those based on the allocation of memory for VIDA.

Operational conditions is whatever makes that function where fault was found operate. If you had low voltage and you happened to wash rear window then the CEM detected low voltage on the relay operating circuit.

Post by **packetfire** » 03 Sep 2012, 12:08

"you have to go erase all DTC's" - I guess I'm too "newbie", I saw no ability to erase anything. Just a list of the major symptoms, and an ability to look at each in detail.

Go back after profiling... is this where one used the DICE unit to "read the car", and get the VIN verified, or where one types in the VIN and selects the options.

Just for laughs, I sat in front of the car configuration screen and thought and though what "SR" and "Without SR" might mean for quite some time before realizing that they were talking about the "Sun Roof"!

Post by **jimmy57** » 03 Sep 2012, 14:24

Scroll the page to the bottom on the "DELIVERY" page and you'll see "ERASE" down at the bottom of the page.

underwood · Post by **underwood** » 13 Sep 2012, 10:34

packetfire, did you manage to clear the codes?
Looks like I'm in exactly the same situation - new owner of dice/vida, v. 2012A. Working on my S60 2002.
I got SRS light on. Check the Vida, it showed driver SIPS high resistance. Just to check the wiring from driver seat to SRS I shorted SIPS wires at the seat connector and Vida now showing both
SRS-0034 - SIPS resistance too high
AND
SRS-0035 - SIPS resistance too low.
After that I checked wiring under seat and found that orange airbag cable has some part of orange cover missing and it's taped with the same manufacturer's black insulation tape. I unwrapped it and found that one wire is torn... Have no clue why it was missing that orange coat in that place.
I repaired the wiring, followed Vida's procedure to erase codes, now the SRS module changed color from red to yellow on fault tracing view, but ALL these previous errors still there and the SRS light stays on.
I would understand that something is still wrong, but the low resistance error definitely was set when I shorten the wires for testing and it should not be there now...
Looks like I'm doing something wrong erasing the codes.
I tried to clear CEM module first, then SRS, tried to Erase All... Every time with starting, reving above 1500 stoping, sarting and idling for 20 secs... Still the same... All previous errors are there.
Am I missing something?
Any help will be greatly appreciated.

Post by **precopster** » 13 Sep 2012, 13:13

Did you actually pull apart the connector with the green/orange wires and reconnect? I had the same fault code due to Vida reading high resistance through this connector. Once I unplugged the connector and replugged (with battery disconnected, of course) the SRS code for drivers seat airbag was able to be cleared.

On my other '99 V70 I replaced the seat with an 850 power seat so in this case I had no connector on the seat so I replaced the connector with 3 x 10ohm 1/4 watt resistors and this got rid of the light as well.

Hope this helps.

Post by **packetfire** » 13 Sep 2012, 19:02

Underwood:

I am still too new to the DICE unit to claim any true expertise, but here's what I see:

What I did was go to "Diagnostics" tab, then 'Fault Trace" sub-tab.
Within that, I selected the "Unselected CSC" tab below the Car Network diagram.
Then I went to the drop-down list of faults found, and selected "Warning Lights and Chimes, Supplemental Restraint System (SRS) indication / no indication, KT".

In the box below, a list appeared:

(Yellow Light) SRS-0034 Side Impact protection (SIPS) bag, left front resistance too high
(Yellow Light) SRS-0105 Side impact protection (SIPS) bag, left front, Circuit fault
Checking the lamps and dials
Checking the SRS module

If you double-click on the fault items (in the list above, the first 2), You see an "Overview" page for that specific fault that shows you if you have really fixed the problem or not. In my case the "Current Operational Cycle"shows a Green Stoplight and a "Disturbance" factor of less than 30%. The "Previous Operational Cycle" will represent the results of prior tests.

From this page, you can click on a "Details" sub-sub tab at the top, or the amazingly good "Fault trace" at the bottom, which walks you through the repair process. The "details" sub-sub tab shows some items that may or may not be useful from the computer, but the important one is about if the fault was found during the current test cycle. In my case, it says "SI 04 Sporadic fault found at least once during current operation cycle YES".

So, this means that I have NOT fixed the fault yet.

The computer is keeping me honest, and refusing to clear the fault just because I say I have fixed it.
I clearly have not, and I need to check the cable, which means pulling apart the armrest to get at the SRS computer.

Once I have fixed it, I can then expect the clearing process you described (under the "Delvery" sub-sub tab) to really clear the error once I do the "on, 1500rpm, off, on, 20 secs of idle" process.

I'm interested that we both have the same fault with the same airbag connection. Are these seat airbag connectors perhaps corrosion-prone? I intend to clean mine with some solvent, and find some conductive grease to coat the connector pin.

Or is there a Volvo airbag connector cleaning process approved by the more expert members? I've been driving an 82 240 for 30 years, so this v70 is my first car with side-impact airbags of any sort.

underwood · Post by **underwood** » 13 Sep 2012, 19:48

Packetfire,
actually your idea make sense - so if something is still wrong, no previous codes will be erased. I did not think about it.
Because I expected that it would show current problems, not past.
Unfortunately can not check deeper right now - that's the daughter's car and now I need to catch her again to work on it

Current operational cycle was showing green light with <30% Disturbance but I did not click on anything else at that screen to get current fault.
Now I know and will try it as soon as I will get hands on that car, thank you.

Post by **packetfire** » 29 Oct 2016, 04:05

Just as a follow-up, in my case the SRS module was "bad", and simply could not be reset.
Lucky for me, a replacement was found that matched at a junkyard, and swapping the module made the codes go away.
So, if you think you have gone crazy, sometimes it IS the module.

Post by **abscate** » 19 Feb 2017, 05:38

precopster wrote:Did you actually pull apart the connector with the green/orange wires and reconnect? I had the same fault code due to Vida reading high resistance through this connector. Once I unplugged the connector and replugged (with battery disconnected, of course) the SRS code for drivers seat airbag was able to be cleared.

On my other '99 V70 I replaced the seat with an 850 power seat so in this case I had no connector on the seat so I replaced the connector with 3 x 10ohm 1/4 watt resistors and this got rid of the light as well.

Hope this helps.

Bumped to document SIPS resistor bypass 1999