.... there isn't much out there to help configure BMW's software the way a user wants at home.
I presume the sudden change in behaviour comes from the module that's been replaced? In BMW land for the can bus comms to behave on these old bikes (allowing features to operate as expected) there needs to be three modules that agree on the VO.
The Vehicle Order (VO) is a list of toys BMW fitted on the bike at build buried inside the brains of certain ECU modules. On these fossils it sits in the DME (engine ECU), the Cluster and the ZFE. I'm not an expert but the list is likely now incorrect on the new ZFE. And thus comms are now unable to get around the bike to let the cruise function.
On the Motoscan app the guy doesn't (and claims never will) support customers playing with the VO
The GS 911 wifi (or better), now has some elements of VO playtime in the current software releases - but you'll need to contact and see whether they can help. Its been quite a journey getting these features to mostly behave, and these days I suspect they may be able to help - but "adding cruise" is not a current option their tool supports.
The VO list was never meant to be fixed in stone - but you are meant to use a main dealer and the BMW diagnostics tools to do this type of work - Adding a feature / option officially is not something many dealers have done in this country - Usually there’s an FSC code (software license) to be purchased and paper trail for the dealership's parts dept to fill out before the dealer tools allow the new software to load on a particular vehicle - Paying for a dealer to do the work and where needed paying for the FSC makes a "retrofit option" official. Just the same as if it was fitted at the factory during its original build.
Of course following what you have said - your bike was built with cruise at build - and it’s the module replacement that (my guess) doesn't have the correct VO data. A dealership tends to be out of their depth at this point but the reality is its 20 mins work...
But they may tell you it not possible - because 1) they don't know better. 2) they don't want to get the old tool out of the cupboard and bother. 3) they don't like owners taking what they see as lucrative billable hours out of their pockets. 4) BMW don't want functioning old bikes - just new bike sales. 5) hate owners fixing stuff with second-hand parts.
If the module you now have on the bike is a suitable part - and all the components on the bike were on the original VO they could literally plug it in and flash the whole bike’s software i-level in 10 minutes and waste a few seconds following up a calibration of ESA if fitted.
you can study the VO BMW believe a particular vehicle has using chassis decode tools like https://bimmervin.com/en
the list would be something like this
I presume the sudden change in behaviour comes from the module that's been replaced? In BMW land for the can bus comms to behave on these old bikes (allowing features to operate as expected) there needs to be three modules that agree on the VO.
The Vehicle Order (VO) is a list of toys BMW fitted on the bike at build buried inside the brains of certain ECU modules. On these fossils it sits in the DME (engine ECU), the Cluster and the ZFE. I'm not an expert but the list is likely now incorrect on the new ZFE. And thus comms are now unable to get around the bike to let the cruise function.
On the Motoscan app the guy doesn't (and claims never will) support customers playing with the VO
The GS 911 wifi (or better), now has some elements of VO playtime in the current software releases - but you'll need to contact and see whether they can help. Its been quite a journey getting these features to mostly behave, and these days I suspect they may be able to help - but "adding cruise" is not a current option their tool supports.
The VO list was never meant to be fixed in stone - but you are meant to use a main dealer and the BMW diagnostics tools to do this type of work - Adding a feature / option officially is not something many dealers have done in this country - Usually there’s an FSC code (software license) to be purchased and paper trail for the dealership's parts dept to fill out before the dealer tools allow the new software to load on a particular vehicle - Paying for a dealer to do the work and where needed paying for the FSC makes a "retrofit option" official. Just the same as if it was fitted at the factory during its original build.
Of course following what you have said - your bike was built with cruise at build - and it’s the module replacement that (my guess) doesn't have the correct VO data. A dealership tends to be out of their depth at this point but the reality is its 20 mins work...
But they may tell you it not possible - because 1) they don't know better. 2) they don't want to get the old tool out of the cupboard and bother. 3) they don't like owners taking what they see as lucrative billable hours out of their pockets. 4) BMW don't want functioning old bikes - just new bike sales. 5) hate owners fixing stuff with second-hand parts.
If the module you now have on the bike is a suitable part - and all the components on the bike were on the original VO they could literally plug it in and flash the whole bike’s software i-level in 10 minutes and waste a few seconds following up a calibration of ESA if fitted.
you can study the VO BMW believe a particular vehicle has using chassis decode tools like https://bimmervin.com/en
the list would be something like this
| X0135 Control, operating concept X0321 Headlight left asymetric X0326 Speedometer mph X0381 Operating instructions, English X0416 ESA X0430 Safety pack X0432 Equipment package 2 X0519 Heated handlebar grips X0530 RDC X0538 Cruise control X0539 On-board computer X0590 Direction indicator LED white X0603 Alarm system X0630 I-ABS generation 2 X0736 National version Great Britain |
Last edited:



K25ADV in my case...




