"RAX Patch Version 3 - Official and Latest"
#32
Evolving Member
iTrader: (1)
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?
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?
#33
Evolved Member
Thread Starter
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?
Cheers,
Rich
#36
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.
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.
#37
Evolved Member
Thread Starter
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 first post's ZIP file attachment of RAX v3 XMLs fixes the issue.
Rich
#38
Evolved Member
Thread Starter
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.
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.
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
#40
Evolved Member
Thread Starter
Rich
#42
Evolved Member
Thread Starter
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
#43
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
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
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
#44
Evolved Member
Thread Starter
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
Thanks,
Frank
Rich
#45
Evolving Member
iTrader: (1)
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.
When i got back down to about 2500 feet everything seemed to be working fine, but please let me know.