TephraMod V7
Oct 10, 2009, 06:57 PM
#76
More questions pertaining to everything under Turbo Boost Single Solenoid. Do the independent gear based BDEL and base wastegate duty tables reference the original TBEC table if our target load is off for each gear? If so why include the original RPM crossover points for low and high gear ranges and well as the BDEL(low and high gear ranges) and BWGDC(low and high gear ranges)? Also Do the WGDC correction intervals for high and low range apply to the independent gears?
as far as the JDM map sensor which addresses do we use for the MAP sensor definitions.
hope it makes sense. trying to get a handle on what/how things work now
thanks again
as far as the JDM map sensor which addresses do we use for the MAP sensor definitions.
hope it makes sense. trying to get a handle on what/how things work now
thanks again
Last edited by RALLInspired; Oct 10, 2009 at 07:22 PM. Reason: clarrification
Oct 10, 2009, 07:25 PM
#79
Oct 10, 2009, 07:40 PM
#81
Evolving Member
Join Date: Sep 2009
Location: Creston, Iowa
Posts: 123
Likes: 0
Received 0 Likes
on
0 Posts
I understand that it is set up for psi based boost and how to switch it over to load based. Im just trying to figure out what "load" the load based follows. The stock setting or 2 byte?
Oct 10, 2009, 07:51 PM
#83
It used the stock setting. You should never use 2 byte load for anything anymore. Tephra uses 1 byte load. Do some searching so you understand how that works too.
Oct 10, 2009, 08:36 PM
#85
Tested V7 out today. Got an Idle Control system code, which I am sure is my BISS, I readjusted it a few minutes ago, but still have to go do a drive to verify. Gave myself a scare when I hit full boost and hit boost cut 
I forgot to change that part of the map... Of course getting the overly rich idle condition with EGR disabled... pretty annoying. Other than that it is driving fine. I haven't been able to go out and actually tune the map though... I will be doing that next week...
I forgot to change that part of the map... Of course getting the overly rich idle condition with EGR disabled... pretty annoying. Other than that it is driving fine. I haven't been able to go out and actually tune the map though... I will be doing that next week...
Oct 10, 2009, 08:36 PM
#86
Evolving Member
Join Date: Sep 2009
Location: Creston, Iowa
Posts: 123
Likes: 0
Received 0 Likes
on
0 Posts
Use the def. in the XML to switch it over, look at the picture in my post it shows you what the values should be if you want load vs. psi based control.
It used the stock setting. You should never use 2 byte load for anything anymore. Tephra uses 1 byte load. Do some searching so you understand how that works too.
It used the stock setting. You should never use 2 byte load for anything anymore. Tephra uses 1 byte load. Do some searching so you understand how that works too.
Oct 10, 2009, 09:00 PM
#88
also which MAP sensor definitions should we use.... some of the addresses still work for this ROM (map test 1 through 4) but both EGR MAP check and MAP scaling for Baro are off for me.
Oct 10, 2009, 09:09 PM
#89
What I think Chris meant is, from the factory, the boost control is load based. However, the load value the boost control system uses is SLIGHTLY different from the load value the timing/fuel maps use. This is what he is referring to as the "stock" boost control system.
This was later patched to reference the same load value that the timing/fuel maps use. This is what he is referring to as the "2 byte" boost control system. Although that's a bit misleading/incorrect. What he should have said is the "common load"or "standard load" boost control system. But yes, the values of this "common load" does match up with what we all came to know as "2 byte load" and that's the point.
As far as 2 byte vs. 1 byte... the difference is only for logging. They both reference the same value, as far as the ECU is concerned for the various maps and for the actual tune. 1 byte exists as a logging improvement only.
This was later patched to reference the same load value that the timing/fuel maps use. This is what he is referring to as the "2 byte" boost control system. Although that's a bit misleading/incorrect. What he should have said is the "common load"or "standard load" boost control system. But yes, the values of this "common load" does match up with what we all came to know as "2 byte load" and that's the point.
As far as 2 byte vs. 1 byte... the difference is only for logging. They both reference the same value, as far as the ECU is concerned for the various maps and for the actual tune. 1 byte exists as a logging improvement only.
Last edited by recompile; Oct 10, 2009 at 09:11 PM.
Oct 10, 2009, 09:38 PM
#90
Account Disabled
iTrader: (8)
Join Date: Sep 2007
Location: Hayward
Posts: 3,366
Likes: 0
Received 0 Likes
on
0 Posts
I am looking for an FTP site so I can manage and upload/delete the files myself. Takes less hassle and human error out to make sure the most recent files are there and what not. I am OK for now but by the end of this month I need to find somewhere to put them....
If it comes down to it when we have been running this for a while and there are no more issues that come up. I will send you them and you can host them since we won't be changing anything anytime soon.
If it comes down to it when we have been running this for a while and there are no more issues that come up. I will send you them and you can host them since we won't be changing anything anytime soon.
Send me a PM.
- Bryan