Coding Made Easier (Cheat Codes in E-Sys Launcher)

[KevinGS]

Originally Posted by dmnc02

IMO, Halsifer's cheat sheet (which you can find here) is still the best for our cars, although it has not been updated in almost a year. There are others that have been updated more recently but are very sloppy.

The above cheat sheet does not include things like "easy entry", "Euro MDM" or codings that relate specifically to the adaptive LED headlights or to HU_NBT2, but those are a few things that a search in the forum should quickly address.

So most of the coding in Hals' F30 list works for our F8X vehicles? His list is long...

[dmnc02]

Originally Posted by KevinGS

So most of the coding in Hals' F30 list works for our F8X vehicles? His list is long...

Yes, the vast majority of the coding in the list does work.

[KevinGS]

Originally Posted by dmnc02

Yes, the vast majority of the coding in the list does work.

Thanks, looks like I have some more coding I'll be doing....there's some nuggets in here that I don't already have coded.

[Invictus]

Originally Posted by aboulfad

It seems few people miss where to get the software, post here and you shall receive.

Please PM me.

[aboulfad]

Originally Posted by Invictus

Please PM me.

The "here" had a link to another thread where you post there and ask for the software. It wasn't meant that you post in this thread and it's Shawn that provides the links.

[stealth70mde]

Originally Posted by dmnc02

Even when the parameter names are the same, the bitmaps (which is what the cheat codes use to identify the parameters) are different between HU_NBT and HU_NBT2. So do not try to apply to HU_NBT2 cheat codes that are meant for HU_NBT, as you will get unpredictable results.

FDL code HU_NBT2 by hand until the cheat codes are updated.

Hmmm, Okay... I have HU_NBT2 and used the cheat codes in the past. Maybe I should restart my coding by hand to be sure I have everything right...

[dmnc02]

Originally Posted by stealth70mde

Hmmm, Okay... I have HU_NBT2 and used the cheat codes in the past. Maybe I should restart my coding by hand to be sure I have everything right...

I was replying to dinonz's question in post #106: he saw no cheat codes for HU_NBT2 and he was asking if it was safe to go into the XML file with the cheat codes and simply change the ECU identifier from HU_NBT to HU_NBT2.

If you saw cheat codes when you selected HU_NBT2, you have no reason to be concerned.

[srfr13]

When I use the cheat codes, I always do them one at a time and select review to see what is being changed before I hit apply. Then after you apply make sure you get the confirmation message that the changes were successful.

While reviewing, I've found a few of the cheat codes changing random parameters that seemed unnecessary or overwriting other coding that I wanted to keep.

[dinonz]

Originally Posted by dmnc02

Yes, the vast majority of the coding in the list does work.

I did notice that many of the things listed for HU_NBT didn't exist in HU_NBT2. There were some coding options I wanted to set but just couldn't find.

I got 90% of it done though.

[banff]

Any progress or updated FDLcodes list?

[Halewafa]

Originally Posted by dmnc02

Right-click on FEM_BODY in the SVT tree and select "Read Coding Data". Then right-click on the CAFD in the folder that appears under the ECU and select "Edit FDL". Select the checkbox for "No-Glare High Beam Assistant (Step 3)", click "Apply", click "OK" in the window that appears asking for confirmation and wait for the message stating that the coding has been successfully applied. Then save the edited CAFD by clicking the diskette icon in the menu bar and go back to the Coding window by clicking the left green arrow in the menu bar. Finally, select the CAFD file you just edited and click "Code FDL".

When scrolling through the checklist, there is the "No-Glare High Beam Assistant (Step 3)" that appears twice. Once towards the top of the list, and one that appears further down. Do I check both boxes? Just one? Which one? Thanks!

[Halewafa]

Originally Posted by Halewafa

When scrolling through the checklist, there is the "No-Glare High Beam Assistant (Step 3)" that appears twice. Once towards the top of the list, and one that appears further down. Do I check both boxes? Just one? Which one? Thanks!

Never mind. I reviewed both and they do the same thing. Just went with the first one.

EDIT: Any issues with doing this the "offline" way? I'm wondering if that's why when I tried it yesterday it didn't work... Just finished trying again, will test them tonight.

[Almaretto]

Originally Posted by Halewafa

Never mind. I reviewed both and they do the same thing. Just went with the first one.

EDIT: Any issues with doing this the "offline" way? I'm wondering if that's why when I tried it yesterday it didn't work... Just finished trying again, will test them tonight.

Does not matter if you loaded offline NCD or are editing CAFD from connected vehicle. Build in Sheets will worth either way.

[0-60Motorsports]

Does this apply to older models like the E46 M3 as well?

[aboulfad]

Originally Posted by 0-60Motorsports

Does this apply to older models like the E46 M3 as well?

Sorry wrong board unfortunately it doesn't... that platform (E46) requires other less friendly software to customize some things, read ncsexpert, ...

[OhioRiderAaron]

Used the "cheater codes" to finish out the ABD headlights and worked great. Much better performance compared to just removing the two VO codes. No more blinding oncoming traffic and the beam control is much quicker and more accurate now.

[0-60Motorsports]

Originally Posted by aboulfad

Sorry wrong board unfortunately it doesn't... that platform (E46) requires other less friendly software to customize some things, read ncsexpert, ...

yeah dont like ncsexpert lol

[packetpilot]

There are some F8X-relevant cheat code updates on my GitHub repo: https://github.com/packetpilot/bmw-f

The name of the repo may change, and also, the launcher may wind up pulling from this repo for XML changes, but until there's app development done with respect to that, you can get cheats from within the 'cheats' directory.

My cheats file (packetpilot.xml) includes these updates for our cars:
- Rear fog cheats (ease to switch on button, and which fog lamp/s are activated with the button)
- DRL taillights updates: outer, and outer+inner tails with DRL
- Fold/Unfolding Mirrors (wasn't working in its prior state on my, no others', 2016+)
- B&O Digital Signal Processing (replacing Logic7, requires HK system or 2016+)
- DRL + Sanding Lights Adjustments: eyebrows and angel eyes control

I'll past it here as well but, where this paste'll go stale, the repo will always be fresh, hopefully with activity from all authors somewhat regularly (and perhaps with more contributions from you!).

<?xml version="1.0" encoding="utf-8" ?>
<FDL>
	<!-- packetpilot -->
	<cafd id="00000794" name="FEM_01" author="packetpilot" series="F030">
	<code description="Rear Fog Switch Enable [dep: switch or blank mod]">
		<group id="3060">
			<function start="7" end="7" mask="00001000b">01</function>
		</group>
	</code>
	<code description="Rear Fog Switch Disable">
		<group id="3060">
			<function start="7" end="7" mask="00001000b">00</function>
		</group>
	</code>
	<code description="Fold/Unfold Mirrors w/ Fob + Comfort Access">
		<group id="3110">
			<function start="1" end="1" mask="=00000001b">01</function>
			<function start="8" end="8" mask="=00000001b">01</function>
		</group>
	</code>
	<code description="No Fold/Unfold Mirrors w/ Fob + Comfort Access">
		<group id="3110">
			<function start="1" end="1" mask="=00000001b">00</function>
			<function start="8" end="8" mask="=00000001b">00</function>
		</group>
	</code>
	</cafd>

	<cafd id="000007A1" name="REM_01" author="packetpilot" series="F030">
	<code description="Outer+Inner Tails w/ DRL">
		<group id="3062">
			<function start="200" end="200" mask="00111111b">14</function>
			<function start="210" end="210" mask="00111111b">15</function>
			<function start="220" end="220" mask="00111111b">16</function>
			<function start="230" end="230" mask="00111111b">17</function>
		</group>
	</code>
	<code description="Outer Tails Only w/ DRL" series="F030">
		<group id="3062">
			<function start="200" end="200" mask="00111111b">14</function>
			<function start="210" end="210" mask="00111111b">15</function>
			<function start="220" end="220" mask="00111111b">00</function>
			<function start="230" end="230" mask="00111111b">00</function>
		</group>
	</code>
	<code description="No Tails w/ DRL" series="F030">
		<group id="3062">
			<function start="200" end="200" mask="00111111b">00</function>
			<function start="210" end="210" mask="00111111b">00</function>
			<function start="220" end="220" mask="00111111b">00</function>
			<function start="230" end="230" mask="00111111b">00</function>
		</group>
	</code>
	<code description="Both Rear Fogs Active [dep: switch activation in FEM_Body]">
		<group id="3063">
			<function start="40" end="40" mask="00111111b">1C</function>
			<function start="50" end="50" mask="00111111b">1D</function>
		</group>
	</code>
	<code description="Left Rear Fog Active [dep: switch activation in FEM_Body]">
		<group id="3063">
			<function start="40" end="40" mask="00111111b">1C</function>
			<function start="50" end="50" mask="00111111b">00</function>
		</group>
	</code>
	<code description="Right Rear Fog Active [dep: switch activation in FEM_Body]">
		<group id="3063">
			<function start="40" end="40" mask="00111111b">00</function>
			<function start="50" end="50" mask="00111111b">1D</function>
		</group>
	</code>
	</cafd>

	<cafd id="00001EF6" name="HU_NBT_EVO" author="packetpilot" series="F030">
	<code description="B-and-O Digital Signal Processing, Replaces Logic7">
		<group id="3000">
			<function start="57" end="57" mask="00110000b">03</function>
		</group>
	</code>
	<code description="No B-and-O Digital Signal Processing, Restores Logic7">
		<group id="3000">
			<function start="57" end="57" mask="00110000b">00</function>
		</group>
	</code>
	</cafd>

	<cafd id="00001082" name="TMS_03" author="packetpilot" series="F030">
	<code description="DRL Headlamp Settings: Angel Eyes Only, No Eyebrow">
		<group id="3005">
			<function start="0" end="15" mask="11111111b">00, 04, 00, 00, 00, 04, 00, 00, 00, 03, 00, 00, 64, 00, 00, 00</function>
		</group>
	</code>
	<code description="DRL Headlamp Settings: Eyebrow Only, No Angel Eyes">
		<group id="3005">
			<function start="0" end="15" mask="11111111b">00, 04, 00, 00, 00, 04, 00, 00, 64, 03, 00, 00, 00, 00, 00, 00</function>
		</group>
	</code>
		</cafd>

	<cafd id="00001083" name="TMS_03" author="packetpilot" series="F030">
	<code description="DRL Headlamp Settings: Angel Eyes Only, No Eyebrow">
		<group id="3005">
			<function start="0" end="15" mask="11111111b">00, 04, 00, 00, 00, 04, 00, 00, 00, 03, 00, 00, 64, 00, 00, 00</function>
		</group>
	</code>
	<code description="DRL Headlamp Settings: Eyebrow Only, No Angel Eyes">
		<group id="3005">
			<function start="0" end="15" mask="11111111b">00, 04, 00, 00, 00, 04, 00, 00, 64, 03, 00, 00, 00, 00, 00, 00</function>
		</group>
	</code>
	</cafd>

</FDL>

[stealth70mde]

packetpilot

I was able to enable the B&O menu in my car based on your findings although I wasn't able to see the cheat code in E-Sys.

It makes a difference when I set it up to "Expanded", a welcomed difference. Seems to sound better than the standard setting but it's hard to know if it sounds better, worse or the same than the Logic 7 setting.

My car was built early April 2016 and I think my iStep is 59.0.

Thanks anyway for this. Will test more tomorrow as I have a long 3 hour drive to do.

[Almaretto]

Originally Posted by packetpilot

- B&O Digital Signal Processing (replacing Logic7, requires HK system or 2016+)

The xml worked fine for me, but I do not understand the purpose of this this code. So you have HK system & leave LOGIC7_SYMBOL aktiv, but you just switched High_END_AUDIO_MENU to B&O's vole_insz without touching AUDIO_SYSTEM OR EQ_VARIANT?

[packetpilot]

Originally Posted by Almaretto

The xml worked fine for me, but I do not understand the purpose of this this code. So you have HK system & leave LOGIC7_SYMBOL aktiv, but you just switched High_END_AUDIO_MENU to B&O's vole_insz without touching AUDIO_SYSTEM OR EQ_VARIANT?

AFAICT, the B&O setting is just giving us the Digital Signal Processing mode in (what I believe to be) either a white-label amp, or simply an amp that's manufactured by Hardon (since they now own B&O), with a mode called "Expanded", replacing the "Logic7" mode.
The Expanded mode (again AFAICT) is a DSP enhancement that, unlike Logic7, does not utilize the front center dash driver, which is just crap and IMO only makes sense for movies. There's what I perceive to be a bit of channel phasing under the "Expanded" mode, but there doesn't seem to be anything close to (what my ears perceive to be) the bites out of the EQ that the Logic7 nonsense involves.

FWIW, I typically hate any DSP whatsoever, but the "Expanded" mode seems to widen the sound stage (through what seems to be simple channel phasing) in a way that seems to make sense for an offset listening position, without tainting the responsiveness curve.

Originally Posted by stealth70mde

packetpilot

I was able to enable the B&O menu in my car based on your findings although I wasn't able to see the cheat code in E-Sys.

It makes a difference when I set it up to "Expanded", a welcomed difference. Seems to sound better than the standard setting but it's hard to know if it sounds better, worse or the same than the Logic 7 setting.

My car was built early April 2016 and I think my iStep is 59.0.

Thanks anyway for this. Will test more tomorrow as I have a long 3 hour drive to do.

Sweet; I'm glad it's working out in some way--thanks for reporting back on the code not showing up; my QA of late has focused more on lighting. I'll try to address with a commit to the repo soon. Please report back if anything's awry; my setup's a bit of a deviation from stock, since my MusicarNW Full Bass Level 3 kit is feeding my under-seat subs. I have a feeling I did test the cheat manually, although my car has the 'first run' of the NBT2 aka 'NBT EVO' (there's an acronym that eludes me--FEUKO or something like that?), whereas perhaps yours has the 'final' version that doesn't straddle two major (hardware?) revisions... clues are welcome of course!
[edit: my differences also might come from having a hamstrung iDrive 6 Light running on my HU right now...]

Also, a new commit is about to push for a "Front Fog-Like" cheat, enabling VLD-based cornering-lights-as-fog-lights, for cars with VLD de-coding removed via VO coding. Not pasting here as that just encourages bad habits, so here's the sauce in the bottle.

[Sedan_Clan]

So much stuff to learn. I'm looking forward to my coding session Saturday.