Key fob remote failing - fixable?

[vitesse]

Originally Posted by hogweed

Thanks Alan... -43 is the one that's supposed to do keys, but trouble is, both versions say the BCU isn't present.



I don't have any BCU malfunctions, as far as I know - everything in the car seems to work...

Sounds like a connection issue, sometimes if Toaf doesn't get as far as displaying the various modules with VIN mileage, you need to switch off and start again.

I can confirm ver 43 is the right one, used it several times with keyfobs.

Or a Windows issue, I've never tried to assign communication ports (as I don't understand Windows) I just let the machine do it and somehow it seems to choose the right one.

Regards

[hogweed]

Originally Posted by vitesse

Sounds like a connection issue, sometimes if Toaf doesn't get as far as displaying the various modules with VIN mileage, you need to switch off and start again.

I can confirm ver 43 is the right one, used it several times with keyfobs.

Or a Windows issue, I've never tried to assign communication ports (as I don't understand Windows) I just let the machine do it and somehow it seems to choose the right one.

Regards

Yeah cheers, not sure about that though as I can read engine errors etc. I'm guessing if it can do that, it's connected

[vitesse]

Yes, if what I've just read is correct, you are connected and Toaf is reading your engine module on pin 7 (and SRS) all the other modules are on pin 8, so if the engine is the only module you can get in to then double check the soldering between pins 7 & 8 (or just bridge them with some fuse wire).

Regards

[hogweed]

Originally Posted by vitesse

Yes, if what I've just read is correct, you are connected and Toaf is reading your engine module on pin 7 (and SRS) all the other modules are on pin 8, so if the engine is the only module you can get in to then double check the soldering between pins 7 & 8 (or just bridge them with some fuse wire).

Regards

OK, will check that, thanks. But I *THINK* I looked at the LSM, too... will report back.


{EDIT} - yes, solid connection from 7 to 8.


This project is the gift that just keeps on giving... got the spare blank cut, tried it in the door, it went most of the way in then jammed. When I tried to pull it out, the fob came off the blade, leaving it stuck solid in the lock.


Good thing I was able to drive it home like that and pull it out with pliers. Now I'm going to have to go back down and have an argument with the "locksmith" (Timpson's, if anybody is thinking of avoiding them).

[vitesse]

You are having fun ... to be fair though and I've done a fair few, I find it's a balance between perhaps later being able to pull the key out of the holder = standard general purpose adhesive or cutting the holder free from the fob = superglue.

Regards

[hogweed]

Originally Posted by vitesse

You are having fun ... to be fair though and I've done a fair few, I find it's a balance between perhaps later being able to pull the key out of the holder = standard general purpose adhesive or cutting the holder free from the fob = superglue.

Regards

Ooh... are they relatively easy to pull out then? I thought I just had a dodgy one...



Anyway, I'm charging up my old W7 machine, see if it works any better on that. W10 is inherently {naughty word} anyway.


PS I have a fair understanding of Windows, and do know how to do things like enumerate serial ports, so if you ever need a hand with general Windows stuff...

[vitesse]

Yes some are relatively easy, that's why Brian's tea, hot water works, others I've found which have been superglued are almost impossible and I usually end up cutting through the softer fob plastic until I get to the harder plastic holder.

I've got two machines with Toaf, an XP and a Win10. The XP has a serial (RS232) lead and in my opinion the better choice, 100% reliable, the Win10 machine has a USB lead and is fussy at times, requiring me to switch off and reconnect before working properly. Only reason I got the Win10 was my 2003 needs Vista or higher to read the SRS system and with my Windows "skills" I didn't want to mess things up.

Might sometime take you up on your offer, as a very long term Mac user I have no idea what "enumerate serial ports" means, Mac stuff just works

Regards

[hogweed]

Originally Posted by vitesse

Mac stuff just works

Well, we'd better not get into that old argument as a retired IT Manager, from my perspective it would be "Mac stuff just DOESN'T work, so no point in even trying..."


I'm really at a loss now, as I'm having exactly the same results with my W7 machine. BCU is "absent"; if I try to read the LSM, it gets half way then crashes with an access violation.


Now, on this machine, I've used the driver supplied with the lead, as the one on the TOAF site won't install, whereas on my W10 laptop, I let Windows use its own drivers. Exactly the same result...


So 2 different machines; 2 different operating systems; 2 different drivers. So I'm beginning to think maybe the lead is faulty, but no way of testing it of course.

[hogweed]

OK, so in increasing desperation, I decided to re-solder the 7-8 connection anyway, and it didn’t make any difference. But having clicked on lots of modules, they all seem to be “absent” except (a) the engine, (b) the LCM – but looking at the LCM causes TOAF to crash irretrievably with that access violation.


Maybe this lead isn't suitable after all…?

[clf]

Originally Posted by hogweed

OK, so in increasing desperation, I decided to re-solder the 7-8 connection anyway, and it didn’t make any difference. But having clicked on lots of modules, they all seem to be “absent” except (a) the engine, (b) the LCM – but looking at the LCM causes TOAF to crash irretrievably with that access violation.


Maybe this lead isn't suitable after all…?

Roger, have you tried the earlier and later versions of toaf to see if either reads the bcu (I know they wont do the keys). Then perhaps if they do, remove and re install the version you are using, in case it is a corruption?

Sent from my SM-A600FN using Tapatalk