urs4 ecu (vems) losing connection to computer

[euro_urs4]

I have been having problems with the connection from my ecu to the labtop, or in general the car is losing connection to the ecu and shutting of. I have ls2 coils with magnacore wires, Vems ecu, etc (if more info needed let me know),

Now the problem I am having is that when I start the car it will run for 3-4 minutes then shut of all of a sudden, but then I will start it and it will stay running for a while and I can go for a drive, then it will occasionally happen while driving, where out of no where it will just shut of. This all started happening after I loaded the new firmware onto vems (ever since had some tuning issues with idle), however right after loading the new firmware this problem has started.

Yesterday I noticed that fuse holder s64, http://forums.quattroworld.com/s4s6/msgs/137287.phtml was burnt out, this was the first time that this has happened, (this occured while driving), every other time that the car shut of it hasn't burnt out, I checked the resistance on the fuse holder, and the 2, three prong white female connectors in the engine bay, and they checked out at 0. (so my assumption is that there is a bare wire possibly touching somewhere), yet I still don't get my chances of this occurring right after the new firmware was loaded on.

Any thoughts and opinions, or ways to approach this would be great thanks in advance.

[UrS4boy]

I suggested before that you need to connect to a LAPtop, not a LABtop.

[kamuto]

I have been having problems with the connection from my ecu to the labtop, or in general the car is losing connection to the ecu and shutting of. I have ls2 coils with magnacore wires, Vems ecu, etc (if more info needed let me know),

Now the problem I am having is that when I start the car it will run for 3-4 minutes then shut of all of a sudden, but then I will start it and it will stay running for a while and I can go for a drive, then it will occasionally happen while driving, where out of no where it will just shut of. This all started happening after I loaded the new firmware onto vems (ever since had some tuning issues with idle), however right after loading the new firmware this problem has started.

Yesterday I noticed that fuse holder s64, http://forums.quattroworld.com/s4s6/msgs/137287.phtml was burnt out, this was the first time that this has happened, (this occured while driving), every other time that the car shut of it hasn't burnt out, I checked the resistance on the fuse holder, and the 2, three prong white female connectors in the engine bay, and they checked out at 0. (so my assumption is that there is a bare wire possibly touching somewhere), yet I still don't get my chances of this occurring right after the new firmware was loaded on.

Any thoughts and opinions, or ways to approach this would be great thanks in advance.

start it, connect laptop with highest serial speed, enable trigger log and leave it until it shuts off

[Ruffiano]

I had a similar problem. Check your ground wires.

[euro_urs4]

start it, connect laptop with highest serial speed, enable trigger log and leave it until it shuts off

Could you explain how to set the highest serial speed ? Is this done on the ecu tab on the front page , and what's the purpose of the highest speed ?

[euro_urs4]

I had a similar problem. Check your ground wires.

was yours also blowing the fuse sometimes? or was it just losing connection to the ecu? (and im guessing your problem was the ground wire?)

[Ruffiano]

was yours also blowing the fuse sometimes? or was it just losing connection to the ecu? (and im guessing your problem was the ground wire?)

yeah it was cutting out randomly and those cut outs would also kill the connection to the laptop.

[euro_urs4]

yeah it was cutting out randomly and those cut outs would also kill the connection to the laptop.

good to know thanks, ill have to look at my grounds tonight. thanks

[euro_urs4]

thought i'd update everyone, so maybe this could help someone in the future, I found out my problem wasn't an electrical issue, came down to being an updated firmware issue on vems that was acting up, switched back to the old firmware and tune and runs fine (had a feeling it was the firmware issue).

[a4kquattro]

1.2.6, for reference. I've submitted an error report to VEMS on it.

[Billman]

good find! any issues on the 1.2.10?