Hi all

Once again my apologies for what might be a redundant or dumb question, but here goes...

I went for a drive tonight with the stock ECU running the show while the MS1 setup to log all the various inputs etc so I can keep a reference of what the stock ECU does. Makes me wonder if there's a way the MS can be set to learn / mimics how the stock ECU behaves, self learning sort of speak, I realized there's an auto tune feature built into the MS but have heard that it's not as good as it sounds.

Mine's a stock motor with mild engine mods (Cams, exhaust, intake) so I find the stock ECU is quite safe for the setup, I'd like to be able to start out with this tune and slow work my way around. Currently I have no confidence in the MS at anything other than cruise mode.

I'm sure if I was to manually track through the log via MLV I'll be able to come up with an AFR target table, but seems redundant.

Is there a way in MLV / MegaTune to say "Use this log to setup my AFR target table, Timing and whatever else useful" ?

Would be pretty nice!!

Here's the log of my stock ECU...

 

why not just tune the car? Why does everyone make this so hard?

 

I know where you're coming from hustler, it cost quite a bit to tune so I'd only want to tune it once I've all that needs doing, possible FI of some sort...shhhh!!!...other half is sleeping (it's 1:35am here in Aus)...she can't know I'm spending more on the car :(. But in the mean time I'd like to start getting to know the MS but trying to do it as safe as possible.

 

Not if you do it on the street with a WBO2.

Step 1: Steal somebody else's MSQ (or use the DIYAutoTune base maps) and make sure your AFR Targets table is as you desire it to be.
Step 2: Give gEGO a broad authority and a fast response time.
Step 3: Start the engine. Make initial coarse corrections by hand.
Step 4: Datalog. Use MLV to auto-correct the VE table (use VEX export / import) and then push the modified VE table back into the MS.
Step 5: Repeat step 4.
Step 6: Repeat step 4.
Step 7: Slow down gEGO a bit, and repeat step 4.

etc.

 

Thats pretty much the way most of the guys do it here.

But, if you have been keeping tabs on TunerStudioMS, there will be a new feature in the release version that will incorporate MLV into TunerStudioMS for on the fly changes. Its crazy.

 

People seriously buy EFI without a wideband?

 

Sorry to threadjack, and i'm gonna let you finish but...

Is there an easy way to just export the vex without closing megatune, opening the map offline, exporting, closing megatune, and importing the vex?

 

Luckily I have one so it helps with VE table, but I wonder how you could tune timing without a visit to the dyno?

 

uhm. what?

I use my friends...
File
Open

 

I didn't need to close MegaTune when working with MLV; I have both open at the same time, after exporting the VEX from MLV, I simply switch over to MegaTune and import table and burn to ECU.

Never need to go offline to load VEX or MSQ, my MS is configured for Inverted Spark though (Awesome mod btw Joe Perez )

 

Yes.

 

Is there an easy way of just importing the VEX file from an msq you just saved after a ve analysis? I just dont like the idea of burning an entire msq file over and over again. A lot of room for error.

 

Nvm, just ignore me. I see the little export button now.

 

I use tunerstudio. I believe it only updates changed information when you ask it to upload.

 

Assuming you are doing this in realtime, with both MT and MLV on the same machine:

1: Open MT.

2: Start a datalog, and drive.

3: When finished, stop the log, and save the MSQ.

4: Open MLV.

5: Within MLV, import the log and the MSQ and perform the analysis.

6: Within MLV, export the modified VE table to a .VEX file.

7: Switch back over to MT, open the VE1 window, import the VEX, burn it, and close the VE1 window.

8: Goto 2.

 

just get the fuel table/enrichments/idle/cold start right, then go to a steady-state dyno and tune spark, its not hard. This is discussed ad nauseam in the DIY instructions.

 

I saw one guy on another forum who managed to capture his stock ECU's timing map by driving around with a timing light and web cam zip tied under his hood. I'm not entirely sure why you would want to log the stock ECU's timing curve in a Miata when there are a lot of good timing base maps out there, however.

Logging the stock timing map or fuel map would require extra IRQ pins that are not available in the MegaSquirt processor. Although I suppose somebody with enough determination could make a signal that converts duty cycle to a voltage and log it through a spare ADC.

 

I've logged the stock timing map on my 2002 via OBD-II, but it looks nothing like the MS map I use. It just knocked everywhere if I used the stock values.

Jim