i know the basemapping procedure for a stock map sensor but, would it be any different for a 2.5/3 bar one??
the reason i ask is because on Chris's site it says he wont make a basemap for larger sensors, and i was wondering if this is because the procedure is diff/unreliable for the larger sensors.

 

I think it kind of depends on what program your using but I know with Uberdata's 3bar sensor you need to rewrite the map scalars to match the sensor. It does take a bit more extra work but it works. As with any basemap though it needs to be tuned, and as we all know the more boost/pressures your engine is recieving the more critical the tuning has to be. Thats probably why Xenocron and others don't want to mess with the 3bar for someones basemap. Thats a setup that needs to be tuned, not run on a basemap.

 

it would be done with TE which has the option for 2/2.5/3 bar. i know running hard on a basemap isnt good but how would you create a starting point to tune past ~11psi ?? is it the same as making a basemap for a stock MAPsensor??

 

Tuning is the same principles from one sensor to the next..

..as far as code.. it's an adjustment in the MAP scalars. TE does it a bit different than UD/Crome.. but ends up with the same result.

 

so i should create a basemap but select the proper MAP size before starting??
no need for a diff anmount of retard or additional fuel?? thats what i am concerned with while making the basemap

 

Exactly...a basemap is iffy at best generally, unless it comes from a nearly identical tuned setup (which is rare).

I have started making basemaps for the Motorola 2.5 Bar Maps in Crome, but thats only because I can set a boost cut at 5psi and not have to worry about them overboosting and killing their motor before being tuned.