When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I suddenly got a B1342 aka "death code" on my VSM today, weird thing is that everything still works normally, door locks, lights, everything. I reset the code and it did not come back so far, but will have to drive a few days to see if it will come back or not.
Is there anyone who knows what fails in them that causes the B1342 to be set? Is it hardware failure or software failure? Everywhere I see info about this, it simply says "replace the module", "this is a death code, no cure, replace module", but nothing about specifically what happens internally which makes the module report its untimely demise.... Would it be possible to repair a module with this code, or is it the main system chips that fail?
Thanks, that pertains to the Restraints Control Module though, but it said one of the faults could be calibration issue, I do have the tools to reprogram the module so might attempt that if it pops up again. And then it said rail failure to ASIC, which means the system chips aren't getting power. If the 3.3V or 5V (assuming standard electronic rails are used) rails are having issues, this may potentially be an easy problem to fix. The biggest problem in that regard is that there's no internal wiring diagram available for these modules..
I saw that, the problem is that the VSM threw B1342_20, which was not covered in that TSB, and I haven't had any luck in finding any chart which contains it either. I have the shop manual here, both hard copy and the electronic DVD one, but they don't specify the DTC other than "B1342 - Fault in module, replace module".
I'm not gonna replace the module until I know it really is dead, and I've checked it internally and not been able to find the fault in it. At the moment, all the systems are still working so it must be doing what it's supposed to be doing...
Is there anyone who knows what fails in them that causes the B1342 to be set? Is it hardware failure or software failure?
.
.
.Would it be possible to repair a module with this code, or is it the main system chips that fail?
Could be a little bit of hardware or software failure.
When the ignition key is turned to "ON", the EBCM goes through a self check. I don't know just how it does this self check but I think of it as a cycle redundancy check of the NVRAM (that's the non-volatile random access memory) looking to see if it lost or gained a bit or two.
If it doesn't like what it found it sets the B1342. The next time the key is turned to "ON", perhaps it could pass? I don't know.
(BTW, we just pulled the EBCM off the ABS module on a 2000 Expy 2 days ago for a similar issue.)
It might be worth it to talk to someone that repairs these modules. Some are just prepared to replace the MOSFET relay on the Kelsey-Hayse modules where the ABS pump motor runs continually. Some seem to be more willing to branch out into other areas of the EBCM.
Here's one I just came across. (I don't know anything about them and are not recommending them).
A new VSM is gonna run me 200 bucks plus shipping, could perhaps find a used one for around half of that. Before I fork out for a new one, I will confirm that this one is dead and at least attempt a reprogramming of it. I'd think that if the module really is dead, I would notice that some systems were behaving erratically or not functioning, I'm thinking this must have been a weird code being set for some unknown reason, so far it did not come back on.
So far so good, it must have been a hiccup or something. Perhaps a voltage drop freaked it out or something, I did do some tailgating with the dome lights on for a while. Anyway, as long as the code doesn't come back, then I will assume it's working as it should. Will post back if it comes back, but for now I'll consider this a non-issue.
Well, the VSM again threw the B1342 today, but instead of B1342_20 as before, it was now B1342_0F. And I can still not find any chart or table that explains that subcode on the DTC for the VSM.. All systems still work, the only thing that doesn't work at the moment is the TPMS system, but that is due to 3 of 4 tire sensors being bad. Gonna replace the sensors next time I'm changing tires, which is soon.
Because if the DTC tells me what has failed inside the VSM, then it could be as easy as replacing a couple of caps on the voltage rail or similar and I would be able to repair it for a few bucks, rather than buying a whole new one at 200 bucks plus shipping... It baffles me that the VSM is saying it's defective when all systems still works.. I would think I would see some systems failing if it was truly dead...
Been reading up on it a bit, and from what I'm seeing is that the error I am getting on the TPMS is consistent with "No communication between instrument cluster and TPMS module". Blinking TPMS indicator for 5 seconds after key on and "Tire pressure sensor fail" in message center. Weird thing is that the Ford dealer here told me it was due to 3 of 4 sensors having failed, so I have new ones here waiting for when I buy new tires. Since the TPMS module is integral in the VSM, my theory then is that the TPMS system in it has failed, while the rest of it is still working. I don't know how modular the module is, but I'm planning to pull it out of the truck tomorrow and have a look, measure some voltages and see if I can find any issues with the hardware. If that checks out, then chances are that there's a problem with an EEPROM or NVRAM, whatever it uses, which needs a JTAG to reflash it, and that's beyond my capabilities since I don't have access to the binary files for it. Could try to reprogram it with the VCM, but I doubt that goes as deep as the EEPROM/NVRAM.
Because if the DTC tells me what has failed inside the VSM, then it could be as easy as replacing a couple of caps on the voltage rail or similar and I would be able to repair it for a few bucks
You know it's never that simple. Yes the problem could point to a couple of caps, but is it really a bad cap or is the PC board cracked, or is it a broken solder joint, or is it a related component in the same circuit as the caps, etc. I'm all for trying to repair things, but even I think twice about digging into an ECM just because of their complexity and the special diagnostic equipment needed to work on them. To me it's like playing handball against the drapes...a whole lot of effort without much promise of a result.
I know.. But I'll try. Given my previous profession and my qualifications, a hardware issue on one of these like a bad cap or two or a crack in the PCB would be a fairly easy fix, just a little more time consuming than just popping a new module in. But if I can't find any hardware issue, then the error is with in the software, something in the base firmware that is not touched by the programming procedure with the VCM and that is not something I can fix, since I'll never be able to obtain the binary files from Ford in order to perform a reflash through JTAG on it. In that case, I'll have to get a new one. Found one for 66 dollars on ebay (just have to confirm part number) which refuses to send to the Philippines... (hint hint)
Pulled the VSM and inspected it today, no obvious issues inside but there was a riser board. I immediately suspected the solder joints on the riser board, years of vibrations could cause micro fractures in the joints, this would fit with the intermittent nature of the DTC. I re-soldered these, reassembled it and put it back into the truck. Ran several self tests with Ford IDS and a Ford VCM, and did not get any DTC's from the module. I'm hoping this did the trick, but have to wait and see if it pops up again after a few days like last time.. Here's some pictures of the module.
At the moment, all the systems are still working so it must be doing what it's supposed to be doing...
