21 replies to this topic

[mqm]

After weeks of trying to sort out my VX when it suddenly decided not to start one day (see earlier posts), and with no ecu connection to help me, it looks as if it is the ecu that has decided to pack in.

 

Having stripped a lot of the loom searching for a broken wire, I'm just hoping it will be straight forward.

 

I've just checked out where to buy and ECUs to Go up near Middlesbrough seem to offer a good deal.  A brand new ecu, with an immobiliser and two transponders for the keys.  All programmed to your specific car.  Whole lot £250.

 

Has anyone used these guys before.  They seem to have excellent feedback on ebay.

 

I'll let you know how things go when I fit the ecu.  If anyone has any tips/recommendations on what to do when chaining the ecu etc, plea let me know.

 

I'm missing my old car and whilst she may getting a bit worn around the edges I do miss driving it even on the dreaded A14.

 

Mark

 

 

[The Batman]

Speak to Eliz p on here she will have a Vx ecu with chips and immobiliser a lot cheaper than that

[Wolfstone]

Are you absolutely sure its the ECU?  

 

As I think you know, I had the same problem.  Traced it eventually to a broken power wire to the ECU near one of the big connectors behind the expansion tank bracket.  Access is best with the n/s/r wheel off and arch liner out.  The broken wire was very hard to spot and was only identified by a pinprick of copper corrosion on the sleeve, which when scraped away revealed a broken wire.  

[mqm]

Wolfstone

 

I have had all the loom undone and checked the connectors, but can't find any fault.  I am getting power to the ecu (ignition off and on) and I am getting a signal between the immobiliser and the ecu.  Going by TIS I need a new ecu or immobiliser.

 

Still no communication from the ecu to the code reader or the Op-Com.  It will start occassionally and it will link with the code reader occassionally that's why I though dodgy connection.  But it seems that it might just be the ecu playing up.

 

Mark

[fezzasus]

TIS was written before the cars aged so won't suggest damaged loom connectors. I'm aware Badgerade went for ITBs because his loom was badly damaged and couldn't talk to the ECU, so it is a known problem.

[siztenboots]

does the NA ecu have the same annoying security bolt that , bugger to get access to drill out. Thats one of the reasons I won't do map updates away from the workshop as you really don't want to leave someone with a corrupt ecu.

[badgerade]

 I'm aware Badgerade went for ITBs because his loom was badly damaged and couldn't talk to the ECU, so it is a known problem.

 

 

It was the ECU pins that were dead/missing on mine.  This arrived at a convenient time when I had some money, Thorney had a very large pricing error on their website for the ITB kit and my wife believed me when I told her it would be the only money I'd be spending on the car

[fezzasus]

does the NA ecu have the same annoying security bolt that , bugger to get access to drill out. Thats one of the reasons I won't do map updates away from the workshop as you really don't want to leave someone with a corrupt ecu.

 

Yup.

[mqm]

If you have a Dremmel with a circular saw try using that to cut a slot in the bolt. 

 

The bolt is countersunk and from the looks of it cutting a slot into it would have been far easier than trying to drill out a steel bolt stuck in alloy as the drill just goes into the softer material.  Mine got quite messy and the hole bigger and bigger!

 

Mark

[fezzasus]

I just took the boot lid off and drilled it out when i send my ECU off.

[mqm]

Eureka!

 

VX is running at last following replacement of the ecu.

 

Had the OP-COM on it and it has a few fault codes which may be sorted once I finish putting it all back together.  That won't be until the weekend.  

 

At first it wouldn't even turn over following the replacement, but that turned out to be just a flat battery!

 

Fault codes that I have are:

U2100 - CAN-Bus Malfunction

 (04) - Present

 

U2108 - CAN-Bus no Communication with ABS/TC

 (04) - Present

 

P1490 - Auxiliary Cooling Pump Relay Open Circuit

 (04) - Present

 

P0130 - O2 Sensor Circuit Malfunction (Bank 1 Sensor 1)

 (08) - Intermittent

 

I know that the P1490 has been present for years as the dealers found that about 5 years ago when it was last put on the Tech2.  My code reader does not find this code for some reason, so this one probably does need sorting.

 

Mark

 

[techieboy]

Needs to go back to the dealer to be reflashed with a VXT configuration and map and not the Astra setup, or whatever that is.

[G-Bob]

Yup....thats an astra map.

I had similar issues when I put an astra one on mine.  EML came on because it couldn't find the Traction Control.

[mqm]

Ecustogo said they had flashed this brand new ecu specifically for my Vx. I assume it will have all the appropriate maps etc. I'll double check with them to make sure. I am confused with the can bus reference as I understood that the Vx didn't have the can bus system. However I see others on the forum have had similar fault codes using op com. Going er wrap the loom and fix it all back I place then take it for a gentle test run. hope the weather improves Mark

[techieboy]

It's not the right map for the VX. It's looking for a CAN connection and traction control which are not included in the VX's configuration, so it's the firmware/map for the wrong car but right (hopefully) engine.

[slindborg]

rage, rage, rage, then less rage from Matt

[siztenboots]

this is the original VXT file then need

 

https://www.dropbox....370cc-11psi.bin

[mqm]

Ok I'm confused (I know that is easy) because if you search for can bus on the forum you get 81 results. Is it the can bus fault that indicates it is an Astra map? If so there's a lot of people with VXs with Astra maps or there's a lot of Astra owners on the site. Haven't had a response so will chase ecustogo. If I do need to sort out the mapping is it main dealer only job? Mark

[Bargi]

It's not the right map for the VX. It's looking for a CAN connection and traction control which are not included in the VX's configuration, so it's the firmware/map for the wrong car but right (hopefully) engine.

 

As above, the map part for the engine is probably OK, but it's looking for extra CABbus bits that don't exist on the VX.

You need to send it back and for them to load the VX specific map. Give them the error codes you're seeing and what they mean and explain there is no CANbus.

Worst case send them the link Siztenboots and have them load that onto it.

Failing all that send it Sizten and buy him a scotch

Edited by Bargi, 15 February 2014 - 12:45 PM.

[siztenboots]

a bit closer Matt Bentley can do it, I've given him the files ,