When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I have a weird problem, and seem unable to log with EvoScan using either Mode23 or RAX v3. I bought the car (2013 Euro Evo X) in January this year 2nd hand - it came with a 56910011 ROM file, so I bench flashed it to 56910009 successfully. However, when I enabled Mode23 logging none of the EvoScan Mode23 gave accurate data - each one changed things slightly.
So I tried enabling RAX v3 (after some headscratching around the include statement only being able to be used once per definition file...I ended up daisy chaining the RAX definition to my evo10base XML. However, using EvoScan, I now just get static data when logging for each item (ie; TPS is at 13 degrees and never changes with throttle position, MAF is always at 0).
To confirm - I do not need to enable Mode23 to use RAX v3? I am using latest versions of ECUFlash and EvoScan - ECUFlash comes with mode23 already present (but disabled) by default. Should I be trying to source some earlier definition files?
My GTA is running an Evo 4 RS rear. All 3 lights came on after a leadfoot uphill fang through very tight bends
that are Very close together. Code 82 pump. My acd maps are pretty aggressive and I'd say the pump couldn't
recover quick enough to supply enough pressure. My rom is an R1 I modded using a Merlin modified xml.
I zeroed all the right columns in all the ayc subjects. Logging shows the ayc is not turning on/off L and R
I've yet to tackle those bends again. Prob in another month.
I can't replicate the code around the typical local streets because the bends aren't close together.
Anyone running acd with ayc come across the 3 lights coming on ? Off/On clears it.
I have a weird problem, and seem unable to log with EvoScan using either Mode23 or RAX v3. I bought the car (2013 Euro Evo X) in January this year 2nd hand - it came with a 56910011 ROM file, so I bench flashed it to 56910009 successfully. However, when I enabled Mode23 logging none of the EvoScan Mode23 gave accurate data - each one changed things slightly.
So I tried enabling RAX v3 (after some headscratching around the include statement only being able to be used once per definition file...I ended up daisy chaining the RAX definition to my evo10base XML. However, using EvoScan, I now just get static data when logging for each item (ie; TPS is at 13 degrees and never changes with throttle position, MAF is always at 0).
To confirm - I do not need to enable Mode23 to use RAX v3? I am using latest versions of ECUFlash and EvoScan - ECUFlash comes with mode23 already present (but disabled) by default. Should I be trying to source some earlier definition files?
Many thanks, Richard
To answer this for posterity - to get Mode23 working I just had to select the Golden 2011 USDM v2 EVOX definition in EvoScan, DOH! However, I'd still like to know whether I need Mode23 enabled in the ROM to get RAX v3 working too?
To answer this for posterity - to get Mode23 working I just had to select the Golden 2011 USDM v2 EVOX definition in EvoScan, DOH! However, I'd still like to know whether I need Mode23 enabled in the ROM to get RAX v3 working too?
Thanks, Richard
Yes you do. RAX Fast Logging needs mode23 enabled.
hi im stuck in the install phase my old laptop crashed and i am trying to install everything from scratch
can someone tell me how i can install both rax 3 and tephramod 3 together in the evo folder?
here is a step by step list of what i have done so far
1 installed ecuflash and evoscan
2 copied rax files to the ecuflash folder
3 set evoscan to obd 2.0 2006 can and selected rax fast logging
4 from the tephrax3mod files ran the registry
5 copied the tephramod-53040310.xml file to ecuflash Evo directory
6 left the bin file to the desktop for later
7 from these 3 files
tephramod-53040310.xml
53040010 2008 EDM lancer evolution x 5mt.xml
53040010 rax3 patch.xml
which file am i supposed to edit and add the line "<include>RAX53040010</include>
and if it is in "53040010 2008 edm lancer evolution x 5mt.xml" file should I keep the code"<include>evo10base</include> and the new line under it or do I overwrite it?
8 after that I'm supposed to download my base map and save it then upload the bin file from tephra to my car correct?
hi im stuck in the install phase my old laptop crashed and i am trying to install everything from scratch
can someone tell me how i can install both rax 3 and tephramod 3 together in the evo folder?
here is a step by step list of what i have done so far
1 installed ecuflash and evoscan
2 copied rax files to the ecuflash folder
3 set evoscan to obd 2.0 2006 can and selected rax fast logging
4 from the tephrax3mod files ran the registry
5 copied the tephramod-53040310.xml file to ecuflash Evo directory
6 left the bin file to the desktop for later
7 from these 3 files
tephramod-53040310.xml
53040010 2008 EDM lancer evolution x 5mt.xml
53040010 rax3 patch.xml
which file am i supposed to edit and add the line "<include>RAX53040010</include>
and if it is in "53040010 2008 edm lancer evolution x 5mt.xml" file should I keep the code"<include>evo10base</include> and the new line under it or do I overwrite it?
8 after that I'm supposed to download my base map and save it then upload the bin file from tephra to my car correct?
thanks
__________________
Hiya. Those EcuFlash "include" statements haven't got any better over the years, unfortunately. You can only have ONE "include" per xml file.
You need to keep evo10base. I'd honestly say the easiest thing to do is just to drop the RAX "include" into evo10base itself. While that's not exactly flexible in terms of catering for multiple ROM types (totally INflexible, really), it has the advantage of actually working.
Let us know when you get to the point when you can see the extra "RAX3" items in the EcuFlash data list, once you've loaded up your ROM.
Rich
Last edited by richardjh; Jul 17, 2019 at 04:04 PM.
Hiya. Those EcuFlash "include" statements haven't got any better over the years, unfortunately. You can only have ONE "include" per xml file.
You need to keep evo10base. I'd honestly say the easiest thing to do is just to drop the RAX "include" into evo10base itself. While that's not exactly flexible in terms of catering for multiple ROM types (totally INflexible, really), it has the advantage of actually working.
Let us know when you get to the point when you can see the extra "RAX3" items in the EcuFlash data list, once you've loaded up your ROM.
Rich
thanks mate that's what I was thinking too but didn't know if it would work t I'll go try it out and update here if they show up
[edit] - Update on April 16th 2019 - Moving to full release.
Hi folks.
I've re-engineered my Ralliart and Evo X (RAX) ROM patches. RAX v3 now supersedes older patches. Some changes are "behind the scenes" stuff only, plus there is an entire new patch for us to play with.
Changes from RAX v1 and v2...
I've moved patch code/data locations around a bit, to ensure RAXv3 is usable with tephraXMOD V3.
I've recoded most patches to make them a bit easier for me to auto-generate using a bulk XML file output program. This adds a significant degree of consistency to patch generation, as you can imagine. I'm thinking of calling it SkyNet. Let's just hope it doesn't become self-aware!
The "SST Upshift Boost Management" patch has been tweaked so as to allow us to configure a hard cap EC limit mid-upshift. For example, if your EC is +8% when you upshift, this patch can apply a hard EC cap of, say, 4% through the WOT upshift, to moderate the possible boost spike. Previously, this patch was hardcoded to enforce 0% EC during WOT upshift.
Because of the relocation work, it is NOT possible to simply flick from older RAX to RAXv3 via those easy-to-use EcuFlash "disabled/enabled" switches...
All old RAX Patch items need to be removed from the ROM.
All old RAX Patch xml files need to be removed from the EcuFlash data file folders.
Only THEN should you copy in the new RAX3 xml file, restart EcuFlash, and patch your ROM.
And now, it's red text time! My favourite part!...
LIABILITY NOTICE
Incorrectly patched instructions can be extremely dangerous to your engine management, and can lead to severe engine damage. You assume ALL responsibility for the integrity of your ECU and engine management, vehicle safety, etc. If you are not confident in the procedures/data involved in the RAX Patch, do not make any change to your vehicle ECU's ROM image.
SAFETY NOTICE
It is important to testing any engine management change in a safe and thorough manner. Tests recommended in the related document are a guideline only. You assume ALL responsibility for the testing approach taken when using ECU ROM patches.
Now, here's some info on the brand new patch I've written in RAX3...
RAX3: Smarter WGDC Error Correction
RAX3 “Smarter EC” makes one simple revision to ECU boost Error Correction:
Upward Error Correction no longer occurs when Boost Levels are RISING
This makes it easier to tune upward EC adjustment to provide rapid, effective correction of below-target boost, without overshooting the target during the recovery phase.
The following diagram shows how EC remains unchanged throughout the spool-up phase, and once boost begins to recover after the post-peak drop.... because upward EC no longer occurs when boost levels are rising:
Sensible Testing Approach
Some ROM IDs have been tested and verified. Some haven't. See the list below to see where we stand.
It is REALLY important you keep your wits about you when trialling an "Untested" ECU patch. An "Untested" patch is not something you slap into your ROM, think "she'll be right, mate", and drive off to work with.
There is a detailed PDF on RAX3 - see attachment. Pay particular attention to the section on TESTING. Most patches have diagnostic logging items built into them, enabling you to watch the patch logic at work using EvoScan.
Don't cut corners. Don't take unnecessary leaps of faith when you can systematically verify correct operation through testing and diagnostics.
If you test out a previously "Untested" patch, please let me know, so I can update the list below.
Testing Status
I'll be noting here the ROM versions (and patches) that have been tested, and by whom. You'll be able to see at a glance what's been trialled successfully.
Evolution X SST - RAX3 ROM ID
52370024.xml - Untested
52690021.xml - Untested
53050006.xml - Untested
53050009.xml - Untested
53050012.xml - TESTED OK - ALL PATCHES - TESTED OK with tephraXModv3 - polik71
54070007.xml - Untested
55580005.xml - Untested
56900007.xml - Untested
56900009.xml - Untested
56880009.xml - Untested
56900009.xml - Untested
56920006.xml - Untested
56920008.xml - TESTED OK - ALL PATCHES with tephraXModv3 - pf
57140001.xml - TESTED OK - ALL PATCHES - psfp
57140003.xml - TESTED OK - ALL PATCHES - psfp
58020005.xml - Untested
59590004.xml - Untested
Evolution X 5MT - RAX3 ROM ID
50845084.xml - Untested
52360018.xml - TESTED OK - ALL PATCHES - RS200Z
52680002.xml - TESTED OK - ALL PATCHES - S.D.
52680015.xml - TESTED OK - ALL PATCHES with tephraXModv3 - itzwolf
52680024.xml - Untested
53040010.xml - TESTED OK - ALL PATCHES - A&C S
54060007.xml - Untested
55570005.xml - Untested
56180001.xml - Untested
56870008.xml - Untested
56890007.xml - Untested
56890009.xml - Untested
56890013.xml - TESTED OK - ALL PATCHES - nonschlont. TESTED OK with tephraXModv3 - itzwolf
56910007.xml - Untested
56910009.xml - TESTED OK - ALL PATCHES - with tephraXModv3 - crimson red
58010005.xml - Untested
59580004.xml - TESTED OK with tephraXModv3 - razorlab
Ralliart SST - RAX3 ROM ID
53590012.xml - Untested
53600010.xml - Untested
53610010.xml - Untested
53610013.xml - TESTED OK - ALL PATCHES - with tephraModv3 - richardjh
55590006.xml - Untested
56940007.xml - Untested
56950006.xml - Untested
58030005.xml - Untested
58640002.xml - (problem found - fixed on May 6th 2017) - TESTED OK - ALL PATCHES - psfp
59570004.xml - Untested
For questions, post 'em here, or email me... raxpatch {at} gmail {dot} com
Has anyone come across RAX rom or xml for 2010 JDM Evo X SST 561900002?
Just wanted to monitor my SST Temps and activating Mode23 didn't work on TorquePro with MUTv2
Any help would be highly appreciated!
yea MUTv2 hasn't worked since Android 8.0. Maybe try Android 7 if still interested. I cant figure this out either. I would think we could address the memory locations that EVOscan uses to get the SST info, but they are listed as "CAN28-0" and the like, and those arent hex addresses. I have no idea how to figure out where these values are in memory...
Racecapture supports RAX patch, as well as custom PIDS via can, but we would need to figure out the addresses that CAN28-0 and CAN35-0 is actually referencing.
I think a lot of the helpful people got worn out helping people. This info was probably around at one point, but sites die and so does the information.
Hi. For SST temperature monitoring as well as knocks you don't need any plugins for TorquePro. Below I will share my findings, so just use these custom PIDs in TorquePro:
1 TC-SST Temperature
PID: 2123
Equation: A-50
Unit type: deg C
Header: TCM or 7E1
Min: -40, Max: 140
2 KnockSum
PID: 2108
Equation: B (2nd byte)
Unit type: count
Header: Auto
Min: 0, Max: 36
Feb 27, 2019, 09:39 AM
