Notices

"RAX Patch Version 3 - Official and Latest"

Thread Tools
 
Search this Thread
 
Old Mar 8, 2017, 06:45 AM
  #31  
Evolving Member
iTrader: (1)
 
ddlopresti's Avatar
 
Join Date: Nov 2011
Location: New York
Posts: 466
Received 19 Likes on 18 Posts
deleted

Last edited by ddlopresti; Mar 10, 2017 at 10:49 AM.
Old Mar 10, 2017, 10:48 AM
  #32  
Evolving Member
iTrader: (1)
 
ddlopresti's Avatar
 
Join Date: Nov 2011
Location: New York
Posts: 466
Received 19 Likes on 18 Posts
With the barometric boost compensation since its either on or off, is there anything to tweak or it just works out of the box? I noticed that the barometer readings when i log only change after i turn the car off and back on, is that how it is supposed to be?

For upward correction, I'm using the base values atm that came with the patch, and i notice a max upward correction of about 1.5 (which happens rarely), is the best practice just to slowly increase this until you hit what you want if you are close to your target psi rather than adjusting the base wastegate tables?
Old Mar 12, 2017, 07:21 AM
  #33  
Evolved Member
Thread Starter
 
richardjh's Avatar
 
Join Date: Oct 2010
Location: Australia
Posts: 2,447
Received 14 Likes on 13 Posts
Originally Posted by ddlopresti
With the barometric boost compensation since its either on or off, is there anything to tweak or it just works out of the box? I noticed that the barometer readings when i log only change after i turn the car off and back on, is that how it is supposed to be?
Well, you need to set "Atmospheric Boost" to 0 (under "Direct Boost" items).

Originally Posted by ddlopresti
For upward correction, I'm using the base values atm that came with the patch, and i notice a max upward correction of about 1.5 (which happens rarely), is the best practice just to slowly increase this until you hit what you want if you are close to your target psi rather than adjusting the base wastegate tables?
Sorry, I'm not sure what you mean, exactly!

Cheers,

Rich
Old Mar 13, 2017, 08:11 AM
  #34  
Evolving Member
iTrader: (1)
 
ddlopresti's Avatar
 
Join Date: Nov 2011
Location: New York
Posts: 466
Received 19 Likes on 18 Posts
Originally Posted by richardjh
Well, you need to set "Atmospheric Boost" to 0 (under "Direct Boost" items).





Sorry, I'm not sure what you mean, exactly!

Cheers,

Rich
I mean, the most upward correction in the wastegate i've seen is 1.5 in my logs

Ok, after setting to 0 it does everything else automatically right? And is it normal to have to turn the car off and on the re set the barometric value?
Old Mar 13, 2017, 08:33 AM
  #35  
EvoM Guru
iTrader: (8)
 
RazorLab's Avatar
 
Join Date: Aug 2003
Location: Mid-Hudson, NY
Posts: 14,065
Received 1,038 Likes on 760 Posts
Originally Posted by ddlopresti
I mean, the most upward correction in the wastegate i've seen is 1.5 in my logs
Do you also have smart EC turned on? If so, the upward correction will only kick in if the boost is dropping, never when it's rising or stable.

Also depends on values in your upward correction vs TPS table and standard correction table.
Old Apr 4, 2017, 03:16 PM
  #36  
Newbie
 
Rasperin's Avatar
 
Join Date: Feb 2017
Location: Bothell, WA
Posts: 73
Received 3 Likes on 3 Posts
Grabbed these for 55570306 (aka TephraV3 of 55570005). Logging seems to be working fine but IAT seems whacky, and when I take the values from my old TephraV1 and try to stuff them in there, well what you would expect to happen when someone does that happens. Trying to feed the engine any load greater than 10% results in the engine cutting itself and bunking like a bronco.

Potentially Pertinent information IAT Adjusted BWGDC (default before modifying them) (offset: d0064 to Temp: d004a)
F temp: 1792 for all 7 rows
WGDC Change: 63.5 for all 7 rows

Edit: As a note, the console gave a timing belt error while bucking. Errors immediately went away, flashed back without IAT and all is well.

Last edited by Rasperin; Apr 6, 2017 at 10:09 AM.
Old May 6, 2017, 03:19 AM
  #37  
Evolved Member
Thread Starter
 
richardjh's Avatar
 
Join Date: Oct 2010
Location: Australia
Posts: 2,447
Received 14 Likes on 13 Posts
58640002 XML had a problem; the MUT address in my EcuFlash's XML file was wrong, and I'd just used it as-is, without checking.

The first post's ZIP file attachment of RAX v3 XMLs fixes the issue.

Rich
Old May 6, 2017, 03:33 AM
  #38  
Evolved Member
Thread Starter
 
richardjh's Avatar
 
Join Date: Oct 2010
Location: Australia
Posts: 2,447
Received 14 Likes on 13 Posts
Originally Posted by Rasperin
Grabbed these for 55570306 (aka TephraV3 of 55570005). Logging seems to be working fine but IAT seems whacky, and when I take the values from my old TephraV1 and try to stuff them in there, well what you would expect to happen when someone does that happens. Trying to feed the engine any load greater than 10% results in the engine cutting itself and bunking like a bronco.

Potentially Pertinent information IAT Adjusted BWGDC (default before modifying them) (offset: d0064 to Temp: d004a)
F temp: 1792 for all 7 rows
WGDC Change: 63.5 for all 7 rows

Edit: As a note, the console gave a timing belt error while bucking. Errors immediately went away, flashed back without IAT and all is well.
Hi. Sorry for the late reply!

The table "IAT Adjusted BWGDC (Requires RAX3)" is a RAX-specific table.
If it contains "63.5" values, it hasn't been initialised at all. That probably means the relevant patch item hasn't been changed from "Data absent" to "Data PRESENT". That item is:

RAX IAT Adjusted BWGDC: Initial Scale/Table Data

You can't just SET the values in that table manually; not if they are "63.5" to begin with. There is more table/scale data behind the scenes which comes in when you set the relevant patch item to "Data PRESENT".


If you are confused, or are having issues after doing everything right, feel free to email me the ROM to check:

raxpatch {at} gmail {dot} com


Rich
Old May 28, 2017, 04:43 AM
  #39  
Evolved Member
Thread Starter
 
richardjh's Avatar
 
Join Date: Oct 2010
Location: Australia
Posts: 2,447
Received 14 Likes on 13 Posts
First post XMLs updated. Added 53590012 and 56880009 to the RAX v3 family.

Rich
Old Jun 18, 2017, 03:20 PM
  #40  
Evolved Member
Thread Starter
 
richardjh's Avatar
 
Join Date: Oct 2010
Location: Australia
Posts: 2,447
Received 14 Likes on 13 Posts
Originally Posted by richardjh
58640002 XML had a problem; the MUT address in my EcuFlash's XML file was wrong, and I'd just used it as-is, without checking.

The first post's ZIP file attachment of RAX v3 XMLs fixes the issue.

Rich
The "fixed" version of 58640002 has been successfully tested by psfp (and friend). All good!

Rich
Old Jul 7, 2017, 01:00 PM
  #41  
Newbie
 
framirezz1025's Avatar
 
Join Date: Jun 2017
Location: new york
Posts: 3
Likes: 0
Received 0 Likes on 0 Posts
Id be wiling to test this patch on 5958006 if you make one. USDM 2015 Evo X GSR 5MT
Attached Files
File Type: bin
5958006NOTUNE.bin (1.00 MB, 0 views)
Old Jul 7, 2017, 04:04 PM
  #42  
Evolved Member
Thread Starter
 
richardjh's Avatar
 
Join Date: Oct 2010
Location: Australia
Posts: 2,447
Received 14 Likes on 13 Posts
Originally Posted by framirezz1025
Id be wiling to test this patch on 5958006 if you make one. USDM 2015 Evo X GSR 5MT
Hi there.

Is there a specific reason or advantage for using 59580006 over 59580004?

59580004 is supported by RAX v3 already. Also, tephra's "XMod V3" is done for 59580004.

If there's something in particular that warrants using 0006 over 0004, sure, I'm happy enough to generate RAX for it... but as of this moment it's not "in the list".

Cheers,

Rich
Old Jul 8, 2017, 07:58 AM
  #43  
Newbie
 
framirezz1025's Avatar
 
Join Date: Jun 2017
Location: new york
Posts: 3
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by richardjh
Hi there.

Is there a specific reason or advantage for using 59580006 over 59580004?

59580004 is supported by RAX v3 already. Also, tephra's "XMod V3" is done for 59580004.

If there's something in particular that warrants using 0006 over 0004, sure, I'm happy enough to generate RAX for it... but as of this moment it's not "in the list".

Cheers,

Rich
Hi Rich,

The car was originally on 52680002 FE rom I was having issues logging a few parameters with mode 23 so I switched to the 5958006 GSR rom. I see now that the patch was already generated for the cars original rom so I'm going to try that again and see if it fixes my original issue.

On another note I used Rax5958004 patch on 5958006 rom and it seems to be working as far as ecuflash is concerned. I guess the addresses between the two roms must be close to identical for the data for the patch. Though I haven't loaded that patched rom to the car yet.

Thanks,
Frank
Old Jul 9, 2017, 07:34 AM
  #44  
Evolved Member
Thread Starter
 
richardjh's Avatar
 
Join Date: Oct 2010
Location: Australia
Posts: 2,447
Received 14 Likes on 13 Posts
Originally Posted by framirezz1025
On another note I used Rax5958004 patch on 5958006 rom and it seems to be working as far as ecuflash is concerned. I guess the addresses between the two roms must be close to identical for the data for the patch. Though I haven't loaded that patched rom to the car yet.

Thanks,
Frank
Okay, I've worked through it, and can confirm that 59580004 RAX Patch v3 can be used on 59580006 as well. Everything the patch needs is the same.

Rich
Old May 9, 2018, 11:52 AM
  #45  
Evolving Member
iTrader: (1)
 
ddlopresti's Avatar
 
Join Date: Nov 2011
Location: New York
Posts: 466
Received 19 Likes on 18 Posts
Sorry to bring this thread back from the dead, but i drove at 4500 feet this past weekend and noticed that i was under boosting by about 4psi and the turbo was spooling super late. Its possible my turbo just can't keep up, but what can i check in the tune/logs to make sure that the barometric sensor based boost is turned on properly and working?

When i got back down to about 2500 feet everything seemed to be working fine, but please let me know.


Quick Reply: "RAX Patch Version 3 - Official and Latest"



All times are GMT -7. The time now is 11:54 PM.