Shouldn't be too difficult.

All you would need is a very basic function that monitors the contents of the ram address and jumps to the right location in the map switching routine any time the value changes. You would also have to change one jump in the map switching routine to avoid an infinte loop.

I'll get you the specifics when I get the chance, but it should really only take a few bytes of code.

Well actually I think he is more interested in switching the maps from a kpw comm. I can see how cool this can be when you are using some kind of touchscreen in your car to select driving modes.

This is the kind of functionality I was hoping was already "in there" or at least could be hacked to work by poking at the routines by writing one or more set of memory locations directly.  If this isn't workable, I'm fine because my main goal was to be able to read the mapset in use, more than write it.


I'm also trying to keep this all working over the typical, blue logging cable.  Without digging back in to the wiring diagrams, I don't think my B5 has CAN-BUS at the OBD connector.  KWP can be used over K-line as well as CAN-BUS so if it's low-level ECU stuff, I may not need CAN-BUS. 


My bug.  :-)

the whole mapswitch stuff is completly after the normal stuff where in a normal bin only is FF in hex editor right?

so if i transfer everthing to my M box bin, the mapswitch works should also work in there?  i use a M box bin in a 2000 eu spec a6 ajk with s4 agb cams and bosch maf so i propably cant use the bin attached in here?

then i definitly cant do that.. maybe somebody could help me with that?

On it

But yea, the routine needs to be referenced or it's not going to do anything

Is it reasonable to use the HEX parts of this code on a 7.1.1 file? I think disassembly is beyond my scope at the moment.