Hi,
Worked on Ford Custom 2013. Wanted to update the whole care. Started with the IMPA module, then some other module and than the RCM.
This was the situation before
And this the situation after flashing
Is there any chance in rehabilitation of both modules? If so does someone know how to proceed?
Best regards,
yoda2
Lost RCM IMPA and
Модератор: DanMc85
-
- Сообщения: 5
- Зарегистрирован: 31 янв 2020, 03:55
Lost RCM IMPA and
У вас нет необходимых прав для просмотра вложений в этом сообщении.
-
- Сообщения: 5
- Зарегистрирован: 31 янв 2020, 03:55
Re: Lost RCM IMPA and
Did some tinkering on RCM module.
Found out that the update version BK2T-14C028-BA.vbf is 334 kb on disk, once loaded in UCDS it says 0 bytes. Tried downloading the file several times, result is the same. See screenshot below
Anyone knows how to fix this problem? I would like to have the RCM unit back up and running.
Found out that the update version BK2T-14C028-BA.vbf is 334 kb on disk, once loaded in UCDS it says 0 bytes. Tried downloading the file several times, result is the same. See screenshot below
Anyone knows how to fix this problem? I would like to have the RCM unit back up and running.
У вас нет необходимых прав для просмотра вложений в этом сообщении.
- kroligoff
- Сообщения: 1503
- Зарегистрирован: 16 янв 2013, 11:38
Re: Lost RCM IMPA and
Try Restore original firmware
-
- Сообщения: 5
- Зарегистрирован: 31 янв 2020, 03:55
Re: Lost RCM IMPA and
Hi,
Thank you for your reply. Via the telegramchat, Sergey S told me that the file BK2T-14C028-BA did not have the correct omit zone. He gave me an adjusted file. With that file and UCDS I managed to make the RCM unit approachable.
From that point on I was able to connect to the RCM unit to read fault memory, erase fault memory etc. However now I have 4 faults left.
I did direct configuration (loaded as built from ETIS) -> "write to module" (also tried with "reset module" on forehand) -> UCDS says "All operations Done! Errors: 0". If do "read from module" every configuration setting is gone. From the telegramchat I understand the eeprom is damaged. I geuss it is non-repairable in a software manner and I have to buy a new/used module.
What do you exactly mean bij original firmware?
Thank you for your reply. Via the telegramchat, Sergey S told me that the file BK2T-14C028-BA did not have the correct omit zone. He gave me an adjusted file. With that file and UCDS I managed to make the RCM unit approachable.
From that point on I was able to connect to the RCM unit to read fault memory, erase fault memory etc. However now I have 4 faults left.
I did direct configuration (loaded as built from ETIS) -> "write to module" (also tried with "reset module" on forehand) -> UCDS says "All operations Done! Errors: 0". If do "read from module" every configuration setting is gone. From the telegramchat I understand the eeprom is damaged. I geuss it is non-repairable in a software manner and I have to buy a new/used module.
What do you exactly mean bij original firmware?
У вас нет необходимых прав для просмотра вложений в этом сообщении.