Thread: intermittent battery light on puma

Check all the fuses and relays under the driver's seat.

Hi guys ive git the same problem taco dead battery light on temp goes to full
I havent got a scangauge hooked up
This seems to be quite a random problem
Also when this happens fender seems to go into limp mode no go
Any idea s would be helpfull all my earths seem ok
Need to get this sorted as we off to the kimberliies soon
Thanks

Originally Posted by 2dae

Hi guys ive git the same problem taco dead battery light on temp goes to full
I havent got a scangauge hooked up
This seems to be quite a random problem
Also when this happens fender seems to go into limp mode no go
Any idea s would be helpfull all my earths seem ok
Need to get this sorted as we off to the kimberliies soon
Thanks

Something is causing the logic circuits to latch up? Sounds like intermittent stray currents and poor earth's to me.

Go through each earth point ( black wires ) in turn, solder the lugs to the wires, then making sure for where the lugs fasten onto the body or chassis there is 'bright' metal to metal contact, after cleaning any paint or corrosion add some copper coat between the surfaces and then seal over the joints with grease or chassis paint, both are good.

It doesn't need much resistance to upset a low current circuit, the path to earth could then be via a light bulb or a relay coil.
.

@2dae, do you you use a remap interface, scangauge or any type of tool that is plugged into the OBDII socket? I have had the battery light come on and the rev counter drop to zero the odd time in the past, usually after either putting on a remap file or when using a nanocom evo mk1. Before I change any map file I check and save any DTC's logged before resetting them, that way the PCM/IPAC modules are clear of any DTC's before I write a new fuelling file onto the PCM with the remap interface. After the writing process has finished I rescan the modules for DTC's and clear the lost communication DTC's. Once in the past I remember putting on the remap file after leaving the dealers only for the battery light to come on, temp gauge into red and the Puma to enter limp mode. I pulled over and as I carry a scan tool checked the PCM/IPAC for logged DTC's using a MSV2 and found the following tested/untested dtc's even though the fault code history was cleared after writing the new fuel file.

Tested DTC's


Untested DTC's.


So the above fault codes explained the limp mode and what I was seeing on the IPAC so I saved them and then cleared them with no further re occurrences of the problem. The other times I have seen the battery light and rev counter go to zero was on my mates 08 plate Puma when ever I used the nanocom to check for DTC's. No issues using the tools functions however 90% of the time after shutting off the ignition and removing the OBD plug then reenergizing the ignition circuit the battery light would come on and the temp gauge would shoot up into the red? Which is a common sight when the alien tech remap interface was writing a remap file to the PCM. SO a quick check of the logged DTC's showed the following codes:

NANOCOM - PUMAENG.APP - PUMA ENGINE fault file

C001 - 88
High Speed CAN Communication Bus

---
1643 - 87
Controller area network (CAN) link engine
control module/transmission control
module circuit/network

---
0606 - 49
Engine control module (ECM) processor

internal
electronic failure

---
068A - 00
Engine control module (ECM) power
relay deenergized - too early

---

Again I saved them then reset them. Once the DTC's were cleared the IPAC returned to normal.

So what was the cause of the issue? On my Puma it was the OBDII socket which I replaced and moved a couple of years ago, and have since then never had the issue. My mate changed his OBD socket but still occasionally gets the temp needle into the red when using certain tools that plug into the OBD socket. Also a point worth noting is that the MSV, IDS, ultragauge, scangauge and Autel units I use regularly have never given any of the above symptoms, only the remap interface and nanocom evo mk1.

HTH Brian.

No i havent got a scan/ ultra gauge in the vechile
Only have a stienbeur chip
Recently had a earth drama took a bit to track the fault
During the track i removed the dash /insrtument cluster
I removed it again to check the plug on the back of the instrament cluster noticed that the wireing loom has a channel that it sits into it seemed to be sitting across it , maybe kinking the connector making maybe a bad connection
Went for a six hour drive on sunday gone fendr drove well no prob will keep an eye on it
2dae out