Cool. Thanks!

 

What was this you said about a spark plug tube being filled with oil? Have you checked into/resolved that issue?

 

Yeah tube seal on valve cover. Took it off cleaned everything and seems good now. Going to order a whole new set anyway. After looking at the seals the one that leaked seems to be different than the other 3. The other 3 have numbers on them the one that leaked didn't. It was a used cover I got to do wrinkle black. The seals looked fine so I kept them on there.

 

So took the car out to do a log today it boosted smooth today. But still need to find out why a/f goes full lean when car and fuel warms up. But now I can't get my Laptop to hook back to the ems after I uploaded a revised calibration from my tuner a pop up comes up saying oops unhandled exception with a bunch of numbers and stuff that means nothing to me. And AEM isn't opened

Do have a brand turbo to Mani and Mani to engine gaskets to try and stop the lil exhaust leak I hear.

And to top the day off on my drive doing the log...my dipstick popped out covering my clean engine bay with oil! And my laptop died and didn't save my log! Atleast its not snowing .......ok that's my rant ...now time to order pizza and hang with the gf.

If anyone knows why I can't hook to my ems please let me know

Thanks

 

Can you screen shot the exceptions that are thrown when you try to upload the calibration? My preliminary guess is that you have a version mismatch. Sorry to read that the logging didn't go well today.

 

Version: AEMTuner v3.2 build 08/06/2013
Core Version: AEMTuner v3.2 build 8/6/2013
Time: Sunday, November 02, 2014 4:05:05 PM
Details:
AEM.Shared.Exceptions.CUnhandledException: An Unhandled exception was found. It will be logged and execution will continue. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at AEM.Shared.Calibration.COutputPin.set_UsedByCoilOr Injector(Boolean value)
at AEM.Shared.Calibration.CCalibration.InjectorActive Changed(CInjectorFunction pInjector, Boolean bOldValue)
at AEM.Shared.Calibration.CCalibration.Init(Boolean fixInvalidOptionsFirst)
at AEM.Shared.Calibration.CCalibration..ctor(CCalibra tionDefinition pCalDef, ICal* cal, Gin* gin, Boolean fixInvalidOptions)
at AEM.Shared.Calibration.CCalibration.CreateCalibrat ionFromMediator(CCalibrationDefinition calDef)
at AEM.FileIO.CFileIOManager.0(String , Boolean )
at AEM.FileIO.CFileIOManager.ReadCalibrationToLoad(St ring fileName)
at 0.1C.3(String strCalibrationFileName)
at 0.1C.a(String )
at 0.1C.DoStartupSequence()
at AEMTuner.AEMTunerForm.Y()
at AEMTuner.AEMTunerForm.0(Object , EventArgs )
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Mes sage& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
--- End of inner exception stack trace ---

This is what comes up in the pop up box. wont let me do anything

 

This happens when trying to open the software or when trying to upload or open the calibration?

 

It comes up if I open aemtuner on my laptop. I uploaded a new calibration from my tuner and went to do a log and my laptop died. I plugged my laptop in nd tried to open aemtuner and this pops up in a window. And I can't do anything. I'm just learning aemtuner so this is all new to me.
I thought about trying to redownload aemtuner to see if it goes away. Haven't tried yet.

 

Tried to re-install AEMtuner still getting the same pop up.

 

Well AEM was no help! Said my laptop going dead could of fried my ems and he has no clue why I'm getting that message. :/