2004 V70 Software problem - CEM/Nothing Works, my fault

[marshallh]

Car was doing great, until I got my DiCE today.
Played around for a while, reading stats, great fun.


1. I clicked "purchase" for the remote control software. My DIM went blank and there was tons of relays clicking. I shut everything off and disconnected DICE.

2. Everything was dead. However, I could still start engine. CD player continued playing.
DIM was completely blank. Turn signals don't work, nor anything else like windows, locks, headlights, etc..

3. After about 10 minutes the DIM started working again, showing SRS URGENT SERVICE. All gauges work properly. Temperate shows "---". Nothing else is working.

4. After 30 more minutes nothing has changed. I can't legally drive this anywhere.

Diagnostics reports the CEM can't talk to several modules.



What should I do next? I would reset the battery except I can't unlock the hatch to get to the battery!!

Major facepalm!

[marshallh]

UPDATE

After unhooking the battery and shunting thru a 1k resistor, re-connected with ignition in II position and everything seems to be working again. Whew.

I still have the SRS URGENT SERVICE code. Is this something I can/should clear with VIDA? I don't want to screw something else up.

[jimmy57]

You interrupted the normal program mode where VIDA goes in and interrogates all the modules and gathers software numbers.
The PROG command is sent to all modules and they stop normal function so the network can be used for communication with Dice instead of the normal messages. When that phase is over the RESET command is sent and everyhting goes back to normal. Since you didn't dump any software you had a recoverable condition. Abruptly exiting can be catastrphic. You are lucky.

Establish communication again, then once it reads everything click the FAULT TRACING tab and then you'll have initial state, unselected CSC, selected CSC, and another one I can't remember.

scroll to the bottom of the panel with the fault codes and click ERASE FAULt CODES

If you look at that lengthy list you will find all sorts of communication codes including one or more for the SRS.

[marshallh]

jimm57 thanks for that explanation. I figured that was happening (modules entering debug mode basically) but didn't know what I was getting into. And lucky I wasn't doing something that was writing NVRAM in some module at the time.

Is there anything else I should be very cautious of doing with VIDA that is not obvious?


I had several existing codes from about 30k miles previous, that were 1-5 occurences, 800 cycles ago. Stuff like the seat memory taking too long, lost communications with some modules 40k miles ago etc
Should I leave these, or clear them? And are they worth bothering with? They all smelled like intermittent/bad connections to me. History now.