There’s actually four different things going on there for those settings, and what would be needed to make them work on pre-2023.
1) The pre-2023 body computer doesn’t broadcast the messages for those settings to tell the radio to populate them, which is why I had someone use an arduino to force those messages to the radio. So, a 2023 BCM would be needed.
2) Forcing the messages to the 2022 UC5 radio module did not make those settings show up, and finding out the 2023 UC5 radio module is a different part number and software, a 2023 radio module would be needed.
3) EVEN after you get the settings to show up in the radio, they probably won’t actually work unless you swap out your current surround view camera processor for the 2023 Camera processor, which is a new part number.
4) Knowing how the AlfaOBD developer gets all the information for putting the settings on the app, it’s going to be a while before he can add these settings to the CustSetMenu 3 list for the average user to enable them. It’s hard to explain, but in the BCM message ID section where CustSetMenu 3 is, there is a block of 24 settings that are just named reserved (because they didn’t have a name yet when the version of engineering software we have was released). With
@jsalbre backup file above, and a process of elimination compared to mine, I was able to narrow it down to a possible 7 of those reserved settings. If I’m able to first have them show up in the radio, then I can go by one by one changing values to see which setting disappears, then I can tell the developer which byte does what, and what to name the setting.