[vrooooom]

When you guys say "code", it's not like coding in the sense of using Terminal w/ MacOS or MSDOS on a PC right? It's more like BimmerCode which is turning switches ON/OFF....am I correct? Coz I'm hyperventilating just reading coding sh*t out. I'm afraid of messing something up.


@F87 your contribution on this forum is immeasurable. Thanks.

[F87source]

Originally Posted by vrooooom

When you guys say "code", it's not like coding in the sense of using Terminal w/ MacOS or MSDOS on a PC right? It's more like BimmerCode which is turning switches ON/OFF....am I correct? Coz I'm hyperventilating just reading coding sh*t out. I'm afraid of messing something up.


@F87 your contribution on this forum is immeasurable. Thanks.

No not at all (and technically what you described is actually command line access of the computer, programming/coding would be writing lines of a programming language via a text editor or ide. You could do it directly to a terminal environment using something like nano or vim but either way that's super off topic).

But yes you're correct, it would be like bimmer code which is where you're turning on and off settings or toggling them to something else (this is known as fdl coding). Or it could be vo coding where you're making some changes to the vehicle order, aka changing a few bits of text. Nothing too crazy.

[varooshgog]

Originally Posted by F87source

That's because the dct isn't codeable, so obviously protool cant code it. I talked to protool and they confirmed this as well = Dcts can only be flashed. So you'll need xhp, or get esys to flash it.


But generally speaking if you can code (code not flash) it on esys you can do it on protool - especially on the older cars (such as the f series) that have been fully mapped out.

That’s fair. I think it is important to call out the distinction between “coding” and “flashing” since they can be misinterpreted to mean the same thing for those unfamiliar to automative software/hardware.

It’s still a great tool, just need to manage expectations and point people to folks like kuba86 if they just want to do the basic differential and dct changes, and don’t care for some of the other coding changes or diagnostics of protool.

[F87source]

Originally Posted by varooshgog

That’s fair. I think it is important to call out the distinction between “coding” and “flashing” since they can be misinterpreted to mean the same thing for those unfamiliar to automative software/hardware.

It’s still a great tool, just need to manage expectations and point people to folks like kuba86 if they just want to do the basic differential and dct changes, and don’t care for some of the other coding changes or diagnostics of protool.

Personally I would rather code things myself since it allows me the ability to change it an unlimited amount of times instantaneously - something you don't get to do if you hire someone to code for you.

Then with the dct id rather have xhp as well, because again id rather be able to change things on my own whim.

Only if I can't do something then id hire someone to do it for me, such as generating fsc codes.