google
site:nefariousmotorsports.com map switching

based on your last post this is way over your level but best of luck understanding these things

2nd prj.

The "maps" you are suggesting are called "using the throttle to tell the car what you want".

If you were talking about race gas, e85, or water meth map variants that would be something entirely different.

Hi,

so I spent a few minutes skimming the forum and internet and am looking for some clarification I am investigating the right area and not "re-inventing the wheel"

what I assumed my original question would be answered with was -

1. Download NEFMOTO_ME7_MULTIMAP
2. Create 1,2,3.. saved as bins MAP1.bin, MAP2.bin, MAP3.bin
3. run NEFMOTO_ME7_MULTIMAP
4. flash multimaps.bin to ECU

--- to change current map
1. press brake
2. switch to ignition 2
3. press gas pedal 1 or 2 or 3 times to change map to 1,2 or 3
4. release brake pedal
5. start engine


----------------------


it seems pretty obvious my assumption above was incorrect


so, whilst walking the dogs I pondered this below...  can someone clarify whether in actual fact I need to do something more like below -
1. create new XDF Entries for max rpm, max load etc etc for each different setting(s) I want to make switchable
2. create a single bin with all of the map1, map2, map3 file items.
3. review the reverse engineering threads and learn how to program the following sort of pseudo code..
    3a. edit the bin (using Macro Assembler? or what else C?) is it compiled or interpreted? - can I find an editor/decompiler on the forum?
    3b. I assume this has a main loop like an Arduino board processor
    3c. if ign = on and engine speed = 0 and on time < 10 seconds and brake = on and accel pedal > 80% then togglemap ++
    3d  if ign = on and engine speed = 0 and on time > 10 seconds and togglemap>0
           3di. flash EML togglemap times
           3dii. for each mappsetting
                       copy map(togglemap) location to real map location


?  If the above is in the right sort of area of investigation, I have a couple of questions.


1. am I copying the MAP settings on the EPROM or in RAM - eg are the map changes lost on a restart of the car

2. I assumed the bin was only the data rather than the processor, in which case does the normal checksum APIs still work for actual code instead of data?

3.  is there an emulator which can use the USB to ODB2 Flash Cable for bench flashing in order to simulate engine speed, pedal press, etc or would I need to create some Arduino program hooking into the ECU and wiring up wires to mean brake accel, engine speed etc to test?


4. if it is persistent then to test I assume I can simply flash the ECU->Switch on Ignition->Test the Brake and Accelerator Presses->Read back the ECU file and make sure the "current map", "lamfa", "LDRXN" etc are all matching the mapn versions


5. has anyone done this already on a BAM 1.8T to use brake and accelerator.



am I in the right sort of area?


Thanks









if this is in the right area

  
  
  
 

lol so, "no not in the right area" then? 

maybe I skimmed the wrong threads?

do you have a 1.8T BAM map switching bin, using brake pedal and accelerator pedal?

what 99% of those modes do, is basically change KFPED map... your throttle is what controls how your car drives lol. You dont do WOT when you are driving in city do you ? you should do map swithcing if you are mapping for different stuff like gas, meth, nitrous etc.

okay for different fuels, or unplug the N75 if leaving with someone, it doesn't mean I dont want to try and do it from an interest point of view.  no offence to TT MK1 owners but there's not a lot of interesting stuff going on, and when a project is running out of "free" project things to do - it means you pay for some hardware updates instead.

Below is the thread which made me think you need to update your individual bin files for more use than data / settings - I might be miles off what is required but finding examples of S4 cruise control map switches are no good for a TT without cruise control and retro fitting cruise control is not a good workaround for me.

I have a spare ECU (if it gets bricked) and PSU etc to put into boot mode if it goes wrong and to test files etc.   if it is simply "too difficult to do" then so be it,  but I honestly originally thought that the map switcher was like a pre-startup map selector, but appears to be far more involved, and probably why it's sold as a base map.


http://nefariousmotorsports.com/forum/index.php?action=printpage;topic=12637.0

This thread above, ended up with mainly arguing over who has screenshots of thanks for someone important  but I do like the idea of removing the checksum test, I suppose this is maybe how people encrypt their maps from being read.

Decided once I have sorted the map switch method; valet mode will be by simply setting CWMDAPP 0x181BD to 8 to enforce the test mode and then it will switch to using the fixed waste gate duty cycle table kfldrapp which will be set to low wgdc.

This will be an easy test it is switched over and could actually be the default map in case the battery is disconnected for a prolonged period.