TephraXMOD V2
Newbie
Joined: Dec 2011
Posts: 34
Likes: 0
From: USA
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
MOMO 
its in da mail..
it was a 2012 so it only just got finished.
not sure whats up with Chets ROM, i think he needs to load the basic info in to a stock V2 (injector+maf) and see if it still does it... pretty strange, no one else has that issue
its in da mail.. it was a 2012 so it only just got finished.
not sure whats up with Chets ROM, i think he needs to load the basic info in to a stock V2 (injector+maf) and see if it still does it... pretty strange, no one else has that issue
The problem is the V2. An identical V1 rom drives awesome.
Newbie
Joined: Sep 2014
Posts: 3
Likes: 0
From: Perth
Help a noob out.
On topic for thread, just need a idea if i'm going about this the right way.
Bought XmodV2, have existing tuned rom on file, load both into ecuflash, click compare roms, copy and paste all tables that contain differences from existing rom to new rom, setup new tables and features as needed. Am I on track, or am I going to explode car?
New rom id is 53040210, old was 53040010, does this need a bench flash or is ecuflash able to do this in car now?
Hundreds of searches and I've read enough to tune a space shuttle, but just these basics are hard to find.
Cheers.
On topic for thread, just need a idea if i'm going about this the right way.
Bought XmodV2, have existing tuned rom on file, load both into ecuflash, click compare roms, copy and paste all tables that contain differences from existing rom to new rom, setup new tables and features as needed. Am I on track, or am I going to explode car?
New rom id is 53040210, old was 53040010, does this need a bench flash or is ecuflash able to do this in car now?
Hundreds of searches and I've read enough to tune a space shuttle, but just these basics are hard to find.
Cheers.
Help a noob out.
On topic for thread, just need a idea if i'm going about this the right way.
Bought XmodV2, have existing tuned rom on file, load both into ecuflash, click compare roms, copy and paste all tables that contain differences from existing rom to new rom, setup new tables and features as needed. Am I on track, or am I going to explode car?
New rom id is 53040210, old was 53040010, does this need a bench flash or is ecuflash able to do this in car now?
Hundreds of searches and I've read enough to tune a space shuttle, but just these basics are hard to find.
Cheers.
On topic for thread, just need a idea if i'm going about this the right way.
Bought XmodV2, have existing tuned rom on file, load both into ecuflash, click compare roms, copy and paste all tables that contain differences from existing rom to new rom, setup new tables and features as needed. Am I on track, or am I going to explode car?
New rom id is 53040210, old was 53040010, does this need a bench flash or is ecuflash able to do this in car now?
Hundreds of searches and I've read enough to tune a space shuttle, but just these basics are hard to find.
Cheers.
As far as bench flashing I haven't seen any word of the version of ECUFlash that supports the V2 requirement eliminating the bench flash method. I did just notice v1.44.4347 was out yesterday but from the thread I saw that was a fix for a certain issue not related to V2 flashing support.
THANK YOU! 2012 is like the red headed step child of roms.
i haven't flashed yet but it looks like bench flash isn't necessary anymore. directions state to use newest ecuflash version and run a supplied registry edit to enable writing to protected areas of the ecu.
As far as bench flashing I haven't seen any word of the version of ECUFlash that supports the V2 requirement eliminating the bench flash method. I did just notice v1.44.4347 was out yesterday but from the thread I saw that was a fix for a certain issue not related to V2 flashing support.
Newbie
Joined: Sep 2014
Posts: 3
Likes: 0
From: Perth
Awesome, learnt more than I thought.
...'Run a supplied registry edit'... If you could point me in the direction of said instructions, would be appreciated. I do recall reading something along those lines but have zero idea on where I read it.
Thanks again.
Thanks again.
Oh nice, what's the registry modification?
I have a 2011 V2 ROM ready to flash over the current 2013 V2 ROM on my 2011 ECU I've just been waiting for the ability to not have to bench flash.
So, what is the setting?
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
so the registry patch (that I send you, but if didn't just let me know) lets V2 be flashed without benching the ECU.
it doesn't, however, allow a completely different ROMID to be flashed - where that flash would change other areas of the protected segment.
it doesn't, however, allow a completely different ROMID to be flashed - where that flash would change other areas of the protected segment.
As always thanks David!
Newbie
Joined: Sep 2014
Posts: 3
Likes: 0
From: Perth
If so, would need to get that from you mate, wasn't on my email.
georgewatts2 at bigpond dot com
Cheers for the info fellas
got home yesterday, played the copy paste table game for a while then flashed. the patch worked perfect. flashed V2 over with no bench needed.
the only hiccup i'm running into is an error trying to use Live Tuner. i get this error:
i know the live tuner instructions say: "Live Tuner utilises the definitions included in ECUFlash, this means that Live Tuner looks at the rommetadata directory for defintion files, it also means that any errors received during a ROM Load need to be resolved in that location."
my laptop is windows 8, has .NET 4.0. the rommetadata directory is in C:\Program Files (x86)\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\
has definition files for my base rom, rax patch, and obviously definitions for v2. searching MAF Scaling in the 3 xml files but everything looked okay.
if you proceed with live tuner and select a drop down item this is the error:
the only hiccup i'm running into is an error trying to use Live Tuner. i get this error:
i know the live tuner instructions say: "Live Tuner utilises the definitions included in ECUFlash, this means that Live Tuner looks at the rommetadata directory for defintion files, it also means that any errors received during a ROM Load need to be resolved in that location."
my laptop is windows 8, has .NET 4.0. the rommetadata directory is in C:\Program Files (x86)\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\
has definition files for my base rom, rax patch, and obviously definitions for v2. searching MAF Scaling in the 3 xml files but everything looked okay.
if you proceed with live tuner and select a drop down item this is the error:
Code:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ObjectDisposedException: Cannot access a closed file.
at System.IO.__Error.FileNotOpen()
at System.IO.FileStream.Seek(Int64 offset, SeekOrigin origin)
at Live_Tuner.Live_Tuner.LocalROM_Query(UInt32 address, UInt32 length)
at Live_Tuner.Live_Tuner.Create_Axis()
at Live_Tuner.Live_Tuner.MapSelector_SelectedValueChanged(Object sender, EventArgs e)
at System.Windows.Forms.ListControl.OnSelectedValueChanged(EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedValueChanged(EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
at System.Windows.Forms.ComboBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34003 built by: FX45W81RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Live_Tuner
Assembly Version: 1.0.5322.17964
Win32 Version: 1.0.5322.17964
CodeBase: file:///C:/Users/mo/Documents/Evo/Tephra%20V2/Live%20Tuner/Live_Tuner.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34003 built by: FX45W81RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.