[cryptz]

So I took my first crack at coding thanks to all of the great write ups on here.

I was able to disable my idrive and camera disclaimer and put the mlogo on the cluster. I also enabled video in motion but honestly I haven't tried that yet. one issue I did have problems with is the amber hud. I tried to make it white all of the time with the following:

KOMBI 3007 DIM_NACHT_EIN Aktiv Aktiv 32 FF

if I change that value from 32 to FF, when I come back in Aktiv is now unknown, it seems you cannot set it to FF and have it still say Aktiv. I also tried changing it to the nonactive german equivalent that didn't work either. it still shows up amber in the hud.

I have a 2014 435i maybe its not supported for some odd reason? or is there something else I need to change?

[radair]

Probably the range goes from 0 to 100%.
You tried FF Hex which means 255 B. This is not possible.

Try 64 Hex which means 100%

Greetings
Radair

[Halsifer]

If it's coded as unknown, that's fine. This feature is to have it so the instrument cluster staying day-mode during the night, correct? I assume if it's unknown, it will not be aktiv, achieving the fact that it will not transition, which is the whole point of the code.

[cryptz]

Originally Posted by Halsifer

If it's coded as unknown, that's fine. This feature is to have it so the instrument cluster staying day-mode during the night, correct? I assume if it's unknown, it will not be aktiv, achieving the fact that it will not transition, which is the whole point of the code.

maybe but it is not achieving any result at all, it is operating as if I didn't code it. I will try the suggestion of setting it to 64 but that is not what the guide states. I am thinking there is possibly something different for the f32. I believe the default value is 8a instead of what the guide states so there are some differences.

[shawnsheridan]

Originally Posted by Halsifer

If it's coded as unknown, that's fine. This feature is to have it so the instrument cluster staying day-mode during the night, correct? I assume if it's unknown, it will not be aktiv, achieving the fact that it will not transition, which is the whole point of the code.

No. The predefined Dropdown box settings and the Werte values are a matched set. So when you change the Dropdown box setting, the Werte value automatically changes with it.

So for example, if you change a Dropdown box settings from nicht_aktiv to aktiv, the Werte value automatically changes from Werte=00 to Werte=01.

That said, it's the Werte value only that matters. However, since hexadecimal values are hardly descriptive, the Dropdown box settings serve to provide a more descriptive way of representing what the Werte value's mean, and to ease changing them.

So, when you change a Werte Value directly to a custom value, the predefined Dropdown box setting, which does not have a match for the custom value, displays "Unknown". The custom Werte value though is most certainly active so long as it is a valid value.

[Halsifer]

Originally Posted by shawnsheridan

No. The predefined Dropdown box settings and the Werte values are a matched set. So when you change the Dropdown box setting, the Werte value automatically changes with it.

So for example, if you change a Dropdown box settings from nicht_aktiv to aktiv, the Werte value automatically changes from Werte=00 to Werte=01.

That said, it's the Werte value only that matters. However, since hexadecimal values are hardly descriptive, the Dropdown box settings serve to provide a more descriptive way of representing what the Werte value's mean, and to ease changing them.

So, when you change a Werte Value directly to a custom value, the predefined Dropdown box setting, which does not have a match for the custom value, displays "Unknown". The custom Werte value though is most certainly active so long as it is a valid value.

Right, I understood the tie between the dropdown menu and the werte value, and how they change dependent on the each other's value. I guess I don't quite understand the meaning of Unknown.

I assume the value range of this code DIM_NACHT_EIN was from 0 to 100 dec (00 to 64 hex) based off what radair pointed out. Say I chose 63 hex (99 dec). Even though it would be labeled as UNKNOWN, that would still correspond to aktiv, just at a custom value so there's no predefined label in the dropdown. We are on the same page about this, yes?

However, I also assumed the if value was set to FF hex (255 dec), this would lead to nicht_aktiv since it's out of range. That's the only reason I thought it UNKNOWN would correspond to nicht_aktiv, as I posted above. Is this true or am I mistaken?

An extension question, are you even able to FDL code values out of range?

[shawnsheridan]

I do not know the valid range of DIM_NACHT_EIN. But generally speaking, I think it all depends on the specific function being coded, and that some items, even those expressed as a percent, can have valid values greater than 100%, and FF could very well be 255% of nominal, particularly when the werte value corresponds to an underlying variable such as voltage, so 3 volts nominal at 255% would be 7.65 volts, or time, so 3 ms nominal would be 7.65 ms. So in these cases, 255 would not be out of range, rather it's just the upper limit.

[G30 B58]

cryptz, when you're ready, you can code mine after redelivery?

Allentown area here.

[cryptz]

does anyone have specific experience with this value though? i appreciate all of the input about what the ranges could be but this particular value has already been listed on everyone's cheat sheets. it just seems that the sheets are wrong which leads me to believe it is different for the f32. it may not even be a codable option on this car..

[Halsifer]

Originally Posted by shawnsheridan

I do not know the valid range of DIM_NACHT_EIN. But generally speaking, I think it all depends on the specific function being coded, and that some items, even those expressed as a percent, can have valid values greater than 100%, and FF could very well be 255% of nominal, particularly when the werte value corresponds to an underlying variable such as voltage, so 3 volts nominal at 255% would be 7.65 volts, or time, so 3 ms nominal would be 7.65 ms. So in these cases, 255 would not be out of range, rather it's just the upper limit.

Sweet, thank you for the clarification.