CwazyWabbit
-
Posts
7,222 -
Joined
-
Last visited
-
Days Won
30
Content Type
Profiles
Forums
Events
Gallery
Blogs
Posts posted by CwazyWabbit
-
-
The following thread, if I'm reading it correctly says the bellhousings are the same though for 300TDI R380 Disco and Defender.
-
I'm fairly sure the shifter housing is in a different position on a Disco R380 compared to a Defender one, even if the bellhousing is the same length. Changing it required a gearbox disassmble/reassemble operation too I think
Yep shifter is located much further back on a Disco box, would end up somewhere in the cubby box on a Defender ....
-
0x0DF1 -- 0xB4FF
.
.
.
0x0DC1 -- 0x84FF
0x0DCO -- 0x83FF
0x0DBF -- 0xFEFF
0x0DBE -- 0xFDFF
0x0DBD -- 0x00FF
0x0DBC -- 0xFFFF
.
.
.
.
0x0DAD -- 0xF0FF
0x0DAC -- 0xEFFF
.
.
.
0x0D00 -- 0x43FF
-
Mine has no cowling, but then it also has no viscous fan either. (Electric fitted).
Has been that way for 3 years now without issue, vast amounts of space to work stand in the engine bay
-
Sorry for the late reply I got carried away trying to automate some stuff, there are now relays and switches all over the place connecting the speedo to the PC
0x300C -- 0x74FF works
but neither of the others do
I just got the 0x4010 if thats any help with your theory?
0x40E0 -- 0xF0FF
.
.
.
0x4080 -- 0x90FF
.
.
.
0x4010 -- 0x20FF
.
.
.
0x4000 -- 0x10FF
Cheers for the help
... remind me to never play cards with you for money 
-
Ok, I think I've spotted something. Try these then:
either both of these will work
0x300C -- 0x74FF
0x4010 -- 0x80FF
or this pair will work
0x4010 -- 0x70FF
Kev
Sorry for the late reply I got carried away trying to automate some stuff, there are now relays and switches all over the place connecting the speedo to the PC
0x300C -- 0x74FF works
but neither of the others do
-
Some new ones for you MrKev including the 0x2008 you asked for
obviously I slipped up the first time I looked for it 
0x206F--0x01FF
.
.
.
0x2008--0x68FF
0x2007--0x69FF
0x2000--0x70FF
0x105F--0x01FF
0x105E--0x02FF
.
.
.
0x1006--0x5AFF
0x1005--0x5BFF
0x1004--0x5CFF
.
.
.
0x1000--0x60FF
0x0FFF--0xC0FF
0x09F5--0xB4FF
0x09F4--0xB3FF
0x0847--0x01FF
.
.
.
0x0804--0x44FF
0x0803--0x45FF
0x0802--0x46FF
0x0801--0x47FF
0x0800--0x48FF
The current list of known pairs (three full stops indicate I'm to lazy to write them all in), those in bold are new pairs.
For those of you reading in decimal
we can now program the following pulses per mile (well actually it's per unit as the speedo has no concept of miles or km, it just counts the pulses)2048 to 2119
2548 to 2549 <--- 2548 is the factory set pulses per km
4095 to 4191 <--- 4100 is the factory set pulses per mile
8192 to 8303
Ideally we need to expand the 4000ish range significantly more in the downward direction to make things more useful.
apparently I have reprogrammed my test KPH speedo about 500 times this evening
-
So are you saying for example that these pairs didn't work, or did you omit them for brevity?
0x1003--0x5DFF
0x1002--0x5EFF
0x1001--0x5FFF
Similarly, the run between 0x0847--0x01FF and 0x0804--0x44FF
Kev
Sorry, I omitted those for brevity although in all honesty I didn't test all the ones omitted, but tested quite a few as I was trying to find how far the sequence carried on.
The sequence seems to be predictable for the following ranges
0x1000 to 0x105F
0x09F4 and 0x09F5
0x0800 to 0x0847
-
He changed the listing on the 17th of June and it sold as a 2.5L unknown engine....
-
Solution with no parts to buy.... http://flashoffroad.com/Accessories/Gauges/vdo/Speedometers.htm
A neat solution to clocking on by using the standard serial port. The altering of the pulse per mile though is only available on aftermarket programmable VDO speedos as far as I can tell
-
Being a technophobe and having a dislike of all things that I don't understand, I went looking on the net for someone to change my speedo reading I found this site. Is this the same format as a TD5 speedo
Unfortunately not, the aftermarket VDO speedos have a menu system to allow them to be easily configured. The TD5 speedo needs dismantling and some soldering to reprogram the internal flash chip.
We can set the mileage reading on a TD5 speedo to whatever you like without paying the likes of digidash £100 for the privilege
We are currently working out how to recalibrate the speedometers to allow for different tyre sizes and we can already freely convert kph speedos to mph speedos and the other way round without changing dials. All these things can be done by reprogramming the flash chip
-
After a bit of experimenting with words 8 and 13 I now have a speedo that reads exactly double the miles with both the trip counter and the needle
so it appears that the first byte of word 13 is a check sum of some description, the valid pairs we have so far are:-
0x1004--0x5CFF
0x09F4--0xB3FF
0x0802--0x46FF
so if we can work out how to calculate the checksum we can then calibrate the speedo
0x105F--0x01FF
0x105E--0x02FF
0x1006--0x5AFF
0x1005--0x5BFF
0x1004--0x5CFF
0x1000--0x60FF
0x09F5--0xB4FF
0x09F4--0xB3FF
0x0847--0x01FF
0x0804--0x44FF
0x0803--0x45FF
0x0802--0x46FF
0x0801--0x47FF
0x0800--0x48FF
Interesting, found a bundle more 'pairs' but what seems an obvious pattern doesn't carry on. I can't guess the match to any others at the start and end of the sequences.
-
I tried from 0x00FF to 0xFFFF just changing the first byte and was unable to get it to work, it may be I missed a number out as it's easy to make a mistake by hand. I'll try it again when my bus pirate turns up as hopefully I'll be able to script it then to remove the human error side of things...
-
May I suggest 0x2008 would be a useful figure, as that would be half mileage, so we'll have a set of 0x0802, 0x1004 and 0x2008....
Kev
I'll do that one first then
-
So words 17, 18 and 52 control needle deflection, and words 8 & 13 seem to control input pulse count calibration....
Have you got any more value pairs, 'cos I can't spot a pattern just yet
Kev
I haven't yet, I'll brute force another couple this evening. I think I'll try a close grouping around one of our existing pairs.
-
After a bit of experimenting with words 8 and 13 I now have a speedo that reads exactly double the miles with both the trip counter and the needle
so it appears that the first byte of word 13 is a check sum of some description, the valid pairs we have so far are:-
0x1004--0x5CFF
0x09F4--0xB3FF
0x0802--0x46FF
so if we can work out how to calculate the checksum we can then calibrate the speedo
-
Are you sure the problem is the engine? The oil seals in the turbo could make it smoke to. It is worth doing compression tests on the engine before pulling it apart as with the sort of mileage it has it's barely run in!
Oh and as a quick win check the cyclone breather is clean.
-
Words 17,18 and 52 (0x03C0,0x0780 and 0xACFF on MPH flash) seem to control what face it believes it has, if I change them on the KPH to match the MPH speedo the needle now moves as if it were indicating KPH on the outside scale of the MPH speedo. Changing any word individually seems to stop the needle moving. THe final two words in memory seem to make no difference whatever they are set to.
-
4100 is 1004 in hex. Exactly what is in word 08. Word 09 is similar. Maybe one value of pluse per mile for the odo and one for the dial?
You were right with the 0x1004 value, this is used to configure the trip meter and mileage record. So as you surmised it is the number of pulses per unit. I have verified this with two speedos in parallel, set at 0x2008 it registers only half the mileage and set at 0x802 it registers twice the mileage.
Unfortunately this works in conjunction with word 13, unless we get the value right for this word then the needle stops moving.
-
If you change the 0x09F4 and 0xB3FF on the KPH speedo to 0x1004 and 0x5CFF instead of showing 100KPH it now indicates just over 60KPH .... could it actually be indicating MPH but using the KPH scale?
Did a second test, using the MPH speedo set the frequency generator to make the MPH speedo show 120MPH, connected it to the modded KPH speedo and it shows 120KPH....
EDIT: Just tested trip meter and that too has changed to working in Miles, well it is perfectly in sync with the MPH one anyway.
EDIT Again to add video
-
Just a thought, on the MPH gauge the 100km/h mark is past vertical, but on the KPH gauge the 100km/h is at vertical. Also, the MPH gauge goes to 120MPH, but the KPH gauge goes to 200km/h (125MPH). Possibly then, the gauges are programmed to move the needle different amounts based on the number of pulses?
You sir are indeed correct!
This evening I had a play with a KPH speedo and there are indeed a few degrees difference between the 100KPH postition on an MPH speedo and a KPH speedo.
So I popped it open and read the memory out of it to see if there were any differences ....
There were, so I reprogrammed the KPH speedo using the file I had from the MPH speedo we played with the other week .....
Connected it back up to the frequency generator I've been using for testing (which was still set to indicate 100KPH) and low and behold the needle now overshot 100KPH by a few degrees!
Now we just have to work out what to change, but we have proved the KPH speed and MPH speedo are the same beast just with a different face and memory contents ...
-
I reckon the suggestion of cutting the wheel nuts
is the best one, it's free and won't affect the true running of the wheels like welding could. You'll probably want a lower torque on the wheel nuts after, but I'm assuming your electric tractor doesn't weigh 2 ton and go 70 + mph ... only an assumption though ;-)
-
did you intend to put a reply in here ???????
I think the whole thing has left him speechless
-
They definitely seem to be coming out of the woodwork now, I suppose people saw that one go for £68 the other day.
... remind me to never play cards with you for money 
Defender 200tdi turbo problem
in Defender Forum (1983 - 2016)
Posted
Have you checked if the wastegate has stuck open? That would give the symptoms you describe. Disconnect the wastegate linkage and make sure you can move the wastegate easily by hand, if not WD40 is your friend