[Dephead2004]

Since January I've had this message on the Instrument Cluster of a 2017 G30. Thinking this was the fob battery I checked out the CR 2032

Varta 2.94V Error message so replaced 7/1/24 with
Maxwell 3.18V Error message so replaced 9/1/24 with
Panasonic 3.32V Error message so replaced 13/1/24 when reading 3.05V with
Varta 3.27V Error message so replaced 2/2/24 when reading 3.07V with
Duracell 3.3V Error message 4/2/24 when reading 3.23

Now thinking that this is not the battery fob so swapped the fob for the second one. This gave the same error message

Checked out Bimmerlink apart from the loads of error messages this one seemd relevant held in the error memory of the Body Domain Controller:
804415 ID transmitter (IDG)Battery under voltage.

This can be cleared in Bimmerlink but as soon as the vehicle is unlocked the error returns.

Both fobs continue to work without error except fro the annoying bong which clears after a few seconds.

There's been some discussion https://x3.xbimmers.com/forums/showt...tage%20battery on X5 forum but no conclusion

There's another YouTube

which demonstrates that you need a new 12v Vehicle Battery. However the comments say that it wasn't that.

Anyone have any insights? Would value observations and comments

[Dephead2004]

Replaced the 12v battery and all keys are back to normal. The reading is now 93% rather than 83% on the old battery. These vehicles are indeed sensitive to loss of current before the vehicle won't start.

[Dephead2004]

One final point after registering the battery in Bimmerlink and receiving the green registration confirmation is that the mileage at which the batteries were exchanged was not recorded.
Anyone experienced this?

[Dephead2004]

Originally Posted by Dephead2004

One final point after registering the battery in Bimmerlink and receiving the green registration confirmation is that the mileage at which the batteries were exchanged was not recorded.
Anyone experienced this?

Answer From Bimmerlink themselves:
Dear Customer,

This is a known issue and we are working on it. Please note that the registration itself worked.