Any help with a MAP for a MS2 extra

[bug_n_67]

I'm all set to do my change over from my stock 67 Beetle to my EFI turbo with a MS2 extra. I met someone at the Great Canadian Bug show who was going to email me a MAP as a starting point for my MS2 as we were running pretty much the same set up, but haven't heard from him. So I'm looking for a little help, if anyone has some thing close to what I'm running could they pass a MAP along as a starting point.
EDIS (using the EDIS Module)
1914 engine
turbo 7lb boost
The only thing I haven't bought yet are the injectors as I'm not sure of the size to get.

[woodsbuggy1]

John,
I see you have made it to the stf. I can send my starting tune when you send me your email address.
Take Care
Kenric

[bug_n_67]

Nothing, someone must have something that I could use as a starting point or maybe point me another form that might be able to help with a VW MS2 setup.

Thanks

[trbugman]

Honestly with MS and the unique engines they are installed on, using another persons tune causes more problems than it helps. The only real exception is the plug and play units because they are going on a known setup for the most part. 99.9% of the time your better to start off with the example tune that is provided with TunerStudio and adjust it to your needs.

[Piledriver]

Tunerstudios VEAL can nail down a VE table in ~20 minutes using only a few on ramp cycles.

If you have hills nearby those work even better.

Setting a reasonable lambda delay allows TS to work well with varying RPMs/loads.
The default is not reasonable unless you have a SBC and cast iron log manifolds.

The autotune in MLV has one delay setting. Choose carefully (and it is likely to always be wrong)
...delay can be >2 seconds at idle RPM/load with typical headers and the WB after the collector.
If you only allow it to autotune above ~4K and ~70KPA you may get reasonable results.
For me it just messes up an already ~perfect table with noise.