dv52 Posted August 2, 2025 Report Share Posted August 2, 2025 @Artriel: Jeffery: I hope that I'm not understanding your reply correctly - but I most definitely do NOT condone IP theft!! If by "a generic OBD2 to USB cable from Amazon" you mean a VCDS clone, then I suggest that you consider that the only reason why the theft of Ross-Tech's hard-earned intellectual property is made possible is because there are willing buyers!! Hmmm.......... again I hope that I'm wrong!! Don Quote Link to comment Share on other sites More sharing options...
Artriel Posted September 5, 2025 Author Report Share Posted September 5, 2025 On 02/08/2025 at 11:00, dv52 said: @Artriel: Jeffery: I hope that I'm not understanding your reply correctly - but I most definitely do NOT condone IP theft!! If by "a generic OBD2 to USB cable from Amazon" you mean a VCDS clone, then I suggest that you consider that the only reason why the theft of Ross-Tech's hard-earned intellectual property is made possible is because there are willing buyers!! Hmmm.......... again I hope that I'm wrong!! Don Hey mate. I had no idea that the generic cables are stealing IP. Ive just taken delivery of an OBDEleven 3 pro kit with 100 credits. Ive had a quick play around with it and using the VAG version of the obdeleven app is fantastic and has much more in depth features than the Carly ecosystem. Quote Link to comment Share on other sites More sharing options...
dv52 Posted September 5, 2025 Report Share Posted September 5, 2025 @Artriel Jeff: Excellent choice!! Try and make a few errors - it's the best way to learn how to use the device! Enjoy!! Don Quote Link to comment Share on other sites More sharing options...
Artriel Posted September 6, 2025 Author Report Share Posted September 6, 2025 2 hours ago, dv52 said: @Artriel Jeff: Excellent choice!! Try and make a few errors - it's the best way to learn how to use the device! Enjoy!! Don Yeah I'm planning on getting more into it this afternoon. Are adaptations the changes you can make that are easily accessible and long codes are more in depth and require more experience and knowledge? Quote Link to comment Share on other sites More sharing options...
dv52 Posted September 6, 2025 Report Share Posted September 6, 2025 @Artriel Jeffery: I'm going to attempt a very amateur and unofficial response to your most excellent question: what's the difference between Adaptation channels and long-code when coding modules? BUT, I start with the fundamental dilemma that I don't believe that there is an official explanation of these terms in the real world outside the VW mother-ship. I'm more than happy for a forum colleague to correct my assertion -please!! My response below is therefore my personal hunch based on my student days learning about control systems theory and production engineering. So, rather than providing the definitive answer to your question - my objective is to create a type of straw-man hypothesis for others who are better informed to correct the errors in my mental meanderings!!😉 So, here goes - alas it will be a bumpy ride because my explanation needs to get a bit geeky! As an overall response to your question - the two coding types have entirely different purposes: Adaptation channels tell the module how to operate the functions that it controls Long-code tells the module which peripherals have been installed (and therefore which software subroutines to operate) Adaptation channels: First, a short intro to control system theory. The multiple modules in a car are ostensibly devices for controlling functions in an environment that is constantly changing (i.e. they are "control modules"). To do this, these modules contain an internal "model" of the function that is being controlled and they use transducers/sensors to measure the real world environment. Software in the module, adjusts the behavior of the internal model using the measured external variables from sensors to provide a predetermined output. These arrangements are called "closed system control loops" meaning that the sensors change the module output via a feedback loop. The simplest form of this control system has just one feedback-loop (see below) More sophisticated modules employ "adaptive" control system design - this is a type of non-linear operating arrangement. Adaptive control detects changes in the operation of a function/device and it "adapts" a bunch of controlling parameters automatically to compensate for the altering conditions in the external world (often, in a way that optimizes the loop response). The use of variable "adaptation parameters" is separate (but obviously, related) to the module's primary purpose. The main reason for using adaptive control in these modules is that most processes in today's vehicles have complex, nonlinear responses - and the processes are often, initially uncertain. At a high-level, the structure of Adaptive control systems look like this: So-comparing the two diagrams, hopefully you can see that adaptive control modules have 2 x "control system loops": one loop is the normal, primary feedback loop as described earlier and the other loop is the parameter adjustment loop. I suspect that the adaptation channel database in a module contains a list of the adjustable parameters for a bunch of secondary loops as shown above (again, I'm guessing). Long-code: The module long-code string has an entirely different purpose - which I suspect is related in the main to the needs of the mass production process. Long-code appears to be a much lower level control mechanism in the module. At least for the modules with which I'm familiar (which use mostly the newer UDS/ODX protocol)- it's easiest to think about long-code as being a bank of simple software switches. Again, at least for newer modules- long code is normally reported as a series of numbers with occasional alpha characters like A,B,C.....F. These are in fact Hexadecimal pairs - meaning that the values use a base 16 counting system. I'm not sure if older modules used different counting systems - perhaps octal, or even quaternary? Hexadecimal numbers have an equivalence in Binary arithmetic (which is counting in base 2) and a hexadecimal pair can be represented as 8 x binary Bits. To use the previous analogy, each Bit can be thought-of as a single software switch that can have a status of either OFF, or ON. In terms of how long-code is used, I suspect that long-code tells the module which of many available options were installed on the factory production line (and equally important - which options/features were NOT installed). Further, I suspect that internal to the module, long-code Bits turn-ON/OFF certain software subroutines in the module firmware thereby aligning the module's operations with the car's physical installations. On the VW vehicle production line, the available options that a car-buyer can select is translated into a long list of "PR codes". I suggest that you Google the term). My hunch is that each Bit in every Byte corresponds to a PR code - so the complete module long-code string is simply a coded list of the installed peripherals as installed on the assembly line . So, if you are still following this - hopefully it's clear that adaptation channels play a role in how the module controls its primary function and it's equally clear that long-code determines which of the available features/options within the module firmware to use in controlling the pimary activity. Now, I've absolutely no doubt that there will be numerous examples where the strict distinctions made above are violated on various modules. As an example, I'm aware that the BCM on late model MQB platform cars have no long-code string, at all (i.e. ALL of the software switches in previous modules have been transferred to adaptation channels). So yes, these are not hard-and-fast distinctions. Nevertheless, I hope the "straw-man" may prompt responses from others I bet you are now sorry that you asked the question!!😉 Don Artriel 1 Quote Link to comment Share on other sites More sharing options...
AHG Posted September 6, 2025 Report Share Posted September 6, 2025 My experience in the OBD11 is that sometimes things move from adaptation to long coding and the other way around … not to negate the previous and detailed explanation. In my experience, on the practical side (what you need to press to do something) it did happen that som options I switched on or off in one car using adaptation, in other cars it was in the same module but in long coding, doing exactly the same thing. So maybe OBDeleven just don’t really tell them apart 🙂 Artriel 1 Quote Link to comment Share on other sites More sharing options...
dv52 Posted September 6, 2025 Report Share Posted September 6, 2025 1 hour ago, AHG said: My experience in the OBD11 is that sometimes things move from adaptation to long coding and the other way around … not to negate the previous and detailed explanation. In my experience, on the practical side (what you need to press to do something) it did happen that som options I switched on or off in one car using adaptation, in other cars it was in the same module but in long coding, doing exactly the same thing. So maybe OBDeleven just don’t really tell them apart 🙂 @AHG: Hmm..... I might be reading your words wrong (my apology if so) - but regardless of manufacturer, NO diagnostic device can read differently the designation of a particular module function as either an adaptation channel, or a long-code. When making code changes - ALL diagnostic devices simply read how function to be change has been defined in the module at the module design stage. That said, often a particular module function can appear in both the adaptation channel database AND in the module long-code string. When this happens, the separate entries do different things (albeit both entries may impact the same module function)! Here's an example: When retrofitting the fog-light on a Golf mk7 (pre-FL), the code change involves both a modification to the 09 module long-code string AND to the 09 module adaptation channels. The former tells the module that the new fog-light has been installed (and connected to a pin on the 09 module) and the latter instructs the module how to operate the lamp But again, the function of each Bit in every Byte in the module long-code AND the purpose of every individual adaptation channel is fundamentally defined at the module design stage - NO diagnostic device can change this definition and AFAIK, every tool must "tell them apart" in the same way! Don Artriel 1 Quote Link to comment Share on other sites More sharing options...
AHG Posted September 7, 2025 Report Share Posted September 7, 2025 As far as I know it may be pretending to be adaptation while it’s actually long code, maybe it’s the app that shows it that way. I’m just reporting what has happened. A few times the exact same option lost, with exact same function s doing the same thing, showed in one of the two in one car and on the other in another car (the two being adaptations and long coding). My experience is with OBDeleven ONLY not saying anything about the car or any other app used Quote Link to comment Share on other sites More sharing options...
dv52 Posted September 7, 2025 Report Share Posted September 7, 2025 @AHG: Thanks for clarifying your point. I suspect that our different views will remain different - ain't nothing wrong with that !!😉 In deference to your standing on this forum as a Senior Member - I've attempted to find a reason for your resolute position Maybe your OBD11 experience where "it may be pretending to be adaptation while it’s actually long code" can indeed be explained? I note from the list of vehicles in your signature that both "Bluey" and your Audi S3 8V are MQB platform vehicles. As I mentioned in my (geeky) explanation to OP - the module that OBD11 calls "central electrics" on MQB platform cars has undergone rudimentary design changes. In summary, the early version 09-module in these cars had the "normal" division of module functions into long-code and adaptation channels (as I describe). However, around mid-2016 stuff changed and the boffins on the VAG mother-ship decided to deactivate the long-code function on the 09 module for ALL newer MQB platform cars. Diagnostic devices report the long-code in newer 09-modules as either a zero-string, or there is no report at all! This change was fundamental because it meant that in addition to entirely deleting the long-code facility - every software switch (i.e. every Bit) function in the previous version module had to be added to the already humongous adaptation channel database on newer version modules! Of course an obvious consequence of this change was that tweak instructions for post 2016 central electrics modules also had to change. Specifically, tweaks that previously accessed the module long-code string, now needed to access the adaptation channel database! It's entirely possible that when implementing tweaks on "Bluey" and the S3 that this changed dynamic could be viewed as the module function "pretending to be adaptation while it’s actually long code". However, this pretense is an illusion - in truth, the adaptation channel reference is correct for newer 09-modules. So maybe this is the reason for your experience? If so, this is NOT particularly an OBD11 thing -the change also impacted all other diagnostic devices in exactly the same manner Totally guessing - of course!! Don AHG 1 Quote Link to comment Share on other sites More sharing options...
AHG Posted September 8, 2025 Report Share Posted September 8, 2025 Sounds logical, and includes tons of info that I didn’t know. Personally, my knowledge on coding is nearly zero. Just tried a few things and know what worked for me. I never really coded (when there were actual codes to remember and write) such as with RossTech VCDS or any of the others (Carly, Calista, etc.). Therefore, we can’t have different opinions because I was not stating an opinion (I don’t have knowledge on the matter to form one) just providing data of things that happened (without knowing why they did) hoping you or someone else can explain them. For me, as a stupid user pressing buttons, today I know to look in both Adaptations and LongCoding as I know (for a fact, which I can’t explain) that sometimes things I expected to see in one actually appeared in the other (in different cars, not in the same car. Some added info, I coded GTI, Tiguan, S1, S3, and a few more, and I don tre,,beer which was different than the other, but numerous things “move” when jumping from car to car (even between modules, but more seldom). So that info is factual, not opinion. As per why, I haven’t the slightest clue. I thought maybe OBDeleven are trying to keep us alert so we don’t get bored, but your explanation sounds more plausible and would affect users that use RossTech, Carists, Carly etc. dv52 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.