Thread: TD5 Defender help - Low power

Originally Posted by discopete

Have you tried a different ECU?

No I haven't. It drove okay before HG was done so I didn't think it would be ECU related

Originally Posted by nathanmac36

No I haven't. It drove okay before HG was done so I didn't think it would be ECU related

Probably not. It's just a possibility I'd eliminate from the equation if it were me.

Cheers, Peter

Originally Posted by discopete

Probably not. It's just a possibility I'd eliminate from the equation if it were me.

Cheers, Peter

You may be on to something here.
I got a nanocom yesterday and connected it to see if any sensors were dud and the ambient pressure was showing 90kPa. The transfer case High/Low switch was also showing that it was in LOW range when its definitely in high. I know the throttle response normally changes when in low range so it may be that the power isn't as bad as I think. Just that the throttle response is in low range.

Another spanner in the works is this morning I have no crank at all and the ECU is saying its immobilised. Yesterday it running fine while I was looking through the nanocom readings and now ECU immobilised and no crank...

Originally Posted by nathanmac36

You may be on to something here.
I got a nanocom yesterday and connected it to see if any sensors were dud and the ambient pressure was showing 90kPa. The transfer case High/Low switch was also showing that it was in LOW range when its definitely in high. I know the throttle response normally changes when in low range so it may be that the power isn't as bad as I think. Just that the throttle response is in low range.

Another spanner in the works is this morning I have no crank at all and the ECU is saying its immobilised. Yesterday it running fine while I was looking through the nanocom readings and now ECU immobilised and no crank...

Ambient pressure as in map sensor? Yeah that's a bit low unless you are at about 1000m above MSL,

The transfer case switch thing is PROBABLY showing incorrectly, it has been for some years with the Nanocom...and it's hard to explain why, I think it's more of a diagnostic term than an indication of the range selected.
I'm not sure it's been rectified in the latest firmware.

Best way to check would be with Nanocom hooked up and going between high and low range and see if it changes, if it does I'd say it's all working ok.

As to the immobilizer...Dunno much about them, AS10 is known to be problematic, try locking and unlocking again see what happens.

Cheers
James

Originally Posted by shack

Ambient pressure as in map sensor? Yeah that's a bit low unless you are at about 1000m above MSL,

The transfer case switch thing is PROBABLY showing incorrectly, it has been for some years with the Nanocom...and it's hard to explain why, I think it's more of a diagnostic term than an indication of the range selected.
I'm not sure it's been rectified in the latest firmware.

Best way to check would be with Nanocom hooked up and going between high and low range and see if it changes, if it does I'd say it's all working ok.

As to the immobilizer...Dunno much about them, AS10 is known to be problematic, try locking and unlocking again see what happens.

Cheers
James

Nanocom shows ambient pressure reading and manifold pressure as separate. The manifold pressure with ignition on but not running shows 102kpa which is correct for roughly 20m altitude.

I tried switching back and forth between high and low but there was no change to the nanocom reading saying it's in low range.

Problem with locking and unlocking is that I don't know if I have the original key and there is no FOB.
There was no central locking installed either so I'm not sure if the key would have even had a fob to mobilize the ECU.

Originally Posted by nathanmac36

Nanocom shows ambient pressure reading and manifold pressure as separate. The manifold pressure with ignition on but not running shows 102kpa which is correct for roughly 20m altitude.

I tried switching back and forth between high and low but there was no change to the nanocom reading saying it's in low range.

Problem with locking and unlocking is that I don't know if I have the original key and there is no FOB.
There was no central locking installed either so I'm not sure if the key would have even had a fob to mobilize the ECU.

Gotcha, you mean the sensor in the airbox, that should read roughly the same as the map sensor when the engine is off, if it doesn't you might have an issue.

On the key thing, I apologize,I was thinking more on the lines of the d2 which has a different setup.
You could unhook the battery and try again, but those AS10 ecu's have a bad rep for leaving people stranded.

Originally Posted by shack

Gotcha, you mean the sensor in the airbox, that should read roughly the same as the map sensor when the engine is off, if it doesn't you might have an issue.

On the key thing, I apologize,I was thinking more on the lines of the d2 which has a different setup.
You could unhook the battery and try again, but those AS10 ecu's have a bad rep for leaving people stranded.

I did try disconnecting the battery to no avail. I find it strange that it was running fine up until I connected the nanocom. The nanocom did have some issues connecting and communicating with the ECU at times.
Once the ECU is immobilised, does it have to be re-mobilised to then accept a security code from the 10AS?

Thanks for the help.

The ECU seems to be behaving a little strangely as shown by the Nanocom readings.

In view of your engine work, I would be carefully checking ALL earth connections - those to the engine and the ECU in particular.

Cheers,

Lionel