Hmm see a pattern is definitely forming...Your solutions seem to contain..Quote:
Originally Posted by Slunnie
Cutting
Sawing
Grinding
Gas axe
Tin Snips
:wasntme:
VERY tongue in cheek and shouldnt be taken as criticism, just humour...
Printable View
Hmm see a pattern is definitely forming...Your solutions seem to contain..Quote:
Originally Posted by Slunnie
Cutting
Sawing
Grinding
Gas axe
Tin Snips
:wasntme:
VERY tongue in cheek and shouldnt be taken as criticism, just humour...
How about fire???
A good inferno should sort it!!!
Andrew
Probably faster than finding the source of the problem, ...............and a permanent fix too !Quote:
Originally Posted by Slunnie
Hopefully you won't need that chime speaker for something more important. ( like a ' no oil ' warning )
I have had problems where the "write" to the BCU after changing settings seems to occasionally get interrrupted (communication error) and in that case some settings end up in their default state. I always record ALL the BCU settings before making any changes then check them ALL after the "write" procedure.
Cheers
There are actually different versions of the BCU, with subtly different memory maps.
And in fact IIRC the seat belt option value in one produces quite a different effect if directly re written in the other or written back without all it's bits intact.
For the technically minded i will try to explain this a bit better.
In the early versions of BCU, just 2 binary bits were used for the seat belt warning, giving 4 possible settings, however in later versions, some market legislation or other determined more options were needed and so the bits used was increased to 3, and the memory re shuffled to accommodate this. However the lower 2 bits were not functionally re mapped as per its predecessor. You gotta love LR logic :(
If you use equipment that is not capable of detecting the difference in BCU version and acting accordingly, you can end up reading in and restoring only 2 of the 3 required bits, thus producing such effects and vice versa.
I know from experience that a lot of equipment has been produced by copying another. Hey thats life and business, unfortunately however this short cut often means such detail and understanding can so easily be lost. Any copier of our system, may not for example have figured that on a Version 7 BCU our system provides just 4 options and on a version 8 or greater you actually get more options.
BTW, i believe the layman way to determine the BCU Version is to count the number of sweeps made on the rear wiper in once activation mode.
There was an update BCU action which when done was supposed to be denoted by a paint dab being applied to the head of a securing bolt, but i also understand that a lot of dealers chose not do this because the later BCU had slightly different diagnostic communication timing and the TestBook simply could not communicate with the new version ECU. I really do not know if this was ever sorted out but have learned to give the old TB a very wide berth.
I should perhaps add that if you use version 7 BCU data to write into a version 8 BCU with our equipment, we automatically re work the 3 bits to achieve the required result. If you do the opposite, as long as its a supported option, we re work the bits accordingly, else we advise it's an invalid and un supported option.
Hi Simon,Quote:
Originally Posted by Slunnie
It is part of the BCU & wired onto the PCB for this control unit;)
Cheers
Thanks Pete, its sounding like Angus probably shouldn't cut the wires! :DQuote:
Originally Posted by sniegy