[DayvG]

You could try and Google esys ultra, would’ve been quicker than asking here

[Dany]

You could try and Google esys ultra, would’ve been quicker than asking here

Thanks mate, I will have a look

[st1]

Who is the developer of Esys Ultra?
Appears to lag the latest software compatibility compared to Bimmer Utility.
Is it any better or worse than BU?

[DayvG]

Who is the developer of Esys Ultra?
Appears to lag the latest software compatibility compared to Bimmer Utility.
Is it any better or worse than BU?

Bimmer utility will work with all versions of esys because BU only uses Esys to load the already modified CAFD/NCD. They are programs that work independently of each other. Esys ultra and other solutions need to physically add support to newer versions of esys. Remember, 3.40 is the base version with 3.40.1 and 3.40.2 being very very minor updates to the software. So minor that you would not notice any difference. Unless you’re a version whore that MUST use the latest version of everything.

As for better or worse, it’s a preference. Some want the simplicity of just using an esys based system. Everything right there in “esys” whilst others want a separate tool to do the “FDL” editing that isn’t esys based because they simply don’t understand/like/want to learn esys. Options for the community, decide for yourself what you prefer. But in essence, if you want to FDL code, they both achieve the exact same thing.

[Node]

I guess st1 meant that the latest version mapped in EsysUltra is still 4.34.20, while BU has had 4.35.42 mapped for quite some time now.

Personnaly I like that BU is a separate utility so they are not tied to limitations of ESys GUI. Like when searching for specific setting you need to change in FDL:
1. In BU you just write criteria and whole list is filtered out leaving the FDL entries which match the criteria ONLY. So if you need to code something related to seatbelt, you immediately see ALL 5 or 10 entries related to seatbelts. ALONG with their current values which you can just change with two clicks each.
2. In ESys you write criteria and then need to click search many many times to go through all such FDL entries. And you just can't see how many there are and what they values are without INSANE amount of clicking. And if you missed one by an extra click on search - just need to start clicking from the start. And changing values requires also huge amount of clicking.

So it's not an issue of not liking or not learning Esys. It's just that Esys is an engineering tool and was never meant to be user friendly from the start. Otherwise I agree that you can achieve same thing in the end. The difference is in time needed to achieve it.

Of course if you are only applying cheat sheets instead of doing manual work, then it's much less of a hassle.