[user0086]

I replaced a Mini Visual Boost (Entry) with an EntryNav and added an activator and GPS antenna.
I added 6UM to the FA and coded the EntryNav accordingly. The car has MINI-connected, but no active subscription.

Now, occasionally the unit stays in "starting navigation", but after the vehicle goes to sleep it works correctly afterwards. If this happens, it is not possible to make a call via Bluetooth and there is a check-control message about Cruise Control not working.

The only DTC stored is for not receiving a GPS signal for 40 KM.

I tried to update the unit, but the HWEL does not match. I attached the FA, current SVT and target SVT.

Current HWEL = 00001703.004.002, Target HWEL = 00001704.003.003
Current BTLD = 00001ABA.110.001.04, Target BTLD = 00001ABA.130.026.001

My questions:
 - Is it possible that updating to the newer software will fix the issue?
 - If so, how can I modify the FA in such a way that it accepts my HWEL?
 - Or is it safe to ignore the differences in HWEL since the BTLD has the same ID?

Thanks in advance for any help!

entrynav.zip
File Type:
Downloaded:	4 times
Size:	5.4 KB

[user0086]

Anyone can tell me if I can safely execute the BTLD update?

[Spirit5676]

When doing the calculation click HW-IDs from SVTactual.

[user0086]

When doing the calculation click HW-IDs from SVTactual.

I know how to force this update, i just want to know if this won't brick the unit.

[Stratofortress]

How does it look with SVT target adjusted to the I-Step shipment of the retrofitted HU?
The HWEL match, and How about the BTLD?