R50/53 Chrono Pack Retrofit - All the info you need (hopefully)
#276
It’s not really possible to find a new chrono, I know what my mistake was, but the flash is lost for my board, now I’m restoring it in pieces and I think if I had a second board, so there was no problem, since I successfully counted the old odometer, reset the vin code and mileage, so for the car it has become new, when I restore the firmware of my chrono package I will do the same
#277
It’s not really possible to find a new chrono, I know what my mistake was, but the flash is lost for my board, now I’m restoring it in pieces and I think if I had a second board, so there was no problem, since I successfully counted the old odometer, reset the vin code and mileage, so for the car it has become new, when I restore the firmware of my chrono package I will do the same
#278
I haven't spoken directly with Mini but from the looks of it, you can still order a new one. I guess I was wondering if that is indeed possible that it can just be coded by mini as a new unit and work around the mileage issue. Might need a new Speedometer tach as well which looks to be available too.
#280
#283
The following users liked this post:
Onizukachan (07-21-2023)
#284
Read eprom successfully with r270.
loaded binary files for 30 I downloaded from GitHub, removed .txt. And renamed from .bin to .BIN
Tried writing the flash (I assume you select flash) and tried writing eeprom with the 0km file.
both said it was “data size invalid” seems to be an absolute assload of commentating in it? The original read was minimal and any commenting mostly gibberish?
loaded binary files for 30 I downloaded from GitHub, removed .txt. And renamed from .bin to .BIN
Tried writing the flash (I assume you select flash) and tried writing eeprom with the 0km file.
both said it was “data size invalid” seems to be an absolute assload of commentating in it? The original read was minimal and any commenting mostly gibberish?
Last edited by Onizukachan; 08-28-2023 at 11:28 PM.
The following users liked this post:
joshzash14 (09-18-2023)
#285
The following users liked this post:
joshzash14 (09-18-2023)
#286
Onizukachan - any chance you'd be open to reprograming my units? (Have a chronos pack and nav unit) - plan to swap the nav units screen out for a carplay like unit in its place, but wouldn't mind having the chronos unit in its place for the time being.
Feel free to PM if you'd like.
Feel free to PM if you'd like.
Last edited by joshzash14; 09-18-2023 at 05:55 PM.
#287
If you were local, I would
if you have a windows computer, get the r270, install the software and download the flash and eeprom files.
Follow the TDLR directions and strip out the numbered wires from the ribbon cable about 6” back and connect the wires as indicated in the pictures on GitHub.
make sure you can read it beforetrying to flash anything.
What I did to get a good read was tin the only rearmost section of exposed wires after stripping so I could press fit them into the socket holes in the board amd when they got to tinned section, boom. They stayed.
there is only one wire that needed to be soldered in place so I tinned that one fully and just touched surface contact point with iron to preheat, then put wire atop and touched wire with iron to make a temp connection I could just pop free after.
when you have a good connection it will read or flash it in 6-10 seconds, when you don’t it will stall and sit there not actually doing anything for minutes.
after you have it flashed, hook it up to car.
Don’t bother with copying vin etc from old one, dont even bother trying to read old one.
once it is virginized, if you have pasoft 1.4 aka bmw scanner, it has the options to import over from ews in menu with a click, instead of having to fndtlessen etc amd switch moduels and codes back and forth in NCSexpert…, those options are in it for one click operation. Worth the $20 for that one too, have had mine for about a decade and used on 2 former early 2000s bmws and now 3 r53s.
if you have a windows computer, get the r270, install the software and download the flash and eeprom files.
Follow the TDLR directions and strip out the numbered wires from the ribbon cable about 6” back and connect the wires as indicated in the pictures on GitHub.
make sure you can read it beforetrying to flash anything.
What I did to get a good read was tin the only rearmost section of exposed wires after stripping so I could press fit them into the socket holes in the board amd when they got to tinned section, boom. They stayed.
there is only one wire that needed to be soldered in place so I tinned that one fully and just touched surface contact point with iron to preheat, then put wire atop and touched wire with iron to make a temp connection I could just pop free after.
when you have a good connection it will read or flash it in 6-10 seconds, when you don’t it will stall and sit there not actually doing anything for minutes.
after you have it flashed, hook it up to car.
Don’t bother with copying vin etc from old one, dont even bother trying to read old one.
once it is virginized, if you have pasoft 1.4 aka bmw scanner, it has the options to import over from ews in menu with a click, instead of having to fndtlessen etc amd switch moduels and codes back and forth in NCSexpert…, those options are in it for one click operation. Worth the $20 for that one too, have had mine for about a decade and used on 2 former early 2000s bmws and now 3 r53s.
#288
As opposed to doing all of this coding stuff, couldn't you just swap over the EEPROM from the car's original cluster to the Chrono cluster? I understand desoldering and resoldering a 52 pin IC is no fun, especially as delicate as EEPROMs can be, but with the right tools, it is possible. I'm guessing you might have to fight some conformal coatings as well... but again, manageable.
So in short, wouldn't moving the E²PROM to the Chronopack cluster from the original cluster take care of the VIN/Mileage/features disparities? What else would be needed at that point? For this thought experiment, I am assuming a 2006 facelift center speedo EEPROM being moved over to a matched set of 2006 facelift Mickey Mouse ears/Chrono gauges.
So in short, wouldn't moving the E²PROM to the Chronopack cluster from the original cluster take care of the VIN/Mileage/features disparities? What else would be needed at that point? For this thought experiment, I am assuming a 2006 facelift center speedo EEPROM being moved over to a matched set of 2006 facelift Mickey Mouse ears/Chrono gauges.
#289
#290
As opposed to doing all of this coding stuff, couldn't you just swap over the EEPROM from the car's original cluster to the Chrono cluster? I understand desoldering and resoldering a 52 pin IC is no fun, especially as delicate as EEPROMs can be, but with the right tools, it is possible. I'm guessing you might have to fight some conformal coatings as well... but again, manageable.
So in short, wouldn't moving the E²PROM to the Chronopack cluster from the original cluster take care of the VIN/Mileage/features disparities? What else would be needed at that point? For this thought experiment, I am assuming a 2006 facelift center speedo EEPROM being moved over to a matched set of 2006 facelift Mickey Mouse ears/Chrono gauges.
So in short, wouldn't moving the E²PROM to the Chronopack cluster from the original cluster take care of the VIN/Mileage/features disparities? What else would be needed at that point? For this thought experiment, I am assuming a 2006 facelift center speedo EEPROM being moved over to a matched set of 2006 facelift Mickey Mouse ears/Chrono gauges.
Thread
Thread Starter
Forum
Replies
Last Post