![]() |
![]() |
![]() |
![]() |
![]() ![]() |
![]() |
BMW Garage | BMW Meets | Register | Search | Today's Posts | Mark Forums Read |
![]() |
![]() ![]() |
BMW 3-Series (E90 E92) Forum
>
MSD80 to MSD81 DME Questions
![]() |
![]() |
12-30-2018, 01:21 PM | #23 | |
Lieutenant Colonel
![]() ![]() 662
Rep 1,893
Posts |
Quote:
Standard OBDII calls to related to the VIN will return the VIN written to the most recent UIF entry. However, MHD does not use a standard call and reads the first entry to the UIF in the DME, which always has the vehicle's original VIN. It is not possible to alter the first entry without fairly expensive software. MHD recognized this was becoming a problem for users who had bricked DMEs and had installed used replacements. Thus, they altered their program to read either DME or CAS Vin entries and, presumably, you only need one of them to match their record. |
|
Appreciate
2
catcher22297.50 |
02-18-2019, 03:59 PM | #24 | |
New Member
20
Rep 20
Posts |
Quote:
:edit: To be be clear - if you live in a pollution controlled state, be very careful who does your DME swap or the VIN will be incorrect. :edit2: Update - MHD writes a new UIF using the donor VIN. After flashing with MHD, my VIN is now incorrectly reported over OBD2 ![]() Last edited by Cyrix2k; 02-18-2019 at 05:09 PM.. |
|
02-22-2019, 09:09 PM | #25 |
New Member
20
Rep 20
Posts |
Final update! MSD8x DMEs have two AIFs. One is written at the factory and cannot be changed to my knowledge. The second can be written to by WinKFP, Tool32 if it's blank, or MHD. After gaining security access to the DME, I tried to write a new AIF with Tool32 and it gave an error - something like "cannot be downloaded to address," which is because MHD already wrote the second AIF and no more slots are available. At this point, the best solution would be an MHD update. Failing that, it may be possible to erase and write a new AIF. I haven't tried that yet.
On to what I actually did do. I "faked" MHD out by man-in-the-middling the CAN bus and replacing the donor VIN with mine as MHD read the VIN in the initial AIF. Then I flashed the DME on the bench which completed successfully. MHD wrote that second AIF with my correct VIN and now it is reported correctly through OBDII. I haven't tried flashing another map but I suspect it may overwrite the AIF so this isn't a great solution. Another interesting note is that I had an EWS manipulation code before that has now disappeared - I have zero active codes. I'm calling this a success! |
Appreciate
2
catcher22297.50 lightmanek116.50 |
05-10-2019, 06:34 PM | #26 | |
New Member
2
Rep 11
Posts |
Quote:
Cyrix2k I am having the exact same issue, can you DM me your email I want to CC you on an email to MHD support to get this bug sorted. |
|
Appreciate
0
|
06-11-2019, 04:14 PM | #27 |
G
![]() 0
Rep 6
Posts |
You don't need to do anything special. Just contact MHD, explain them you had your DME replaced and they will take care of it for licensing purposes.
|
Appreciate
0
|
09-16-2019, 10:58 PM | #28 |
New Member
20
Rep 20
Posts |
I haven't tried this, but I'm not sure that's correct. MHD will recognize the license as valid since the licensed VIN is still present in the CAS; it just writes back the "wrong" VIN (donor) which will cause the vehicle to fail OBD-II emissions in some states.
|
Appreciate
0
|
![]() |
Bookmarks |
Thread Tools | Search this Thread |
|
|