Its diesel and the dial says - Diesel.

It still needs changing to gauge variant 2 so the rev gauge only goes to 6000rpm with a redline at 4000rpm rather than going to 8000rpm with a redline at 6000.

It can be done by editing the CCF in SDD.

I can help if needed 👍

Should look the picture below:-

It can be done.

I am not worried about that as I am never going to rev that high in the LR. For that I have a motorcycle

May be when I have some spare time...

It really does finish the job off and doesn’t take that long to do 👌

It does.

I am trying to build a CAN gateway that maps the applicabe CAN IDs from Discovery 3/(RRS MK1) on the 29 bits CAN bus to the 11 bits CAN bus that the TFT IPC is using. This way also the D3/RRS can use this fantastic upgrade. Nobody here that by any change has sniffed both CAN buses of both Range Rover and Discovery3/RRS for the applicable CAN IDs so I can try these in the Arduino scetch I am running?

I’d be really interested in watching this progress and possible purchase one or build my own?

got everything connected, correct CAN scetch running, original IPC disconnected however TFT does not turn on. Next step is to read VIN and milage etc as described so kindly by TheWojtek as a reference:
- The VIN is located at position 0A8: copy 17 bytes of the VIN from old cluster file to new cluster file.
- Dash type is located at position 0C0: copy 16 bytes*
- Mileage is located at position 784: copy 16 bytes*
- Immobiliser is located at position 7E8: copy 31 bytes (right to the end of file)

I will try this first on a used Discovery 4 IPC as its eeprom is readily accessable. Maybe the Immobilizer routine with wrong VIN and Milage in the D4/RR IPC prevents the IPC to respond to CAN messages and turn on

When I was converting mine I forgot to put the dash model in and it failed to switch on.

Do you need a copy of an L322 TFT eeprom file?

many thanks for the offer but have the xhorse vvdi2 and vvdi prog so will read and modify the tft eeprom when the D4 IPC proof of concept works. D4 and 2012 Range Rover share the exact same pinout of the IPC connector.

some progress and nice to know for others is that the D3 milage is held in IC9, EEPROM ST35080VP. The milage is stored as is, not encrypted like with the Discovery 4. mine had 236862 Km at time of IPC removal. put that in a decimal to hex converter and you get 39D3E. At position A0Dh the value is stored as 039D3E and only once. Not repeated 5x as with Discovery 4. And no VIN in this file.

Whoa, getting this cluster to work in a pre-facelift RRS/Disco3 is just some next-level engineering. There was a guy in Russia who had a plug-and-play CAN converter done for this very application, but not doing business with Russia and he vanished anyway, so @Dutchviking is the only hope for prefacelift folks. Regards etc.,

Wojtek

---
WAS: 2006 RRS Supercharged
IS: 2010 RRS TDV8 HSE

the CAN gateway is working and I already sniffed my own D3 and a visiting Discovery 4 as CAN messages between both cars are different so we need to map D3 messages to become D4 messages that the cluster understands. And then there is the immobilizer problem. Copying Milge and VIN to my D4 cluster eeprom is not enough. Panel does not even turn on. I have to find the immobilizer code in the D3 eeprom dump and copy that to the D4 eeprom and see if that does the trick.

Ordred a 2012 Range Rover ECU kit and will build a rig to be able to sniff the can bus as I do not have a Land Rover with an 11 bits can bus at hand. When can bus ids for ignition on, door open, lights, turn signal, hazard lights etc etc are known I can build a can id mapping between Discovery 3 29 bits and Range Rover 11 bits, to wake-up the IPC and show relevant information on it. Things like RPM and speed I already found on other forums.