848 Swapping Dash By Transferring Memory?

Discussion in '848 / 1098 / 1198' started by tboooe, Sep 15, 2020.

  1. My 848 dash needs to be replaced but I do not have the code card nor do I want to go through the hassle of getting a new one reprogrammed with an external service. I was wondering if anyone knows how the information that ties a dashboard to particular code is stored in the dash? I assume since new dashes can be reprogrammed that the information is stored in memory on the PCB somewhere. Assuming I can find where the memory chip is, I wonder if I can transfer this chip from my old dash to a new one and have it work with my existing keys and also maintain my odometer reader.


    What does everyone this? Long shot?
     
  2. Try looking on the Digital Kaos forum
     
  3. Did you successfully swap memory chip from your old dash to the new one?

    I also need to replace my dash and I don't want to wait for 3 weeks to ship my old and new (used ebay) dash somewhere to be programmed for some good €€€ in the middle of allready too short riding season in Finland when I could just ask my local electronic shop to swap some eeproms for 20€ while I wait

    Also tried to look trough Digital Kaos forum as chrisw suggessed but I didn't find anything specific
     
  4. Read this
     

    Attached Files:

    • Like Like x 1
  5. Took apart the new dash. Is this the eeprom in question? 24C16WP

    IMG_20240603_124027.jpg
     
  6. Thank you Chris for your help I successfully copied my old eeprom and transferred it to the new dash and it works!

    Immo code was easy to recognise but out of curiosity I tried to find km reading but I don't understand how to calculate that reading from that hex code. Can you explain how that can be calculated, and can I create that number for different km reading if I need to?

    View attachment 318653

    Screenshot_20240613_193419~2.jpg
     
  7. Sorry I cannot fully help.
    It is stored at line 010 00 01 and 020 00 01. The hex is FC FE.
    The PDF I attached shows how the odometer reading is calculated from the hex.
    You may find the info on a forum called Digital Kaos.
    In order for the dash to store the odometer value you also need to calculate a CheckSum otherwise the odometer will revert to the originally stored data. I do not know how to calculate the checksum. The checksum in your screenshot is FD.
    You may wish to crop your screen shot so it just shows your odometer reading for security reasons.
     
  8. I have been playing with the odometer calculation from the hex value.
    Is your current odometer - 6527.8 km?
     
  9. That code is from my donor dash and it has 19634km on it
     
  10. Is it in theory possible to change Immo code to what ever I like?
    When it is written there for example as 01 02 03 05 06 so 123456 and lets say I would like to change that to 987654 so if I would replace those numbers with 09 08 07 06 05 04 (Immo code appears there 3 times so I would replace all those numbers) would it change my key code from 123456 to 987654?

    As to km reading if companys like odo-pro.com can program them (or so they say) I wonder how they do it, with this eeprom code modification method or some other way
     
  11. Got it. Your odometer reading is held as FE FC 02
    Reorder this to 02 FE FC and convert to decimal
    That gives 196348 (divide by 10) = 19634.8km

    To work from the dash odometer reading to hex you must include the partial kilometre ie the .8

    Have no idea on how to calculate the checksum
     
  12. The immo code is linked to your black keys and is locked in the eeprom by Checksum. It is created when the first keys are programmed to the virgin dash and I believe it does not change even when a new key set is programmed to the dash. Hence, the importance of the code card. In order to set your ‘own’ bypass code you would need to calculate the checksum.
     
Do Not Sell My Personal Information